patchelfUnstable: unstable-2022-10-26 -> unstable-2023-03-07

Automatic update generated by nixpkgs-update tools. This update was made based on information from passthru.updateScript.
meta.description for patchelfUnstable is: "A small utility to modify the dynamic linker and RPATH of ELF executables"
meta.homepage for patchelfUnstable is: "https://github.com/NixOS/patchelf"
meta.changelog for patchelfUnstable is: ""
Updates performed

Ran passthru.UpdateScript

To inspect upstream changes

Compare changes on GitHub

Impact

Checks done (click to expand)

built on NixOS
The tests defined in passthru.tests, if any, passed
found unstable-2022-10-28 in filename of file in /nix/store/vjns4jqy8x6x9i0bwhj2gba4y0fm21p6-patchelf-unstable-2022-10-28

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

3 total rebuild path(s)

3 package rebuild(s)

First fifty rebuilds by attrpath
patchelfUnstable
python310Packages.tensorflowWithCuda
python39Packages.tensorflowWithCuda

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/vjns4jqy8x6x9i0bwhj2gba4y0fm21p6-patchelf-unstable-2022-10-28 \
  --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 patchelfUnstable https://github.com/r-ryantm/nixpkgs/archive/aba42c8417cfe6ea7a76d9aa7b2583f92cf167f7.tar.gz

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/vjns4jqy8x6x9i0bwhj2gba4y0fm21p6-patchelf-unstable-2022-10-28
ls -la /nix/store/vjns4jqy8x6x9i0bwhj2gba4y0fm21p6-patchelf-unstable-2022-10-28/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.
nixpkgs-review took longer than 45m and timed out

Maintainer pings
cc @edolstra for testing.

Automatic update generated by nixpkgs-update tools. This update was made based on information from passthru.updateScript.
meta.description for patchelfUnstable is: "A small utility to modify the dynamic linker and RPATH of ELF executables"
meta.homepage for patchelfUnstable is: "https://github.com/NixOS/patchelf"
meta.changelog for patchelfUnstable is: ""
Updates performed

Ran passthru.UpdateScript

To inspect upstream changes

Compare changes on GitHub

Impact

Checks done (click to expand)

built on NixOS
The tests defined in passthru.tests, if any, passed
found unstable-2022-11-04 in filename of file in /nix/store/gpy74r7af7mk88klvcip0ggz8rmg1vqi-patchelf-unstable-2022-11-04

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

3 total rebuild path(s)

3 package rebuild(s)

First fifty rebuilds by attrpath
patchelfUnstable
python310Packages.tensorflowWithCuda
python39Packages.tensorflowWithCuda

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/gpy74r7af7mk88klvcip0ggz8rmg1vqi-patchelf-unstable-2022-11-04 \
  --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 patchelfUnstable https://github.com/r-ryantm/nixpkgs/archive/45addddb191f601045fb21aed85d2eb74deb18f3.tar.gz

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/gpy74r7af7mk88klvcip0ggz8rmg1vqi-patchelf-unstable-2022-11-04
ls -la /nix/store/gpy74r7af7mk88klvcip0ggz8rmg1vqi-patchelf-unstable-2022-11-04/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.
nixpkgs-review took longer than 45m and timed out

Maintainer pings
cc @edolstra for testing.

Automatic update generated by nixpkgs-update tools. This update was made based on information from passthru.updateScript.
meta.description for patchelfUnstable is: "A small utility to modify the dynamic linker and RPATH of ELF executables"
meta.homepage for patchelfUnstable is: "https://github.com/NixOS/patchelf"
meta.changelog for patchelfUnstable is: ""
Updates performed

Ran passthru.UpdateScript

To inspect upstream changes

Compare changes on GitHub

Impact

Checks done (click to expand)

built on NixOS
The tests defined in passthru.tests, if any, passed
found unstable-2022-11-06 in filename of file in /nix/store/a6v1s6jzm8banhb6bs730i2xq0lyc61n-patchelf-unstable-2022-11-06

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

3 total rebuild path(s)

3 package rebuild(s)

First fifty rebuilds by attrpath
patchelfUnstable
python310Packages.tensorflowWithCuda
python39Packages.tensorflowWithCuda

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/a6v1s6jzm8banhb6bs730i2xq0lyc61n-patchelf-unstable-2022-11-06 \
  --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 patchelfUnstable https://github.com/r-ryantm/nixpkgs/archive/8b0beedf2c02c78019ebd0f3e645445b34891b05.tar.gz

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/a6v1s6jzm8banhb6bs730i2xq0lyc61n-patchelf-unstable-2022-11-06
ls -la /nix/store/a6v1s6jzm8banhb6bs730i2xq0lyc61n-patchelf-unstable-2022-11-06/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

2 packages failed to build:

python310Packages.tensorflowWithCuda
python39Packages.tensorflowWithCuda

1 package built:

patchelfUnstable

Maintainer pings
cc @edolstra for testing.

Automatic update generated by nixpkgs-update tools. This update was made based on information from passthru.updateScript.
meta.description for patchelfUnstable is: "A small utility to modify the dynamic linker and RPATH of ELF executables"
meta.homepage for patchelfUnstable is: "https://github.com/NixOS/patchelf"
meta.changelog for patchelfUnstable is: ""
Updates performed

Ran passthru.UpdateScript

To inspect upstream changes

Compare changes on GitHub

Impact

Checks done (click to expand)

built on NixOS
The tests defined in passthru.tests, if any, passed
found unstable-2022-11-08 in filename of file in /nix/store/7wdvyg2gs5qs40g2xg7c2n6hpl97q5by-patchelf-unstable-2022-11-08

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

3 total rebuild path(s)

3 package rebuild(s)

First fifty rebuilds by attrpath
patchelfUnstable
python310Packages.tensorflowWithCuda
python39Packages.tensorflowWithCuda

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/7wdvyg2gs5qs40g2xg7c2n6hpl97q5by-patchelf-unstable-2022-11-08 \
  --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 patchelfUnstable https://github.com/r-ryantm/nixpkgs/archive/10969ffc62f61c33ef58d5c598c5a742c3099f9d.tar.gz

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/7wdvyg2gs5qs40g2xg7c2n6hpl97q5by-patchelf-unstable-2022-11-08
ls -la /nix/store/7wdvyg2gs5qs40g2xg7c2n6hpl97q5by-patchelf-unstable-2022-11-08/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.
nixpkgs-review took longer than 45m and timed out

Maintainer pings
cc @edolstra for testing.

Automatic update generated by nixpkgs-update tools. This update was made based on information from passthru.updateScript.
meta.description for patchelfUnstable is: "A small utility to modify the dynamic linker and RPATH of ELF executables"
meta.homepage for patchelfUnstable is: "https://github.com/NixOS/patchelf"
meta.changelog for patchelfUnstable is: ""
Updates performed

Ran passthru.UpdateScript

To inspect upstream changes

Compare changes on GitHub

Impact

Checks done (click to expand)

built on NixOS
The tests defined in passthru.tests, if any, passed
found unstable-2022-11-14 in filename of file in /nix/store/kpvd185rzv6ba4yw9zav3z3azl0iyr25-patchelf-unstable-2022-11-14

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

3 total rebuild path(s)

3 package rebuild(s)

First fifty rebuilds by attrpath
patchelfUnstable
python310Packages.tensorflowWithCuda
python39Packages.tensorflowWithCuda

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/kpvd185rzv6ba4yw9zav3z3azl0iyr25-patchelf-unstable-2022-11-14 \
  --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 patchelfUnstable https://github.com/r-ryantm/nixpkgs/archive/dceff119fa5d0c4fa4925f355bbd18fa3a532541.tar.gz

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/kpvd185rzv6ba4yw9zav3z3azl0iyr25-patchelf-unstable-2022-11-14
ls -la /nix/store/kpvd185rzv6ba4yw9zav3z3azl0iyr25-patchelf-unstable-2022-11-14/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.
nixpkgs-review took longer than 45m and timed out

Maintainer pings
cc @edolstra for testing.

Automatic update generated by nixpkgs-update tools. This update was made based on information from passthru.updateScript.
meta.description for patchelfUnstable is: "A small utility to modify the dynamic linker and RPATH of ELF executables"
meta.homepage for patchelfUnstable is: "https://github.com/NixOS/patchelf"
meta.changelog for patchelfUnstable is: ""
Updates performed

Ran passthru.UpdateScript

To inspect upstream changes

Compare changes on GitHub

Impact

Checks done (click to expand)

built on NixOS
The tests defined in passthru.tests, if any, passed
found unstable-2022-11-17 in filename of file in /nix/store/s17f1wfnsp4rl93fv3wdaq299i1f0i8h-patchelf-unstable-2022-11-17

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

3 total rebuild path(s)

3 package rebuild(s)

First fifty rebuilds by attrpath
patchelfUnstable
python310Packages.tensorflowWithCuda
python39Packages.tensorflowWithCuda

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/s17f1wfnsp4rl93fv3wdaq299i1f0i8h-patchelf-unstable-2022-11-17 \
  --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 patchelfUnstable https://github.com/r-ryantm/nixpkgs/archive/b85a759516cd9377c332d1ef7a6930216ed4947d.tar.gz

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/s17f1wfnsp4rl93fv3wdaq299i1f0i8h-patchelf-unstable-2022-11-17
ls -la /nix/store/s17f1wfnsp4rl93fv3wdaq299i1f0i8h-patchelf-unstable-2022-11-17/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.
nixpkgs-review took longer than 45m and timed out

Maintainer pings
cc @edolstra for testing.

Automatic update generated by nixpkgs-update tools. This update was made based on information from passthru.updateScript.
meta.description for patchelfUnstable is: "A small utility to modify the dynamic linker and RPATH of ELF executables"
meta.homepage for patchelfUnstable is: "https://github.com/NixOS/patchelf"
meta.changelog for patchelfUnstable is: ""
Updates performed

Ran passthru.UpdateScript

To inspect upstream changes

Compare changes on GitHub

Impact

Checks done (click to expand)

