python311Packages.pyvex: 9.2.84 -> 9.2.90

Automatic update generated by nixpkgs-update tools. This update was made based on information from passthru.updateScript.
meta.description for python311Packages.pyvex is: Python interface to libVEX and VEX IR
meta.homepage for python311Packages.pyvex is: https://github.com/angr/pyvex
Updates performed

Ran passthru.UpdateScript

To inspect upstream changes
Impact
Checks done

built on NixOS
The tests defined in passthru.tests, if any, passed
found 9.2.86 with grep in /nix/store/sccd8hybw3qsx1apkj7k312m2ykygkdb-python3.11-pyvex-9.2.86
found 9.2.86 in filename of file in /nix/store/sccd8hybw3qsx1apkj7k312m2ykygkdb-python3.11-pyvex-9.2.86

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

8 total rebuild path(s)

8 package rebuild(s)

First fifty rebuilds by attrpath
python311Packages.ailment
python311Packages.angr
python311Packages.angrcli
python311Packages.angrop
python311Packages.cle
python311Packages.pyvex
python312Packages.ailment
python312Packages.pyvex

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/sccd8hybw3qsx1apkj7k312m2ykygkdb-python3.11-pyvex-9.2.86 \
  --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 python311Packages.pyvex https://github.com/r-ryantm/nixpkgs/archive/7433e5bbd7b26ca696e245edbbaa804778bbe7be.tar.gz

Or:
nix build github:r-ryantm/nixpkgs/7433e5bbd7b26ca696e245edbbaa804778bbe7be#python311Packages.pyvex

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/sccd8hybw3qsx1apkj7k312m2ykygkdb-python3.11-pyvex-9.2.86
ls -la /nix/store/sccd8hybw3qsx1apkj7k312m2ykygkdb-python3.11-pyvex-9.2.86/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

4 packages failed to build:

python311Packages.angr
python311Packages.angrcli
python311Packages.angrop
python311Packages.cle

4 packages built:

python311Packages.ailment
python311Packages.pyvex
python312Packages.ailment
python312Packages.pyvex

Maintainer pings
cc @fabaff for testing.

Automatic update generated by nixpkgs-update tools. This update was made based on information from passthru.updateScript.
meta.description for python311Packages.pyvex is: Python interface to libVEX and VEX IR
meta.homepage for python311Packages.pyvex is: https://github.com/angr/pyvex
Updates performed

Ran passthru.UpdateScript

To inspect upstream changes
Impact
Checks done

built on NixOS
The tests defined in passthru.tests, if any, passed
found 9.2.87 with grep in /nix/store/vk7fay98nizjvlmj8amywm3zfazc24ca-python3.11-pyvex-9.2.87
found 9.2.87 in filename of file in /nix/store/vk7fay98nizjvlmj8amywm3zfazc24ca-python3.11-pyvex-9.2.87

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

8 total rebuild path(s)

8 package rebuild(s)

First fifty rebuilds by attrpath
python311Packages.ailment
python311Packages.angr
python311Packages.angrcli
python311Packages.angrop
python311Packages.cle
python311Packages.pyvex
python312Packages.ailment
python312Packages.pyvex

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/vk7fay98nizjvlmj8amywm3zfazc24ca-python3.11-pyvex-9.2.87 \
  --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 python311Packages.pyvex https://github.com/r-ryantm/nixpkgs/archive/8fe7ee5d4ba6195de3a546e0ccf0bce055999a69.tar.gz

Or:
nix build github:r-ryantm/nixpkgs/8fe7ee5d4ba6195de3a546e0ccf0bce055999a69#python311Packages.pyvex

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/vk7fay98nizjvlmj8amywm3zfazc24ca-python3.11-pyvex-9.2.87
ls -la /nix/store/vk7fay98nizjvlmj8amywm3zfazc24ca-python3.11-pyvex-9.2.87/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

8 packages failed to build:

python311Packages.angr
python311Packages.angr.dist
python311Packages.angrcli
python311Packages.angrcli.dist
python311Packages.angrop
python311Packages.angrop.dist
python311Packages.cle
python311Packages.cle.dist

8 packages built:

python311Packages.ailment
python311Packages.ailment.dist
python311Packages.pyvex
python311Packages.pyvex.dist
python312Packages.ailment
python312Packages.ailment.dist
python312Packages.pyvex
python312Packages.pyvex.dist

Maintainer pings
cc @fabaff for testing.

Automatic update generated by nixpkgs-update tools. This update was made based on information from passthru.updateScript.
meta.description for python311Packages.pyvex is: Python interface to libVEX and VEX IR
meta.homepage for python311Packages.pyvex is: https://github.com/angr/pyvex
Updates performed

Ran passthru.UpdateScript

To inspect upstream changes
Impact
Checks done

built on NixOS
The tests defined in passthru.tests, if any, passed
found 9.2.89 with grep in /nix/store/0jw4q2azc6g32n93wzbgnkz1wqphli39-python3.11-pyvex-9.2.89
found 9.2.89 in filename of file in /nix/store/0jw4q2azc6g32n93wzbgnkz1wqphli39-python3.11-pyvex-9.2.89

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

8 total rebuild path(s)

8 package rebuild(s)

First fifty rebuilds by attrpath
python311Packages.ailment
python311Packages.angr
python311Packages.angrcli
python311Packages.angrop
python311Packages.cle
python311Packages.pyvex
python312Packages.ailment
python312Packages.pyvex

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/0jw4q2azc6g32n93wzbgnkz1wqphli39-python3.11-pyvex-9.2.89 \
  --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 python311Packages.pyvex https://github.com/r-ryantm/nixpkgs/archive/e335ec600079b3aa01cb0922bcf8ca27aef4c7cf.tar.gz

Or:
nix build github:r-ryantm/nixpkgs/e335ec600079b3aa01cb0922bcf8ca27aef4c7cf#python311Packages.pyvex

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/0jw4q2azc6g32n93wzbgnkz1wqphli39-python3.11-pyvex-9.2.89
ls -la /nix/store/0jw4q2azc6g32n93wzbgnkz1wqphli39-python3.11-pyvex-9.2.89/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

4 packages failed to build:

python311Packages.angr
python311Packages.angrcli
python311Packages.angrop
python311Packages.cle

4 packages built:

python311Packages.ailment
python311Packages.pyvex
python312Packages.ailment
python312Packages.pyvex

Maintainer pings
cc @fabaff for testing.

Automatic update generated by nixpkgs-update tools. This update was made based on information from passthru.updateScript.
meta.description for python311Packages.pyvex is: Python interface to libVEX and VEX IR
meta.homepage for python311Packages.pyvex is: https://github.com/angr/pyvex
Updates performed

Ran passthru.UpdateScript

To inspect upstream changes
Impact
Checks done

built on NixOS
The tests defined in passthru.tests, if any, passed
found 9.2.90 with grep in /nix/store/05jws10yxvn4jycpyv4q6kzcnnljxnv6-python3.11-pyvex-9.2.90
found 9.2.90 in filename of file in /nix/store/05jws10yxvn4jycpyv4q6kzcnnljxnv6-python3.11-pyvex-9.2.90

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

8 total rebuild path(s)

8 package rebuild(s)

First fifty rebuilds by attrpath
python311Packages.ailment
python311Packages.angr
python311Packages.angrcli
python311Packages.angrop
python311Packages.cle
python311Packages.pyvex
python312Packages.ailment
python312Packages.pyvex

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/05jws10yxvn4jycpyv4q6kzcnnljxnv6-python3.11-pyvex-9.2.90 \
  --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 python311Packages.pyvex https://github.com/r-ryantm/nixpkgs/archive/f61435d406042b48e59900f21e9e2655644958ed.tar.gz

Or:
nix build github:r-ryantm/nixpkgs/f61435d406042b48e59900f21e9e2655644958ed#python311Packages.pyvex

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/05jws10yxvn4jycpyv4q6kzcnnljxnv6-python3.11-pyvex-9.2.90
ls -la /nix/store/05jws10yxvn4jycpyv4q6kzcnnljxnv6-python3.11-pyvex-9.2.90/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

4 packages failed to build:

python311Packages.angr
python311Packages.angrcli
python311Packages.angrop
python311Packages.cle

4 packages built:

python311Packages.ailment
python311Packages.pyvex
python312Packages.ailment
python312Packages.pyvex

Maintainer pings
cc @fabaff for testing.

Automatic update generated by nixpkgs-update tools. This update was made based on information from passthru.updateScript.
meta.description for python311Packages.pyvex is: Python interface to libVEX and VEX IR
meta.homepage for python311Packages.pyvex is: https://github.com/angr/pyvex
Updates performed

Ran passthru.UpdateScript

To inspect upstream changes
Impact
Checks done

built on NixOS
The tests defined in passthru.tests, if any, passed
found 9.2.91 with grep in /nix/store/iyggg6k10k018558hcxw2izsxlgjqky1-python3.11-pyvex-9.2.91
found 9.2.91 in filename of file in /nix/store/iyggg6k10k018558hcxw2izsxlgjqky1-python3.11-pyvex-9.2.91

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

8 total rebuild path(s)

8 package rebuild(s)

First fifty rebuilds by attrpath
python311Packages.ailment
python311Packages.angr
python311Packages.angrcli
python311Packages.angrop
python311Packages.cle
python311Packages.pyvex
python312Packages.ailment
python312Packages.pyvex

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/iyggg6k10k018558hcxw2izsxlgjqky1-python3.11-pyvex-9.2.91 \
  --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 python311Packages.pyvex https://github.com/r-ryantm/nixpkgs/archive/cc172e39f10ed966080913bd14b6091f6fa45e9d.tar.gz

Or:
nix build github:r-ryantm/nixpkgs/cc172e39f10ed966080913bd14b6091f6fa45e9d#python311Packages.pyvex

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/iyggg6k10k018558hcxw2izsxlgjqky1-python3.11-pyvex-9.2.91
ls -la /nix/store/iyggg6k10k018558hcxw2izsxlgjqky1-python3.11-pyvex-9.2.91/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

4 packages failed to build:

