[Bug]: b5 not found on PATH

Current Behavior
The default b5 installation did not modify my PATH variable to include the b5 binaries.
Is the command line warning of the pip install sufficient, or would you like to include a hint in your installation description?
https://github.com/ll7/paf22/blob/f5b7536b4ac227ae78773ee81861d2395e30ad16/doc/01_general/02_installation.md?plain=1#L7
My terminal output:
$ pip install b5
Collecting b5
  Downloading b5-1.3.3-py3-none-any.whl (42 kB)
     |████████████████████████████████| 42 kB 2.7 MB/s
Collecting Jinja2<4.0.0,>=3.0.1
  Downloading Jinja2-3.1.2-py3-none-any.whl (133 kB)
     |████████████████████████████████| 133 kB 7.0 MB/s
Collecting packaging<22.0,>=21.3
  Downloading packaging-21.3-py3-none-any.whl (40 kB)
     |████████████████████████████████| 40 kB 4.1 MB/s
Collecting PyYAML<7.0,>=6.0
  Downloading PyYAML-6.0-cp38-cp38-manylinux_2_5_x86_64.manylinux1_x86_64.manylinux_2_12_x86_64.manylinux2010_x86_64.whl (701 kB)
     |████████████████████████████████| 701 kB 18.8 MB/s
Collecting MarkupSafe<3.0.0,>=2.0.1
  Downloading MarkupSafe-2.1.1-cp38-cp38-manylinux_2_17_x86_64.manylinux2014_x86_64.whl (25 kB)
Collecting termcolor<2.0.0,>=1.1.0
  Downloading termcolor-1.1.0.tar.gz (3.9 kB)
Collecting pyparsing!=3.0.5,>=2.0.2
  Downloading pyparsing-3.0.9-py3-none-any.whl (98 kB)
     |████████████████████████████████| 98 kB 28.2 MB/s
Building wheels for collected packages: termcolor
  Building wheel for termcolor (setup.py) ... done
  Created wheel for termcolor: filename=termcolor-1.1.0-py3-none-any.whl size=4830 sha256=1cd4fdba7b71f8be8136a3004b9b5b542844039367256287408de3671ad4cade
  Stored in directory: /home/luttkule/.cache/pip/wheels/a0/16/9c/5473df82468f958445479c59e784896fa24f4a5fc024b0f501
Successfully built termcolor
Installing collected packages: MarkupSafe, Jinja2, pyparsing, packaging, PyYAML, termcolor, b5
  WARNING: The scripts b5, b5-execute and b5-init are installed in '/home/luttkule/.local/bin' which is not on PATH.
  Consider adding this directory to PATH or, if you prefer to suppress this warning, use --no-warn-script-location.
Successfully installed Jinja2-3.1.2 MarkupSafe-2.1.1 PyYAML-6.0 b5-1.3.3 packaging-21.3 pyparsing-3.0.9 termcolor-1.1.0

$ b5 install
b5: command not found

Expected Behavior
Discuss if this issue is intentional, or you want to include a hint.
How to reproduce the issue
clean b5 install and usage.

@ll7 did you source your .bashrc after install / opened a new terminal?
Or did you mean that it should work without this and we should include a hint to do this?
For me, everything worked out of the box.

https://github.com/ll7/paf22/blob/main/doc/01_general/02_installation.md?plain=1#L7-L18
Does not mention that I should source my terminal after the pip install.
Additionally, if I don't modify my ~/.bashrc manually to include export PATH=$PATH:/home/luttkule/.local/bin I get a b5: command not found.

@ll7 can't reproduce your issue. Just tried with a clean Ubuntu installation in docker without sourcing or reopening terminal:
➜  ~ docker run -it ubuntu

Output
Unable to find image 'ubuntu:latest' locally
latest: Pulling from library/ubuntu
0509fae36eb0: Already exists
Digest: sha256:4b1d0c4a2d2aaf63b37111f34eb9fa89fa1bf53dd6e4ca954d47caebca4005c2
Status: Downloaded newer image for ubuntu:latest

root@b2c7ae46428a:/# apt-get update

Output
  Get:1 http://ports.ubuntu.com/ubuntu-ports jammy InRelease [270 kB]
  Get:2 http://ports.ubuntu.com/ubuntu-ports jammy-updates InRelease [114 kB]
  Get:3 http://ports.ubuntu.com/ubuntu-ports jammy-backports InRelease [99.8 kB]
  Get:4 http://ports.ubuntu.com/ubuntu-ports jammy-security InRelease [110 kB]
  Get:5 http://ports.ubuntu.com/ubuntu-ports jammy/main arm64 Packages [1758 kB]
  Get:6 http://ports.ubuntu.com/ubuntu-ports jammy/restricted arm64 Packages [24.2 kB]
  Get:7 http://ports.ubuntu.com/ubuntu-ports jammy/universe arm64 Packages [17.2 MB]
  Get:8 http://ports.ubuntu.com/ubuntu-ports jammy/multiverse arm64 Packages [224 kB]
  Get:9 http://ports.ubuntu.com/ubuntu-ports jammy-updates/restricted arm64 Packages [253 kB]
  Get:10 http://ports.ubuntu.com/ubuntu-ports jammy-updates/main arm64 Packages [880 kB]
  Get:11 http://ports.ubuntu.com/ubuntu-ports jammy-updates/multiverse arm64 Packages [2315 B]
  Get:12 http://ports.ubuntu.com/ubuntu-ports jammy-updates/universe arm64 Packages [829 kB]
  Get:13 http://ports.ubuntu.com/ubuntu-ports jammy-backports/universe arm64 Packages [7263 B]
  Get:14 http://ports.ubuntu.com/ubuntu-ports jammy-backports/main arm64 Packages [3184 B]
  Get:15 http://ports.ubuntu.com/ubuntu-ports jammy-security/universe arm64 Packages [644 kB]
  Get:16 http://ports.ubuntu.com/ubuntu-ports jammy-security/main arm64 Packages [584 kB]
  Get:17 http://ports.ubuntu.com/ubuntu-ports jammy-security/restricted arm64 Packages [230 kB]
  Fetched 23.2 MB in 20s (1164 kB/s)
  Reading package lists... Done

root@b2c7ae46428a:/# apt-get install python3 pip

Output
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Note, selecting 'python3-pip' instead of 'pip'
python3 is already the newest version (3.10.6-1~22.04).
The following additional packages will be installed:
  binutils binutils-aarch64-linux-gnu binutils-common build-essential bzip2
  ca-certificates cpp cpp-11 dirmngr dpkg-dev fakeroot fontconfig-config
  fonts-dejavu-core g++ g++-11 gcc gcc-11 gcc-11-base gnupg gnupg-l10n
  gnupg-utils gpg gpg-agent gpg-wks-client gpg-wks-server gpgconf gpgsm
  javascript-common libalgorithm-diff-perl libalgorithm-diff-xs-perl
  libalgorithm-merge-perl libasan6 libassuan0 libatomic1 libbinutils
  libbrotli1 libbsd0 libc-dev-bin libc-devtools libc6-dev libcc1-0
  libcrypt-dev libctf-nobfd0 libctf0 libdeflate0 libdpkg-perl libexpat1-dev
  libfakeroot libfile-fcntllock-perl libfontconfig1 libfreetype6 libgcc-11-dev
  libgd3 libgdbm-compat4 libgdbm6 libgomp1 libhwasan0 libisl23 libitm1
  libjbig0 libjpeg-turbo8 libjpeg8 libjs-jquery libjs-sphinxdoc
  libjs-underscore libksba8 libldap-2.5-0 libldap-common
  liblocale-gettext-perl liblsan0 libmd0 libmpc3 libmpfr6 libnpth0 libnsl-dev
  libperl5.34 libpng16-16 libpython3-dev libpython3.10 libpython3.10-dev
  libsasl2-2 libsasl2-modules libsasl2-modules-db libstdc++-11-dev libtiff5
  libtirpc-dev libtsan0 libubsan1 libwebp7 libx11-6 libx11-data libxau6
  libxcb1 libxdmcp6 libxpm4 linux-libc-dev lto-disabled-list make manpages
  manpages-dev netbase openssl patch perl perl-modules-5.34 pinentry-curses
  python3-dev python3-distutils python3-lib2to3 python3-pkg-resources
  python3-setuptools python3-wheel python3.10-dev rpcsvc-proto ucf xz-utils
  zlib1g-dev
Suggested packages:
  binutils-doc bzip2-doc cpp-doc gcc-11-locales dbus-user-session
  libpam-systemd pinentry-gnome3 tor debian-keyring gcc-11-doc gcc-multilib
  autoconf automake libtool flex bison gdb gcc-doc parcimonie xloadimage
  scdaemon apache2 | lighttpd | httpd glibc-doc git bzr libgd-tools gdbm-l10n
  libsasl2-modules-gssapi-mit | libsasl2-modules-gssapi-heimdal
  libsasl2-modules-ldap libsasl2-modules-otp libsasl2-modules-sql
  libstdc++-11-doc make-doc man-browser ed diffutils-doc perl-doc
  libterm-readline-gnu-perl | libterm-readline-perl-perl
  libtap-harness-archive-perl pinentry-doc python-setuptools-doc
The following NEW packages will be installed:
  binutils binutils-aarch64-linux-gnu binutils-common build-essential bzip2
  ca-certificates cpp cpp-11 dirmngr dpkg-dev fakeroot fontconfig-config
  fonts-dejavu-core g++ g++-11 gcc gcc-11 gcc-11-base gnupg gnupg-l10n
  gnupg-utils gpg gpg-agent gpg-wks-client gpg-wks-server gpgconf gpgsm
  javascript-common libalgorithm-diff-perl libalgorithm-diff-xs-perl
  libalgorithm-merge-perl libasan6 libassuan0 libatomic1 libbinutils
  libbrotli1 libbsd0 libc-dev-bin libc-devtools libc6-dev libcc1-0
  libcrypt-dev libctf-nobfd0 libctf0 libdeflate0 libdpkg-perl libexpat1-dev
  libfakeroot libfile-fcntllock-perl libfontconfig1 libfreetype6 libgcc-11-dev
  libgd3 libgdbm-compat4 libgdbm6 libgomp1 libhwasan0 libisl23 libitm1
  libjbig0 libjpeg-turbo8 libjpeg8 libjs-jquery libjs-sphinxdoc
  libjs-underscore libksba8 libldap-2.5-0 libldap-common
  liblocale-gettext-perl liblsan0 libmd0 libmpc3 libmpfr6 libnpth0 libnsl-dev
  libperl5.34 libpng16-16 libpython3-dev libpython3.10 libpython3.10-dev
  libsasl2-2 libsasl2-modules libsasl2-modules-db libstdc++-11-dev libtiff5
  libtirpc-dev libtsan0 libubsan1 libwebp7 libx11-6 libx11-data libxau6
  libxcb1 libxdmcp6 libxpm4 linux-libc-dev lto-disabled-list make manpages
  manpages-dev netbase openssl patch perl perl-modules-5.34 pinentry-curses
  python3-dev python3-distutils python3-lib2to3 python3-pip
  python3-pkg-resources python3-setuptools python3-wheel python3.10-dev
  rpcsvc-proto ucf xz-utils zlib1g-dev
