CLI failing to build with docker-in-docker

I have created a reproduction repo of this issue. My project includes nx monorepo tooling, so that is included for posterity.
Filed a related issue here. https://github.com/devcontainers/features/issues/679
https://github.com/ontoneio/dc-docker-in-docker-repro
When this container is run on WSL2 with dependencies install, user can run npx nx run devcontainer:build  and these are the logs that come back.
UPDATE: When rolling the npm package version of @devcontainers/cli back to 0.49.0 AND "moby": false setting with the latest version of docker-in-docker container feature, I CAN in fact build my devcontainer docker image for publishing. This points to an issue with the @devcontainer/cli package
> nx run devcontainer:build

[2023-08-30T20:31:13.256Z] @devcontainers/cli 0.51.1. Node.js v18.17.0. linux <IP_ADDRESS>-microsoft-standard-WSL2 x64.
[2023-08-30T20:31:14.646Z] Resolving Feature dependencies for 'ghcr.io/devcontainers/features/common-utils:2'...
[2023-08-30T20:31:15.785Z] Resolving Feature dependencies for 'ghcr.io/devcontainers/features/docker-in-docker:2'...
[2023-08-30T20:31:16.290Z] Resolving Feature dependencies for 'ghcr.io/devcontainers-contrib/features/volta:1'...
[2023-08-30T20:31:17.564Z] Soft-dependency 'ghcr.io/devcontainers-contrib/features/gh-release' is not required.  Removing from installation order...
[2023-08-30T20:31:18.888Z] Start: Run: docker buildx build --load --build-arg BUILDKIT_INLINE_CACHE=1 -f /tmp/devcontainercli-vscode/container-features/0.51.1-1693427474624/Dockerfile-with-features -t ghcr.io/ontoneio/bug-repro:latest --target dev_containers_target_stage --build-arg vscode=true --build-context dev_containers_feature_content_source=/tmp/devcontainercli-vscode/container-features/0.51.1-1693427474624 --build-arg _DEV_CONTAINERS_BASE_IMAGE=packaging --build-arg _DEV_CONTAINERS_IMAGE_USER=root --build-arg _DEV_CONTAINERS_FEATURE_CONTENT_SOURCE=dev_container_feature_content_temp /home/vscode/bug-repros/dc-docker-in-docker-repro
[2023-08-30T20:31:20.026Z] #0 building with "default" instance using docker driver
#1 [internal] load .dockerignore
#1 transferring context: 2B done
#1 DONE 0.0s
#2 [internal] load build definition from Dockerfile-with-features
#2 transferring dockerfile: 5.49kB done
#2 DONE 0.0s
#3 resolve image config for docker.io/docker/dockerfile:1.4
[2023-08-30T20:31:20.628Z] #3 ...
#4 [auth] docker/dockerfile:pull token for registry-1.docker.io
#4 DONE 0.0s
[2023-08-30T20:31:20.779Z]
#3 resolve image config for docker.io/docker/dockerfile:1.4
[2023-08-30T20:31:21.079Z] #3 DONE 1.1s
#5 docker-image://docker.io/docker/dockerfile:1.4@sha256:9ba7531bd80fb0a858632727cf7a112fbfd19b17e94c4e84ced81e24ef1a0dbc
#5 CACHED
[2023-08-30T20:31:21.209Z]
#6 [context dev_containers_feature_content_source] load .dockerignore
#6 transferring dev_containers_feature_content_source: 2B done
#6 DONE 0.0s
#7 [internal] load metadata for mcr.microsoft.com/vscode/devcontainers/base:ubuntu-22.04
#7 DONE 0.1s
[2023-08-30T20:31:21.360Z]
#8 [base 1/3] FROM mcr.microsoft.com/vscode/devcontainers/base:ubuntu-22.04@sha256:fdb79b61fb4e955b4042ddb25bbae616316984bcd46c193196c6e1664a5d367f
#8 DONE 0.0s
#9 [context dev_containers_feature_content_source] load from client
#9 transferring dev_containers_feature_content_source: 56.48kB done
#9 DONE 0.0s
#10 [op_system 6/6] RUN usermod -aG docker vscode
#10 CACHED
#11 [dev_containers_target_stage 1/6] RUN mkdir -p /tmp/dev-container-features
#11 CACHED
#12 [base 3/3] RUN mkdir -p /home/vscode/.vscode-server/extensions     && chown -R vscode /home/vscode/.vscode-server
#12 CACHED
#13 [op_system 1/6] RUN mkdir /home/vscode/.volta
#13 CACHED
#14 [op_system 3/6] RUN wget https://github.com/ko1nksm/shdotenv/releases/latest/download/shdotenv --directory-prefix /home/vscode/bin/shdotenv
#14 CACHED
#15 [op_system 2/6] RUN chown -R vscode:$(id -gn vscode) /home/vscode/.volta
#15 CACHED
#16 [dev_containers_feature_content_normalize 1/2] COPY --from=dev_containers_feature_content_source devcontainer-features.builtin.env /tmp/build-features/
#16 CACHED
#17 [base 2/3] RUN if [[ -z "true" ]] ; then printf "\nERROR: This Dockerfile needs to be built with VS Code !" && exit 1; else printf "VS Code is detected: true"; fi
#17 CACHED
#18 [dev_containers_feature_content_normalize 2/2] RUN chmod -R 0755 /tmp/build-features/
#18 CACHED
#19 [op_system 5/6] RUN groupadd docker
#19 CACHED
#20 [op_system 4/6] RUN chown -R vscode:$(id -gn vscode) /home/vscode/bin/shdotenv
#20 CACHED
#21 [dev_containers_target_stage 2/6] COPY --from=dev_containers_feature_content_normalize /tmp/build-features/ /tmp/dev-container-features
#21 CACHED
#22 [dev_containers_target_stage 3/6] RUN echo "_CONTAINER_USER_HOME=$( (command -v getent >/dev/null 2>&1 && getent passwd 'root' || grep -E '^root|^[^:]*:[^:]*:root:' /etc/passwd || true) | cut -d: -f6)" >> /tmp/dev-container-features/devcontainer-features.builtin.env && echo "_REMOTE_USER_HOME=$( (command -v getent >/dev/null 2>&1 && getent passwd 'vscode' || grep -E '^vscode|^[^:]*:[^:]*:vscode:' /etc/passwd || true) | cut -d: -f6)" >> /tmp/dev-container-features/devcontainer-features.builtin.env
[2023-08-30T20:31:21.663Z] #22 DONE 0.3s
#23 [dev_containers_target_stage 4/6] RUN --mount=type=bind,from=dev_containers_feature_content_source,source=volta_0,target=/tmp/build-features-src/volta_0     cp -ar /tmp/build-features-src/volta_0 /tmp/dev-container-features  && chmod -R 0755 /tmp/dev-container-features/volta_0  && cd /tmp/dev-container-features/volta_0  && chmod +x ./devcontainer-features-install.sh  && ./devcontainer-features-install.sh  && rm -rf /tmp/dev-container-features/volta_0
[2023-08-30T20:31:22.115Z] #23 0.436 ===========================================================================
#23 0.436 Feature       : Volta (via Github Releases)
#23 0.436 Description   : Volta is a hassle-free way to manage your JavaScript command-line tools.
#23 0.436 Id            : ghcr.io/devcontainers-contrib/features/volta
#23 0.436 Version       : 1.0.3
#23 0.436 Documentation : http://github.com/devcontainers-contrib/features/tree/main/src/volta
#23 0.436 Options       :
#23 0.436     VERSION="latest"
#23 0.436 ===========================================================================
#23 0.437 bash: cannot set terminal process group (1): Inappropriate ioctl for device
#23 0.437 bash: no job control in this shell
[2023-08-30T20:31:23.619Z] #23 1.923 nanolayer
[2023-08-30T20:31:27.235Z] #23 5.494 cd /tmp/tmpz5s67sx1 && chmod +x -R . && _REMOTE_USER="vscode" _REMOTE_USER_HOME="/home/vscode" REPO="volta-cli/volta" BINARYNAMES="volta" VERSION="latest" ASSETREGEX="" BINLOCATION="/usr/local/bin" LIBNAME="" LIBLOCATION="/usr/local/lib" NANOLAYER_VERBOSE="" NANOLAYER_FORCE_CLI_INSTALLATION="" NANOLAYER_PROPAGATE_CLI_LOCATION="1" NANOLAYER_CLI_LOCATION="/tmp/nanolayer-OLRtG2g2lH/nanolayer" bash  -i  +H ./install.sh
#23 5.494 Found a pre-existing nanolayer which were given in env varialbe: /tmp/nanolayer-OLRtG2g2lH/nanolayer
[2023-08-30T20:31:28.115Z] #23 6.523 'volta-1.1.1-macos-aarch64.tar.gz' filtered by '([Mm]ac[Oo][Ss]|[Mm]ac\-[Oo][Ss]|\-osx\-|_osx_|[Dd]arwin|\.dmg)' (negative)
#23 6.523 'volta-1.1.1-macos.tar.gz' filtered by '([Mm]ac[Oo][Ss]|[Mm]ac\-[Oo][Ss]|\-osx\-|_osx_|[Dd]arwin|\.dmg)' (negative)
#23 6.523 'volta-1.1.1-windows-x86_64.msi' filtered by '(windows|Windows|WINDOWS|win32|\-win\-|\.msi$|.msixbundle$|\.exe$)' (negative)
#23 6.523 'volta-1.1.1-windows.zip' filtered by '(windows|Windows|WINDOWS|win32|\-win\-|\.msi$|.msixbundle$|\.exe$)' (negative)
[2023-08-30T20:31:28.267Z] #23 6.524 'volta-1.1.1-linux.tar.gz' filtered by '([Aa]md64|\-x64|x64|x86[_-]64)'
#23 6.524 'volta.manifest' filtered by '([Aa]md64|\-x64|x64|x86[_-]64)'
#23 6.524 'volta.manifest' filtered by '([Ll]inux)'
#23 6.524 'volta-1.1.1-linux.tar.gz' filtered by '(?i)(ubuntu)'
#23 6.524 'volta-1.1.1-linux.tar.gz' filtered by '.*static.*'
#23 6.524 'volta-1.1.1-linux.tar.gz' filtered by '(?i)(debian)'
#23 6.526 resolved asset: volta-1.1.1-linux.tar.gz
[2023-08-30T20:31:28.868Z] #23 7.190 asset recognized as an archive file
[2023-08-30T20:31:29.170Z] #23 7.463 binary members found in archive are: ['volta']
[2023-08-30T20:31:29.472Z] #23 7.735 archive recognized as library (contains additional files outside of requested binaries)
#23 7.735 extracting volta-1.1.1-linux.tar.gz into /usr/local/lib/volta
[2023-08-30T20:31:29.726Z] #23 8.068 linking /usr/local/lib/volta/volta to /usr/local/bin/volta
#23 8.133 Done!
[2023-08-30T20:31:29.876Z] #23 DONE 8.2s
#24 [dev_containers_target_stage 5/6] RUN --mount=type=bind,from=dev_containers_feature_content_source,source=common-utils_1,target=/tmp/build-features-src/common-utils_1     cp -ar /tmp/build-features-src/common-utils_1 /tmp/dev-container-features  && chmod -R 0755 /tmp/dev-container-features/common-utils_1  && cd /tmp/dev-container-features/common-utils_1  && chmod +x ./devcontainer-features-install.sh  && ./devcontainer-features-install.sh  && rm -rf /tmp/dev-container-features/common-utils_1
[2023-08-30T20:31:30.328Z] #24 0.453 ===========================================================================
#24 0.453 Feature       : Common Utilities
#24 0.453 Description   : Installs a set of common command line utilities, Oh My Zsh!, and sets up a non-root user.
#24 0.453 Id            : ghcr.io/devcontainers/features/common-utils
#24 0.453 Version       : 2.1.2
#24 0.453 Documentation : https://github.com/devcontainers/features/tree/main/src/common-utils
#24 0.453 Options       :
#24 0.453     INSTALLZSH="true"
#24 0.453     CONFIGUREZSHASDEFAULTSHELL="false"
#24 0.453     INSTALLOHMYZSH="true"
#24 0.453     INSTALLOHMYZSHCONFIG="true"
#24 0.453     UPGRADEPACKAGES="true"
#24 0.453     USERNAME="vscode"
#24 0.453     USERUID="1000"
#24 0.453     USERGID="1000"
#24 0.453     NONFREEPACKAGES="false"
#24 0.453 ===========================================================================
#24 0.459 Marker file found:
#24 0.460     PACKAGES_ALREADY_INSTALLED=true
#24 0.460     LOCALE_ALREADY_SET=true
#24 0.460     EXISTING_NON_ROOT_USER=vscode
#24 0.460     RC_SNIPPET_ALREADY_ADDED=true
#24 0.460     ZSH_ALREADY_INSTALLED=true
[2023-08-30T20:31:32.434Z] #24 2.528 Done!
#24 DONE 2.6s
#25 [dev_containers_target_stage 6/6] RUN --mount=type=bind,from=dev_containers_feature_content_source,source=docker-in-docker_2,target=/tmp/build-features-src/docker-in-docker_2     cp -ar /tmp/build-features-src/docker-in-docker_2 /tmp/dev-container-features  && chmod -R 0755 /tmp/dev-container-features/docker-in-docker_2  && cd /tmp/dev-container-features/docker-in-docker_2  && chmod +x ./devcontainer-features-install.sh  && ./devcontainer-features-install.sh  && rm -rf /tmp/dev-container-features/docker-in-docker_2
[2023-08-30T20:31:32.887Z] #25 0.454 ===========================================================================
#25 0.454 Feature       : Docker (Docker-in-Docker)
#25 0.454 Description   : Create child containers *inside* a container, independent from the host's docker instance. Installs Docker extension in the container along with needed CLIs.
#25 0.454 Id            : ghcr.io/devcontainers/features/docker-in-docker
#25 0.454 Version       : 2.4.0
#25 0.454 Documentation : https://github.com/devcontainers/features/tree/main/src/docker-in-docker
#25 0.454 Options       :
#25 0.454     VERSION="2.4.0"
#25 0.454     MOBY="true"
#25 0.454     DOCKERDASHCOMPOSEVERSION="v2"
#25 0.454     AZUREDNSAUTODETECTION="true"
#25 0.454     DOCKERDEFAULTADDRESSPOOL=""
#25 0.454     INSTALLDOCKERBUILDX="true"
#25 0.454 ===========================================================================
[2023-08-30T20:31:33.640Z] #25 1.161 DOCKER_MOBY_ARCHIVE_VERSION_CODENAMES=bookworm buster bullseye bionic focal jammy
#25 1.161 Distro codename  'jammy'  matched filter  'bookworm buster bullseye bionic focal jammy'
#25 1.170 find: '/var/lib/apt/lists/*': No such file or directory
#25 1.170 Running apt-get update...
[2023-08-30T20:31:34.046Z] #25 1.706 Get:1 http://security.ubuntu.com/ubuntu jammy-security InRelease [110 kB]
[2023-08-30T20:31:34.348Z] #25 1.947 Get:2 http://archive.ubuntu.com/ubuntu jammy InRelease [270 kB]
[2023-08-30T20:31:34.951Z] #25 2.548 Get:3 http://security.ubuntu.com/ubuntu jammy-security/universe amd64 Packages [990 kB]
[2023-08-30T20:31:35.403Z] #25 2.942 Get:4 http://archive.ubuntu.com/ubuntu jammy-updates InRelease [119 kB]
[2023-08-30T20:31:36.156Z] #25 3.747 Get:5 http://archive.ubuntu.com/ubuntu jammy-backports InRelease [109 kB]
[2023-08-30T20:31:36.888Z] #25 4.547 Get:6 http://archive.ubuntu.com/ubuntu jammy/restricted amd64 Packages [164 kB]
[2023-08-30T20:31:37.775Z] #25 5.434 Get:7 http://archive.ubuntu.com/ubuntu jammy/main amd64 Packages [1792 kB]
[2023-08-30T20:31:37.925Z] #25 5.453 Get:8 http://security.ubuntu.com/ubuntu jammy-security/main amd64 Packages [909 kB]
[2023-08-30T20:31:39.430Z] #25 6.998 Get:9 http://security.ubuntu.com/ubuntu jammy-security/restricted amd64 Packages [984 kB]
[2023-08-30T20:31:40.328Z] #25 7.988 Get:10 http://archive.ubuntu.com/ubuntu jammy/universe amd64 Packages [17.5 MB]
[2023-08-30T20:31:41.186Z] #25 8.846 Get:11 http://security.ubuntu.com/ubuntu jammy-security/multiverse amd64 Packages [44.0 kB]
[2023-08-30T20:32:02.570Z] #25 30.17 Get:12 http://archive.ubuntu.com/ubuntu jammy/multiverse amd64 Packages [266 kB]
[2023-08-30T20:32:03.623Z] #25 31.16 Get:13 http://archive.ubuntu.com/ubuntu jammy-updates/multiverse amd64 Packages [49.8 kB]
[2023-08-30T20:32:04.227Z] #25 31.79 Get:14 http://archive.ubuntu.com/ubuntu jammy-updates/universe amd64 Packages [1251 kB]
[2023-08-30T20:32:07.240Z] #25 34.84 Get:15 http://archive.ubuntu.com/ubuntu jammy-updates/restricted amd64 Packages [1010 kB]
[2023-08-30T20:32:09.197Z] #25 36.72 Get:16 http://archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages [1182 kB]
[2023-08-30T20:32:11.005Z] #25 38.57 Get:17 http://archive.ubuntu.com/ubuntu jammy-backports/main amd64 Packages [49.2 kB]
[2023-08-30T20:32:11.607Z] #25 39.19 Get:18 http://archive.ubuntu.com/ubuntu jammy-backports/universe amd64 Packages [25.6 kB]
[2023-08-30T20:32:11.719Z] #25 39.38 Fetched 26.8 MB in 38s (702 kB/s)
#25 39.38 Reading package lists...
[2023-08-30T20:32:12.169Z]
[2023-08-30T20:32:12.320Z] #25 39.86 Reading package lists...
[2023-08-30T20:32:12.771Z]
#25 40.33 Building dependency tree...
[2023-08-30T20:32:12.873Z]
#25 40.43 Reading state information...
#25 40.53 wget is already the newest version (1.21.2-2ubuntu1).
#25 40.53 ca-certificates is already the newest version (20230311ubuntu<IP_ADDRESS>).
#25 40.53 curl is already the newest version (7.81.0-1ubuntu1.13).
#25 40.53 dirmngr is already the newest version (2.2.27-3ubuntu2.1).
#25 40.53 gnupg2 is already the newest version (2.2.27-3ubuntu2.1).
#25 40.53 Suggested packages:
#25 40.53   firewalld kmod nftables
[2023-08-30T20:32:13.023Z] #25 40.57 The following NEW packages will be installed:
#25 40.57   iptables libip4tc2 libip6tc2 libnetfilter-conntrack3 libnfnetlink0
#25 40.57   libnftnl11 pigz
#25 40.57 The following packages will be upgraded:
#25 40.57   apt-transport-https
[2023-08-30T20:32:13.325Z] #25 40.90 1 upgraded, 7 newly installed, 0 to remove and 11 not upgraded.
#25 40.90 Need to get 686 kB of archives.
#25 40.90 After this operation, 3663 kB of additional disk space will be used.
#25 40.90 Get:1 http://archive.ubuntu.com/ubuntu jammy/universe amd64 pigz amd64 2.6-1 [63.6 kB]
[2023-08-30T20:32:13.897Z] #25 41.56 Get:2 http://archive.ubuntu.com/ubuntu jammy-updates/main amd64 libip4tc2 amd64 1.8.7-1ubuntu5.1 [19.8 kB]
[2023-08-30T20:32:14.500Z] #25 42.02 Get:3 http://archive.ubuntu.com/ubuntu jammy-updates/main amd64 libip6tc2 amd64 1.8.7-1ubuntu5.1 [20.2 kB]
[2023-08-30T20:32:14.952Z] #25 42.49 Get:4 http://archive.ubuntu.com/ubuntu jammy/main amd64 libnfnetlink0 amd64 1.0.1-3build3 [14.6 kB]
[2023-08-30T20:32:15.253Z] #25 42.80 Get:5 http://archive.ubuntu.com/ubuntu jammy/main amd64 libnetfilter-conntrack3 amd64 1.0.9-1 [45.3 kB]
[2023-08-30T20:32:15.856Z] #25 43.41 Get:6 http://archive.ubuntu.com/ubuntu jammy/main amd64 libnftnl11 amd64 1.2.1-1build1 [65.5 kB]
[2023-08-30T20:32:16.413Z] #25 44.07 Get:7 http://archive.ubuntu.com/ubuntu jammy-updates/main amd64 iptables amd64 1.8.7-1ubuntu5.1 [455 kB]
[2023-08-30T20:32:17.618Z] #25 45.20 Get:8 http://archive.ubuntu.com/ubuntu jammy-updates/universe amd64 apt-transport-https all 2.4.10 [1510 B]
[2023-08-30T20:32:18.182Z] #25 45.84 Fetched 686 kB in 5s (148 kB/s)
[2023-08-30T20:32:18.295Z] #25 45.86 Selecting previously unselected package pigz.
#25 45.86 (Reading database ...
 No full or partial Docker / Moby version match found for "2.4.0" on OS ubuntu jammy (amd64). Available versions:
