trillian: 1.6.0 -> 1.6.1

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://github.com/google/trillian/releases.
meta.description for trillian is: Transparent, highly scalable and cryptographically verifiable data store
meta.homepage for trillian is: https://github.com/google/trillian
Updates performed

Golang update

To inspect upstream changes

Release on GitHub

Compare changes on GitHub

Impact
Checks done

built on NixOS
The tests defined in passthru.tests, if any, passed
found 1.6.1 in filename of file in /nix/store/61k4nk1nz5vvyf9z6bd4frnh1rz4952h-trillian-1.6.1

Rebuild report (if merged into master) (click to expand)

2 total rebuild path(s)

2 package rebuild(s)

First fifty rebuilds by attrpath

trillian

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/61k4nk1nz5vvyf9z6bd4frnh1rz4952h-trillian-1.6.1 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A trillian https://github.com/r-ryantm/nixpkgs/archive/29bc1320208295f630b169d8e9b0d1e8ab9844c3.tar.gz

Or:
nix build github:r-ryantm/nixpkgs/29bc1320208295f630b169d8e9b0d1e8ab9844c3#trillian

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/61k4nk1nz5vvyf9z6bd4frnh1rz4952h-trillian-1.6.1
ls -la /nix/store/61k4nk1nz5vvyf9z6bd4frnh1rz4952h-trillian-1.6.1/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1

1 package built:

trillian

Maintainer pings
cc @adisbladis for testing.