0 upgraded, 118 newly installed, 0 to remove and 2 not upgraded.
Need to get 91.3 MB of archives.
After this operation, 318 MB of additional disk space will be used.
Do you want to continue?
(Reading database ... 5140 files and directories currently installed.)
Preparing to unpack .../000-liblocale-gettext-perl_1.07-4build3_arm64.deb ...
Unpacking liblocale-gettext-perl (1.07-4build3) ...
Selecting previously unselected package perl-modules-5.34.
Preparing to unpack .../001-perl-modules-5.34_5.34.0-3ubuntu1.1_all.deb ...
Unpacking perl-modules-5.34 (5.34.0-3ubuntu1.1) ...
Selecting previously unselected package libgdbm6:arm64.
Preparing to unpack .../002-libgdbm6_1.23-1_arm64.deb ...
Unpacking libgdbm6:arm64 (1.23-1) ...
Selecting previously unselected package libgdbm-compat4:arm64.
Preparing to unpack .../003-libgdbm-compat4_1.23-1_arm64.deb ...
Unpacking libgdbm-compat4:arm64 (1.23-1) ...
Selecting previously unselected package libperl5.34:arm64.
Preparing to unpack .../004-libperl5.34_5.34.0-3ubuntu1.1_arm64.deb ...
Unpacking libperl5.34:arm64 (5.34.0-3ubuntu1.1) ...
Selecting previously unselected package perl.
Preparing to unpack .../005-perl_5.34.0-3ubuntu1.1_arm64.deb ...
Unpacking perl (5.34.0-3ubuntu1.1) ...
Selecting previously unselected package openssl.
Preparing to unpack .../006-openssl_3.0.2-0ubuntu1.7_arm64.deb ...
Unpacking openssl (3.0.2-0ubuntu1.7) ...
Selecting previously unselected package ca-certificates.
Preparing to unpack .../007-ca-certificates_20211016_all.deb ...
Unpacking ca-certificates (20211016) ...
Selecting previously unselected package libmd0:arm64.
Preparing to unpack .../008-libmd0_1.0.4-1build1_arm64.deb ...
Unpacking libmd0:arm64 (1.0.4-1build1) ...
Selecting previously unselected package libbsd0:arm64.
Preparing to unpack .../009-libbsd0_0.11.5-1_arm64.deb ...
Unpacking libbsd0:arm64 (0.11.5-1) ...
Selecting previously unselected package netbase.
Preparing to unpack .../010-netbase_6.3_all.deb ...
Unpacking netbase (6.3) ...
Selecting previously unselected package python3-pkg-resources.
Preparing to unpack .../011-python3-pkg-resources_59.6.0-1.2_all.deb ...
Unpacking python3-pkg-resources (59.6.0-1.2) ...
Selecting previously unselected package ucf.
Preparing to unpack .../012-ucf_3.0043_all.deb ...
Moving old data out of the way
Unpacking ucf (3.0043) ...
Selecting previously unselected package libpng16-16:arm64.
Preparing to unpack .../013-libpng16-16_1.6.37-3build5_arm64.deb ...
Unpacking libpng16-16:arm64 (1.6.37-3build5) ...
Selecting previously unselected package libxau6:arm64.
Preparing to unpack .../014-libxau6_1%3a1.0.9-1build5_arm64.deb ...
Unpacking libxau6:arm64 (1:1.0.9-1build5) ...
Selecting previously unselected package libxdmcp6:arm64.
Preparing to unpack .../015-libxdmcp6_1%3a1.1.3-0ubuntu5_arm64.deb ...
Unpacking libxdmcp6:arm64 (1:1.1.3-0ubuntu5) ...
Selecting previously unselected package libxcb1:arm64.
Preparing to unpack .../016-libxcb1_1.14-3ubuntu3_arm64.deb ...
Unpacking libxcb1:arm64 (1.14-3ubuntu3) ...
Selecting previously unselected package libx11-data.
Preparing to unpack .../017-libx11-data_2%3a1.7.5-1_all.deb ...
Unpacking libx11-data (2:1.7.5-1) ...
Selecting previously unselected package libx11-6:arm64.
Preparing to unpack .../018-libx11-6_2%3a1.7.5-1_arm64.deb ...
Unpacking libx11-6:arm64 (2:1.7.5-1) ...
Selecting previously unselected package manpages.
Preparing to unpack .../019-manpages_5.10-1ubuntu1_all.deb ...
Unpacking manpages (5.10-1ubuntu1) ...
Selecting previously unselected package xz-utils.
Preparing to unpack .../020-xz-utils_5.2.5-2ubuntu1_arm64.deb ...
Unpacking xz-utils (5.2.5-2ubuntu1) ...
Selecting previously unselected package binutils-common:arm64.
Preparing to unpack .../021-binutils-common_2.38-4ubuntu2_arm64.deb ...
Unpacking binutils-common:arm64 (2.38-4ubuntu2) ...
Selecting previously unselected package libbinutils:arm64.
Preparing to unpack .../022-libbinutils_2.38-4ubuntu2_arm64.deb ...
Unpacking libbinutils:arm64 (2.38-4ubuntu2) ...
Selecting previously unselected package libctf-nobfd0:arm64.
Preparing to unpack .../023-libctf-nobfd0_2.38-4ubuntu2_arm64.deb ...
Unpacking libctf-nobfd0:arm64 (2.38-4ubuntu2) ...
Selecting previously unselected package libctf0:arm64.
Preparing to unpack .../024-libctf0_2.38-4ubuntu2_arm64.deb ...
Unpacking libctf0:arm64 (2.38-4ubuntu2) ...
Selecting previously unselected package binutils-aarch64-linux-gnu.
Preparing to unpack .../025-binutils-aarch64-linux-gnu_2.38-4ubuntu2_arm64.deb ...
Unpacking binutils-aarch64-linux-gnu (2.38-4ubuntu2) ...
Selecting previously unselected package binutils.
Preparing to unpack .../026-binutils_2.38-4ubuntu2_arm64.deb ...
Unpacking binutils (2.38-4ubuntu2) ...
Selecting previously unselected package libc-dev-bin.
Preparing to unpack .../027-libc-dev-bin_2.35-0ubuntu3.1_arm64.deb ...
Unpacking libc-dev-bin (2.35-0ubuntu3.1) ...
Selecting previously unselected package linux-libc-dev:arm64.
Preparing to unpack .../028-linux-libc-dev_5.15.0-56.62_arm64.deb ...
Unpacking linux-libc-dev:arm64 (5.15.0-56.62) ...
Selecting previously unselected package libcrypt-dev:arm64.
Preparing to unpack .../029-libcrypt-dev_1%3a4.4.27-1_arm64.deb ...
Unpacking libcrypt-dev:arm64 (1:4.4.27-1) ...
Selecting previously unselected package rpcsvc-proto.
Preparing to unpack .../030-rpcsvc-proto_1.4.2-0ubuntu6_arm64.deb ...
Unpacking rpcsvc-proto (1.4.2-0ubuntu6) ...
Selecting previously unselected package libtirpc-dev:arm64.
Preparing to unpack .../031-libtirpc-dev_1.3.2-2ubuntu0.1_arm64.deb ...
Unpacking libtirpc-dev:arm64 (1.3.2-2ubuntu0.1) ...
Selecting previously unselected package libnsl-dev:arm64.
Preparing to unpack .../032-libnsl-dev_1.3.0-2build2_arm64.deb ...
Unpacking libnsl-dev:arm64 (1.3.0-2build2) ...
Selecting previously unselected package libc6-dev:arm64.
Preparing to unpack .../033-libc6-dev_2.35-0ubuntu3.1_arm64.deb ...
Unpacking libc6-dev:arm64 (2.35-0ubuntu3.1) ...
Selecting previously unselected package gcc-11-base:arm64.
Preparing to unpack .../034-gcc-11-base_11.3.0-1ubuntu1~22.04_arm64.deb ...
Unpacking gcc-11-base:arm64 (11.3.0-1ubuntu1~22.04) ...
Selecting previously unselected package libisl23:arm64.
Preparing to unpack .../035-libisl23_0.24-2build1_arm64.deb ...
Unpacking libisl23:arm64 (0.24-2build1) ...
Selecting previously unselected package libmpfr6:arm64.
Preparing to unpack .../036-libmpfr6_4.1.0-3build3_arm64.deb ...
Unpacking libmpfr6:arm64 (4.1.0-3build3) ...
Selecting previously unselected package libmpc3:arm64.
Preparing to unpack .../037-libmpc3_1.2.1-2build1_arm64.deb ...
Unpacking libmpc3:arm64 (1.2.1-2build1) ...
Selecting previously unselected package cpp-11.
Preparing to unpack .../038-cpp-11_11.3.0-1ubuntu1~22.04_arm64.deb ...
Unpacking cpp-11 (11.3.0-1ubuntu1~22.04) ...
Selecting previously unselected package cpp.
Preparing to unpack .../039-cpp_4%3a11.2.0-1ubuntu1_arm64.deb ...
Unpacking cpp (4:11.2.0-1ubuntu1) ...
Selecting previously unselected package libcc1-0:arm64.
Preparing to unpack .../040-libcc1-0_12.1.0-2ubuntu1~22.04_arm64.deb ...
Unpacking libcc1-0:arm64 (12.1.0-2ubuntu1~22.04) ...
Selecting previously unselected package libgomp1:arm64.
Preparing to unpack .../041-libgomp1_12.1.0-2ubuntu1~22.04_arm64.deb ...
Unpacking libgomp1:arm64 (12.1.0-2ubuntu1~22.04) ...
Selecting previously unselected package libitm1:arm64.
Preparing to unpack .../042-libitm1_12.1.0-2ubuntu1~22.04_arm64.deb ...
Unpacking libitm1:arm64 (12.1.0-2ubuntu1~22.04) ...
Selecting previously unselected package libatomic1:arm64.
Preparing to unpack .../043-libatomic1_12.1.0-2ubuntu1~22.04_arm64.deb ...
Unpacking libatomic1:arm64 (12.1.0-2ubuntu1~22.04) ...
Selecting previously unselected package libasan6:arm64.
Preparing to unpack .../044-libasan6_11.3.0-1ubuntu1~22.04_arm64.deb ...
Unpacking libasan6:arm64 (11.3.0-1ubuntu1~22.04) ...
Selecting previously unselected package liblsan0:arm64.
Preparing to unpack .../045-liblsan0_12.1.0-2ubuntu1~22.04_arm64.deb ...
Unpacking liblsan0:arm64 (12.1.0-2ubuntu1~22.04) ...
Selecting previously unselected package libtsan0:arm64.
Preparing to unpack .../046-libtsan0_11.3.0-1ubuntu1~22.04_arm64.deb ...
Unpacking libtsan0:arm64 (11.3.0-1ubuntu1~22.04) ...
Selecting previously unselected package libubsan1:arm64.
Preparing to unpack .../047-libubsan1_12.1.0-2ubuntu1~22.04_arm64.deb ...
Unpacking libubsan1:arm64 (12.1.0-2ubuntu1~22.04) ...
Selecting previously unselected package libhwasan0:arm64.
Preparing to unpack .../048-libhwasan0_12.1.0-2ubuntu1~22.04_arm64.deb ...
Unpacking libhwasan0:arm64 (12.1.0-2ubuntu1~22.04) ...
Selecting previously unselected package libgcc-11-dev:arm64.
Preparing to unpack .../049-libgcc-11-dev_11.3.0-1ubuntu1~22.04_arm64.deb ...
Unpacking libgcc-11-dev:arm64 (11.3.0-1ubuntu1~22.04) ...
Selecting previously unselected package gcc-11.
Preparing to unpack .../050-gcc-11_11.3.0-1ubuntu1~22.04_arm64.deb ...
Unpacking gcc-11 (11.3.0-1ubuntu1~22.04) ...
Selecting previously unselected package gcc.
Preparing to unpack .../051-gcc_4%3a11.2.0-1ubuntu1_arm64.deb ...
Unpacking gcc (4:11.2.0-1ubuntu1) ...
Selecting previously unselected package libstdc++-11-dev:arm64.
Preparing to unpack .../052-libstdc++-11-dev_11.3.0-1ubuntu1~22.04_arm64.deb ...
Unpacking libstdc++-11-dev:arm64 (11.3.0-1ubuntu1~22.04) ...
Selecting previously unselected package g++-11.
Preparing to unpack .../053-g++-11_11.3.0-1ubuntu1~22.04_arm64.deb ...
Unpacking g++-11 (11.3.0-1ubuntu1~22.04) ...
Selecting previously unselected package g++.
Preparing to unpack .../054-g++_4%3a11.2.0-1ubuntu1_arm64.deb ...
Unpacking g++ (4:11.2.0-1ubuntu1) ...
Selecting previously unselected package make.
Preparing to unpack .../055-make_4.3-4.1build1_arm64.deb ...
Unpacking make (4.3-4.1build1) ...
Selecting previously unselected package libdpkg-perl.
Preparing to unpack .../056-libdpkg-perl_1.21.1ubuntu2.1_all.deb ...
Unpacking libdpkg-perl (1.21.1ubuntu2.1) ...
Selecting previously unselected package bzip2.
Preparing to unpack .../057-bzip2_1.0.8-5build1_arm64.deb ...
Unpacking bzip2 (1.0.8-5build1) ...
Selecting previously unselected package patch.
Preparing to unpack .../058-patch_2.7.6-7build2_arm64.deb ...
Unpacking patch (2.7.6-7build2) ...
Selecting previously unselected package lto-disabled-list.
Preparing to unpack .../059-lto-disabled-list_24_all.deb ...
Unpacking lto-disabled-list (24) ...
Selecting previously unselected package dpkg-dev.
Preparing to unpack .../060-dpkg-dev_1.21.1ubuntu2.1_all.deb ...
Unpacking dpkg-dev (1.21.1ubuntu2.1) ...
Selecting previously unselected package build-essential.
Preparing to unpack .../061-build-essential_12.9ubuntu3_arm64.deb ...
Unpacking build-essential (12.9ubuntu3) ...
Selecting previously unselected package libassuan0:arm64.
Preparing to unpack .../062-libassuan0_2.5.5-1build1_arm64.deb ...
Unpacking libassuan0:arm64 (2.5.5-1build1) ...
Selecting previously unselected package gpgconf.
Preparing to unpack .../063-gpgconf_2.2.27-3ubuntu2.1_arm64.deb ...
Unpacking gpgconf (2.2.27-3ubuntu2.1) ...
Selecting previously unselected package libksba8:arm64.
Preparing to unpack .../064-libksba8_1.6.0-2ubuntu0.1_arm64.deb ...
Unpacking libksba8:arm64 (1.6.0-2ubuntu0.1) ...
Selecting previously unselected package libsasl2-modules-db:arm64.
Preparing to unpack .../065-libsasl2-modules-db_2.1.27+dfsg2-3ubuntu1_arm64.deb ...
Unpacking libsasl2-modules-db:arm64 (2.1.27+dfsg2-3ubuntu1) ...
Selecting previously unselected package libsasl2-2:arm64.
Preparing to unpack .../066-libsasl2-2_2.1.27+dfsg2-3ubuntu1_arm64.deb ...
Unpacking libsasl2-2:arm64 (2.1.27+dfsg2-3ubuntu1) ...
Selecting previously unselected package libldap-2.5-0:arm64.
Preparing to unpack .../067-libldap-2.5-0_2.5.13+dfsg-0ubuntu<IP_ADDRESS>_arm64.deb ...
Unpacking libldap-2.5-0:arm64 (2.5.13+dfsg-0ubuntu<IP_ADDRESS>) ...
Selecting previously unselected package libnpth0:arm64.
Preparing to unpack .../068-libnpth0_1.6-3build2_arm64.deb ...
Unpacking libnpth0:arm64 (1.6-3build2) ...
Selecting previously unselected package dirmngr.
Preparing to unpack .../069-dirmngr_2.2.27-3ubuntu2.1_arm64.deb ...
Unpacking dirmngr (2.2.27-3ubuntu2.1) ...
Selecting previously unselected package libfakeroot:arm64.
Preparing to unpack .../070-libfakeroot_1.28-1ubuntu1_arm64.deb ...
Unpacking libfakeroot:arm64 (1.28-1ubuntu1) ...
Selecting previously unselected package fakeroot.
Preparing to unpack .../071-fakeroot_1.28-1ubuntu1_arm64.deb ...
Unpacking fakeroot (1.28-1ubuntu1) ...
Selecting previously unselected package fonts-dejavu-core.
Preparing to unpack .../072-fonts-dejavu-core_2.37-2build1_all.deb ...
Unpacking fonts-dejavu-core (2.37-2build1) ...
Selecting previously unselected package fontconfig-config.
Preparing to unpack .../073-fontconfig-config_2.13.1-4.2ubuntu5_all.deb ...
Unpacking fontconfig-config (2.13.1-4.2ubuntu5) ...
Selecting previously unselected package gnupg-l10n.
Preparing to unpack .../074-gnupg-l10n_2.2.27-3ubuntu2.1_all.deb ...
Unpacking gnupg-l10n (2.2.27-3ubuntu2.1) ...
Selecting previously unselected package gnupg-utils.
Preparing to unpack .../075-gnupg-utils_2.2.27-3ubuntu2.1_arm64.deb ...
Unpacking gnupg-utils (2.2.27-3ubuntu2.1) ...
Selecting previously unselected package gpg.
Preparing to unpack .../076-gpg_2.2.27-3ubuntu2.1_arm64.deb ...
Unpacking gpg (2.2.27-3ubuntu2.1) ...
Selecting previously unselected package pinentry-curses.
Preparing to unpack .../077-pinentry-curses_1.1.1-1build2_arm64.deb ...
Unpacking pinentry-curses (1.1.1-1build2) ...
Selecting previously unselected package gpg-agent.
Preparing to unpack .../078-gpg-agent_2.2.27-3ubuntu2.1_arm64.deb ...
Unpacking gpg-agent (2.2.27-3ubuntu2.1) ...
Selecting previously unselected package gpg-wks-client.
Preparing to unpack .../079-gpg-wks-client_2.2.27-3ubuntu2.1_arm64.deb ...
Unpacking gpg-wks-client (2.2.27-3ubuntu2.1) ...
Selecting previously unselected package gpg-wks-server.
Preparing to unpack .../080-gpg-wks-server_2.2.27-3ubuntu2.1_arm64.deb ...
Unpacking gpg-wks-server (2.2.27-3ubuntu2.1) ...
Selecting previously unselected package gpgsm.
Preparing to unpack .../081-gpgsm_2.2.27-3ubuntu2.1_arm64.deb ...
Unpacking gpgsm (2.2.27-3ubuntu2.1) ...
Selecting previously unselected package gnupg.
Preparing to unpack .../082-gnupg_2.2.27-3ubuntu2.1_all.deb ...
Unpacking gnupg (2.2.27-3ubuntu2.1) ...
Selecting previously unselected package javascript-common.
Preparing to unpack .../083-javascript-common_11+nmu1_all.deb ...
Unpacking javascript-common (11+nmu1) ...
Selecting previously unselected package libalgorithm-diff-perl.
Preparing to unpack .../084-libalgorithm-diff-perl_1.201-1_all.deb ...
Unpacking libalgorithm-diff-perl (1.201-1) ...
Selecting previously unselected package libalgorithm-diff-xs-perl.
Preparing to unpack .../085-libalgorithm-diff-xs-perl_0.04-6build3_arm64.deb ...
Unpacking libalgorithm-diff-xs-perl (0.04-6build3) ...
Selecting previously unselected package libalgorithm-merge-perl.
Preparing to unpack .../086-libalgorithm-merge-perl_0.08-3_all.deb ...
Unpacking libalgorithm-merge-perl (0.08-3) ...
Selecting previously unselected package libbrotli1:arm64.
Preparing to unpack .../087-libbrotli1_1.0.9-2build6_arm64.deb ...
Unpacking libbrotli1:arm64 (1.0.9-2build6) ...
Selecting previously unselected package libfreetype6:arm64.
Preparing to unpack .../088-libfreetype6_2.11.1+dfsg-1ubuntu0.1_arm64.deb ...
Unpacking libfreetype6:arm64 (2.11.1+dfsg-1ubuntu0.1) ...
Selecting previously unselected package libfontconfig1:arm64.
Preparing to unpack .../089-libfontconfig1_2.13.1-4.2ubuntu5_arm64.deb ...
Unpacking libfontconfig1:arm64 (2.13.1-4.2ubuntu5) ...
Selecting previously unselected package libjpeg-turbo8:arm64.
Preparing to unpack .../090-libjpeg-turbo8_2.1.2-0ubuntu1_arm64.deb ...
Unpacking libjpeg-turbo8:arm64 (2.1.2-0ubuntu1) ...
Selecting previously unselected package libjpeg8:arm64.
Preparing to unpack .../091-libjpeg8_8c-2ubuntu10_arm64.deb ...
Unpacking libjpeg8:arm64 (8c-2ubuntu10) ...
Selecting previously unselected package libdeflate0:arm64.
Preparing to unpack .../092-libdeflate0_1.10-2_arm64.deb ...
Unpacking libdeflate0:arm64 (1.10-2) ...
Selecting previously unselected package libjbig0:arm64.
Preparing to unpack .../093-libjbig0_2.1-3.1ubuntu<IP_ADDRESS>_arm64.deb ...
Unpacking libjbig0:arm64 (2.1-3.1ubuntu<IP_ADDRESS>) ...
Selecting previously unselected package libwebp7:arm64.
Preparing to unpack .../094-libwebp7_1.2.2-2_arm64.deb ...
Unpacking libwebp7:arm64 (1.2.2-2) ...
Selecting previously unselected package libtiff5:arm64.
Preparing to unpack .../095-libtiff5_4.3.0-6ubuntu0.3_arm64.deb ...
Unpacking libtiff5:arm64 (4.3.0-6ubuntu0.3) ...
Selecting previously unselected package libxpm4:arm64.
Preparing to unpack .../096-libxpm4_1%3a3.5.12-1build2_arm64.deb ...
Unpacking libxpm4:arm64 (1:3.5.12-1build2) ...
Selecting previously unselected package libgd3:arm64.
Preparing to unpack .../097-libgd3_2.3.0-2ubuntu2_arm64.deb ...
Unpacking libgd3:arm64 (2.3.0-2ubuntu2) ...
Selecting previously unselected package libc-devtools.
Preparing to unpack .../098-libc-devtools_2.35-0ubuntu3.1_arm64.deb ...
Unpacking libc-devtools (2.35-0ubuntu3.1) ...
Selecting previously unselected package libexpat1-dev:arm64.
Preparing to unpack .../099-libexpat1-dev_2.4.7-1ubuntu0.2_arm64.deb ...
Unpacking libexpat1-dev:arm64 (2.4.7-1ubuntu0.2) ...
Selecting previously unselected package libfile-fcntllock-perl.
Preparing to unpack .../100-libfile-fcntllock-perl_0.22-3build7_arm64.deb ...
Unpacking libfile-fcntllock-perl (0.22-3build7) ...
Selecting previously unselected package libjs-jquery.
Preparing to unpack .../101-libjs-jquery_3.6.0+dfsg+~3.5.13-1_all.deb ...
Unpacking libjs-jquery (3.6.0+dfsg+~3.5.13-1) ...
Selecting previously unselected package libjs-underscore.
Preparing to unpack .../102-libjs-underscore_1.13.2~dfsg-2_all.deb ...
Unpacking libjs-underscore (1.13.2~dfsg-2) ...
Selecting previously unselected package libjs-sphinxdoc.
Preparing to unpack .../103-libjs-sphinxdoc_4.3.2-1_all.deb ...
Unpacking libjs-sphinxdoc (4.3.2-1) ...
Selecting previously unselected package libldap-common.
Preparing to unpack .../104-libldap-common_2.5.13+dfsg-0ubuntu<IP_ADDRESS>_all.deb ...
Unpacking libldap-common (2.5.13+dfsg-0ubuntu<IP_ADDRESS>) ...
Selecting previously unselected package libpython3.10:arm64.
Preparing to unpack .../105-libpython3.10_3.10.6-1~22.04.1_arm64.deb ...
Unpacking libpython3.10:arm64 (3.10.6-1~22.04.1) ...
Selecting previously unselected package zlib1g-dev:arm64.
Preparing to unpack .../106-zlib1g-dev_1%3a1.2.11.dfsg-2ubuntu9.2_arm64.deb ...
Unpacking zlib1g-dev:arm64 (1:1.2.11.dfsg-2ubuntu9.2) ...
Selecting previously unselected package libpython3.10-dev:arm64.
Preparing to unpack .../107-libpython3.10-dev_3.10.6-1~22.04.1_arm64.deb ...
Unpacking libpython3.10-dev:arm64 (3.10.6-1~22.04.1) ...
Selecting previously unselected package libpython3-dev:arm64.
Preparing to unpack .../108-libpython3-dev_3.10.6-1~22.04_arm64.deb ...
Unpacking libpython3-dev:arm64 (3.10.6-1~22.04) ...
Selecting previously unselected package libsasl2-modules:arm64.
Preparing to unpack .../109-libsasl2-modules_2.1.27+dfsg2-3ubuntu1_arm64.deb ...
Unpacking libsasl2-modules:arm64 (2.1.27+dfsg2-3ubuntu1) ...
Selecting previously unselected package manpages-dev.
Preparing to unpack .../110-manpages-dev_5.10-1ubuntu1_all.deb ...
Unpacking manpages-dev (5.10-1ubuntu1) ...
Selecting previously unselected package python3.10-dev.
Preparing to unpack .../111-python3.10-dev_3.10.6-1~22.04.1_arm64.deb ...
Unpacking python3.10-dev (3.10.6-1~22.04.1) ...
Selecting previously unselected package python3-lib2to3.
Preparing to unpack .../112-python3-lib2to3_3.10.6-1~22.04_all.deb ...
Unpacking python3-lib2to3 (3.10.6-1~22.04) ...
Selecting previously unselected package python3-distutils.
Preparing to unpack .../113-python3-distutils_3.10.6-1~22.04_all.deb ...
Unpacking python3-distutils (3.10.6-1~22.04) ...
Selecting previously unselected package python3-dev.
Preparing to unpack .../114-python3-dev_3.10.6-1~22.04_arm64.deb ...
Unpacking python3-dev (3.10.6-1~22.04) ...
Selecting previously unselected package python3-setuptools.
Preparing to unpack .../115-python3-setuptools_59.6.0-1.2_all.deb ...
Unpacking python3-setuptools (59.6.0-1.2) ...
Selecting previously unselected package python3-wheel.
Preparing to unpack .../116-python3-wheel_0.37.1-2_all.deb ...
Unpacking python3-wheel (0.37.1-2) ...
Selecting previously unselected package python3-pip.
Preparing to unpack .../117-python3-pip_22.0.2+dfsg-1_all.deb ...
Unpacking python3-pip (22.0.2+dfsg-1) ...
Setting up python3-pkg-resources (59.6.0-1.2) ...
Setting up libksba8:arm64 (1.6.0-2ubuntu0.1) ...
Setting up javascript-common (11+nmu1) ...
Setting up gcc-11-base:arm64 (11.3.0-1ubuntu1~22.04) ...
Setting up libpython3.10:arm64 (3.10.6-1~22.04.1) ...
Setting up libxau6:arm64 (1:1.0.9-1build5) ...
Setting up lto-disabled-list (24) ...
Setting up manpages (5.10-1ubuntu1) ...
Setting up libbrotli1:arm64 (1.0.9-2build6) ...
Setting up libsasl2-modules:arm64 (2.1.27+dfsg2-3ubuntu1) ...
Setting up binutils-common:arm64 (2.38-4ubuntu2) ...
Setting up libdeflate0:arm64 (1.10-2) ...
Setting up linux-libc-dev:arm64 (5.15.0-56.62) ...
Setting up libctf-nobfd0:arm64 (2.38-4ubuntu2) ...
Setting up libnpth0:arm64 (1.6-3build2) ...
Setting up libassuan0:arm64 (2.5.5-1build1) ...
Setting up libgomp1:arm64 (12.1.0-2ubuntu1~22.04) ...
Setting up perl-modules-5.34 (5.34.0-3ubuntu1.1) ...
Setting up bzip2 (1.0.8-5build1) ...
Setting up libldap-common (2.5.13+dfsg-0ubuntu<IP_ADDRESS>) ...
Setting up libjbig0:arm64 (2.1-3.1ubuntu<IP_ADDRESS>) ...
Setting up libfakeroot:arm64 (1.28-1ubuntu1) ...
Setting up libasan6:arm64 (11.3.0-1ubuntu1~22.04) ...
Setting up libsasl2-modules-db:arm64 (2.1.27+dfsg2-3ubuntu1) ...
Setting up fakeroot (1.28-1ubuntu1) ...
update-alternatives: using /usr/bin/fakeroot-sysv to provide /usr/bin/fakeroot (fakeroot) in auto mode
update-alternatives: warning: skip creation of /usr/share/man/man1/fakeroot.1.gz because associated file /usr/share/man/man1/fakeroot-sysv.1.gz (of link group fakeroot) doesn't exist
update-alternatives: warning: skip creation of /usr/share/man/man1/faked.1.gz because associated file /usr/share/man/man1/faked-sysv.1.gz (of link group fakeroot) doesn't exist
update-alternatives: warning: skip creation of /usr/share/man/es/man1/fakeroot.1.gz because associated file /usr/share/man/es/man1/fakeroot-sysv.1.gz (of link group fakeroot) doesn't exist
update-alternatives: warning: skip creation of /usr/share/man/es/man1/faked.1.gz because associated file /usr/share/man/es/man1/faked-sysv.1.gz (of link group fakeroot) doesn't exist
update-alternatives: warning: skip creation of /usr/share/man/fr/man1/fakeroot.1.gz because associated file /usr/share/man/fr/man1/fakeroot-sysv.1.gz (of link group fakeroot) doesn't exist
update-alternatives: warning: skip creation of /usr/share/man/fr/man1/faked.1.gz because associated file /usr/share/man/fr/man1/faked-sysv.1.gz (of link group fakeroot) doesn't exist
update-alternatives: warning: skip creation of /usr/share/man/sv/man1/fakeroot.1.gz because associated file /usr/share/man/sv/man1/fakeroot-sysv.1.gz (of link group fakeroot) doesn't exist
update-alternatives: warning: skip creation of /usr/share/man/sv/man1/faked.1.gz because associated file /usr/share/man/sv/man1/faked-sysv.1.gz (of link group fakeroot) doesn't exist
Setting up libtirpc-dev:arm64 (1.3.2-2ubuntu0.1) ...
Setting up rpcsvc-proto (1.4.2-0ubuntu6) ...
Setting up libx11-data (2:1.7.5-1) ...
Setting up make (4.3-4.1build1) ...
Setting up libmpfr6:arm64 (4.1.0-3build3) ...
Setting up gnupg-l10n (2.2.27-3ubuntu2.1) ...
Setting up xz-utils (5.2.5-2ubuntu1) ...
update-alternatives: using /usr/bin/xz to provide /usr/bin/lzma (lzma) in auto mode
update-alternatives: warning: skip creation of /usr/share/man/man1/lzma.1.gz because associated file /usr/share/man/man1/xz.1.gz (of link group lzma) doesn't exist
update-alternatives: warning: skip creation of /usr/share/man/man1/unlzma.1.gz because associated file /usr/share/man/man1/unxz.1.gz (of link group lzma) doesn't exist
update-alternatives: warning: skip creation of /usr/share/man/man1/lzcat.1.gz because associated file /usr/share/man/man1/xzcat.1.gz (of link group lzma) doesn't exist
update-alternatives: warning: skip creation of /usr/share/man/man1/lzmore.1.gz because associated file /usr/share/man/man1/xzmore.1.gz (of link group lzma) doesn't exist
update-alternatives: warning: skip creation of /usr/share/man/man1/lzless.1.gz because associated file /usr/share/man/man1/xzless.1.gz (of link group lzma) doesn't exist
update-alternatives: warning: skip creation of /usr/share/man/man1/lzdiff.1.gz because associated file /usr/share/man/man1/xzdiff.1.gz (of link group lzma) doesn't exist
update-alternatives: warning: skip creation of /usr/share/man/man1/lzcmp.1.gz because associated file /usr/share/man/man1/xzcmp.1.gz (of link group lzma) doesn't exist
update-alternatives: warning: skip creation of /usr/share/man/man1/lzgrep.1.gz because associated file /usr/share/man/man1/xzgrep.1.gz (of link group lzma) doesn't exist
update-alternatives: warning: skip creation of /usr/share/man/man1/lzegrep.1.gz because associated file /usr/share/man/man1/xzegrep.1.gz (of link group lzma) doesn't exist
update-alternatives: warning: skip creation of /usr/share/man/man1/lzfgrep.1.gz because associated file /usr/share/man/man1/xzfgrep.1.gz (of link group lzma) doesn't exist
Setting up libpng16-16:arm64 (1.6.37-3build5) ...
Setting up libmpc3:arm64 (1.2.1-2build1) ...
Setting up libatomic1:arm64 (12.1.0-2ubuntu1~22.04) ...
Setting up patch (2.7.6-7build2) ...
Setting up fonts-dejavu-core (2.37-2build1) ...
Setting up ucf (3.0043) ...
debconf: unable to initialize frontend: Dialog
debconf: (No usable dialog-like program is installed, so the dialog based frontend cannot be used. at /usr/share/perl5/Debconf/FrontEnd/Dialog.pm line 78.)
debconf: falling back to frontend: Readline
Setting up libjpeg-turbo8:arm64 (2.1.2-0ubuntu1) ...
Setting up libsasl2-2:arm64 (2.1.27+dfsg2-3ubuntu1) ...
Setting up libwebp7:arm64 (1.2.2-2) ...
Setting up libubsan1:arm64 (12.1.0-2ubuntu1~22.04) ...
Setting up libmd0:arm64 (1.0.4-1build1) ...
Setting up libnsl-dev:arm64 (1.3.0-2build2) ...
Setting up libhwasan0:arm64 (12.1.0-2ubuntu1~22.04) ...
Setting up libcrypt-dev:arm64 (1:4.4.27-1) ...
Setting up gpgconf (2.2.27-3ubuntu2.1) ...
Setting up netbase (6.3) ...
Setting up libjs-jquery (3.6.0+dfsg+~3.5.13-1) ...
Setting up libbinutils:arm64 (2.38-4ubuntu2) ...
Setting up libisl23:arm64 (0.24-2build1) ...
Setting up libc-dev-bin (2.35-0ubuntu3.1) ...
Setting up openssl (3.0.2-0ubuntu1.7) ...
Setting up libbsd0:arm64 (0.11.5-1) ...
Setting up python3-lib2to3 (3.10.6-1~22.04) ...
Setting up libcc1-0:arm64 (12.1.0-2ubuntu1~22.04) ...
Setting up liblocale-gettext-perl (1.07-4build3) ...
Setting up gpg (2.2.27-3ubuntu2.1) ...
Setting up liblsan0:arm64 (12.1.0-2ubuntu1~22.04) ...
Setting up libitm1:arm64 (12.1.0-2ubuntu1~22.04) ...
Setting up libgdbm6:arm64 (1.23-1) ...
Setting up libjs-underscore (1.13.2~dfsg-2) ...
Setting up gnupg-utils (2.2.27-3ubuntu2.1) ...
Setting up libtsan0:arm64 (11.3.0-1ubuntu1~22.04) ...
Setting up libctf0:arm64 (2.38-4ubuntu2) ...
Setting up libjpeg8:arm64 (8c-2ubuntu10) ...
Setting up python3-distutils (3.10.6-1~22.04) ...
Setting up pinentry-curses (1.1.1-1build2) ...
Setting up cpp-11 (11.3.0-1ubuntu1~22.04) ...
Setting up manpages-dev (5.10-1ubuntu1) ...
Setting up libxdmcp6:arm64 (1:1.1.3-0ubuntu5) ...
Setting up libxcb1:arm64 (1.14-3ubuntu3) ...
Setting up gpg-agent (2.2.27-3ubuntu2.1) ...
Setting up python3-setuptools (59.6.0-1.2) ...
Setting up fontconfig-config (2.13.1-4.2ubuntu5) ...
Setting up gpgsm (2.2.27-3ubuntu2.1) ...
Setting up binutils-aarch64-linux-gnu (2.38-4ubuntu2) ...
Setting up binutils (2.38-4ubuntu2) ...
Setting up python3-wheel (0.37.1-2) ...
Setting up libldap-2.5-0:arm64 (2.5.13+dfsg-0ubuntu<IP_ADDRESS>) ...
Setting up dirmngr (2.2.27-3ubuntu2.1) ...
Setting up ca-certificates (20211016) ...
debconf: unable to initialize frontend: Dialog
debconf: (No usable dialog-like program is installed, so the dialog based frontend cannot be used. at /usr/share/perl5/Debconf/FrontEnd/Dialog.pm line 78.)
debconf: falling back to frontend: Readline
Updating certificates in /etc/ssl/certs...
127 added, 0 removed; done.
Setting up libfreetype6:arm64 (2.11.1+dfsg-1ubuntu0.1) ...
Setting up libgdbm-compat4:arm64 (1.23-1) ...
Setting up python3-pip (22.0.2+dfsg-1) ...
Setting up libjs-sphinxdoc (4.3.2-1) ...
Setting up gpg-wks-server (2.2.27-3ubuntu2.1) ...
Setting up libgcc-11-dev:arm64 (11.3.0-1ubuntu1~22.04) ...
Setting up gcc-11 (11.3.0-1ubuntu1~22.04) ...
Setting up cpp (4:11.2.0-1ubuntu1) ...
Setting up libc6-dev:arm64 (2.35-0ubuntu3.1) ...
Setting up libx11-6:arm64 (2:1.7.5-1) ...
Setting up libtiff5:arm64 (4.3.0-6ubuntu0.3) ...
Setting up libfontconfig1:arm64 (2.13.1-4.2ubuntu5) ...
Setting up libperl5.34:arm64 (5.34.0-3ubuntu1.1) ...
Setting up libxpm4:arm64 (1:3.5.12-1build2) ...
Setting up gpg-wks-client (2.2.27-3ubuntu2.1) ...
Setting up gcc (4:11.2.0-1ubuntu1) ...
Setting up perl (5.34.0-3ubuntu1.1) ...
Setting up libexpat1-dev:arm64 (2.4.7-1ubuntu0.2) ...
Setting up libgd3:arm64 (2.3.0-2ubuntu2) ...
Setting up libdpkg-perl (1.21.1ubuntu2.1) ...
Setting up libstdc++-11-dev:arm64 (11.3.0-1ubuntu1~22.04) ...
Setting up zlib1g-dev:arm64 (1:1.2.11.dfsg-2ubuntu9.2) ...
Setting up gnupg (2.2.27-3ubuntu2.1) ...
Setting up libc-devtools (2.35-0ubuntu3.1) ...
Setting up g++-11 (11.3.0-1ubuntu1~22.04) ...
Setting up libfile-fcntllock-perl (0.22-3build7) ...
Setting up libalgorithm-diff-perl (1.201-1) ...
Setting up dpkg-dev (1.21.1ubuntu2.1) ...
Setting up libpython3.10-dev:arm64 (3.10.6-1~22.04.1) ...
Setting up python3.10-dev (3.10.6-1~22.04.1) ...
Setting up g++ (4:11.2.0-1ubuntu1) ...
update-alternatives: using /usr/bin/g++ to provide /usr/bin/c++ (c++) in auto mode
update-alternatives: warning: skip creation of /usr/share/man/man1/c++.1.gz because associated file /usr/share/man/man1/g++.1.gz (of link group c++) doesn't exist
Setting up build-essential (12.9ubuntu3) ...
Setting up libalgorithm-diff-xs-perl (0.04-6build3) ...
Setting up libalgorithm-merge-perl (0.08-3) ...
Setting up libpython3-dev:arm64 (3.10.6-1~22.04) ...
Setting up python3-dev (3.10.6-1~22.04) ...
Processing triggers for libc-bin (2.35-0ubuntu3.1) ...
Processing triggers for ca-certificates (20211016) ...
Updating certificates in /etc/ssl/certs...
0 added, 0 removed; done.
Running hooks in /etc/ca-certificates/update.d...
done.

