Feature request: MessagePackParser

The option format now accepts msgpack for output plugins via MessagePackFormatter at #479. In the opposite direction, it doesn't seems that it accepts msgpack for most of input plugins. The pair of MessagePackParser and MessagePackFormatter would show a clean symmetry for both input and output plugins. In_forward, in_exec and in_http do implement it, respectively.
The msgpack parser allows for users to send a compact log with time and tag claimed by the source. I'd like to send a log via UDP which is simple, in my case. It'd be great when in_udp could accept msgpack format as well as in_forward does. On another case, in_tail could import log files dumped by MessagePackFormatter.
I'm not sure that it's possible to implement the MessagePackParser as the current parses might request source as a string but not a binary, however.

I'm not sure that it's possible to implement the MessagePackParser as the current parses might request source as a string but not a binary, however.

Yes, this point is difficult problem. Current Parser is used with text based protocol.
For example, in_tail, in_udp and in_tcp assumes incoming events are separated by \n.
If we support msgpack format, we should change input plugins to support binary protocol before.

Thank you for your reply.
I'm closing this request as I misunderstood about MessagePackFormatter. It dumps only record but not the trio of [tag, time, record]. It could not dump (or journal) the whole stream  of events, then.
I found a simple workaround to import a log file dumped by MessagePackFormatter, anyway. The fluent-cat looks to accept the same format of series of multiple records.
fluent-cat tag --msgpack < dump.log

I guess fluent-cat above is enough in most cases to import a dumped log. The original tag and time of events should be included within the records before dumped and restored after imported.

I'd like to send a log via UDP which is simple, in my case.

I'll use JSON on UDP, then. A UDP packet still has a limit for size of its payload. It does not work with a long event stream dumped. JSON on UDP could be enough for a single event.


Restore event tracking for Give

Regression caused by #1313
Restores back to the setup that we've been using until now. Otherwise historical and future data won't match.

@alexleventer can you take a look?

@alexleventer can you take a look?

@cptnanon can you take a look as well please

@alexleventer can you take a look?

@cptnanon can you take a look as well please

Looks good. It only needs to include the changes from #1477.


Automate testing of links and accessibility

Add automated TravisCI tests for the following aspects of the UI Guide HTML:

[ ] Accessibility audit of pages to ensure they are WCAG2AA compliant (use pa11y) Ref #57
[ ] Audit links and image src's to ensure they are valid (use broken link detector)

For broken-link-checker npm package, you can use the following command to check a given page comprehensively:
$ blc -g --filter-level 3 http://localhost:49627/


sorting array for cpp

Sort an Array in C++ using STL function sort()

your repo is not adding any value to this repo ! . try to come up with a better solution


GROMACS File Readers

@JensWehner you had trouble with gromacs file readers before, did you ever get the problem fixed. I'm getting tones of linker errors now as well.

I'm wondering if all the gmx files now need a refactor.

I'm getting tones of linker errors now as well.

Any details?

I had an old version of a gromacs libarray around, which caused those errors. Everything is fine now, it was a user error.

We might need to update cmake,
Found GROMACS: /usr/lib/x86_64-linux-gnu/libgromacs_d.so (found suitable version "2019.6", minimum required is "2018")
Here is a list of the errors
../libcsg/libvotca_csg.so.7: undefined reference to gmx_mtop_t::gmx_mtop_t()' ../libcsg/libvotca_csg.so.7: undefined reference to read_first_frame(gmx_output_env_t const*, t_trxstatus**, char const*, t_trxframe*, int)'
../libcsg/libvotca_csg.so.7: undefined reference to open_trx(char const*, char const*)' ../libcsg/libvotca_csg.so.7: undefined reference to close_trx(t_trxstatus*)'
../libcsg/libvotca_csg.so.7: undefined reference to output_env_init(gmx_output_env_t**, gmx::IProgramContext const&, time_unit_t, bool, xvg_format_t, int)' ../libcsg/libvotca_csg.so.7: undefined reference to read_next_frame(gmx_output_env_t const*.,. /t_trxstatuslibcsg*/,libvotca_csg.so.7 :t_trxframe undefined) 'reference
.to. /libcsggmx_mtop_t/:libvotca_csg.so.7::gmx_mtop_t (undefined) 'reference  .to. /libcsggmx_mtop_t/:libvotca_csg.so.7::~ gmx_mtop_tundefined( )reference'
to. ./read_first_framelibcsg(/gmx_output_env_tlibvotca_csg.so.7 :const *undefined,  referencet_trxstatus *to* , write_trxframechar( t_trxstatusconst*,,  t_trxframet_trxframe**,,  gmx_conect_tint*))''
.collect2: error: ld returned 1 exit status
./libcsg/libvotca_csg.so.7: undefined reference to open_trx(char const*, char const*)' ../libcsg/libvotca_csg.so.7: undefined src/tools/CMakeFiles/csg_property.dir/build.make:98: recipe for target 'src/tools/csg_property' failed referencemake[2]: *** [src/tools/csg_property] Error 1  toCMakeFiles/Makefile2:939: recipe for target 'src/tools/CMakeFiles/csg_property.dir/all' failed  make[1]: *** [src/tools/CMakeFiles/csg_property.dir/all] Error 2 make[1]: *** Waiting for unfinished jobs....
close_trx(t_trxstatus*)'
../libcsg/libvotca_csg.so.7: undefined reference to output_env_init(gmx_output_env_t**, gmx::IProgramContext const&, time_unit_t, bool, xvg_format_t, int)' ../libcsg/libvotca_csg.so.7: undefined reference to read_next_frame(gmx_output_env_t const*, t_trxstatus*, t_trxframe*)'
../libcsg/libvotca_csg.so.7: undefined reference to gmx_mtop_t::~gmx_mtop_t()' ../libcsg/libvotca_csg.so.7: undefined reference to write_trxframe(t_trxstatus*, t_trxframe*, gmx_conect_t*)'
collect2: error: ld returned 1 exit status
src/tools/CMakeFiles/csg_resample.dir/build.make:98: recipe for target 'src/tools/csg_resample' failed
make[2]: *** [src/tools/csg_resample] Error 1
CMakeFiles/Makefile2:976: recipe for target 'src/tools/CMakeFiles/csg_resample.dir/all' failed
make[1]: *** [src/tools/CMakeFiles/csg_resample.dir/all] Error 2

I'll look into this to make sure I'm not doing something wonky with the files in my system library/includes.

@junghans what version of gromacs is being used in the ci?

We build against:

Gromacs-2019.6 on Fedora
Gromacs 2018.7 on Ubuntu-18.04
Gromacs-2020 on Ubunutu 20.04
lastest Gromacs-2019/2020/2021 (single/double) in our containers

There is a problem with the FindGromacs cmake module. Recently the gromacs has switched the api versioning system. Current versions of gromacs are now versioning starting at version 0 which breaks our current cmake module.

Also using the spack gromacs causes problems because it is built with openmpi, gromacs_mpi and libgromacs_mpi need to be added as possible options. I'm working on a solution but welcome feedback.

Also using the spack gromacs causes problems because it is built with openmpi, gromacs_mpi and libgromacs_mpi need to be added as possible options. I'm working on a solution but welcome feedback.

There is something wrong, in spack votca-csg depends on gromacs without mpi: https://github.com/spack/spack/blob/a20ba315f57bcbbb73838d1b67a15a9e14d580cd/var/spack/repos/builtin/packages/votca-csg/package.py#L35

There is a problem with the FindGromacs cmake module. Recently the gromacs has switched the api versioning system. Current versions of gromacs are now versioning starting at version 0 which breaks our current cmake module.

Remember that we have two mechanisms to detect gromacs:
https://github.com/votca/csg/blob/master/CMakeLists.txt#L86-L89
First we try gromacs-2021 via cmake config and then <=gromacs-2020 via our custom find module.

Plus whatever you do make sure we can still use gromacs-2018/2019 as this is needed for the coarse-graining part.

First we try gromacs-2021 via cmake config and then <=gromacs-2020 via our custom find module.

I have a question why can't we use the config method for also finding earlier versions?

First we try gromacs-2021 via cmake config and then <=gromacs-2020 via our custom find module.

I have a question why can't we use the config method for also finding earlier versions?

Because it is brocken in earlier versions.

Fixed in #705


Don't allow NUL bytes in indexed strings

Might be enough to allow us to continue to index primary keys by default if we're confident that embedded nulls are the only problem, and even if we do make it opt-in we need this check until string indexes are fixed.
@alazier

Are we sure string properties without indexes work properly with NULL bytes? It would be great if we had a test which was confirmed to crash when using indexes so we could confirm that NULL bytes work otherwise. If not we will need to do this check for all string properties.

Added this check in core instead.


workspace: when setting post-release, dependents not updated

With your help in the previous issue, I could cut a 0.5.0 release of chars, thanks for that! Unfortunately, the process failed when it was bumping the dev versions for the two crates:
:;    cargo release minor --verbose
[2020-03-20T13:38:50Z DEBUG] Files changed in chars_data since chars_data-v0.4.1: [
        "/Users/asf/Hacks/chars/chars_data/chars_data/Cargo.toml",
        "/Users/asf/Hacks/chars/chars_data/chars_data/data/entities/LICENSE",
        "/Users/asf/Hacks/chars/chars_data/chars_data/data/entities/README.md",
        "/Users/asf/Hacks/chars/chars_data/chars_data/data/entities/entities.json",
        "/Users/asf/Hacks/chars/chars_data/chars_data/data/entities/retrieve.sh",
        "/Users/asf/Hacks/chars/chars_data/chars_data/data/unicode/NameAliases.txt",
        "/Users/asf/Hacks/chars/chars_data/chars_data/data/unicode/UnicodeData.txt",
        "/Users/asf/Hacks/chars/chars_data/chars_data/src/ascii.rs",
        "/Users/asf/Hacks/chars/chars_data/chars_data/src/fst_generator.rs",
        "/Users/asf/Hacks/chars/chars_data/chars_data/src/unicode.rs",
    ]
[2020-03-20T13:38:50Z DEBUG] Files changed in chars since v0.4.1: [
        "/Users/asf/Hacks/chars/chars/chars/Cargo.toml",
        "/Users/asf/Hacks/chars/chars/chars/release.toml",
        "/Users/asf/Hacks/chars/chars/chars/src/display.rs",
        "/Users/asf/Hacks/chars/chars/chars/src/unicode/mod.rs",
        "/Users/asf/Hacks/chars/chars/chars/tests/human_names.rs",
    ]
    ]
Release
Release
  chars_data 0.5.0
  chars 0.5.0
? [y/N]
y
[2020-03-20T13:38:53Z INFO ] Update chars_data to version 0.5.0
[2020-03-20T13:38:53Z INFO ] Fixing chars's dependency on chars_data to `^0.5.0` (from `^0.4.1-dev`)
[2020-03-20T13:38:53Z INFO ] Update chars to version 0.5.0
[2020-03-20T13:38:54Z DEBUG] Substituting values for /Users/asf/Hacks/chars/chars/../CHANGELOG.md
[2020-03-20T13:38:54Z DEBUG] Substituting values for /Users/asf/Hacks/chars/chars/../CHANGELOG.md
[2020-03-20T13:38:54Z DEBUG] Substituting values for /Users/asf/Hacks/chars/chars/../CHANGELOG.md
[master 08543b9] Release {{version}} 🎉🎉
 4 files changed, 8 insertions(+), 6 deletions(-)