python311Packages.angr
python311Packages.angrcli
python311Packages.angrop
python311Packages.cle

4 packages built:

python311Packages.ailment
python311Packages.pyvex
python312Packages.ailment
python312Packages.pyvex

Maintainer pings
cc @fabaff for testing.

Automatic update generated by nixpkgs-update tools. This update was made based on information from passthru.updateScript.
meta.description for python311Packages.pyvex is: Python interface to libVEX and VEX IR
meta.homepage for python311Packages.pyvex is: https://github.com/angr/pyvex
Updates performed

Ran passthru.UpdateScript

To inspect upstream changes
Impact
Checks done

built on NixOS
The tests defined in passthru.tests, if any, passed
found 9.2.92 with grep in /nix/store/3y1yz8qmgnaad6459p9b0af6ab6zraz0-python3.11-pyvex-9.2.92
found 9.2.92 in filename of file in /nix/store/3y1yz8qmgnaad6459p9b0af6ab6zraz0-python3.11-pyvex-9.2.92

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

8 total rebuild path(s)

8 package rebuild(s)

First fifty rebuilds by attrpath
python311Packages.ailment
python311Packages.angr
python311Packages.angrcli
python311Packages.angrop
python311Packages.cle
python311Packages.pyvex
python312Packages.ailment
python312Packages.pyvex

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/3y1yz8qmgnaad6459p9b0af6ab6zraz0-python3.11-pyvex-9.2.92 \
  --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 python311Packages.pyvex https://github.com/r-ryantm/nixpkgs/archive/cd766bb8bdba89d0e2f127c63adba564fa63c3cb.tar.gz

Or:
nix build github:r-ryantm/nixpkgs/cd766bb8bdba89d0e2f127c63adba564fa63c3cb#python311Packages.pyvex

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/3y1yz8qmgnaad6459p9b0af6ab6zraz0-python3.11-pyvex-9.2.92
ls -la /nix/store/3y1yz8qmgnaad6459p9b0af6ab6zraz0-python3.11-pyvex-9.2.92/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 --extra-nixpkgs-config '{ allowInsecurePredicate = x: true; }' run on x86_64-linux 1

8 packages failed to build:

python311Packages.angr
python311Packages.angr.dist
python311Packages.angrcli
python311Packages.angrcli.dist
python311Packages.angrop
python311Packages.angrop.dist
python311Packages.cle
python311Packages.cle.dist

8 packages built:

python311Packages.ailment
python311Packages.ailment.dist
python311Packages.pyvex
python311Packages.pyvex.dist
python312Packages.ailment
python312Packages.ailment.dist
python312Packages.pyvex
python312Packages.pyvex.dist

Maintainer pings
cc @fabaff for testing.

Automatic update generated by nixpkgs-update tools. This update was made based on information from passthru.updateScript.
meta.description for python311Packages.pyvex is: Python interface to libVEX and VEX IR
meta.homepage for python311Packages.pyvex is: https://github.com/angr/pyvex
Updates performed

Ran passthru.UpdateScript

To inspect upstream changes
Impact
Checks done

built on NixOS
The tests defined in passthru.tests, if any, passed
found 9.2.93 with grep in /nix/store/2drn4wfgxncq69rjjxx7bhq2lh8hcw7v-python3.11-pyvex-9.2.93
found 9.2.93 in filename of file in /nix/store/2drn4wfgxncq69rjjxx7bhq2lh8hcw7v-python3.11-pyvex-9.2.93

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

8 total rebuild path(s)

8 package rebuild(s)

First fifty rebuilds by attrpath
python311Packages.ailment
python311Packages.angr
python311Packages.angrcli
python311Packages.angrop
python311Packages.cle
python311Packages.pyvex
python312Packages.ailment
python312Packages.pyvex

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/2drn4wfgxncq69rjjxx7bhq2lh8hcw7v-python3.11-pyvex-9.2.93 \
  --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 python311Packages.pyvex https://github.com/r-ryantm/nixpkgs/archive/ae7437def2e49f0f0279eacdcb232d15a7516886.tar.gz

Or:
nix build github:r-ryantm/nixpkgs/ae7437def2e49f0f0279eacdcb232d15a7516886#python311Packages.pyvex

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/2drn4wfgxncq69rjjxx7bhq2lh8hcw7v-python3.11-pyvex-9.2.93
ls -la /nix/store/2drn4wfgxncq69rjjxx7bhq2lh8hcw7v-python3.11-pyvex-9.2.93/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 --extra-nixpkgs-config '{ allowInsecurePredicate = x: true; }' run on x86_64-linux 1

8 packages failed to build:

python311Packages.angr
python311Packages.angr.dist
python311Packages.angrcli
python311Packages.angrcli.dist
python311Packages.angrop
python311Packages.angrop.dist
python311Packages.cle
python311Packages.cle.dist

8 packages built:

python311Packages.ailment
python311Packages.ailment.dist
python311Packages.pyvex
python311Packages.pyvex.dist
python312Packages.ailment
python312Packages.ailment.dist
python312Packages.pyvex
python312Packages.pyvex.dist

Maintainer pings
cc @fabaff for testing.


Binary conflicts with CLI Bible program

There's a command-line Bible program called bible-kjv available in Debian's
repositories and the Arch
User Repository, but it installs
its binary as bible, conflicting with this program. Is there any chance this
program's binary could be renamed to bible_gui or something like that to fix
the conflict? Since this is a GUI program that's normally launched from a
desktop entry, it shouldn't be a problem for users to have the binary's name
change.

In progress... next release.

The new updated version has a new app name. Solved.


innerRef is not working - throws React error

innerRef is not working on MenuList component.
Expected Behavior 🤔
innerRef works
Current Behavior 😯
innerRef throws this error:

Warning: Function components cannot be given refs. Attempts to access this ref will fail.

Check the render method of `WithStyles(List)`.
    in List (created by WithStyles(List))
    in WithStyles(List) (created by MenuList)
    in MenuList (created by Popper)
    in ClickAwayListener (created by Popper)
    in div (created by Paper)
    in Paper (created by WithStyles(Paper))
    in WithStyles(Paper) (created by Popper)
    in Transition (created by Grow)
    in Grow (created by WithTheme(Grow))
    in WithTheme(Grow) (created by Popper)
    in div (created by Popper)
    in Portal (created by Popper)
    in Popper (created by WithTheme(Popper))
    in WithTheme(Popper) (created by MenuListComposition)
    in div (created by MenuListComposition)
    in div (created by MenuListComposition)
    in MenuListComposition (created by WithStyles(MenuListComposition))
    in WithStyles(MenuListComposition)

Steps to Reproduce 🕹

Link:https://codesandbox.io/s/9lvnk027op

Click "Toggle menu grow"
Look at the codesandbox console

Context 🔦

I'm trying to access the underlying ul to get access to li elements to build autoscroller to selected one element
Your Environment 🌎

Tech
Version

Material-UI
v3.6.1

React
16.6.3

@sztrzask The innerRef property is applied on the List functional component. The warning is expected. You can use the RootRef component instead.
In the future, #10825 should provide a clean answer.

I tried this as well, and seems like innerRef is not called when passed a function, as can be demonstrated using this code:
<Paper
    innerRef={(node) => console.log('+++', node)}