root@b2c7ae46428a:/# pip install b5

Output
Collecting b5
Downloading b5-1.3.3-py3-none-any.whl (42 kB)
   ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 42.1/42.1 KB 508.7 kB/s eta 0:00:00
Collecting Jinja2<4.0.0,>=3.0.1
Downloading Jinja2-3.1.2-py3-none-any.whl (133 kB)
   ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 133.1/133.1 KB 238.3 kB/s eta 0:00:00
Collecting MarkupSafe<3.0.0,>=2.0.1
Downloading MarkupSafe-2.1.1-cp310-cp310-manylinux_2_17_aarch64.manylinux2014_aarch64.whl (26 kB)
Collecting termcolor<2.0.0,>=1.1.0
Downloading termcolor-1.1.0.tar.gz (3.9 kB)
Preparing metadata (setup.py) ... done
Collecting PyYAML<7.0,>=6.0
Downloading PyYAML-6.0-cp310-cp310-manylinux_2_17_aarch64.manylinux2014_aarch64.whl (733 kB)
   ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 733.7/733.7 KB 992.0 kB/s eta 0:00:00
Collecting packaging<22.0,>=21.3
Downloading packaging-21.3-py3-none-any.whl (40 kB)
   ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 40.8/40.8 KB 857.6 kB/s eta 0:00:00