[2023-08-30T20:32:21.897Z] #25 49.52  23.0.6+azure-ubuntu22.04u2
#25 49.52  20.10.25+azure-ubuntu22.04u2
#25 49.52  20.10.25+azure-ubuntu22.04u1
#25 49.52  20.10.24+azure-ubuntu22.04u1
#25 49.52  20.10.23+azure-ubuntu22.04u2
#25 49.52  20.10.22+azure-ubuntu22.04u1
#25 49.52  20.10.21+azure-ubuntu22.04u2
#25 49.52  20.10.21+azure-ubuntu22.04u1
#25 49.52  20.10.20+azure-ubuntu22.04u1
#25 49.52  20.10.18+azure-ubuntu22.04u2
#25 49.52  20.10.18+azure-ubuntu22.04u1
#25 49.52  20.10.17+azure-ubuntu22.04u1
#25 49.52  20.10.15+azure-1
#25 49.52  20.10.14+azure-1
#25 49.52 ERROR: Feature "Docker (Docker-in-Docker)" (ghcr.io/devcontainers/features/docker-in-docker) failed to install! Look at the documentation at https://github.com/devcontainers/features/tree/main/src/docker-in-docker for help troubleshooting this error.
#25 ERROR: process "/bin/bash -c cp -ar /tmp/build-features-src/docker-in-docker_2 /tmp/dev-container-features  && chmod -R 0755 /tmp/dev-container-features/docker-in-docker_2  && cd /tmp/dev-container-features/docker-in-docker_2  && chmod +x ./devcontainer-features-install.sh  && ./devcontainer-features-install.sh  && rm -rf /tmp/dev-container-features/docker-in-docker_2" did not complete successfully: exit code: 1
[2023-08-30T20:32:21.917Z] ------
 > [dev_containers_target_stage 6/6] RUN --mount=type=bind,from=dev_containers_feature_content_source,source=docker-in-docker_2,target=/tmp/build-features-src/docker-in-docker_2     cp -ar /tmp/build-features-src/docker-in-docker_2 /tmp/dev-container-features  && chmod -R 0755 /tmp/dev-container-features/docker-in-docker_2  && cd /tmp/dev-container-features/docker-in-docker_2  && chmod +x ./devcontainer-features-install.sh  && ./devcontainer-features-install.sh  && rm -rf /tmp/dev-container-features/docker-in-docker_2:
49.52  20.10.22+azure-ubuntu22.04u1
49.52  20.10.21+azure-ubuntu22.04u2
49.52  20.10.21+azure-ubuntu22.04u1
49.52  20.10.20+azure-ubuntu22.04u1
49.52  20.10.18+azure-ubuntu22.04u2
49.52  20.10.18+azure-ubuntu22.04u1
49.52  20.10.17+azure-ubuntu22.04u1
49.52  20.10.15+azure-1
49.52  20.10.14+azure-1
49.52 ERROR: Feature "Docker (Docker-in-Docker)" (ghcr.io/devcontainers/features/docker-in-docker) failed to install! Look at the documentation at https://github.com/devcontainers/features/tree/main/src/docker-in-docker for help troubleshooting this error.
------
[2023-08-30T20:32:21.917Z] Dockerfile-with-features:98
--------------------
  97 |     ENV DOCKER_BUILDKIT="1"
  98 | >>> RUN --mount=type=bind,from=dev_containers_feature_content_source,source=docker-in-docker_2,target=/tmp/build-features-src/docker-in-docker_2 \
  99 | >>>     cp -ar /tmp/build-features-src/docker-in-docker_2 /tmp/dev-container-features \
 100 | >>>  && chmod -R 0755 /tmp/dev-container-features/docker-in-docker_2 \
 101 | >>>  && cd /tmp/dev-container-features/docker-in-docker_2 \
 102 | >>>  && chmod +x ./devcontainer-features-install.sh \
 103 | >>>  && ./devcontainer-features-install.sh \
 104 | >>>  && rm -rf /tmp/dev-container-features/docker-in-docker_2
 105 |
--------------------
ERROR: failed to solve: process "/bin/bash -c cp -ar /tmp/build-features-src/docker-in-docker_2 /tmp/dev-container-features  && chmod -R 0755 /tmp/dev-container-features/docker-in-docker_2  && cd /tmp/dev-container-features/docker-in-docker_2  && chmod +x ./devcontainer-features-install.sh  && ./devcontainer-features-install.sh  && rm -rf /tmp/dev-container-features/docker-in-docker_2" did not complete successfully: exit code: 1
[2023-08-30T20:32:21.924Z] Exit code 1
Error: Command failed: docker buildx build --load --build-arg BUILDKIT_INLINE_CACHE=1 -f /tmp/devcontainercli-vscode/container-features/0.51.1-1693427474624/Dockerfile-with-features -t ghcr.io/ontoneio/bug-repro:latest --target dev_containers_target_stage --build-arg vscode=true --build-context dev_containers_feature_content_source=/tmp/devcontainercli-vscode/container-features/0.51.1-1693427474624 --build-arg _DEV_CONTAINERS_BASE_IMAGE=packaging --build-arg _DEV_CONTAINERS_IMAGE_USER=root --build-arg _DEV_CONTAINERS_FEATURE_CONTENT_SOURCE=dev_container_feature_content_temp /home/vscode/bug-repros/dc-docker-in-docker-repro
    at CAA (/home/vscode/bug-repros/dc-docker-in-docker-repro/node_modules/@devcontainers/cli/dist/spec-node/devContainersSpecCLI.js:463:1752)
    at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
    at async jw (/home/vscode/bug-repros/dc-docker-in-docker-repro/node_modules/@devcontainers/cli/dist/spec-node/devContainersSpecCLI.js:462:1691)
    at async itA (/home/vscode/bug-repros/dc-docker-in-docker-repro/node_modules/@devcontainers/cli/dist/spec-node/devContainersSpecCLI.js:611:22377)
    at async ttA (/home/vscode/bug-repros/dc-docker-in-docker-repro/node_modules/@devcontainers/cli/dist/spec-node/devContainersSpecCLI.js:611:20283)
{"outcome":"error","message":"Command failed: docker buildx build --load --build-arg BUILDKIT_INLINE_CACHE=1 -f /tmp/devcontainercli-vscode/container-features/0.51.1-1693427474624/Dockerfile-with-features -t ghcr.io/ontoneio/bug-repro:latest --target dev_containers_target_stage --build-arg vscode=true --build-context dev_containers_feature_content_source=/tmp/devcontainercli-vscode/container-features/0.51.1-1693427474624 --build-arg _DEV_CONTAINERS_BASE_IMAGE=packaging --build-arg _DEV_CONTAINERS_IMAGE_USER=root --build-arg _DEV_CONTAINERS_FEATURE_CONTENT_SOURCE=dev_container_feature_content_temp /home/vscode/bug-repros/dc-docker-in-docker-repro","description":"An error occurred building the image."}
Warning: run-commands command "devcontainer build --workspace-folder ./ --image-name ghcr.io/ontoneio/bug-repro:latest" exited with non-zero status code

 ———————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————

 >  NX   Ran target build for project devcontainer (1m)

    ✖    1/1 failed
    ✔    0/1 succeeded [0 read from cache]

UPDATE: I have run into a new error.
Tool Versions:
@devcontainer/cli : 0.49.0
docker-in-docker: latest OR 2.4.0
Repro Link is updated to reflect changes.
https://github.com/ontoneio/dc-docker-in-docker-repro
ERROR LOGS received below after running npx nx run devcontainer:build --verbose
> nx run devcontainer:build

[2023-08-31T00:48:11.058Z] @devcontainers/cli 0.49.0. Node.js v18.17.1. linux <IP_ADDRESS>-microsoft-standard-WSL2 x64.
[2023-08-31T00:48:12.085Z] Resolving Feature dependencies for 'ghcr.io/devcontainers/features/common-utils:2'...
[2023-08-31T00:48:13.686Z] Resolving Feature dependencies for 'ghcr.io/devcontainers/features/docker-in-docker:2'...
[2023-08-31T00:48:14.105Z] Resolving Feature dependencies for 'ghcr.io/devcontainers-contrib/features/volta:1'...
[2023-08-31T00:48:15.377Z] Soft-dependency 'ghcr.io/devcontainers-contrib/features/gh-release' is not required.  Removing from installation order...
[2023-08-31T00:48:16.516Z] Start: Run: docker buildx build --load --build-arg BUILDKIT_INLINE_CACHE=1 -f /tmp/devcontainercli-vscode/container-features/0.49.0-1693442892070/Dockerfile-with-features -t ghcr.io/ontoneio/bug-repro:latest --target dev_containers_target_stage --build-arg vscode=true --build-context dev_containers_feature_content_source=/tmp/devcontainercli-vscode/container-features/0.49.0-1693442892070 --build-arg _DEV_CONTAINERS_BASE_IMAGE=packaging --build-arg _DEV_CONTAINERS_IMAGE_USER=root --build-arg _DEV_CONTAINERS_FEATURE_CONTENT_SOURCE=dev_container_feature_content_temp /workspaces
[2023-08-31T00:48:16.574Z] ERROR: Cannot connect to the Docker daemon at unix:///var/run/docker.sock. Is the docker daemon running?
[2023-08-31T00:48:16.576Z] Exit code 1
Error: Command failed: docker buildx build --load --build-arg BUILDKIT_INLINE_CACHE=1 -f /tmp/devcontainercli-vscode/container-features/0.49.0-1693442892070/Dockerfile-with-features -t ghcr.io/ontoneio/bug-repro:latest --target dev_containers_target_stage --build-arg vscode=true --build-context dev_containers_feature_content_source=/tmp/devcontainercli-vscode/container-features/0.49.0-1693442892070 --build-arg _DEV_CONTAINERS_BASE_IMAGE=packaging --build-arg _DEV_CONTAINERS_IMAGE_USER=root --build-arg _DEV_CONTAINERS_FEATURE_CONTENT_SOURCE=dev_container_feature_content_temp /workspaces
    at Yte (/workspaces/node_modules/@devcontainers/cli/dist/spec-node/devContainersSpecCLI.js:2031:1698)
    at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
    at async mC (/workspaces/node_modules/@devcontainers/cli/dist/spec-node/devContainersSpecCLI.js:2030:1691)
    at async Vne (/workspaces/node_modules/@devcontainers/cli/dist/spec-node/devContainersSpecCLI.js:2179:22211)
    at async qne (/workspaces/node_modules/@devcontainers/cli/dist/spec-node/devContainersSpecCLI.js:2179:20144)
{"outcome":"error","message":"Command failed: docker buildx build --load --build-arg BUILDKIT_INLINE_CACHE=1 -f /tmp/devcontainercli-vscode/container-features/0.49.0-1693442892070/Dockerfile-with-features -t ghcr.io/ontoneio/bug-repro:latest --target dev_containers_target_stage --build-arg vscode=true --build-context dev_containers_feature_content_source=/tmp/devcontainercli-vscode/container-features/0.49.0-1693442892070 --build-arg _DEV_CONTAINERS_BASE_IMAGE=packaging --build-arg _DEV_CONTAINERS_IMAGE_USER=root --build-arg _DEV_CONTAINERS_FEATURE_CONTENT_SOURCE=dev_container_feature_content_temp /workspaces","description":"An error occurred building the image."}
Warning: run-commands command "devcontainer build --workspace-folder ./ --image-name ghcr.io/ontoneio/bug-repro:latest" exited with non-zero status code

 ———————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————

 >  NX   Running target build for project devcontainer failed

   Failed tasks:

   - devcontainer:build

   Hint: run the command with --verbose for more details.

The last log shows ERROR: Cannot connect to the Docker daemon at unix:///var/run/docker.sock. Is the docker daemon running?. Please check that Docker is running.
Does docker-in-docker work with the latest devcontainers CLI (0.50.2) when you install it without anything else?
{
    "name": "dc-docker-in-docker-repro",
    "image": "mcr.microsoft.com/vscode/devcontainers/base:ubuntu-22.04",
    "features": {
      "ghcr.io/devcontainers/features/docker-in-docker:2": {
        "version": "latest",
        // "moby": false,
        "dockerDashComposeVersion": "v2"
      }
    }
  }

Hi @chrmarti ,
When I only install docker-in-docker like above and install volta for node.js separately to use the @devcontainer/cli  I still get the same error.
I am using docker-desktop with WSL integration turned on. I still have access to docker somehow though, because when I run docker info I get the following. Which is really weird, I am not sure what changed that could make me lose access to the daemon.
Client:
 Context:    default
 Debug Mode: false
 Plugins:
  buildx: Docker Buildx (Docker Inc.)
    Version:  v0.11.2
    Path:     /home/vscode/.docker/cli-plugins/docker-buildx
  compose: Docker Compose (Docker Inc.)
    Version:  2.20.3+azure-1
    Path:     /usr/libexec/docker/cli-plugins/docker-compose

Server:
ERROR: Cannot connect to the Docker daemon at unix:///var/run/docker.sock. Is the docker daemon running?
errors pretty printing info

Any updates on this? @chrmarti @samruddhikhandale ?
I still have the same issues.
I can run docker from my WSL2 instance. docker run hello-world does in fact return the image and run in.
The problem stems from when I now work inside the devcontainer that is using bind mounted files in WSL2, and try to access docker. It's always met with docker: Cannot connect to the Docker daemon at unix:///var/run/docker.sock. Is the docker daemon running?.
I have tried every trick I can find and I am pretty frustrated that this seemingly started from not changing anything. Seems like the bind mounting is broken for the docker.sock.

Discussed this in the community slack channel. Using docker-outside-of-docker Feature helped fix the issue as Docker-in-docker is a separate docker daemon inside of the main container, sort of like nested virtualization. It uses a totally separate /var/lib/docker directory that is not shared with the host. Docker-outside-of-docker is a different model however where the host’s docker socket is bind mounted into the container, so docker commands executed from inside the container actually execute on the host.
Feel free to reopen if needed, thanks!


Blazor and TypeScript

The other day I tried to write my JS interop scripts in TypeScript. This worked quite well. There are documentations like this tutorial that describes how to get simple TypeScript support in C# projects and also documentation that describe how to manage npm packages in your projects. (I ended up with a more sophisticated but still simple solution with a single output file created with Webpack.) But then I searched the net for "blazor typescript" to find a .d.ts file/package for the DotNet and DotNetObject strongly typed definitions and found nothing. Also searching for "blazor" in the npm packages repository gave me no useful result. I only found the quite outdated 3rd party project @types/blazor__javascript-interop at DefinitelyTyped. One participant of that project told me finally about @microsoft/dotnet-js-interop.
My suggestion is to add a section about TypeScript to the official documentation, e.g. in Blazor ->JavaScript interop -> Overview. In my opinion you don't need to go into the deep details, but @microsoft/dotnet-js-interop should definitely be mentioned.

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