[!TIP]
As a maintainer, if your package is located under pkgs/by-name/*, you can comment @NixOS/nixpkgs-merge-bot merge to automatically merge this update using the nixpkgs-merge-bot.

Add a :+1: reaction to pull requests you find important.

Result of nixpkgs-review pr 339440 run on aarch64-darwin 1

1 package built:

trillian


CUDA memory requirement

@yxlu-0102
I would like to check what is the minimum vram to run this model. I have a 2070Super and running into OOM error.
    skip = torch.cat([x, skip], dim=1)
torch.cuda.OutOfMemoryError: CUDA out of memory. Tried to allocate 1.84 GiB (GPU 0; 8.00 GiB total capacity; 5.63 GiB already allocated; 455.00 MiB free; 5.65 GiB reserved in total by PyTorch) If reserved memory is >> allocated memory try setting max_split_size_mb to avoid fragmentation.  See documentation for Memory Management and PYTORCH_CUDA_ALLOC_CONF

I used two 3090ti GPUs to train the MP-SENet model, each with a memory size of 24 GB.

@yxlu-0102
Is it the same for inference?

One GPU with a memory size of 24 GB is enough for the inference process.

@yxlu-0102
I just tried inferencing on my 3090ti, and I am still getting OOM error. Is there a way to reduce the memory usage?

Due to the variable length of speech, the memory consumption for generating each speech is not fixed, and it doesn't depend on whether the GPU is a 3090 or not. It primarily depends on the amount of GPU memory you have.
During training, you can reduce GPU memory usage by adjusting the batch size and segment length, but this may have an impact on the training results.


SPA_POD_BUILDER_INIT issue

Was just compiling the latest wf-recorder against pipewire on nix. and got this issue
Running phase: unpackPhase
@nix { "action": "setPhase", "phase": "unpackPhase" }
unpacking source archive /nix/store/mlcvl0v0nwplcbff6l35y37bs7xmp838-source
source root is source
Running phase: patchPhase
@nix { "action": "setPhase", "phase": "patchPhase" }
Running phase: updateAutotoolsGnuConfigScriptsPhase
@nix { "action": "setPhase", "phase": "updateAutotoolsGnuConfigScriptsPhase" }
Running phase: configurePhase
@nix { "action": "setPhase", "phase": "configurePhase" }
mesonConfigurePhase flags: --prefix=/nix/store/j98jqs07jj525kbcdwfxbig0d1j74azf-wf-recorder-0.5.0 --libdir=/nix/store/j98jqs07jj525kbcdwfxbig0d1j74azf-wf-recorder-0.5.0/lib --libexecdir=/nix/store/j98jqs07jj525kbcdwfxbig0d1j74azf-wf-recorder-0.5.0/libexec --bindir=/nix/store/j98jqs07jj525kbcdwfxbig0d1j74azf-wf-recorder-0.5.0/bin --sbindir=/nix/store/j98jqs07jj525kbcdwfxbig0d1j74azf-wf-recorder-0.5.0/sbin --includedir=/nix/store/j98jqs07jj525kbcdwfxbig0d1j74azf-wf-recorder-0.5.0/include --mandir=/nix/store/j98jqs07jj525kbcdwfxbig0d1j74azf-wf-recorder-0.5.0/share/man --infodir=/nix/store/j98jqs07jj525kbcdwfxbig0d1j74azf-wf-recorder-0.5.0/share/info --localedir=/nix/store/j98jqs07jj525kbcdwfxbig0d1j74azf-wf-recorder-0.5.0/share/locale -Dauto_features=enabled -Dwrap_mode=nodownload --buildtype=plain
The Meson build system
Version: 1.5.2
Source dir: /build/source
Build dir: /build/source/build
Build type: native build
Project name: wf-recorder
Project version: 0.5.0
C compiler for the host machine: gcc (gcc 13.3.0 "gcc (GCC) 13.3.0")
C linker for the host machine: gcc ld.bfd 2.43.1
C++ compiler for the host machine: g++ (gcc 13.3.0 "g++ (GCC) 13.3.0")
C++ linker for the host machine: g++ ld.bfd 2.43.1
Host machine cpu family: x86_64
Host machine cpu: x86_64
Program git found: NO
Found pkg-config: YES (/nix/store/946chn5ja4yrvnnc5izwv792cc57xpy8-pkg-config-wrapper-0.29.2/bin/pkg-config) 0.29.2
Run-time dependency wayland-client found: YES 1.23.1
Run-time dependency wayland-protocols found: YES 1.38
Run-time dependency libpulse-simple found: YES 17.0
Run-time dependency libpipewire-0.3 found: YES 1.2.5
Message: Using default audio backend: auto
Run-time dependency libavutil found: YES 59.39.100
Run-time dependency libavcodec found: YES 61.19.100
Run-time dependency libavformat found: YES 61.7.100
Run-time dependency libavdevice found: YES 61.3.100
Run-time dependency libavfilter found: YES 10.4.100
Run-time dependency libswresample found: YES 5.3.100
Run-time dependency threads found: YES
Run-time dependency gbm found: YES 24.2.5
Run-time dependency libdrm found: YES 2.4.123
Configuring config.h using configuration
Program wayland-scanner found: YES (/nix/store/ww53l1gfyxka2n94wllv9kfm0g9m87a4-wayland-scanner-1.23.1-bin/bin/wayland-scanner)
Message:
----------------
wf-recorder 0.5.0
----------------
Default audio backend: pulse
  - pulse: true
  - pipewire: true
Build targets in project: 2

wf-recorder 0.5.0

  User defined options
    auto_features: enabled
    bindir       : /nix/store/j98jqs07jj525kbcdwfxbig0d1j74azf-wf-recorder-0.5.0/bin
    buildtype    : plain
    includedir   : /nix/store/j98jqs07jj525kbcdwfxbig0d1j74azf-wf-recorder-0.5.0/include
    infodir      : /nix/store/j98jqs07jj525kbcdwfxbig0d1j74azf-wf-recorder-0.5.0/share/info
    libdir       : /nix/store/j98jqs07jj525kbcdwfxbig0d1j74azf-wf-recorder-0.5.0/lib
    libexecdir   : /nix/store/j98jqs07jj525kbcdwfxbig0d1j74azf-wf-recorder-0.5.0/libexec
    localedir    : /nix/store/j98jqs07jj525kbcdwfxbig0d1j74azf-wf-recorder-0.5.0/share/locale
    mandir       : /nix/store/j98jqs07jj525kbcdwfxbig0d1j74azf-wf-recorder-0.5.0/share/man
    prefix       : /nix/store/j98jqs07jj525kbcdwfxbig0d1j74azf-wf-recorder-0.5.0
    sbindir      : /nix/store/j98jqs07jj525kbcdwfxbig0d1j74azf-wf-recorder-0.5.0/sbin
    wrap_mode    : nodownload

Found ninja-1.12.1 at /nix/store/m5d2zsm9252fdr825lahyqxpn2av8136-ninja-1.12.1/bin/ninja
mesonConfigurePhase: enabled\ parallel\ building
Running phase: buildPhase
@nix { "action": "setPhase", "phase": "buildPhase" }
build flags: -j16
[1/20] Generating 'proto/libwl_protos.a.p/xdg-output-unstable-v1-protocol.c'
[2/20] Generating 'proto/libwl_protos.a.p/wlr-screencopy-unstable-v1-protocol.c'
[3/20] Generating 'proto/libwl_protos.a.p/xdg-output-unstable-v1-client-protocol.h'
[4/20] Generating 'proto/libwl_protos.a.p/linux-dmabuf-unstable-v1-protocol.c'
[5/20] Generating 'proto/libwl_protos.a.p/wlr-screencopy-unstable-v1-client-protocol.h'
[6/20] Generating 'wf-recorder.p/xdg-output-unstable-v1-client-protocol.h'
[7/20] Generating 'proto/libwl_protos.a.p/linux-dmabuf-unstable-v1-client-protocol.h'
[8/20] Generating 'wf-recorder.p/linux-dmabuf-unstable-v1-client-protocol.h'
[9/20] Generating 'wf-recorder.p/wlr-screencopy-unstable-v1-client-protocol.h'
[10/20] Compiling C object wf-recorder.p/src_averr.c.o
[11/20] Compiling C object proto/libwl_protos.a.p/meson-generated_wlr-screencopy-unstable-v1-protocol.c.o
[12/20] Compiling C object proto/libwl_protos.a.p/meson-generated_xdg-output-unstable-v1-protocol.c.o
[13/20] Compiling C object proto/libwl_protos.a.p/meson-generated_linux-dmabuf-unstable-v1-protocol.c.o
[14/20] Linking static target proto/libwl_protos.a
[15/20] Compiling C++ object wf-recorder.p/src_audio.cpp.o
[16/20] Compiling C++ object wf-recorder.p/src_pulse.cpp.o
[17/20] Compiling C++ object wf-recorder.p/src_frame-writer.cpp.o
FAILED: wf-recorder.p/src_frame-writer.cpp.o
g++ -Iwf-recorder.p -I. -I.. -I/nix/store/3336f1n8bj16f9pypnxmkjang2w8vcah-wayland-1.23.1-dev/include -I/nix/store/h0j33vqdmai1jvzlb89ilnkf5vqzn0zn-ffmpeg-7.1-dev/include -I/nix/store/jblzyd8dzz5vwmw6z3p6bzkxxkwffayf-mesa-24.2.5-dev/include -I/nix/store/lp2mk0k2qx41y2hln8vdbi003i434vr3-libdrm-2.4.123-dev/include -I/nix/store/lp2mk0k2qx41y2hln8vdbi003i434vr3-libdrm-2.4.123-dev/include/libdrm -I/nix/store/ipjdmzq8w2vc36lysgsg20f59jdbv673-libpulseaudio-17.0-dev/include -I/nix/store/n4865ip986ymcsiwblm5ff89ybln9nw1-pipewire-1.2.5-dev/include/pipewire-0.3 -I/nix/store/n4865ip986ymcsiwblm5ff89ybln9nw1-pipewire-1.2.5-dev/include/spa-0.2 -fdiagnostics-color=always -D_GLIBCXX_ASSERTIONS=1 -D_FILE_OFFSET_BITS=64 -Wall -Winvalid-pch -Wextra -std=c++17 '-DWFRECORDER_VERSION="0.5.0"' -Wno-deprecated-declarations -D_REENTRANT -pthread -MD -MQ wf-recorder.p/src_frame-writer.cpp.o -MF wf-recorder.p/src_frame-writer.cpp.o.d -o wf-recorder.p/src_frame-writer.cpp.o -c ../src/frame-writer.cpp
../src/frame-writer.cpp: In member function 'void FrameWriter::init_video_filters(const AVCodec*)':
../src/frame-writer.cpp:374:53: error: 'AVFilterLink' {aka 'struct AVFilterLink'} has no member named 'frame_rate'
  374 |     this->videoCodecCtx->framerate = filter_output->frame_rate; // can be 1/0 if unknown
      |                                                     ^~~~~~~~~~
[18/20] Compiling C++ object wf-recorder.p/src_pipewire.cpp.o
In file included from /nix/store/n4865ip986ymcsiwblm5ff89ybln9nw1-pipewire-1.2.5-dev/include/spa-0.2/spa/param/audio/format-utils.h:12,
                 from ../src/pipewire.cpp:4:
/nix/store/n4865ip986ymcsiwblm5ff89ybln9nw1-pipewire-1.2.5-dev/include/spa-0.2/spa/pod/parser.h: In function 'void spa_pod_parser_init(spa_pod_parser*, const void*, uint32_t)':
/nix/store/n4865ip986ymcsiwblm5ff89ybln9nw1-pipewire-1.2.5-dev/include/spa-0.2/spa/pod/parser.h:36:94: warning: missing initializer for member 'spa_pod_parser_state::flags' [-Wmissing-field-initializers]
   36 | #define SPA_POD_PARSER_INIT(buffer,size)  ((struct spa_pod_parser){ (buffer), (size), 0, {0} })
      |                                                                                ^
/nix/store/n4865ip986ymcsiwblm5ff89ybln9nw1-pipewire-1.2.5-dev/include/spa-0.2/spa/pod/parser.h:41:19: note: in expansion of macro 'SPA_POD_PARSER_INIT'
   41 |         *parser = SPA_POD_PARSER_INIT(data, size);
      |                   ^~~~~~~~~~~~~~~~~~~
/nix/store/n4865ip986ymcsiwblm5ff89ybln9nw1-pipewire-1.2.5-dev/include/spa-0.2/spa/pod/parser.h:36:94: warning: missing initializer for member 'spa_pod_parser_state::frame' [-Wmissing-field-initializers]
   36 | #define SPA_POD_PARSER_INIT(buffer,size)  ((struct spa_pod_parser){ (buffer), (size), 0, {0} })
      |                                                                                ^
/nix/store/n4865ip986ymcsiwblm5ff89ybln9nw1-pipewire-1.2.5-dev/include/spa-0.2/spa/pod/parser.h:41:19: note: in expansion of macro 'SPA_POD_PARSER_INIT'
   41 |         *parser = SPA_POD_PARSER_INIT(data, size);
      |                   ^~~~~~~~~~~~~~~~~~~
In file included from /nix/store/n4865ip986ymcsiwblm5ff89ybln9nw1-pipewire-1.2.5-dev/include/spa-0.2/spa/param/audio/format-utils.h:13:
/nix/store/n4865ip986ymcsiwblm5ff89ybln9nw1-pipewire-1.2.5-dev/include/spa-0.2/spa/pod/builder.h: In function 'void spa_pod_builder_init(spa_pod_builder*, void*, uint32_t)':
/nix/store/n4865ip986ymcsiwblm5ff89ybln9nw1-pipewire-1.2.5-dev/include/spa-0.2/spa/pod/builder.h:52:101: warning: missing initializer for member 'spa_pod_builder_state::flags' [-Wmissing-field-initializers]
   52 | #define SPA_POD_BUILDER_INIT(buffer,size)  ((struct spa_pod_builder){ (buffer), (size), 0, {0}, {0} })
      |                                                                                ^
/nix/store/n4865ip986ymcsiwblm5ff89ybln9nw1-pipewire-1.2.5-dev/include/spa-0.2/spa/pod/builder.h:79:20: note: in expansion of macro 'SPA_POD_BUILDER_INIT'
   79 |         *builder = SPA_POD_BUILDER_INIT(data, size);
      |                    ^~~~~~~~~~~~~~~~~~~~
/nix/store/n4865ip986ymcsiwblm5ff89ybln9nw1-pipewire-1.2.5-dev/include/spa-0.2/spa/pod/builder.h:52:101: warning: missing initializer for member 'spa_pod_builder_state::frame' [-Wmissing-field-initializers]
   52 | #define SPA_POD_BUILDER_INIT(buffer,size)  ((struct spa_pod_builder){ (buffer), (size), 0, {0}, {0} })
      |                                                                                ^
/nix/store/n4865ip986ymcsiwblm5ff89ybln9nw1-pipewire-1.2.5-dev/include/spa-0.2/spa/pod/builder.h:79:20: note: in expansion of macro 'SPA_POD_BUILDER_INIT'
   79 |         *builder = SPA_POD_BUILDER_INIT(data, size);
      |                    ^~~~~~~~~~~~~~~~~~~~
/nix/store/n4865ip986ymcsiwblm5ff89ybln9nw1-pipewire-1.2.5-dev/include/spa-0.2/spa/pod/builder.h:52:101: warning: missing initializer for member 'spa_callbacks::data' [-Wmissing-field-initializers]
   52 | #define SPA_POD_BUILDER_INIT(buffer,size)  ((struct spa_pod_builder){ (buffer), (size), 0, {0}, {0} })
      |                                                                                ^
/nix/store/n4865ip986ymcsiwblm5ff89ybln9nw1-pipewire-1.2.5-dev/include/spa-0.2/spa/pod/builder.h:79:20: note: in expansion of macro 'SPA_POD_BUILDER_INIT'
   79 |         *builder = SPA_POD_BUILDER_INIT(data, size);
      |                    ^~~~~~~~~~~~~~~~~~~~
../src/pipewire.cpp: In member function 'virtual void PipeWireReader::start()':
/nix/store/n4865ip986ymcsiwblm5ff89ybln9nw1-pipewire-1.2.5-dev/include/spa-0.2/spa/pod/builder.h:52:101: warning: missing initializer for member 'spa_pod_builder_state::flags' [-Wmissing-field-initializers]
   52 | #define SPA_POD_BUILDER_INIT(buffer,size)  ((struct spa_pod_builder){ (buffer), (size), 0, {0}, {0} })
      |                                                                                ^
../src/pipewire.cpp:191:32: note: in expansion of macro 'SPA_POD_BUILDER_INIT'
  191 |     struct spa_pod_builder b = SPA_POD_BUILDER_INIT(buffer, sizeof(buffer));
      |                                ^~~~~~~~~~~~~~~~~~~~
/nix/store/n4865ip986ymcsiwblm5ff89ybln9nw1-pipewire-1.2.5-dev/include/spa-0.2/spa/pod/builder.h:52:101: warning: missing initializer for member 'spa_pod_builder_state::frame' [-Wmissing-field-initializers]
   52 | #define SPA_POD_BUILDER_INIT(buffer,size)  ((struct spa_pod_builder){ (buffer), (size), 0, {0}, {0} })
      |                                                                                ^
../src/pipewire.cpp:191:32: note: in expansion of macro 'SPA_POD_BUILDER_INIT'
  191 |     struct spa_pod_builder b = SPA_POD_BUILDER_INIT(buffer, sizeof(buffer));
      |                                ^~~~~~~~~~~~~~~~~~~~
/nix/store/n4865ip986ymcsiwblm5ff89ybln9nw1-pipewire-1.2.5-dev/include/spa-0.2/spa/pod/builder.h:52:101: warning: missing initializer for member 'spa_callbacks::data' [-Wmissing-field-initializers]
   52 | #define SPA_POD_BUILDER_INIT(buffer,size)  ((struct spa_pod_builder){ (buffer), (size), 0, {0}, {0} })
      |                                                                                ^
../src/pipewire.cpp:191:32: note: in expansion of macro 'SPA_POD_BUILDER_INIT'
  191 |     struct spa_pod_builder b = SPA_POD_BUILDER_INIT(buffer, sizeof(buffer));
      |                                ^~~~~~~~~~~~~~~~~~~~
[19/20] Compiling C++ object wf-recorder.p/src_main.cpp.o
ninja: build stopped: subcommand failed.

It looks like you need latest wf-recorder with this commit. The rest of the output are warnings related to pipewire. You can disable pipewire with -Dpipewire=disabled if you would like.


Fix infinite loop in ExcessiveDocstringSpacing

TL;DR: Reproduction
Leading/trailing non-ASCII whitespace triggers an infinite loop error.
ruby -e 'File.open("spec/file_spec.rb", "w+") { |f| f.puts "describe \'\u00a0foo\' do; end" }'
bundle exec rubocop --only RSpec/ExcessiveDocstringSpacing -a spec/file_spec.rb

Slightly longer
The test predicate for RSpec/ExcessiveDocstringSpacing now flags leading and trailing text matching [[:blank:]], but the corrector still calls strip[^1].  POSIX bracket expressions match non-ASCII characters, but strip only removes ASCII whitespace. The correction does not remove the offense. As a result, leading/trailing non-ASCII whitespace triggers an infinite correction loop, since the corrector doesn't remove the offending pattern.
Details
In 408e69be903f1114e44e2f1ea8ef70d8c02cf279, the test predicate for excessive whitespace was changed to use [[:blank:]]:
         def excessive_whitespace?(text)
-          return true if text.start_with?(' ') || text.end_with?(' ')
-
-          text.match?(/[^\n ]  +[^ ]/)
+          text.match?(/
+            # Leading space
+            \A[[:blank:]]
+            |
+            # Trailing space
+            [[:blank:]]\z
+            |
+            # Two or more consecutive spaces, except if they are leading spaces
+            [^[[:space:]]][[:blank:]]{2,}[^[[:blank:]]]
+          /x)
         end

But the corrector method continued to use strip for leading/trailing whitespace, only using [[:blank:]] for internal whitespace:
         # @param text [String]
         def strip_excessive_whitespace(text)
-          text.strip.gsub(/  +/, ' ')
+          text.strip.gsub(/[[:blank:]]{2,}/, ' ')
         end

The test predicate now flags leading and trailing text matching [[:blank:]], but the corrector still calls strip. POSIX bracket expressions like [[:blank:]] match non-ASCII characters, but  strip only removes ASCII whitespace. Calling the corrector does not correct the problem. As a result, leading/trailing non-ASCII whitespace triggers an infinite correction loop.
[^1]: I've hard-coded the commit SHAs to the current master referent to keep it working into the future, but today, August 14, 2023, those point to today's master, 408e69be903f1114e44e2f1ea8ef70d8c02cf279.)

Before submitting the PR make sure the following are checked:

[X] Feature branch is up-to-date with master (if not - rebase it).
[X] Squashed related commits together.
[X] Added tests.
[X] Updated documentation.
[X] Added an entry to the CHANGELOG.md if the new code introduces user-observable changes.
[X] The build (bundle exec rake) passes (be sure to run this locally, since it may produce updated documentation that you will need to commit).

If you have created a new cop:

[ ] Added the new cop to config/default.yml.
[ ] The cop is configured as Enabled: pending in config/default.yml.
[ ] The cop is configured as Enabled: true in .rubocop.yml.
[ ] The cop documents examples of good and bad code.
[ ] The tests assert both that bad code is reported and that good code is not reported.
[ ] Set VersionAdded: "<<next>>" in default/config.yml.

If you have modified an existing cop's configuration options:

[ ] Set VersionChanged: "<<next>>" in config/default.yml.

I left the actual character in the test to match existing convention, but since the file now has several whitespace characters that can't be visually differentiated, it might make sense to switch out the em space for "\u3000" and the non-breaking space for "\u00a0". Let me know if you'd like me to make that change.

it might make sense to switch out the em space for "\u3000" and the non-breaking space for "\u00a0". Let me know if you'd like me to make that change.

Certainly, that's right. Can you make the changes? It's fine to squash the commits into one.


About KITTI data set reading problems

As we all know, KITTI's official data set is stored as .bin format, while your code is read in .ply format. I wonder if I made a mistake.

In our code, we wanted to unify the reading of LiDAR data with a single format of binary type ply with timestamp. Indeed, KITTI distributes its Velodyne data in .bin but without timestamp. We provide KITTI data converted to ply binary downloadable in this folder: https://cloud.mines-paristech.fr/index.php/s/UwgVFtiTOmrgKp5 The password is : npm3d

Hello, the KITTI data processed by you is too large for me to download, can you provide the processing scripts to convert the original *.bin in KITTI odometry to *.ply? In that way, I can do that processing step myself.


Error in ranges of GHSA-jjjh-jjxp-wpff.json

Hi,
It seems that there is a mistake in the advisory GHSA-jjjh-jjxp-wpff.json.
https://github.com/github/advisory-database/blob/main/advisories/github-reviewed/2022/10/GHSA-jjjh-jjxp-wpff/GHSA-jjjh-jjxp-wpff.json
"ranges": [
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "0"
},
{
"fixed": "<IP_ADDRESS>"
}
]
}
],
According to the ranges, the fix is in version <IP_ADDRESS> and the correct patch is in the version <IP_ADDRESS>.
So, the correct range should be:
"ranges": [
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "0"
},
{
"fixed": "<IP_ADDRESS>"
}
]
}
],
Thank you!

Hi @xaldama, https://github.com/advisories/GHSA-jjjh-jjxp-wpff should show <IP_ADDRESS> as patched now!


GoogleMaps Streetview -> Shadowmap issue

Just stumbeled upon a bug: when coming from a Streetview URL the transition to Shadowmap does not work:
https://www.google.com/maps/@48.2053598,16.3534625,3a,75y,97.74h,76.29t/data=!3m6!1e1!3m4!1so90_Nz1TkotTDYyW0_zCbQ!2e0!7i16384!8i8192
turns into
https://app.shadowmap.org/?lat=48.2053598,16.3534625,3a,75y&lng=97.74h&zoom=15
which then turns into
https://app.shadowmap.org/?lat=48.20536&lng=97.74000&zoom=15&vq=2&time=1647957057724&basemap=map
happens on Firefox and Chrome

created a pull request for a fix: https://github.com/ShadowmapTechnologies/LocationBrowserExtension/pull/6


Subscribe (sandbox.on) to all events

Hey..
I would really like a subscribe to anything-option for the built in meditator.
something like
sandbox.on(function(msg, ...) {
});
or
sandbox.on('*', function(msg, ...) {
});

As an option you could create a channel with the name * and pipe all events to it.


Feature request: Third-party generator support

Inspired by prisma generator feature. I find it very useful for generating json/types/schemas/validators/trpc/etc. The idea is to have a plugin type function that has access to the underlying orm schema/types with the ability to automatically generate and output code based on that.
Use cases include generating custom CRUD types, various API schema/routes patterns (trpc, openAPI, graphQL), non-zod validators, running complex multi-schema migrations, etc
I guess the main challenge is the entry point fur such function. Prisma includes/requires a convenient generation step for that purpose. In the case of orchid-orm this could be part of the connection configuration and can be conditionally (necessary for production builds) triggered during initialization. The user than installs the package which includes predifined initialization function accepting the schema and handles the rest. Bonus points for compatibility with Prisma generators (not sure how feasible that is).
In terms of syntax it could look like something like this:
orchidORM({
  // databaseURL has the following format:
  // postgres://user:password@localhost:5432/dbname
  //
  // ssl option can be specified as a parameter:
  // postgres://user:password@localhost:5432/dbname?ssl=true
  databaseURL: process.env.DATABASE_URL,

  // ssl can also be specified as an option:
  ssl: true,
  generators: [
    {
       name: 'orchid-orm-trpc-generator',
       config: { ... },
       enabled: process.env.MODE === 'development',
    }
  ]

  log: true, // option for logging, false by default
  autoPreparedStatements: true, // see in query builder setup docs, false by default
  noPrimaryKey: 'ignore', // see in query builder setup docs, 'error' by default
}, {
  user: UserTable,
  message: MessageTable,
})

PS: Let me know, if I am missing something. I have a couple of more features in mind that I shared on reddit. I can follow the above template to create issues for them. OrchidORM looks really promising, I would love to also help with the project, so I will stay in touch once I free up my schedule a bit.

This sounds very useful and interesting!
I see Prisma has a lot of generators for various frameworks. tRPC is a good starting point.
Making it compatible with Prisma would be a big win because all Prisma generators would work with Orchid.
So many ideas and everything to do, it would be awesome if other people could help.
And of course, create more issues if you have more ideas, sooner or later all will be done.


UI validation rules for the Provider resource name are not aligned with Kubernetes standards

A follow up for: #646
The current UI validation rules for the Provider resource name value are not aligned with Kubernetes DNS Subdomain Name standards.
Differences:

The '.' character is not allowed
Starts with an alphabet character instead of allowing to start with an alphanumeric character

cc:// @RichardHoch @anarnold97

@sgratch Please see my comment on https://issues.redhat.com/browse/MTV-684. Thanks.


Please keep ASTNodeTypeString consistent with current types

ASTNodeTypeString is missing types like CatchClause.
The team of prettier-plugin-solidity is considering using this fork to continue support for the language and a place like this list is a good place to see new types or deprecated ones (rather than searching through the codebase or solely relying on our tests).

Tagging @GNSPS cause no one seems to be watching this repo (at least that's what github says).

Yeah, I don't know why I wasn't watching! 😱 Thank you @fvictorio! These were some crazy days.
Looking into this now. But first impression is that since this is a generated file it might be a grammar problem. I thought I had included catch clauses but I'll check.

Actually, since we're not using the typescript definitions ourselves, if you guys want to throw some PRs my way, feel free to do so. Otherwise I'll take some time to review this specific issue!


Cleanup dependencies

@connor4312 Let's merge this in and then remove more stuff, please help me out 😄


Make nearest neighbor threshold configurable

should be set to a percentage of the most common word
should default to a reasonable value if not explicitly set

released as 0.14.0-v0.4.15 and 0.16.0-v0.4.15


Add Spring Boot client-side SSL example

This issue is stale because it has been open 170 days with no activity. Remove stale label or comment or this will be closed in 10 days


click apperance option and then black and no response

Version: 1.0.77
Platform: win32 6.1.7601
Plugins: altair, clickable-links, quick-cmds, scrollbar, shell-selector, theme-gruvbox, theme-windows10, title-control

this problem didn't accur upon new version any more


NIFI-9033: Defining Validators and default values for NifiStatelessCo…

…nnectors' DATA_FLOW name.

Thank you for submitting a contribution to Apache NiFi.
Please provide a short description of the PR here:
Defining Validator and default value for NifiStateless Connectors. Fixes bug NIFI-9033
In order to streamline the review of the contribution we ask you
to ensure the following steps have been taken:
For all changes:

[ ] Is there a JIRA ticket associated with this PR? Is it referenced
in the commit message?

[ ] Does your PR title start with NIFI-XXXX where XXXX is the JIRA number you are trying to resolve? Pay particular attention to the hyphen "-" character.

[ ] Has your PR been rebased against the latest commit within the target branch (typically main)?

[ ] Is your initial contribution a single, squashed commit? Additional commits in response to PR reviewer feedback should be made on this branch and pushed to allow change tracking. Do not squash or use --force when pushing to allow for clean monitoring of changes.

For code changes:

[ ] Have you ensured that the full suite of tests is executed via mvn -Pcontrib-check clean install at the root nifi folder?
[ ] Have you written or updated unit tests to verify your changes?
[ ] Have you verified that the full build is successful on JDK 8?
[ ] Have you verified that the full build is successful on JDK 11?
[ ] If adding new dependencies to the code, are these dependencies licensed in a way that is compatible for inclusion under ASF 2.0?
[ ] If applicable, have you updated the LICENSE file, including the main LICENSE file under nifi-assembly?
[ ] If applicable, have you updated the NOTICE file, including the main NOTICE file found under nifi-assembly?
[ ] If adding new Properties, have you added .displayName in addition to .name (programmatic access) for each of the new properties?

For documentation related changes:

[ ] Have you ensured that format looks appropriate for the output in which it is rendered?

Note:
Please ensure that once the PR is submitted, you check GitHub Actions CI for build issues and submit an update to your PR as soon as possible.

Thanks for the fix @in-park! All looks good to me. +1 merged to main


 I somewhat followed along with the approach in this blog to decouple things

@brittonhayes FYI these changes radically change the structure of the backend/ directory, but I think this new organization will be helpful going forward


Amplify Aurora serverless SQL injection

Hi There,
I'm using Amplify to create a GraphQL API with an Aurora Serverless datasource. I'm currently trying to fix a problem with an apostrophe that is breaking my query which is a completely different issue but now this makes me wonder if the default resolvers that Amplify generate when running amplify api add-graphql-datasource are susceptible to SQL injection.
I'd appreciate if you can clarify this.

Hi @geoffreyaguero the default resolvers use the input sanitization from the AppSync documentation: https://docs.aws.amazon.com/appsync/latest/devguide/tutorial-rds-resolvers.html#input-sanitization
That being said we encourage all customers to review their input vectors and apply additional controls if necessary.


Issue when running './build_docker.sh'

Have you solved it?

For this specific issue, this works on the Dockerfile:
FROM phusion/baseimage:latest-amd64
But there are other issues I am working on. I had the dockerbuild working but unable to start when running the image.
I will provide a PR when I finish with my test.

This should resolve the current issues: https://github.com/kongyew/greenplum-oss-docker/pull/6


Add renovate.json for deps update

/test ovn-operator-build-deploy-kuttl

Failures unrelated, kuttl jobs not required for this change, merged manually to update a ci patch.


Correction for raw affiliation School of Management, Economics and Mathematics, King’s University College at Western University Canada, London, Canada

Correction needed for raw affiliation School of Management, Economics and Mathematics, King’s University College at Western University Canada, London, Canada
raw_affiliation_name: School of Management, Economics and Mathematics, King’s University College at Western University Canada, London, Canada
new_rors: ;02grkyz14
previous_rors: 048f5b183;02grkyz14
works_examples: W4387872219;W4390237365
contact: 56b36e8cfbd235c8a0728d3f06b0a59b:0982d268fa97f95a @ uwo.ca

This issue was accepted and ingested by the OpenAlex team on 2024-12-21. The new affiliations should be visible within the next 7 days.


Array comparisons always result in polyEqual warning

Version
<IP_ADDRESS> (Latest)
Operating System

[X] Any
[ ] Linux
[ ] macOS
[ ] Windows
[ ] Other Unix

OS Version
No response
Processor

[X] Any
[ ] Arm (using Rosetta)
[ ] PowerPC
[ ] Sparc
[ ] x86 (32-bit)
[ ] x86-64 (64-bit)
[ ] Other

System Component
Core system
Severity
Minor
Description
The polyEqual warning is meant to warn users that the compiler is falling back to a non-synthesized equality test.
However, this warning occurs on completely legitimate uses on the array type.
Transcript
- val arr : char array = Array.array (10, #"x");
- arr = arr;
stdIn:2.5 Warning: calling polyEqual
val it = true : bool

Expected Behavior
- val arr : char array = Array.array (10, #"x");
- arr = arr;
val it = true : bool

This should probably not produce a warning even if the type is polymorphic, just like how ref works.
- fun myArrEq (a1 : 'a array, a2 : 'a array) : bool = a1 = a2;
val it = fn : 'a array * 'a array -> bool

Steps to Reproduce
Write = on arrays.
Additional Information
This is probably fairly easy to special-case for now, but the polyEqual warning needs an overhaul.
The warning should really be based on the type of expressions (ie. the warning should occur before the backend), rather than the contents of the optimized intermediate language.
We should be able to guarantee that all well-understood uses of op = are specialized.
Email address
skyler DOT soss AT gmail DOT com

The warning message just means that it is using the generic equality testing function, instead of a type-specialized test.

To address this issue, see the atomeq function in base/compiler/FLINT/trans/pequal.sml; there need to be cases added to handle array types.

Fixed for 110.99.7.


ARP: Rawns.Reddit-Wallpaper-Changer

Microsoft Reviewers: Open in CodeFlow

cc @ryfu-msft: you might have to remove the "Policy-Test-2.3" label for the PR to merge.

cc @ryfu-msft: you might have to remove the "Policy-Test-2.3" label from the PR so it can be merged.

Its actually the Changes Required on the wrong line that is making it not pass


How to get an Opportunity Sales Process / Stage / Selected Values

What I am attempting to do is get the selected values from the screen shot below:

Using the following function I can get the different Sales Processes:
Layouts SObject
 conn.sobject("Opportunity").layouts(function(err, meta) {
   if (err) { return console.error(err); }
   console.log(meta["recordTypeMappings"]);
 });

Results:
[
    {
        "available": true,
        "defaultRecordTypeMapping": true,
        "layoutId": "00h41000005Xx7fAAC",
        "master": false,
        "name": "New Business",
        "picklistsForRecordType": [],
        "recordTypeId": "01241000000vEPaAAM",
        "urls": {
            "layout": "/services/data/v37.0/sobjects/Opportunity/describe/layouts/01241000000vEPaAAM"
        }
    },
    {
        "available": true,
        "defaultRecordTypeMapping": false,
        "layoutId": "00h4100000401ZZAAY",
        "master": false,
        "name": "Renewal",
        "picklistsForRecordType": [],
        "recordTypeId": "01241000000vE4gAAE",
        "urls": {
            "layout": "/services/data/v37.0/sobjects/Opportunity/describe/layouts/01241000000vE4gAAE"
        }
    },
    {
        "available": true,
        "defaultRecordTypeMapping": false,
        "layoutId": "00h41000005Xx42AAC",
        "master": false,
        "name": "Win Back",
        "picklistsForRecordType": [],
        "recordTypeId": "01241000000vELDAA2",
        "urls": {
            "layout": "/services/data/v37.0/sobjects/Opportunity/describe/layouts/01241000000vELDAA2"
        }
    },
    {
        "available": true,
        "defaultRecordTypeMapping": false,
        "layoutId": "00h41000005Xx7fAAC",
        "master": true,
        "name": "Master",
        "picklistsForRecordType": [],
        "recordTypeId": "012000000000000AAA",
        "urls": {
            "layout": "/services/data/v37.0/sobjects/Opportunity/describe/layouts/012000000000000AAA"
        }
    }
]

Using the Salesforce Workbench: REST Explorer I am able to paste in the Renewal > "urls" > "layout": /services/data/v37.0/sobjects/Opportunity/describe/layouts/01241000000vE4gAAE and see that the values I am looking for are buried in the following path
editLayoutSections/[Item 1]/layoutRows/[Item 4]/layoutItems/Stage/layoutComponents/StageName/details/picklistValues

Is there a way in JSforce to get the picklistValues?

Found the following Pull Request #586 referencing layouts/recordTypeId

Using the following JSforce logic I was able to get what I was looking for:
var _request = {
    body: "",
    header: { "Content-Type": "application/json" },
    method: "get",
    url: "/services/data/v37.0/sobjects/Opportunity/describe/layouts/01241000000vE4gAAE"
};

conn.request(_request, function(err, resp) {
    if (err) return res.send(err.toString());
    console.log(resp["editLayoutSections"][0]["layoutRows"][3]["layoutItems"][1]["layoutComponents"][0]["details"]["picklistValues"]);
});

The original logic to get the picklistValues was not very dynamic, so with the help of the following code from Alex Quan I made the following changes:
function findObjects(obj, targetProp, targetValue, finalResults) {
    function getObject(theObject) {
        let result = null;
        if (theObject instanceof Array) {
            for (let i = 0; i < theObject.length; i++) {
                getObject(theObject[i]);
            }
        } else {
            for (let prop in theObject) {
                if (theObject.hasOwnProperty(prop)) {
                    if (prop === targetProp) {
                        if (theObject[prop] === targetValue) {
                            finalResults.push(theObject);
                        }
                    }
                    if (theObject[prop] instanceof Object || theObject[prop] instanceof Array) {
                        getObject(theObject[prop]);
                    }
                }
            }
        }
    }
    getObject(obj);
};

var _request = {
    body: "",
    header: { "Content-Type": "application/json" },
    method: "get",
    url: "/services/data/v37.0/sobjects/Opportunity/describe/layouts/01241000000vE4gAAE"
};

conn.request(_request, function(err, resp) {
    if (err) return res.send(err.toString());

    var StageNames = [];
    var Types = [];
    findObjects(myObject, 'name', 'StageName', StageNames);
    findObjects(myObject, 'name', 'Type', Types);
    console.log('StageNames: ', StageNames[0]["picklistValues"]);
    console.log('Types:', Types[0]["picklistValues"]);
});


Improve and clarify explicit endianness support

For some applications, choosing the endianness at the crate level is too coarse and users need to mix archive endianness within a single crate. A good example is a service that communicates with two other services, one that's big-endian and one that's little-endian. It should be able to make big-endian archives for one service and little-endian ones for the other.
Here's the proposed API:
#[derive(Archive, Serialize, Deserialize)]
struct Example {
    // This integer is archived as a little-endian i32
    #[with(LittleEndian)]
    a: i32,
    // This integer is archived as a big-endian i32
    #[with(BigEndian)]
    b: i32,
    // This integer is archived with dynamic endianness determined by the serializer
    #[with(DynamicEndian)]
    c: i32,
}

The little- and big- endian cases are fairly straightforward, mostly just wrapping types with rend::LittleEndian and rend::BigEndian respectively.
The DynamicEndian case is a little more complicated. It will require a serializer trait (Endianness?) that provides the endianness that the type should be serialized with. Likewise, the endianness trait will be required during validation and deserialization to make sure that types are handled correctly. Maybe this portion would be better to separate into a separate crate?

Just a small note that DynamicEndian would mirror the endianness handling we have now, for cases where a library wants to leave the endianness up to their users (probably for performance reasons). This design would allow the users of a library to specify the endianness at the site instead.

Oh another nice extension that would be quite nice to add to the api would be allowing #[with(LittleEndian)] on types containing #[with(DynamicEndian)], so that we can still use the declarative API for it. Though this is trickier with the restriction of needing the DynamicEndian attribute, I think it's still worth exploring

Following more discussion in the Discord server, here's a design I think suits us best:
Step 1. Implement the traits for rend::{LittleEndian, BigEndian}
This enables type authors to declaratively fix the endianness of their primitives to native endian (i32), little endian (i32_le) or big endian (i32_be).
Extensions
A #[with(LittleEndian)] attribute could automatically deserialize to the native endianness, removing the need for getters on the non-archived type
Disadvantages
Accessing the non-native types requires a getter, even in the fully deserialized form. In extreme cases, this could even affect performance.
Step 2. Provide a DynamicEndian (i32_de) type, used for types that can have their endianness configured at serialisation-time. The caller of Serialize::serialize will provide a Serializer which defines the endianness to use.
Extensions
An ArchiveWith implementation could be written to enable users to write #[with(LittleEndianSerializer)], causing the field to be switched to a little endian Serializer
Disadvantages
We cannot know which endianness a _de type was serialised with, so their archived type must be UnknownEndian<T>.
Step 3. Provide a GlobalEndian (i32_ge) type, which allows the binary crate at the top of the dependency graph to configure which endianness is used for serialisation at zero cost. This still enables zcd, as the incoming data can be assumed to be generated by the current program and therefore matches the global endianness.
The endianness of GlobalEndian is controlled by features on the rkyv crate.
Disadvantages
This must never ever be used by anything but a binary crate author. It will cause conflicts between libraries.
It is also dangerous to use for communication purposes, as it could invite strange bugs between multiple applications using the same library.

Moving this out of 0.8. We can support more flexible endianness through a Basis trait. That's post-0.8 work right now.


#22: Allow uploads for Blob.

Fixes #22.
@jamgold can you please check if this satisfies your use-case?

when I try to submit the result of canvas.toBlob() it gives me
Exception while invoking method 'slingshot/uploadRequest' Error: Match error: Missing key 'name'

Sorry about that. Try now. (was assigning a name manually in my tests).

Exception while invoking method 'slingshot/uploadRequest' TypeError: Cannot call method 'split' of undefined

Yes, that was it. My key method used the filename. I changed it to
    key: function (file) {
      var ext = file.type.split(/\//).pop();
      var dir = 'slingshot/';
      var fn = Meteor.uuid()+ "." + ext;
      return dir + fn ;
    }

and it works.
This is awesome

Great. Thank you for checking it out.


Error linking to zenodo

I am trying to link ScienceDataFlow (SDF) to Zenodo using the command:
sdf link ./ zenodo <token< --name "project-name"
However, I am encountering the following error:
Error: error decoding response body: missing field `title` at line 1 column 277

Caused by:
    missing field `title` at line 1 column 277

I have generated and used a  personal access token for authentication.
I have already completed a previous initialization (sdf init).
I'm using Ubuntu 20.04

Hi,
I'm unable to reprodue your error on scidataflo 0.8.11.
Which version of scidataflow are you using ? Could you share data_manifest.yml ? Thanks

Hi Tomas-Pe,
I am also unable to replicate it — I will close this issue but please feel free to reopen it if the issue persists.


Error while deploying out of the box Azure landing zone accelerator Template (treyresearch)

Hi All,
I am trying to deploy out of the box Template for Enterprise Scale (Azure landing zone accelerator) and after providing values for all the parameters I am getting Validation error:
"Deployment template validation failed: 'The deployment metadata 'SUBSCRIPTION' is not valid.'. (Code: InvalidTemplate)"
Raw Error:  {
"code": "InvalidTemplate",
"message": "Deployment template validation failed: 'The deployment metadata 'SUBSCRIPTION' is not valid.'."
}
https://github.com/Azure/Enterprise-Scale/blob/main/docs/reference/treyresearch/README.md
I am not sure how I can fix the Subscription issue (as I have not modified anything in the template and simply used the Deploy to Azure option from Github.
The Admin account I am using has the permissions to create Subscriptions (like Pay As You go, etc.) not sure how I can resolve above error.
If I have one subscription with root level permission and another subscription with (Service Administrator) permission is there a way to POC this Enterprise Scale Landing zone accelerator? Any guidance on this?
Any help in resolving this?

Hey @DeepMalh44,
Thanks for raising this. This error normally appears due to you using the same subscription in more than one place. e.g. for platform and then also same subscription as a landing zone.
A subscription can only be used in one place in the accelerator. Please ensure this is done and let us know how you get on.
If further assistance is required please provide the correlation ID, if possible, so we can help track it down further 👍
Thanks
Jack

Thank you @jtracey93 I appreciate your quick response, you are correct I was making that mistake of using "Dedicated" subscription option and going with the same subscription (my bad).
I am going to request for couple of more subscriptions and give it a try and report back the outcome but I am hoping to get Green on execution post fixing this issue.

Post created 4 subscriptions and re-running the deploy with DEDICATED option and making sure unique subscription is selected respectively it worked like charm! Thank you @jtracey93 .


Visual Feedback and Confirmation

@jaibhedia
**Providing clear visual feedback and confirmation to users and it ensures that users know their actions have been recognized and understand the outcomes of their interactions with the website.
Describe the solution you'd like

Display loading spinners or progress indicators during data fetching or processing actions to inform users that their request is being
handled.
Provide clear and concise success and error messages after form submissions or actions, with guidance on how to resolve issues.
Allow users to undo certain actions, such as deleting an item, to prevent accidental data loss.

Additional context
By implementing these visual feedback and confirmation strategies, the VoteChain website can create a more engaging and user-friendly experience, ensuring users feel confident and informed throughout their interactions.
Please assign me this issue and add gssoc label on it , i will work on it ...

@jaibhedia please assign me this issue...


Start markdown

Welcome to introduction to markdown.
First lesson of markdown.

Finished doing the first step of markdown


Family365 is a fake business

Discussed in https://github.com/familytree365/genealogy/discussions/1905

Originally posted by jacob-liu-g March  8, 2022
@everyone you got scammed, please check @curtisdelicata 's Linkedin profile.  He never pay for developers.
He runs fake business called FamilyTree365. He lies developers to contribute the project for a week and pretend to pay after a week but he disappears after receiving PR.
I should alert other honest developers and customers that you should never support Curtis Delicata since he is a fraud.
I can share you more evidence if anybody interested.
https://www.linkedin.com/feed/update/urn:li:activity:6906662303572606976/

What makes you think he's a scammer? @jacob-liu-g ? He's a developer like any other.

More evidence would be great, got a PR you could show us @jacob-liu-g ?


Gateway docker refactorization

Summary
Fix #311
Details and comments

Moved gateway's Dockerfile to the /infrastructure folder
Migrated github actions to use the new folder
Sync gateway's Dockerfile with repository
Added repository to the docker-compose
Completed the configuration for docker-compose & docker-compose-dev

🤔 I will take a look as soon as I can


Stress Test MGC.exe

The generator executable, and it's parts, should be stressed tested to validate things work correctly in a high volume environment. The generator should be able to run against multiple concurrent processes and not run into any issues. To achieve this, we need to be able to "reset" the generator on each run to ensure subsequent runs of the generator don't just cont. to read plugins, and its' dependencies, from cache.

First noted in https://github.com/jorgerangel-msft/Microsoft.Generator.CSharp/pull/4#discussion_r1516825385. We should also consider testing that the versions of packages installed using the nuget catalog are the same as installing the packages directly using the nuget client.


Persistence and more; #1000

This addresses #1000 and many other small bug fixes.
Signed-off-by: Simon Schubert<EMAIL_ADDRESS>

re-running TravisCI build

Is there a way to obtain the behave logs?  I'd guess this is a timing issue again.

@corecode could you rebase this? Thanks

@jyellick or @tuand27613 could you guys help review this PR.  My naive observation is that I don't see a behave test here to cover issue #1000, and I can't tell whether the unit tests cover the said small bug fixes.

@binhn This entire PR should be included in #1325 and has those conflicts resolved.  I believe this PR can be closed, pending confirmation from @corecode

All of this has been folded into #1325

The behave test for issue680 also tests for persistence.


Improve reporting for hook errors

We weren't really reporting hook errors, but they're actually very common so it's important we do.
The second commit is an optional refactor that I'd like to get your thoughts on. The motivation was to reduce the number of parameters on the TestBlock constructor, making it easier to write block transforms.

:ship: it


💡 [FEATURE] - Addition of favicon

Idea Contribution

[X] I have read all the feature request issues.
[X] I'm interested in working on this issue
[X] I'm part of GSSOC organization

Explain feature request
addition of a favicon would enhance the look of the website
Explain your solution
No response
Any alternative approaches/features
No response
Additional Context
No response

This issue was resolved


add cloudbees-developers to second tier

Description
This PR adds the team cloudbees-developers to another possible set of cloudbees-owned plugins.
Keeping in draft right now as this is a first pass.

Submitter checklist for adding or changing permissions

Always

[ ] Add link to plugin/component Git repository in description above

For a newly hosted plugin only

[ ] Add link to resolved HOSTING issue in description above

For a new permissions file only

[ ] Make sure the file is created in permissions/ directory
[ ] artifactId (pom.xml) is used for name (permissions YAML file).
[ ] groupId / artifactId (pom.xml) are correctly represented in path (permissions YAML file)
[ ] Check that the file is named plugin-${artifactId}.yml for plugins

When adding new uploaders (this includes newly created permissions files)

[ ] Make sure to @mention an existing maintainer to confirm the permissions request, if applicable
[ ] Use the Jenkins community (LDAP) account name in the YAML file, not the GitHub account name
[ ] Make sure to @mention the users being added so their GitHub account names are known if they require GitHub merge access (see below).
[ ] All newly added users have logged in to Artifactory at least once

Reviewer checklist (not for requesters!)

[ ] Check this if newly added person also needs to be given merge permission to the GitHub repo (please @ the people/person with their GitHub username in this issue as well). If needed, it can be done using an IRC Bot command
[ ] Check that the $pluginId Developers team has Admin permissions while granting the access.
[ ] In the case of plugin adoption, ensure that the Jenkins Jira default assignee is either removed or changed to the new maintainer.
[ ] If security contacts are changed (this includes add/remove), ping the security officer (currently @Wadeck) in this pull request. If an email contact is changed, wait for approval from the security officer.

There are IRC Bot commands for it

compare #2265

obsolete PR, closing


HDDS-6964. [Snapshot] Split out shared "Path based access" code from OM.

What changes were proposed in this pull request?
This PR refactors some of the OzoneManager code to make it available for use by the upcoming Om Snapshotting feature.
OmMReader class
Reading the metadata for OM snapshots is quite similiar to reading the metadata for the active fs.  The main difference is a different RocksDb instance is used by the OmMetadataManager, KeyManager, etc.  The code that reads that metadata is currently in the OzoneManager class.
This PR refactors that code and moves it into a new class called the OmMReader, (Ozone Metadata Reader.)  To replace the code removed from the ozoneManager, an OmMReader will be constructed using the RocksDb for the active fs.  For snapshots, the OmMReader will be constructed with the rocksDb instance corresponding to that snapshot.
Metrics
The code in OmMReader makes extensive use of the OMMetrics class. Snapshotting will need its own version so I've created a new interface that correspond to it: OmMReaderMetrics. This interface is used in the OmMReader code so that the OzoneManager and Snapshotting can each have their own. (They each pass their own version into the OmMReader.)
Removal of obsolete IOzoneAcl code
In the process of doing the refactoring, I discovered that much of the IOzoneAcl interface is no longer in use.  So I removed those methods, (and fixed the few tests that still invoked them.)
These are the methods removed
KeyManagerImpl changes
In addition to the IOzoneAcl deletion mentioned above, I also had to change the KeyManagerImpl to not read the metadataManager through the ozoneManager.
In a few places, it was unnecessarily reading metadata like so: "ozoneManager.getMetadataManager()" instead of using the metadataManager field initialized by its constructor.
That would prevent the snapshot rocksDb instance from being read so I switched those to use the metadataManager field.
Initialization of the OmMReader field in OzoneManager
After reviewing the code, I feel the correct place to init the OmMReader is in the instantiateServices() method here.
The KeyManager and others are set there, and the OmMReader should be reset anytime that method is called and those are reset.
metrics field
However, the omMReader needs the omMetrics which is initialized after instantiateServices() is called in the ozone manager constructor.
To work around that, I moved the OMMetrics.create() to before instantiateServices() is called in the constructor:
+    metrics = OMMetrics.create();
     instantiateServices(false);

omRpcAddress field
The omRpcAddress has the same problem but I was hesitant to move that code, so omMReader doesn't store it as a field.  It just accesses it through the om, like so:  "ozoneManager.getOmRpcServerAddr()"
volatile fields
The new omMReader field in the OzoneManager is not final, and will be changed each time instantiateServices() is called, (as it should.)
But the OzoneManager is multithreaded code, and, IMHO, such fields should be defined "volatile".  But the keyManager, volumeManager fields etc are also changed by instantiateServices(), and they are not defined to be "volatile".  That seems like a bug to me, but perhaps it was intentially done for performance reasons.  In any case, I have not made the omMReader field volatile for now.
Let me know if you think that is correct.
Reviewing the changes
There are lot of changes in this PR but most are very straightforward.  The only part that is hard to review is the code that is moved from the OzoneManager to the OmMReader and the only reason that is hard is because the diff tool isn't smart enough to find the changes in the new file.
So I created a python script that uses string matching to generate a version of OmMReader that has the original unchanged OzoneManager methods pasted in.  You can see the diffs here
As you'll see, these are the main things changed, in the code moved to the OmMReader:

A few private methods were made package-private.
The "LOG" and "AUDIT" field names were changed to "log" and "audit".  (Since they are no longer static final, checkstyle won't let them be all caps.)
Changed the omRpcAddress access to "ozoneManager.getOmRpcServerAddr()" as mentioned above.
Changed the call to resolveBucketLink() to ozoneManager.resolveBucketLink().

What is the link to the Apache JIRA
https://issues.apache.org/jira/browse/HDDS-6964
How was this patch tested?
All tests continue to work.
In my own repo, I've added some code that excercises the OmMReader to read snapshots.  That will be part of the next PR.

A flaky test, unrelated to snapshotting, was preventing the tests from passing since I did the rebase.  I debugged it and added the fix to this pr.  I describe the problem here
This is the fix

@GeorgeJahad let us discuss the refactoring changes in the weekly call tomorrow.


[online leaderboard] av2 scene flow test data have different array, cannot eval online

Information:

Error message online:

boolean index did not match indexed array along dimension 0; dimension is 67074 but corresponding boolean dimension is 67073'

API version I used: https://github.com/argoverse/av2-api/commit/64dd83c1429f1d5aaea2e0333d88fa2630e5328c

Dataset version I downloaded through at 01 Jun 2023:

s5cmd --no-sign-request cp "s3://argoverse/datasets/av2/sensor/val/*" sensor/val
s5cmd --no-sign-request cp "s3://argoverse/datasets/av2/sensor/test/*" sensor/test
# also the mask
s5cmd --no-sign-request cp "s3://argoverse/tasks/3d_scene_flow/zips/*" .

Script I run, note There is no error when I run the local evaluation scripts.

# generate mask
python3 av2-api/src/av2/evaluation/scene_flow/make_mask_files.py test-mask.zip <data_set_path>  --split test
# run the example submission
python av2-api/src/av2/evaluation/scene_flow/example_submission.py checkpoints/results/test/example <data_set_path> test-mask.zip
# upload to the online leaderboard

I didn't change the code av2-api, so maybe there are some dataset or mask file versions different now and the online leaderboard didn't update?

Ha I see the problem is the downloaded mask and run av2-api script is different, I rerun with downloaded mask file and success.
av2-api/src/av2/evaluation/scene_flow/make_mask_files.py


♿(frontend) remove redundant form role in the LTI app

It's considered as a bad A11y practice to add redundant semantic. A <form> element has already a form role, specifying it again is redundant. It might make screen readers behave buggy.
I would suggest adding the eslint-plugin-jsx-a11y plugin to the ESLint custom configuration. It's a dependency of react-scripts, used by the standalone app but not the LTI app.

Note: the lint-git job fails because I am not in the list of contributors. Do I need to fix it?

Note: the lint-git job fails because I am not in the list of contributors. Do I need to fix it?

Yes please


feat: add Feel editor

This PR adds new Fields that support FEEL in InputFields and TextAreas. See the usage in the Properties Panel in this PR.

test it out the integration with npx @bpmn-io/sr bpmn-io/bpmn-js-properties-panel#feel-editor -l bpmn-io/properties-panel#feel-editor

Broke after rebase on main, I will rework it to work with the changes made in https://github.com/bpmn-io/properties-panel/pull/160


Secret Manager Examples

I don't know whether to call these examples or built-ins but it would be awesome to have secret managers that were defined. We could distribute them as separate PS modules so they would be plug and play.
Some good ones

PSSecretStore
Windows Credential Manager
Azure KeyVault

I'm sure there are more but it would be great if people didn't have to configure this themselves.

We are now using the secret management module rather than our own implementation since it does everything we want. We'll wait on MSFT to release some examples.


App does not build

Short description of the issue

app does not build
Issue type
build issue
What is the expected behaviour?
app can be compiled
What is actually happening?
see screenshot
Steps to reproduce
build in xcode Version 10.2 (10E125)
Additional information
Version you are using: latest/develop
tvOS version: latest
Xcode version: Version 10.2 (10E125)

Unfortunately the NPO had killed the video server, only DRM FairPlay is possible, of which I don't have the implementation. So unfortunately it looks like the time has come to sunlight the app, unless someone has more details on the FairPlay setup.

Thnx buddy for your hard work on the app; I hope the sun will shine again (we &^&& paid taxes for the content!) any time soon.....

See PlayerViewController+FairPlay.swift  for some tests I did. Unfortunately I'm not sure how to authenticate against the license server, most likely you need some private secret for that.


Disable StoreAPI if agent enabled

Changes
Made changes in storeset.go by adding a extra variable which checks whether the agent is enabled or not.
#6606

hello @yeya24 I am trying to implement this can you please suggest your feedback regarding this error and the changes that i have done.

@Vanshikav123 Please make your changes can be compiled first.


Generator crash on class that doesn't implement an interface correctly

The code below is incorrect (Class1 doesn't implement Interface1 correctly since f takes a float instead of a MyEnum).
However, the generator will crash, instead of emitting diagnostics.
namespace CppComponent
{
    public enum MyEnum
    {
        Value1 = 42,
        Value2 = 99
    }

    public interface Interface1
    {
        void f(int x, MyEnum y);
    }

    sealed public class Class1 : Interface1
    {
        public void f(int x, float y);
    }
}

We might need a diagnostic to check all the methods to ensure it correctly implements the interface, but I would also expect C# built-in diagnostics to catch it.  We should look at why it isn't.


Fix Client SslStream CRL verification

Logic appears to be inverted. When IgnoreCertificateRevocationErrors, SslStream was requested to checkCertificateRevocation which were then ignored in the callout validator.

Thank you for your contribution. Good work 👍 I will release 3.0.7 soon which will include this fix.


unplugging my  DSU on my 2018 Toyota Prius

Describe the bug
Openpilot has always worked with my 2018 Toyota Prius On comma 2 and comma 3.  But one day my comma three did a camera malfunction and I had to factory reset the comma.  After I did that My comma did not want to work cuz the DSU was unplugged so I turn my car off and plugged in the DSU and I get assistance but it's not open pilot. Now every time I unplug the DSU, cruise control does not work aka openpilot.  I only have adaptive cruise control with the DSU plugged in but it's not openpilot.  I also get the yellow/orange pre-collision system  light flashing when the DSU is unplugged.
What hardware does this issue affect?
comma three, comma two
Which car does this affect?
2018
Provide a route where the issue occurs
?
openpilot version
0.8.10
Additional info
Please 🙏 help, CommaAi team told me someone Eric from here can help.

Check out our Discord or GitHub Discussions for getting started.

I checked out the page, how come you close this on me instantly

I checked out the page still need help


Still cannot connect to any node

Could not connect Request failed with status code 417 (path="connection")

Fixed with today's update, thanks!


Volume up/down as trigger from remote

Hi Merdok!
I've just  update to the new version 2.x.x of your plugin. Great changes!
Is it me, or is the volume up/down trigger not working any longer?
https://github.com/merdok/homebridge-webos-tv/pull/147
When I press up/down on the remote, I can see the following message in homebridge debug:
[TV] Audio status changed. Current volume: 7, Muted: No
Still my automations don't get triggered.
I check to code and noticed the prepareTvSpeakerService() and the following lines:
this.logDebug('Volume change over the remote control (VolumeSelector), pressed: %s', state === Characteristic.VolumeSelector.DECREMENT ? 'Down' : 'Up');
This debug message is not show. Could this be related to the missing up/down tigger or am I doing something wrong?
Thanks!
 This somehow got lost during the update. Will have a look at it and try to add it back in the next update.

Thx!

Should be fixed in version 2.1.2

That was fast, thanks! Work great!


backgroundColor

flutter_inner_drawer-1.0.0+1/lib/inner_drawer.dart:585:38: Error: The getter 'backgroundColor' isn't defined for the class 'ThemeData'.

Got this error when run project


Chip: Fix OnClick/OnClose causing NullReferenceException (#2866)

Description

Fixes #2866
How Has This Been Tested?

implemented unit test for OnClick and OnClose
modified ReadOnly unit test in order to test OnClose event

Types of changes

[x] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] Improvement/refactoring (non-breaking change that doesn't add any features but makes things better)

Checklist:

[x] The PR title is no longer than 64 characters.
[x] The PR is submitted to the correct branch (dev).
[x] My code follows the code style of this project.
[ ] I've added relevant changes to the documentation (applies to new features and breaking changes in library)

@JonBunator Thank you for the fix. @henon I hope it will be released soon. After the upgrade to the last version, there is no more the display of Chips.

Thanks!


Update simplefm_example.php

Coverage remained the same at 100.0% when pulling 73f9a3519f5bbd98a7ea974c4e3c73b6d845b8b6 on jeremiahsmall:feature/documentation into 50f2f3b67956b223034335e5c56f7cae2eed26b9 on soliantconsulting:develop.

Coverage remained the same at 100.0% when pulling 58c70e751f816e43c195c402b4c16b0885b0f5d0 on jeremiahsmall:feature/documentation into 50f2f3b67956b223034335e5c56f7cae2eed26b9 on soliantconsulting:develop.

Coverage remained the same at 100.0% when pulling 9c050d54ffe14e6b18ebed864a6d3648cd401b3c on jeremiahsmall:feature/documentation into 50f2f3b67956b223034335e5c56f7cae2eed26b9 on soliantconsulting:develop.

Coverage remained the same at 100.0% when pulling e952d5f5f7d7d336400239fc355ca477f9a297b6 on jeremiahsmall:feature/documentation into 50f2f3b67956b223034335e5c56f7cae2eed26b9 on soliantconsulting:develop.

Coverage remained the same at 100.0% when pulling f1029bcc0bbae01f0c2c2aedb29381897c8a743d on jeremiahsmall:feature/documentation into 50f2f3b67956b223034335e5c56f7cae2eed26b9 on soliantconsulting:develop.

Coverage remained the same at 100.0% when pulling 5e34e919e68add695c1dda4162627484c0a6639b on jeremiahsmall:feature/documentation into 50f2f3b67956b223034335e5c56f7cae2eed26b9 on soliantconsulting:develop.


Improve setup process for new contributors:

Currently we give contributors the credentials (not ideal because we want to keep these private)
Solution 1: Add instructions for how contributors can create their own Auth0 credentials (not ideal because it may too daunting/complex). Or maybe this is manageable?  Let's investigate.
Solution 2: Create a Dev Log-in setup (simpler than Auth0)

The current solutions for this have been addressed by #153 or with this guide for local (no GitPod) development.


chore(deps): update

Objectif(s)

Faire taire dependabot

:tada: This PR is included in version 1.16.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


Figure out difference between our SWAVES Client and the VSO results

See https://github.com/sunpy/radiospectra/pull/35#issuecomment-797389626

The radiospectra client will be removed as the URL is now dead.


Sample Kotlin Grammar does not load properly and is unusable.

How to reproduce:

Go to Antlr Lab Site
Click on the sample dropdown, and select either entry for Kotlin. (I'm assuming one entry is for kotlin-formal, but neither work)
Click on the tab labeled Parser.

You'll see that the Lexer is incorrectly placed in the parser, instead of the kotlin parser. The sample does not function in this state.
Even with the kotlin parser in the correct place, a solution is needed for importing UnicodeClasses.g4, which the kotlin lexer relies on.
Otherwise, the sample will throw many implicit token errors. I usually have to manually copy the contents of unicodeClasses.g4 to the end of the lexer to use the kotlin grammar with antlr lab.

Someone manually changed the grammars.json file. https://github.com/antlr/grammars-v4/blob/1e08bcbcc56b8ff2cfad7508815544e141d188e9/grammars.json#L2070. It's wrong and it should have been generated by script, not hand edited. https://github.com/antlr/grammars-v4/blob/master/_scripts/mkindex.py

Upon further inspection, this is actually a bug with mkindex.py itself.
I tried running mkindex.py again and got this output, which is still wrong:
grammar.json

The problem lies with lines 113 and 114:
lexer = grammars[0] if 'Lexer' in grammars[0] else grammars[1]
parser = grammars[0] if 'Parser' in grammars[0] else grammars[1]

The Kotlin pom file defines UnicodeClasses.g4 first, then the lexer and parser are listed. This edge case means that both lexer and parser are set to grammars[1].
<includes>
   <include>UnicodeClasses.g4</include>
   <include>KotlinLexer.g4</include>
   <include>KotlinParser.g4</include>
</includes>

I also noticed that kotlin-formal/pom.xml doesn't include UnicodeClasses.g4 at all, even though KotlinLexer.g4 still imports from it.

Upon further inspection, this is actually a bug with mkindex.py itself. I tried running mkindex.py again and got this output, which is still wrong: grammar.json

Thanks for checking this. The error is in the pom.xml itself--it has UnicodeClasses.g4 stated as a "top-level g4". Yes, it is a "lexer grammar", but it is not a "top-level g4". A "top-level g4" is a g4 that we run the tool on. UnicodeClasses.g4 is an imported file, so the tool should not be run on this file.
(And honestly, I don't understand why we are using the pom.xml for this information, when this can all be derived solely by trparse/trquery.)
I'll need to fix the pom.xml and reindex.

While the parser and lexer grammar tabs fill up with the correct .g4 data, lab.antlr.org does not work with either of the kotlin grammars. It can't because the .g4's contain "import" statements, and lab.antlr.org does not implement UI for imported grammars. The mk-index script does not weed out these grammars, but it should. https://github.com/antlr/grammars-v4/issues/4201


Fixed granting access and improved Admin page functionality

When requests are approved by approvers, only then does a user's utorid appear on the Admin page with the button "Grant Access". Admin page now shows list of users who have been granted access. Fixed event creation in the backend.

lgtm, closes #28


Suggestion: get_data() function is deprecated

The get_data() function has been deprecated since nibabel version 3.0 and is no longer recommended. In its place is the get_fdata() function, which provides a more predictable return type.
So we need to change get_data() to get_fdata() so that the code runs successfully

Thank you so much for pointing this out! We have updated the get_data() to get_fdata().


Gradients on the cell not available for most calculations

Is your feature request related to a problem? Please describe.
The gradients of the translation vectors are not available in the AUX file except for 1SCF calculations, which means it is impossible to calculate the stress.
Describe the solution you'd like
Add the gradients of the translation vectors to the AUX file win a consistent fashion. Currently they are appended to the atomic gradients for 1SCF calculations -- 9 extra values for a 3-D periodic system. They could be appended in other calculations -- optimization, FORCE, etc. -- or it might be cleaner to add them as a separate field, as the translation vectors are currently:
 INITIAL_TRANS_VECTS:ANGSTROMS[9]=
   5.4309   0.0000   0.0000
   0.0000   5.4309   0.0000
   0.0000   0.0000   5.4309

They are not appended to the coordinates, so it would be more consistent to not append the gradients (and also might break fewer codes!)
It would also be easy and valuable to calculate the complete stress tensor and make it available, probably in Voigt notation. The documentation provides the formula in the section on the pressure on the faces of cells:
The scalar, f1, of the component of the gradient vector, g1, in the direction of the translation vector, Tv1, is given by:

 f1 = (g1(x)·Tv1(x) + g1(y)·Tv1(y)  + g1(z)·Tv1(z)).

Using the volume of the unit cell, V = |Tv1·(Tv2⊗Tv3)|  or:

V = |Tv3(x)*(Tv1(y)·Tv2(z) - Tv1(z)·Tv2(y)) + Tv3(y)*(Tv1(z)·Tv2(x) - Tv1(x)·Tv2(z)) + Tv3(z)*(Tv1(x)·Tv2(y) - Tv1(y)·Tv2(x))|,

and conversion factors to go from kcals and moles to ergs and unit cells, the pressure, P, in Pascals, can be calculated using:

P = -4184·1030/(6.022·1023)·f·V-1

For a 3-D system there are 3 translation vectors and their corresponding gradients. If we label them 1, 2, 3 or x, y, z then the stress tensor following the equation for P (which is really stress) is:
S11 S12 S13
S21 S22 S23
S31 S32 S33

The Voigt notation is a 6-vector: Sxx Syy Szz Syz Sxz Sxy (note the unusual order!). The terms are:
Sxx = S11
Syy = S22
Szz = S33
Syz = (S23 + S32) / 2
Sxz = (S13 + S32) / 2
Sxy = (S12 + S21) / 2

Which accounts for the small symmetry breaking in MOPAC.
These would be useful both in the output and in the AUX file.

Sorry about the delay in addressing this issue, which on the surface was a very straightforward request. I started working on it multiple times this year, but ended up repeatedly getting confused and stopping. After finally committing to work through the confusion, I think the major points of this request are now resolved. There are some lingering issues, but they will require a more thoughtful approach when I focus on interface revisions in upcoming versions.
About the stress tensor, it is now implemented and tested against a finite-difference reference. There were a lot of minor confusions and problems along the way. First, the sign of the pressure is internally flipped in MOPAC. Second, there isn't universal agreement on the sign of the stress tensor itself in electronic structure codes, although I'm using the more standard engineering convention here (i.e. the diagonals of the stress tensor are the negative of pressure). Third, your assertion that Jimmy's note on "Pressure on the faces of a unit cell" was directly related to stress tensor calculations was not correct, and I needed to more broadly refresh my knowledge of the topic. Jimmy is calculating a pressure on a crystal face in a very literal way, which is in the direction of the translation vectors, whereas the stress tensor indices are the Cartesian coordinates (i.e. they are distinct derivatives if the translation vectors are not aligned with Cartesian coordinates). Also, proper calculations of stress tensors are calculating a uniform deformation of space, so the gradients of atomic coordinates also contribute to the stress tensor (see DOI:10.1016/j.cpc.2015.01.003 for a thorough discussion).
Finally, the finite-pressure gradients in MOPAC were never implemented correctly for non-orthorhombic crystals, and I ended up having to debug and re-implement them. This bug might have something to do with "the small symmetry breaking in MOPAC" you are referring to.
About printing gradients and stresses more consistently in the AUX file, I've added them in whenever updated coordinates are printed (i.e. geometry optimization and reaction coordinate methods). While I've added in more print statements, they will only trigger if the gradients are calculated. I am not printing gradient information with FORCE, because it requires the gradients to be very close to zero to function correctly, so gradient information should be useless when that feature is used as intended.
About separating atomic-coordinate and translation-vector derivatives, there are some subtle problems with changing the existing approach. MOPAC has 3 overlapping systems of bookkeeping - the "atoms" (which include things like sparkles and translation vectors), the "real atoms" (which are specifically atoms with atomic orbitals attached to them), and the optimized degrees of freedom (which include the x, y, and z coordinates of each atom and translation vector). If a particular coordinate of a particular atom is not set to be optimized, then it won't be on the list of optimized degrees of freedom and its derivative won't be calculated. MOPAC only prints the gradient components that it calculates. I can't guarantee that a list of gradients on all of the atoms or translation vectors doesn't have gaps because some components weren't calculated. I could retain the current approach and also print the set of atomic and translation vector gradients separately when they are all available, but that would be redundant and conditional. This is a case where MOPAC's flexibility complicates its interface, no matter which approach you take. A simpler interface would involve restricting some of that flexibility (e.g. forcing all coordinates to be optimized).

Weeeelllll, I didn't realize it would be that complicated! Sorry! But thanks for the tremendous effort. This will be very useful and important for periodic systems. As for the limitations you mention at the end, I would think that in essentially all cases, no parameters will be fixed, with the possible exception of lattice parameters that are zero by symmetry, which should be simple to handle externally. For example, in an orthorhombic cell you might choose to fix the angles at 90º so that noise doesn't slip into them, optimizing only the three cell lengths.


DOCS change logs etc

Codecov Report

Merging #42 (5d7cff5) into main (8ef3fa9) will decrease coverage by 33.41%.
The diff coverage is n/a.

:exclamation: Current head 5d7cff5 differs from pull request most recent head bcbe457. Consider uploading reports for the commit bcbe457 to get more accurate results

Additional details and impacted files

@@             Coverage Diff             @@
##             main      #42       +/-   ##
===========================================
- Coverage   91.31%   57.90%   -33.41%
===========================================
  Files           9        9
  Lines         449      449
===========================================
- Hits          410      260      -150
- Misses         39      189      +150

see 7 files with indirect coverage changes


Kedro-airflow setup.py requires test_requirements.txt, but it's not packaged in pypi

Description
Kedro-airflow setup.py requires test_requirements.txt, but it's not packaged in pypi
Context
I am trying to package kedro-airflow and kedro-viz for conda-forge so that I can conda install them.  Conda-forge runs setup.py as part of the build process.  Kedro-airflow directly references test_requirements.txt in setup.py, but test_requirements.txt is not packaged in the build for pypi, so running setup.py fails.
Steps to Reproduce

Download kedro-airflow via pypi.
unzip it and run python setup.py.

Expected Result
Setup.py succeeds.
Actual Result
Setup.py fails because test_requirements.txt is missing.
 FileNotFoundError: [Errno 2] No such file or directory: 'test_requirements.txt'

@cshaley Thanks for the report! My opinion is that test_requires and the associated python setup.py test are both pretty useless/deprecated, and we don't use that in the CI anyway (thankfully), so the easiest solution is to just kill them. :)
Deprecation references:

https://github.com/pypa/setuptools/issues/1684
https://github.com/pytest-dev/pytest/issues/5534

Note: same thing is true of Kedro-viz. I'm also looking to package it on conda forge but this issue got in the way.   @deepyaman Shall I open an issue there as well?

Resolved by #55


Fix inline comments in EnvironmentControllerTests

This PR fixes inline comments in EnvironmentControllerTests as they look opposite.

Current coverage is 68.81% (diff: 100%)

Merging #520 into master will not change coverage

@@             master       #520   diff @@
==========================================
  Files            60         60
  Lines          2046       2046
  Methods           0          0
  Messages          0          0
  Branches        341        341
==========================================
  Hits           1408       1408
  Misses          499        499
  Partials        139        139

Powered by Codecov. Last update f596d13...9a3903d


feat: [RFC] Rewrite for monaco editor, react context and the beginnings of the redesign

moved to a non forked branch, #1523

@ncthbrt please open a PR, others are using it as a base for their RFCs tomorrow!

There is a PR against this PR - it introduces monaco!
https://github.com/acao/graphiql/pull/17

ok, about to merge in monaco support here soon, which also resolves several issues we had with this fantastic PR!

next up, https://github.com/acao/graphiql/pull/20/files!

next steps:

merge in @harshithpabbati's PR above
yank out changes to most everywhere except packages/graphiql, thus maybe a few smaller, pre-cursory PRs. for example, improvements to monaco-graphql anbd the LSP to suit this PR can be broken out into it's own PR. this PR should be packages/graphiql and whatever tooling/etc changes required

new directions:

if someone wants to spike a PR adding react-i18n-next to this, that would be rad. there's a lingering closed PR that did this with russian translations. the author had also rewrote a significant portion of the codebase in the PR and he didn't make a simplified version.
A PR to pull doc explorer into a new, seperate npm package named @graphiql-plugins/doc-explorer-classic and import as a prop, or to replace it with a green plugin component for the new doc explorer :D. repeat with query explorer!
spike off this PR to add a PluginManagerContext for rendering plugin components that invoke API behaviors
adding a bunch of cool components and improvements to the new src/components/common

next steps:

merge in @harshithpabbati's PR above
yank out changes to most everywhere except packages/graphiql, thus maybe a few smaller, pre-cursory PRs. for example, improvements to monaco-graphql anbd the LSP to suit this PR can be broken out into it's own PR. this PR should be packages/graphiql and whatever tooling/etc changes required

new directions:

if someone wants to spike a PR adding react-i18n-next to this, that would be rad. there's a lingering closed PR that did this with russian translations. the author had also rewrote a significant portion of the codebase in the PR and he didn't make a simplified version.
A PR to pull doc explorer into a new, seperate npm package named @graphiql-plugins/doc-explorer-classic and import as a prop, or to replace it with a green plugin component for the new doc explorer :D. repeat with query explorer!
spike off this PR to add a PluginManagerContext for rendering plugin components that invoke API behaviors
adding a bunch of cool components and improvements to the new src/components/common

@acao shall I start with pulling the doc-explorer component to @graphiql-plugins/doc-explorer-classic ?

@harshithpabbati I've been working on that and the props interface for tabs today, taking care of a sick family member as well so I haven't finished. Would you be interested in taking a pass at react-i18n-next? just to add tooling and to handle the english locale strings for one or a few components to get started, or you could go all out on that if you want!

@harshithpabbati I've been working on that and the props interface for tabs today, taking care of a sick family member as well so I haven't finished. Would you be interested in taking a pass at adding react-i18n-next? just to add tooling and to handle the english locale strings for one or a few components to get started, or you could go all out on that if you want!

Yeah, sure I will look into it.

@harshithpabbati I've been working on that and the props interface for tabs today, taking care of a sick family member as well so I haven't finished. Would you be interested in taking a pass at adding react-i18n-next? just to add tooling and to handle the english locale strings for one or a few components to get started, or you could go all out on that if you want!

I wish he/she get well soon

thank you! she will be ok, she doesn’t have covid thankfully, still taking care of her though
so, the effort of pluginifying doc explorer is taking a bit longer but we’re almost there! i fixed the editor display locally.

@harshithpabbati merged! now you'll want to update your i18n PR

@acao yeah, I am on it!

hmm... I've think I've gone one bridge too far bringing the plugin ecosystem into this PR. heads up @harshithpabbati, going to revert those commits and we can make another branch for the plugin effort to be based off of

@acao type in commit-msg it should be Co-authored-by: harshithpabbati<EMAIL_ADDRESS>

moving to #1523


Propose Release 6.3.0

I followed the docs at https://github.com/containers/oci-spec-rs/blob/main/release.md.
In Particular I am interested in the artifact_type added in https://github.com/containers/oci-spec-rs/pull/145.  Thanks!

@saschagrunert I agree with releasing the new version WDYT?

closing since dco is messed up with the extra commit. I re-ran the script and it created a new branch


Port tests in explain_analyze.rs to sqllogictest

Is your feature request related to a problem or challenge?
Part of https://github.com/apache/arrow-datafusion/issues/6195. We are trying to

keep the DataFusion code base clean and easy to contribute to and modify
Understand what features are covered and what are not

Part of doing so is having a single location for most test coverage so new tests can be added easily and people can follow the existing patterns easily
Describe the solution you'd like
Port the tests in https://github.com/apache/arrow-datafusion/blob/main/datafusion/core/tests/sql/explain_analyze.rs to
explain_analyze.slt in https://github.com/apache/arrow-datafusion/tree/main/datafusion/sqllogictest/test_files
Note you can create catalogs and schema via SQL now
Catalogs: https://arrow.apache.org/datafusion/user-guide/sql/ddl.html#create-database
Schema: https://arrow.apache.org/datafusion/user-guide/sql/ddl.html#create-schema
Notes:

Instructions for running sqllogitest are here: https://github.com/apache/arrow-datafusion/tree/main/datafusion/sqllogictest

Describe alternatives you've considered
No response
Additional context
I think these are good first issues as they teach the contributor about the DataFusion codebase and tests, as well as see the end user apis in practice.

I am not sure if this test is easy to port or not (it may required normalization of the output that is not possible in sqllogictests)

Maybe I can help with this.
But I am not sure if the test is easy to port, maybe i will need some help @alamb


Usability Issue Thread

Writing themes is hard, just post things that are not usable.

Not a fan of the removed color.

Not really a usability issue, it's more just annoyingly inconsistent.


Test mac on self-hosted runner

We should be able to replace the python installation once #358 is merged, which should solve the current errors.
I'll probably stick this in the dev guide at some point, but for future reference, we haven't managed to find a nice way to set up the self-hosted runner as a service (see issues e.g. https://github.com/actions/runner/issues/349, https://github.com/actions/runner/issues/1959, https://github.com/actions/runner/issues/1476), which may partly be because we are unable to set auto login, and as we wanted to avoided running things with sudo access.
The solution, which seems to be working for now, is to use the standard run.sh script in the background, and disowning the task, so we can log out:
nohup ./run.sh &!

Sleep options etc. may need revisiting, but the runner has remained online for over an hour.


Fish shell offered when not installed

Testing #119427
macOS Catalina
Shouldn't this check if fish is installed?

The solution is obviously to install the Fish shell
(jk :)

This happened because of my dodgy workaround here: https://github.com/microsoft/vscode/issues/119534
/duplicate


Fething movie data again during orientation change

When screen is rotated , it fetches the same data which is already's been fetched.We can handle it on by implementing call back savedInstance in MovieListingFragment as well as in MovieDetailFragment

Thanks. #59


[FLINK-36420][Formats/Avro] Bump avro from 1.11.3 to 1.11.4

What is the purpose of the change
Bump Avro dependency version from 1.11.3 to 1.11.4
Brief change log
Bump Avro dependency version from 1.11.3 to 1.11.4 in pom and NOTICE
Verifying this change
This change is a trivial rework / code cleanup without any test coverage.
Does this pull request potentially affect one of the following parts:

Dependencies (does it add or upgrade a dependency): yes
The public API, i.e., is any changed class annotated with @Public(Evolving): no
The serializers: no
The runtime per-record code paths (performance sensitive): no
Anything that affects deployment or recovery: JobManager (and its components), Checkpointing, Kubernetes/Yarn, ZooKeeper: no
The S3 file system connector: no

Documentation

Does this pull request introduce a new feature? no
If yes, how is the feature documented? not applicable

@flinkbot run azure


[BUG] No Keybind for Controller

🔵 Describe the bug:
Creating a keybind for a gamepad button does not work.
🔵 To reproduce: (Steps to reproduce the behavior)

Go to 'Keybindings'
Click on 'Not Bound'
Press '2' on Keyboard
Keybind assigns to '2'
Click on 'Not Bound'
Press 'RT' (my number 2 on controller)
Key does not bind like it does in WoW's Keybind options screen

🔵 The error:
No error message.  Expected outcome failing.

🔵 Screenshots:
N/A
🔵 Expected behavior:
Expect 'RT' to assign to the keybind.
🔵 GSE Version:

Version: 3.2.01-6-g184b303
Downloaded From: via Curseforge Desktop App

🔵 Additional context:
The gamepad button does bind in WoW's Keybinding settings.  GSE is not capturing the gamepad button press.  I only play WoW with a controller.  Previously, just dragging the icon from Macros into the keybound action bar slot worked.

Best I can suggest is:
/Console GamePadEnable 1
Then try.
If that doesn't work its not something I can do anything about.

I raised this upstream: https://www.wowace.com/projects/ace3/issues/662

Aww.  I hope they look into it soon.  Thanks for the help though.
Yeah, WoW’s keybind interface wouldn’t accept controller inputs if GamePadEnabled was off.  And any third party desktop apps that allow me to script the controller buttons to specific keyboard keys, doesn’t also support 'shift/ctrl' modifiers like WoW’s native support does.
And yes, I exclusively play with an Xbox controller, only ever needing the keyboard to type.  Again, thanks for the help.  Hope everyone can get everything sorted with prepatch discombobulating everything else.

So....
I found these two files.  Gamepad config for my Xbox Elite controller, which doesn't require anything like Console Port to work with the game.  Someone else's Gamepad config may be different, depending on how WoW recognizes the buttons on their controller.
And then the character specific GSE keybind file.
I took a gamble and just copied the name of the gamepad button name over the '2' I had tried previously set the keybind to.
WoW's Gamepad Config & GSE Character Keybind(s):

GSE recognizing the button name...and it does indeed work:
https://youtu.be/-Eq_ZetlsrE

Aww. I hope they look into it soon. Thanks for the help though.
Yeah, WoW’s keybind interface wouldn’t accept controller inputs if GamePadEnabled was off. And any third party desktop apps that allow me to script the controller buttons to specific keyboard keys, doesn’t also support 'shift/ctrl' modifiers like WoW’s native support does.
And yes, I exclusively play with an Xbox controller, only ever needing the keyboard to type. Again, thanks for the help. Hope everyone can get everything sorted with prepatch discombobulating everything else.

actually i've gotten it to work with JoyToKey, in conjunction with the ConsolePort addon. i'm not sure if it would work without ConsolePort, but I'm guessing it probably would, as I don't think it's really doing anything special in this scenario:
here's what I tossed in the ConsolePort discord the other day:

do what GSE says to do for your imported sequence from Wowlazymacros or whatever. in my example, i mapped Feral_single to Shift-Q within the GSE keymapping options
open JoyToKey (i had to open as administrator in Windows 10, not sure if that's required for Win11)
i created a new profile and mapped "Button 32" on the "Xbox Series X Controller" tab to Shift-Q
I clicked over to the options tab (not up on the menu bar, just the Options tab next to the xbox controller tab)
I clicked the Button Mapping thing
scrolled all the way down to "Button 32" and set "Trigger when the following button is pressed" to Button 3 (X button) and "Only trigger when the following button is also pressed" to Button 5 (LB)
loaded up WoW.  now when i hold LB and hit X.... MY GSE MACRO FIRES   😺

there was some question as to whether or not JoyToKey violates TOS, but I've been using it off and on since I started playing in 5.4 and never had an issue. that could of course change at any time, but i'm risking it for now as i've always been a controller-only player of WoW.

Technically it does but AHK and GHub also violate the ToS so it’s caveat emptor - you knowingly take the risk.

The solution for this while I figure out to do this with the gauze is also available https://github.com/TimothyLuke/GSE-Advanced-Macro-Compiler/issues/1533#issuecomment-2254522883 and has been proven to work


(from ISO/IEC 2382:2015) Bibliographic references status (withdrawn/cancelled) should be shown adhering to publication date

This document is ISO/IEC 2382:2015 at:

https://github.com/metanorma/iso-iec-2382

Basically, a document's references should reflect its bibliographic references according to its  publication date, e.g. should not render the "withdrawn/replaced" footnote beyond its own publishing date.
Since this document was already published and has replaced a number of its references, it is now showing that it "itself" has cancelled and replaced its references. Which is incorrect because at the year it was published, those documents were not cancelled/replaced (until this particular document was published!).

We need to set the "publication date" (or an override) so that the bibliographic items are "rewound" to that publication date when generating references.

Actually this ticket is identical to:

https://github.com/metanorma/metanorma-standoc/issues/773

Moving this to metanorma-standoc.


[iOS] ColumnSet.AllElements.Stretch.ToggleVisibility.json card is not rendering

Platform

iOS

Version of SDK
master
Issue
The card is not rendering at all, all the other cards render but this one

i'm closing this since it was due to parsing failure.

The problem is with the json file, the json contains an extra ',' that makes all renderers not being able to parse the json file

Have we fixed the actual card with the bad json?

Also do the renderers provide an actionable message upon this parsing failure to help troubleshoot things a bit?

Reopening to track fixing the broken sample file.


Introduce test process.

For development, introduce test process this repository.

It seems goss is good for me.

I understood how to run goss for testing server image with docker container on  https://github.com/bynnchapu/docker-ansible/pull/1.


send code of the function to the endpoint

Upload source code with the bundle. It will be stored in metadata field

but @ivan-khomyakov-sc we should have a follow up to this to move it to its own column in the db, i'll slack you when i write the readme for migrations


Add basic date display on right of package list

Not sure this is the best location but it saves on the hassle of trying to get them to neatly line up with the headers which is tricky due to the different font sizes and maybe the underline.
Currently displays an ugly iso8601 format for the date. Would be better as '3 days ago' style display but I'm not sure of the best package/lib to help with that.

I think a YYYY-MM-DD format might be a reasonable fallback if a '3 days ago' approach is harder to come by. birl doesn't seem to offer easy access to a YYYY-MM-DD format though we could just split the current output on the T. Otherwise it is a bit more work to go via the Month type and other things but obviously not hard.

All makes sense. I'll try to have a look over the next day or two. No worries if someone comes along with a bigger change that conflicts though.

Updated as you requested (I forgot about 'float'!)
And updated to birl 0.11 to use 'legible_difference'.


Disallow appointments to span two days

Codecov Report

Merging #188 (7624942) into master (af312f6) will decrease coverage by 0.10%.
The diff coverage is 33.33%.

@@             Coverage Diff              @@
##             master     #188      +/-   ##
============================================
- Coverage     79.42%   79.31%   -0.11%
- Complexity      962      963       +1
============================================
  Files           146      146
  Lines          2814     2819       +5
  Branches        330      332       +2
============================================
+ Hits           2235     2236       +1
- Misses          492      494       +2
- Partials         87       89       +2

Impacted Files
Coverage Δ

...c/commands/apptcommand/EditAppointmentCommand.java
86.81% <0.00%> (-1.96%)
:arrow_down:

...ermd/logic/parser/AddAppointmentCommandParser.java
88.63% <33.33%> (-4.23%)
:arrow_down:

...ava/seedu/plannermd/model/appointment/Session.java
93.33% <100.00%> (+0.15%)
:arrow_up:

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 af312f6...7624942. Read the comment docs.