built on NixOS
The tests defined in passthru.tests, if any, passed
found unstable-2022-12-27 in filename of file in /nix/store/3zk42zndb990xfv7260n9yiy57wvmrd5-patchelf-unstable-2022-12-27

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

3 total rebuild path(s)

3 package rebuild(s)

First fifty rebuilds by attrpath
patchelfUnstable
python310Packages.tensorflowWithCuda
python39Packages.tensorflowWithCuda

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/3zk42zndb990xfv7260n9yiy57wvmrd5-patchelf-unstable-2022-12-27 \
  --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 patchelfUnstable https://github.com/r-ryantm/nixpkgs/archive/373bc948785dc3c4c3e09e4c6f55c6c0d812fa75.tar.gz

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/3zk42zndb990xfv7260n9yiy57wvmrd5-patchelf-unstable-2022-12-27
ls -la /nix/store/3zk42zndb990xfv7260n9yiy57wvmrd5-patchelf-unstable-2022-12-27/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.
nixpkgs-review took longer than 45m and timed out

Maintainer pings
cc @edolstra for testing.

Automatic update generated by nixpkgs-update tools. This update was made based on information from passthru.updateScript.
meta.description for patchelfUnstable is: A small utility to modify the dynamic linker and RPATH of ELF executables
meta.homepage for patchelfUnstable is: https://github.com/NixOS/patchelf
Updates performed

Ran passthru.UpdateScript

To inspect upstream changes

Compare changes on GitHub

Impact

Checks done (click to expand)

built on NixOS
The tests defined in passthru.tests, if any, passed
found unstable-2023-01-10 in filename of file in /nix/store/gww0rix1sggf6z2407mjqv6y4yg7h7l0-patchelf-unstable-2023-01-10

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

3 total rebuild path(s)

3 package rebuild(s)

First fifty rebuilds by attrpath
patchelfUnstable
python310Packages.tensorflowWithCuda
python39Packages.tensorflowWithCuda

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/gww0rix1sggf6z2407mjqv6y4yg7h7l0-patchelf-unstable-2023-01-10 \
  --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 patchelfUnstable https://github.com/r-ryantm/nixpkgs/archive/f2fef65e7978f927377191c166a5bc859f495974.tar.gz

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/gww0rix1sggf6z2407mjqv6y4yg7h7l0-patchelf-unstable-2023-01-10
ls -la /nix/store/gww0rix1sggf6z2407mjqv6y4yg7h7l0-patchelf-unstable-2023-01-10/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.
nixpkgs-review took longer than 45m and timed out

Maintainer pings
cc @edolstra for testing.

Automatic update generated by nixpkgs-update tools. This update was made based on information from passthru.updateScript.
meta.description for patchelfUnstable is: A small utility to modify the dynamic linker and RPATH of ELF executables
meta.homepage for patchelfUnstable is: https://github.com/NixOS/patchelf
Updates performed

Ran passthru.UpdateScript

To inspect upstream changes

Compare changes on GitHub

Impact

Checks done (click to expand)

built on NixOS
The tests defined in passthru.tests, if any, passed
found unstable-2023-02-19 in filename of file in /nix/store/8nfx39wnmk5shbfc4y2c9z75vqycrp8g-patchelf-unstable-2023-02-19

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

2 total rebuild path(s)

2 package rebuild(s)

First fifty rebuilds by attrpath
patchelfUnstable
python310Packages.tensorflowWithCuda

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/8nfx39wnmk5shbfc4y2c9z75vqycrp8g-patchelf-unstable-2023-02-19 \
  --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 patchelfUnstable https://github.com/r-ryantm/nixpkgs/archive/b1f034db95e14612a953421b303022fca71901b5.tar.gz

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/8nfx39wnmk5shbfc4y2c9z75vqycrp8g-patchelf-unstable-2023-02-19
ls -la /nix/store/8nfx39wnmk5shbfc4y2c9z75vqycrp8g-patchelf-unstable-2023-02-19/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.
nixpkgs-review took longer than 45m and timed out

Maintainer pings
cc @edolstra for testing.

Automatic update generated by nixpkgs-update tools. This update was made based on information from passthru.updateScript.
meta.description for patchelfUnstable is: A small utility to modify the dynamic linker and RPATH of ELF executables
meta.homepage for patchelfUnstable is: https://github.com/NixOS/patchelf
Updates performed

Ran passthru.UpdateScript

To inspect upstream changes

Compare changes on GitHub

Impact

Checks done (click to expand)

built on NixOS
The tests defined in passthru.tests, if any, passed
found unstable-2023-02-20 in filename of file in /nix/store/nfw7clpb6xz47l0jifgxpcfkik9h4spl-patchelf-unstable-2023-02-20

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

2 total rebuild path(s)

2 package rebuild(s)

First fifty rebuilds by attrpath
patchelfUnstable
python310Packages.tensorflowWithCuda

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/nfw7clpb6xz47l0jifgxpcfkik9h4spl-patchelf-unstable-2023-02-20 \
  --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 patchelfUnstable https://github.com/r-ryantm/nixpkgs/archive/021491bb239a91e0239be205bc07efe9d5d8ccf7.tar.gz

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/nfw7clpb6xz47l0jifgxpcfkik9h4spl-patchelf-unstable-2023-02-20
ls -la /nix/store/nfw7clpb6xz47l0jifgxpcfkik9h4spl-patchelf-unstable-2023-02-20/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.
nixpkgs-review took longer than 45m and timed out

Maintainer pings
cc @edolstra for testing.

Automatic update generated by nixpkgs-update tools. This update was made based on information from passthru.updateScript.
meta.description for patchelfUnstable is: A small utility to modify the dynamic linker and RPATH of ELF executables
meta.homepage for patchelfUnstable is: https://github.com/NixOS/patchelf
Updates performed

Ran passthru.UpdateScript

To inspect upstream changes

Compare changes on GitHub

Impact

Checks done (click to expand)

built on NixOS
The tests defined in passthru.tests, if any, passed
found unstable-2023-02-24 in filename of file in /nix/store/dlxmlikl89rbb5cjsx4hrbbmdjz2zmbq-patchelf-unstable-2023-02-24

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

2 total rebuild path(s)

2 package rebuild(s)

First fifty rebuilds by attrpath
patchelfUnstable
python310Packages.tensorflowWithCuda

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/dlxmlikl89rbb5cjsx4hrbbmdjz2zmbq-patchelf-unstable-2023-02-24 \
  --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 patchelfUnstable https://github.com/r-ryantm/nixpkgs/archive/83213572ce71ef4a1beb17e3cee0842513ea5549.tar.gz

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/dlxmlikl89rbb5cjsx4hrbbmdjz2zmbq-patchelf-unstable-2023-02-24
ls -la /nix/store/dlxmlikl89rbb5cjsx4hrbbmdjz2zmbq-patchelf-unstable-2023-02-24/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.
nixpkgs-review took longer than 45m and timed out

Maintainer pings
cc @edolstra for testing.

Automatic update generated by nixpkgs-update tools. This update was made based on information from passthru.updateScript.
meta.description for patchelfUnstable is: A small utility to modify the dynamic linker and RPATH of ELF executables
meta.homepage for patchelfUnstable is: https://github.com/NixOS/patchelf
Updates performed

Ran passthru.UpdateScript

To inspect upstream changes

Compare changes on GitHub

Impact

Checks done (click to expand)

built on NixOS
The tests defined in passthru.tests, if any, passed
found unstable-2023-03-07 in filename of file in /nix/store/1bwaszfzz0cgxx5nxawh6x077x2n52g8-patchelf-unstable-2023-03-07

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

2 total rebuild path(s)

2 package rebuild(s)

First fifty rebuilds by attrpath
patchelfUnstable
python310Packages.tensorflowWithCuda

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/1bwaszfzz0cgxx5nxawh6x077x2n52g8-patchelf-unstable-2023-03-07 \
  --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 patchelfUnstable https://github.com/r-ryantm/nixpkgs/archive/c2fc72d723aa7e1e79354303707c5eb174e2f9b5.tar.gz

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/1bwaszfzz0cgxx5nxawh6x077x2n52g8-patchelf-unstable-2023-03-07
ls -la /nix/store/1bwaszfzz0cgxx5nxawh6x077x2n52g8-patchelf-unstable-2023-03-07/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.
nixpkgs-review took longer than 45m and timed out

Maintainer pings
cc @edolstra for testing.

@ofborg build python310Packages.tensorflowWithCuda

Wait, does python310Packages.tensorflowWithCuda really build with that?

Wait, does python310Packages.tensorflowWithCuda really build with that?

Yup!

There should be no more reason to do it. Proposed tensorflow switch to stable patchelf as https://github.com/NixOS/nixpkgs/pull/221870


Inline scripts should be externalized

In chat/room page, some javascript from plugins are inline scripts.
It's bad for performance.
So they should be externalized.

Coverage increased (+0.01%) to 89.8% when pulling<PHONE_NUMBER>f3f96377ee178c4238826558c805f2 on mallowlabs:id/209 into 16e47335240f0318b6db2d92be81adc5c1ba1a46 on codefirst:master.

Thanks :rabbit2:


Add Coverage Reporting

Codecov Report

:exclamation: No coverage uploaded for pull request base (main@cc2fa29). Click here to learn what that means.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main      #52   +/-   ##
=======================================
  Coverage        ?   58.25%
=======================================
  Files           ?       22
  Lines           ?      642
  Branches        ?        0
=======================================
  Hits            ?      374
  Misses          ?      223
  Partials        ?       45

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 cc2fa29...24e9cdc. Read the comment docs.


HF1 - Forks - fork choice by block,slot pair

https://notes.ethereum.org/@vbuterin/HF1_proposal#Fork-choice-by-block-slot-pair

spec PR is still pending
https://github.com/ethereum/eth2.0-specs/pull/2197


Min SNR weighting implemented as max SNR weighting