...
```jsx


eval flavors

Numpy has
numpy.ascontiguousarray
numpy.asfortranarray
currently, in xtensor-blas, we have a view_eval which is morally passing through things that have a raw data interface, but should really behave like numpy.ascontiguousarray or numpy.asfortranarray.
I guess that we could have a
template<layout_type L=XTENSOR_DEFAULT_LAYOUT, class E>
return_type contiguous_eval(E&&)

which would basically behave like numpy.ascontiguousarray by default (if XTENSOR_DEFAULT_LAYOUT is row_major), but could also be called with contiguous_eval<layout_type::column_major>(e); to behave like numpy.asfortranarray.

Moving this upstream in xtensor would allow xtensor-blas to make use of it instead of the view_eval.

The return type would always be

an adaptor for things that have a data interface.
a container otherwise.


a11y: make Select Dialog to be a listbox with options

Description
The PR improves the button role by making the control to appear as a listbox with options which is closer to the control functionality.
Task Item

VSTS 70436

Screenshots

#minor

Updated, thanks for looking into this!


Add Segment to the UI

⚠ Please check that this feature request hasn't been suggested before.

[X] I searched previous Ideas in Discussions didn't find any similar feature requests.
[X] I searched previous Issues didn't find any similar feature requests.

🔖 Feature description
Enable Segment in Superagent UI
📝 Additional Context
No response
Acknowledgements

[X] My issue title is concise and descriptive.
[X] I have searched the existing issues to make sure this feature has not been requested yet.
[X] I have provided enough information for the maintainers to understand and evaluate this request.

Fixed.


adding ability to specify webpack port via env variable or command li…

…ne option to grunt

Coverage increased (+0.02%) to 87.48% when pulling fa004fb2546c8c3e6fcdf429531c4dc3d302b78e on nag-cyan:master into 157d1c50a8dd22fa8f710606edcb327c30a62f76 on cyaninc:master.

Hey @rajan-cyan.  Can you manually bump up the version in package.json, and then I can merge it.  I think this would count as a minor change.

Coverage increased (+0.02%) to 87.48% when pulling 9c920765e614a75c745b0b5c204be27f1b972076 on rajan-cyan:master into 157d1c50a8dd22fa8f710606edcb327c30a62f76 on cyaninc:master.

@rajan-cyan And don't forget the version bump.  @job13er Mentioned that version bumping is a manual process here.

@sophypal
How do I bump the version?

@sophypal
Thanks... version updated.

Coverage increased (+0.02%) to 87.48% when pulling 0d8cf94636f819daee20459ddd360ef67c82517f on rajan-cyan:master into 157d1c50a8dd22fa8f710606edcb327c30a62f76 on cyaninc:master.


Experience Event: should commerce be transaction?

Should we rename the commerce property to transaction?

"commerce" is what has been used by data producers for a few months now.  Not sure we can handle a change at this time.

I get that a change would be inconvenient, but my question is a about the scope of the property: are we planning to restrict this only to commerce (buying goods) or all kinds of transactions (managing subscriptions, memberships, etc.)
If it's the former, we should stay with commerce. If it's the latter, we need to decide if it makes sense to have either both a commerce and a transaction property, and where the line between the two would be, or to expand the scope and name of the commerce property accordingly.
For data producers that are posting data according to a pre-1.0 version of XDM, you might want to consider adapters to re-write the data, but until we've reached 1.0, there can and will be changes. (Unless we agree to change the rules)

transaction is a subset of commerce, the intent of this area is more then a "transaction" so I am much more comfortable with commerce.

Ok.


Directly exported functions wrapping the dynamic import causes issues when run in "parallel"

Bug Report
When wrapping the dynamic import, exporting the function directly and building for CommonJS, the built artifact will contain a var _a outside of the function's scope which will cause issues when importing in "parallel", for example with Promise.all.
🔎 Search Terms
dynamic import, import, hoist, outside scope, var _a
🕗 Version & Regression Information

This is a regression starting from version 4.9.0-dev.20221019 introduced with #49663

⏯ Playground and reproduction link

Reproduction repo enisdenjo/ts-issue-dynamic-import
Playground link with relevant code

💻 Code
// importFn.ts

export async function importFn(path: string) {
  return import(path);
}

The transpiled code will have problems with parallelism, running the following:
// assuming neither module exists
Promise.all(["idontexist-1", "idontexist-2"].map(importFn));

will raise an error: "Cannot find module 'idontexist-2'" while importing idontexist-1.
🙁 Actual behavior
// importFn.js

"use strict";
var _a; // 👈 outside func scope
Object.defineProperty(exports, "__esModule", { value: true });
exports.importFn = void 0;
async function importFn(path) {
    return _a = path, Promise.resolve().then(() => require(_a));
}
exports.importFn = importFn;

🙂 Expected behavior
// importFn.js

"use strict";
Object.defineProperty(exports, "__esModule", { value: true });
exports.importFn = void 0;
async function importFn(path) {
    var _a; // 👈 inside func scope
    return _a = path, Promise.resolve().then(() => require(_a));
}
exports.importFn = importFn;

Duplicate of #51554 and fixed by https://github.com/microsoft/TypeScript/pull/51562


Compilation errors issued for correct lombok annotations

Hi,
I have recently worked on upgrading some libraries in my project, and I faced an issue, where lombok would report compilation errors for correctly applied annotations. There were other problems in the project that had to be fixed, but lombok was simply causing unnecessary noise with these annotations, which made it more difficult to fix errors. Once I chased down and fixed the root cause issues, it worked fine, but initially it looked like something was wrong with lombok itself.
The most common error was related to Builder annotation, and looked like this:
/path/to/SomeClass.java:18: error: cannot find symbol
   public static SomeClass.Builder fromClass(SomeClass someClass) {
                           ^
  symbol:   class Builder
  location: class SomeClass

Thanks and regards,
Marcin

Without more information, I don't have a way to reproduce this problem.

I don't see a way I could create a sample configuration in a reasonable amount of time, since it's also very project dependent. If I do, then I'll let you know, but let's close the issue for now.

Thanks for your quick response.


Some issues in AVS functional self test checklist

Hi AVS team,
AVS SDK 1.7.1
Here are some issues in AVS functional_self-test-checklist_v1.9
Could you have comments ?
Section 5:
case 5.3: It will respond "Savaan is not supported on this device"
Section 8:
case 8.1: Take Device 1 offline by powering down. It's strange that AVS will not show offline after 1 minutes on APP (will wait about 10 minutes), but Echo will be.
case 8.1: other case, Is the DOD support now ?

Hi zeusshang,
We have already run through the checklist and have the SDK certified. We will redo the tests and report the findings.
Thanks
Priya

Hi Zuesshang,
Please see our findings below
Section   5:
case   5.3: It will respond "Savaan is not supported on this device"
Savaan should be enabled for the device type that you are testing. If not this is the expected behavior.
Section   8:
case   8.1: Take Device 1 offline by powering down. It's strange that AVS will not  show offline after 1 minutes on APP (will wait about 10 minutes), but Echo   will be.
Which platform are you seeing this. We tested on Linux and PI and it is immediate. For mac I have seen it stays online but once you refresh app the status changes to offline. This is again not an SDK issue.
case   8.1: other case, Is the DOD support now ?
What is DOD? Could you elaborate on the use case.
Thanks
Priya

Hi @priyagsenthil ,
Sorry for the confused, the DOD is "do not disturb" case. I think "case 8.1" is for this case.
It's because we will go into Amazon Lab, we just want to clarify which is SDK issue, and which cases we can ignore due to server site issue.

Hi @priyagsenthil ,
About case 8.1 the offline will be detected by APP for 10 minutes, I ever raised this case at #616 , and it said 10 minutes is expected.
Actually, if we suddenly power off the AVS client, I think it should be not SDK issue, right ?
If it's not, it does not make sense to define this test case in Amazon self test.

Hi Zeus,
I'm developer from China, I guess you too.
If you can, can you add me WeChat, we can exchange the experience of AVS certification.
WeChat: leino11121
Email<EMAIL_ADDRESS>BTW, I have the same issue for the notification, but I cant wait avs team to fix it, so I change some code on the sdk. It works fine for now.

Hi zeusshuang,
I am sorry to see that this issue has been languishing unanswered for a very long time.  Is this still an issue?  Do you still need us to double check something, or should we close this?
Thank you,
-SWH

Hi @scotthea-amazon ,
We can close this case now.
If I got the same issue again, I will create another ticket.
Thanks,

Thank you Hi zeusshuang.  I am closing the issue.


pkg/controller: Fix CR with same name in different namespaces

This patch uses <namespace>/<cluster-name> as key to store the cluster in Controller struct to avoid over-writing same named CR's in different namespaces.
Fixes #1954
Please read https://github.com/coreos/etcd-operator/blob/master/CONTRIBUTING.md#contribution-flow

@etcd-bot ok to test

@alaypatel07 thank you very much this looks great. Can you also update the CHANGELOG?

@hexfusion hope that works!

lgtm

@alaypatel07 thanks!

@hexfusion Any idea when the next etcd-operator release is gonna come out? We use a single etcd-operator with the cluster-wide option and we had several name clashes in the past in development environments, so this fix is highly appreciated.

@trevex we just merged https://github.com/coreos/etcd-operator/pull/2028 and will begin moving towards release.

Hopefully next week on time-frame.


Optimize StreamingDelete

Implement delete(Datafile) in StreamingDelete, to make use of optimized deletes from #387.
This PR resolves #409.

@aokolnychyi, @rdblue
Could you please take a look? Thank you.

Mostly looks good, but I don't think that DeleteFiles needs to change. Thanks for working on this @sujithjay!

I have made the changes, @rdblue.

Merged! Thanks for fixing this, @sujithjay!


Fix matching for volume paths in cp

Fixes #9787

How does this relate to #9871 is it ok with, and doesn't conflict..

Since he's deprecating container.Copy this would conflict with it.

since @jlhawn has cherry picked this into #9871 we are going to close this :) and it will be merged with that PR


Add mypy to pre-commit

As per this post.
There is some setup required for getting mypy to work as expected (checking the entire repo instead of just changed files)

Duplicate of #53


Winget --version to show correct variable and / or rendered link to log

Description of the new feature / enhancement
Basic idea:
winget should detect if it is executed in cmd or PowerShell, and change the output of the log path accordingly to use the common variable to localappdata, which is $env:localappdata in PowerShell, and %localappdata% in cmd.
Based on feedback, it would be most feasible to follow this approach which should ease the whole process and remove the idea to determine the variable name based on cmd or PowerShell.
Extended idea:
When Winget detects it is run in Windows Terminal it should render the path to the logs, so it can be opened simply by ctrl+left mouse click in Windows Terminal and open it in File Explorer
(this might need remote work of the Windows Terminal team)
Currently only https seems to handled, no local paths.
fyi @DHowett
Just in case  rendering the link and determination is too complicated or not worth the time, I would like to fall back to the basic idea that "winget --info" when run in a PowerShell session should show the logs folder as $env:localappdata, so a user can directly copy the path and change to this folder in the shell.
Proposed technical implementation details
Winget shall detect if it is running in Windows Terminal (if possible)
Winget shall detect if it is running in PowerShell or cmd session
Winget --info shall output the link to logs as a rendered link (Windows Terminal would do this in the correct format)
Examples:
Winget run in native shell as cmd or PowerShell 5.x / 7.x
current behaviour:
Logs: %LOCALAPPDATA%\Packages\Microsoft.DesktopAppInstaller_8wekyb3d8bbwe\LocalState\DiagOutputDir
Winget run in Windows Terminal (e. g. Windows 11 default shell) as cmd
Logs: %LOCALAPPDATA%\Packages\Microsoft.DesktopAppInstaller_8wekyb3d8bbwe\LocalState\DiagOutputDir
Winget run in Windows Terminal (e. g. Windows 11 default shell) PowerShell 5.x / 7.x
$env:localappdata\Packages\Microsoft.DesktopAppInstaller_8wekyb3d8bbwe\LocalState\DiagOutputDir
Use case:
improved accessibility to logs based on user's preferred shell.

While technically possible It's very unlikely it is redirected to a different location indeed or on the other hand the value of the var could be parsed and displayed. Very good point @Trenly

@Karl-WE - Does the above linked PR for the user setting close this issue, or should it be kept open for rendering the correct styling for environment variables?

[Policy] Needs Author Feedback
[Policy] Area-output

Reading the PR once again I believe this is still relevant. @denelon @Trenly .
Pardon I haven't noticed this tagging earlier.
Just checked the output of --version and --info
In winget in cmd and Microsoft Terminal / PowerShell.
I am still convinced it would be most helpful for TS to render the directories as links that are supported in Microsoft Terminal and also using $env:localappdata when invoked in PowerShell.


run API flask application using uWSGI.

instead of running flask with the builtin development server, use
a proper application server. uWSGI can be configured either via
files or environment variables; the chart has been extended to
allow environment variables to be injected into the container.
see #34

Hey @UiP9AV6Y , thanks for your approach to use uWSGI.
We already opened an issue to use the FastAPI Framework instead of Flask. We will discuss if we use FastAPI or uWSGI and decide what to to with your PR.
Thanks a lot for your commitment.

yes, i saw that issue but didn't think much of it as fastAPI is a framework operating on the same stack level ask flask. but apperently the integration into an application server is done via ASGI, which uWSGI does not support (from a quick search there seems to be some third party effort).
i thinks the base concept of this PR can still be reused when switching to fastAPI and uvicorn/daphne/hypercorn.
let me know about the outcome, as it also affects my other PRs.


demo.sh error and Running the Kolide server error

I had an error when running quickstart script on both CentOS and Ubuntu.

[root@localhost kolide-quickstart]# ./demo.sh up simple [license string]
Using default tag: latest
latest: Pulling from kolide/kolide
Digest: sha256:9a802751690fe3a93f7c11d084128fa631cba964d22c772ff58b153d01034e91
Status: Image is up to date for kolide/kolide:latest
Using default tag: latest
latest: Pulling from kolide/openssl
Digest: sha256:9d86215afdd5d76faae9de32b7be862a64542ff7ddcc753c43b34118f42aead8
Status: Image is up to date for kolide/openssl:latest
kolidequickstart_redis_1 is up-to-date
Starting kolidequickstart_mysql_1
kolidequickstart_mailhog_1 is up-to-date
Starting kolidequickstart_kolide_1
Waiting for MySQL to accept connections...
.\C
Error: MySQL failed to start up. Exiting.
[root@localhost kolide-quickstart]#

CentOS error when preparing db (CentOS/Ubuntu):

/usr/bin/kolide prepare db \
>     --mysql_address=<IP_ADDRESS>:3306 \
>     --mysql_database=kolide \
>     --mysql_username=root \
>     --mysql_password=toor
2017/02/21 15:04:36 FAIL<PHONE_NUMBER>2641_CreateTablePasswordResetRequests.go (Error 1067: Invalid default value for 'expires_at'), quitting migration.

Thanks for reporting the issue. We've only tested the script on macOS so far.
I'll try to duplicate the errors with docker on ubuntu/centos and resolve any differences.

Having the exact same error on Ubuntu 14.04 at the moment. Happy to provide any info that would be helpful in diagnosing the issue.

Thanks for the feedback. I've been working on troubleshooting this issue today and will have a PR with a fix soon.

@groob is there a way to quickly reset our docker environment to test the fix or is that not necessary?

@Centurion89 I tested it myself, but it would be great to get a confirmation
# remove existing containers (note this will remove any containers on the host. you can also remove # the kolide ones manually if you'd prefer
docker rm -f $(docker ps -a -q)

# clone my fork
git clone https://github.com/groob/kolide-quickstart.git

# check out the branch
cd kolide-quickstart &&  git checkout initialize && cd ..

# run through the usual steps in the quickstart
cd kolide-quickstart && ./demo.sh up simple <license>

Does the osquery_status log file show up after adding some hosts?

@zwass yes it does.

The only container that had any issues was mysql, because it adds a custom user and group
https://github.com/docker-library/mysql/blob/eeb0c33dfcad3db46a0dfb24c352d2a1601c7667/5.7/Dockerfile#L4

@groob fix confirmed - thanks!

Merging, thanks for the verification 👍

Wow! Tested and is now up and running!
Great work guys!


Missing ligatures in PDF

'fi', 'ff', 'fl' and maybe other ligatures may appear as blank glyphs in the PDF.

I open the PDF file in Chrome browser and can see these ligatures are not rendered properly:

I'm seeing this issue as well:


Add Component(1) support

At the moment, someone else is maintaining a Component-compatible React repo: https://github.com/njpatel/react …but it's nearly identical to this, apart from having a component.json.
Although the name of this repo is coupled to Bower, it would be good to have Facebook officially manage the Component(1) module too.
Thanks

I’m closing this as inactive. I think the community has pretty much converged at using npm for front-end libraries as it provides the desired flexibility both for CommonJS and multiple UMD builds. I encourage you to look into using npm instead. We don’t plan to support Component directly.

:+1:


@mui/material styles only applied when story width is unset in the production build

Describe the bug
Production Ladle builds that use the @mui/material package do not apply the appropriate styles when the story width is changed.  Works as expected when using ladle serve.
With the story width set to unset:

Setting story width to any other value:

My guess is that it has something to do with the css-in-js.  I'm going to try to reproduce with a similar library like styled-components .
Reproduction
https://stackblitz.com/edit/ladle-ehhg6r
Run pnpm run prod

The issue is that the width addon puts stories into an iframe. We copy over styles from the main window but CSS in JS libraries are a bit tricky to handle like that and it's also different for each one of them. This is how we do it for Styletron: https://github.com/uber/baseweb/blob/master/.ladle/components.tsx#L27:L40
I want to add some documentation & setup examples for different (most popular) CSS in libraries.

Thanks that pointed me in the right direction.  I got it working with this components.tsx:
import React, { useMemo } from 'react'
import { GlobalProvider } from '@ladle/react'
import { CssBaseline, ThemeProvider } from '@mui/material'
import { theme } from '../src/theme'
import { CacheProvider } from '@emotion/react'
import createCache from '@emotion/cache'

import '../src/index.css'

let prevWidth = 0
const defaultCache = createCache({
  key: 'emotion',
  container: document.head,
})

// all stories are wrapped in this
export const Provider: GlobalProvider = ({ children, globalState }) => {
  const cache = useMemo(() => {
    const widthChange =
      (prevWidth > 0 && globalState.width === 0) ||
      (prevWidth === 0 && globalState.width > 0)

    if (widthChange) {
      const iframe = document.querySelector(
        `[title='Story ${globalState.story}']`,
      ) as HTMLIFrameElement | null

      const targetHead = iframe?.contentDocument?.head

      if (targetHead) {
        return createCache({
          key: 'emotion',
          container: targetHead,
        })
      }
    }

    return defaultCache
  }, [globalState.width])

  return (
    <CacheProvider value={cache}>
      <ThemeProvider theme={theme}>
        <CssBaseline />
        {children}
      </ThemeProvider>
    </CacheProvider>
  )
}


skip account limit check during cluster create

Environment:

AWS ParallelCluster / CfnCluster version : 2.3.1

Bug description and how to reproduce:
Recently upgraded to version 2.3.1, and noticed that I couldn't create new clusters due to the account limit check imposed by #872
We usually do a sort of blue-green deployment for our clusters, where we deploy a new set of clusters with some changes to replace the existing ones, and allow jobs to transition from new to old. This new account limit check means that we would have to have account limits that are double what we want the max_queue_size of the clusters to be for us to do this deployment.
Is there a way to skip the check? If not, could you add an option to do so?

Hi @keien
You can disable the checks with:
[global]
sanity_check = false

but I assume you already know this and are asking for a specific way to disable the account limit check only. I've added a feature request flag and will discuss with the team.
Is it's important to note that the account limit check is only done on a per-cluster basis, so if you have, let's say a limit of 10 c5n instances, you can have two clusters each with max_queue_size = 10

right, this is more of an issue when there’s an existing cluster that already has some instances, and we want to provision a new cluster with the same instance type. For example, I have a m5.large cluster with a max queue of 100, with 10 instances running in the cluster. I then want to create a new cluster with the same m5.large instances and also a max queue of 100. However, my account limit for m5.large is also 100, so the pcluster create will fail saying that I am asking for more instances (110) than my account limit (100). In the worst case, if I have an existing cluster with the max number of instances, I would need to double my account limit just to provision another cluster.

I'm going to close this issue because we added the possibility to skip AWS limits check and then we improved the sanity check to be a configuration tester rather than a limit checker: https://github.com/aws/aws-parallelcluster/pull/1779


chore(main): release sandworm-jest 1.5.0

:robot: I have created a release beep boop
1.5.0 (2022-11-28)
Features

update utils to v1.9.0 (42007b5)

This PR was generated with Release Please. See documentation.

:robot: Release is at https://github.com/sandworm-hq/sandworm-jest/releases/tag/sandworm-jest-v1.5.0 :sunflower:


feature request: jsonmodel loaddata add data to http body

Hi,
I want to add a feature request to jsonmodel class (https://openui5.hana.ondemand.com/api/sap.ui.model.json.JSONModel#methods/getProperty):
Currently it's possible to switch the http method e.g. from GET to POST, add parameters etc. But there is no way to add data to the http body. So always when I'm doing a HTTP POST request and a JSON is coming as response which I want to load and set it to a model, I need to do it with ajax of jquery or plain JS. I wish I could do it with the loaddata method from JSONModel.
Arguments that it's already possible with e.g. ajax are (IMO) no real arguments. Against argument is e.g. drag and drop, which was only possible with plain JS / Jquery for a long time.
Thx in advance!
BR

Hello @DubZyy ,
Thank you for sharing your enhancement proposal. I've created an internal incident<PHONE_NUMBER>. The status of the issue will be updated here in GitHub.
Regards,
Petya Bogdanova
(UI5 Dispatcher)

Since there is no response from the author for more than 4 weeks I'm closing the ticket.


Define allowscalar

This PR defines an allowscalar method, that provides a device-agnostic way to use CUDA.@allowscalar.
This should help us remove CUDA as a dependency in the ClimaCore test suite.

Can you please add tests?

Yes, absolutely.


Patient Document

Create a modal in the Patient's list to upload patient document
Create a modal in the Patient's header to view the document

Where do we store this document? Cloudinary?

Consider using google drive links, this looks helpful but haven't tried it yet:
https://django-googledrive-storage.readthedocs.io/en/latest/


[Question] anyone have experiment SSR react + sailsjs ?

Sails version: 0.12
Node version: 6.6.0
NPM version: 4.02
Operating system: Linux Ubuntu
[Question] anyone have experiment SSR react + sailsjs ?
please share your

fixed

ok, fixed


Fix user defined outcome connections in Branching activities

Fixes #5686

Shouldn't it target 1.9.x if this is a bug fix?

1.9.x is ok - but in the dev branch, branch outcome labels are broken after this commit https://github.com/OrchardCMS/Orchard/commit/2a57a153632d31a8692f2ad437e6d5e897e33c79 which I'm guessing is necessary for localized sites.  I don't have a localized site, but after the commit mentioned, the branch labels are broken.  See the original issue: https://orchard.codeplex.com/workitem/20834


Bug fixes at filesystem-ag-driver and add a new docker script for node.js binding test

Fixed several bugs at the filesystem-ag-driver and its irods plugin
Added a new docker script for testing libsyndicate-node.js binding
Actual code of libsyndicate-node.js will be downloaded from another repository (https://github.com/syndicate-storage/libsyndicate-node.js)

Hey Illyoung, can you re-sync your fork with master and send the PR again?  Your commits are out of sync.


WIP:  DirectoryService: Add support for other directories

Adds support for the APIs:

create_microsoft_ad()
connect_directory()
create_alias()
enable_sso()
disable_sso()

Codecov Report

Merging #4507 (cf59560) into master (213c081) will increase coverage by 0.00%.
The diff coverage is 100.00%.

@@           Coverage Diff           @@
##           master    #4507   +/-   ##
=======================================
  Coverage   95.17%   95.18%
=======================================
  Files         511      511
  Lines       57666    57727   +61
=======================================
+ Hits        54885    54946   +61
  Misses       2781     2781

Flag
Coverage Δ

servertests
48.24% <14.28%> (-0.04%)
:arrow_down:

test_responses
32.34% <19.04%> (-0.02%)
:arrow_down:

unittests
95.08% <100.00%> (+<0.01%)
:arrow_up:

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

Impacted Files
Coverage Δ

moto/ds/exceptions.py
100.00% <100.00%> (ø)

moto/ds/models.py
97.04% <100.00%> (+0.72%)
:arrow_up:

moto/ds/responses.py
100.00% <100.00%> (ø)

Continue to review full report at Codecov.

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

@bblommers I have a lot of validation steps in this code.  The steps and logic is not organized that well and the logic takes up a lot of space in models.py.  I could make the validation functions individual validations using static methods in the Directory class.   Or I could create a bunch of separate functions and move them to a new file, say validation.py or utils.py.  Or create a separate Validations class in a separate file?  Do you have a preference or an alternative suggestion?
It's an issue I've come up against before, so it'd be nice to have a better approach, otherwise models.py can get pretty large.

@kbalk No preference here! Having the validation code separated out from models.py would indeed by good, but I trust your judgement in how that's done exactly.

I've got a Terraform script that creates an AD Connector and the script fails with my moto code.  I'm debugging the problem and it's taking me some time.  The other thing I have left to do is reorganize the validation.  So it may be a day or two before this code is ready for review.

@bblommers The rearrangement of the validation handling is not ideal, but it feels a little less messy.
I discovered I was not setting the DnsIpAddrs field, so that was causing the terraform script to fail.  My calculation of those IPs is not great, but it was the best I could do with the knowledge I have.  If someone has a better solution, I hope they change the code.


Standardize FreeBSD worker configuration

Remove one builder from the freebsd-current worker. There's not a sufficient
amount of value in testing both debug and non-debug builds on the same worker,
particularly since only one (buildbot) build is allowed to run at a time, so
they end up queued and run sequentially.
While I'm here:
Switch the freebsd-current worker to the 'SharedUnixBuild', because it also
builds with --with-debug and @vstinner says debug is likely to be more valuable
on bleeding edge OS versions. Accordingly, switch freebsd10 worker to the
'NonDebugUnixBuild'.
Set -j4 on freebsd-current worker to match freebsd10 worker for in-test
parallism, allowing the worker owner to (somewhat) manage parallelism/load
themselves via guest CPU configuration.
Update the freebsd10 worker description to use the canonical branch label/term: STABLE, not ".x".

I applied the new config:
b'2018-09-28 11:16:06+0000 [Broker,418,<IP_ADDRESS>] Worker koobs-freebsd10 attached to AMD64 FreeBSD 10-STABLE Non-Debug 2.7'
b'2018-09-28 11:16:06+0000 [Broker,418,<IP_ADDRESS>] Worker koobs-freebsd10 attached to AMD64 FreeBSD 10-STABLE Non-Debug 3.7'
b'2018-09-28 11:16:06+0000 [Broker,418,<IP_ADDRESS>] Worker koobs-freebsd10 attached to AMD64 FreeBSD 10-STABLE Non-Debug 3.x'
b'2018-09-28 11:16:06+0000 [Broker,418,<IP_ADDRESS>] Worker koobs-freebsd10 attached to AMD64 FreeBSD 10-STABLE Non-Debug custom'
b'2018-09-28 11:16:06+0000 [Broker,418,<IP_ADDRESS>] Worker koobs-freebsd10 attached to AMD64 FreeBSD 10-STABLE Non-Debug 3.6'
b'2018-09-28 11:16:07+0000 [Broker,438,<IP_ADDRESS>] Worker koobs-freebsd-current attached to AMD64 FreeBSD CURRENT Shared custom'
b'2018-09-28 11:16:07+0000 [Broker,438,<IP_ADDRESS>] Worker koobs-freebsd-current attached to AMD64 FreeBSD CURRENT Shared 3.6'
b'2018-09-28 11:16:07+0000 [Broker,438,<IP_ADDRESS>] Worker koobs-freebsd-current attached to AMD64 FreeBSD CURRENT Shared 3.7'
b'2018-09-28 11:16:07+0000 [Broker,438,<IP_ADDRESS>] Worker koobs-freebsd-current attached to AMD64 FreeBSD CURRENT Shared 3.x'
b'2018-09-28 11:16:07+0000 [Broker,438,<IP_ADDRESS>] Worker koobs-freebsd-current attached to AMD64 FreeBSD CURRENT Shared 2.7'
b'2018-09-28 11:16:07+0000 [Broker,438,<IP_ADDRESS>] configuration update complete'
Reconfiguration appears to have completed successfully

Gracias @vstinner


How to run a query (REST or GraphQL) with "SELECT count(*)"

Hi everybody
Also the same request as #1513 , but this time with "SELECT count(*) AS c". We use such query to get a counter before to drill down  on a next page.
Thx in advance.

Aggregation functions are not currently supported in REST but they are in GraphQL.
The docs for count in GraphQL are still pending (https://github.com/stargate/docs/issues/117) but you can see some sample in the test here

Hi @dougwettlaufer
thx a lot for your answer...
Indeed, what I wanted to do is :
query get_nb_thread_for_AAA {
    message (value: {thread_id:"AAA"}) {
      values {
      	c: _bigint_function(name: "count", args: ["message_id"])
      }
    }
}

It works for me. Thx a lot.


fix(url-query): fix join query

the previous join only joined on index_record and index_record_hash table, actually didn't filter out index_record_url by hashes
previous query:
print index_s.query(IndexRecordUrl).join(IndexRecord.hashes).filter(and_(Inde
xRecordHash.hash_value=='f787197cffb8ee0e9e4f061b89b61a07'))
SELECT index_record_url.did AS index_record_url_did, index_record_url.url AS index_record_url_url
FROM index_record_url, index_record JOIN index_record_hash ON index_record.did = index_record_hash.did
WHERE index_record_hash.hash_value = %(hash_value_1)s

current query:
print index_s.query(IndexRecordUrl).join(IndexRecordUrl.index_record).join(In
dexRecord.hashes).filter(and_(IndexRecordHash.hash_value=='f787197cffb8ee0e9e4f061b89b
61a07'))
SELECT index_record_url.did AS index_record_url_did, index_record_url.url AS index_record_url_url
FROM index_record_url JOIN index_record ON index_record.did = index_record_url.did JOIN index_record_hash ON index_record.did = index_record_hash.did
WHERE index_record_hash.hash_value = %(hash_value_1)s

r? @MurphyMarkW

That's weird, and I -think- I get why that's happening. In any case, that's obviously the more correct query, so +1'd for that.
We should prolly replace these with subqueries in general. Should be much more performant.


Application opens maximized, unresizeable

Is it by design that the app opens maximized and unresizeable? I can go into full screen mode, but I cannot shrink the window smaller or move it around the screen.

Same here... 😭

The window should remember its size, but it's not implemented yet. Moving and resizing should be fixed now.

confirmed - I can resize and move window now


Lot of false negatives on the binary image - is the segmentation branch really necessary?

Hello,
Thanks for your work.
I downloaded the pretrained model and tested it on my own images (1280x720, rgb)
When looking at the results, the binary image always gives a lot of false negatives pixels and no false positives. Most of the time, only parts of the groundtruth lanes are detected as positives.
However I noticed that the embeddings image (rgb using the channels 0, 1, 2 if I am correct) gives something really good (lanes are clearly drawn with different colors, even though the background is still here).
Is the binary branch really necesary ? It looks like the embeddings branch also learns the ability to differentiate lanes from background.
I am thinking of not applying the binary mask, only predict the embeddings branch and simply do clustering on the embeddings.
What do you think ?

@alexgoup The embedding branch can be extracted alone to do the lane detection task:)

Ok, but do you think processing the embeddings alone could possibly lead to better results than using the binary mask ? Or is it a particularity of my test set?
Thanks for your answer.

Yes, the cluster process is easier once the background is removed. But using the mask is relevant only if the binary segmentation is of good quality (not too much false negatives/positives pixels).

Any idea why the binary image looks that bad on such a test image ? Especially on the left lane ?

@alexgoup It is about the training process. The model I uploaded was some kind of overfitted to the tusimple lane dataset. It is quite normal the model performs not as well as the tusimple lane dataset. According to your situation you can either train your own model on your own dataset or train a new model on tusimple lane dataset with a earlier stop:)

Earlier stop won't generalize well either, I've tried it. What you can do is use that instance mask image and do post-processing on your own it'll give much better results. I'm using the 94k epochs model tho.

@teaddicted If you check the tboard file you will find the val cost raise around 100k epoch so earlier stop is not useless in my opinion:)

@teaddicted Yep I think we share the same opinion:)

Thanks.
The tests I did were with the 200k epochs model.
Can you please upload the 94k model ?
If it's not working well I will retrain on my own data.

Thanks, can you just tell me which older version should I pull ?

@alexgoup I'm not that sure maybe that f7010e29029b2645e114a56c61190b9026367c2f? ==!

hi @alexgoup  how did you train the model with your own data? Did you use the python script  (/tools/generate_tusimple_dataset )which generates the instance segmentation and binary segmentation imges ?

@alexgoup It's your test set. With the binary segmentation as a mask the cluster process will be much easier than the do such a clustering without a mask:)

I carefully read your code and didn't find place where you use segmentation mask in embedding proccess.
In discriminative_loss.py you calculate loss for full embedding tensor including background:
unique_labels, unique_id, counts = tf.unique_with_counts(correct_label)     counts = tf.cast(counts, tf.float32)     num_instances = tf.size(unique_labels)
Here num_instances here = num of lines + 1 (background class)
Am I right?


API Call to get connected peers?

Is there a way of making a call to get the connected peers? That way i could parse the returned json data (assuming REST) to get a list of the IPs so that I could stick the records into my pihole custom DNS entries dynamically.
Cheers

@itsalljustdata
In theory yes, but there are caveats.
Web UI calls the Management API to get a list of peers with status:
https://app.netbird.io:33071/api/peers
However, it requires a JWT token that is generated on auth. It expires after a while, so you will need to re-authenticate. Probably this won't fit your use case.
P.S. We are working on API separately and will be releasing it compatible with OpenAPI.

Cheers Misha.
I'm probably best hanging on for the API to be released.
Although...
Given that I authenticate with github, would that not make the re-authing process easier to manage?

Cheers Misha.
I'm probably best hanging on for the API to be released.
Although...
Given that I authenticate with github, would that not make the re-authing process easier to manage?

@mlsmaycon what do you think?

Hi @itsalljustdata, we are looking at some alternative to the JWT to serve as authentication, maybe not using your browser session with GitHub, but rather following they concept with personal access tokens(PAT), stay tuned we should have that sorted out by Q4/2022

@itsalljustdata we've release support to PATs and Service Users which allow for API calls using tokens. For more details, check out our API docs: https://docs.netbird.io/api


Fixes #16

https://github.com/maidsafe/socket-collection/issues/16

@S-Coyle could you pls merge this if OK


Move to Typescript

Working GitHub pages setup can be found here:
https://github.com/46bit/rtt

I'd love to assist you with this. Do you want to use Gulp or Webpack? Or alternatively migrate to a more powerful framework such as React?


Fix Portworx name in doc

LGTM. FYI, to get this into the live github pages sites, you'll also need to submit a PR to the gh-pages branch of this repo, under both the master and v0.9.0 directories

@skriss I don't see this file in the gh-pages branch under either of those directories.

@rosskukulinski Sure, I'll send out a PR with that info.


modify README.md

ok

don't use public repositories to experiment with using github...or you risk getting banned from them

sorry


Toaster styling + clipboard event mgmt

Made toaster messaging consistent with current look-and-feel
Using built-in success callback for clipboard to display toaster feedback

@carrotderek looks much better than what I did!
Is the info not too dark for dark mode?

@Nasicus good point! I made a change in #78


#15 - Make options on adalFetch optional

This change makes the options parameter of the adalFetch function optional. This behavior matches up with that of the underlying JS fetch API in which the equivalent parameter is also optional.

done


Update JWT Example

This updates the JWT example to use #2487. Note that there are some sharp edges which may need further thought, and that the while #2487 and https://github.com/risc0/RustCrypto-RSA/pull/2 are in review this isn't fully ready (i.e. can't patch correctly).
Replaces #2482

Marking as draft b/c https://github.com/risc0/risc0/pull/2487 and https://github.com/risc0/RustCrypto-RSA/pull/2 are needed first

Status: investigating why the ZKR doesn't seem to be registered if I run the test from the examples directory, but it does seem to be registered if I run the test from the examples/jwt-validator directory.

Superseded by #2505


API rate limit exceeded error

Is there a way I can send the request authenticated as my github user?
$ name-your-contributors hoodiehq --since=2016-02-01T00:20:000Z
err { [Error: {"message":"API rate limit exceeded for <IP_ADDRESS>. (But here's the good news: Authenticated requests get a higher rate limit. Check out the documentation for more details.)","documentation_url":"https://developer.github.com/v3/#rate-limiting"}]
  status: 403,
  json:
   { message: 'API rate limit exceeded for <IP_ADDRESS>. (But here\'s the good news: Authenticated requests get a higher rate limit. Check out the documentation for more details.)',
     documentation_url: 'https://developer.github.com/v3/#rate-limiting' } }
Unable to get unique users { [Error: {"message":"API rate limit exceeded for <IP_ADDRESS>. (But here's the good news: Authenticated requests get a higher rate limit. Check out the documentation for more details.)","documentation_url":"https://developer.github.com/v3/#rate-limiting"}]
  status: 403,
  json:
   { message: 'API rate limit exceeded for <IP_ADDRESS>. (But here\'s the good news: Authenticated requests get a higher rate limit. Check out the documentation for more details.)',
     documentation_url: 'https://developer.github.com/v3/#rate-limiting' } }
err { [Error: {"message":"API rate limit exceeded for <IP_ADDRESS>. (But here's the good news: Authenticated requests get a higher rate limit. Check out the documentation for more details.)","documentation_url":"https://developer.github.com/v3/#rate-limiting"}]
  status: 403,
  json:
   { message: 'API rate limit exceeded for <IP_ADDRESS>. (But here\'s the good news: Authenticated requests get a higher rate limit. Check out the documentation for more details.)',
     documentation_url: 'https://developer.github.com/v3/#rate-limiting' } }

Fun times. Sorry, you're the first other user to really take a crack at this. Writing up some docs about it, one second.

thanks :) looking good with https://github.com/RichardLitt/name-your-contributors/commit/07b3994d24eaf5018b73010f0d33f12dc792de47


Set minimum SSL protocol to TLS 1.2

Drop TLS 1.0
Drop TLS 1.1

This can be done on Cloudflare's settings page.
By the way, the reason why this is beneficial is explained in this article:
https://blog.qualys.com/product-tech/2018/11/19/grade-change-for-tls-1-0-and-tls-1-1-protocols

Setting implemented on Cloudflare's settings page.


configuring gapp engine auto-deploy on Travis

This pull request addresses the problems described at issue #1151

@felipesanches ping status on this?

It was left aside on purpose because I'm manually deploying it whenever there's something important. At some point I'll resume this, but it does not seem top-priority if compared to the other stuff I'm assigned to.


Add RBAC to README.md

This is just an example that works for me..
---
kind: ClusterRole
apiVersion: rbac.authorization.k8s.io/v1
metadata:
  name: kube-slack
rules:
- apiGroups: [""]
  resources: ["pods"]
  verbs: ["get", "watch", "list"]
---
apiVersion: v1
kind: ServiceAccount
metadata:
  name: kube-slack
  namespace: kube-system
---
apiVersion: rbac.authorization.k8s.io/v1beta1
kind: ClusterRoleBinding
metadata:
  name: kube-slack
roleRef:
  apiGroup: rbac.authorization.k8s.io
  kind: ClusterRole
  name: kube-slack
subjects:
  - kind: ServiceAccount
    name: kube-slack
    namespace: kube-system

Could you please submit this as a PR?
I see @jstriebel also wrote similar RBAC in his Helm chart

Closed in #26


Read only file/folder implementation

Currently we only have an implementation fully compatible with read/write FTP files/folders. We will have to check the item permissions to see if it's read only.
On my own IIS-powered local FTP server, permission checks do not seem to work properly, a read-only file doesn't give any permissions (None), same for read-write files.
One workaround is to try and see if we can append to the file, but the extra roundtrips needed to do this will slow down performance especially on slow networks.

I did some digging through the FluentFTP repo and couldn't find any obvious documentation or code locations that would specify a connection is "read-only". The closest thing seems to be the idea of anonymous connections, but this is only one way that FTP might be read-only, with individual directory permissions being the other.
Generally, this is analogous to having both individual and root/drive level access permissions in the inbox SystemFile. Since we haven't explicitly addressed and documented how to handle this scenario, let's do that now.
Gathering existing established conventions for this library from past discussions:
From https://github.com/Arlodotexe/OwlCore.Storage/issues/37#issuecomment-1658828466:

Our API dictates the resource should exist with reasonable confidence on construction so that when you try to access the file and use the object, it doesn't throw.

From https://github.com/Arlodotexe/OwlCore.Storage/pull/56#pullrequestreview-2131480054:

A file or folder resource should exist before it's accessed through our abstraction. [...] Instances that are created internally can pre-validate this and skip the consumer-facing validation/guard.

From this discussion in the UWP Community Discord:

Permissions and authentication should always be settled by the underlying API before (when async, like StorageFile/UAC/FTP/OneDrive/etc) or during (when synchronous, like zip passwords) creation of a folder or file instance.
For authenticated resources, you'll have specific exceptions thrown from the underlying library if the permissions are unexpectedly revoked. If that happens, just catch the exception at the application-side callsite to the storage abstraction, refresh permissions, and rerun.
Remember that recursive operations are implemented by your applications and not this library.

I believe these comments have everything we need to pick a direction here.
Carefully leaving recursive enumeration to the consuming application means that the responsibility of authentication falls to the consumer prior to construction, following the same rules we've established for other authenticated resources.
This means we shouldn't need to change SystemFile or SystemFolder to account for these scenarios. The next step is to figure out how these translate to the FTP protocol, and how FluentFTP handles those things.

couldn't find any obvious documentation or code locations that would specify a connection is "read-only". The closest thing seems to be the idea of anonymous connections, but this is only one way that FTP might be read-only, with individual directory permissions being the other.

Anonymous connections can also have R/W permission, mostly in the case of having a test server so this isn't a reliable way to check for it.

Permissions and authentication should always be settled by the underlying API before (when async, like StorageFile/UAC/FTP/OneDrive/etc) or during (when synchronous, like zip passwords) creation of a folder or file instance.

Main problem here is you have to distinguish between R/O & R/W folders & files during enumeration. I think for other operations i.e. copying and moving this approach is okay and we don't have to do anything on this part.
There don't seem to be any issues reported regarding permission checks so no idea if it's just an issue on my end.

Anonymous connections can also have R/W permission, mostly in the case of having a test server so this isn't a reliable way to check for it.

Good point, noted.
Regarding this:

Main problem here is you have to distinguish between R/O & R/W folders & files during enumeration. I think for other operations i.e. copying and moving this approach is okay and we don't have to do anything on this part.

I think the analysis above holds everything we need to clarify how to handle this.
When we say that

Our API dictates the resource should exist with reasonable confidence on construction so that when you try to access the file and use the object, it doesn't throw.

and

Instances that are created internally can pre-validate this and skip the consumer-facing validation/guard.

We're also implying that distinguishing between "read-only" and "modifiable" can just be the responsibility of the consumer, it doesn't need to happen dynamically at runtime. They should know whether they have the ability to modify or not, and that assumption can be trickled down to child instances.
This is what we mean by highlighting:

Permissions and authentication should always be settled by the underlying API before (when async, like StorageFile/UAC/FTP/OneDrive/etc) or during (when synchronous, like zip passwords) creation of a folder or file instance.
For authenticated resources, you'll have specific exceptions thrown from the underlying library if the permissions are unexpectedly revoked. If that happens, just catch the exception at the application-side callsite to the storage abstraction, refresh permissions, and rerun.
Remember that recursive operations are implemented by your applications and not this library.

It's important to think about this because SystemFile and SystemFolder are simple and rather fitting analogies where this hasn't been fully explored. Any problems we solve or improvements we make in this space for FTP will translate to all other implementations which have a permissions system.

To some degree this issue/concern is resolved. It'll be the consumer's responsibility to check if the filesystem is read only or not.
Another set of tests & env variables will be added for read-only filesystems specifically where folders & files are assumed to exist.


Disable the QUIC TestRun in active_timeout AuTest

We have added QUIC version 0x1 support to our 10-Dev branch via #8956,
but that has not been backported to 9.x and we don't plan to backport
that at this time. ASF CI will be updated with the latest version of
curl which uses 0x1 and would therefore fail. This change disables the
QUIC TestRun of active_timeout so it doesn't run on 9.x since ATS
doesn't support the latest QUIC test tools on that branch. This patch,
therefore, should not go into 10-Dev.
Note that this patch can be reverted in the future if we decide to
backport QUIC 0x1 support to 9.x.

Cherry-picked to v9.2.x


[SUGGESTION] New/Updated badges

Great UI lib, thanks! And, good to see such regular updates!
I want to suggest that a new badge is placed next to the component name (in the nav) when a new component is added and an updated badge when new features are added to a component.

Hello @go4cas,
Thanks for your suggestion! I've added an Edge badge for features that are currently only on the dev branch. When a new release happen, those badges will be marked asNew.
Not sure about the Updated badge though, this would require a lot of work to maintain as anything can be an update.


Use merge for toJson object

This will avoid infinite recursion with circular references
Summary

[x] Tell us about the problem your pull request is solving.
#196 - infinite recursion when there are circular references
[x] Are there any open issues that are related to this?
closes #196, caused by #179
[x] Is this PR dependent on PRs in other repos?
caused by #179

Other Information
Question

Is merge the best route here? it's probably the easiest, but maybe not the most performant  if we already know the key we want to copy to the json object.
Should we use merge for cloneWithAccessors?

@marshallswain could you take a look at my questions in this?
@Palivonas this passes your reproduction repo, are there any other test cases to do?

I’ll bet this won’t work with getters whicj have no setter.

@marshallswain if they are enumerable it should work, check this code sample, the last output is the most relevant
https://runkit.com/nickbolles/lodash-merge-and-defineproperties

@NickBolles It seems to me like lodash.merge works exactly the same as copyWithAccessors.  Thanks for setting up that runkit.

Published as<EMAIL_ADDRESS>

@marshallswain NP!
So do we need to add any documentation to the instance defaults (or anything else) to make sure that getters are enumerable if you want the property serialized to JSON (such as when SSR and sending it to the client). #196 is a good example that we could point to the documentation.

@NickBolles Yeah.  Feel free to make a note in the /docs repo.


Add user authentication

Fixes #17

Codecov Report

Merging #41 (d6fa410) into main (f9323b3) will increase coverage by 0.85%.
The diff coverage is 71.42%.

@@            Coverage Diff             @@
##             main      #41      +/-   ##
==========================================
+ Coverage   18.33%   19.19%   +0.85%
==========================================
  Files           5        7       +2
  Lines         180      198      +18
==========================================
+ Hits           33       38       +5
- Misses        138      150      +12
- Partials        9       10       +1

Impacted Files
Coverage Δ

pkg/service/job.go
0.00% <ø> (ø)

pkg/service/account.go
71.42% <71.42%> (ø)

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 f9323b3...d6fa410. Read the comment docs.


Add --delete-namespace option for helm uninstall

What this PR does / why we need it:
close #8911
Special notes for your reviewer:
If applicable:

[ ] this PR contains documentation
[ ] this PR contains unit tests
[ ] this PR has been tested for backwards compatibility

Closing as per https://github.com/helm/helm/issues/8911#issuecomment-711378545.


Flake8

added flake8.yml file and image
Close #17

Please change the PR title to something meaningful

now the title good ? @natifridman


Not enough data in buffer

This error occurs periodically in the file Buffer.php
Any ideas how I can solve it?
In Buffer.php line 56:
Not enough data in buffer to read 1 bytes

My project runs on digitalocen servers (4 GB Memory / 80 GB Disk / FRA1 - Ubuntu 18.04.3 (LTS) x64). Mysql version 5.7.31.
It is difficult for me to reproduce the problem, but it occurs periodically after some time while the script is running.
Only restarting the script helps - supersvisor restart all.
PHP Fatal error:  Uncaught LogicException: Not enough data in buffer to read 1 bytes in /var/www/etherra-auction/backend/vendor/react/mysql/src/Io/Buffer.php:56 Stack trace: #0 /var/www/etherra-auction/backend/vendor/react/mysql/src/Io/Buffer.php(115): React\MySQL\Io\Buffer->read() #1 /var/www/etherra-auction/backend/vendor/react/mysql/src/Io/Buffer.php(168): React\MySQL\Io\Buffer->readInt1() #2 /var/www/etherra-auction/backend/vendor/react/mysql/src/Io/Buffer.php(192): React\MySQL\Io\Buffer->readIntLen() #3 /var/www/etherra-auction/backend/vendor/react/mysql/src/Io/Parser.php(260): React\MySQL\Io\Buffer->readStringLen() #4 /var/www/etherra-auction/backend/vendor/evenement/evenement/src/Evenement/EventEmitterTrait.php(123): React\MySQL\Io\Parser->parse() #5 /var/www/etherra-auction/backend/vendor/react/stream/src/Util.php(71): Evenement\EventEmitter->emit() #6 /var/www/etherra-auction/backend/vendor/evenement/evenement/src/Evenement/EventEmitterTrait.php(123): React\Stream\Util::React\Stream\{closure}() #7 /var/www/etherra-auc in /var/www/etherra-auction/backend/vendor/react/mysql/src/Io/Buffer.php on line 56

I'm still hoping for a simplified script to reproduce this.
I've personally been running this project in production for years and we're not aware of any such issues.
If you can help us pinpoint any issues, I'm happy to take a look. In the meantime, I'm not sure there's much we can do unfortunately.

Closing this due to a lack of feedback, as we can not reproduce this. Please come back with more details if this problem persists and we can reopen this :+1:

Just ran into the same issue (running with Framework X):
Not enough data in buffer to read 55 bytes
This only occurs if a certain sequence of queries is sent. If I restart the server in between, the affected query runs ok. I'm accessing the repository with the affected query from different controllers and then it breaks. If I access it multiple times from the same controller, all is ok.
Another strange thing is if I complicate the query a bit, the query just never returns and the whole connection is stuck instead of throwing the above mentioned error message.
The query itself is very basic and I can't see anything wrong with it at all.

Small update: To me it looks like that some packets stay in the buffer even after queries are completed (like EOF_Packet). When new packets arrive, these old packets get interpreted first but the state does not match (e.g. interpreted as result set instead of header).
I found that in the function onResultDone() in Parser.php:296 $command->emit('end'); is run before the state is reset (resultFields and rsState) - if I do this before emitting end, all works for me. Don't know if this fix is correct, though...

Looks like I was using Fibers wrong (shout-out to @clue) and this caused the issue, so from my side all is ok now.

I've helped @pfk84 to debug the error above and could eventually track this down to an incorrect usage of reactphp/async and not an error in this MySQL implementation. The problem boiled down to calling await($db->query($sql)) from within a promise callback like $promise->then($fn). The subtle error is that await() is blocking and must not be called from within a promise callback, so this needs to be wrapped in a $promise->then(async($fn)) to make this work. The error messages where somewhat misleading and unhelpful, so the conclusion here is to improve error reporting for incorrect fiber usage as discussed in https://github.com/reactphp/async/issues/50.
Along the way, I've also spent a fair amount of time analyzing the MySQL parser and could indeed find a problem that turned out to be unrelated to @pfk84's error but could potentially have caused @yanmandev's original report. I've filed #158 to fix this issue. Together with this analysis, you're looking at ~8 hours of work, enjoy!


[IMPROVEMENT] Remove outdated replica IM pod operation after IM consolidation ready in 1.5

Is your improvement request related to a feature? Please describe (👍 if you like this request)
https://github.com/longhorn/longhorn-manager/pull/2371#discussion_r1434782250
Describe the solution you'd like

Describe alternatives you've considered

Additional context

So the task is to delete https://github.com/longhorn/longhorn-manager/blob/2931e5b7bbc88849f67e9eb9cdab32b3fa531da4/controller/node_controller.go#L1017-L1033 and https://github.com/longhorn/longhorn-manager/blob/2931e5b7bbc88849f67e9eb9cdab32b3fa531da4/controller/node_controller.go#L1043-L1048?


Feature/covenant api

Addresses #159 with the addition of the ICovenantApi and corresponding models.

Added necessary models for Covenant API set
Included Fluent Assertions for validating data serialization in unit and integration tests

Integration tests pull raw data back from Blizzard to validate against .NET model

🥳


feat: show/store pubKeyOperator using the same scheme it was set originally via protx-es

Issue being fixed or feature implemented
It's pretty confusing that we display pubKeyOperator using new theme after v19 hf for masternodes that were never registered with proregtx v2. This patch aims to fix this.
What was done?
Store nVersion (legacy/bls) in CDeterministicMNState and CDeterministicMNStateDiff. As a side-effect this patch also changes the way nVersion behaves in CSimplifiedMNListEntry and CSimplifiedMNList (and imo in the right way). And as a yet another side-effect this also changes the way pubKeyOperator is stored in CDeterministicMNState and CDeterministicMNStateDiff (no need for post-v19-hf db migration anymore). Tweaked all the debug and rpc output to use these changes and display pubKeyOperator using the right scheme.
How Has This Been Tested?
n/a
Breaking Changes
Changes in CDeterministicMNState and CDeterministicMNStateDiff (technically) require migration but I skipped this part since we are going to re-hardfork testnet to test v19 migration again (which will require reindexing for v19 nodes anyway I think). Changes in CSimplifiedMNListEntry and CSimplifiedMNList might require attention of mobile teams.
Checklist:

[ ] I have performed a self-review of my own code
[ ] I have commented my code, particularly in hard-to-understand areas
[ ] I have added or updated relevant unit/integration/functional/e2e tests
[ ] I have made corresponding changes to the documentation

For repository code-owners and collaborators only

[ ] I have assigned this pull request to a milestone

Changes in CSimplifiedMNListEntry and CSimplifiedMNList might require attention of mobile teams.

@hashengineering Sounds like this may be something you want to look at


How to experiment with the custom dataset？

You have done a brilliant job. I would like to ask how to experiment with a custom dataset, I have already trained to get the YOLOX model, how should I add the tracker?

@snehitvaddi Thanks you very much for your suggestion! We have added a google colab demo. You can find the link in readme.

@ifzhang May I know how to train the custom dataset? As my datasets are COCO format and json annotation format. I do not have frame id and track id like MOT17 (the example in this repository). How do I create the custom dataset format? Could you please tell me how to do it as I am newbie in this field:(

Hi, @ImSuMyatNoe. Did you succeed in training your custom dataset. I also happen to have coco-annotated dataset with no frame_id and track_id. I hope you can share your steps if you managed to handle this. Thank you.

@ifzhang May I know how to train the custom dataset? As my datasets are COCO format and json annotation format. I do not have frame id and track id like MOT17 (the example in this repository). How do I create the custom dataset format? Could you please tell me how to do it as I am newbie in this field:(
Hi, @ImSuMyatNoe.Did you succeed in training your custom dataset.  If you are successful, can you share it with me?thank you very much。

Hi, @ImSuMyatNoe.Did you succeed in training your custom dataset.If you are successful, can you share it with me?？thank you very much。

Hi, @ImSuMyatNoe .Did you succeed in training your custom dataset.If you are successful, can you share it with me?？thank you very much。


[Feature Request] Separating presentation from validation

Summary
Currently React Stripe Elements are very monolithic, they contain both presentation and validation logic. Please consider separating the two so that developers can reuse their existing presentation components with Stripe's validation logic.
Other information
Context: I wanted to use the Material UI library for credit card forms, since the rest of my application uses it. As far as I can tell, this is not possible. As an alternative, I found your Example 2 which comes close to Material Design. However it is straight JavaScript and CSS code, which would take quite an effort to convert to React and JSS (the CSS in JS implementation used by Material UI).
These issues would all go away if we could use our preferred UI libraries with Stripe's validation logic. For example, we could call a Stripe API on every change event to check for errors. This would tremendously reduce the effort to keep our look and feel consistent with rest of our apps.

Hi @nareshbhatia. Thanks for the notes!
For PCI DSS SAQ A compatibility, you need Stripe to handle sensitive card information, which means the actual inputs for sensitive card information need to be hosted in Stripe iframes.
I'm not familiar with that particular library. However, while you won't be able to use their <Input> directly, you should be able to lightly wrap Stripe Elements with whatever other components you need. If there's something specific that's blocking that, please let us know!

Hi @jenan-stripe, thanks for the context. There is nothing blocking at the moment. It's just that we will have to put more effort into making our Stripe forms look & feel like the rest of our app. If anything, it would be helpful to provide example 2 translated as a React app. It would nicely complement react-stripe-elements.


Keep GitHub Actions up to date with GitHub's Dependabot

Fixes the warnings at the bottom right of
https://github.com/ut-code/utcode-learn/actions/runs/7624514500

https://docs.github.com/en/code-security/dependabot/working-with-dependabot/keeping-your-actions-up-to-date-with-dependabot
https://docs.github.com/en/code-security/dependabot/dependabot-version-updates/configuration-options-for-the-dependabot.yml-file#package-ecosystem

Thank you for your PR. To fix the warning, it seems that we just need to update the actions/setup-node version in our GitHub Actions workflows. Thank you for your effort and contribution.

@cclauss Thank you for your PR. To fix the warning, it seems that we just need to update the actions/setup-node version in our GitHub Actions workflows. Thank you for your effort and contribution.

This PR is an automated way to solve the problem for the current issue and future issues.  The manual process that you suggested is also a possibility.

This PR is an automated way to solve the problem for the current issue and any future issues. The manual process that you suggested is also a possibility.

I know that Dependabot is useful in some situation. While I see its value, reviewing and testing its automated PRs is little hard. As you know, currently, we are not using Dependabot for npm or other updates in this project. So I think it is more natural to just update the actions.


Update desktop-assume-referential-integrity.md

Adding reference to Fabric interaction and semantic models in direct lake mode.

@davidiseminger
Can you review the proposed changes?
Important: When the changes are ready for publication, adding a #sign-off comment is the best way to signal that the PR is ready for the review team to merge.
#label:"aq-pr-triaged"
@MicrosoftDocs/public-repo-pr-review-team

Thanks - signing off.
#sign-off


Peer Review

Peer Review for Nikhil Lalwani's website

The website looks easy to follow and the CSS/SASS is on point as the blog layout looks really good and the background colors as well. One thing to improve on is organizing the blog section on the website and adding more to the about page. Other than that, keep up the great work!

Pros: Your project looked overall really good

I really liked how you included a knock version of google. It shows your knowledge of python hacks.
I love the simplisitc theme of you website and the moving text that appear every once in awhile.
Cons:
Add some functionality to you about page maybe moving the images.
I also think that you could add some javascript game within your website or something that relates to you.

I love the theme of the website, the gradient of grey circles in the background are both non-distracting and pleasing to look at. The motivational quotes flying across the home screen is also fun.
But there is not much stuff to interact with, and the about me page feels a little boring.

Nikhil Lalwani

Skill
Mastered (Y/N)
Rank (1-4)
Ratio
Notes

Attendance
[ Y]
3.5
0.8
only absent once

Work Habits
[ Y]
3.8
0.85
usually on task

Behavior
[Y ]
4
0.95
Good

Timeliness
[ Y]
4
0.95
Always early

Tech Sense
[ Y]
4
0.95
very good with terminal and solving problems

Tech Talk
[ Y]
4
0.9
good

Tech Growth
[ Y]
3.8
0.8
some growth

Advocacy
[Y ]
4
0.9

Comm & Collab
[ Y]
4
0.9

Integrity
[ Y]
4
0.95
good

Organized
[ ]
4
0.9
is organized

Total
9 Y
43.1
9.845

Average

3.91
0.895

Skill
Mastered (Y/N)
Rank (1-4)
Ratio
Notes

Attendance
[ Y]
3.5
0.8
only absent once

Work Habits
[ Y]
3.8
0.85
usually on task

Behavior
[Y ]
4
0.95
Good

Timeliness
[ Y]
4
0.95
Always early

Tech Sense
[ Y]
4
0.95
very good with terminal and solving problems

Tech Talk
[ Y]
4
0.9
good

Tech Growth
[ Y]
3.8
0.8
some growth

Advocacy
[Y ]
4
0.9

Comm & Collab
[ Y]
4
0.9

Integrity
[ Y]
4
0.95
good

Organized
[ ]
4
0.9
is organized

Total
9 Y
43.1
9.845

Average

3.91
0.895


Error handling when network fails

Hi,
Actually, this is not a bug or issue.
I couldn't find the information regard to error handling when network fail. If I use streaming URL for playing radio, but for some reason, the network failed. Do RNTP callbacks or has a function to handle that?
I am kind of thinking to use NetInfo, and monitoring network status. However, I am not sure this is the perfect solution for handling this.
Any idea?

I think playback-error is what you're looking for.

@Guichaguri, I am running into an issue where the playback-error event is not being called, even when I use fake audio file URLs. For example in my registered events I have:
PVTrackPlayer.addEventListener('playback-error', (x) => console.log('playback error', x))

And elsewhere I load the TrackPlayer using:
await TrackPlayer.add({
  id,
  url: 'http://fakelink.not.real/example.mp1234',
  title,
  artist,
  artwork
})

But when I run that code, the playback-error event is never called.
Meanwhile I have another event listener registered for playback-state, and that is called on load and when I hit play/pause. On load, the playback-state says it is "ready", which seems incorrect to me, since it is trying to reach a non-existent file, I would think the state should be "error" or "none".
Is this a bug in the code? Or could I have something configured incorrectly?
Thanks for all your work on react-native-track-player :) it's great stuff