ID: 57ed3088-2f9b-f51a-fd17-0c0de2949c57
Version Independent ID: 49fa31d8-72a6-01a1-027d-6edeac9e0fc4
Content: ASP.NET Core Blazor JavaScript interoperability (JS interop)
Content Source: aspnetcore/blazor/javascript-interoperability/index.md
Product: aspnet-core
Technology: aspnetcore-blazor
GitHub Login: @guardrex
Microsoft Alias: riande

Thanks @Flachdachs ... Let's ask @mkArtakMSFT and @danroth27 to take a look at your request.

@Flachdachs ... Management is agreeable to surfacing information on @microsoft/dotnet-js-interop.
The most basic info is from the package.json file ...

Provides abstractions and features for interop between .NET and JavaScript code.

... with the link at npm ...
https://www.npmjs.com/package/@microsoft/dotnet-js-interop?activeTab=readme
... and the reference source at ...
https://github.com/dotnet/aspnetcore/tree/main/src/JSInterop
What else would be helpful, or would it be enough to merely surface its existence with the cross-links?

The minimum in my opinion is to mention that @microsoft/dotnet-js-interop exists. To be a bit more helpful the two links from my opening post can help readers to get things rolling. But the first article isn't Blazor specific, the reader has to adjust some parts to the conditions in a Blazor project. Not a big deal if you understand what you are doing and not just repeating tutorials step by step.
Also for complete newbies a short description what TypeScript is and how it can help can be useful, including the link to https://www.typescriptlang.org/ for the details and a tutorial.
The next step would be using webpack or a comparable tool. Because following the mentioned tutorials you will get one .js file for each .ts file, and you need to add references for each of them in the index.html resp. _Host.cshtml. Additionally references are different when using a Razor Class Library, but that is already described in the docs. However, webpack can create a bundled single file. But this is an advanced topic, that should be covered on a separate page. I can't tell how much JS Interop a typically project needs and how many developers have the wish to separate their code in multiple files. On the other hand it wasn't that difficult (for me) to figure out a solution after reading webpack's tutorial.

UPDATE: I'll circle around to this issue after I get caught up on .NET 8 preview coverage. It might take a few weeks to get there, but this is tracked and won't get lost. I will get back to it ASAP 🏃.

Yes, that's fine. For a full-fledged article on the subject, we'd want to have it approved before you went to the trouble of spending a lot of time on a write-up. If the content is relatively short, more like for a section of a topic, it's less of a burden if management decides not to carry the content. You can post a comment here, and then we'll take it from there.


Specify cols key when spawning pty shell

The column size param in pty.js is named ‘cols’, but the shorthand notation treats it as ‘columns’, causing the column count to not be correct.
I was seeing the issue described in zeit/hyper#1030 both on Mac and PC, and this fixed the issue.

Thanks 🙌


Problem with 3d_segmentation/brats_segmentation_3d.ipynb

Hello,
I tried this tutorial, but I don't have the waited result. I obtained a binary segmentation, whereas the title suggests multi label segmentation.
The label images have 4 labels (0 to 3) and if I comment ConvertToMultiChannelBasedOnBratsClassesd class, I have a multi label image (but the model cannot be created). If I display label image with this correction function, I obtain just two color (purple and yellow), but the example have three color (purple, yellow and green).
So I don't understand my mistake. What is the result of this tutorial ? And if it's multi label (et and I need it), where is the mistake ?
Thank you for your reading !

Sure, you can see my result below. And thanks for your answer, I was scared to misunterstand the goal of this tutorial.
image shape: torch.Size([4, 240, 240, 155])
label shape: torch.Size([3, 240, 240, 155])

No problem.
Please feel free to raise a discussion or issue if you have any more questions.
Thanks.


Direct user attention to search bar in new API

Per feedback in  https://groups.google.com/forum/#!topic/closure-library-discuss/lRtUBzLTgy8 , it's not always obvious the search bar is now the new entry point to search the API docs. Perhaps we can do something to draw user attention to the search bar?
Some ideas:

Add some "Start here" (or similar text) to the search box place holder text
Mention "use search bar above" in the landing page text
"Highlight" the search bar on the landing page