Hey Phil! I believe that the Min SNR weighting is currently implemented as
loss_weight = max(snr, self.min_snr_gamma)
instead of
loss_weight = min(snr, self.min_snr_gamma)
I think line 839 should be
maybe_clipped_snr.clamp_(max = self.min_snr_gamma)
https://github.com/lucidrains/recurrent-interface-network-pytorch/blob/77e4ced5cd8d091acae31ad2cb19a32f64a4eb3a/rin_pytorch/rin_pytorch.py#L833-L850
Apologies if I'm misunderstanding something 🙂

@justinlovelace oh yes you are right! thank you for finding this so quickly
ugh i committed this error in a number of other repos too

Happy to help! Was just trying the new weighting scheme out for some of my work and noticed the issue

thank you Justin! and if Lovelace is your last name, you'd be the first Lovelace I've met (besides knowing the famous Ada)


WFLY-16475: Upgrade HAL to 3.6.0.Final

https://issues.redhat.com/browse/WFLY-16475

Thanks @hpehl


tag 2.27.0 is having issue where stellar core is failing to run inside the horizon for testnet servers

What version are you using?
2.27.0

What did you do?
after the latest protocol release, i wanted to upgrade my testnet servers from tag 2.27.0-rc2-384 to tag 2.27.0 (released on dec 18)

What did you expect to see?
stellar core should be able to run, as there were no major fixes to be done on my code
What did you see instead?
time="2024-01-05T08:28:37.977Z" level=warning msg="could not load stellar-core info: http request errored: Get \"http://localhost:11626/info\": dial tcp <IP_ADDRESS>:11626: connect: connection refused" pid=1 time="2024-01-05T08:28:37.977Z" level=error msg="failed to load the stellar-core info" err="http request errored: Get \"http://localhost:11626/info\": dial tcp <IP_ADDRESS>:11626: connect: connection refused" pid=1 stack="[main.go:43 client.go:139 app.go:230 app.go:442 asm_amd64.s:1598]"
this is my docker run command i am using earlier
docker run --name horizon   --network=host --rm --mount type=bind,source=/etc/default/horizon-stellar-captive-core.toml,target=/etc/default/stellar-captive-core.toml  --mount type=bind,source=/etc/default/stellar-horizon,target=/etc/default/stellar-horizon -e NETWORK=testnet -e DATABASE_URL=postgres://postgres:xxxxxxxxxxxx@xxxxxxxx:5432/postgres?sslmode=disable -e PER_HOUR_RATE_LIMIT=0 -e INGEST=true -e STELLAR_CORE_BINARY_PATH=/usr/bin/stellar-core stellar/stellar-horizon:2.27.0 --apply-migrations
after all the possible tries. I manually did a private build on my server and made the server work.
I pulled the latest (with head point to b0220a0d92ba925cfb22f976f7805f4c4a3b4992 this commit) and generated a docker image using docker compose in the latest. This docker image seems to be working for me to bring up the chain.
these are versions of stellar inside my private build container
 stellar-core-prometheus-exporter/now 0.10.5-18 amd64 [installed,local] stellar-core-utils/now 0.2-9 amd64 [installed,local] stellar-core/now 20.0.2-1633.669916b56.focal amd64 [installed,local] stellar-horizon-utils/now 0.3-5 amd64 [installed,local] stellar-horizon/now 2.28.0~rc1-396 amd64 [installed,local]
looks like 2.28.0~rc1-396 is working but not 2.27.0

2.28.0 is now officially released


flash attention should be required when using sample_packing

Please check that this issue hasn't been reported before.

[X] I searched previous Bug Reports didn't find any similar reports.

Expected Behavior
validation error should occur
Current behaviour
no validation error
Steps to reproduce
set sample_packing: false and flash_attention: false
Possible solution
add validation
Which Operating Systems are you using?

[X] Linux
[ ] macOS
[ ] Windows

Python Version
3.10
axolotl branch-commit
main
Acknowledgements

[X] My issue title is concise, descriptive, and in title casing.
[X] I have searched the existing issues to make sure this bug has not been reported yet.
[X] I am using the latest version of axolotl.
[X] I have provided enough information for the maintainers to reproduce and diagnose the issue.

Hi @winglian and @NanoCode012 .
I am using old V100 GPUs and they do not support flash attention.
But it works with sample_packing.
What exactly is wrong on using sample_packing without flash attention?
Why is this a bug?


Update the nodejs version matrix for travis

Travis is testing nodejs versions not supported. According to this (https://endoflife.date/nodejs), anything below 14 is not supported anymore.

Not supported by node itself - but absolutely supported by this package. Platform support is irrelevant as to whether packages should support a version or not.


Validation accuracy higher than training accuracy

Hi, I'm training using the example script on the cats and dogs dataset, and noticed the validation accuracy is consistently higher than training accuracy throughout training. This occurs both with and without dropout and dropout_emb. Is this typical for a ViT? Below is a plot of training and validation accuracy for SmallDatasetVit compared to a CNN for reference.
The model and parameters used are as follows:
from vit_pytorch.vit_for_small_dataset import ViT
batch_size = 64
model = ViT(
image_size = 224,
patch_size = 16,
num_classes = 2,
dim = 1024,
depth = 6,
heads = 16,
mlp_dim = 2048,
dropout = 0.1,
emb_dropout = 0.1)

Update: if this is occurring for anyone else, it's to do with torch's random image augmentation on the train data. I got these results using RandomResizedCrop and RandomHorizontalFlip like in the example code. This also occurs when using the same transforms on a torch CNN (the example above in red was keras). Without image augmentation, the training accuracy far exceeds validation accuracy, but performance is diminished. It's nothing VIT-specific, just torch.


Replace getAll with getKeys in PartialEvaluator_hasBlendModes to speed up loading of badly generated PDF files (issue 6961)

Some bad PDF generators, in particular "Scribus PDF", duplicates resources a lot at various levels of the PDF files. This can lead to PartialEvaluator_hasBlendModes taking an unreasonable amount of time to complete.
The reason is that the current code is using Dict_getAll, which recursively dereferences all indirect objects, which can be really slow. This patch instead uses Dict_getKeys, and then manually looks up only the necessary indirect objects.
I've added the PDF file as a load test. The most important thing here is probably to ensure that the file remains available in the repo, and the comment should help reduce the chance of regressions. (Note that locally, the load test times out without this patch, but we cannot really assume that that always happens.)
Fixes #6961.

/botio-linux preview

/botio test

/botio-linux test

/botio test

Looks good. Thank you for the patch.

Awesome work, thanks for fixing this so quickly!


Invalid credentials

Hey guys,  I installed all codes into the custom components folder. When I install the integration into HA the system asked me as disceibed in the guideline to set account Infos as user and PW. The user (my mail address) and password are definitively correct, but the system refused to login : invalid credentials.  Anyone else who had this problem? Ha version 2021.5.0
Thanks in advance for your help
Peter

The component is currently in a non working state due to underlying service API changes. I’m working on a fix, stay tuned.

Hi Tellerbop,
Looking forward to it - about to fill the pool :)
Thanks!
Perry

I've been in contact with Hayward for a long time now but I'm afraid it has been without success. They are currently not planning to implement any API for integrators to use during 2021.
They are instead pointing us to use MODBUS RS-485 tcp/502 but at least with my installation I see no possibility to enable it.
Below is the latest email I sent. I'll get back to you when and if I get an answer but until then I'm afraid there will be no development.
_**Excuse me for being blunt but I and many others are a bit frustrated about this situation.
I think Hayward/Sugar Valley (and many other companies) still misunderstand how many users look at "home automation". Home automation is not just providing an application, it's about providing integration possibilities. I have 40+ apps in my phone from companies like yours which are either required to install the appliance or to manage it. However, many actually DO provide API's for their services as well so I can live with having them installed just to install them.
But in the home automation world many users do not want another application. We want one place to control every aspect of our home, One place to receive notifications and one place to harmonize integrations.
For instance - Your app doesn't even provide notifications, something I HAD with the old API because we implemented it based on the data you provide. The user can even choose what platform to receive the notification, like Signal, Telegram, Facebook, etc.
Look at this ever growing list of integrations: Integrations - Home Assistant (home-assistant.io)  or Homey Apps This is where your spot should be.
I BOUGHT Hayward Control Station ONLY because it had an API. If it wasn't, I would have bought another brand, probably a swedish one. Now you have destroyed this functionality leaving us with a non working integration, useless application and the only option you have left us with is MODBUS. But in my case, there are NO instructions whatsoever on how to enable the interface.
You are creating angry customers by handling the situation like this. It's not customer centricity and definitely bad PR.
I and others are definitely here to help, I'm offering my time and help to provide a working integration with one of the largest home automation applications out there and I'm sure many with me will follow for other platforms - but we can't do it without your help.
Please prioritize and forward to whom it may concern.**_

Same answer here form Sugar Valley (Hayward): there will be no API access.
In my case, I was able to install a Modbus-to-LAN interface next to the unit and I have to say it works flawlessly, and no cloud needed. But I understand it might be cumbersome for some installations. Thanks for trying. It was great while it lasted.

Hayward is activly promoting the Modbus functionality in their product.

But when I asked Hayward for a documentation they just replyed with 2 lines...
All our products include MODBUS technology RS485, so you can use it with no problem.
You must ask your dealer about the Modbus protocol when you buy the product.
Muchas gracias
WTF

My dealer has NO CLUE about modbus. But I think I've managed to find out where it is. It's not obvious, it's not marked on the board but I found a clue here  and will buy a RS485 to wifi adapter to test with.

I have a working implementation of a VistaPool integration.
But it's written in C# and therefore requires NetDaemon.
The code is a quick and dirty PoC and by no means production ready. But it's running here for a couple of weeks without any issues.
So if anybody is interested I can create a public repo and share the code.

@mutzl That would be great! - I'd just like to get the temperature en redox readings

Have you tried reverse engineering the API? I've never done such a thing, but I looked into it yesterday and I found the source and some logic for some parameters. Not everything though and I don't know my skills are sufficient.

My dealer has NO CLUE about modbus. But I think I've managed to find out where it is. It's not obvious, it's not marked on the board but I found a clue here  and will buy a RS485 to wifi adapter to test with. It's just that you pay quite a bit of money for the wifi module but you can do absolutely nothing with it :)