Collecting pyparsing!=3.0.5,>=2.0.2
Downloading pyparsing-3.0.9-py3-none-any.whl (98 kB)
   ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 98.3/98.3 KB 860.8 kB/s eta 0:00:00
Building wheels for collected packages: termcolor
Building wheel for termcolor (setup.py) ... done
Created wheel for termcolor: filename=termcolor-1.1.0-py3-none-any.whl size=4848 sha256=2f056041db8d9e6d4d21fe7586e7cc176cd6de321ec2f5968592a8cca77664c5
Stored in directory: /root/.cache/pip/wheels/a1/49/46/1b13a65d8da11238af9616b00fdde6d45b0f95d9291bac8452
Successfully built termcolor
Installing collected packages: termcolor, PyYAML, pyparsing, MarkupSafe, packaging, Jinja2, b5
Successfully installed Jinja2-3.1.2 MarkupSafe-2.1.1 PyYAML-6.0 b5-1.3.3 packaging-21.3 pyparsing-3.0.9 termcolor-1.1.0
WARNING: Running pip as the 'root' user can result in broken permissions and conflicting behaviour with the system package manager. It is recommended to use a virtual environment instead: https://pip.pypa.io/warnings/venv

root@b2c7ae46428a:/# b5

Output
b5 1.3.3
Executing task help