Yup, UX definitely needs some love (help is appreciated!)
Some hidden shortcuts (they're at least listed on the element titles):

The search bar is listed first in tab order
/ or CTRL+E will focus the search bar (E instead of F to avoid conflicting with browser's text find)
n opens the side nav menu

My current thinking is to make the nav menu always open on larger screens. Will try to work on it ~soon

That sounds great. I've also udpated our readme.md with some pointer text.
On Wed, Jun 29, 2016 at 1:39 PM, jleyba<EMAIL_ADDRESS>wrote:

My current thinking is to make the nav menu always open on larger screens.
Will try to work on it ~soon
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/jleyba/js-dossier/issues/73#issuecomment-229481442,
or mute the thread
https://github.com/notifications/unsubscribe/AMh5YM_EVngfRvDnyQzQRzT2iwm_KzEfks5qQtgQgaJpZM4I_Sjq
.


Transport asm.js correctly

Peephole passes and others should not traverse into functions annotated with 'use asm'.  The 'use asm' string needs to be retained.

It seems rather strange to me, to use both asm.js and Closure Compiler on the same code. But I have heard that some people do it, so I guess we could do this.

Is there any progress on this? Would be very nice to have asm.js in very hot functions without closure compiler ripping it apart into normal js code.

The "only" thing really needed is that a function with "use asm" at its beginning is just handled like a text, so that if not making it smaller, it is at least preserved 1:1 instead of loosing its performance gains...


Preconditioner

One of the method I coded in Rust is the "Conjugate gradient solver for positive-definite matrices." I see that you already coded this method. I didn't compare them yet because there's a small difference: I'm using a diagonal conditioner
for idx_iter in 1..max_iterations {
    // We're using the diagonal conditioner.
    let z = &r / &diag;
    ... standard algo, I think ...

As you know, I'm not a mathematician at all, so I can't explain you what this is and why we need it in argmin. Maybe almost nobody uses that and we shouldn't code it. I don't know. This looks like a new trait and a new template parameter, something you may be tired of :)
Is there a minimum-effort way to compare our algo? Like, using what you already coded to update the array or some magic that you know?

Preconditioning would be a nice feature! If I understand it correctly, it only requires another multiplication with a matrix (or the inverse of a matrix) with a vector. I'm however unsure how this is best done in practice. I've used preconditioning by applying the preconditioning to the system itself, but not as part of the solver. I guess that, depending on the type of preconditioning, there may be computationally efficient implementations, and we should not limit the implementation such that these become impossible. But I don't have a sufficient overview over the topic. Do you by any chance know how this is solved in other solvers?
Could you elaborate how you would solve this with a trait? From the top of my head I'd say that an optional field holding the preconditioner may be sufficient, at least for a basic implementation.

Is there a minimum-effort way to compare our algo? Like, using what you already coded to update the array or some magic that you know?

Do you want to compare performance (speed) or performance (convergence, ...)? For the latter I suppose choosing your preconditioner such that it has no effect would work. The former probably requires some code.


Breaks when upgrading to react-map-gl >= v3.3.0

Need to export a bundle instead of just the transpiled code.

For now just fixed version for react-map-gl to v3.2.10.


CCH seems to fails with the latest beta (0.96.0b0)

Describe the bug:
CCH does not seem to load, throwing this error in the home assistant logging.
Config YAML:
HA and/or Browser Error:
2019-07-11 19:55:10 ERROR (MainThread) [frontend.js.latest.201907100] http://hass.wiebel.nl:8123/community_plugin/compact-custom-header/compact-custom-header.js:210:46 TypeError: null is not an object (evaluating 'root
    .querySelector("hui-notification-drawer")
    .shadowRoot')

HA, Card, and Browser Versions:
HA 0.96.0b0, CCH 1.2.1 and any browser

It seems a bit obvious because the HA-team made a lot of change to the ui :)

I am aware and will have a "beta" version I've been working on up later today, few kinks to work out first. I will post here to let you know.

Beta works well.  Only small problem I have is getting rid of the menu button, I basically have two of them now.

Yeah, that's just how Lovelace looks now. Unless you're on a mobile device or your window is slim you will see two. You could use CCH to fix this by making an exception to hide the menu button depending on the width of your screen using a media_query.

cch:
  exceptions:
    - conditions:
        media_query: "(min-width: 1400px)"
      config:
        menu: hide

Like that for example. You could use a user_agent as well.


Manual whole-line completion with ^X^L inserts the wrong entry into the buffer.

FAQ

[X] I have checked the FAQ and it didn't resolve my problem.

Announcement

[X] I have checked Breaking change announcement.

Minimal reproducible full config
if has('vim_starting')
  set encoding=utf-8
endif
scriptencoding utf-8

if &compatible
  set nocompatible
endif

let s:plug_dir = expand('/tmp/plugged/vim-plug')
if !filereadable(s:plug_dir .. '/plug.vim')
  execute printf('!curl -fLo %s/autoload/plug.vim --create-dirs https://raw.githubusercontent.com/junegunn/vim-plug/master/plug.vim', s:plug_dir)
end

execute 'set runtimepath+=' . s:plug_dir
call plug#begin(s:plug_dir)
Plug 'hrsh7th/nvim-cmp'
Plug 'hrsh7th/cmp-buffer'
call plug#end()
PlugInstall | quit

" Setup global configuration. More on configuration below.
lua << EOF
local cmp = require "cmp"
cmp.setup {
  mapping = {
    ['<CR>'] = cmp.mapping.confirm({ select = true })
  },

  sources = cmp.config.sources({
    { name = "nvim_lsp" },
    { name = "buffer" },
  }),
}
EOF

Description
Hi,
Cool plugin! I've tried it this week for using it with LSP and really like it so far.
My only problem is that it breaks manual whole-line completion.
This seems to happen independently of other plugins, filetype, file content and doesn't depend on if the autocompletion menu was open or not.
So when I type (^X^L) to start manual line completion, then the automatic completion menu is dismissed (if it was visible), and the manual line completion menu appears, and then I can use <C-p> and <C-n> to select an entry, but when I press <CR> to accept the selected line, then a different line is inserted. This does not always happen, but in more than 50% of my attempts. I tried it with different settings for 'completeopt' and even tried to override <CR> to be used only when the menu is visible using cmp.core.view:visible(), but it made no difference. Sometimes it seems to be an off-by-one selection, but sometimes the inserted text is farther away. It happens when the line is empty, and if there's something written to complete. I've spent about 2 hours trying to fix this, and have no idea what's happening here.
Steps to reproduce
nvim -u ~/cmp-repro.vim ~/cmp-repro.vim
Insert two empty lines at the beginning of the file, go to first line.
Press ^X^L and use ^P or ^N to choose some entry.
Select the entry with <CR>.
Expected behavior
The selected line should be inserted in the buffer.
Actual behavior
Another line that was not selected is inserted in the buffer.
Additional context
Output of :version:
NVIM v0.8.0
Build type: Release
LuaJIT 2.1.0-beta3
Compiled by builduser

Running on Manjaro XFCE.

Hm... To be honest, I can't understand the root cause (but reproduced).
set completeopt=menuone,noselect,noinsert

I think the above option will improve the behavior. Could you try this?

I added that line at the beginning of the minimal reproducible config from above, but the bug is still happening.
Is it possible, as a workaround, to completely disable nvim-cmp for only manual line completion?
Another workaround is to use https://github.com/amarakon/nvim-cmp-buffer-lines but that doesn't currently work for large files.

if has('vim_starting')
  set encoding=utf-8
endif
scriptencoding utf-8

if &compatible
  set nocompatible
endif

let s:plug_dir = expand('/tmp/plugged/vim-plug')
if !filereadable(s:plug_dir .. '/plug.vim')
  execute printf('!curl -fLo %s/autoload/plug.vim --create-dirs https://raw.githubusercontent.com/junegunn/vim-plug/master/plug.vim', s:plug_dir)
end

execute 'set runtimepath+=' . s:plug_dir
call plug#begin(s:plug_dir)
Plug 'hrsh7th/nvim-cmp'
Plug 'hrsh7th/cmp-buffer'
call plug#end()
PlugInstall | quit

set completeopt=menu,menuone,noselect

" Setup global configuration. More on configuration below.
lua << EOF
local cmp = require "cmp"
cmp.setup {
  mapping = {
    ['<CR>'] = cmp.mapping.confirm({ select = true })
  },

  sources = cmp.config.sources({
    { name = "nvim_lsp" },
    { name = "buffer" },
  }),
}
EOF

In my environment, the above setup solve this problem.

I've just tried it with that file, i.e.
nvim --clean -u init.vim.reproduce_bug_in_nvim_cmp_2 init.vim.reproduce_bug_in_nvim_cmp_2
but the bug still happens.
On my first few attempts, the correct line was selected, but after about five attempts, the wrong line began to be selected.
Sometimes, another weird thing happens: I press  to insert a line, but nothing happens, as if I hadn't pressed any key at all.

I just noticed that the same problem (the wrong entry gets selected) occurs when using repeated ^X^P selection, i.e. ^X^P^X^P^X^P to select words that appear in the file in a sequence. In my books, this is a much more serious problem than ^X^L not working.
On the plus, side, I think I found a workaround that actually works: when the entry is already selected, I can just keep writing, and the correct selection keeps being inserted. In other words, as long as I avoid the Enter key, nothing bad happens. Obviously, that makes using <Up> and <Down> inconvenient, which is a bit annoying. Maybe <CR> could be made to work by a mapping that just does <C-n><C-p><Space><Backspace>, but that does seem annoyingly hacky.

Okay, so here's a hacky workaround that seems to work for me for now and actually lets me use <CR>:
['<CR>'] = function(fallback) -- ugly workaround because manual completion (not only ^X^L) is broken!
    if cmp.visible() then
        cmp.select_next_item({ behavior = cmp.SelectBehavior.Insert })
        cmp.select_prev_item({ behavior = cmp.SelectBehavior.Insert })
        vim.cmd([[call feedkeys("\<Space>\<BS>")]])
    else
        fallback()
    end
end,

Could you please provide detailed steps to reproduce?
Apparently I don't understand your actual problem

Ok, I'll try again:
Autocompletion works fine.
Manual completion invoked with ^X^L and ^X^P does not:
The problem is that using <CR> to input a selected line into the buffer, sometimes a different line is inserted into the buffer instead.
It seems weirdly indeterministic, and does not happen every time, but it happens quite often, probably >50% of my attempts.
I find it very surprising that no one has reported this so far, since ^X^L and ^X^P^X^P^X^P are useful features even if autocompletion is available.
Here's an exact sequence of keystrokes which I can use to reproduce. I've tried this several times and the result is the same every time.
Save the minimal reproducible full config from my first post as init.vim.nvim-cmp-1326-reproduce.
Save the following content as file nvim-cmp-1326-input-file:
111
222
333

where the last line is blank.
Now, in the shell, input:
nvim --clean -u init.vim.nvim-cmp-1326-reproduce nvim-cmp-1326-input-file

and then in neovim, the following keypresses:
Gi<C-x><C-l><CR>
After pressing <C-x><C-l> the buffer contains 333 (as expected), but after pressing <CR>, instead 111 will be inserted into the buffer.
Instead of <C-x><C-l> if I try it with <C-x><C-p>, the same thing happens.

@bagohart Yes. Your reproduction steps can be reproduced the problem.
I think it's depending on to the completeopt value. Can you try to change the completeopt?
In my environment, the set completeopt=menu,menuone,noselect solves the problem.
(Sorry. In my previous post, I wrote set completeopt=menu,menuone,noinsert but it's just wrong)

The bug is happening with this setting for completeopt, too.
Minimal reproducible full config: (same as above, but with added completeopt value)
if has('vim_starting')
  set encoding=utf-8
endif
scriptencoding utf-8

if &compatible
  set nocompatible
endif

let s:plug_dir = expand('/tmp/plugged/vim-plug')
if !filereadable(s:plug_dir .. '/plug.vim')
  execute printf('!curl -fLo %s/autoload/plug.vim --create-dirs https://raw.githubusercontent.com/junegunn/vim-plug/master/plug.vim', s:plug_dir)
end

execute 'set runtimepath+=' . s:plug_dir
call plug#begin(s:plug_dir)
Plug 'hrsh7th/nvim-cmp'
Plug 'hrsh7th/cmp-buffer'
call plug#end()
PlugInstall | quit

set completeopt=menu,menuone,noselect

" Setup global configuration. More on configuration below.
lua << EOF
local cmp = require "cmp"
cmp.setup {
  mapping = {
    ['<CR>'] = cmp.mapping.confirm({ select = true })
  },

  sources = cmp.config.sources({
    { name = "nvim_lsp" },
    { name = "buffer" },
  }),
}
EOF

To reproduce:
Save that file as init.vim.nvim-cmp-1326-reproduce-menu_menuone_noselect
Execute nvim --clean -u init.vim.nvim-cmp-1326-reproduce-menu_menuone_noselect nvim-cmp-1326-input-file.
Press Gi<C-x><C-l><C-p><CR>.
Again, 333 should be inserted, but 111 is inserted. This works for both ^X^L and ^X^P.

Hi! I am facing the same issue. I find the bug is happening if you move backward in any native completion menu.
As an example, if you press <C-n> in insert mode, then move around with <C-n> and <C-p>, completion works fine. However if you start with <C-p>, or start any kind of completion by moving backwards in the completion menu (for example <C-x> <C-l> <C-p>), completion breaks. It turns out completion still starts at the top. So if you press <C-p> twice, it will paste the second suggestion from the top, not from the bottom.
I tried playing around with completeopt, to no avail, it does not seem to have any effect on native completion as a matter of fact, when lsp-zero is loaded. What helps is disabling nvim-cmp, for example by setting the preset to lsp-compe. Of course then you will not have completion for LSP, however it confirms that the issue is with the configuration of nvim-cmp.
Running Neovim 0.8.2 on Fedora:
NVIM v0.8.2
Build type: RelWithDebInfo
LuaJIT 2.1.0-beta3
Compilation: /usr/bin/gcc -O2 -flto=auto -ffat-lto-objects -fexceptions -g -grecord-gcc-switches -pipe -Wall -Werror=format-security -Wp,-D_FORTIFY_SOURCE=2 -Wp,-D_GLIBCXX_ASSERTIONS -specs=/usr/lib/rpm/redhat/redhat-hardened-cc1 -fstack-protector-strong -specs=/usr/lib/rpm/redhat/redhat-annobin-cc1 -m64 -mtune=generic -fasynchronous-unwind-tables -fstack-clash-protection -fcf-protection -DNVIM_TS_HAS_SET_MATCH_LIMIT -DNVIM_TS_HAS_SET_ALLOCATOR -O2 -g -Og -g -Wall -Wextra -pedantic -Wno-unused-parameter -Wstrict-prototypes -std=gnu99 -Wshadow -Wconversion -Wdouble-promotion -Wmissing-noreturn -Wmissing-format-attribute -Wmissing-prototypes -Wimplicit-fallthrough -Wvla -fstack-protector-strong -fno-common -fdiagnostics-color=auto -DINCLUDE_GENERATED_DECLARATIONS -D_GNU_SOURCE -DNVIM_MSGPACK_HAS_FLOAT32 -DNVIM_UNIBI_HAS_VAR_FROM -DMIN_LOG_LEVEL=3 -I/builddir/build/BUILD/neovim-0.8.2/redhat-linux-build/cmake.config -I/builddir/build/BUILD/neovim-0.8.2/src -I/usr/include -I/usr/include/luajit-2.1 -I/builddir/build/BUILD/neovim-0.8.2/redhat-linux-build/src/nvim/auto -I/builddir/build/BUILD/neovim-0.8.2/redhat-linux-build/include
Compiled by mockbuild@koji

Features: +acl +iconv +tui
See ":help feature-compile"

   system vimrc file: "$VIM/sysinit.vim"
  fall-back for $VIM: "/usr/share/nvim"

Run :checkhealth for more info

@bagohart, is this still reproducing for you using your minimal config from https://github.com/hrsh7th/nvim-cmp/issues/1326#issuecomment-1366593346 on latest main branch (commit 777450f)? I had the same issue as you, still repro with your first config, but found that your second config with the completeopts set did not repro the issue -- i.e. completeopts with noselect fixed my issue. Why noselect fixes the behavior I'm observing and why it only affects a few native modes (<C-X><C-L>,<C-X><C-P>) is a deeper question.
In my observation, the base error also doesn't seem to be an off-by-1 error, but rather a sign error (it seems to reliably reverse top/bottom of menu).  It can be hard to notice because the order of the menu changes and this can make it seem more like an off-by-n. I detail more about that in the duplicate issue I filed before finding this one. This is close to the behavior described by @hmrks but is different in that the behavior I observe does not occur with <C-N> or <C-P> completion, but rather only the two <C-X> modes described above, and does not depend on initial <C-P>.
@hmrks As another user, I do not see the same behavior with <C-N> or <C-P> completion. Simply disabling nvim-cmp in lsp-zero.nvim and seeing the issue disappear is useful information, but ultimately insufficient evidence that nvim-cmp is the culprit. It only shows that lsp-zero and nvim-cmp together can cause the issue. It very well might still be nvim-cmp, but without a minimal reproducible workflow there is nothing to help the maintainer or a contributor reproduce or trace the issue to begin troubleshooting.

NVIM v0.8.3
Build type: Release
LuaJIT 2.1.0-beta3
Compiled by builduser

Features: +acl +iconv +tui
See ":help feature-compile"

OS: WSL2 running Arch Linux on Win 11

@bagohart, is this still reproducing for you using your minimal config from #1326 (comment) on latest main branch (commit 777450f)? I had the same issue as you, still repro with your first config, but found that your second config with the completeopt set did not repro the issue -- i.e. completeopt with noselect fixed my issue. Why noselect fixes the behavior I'm observing and why it only affects a few native modes (<C-X><C-L>,<C-X><C-P>) is a deeper question.

Yes, it still reproduces with the same example and procedure described above, still using the same file
111
222
333

I think I am on the same nvim version:
NVIM v0.8.3
Build type: Release
LuaJIT 2.1.0-beta3
Compiled by builduser

Features: +acl +iconv +tui
See ":help feature-compile"

   system vimrc file: "$VIM/sysinit.vim"
  fall-back for $VIM: "/usr/share/nvim"

Run :checkhealth for more info

Snippets for debugging.
:imap \ <cmd>put =execute('lua print(vim.fn.complete_info({''selected''}).selected)')<CR>
imap [ <cmd>lua require('cmp.utils.feedkeys').call(require('cmp.utils.keymap').t(string.rep('<C-P>',1)),'in')<CR>
With the above mapping, you can hit \ in insert mode and it will show you what nvim thinks is selected in the native pumenu.  You can also use [ navigate up, mimicking the feedkeys behavior that nvim-cmp is using to navigate native pumenu.
In lua/cmp/init.lua, nvim-cmp differentiates between cmp menus and native pumenus. cmp menu is checked with cmp.core.view:visible() and native menus checked with vim.fn.pumvisible(). Behavior is different depending on which type of menu is visible.

For pumvisible() native menu:

to navigate the menu up, select_prev_item uses feedkeys.... The mapping above for [ mimics this to make debugging clearer.
cmp.confirm calls complete_info. This normally gives the correct index and can be checked with the \ mapping above. If feedkeys.... <C-P>... is called first, e.g. with [ mapping above, then the selected index is wrong.

Testing just the \ mapping in nvim --clean, I was unable to get wrong index, so my initial hunch is that this isn't an upstream issue but I can't rule it out. I am not a lua or nvim expert at all, so not sure if I'll be able to tackle this but hopefully tracking down this far will help.

Repro config

CLICK ON ME! Click to expand and save as `repro_nvim_cmp_vimrc`

if has('vim_starting')
  set encoding=utf-8
endif
scriptencoding utf-8

if &compatible
  set nocompatible
endif

let s:plug_dir = expand('/tmp/plugged/vim-plug')
if !filereadable(s:plug_dir .. '/plug.vim')
  execute printf('!curl -fLo %s/autoload/plug.vim --create-dirs https://raw.githubusercontent.com/junegunn/vim-plug/master/plug.vim', s:plug_dir)
end

execute 'set runtimepath+=' . s:plug_dir
call plug#begin(s:plug_dir)
Plug 'hrsh7th/nvim-cmp'
Plug 'hrsh7th/cmp-buffer'
call plug#end()
PlugInstall | quit

set completeopt=menu,menuone,noselect

" Setup global configuration. More on configuration below.
lua << EOF
local cmp = require "cmp"
cmp.setup {
  mapping = cmp.mapping.preset.insert({
    ['<CR>'] = cmp.mapping.confirm({ select = true })
  }),

  sources = cmp.config.sources({
    { name = "nvim_lsp" },
    { name = "buffer" },
  }),
}
EOF

imap \ <cmd>put =execute('lua print(vim.fn.complete_info({''selected''}).selected)')<CR>
imap [ <cmd>lua require('cmp.utils.feedkeys').call(require('cmp.utils.keymap').t(string.rep('<C-P>',1)),'in')<CR>
nmap \\ iaaa<CR>bbb<CR>ccc<CR>ddd<CR>eee<CR>

Note the 3 maps, \ to print the complete_info index, [ to mimic the select_prev_item behavior on pumenu, and \\ to make it fast to get to an example file that shows the error.
Repro Steps

download the config above to repro_nvim_cmp_vimrc
nvim --clean -u repro_nvim_cmp_vimrc and wait to get an empty buffer
in normal mode, hit \\ which is mapped to create the example file:aaa
bbb
ccc
ddd
eee

and will put you on a newline under "eee" in insert mode
in insert mode, <C-X><C-L> to pull up the native line completion pumenu, which should have 5 lines in order from "aaa" at top to "eee" at bottom
in insert mode, [[[[ to navigate backwards in the menu 4 times, apparently selecting the "bbb" option
in insert mode, with the pumenu still visible, \\\\ to see the selected item index be put in the buffer 4 times

(I decided to keep hitting \ binding so that it goes down far enough and is not hidden by the completion menu)

Notice that the index that it is showing is 3, when it should be 1
in insert mode, <CR> to select what looks like "bbb", and see "ddd" get inserted instead. Wrong behavior, but corresponds to the complete_info index.

Some more investigation. I think this is a subtle upstream bug affecting the scripting interface for complete_info. Linked this issue in the upstream report, follow there to repro and see that complete_info is not behaving as documented.

for now, here's a different, only slightly less hacky workaround than sending <Space><BS> that relies on <C-X><C-Z> stop completion.
mapping = cmp.mapping.preset.insert({
    -- cmp.mapping.preset.insert provides <C-N>, <C-P>, etc
    ['<C-d>'] = cmp.mapping.scroll_docs(-4),
    ['<C-f>'] = cmp.mapping.scroll_docs(4),
    ['<C-Space>'] = cmp.mapping.complete(),
    ['<CR>'] = function(fallback)
        if vim.fn.pumvisible() == 1 then
            -- native pumenu
            -- workaround for neovim/neovim#22892
            if vim.fn.complete_info({'selected'}).selected == -1 then
                -- nothing selected, insert newline
                feedkeys.call(keymap.t('<CR>'), 'in')
            else
                -- something selected, confirm selection by stopping Ctrl-X mode
                -- :h i_CTRL-X_CTRL-Z*
                feedkeys.call(keymap.t('<C-X><C-Z>'), 'in')
            end
        else
            -- `nvim-cmp` default confirm action
            -- Accept currently selected item.
            -- Set `select` to `false` to only confirm explicitly selected items.
            cmp.mapping.confirm({ select = false })(fallback)
        end
    end
}),

You'll need to put the following requires somewhere sensible also:
local cmp = require'cmp'
local feedkeys = require('cmp.utils.feedkeys')
local keymap = require('cmp.utils.keymap')

Alright, now I'll stop spamming this thread. Hopefully upstream will fix the underlying issue and then we can get a better sense of if anything needs to change in nvim-cmp.

@d-r-a-b is great. I checked the vim issue thread. thank you!

@d-r-a-b I'm now on neovim 0.9.4 and cannot reproduce the bug anymore, with neither ^x^l nor ^x^p. Same for you? If so, I guess this issue can finally be closed.


[Quilt] Crash when opening Keymap controls on loader version 0.18.x

MC 1.19.2
Quilt Loader 0.18.1-beta.23
QFAPI 4.0.0-beta.24
Keymap 0.7.0-beta.0+1.19.2-fabric
To reproduce install the mod on Quilt Loader 0.18.1-beta.23, launch the game and click on "Keymap" button in settings. Loader 0.17.7 works without issues.
Logs: https://gist.github.com/SplendidAlakey/514ee26ac870c5aabe47481668b77476

Will look into this, thanks!

Seems like some breaking changes with how quilt 0.18.1 handles jar file systems,
For the time being, the workaround mentioned over at https://github.com/QuiltMC/quilt-loader/issues/142#issuecomment-1334104456, works good on my end, add -Dloader.workaround.jar_copied_mods=keymap to your java lauch args, not sure how to handle multiple mods that use the workarounds tho, perhaps comma separate them?
In any case, will continue investigating till I can find a satisfactory solution, or wait till 0.18.1 gets stable, since they quilt team might have a better solution for a later date, thanks!

Ah, yeah, I see. For the time being they've been adding erroring mods to the list of mods, that will be copied to a temp location first, so that it works out of the box. See: https://github.com/QuiltMC/quilt-loader/commit/b8d79bd5e23c0d335a04d53ae6cdc5e4658d1927, https://github.com/QuiltMC/quilt-loader/commit/233c57515ddc7dd91b164950a3fc17499cb4b336 and https://github.com/QuiltMC/quilt-loader/commit/15c9f3bea2c2268a8bcc78f69292b6b233554995. That last commit addresses specifically a server crash, which is not solved by the workaround, that works for clients, but since Keymap is a client-side mod, you can ignore it. Not sure, if a better solution is planned.

Yeah, honestly don't think its a good solution tho, even if temporary, specially for some mods that don't really plan on officially supporting quilt, since the quilt team will then have to manually keep track of all erring mods, unless they can figure out how to automatically handle those.
That said, I just published a fix for the 1.19.2 version of keymap, is now up on modrinth, under review over at cf, hope it works on your end too 🍻

Yep, it works. Thank you!


(Feature) Make Dapp react to balance changed events

#163864746
App subscribes to the account's Transfer events, and updates balance/entitlement when a change occurs.
Created an <AccountProvider/> to handle events subscriptions and share balance/entitlement to the component that requires it.

How about using Undux as store?

Sure thing!
Just to clarify, I used the context provider as a middle step before jumping to undux. As it does what we needed for this task, and doesn't populate the props with undesired data.

So maybe open a story/chore for that undux integration starting with the
balance.
We can perhaps also use undux as a pipeline to process blockchain events we
listen to
Hadar Rottenberg
Technical Lead, GoodDollar
+972-507 319 093  (telegram http://t.me/sirpy, whatsapp)  blog
https://medium.com/dablock gooddollar.org http://www.gooddollar.org/

https://www.facebook.com/TheGoodDollar
https://twitter.com/TheGoodDollar http://instagram.com/good.dollar
http://t.me/GoodDollarX
https://www.linkedin.com/company/gooddollar/
http://medium.com/@GoodDollar
http://youtube.com/channel/UC_8oVeHIUo9U8gAc2BwaviA
http://reddit.com/user/GoodDollar https://github.com/gooddollar
Join the OpenUBI https://t.me/openUBI movement!*

On Mon, Feb 18, 2019 at 1:36 PM Fernando<EMAIL_ADDRESS>wrote:

How about using Undux as store?
Sure thing!
Just to clarify, I used the context provider as a middle step before
jumping to undux. As it does what we needed for this task, and doesn't
populate the props with undesired data.
—
You are receiving this because your review was requested.
Reply to this email directly, view it on GitHub
https://github.com/GoodDollar/GoodDAPP/pull/21#issuecomment-464698895,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAo9d_rE_arof4TIyqklWp1S-uO29nv8ks5vOpBHgaJpZM4a97j2
.


fix: Remove bunx shim.

Context: https://github.com/moonrepo/bun-plugin/issues/12

Gonna wait for the new shim system to figure this out.


Compiling Error different Node.js version

Hey Guys,
i've installed Ubuntu 18.04 on my notebook and installed the newest LTS Version of Nodejs.
When i'm trying to run my electron app i am getting this error:

better_sqlite3.node'
was compiled against a different Node.js version using
NODE_MODULE_VERSION 64. This version of Node.js requires
NODE_MODULE_VERSION 57. Please try re-compiling or re-installing

Does anyone know how to fix it? Do i have to downgrade my nodejs version?

rm -rf node-modules
npm install

You need to reinstall it after switching to a new Nodejs version.

rm -rf node_modules
npm install

You need to reinstall it after switching to a new Nodejs version.

I've downgraded nodejs to 8.10.0 and npm to 3.5.2. The problem is that better-sqlite3 and electron 3.10 Version don't work together. Electron Version 2.0.6 works fine for me. With which Version of electron did you test your modul?

Ahhh, for Electron, you'll need to use electron-rebuild. In fact there's a dedicated Electron Help Thread

Ahhh, for Electron, you'll need to use electron-rebuild. In fact there's a dedicated Electron Help Thread.

Thanks!
I've installed electron-rebuild
node_modules/.bin/electron-rebuild -f -w better-sqlite3
After this it worked!


Any plan to remove "ALPHA"?

As 1.9.20, KMP is stable and ready for production, maybe it's the right time to remove "ALPHA" in this library version name?

Definitely! There are still some things that need to be done before we can call this library stable. Shouldn't bee too long though 🙂

I'd love if we could change to a standarized machine parsable versioning format.
Renovate just pushed an update:
        )
    ],
    dependencies: [
-       .package(url: "https://github.com/rickclephas/KMP-NativeCoroutines.git", exact: "1.0.0-ALPHA-25")
+       .package(url: "https://github.com/rickclephas/KMP-NativeCoroutines.git", exact: "1.0.0-ALPHA-9-spm-rxswift")
    ],
    targets: [
        .binaryTarget(


Bug: magic link login fails from TBS tablet in Outlook

Summary
Users trying to login with a @tbs-sct.gc.ca email address are getting a Magic link invalid error when they attempt to login from their TBS tablet using Outlook.
Using the @tbs-sct.gc.ca email address works properly through the iPhone mail client.

This is now working in Staging.  We still need to verify that expired magic link items are deleted as expected from the table.

Confirmed that expired items are being deleted from the table.


baseline metrics

As a baseline, we could use the same metrics karlis used in innovation sweet spots - we could also use his code from the repo to calculate i.e.:

#of orgs founded per topic (pending topic definition: i.e. crunchbase category, cluster etc.)
#of funding rounds per topic per topic (pending topic definition: i.e. crunchbase category, cluster etc.)
Overall funding per topic

We could also join on patent assignees and look at the number of patents per topic.
After that, we could also calculate more complex indicators around emergence metrics, look into novelpy

what can we take from innovation sweet spots?

related to #57, #58, #59


Need to add session.id on all data in iOS

Currently, Session.id is only applied to view load traces.

in pr #126


Opportunity to delete and restore the deleted photo at the same window

A great facepalm.... We don't have option of deleting photo for users.
So it would be better to add this amazing feature for our dear users.
And...
Sometimes users regret they deleted their photos and want rapidly to get them back.
At that moment, users need to upload these photos again in other window and they said it isn`t easy for them - in that case, you will do a lot of actions.
It will be good to add this option restoring deleted photos in the same window in which you delete ones.
I think in future we will come up with how it need to look like ( I am about the icon of deleting the photo - maybe "X", I really don't know now).

Check also #31

button for deleting can appear on hover


Adjust behavior of ['tool', , 'continue'] to always fail on fatal error

I think the current behavior of ['tool', <tool> ,'continue'] is unideal. It's necessary in some cases because your tool produces nonfatal errors, but even in these cases I think you don't want the flow to continue running if the tool errors out with a nonzero status, since in that case future steps are probably pretty likely to fail.
This PR proposes the simplest possible change, which is to always kill the flow if the tool exits with a nonzero status. Another proposal that I'd be happy to implement would be to make 'continue' take a few possible values, something like:

"never": always quit on any error condition
"nonfatal": only quit on fatal errors (always continue if tool quits successfully)
"always": flow always continues

Are we interpreting this as continue on error on 'self.error' or an exeuctable error code. There is a fair number of tools (open/closed) that supports this behavior, but I agree that there might be room for more than a binary 1/0 choice.
https://docs.github.com/en/actions/using-workflows/workflow-syntax-for-github-actions#jobsjob_idstepscontinue-on-error
From Make:
-i, --ignore-errors
Ignore all errors in commands executed to remake files.

I hadn't considered the self.error case, but the current implementation of this parameter is that it applies to both the "errors" metric (otherwise we always quit if a tool post_process() finds errors in the logfile) as well as executable error code. If we want to have it be able to apply to both, I think a third option is useful, since there are cases where I'd want the flow to continue if the tool reports errors but a zero return code (generally indicating nonfatal errors), but quit early if the tool returns a different return code (generally indicating fatal errors).

tool, continue should be fed into tool directly
always quit if tool returns error code
separate switch for controlling flow continue behavior

Working on addressing the changes from our offline discussion now, and I've come across a few decisions that I think could warrant discussion:

Before merging, I plan to add an option back to the error check at the end of _runtask(). One question though: should we make this error check a special case, or should we perhaps broaden it to a check of all flowgraph goals? I could see arguments either way, since errors clearly seem like a special case to me. However, using the goals could make things a little more flexible/configurable, and they aren't currently checked by anything except min/max functions right now.
Should we keep the return codes in post_process()? It looks like all our tools return zero right now, and they can always increment the error metric on error (which can be used to kill the flow depending on configuration), and they can throw an exception for something truly fatal. Not sure what the use case of this third error signalling mechanism is.
We mentioned self.error briefly, so I spent some time thinking about what seems most intuitive there. I opened a separate issue (#1054) with my thoughts on that since it feels like a whole other can of worms.


Remove Recovery Services Vault  -> Get-AzRecoveryServicesBackupContainer: A parameter cannot be found that matches parameter name 'Status'.

Since I'm lazy I just run the script in the azure portal shell.  I needed to remove the "-Status Registered" parameter for the Get-AzRecoveryServicesBackupContainer  function because I got the error:  A parameter cannot be found that matches parameter name 'Status'.
Just wanted to let you know so you might could update / double check the script.
PS /home/XXXXXX> Get-AzRecoveryServicesBackupContainer -ContainerType AzureVMAppContainer -Status Registered -VaultId $VaultToDelete.ID | Where-Object {$_.ExtendedInfo.WorkloadType -eq "SQL"}

Get-AzRecoveryServicesBackupContainer: A parameter cannot be found that matches parameter name 'Status'.

Thanks for raising the issue!, I didn't even see this come through on my emails, so apologies for the late reply.  That should be it updated now.


Add openDirection prop

Addresses #648.

Add openDirection prop to <DateRangePicker/>, <SingleDatePicker/>, <DateRangePickerInputController/>, <DateRangePickerInput/>, <SingleDatePickerInput/>, `
Add SCSS variables for input font size, padding, etc. (used in calculation for open-up absolute positioning)
Add stories and tests for new prop

Coverage remained the same at 86.243% when pulling 20e3da65b290d640c168e88ea9d48581a0a5a6d7 on timhwang21:timhwang21/648-open-upwards into 83d55bfc6f617c7303c524899f3380634a8bbf21 on airbnb:master.

Coverage remained the same at 86.473% when pulling 20d30445a7ee150e8eb7e690c331bd7e1d2617fb on timhwang21:timhwang21/648-open-upwards into 9685cc94710cf52383e566813cc03c26f7482d5f on airbnb:master.

Is there anything stopping this being merged currently? Would love to see this go in!

Ah, I'll resolve the merge conflicts when I have a sec, hopefully today or tomorrow.

Coverage remained the same at 86.5% when pulling cdf779e14e0e07ccf61c1ed7e934c7698787e934 on timhwang21:timhwang21/648-open-upwards into 2d56f39e2a971354984b568f0d10dacd7bd8eea2 on airbnb:master.

Cheers @timhwang21 @majapw !

@majapw - so can we take care of singleDatePicker based on viewport height or width?
so in my case by default i want to open calendar down, and if i am at the bottom of the page want calendar to open Up.
please advise?
thanks


Please remove logback dependency

The project currently has a runtime dependency on logback. As far as I can see superflously. Please remove it, I decide my preferred logging framework myself.
https://github.com/natty-parser/natty/pull/58

@mccartney ?


Refactor Langmuir.get_motive

The Langmuir.get_motive method should be refactored to correspond to the name and functionality of TECBase.motive.

[ ] Rename to motive.
[ ] Update documentation to be consistent with TECBase.
[ ] Refactor.

Related issues

#111

I'm closing this issue because it isn't really atomic and the spirit of this issue is encompassed by the refactor Langmuir class milestone.


Scientific name

Small QoL improvement would to also print out the scientific name corresponding to the NCBI tax ID

Agreed (and no idea why I did not think of it earlier)! Will definitely include this in the next version.


PS check command error on Windows 11

Greetings, I know that Windows 11 is not tested for this project, but, maybe is a good idea to review about it.
I was just testing the powershell command to check if the hardware is allowed to use, and got this error.
$asushw = Get-CimInstance -Namespace root/wmi -ClassName ASUSHW
Get-CimInstance : Invalid class
At line:1 char:11
+ $asushw = Get-CimInstance -Namespace root/wmi -ClassName ASUSHW
+           ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : MetadataError: (root/wmi:ASUSHW:String) [Get-CimInstance], CimException
    + FullyQualifiedErrorId : HRESULT 0x80041010,Microsoft.Management.Infrastructure.CimCmdlets.GetCimInstanceCommand

This is an expected error on unsupported hardware or the command should be different to check on Windows 11?
I am testing this on this version
Name                           Value
----                           -----
PSVersion                      5.1.22621.3810
PSEdition                      Desktop
PSCompatibleVersions           {1.0, 2.0, 3.0, 4.0...}
BuildVersion                   10.0.22621.3810
CLRVersion                     4.0.30319.42000
WSManStackVersion              3.0
PSRemotingProtocolVersion      2.3
SerializationVersion           <IP_ADDRESS>

Win11, and i have the error too

Same here, Win11. Same error.


Multiple vuetables

can more than 1 vuetable be setup on the same page? if so, how does one be sure loading, sorting, etc get triggered on each individual vuetable instead of on all?
it's probable we'll want to use more than one on a page, i.e. for a dashboard page showing different tables of data.
note: i'm using the dist .js file for vuetable...

@clemsontiger Technically, you can have more than 1 Vuetable instance on the same page and it should work without interfering with each other if the API endpoint is not the same. However, you will have to ref differently and be careful about your logic when interacting with each API endpoint.
I've demonstrated in the previous version of Vuetable here which work with Vue 1.x. But the concept is more or less the same, you'll have to try out in a small test project (where the code and be shown). And if you're stuck, I can see the code and give you the advice.

@clemsontiger For example I extracted all vuetable related stuff into one component (sorting, refresh etc) and pass only the table related props to it (columns, api url, sorting data) without having to worry too much about loading/sorting works internally.

Thanks all. I'll spend more time on it.. a working example of multiple vuetables along with refreshing and/or searching individually would be awesome if you have the time, but understand if you do not.

@cristijora do you have an example showing of how you "... extracted all vuetable related stuff into one component (sorting, refresh etc) and pass only the table related props to it (columns, api url, sorting data) without having to worry too much about loading/sorting works internally."? I'd love to see how to setup independent vuetables this way.

I don't have one but I can make a fiddle I guess

@cristijora I'd be very appreciative.

This could be a starting point http://jsfiddle.net/z11fe07p/2074/
Probably extracting the api url as an endpoint would also be a good idea. The main idea is to make a component together with pagination, sorting etc and then to extract the props which are meaningful (fields, api-url etc)

Thank you. that's a big help to get me going.

@cristijora humor me, but how do I set the a component prop directly instead of hooking it to the parent Vue? Trying to extract the api-url, but doesn't seem to work. http://jsfiddle.net/clemsontiger/g8oseayy/3/
thanks...

You had some typos http://jsfiddle.net/g8oseayy/8/
Use v-bind:prop="variableName" if you reference a variable or shorthanded :prop="variableName"
v-bind:api-url="apiUrl"
Use prop="some string value" if you want to reference a string directly
api-url="https://vuetable.ratiw.net/api/users"

ugh, sorry. I'll try to stop bothering you with vue 101 questions. thanks again.

Feel free to write on vuejs gitter channel https://gitter.im/vuejs/vue#utm_source=notification&utm_medium=email&utm_campaign=unread-notifications
Since these are more general vue related questions rather than vue-table. You can get a faster response there if you have a fiddle with you :)

doing pretty good now, but can't seem to get it right to be able to define special fields via slots.  I followed the documentation at:  https://vuejs.org/v2/guide/components.html#Scoped-Slots and https://ratiw.github.io/vuetable-2/#/Special-Fields?id=-__slot
here's the fiddle that's not working: http://jsfiddle.net/clemsontiger/g8oseayy/9/

@cristijora also not sure how to refresh the component from the parent Vue... for instance if one has a filter external to the component...

@clemsontiger You cannot simply pass scoped slot down into the underlying component in template based component. You'll have to use render function based component only as pointed out here.
But there are a few new lesson from Vuetable Tutorial that will walk you through the process in lesson 17. I would suggest you started from lesson 14 so that you don't accidentally miss on anything.

@ratiw thanks, this is helpful. one quick thing though, I'm trying to setup the filter with my component wrapper, and on the mounted it calls $on
this.$events.$on('filter-set', eventData => this.onFilterSet(eventData));
I'm getting a: "Cannot read property '$on' of undefined" Keep in mind i'm using the CDN dist javascript library. Do i have to reference $on some other way?

@ratiw Also, in the tutorial you say "As of the current release of Vue 2.3, there is still no way to pass the scoped slot down into the component via template. " Does this mean a future version will alllow to pass scoped slot without the user of render? uses a template is much clearer to understand....

@clemsontiger Did you install vue-events as stated in the tutorial? The $events is only made available when you install vue-events plugin.
For the scoped slot, that's what I've read the answer from the Vue.js team member in the forum. I also thought that it is possible, but we'll have to wait and see. They might already have their hands full at the moment.

@ratiw no, since I'm using the JavaScript vuetable-2.js file, I assumed vue-events was bundled in with it. I'm not sure but I think $emit works with cuetable-2.js, so not sure why $on does not. I guess I'll have to find a JavaScript vue-events.js file as well?

@clemsontiger Please go through this tutorial.

@ratiw, yes I saw this, but again I'm not using webpack to bundle everything, I'm using the standalone vue able-2.js file. I guess I'll have to find a non webpack vueevents.js file to include.... thanks

For the published NPM package, you can almost always use https://unpkg.com/<package_name> to get that. Try https://unpkg.com/vue-events.
Also, if the project exists on GitHub and the repo contains the dist file, you can pull those file using the following syntax as well.
https://rawgit.com/<username>/<pacakge_name>/<branch>/dist/<file>

For example, Vuetable-2
https://rawgit.com/ratiw/vuetable-2/master/dist/vuetable-2.css

https://rawgit.com/ratiw/vuetable-2/master/dist/vuetable-2.js

https://rawgit.com/ratiw/vuetable-2/master/dist/vuetable-2-full.js

didn't know you could do that, thanks! really appreciate all the help.

@ratiw great. I've got it all working now for single vuetable. Now just trying to determine how I can have multiple, separate filters for each vuetable.

I think someone had already asked this question. try searching the issues, you might find the answer.

@ratiw yes, I found it, thanks. Unfortunately it sounds like he got it to work by building the Filter component directly into his vuetable component, which I'd prefer not to do as we'll be implementing in a variety of way where the filtering content will not always be required and  when it is used, could differ depending on the scenario...
I'll go ahead and close this issue though, as I was successful in being able to setup multiple vuetables on the same page and each have its sorting, paging, and api source independent of the other. Along with getting the slots to work (albeit with using the render function).
Again, thanks for humoring me and helping me out, even though I'm not using vuetables in the typical webpack bundling way...
@cristijora really appreciate all your help as well.


Look for any open pull requests in the repository with the title "e2e-tests update" and
see if there are recent e2e-tests updates that will be applicable to your change.

/retest

Switching to draft because it looks like SpaceRequests do not work the konflux-ci namespace because that's not a tenant namespace. The controller just completely ignores it.


MLP: Simplify momentum and Nesterov updates

Momentum updates are complicated due to Nesterov requiring an initial update before gradient calculations. There is, however, a different form of the Nesterov update that can be cleanly performed after the regular update, simplifying the code.
Note: the gradientInPlace update for zero momentum is still retained without the velocity vectors since it avoids copying the gradient vectors.

Refer to this link for build results (access rights to CI server needed):
https://builds.apache.org/job/madlib-pr-build/656/

Refer to this link for build results (access rights to CI server needed):
https://builds.apache.org/job/madlib-pr-build/660/

Refer to this link for build results (access rights to CI server needed):
https://builds.apache.org/job/madlib-pr-build/662/

is this ready to merge?


[Feature Request] Leverage Bisq API inside Sparrow

Description
Bisq is the closest form to a decentralized platform to acquire and sell non-KYC coins the bitcoin space has produced in its over 10 years of existence. It lacks liquidity though, as only power users seem to leverage the platform.
With release of its version v1.9.1  the developers have implemented an API. It is documented here and here. According to the docs the API allows you to

"...access local Bisq daemon API endpoints, which provide a subset of the Bisq Desktop application's feature set: check balances, transfer BTC and BSQ, create payment accounts, view offers, create and take offers, and execute trades."

Sparrow and Bisq are both written in Java. There are already example snippets for the implementation of the capabilities in the second documentation reference provided above. It would be amazing to see Sparrow implement these features in a nice and less resource intensive way than the current Bisq GUI. This would be a big step for Sparrow but I feel it needs some discussion as it somewhat shifts the focus from a sole wallet to a more holistic piece of bitcoin software. Some thoughts below.
Discussion
Positive Aspects:

Helps to introduce people to Bisq, the only somewhat censorship resistant way to trade bitcoin p2p (really important in the future imho)
Liquidity growth for all Bisq users
Unique feature for Sparrow Wallet, confirming its lead in the space and could be the next "big thing" for Sparrow to aim for
Holistic approach: buy/sell, store, and coinjoin bitcoin in one single wallet

Problematic Aspects:

Adds complexity to Sparrows codebase (?) and the wallet UX/UI-flow
Imports problems of Bisq into Sparrow (think unhappy users that don't understand how the Bisq trading system works and blame Sparrow for it)
Increases the hardware demand for running Sparrow (?)
Draws attention from potential "wallet" features which can't be implemented bc of the shifted focus

What else? Would appreciate a good discussion if this is something worthwhile to consider. Maybe you could levereage your reach on Twitter @craigraw if you're not completely against such a direction for your project.

I like the concept of course, as I am a power user of both software tools. A good start could be integrating the bisq wallet with sparrow's implementation of whirlpool. Instead of using the wallet integrated into the bisq platform, you could instead import the seed into sparrow and use the whirlpool features when signing deposits, etc. One can do this now, but with a separate wallet (the external wallet option for funding a trade). Perhaps we could do this today by simply copying the seed and derivation for the bisq wallet into sparrow and doing all the work in the sparrow wallet. It should reflect on the bisq application in parallel. I'll have to play with that. Coinjoining into and out of a trade sessions is best practice, and this could make it a smoother process.

Bisq is a temporary proxy between fiat and bitcoin until bitcoin is established as The New World Monetary Standard.
With that in mind, in the future we won't need BISQ, but will need coinjoin.

Since this isn't twitter I will not argue with you and let you in the believe that this just somehow materialized out of nowhere.

i think it takes a long time until other currencys are extinct. i think with most cryptocurrencys one can use htlc's to trade with no need of an escrow. one could "hide" bisq behind some options where a warning appears tthat you should read about bisq first. or hide it like whirlpool behind "add acounts"


Update Helm release thanos to v12

This PR contains the following updates:

Package
Update
Change

thanos (source)
major
11.5.5 -> 12.8.3

Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.

[ ] If you want to rebase/retry this PR, check this box

This PR has been generated by Renovate Bot.

Renovate Ignore Notification
Because you closed this PR without merging, Renovate will ignore this update. You will not get PRs for any future 12.x releases. But if you manually upgrade to 12.x then Renovate will re-enable minor and patch updates automatically.
If you accidentally closed this PR, or if you changed your mind: rename this PR to get a fresh replacement PR.


[UI] Runtime framework selection in model deployment - dropdown is available only if there's multiple selection

rh-pre-commit.version: 2.3.2
rh-pre-commit.check-secrets: ENABLED

Thanks @rnetser can you please add ODS-CI result (screenshot or jenkins partial link) ?

Thanks @rnetser can you please add ODS-CI result (screenshot or jenkins partial link) ?

note that the test is not completed as data connection fails


Automatically start "unify all" after the editor state is loadded

Add optional automatic "unify all" action right after the mm-lamp page loaded. This will add time for the initial loading. So experienced users may turn this off. But for new users this will allow them to see green checkmarks and visualizations without unifying first. This will be useful for small examples distributed via URL.
This also may be implemented via a parameter in the URL. So the author of the URL decides how the page should open. Probably this second option is better.

I like this idea!

This feature is implemented in version 22. There is a new setting Automatically "Unify All" on the settings tab. It is On by default. When it is On, mm-lamp invokes "unify all" each time the editor content is changed. As a side effect, it closes this issue because this new feature invokes "unify all" after opening an editor by navigating to an mm-lamp URL too.


Bug report

The problem
Apps which are created via the Instance will not be deleted if I change the name.
e.g. Created an App "Test" which I then renamed into "Wetter" Both Apps were still active and I had to manually delete the app in the objects list
Version of nodejs
16.19.1
Version of ioBroker js-controller
4.0.24
Version of Adapter
0.008
Operating system running ioBroker
Debian
Checklist of files to include below

[X] iobroker.current.log (Please share the logs in debug mode)
[ ] Contents of the JavaScript browser console (always include in cases of issues with the user interface)

Additional information & file uploads
No response

Just use lower case letters for app names


Cross adapter associations generate incorrect child operations

While testing more associations between sails-memory and sails-mysql, I ran into a bug where populating all of my record's associations would cause the record to not be found.  The problem only occurred when I included the sails-mysql model in the associations along with more than one association from sails-mysql.
I ultimately tracked down the problem in query/finders/operations.js on line 214.  It appears that while building up the operations, it attempts to find child operations of previous operations, but doesn't check if it's already set the child of that operation and overwrites it.
By modifying this check so that it won't set the child if there already is one, it creates a new operation that runs correctly.
I admit that I don't fully understand the consequences of doing this, but it works for my case.  It seems like it should be possible to make the child operations a list, which would probably also fix it.
I'm going to submit a pull request that fixes my case, and if I encounter further problems I can try extending it to make it a list.

@bradshja, would you mind adding a test to your PR please?

Moved #976 from @stellarashes here:

When I set a cross database association in my model, calling populate on the association would result in empty object for that member, whereas populating the association in the same database worked as expected (both the associations are 1-1).  After much debugging, I realized the results from the same database had the query results for population with the key of child key, whereas the cross database had the results with the key of the alias.  Further debugging showed that this key, being an alias, gets overwritten during the _transformer.unserialize() method, resulting in the row(s) from the other database being lost, and eventually gets resolved to an empty object.  When I've set populate.js line 54 from alias to fkToChild, everything worked as expected (but of course it caused unit tests to fail).  Was this intentional? (version 0.10.21 of waterline)

@stellarashes, there is an open PR for this, #848 can you try it please?

@stellarashes, thanks for investigating! I've tried to run your code change suggestion against some cross connection associations tests I've created in https://github.com/balderdashy/waterline-adapter-tests/commit/dc7c871377b2a6e2c89f1719c9675309cf966c6e and it actually broke more tests than are currently broken... :disappointed:  I suppose there is some issue with populate.js#L54 but the solution will probably have to be different....

Should be fixed by #925 / #984, please re-open if the issue persists.


Timing attack

I have a theoretical question about this snippet of code:
        // To keep safe from timing-attacks we iterate *all* possible codes even though we already may have
        // verified a code is correct. We use the timeslice variable to hold either 0 (no match) or the timeslice
        // of the match. Each iteration we either set the timeslice variable to the timeslice of the match
        // or set the value to itself.  This is an effort to maintain constant execution time for the code.
        for ($i = -$discrepancy; $i <= $discrepancy; $i++) {
            $ts = $timetamp + ($i * $this->period);
            $slice = $this->getTimeSlice($ts);
            $timeslice = $this->codeEquals($this->getCode($secret, $ts), $code) ? $slice : $timeslice;
        }

        return $timeslice > 0;

I wonder if the iteration of all possible code is really needed to keep safe from timing attack.
Eventually, if we do early return as soon as a code is correct, the only leaked information is the number of time slice checked.
What do you think?

It's a remote (if at all) chance in this particular case, but timing side-channel attacks are very real. It's a small effort to sidestep it with this code, why not do it? It's the reason hash_equals exists. The 'early exit' would save us from a 'few' CPU cycles but I think that would be a micro-optimisation.

It's a remote (if at all) chance in this particular case, but timing side-channel attacks are very real. It's a small effort to sidestep it with this code, why not do it? It's the reason hash_equals exists. The 'early exit' would save us from a 'few' CPU cycles but I think that would be a micro-optimisation.

Precisely, I would like to know, in this particular case, if that small effort is done to have peace of mind (given the micro-optimization may not worth it), or if there is an identified exploit that could use the leak of that particular information.
It's like the comment in the codeEquals function:
        // In general, it's not possible to prevent length leaks. So it's OK to leak the length. The important part is that
        // we don't leak information about the difference of the two strings.

So it seems to be OK to leak the length. Maybe would it be OK to leak "the number of slices checked"? (regardless of the motivation do the micro-optimization)

Precisely, I would like to know, in this particular case, if that small effort is done to have peace of mind (given the micro-optimization may not worth it), or if there is an identified exploit that could use the leak of that particular information.
It's like the comment in the codeEquals function:
        // In general, it's not possible to prevent length leaks. So it's OK to leak the length. The important part is that
        // we don't leak information about the difference of the two strings.

So it seems to be OK to leak the length. Maybe would it be OK to leak "the number of slices checked"? (regardless of the motivation do the micro-optimization)

It's ok to leak the length since we can assume any attacker knows the length anyway (they could simply create an account and see what kind of codes they get). Also, the number of possible (realistic) lengths is limited to just a handful.

Maybe would it be OK to leak "the number of slices checked"?

It won't be horrible if it was leaked, but, in general, you try to leak as little as possible. For the length there's no real solution (padding it to a fixed length wouldn't help since the padding itself would take a measurable amount of difference in time for each length) but for the number of slices we can easily check them all and make the operation constant time.
Out of curiosity: Why are you asking? What is it that you're after?

It's ok to leak the length since we can assume any attacker knows the length anyway (they could simply create an account and see what kind of codes they get). Also, the number of possible (realistic) lengths is limited to just a handful.

Maybe would it be OK to leak "the number of slices checked"?

It won't be horrible if it was leaked, but, in general, you try to leak as little as possible. For the length there's no real solution (padding it to a fixed length wouldn't help since the padding itself would take a measurable amount of difference in time for each length) but for the number of slices we can easily check them all and make the operation constant time.
Out of curiosity: Why are you asking? What is it that you're after?

It's just a question from a curious (and maybe pedantic?) developer.
Thank you for your time and for the answer, it's clear to me.

It's just a question from a curious (and maybe pedantic?) developer.
Thank you for your time and for the answer, it's clear to me.