My vendor just sent me some MODBUS documentation.
If you want me to share that, just send me an email.

Have you tried reverse engineering the API? I've never done such a thing, but I looked into it yesterday and I found the source and some logic for some parameters. Not everything though and I don't know my skills are sufficient.

Yes i have @mutzl has a working copy in c#. However, this is not an official API, it's querying directly against Google Firebase and out of courtesy and respect I'm asking for permission to use it.

@mutzl Could you please share your integration.
I'll send you an email for the modbus documentation, although I don't know I'll be able to use it. At least I'll have it for future reference.

@olafvs could you share the mobus docs with me too?
Thanks!
Perry

These are the three files I received.

No luck .... file.io: "The file you requested has been deleted"
Keen to try Modbus if all other roads are dead ends. I have a USR ethernet device.

Same here: "The file you requested has been deleted"

Ok, Of cource I can mail them, but I want to keep the files online for future reference.
Another free service:
https://gofile.io/d/8ZitaN

This works - thanks!

Hey guys, obviously you're all more pros than me. Since days I try to setup Modus in HA without success. To be honest I didn't understand your conversation: I have a WIFI Module within VISTAPOOL. Does it mean, that I have to buy another component to get things running? I downloaded the MODBUS files but I can't use them because a lack of knowledge. If possible it would be great to have a step by step introduction how to use all the stuff. Thanks a lot Peter

@MisterP64 - I got it to work after fiddling around for a hours and are able to read temp etc. I'd be happy to help out if needed however, you do need to purchase a modbus interface to connect to either "display" or "external" i used this one: https://www.amazon.nl/gp/product/B08Q4MNT4P/ref=ppx_yo_dt_b_asin_title_o01_s00?ie=UTF8&psc=1

Hey guys, obviously you're all more pros than me. Since days I try to setup Modus in HA without success. To be honest I didn't understand your conversation: I have a WIFI Module within VISTAPOOL. Does it mean, that I have to buy another component to get things running? I downloaded the MODBUS files but I can't use them because a lack of knowledge. If possible it would be great to have a step by step introduction how to use all the stuff. Thanks a lot Peter

Yes you need to buy a separate component as the wifi module included is not modbus enabled. I’ve commented this fact to Hayward but they just keep ignoring the stupidity in this. 😂
I’ve ordered some stuff from China to build my own module with a local rest api to avoid the modbus implementation - just might sell it when done as Hayward clearly does not know what modern home automation is. 😉

@ppenders and tellerbop thanks for the quick response. I'll try the modus thing, but I fear that I will not succeed in HA modes setup. I cannot understand the companies like sugar valley. same happened with Mercedes me and others. They all want to do their thing and they are not customer oriented. Does someone have a config example of the modes in HA, who would like to share it? Regards Peter

@MisterP64 this topic can get you going and has a lot of examples to get started: https://community.home-assistant.io/t/vistapool-integration/128695/10
As mentioned before - you will need additional hardware.

The new release of Hayward uses firestore from google, I'm not familiar with this but I was able to reverse engineer the website to get pool value. So far, I've not been able to send command. if anyone is familiar with firestore, we could surely get it done.
sharing my code to read pool data, it's written for openhab, but you can understand what it's doing. You can get the API key from the developer console on website poolwatch.hayward.fr

// Verify the user account and get id and refresk token
var jsonResponse = sendHttpPostRequest('https://www.googleapis.com/identitytoolkit/v3/relyingparty/verifyPassword?key='+Hayward_APIKey, 'application/json', '{email: "'+Hayward_User+'", password: "'+Hayward_Passwd+'", returnSecureToken: true}',5000)
val idToken = transform("JSONPATH","$.idToken", jsonResponse)
val refreshToken = transform("JSONPATH","$.refreshToken", jsonResponse)
Hayward_refreshToken.postUpdate(refreshToken)

// Using the received if token get the access token and user id
jsonResponse = sendHttpPostRequest('https://www.googleapis.com/identitytoolkit/v3/relyingparty/getAccountInfo?key='+Hayward_APIKey, 'application/json', '{idToken:"'+idToken+'"}',5000)
jsonResponse = sendHttpPostRequest('https://securetoken.googleapis.com/v1/token?key='+Hayward_APIKey, 'application/json', '{grant_type:"refresh_token", refresh_token:"'+refreshToken+'"}', 5000)
val access_token = transform("JSONPATH","$.access_token", jsonResponse )
val user_id = transform("JSONPATH","$.user_id", jsonResponse)
Hayward_accessToken.postUpdate(access_token)

// Using the access token get the pool id
jsonResponse = queryAPI.apply('https://firestore.googleapis.com/v1beta1/projects/hayward-europe/databases/(default)/documents/users/'+user_id, readResponse)
postUpdate('Hayward_poolID', transform("JSONPATH","$.fields.pools.arrayValue.values[0].stringValue", jsonResponse))

// READ THE POOL DATA
jsonResponse = queryAPI.apply('https://firestore.googleapis.com/v1beta1/projects/hayward-europe/databases/(default)/documents/pools/'+Hayward_poolID.state.toString, readResponse)

I bought the additional hardware two days after you mentioned that I reedit. Since weeks now I try to get this modes thing started. I just have problems to reach the additional hardware ppenders recommended to me. The thing is that I have no clue how to set up the initial things in HA. The component is shown in my WIFI setting as EW 11_..., so I am sure to have a connection with it. Attached you can see the Logs of my system.
thanks for your support

Hey guys, I changed the IP of the Elfin EW 11 into a new IP. Now I get a TIME OUT ; the original IP was not the classical one (10.10.100.---) I have access to the Elfin via WIFI and Router, can modify the settings, but HA sends this logfile:

Do you have any idea what went wrong

Hello, meanwhile I suceeded in setting up modbus and establishing a connection to the Elfin EW 11 (I checked it with the hiflying app tcpudpdgb on their Website). Nevertheless HA doesn't detect any sensor in Vistapool. Attached my config. Could you see any mistake (The X in the IP are set only in this post, real IP is set in config).  The lovelace card gave the response: sensor.mbf_measure_temperature not available. Thanks for your support

first picture is Lovelace, second one is config folder within HA (I didn't make it clear in my last post, sorry).


controller helpers

this is a set of controller helpers to make it easier to build controllers

Do we need a helper on the controller-runtime utils for Finalizer and Patching?

eventually I would like to appear in controller runtime, but I did not find it anywhere so far in a way that it extends the client gracefully.

This may have been covered already by the bootstrap controller PR? @henderiw

this is covered by the bootstrap controller now


Is it possible to make scanner only active when qr code is in the center of screen (or any specific place on screen)

Right now whenever the camera detects a QR code on the screen, the onRead() will be activated
is it possible to make the onRead() only active when the QR code is in the center of the screen?

There are other event arguments in "onRead" event. For example if you log the event arguments like this:
 const onQrRead = (e) => {
        console.log(JSON.stringify(e))
    }

The output will be something like that:
{
  "bounds": {
    "width": 1920,
    "height": 1440,
    "origin": [
      {
        "y": "1162.0",
        "x": "527.5"
      },
      {
        "y": "796.5",
        "x": "520.5"
      },
      {
        "y": "799.0",
        "x": "908.0"
      },
      {
        "y": "1125.5",
        "x": "857.0"
      }
    ]
  },
  "type": "QR_CODE",
  "rawData": "42438663130393239392d643639622d346165632d623136662d6539376530663632393435660ec11ec11ec11ec11",
  "data": "8f109299-d69b-4aec-b16f-e97e0f62945f",
  "target": 1219
}

You can use bounds.origin object. These are the coordinates of 3 position and 1 alignment points. In other words these are the coordinates of the big points clockwise starting from the bottom left. You can check if all of these coordinates are in your specific region or not. if they are not, you can just "return" your onRead event.


Fix issue #185- Add to useful links

Hi @SirLich ,
I have fixed the #185.
Let me know if everything looks okay or I need to modify anything else.
Thanks.
Badal

Looks good buddy. Thanks for the pr!


Code Splitting / Route Chunking

My biggest concern with setting up a new routing library is not architecting my way out of code splitting. Now I haven't tried this, but would this sort of approach used alongside React Router work just as well here with Redux Little Router?
Quick and dirty code splitting with React Router v4
https://gist.github.com/acdlite/a68433004f9d6b4cbc83b5cc3990c194
More details from this article:
https://medium.com/@apostolos/server-side-rendering-code-splitting-and-hot-reloading-with-react-router-v4-87239cfc172c
I don't see why not, but I'm coming in a little green. This is described alternatively as "async routes", so I suppose this would be an implementation of async Fragments, in a way.

Hi @mherodev! If you're just using Fragment and not relying on data attached to static routes, the React Router approach should work just fine. I'll add a demo soon.
If you do use static routes, there's a replaceRoutes action creator in v14.2.0. You'll want to look at the advanced docs for usage.


Build a dashboard

We need a simple dashboard to point at projection endpoints (multiple) which will list them all.

blocking for BRV-48


Update helm-chart

Set redpanda image to v21.3.7
Deprecate redpanda Chart
Set redpanda image to v21.4.2
Fix test: api status to cluster info

https://github.com/vectorizedio/helm-charts/pull/33


Adsk contrib - Fix issue with minizip build

This is the PR for Impossible to build against system/external minizip-ng.
I removed the minizip-ng subfolder part when including minizip-ng's headers. This fixes the issue with external builds that don't use that subfolder.
For internal builds, a subfolder is created like the other modules that OCIO is able to download and install manually.
I've decided that having Findminizip-ng.cmake and Findminizip.cmake is less confusing than having only a Findminizip.cmake since "minizip" is not the actual name of the library (minizip-ng without MZ_COMPAT=ON).
Therefore, the build system does the following:

Search for minizip-ng (libminizip-ng) (without MZ_COMPAT=ON)
If minizip-ng is not found,  Search minizip-ng with MZ_COMPAT=ON (which is libminizip).
If steps 1 and 2 are not found, download and install minizip-ng with MZ_COMPAT=OFF.
It is set as OFF because we don't need the compatibility part. We are using the "new" API from minizip-ng.

Note that the analysis workflow is failing, but it was failing before already. The PR does not introduce any new problems with the analysis workflow.

@remia @michdolan , could one of you review this?  Merging this would simplify an upcoming PR for us.  TIA!

Looks good to me, thanks for updating the Analysis workflow! One thing I noticed while testing on macOS, the build with install ALL externals deps works perfectly but when using the minizip-ng from brew, it seems the mz_strm_zlib.h header is missing from /usr/local/include (all the other minizip include are present though). Does anyone else have this issue?

Looks good to me, thanks for updating the Analysis workflow! One thing I noticed while testing on macOS, the build with install ALL externals deps works perfectly but when using the minizip-ng from brew, it seems the mz_strm_zlib.h header is missing from /usr/local/include (all the other minizip include are present though). Does anyone else have this issue?

The minizip-ng packages available through brew do not have a dependency on zlib. That tells me that particular minizip-ng wasn't built with zlib compression activated. Based on the dependencies list, it was built with xz and zstd compression activated - which corresponds with the missing mz_strm_zlib.h.

Thanks for the review Remi!  Regarding the Brew issue, based on Cedrik's reply, it sounds like the Brew minizip-ng cannot be used with OCIO since it was not compiled with zlib support activated.  In any case, I think we could merge this one now to unblock Cedrik's other PR.  We could come back to the Brew issue later, if that's ok with you.

Thanks @cedrik-fuoco-adsk yeah that make sense, I guess I'm surprised that zlib is not used it seemed like an obvious choice (to my naive eyes). Agree @doug-walker sorry for dragging this PR!

Don't worry Remi, you did not drag the PR.  You raised an excellent point about Brew.  And in fact you sped up the PR by reviewing it, thank you!!


Feature/add snowflake compatibility

completed all of the items in the issue we created with the exception of investigating field definitions for useragents and performance_timing contexts
tested on 1 snowflake project and 1 redshift project and both ran the entire projects successfully

@drewbanin - this is ready to review when you get a chance


ScatteredInterpolation.jl

added ScatteredInterpolations.jl support
added docstring

Note: Currently the Scatteredinterpolators are ~100 slower... no idea why yet :)