Usage: b5 <task> <args>

Tasks:
   1	help

Task exited ok

Just found a possible reason, created a PR where the problem is listed under common problems.

WARNING: The scripts b5, b5-execute and b5-init are installed in '/home/luttkule/.local/bin' which is not on PATH.
  Consider adding this directory to PATH or, if you prefer to suppress this warning, use --no-warn-script-location.

This explicitly mentioned why I won't be able to find b5. This message appeared during my pip install b5.

Yes, but this sounds pretty similar to the error message mentioned in the PR.
Nevertheless, I also added this as second solution in the common problems section in the PR. But in my opinion adding it directly to the PATH should be only the second option, since it should be already added in the .profile file, which is only loaded  on login. Here another thread which describes this issue.
However, as described it doesn't seem to be necessary in every setup, so I wouldn't include it in the install commands and leave it under common problems.


fix: Green dot does not appear in LHN when the request is created in workspace chat

Details

Fixed Issues

$ https://github.com/Expensify/App/issues/32924
PROPOSAL: https://github.com/Expensify/App/issues/32924#issuecomment-1853168412
Tests

Create a new workspace.
Go to the workspace chat > + > Request money.
Create a manual expense in the workspace chat.
Verify that the green dot is appear next to workspace chat in LHN.

[x] Verify that no errors appear in the JS console

Offline tests

Same as above
QA Steps

Create a new workspace.
Go to the workspace chat > + > Request money.
Create a manual expense in the workspace chat.
Verify that the green dot is appear next to workspace chat in LHN.

[x] Verify that no errors appear in the JS console

PR Author Checklist

[x] I linked the correct issue in the ### Fixed Issues section above
[x] I wrote clear testing steps that cover the changes made in this PR

[x] I added steps for local testing in the Tests section
[x] I added steps for the expected offline behavior in the Offline steps section
[x] I added steps for Staging and/or Production testing in the QA steps section
[x] I added steps to cover failure scenarios (i.e. verify an input displays the correct error message if the entered data is not correct)
[x] I turned off my network connection and tested it while offline to ensure it matches the expected behavior (i.e. verify the default avatar icon is displayed if app is offline)
[x] I tested this PR with a High Traffic account against the staging or production API to ensure there are no regressions (e.g. long loading states that impact usability).

[x] I included screenshots or videos for tests on all platforms
[x] I ran the tests on all platforms & verified they passed on:

[x] Android / native
[x] Android / Chrome
[x] iOS / native
[x] iOS / Safari
[x] MacOS / Chrome / Safari
[x] MacOS / Desktop

[x] I verified there are no console errors (if there's a console error not related to the PR, report it or open an issue for it to be fixed)
[x] I followed proper code patterns (see Reviewing the code)

[x] I verified that any callback methods that were added or modified are named for what the method does and never what callback they handle (i.e. toggleReport and not onIconClick)
[x] I verified that the left part of a conditional rendering a React component is a boolean and NOT a string, e.g. myBool && <MyComponent />.
[x] I verified that comments were added to code that is not self explanatory
[x] I verified that any new or modified comments were clear, correct English, and explained "why" the code was doing something instead of only explaining "what" the code was doing.
[x] I verified any copy / text shown in the product is localized by adding it to src/languages/* files and using the translation method

[x] If any non-english text was added/modified, I verified the translation was requested/reviewed in #expensify-open-source and it was approved by an internal Expensify engineer. Link to Slack message:

[x] I verified all numbers, amounts, dates and phone numbers shown in the product are using the localization methods
[x] I verified any copy / text that was added to the app is grammatically correct in English. It adheres to proper capitalization guidelines (note: only the first word of header/labels should be capitalized), and is approved by marketing by adding the Waiting for Copy label for a copy review on the original GH to get the correct copy.
[x] I verified proper file naming conventions were followed for any new files or renamed files. All non-platform specific files are named after what they export and are not named "index.js". All platform-specific files are named for the platform the code supports as outlined in the README.
[x] I verified the JSDocs style guidelines (in STYLE.md) were followed

[x] If a new code pattern is added I verified it was agreed to be used by multiple Expensify engineers
[x] I followed the guidelines as stated in the Review Guidelines
[x] I tested other components that can be impacted by my changes (i.e. if the PR modifies a shared library or component like Avatar, I verified the components using Avatar are working as expected)
[x] I verified all code is DRY (the PR doesn't include any logic written more than once, with the exception of tests)
[x] I verified any variables that can be defined as constants (ie. in CONST.js or at the top of the file that uses the constant) are defined as such
[x] I verified that if a function's arguments changed that all usages have also been updated correctly
[x] If a new component is created I verified that:

[x] A similar component doesn't exist in the codebase
[x] All props are defined accurately and each prop has a /** comment above it */
[x] The file is named correctly
[x] The component has a clear name that is non-ambiguous and the purpose of the component can be inferred from the name alone
[x] The only data being stored in the state is data necessary for rendering and nothing else

[x] Any internal methods bound to this are necessary to be bound (i.e. avoid this.submit = this.submit.bind(this); if this.submit is never passed to a component event handler like onClick)

[x] All JSX used for rendering exists in the render method
[x] The component has the minimum amount of code necessary for its purpose, and it is broken down into smaller components in order to separate concerns and functions

[x] If any new file was added I verified that:

[x] The file has a description of what it does and/or why is needed at the top of the file if the code is not self explanatory

[x] If a new CSS style is added I verified that:

[x] A similar style doesn't already exist
[x] The style can't be created with an existing StyleUtils function (i.e. StyleUtils.getBackgroundAndBorderStyle(themeColors.componentBG))

[x] If the PR modifies code that runs when editing or sending messages, I tested and verified there is no unexpected behavior for all supported markdown - URLs, single line code, code blocks, quotes, headings, bold, strikethrough, and italic.
[x] If the PR modifies a generic component, I tested and verified that those changes do not break usages of that component in the rest of the App (i.e. if a shared library or component like Avatar is modified, I verified that Avatar is working as expected in all cases)
[x] If the PR modifies a component related to any of the existing Storybook stories, I tested and verified all stories for that component are still working as expected.
[x] If a new page is added, I verified it's using the ScrollView component to make it scrollable when more elements are added to the page.
[x] If the main branch was merged into this PR after a review, I tested again and verified the outcome was still expected according to the Test steps.
[x] I have checked off every checkbox in the PR author checklist, including those that don't apply to this PR.

Screenshots/Videos

Android: Native

Android: mWeb Chrome

iOS: Native

iOS: mWeb Safari

https://github.com/Expensify/App/assets/113963320/f7f9bcb1-eb51-4add-a38d-85741deddae8

MacOS: Chrome / Safari

https://github.com/Expensify/App/assets/113963320/3a563a25-bd85-441a-be60-f6dc61740d85

MacOS: Desktop

https://github.com/Expensify/App/assets/113963320/5f6e1187-700f-4313-974c-010cca382d80

Reviewer Checklist

[ ] I have verified the author checklist is complete (all boxes are checked off).
[ ] I verified the correct issue is linked in the ### Fixed Issues section above
[ ] I verified testing steps are clear and they cover the changes made in this PR

[ ] I verified the steps for local testing are in the Tests section
[ ] I verified the steps for Staging and/or Production testing are in the QA steps section
[ ] I verified the steps cover any possible failure scenarios (i.e. verify an input displays the correct error message if the entered data is not correct)
[ ] I turned off my network connection and tested it while offline to ensure it matches the expected behavior (i.e. verify the default avatar icon is displayed if app is offline)

[ ] I checked that screenshots or videos are included for tests on all platforms
[ ] I included screenshots or videos for tests on all platforms
[ ] I verified tests pass on all platforms & I tested again on:

[ ] Android: Native
[ ] Android: mWeb Chrome
[ ] iOS: Native
[ ] iOS: mWeb Safari
[ ] MacOS: Chrome / Safari
[ ] MacOS: Desktop

[ ] If there are any errors in the console that are unrelated to this PR, I either fixed them (preferred) or linked to where I reported them in Slack
[ ] I verified proper code patterns were followed (see Reviewing the code)

[ ] I verified that any callback methods that were added or modified are named for what the method does and never what callback they handle (i.e. toggleReport and not onIconClick).
[ ] I verified that the left part of a conditional rendering a React component is a boolean and NOT a string, e.g. myBool && <MyComponent />.
[ ] I verified that comments were added to code that is not self explanatory
[ ] I verified that any new or modified comments were clear, correct English, and explained "why" the code was doing something instead of only explaining "what" the code was doing.
[ ] I verified any copy / text shown in the product is localized by adding it to src/languages/* files and using the translation method
[ ] I verified all numbers, amounts, dates and phone numbers shown in the product are using the localization methods
[ ] I verified any copy / text that was added to the app is grammatically correct in English. It adheres to proper capitalization guidelines (note: only the first word of header/labels should be capitalized), and is approved by marketing by adding the Waiting for Copy label for a copy review on the original GH to get the correct copy.
[ ] I verified proper file naming conventions were followed for any new files or renamed files. All non-platform specific files are named after what they export and are not named "index.js". All platform-specific files are named for the platform the code supports as outlined in the README.
[ ] I verified the JSDocs style guidelines (in STYLE.md) were followed

[ ] If a new code pattern is added I verified it was agreed to be used by multiple Expensify engineers
[ ] I verified that this PR follows the guidelines as stated in the Review Guidelines
[ ] I verified other components that can be impacted by these changes have been tested, and I retested again (i.e. if the PR modifies a shared library or component like Avatar, I verified the components using Avatar have been tested & I retested again)
[ ] I verified all code is DRY (the PR doesn't include any logic written more than once, with the exception of tests)
[ ] I verified any variables that can be defined as constants (ie. in CONST.js or at the top of the file that uses the constant) are defined as such
[ ] If a new component is created I verified that:

[ ] A similar component doesn't exist in the codebase
[ ] All props are defined accurately and each prop has a /** comment above it */
[ ] The file is named correctly
[ ] The component has a clear name that is non-ambiguous and the purpose of the component can be inferred from the name alone
[ ] The only data being stored in the state is data necessary for rendering and nothing else
[ ] For Class Components, any internal methods passed to components event handlers are bound to this properly so there are no scoping issues (i.e. for onClick={this.submit} the method this.submit should be bound to this in the constructor)
[ ] Any internal methods bound to this are necessary to be bound (i.e. avoid this.submit = this.submit.bind(this); if this.submit is never passed to a component event handler like onClick)
[ ] All JSX used for rendering exists in the render method
[ ] The component has the minimum amount of code necessary for its purpose, and it is broken down into smaller components in order to separate concerns and functions

[ ] If any new file was added I verified that:

[ ] The file has a description of what it does and/or why is needed at the top of the file if the code is not self explanatory

[ ] If a new CSS style is added I verified that:

[ ] A similar style doesn't already exist
[ ] The style can't be created with an existing StyleUtils function (i.e. StyleUtils.getBackgroundAndBorderStyle(theme.componentBG)

[ ] If the PR modifies code that runs when editing or sending messages, I tested and verified there is no unexpected behavior for all supported markdown - URLs, single line code, code blocks, quotes, headings, bold, strikethrough, and italic.
[ ] If the PR modifies a generic component, I tested and verified that those changes do not break usages of that component in the rest of the App (i.e. if a shared library or component like Avatar is modified, I verified that Avatar is working as expected in all cases)
[ ] If the PR modifies a component related to any of the existing Storybook stories, I tested and verified all stories for that component are still working as expected.
[ ] If the PR modifies a component or page that can be accessed by a direct deeplink, I verified that the code functions as expected when the deeplink is used - from a logged in and logged out account.
[ ] If the PR modifies the form input styles:

[ ] I verified that all the inputs inside a form are aligned with each other.
[ ] I added Design label so the design team can review the changes.

[ ] If a new page is added, I verified it's using the ScrollView component to make it scrollable when more elements are added to the page.
[ ] If the main branch was merged into this PR after a review, I tested again and verified the outcome was still expected according to the Test steps.
[ ] I have checked off every checkbox in the PR reviewer checklist, including those that don't apply to this PR.

Screenshots/Videos

Android: Native

Android: mWeb Chrome

iOS: Native

iOS: mWeb Safari

MacOS: Chrome / Safari

MacOS: Desktop

@tienifr lets complete screenshots or videos section.

Not able to invite other account to a workspace, will continue testing once i am able to https://github.com/Expensify/App/issues/33560

there is a noticeable delay before the green dot appears, when offline it will not show. is this something we can fix?
https://github.com/Expensify/App/assets/75031127/87c13f63-38ec-44c4-addb-0e33ea6b2baf

@tienifr lets complete the videos/screenshot section from the checklist.

@tienifr let me know once its completed, we've to get this merged, its been pending for weeks.

@tienifr lint is failing.

:hand: This PR was not deployed to staging yet because QA is ongoing. It will be automatically deployed to staging after the next production release.

🚀 Deployed to staging by https://github.com/nkuoch in version: 1.4.33-0 🚀

platform
result

🤖 android 🤖
success ✅

🖥 desktop 🖥
success ✅

🍎 iOS 🍎
cancelled 🔪

🕸 web 🕸
success ✅

🚀 Deployed to production by https://github.com/francoisl in version: 1.4.33-5 🚀

platform
result

🤖 android 🤖
success ✅

🖥 desktop 🖥
success ✅

🍎 iOS 🍎
failure ❌

🕸 web 🕸
success ✅


Create edu.txt

@dapengtx I am sorry, this request has signs of fraud. I have to close it without merging. If you are a student of this school, please apply with official document ("OFFICIAL DOCUMENT" tab at https://www.jetbrains.com/shop/eform/students).


Apply refKeyCase in buildRefValues

Relates to #86
Apply refKeyCase in buildRefValues so that correct upsert/remove is chosen during buildIndexObjects.
Found this edge case scenario in the app-code and isolated it to 100% reproducibility (See added test case). If the index has a refKeyCase and preSave modification to that field, adding a doc with a value for that field with a case different than what was previous saved, will cause lounge to setup a remove and an upsert back to back for what ends up being the same ref document, and this results in a couchbase "Temporary failure" 100% of the time on save/index, presumably because its trying to remove and mutate the same doc, essentially at the same time? In any case, it shouldn't even be trying to remove in the first place in this scenario, and the fix in this PR causes the ref compare to properly identify that it is just an upsert.
To see the failure, the added test needs to be run without the CB mock:
DEBUG=lounge node_modules/.bin/mocha --exit test/model.index.save.spec.js
lounge array index. operation: upsert key<EMAIL_ADDRESS>refKeyValue: 9d69764c-a4e5-44eb-9563-7fc1ebc845b1 +335ms
lounge array index: mutateIn<EMAIL_ADDRESS>+1ms
lounge array index<EMAIL_ADDRESS>not found for mutateIn trying to do atomic transform +0ms
lounge save. type: User  key: 9d69764c-a4e5-44eb-9563-7fc1ebc845b1 +1ms
lounge array index. operation: remove key<EMAIL_ADDRESS>refKeyValue: 08add56d-a643-46db-98d8-324136e72e7b +1ms
lounge array index. operation: upsert key<EMAIL_ADDRESS>refKeyValue: 08add56d-a643-46db-98d8-324136e72e7b +0ms
lounge array index: mutateIn<EMAIL_ADDRESS>+0ms
lounge Temporary failure received from server. Try again later +1ms
1) should index sucessfully with matching ref but different case, when refKeyCase is set

  17 passing (6s)
  1 failing

  1) Model index on save tests
       should index sucessfully with matching ref but different case, when refKeyCase is set:
     Uncaught CouchbaseError: Temporary failure received from server. Try again later