[2020-03-20T13:38:54Z INFO ] Running cargo publish on chars_data
    Updating crates.io index
   Packaging chars_data v0.5.0 (/Users/asf/Hacks/chars/chars_data)
   Verifying chars_data v0.5.0 (/Users/asf/Hacks/chars/chars_data)
   Compiling memchr v2.3.3
   Compiling fst v0.4.0
   Compiling lazy_static v1.4.0
   Compiling regex-syntax v0.6.17
   Compiling unicode-width v0.1.7
   Compiling quick-error v1.2.3
   Compiling unicode_names2 v0.4.0
   Compiling thread_local v1.0.1
   Compiling getopts v0.2.21
   Compiling aho-corasick v0.7.10
   Compiling regex v1.3.5
   Compiling regex v1.3.5
   Compiling chars_data v0.5.0 (/Users/asf/Hacks/chars/target/package/chars_data-0.5.0)
    Finished dev [unoptimized + debuginfo] target(s) in 24.07s
   Uploading chars_data v0.5.0 (/Users/asf/Hacks/chars/chars_data)
[2020-03-20T13:39:47Z INFO ] Waiting for publish to complete...
[2020-03-20T13:39:50Z INFO ] Running cargo publish on chars
    Updating crates.io index
   Packaging chars v0.5.0 (/Users/asf/Hacks/chars/chars)
   Verifying chars v0.5.0 (/Users/asf/Hacks/chars/chars)
  Downloaded chars_data v0.5.0
   Compiling memchr v2.3.3
   Compiling fst v0.4.0
   Compiling lazy_static v1.4.0
   Compiling unicode-width v0.1.7
   Compiling regex-syntax v0.6.17
   Compiling unicode_names2 v0.4.0
   Compiling quick-error v1.2.3
   Compiling byteorder v1.3.4
   Compiling thread_local v1.0.1
   Compiling getopts v0.2.21
   Compiling aho-corasick v0.7.10
   Compiling regex v1.3.5
   Compiling chars_data v0.5.0
   Compiling chars v0.5.0 (/Users/asf/Hacks/chars/target/package/chars-0.5.0)
    Finished dev [unoptimized + debuginfo] target(s) in 45.72s
   Uploading chars v0.5.0 (/Users/asf/Hacks/chars/chars)