superseded by #20

it seems that #20 only implements ScatteredInterpolation.jl for extrapolating the boundary helper-points.
Whereas this implements ScatteredInterpolation for all points as interpolators.
Did I miss something?

No, I think we could still merge this, even though it may not be the best interpolator...

they are for sure not the best ones, super slow for started. But there are plenty of different algorithms implemented.

Codecov Report

Merging #5 (a4aa0f9) into master (580252f) will decrease coverage by 5.50%.
The diff coverage is 0.00%.

@@            Coverage Diff             @@
##           master       #5      +/-   ##
==========================================
- Coverage   89.85%   84.35%   -5.51%
==========================================
  Files           5        5
  Lines         138      147       +9
==========================================
  Hits          124      124
- Misses         14       23       +9

Impacted Files
Coverage Δ

src/TopoPlots.jl
100.00% <ø> (ø)

src/interpolators.jl
60.00% <0.00%> (-33.75%)
:arrow_down:

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.


[DO NOT MERGE YET] Use ament for amathutils_lib

Status
PRODUCTION / DEVELOPMENT
Description
Replace catkin with ament_cmake for amathutils_lib for future ROS2 transitioning (#2015).
Related PRs
#2014

Closed as obsolete.

Gitlab CI pipeline:
https://gitlab.com/maximosipov/autoware/pipelines/49132626


[RN] (Chore) #2450 Send/Receive by address - User should see a warning message

Description
Its a copy of #2451 PR for react-native branch.
About #2450

@yaroslav-fedyshyn-nordwhale pls see comments on master PR


Need help with maintenance?

Hi @jonboulle,
First of all, thanks for this package, I think it's a quite popular one!
I noticed there are a couple open issues and PRs and I wonder if you need help with maintenance. Either as a contributor to this repo, or if you don't want to maintain it anymore, as a managed fork somewhere (eg. https://github.com/gofrs).
Let me know what you think!

You're right, unfortunately I don't really have the capacity any more to provide proper maintenance.
I would be glad to hand over most of that responsibility if someone is willing to take it on.   :-)

I am. :)

Thanks!
I'll do my best!


[GHSA-45pg-36p6-83v9] Langchain SQL Injection vulnerability

Updates

CVSS v3
CVSS v4
Severity

Comments
I am the security researcher that found the vulnerability. NVD CVSS score is of 9.8 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
This vulnerability is easy to exploit, exists in the default configuration, and results in full database exposure. The affected database is commonly used in scenarios where this functionality's interface exposes user input to the package. + credit would be nice ;) Thanks.

Hey there. It looks like the cvss 3.1 score we have comes from the huntr.dev report which I'm inclined to believe that over the nvd score. Reading from the huntr thread it seems like langchain does document that access control is the responsibility of the api user.
Ref: https://huntr.com/bounties/8f4ad910-7fdc-4089-8f0a-b5df5f32e7c5

As noted in the Huntr thread, I reported the issue with the same severity
that NVD ultimately assigned. I had an extensive discussion there about it,
and they acknowledged that the vulnerability has a significant impact.
LangChain includes a dangerous functionality opt-in called
"allow_dangerous_requests",  but it is implemented in numerous chains but
was not consistently across all text2query chains/tools. After my
disclosure, they mitigated these vulnerabilities and added
"allow_dangerous_requests" to the affected chains/tools.
For example, one of the chains mitigated because of my report is referenced
here:
LangChain GitHub
https://github.com/langchain-ai/langchain/blame/abaea28417adb63dae0cfad3c60dff5297e3ce0d/libs/community/langchain_community/chains/graph_qa/neptune_sparql.py#L116
.
Following the "Secure By Design" and "Secure By Default" principles
outlined in CISA’s guidelines, all code should be secure by default. As I
further highlighted in the Huntr thread, neither Neo4j nor LangChain's
official blogs or documentation reference the security implications of this
vulnerability. The only mentions are in general guidelines or as a source
code comment.
From a technical perspective, the CVSS score assigned to this vulnerability
is incorrect. This is not a local vulnerability but a network
vulnerability. An attacker does not need internal access to exploit it,
and the impact on integrity and availability is High, not Low, as they
indicated. The vulnerability enables full database compromise and could
even impact multi-tenant setups. Moreover, the attack complexity is
extremely low—just a single line of text is enough to exploit it.
Any SQL injection can be mitigated by placing a least privileged user and
also this won't remediate this vulnerability fully as the user can still
READ unintended database data in a raw way. After all, I think this is a
classic showcase how a vendor "decides" severity score based on business
objective and not pure technical perspective as the CVSS score they
reported is false no matter if it had or didn't have a security note (and
if a security note). Apache could also claim in Log4shell not to log "user
input" and if so, it is the responsibility of the user but this is not how
application security and vulnerability works. This is a joint effort and
all should take full "ownership" as threat actors are just waiting to
exploit the weakness.
CISA REF of NVD score acceptance:
https://www.cisa.gov/news-events/bulletins/sb24-309
Anyways, I would like to have your thoughts about it.
Liad
בתאריך יום ד׳, 20 בנוב׳ 2024 ב-22:39 מאת Jon @.***
>:

Hey there. It looks like the cvss 3.1 score we have comes from the
huntr.dev report which I'm inclined to believe over the nvd score.
Reading from the huntr thread it seems like langchain does document that
access control is the responsibility of the api user.
Ref: https://huntr.com/bounties/8f4ad910-7fdc-4089-8f0a-b5df5f32e7c5
—
Reply to this email directly, view it on GitHub
https://github.com/github/advisory-database/pull/5025#issuecomment-2489500687,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AOF3AD6CZD2KNKSE2U2R3YD2BTXP3AVCNFSM6AAAAABSFLFQQWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDIOBZGUYDANRYG4
.
You are receiving this because you authored the thread.Message ID:
@.***>

LangChain includes a dangerous functionality opt-in called "allow_dangerous_requests",  but it is implemented in numerous chains but was not consistently across all text2query chains/tools. After my disclosure, they mitigated these vulnerabilities and added "allow_dangerous_requests" to the affected chains/tools.

That reads like it should be a considered a vuln in the chain that uses the function to me. It seems somewhat analogous to a database exposing full sql capacity. One would not say that mySQL or postgresql or whatever is vulnerable to sql injection, but rather some application using it could be depending on the context of the application.

From a technical perspective, the CVSS score assigned to this vulnerability is incorrect. This is not a local vulnerability but a network vulnerability

Is that the case? Does langchain accept prompts from the network by default?

I’m not sure I follow your analogy. Databases that expose SQL queries are
explicitly designed to run SQL, whereas LangChain is not intended as a SQL
engine to run queries like other packages, alembic or sqlalchemy. Instead,
it takes user text input and generates SQL (or Cypher) queries under the
hood as langchain is a "Build context-aware reasoning applications".
If you compare this to the alternative LlamaIndex, you’ll notice they avoid
this vulnerability by separating the logic for generating a Cypher query
from executing it.
Here’s the difference:

LlamaIndex: User input (text) → Cypher query generation → Explicit
action to execute the query on the database (2-step process) → System
response (text).
LangChain: User input (text) → Cypher query automatically executed
on the database (single-step process) → System response (text).

This distinction is critical because LangChain’s approach combines query
generation and execution into a single action, increasing the risk of
vulnerabilities and there isn't a way to validate a query before it runs on
the database.
Is this a network vulnerability?
LangChain doesn’t accept prompts directly from the network by default, but
it is almost always integrated into APIs or applications that do (This is
how RAG applications work and is useless if not). This makes it effectively
a network vulnerability because the system becomes exposed through typical
usage. as "Local" vulnerability means the attacker has already access to
the machine / component usually seen in PE vulnerabilities or LFI
vulnerabilities. For example, Log4j itself does not expose a network
interface but became a network vulnerability due to its handling of
untrusted input, such as logging user-provided data that could trigger
malicious behavior like JNDI lookups.
Furthermore, you can even look at the integrity, availability and
complexity as they are reported false as well, as How complex is it to
write "Delete all my nodes in database" and after this action database
can't serve nothing as all was deleted by the attacker (availability).
I hope my detailed answer gives more sense of the vulnerability and its
impact.
Liad
בתאריך יום ה׳, 21 בנוב׳ 2024 ב-0:34 מאת Jon @.***
>:

LangChain includes a dangerous functionality opt-in called
"allow_dangerous_requests", but it is implemented in numerous chains but
was not consistently across all text2query chains/tools. After my
disclosure, they mitigated these vulnerabilities and added
"allow_dangerous_requests" to the affected chains/tools.
That reads like it should be a considered a vuln in the chain that uses
the function to me. It seems somewhat analogous to a database exposing full
sql capacity. One would not say that mySQL or postgresql or whatever is
vulnerable to sql injection, but rather some application using it could be
depending on the context of the application.
From a technical perspective, the CVSS score assigned to this
vulnerability is incorrect. This is not a local vulnerability but a network
vulnerability
Is that the case? Does langchain accept prompts from the network by
default?
—
Reply to this email directly, view it on GitHub
https://github.com/github/advisory-database/pull/5025#issuecomment-2489671997,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AOF3AD5YT2LIAR53D77AMXD2BUE63AVCNFSM6AAAAABSFLFQQWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDIOBZGY3TCOJZG4
.
You are receiving this because you authored the thread.Message ID:
@.***>

I’m not sure I follow your analogy.

The analogy is that an api from one project is created to be used in an open ended way by another project.

LangChain doesn’t accept prompts directly from the network by default, but it is almost always integrated into APIs or applications that do.

Would that not be a problem with the use of langchain as opposed to langchain itself?

I am not sure why you keep focusing only on a specific sentence without the
context of the paragraph.

Langchain and in specific GraphCypherQAChain is designed to get user
input, this is the way it works also in any blog you open from the
official Docs of langchain or neo4j they explain exactly how to use this
functionality and in most or all cases the input passed is user input. *Does
log4shell a network vulnerability or a local one? *

2. Again, please address all other params in the CVSS score.

The problem lies within LangChain itself, as they fall short in
implementing security measures at the API level, unlike other Text2Action
chains they provide. LangChain is not intended to execute raw SQL queries
over a database, and this is not its purpose. Instead, it takes user input
as text and returns a response for "context-aware reasoning applications,"
as stated in the first line of the GitHub project. It is their
responsibility to provide a secure way to use this functionality.

A comparable example is the Log4Shell vulnerability. The purpose of Log4j
is to serve as a logging framework, not a JNDI and LDAP tool. However,
Log4j used these functionalities to enhance its logging system,
inadvertently creating a vulnerability, and had these features enabled by
default. Similarly, LangChain's purpose is to return "smarter" answers to
questions using "Cypher" as a tool to improve the quality of the responses.
Unfortunately, this functionality is also enabled by default, posing
significant risks.
Thanks,
Liad
בתאריך יום ה׳, 21 בנוב׳ 2024 ב-1:41 מאת Jon @.***
>:

I’m not sure I follow your analogy.
The analogy is that an api from one project is created to be used in an
open ended way by another project.
LangChain doesn’t accept prompts directly from the network by default, but
it is almost always integrated into APIs or applications that do.
Would that not be a problem with the use of langchain as opposed to
langchain itself?
—
Reply to this email directly, view it on GitHub
https://github.com/github/advisory-database/pull/5025#issuecomment-2489762250,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AOF3AD3VOJZCDMGXIXW7ZKL2BUMZLAVCNFSM6AAAAABSFLFQQWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDIOBZG43DEMRVGA
.
You are receiving this because you authored the thread.Message ID:
@.***>

I'm not seeing evidence that convinces me to change the cvss so I am not accepting this PR. We believe huntr did an appropriate job scoring this vulnerability and we would advise you to reach out to applications using langchain inappropriately in order to help secure them.

I really not sure about what evidence are you trying to find. It is what it
is.
Langchain has business objective to have as lowest CVSS score.
You claim you “trust” huntr for scoring correctly but in fact and it’s not
debatable about availability, integrity and complexity.
Is this complex to exploit? No, so how complexity is high?
Is this vulnerability can delete or modify the data in the database? Yes,
so how its Low?
Furthermore you did not approach any of my questions and you don’t explain
why you think differently.
I did not score the NVD and they scored it as 9.8 not me.
Anyways, I may release this thread to the public to hear their thoughts
about it.
Liad
בתאריך יום ה׳, 21 בנוב׳ 2024 ב-20:16 מאת Jon @.***>:

I'm not seeing evidence that convinces me to change the cvss so I am not
accepting this PR. We believe huntr did an appropriate job scoring this
vulnerability and we would advise you to reach out to applications using
langchain inappropriately in order to help secure them.
—
Reply to this email directly, view it on GitHub
https://github.com/github/advisory-database/pull/5025#issuecomment-2491949782,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AOF3AD6XRXKIXMWDMM7B5YT2BYPQPAVCNFSM6AAAAABSFLFQQWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDIOJRHE2DSNZYGI
.
You are receiving this because you authored the thread.Message ID:
@.***>


Echo at the end of each recording.

Hi there,
I'm doing some training on my own data, got up to around 120k steps, but at the end of each sentence I synthesise the sentence continually echo. Has anybody come across this and found a solution?
Thanks

+1.
I've cut all the silence from the end (even sacrificing some sound sometimes) and am using attention from https://github.com/keithito/tacotron/blob/tacotron2-work-in-progress/models/attention.py as @keithito suggested, but it doesn't help.

Yeah, i'm having this problem too. The audio keeps repeating the last couple of words.
eval-69000-2.zip

I'm having same problem. The synthesized audio keep echoing. How can I trim it?

What's about the alignment? IMHO. I think tacotron has still tried to learn how to stop the sequence by the "\n" characters. Maybe your dataset is not large enough to get Tacotron detect whether the end of the speech?

@NTT123 Has adding silence solved the problem with echo in your case? I also tried adding 1sec of silence at the end of each training sample, bit it didn't work for me.

@Quadraaa It works for my dataset (7 hours Vietnamese voice). Adding 1 sec silence forces the network to learn to generate a long silence after the end of stream symbol ~.
You should listen to logs/tacotron/step-audio.wav files. If the network trained correctly, it should be able to generate 1 sec silences at the end of the audio.

@NTT123 Thanks for the info.
Maybe the problem is that my data is not of a very high quality. The length is about 15 hours. If I add 1sec silence the echo effect gets less (although it still exists), but the model starts to generate noise instead. So if I cut all the silence, I get echo with very little noise sometimes, and when I cut all the silence and then add 1 sec of pure silence, I get echo + noise. Going to try a different datasetof a larger size. I also noticed that the speaker in the recording I am using usually makes very long pauses between words. It may be contributing to the problem, I suppouse. Usually the generation stops mistakenly after a comma.
I listened to logs/tacotron/step-audio.wav files, the silence at the end is generated.

@Quadraaa, I also though that your problem is the long silences in your training samples. I personally used pydub to spit the audio files into audio segments of no longer 500 ms silences.

@jlin816 That's probably because it doesn't have the gate. Can you also share your dataset?

Sure, here are the synthesized samples after 78.9k iterations. Admittedly my task is a little unconventional -- I'm trying to synthesize with phonemic/anatomical parameters rather than text, but it has been working surprisingly well aside from the echo.
eval-78900.zip

In my many tests, I have found that the more steps it trains, the larger probability the ending echoes would happen. I am afraid there should be something to be adjusted in the attention model. @keithito

Oh, that's awesome! I'll definitely try it out. :-)

@rafaelvalle What parameters are there related to the distribution of words per second of your dataset ?

@keithito I don't know why tacotron model don't need padding in synthesize.py?


refactor(etag): simplify cloning logic

If the upstream response doesn't include an ETag header, the ETag middleware needs to clone the response so it can read the body to compute an ETag. This commit simplifies the management of the original and cloned responses.

Hi @jamesarosen !
Looks good! One thing, could you do yarn denoify and git add&commit&push the generated file?

Hi @jamesarosen !
Thanks!


autoOpenBrowser config opens wrong address

autoOpenBrowser brought over from Vue's webpack template is set to open the dev server address, not Craft project's address.

@mildlygeeky

Thanks!


Archive page breaks

In the artist-three chapter, the 2nd page is dated Feb 8, 2024.

If I add another page in artist -two chapter, and date it Feb 9, 2024, the archive page will break.

Thanks for sharing your mini Hugo Webcomic theme.

Hello! This is expected behaviour as pages are placed in order of earliest to latest date, by default.
If you would like to display pages in some other order, place a weight field in the frontmatter of each comic page .md file. For example, in content/comic/artist-one/1.md:
+++
weight = 10
date = 2023-12-01T00:00:00
+++

Pages with higher weight will be displayed first. Negative weights are allowed. If a page lacks a weight field, it will be displayed before the pages that do have a weight field.
I hope this helps!

Thank you so much.


Fix bug for restaring job

fix bugs when job's name is like this:
Before:
a.1/a ==>a.2
Now:
a.1/a ==>a.1/a.1

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you all sign our Contributor License Agreement before we can accept your contribution.1 out of 2 committers have signed the CLA.:white_check_mark: chengshifan:x: I517992I517992 seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.You have signed the CLA already but the status is still pending? Let us recheck it.


Wrong resolution

When I try to download a movie it downloads to me in 480p resolution despite specifying 1080p. I tried download movie manualy, and 1080p has exist.
https://prnt.sc/MxF-a8FKO02e
https://prnt.sc/WuaXMYOKYBwA
https://prnt.sc/vvGUvzMyMVh6
My manual download
https://prnt.sc/Mm5nKxrukxqt

@eryczkekamyczke Thanks for raising an issue! I checked and indeed there was a bug where the specified resolution was ignored and the default resolution for a video would be used. I already fixed that in #5 and should be working now.
You can run pip install cda-dl -U to get the latest version of the program.