Note the remove/upsert of the same document key.
Running that test, with the fix, it adds the new document, with the correct refkey, every time.

There appears to be one failing test, which also fails for me in master.... looking into that


Phonebook feature not clear/not working

Describe the bug
No phonebook switch in Home and Eve.
No resolution of caller id's in callmonitor.
To Reproduce
Steps to reproduce the behavior:

Go to '...'
Click on '....'
Scroll down to '....'
See error

Expected behavior
A clear and concise description of what you expected to happen.
From the docs I understand that I can use an option Phonebook.
I choose this in the config, but don.t know where to look for the switch that is supposed to be generated.
I see call monitor incoming and outgoing in Eve. I can confirm that an incoming call is registered, but I expected caller details.
I suppose the Phonebook option is needed for this ?.
Screenshots
If applicable, add screenshots to help explain your problem.
Screen in Eve.

Desktop (please complete the following information):

OS: Rpi
Version homebridge-fritz-platform v5.0.8

Smartphone (please complete the following information):

Device: max XS
OS: [e.g. iOS14
Browser [e.g. stock browser, safari]
Version [e.g. 22]

Additional context
Add any other context about the problem here.

If you choose phonebook accessory type as „characteristic“, then u need to look into your master device via third party app.
Accessory type „switch“ means that it will be exposed a a switch.

Thanks for your reply.
Still it is not clear to me what is the use case of Phonebook option.
I'm aware of the Phonebook in Fritz. Ut hiw can I use it in your plugin?
I assumed it was used for lookup of callers in the monitor?
As the screendump shows this does not work.

The phonebook option creates a phonebook.json file with all of your phonebook entries which will be used for callmonitor to get information about the caller

OK
I've found phonebook.json in /usr/lib/homebridge/fritzbox on my raspberry.
File however is empty.

You need to turn on the phonebook switch to generate the file

I receive folllowing error
``
[FritzPlatform] FritzBox PhoneBook: An error occured during setting state (phoneBook)
[11/13/2020, 5:04:32 PM] [FritzPlatform] Error: action X_AVM-DE_GetVoIPCommonCountryCode of urn:dslforum-org:service:X_VoIP:1 not known
at Service. (/usr/local/lib/node_modules/homebridge-fritz-platform/node_modules/@seydx/fritzbox/src/lib/service.ts:182:13)
at Generator.next ()
at fulfilled (/usr/local/lib/node_modules/homebridge-fritz-platform/node_modules/@seydx/fritzbox/dist/lib/service.js:5:58)
at runMicrotasks ()
at processTicksAndRejections (internal/process/task_queues.js:93:5)
``

@tooh
Which fritzbox router and firmware ?

Fon WLAN 7390
Fritz!OS : 06.86

@tooh
You need at least v7 to use this plugin. Otherwise u will get errors.
Your FritzBox doesn’t support VOIP, the plugin needs the endpoint to query the correct country prefix like +49
I could implement a fallback, so user can decide it over config.json, but i can not guarantee that everything else will working fine due to the reason u re on FW v6.86

@SeydX thanks for investigating.
I see on the AVM site that the 7390  is end of support, so I assume they will not upgrade the firmware.
I appreciate your offer, but I agree with you that probably the next issue is around the corner.

@tooh
i will implement a „country“ option to config to skip the VOIP API call. This should fix the phoneBook issue for you

@SeydX
Much appreciated!

@tooh
Should be fixed with v5.0.10

@tooh
there is a „countryPrefix“ option now under callmonitor. Just add your country prefix there with config ui x and it should work

@SeydX
Installed new version.
Testresults:

Phonebook is now dumped to the directory.

Added countrycode in config.

No resolution of callername yet.
I'm debugging this by switching on the -D flag on homebridge level.
Do not see anything related to the callername yet. Will investigate further.
Remarkable observation: logging info coming from your plugin is labeled as coming from WeatherPlus, another
Plugin I use that is using fakegato.
Will investigate this further.
Thanks  for now.

Remarkable observation: logging info coming from your plugin is labeled as coming from WeatherPlus, another
Plugin I use that is using fakegato.

Whot? Can i see the log pls


How to get similarity_Lm3D_all.mat？

Thank you very much for your work. Could you please tell me where I can download the similarity_lm3d_all.mat file? Thank you

seen in BFM folder

Thank you. I'm working on your experiment-------- 原始邮件 --------发件人： "Xiaobin HU(kevin)"<EMAIL_ADDRESS>2021年2月4日周四 20:02收件人： HUuxiaobin/Face-Super-Resolution-Guided-by-3D-Facial-Priors<EMAIL_ADDRESS>TREASUREPPY<EMAIL_ADDRESS>State change<EMAIL_ADDRESS>  题： Re: [HUuxiaobin/Face-Super-Resolution-Guided-by-3D-Facial-Priors] How to get similarity_Lm3D_all.mat？ (#3)
seen in BFM folder
—You are receiving this because you modified the open/close state.Reply to this email directly, view it on GitHub, or unsubscribe.


Change default install path to ./.bundle/gems [WIP]

Opening this PR from a branch in the bundler repo, so we can all collaborate on it... /cc @smlance

Reviewing the failing clean specs makes me realize something... we don't allow saving flags on install (like install --system) in 2.0. So, how can you use system gems via bundle config?  Just clearing the value won't work, because we're changing the default. @bundler/core, any thoughts?

Talked this over with @smlance, and the current plan is:

[ ] bundle config path.system trueprints a warning ifpath` is set when you set it
[ ] bundle config path foo prints a warning if path.system is set when you set it
[ ] unset the conflicting option when we print the warning

This is looking good, so I'm going to squash the commits, open a new PR, and merge!

I must have missed a ton of context here, but what's the reasoning for
changing this from vendor/bundle? Just having a single bundler directory?
On Wed, Jul 1, 2015 at 7:30 PM Stefan Lance<EMAIL_ADDRESS>wrote:

This is looking good, so I'm going to squash the commits, open a new PR,
and merge!
—
Reply to this email directly or view it on GitHub
https://github.com/bundler/bundler/pull/3784#issuecomment-117849792.

fwiw: changes like this, while they may seem innocuous, can definitely break scripts designed to work with bundler. It should be considered a semver breaking change, and I agree with @hone that it would be good to articulate the rationale for changes with breaking potential.

This is targeting the Bundler 2.0 branch already, @wycats ?

@hone @wycats we've been talking about the plan for 2.0 in the Slack for a year, and had Trello cards clearly outlining the exact plan for over six months. I'm happy to discuss if you would like, but this pull request is not the right place to discuss why this particular change is being made.

@segiddins even if it's targeting 2.0, bundler should still be careful about the breaking changes it makes. A major version bump means bundler can make changes, but the cost of the changes should still outweigh the benefits.

@indirect I have mostly stayed out of bundler discussions because the project maintained the basic assumptions and assumed the basic constraints we agreed to when we started the project.
As a daily user of bundler, and someone who has evangelized bundler's ideas to other communities (and very recently implemented a similar strategy for Rust), I think it's appropriate for me to express concerns about the number of changes in 2.0, even though I stayed hands-off of the development process.
Since I'm not involved in the development process, you can feel free to ignore anything I've said; them's the break with open source. I'm just letting you know how I feel.

@wycats thanks for letting us know how you feel. FWIW, Cargo's default strategy is much closer to this change than it is to Bundler 1.0's default strategy. Again, I'm happy to discuss, as long as it's somewhere else. This PR is for code review of @smlance's Google Summer of Code work implementing the long-standing plans for 2.0.

@indirect No problem. Name a place :smile:
For what it's worth, one of the basic principles was keeping things stable between releases of bundler, so that people can generally use Gemfile.locks and directory structures produced by a new version of bundler with an old version of bundler. Obviously, any new features in the DSL would not work with old versions of bundler, but people tend to have new versions of bundler on their system well before they start using the new features in their projects.
We've talked about all of this before, and I think 2.0 is an ok time to make people upgrade "all at once" if absolutely necessary.
In case it's not clear, I am extremely thankful for all the hard work you and others have done to maintain bundler over the years. When I say I've kept out of development because you've done a good job maintaining the aspects of bundler I care about, I'm not just saying it; it's really true.

@wycats https://trello.com/c/K4zdOFl8/51-default-installs-to-path-bundle-gems is the troll card for this change in particular, and there's a whole column for breaking changes in 2.0 at https://trello.com/b/DioUaKgx/bundler.

Thanks @segiddins. I didn't mean to hijack the thread. I was just curious on the reasoning. Talked with @indirect a bit about it. I follow up on the card. Cheers and thanks for working on bundler @smlance!

@indirect and I thought it made sense to change the install_path and bin_path in source/rubygems.rb as well, since these variables are used when bundle install is run. Are there any other default bundle path variables in the code that need to be changed?

The bundle install --deployment path redundancy can be seen here: https://gist.github.com/smlance/d8214f81c2652de98e3a

looking good :+1:


Add sort/test to status/Jamfile.v2

This will enabling testing of the new sort library.
The sort library is here: https://github.com/boostorg/sort.  Do I also need to add it directly to this boost project in some fashion?

Is there something I should do to test that this all works properly, aside from making sure that boostorg/sort's test directory runs without trouble?

OK, done. Also added sort to .gitmodules.
I change libs/sort/test/Jamfile.v2 to conform to the usual test-suite naming convention. So please do a pull on your local working copy.
The regression tests look good so far, although only a few test runners have cycled. See http://www.boost.org/development/tests/develop/developer/summary.html
Thanks,
--Beman

Thanks!
On Tue Jan 20 2015 at 7:05:48 AM Beman Dawes<EMAIL_ADDRESS>wrote:

Closed #43 https://github.com/boostorg/boost/pull/43.
—
Reply to this email directly or view it on GitHub
https://github.com/boostorg/boost/pull/43#event-221552701.


Fix Issue 20799 - schwartzSort does not pin transformation results wi…

…th indirections, leading to memory corruption

Memory corruptions sound like it should be targeting stable.

-> https://github.com/dlang/phobos/pull/7471


input value does not get updated as page loads

I'm submitting a ...

[ ] bug report

Current behavior:

When i bind the model value , unless i click inside the input text box the model value is not updated ..
Expected / new behavior:

I would like the model value updated with the current value as the page renders , but instead it renders only when i focus on the input text box
http://embed.plnkr.co/P5hoQ2/
please check the above plunk , in that with precision input text box , unless i click inside the text box the value does not show up i.e.. 0.5
Minimal reproduction of the problem with instructions:

AngularJS version: 1.6.4

Browser: [all | Chrome XX | Firefox XX | Edge XX | IE XX | Safari XX | Mobile Chrome XX | Android X.X Web Browser | iOS XX Safari | iOS XX UIWebView | iOS XX WKWebView ]

Anything else:

I'm afraid that this looks like a bug in the numbersOnly library and not in AngularJS.
From a brief look at their directive it is not rendering correctly until one of its event handlers is triggered.
Please submit a bug at https://github.com/willmendesneto/ng-numbers-only.


Recognize the new core project-level config block

Fixes #369

My understanding of @AaronFriel's explanation around this was that YAML was going to stop looking at the config block directly and look at config and configSecretKeys in the run request from the engine instead.

So YAML would use the Go SDK to do things like conf.TryInt("instanceSize") instead of the project file config block? If so, would it make sense to have a separate syntax instead of interpolated expressions to get a config value, i.e. conf.instanceSize
Would we still need to read in the new config block while loading the template to get the default value of config values if not set?
cc @iwahbe

So YAML would use the Go SDK to do things like conf.TryInt("instanceSize") instead of the project file config block? If so, would it make sense to have a separate syntax instead of interpolated expressions to get a config value, i.e. conf.instanceSize

cc @iwahbe

We already use the go SDK to pull config values, see https://github.com/pulumi/pulumi-yaml/blob/0197f6544aee26c557ba84573cd0a1506eed3e3c/pkg/pulumiyaml/run.go#L845-L850
In the past, we needed to read the config to known what values to pull into scope, and what defaults to provide. If defaults will be handled for us, we can just inject config values into our scope and error (during topologicallySortedResources) when attempting to use missing values.
I don't see why changing the implementation should change the user syntax.

For updating our examples and being able to convert YAML->PCL, we may need to parse the config block? @iwahbe

For updating our examples and being able to convert YAML->PCL, we may need to parse the config block? @iwahbe

Parsing the config block is complicated already, and will get more so when we introduce new sources of config. Even now, consider the following 3 files:
Pulumi.yaml:
name: proj
runtime: yaml
main: src/Main.yaml
config:
  prefix:
    default: abc

Pulumi.dev.yaml:
config:
  pros:tag: tag2

src/Main.yaml:
resources:
  bucket:
    type: aws:s3:Bucket
    properties:
      bucket: ${prefix}-bucket
      tags:
        stackTag: ${tag}

I can see how we will need the information though. Right now, I think we can continue going through configuration for this. In the future we can add the ability to describe the config when converting YAML->PCL.

In the future we can add the ability to describe the config when converting YAML->PCL.

I think that might sync well with the ideas of code generating config types for the other languages. We should try to make sure those two things use the same language.


Fixes neugram/ng#154.

Codecov Report

Merging #162 into master will decrease coverage by 0.17%.
The diff coverage is 39.74%.

@@            Coverage Diff             @@
##           master     #162      +/-   ##
==========================================
- Coverage      51%   50.82%   -0.18%
==========================================
  Files          22       22
  Lines        9539     9696     +157
==========================================
+ Hits         4865     4928      +63
- Misses       4203     4291      +88
- Partials      471      477       +6

Impacted Files
Coverage Δ

parser/expr_equal.go
26.94% <0%> (+0.3%)
:arrow_up:

format/expr.go
52.61% <0%> (-19.77%)
:arrow_down:

syntax/walk.go
90.53% <100%> (+0.11%)
:arrow_up:

typecheck/typecheck.go
21.69% <17.94%> (-0.11%)
:arrow_down:

gengo/gengo.go
92.68% <68.96%> (-0.98%)
:arrow_down:

eval/eval.go
79.4% <87.32%> (+0.41%)
:arrow_up:

parser/parser.go
69.86% <90%> (+0.87%)
:arrow_up:

Continue to review full report at Codecov.

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


kotlin version error when building android release  and i dont know how to solve this

w: Runtime JAR files in the classpath should have the same version. These files were found in the classpath:
    C:/Users/xiaoshuyui/.gradle/caches/modules-2/files-2.1/org.jetbrains.kotlin/kotlin-stdlib-jdk8/1.5.30/5fd47535cc85f9e24996f939c2de6583991481b0/kotlin-stdlib-jdk8-1.5.30.jar (version 1.5)
    C:/Users/xiaoshuyui/.gradle/caches/modules-2/files-2.1/org.jetbrains.kotlin/kotlin-stdlib-jdk7/1.5.30/525f5a7fa6d7790a571c07dd24214ed2dda352fe/kotlin-stdlib-jdk7-1.5.30.jar (version 1.5)
    C:/Users/xiaoshuyui/.gradle/caches/modules-2/files-2.1/org.jetbrains.kotlin/kotlin-stdlib/1.6.10/b8af3fe6f1ca88526914929add63cf5e7c5049af/kotlin-stdlib-1.6.10.jar (version 1.6)
    C:/Users/xiaoshuyui/.gradle/caches/modules-2/files-2.1/org.jetbrains.kotlin/kotlin-stdlib-common/1.6.10/c118700e3a33c8a0d9adc920e9dec0831171925/kotlin-stdlib-common-1.6.10.jar (version 1.6)
    C:/Users/xiaoshuyui/.gradle/caches/modules-2/files-2.1/org.jetbrains.kotlin/kotlin-stdlib/1.5.31/6628d61d0f5603568e72d2d5915d2c034b4f1c55/kotlin-stdlib-1.5.31.jar (version 1.5)
    C:/Users/xiaoshuyui/.gradle/caches/modules-2/files-2.1/org.jetbrains.kotlin/kotlin-stdlib-common/1.5.31/43331609c7de811fed085e0dfd150874b157c32/kotlin-stdlib-common-1.5.31.jar (version 1.5)
w: Some runtime JAR files in the classpath have an incompatible version. Consider removing them from the classpath
e: C:/Users/xiaoshuyui/.gradle/caches/modules-2/files-2.1/org.jetbrains.kotlin/kotlin-stdlib/1.6.10/b8af3fe6f1ca88526914929add63cf5e7c5049af/kotlin-stdlib-1.6.10.jar!/META-INF/kotlin-stdlib.kotlin_module: Module was compiled with an incompatible version of Kotlin. The binary version of its metadata is 1.6.0, expected version is 1.4.0.
e: C:/Users/xiaoshuyui/.gradle/caches/modules-2/files-2.1/org.jetbrains.kotlin/kotlin-stdlib-common/1.6.10/c118700e3a33c8a0d9adc920e9dec0831171925/kotlin-stdlib-common-1.6.10.jar!/META-INF/kotlin-stdlib-common.kotlin_module: Module was compiled with an incompatible version of Kotlin. The binary version of its metadata is 1.6.0, expected version is 1.4.0.
e: D:/github_repo/codind/code-find/frontend/codind/build/package_info_plus/tmp/kotlin-classes/release/META-INF/package_info_plus_release.kotlin_module: Module was compiled with an incompatible version of Kotlin. The binary version of its metadata is 1.6.0, expected version is 1.4.0.

here is my build.gradle info

Ran into this same issue. I solved it by updating ext.kotlin_version in android > build.gradle from 1.3.50 to the latest version listed on https://kotlinlang.org/docs/gradle.html#plugin-and-versions; 1.6.20.
buildscript {
    ext.kotlin_version = '1.6.20'
    repositories {
        google()
        jcenter()
    }

I noticed you already have the latest. But not sure about the -M1. Is this something unique for M1 macs?

I still cannot fix this error.

But thanks .

Ran into this same issue. I solved it by updating ext.kotlin_version in android > build.gradle from 1.3.50 to the latest version listed on https://kotlinlang.org/docs/gradle.html#plugin-and-versions; 1.6.20.
buildscript {
    ext.kotlin_version = '1.6.20'
    repositories {
        google()
        jcenter()
    }

I noticed you already have the latest. But not sure about the -M1. Is this something unique for M1 macs?

I don't know why, but that's how I solved the problem:
file path: ${projectRoot}/android/build.gradle

It maybe the java version. I was using java1.8 when building apks, and I upgrades to java 11 today, it seems OK now.


pkg/k8s: do not perform an early return on ipcache errors

Although ipcache might return an error, we should not perform an early
return in the event handling of the pod event because some other
components that are unrelated to ipcache might depend on this specific
event per perform correctly. Instead we will log the ipcache error and
let the execution of the method to continue.
The pod might, for example, be in a "Pending" state which has its
status IP addresses not set but might be able to change labels in the
meanwhile which Cilium should react upon those changes which are not
related with ipcache.
Improved event handling for pod events by removing an unnecessary early return, allowing unrelated components to execute correctly, while enhancing ipcache error logging.

/test

/test


"uv --preview lock" does not read uv.toml or pyproject.toml settings

The uv --preview lock command does not find/respect settings in either a pyproject.toml or a uv.toml file, and thus resolution fails for internal Pypi repositories:
[pip]
extra-index-url = [
  "https://artifactory/artifactory/api/pypi/pypi-internal/simple",
  "https://artifactory/artifactory/api/pypi/pypi-external/simple",
]
index-url = "https://server/pypi/simple"

Or in pyproject.toml:
[tool.uv.pip]
extra-index-url = [
  "https://artifactory/artifactory/api/pypi/pypi-internal/simple",
  "https://artifactory/artifactory/api/pypi/pypi-external/simple",
]
index-url = "https://server/pypi/simple"

$ uv --preview lock --show-settings
...
LockSettings {
    python: None,
    refresh: None(
        Timestamp(
            SystemTime {
                tv_sec:<PHONE_NUMBER>,
                tv_nsec: 61301000,
            },
        ),
    ),
    settings: ResolverSettings {
        index_locations: IndexLocations {
            index: None,
            extra_index: [],
            flat_index: [],
            no_index: false,
        },
        index_strategy: FirstIndex,
        keyring_provider: Disabled,
        resolution: Highest,
        prerelease: IfNecessaryOrExplicit,
        config_setting: ConfigSettings(
            {},
        ),
        exclude_newer: None,
        link_mode: Clone,
        upgrade: None,
        build_options: BuildOptions {
            no_binary: None,
            no_build: None,
        },
    },
}

Passing --index-url and --extra-index-url on the command line does work.

Hi! We don't read the tool.uv.pip settings outside the uv pip CLI — instead use the top-level tool.uv options that correspond to their pip-specific counterparts.

That doesn't appear to work with pyproject.toml:
[tool.uv]     ■ Additional properties are not allowed ('extra-index-url', 'index-url' were unexpected)
extra-index-url =

And emits a schema validation error.
In uv.toml if I remove any section wrapper and just have the raw key/value assignments, that works, but emits the same schema validation error.

Both of the following work for me?
[tool.uv]
index-url = "https://test.pypi.org/simple"
extra-index-url = ["https://test.pypi.org/simple"]

Are you on the latest version?
Yeah uv pip will inherit these settings. If you set them in [tool.uv.pip] that will take precedence over the top-level one.

Yes - uv 0.2.24 (527b711bc 2024-07-10)
I think I found the issue. If there is an empty or commented out uv.toml then the values in pyproject.toml won't be read.

Do you mean, the JSON Schema on SchemaStore? Definitely need to update that.
We should probably warn if you have both a uv.toml and a pyproject.toml with a [tool.uv] table in the same directory.

Yes - the JSON Schema on SchemaStore.

https://github.com/SchemaStore/schemastore/pull/3919

I'll use this issue to track adding a warning.


.find([cheerio Object]) fails

Example:
$script = $('script[type="text/javascript"]')
$('body').find($script); // fail!

Was hoping to close this one, but this one is going to take some more effort. jQuery uses the DOM's native compareDocumentPosition


Adding Content to the Landing page

Is your proposal related to a problem?
When on the landing page it seems quite difficult to understand what actually "Biotree" does. There's no about us page or something. one would have to check the FAQ section to know.

Describe the solution you'd like
Hence, I would like to suggest adding a summary/description/Catchphrase at the top of the landing page below the navbar. Since it would catch the user's attention as soon as the page loads
(Describe your proposed solution here.)
I would like to add an attractive catch phrase along with minimal but understanding description about the website.
Requirement/Document
I would like to get a brief summary of the website or what details need to be displayed
(Share it here.)

i would like work on this proposal, can you assign it to me ?

Sorry it's first come first serve


fixed: Text cut off on mobile #100

closes #100

made other small UI changes to the issue-card

@Cahllagerfeld deleted the yarn.lock


CLI[UX] Use prompts and show progress status for init command

:tada: This issue has been resolved in version 0.14.0 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


win7 64位电脑安装atx时出现 ImportError: No module named _markerlib 错误。

使用命令pip install --upgrade --pre atx安装的时候出现如题的错误。
Requirement already up-to-date: backports.ssl-match-hostname in c:\python27\lib\site-packages (from tornado==4.3->atx)
Collecting distribute (from atx-androguard==3.0->atx)
Using cached distribute-0.7.3.zip
Complete output from command python setup.py egg_info:
running egg_info
creating pip-egg-info\distribute.egg-info
writing requirements to pip-egg-info\distribute.egg-info\requires.txt
writing pip-egg-info\distribute.egg-info\PKG-INFO
writing top-level names to pip-egg-info\distribute.egg-info\top_level.txt
writing dependency_links to pip-egg-info\distribute.egg-info\dependency_links.txt
Traceback (most recent call last):
File "", line 1, in
File "c:\users\admini~1\appdata\local\temp\pip-build-eqpmia\distribute\setup.py", line 58, in
setuptools.setup(**setup_params)
File "c:\python27\lib\distutils\core.py", line 152, in setup
dist.run_commands()
File "c:\python27\lib\distutils\dist.py", line 953, in run_commands
self.run_command(cmd)
File "c:\python27\lib\distutils\dist.py", line 972, in run_command
cmd_obj.run()
File "setuptools\command\egg_info.py", line 177, in run
writer = ep.load(installer=installer)
File "pkg_resources.py", line 2241, in load
if require: self.require(env, installer)
File "pkg_resources.py", line 2254, in require
working_set.resolve(self.dist.requires(self.extras),env,installer)))
File "pkg_resources.py", line 2471, in requires
dm = self._dep_map
File "pkg_resources.py", line 2682, in _dep_map
self.__dep_map = self._compute_dependencies()
File "pkg_resources.py", line 2699, in _compute_dependencies
from _markerlib import compile as compile_marker
ImportError: No module named _markerlib

重新更新pip、setuptools 、distribute就可以了，easy_install distribute或者pip install --upgrade distribute。


Why not have a private DJIBaseProduct product?

Is there a deeper meaning to why "DJIBaseProduct product = DJIDemoApplication.getProductInstance();" is called so often instead of declaring a private variable DJIBaseProduct, initializing it one time in the onResume method? Or could there be problems?
Thanks for the help :)

Thanks for the quick response :)
I have another question, because I'm waiting to get a phantom and therefore can't really check what I'm coding, maybe you could help me out again if this is not so offtopic: :
What exactly happens to the drone when you invoke  mMissionManager.stopMissionExecution(new DJICommonCallbacks.DJICompletionCallback() in your code? (Also pauseMissionExecution). Does the drone land or does it hover in the air? And does startMissionExecution resume the aborted mission or does it begin at the beginning?
I hope I can ask these questions here in the context of the Demo here, if this is not the right site to ask this, excuse me :)

Hi, please refer to the tutorial of this sample code: Creating a MapView and Waypoint Application, it has already been updated to Android SDK 3.3 and explain your questions in details. Hope this help!


[WFLY-14841]:Remove dependency on PicketBox from Web Services

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

Thanks for working on this, @jimma! It looks like at least some of the failures here are due to some checkstyle issues. Once that's sorted out, if CI passes, one option might be to submit a PR against Darran's branch to get the fixes incorporated into his PR.

@fjuma  Looks these checkstyle errors are fixed.

@jimma Can this be squashed down to 1 or two commits? Thanks.

@bstansberry Done.

/retest

Superseded by https://github.com/wildfly/wildfly/pull/15139


Cody Gray: Watch 7aref.com

Cody Gray requests the watch of the watch_keyword 7aref\.com. See the MS search here and the Stack Exchange search in text, in URLs, and in code.

7aref\.com has been seen in 1 true positive, 0 false positives, and 0 NAAs.

7aref\.com has been seen in 1 true positive, 0 false positives, and 0 NAAs.

Approved by Spevacus in Charcoal HQ

Approved by Spevacus in Charcoal HQ


Support compile-time constants in CuPy JIT

This PR supports compile-time constants in CuPy JIT. This enhancement simplifies generated code by evaluating some numerical expressions in transpile time and enables us to use Python objects of any type, even if it is a non-numerical object, in compile-time.

This is to evaluate numerical expresions in transpile time?
Cool!

Yes, this enhancement can shrink the given code by evaluating numerical expressions in transpile time.

PTAL.

Jenkins, test this please

Jenkins CI test (for commit 6704231d6fb11b683d39c02ccf0be0e030f0509a, target branch master) succeeded!


script compatible with lnd rpc

Hello Czino ,
Please can you make the script compatible with lnd rpc so we can run it on umbrel node.

@pratapc65 I'm not sure I understand what you mean. The script already calls lncli which communicates with your local lnd via RPC ... by default it assumes that your lnd is at localhost:10009, but you can change that via the --rpcserver argument.... e.g., if you use a different port or if you want to access a remote server.


ssl in help channel, on freenode

hehe. i actually removed SSL from help channel due to some complaints.
SSL remains in the main channel, and others. any unregistered/non-SSL users will be forwarded to #gridcoin-help through +F mode. :)

Is the SSL requerement really necessary? My IRC client does not support SSL so I cannt enter. Thats another barrier for newbies becoming a member of the community

It's also interfering with the slack<->irc bot :(

How come the slack bot cannot work with SSL? @Quezacoatl1 perhaps that's an indicator that you should switch IRC client?

@grctest I think it does but not out of the box. See last comment: https://github.com/ekmartin/slack-irc/issues/38#issuecomment-257107876
I'm still not sure why we require SSL in an open channel. For closed discussions, fine, but this one is for anyone to read anyway.

in the interest of preparedness for the future (god knows if people will be able to change your text in transit soon), and also to show people that we hold ourselves to the same standard of security that we are asking of people. while SSL isn't required by projects, we have been going around telling people to SSL their sites. it's not that hard to do... pretty frivolous complaints for the most part. and in my opinion, as well as some other ops, it's a good primer to show people that this isn't something you can try in a couple of seconds... it takes a bit of work. ;)

I've removed the forced SSL on the main chat due to the bots being negatively affected. Users can use SSL if they want, we're just not enforcing it. It's up to end users if they want to be secure or not. IRC should be considered entirely public, so interception of SSL traffic is pointless when you can just join and monitor the plain text chat.

also, it should be noted that #elitebnc on Freenode gives out free bnc's that automatically connect through SSL no matter what client you are on. :)


don't remove empty string

This is a mildly breaking change, but is also what I assumed default behavior would be, curious what others think.
With current cast behaviour, if an empty string is sent as a param, that string gets removed, due to default empty values behaviour https://hexdocs.pm/ecto/Ecto.Changeset.html#module-empty-values
If I want to clear a text field, I typically send a json object of the form
{ field-to-clear: ""}

This is getting changed to nil, and I can't clear fields.
I could set default empty string, but there's only one update route, and other actions will send an object of form
{ other-field: 55 }

And with default empty string, this unrelated update zeroes out my text field.
This update is all that's necessary to get my narrow use case working, I haven't dug too hard into potential consequences elsewhere.
Requires ecto version bump to pass tests.
Also leaving internet as soon as I post this, so not going to be a good conversationalist for a couple days.

Looks like something reasonable to me. Could you please also add a test to your PR?
I'm just not using this package right now. So I hope someone can give it a try and see if we should bump a major version or something.


Make all (but one?) of the Parameter arguments keywords only

Parameters can currently be constructed with a variable number of positional arguments.
param.List([1, 2], int, int, True, (2, 4))
param.ObjectSelector(1, [1, 2, 3])

PEP 3102 implemented in Python 3.0 added support for declaring arguments that are keywords-only:
def compare(a, b, *, key=None):
    pass

# key must be passed as a keyword argument
compare(1, 2, key=operator.eq)

Param dates from way before this PEP was accepted and does not benefit from it, while I think it should :)
There's however a remaining question, that is about the first argument. @jbednar explained me that the spirit of the current state is that the first argument is the value that makes the most sense for the Parameter at hand. For instance, for Number it is the default number, or for Boolean the default boolean value. In most cases, default is indeed the first argument and can be passed by position, for example param.Boolean(True). There are a few Parameters that don't have default as their first argument:

ClassSelector has class_
Selector has objects. Note that its subclasses - ListSelector, FileSelector,  and MultiFileSelector - still have default as a first argument :/ Same for ObjectSelector that is deprecated but still used a lot.
Composite has attribs
Dynamic actually has default as its first argument but it accepts it as keyword only

Now there are multiple ways to approach that, all have their pros and cons, and all are more or less a breaking change:

all arguments keyword only
all arguments keyword only but the first one that is always default
all arguments keyword only but the first one that is the one that makes sense (mostly default, but can also be objects, class_, ...)

This is a timely question with the upcoming Param 2.0 and the Sentinel work (https://github.com/holoviz/param/pull/605) that touched the signatures.
Will need the opinion of Param users on this one to get a feeling on what the best API could be and what the extent of the breaking change you would be willing to accept: @jlstevens, @philippjfr, @Hoxbro, @MarcSkovMadsen

My vote goes to 2.
I believe this keeps things simple.

My vote is also on number 2 for the same reason as @MarcSkovMadsen.

I would personally be happy with option 1 and that seems like the simplest way to me as well.
Option 2 is also very reasonable and may feel more natural for some users. That said, I agree with Philipp in that I only think this should be done if the semantics for a positional argument are completely clear for all parameters (which is not the case right now).

I have opened https://github.com/holoviz/param/pull/737 for you to see how it feels to have a warning emitted when a positional argument is passed to a Parameter.
# foo.py
import param

class P(param.Parameterized):
    n = param.Number(1)

Output:
foo.py:4: DeprecationWarning: Passing 'default' as positional argument(s) to 'param.Number' was deprecated, please pass them as keyword arguments.
  n = param.Number(1)

If we pursue with this approach, the plan I'd suggest would be to:

merge #737 before Param 2.0 is release; the documentation will also need to be updated
make the arguments keywords-only in Param 3.0
eventually make default the only allowed positional argument in Param 3.1


Is MatplotlibLocalWriter same to MatplotlibWriter?

I'm trying to save some plots to local folder by matplotlib based on this document.
However, I received ImportError below:

cannot import name 'MatplotlibLocalWriter' from 'kedro.contrib.io.matplotlib'.

I checked function names in kedro.contrib.io.matplotlib, and found similarly function MatplotlibWriter.
Are they same function? If so, I suggest to edit that documents.
Thank you for your help.

Hi @8-u8! Thank you for raising this error. What version of Kedro are you using?
In kedro 0.15.6 and kedro 0.15.7, we are deprecating MatplotlibLocalWriter in favour of MatplotlibWriter. We released a new series of datasets that have file storage abstraction, have a look at the Release notes here.
If you are using MatplotlibWriter with the YAML API in kedro 0.15.6 and kedro 0.15.7 then your catalog.yml would look like this:
results_plot:
  type: matplotlib.MatplotLibWriter
  filepath: 08_results/plots/output_1.jpg

Thank you @yetudada !
I've checked version, then it was 0.15.5....!
I will upgrade Kedro to latest version.

Upgrade and let me know if this sorts out your issue. I'll only close this issue when you have successfully managed to use the new MatplotlibWriter.

Closing this, but if you still need any help with this, feel free to reopen it.


Bio and links

Daniel García-Ruano studied experimental evolution in fission yeast during his PhD, gaining interest in computational approaches and reproducibility in science. He started collaborating with ShareYourCloning as a testing user to later dive in the code and implement new use cases. Currently, he is a non-tenured associate professor in Cell Biology at the University of Bordeaux, with a research intereset in machine learning for transcript classification.
https://x.com/soybiotec/
https://www.linkedin.com/in/dgruano/
https://orcid.org/0000-0002-5033-8013/

Updated!


Total count not updating when document gets deleted

Hi, I'm having a problem where calling .total_count on the records that elasticsearch returns will not diminish when I delete an existing document from the index. It does, however, increment when I add a document. Am I missing something here? Is there another way to get the number of extant records that I have?

Hi @emilia-friedberg .
As per docs, there is a slight latency (normally one second) from the time you index a document until the time it becomes searchable (in your case you are checking only the count).
Can you please elaborate a little more on this. Please list down the steps you are performing and then I will surely help you out. Thanks.

Hello, @anuj-verma is correct — any write operation is reflected only after a delay. To "force" the refresh of the index, either use the :refresh parameter to the write operations or call the "Index Refresh" API, but note that this can have significant performance implications.

@emilia-friedberg Is this still an issue? Were you able to resolve it by using the :refresh parameter (while keeping in mind the performance implications)?


Frame Set Background

Frame Set background is resulting in near zero value vectors everywhere in the image.

Also, the "View Background" option disappears almost immediately

Is this in both the PIV and frame extraction page?

Extraction page is where I came across the inabili9ty to see the generated background, The frame set resulting in zero value vectors everywhere is in PIV results. Sorry, I probably should have opened two issues.

That's okay. I was just wondering where to start looking. If it isn't an easy fix, I'll probably open a second ticket.

Is the "View Background" checkbox disappearing or the view background popup disappearing?

The view background popup is not appearing with the view background checkbox selected

#192 fixes background preview popup issue