[2020-03-20T13:40:38Z INFO ] Waiting for publish to complete...
[2020-03-20T13:40:44Z DEBUG] Creating git tag chars_data-v0.5.0
[2020-03-20T13:40:44Z DEBUG] Creating git tag v0.5.0
[2020-03-20T13:40:44Z INFO ] Starting chars_data's next development iteration 0.5.1-dev
[2020-03-20T13:40:44Z WARN ] Fatal: Invalid TOML file format: Error during execution of `cargo metadata`: error: no matching package named `chars_data` found
    location searched: /Users/asf/Hacks/chars/chars_data
    prerelease package needs to be specified explicitly
    chars_data = { version = "0.5.1-dev" }
    required by package `chars v0.5.0 (/Users/asf/Hacks/chars/chars)

So, looks like what's happening in that stage is:

It bumps the version of chars_data to 0.5.1-dev
It tries to bump the dependency in chars on chars_data to 0.5.1-dev
at that point, cargo refuses to find dev release version dependencies with no exact match -> error

I think I saw a cargo bug to that effect before, but I can't find it at the moment. I wonder if you can even do that bump with any in-flight versions of files. I imagine that the process might have to be:

Bump the version of chars_data to 0.5.1-dev but keep the previous Cargo.toml in place (save the update to a temp file, probably?)
Bump the dependency version in all dependent crates while cargo metadata still agrees, but also keep those old Cargo.toml files in place
Move all the temp files into place

This is a wild guess because I feel like the cargo book doesn't do a good job talking about prerelease
Currently, chars has
dev-version-ext = "dev"

I think that should be
dev-version-ext = "dev.0"

We append  dev-version-ext as-is and do not parse it or add the number to it.  I suspect the number is required.
Note the default is
dev-version-exit = "alpha.0"

FYI we only support bumping RC, Beta, and Alpha.  If Cargo supports Dev, we could add support for it.

I don't think that's what is happening. I have constructed a cargo workspace in the in-between state that cargo release leaves chars's workspace in https://github.com/antifuchs/cargo-dev-version-test-example (in the dev-version-half-done branch):

Two crates lib-foo and lib-bar.
lib-foo depends on lib-bar
lib-bar is at version 0.1.0-dev.0
lib-foo still declares its dependency on lib-bar at version 0.1.0.

Running cargo metadata in the lib-foo directory of that workspace errors out, because cargo refuses to resolve a dependency that's declared as having version 0.1.0 but the actual version in the path dependency is 0.1.0-dev.0 (or 0.1.0-dev, it doesn't matter).
I believe that's what's happening in the cargo release process for chars above: After cutting the releases, it bumps the version of chars_data to 0.5.0-dev, then cargo in chars can't find the original dependency (declared to be 0.5.0) anymore, because it's one with alphabetic parts in the version numbers.
I'm pretty sure this is cargo's pre-release prevention kicking in here... If you only-numeric components like 0.1.1, everything in those in-between states keeps fitting together perfectly.
One thing I can think of that would probably help is to reverse the order: Bump the versions (and their dependency versions) of the last-released crate (I assume that's the "outermost" dependent crate) first. You can see an example of this in the dev-version-working branch of the repo above.

Oh, we aren't updating dependents after bumping the post-release version.  I overlooked that since I don't do post-release version bumps.
The logic for updating dependents is here
https://github.com/sunng87/cargo-release/blob/master/src/main.rs#L514
while that is missing from here
https://github.com/sunng87/cargo-release/blob/master/src/main.rs#L728

I think I just got bitten by this exact bug.  Dry run output (after cleaning up the failure):
cfkaran2@Hammer:~/Documents/repositories/bit_network$ cargo release --dry-run --workspace -vvvvvv
[2020-05-08T14:11:21Z DEBUG] Creating git tag bit_network_library-v0.1.0
[2020-05-08T14:11:21Z TRACE] cd /home/cfkaran2/Documents/repositories/bit_network/bit_network_library
[2020-05-08T14:11:21Z TRACE] git tag -a bit_network_library-v0.1.0 -m (cargo-release) bit_network_library version 0.1.0
[2020-05-08T14:11:21Z DEBUG] Creating git tag bit_network_driver-v0.1.0
[2020-05-08T14:11:21Z TRACE] cd /home/cfkaran2/Documents/repositories/bit_network/bit_network_driver
[2020-05-08T14:11:21Z TRACE] git tag -a bit_network_driver-v0.1.0 -m (cargo-release) bit_network_driver version 0.1.0
[2020-05-08T14:11:21Z DEBUG] Creating git tag bit_network_visualizer-v0.1.0
[2020-05-08T14:11:21Z TRACE] cd /home/cfkaran2/Documents/repositories/bit_network/bit_network_visualizer
[2020-05-08T14:11:21Z TRACE] git tag -a bit_network_visualizer-v0.1.0 -m (cargo-release) bit_network_visualizer version 0.1.0
[2020-05-08T14:11:21Z INFO ] Starting bit_network_library's next development iteration 0.1.1-alpha.0
[2020-05-08T14:11:21Z TRACE] cd /home/cfkaran2/Documents/repositories/bit_network/bit_network_library
[2020-05-08T14:11:21Z TRACE] git commit  -am (cargo-release) start next development iteration 0.1.1-alpha.0
[2020-05-08T14:11:21Z INFO ] Starting bit_network_driver's next development iteration 0.1.1-alpha.0
[2020-05-08T14:11:21Z TRACE] cd /home/cfkaran2/Documents/repositories/bit_network/bit_network_driver
[2020-05-08T14:11:21Z TRACE] git commit  -am (cargo-release) start next development iteration 0.1.1-alpha.0
[2020-05-08T14:11:21Z INFO ] Starting bit_network_visualizer's next development iteration 0.1.1-alpha.0
[2020-05-08T14:11:21Z TRACE] cd /home/cfkaran2/Documents/repositories/bit_network/bit_network_visualizer
[2020-05-08T14:11:21Z TRACE] git commit  -am (cargo-release) start next development iteration 0.1.1-alpha.0
[2020-05-08T14:11:21Z INFO ] Pushing HEAD to origin
[2020-05-08T14:11:21Z TRACE] cd /home/cfkaran2/Documents/repositories/bit_network
[2020-05-08T14:11:21Z TRACE] git push origin
[2020-05-08T14:11:21Z INFO ] Pushing bit_network_library-v0.1.0 to origin
[2020-05-08T14:11:21Z TRACE] cd /home/cfkaran2/Documents/repositories/bit_network
[2020-05-08T14:11:21Z TRACE] git push origin bit_network_library-v0.1.0
[2020-05-08T14:11:21Z INFO ] Pushing bit_network_driver-v0.1.0 to origin
[2020-05-08T14:11:21Z TRACE] cd /home/cfkaran2/Documents/repositories/bit_network
[2020-05-08T14:11:21Z TRACE] git push origin bit_network_driver-v0.1.0
[2020-05-08T14:11:21Z INFO ] Pushing bit_network_visualizer-v0.1.0 to origin
[2020-05-08T14:11:21Z TRACE] cd /home/cfkaran2/Documents/repositories/bit_network
[2020-05-08T14:11:21Z TRACE] git push origin bit_network_visualizer-v0.1.0

And doing the actual run:
cfkaran2@Hammer:~/Documents/repositories/bit_network$ cargo release --workspace -vvvvvv
Release
  bit_network_library 0.1.0
  bit_network_driver 0.1.0
  bit_network_visualizer 0.1.0
? [y/N]
y
[2020-05-08T14:18:40Z DEBUG] Creating git tag bit_network_library-v0.1.0
[2020-05-08T14:18:40Z DEBUG] Creating git tag bit_network_driver-v0.1.0
[2020-05-08T14:18:40Z DEBUG] Creating git tag bit_network_visualizer-v0.1.0
[2020-05-08T14:18:40Z INFO ] Starting bit_network_library's next development iteration 0.1.1-alpha.0
[2020-05-08T14:18:40Z WARN ] Fatal: Invalid TOML file format: Error during execution of `cargo metadata`: error: no matching package named `bit_network_library` found
    location searched: /home/cfkaran2/Documents/repositories/bit_network/bit_network_library
    prerelease package needs to be specified explicitly
    bit_network_library = { version = "0.1.1-alpha.0" }
    required by package `bit_network_driver v0.1.0 (/home/cfkaran2/Documents/repositories/bit_network/bit_network_driver)`
cfkaran2@Hammer:~/Documents/repositories/bit_network$ git tag -l
bit_network_driver-v0.1.0
bit_network_library-v0.1.0
bit_network_visualizer-v0.1.0
cfkaran2@Hammer:~/Documents/repositories/bit_network$ cargo metadata --format-version 1
error: no matching package named `bit_network_library` found
location searched: /home/cfkaran2/Documents/repositories/bit_network/bit_network_library
prerelease package needs to be specified explicitly
bit_network_library = { version = "0.1.1-alpha.0" }
required by package `bit_network_driver v0.1.0 (/home/cfkaran2/Documents/repositories/bit_network/bit_network_driver)`

It looks like bit_network_library gets version bumped, and then cargo metadata gets grumpy, both leaving my repository is weird inconsistent state (properly tagged, but only one of the Cargo.toml files being version bumped).
Any idea on if/when this will be resolved?

@ckaran, I managed to cleanly release my crate with a cargo-release version that had the fix from #209 applied. I'd love some independent verification, so if you're willing to try it - I'd love to see if it works for you (:

@antifuchs I'd be glad to!  Is there a recommended method for testing it out that won't replace my current install of cargo release?

@ckaran I'm pretty sure you can cargo run --manifest-path /path/to/cargo-release/Cargo.toml -- [cargo release options] your way to victory! But, note: The PR just got merged to HEAD, you can probably just install the git version of cargo release now (:

@antifuchs I just cloned the latest version of the repository (14ecbe336ae1ed7205b4a7f5f4f9783b76b132d5), and it didn't work for me.
$ cargo run --manifest-path /home/cfkaran2/Documents/repositories/cargo-release/Cargo.toml -- release --workspace
    Finished dev [unoptimized + debuginfo] target(s) in 0.06s
     Running `/home/cfkaran2/Documents/repositories/cargo-release/target/debug/cargo-release release --workspace`
Release
  bit_network_library 0.1.0
  bit_network_driver 0.1.0
  bit_network_visualizer 0.1.0
? [y/N]
y
[2020-05-11T15:18:27Z INFO ] Starting bit_network_library's next development iteration 0.1.1-alpha.0
[2020-05-11T15:18:27Z WARN ] Fatal: Invalid TOML file format: Error during execution of `cargo metadata`: error: no matching package named `bit_network_library` found
    location searched: /home/cfkaran2/Documents/repositories/bit_network/bit_network_library
    prerelease package needs to be specified explicitly
    bit_network_library = { version = "0.1.1-alpha.0" }
    required by package `bit_network_driver v0.1.0 (/home/cfkaran2/Documents/repositories/bit_network/bit_network_driver)`

The tags were correctly set in the repository, but only the top-level Cargo.toml file was picked up, and only one of the Cargo.toml files was updated (bit_network_library).

I seem to have run into the same problem with cargo-release v0.13.10.  In the root of my repo, I've got "dropshot" and "dropshot_endpoint".  "dropshot" depends on "dropshot_endpoint" -- always the same version.  (The latter is a proc macro used in the former -- that's the only reason it's a separate crate.)  It seems that when I try to do a release of v0.4.0, it updates "dropshot_endpoint" to v0.4.1-alpha.0, then tries to update "dropshot", but cargo bails:
[2021-02-02T00:42:49Z WARN ] Fatal: Invalid TOML file format: Error during execution of `cargo metadata`: error: no matching package named `dropshot_endpoint` found
    location searched: /Users/dap/oxide/dropshot/dropshot_endpoint
    prerelease package needs to be specified explicitly
    dropshot_endpoint = { version = "0.4.1-alpha.0" }
    required by package `dropshot v0.4.0 (/Users/dap/oxide/dropshot/dropshot)`

This seems to go back to @antifuchs's original comment: there doesn't seem to be an order in which this will always work without saving the Cargo.toml updates to temp files first?
FYI: in my case, I didn't have a clean cargo release because I had chosen the same tag for both crates and it bailed out.  I fixed this by hand and reran it as  cargo release --skip-tag --skip-publish -vvv 0.4.0 and got the error above.  I don't think this matters but I wanted to mention it just in case!

@ckaran and @davepacheco I created a test repo to try to reproduce the problems you are having but I didn't get failures.  Could you create a PR that gets it into the failure state to help clarify what the difference is?
https://github.com/epage/cargo-release-test

Thanks @epage!  I went ahead and did that: https://github.com/epage/cargo-release-test/pull/1/
This was helpful.  My problem was a result of trying to use cargo release with the same version after a previous cargo release had failed.  It would be nice if the tool handled this better, but it may be different than what's described here.

@epage My apologies, but I'm not likely to get the time to do this for quite a while; I'm in the middle of several other projects and can't really pause.  Is what @davepacheco sufficient, or do you really need me to create a minimized workspace that illustrates the issue?

Finally got a chance to dig into some of these problems.   One problem is we relied on cargo to resolve dependencies for us but for some reason in one case its not, so we are getting confused

I believe #295 resolves the remaining work for closing this out.  Feel free to open an issue if you run into another corner case.


cant use WavLM as upstream

using:
-m train -n WavLM_exp -u wavlm -d sv_voxceleb1 -s hidden_states -l -1
I get the following error:
AttributeError: module 's3prl.hub' has no attribute 'wavlm'
thanks

This is typically due to unsuccessful installation of S3PRL.
Could you please detail how you install it?

I'm working on windows so I am using the downloaded git and did pip install s3prl.
using Hubert is working fine:
-m train -n HuBERT_exp -u hubert -d sv_voxceleb1 -s hidden_states -l -1

Cool! Then I guess the reason is that our uploaded Pypi version is out-of-date and most supported upstreams are in the master branch only.
Is it possible for you (Windows) to install the editable version?
pip install -e ./


Code refactor and simplification

Tried to simplify and refactor the code
Event is now a class
Period is now a class
Both are accessed as objects (ie event.date) and can be dumped as dict (event.to_dict())

@mdallaire @clauderobi and anyone else :)
Please review, so we can get the code more readable and flexible

Looks good to me!


[SPM] Adds SPM support

DESCRIPTION
This PR adds SPM Support to Swift-Youtube-Player to allow usage with Apple's official package manager and for use within Tooling like Tuist.

@gilesvangruisen Wanted to check if this PR can be merged. I would expect a lot of us maintaining our own forks as we move to SPM.


Add tracing crate examples to log

Actually adding the recipes is reasonably easy,. I note that the contribution guidelines say not to add new crates though.
I wonder if adding an "Alternatives" section to each recipe could be worth doing, or if this would be best done by adding a tracing version of each log recipe?

I found a direct tie between the cookbook and the playground so I recommend any crate that is blessed.rs or top 100 and already in the playground.  I checked top 100 and did not find tracing.

It's in blessed.rs, so that seems reasonable to add. I ask because I've seen comments on a few places (various discord, reddit posts etc.) about how approachable getting started in tracing can be. I wanted to contribute recipes for it.
I went down the rabbit hole of trying to understand the playground inclusion criteria. There's likely a lot of crates that deserve to be on the playground list but that are overshadowed by crates that are used internally by many other crates rather than used directly. It might be nice to fix that someday.
I'm going to add an extra section alongside the log section with tracing equivalents.

It's in blessed.rs

Then it is blessed by the cookbook.

I noticed that the version by @john-cd already has this in https://john-cd.com/rust_howto/categories/development-tools_debugging/tracing.html, so rather than re-inventing the wheel, I'd suggest incorporating / merging those changes back into the cookbook from https://github.com/john-cd/rust_howto/tree/main

I see a difference in licensing, and it would take them opening a pr and making it CC0 for it to be allowed.

@AndyGauge  @joshka - all examples in my book are CC0. Feel free to copy them into the Rust Cookbook.
Note that there is a lot of stuff that is hidden from view in the book at this point - so check the GitHub.
For tracing examples: https://github.com/john-cd/rust_howto/tree/main/deps/tests/categories/development_tools_debugging
Just add a link to https://github.com/john-cd/rust_howto and  https://john-cd.com/rust_howto/ somewhere!


A recent change has slowed down Hugo

Without benchmarks I would have never guessed, but I will have to investigate this before we release this to the world.
▶ go test -run="NONE" -bench="BenchmarkSiteBuilding/TOML,num_root_sections=5,num_pages=1000,tags_per_page=1$" -test.benchmem=true -count 5 ./hugolib

▶ benchstat pre.bench post.bench
name                                                                    old time/op    new time/op    delta
SiteBuilding/TOML,num_root_sections=5,num_pages=1000,tags_per_page=1-4     112ms ± 8%     160ms ± 7%  +43.32%  (p=0.008 n=5+5)

name                                                                    old alloc/op   new alloc/op   delta
SiteBuilding/TOML,num_root_sections=5,num_pages=1000,tags_per_page=1-4    68.8MB ± 0%    68.8MB ± 0%     ~     (p=1.000 n=5+5)

name                                                                    old allocs/op  new allocs/op  delta
SiteBuilding/TOML,num_root_sections=5,num_pages=1000,tags_per_page=1-4      608k ± 0%      608k ± 0%     ~     (p=1.000 n=5+5)

I cannot reproduce the above results, I must have done something wrong.
▶ benchstat pre.bench post.bench
name                                                                    old time/op    new time/op    delta
SiteBuilding/TOML,num_root_sections=5,num_pages=1000,tags_per_page=1-4     114ms ±10%     110ms ± 2%   ~     (p=1.000 n=5+5)

name                                                                    old alloc/op   new alloc/op   delta
SiteBuilding/TOML,num_root_sections=5,num_pages=1000,tags_per_page=1-4    68.8MB ± 0%    68.8MB ± 0%   ~     (p=1.000 n=5+5)

name                                                                    old allocs/op  new allocs/op  delta
SiteBuilding/TOML,num_root_sections=5,num_pages=1000,tags_per_page=1-4      608k ± 0%      608k ± 0%   ~     (p=0.841 n=5+5)

I have redid the tests 3 times with approx the above result. Closing this.


Cell magic not converting properly when exporting as Python script

With the following cell in notebook,
%%timeit
print('hi')

when we export to Python script, we get:
# To add a new cell, type '# %%'
# To add a new markdown cell, type '# %% [markdown]'
# %%
from IPython import get_ipython

# %%
get_ipython().run_cell_magic('timeit', '', "print('hi')")

Is it possible to convert directly to cell magic (%%timeit) in the interactive Python page instead of this get_ipython() output? It becomes difficult to edit if you use cell magic with larger chunks of code.

@TarjinderSingh I'm not sure if I'm totally following here. Our conversion utility uses nbconvert to convert a notebook into a python script file. The conversion from cell magics to get_ipython() commands is a part of nbconvert and is required to get a runnable python script, as cell magics are not valid python outside of a notebook cell. Are you essentially looking for a convert to .py option that doesn't general a valid .py file, but does generate a .py file with cells that are valid in our interactive window?

Right, it would be ideal to have a .py file with cells that are valid in your interactive window, and doesn't collapse Python code into a string format.
ie
# %%
%%timeit
print('hi')

Even more ideally, would be a format that generates a valid .py file, and yet renders magic properly in your interactive window. ie
# %%
# ! %%timeit
print('hi')

assuming that # ! indicates a comment line that should be processed as a magic cell.

Some magic commands like %%file or %load are not yet supported.
IMHO it's important to make the converted magic commands readable.
The main question is how to implement it so that python files run even without vscode.


Add an explicit Close function

Useful for long running processes that don't want to depend on the GC for cleanup

Changed to return any error from Close.

Oh. Heh. I hadn't noticed that unlock also closes the file descriptor. Hm.
I suppose this isn't really necessary then -- though, I feel like I would really want to ensure that the descriptor gets closed, regardless of whether there's an error that occurs when unlocking?

@virtuald might you have a spare moment to look at this one more time?

I can take a look this weekend.


Usable with ImageBackground?

Using <Image> with children is deprecated and will be an error in the near future. Is it possible to easily integrate this library with the new <ImageBackground>?
The docs do suggest implementing ImageBackground yourself. Is that an option for this package?
https://facebook.github.io/react-native/docs/images.html#background-image-via-nesting

Thank you for this information. I'll investigate it.
On Fri, Apr 6, 2018, 4:50 AM David Schumann<EMAIL_ADDRESS>wrote:

Using  with children is deprecated and will be an error in the
near future. Is it possible to easily integrate this library with the new
?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/billmalarky/react-native-image-cache-hoc/issues/21,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABxTU5St-x6qMlyhPtiJD1GtIjLKQZiOks5tlyxngaJpZM4TJtfT
.

Any news on this? Can't use this plug-in in this current state :(

I think it is, see; https://github.com/facebook/react-native/blob/master/Libraries/Image/ImageBackground.js

Hey, did you ever find the solution for this problem? Considering using this lib if it can be used with ImageBackground

It's working with me, replace the Image with ImageBackground.
const CacheableImageBackground = imageCacheHoc(ImageBackground);


Provide methods to  call zipkin APIs

Feature:
Provide (static) methods to make calls to zipkin APIs
Explain:
Zipkin expose those APIs to user, and the documentation is written in Swagger. A yaml file is also available for api/v2. In order to make calls to those APIs, users may need use raml or swagger to generate client-side code to make those calls to zipkin server. It's a lot of work and many classes including client implementations and models will be generated.
It would save a lot of work if zipkin itself provide interfaces to make those calls.
Example
public static List getTraceById (String traceId, @Optional String version);
(version could be v1 or v2, due to the version of zipkin that the user uses)
The zipkin server url is defined by user by overriding the following default value:
spring.zipkin.base-url=http://localhost:9411/

see also https://github.com/openzipkin/zipkin-api-example

@shakuzen  Hi, the use cases could be: user may want to get/post a span; user want to get the trace by traceId. Since the Zipkin APIs are exposed to public, and we can even override the reporter and Tracefilter to add extra tags and so on,  it's is possible that users will make use of those APIs for their own Log & tracing solution. I would be very appreciate if this functionalities can be provided and they will be very helpful.

@adriancole Hi, many thanks that you show me an example. But pity is that it make uses of swagger for code generation, which I have explained before is very heavy for user. Besides, "localhost:9411" is hard-coded in the example and it's in go. It would be better if a common java library is provided and make use of the user input of spring.zipkin.base-url, and expose those APIs as methods for call.

so the use case you mention isn't typical, so it is hard to say how much
value there is in publishing this. For example, we don't create features
without 3 folks asking and creating a new library before that happens would
be too early as well, especially under the assumption it would be backed
into a sleuth app :P
I would recommend that you try to use something like feign which if you are
only getting a trace by ID will be easy to do on your own. You make sure
the decoder uses SpanBytesDecoder.decodeList. Can you try this please?

you can also look at some older code here, as well which while written against the v1 api (io.zipkin.java:zipkin code in package zipkin), can be a hint for v2 api (io.zipkin.zipkin2:zipkin code in package zipkin2)
https://github.com/openzipkin/zipkin/commit/8f99f3cf44cbcdc678b9ae845d501ba2fc2422a4#diff-428d6e11ec1d9804af04afc7ecc13c91L33

@shakuzen You are right, Feign or directly using RestTemplate are the alternatives. I know how to do it. The problem is which is the best solution or the most effective way. User will still need model Span or Trace as entity in this case.
Maybe we can wait for few days if there are other users want the same feature before we close it.
I still believe its would be valuable to have such features. Zipkin GUI is not enough as an output for the whole distributed tracing solution.

I wonder if somehow we are overthinking this..
There is a library with a decoder, why do you need to do any entity mapping?
List<zipkin2.Span> decoded =
SpanBytesDecoder.JSON_V2.decodeList(your_byte_from_http_response);
There's no concept of Trace in zipkin it is a list of spans.. if only
getting by id using the above makes the code far less text than the
conversation so far.
On Thu, Aug 30, 2018 at 2:50 PM Guangming Luo<EMAIL_ADDRESS>wrote:

@shakuzen You are right, Feign or directly using RestTemplate are the alternatives. I know how to do it. The problem is which is the best solution or the most effective way. User will still need model Span or Trace as entity in this case.
Maybe we can wait for few days if there are other users want the same feature before we close it.
I still believe its would be valuable to have such features. Zipkin GUI is not enough as an output for the whole distributed tracing solution.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.

here's a working example, where the only dependencies are io.github.openfeign:feign-core and io.zipkin.zipkin2:zipkin
Hopefully this can buy you time as we don't typically enter work like creating a new library etc within days anyway.

  interface Zipkin {

    @RequestLine("GET /api/v2/trace/{traceId}")
    List<Span> getTrace(@Param("traceId") String traceId);

    static Zipkin connect() {
      Decoder decoder = new Decoder.Default() {
        @Override
        public Object decode(Response response, Type type) throws IOException {
          if (response.request().url().contains("/api/v2/trace/")) {
            byte[] bytes = (byte[]) super.decode(response, byte[].class);
            if (bytes == null) return null;
            return SpanBytesDecoder.JSON_V2.decodeList(bytes);
          }
          return super.decode(response, type);
        }
      };

      return Feign.builder()
          .decoder(decoder)
          .logger(new Logger.ErrorLogger())
          .logLevel(Logger.Level.BASIC)
          .target(Zipkin.class, "http://localhost:9411");
    }
  }

  public static void main(String... args) {
    Zipkin zipkin = Zipkin.connect();

    System.out.println(zipkin.getTrace("96e7c98dd2d01b3c"));
  }

@adriancole  You are right, Trace is a list of Span with the same traceId.
Great to know that there is already a library zipkin2.Span for span and there is a decoder.
In this case, Feign could  be the most effective solution.
Many thanks for the working example.


Release

Codecov Report

Merging #87 (fab3ac1) into main (e91e09c) will not change coverage.
The diff coverage is 92.85%.

@@           Coverage Diff           @@
##             main      #87   +/-   ##
=======================================
  Coverage   71.06%   71.06%
=======================================
  Files          12       12
  Lines        1258     1258
=======================================
  Hits          894      894
  Misses        364      364

Impacted Files
Coverage Δ

sarif-fmt/src/bin.rs
51.55% <91.30%> (ø)

clang-tidy-sarif/src/bin.rs
93.33% <100.00%> (ø)

clippy-sarif/src/bin.rs
93.75% <100.00%> (ø)

hadolint-sarif/src/bin.rs
93.75% <100.00%> (ø)

serde-sarif/src/lib.rs
100.00% <100.00%> (ø)

shellcheck-sarif/src/bin.rs
93.75% <100.00%> (ø)

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update e91e09c...fab3ac1. Read the comment docs.


Add compatibility with Laravel 6

This pull request adds compatibility with Laravel 6

Thanks for this pull request! Have you tested it out yet? Thanks!

Hi, yes I tested it out in a real application (using Laravel dev-master) and everything seems to be working as expected. I had to change the array_ and str_ helper functions to use the class-based equivalent though.

Great, @DanielCoulbourne will take a look at this shortly--thanks!

Thanks @victorlap!

Hi thanks for merging!
Can you release a new version now that Laravel 6.0 is out?


Improve string concatenations in metric reporter

Purpose

Improve string concatenations in metric reporter using string templates and string arrays.
Related to: https://github.com/ballerina-platform/ballerina-lang/issues/22820

This change is not introduced any logic changes. Hence no need of adding new test cases.
However, since this change reduced the number of lines, the expected code coverage number is not reaching now.


TF Lite zeros_like_test death test case added

Unsupported validation test case added for zeros_like operator

Corrupt PR is replaced with #27372


ci: add cargo doc

Fixes #744

#748  👈 (View in Graphite)
main

This stack of pull requests is managed by Graphite. Learn more about stacking.


(Bug) User cant capture image from camera

On profile page when pressing the camera on mobile it only gives option to upload a file, it should also allow to use the camera
pressing save show go back to profile after save is success
there is a strange "zoom" effect when you press save.
the design is broken. camera is supposed to be on the top right. the button can stay at the bottom.

Correct: (button can stay at bottom like in incorrect state)

incorrect:

This issue didn't reproduce on Dev env (V 0.18.1-2)
Please take a look at the video.

Option to upload a file is present and the user can capture an image from the camera
The "Done" button and icon of adding the photo are on correct places after save is success

The device used: iPhone 8 Plus // iOS 13.1.3
Video: https://www.screencast.com/t/jgdFIoldJH


Link to the background of Simple.Web is broken

I have tried following the link to the background of Simple.web but return a 404 response

Is it perhaps this post: http://blog.markrendle.net/simple-web/ ?


radvis_bw: new abstellanlagen_ort BILDUNGSEINRICHTUNG

abstellanlagen_ort seems to have a new enum value, BILDUNGSEINRICHTUNG. This should be supported at ParkAPI Sources.

I have created PR for this.
I also noticed the variable sources_to_ignore in the current converter.py is empty, but defined as environment variable. When I leave it empty, I get AssertionError below and doesn't pass the GitHub lint test.
"MOBIDATABW" is now added to the empty variable list sources_to_ignore in the PR...Is that okay?
=================================== FAILURES ===================================
_____________ RadvisBwConverterTest.test_get_static_parking_sites ______________

radvis_bw_pull_converter = <parkapi_sources.converters.radvis_bw.converter.RadvisBwPullConverter object at 0x7f4c5b6c3790>
requests_mock = <requests_mock.mocker.Mocker object at 0x7f4c5b305570>

    @staticmethod
    def test_get_static_parking_sites(radvis_bw_pull_converter: RadvisBwPullConverter, requests_mock: Mocker):
        json_path = Path(Path(__file__).parent, 'data', 'radvis_bw.json')
        with json_path.open() as json_file:
            json_data = json_file.read()

        requests_mock.get(
            'https://radvis.landbw.de/api/geoserver/basicauth/radvis/wfs?service=WFS&version=2.0.0&request=GetFeature'
            '&typeNames=radvis%3Aabstellanlage&outputFormat=application/json',
            text=json_data,
        )
        static_parking_site_inputs, import_parking_site_exceptions = radvis_bw_pull_converter.get_static_parking_sites()

>       assert len(static_parking_site_inputs) == 690
E       AssertionError: assert 3034 == 690
E        +  where 3034 = len([StaticParkingSiteInput(uid='15176[65](https://github.com/ParkenDD/parkapi-sources-v3/actions/runs/11890892696/job/33130492627#step:6:66)02', name='Abstellanlage', group_uid='151766502', purpose=<PurposeType.BIKE: 'BIKE...ty_truck=UnsetValue, capacity_bus=UnsetValue, opening_hours=UnsetValue, external_identifiers=UnsetValue, tags=[]), ...])

tests/converters/radvis_bw_test.py:45: AssertionError
=========================== short test summary info ============================
FAILED tests/converters/radvis_bw_test.py::RadvisBwConverterTest::test_get_static_parking_sites - AssertionError: assert 3034 == 690
 +  where 3034 = len([StaticParkingSiteInput(uid='1517[66](https://github.com/ParkenDD/parkapi-sources-v3/actions/runs/11890892696/job/33130492627#step:6:67)502', name='Abstellanlage', group_uid='151766502', purpose=<PurposeType.BIKE: 'BIKE...ty_truck=UnsetValue, capacity_bus=UnsetValue, opening_hours=UnsetValue, external_identifiers=UnsetValue, tags=[]), ...])

Please do not hardode such values. There are two approaches to resolves this:

set the PARK_API_RADVIS_IGNORE_SOURCES in your mocked test
change the number of results in the tests, which would be reasonable as you also updated the test data

Thanks for the Tips, It has now been updated.


Typescript metro plugin doesn't build project references

What happened?
When you use project references TypeScript force you to build your source code. When you have clean codebase there are no builded files and @rnx-kit/metro-plugin-typescript throws error about that.
I think there should an option like in fork-ts-checker-webpack-plugin - { typescript: { build: true, mode: 'write-dts' } }
Ideally, just running metro should be enough, without separate running of tsc compliler
Affected Package
@rnx-kit/metro-plugin-typescript
Version
0.4.5
Which platforms are you seeing this issue on?

[ ] Android
[X] iOS
[ ] macOS
[ ] Windows

System Information
System:
  OS: macOS 14.6.1
  CPU: (10) arm64 Apple M1 Max
  Memory: 9.35 GB / 64.00 GB
  Shell:
    version: "5.9"
    path: /bin/zsh
Binaries:
  Node:
    version: 22.7.0
    path: ~/.nvm/versions/node/v22.7.0/bin/node
  Yarn:
    version: 1.22.22
    path: ~/.nvm/versions/node/v22.7.0/bin/yarn
  npm:
    version: 10.8.2
    path: ~/.nvm/versions/node/v22.7.0/bin/npm
  Watchman: Not Found
Managers:
  CocoaPods:
    version: 1.15.2
    path: /Users/dima/.rbenv/shims/pod
SDKs:
  iOS SDK:
    Platforms:
      - DriverKit 23.5
      - iOS 17.5
      - macOS 14.5
      - tvOS 17.5
      - visionOS 1.2
      - watchOS 10.5
  Android SDK: Not Found
IDEs:
  Android Studio: 2023.3 AI-233.14808.21.2331.11842104
  Xcode:
    version: 15.4/15F31d
    path: /usr/bin/xcodebuild
Languages:
  Java:
    version: 17.0.12
    path: /usr/bin/javac
  Ruby:
    version: 2.7.6
    path: /Users/dima/.rbenv/shims/ruby
npmPackages:
  "@react-native-community/cli": Not Found
  react: Not Found
  react-native: Not Found
  react-native-macos: Not Found
npmGlobalPackages:
  "*react-native*": Not Found
Android:
  hermesEnabled: Not found
  newArchEnabled: Not found
iOS:
  hermesEnabled: Not found
  newArchEnabled: false

Steps to Reproduce

Set-up typescript project references
Add @rnx-kit/metro-plugin-typescript to your metro config
Run expo ios

Code of Conduct

[X] I agree to follow this project's Code of Conduct

Hi, this sounds like a feature request rather than something not working correctly. @rnx-kit/metro-plugin-typescript does not run in build mode, hence it does not look at project references. It's only supposed to do type checking, not build.
If you're on a recent version of Metro and you're using package exports, have you tried adding a typescript condition? In your Metro config, you can enable unstable_enablePackageExports and set unstable_conditionNames to something like ['typescript', 'require', 'import', 'react-native']. This should tell Metro to look for .ts files instead and you won't have to build anything.

@tido64 I am not sure that this issue is connected with packages export, as I understand the error is coming from typescript type checker itself.
As I understand the plugin is supposed to allow you to do type checking by metro, if you have project references you have to run tsc manually what makes usages of @rnx-kit/metro-plugin-typescript useless, because the plugin can't work without tsc running in separate terminal and this is already performing type checking

@tido64 I am not sure that this issue is connected with packages export, as I understand the error is coming from typescript type checker itself.

It isn't. I'm saying there is a solution for your scenario with package exports that avoids building altogether.
I am not opposed to adding proper support for project references, but that will be an option that we have to add. I'm not sure of the scope of this work and will have to ask someone who knows these bits better than I do.
Out of curiousity, what is the error you're seeing?

@tido64 I have this error in clean repo
iOS Bundling failed 2039ms index.js (2831 modules)
error: Error: ENOENT: no such file or directory, open '/Users/dima/projects/sandbox/tamagui-front/front-lib/design/core/DesignShell/index.d.ts'
    at Object.readFileSync (node:fs:441:20)
    at VersionedSnapshot.getSnapshot (/Users/dima/projects/sandbox/tamagui-front/node_modules/@rnx-kit/typescript-service/lib/snapshot.js:20:42)
    at ExternalFileCache.getSnapshot (/Users/dima/projects/sandbox/tamagui-front/node_modules/@rnx-kit/typescript-service/lib/cache.js:59:21)
    at Object.getScriptSnapshot (/Users/dima/projects/sandbox/tamagui-front/node_modules/@rnx-kit/typescript-service/lib/project.js:24:123)
    at getOrCreateSourceFileByPath (/Users/dima/projects/sandbox/tamagui-front/node_modules/@rnx-kit/typescript-service/node_modules/typescript/lib/typescript.js:149926:35)
    at Object.getOrCreateSourceFile (/Users/dima/projects/sandbox/tamagui-front/node_modules/@rnx-kit/typescript-service/node_modules/typescript/lib/typescript.js:149922:14)
    at /Users/dima/projects/sandbox/tamagui-front/node_modules/@rnx-kit/typescript-service/node_modules/typescript/lib/typescript.js:149843:42
    at Object.getSourceFileWithCache [as getSourceFile] (/Users/dima/projects/sandbox/tamagui-front/node_modules/@rnx-kit/typescript-service/node_modules/typescript/lib/typescript.js:124074:24)
    at findSourceFileWorker (/Users/dima/projects/sandbox/tamagui-front/node_modules/@rnx-kit/typescript-service/node_modules/typescript/lib/typescript.js:126535:23)
    at findSourceFile (/Users/dima/projects/sandbox/tamagui-front/node_modules/@rnx-kit/typescript-service/node_modules/typescript/lib/typescript.js:126451:20)

When I run tsc --build  the error goes away


Module '"reactflow"' has no exported member...

 Did you mean to use 'import ReactFlowProvider from "reactflow"' instead?
error TS2614: Module '"reactflow"' has no exported member 'Background'. Did you mean to use 'import Background from "reactflow"' instead?
...

Your Example Website or App
No response
Steps to Reproduce the Bug or Issue
Using Reactflow v11.10.1 with the following code:
import ReactFlow, {
  Controls,
  useReactFlow,
  ReactFlowProvider,
  Background,
  BackgroundVariant,
  Connection,
  ConnectionLineType,
  useEdgesState,
  useNodesState,
} from "reactflow";

Expected behavior
I expect the imported modules to work, because using the actual repository doesn't seem to experience any issues.
Screenshots or Videos
No response
Platform

OS: Windows
Browser: N/A
Version: N/A

Additional context
I am using pnpm 8.11.0 to install all packages, not normal npm. I am running Node v18.19.0.

I can't reproduce this. Is it still an issue for you?

please re-open if it's still an issue for you.


Debian sections updates

This is intended to fix lintian messages about wrong-section-according-to-package-name.
@IsaacJT for review

These two commit got applyed to debian.native:

debian: set libcmocka-mocks-dev section to libdevel f402a94
debian: set cmocka-mocks-doc section to doc d7407e5

I rebased the remaining one to branch main.

@ahresse  we applied your changes to debian.native on the main branch. With the latest release for debian we published it for the debian/main.
Please have a look if you miss something otherwise we can close this as merged.

I re-based remaining commits on current main (https://github.com/Elektrobit/cmocka_mocks/commit/7cf0b19c0209299ca3e66e2cb34ace2247413a32) to make this PR ready for merge.

Yes, I see we have here different ideas on how to categorize our mock-libraries. Our thought is , the libmock-mylib provides mocks used to develop unit tests when I link against mylib.
@ahresse What are your thoughts about libmock-xy and section : lib  vs libdevel ?


re: AR19 migration

@imkleats
re: https://github.com/CUCentralAdvancement/essential-cu/pull/146

In stories, the audio player does not show the progress indicator moving when play is pressed.

Some template use the wrong font size and the images are on the wrong side. It's mostly the templates that are non-full-screen images.

Right:

Wrong:

cc @duquennoisa

@imkleats  reply to Tim's post
Looks like the font size isn't changing based on media queries for the vertical and horizontal split layouts.

@imkleats I noticed a difference in the mobile experience (on my phone, not on the firefox preview)
On the homepage module the accordion menu doesn't open all the way on the heroku app version

vs the live version

Then on the landing page of the story the mobile version isn't triggered which we had to split over two pages (not ideal- i know) but it did include a swipe indicator:
Live version:

Heroku:

I can probably add the "Swipe >" indicator using a ::before selector tied to a screen size media query. I'll see if I can replicate & figure out the accordion menu issue on my end.

Hey @tskillern @duquennoisa @mattroush - we've incorporated fixes for all the items you've noted & pushed the app to staging. The link for that is https://essential-staging-cu.herokuapp.com/. Please let us know if you find anything else. We're targeting a tentative launch of Thursday at the latest (earlier if you're able to review & don't find any additional issues). Thanks for your eyes on this.


normalization pitch and energy

Hi Florian. I just read your paper on EXACT PROSODY CLONING IN ZERO-SHOT MULTISPEAKER TEXT-TO-SPEECH(https://arxiv.org/pdf/2206.12229.pdf). Great job. Very interesting contributions, thanks for sharing this.
I was curious on the way you normalization pitch and energy? In paper, it's mention: "a way of normalizing pitch and energy that allows for the overwriting procedure to be compatible with a zero-shot multispeaker setting by
regaining the value ranges for each speaker through an utterance level speaker embedding" and "we normalize those values by dividing them by the average of the sequence that they occur in. "
Does it mean

that utterance speaker embedding as the input of the variance adaptor ?
use the phone level pitch/energy feature?
Thank you in advance. Best!

Hi! It's a very simple solution: We calculate the average of all frames in an utterance that are not 0
https://github.com/DigitalPhonetics/IMS-Toucan/blob/ee3b7988b15f871414829d30f24b5cc2a9d097b3/TrainingInterfaces/Text_to_Spectrogram/FastSpeech2/PitchCalculator.py#L58
and then we divide the entire sequence by this average
https://github.com/DigitalPhonetics/IMS-Toucan/blob/ee3b7988b15f871414829d30f24b5cc2a9d097b3/TrainingInterfaces/Text_to_Spectrogram/FastSpeech2/PitchCalculator.py#L59
This is done for both pitch and energy. This way we get float values that are centered around 1 that maintain information about the pitch curve and its variance. Those values will always be around 1, regardless of the fundamental frequency of the speaker's voice. So we transform the absolute values into relative values, which can be transferred to other speakers. But to produce the speech, the model has to somehow reconstruct the absolute values, however for the target speaker, not the source speaker. And we don't know those values for the target speaker. But luckily, the model can learn to do this internally, as long as it has the speaker embedding available as conditioning signal. And this is the case anyway, because we train the TTS as multispeaker model, so the speaker embedding is combined with the encoder output.
Answers directly to your questions:

The speaker embedding is combined with the encoder output, which then becomes the input to the variance adaptor
Yes, we calculate one average value per phone (as in FastPitch) and then afterwards we normalize all of those values to be relative instead of absolute (so we can transfer curves between speakers).

Thank you for your patient reply, very interesting work！
Can we synthesize audio with the same prosody and different text ?

This technique is meant for cloning exactly unit by unit. To transfer the general prosody to a different text, we use a different technique. There we use speaker embeddings, however not speaker embeddings that are trained as speaker verificcation model (which is usually then case). We use speaker embeddings that are trained with the GST approach and the modifications that adaspeech 4 proposes to the GST setup. By using an embedding derived from a reference audio with desired prosody there, we can control the general prosody, however no longer independent of the speaker.


Pie chart display series-1 depite assigning one string to it

Bug report
on the pie chart label, it shows series-1 instead of the intended string
Codesandbox
below is the codesandbox, line 97 - 99 is the line of code where i insert the string
https://codesandbox.io/s/funny-fermat-wos51?file=/src/App.js
options.labels did not update accordingly, it shows series-1 instead
Explanation

What is the behavior you expect?
render the intented string onto the data label
What is happening instead?
series 1 instead

Please ask basic react questions on Stackoverflow.
ApexCharts will update the chart automatically if the state is updated. In your example of the pie chart, you are not using a state, but a local variable.


file selection screen doesn't honor the reverse or '*' option

The main file display always uses reverse video even when '*' menu option is set.

The * or reverse on the file display is actually controlled by a different option found in the home screen settings menu. Perhaps the same option could be used for both.


Webapp:App Service web app SSL import command from Keyvault access right issue

I have web app is in different resource group and keyvault is in different resource group as my keyvault contain shared secrets like wildcard certificate which can be utilized by all my 50-100 web app across enterprise . I Want to import SSL certificate stored inside keyvault to app service web app using  “az webapp config ssl import" command. I tried to trigger Azure CLI command from Azure devops as part of my app service deployment automation using service principal. I granted Get and List keyvault access to service principal and it has contributor access to app service web app resource group. But "az webapp config ssl import" command throw error and ask for first read access for keyvault and once we grant read access it throw error for write access. Which seems strange as we don't want to give write access to keyvault just for importing ssl certificate from keyvault. Even i tried to grant all in keyvault access policy. But "az webapp config ssl import" command only work once i gave contributor/read-write access to service principal. This is security concern as granting contributor access for keyvault to any service principal is not allowed best practice to avoid any accidental problem for other important secret stored inside respective keyvault. So need solution for this. Also we can't use seperate keyvault for each web app as it will be nightmare to manage and maintain shared secret for each and every keyvault dedicated to respective web app.

routing to appropriate team

The error seems to appear even if you have provided Read access - as long as it can address your keyvault it should have worked. One thing to note if only the most recent Azure CLI version supports key vaults from other resource groups being used - though specifying the full resource ID of your keyvault would work;

@AnandPatel4Git checking to see if your issue is resolved?

closing due to lack of response.


wip: update k3s and use debian 11 in devstack machine

What this PR does / why we need it:
see https://github.com/kubernetes/cloud-provider-openstack/pull/2108#issuecomment-1435650268
this is why debian 11 was chosen instead of ubuntu to host devstack
Which issue this PR fixes(if applicable):
fixes #
Special notes for reviewers:

Release note:

NONE

/test openstack-cloud-csi-cinder-e2e-test
/test openstack-cloud-controller-manager-e2e-test
/test openstack-cloud-csi-manila-e2e-test

/test openstack-cloud-csi-cinder-sanity-test
/test openstack-cloud-csi-manila-sanity-test
/test openstack-cloud-keystone-authentication-authorization-test

perhaps same bug exists still in debian 11
root@ip-10-0-0-245:~/cloud-provider-openstack# apt-get install libgpgme11
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
libgpgme11 is already the newest version (1.14.0-1+b2).
libgpgme11 set to manually installed.
0 upgraded, 0 newly installed, 0 to remove and 4 not upgraded.
root@ip-10-0-0-245:~/cloud-provider-openstack# pip list|grep gpg
gpg                    1.14.0-unknown

root@ip-10-0-0-245:~/cloud-provider-openstack# cat /etc/os-release
PRETTY_NAME="Debian GNU/Linux 11 (bullseye)"
NAME="Debian GNU/Linux"
VERSION_ID="11"
VERSION="11 (bullseye)"
VERSION_CODENAME=bullseye
ID=debian
HOME_URL="https://www.debian.org/"
SUPPORT_URL="https://www.debian.org/support"
BUG_REPORT_URL="https://bugs.debian.org/"
root@ip-10-0-0-245:~/cloud-provider-openstack# uname -a
Linux ip-10-0-0-245 5.10.0-21-cloud-amd64 #1 SMP Debian 5.10.162-1 (2023-01-21) x86_64 GNU/Linux


Possible fix for issue #804

Possible fix for issue https://github.com/jonataslaw/getx/issues/804

This is the solution for the future release. The Api Window was deprecated, and changed to SingletonFlutterWindow on master, however, this PR will break Stable.
So I will wait until this version becomes stable to accept this.

Perfectly worked for me, thanks 👍


feat(pie-monorepo): modified CI Workflow for cater for staging environment

Describe your changes (can list changeset entries if preferable)
[Added] - Modified CI Workflow for cater for staging environment
Author Checklist (complete before requesting a review)

[ ] I have performed a self-review of my code
[ ] If it is a core feature, I have added thorough tests.
[ ] If it is a PIE Docs change, I have reviewed the PR preview
[ ] If there are visual test updates, I have reviewed them properly before approving

Reviewer checklists (complete before approving)
Reviewer 1

[ ] If it is a PIE Docs change, I have reviewed the PR preview
[ ] If there are visual test updates, I have reviewed them

Reviewer 2

[ ] If it is a PIE Docs change, I have reviewed the PR preview
[ ] If there are visual test updates, I have reviewed them

Closing this temporarily as work has been paused on using this workflow in fozzie-components.


Failed to import - browserslist

Failing module

GitHub: https://github.com/browserslist/browserslist
npm: https://www.npmjs.com/package/browserslist

Accessing URL<EMAIL_ADDRESS>on WebKit browsers gives HTTP 500
Error message
Response:
/* esm.sh - error */
throw new Error("[esm.sh] " + "yarn add<EMAIL_ADDRESS>");
export default null;

Additional info

esm.sh version: 96
Browser version:

Safari, 16.0
Safari Technology Preview, Release 155 (Safari 16.4, WebKit 176<IP_ADDRESS>)

it's recovered now, the server was out of the disk space that is stolen by npm cache

Thank you!


md-color package include paths continue throwing errors on compile

Hi, After abandon/rest on the project I was working on while I reported https://github.com/zavoloklom/material-design-typography/pull/1, I resumed work and tested what you did, but it keeps triggering a FileError error.
This is how I'm including the files i my project main files:
@bower-path:            '../public/vendors/bower_components';

@import<EMAIL_ADDRESS>@import<EMAIL_ADDRESS>@import<EMAIL_ADDRESS>
and it triggers the error:
    Running "less:dev" (less) task
    >> FileError: 'bower_components/material-design-color-palette/less/variables.less' wasn't found. Tried - public/vendors/bower_components/material-design-typography/less/bower_components/material-design-color-palette/less/variables.less,less/bower_components/material-design-color-palette/less/variables.less,bower_components/material-design-color-palette/less/variables.less in public/vendors/bower_components/material-design-typography/less/material-design-typography.less on line 6, column 1:
    >> 5 // MD Color Palette
    >> 6 @import "bower_components/material-design-color-palette/less/variables.less";
    >> 7 @import "bower_components/material-design-color-palette/less/mixins.less";
    Warning: Error compiling less/main.less Use --force to continue.

I tried again with the PR https://github.com/zavoloklom/material-design-typography/pull/1/files, and worked fine this time too.
Maybe we can came to an understanding and fix this once for all? :smile:
Thanks in advance for your time and this library.

Maybe some variant of the following code can be used to make both paths work properly?
// MD Color Palette
@import (optional) "bower_components/material-design-color-palette/less/variables.less";
@import (optional) "bower_components/material-design-color-palette/less/mixins.less";

@import (optional, reference) "../../../bower_components/material-design-color-palette/less/variables.less";
@import (optional, reference) "../../../bower_components/material-design-color-palette/less/mixins.less";

My only concern with this code is when both the local and the external bower_components exists, but it seems that the case is very remote.
An update like this could help a lot, since I'm live-compiling the library in my project, not pre-compiling it since I'm changing lot of vars that affect the final output.


Login, Signup and Profile pages show Ads, violating Adsense terms

Still not solved.
It still appear on register page (signup), and even on Login, sometimes it still appear. And therefore violation adsense terms...

I needed to edit one html page. And add some code on it:

After that it was solved.

#29


group queries initial value can't be empty

Hi,
I'm writing some group queries using Doctrine mongoDB lately, and I noticed that Doctrine\MongoDB\Query\Builder::group() requires the second argument($initial) to be an array containing at least one key. While this apply to a good bunch of cases, it can happen, sometimes, that I'd like to avoid hardcoding a key in there(mongoDB itself does not force you to do such thing) and add it afterwards in the reduce step. An example could be having many separate counters to keep track of different values of the same field(thinking about tags, I'd like to reduce on something like this: {tag1: 123, tag2: 111, tag3: 333} instead of an hardcoded {count: 456} object. A workaround to the current behavior is to add a bogus key/value so that it doesn't crash the query, but it feels a little wrong to me.
Thanks

Hi, can you provide a test case for what you are explaining?

sure, I'll try to do that asap, hopefully today! :)

Hi, I am not sure I can reproduce the error without fixtures(or perhaps I am missing how to do that, sorry I'm starting unit testing these days), but I think the test should look like this, assuming there's a matching record and that the $key value is actually extracted from the db and therefore unknown unless precisely set in the fixtures:
public function testGroupWithEmptyInitialValue()
    {
        $key = 'aKeyFromTheDb';
        $reduce = "function (obj, prev) {
            var key = '$key';
            if(!prev[key]) {
                prev[key] = 0;
            }
            prev[key]++;
        }";
        $qb = $this->getTestQueryBuilder()
            ->group(array(), array())
            ->reduce($reduce);

        $expected = array(
            'initial' => array(
                $key => 1
            ),
            'keys' => array()
        );
        $this->assertEquals($expected, $qb->debug('group'));
    }


[Fix] Add max_keep_ckpts for groupfree3d

Thanks for your contribution and we appreciate it a lot. The following instructions would make your pull request more healthy and more easily get feedback. If you do not understand some items, don't worry, just make the pull request and seek help from maintainers.
Motivation
The size of a most simple groupfree3d ckpt is around 170MB, and there are by default 400 ckpts saved in one run, which will take about 70GB space. There is a high chance of disk space/quota exceed, which will terminate training.
Modification
I added  max_keep_ckpts  in groupfree3d configs.
BC-breaking (Optional)
Does the modification introduce changes that break the back-compatibility of the downstream repos?
If so, please describe how it breaks the compatibility and how the downstream projects should modify their code to keep compatibility with this PR.
Use cases (Optional)
If this PR introduces a new feature, it is better to list some use cases here, and update the documentation.
Checklist

Pre-commit or other linting tools are used to fix the potential lint issues.
The modification is covered by complete unit tests. If not, please add more unit test to ensure the correctness.
If the modification has potential influence on downstream projects, this PR should be tested with downstream projects.
The documentation has been modified accordingly, like docstring or example tutorials.

@hjin2902 , please take a look. If you approve, you can also update #702 ?

@hjin2902 , please take a look. I cannot request review from you. If you approve, you can also update #702 ?

Sorry for the late reply!
Yes, we can add config like this, but a potential problem is that the best checkpoint may not in the last 10 epoch. So maybe the value of max_keep_ckpts should be large enough.


making sure that C headers are included in source distribution (sdist)

Currently, this module cannot be installed from a source distribution since the C header files are not included.
You can see in the logs that with this manifest file, the issue should be fixed:

LGTM. Thank you!


Other games

is it possible to apply this to other games that have stutter? or is it just a point hack for wow? is it possible to create something universal?

VanillaFixes only applies to WoW. Maybe this function would help other (old) games:
https://github.com/hannesmann/vanillafixes/blob/main/src/dll/dll.c#L12

it is possible remove 64fps cap in Warcraft 3 1.26a? Can you make support?


Support OTel scope_logs

Is your feature request related to a problem? Please describe.
OTel added scope_logs which replaces instrumentation_library_logs.
Describe the solution you'd like
Support scope_logs per the spec. Retain backward compatibility.

Also, we should verify the behavior at the integration testing level via #1963 .


feat: use caching layer when fetching blocks for logs

Closes #2302

Codecov Report

Merging #2350 (5476c24) into main (370c395) will decrease coverage by 31.13%.
The diff coverage is 0.00%.

:mega: This organization is not using Codecov’s GitHub App Integration. We recommend you install it so Codecov can continue to function properly for your repositories. Learn more
@@             Coverage Diff             @@
##             main    #2350       +/-   ##
===========================================
- Coverage   70.77%   39.65%   -31.13%
===========================================
  Files         480      480
  Lines       58129    58130        +1
===========================================
- Hits        41142    23052    -18090
- Misses      16987    35078    +18091

Flag
Coverage Δ

integration-tests
?

unit-tests
39.65% <0.00%> (-27.21%)
:arrow_down:

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files
Coverage Δ

crates/rpc/rpc-builder/src/auth.rs
0.00% <0.00%> (-46.96%)
:arrow_down:

crates/rpc/rpc-builder/src/lib.rs
17.32% <0.00%> (-41.12%)
:arrow_down:

crates/rpc/rpc/src/eth/filter.rs
0.00% <0.00%> (-6.98%)
:arrow_down:

... and 272 files with indirect coverage changes
Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.


Add updated thumbnails

My repositories are messed up.  I've been trying to get them back up to date.  I thought I had, but when I make this pull request, it still has a merge with upstream/davidsBranch.  I'm not sure how to delete that commit.  I'll try again.


chore(time): use import syntax to support rollup

Will merge and deploy once we've seen that the time tests pass in CI. Thanks for the über quick review @jvanbruegge!

Only failure was:

Mobile Safari 8.0.0 (iOS 8.4.0) historyDriver - xstream should allow going back/forwards with go, goBack, goForward FAILED
AssertionError: '/test' === '/other' (/tmp/karma-typescript-bundle-6830yMisz03aF5d4.js:1829)
Mobile Safari 8.0.0 (iOS 8.4.0): Executed 11 of 19 (1 FAILED) (skipped 8) (1.388 secs / NaN secs)

All of the time tests passed. We're good to go.

Released<EMAIL_ADDRESS>with these fixes.


Option to have quick-key prepend items instead of overwriting

I do wonder if there's a way to make the quick key appear appear before the item, the way the indicies do.

I assumed the user is already looking at the candidate and so avoiding any pushing of the candidates would be nicer but that is just my preference, you can open an issue for that if you like and I will add an option it.
Originally posted by @clemera in https://github.com/raxod502/selectrum/issues/304#issuecomment-797005823

What about prefixing all the candidates with a space optionally? I think that's the simplest solution.

Yes, that would be an alternative I also thought about, there could be a configurable padding.

Another thing - I wonder if it makes sense to simplify the current implementation at the expense of some generality. Is it realistic that there are more candidates visible than keys? I guess usually not. Then we always only need a single key. Or probably your plan is to make this work with a grid view too where we have many more candidates?

There can be more, for example when you use selectrum-display-full-frame (which I also do for some commands). Just noticed that for that case you would also need a two space padding.

Another idea would be that instead of padding people which prefer not overwriting the candidates could use selectrum-show-indices to show the keys all the time.

I also forgot you can already configure padding using selectrum-show-indices: (setq selectrum-show-indices (lambda (_) " "))

Sounds good. Maybe modify the show indices custom var such that it allows 'indices 'spaces nil? Maybe rename the variable such that it makes sense, selectrum-prefix-candidates for example.

Another idea would be that instead of padding people which prefer not overwriting the candidates with keys could use selectrum-show-indices to show the keys all the time.

The whole point of the original #304 was that I typically did not want to show indices all the time but occasionally wanted to toggle them on to use a quick key.  The solution was quick keys and this issue is to avoid them overwriting the candidates.

Okay, what do you think about using constant padding which then gets overwritten when using quick keys? I changed the order now so you can try it using (setq selectrum-show-indices (lambda (_) " ")).

As I wrote earlier in #304 I use this and it works pretty well:
(defun hrm-selectrum-toggle-show-indices ()
  "Toggles avy-like behavior in selectrum minibuffers."
  (interactive)
  (setq selectrum-show-indices (not selectrum-show-indices)))

I kind of like the way the candidates move over to make room for the indices, it's a visual cue that I can use them. It also means the space isn't wasted when indices aren't activated.
If the indicies changed to quick-keys that would be ideal to me, meaning I hit M-m or M-i to activate them and then the candidates move over and the quick-keys display the way the above function toggles the display of indices.  Then I just hit the quick-key, which would be easier than using a numeric argument to RET.
I can see how people will have different preferences.
If my choice is having quick-keys overwrite the candidate or having a permanent left margin, I'd prefer the overwrite.  I don't think I'll use them all that often and their visual behavior matching avy (which I also use infrequently) is reasonable and consistent.

Prepending doesn't work well for horizontal style, I would prefer to avoid introducing another display option for now. We can default to prepend for vertical style and overwrite for horizontal style. I initially thought that I would be annoyed by prepending but after using it for a while I agree that it is actually nicer.

@hmelman I change it now to automatically use the desired behavior for vertical style.

Thanks, looks great.

I like it too :) Closing this, since no option will be added.


Remove need for prefetch when proxying images

This is actually much slower, but may still be useful for requiring authentication to fetch from cache


What is the location of .csv file?

In the same directory as the script, or you can specify it at line 6 and 7.


Added Index in Quantification along with tests

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/RNAdam-prb/74/
Test PASSed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/RNAdam-prb/80/
Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/RNAdam-prb/81/
Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/RNAdam-prb/82/
Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/RNAdam-prb/83/
Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/RNAdam-prb/84/
Test FAILed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/RNAdam-prb/85/
Test PASSed.

Merged! Thanks @ananth-pallaseni!


Question: Is the CLOB data type supported?

odbc Package Version: 2.4.8
ODBC Driver: unixODBC 2.3.9
Database Name: DB2 for i
Database Version: V7R5
Database OS: IBM i
Node.js Version: v18.17.1
Node.js OS: IBM i

It looks to me as though the CLOB data type is still not supported but I wanted to check this for sure.
I created a simple SQL stored procedure with two parameters; one an input CLOB and the second an output CLOB. When I run my test Node.js App I get the following message.
Error: [odbc] Error binding parameters to the procedure
I've looked at the following similar issues, which (along with my test results) suggest that CLOB isn't currently supported.

#11: Calling Stored Procedures Issue
#129: CLOB support
#137: [BUG] Unable to Call Stored Procedure with CLOB Parameters
#342: Revisit CLOB support

I noticed in issue #137 this suggested an RFE had been raised. I checked the Ideas portal and I couldn't find one.
Is the CLOB data type supported?

Hi @richardm90! Apologies I didn't see your issue until now, I use CLOB fields with node-odbc connecting to my IBMi at work without any issues on 7.4. If you could share a simplified example I'd be happy to take a look at what you are trying to do.

Hi @brandonp42 and no problem, this is the test I was using.
My stored procedure.
CREATE OR REPLACE PROCEDURE RMTEMP.TEST_CLOB (
  IN    PARAM1 CLOB(1K) ,
  INOUT PARAM2 CLOB(1K) ,
  OUT   PARAM3 CLOB(1K)
)
BEGIN
  SET PARAM1 = 'Out1';
  SET PARAM2 = 'Out2';
  SET PARAM3 = 'Out3';
END;

-- CALL RMTEMP.TEST_CLOB('In1', 'In2', 'In3');

My Node.js app. This uses a DSN called MYIBMI to connect to my IBM i server.
const odbc = require('odbc');

odbc.connect('DSN=MYIBMI', (error, connection) => {
  if (error) { throw error; }
  let param1='In1';
  let param2='In2';
  let param3='In3';
  connection.callProcedure(null, 'RMTEMP', 'TEST_CLOB', [param1, param2, param3], (error, result) => {
    if (error) { throw error; }

    connection.close();
    console.log(result);
  });
});

Running the Node.js app gives me the following error.
Error: [odbc] Error binding parameters to the procedure
If I change my stored procedure from using CLOBs to VARCHARs it works as expected.
CREATE OR REPLACE PROCEDURE RMTEMP.TEST_CLOB (
  IN    PARAM1 VARCHAR(50) ,
  INOUT PARAM2 VARCHAR(50) ,
  OUT   PARAM3 VARCHAR(50)
)
BEGIN
  SET PARAM1 = 'Out1';
  SET PARAM2 = 'Out2';
  SET PARAM3 = 'Out3';
END;

-- CALL RMTEMP.TEST_CLOB('In1', 'In2', 'In3');

Okay, I looked into this a little more today and you are right that calling stored procedures with output parameters using the .callProcedure() function does not currently work. However if you return a result set with your variables using the .query() function it does work, here's an example:
CREATE OR REPLACE PROCEDURE RMTEMP.TEST_CLOB (
  IN    PARAM1 CLOB(1K) ,
  INOUT PARAM2 CLOB(1K) ,
  OUT   PARAM3 CLOB(1K)
)
LANGUAGE SQL
DYNAMIC RESULT SETS 1
BEGIN
  declare c1 cursor with return for
    with params (param1, param2, param3) as (values (param1, param2, param3))
    select * from params;

  SET PARAM1 = 'Out1';
  SET PARAM2 = 'Out2';
  SET PARAM3 = 'Out3';

  open c1;
  return;
END;

-- CALL RMTEMP.TEST_CLOB('In1', 'In2', 'In3');

The javascript code (I'm using async/await but you can still use callback functions):
import odbc from 'odbc';

let conn = await odbc.connect('DSN=*LOCAL');

let param1='In1';
let param2='In2';
let param3='In3';

let result = await conn.query('call SPLIBBPJNK.TEST_CLOB(?, ?, ?)', [param1, param2, param3]);

console.log(result);

Thanks @brandonp42 , I can get that to work. Is that how you need to work with CLOBs? Should you be able to use callProcedure with CLOBS?

My opinion is that in an ideal world you should be able to use callProcedure with CLOBS but it seems like there needs to be a code update to support that. I haven't worked on this codebase before so I am not sure how easy/hard it would be. I was hoping that @markdirish would chime in - I'm willing to give it a try but he knows this codebase the best.
Most of my efforts recently have been digging into the XMLSERVICE codebase and working on that - it uses CLOBS with stored procedures so I was really surprised initially when I saw your issue here. However, (when called from the nodejs toolkit) we're not doing the callProcedure function, it's using a call with a result set; that's why I suggested the workaround I gave you. It's maybe not the best solution but it seems to work as long as you don't need multiple result sets. I did a quick test with multiple result sets and it didn't work - when I get a chance to re-confirm and put a full example together I will open a new issue for that.

Thanks for the update and this does answer my original question of "Are CLOBs supported?", which they are using query and a result set but not using callProcedure.

I've been looking at how I can adapt my stored procedures to return a result set as the work around to the CLOB parameter problem and it's a bit of a faff. My stored procedures are all external stored procedures (call RPGLE program) so I'm thinking I'd need to create an additional SQL stored procedure that calls my external stored procedure and then returned the parameters as a result set. It just sounds like a lot of messing around.
Should you be able to use callProcedure with CLOBS? Is this a bug?

Still an open question


network: pass addresses to iohandle in connect/bind

Let IoHandle decide how to use Addresses, instead of passing the raw
sockaddr struct.
Signed-off-by: Florin Coras<EMAIL_ADDRESS>Risk Level: Low
Testing: unit tests
Docs Changes: n/a
Release Notes: n/a

Prep work for #11618 cc @yanavlasov @ggreenway


Test case update (using incorerct syntax) created 500 error

High-level summary of the problem.
When attempting to update 1 specific  test case using the test case edit UI by admin user , adding (presumably) incorrect syntax has completely broken access to the test cases page instead of just giving an error noting the specific test case cannot be updated
Steps to reproduce

Edit a test case using the test case edit UI
Add incorrect syntax to an expected test case body
Trying to access test cases page https://compliance.mobilemoneyapi.io/admin/test-cases to reverse the change causes error so no way to edit the test case back to original

Expected outcome
After steps 1 and 2 if syntax is not correct, error message should be shown that test case cannot be updated and admin should be able to cancel the update and have access to the https://compliance.mobilemoneyapi.io/admin/test-cases page as normal
Actual outcome
Tying to access test cases page https://compliance.mobilemoneyapi.io/admin/test-cases to reverse the change causes error
500 Oops...You just found an error page  We are sorry but your request contains bad syntax and cannot be fulfilled.

@Viji-GSMA  Add incorrect syntax to an expected test case body
Please explain it in more detail and provide some examples.
Could you specify, please? What exactly the wrong syntax did you use?

HI @KisIrene I'm not sure exactly what I did wrong - it may well have been incorrect syntax - but in a way that is irrelevant - the point is whatever the error, the admin should just get an error message and be unable to update the test case (regardless of the exact error)
Instead I just receive this page   https://compliance.mobilemoneyapi.io/admin/test-cases with the 500 error when I try to go back to admin>test cases
As noted above this does not enable me to go back into the test case and edit it
This should clearly not happen

Fixed in 9732df39bb2c2e8270854998023388d2ed09b859.


Cannot set column 'instance'. The value violates the MaxLength limit of this column

"2016-05-09 09:11:20,519 [5] INFO TabMon.CounterConfig.CounterConfigLoader - Loaded 74 MBean counters on n4dtab1.
2016-05-09 09:11:20,519 [5] DEBUG TabMon.TabMonAgent - Successfully loaded 373 counters from configuration file.
2016-05-09 09:11:20,535 [5] DEBUG TabMon.Sampler.CounterSampler - Dynamically built result schema 'countersamples'. [48 columns]
2016-05-09 09:11:20,535 [5] INFO TabMon.TabMonAgent - TabMon initialized!  Starting performance counter polling..
2016-05-09 09:11:20,535 [5] INFO Topshelf.Runtime.Windows.WindowsServiceHost - [Topshelf] Started
2016-05-09 09:11:20,535 [6] INFO TabMon.Sampler.CounterSampler - Polling..
2016-05-09 09:11:20,550 [6] FATAL Topshelf.Runtime.Windows.WindowsServiceHost - The service threw an unhandled exception
System.ArgumentException: Cannot set column 'instance'. The value violates the MaxLength limit of this column.**
at System.Data.DataColumn.CheckMaxLength(DataRow dr)
at System.Data.DataTable.RaiseRowChanging(DataRowChangeEventArgs args, DataRow eRow, DataRowAction eAction, Boolean fireEvent)
at System.Data.DataTable.SetNewRecordWorker(DataRow row, Int32 proposedRecord, DataRowAction action, Boolean isInMerge, Boolean suppressEnsurePropertyChanged, Int32 position, Boolean fireEvent, Exception& deferredException)
at System.Data.DataTable.InsertRow(DataRow row, Int64 proposedID, Int32 pos, Boolean fireEvent)
at TabMon.Sampler.CounterSampler.SampleAll()
at TabMon.TabMonAgent.Poll(Object stateInfo)"
Hi , I am getting the error stated above, but would have not idea where to begin resolving. Its a big ask, but you help would be much appreciated .
Many thanks

Hi Hucklerl, this looks like a bug..  One of the PerfMon counters you're polling has an instance name that is unexpectedly long.  If you can find out which counter it is, removing it from monitoring in Counters.config would be a workaround.  Usually the longest instance names we see are in network adapters so I'd try to start there.
Flagging this as a bug to be fixed in the code.

Hi
Thanks for the response . We have found the issue and have renamed the network adapters and now waiting for the server to reboot for the new name to cascade through the registers.
Regards

Fixed in #92 -- this column length has been extended to the max allowable length.


UX: convert all the buttons to have an icon before text

All buttons that have an icon should have the icon before text instead of after.
hint:
Use the iconBeforeText flag.

Can we choose to have Tooltips to both Add and Remove.
And also add ( or remove ) the labels to both buttons

With team we decide to not add labels Remove to the trash icon and stay with labels Add next to plus, also we agreed that Tooltips here aren't necessary. We can discuss it later and make a follow-up if it will be necessary.


Add Nexus

What is the vendor's name?
Sonatype Nexus3
What is the vendor's pricing site?
There is no price listing page, but SSO is not available in OSS.
https://help.sonatype.com/repomanager3/product-information/repository-manager-pro-features

There's a price listing here https://www.sonatype.com/products/repository-pro

Starts at $3000/year (based on 25 users)

...


not getting any results back from dockerized pengines in python

Hello,
I am trying to understand how to work with pengines. I have opened up an issue in the swi-prolog forum but got no attention there yet:
https://swi-prolog.discourse.group/t/pengines-issue/1838
That I am reproducing here below:

I’m using: SWI-Prolog version 8.0.3, via pengines on docker
Gundam:my_codes andreacortis$ docker run -p <IP_ADDRESS>:3030:3030 -i -d -t pengines

Gundam:my_codes andreacortis$ docker ps
CONTAINER ID        IMAGE               COMMAND                  CREATED             STATUS              PORTS                    NAMES
c988c1b8f54e        pengines            "swipl daemon.pl --p…"   16 minutes ago      Up 16 minutes       <IP_ADDRESS>:3030->3030/tcp   elegant_noether

the server is up and running
Gundam:my_codes andreacortis$ curl http://<IP_ADDRESS>:3030/docs/index.html
<!DOCTYPE html>
<html lang="en">
   <head>
      <!-- Meta, title, CSS, favicons, etc. -->
      <meta charset="utf-8">
      <meta name="viewport" content="width=device-width, initial-scale=1.0">
      <meta name="description" content="">
      <meta name="author" content="">
      <title>
[...]

I want the code to: reproduce the example at https://github.com/ian-andrich/PythonPengines
by using these commands in python:
from pengines.Builder import PengineBuilder
from pengines.Pengine import Pengine
pengine_builder = PengineBuilder(urlserver="http://<IP_ADDRESS>:3030")

In [20]: pengine = Pengine(builder=pengine_builder,slave_limit=1, debug=True)
Starting call.
Starting post request with URL http://<IP_ADDRESS>:3030/pengine/create, content_type: application/json, and body: {"chunk": 100, "format": "json"}
Starting Post request.
URL is:  http://<IP_ADDRESS>:3030/pengine/create
Data (body) :  b'{"chunk": 100, "format": "json"}'
Headers:  {'User-Agent': 'PythonPengine', 'Accept': 'application/json', 'Accept-Language': 'en-us,en;q=0.5', 'Content-type': 'application/json'}
response_string is : {
  "event":"create",
  "id":"84ec823c-c2dc-4993-86f5-7d64d8ee996f",
  "slave_limit":3
}
{'event': 'create', 'id': '84ec823c-c2dc-4993-86f5-7d64d8ee996f', 'slave_limit': 3}
Initialization complete.

In [21]: query = "X = 3, writeln(X)"
    ...: pengine.ask(query)
    ...: print(pengine.currentQuery.availProofs)
Starting the call to ask.
Current state is idle
Initializing query with query: X = 3, writeln(X)
Call to ask is complete
[]

I am not getting anything back and I do not understand if this is a prolog issue or a python issue.
By the way, I also get an empty list by trying the query
query = "member(X, [1,2,3])"
pengine.ask(query)
print(pengine.currentQuery.availProofs)
or any other query.

Any advice, please?
Thanks
Andrea

@cmungall We aren't having this problem in the test suite are we?

@andreaBelmont Please take a look at our test suite and travis ci stuff.
@cmungall Uses a comparable docker based set up for running the Pengine, and our tests don't seem to be having problems.
I suspect at least part of the problem is our documentation is out of date.

Just saw this: I am going to take a look.

@andreaBelmont Let me know if it's not making sense.

You are right, I am now able to run the query by first running the docker container
docker run -d -p 4242:9083 -e PORT=9083 --name sparqlprog_pengines cmungall/sparqlprog

and then using it from python
In [1]: from pengines.Builder import PengineBuilder
   ...: from pengines.Pengine import Pengine
   ...: q = "member(X, [1,2,3])"
   ...: factory = PengineBuilder(urlserver="http://localhost:4242", destroy=False, ask=q)
   ...: pengine = Pengine(builder=factory, debug=False)
   ...: results = pengine.currentQuery.availProofs
   ...: print(results)
[{'X': 1}, {'X': 2}, {'X': 3}]


RuntimeError: NCCL error in: /pytorch/torch/lib/c10d/ProcessGroupNCCL.cpp:911, unhandled system error, NCCL version 2.7.8

i have crazy,help me please
Traceback (most recent call last):
File "./train_sup_change.py", line 48, in
blob = trainer.run(after_construct_launcher_callbacks=[register_evaluate_fn])
File "/home/cy/miniconda3/envs/STAnet/lib/python3.8/site-packages/ever/api/trainer/th_amp_ddp_trainer.py", line 98, in run
kwargs.update(dict(model=self.make_model()))
File "/home/cy/miniconda3/envs/STAnet/lib/python3.8/site-packages/ever/api/trainer/th_amp_ddp_trainer.py", line 87, in make_model
model = nn.parallel.DistributedDataParallel(
File "/home/cy/miniconda3/envs/STAnet/lib/python3.8/site-packages/torch/nn/parallel/distributed.py", line 496, in init
dist._verify_model_across_ranks(self.process_group, parameters)
RuntimeError: NCCL error in: /pytorch/torch/lib/c10d/ProcessGroupNCCL.cpp:911, unhandled system error, NCCL version 2.7.8
ncclSystemError: System call (socket, malloc, munmap, etc) failed.
ERROR:torch.distributed.elastic.multiprocessing.api:failed (exitcode: 1) local_rank: 0 (pid: 31335) of binary: /home/cy/miniconda3/envs/STAnet/bin/python
ERROR:torch.distributed.elastic.agent.server.local_elastic_agent:[default] Worker group failed

Sorry, by this information you provided, I can't get why the problem happened.
In our testing environment, the training scripts both worked well.
PyTorch == 1.7.0
python == 3.7
cuda == 10.1


Decorating interface is still a recipe for disaster

Recently got a bad crash in Document Intelligence spec because an interface had the versioning metadata but that won't get carried over to the client.tsp that use op is
We added a linter rule but that is limited to http route and even in this case it wouldn't help as there is linting rule warning it would still keep going and crash.

Could we have something like that
@useOperation(T)
op Ref<T extends TypeSpec.Reflection.Operation>(): never;

and in client.tsp
@client({service: FooService})
namespace FooClient {
  op getPet is Ref<FooService.Pets.geet>;
  op listPets is Ref<FooService.Pets.list>;

}

of course emitters will need to understand this new "operation" + decorator


soc: nxp: lpc55xxx: fix dependencies for SOC_FLASH_MCUX

SOC_FLASH_MCUX has additional dependencies for LPC55xxx CPUs, due to the fact that the flash should be disabled when executing in nonsecure mode.
Since the merge of HWMv2, this dependency has been set incorrectly at the SOC level, resulting in the IAP flash driver being enabled when targeting CPU1, which is incorrect. Fix the Kconfig dependency to resolve this issue.
Fixes #79576

due to the fact that the flash should be disabled when executing in nonsecure mode.
Fine for TFM/ns case.
But for a multicore use case (without TFM/ns) both CPU0 and CPU1 should have access the Flash ROM API. Right?

But for a multicore use case (without TFM/ns) both CPU0 and CPU1 should have access the Flash ROM API. Right?

I believe so. As far as I know, this isn't a technical restriction, we just don't have flash support enabled for CPU1 right now, so the Kconfig dependency here was incorrect.


"Reactivity->Updating arrays and objects" lesson doesn't work

The original code doesn't react:
numbers.push(numbers.length + 1);
numbers.numbers;

And neither does the new code: numbers = [...numbers, numbers.length + 1];
This is in the most recent version of Brave browser: Version 1.58.129 Chromium: 117.0.5938.88 (Official Build) (64-bit)

Oh silly me, I think the dev server just got an error. I had to refresh 🤦♂


solved the issue of duplicate statements on contributing.md

Signed-off-by: shubham-tyagi<EMAIL_ADDRESS>Description
solved the issue of duplicate statements on contributing.md more modification.

There was an English contributing docs file under Spanish docs folder.
Now suggested reading component could be used for Spanish language as well.

This PR fixes #
Notes for Reviewers
Please see if I missed something or if there is anything else needed to be done.
Signed commits

[ ] Yes, I signed my commits.

🚀 Preview for commit c1bbea44c601e50476e44dfac188f8b2dc57cc29 at: https://61b73a172de32cecfd893ee4--meshery-docs-preview.netlify.app