Enable support for MonitoringRoleARN

Currently, MonitoringRoleARN is not supported in eb-create-environment. And RDS creation will fail if MonitoringInterval is set to anything other than 0 due to missing MonitoringRoleARN.


Rename of the original database

Step 3, rename the original database, fails with this information:
Msg 5030, Level 16, State 2, Line 1
The database could not be exclusively locked to perform the operation.
Completion time: 2020-11-10T09:25:20.6979855+00:00
one way to do is:
ALTER DATABASE <original Dynamics 365 database> SET SINGLE_USER WITH ROLLBACK IMMEDIATE;
ALTER DATABASE <original Dynamics 365 database> MODIFY NAME = <original Dynamics 365 database>_ORIG
Also be aware that renaming the database does not rename the files of the database.

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: fe0d2c68-08ea-77b8-af74-cd889a8344ca
Version Independent ID: d88b6646-49de-f7eb-3d7c-7d1e700131e1
Content: Upgrade data in development or demo environments - Finance & Operations | Dynamics 365
Content Source: articles/fin-ops-core/dev-itpro/migration-upgrade/upgrade-data-to-latest-update.md
Service: dynamics-ax-platform
Product: ****
Technology: ****
GitHub Login: @laneswenka
Microsoft Alias: laswenka

@rabol, thanks for the feedback.
@laneswenka, please review.


Background-color: transparent missing

Should be in skins? We declare the transparent variable but don't use it. (May be useful to reset background color.)

This has been fixed in master :)


issue #106 MPII Human Pose Dataset upload example

[x] Visible on app.activeloopai.com
[x] Tested.

@sanchitvj it is a linting error, please check for more details https://github.com/activeloopai/Hub/pull/168/checks?check_run_id=1337803484
Please see linting parameters at https://github.com/activeloopai/Hub/blob/master/CONTRIBUTING.md#formatting-and-linting if you use vscode you can just copy it.

I've merged to master. Good job @sanchitvj!


Silence ply errors

Running slimit on cygwin produces several warnings each time it is run
>>> import slimit
s>>> slimit.minify("")
WARNING: Couldn't write lextab module <module 'slimit.lextab' from '/usr/lib/python3.6/site-packages/slimit/lextab.py'>. Won't overwrite existing lextab module
WARNING: yacc table file version is out of date
WARNING: Token 'LINE_COMMENT' defined, but not used
WARNING: Token 'BLOCK_COMMENT' defined, but not used
WARNING: Token 'LINE_TERMINATOR' defined, but not used
WARNING: Token 'CLASS' defined, but not used
WARNING: Token 'CONST' defined, but not used
WARNING: Token 'ENUM' defined, but not used
WARNING: Token 'EXPORT' defined, but not used
WARNING: Token 'EXTENDS' defined, but not used
WARNING: Token 'IMPORT' defined, but not used
WARNING: Token 'SUPER' defined, but not used
WARNING: There are 10 unused tokens
WARNING: Couldn't create <module 'slimit.yacctab' from '/usr/lib/python3.6/site-packages/slimit/yacctab.py'>. Won't overwrite existing tabmodule
''

Using ply v 3.10.  Only fix for me appears to be to revert to ply 3.4

I get the same verbose dreck spewed out to stderr.  This exceedingly ugly one-liner anywhere after import slimit, but before calling minify() silences the logging:
slimit.lexer.ply.lex.PlyLogger =  \
slimit.parser.ply.yacc.PlyLogger = \
  type('_NullLogger', (slimit.lexer.ply.lex.NullLogger,),
       dict(__init__=lambda s, *_, **__: (None, s.super().__init__())[0]))

This works for me in Python 3.6 with slimit 0.8.1 and ply 3.11 -- maybe others, but YMMV.
All this does is monkey-patches the PlyLogger class with the NullLogger class the ply package defines itself, adapting for the differences in initializer signatures between the two classes (shame, shame).  If ply has a configuration setting or optional initializer parameter somewhere that effectively does this -- and it should -- I couldn't find it.  (Hint, hint, ply maintainers.)  Maybe in lieu of that, slimit should do this internally instead of putting the onus on the user?

@rod-app The problem actually goes deeper than that - if those messages are generated every time minify is called, it means that the ply tab modules are being regenerated (which takes as long as a second), and if there are a number of JavaScript files being processed that extra delay and thus performance hit to the program will accumulate rather quickly.  Removing the message simply hides the problem but not actually fixing it - the only way to fix it is to manually remove the problematic tab files and regenerate them correct as I had suggested.
The fork that I made (calmjs.parse) does not track the tab files for the source repository, but they are package/generated for every supported (and released) ply versions, such that they are not needlessly being regenerated for the end-users, and in the case a newer version of ply is out there is a specific command (python -m calmjs.parse.parsers.optimize) with the reasoning behind it explained in the README for the package.
Also please note that slimit has not received a new release for nearly 6 years now, so I made that fork as an attempt to rectify the situation (the slimit minify equivalent is available via from calmjs.parse import es5 and then call es5.minify_print).

Thanks for the response, Tommy.  I integrated calmjs into my app,
substituting for slimit, and everything works fine.  You were right --
slimit' had been shockingly (unacceptably) slow on account of needing to regenerate the tab files each request.  I haven't benchmarked anything, but calmjs` is noticeably faster.
There are a number of out-and-out wrong Python JS minifiers out there;
yours is a keeper.  Excellent work!
Rod Pullmann   Appion, Inc.
(303) 589-4405
On Sat, Feb 16, 2019 at 5:27 PM Tommy Yu<EMAIL_ADDRESS>wrote:

@rod-app https://github.com/rod-app The problem actually goes deeper
than that - if those messages are generated every time minify is
called, it means that the ply tab modules are being regenerated (which
takes as long as a second), and if there are a number of JavaScript files
being processed that extra delay and thus performance hit to the program
will accumulate rather quickly. Removing the message simply hides the
problem but not actually fixing it - the only way to fix it is to manually
remove the problematic tab files and regenerate them correct as I had
suggested.
The fork that I made (calmjs.parse
https://github.com/calmjs/calmjs.parse) does not track the tab files
for the source repository, but they are package/generated for every
supported (and released) ply versions, such that they are not needlessly
being regenerated for the end-users, and in the case a newer version of ply
is out there is a specific command (python -m
calmjs.parse.parsers.optimize) with the reasoning behind it explained in
the README for the package.
Also please note that slimit has not received a new release for nearly 6
years now, so I made that fork as an attempt to rectify the situation (the
slimit minify equivalent is available via from calmjs.parse import es5
and then call es5.minify_print).
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/rspivak/slimit/issues/97#issuecomment-464402589, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AlQiEx4neYv6BZxKj4OPQl0ah7ERsrmVks5vOKHdgaJpZM4RghW4
.

--

This message may contain privileged
or confidential information for the sole use of the intended  recipient.
Any review or distribution by others is strictly prohibited.  If you are
not the intended recipient of this message, you may not make use of, or
rely in any way on this information.  You should immediately notify the
sender by reply email and destroy this message.  Please advise us
immediately if you or your employer do not consent to Internet email for
messages of this kind.


LFQ, TMT and DIA datasets to be benchmark

LFQ dataset to be benchmark https://www.sciencedirect.com/science/article/pii/S1535947620333107
Dataset: https://www.ebi.ac.uk/pride/archive/projects/PXD000279

This dataset benchmark LFQ, TMT and DIA in the same sample:
https://pubs.acs.org/doi/10.1021/acsomega.0c04030


Fix for backwards-incompatible Mistral API change

The latest version of the Mistral SDK contains backward-incompatible API changes. This updates Pixeltable for compatibility

This change is


ic-certified-map release 0.2.0 not documented in the CHANGELOG.md

See: https://github.com/dfinity/cdk-rs/blob/main/src/ic-certified-map/CHANGELOG.md
But it is certainly out in the wild: https://docs.rs/ic-certified-map/0.2.0/ic_certified_map
The [Unreleased] section is touched by https://github.com/dfinity/cdk-rs/commit/2112e912e156b271389a51777680de542bb43980, which is post-0.2.0.
As a side-request, can we have a new release from main? dfinity/ic won't build with "0.2.0" as some trait derivations are missing.

dfinity/internet-identity also requires a newer release than "0.2.0".

@eric-swanson @roman-kashitsyn can you cut a release or get in touch with the relevant people? Thanks!


arm-trusted-firmware: set DEBUG and LOG_LEVEL from bitbake

this allows ability to modify these in other layers if needed

Similar to https://github.com/OE4T/meta-tegra/pull/1699; will apply to Jetpack 5 branches: kirkstone and scarthgap-l4t-r35.x


Sending commands via RS485 fails

Hi,
I use the following board in order to communicate with the SoyoSource: Link
However, the connector is shown as not connected and only the TXD LED of the board flashes:

Is there a chance that I did a mistake?
Thanks in advance
Jan

Which Soyosource model do you own? Could you provide the color of the mainboard, too. It's the WiFi version, correct? This device doesn't respond to RS485 messages. Flashing of the TX LED only is fine here.
Do you own the original limiter clamp? Please connect the clamp to your Soyosource and check the limiter connected binary sensor again. Is your device able to receive power demand frames in general?

I have a 1000W WiFi version with purple mainboard. Unfortunately I cannot check using the original limiter at the moment as I soldered it to the RS485 communication module. I will try to build a separate cable for testing.
Thank you so far.

I built a new cable, but I was not aware that I need to connect the limiter to the grid (which is something that I will not do).
I attached a video, just to confirm that we talk about the same thing when we refer to "flashing LED".
https://github.com/syssi/esphome-soyosource-gtn-virtual-meter/assets/52739230/8257cbca-9568-44b4-bc86-81d651720238

Lol. Good catch! This isn't the LED I was talking about. The RS485 converter has a RX and TX LED. The TXD one should flash. May be your ESP is constantly crashing. Please take look at the log output of the serial interface.

But the right one is my converter (the one that I mentioned in my initial post). And the LED on this board/converter is labeled "TXD". Do I miss something? :-/

I wasn't awake this morning and it looks like I was confused from the flashing of your ESP. Your RS485 converter blinks too and this is important because it indicates the outgoing traffic of your ESP. Do you have to chance to attach a second RS485 converter and ESP to retrieve he current setup and dump the incoming traffic of the other side? I could provide a YAML to dump the traffic.

I am a little bit torn now.

Most probably I will go for a simpler solution where I will run on constant power.
On the other hand: This sounds so cool ^^

Out of curiosity, I would like to run this experiment in case you are free (I don't want to block you from doing something more important). And it will take some time as I will need to order some ESP32s from China :-)

The experiment doesn't cost me much effort. Please use this YAML for the receiving ESP: https://github.com/syssi/esphome-soyosource-gtn-virtual-meter/blob/main/tests/esp8266-limiter-rx.yaml
The setup should look like this:
ESP1 <--RX/TX--> RS485 converter1 <--A/B--> RS485 converter2 <--RX/TX--> ESP2

The ESP1 will publish the power demand periodically. The TX LED of the "RS485 converter1" should blink periodically. On the second RS485 converter the RX LED should blink periodically and the received frame should be printed to the log.

It turned out that the wires at the RS485 plug were swapped in my case. Now things work out perfectly.
Thanks for your great documentation!


bug: Triage end2end tests failing consistently

Describe the bug
During my recent work on local dev setup, the end2end tests consistently failing on several tests (see below trace):
========== ./gradlew testEnd2End trace excerpt ================
Polling for ReportStream results.  (Max poll time 480 seconds)
Test end2end finished in 510 seconds
Test passed: for ignore.CSV action receive:  Expecting 5 item lineage records and got 5
Test passed: for ignore.CSV action batch:  Expecting 5 item lineage records and got 5
*** TEST FAILED*** for ignore.CSV action send:  Expecting 5 item lineage records but got 0
Test passed: for ignore.HL7 action receive:  Expecting 5 item lineage records and got 5
Test passed: for ignore.HL7 action batch:  Expecting 5 item lineage records and got 5
*** TEST FAILED*** for ignore.HL7 action send:  Expecting 5 item lineage records but got 0
Test passed: for ignore.HL7_BATCH action receive:  Expecting 5 item lineage records and got 5
Test passed: for ignore.HL7_BATCH action batch:  Expecting 5 item lineage records and got 5
*** TEST FAILED*** for ignore.HL7_BATCH action send:  Expecting 5 item lineage records but got 0
Test passed: for ignore.HL7_NULL action receive:  Expecting 5 item lineage records and got 5
Test passed: for ignore.HL7_NULL action batch:  Expecting 5 item lineage records and got 5
*** Tests FAILED:  end2end ***

Task :primeCLI FAILED

FAILURE: Build failed with an exception.

What went wrong:
Execution failed for task ':primeCLI'.

Process 'command '/usr/lib/jvm/java-11-openjdk-amd64/bin/java'' finished with non-zero exit value 1

Try:

Run with --stacktrace option to get the stack trace.
Run with --info or --debug option to get more log output.
Run with --scan to get full insights.

Get more help at https://help.gradle.org

BUILD FAILED in 9m 4s
6 actionable tasks: 2 executed, 4 up-to-date
=================== end trace excerpt ===============
Impact on ReportStream
Need to find out the root cause of the 3 tests, fix if they are cause by any recent changes
Steps to reproduce
Steps to reproduce the behavior:

Go to report stream local repo
Setup a local dev report stream instance by following : https://github.com/CDCgov/prime-reportstream/blob/master/prime-router/docs/getting-started/getting-started.md
After ./cleanslate.sh successfully finished, check report stream and supporting services are up and running
Might need to run ./gradlew reloadTables and ./gradlew reloadSetting to avoid tests termination due to schema loading error
run ./gradlew testEnd2End

then should be able to see the test failures.
Expected behavior
A clean run of end2end tests with all tests passing
Resources
None
Logs
See stdout in first section
Device info
Desktop (please complete the following information)

OS: Mac, WSL2, Linux
Browser NA
Version NA

Smartphone (please complete the following information)

Device: [e.g. iPhone6]
OS: [e.g. iOS8.1]
Browser [e.g. stock browser, safari]
Version [e.g. 22]

Additional context
Add any other historical context about the problem here.

@JFU-NAVA-PBC Please confirm that this is ready for grooming.

@bishoyayoub yes

@JFU-NAVA-PBC Please use #4932 to use the terminology "As a [User Persona - who are we building this for?]
I want to [Intent - what is this user trying to achieve?],
so that [Outcome - what is the value add to the user]."

@bishoyayoub I used the bug template since the test failure could be due to my local setup, or it could be a real problem.

@bishoyayoub @arnejduranovic After going through the "Dev get started" docs, I noticed that this is false alarm.
Fixed the SFTP permission stuff, and all smoke tests passed.
I'll close the ticket


Succeed when unloading namespace bundles not owned by any broker

Motivation
As explained in #707, there are currently 500 Server Error reported when unloading a namespace bundle which is not owned by any broker.
The correct behavior should be to ignore bundles which are not loaded.

Updated

LGTM.. just a minor comment if we want to change it. 👍

retest this please


python38: fix build on macOS

Motivation for this change
Python 3.8 fails to build on macOS for two reasons:

python-3.x-distutils-C++.patch fails to apply cleanly.

An #include for <util.h> is missing, causing a build failure:
./Modules/posixmodule.c:6586:9: error: implicit declaration of function 'openpty' is invalid in C99
if (openpty(&master_fd, &slave_fd, NULL, NULL, NULL) != 0)
^

Things done

[ ] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS)
Built on platform(s)

[ ] NixOS
[x] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nix-review --run "nix-review wip"
[x] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Ensured that relevant documentation is up to date
[x] Fits CONTRIBUTING.md.

Notify maintainers
cc @fridh

@grahamcofborg build python38


Do not bundle JSX syntax

The JSX syntax can be pulled from https://github.com/reactjs/sublime-react.
Installing both creates duplicates:

Hey @STRML, we've just released https://github.com/6to5/6to5-sublime as 6to5 in Package Control. It shows the syntax name as "JavaScript JSX" - without parens, but we're going to change the name soon. It works with SublimeLinter-jsxhint already since Sublime identifies it as javascript_jsx, and you've got it already listed in the syntax list.
How do you feel about removing the existing syntax, in favor of linking to ours? We have proper ES6 and JSX support. This way we don't confuse users. (Ugh this sentence reads so shady - it's not meant to be - sorry)


Local file JPG support

I'm trying to load a JPG from a local directory (C:\xxx\xxxx) but when I change the "url:" to
"url: 'file:\\C:/xxx/xxx/yyy.jpg'",  it fails to load the JPG file and the Browser I'm using will load it if I type "file:\\C:/xxx/xxx/yyy.jpg" in the url address bar.
OpenSeadragon({
...
tileSources: {
type: 'image',
url:  '/example-images/grand-canyon-landscape-overlooking.jpg',
buildPyramid: false
}
...
});

Is it just the backslash? Try \\ instead of \

It's actually "file:///c:\xxx\xxx\yyy.jpg",   not "file:\......,  mis-typed it.
The code actually has "\" instead of "",   I've also tried changing all of the "\" to "/".
Here's what the HTM file contains:

Hi, I think you could have a look at this page (http://openseadragon.github.io/docs/). At the end of it, it says
"If you are working directly from the file system (accessing your web page from file:///path/to/your/file.htm) you may need to change your browser's local files security policy so that your zooming image data can be loaded. Alternatively, you can run a local server. You can find help on both methods in three.js documentation."
And you may find some useful information about osd with local file.
Hope it will help you.

I looked at the information,  but the browser allows for the JPG to load if I type the same string into the url address bar.  It's only from openseadragon that the image will not load.
So I believe it's how openseadragon is processing the url or local file string.

Yes, OpenSeadragon draws the images onto a canvas, and there are stricter security rules around doing that. If you don't want the smoothness of Canvas, you can include useCanvas: false in your options when you create your viewer; that may help with this issue.

OK, I will give that try.  Thanks.

Using  useCanvas: false   did not help.  Same issue.
It turns out the JPG files that will be accessed is on a remote server,  so I tested setting up a local Web Server on it and was able to access the JPGs using a http:.... url.
On a side note, on the local server I was able to access the JPGs if the files were located under the
local Web server folder and used the http path to it vs file:///.....   I was hoping to give the user  the option of storing file anywhere locally.

There may browser-dependent ways to override security policy to allow reading local files, but in general it’s not allowed except for user action (click) and the File API, which isn’t going to work for the image tiles

On a side note:   Is there a cache used by OpenSeaDragon?  I've seen it when the JPG I'm trying to load doesn't but display the previous JPG,  although the HTML called contains a different JPG name.  I tried adding code to the HTML to turn off browser caching.  If OpenSeaDragon has a cache how can it be turned off?   The Canvas is turned off.

Are you talking about when the page refreshes, or when you change things while the page is still running?

When the page refreshes,  when I load a new HTML which opens the OpenSeaDragon viewier with a new JPG.

OpenSeadragon doesn't do any sort of local caching that would survive a refresh. I'm not sure what would be causing the issue you're seeing.

Possible that the server of the tiles has a cache or unchanging etag header?
Either way, for development, one can always open development tool in
Chrome/FF, and check the box "disable cache" under "network".
Or use an incognito window, which should also ignore caches.
On Mon, 16 Sep. 2019, 19:29 Ian Gilman<EMAIL_ADDRESS>wrote:

OpenSeadragon doesn't do any sort of local caching that would survive a
refresh. I'm not sure what would be causing the issue you're seeing.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/openseadragon/openseadragon/issues/1706?email_source=notifications&email_token=AET34F5KGOL3UVOG6VF3PULQJ67AVA5CNFSM4ITKYJDKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD6Z42KQ#issuecomment-531877162,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AET34F4JJIF766COCVTBBTDQJ67AVANCNFSM4ITKYJDA
.