Failed to build base image: isaac_ros_dev-aarch64, aborting.

I have native installation in NVME, the guide says is more direct but there is no steps for that , just for add a nvme in a existent SD o eMMC installation. I did the sanity tests and everything appears right, on different my docker is installed in /var/lib/docker , jetpack installed it there.
I have no clue of docker, so no idea, /var/lib is a directory that needs sudo. following the only guide that there is for nvme, I would need make an SSD disk inside the NVME which doesn't make sense.
nrover@nrover:~/workspaces/isaac_ros-dev/src$ git clone https://github.com/NVIDIA-ISAAC-ROS/isaac_ros_visual_slam
Cloning into 'isaac_ros_visual_slam'...
remote: Enumerating objects: 359, done.
remote: Counting objects: 100% (84/84), done.
remote: Compressing objects: 100% (63/63), done.
remote: Total 359 (delta 26), reused 50 (delta 20), pack-reused 275
Receiving objects: 100% (359/359), 199.30 KiB | 857.00 KiB/s, done.
Resolving deltas: 100% (145/145), done.
Filtering content: 100% (29/29), 332.96 MiB | 3.35 MiB/s, done.
nrover@nrover:~/workspaces/isaac_ros-dev/src$ git clone https://github.com/NVIDIA-ISAAC-ROS/isaac_ros_common
Cloning into 'isaac_ros_common'...
remote: Enumerating objects: 758, done.
remote: Counting objects: 100% (162/162), done.
remote: Compressing objects: 100% (110/110), done.
remote: Total 758 (delta 64), reused 79 (delta 47), pack-reused 596
Receiving objects: 100% (758/758), 451.25 KiB | 1.50 MiB/s, done.
Resolving deltas: 100% (268/268), done.
Filtering content: 100% (8/8), 806.54 KiB | 627.00 KiB/s, done.
nrover@nrover:~/workspaces/isaac_ros-dev/src$ git clone https://github.com/NVIDIA-ISAAC-ROS/isaac_ros_nitros
Cloning into 'isaac_ros_nitros'...
remote: Enumerating objects: 1377, done.
remote: Counting objects: 100% (1377/1377), done.
remote: Compressing objects: 100% (892/892), done.
remote: Total 1377 (delta 448), reused 1262 (delta 342), pack-reused 0
Receiving objects: 100% (1377/1377), 607.87 KiB | 1.53 MiB/s, done.
Resolving deltas: 100% (448/448), done.
Filtering content: 100% (82/82), 229.49 MiB | 3.60 MiB/s, done.
nrover@nrover:~/workspaces/isaac_ros-dev/src$ cd ${ISAAC_ROS_WS}/src/isaac_ros_common && \
>   ./scripts/run_dev.sh ${ISAAC_ROS_WS}
Error: Failed to call git rev-parse --git-dir: exit status 128
Building aarch64.ros2_humble.user base as image: isaac_ros_dev-aarch64 using key aarch64.ros2_humble.user
Using base image name not specified, using ''
Using docker context dir not specified, using Dockerfile directory
Resolved the following Dockerfiles for target image: aarch64.ros2_humble.user
/home/nrover/workspaces/isaac_ros-dev/src/isaac_ros_common/scripts/../docker/Dockerfile.user
/home/nrover/workspaces/isaac_ros-dev/src/isaac_ros_common/scripts/../docker/Dockerfile.aarch64.ros2_humble
Building /home/nrover/workspaces/isaac_ros-dev/src/isaac_ros_common/scripts/../docker/Dockerfile.aarch64.ros2_humble as image: aarch64-ros2_humble-image with base:
[+] Building 845.6s (4/4) FINISHED
 => [internal] load build definition from Dockerfile.aarch64.ros2_humble   0.0s
 => => transferring dockerfile: 575B                                       0.0s
 => [internal] load .dockerignore                                          0.0s
 => => transferring context: 2B                                            0.0s
 => [internal] load metadata for nvcr.io/nvidia/isaac/ros:aarch64-ros2_hu  3.9s
 => ERROR [1/1] FROM nvcr.io/nvidia/isaac/ros:aarch64-ros2_humble_c8ad2  841.7s
 => => resolve nvcr.io/nvidia/isaac/ros:aarch64-ros2_humble_c8ad2c6ecc687  0.0s
 => => sha256:a8b1b944a2887ae21de58136aac7c36068913c475 23.66kB / 23.66kB  0.0s
 => => sha256:0a1def070f0bd005945e0ead69f08e488bbc0 234.18MB / 234.18MB  165.2s
 => => sha256:f0d41bdab50f2b735b49f10b946cfcf6b6482f5775e 4.25kB / 4.25kB  1.8s
 => => sha256:78723028f99f1d36e23952b4c8134a997ab8c5db464 9.78kB / 9.78kB  0.0s
 => => sha256:f04b4bbe15805316c8fda79beedd3b77e6b1ffcd 27.19MB / 27.19MB  16.3s
 => => sha256:6328a89a71f9e593c89369d44599854fdb241ec009e 4.14kB / 4.14kB  3.1s
 => => sha256:f7adbdc55099abf403d0f5f641e6b4adf565717a5172f44 900B / 900B  4.3s
 => => sha256:4d9a358decc4b98b779e4af5d96a9193a48fb1bd18f3646 205B / 205B  6.0s
 => => sha256:3dfc1c856868daa08ed3e7fc42e65c9901389e20752f57c 210B / 210B  7.6s
 => => sha256:ef8e5ac0e0fe7bbb56f45b5fbddf88c57535ec1859417cf 290B / 290B  8.7s
 => => sha256:acffb039d986ce986cdac87bc14867357361865b03ae6ec 298B / 298B  9.8s
 => => sha256:cb612f8e41f48356a6320d326a3dc34da98ff154 14.49kB / 14.49kB  10.6s
 => => sha256:964b1c4825f38a0e4f31032fe0cec60f5db20fcb 95.97MB / 95.97MB  78.8s
 => => extracting sha256:f04b4bbe15805316c8fda79beedd3b77e6b1ffcd0acf8122  0.5s
 => => sha256:65f859c93f73608bdc5389b1227a4233c44c412b 18.27MB / 18.27MB  26.0s
 => => sha256:a084f32754a1632420a462ca658a72d66366ea11fb 2.19kB / 2.19kB  27.5s
 => => sha256:5ccd4a259fa8c7f3ac08c338527544275cb5ed9e 13.78MB / 13.78MB  40.0s
 => => sha256:67964a03da1d786482fa48f39762dc4d1c712a33 13.69MB / 13.69MB  51.1s
 => => sha256:e93e45fba8a1609d2859caa55afc347b48ce9 639.23MB / 639.23MB  554.0s
 => => sha256:30f86aa4b0e9395b3182a6ad84384e7364de5be 28.60MB / 28.60MB  110.2s
 => => sha256:06e404a62dc0081bd6686c738e216983f1eef093f 4.88MB / 4.88MB  117.3s
 => => sha256:6f0ad9fb03443b090c0300973bb9d16c2c36474 22.13MB / 22.13MB  134.3s
 => => sha256:dc1a845923ddf836408a99594d8c23b6cb493d207 5.52MB / 5.52MB  137.9s
 => => sha256:5a581758e63639f0b54cce331fd7aeb010e2c6ba8 1.00GB / 3.55GB  841.7s
 => => sha256:53784718ebe6f43e11c6a24f152360d7606b748 35.95kB / 35.95kB  166.6s
 => => extracting sha256:0a1def070f0bd005945e0ead69f08e488bbc02a6c8911eb5  4.7s
 => => sha256:fe0dcfb81a1d8f824fe19ed339b194cbe348aa2 37.80kB / 37.80kB  168.0s
 => => sha256:bef4be2e0bcaf94c756a524c6bc3fdb7275ff 240.73MB / 240.73MB  364.2s
 => => extracting sha256:f0d41bdab50f2b735b49f10b946cfcf6b6482f5775e08afd  0.0s
 => => extracting sha256:6328a89a71f9e593c89369d44599854fdb241ec009e775ce  0.0s
 => => extracting sha256:f7adbdc55099abf403d0f5f641e6b4adf565717a5172f44e  0.0s
 => => extracting sha256:4d9a358decc4b98b779e4af5d96a9193a48fb1bd18f3646b  0.0s
 => => extracting sha256:3dfc1c856868daa08ed3e7fc42e65c9901389e20752f57c3  0.0s
 => => extracting sha256:ef8e5ac0e0fe7bbb56f45b5fbddf88c57535ec1859417cf3  0.0s
 => => extracting sha256:acffb039d986ce986cdac87bc14867357361865b03ae6ec4  0.0s
 => => extracting sha256:cb612f8e41f48356a6320d326a3dc34da98ff1547949e7ce  0.0s
 => => extracting sha256:964b1c4825f38a0e4f31032fe0cec60f5db20fcb287a4db6  1.6s
 => => extracting sha256:65f859c93f73608bdc5389b1227a4233c44c412b5cf1e949  0.5s
 => => extracting sha256:a084f32754a1632420a462ca658a72d66366ea11fba39d4d  0.0s
 => => extracting sha256:5ccd4a259fa8c7f3ac08c338527544275cb5ed9e37f1be4f  0.3s
 => => extracting sha256:67964a03da1d786482fa48f39762dc4d1c712a33df82bdf8  0.2s
 => => sha256:9708e8630251c05083d1d78be2683b1861bfb33 23.36MB / 23.36MB  396.1s
 => => sha256:9682d7c8965dce3939a4e91892a7f1f4bd14a03 545.26MB / 1.18GB  841.7s
 => => sha256:ee2b30cf1b123cfd622f46043bd99d306b32a5a1a 2.15MB / 2.15MB  558.8s
 => => extracting sha256:e93e45fba8a1609d2859caa55afc347b48ce904ca855cb5  12.0s
 => => sha256:74f2dfaefb5dc2bfbe6a890cbbe0e98bd0eae6847 2.71MB / 2.71MB  567.9s
 => => extracting sha256:30f86aa4b0e9395b3182a6ad84384e7364de5be8ee86551e  0.5s
 => => extracting sha256:06e404a62dc0081bd6686c738e216983f1eef093f8282e55  0.1s
 => => extracting sha256:6f0ad9fb03443b090c0300973bb9d16c2c36474c00450f70  0.4s
 => => extracting sha256:dc1a845923ddf836408a99594d8c23b6cb493d207b195bdb  0.1s
 => => sha256:48b3ef0fc20045bc39cd07595a2bd474d58da2b 70.55MB / 70.55MB  622.7s
 => => sha256:5ba30f47ca60c6c648372a499ab3a73f67665 138.95MB / 138.95MB  754.0s
 => => sha256:2ce3cfcaa47604fe573571d943d60c7e98a49a102493d 0B / 2.99MB  841.7s
------
 > [1/1] FROM nvcr.io/nvidia/isaac/ros:aarch64-ros2_humble_c8ad2c6ecc68747eca2f1df62e25ae5e@sha256:78723028f99f1d36e23952b4c8134a997ab8c5db464a43984138c7d120aa5896:
------
failed to copy: httpReadSeeker: failed open: failed to authorize: rpc error: code = Unknown desc = failed to fetch anonymous token: unexpected status: 401 Unauthorized
Failed to build base image: isaac_ros_dev-aarch64, aborting.
~/workspaces/isaac_ros-dev/src/isaac_ros_common
nrover@nrover:~/workspaces/isaac_ros-dev/src/isaac_ros_common$ cd ${ISAAC_ROS_WS}/src/isaac_ros_common &&   ./scripts/run_dev.sh ${ISAAC_ROS_WS}
Error: Failed to call git rev-parse --git-dir: exit status 128
Building aarch64.ros2_humble.user base as image: isaac_ros_dev-aarch64 using key aarch64.ros2_humble.user
Using base image name not specified, using ''
Using docker context dir not specified, using Dockerfile directory
Resolved the following Dockerfiles for target image: aarch64.ros2_humble.user
/home/nrover/workspaces/isaac_ros-dev/src/isaac_ros_common/scripts/../docker/Dockerfile.user
/home/nrover/workspaces/isaac_ros-dev/src/isaac_ros_common/scripts/../docker/Dockerfile.aarch64.ros2_humble
Building /home/nrover/workspaces/isaac_ros-dev/src/isaac_ros_common/scripts/../docker/Dockerfile.aarch64.ros2_humble as image: aarch64-ros2_humble-image with base:
[+] Building 0.6s (3/3) FINISHED
 => [internal] load build definition from Dockerfile.aarch64.ros2_humble   0.0s
 => => transferring dockerfile: 58B                                        0.0s
 => [internal] load .dockerignore                                          0.0s
 => => transferring context: 2B                                            0.0s
 => ERROR [internal] load metadata for nvcr.io/nvidia/isaac/ros:aarch64-r  0.5s
------
 > [internal] load metadata for nvcr.io/nvidia/isaac/ros:aarch64-ros2_humble_c8ad2c6ecc68747eca2f1df62e25ae5e:
------
failed to solve with frontend dockerfile.v0: failed to create LLB definition: failed to authorize: rpc error: code = Unknown desc = failed to fetch anonymous token: unexpected status: 401 Unauthorized
Failed to build base image: isaac_ros_dev-aarch64, aborting.
~/workspaces/isaac_ros-dev/src/isaac_ros_common

second try...
different error.
=> sha256:5a581758e63639f0b54cce331fd7aeb010e2c6ba88bfc7c25e322f91bb36ec8f 652.21MB / 3.55GB                             864.3s
 => => extracting sha256:0a1def070f0bd005945e0ead69f08e488bbc02a6c8911eb5532a27a020aef1e4                                      4.7s
 => => sha256:53784718ebe6f43e11c6a24f152360d7606b748f0fd337108cd25662515ac807 35.95kB / 35.95kB                             204.5s
 => => sha256:fe0dcfb81a1d8f824fe19ed339b194cbe348aa202467bed6ea2cd051a2e745f3 37.80kB / 37.80kB                             205.9s
 => => sha256:bef4be2e0bcaf94c756a524c6bc3fdb7275ff5bc56484bc8435e3be5a9372599 240.73MB / 240.73MB                           426.0s
 => => extracting sha256:f0d41bdab50f2b735b49f10b946cfcf6b6482f5775e08afdc138b1cc27a1ce91                                      0.0s
 => => extracting sha256:6328a89a71f9e593c89369d44599854fdb241ec009e775cec3b3cdb7108af8a0                                      0.0s
 => => extracting sha256:f7adbdc55099abf403d0f5f641e6b4adf565717a5172f44ebe69bd27c987cb71                                      0.0s
 => => extracting sha256:4d9a358decc4b98b779e4af5d96a9193a48fb1bd18f3646b4a436cea1d0b0bda                                      0.0s
 => => extracting sha256:3dfc1c856868daa08ed3e7fc42e65c9901389e20752f57c3089524341c36e24a                                      0.0s
 => => extracting sha256:ef8e5ac0e0fe7bbb56f45b5fbddf88c57535ec1859417cf382c63908be240fd1                                      0.0s
 => => extracting sha256:acffb039d986ce986cdac87bc14867357361865b03ae6ec4a88d0b8995d43efa                                      0.0s
 => => extracting sha256:cb612f8e41f48356a6320d326a3dc34da98ff1547949e7ce031ae24679b8a8b6                                      0.0s
 => => extracting sha256:964b1c4825f38a0e4f31032fe0cec60f5db20fcb287a4db670108b4e46cf3dcf                                      1.6s
 => => extracting sha256:65f859c93f73608bdc5389b1227a4233c44c412b5cf1e94936f182904b974d4f                                      0.5s
 => => extracting sha256:a084f32754a1632420a462ca658a72d66366ea11fba39d4d8fac49c28854ad0c                                      0.0s
 => => extracting sha256:5ccd4a259fa8c7f3ac08c338527544275cb5ed9e37f1be4fcc274e3e03de990c                                      0.4s
 => => extracting sha256:67964a03da1d786482fa48f39762dc4d1c712a33df82bdf8734160af5177ad60                                      0.2s
 => => sha256:9708e8630251c05083d1d78be2683b1861bfb338748c7fbe43cb254836eae65b 23.36MB / 23.36MB                             453.1s
 => => sha256:9682d7c8965dce3939a4e91892a7f1f4bd14a03382b94bd26886e60eee093f53 423.62MB / 1.18GB                             864.3s
 => => sha256:ee2b30cf1b123cfd622f46043bd99d306b32a5a1a5ef75a15b3d962ad80f30bd 0B / 2.15MB                                   864.3s
 => => extracting sha256:e93e45fba8a1609d2859caa55afc347b48ce904ca855cb5817b3d92141d20b79                                     12.5s
 => => extracting sha256:30f86aa4b0e9395b3182a6ad84384e7364de5be8ee86551e7ab5d2997152ef9a                                      0.5s
 => => extracting sha256:06e404a62dc0081bd6686c738e216983f1eef093f8282e553c8e61f0967063ea                                      0.1s
 => => extracting sha256:6f0ad9fb03443b090c0300973bb9d16c2c36474c00450f70092ad684d0000f41                                      0.4s
 => => extracting sha256:dc1a845923ddf836408a99594d8c23b6cb493d207b195bdb5e7c94a290d2dc9d                                      0.1s
------
 > [1/1] FROM nvcr.io/nvidia/isaac/ros:aarch64-ros2_humble_c8ad2c6ecc68747eca2f1df62e25ae5e@sha256:78723028f99f1d36e23952b4c8134a997ab8c5db464a43984138c7d120aa5896:
------
failed to copy: httpReadSeeker: failed open: failed to authorize: rpc error: code = Unknown desc = failed to fetch anonymous token: unexpected status: 401 Unauthorized
Failed to build base image: isaac_ros_dev-aarch64, aborting.

Thanks for posting this. We're looking into it. The issue is "failed to fetch anonymous token: unexpected status: 401 Unauthorized" which means docker registry is requiring us to log in before pulling the images but you should not need to. You can log into NGC and run docker login with your NGC token from setup. As a workaround, you can also build the image locally by deleting the file "Dockerfile.aarch64.ros2_humble" which will then cause the scripts to build from scratch rather than use the prebuilt image (note: this will take a while).

Hi FPSychotic
You can temporarily fix it with assigning DOCKER_BUILDKIT=0
here https://github.com/NVIDIA-ISAAC-ROS/isaac_ros_common/blob/main/scripts/build_base_image.sh#L71
It works for me.

I have a similar issue. Below is part of the output:
`
#!/bin/bash
Repositório principal - ISAAC ROS VISUAL SLAM
https://github.com/NVIDIA-ISAAC-ROS/isaac_ros_visual_slam
Tutorial de referência deste script (Visual SLAM usando uma câmera RealSense com IMU integrada)
https://github.com/NVIDIA-ISAAC-ROS/isaac_ros_visual_slam/blob/main/docs/tutorial-realsense.md
Configuração do ambiente de desenvolvimento Isaac ROS
https://github.com/NVIDIA-ISAAC-ROS/isaac_ros_common/blob/main/docs/dev-env-setup.md
Configuração do Isaac ROS RealSense
https://github.com/NVIDIA-ISAAC-ROS/.github/blob/main/profile/realsense-setup.md
cd ${ISAAC_ROS_WS}
if [ ! -d "src" ]; then
mkdir src
fi
cd /tmp &&
if [ ! -d "librealsense" ]; then
git clone https://github.com/IntelRealSense/librealsense &&
cd librealsense &&
git lfs pull &&
cd ..
fi
cd librealsense &&
./scripts/setup_udev_rules.sh && \
cd ${ISAAC_ROS_WS}/src
if [ ! -d "isaac_ros_common" ]; then
git clone https://github.com/NVIDIA-ISAAC-ROS/isaac_ros_common &&
cd isaac_ros_common &&
git checkout release-dp3.1 &&
git lfs pull &&
cd ..
fi
if [ ! -d "isaac_ros_visual_slam" ]; then
git clone https://github.com/NVIDIA-ISAAC-ROS/isaac_ros_visual_slam &&
cd isaac_ros_visual_slam &&
git checkout release-dp3.1 &&
git lfs pull &&
cd ..
fi
if [ ! -d "isaac_ros_nitros" ]; then
git clone https://github.com/NVIDIA-ISAAC-ROS/isaac_ros_nitros &&
cd isaac_ros_nitros &&
git checkout release-dp3.1 &&
git lfs pull &&
cd ..
fi
if [ ! -d "realsense-ros" ]; then
git clone https://github.com/IntelRealSense/realsense-ros.git -b 4.51.1 &&
cd realsense-ros &&
git lfs pull &&
cd ..
fi
cd ${ISAAC_ROS_WS}/src/isaac_ros_common/scripts &&
touch .isaac_ros_common-config &&
echo CONFIG_IMAGE_KEY=ros2_humble.realsense > .isaac_ros_common-config
cd ${ISAAC_ROS_WS}/src
read -p "Pressione Enter depois de conectar a camera RealSense"
cd ${ISAAC_ROS_WS}/src/isaac_ros_common &&
./scripts/run_dev.sh ${ISAAC_ROS_WS}
....
...
..
.
`
Building aarch64.ros2_humble.realsense.user base as image: isaac_ros_dev-aarch64 using key aarch64.ros2_humble.realsense.user
Using base image name not specified, using ''
Using docker context dir not specified, using Dockerfile directory
WARNING: Plugin "/home/mmazza/.docker/cli-plugins/docker-buildx" is not valid: failed to fetch metadata: fork/exec /home/mmazza/.docker/cli-plugins/docker-buildx: exec format error
Resolved the following Dockerfiles for target image: aarch64.ros2_humble.realsense.user
/home/mmazza/workspaces/isaac_ros-dev/src/isaac_ros_common/scripts/../docker/Dockerfile.user
/home/mmazza/workspaces/isaac_ros-dev/src/isaac_ros_common/scripts/../docker/Dockerfile.realsense
/home/mmazza/workspaces/isaac_ros-dev/src/isaac_ros_common/scripts/../docker/Dockerfile.aarch64.ros2_humble
Building /home/mmazza/workspaces/isaac_ros-dev/src/isaac_ros_common/scripts/../docker/Dockerfile.aarch64.ros2_humble as image: aarch64-ros2_humble-image with base:
failed to fetch metadata: fork/exec /home/mmazza/.docker/cli-plugins/docker-buildx: exec format error
ERROR: BuildKit is enabled but the buildx component is missing or broken.
Install the buildx component to build images with BuildKit:
https://docs.docker.com/go/buildx/
Failed to build base image: isaac_ros_dev-aarch64, aborting.


Add blog to website

Moved from: https://github.com/scalabridge/organization/issues/3#issuecomment-243039666\
@jarrodwb I'm ok with using Jekyll given the ease of setup.

Now that Jekyll is setup all we need is a blog entry. If you have something just let me know and I will get it incorporated into the site.


Display cafe url, not peer id

For the work around showing Contact cafes and own cafes, let's display the cafe url instead of the peer id. Peer id doesn't mean much since it's so long.

With the 0.3.0 release (queuing stuff), I've switched back to p2p cafe
connections in the hope that it'll be more reliable now. So, maybe we can
keep this like it is until we've determined whether or not that's going to
work.
On Wed, Jun 5, 2019 at 8:45 AM Aaron Sutula<EMAIL_ADDRESS>wrote:

For the work around showing Contact cafes and own cafes, let's display the
cafe url instead of the peer id. Peer id doesn't mean much since it's so
long.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/textileio/photos/issues/1125?email_source=notifications&email_token=AACYEKEBGFCT7DAGF7OYHGDPY7NTJA5CNFSM4HT4UD42YY3PNVWWK3TUL52HS4DFUVEXG43VMWVGG33NNVSW45C7NFSM4GXZZBSQ,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AACYEKBAYMU3NBE57T5MYTTPY7NTJANCNFSM4HT4UD4Q
.

Okay, I'll leave this as it is for the time being. Changing it from URL -> peer ID is dead simple so I can change this at the drop of a hat.

Seems like we've decided peer id is the way to go-good to close this issue now?

lots of changes here, closing this specific thing for now. we can open a new one for updates to the current 'bot' look.


[REVIEW] Added else condition, Initial some parameters and modify template related dashboard.html

Fixed  https://github.com/leap-solutions-asia/auto-scaling/issues/12
Solutions

Added else condition to display dashboard if there is no autoscaling.status, parameters will not include the chart.
Initial parameters in dashboard.html before render to template
Modify dashboard.

I think OK. I'll merge it.


feat(takeUntil): no longer subscribes to source if notifier synchrono…

…usly emits
closes #2189
cc @trxcllnt

Given that this is a copy of #2189, which is already reviewed, I'm going to merge it once it's green.


for…of through Map broken if target is "es5"

TypeScript Version:  2.3.2
Code
this.edges = new Map();
...
for (let [key, value] of this.edges) {
    console.log(this.edges);
    if (value.has(nodeId)) {
        value.delete(nodeId);
        if (value.size === 0) {
            this.edges.delete(key);
         }
         console.warn(`Edge from ${key} to ${nodeId} implicitly removed.`);
    }
}

Expected behavior:
If transpilation target is "es5" tsc will generate wrong code where loop doesn't iterate over this.edges because length field in generated object _a doesn't exist.
Actual behavior:
Generated code should loop through array as expected.
I've prepared the repository to easily check the bug: https://github.com/evgenymarkov/forof-bug

use --downlevelIteration.
Normally the compiler would give you an error about that, but errors are suppressed by default in .js files.


Concorde cannot be found

Thank you for having that wonderful tutorial that you posted on https://towardsdatascience.com/. I'm on step four now and have downloaded your code from github. I'm getting this error and I'm not sure how to solve it (error.png). Running linux mint, python3.8.10, in a virtual environment. Any ideas on this one would be appreciated, thx.

Reported via email.

I am unable to reproduce this.


Technicians Type has Skills property mistaken

It's set to String when it should be an Object.

fixed this as well in latest PR


Multiple images not showing u p

Have I missed an image?

Please let me know what I am doing wrong.

Yep, I've had the same issue.
Make a new folder in your www folder named: lg-icons
In that new folder place all of your lg icons. Refresh browser and the icons are shown up.

Hi, @drezin2112 , are you still experiencing this issue? As freggel noted, it's important to keep the www files in the same structure as they appear in this repo. If you still experience the issue, it usually goes away after a cache reset in your browser.


CUDA out of memory

I am using 8 24GB gpus.
I set the LLAVA_PARAMS_PATH as liuhaotian/llava-v1.5-13b and NUM_DEVICES = 8.
I got out of memory error. Could you let me know what I have to change?

Hello, did you encounter KeyError: 'llava' and how did you handle it


--max-views is not working in latest releases.

Please follow the guide below

You will be asked some questions and requested to provide some information, please read them carefully and answer honestly
Put an x into all the boxes [ ] relevant to your issue (like this: [x])
Use the Preview tab to see what your issue will actually look like

Make sure you are using the latest version: run youtube-dl --version and ensure your version is 2018.11.03. If it's not, read this FAQ entry and update. Issues with outdated version will be rejected.

[ ] I've verified and I assure that I'm running youtube-dl 2018.11.03

Before submitting an issue make sure you have:

[ ] At least skimmed through the README, most notably the FAQ and BUGS sections
[ ] Searched the bugtracker for similar issues including closed ones
[ ] Checked that provided video/audio/playlist URLs (if any) are alive and playable in a browser

What is the purpose of your issue?

[ ] Bug report (encountered problems with youtube-dl)
[ ] Site support request (request for adding support for a new site)
[ ] Feature request (request for a new functionality)
[ ] Question
[ ] Other

The following sections concretize particular purposed issues, you can erase any section (the contents between triple ---) not applicable to your issue

If the purpose of this issue is a bug report, site support request or you are not completely sure provide the full verbose output as follows:
Add the -v flag to your command line you run youtube-dl with (youtube-dl -v <your command line>), copy the whole output and insert it here. It should look similar to one below (replace it with your log inserted between triple ```):
[debug] System config: []
[debug] User config: []
[debug] Command-line args: [u'-v', u'http://www.youtube.com/watch?v=BaW_jenozKcj']
[debug] Encodings: locale cp1251, fs mbcs, out cp866, pref cp1251
[debug] youtube-dl version 2018.11.03
[debug] Python version 2.7.11 - Windows-2003Server-5.2.3790-SP2
[debug] exe versions: ffmpeg N-75573-g1d0487f, ffprobe N-75573-g1d0487f, rtmpdump 2.4
[debug] Proxy map: {}
...
<end of log>

If the purpose of this issue is a site support request please provide all kinds of example URLs support for which should be included (replace following example URLs by yours):

Single video: https://www.youtube.com/watch?v=BaW_jenozKc
Single video: https://youtu.be/BaW_jenozKc
Playlist: https://www.youtube.com/playlist?list=PL4lCao7KL_QFVb7Iudeipvc2BCavECqzc

Note that youtube-dl does not support sites dedicated to copyright infringement. In order for site support request to be accepted all provided example URLs should not violate any copyrights.

Description of your issue, suggested solution and other information
Explanation of your issue in arbitrary form goes here. Please make sure the description is worded well enough to be understood. Provide as much context and examples as possible.
If work on your issue requires account credentials please provide them or explain how one can obtain them.

youtube-dl --max-views 9000 https://www.youtube.com/watch?v=hY7m5jjJ9mM
Downloads a cat video with 81 million views!

Same problem with older versions. YouTube must have changed something.
I hope someone can fix this. Thanks for your help.


Fixed abstract classes not working. Fixes #1603

I'm brand new to Python, Django, and Wagtail, so this might not be what you want. But I ran into a problem while trying to learn Wagtail and this fixed it for me.
Although I have a hunch that wagtail.wagtailcore.models.get_page_types() shouldn't be returning my abstract type at all. So maybe that's the proper fix.

Fixed in #1631


Added Keycloak backend plugin support

Added Keycloak backend plugin support

Other than the small change in the README it looks good.  Verified it was working as expected.
Given we have this now doesn't that make the GitHub App optional?


fix: BFloat16 extension and tests

the tests are still returning zero similar to #1695, but at least this tests if the extension loads correctly. Marked them as broken for now.
fixes #1723

:warning: Please install the  to ensure uploads and comments are reliably processed by Codecov.
Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 96.35%. Comparing base (02c5855) to head (48e4f0c).

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
Additional details and impacted files
@@             Coverage Diff             @@
##             main    #1725       +/-   ##
===========================================
+ Coverage   67.39%   96.35%   +28.95%
===========================================
  Files          32        9       -23
  Lines       12772      411    -12361
===========================================
- Hits         8608      396     -8212
+ Misses       4164       15     -4149

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.

I'm getting reports about this causing lots of test and tutorial failures. Is the patch being released?


Request: Holed shapes with multiple hole sizes

Right now the HoledHexagon, HoledRectangle, and HoledSquare shapes are able to accept multiple holes, but all of the holes must be of the same dimension. I would like the ability to define these shapes with various (ideally arbitrary numbers of) hole sizes and to retain the ability to have arbitrary numbers of holes for a given size. This could be very useful for defining things like shield blocks or the assemblies of Sodium Graphite Reactors.
I looked into implementing this, but it seems like it would actually be somewhat difficult. My thought was an input that would look something like this:
blocks:
    block1:
        component1:
            shape: HoledHexagon
            material: SS316
            Tinput: 500
            Thot: 510
            op: 15
            holeOD: [0.1, 0.2, 0.3]
            nHoles: [4, 5, 6]
            mult: 1
        component2:
            shape: DerivedShape
            material: Sodium
            Tinput: 500
            Thot: 510

This would maintain backwards compatibility if the user didn't enter a list for the holeOD and nHoles attributes.
The issue is complicated by the current design of two major pieces (and possibly more):

The parsing of component attributes currently does not support values that are lists
The thermal expansion of components is not set up for an attribute that might be a list

Issue (1) can probably be relatively easily circumvented by modifying the from_yaml within the ComponentDimensions class, if that were an acceptable solution.
But issue (2) seems quite a bit more complicated. In addition to lists not being supported right now from the perspective of expanding the dimensions, there is not currently a syntax in ARMI for linking dimensions that might be in a list. For instance, if we wanted to add a pin into one of the holes:

blocks:
    block1:
        component1:
            shape: HoledHexagon
            material: SS316
            Tinput: 500
            Thot: 510
            op: 15
            holeOD: [0.1, 0.2, 0.3]
            nHoles: [4, 5, 6]
            mult: 1
        component2:
            shape: Circle
            material: Inconel
            Tinput: 500
            Thot: 510
            od: component1.holeOD  # <------ How to specify which hole `od` is linked to?
            mult: 1
        component3:
            shape: DerivedShape
            material: Sodium
            Tinput: 500
            Thot: 510

I tried a couple things, but this is probably too much effort for me right now. If anyone else has any other ideas, I'd be happy to hear them.

I think that generalizing these components to have "n" inputs will be generally challenging as you noted above. One problem as you noted is that the setDimension implementation of Component assumes that a single dimension name/key represents a single value (i.e., a float) and it does not know how to interpret a list of floats:
https://github.com/terrapower/armi/blob/9d1aaa76eadc0eb5c4f50cf8790d4fc2050e6322/armi/reactor/components/component.py#L723-L753
Another issue that you bring up is with component linking based on the name/key of the dimension. In this case we would need to be able to do something like component1.holeOD.0 or something to represent linking to the value in the first index of the list. This would require some type of list expansion treatment at a pretty low level in the Component implementation.
My suggestion is that if you need up to "x" number of holes for your work that we consider a less elegant solution. For example, take "x" to be 3.
 blocks:
    block1:
        component1:
            shape: HoledHexagon
            material: SS316
            Tinput: 500
            Thot: 510
            op: 15
            holeOD: 0.1
            nHoles: 4
            holeOD2: 0.2
            nHoles2: 5
            holeOD3: 0.3
            nHoles3: 6
            mult: 1
        component2:
            shape: Circle
            material: Inconel
            Tinput: 500
            Thot: 510
            od: component1.holeOD
            mult: 1
        component3:
            shape: Circle
            material: Inconel
            Tinput: 500
            Thot: 510
            od: component1.holeOD2
            mult: 1
        component4:
            shape: DerivedShape
            material: Sodium
            Tinput: 500
            Thot: 510

This is not ideal because it doesn't offer a dynamic solution, but at a minimum it can extend the support of this complex block definition for your work while maintaining backwards compatibility. My guess is that many designs won't exceed 3 or 4 different hole types in practice, so this could at least be a stop gap until a generalized implementation is suggested.
Let's see what @john-science / @ntouran think about this.

Also, FYI, I can deal without this capability. I want it and I think it would be generally useful, but I don't need anyone to go out of their way to make it happen. This probably should have been a 'discussion' rather than an 'issue', but I only thought of that after I put it here.

I am not against this idea, but it would be hard to validate the user's input data.
For instance, can six holes of radius 0.85 fit inside a hexagon with maximum radius 1?  How about can 32 holes of radius 0.1?
This is known as the "knapsack problem" and relates to the "big packing problem".  It is an NP hard computational problem, and would be very slow to solve, generally.

Hmm, the input validation is a good point that I didn't think about at all.
There are definitely some things that we could check against to provide confidence, but you're right that providing certifiable checks against arbitrarily complex combinations of holes would be not feasible within this context.

Without a clear action to complete this issue ee might want to close this and move to a discussion that focuses on the desired geometry complexity that the ARMI framework should allow and accept. I think that it's clear right now that the arbitrariness of "n" holes with independent sizes is not possible now.
I think that it's pretty easy to check if the area of the hexagon minus the holes is greater than 0, but that says nothing about if their arrangement is valid. Also, allowing linked parameters with this type of model is not supported right now and probably shouldn't be supported given that it will expand the complexity blueprints and component dimension management significantly.
If anyone wants to implement a 2-holed, 3-holed, or explicit "x"-integer design in the future then refer to my example above.


Can't get the full volume using actual thickness.

Hi NeSVoR team,
Thank you so much for making the code public! I tried to reproduce your results using the CRL atlas dataset. But found that I need to enter a larger parameter than the actual thickness to get the full volume.
I used the following code to get to the thickness of the data as [0.8,0.8,0.8].
img = nib.load(nii_file)   #turn into numpy  data = img.get_fdata()   affine = img.affine  resolution = affine.diagonal()[:3]
I used the following command for SVR：
nesvor reconstruct \ --input-stacks .../STA33.nii.gz .../STA33.nii.gz .../STA33.nii.gz \ --thicknesses 0.8 0.8 0.8 \     --output-volume .../3316.nii.gz \ --bias-field-correction \ --output-resolution 0.8
However, I got an incomplete volume：

If I change the command to
--thicknesses 0.8 0.8 0.8
I can then get the full volume:

I have noticed that the results I get are similar to those in 'Cannot reproduce results on FeTA using your slicing strategy' (a closed issue). Could you clarify what are the limitations of the thickness parameter?

Sorry, there is a mistake in my first description. The second image corresponds to the command
--thicknesses 1.4 1.4 1.4


Make Linux UI logging behave like other platforms

This should cause UI logs to be uploaded on Linux (!).

Not sure how to test this end-to-end except cutting a new Linux release and then using that, but I've verified that opening the app dumps logs to the file.

Discussed a bit with @chrisnojima but we should probably discuss on Monday when @oconnor663 gets back.

@akalin-keybase should we do a hangout sometime today?

Chatted with @oconnor663, we decided that I'd try removing the stdout logging and make logFileName return a non-empty path.

Okay, this should be ready again for review @oconnor663 @jzila and @keybase/react-hackers

(Just tested on my machine: https://keybase.io/_/admin/logdump_viewer?603618386#67cf6afe93c10925c190321c )

bump (from @keybase/react-hackers)


Winter.Builder doesn't work with this skin

Excuse me, the builder plugin cannot be used for this skin

yep.

may be not the correct way, but we can skip skin on builder page
 public function boot()     {         // Only apply skin modifications to the backend context         if ($this->app->runningInBackend() &&  !\Str::contains($_SERVER['REQUEST_URI'], "winter/builder")) {             $this->applyBackendSkin();             $this->extendBackendControllers();             $this->extendBackendWidgets();             $this->extendBrandSettingsForm();             $this->extendBackendAuthController();         }     }

@algofran can you spend a few hours looking into what's causing the Winter.Builder plugin to not play nicely with this plugin?

@algofran can you spend a few hours looking into what's causing the Winter.Builder plugin to not play nicely with this plugin?

I'll try 👌


nixos/chrony: Let Chrony control/track RTC drift

Description of changes
Previously, chrony practically ignored the RTC and keeping the RTC on time was done on shutdown.
There are three different ways for chrony to handle the RTC:

rtcsync: Copy system clock to RTC every 11 Minutes, without tracking the RTC drift.
rtcfile: Track the drift of the RTC relative to the synchronized system time. This writes the drift and offset to file on shutdown of chrony (or manual writertc in chronyc), but does not update the RTC.
rtcfile + rtcautotrim: If rtcautotrim is enabled and the error exceeds the specified maximum error, chrony updates the RTC. It can also be done manually with trimrtc in chronyc.

The latter configuration is pretty much guaranteed to be the best for both long-running servers and intermittently running devices.
See also what the ArchWiki Page for chrony has to say to this.
Since chrony is now in charge of updating the RTC, it is disabled when running chrony and having the new enableRTCTrimming option enabled.
I wanted to call it rtcSync, but decided against it as rtcsync does the naive handling of the RTC, which is less useful.
Since it is the most sane default when running chrony, I enabled it by default.
Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[x] Tested basic functionality of all binary files (usually in ./result/bin/)
23.11 Release Notes (or backporting 23.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[x] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[ ] Fits CONTRIBUTING.md.

Hey @thoughtpolice, mind looking over this again?

Result of nixpkgs-review pr 259405 run on x86_64-linux 1

2 packages blacklisted:

nixos-install-tools
tests.nixos-functions.nixos-test

Hey @thoughtpolice, is it possible you look over this and merge it?
This has been working fine for me for months on dozens of systems.
If the system doesn't have an RTC or it can't be controlled, there'll be an error message in the log but chrony continues to function as normal.

@thoughtpolice Thank you so much for your time, review and merge!

@vifino error start service:
systemd[1]: Started chrony NTP daemon.
chronyd[16748]: chronyd version 4.4 starting (+CMDMON +NTP +REFCLOCK +RTC +PRIVDROP +SCFILTER +SIGND +ASYNCDNS +NTS +SECHASH +IPV6 -DEBUG)
chronyd[16748]: Fatal error : rtcfile directive cannot be used with rtcsync
chronyd[16748]: Fatal error : rtcfile directive cannot be used with rtcsync
systemd[1]: chronyd.service: Main process exited, code=exited, status=1/FAILURE
systemd[1]: chronyd.service: Failed with result 'exit-code'.

Fixed. Remove rtcsync from extraConfig.

@Izorkin Thank you for telling me - I accidentally dropped the assertion that is supposed to tell you before it fails during rebasing this change.
Please check out #268335 and leave a review if you can.


Add support for Laravel Vapor

Currently the package doesn't seem to be compatible with Laravel Vapor out of the box. I've added a temporary route to solve it for personal use but would be nice if a more robust implementation could be bundled into the package.
Route::get('/docs', function () {
	$contents = file_get_contents(asset('docs/index.html'));
	$contents = str_replace(env('APP_URL') .'/', asset('/'), $contents);

	$contents = str_replace('href="css', 'href="'. asset('/') .'docs/css', $contents);
	$contents = str_replace('src="js', 'src="'. asset('/') .'docs/js', $contents);
	$contents = str_replace('src="images', 'src="'. asset('/') .'docs/images', $contents);

	return $contents;
});

Let me know if I can help further in this 👍🏻

I created a Console command that essentially does the same.
The only difference, is that I can run it automatically when deploying to Vapor.

Can you share it here?
On Tue, 31 Mar 2020 at 3:34 pm, Benjamin Gonzalez<EMAIL_ADDRESS>wrote:

I created a Console command that essentially does the same.
The only difference, is that I can run it automatically when deploying to
Vapor.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/mpociot/laravel-apidoc-generator/issues/716#issuecomment-606630866,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAYW3XNPYGPJ6QBUQ2BSTBDRKHWPJANCNFSM4LUFSXTA
.

I don't use images in my documentation, but you can easily implement something similar to fix images :)
namespace App\Console\Commands;

use Illuminate\Console\Command;

class EditBladeDocumentationCommand extends Command
{
    /**
     * The name and signature of the console command.
     *
     * @var string
     */
    protected $signature = 'apidoc:fix';

    /**
     * The console command description.
     *
     * @var string
     */
    protected $description = 'Fixes the API documentation to use Laravel asset method ';

    /**
     * Create a new command instance.
     *
     * @return void
     */
    public function __construct()
    {
        parent::__construct();
    }

    /**
     * Execute the console command.
     *
     * @return mixed
     */
    public function handle()
    {
        $path = resource_path('views/apidoc/index.blade.php');

        if ( strpos(file_get_contents($path), '{{ asset(') == 0) {
            $this->fixFile($path, "/docs/css/style.css");
            $this->fixFile($path, "/docs/js/all.js");
        } else {
            $this->info('No fix was necessary');
        }

        $this->call('view:clear');
    }

    /**
     * @param string $path
     * @param string $toBeFixed
     * @param string $fix
     */
    private function fixFile(string $path, string $toBeFixed): void
    {
        $fileContent = file_get_contents($path);
        $updatedVersion = str_replace($toBeFixed, "{{ asset('$toBeFixed') }}", $fileContent);
        file_put_contents($path, $updatedVersion);
        $this->info("File $path fixed.");
    }
}

Thanks will explore this option as well.

@BenjaminRosell are you generating a postman collection.json for your docs? It appears that the collection.json isn't deploying to S3 for me 😕

Hmmm. You are right ! I dont see it beign deployed either. Will see what I can do tonight.
Cheers !

Wonder if @shalvah has already looked into this.

@BenjaminRosell Just installed the package today and got it working locally, can't seem to get it working in Vapor either.

Hey @cwilby !
What do you mean by not beign able to make it work on Vapor ? Are you talking about the Postman Route ?
THanks :)

👋
So currently my solution is to build the static html and serve the output elsewhere.  I'd like to use the laravel type instead, not sure how to do that yet.

So @devonmather, I think I have a pretty good idea on why this is not working. If you look at the \MPociot\ApidDoc\Http\Controller.php we see:
    public function json()
    {
        return response()->json(
            json_decode(Storage::disk('local')->get('apidoc/collection.json'))
        );
    }

Since you are using the localstorage, and Vapor is a non-writable storage, you cant really use the local environment unless you commit that file to your repo... or something hacky...
Maybe a better solution would be to use an S3 bucket (since you are already on aws, i dont think that would be a problem). We could very easily use a .ENV variable to fix this problem. I'll do a Pull request latter this week to propose @shalvah with a fix.

So currently my solution is to build the static html and serve the output elsewhere. I'd like to use the laravel type instead, not sure how to do that yet.

I think you can use laravel, and then the command I posted a bit earlier as a pre-deploy hook on your vapor.yamlfile

@BenjaminRosell I'm actually using the static generation. So the collection.json is compiled in the public directory. The issue arises because Vapor doesn't upload json files to S3 according to their support. But I wasn't able to actually figure out why a .json file in public directory is stripped from upload to S3, or how to reference it as they have described.

I think we are saying the same thing... but the problem is that the /storage folder is not synced to Vapor, because they are environment specific... Which means that on vapor, this file simply does not exist... Look at the build that is actually uploaded to lambda. It does not include anything although they are present locally...

Two solutions... Add the file elsewhere to the repo and create a symlink, or simply use an S3 instance...
In my case I will choose the second.

@BenjaminRosell I'm curious to see if it works for you. We aren't actually talking about the same approach as far as I can tell.
I'm using 'type' => 'static' in doing so the collection.json isn't placed in the storage folder. It's place in the public folder.

Now every file from that directory is uploaded to S3. Except the collection.json

Let me know if you have more luck in the 'type' => 'laravel' approach, I briefly tried that too without luck.

I see !
Is it the actual file or a symlink ?

I found how it handles the creation of the Documentation. Still wondering why it doesn't work if the file is in the lambda function... What do you see in the logs ?

I think refactoring to add a config option for the storage disk to be used could be a good direction, so Storage::disk('local') becomes Storage::disk('apidoc.storage_disk'); or similar.
With that, dependents can configure their own storage disk/access and fallback to local storage.

@BenjaminRosell did you mean EditBladeDocumentationCommand?

Alright guys, I just submitted a pull request to fix our issues.
https://github.com/mpociot/laravel-apidoc-generator/pull/729


Add support for watchos target

Kotlin Docs suggests that the library provide support for watchos
This also includes androidNative if possible
The current versions of watchos in the Maven repository are between 0.1.2 and 0.1.4, and the latest release is missing

@zhangzih4n It will available in upcoming version

@zhangzih4n watchos targets added in version 0.2.0


fix bad handling of nrm_vector_t (storing objects instead of pointers)

A small number of places in the code are storing full objects inside a nrm_vector_t instead of just storing pointers de the objects.
This need to be fixed in the general case. Be careful though that the internal msg API probably still need to do that, deep copies when sending messages avoid lifetime issues between the daemon and the messaging layer.

Please provide an example of a place where full objects are stored inside an nrm_vector_t as I was not successful in finding one.

Therefore I can confirm that there isn't any occurrence where full objects are stored in an nrm_vector_t.


Compilation error in Umbraco 7.5.14

ezSearch is failing in 7.5.14 with an error in the eventlog:
The type or namespace name 'Helpers' does not exist in the namespace 'Microsoft.Web' (are you missing an assembly reference?)
I can't see anywhere in the source that there might be a reference to Microsoft.Web.Helpers anywhere?

We have sites running on 7.5.14 with ezSearch and don't see issue; have seen it before related to reCaptcha used by some packages?


cdc: observe region changed events

What problem does this PR solve?
Problem Summary: The merge source region may be destroyed when commit merge. For now, CDC observer have not observed this event and the connection to source region would be hang up.
What is changed and how it works?
What's Changed: Observe region change events
Related changes

Need to cherry-pick to the release branch

Check List
Tests

Unit test
Integration test

Release note
N/A

/merge

@5kbpers Please fix lint 😂

/merge

/merge


Fix JDBC3ResultSet.getBinaryStream()

Bugfix for this issue: https://bitbucket.org/xerial/sqlite-jdbc/issues/163/null-pointer-exception-on-null-input

Good catch. Thanks!


Content Publishing - Components  (02 Link List)

User Story

As an IBM.com Library components adopter,

I need a way to learn more about the components

so that I can utilize the components to my day to day work.

Additional information

Take a look at the storybook - so you know how the component works.   You will also use Storybook as a reference to accurately include the images in the Sketch file.

Download this Sketch template to your machine to make the updates. Name the Sketch file with the following convention: Name of the component + version. ex: Link list v1.0.sketch

Use the component description included in the Components Overview Box Note - for the 'Intro' section of the newly downloaded Sketch file

For the image creation, please use the components from the Design Kit for image creation, if the component can not be found in the Design Kit, navigate to the visual spec file within this Component Box folder sometimes it might be under the Pattern Box folder. The image that works successfully for most patterns is the 1312px image. Adjustments may be needed to have this image accurately reflect the Storybook designs.

Export the individual images with a 2X setting, saving them into the Components sub-folder that contains the Sketch file.  These exported images will be used when creating the Markdown for publishing. Please use the lowercase with a dash in between for image naming. For example, lightbox-media-viewer.jpg.

Once complete, save the revised Sketch file in the Components folder / sub-folder here.

Use this Sketch file to create the Markdown version of the web page in Github.

Find the .mdx file for the component assigned
Copy the content from the Sketch file into the .mdx file
Once complete, create the Pull Request and review, using the Preview link, to be sure it matches the Sketch file design
When ready to deploy, include Jenny as a PR Reviewer and Approver.
Jenny will review and merge the PR

Acceptance criteria

[ ] Content crafting is done.
[ ] Asset image creation is done.
[ ] Page design is done.
[ ] Publishing with markdowns is done.
[ ] QA'd by Jenny
[ ] Web page preview is approved by Linda, Jeff and Wonil
[ ] Web page is published

@sethibm
Here is the content for each Link list variations:
Default
Default Link list displays links in a card format. Typically used for resource links on the side of the main content of the page.
Horizontal
Horizontal Link List displays links horizontally, icons can be placed on the left or right of text. Typically used within the main content of the page.
Vertical
Vertical Link List displays links as a vertical list, icons can be placed on the left or right of text.
Vertical with cards
Vertical with cards Link List combines the Vertical and Default Link lists. Typically used for varying resource links on the side of the main content of the page.
End of section
End of section Link List typically used at the end of a section of content to list a number of CTAs for the user.

Content has been added to Markdown. PR can be viewed here: https://github.com/carbon-design-system/ibm-dotcom-library-website/pull/604
Seth is updating the images before we merge branch.


Allow other directories to be discovered as well.

$kernel
    ->discoverPackage($path, $namespace)
    ->…
;

Also make this available via AppConfig

A good idea is to have this interface:
namespace Tempest;

interface Package
{
    public function getPath(): string;

    public function getNamespace(): string;
}

…

$kernel->registerPackage($package);


How can I add my new posts to a sub folder?

Hi,
Thanks for make a such cool theme! I like it very much.
But now I have one question, I want to add a new post to a folder because I don't want to mix these 'meta pages' with my own blog posts.
How can I make it? I try add a folder and add page under it but seems it can't be accessed.

We can't speak to the specifics of your particular site. If you contact GitHub support (or post to the GitHub Community forum) they should be able to help you get things straightened out. 😸


refactor(meshes): set-up data transformations

Set-up data transformations for the meshes module.
Signed-off-by: Philipp Rudloff<EMAIL_ADDRESS>

Good to go!

FYI, I just pushed a small change that adds a config property to Mesh because I realized https://github.com/kumahq/kuma-gui/pull/1913 was happening and so I fixed it here as well.

Ah yes I just saw that and wondered where else we need to keep an eye out for that! Thanks!

(just looked again in case, still good to go!)
(we should make an e2e test for these things to check that they don't contain one of our augmented properties)


Since 5.0.0, breaks page with isBuffer is not a function.

Version
5.0.0
Browser and OS info
Version 73.0.3683.86 (Official Build) (64-bit)
Steps to reproduce
Navigating my product's webpage (locally and in production) with vue tools, I get the following error:
 VM259:1 Uncaught TypeError: t.isBuffer is not a function
    at y (<anonymous>:1:2232)
    at f (<anonymous>:1:3275)
    at Object.<anonymous> (<anonymous>:1:928)
    at Object.r (<anonymous>:1:375)
    at Object.emit (<anonymous>:1:694)
    at t (vuex.min.js:6)
    at vuex.min.js:6
    at Array.forEach (<anonymous>)
    at new V (vuex.min.js:6)
    at Object.<anonymous> (app-74311e04b1.min.js:39)

Which points to the (minified) code:
if (g && t.isBuffer(e))
What is expected?
This shouldn't cause the web page I'm browsing to stop working.
What is actually happening?
Web page I'm using with vue-devtools enabled in the browser stops working entirely.  If I disable the extension, the page/site loads just fine.

Duplicate of #874


Q: -K value

Is the very large value of -K 100000000 (100 mill) used for a specific reason?  Initially this was to prevent variability when specifying different numbers of threads.
The parabricks comparison command indicates10000000 (10 mill).
Would a 10 million value work without any detriment to run time?

The K option is used just to compare the SAM output result.
I remember there were no significant differences in performance with regard to the K value (you can just remove the K option).
If you are running BWA-MEME with more than 36 physical cores ( 72 vCPU), we recommend using mimalloc for performance.

Using mimalloc has no improvement in performance with cores less than 36, while it requires much more runtime memory.
In case of many cores, malloc in glibc affects the multithreaded performance.
Instead of changing overall implementation, we decided to use LD_PRELOAD=/usr/bin/libmimalloc.so  bwa-meme <options>.
Thanks for the update, I was also wondering why the new bwa-meme version was not available.

I understand the use of LD_PRELOAD, used it with gperftools tcmalloc_minimal on the legacy bwa for ~8% speedup on modest threads (>12 IIRC).
I was more meaning install the library as part in the conda package so that it could be easily available, also very beneficial for containerised builds based on conda.

Thats a good suggestion, I will include it in the  package!


Ability to dynamically send time parameters in the request ,for creating meeting, startTIme endtime etc which are the details in the examples

Is your feature request related to a problem? Please describe.
The API, that I am working on requires me to get the meetingId of a meeting that has started and not expired at the same time.
It should be an ongoing meeting. Hence having predefined meeting details already in the database doesn't work as it gets expired after some time
Describe the solution you'd like
Being able to dynamically create a meeting by calling the respective spec file and sending parameters as request body, to the meeting contract test. As a result, create the meeting with the desired start and end time.
Additional context

If the meeting is not started the API throws an error as "Meeting not started yet"

If the meeting has ended the API throws an error as "Meeting has been expired"

Moving this feature request to specmatic-node project as it fits the helper library


I cannot open build tasks by ctrl+shift+b because of this extension

Type: Bug
turn on this extension and use hotkeys to bring up the task menu, it will stuck at the 'Fetching Tasks' phase.
Extension version: 0.21.1
VS Code version: Code 1.76.0 (Universal) (92da9481c0904c6adfe372c12da3b7748d74bdcb, 2023-03-01T10:23:45.993Z)
OS version: Darwin x64 21.6.0
Modes:
Sandboxed: Yes

System Info

Item
Value

CPUs
Intel(R) Core(TM) i7-3720QM CPU @ 2.60GHz (8 x 2600)

GPU Status
2d_canvas: enabledcanvas_oop_rasterization: disabled_offdirect_rendering_display_compositor: disabled_off_okgpu_compositing: enabledmetal: disabled_offmultiple_raster_threads: enabled_onopengl: enabled_onrasterization: enabledraw_draw: disabled_off_okskia_renderer: enabled_onvideo_decode: enabledvideo_encode: enabledvulkan: disabled_offwebgl: enabledwebgl2: enabledwebgpu: disabled_off

Load (avg)
6, 6, 5

Memory (System)
16.00GB (2.63GB free)

Process Argv
--crash-reporter-id d2743afe-0b94-4c78-b00e-97554cafa983

Screen Reader
no

VM
0%

A/B Experiments
vsliv368:30146709
vsreu685:30147344
python383:30185418
vspor879:30202332
vspor708:30202333
vspor363:30204092
vslsvsres303:30308271
pythonvspyl392:30443607
vserr242cf:30382550
pythontb:30283811
vsjup518:30340749
pythonptprofiler:30281270
vsdfh931cf:30280410
vshan820:30294714
vstes263:30335439
vscoreces:30445986
pythondataviewer:30285071
vscod805cf:30301675
binariesv615:30325510
bridge0708:30335490
bridge0723:30353136
cmake_vspar411:30581797
vsaa593cf:30376535
pythonvs932:30410667
cppdebug:30492333
vsclangdc:30486549
c4g48928:30535728
dsvsc012cf:30540253
pynewvextcfv2:30669238
azure-dev_surveyone:30548225
vscccc:30610679
pyindex848:30662994
nodejswelcome1cf:30587006
282f8724:30602487
pyind779:30671433
89544117:30613380
pythonsymbol12:30671437
vsctsb:30662444
pythonb192:30669360

We just merged a potential fix for this issue yesterday. Could you try this vsix
vscode-java-test-0.38.2023030203.vsix.zip
And let us know if the problem get resolved?

We merged a potential fix for this issue yesterday. Could you try install
vscode-java-dependency-0.21.2023030301.vsix.zip
And let us know if the problem get resolved?

@jdneo sorry it's not working after installing the fix. Is this a new issue? I didn't have any issues several days ago. I just realized my old pc cannot open the tasks menu too with this extension.

It's not stuck but extremely slow on my old pc. It's downloading the necessary Gradle dependencies. After it's done the menu shows up.
So I wonder if it should not make the users wait because we don't always work with Java projects. There are a lot of tasks too.
On my new pc, the menu won't show up anymore. Because there's no JDK installed.

Ok, so it turns out that waiting for the LS being ready is not ideal.
We should just catch the error when we sending the requests to LS but LS is not ready.
@CsCherrYY is working on it now.

Hi @rockingdice
It would be great if you could try this bit with the new fix, and let us know if the problem is fixed.
vscode-java-dependency-0.21.2023030900.vsix.zip
Thank you!


Expose HFHexStringFromData & HFDataFromHexString

The functions HFHexStringFromData & HFDataFromHexString are currently private, but I think they're highly useful functions and would love to have them available in the framework.
[edit] What I'm really wanting to do is get the selected characters from the view (either the hex or the ascii, depending on which has focus). There doesn't appear to be any easy way to do this currently.

What I'm really wanting to do is get the selected characters from the view

Which view?

The HFTextView. There are functions to get the selected bytes, but I want to get the actual hex or ascii characters that the user has selected. I.e. the same characters you would get if you hit copy.

yeah that function should work for hex. For ascii you can just use NSString initWithBytes directly.


Atom.Object.defineProperty.get is deprecated.

atom.workspaceView is no longer available.
In most cases you will not need the view. See the Workspace docs for
alternatives: https://atom.io/docs/api/latest/Workspace.
If you do need the view, please use atom.views.getView(atom.workspace),
which returns an HTMLElement.
Atom.Object.defineProperty.get (/Applications/Atom.app/Contents/Resources/app/src/atom.js:54:11)
Object.activate (/Users/ahmet/.atom/packages/rspec/lib/rspec.coffee:21:9)

Should be fine now, thanks for reporting.

:+1:


[WIP]Update module

validate against rubocop
update travis matrix
bump versions
fix puppet lint complaints

I cherrypicked around, this commit seems to introduce the current error, master is broken :(
@derdanne could you take a look please?

Hi, tested the module on an Archlinux with a v3 server profile, works fine.

@bastelfreak
Thanks for your hard work on this module. I will have time to take a deeper look at it in the next week.

thanks. So in general I'm fine with this and ready for merge. Just to things:

I've no clue why the one test fails, but that error is also present in master
the tests should be refactored, but in a separate PR

:+1: for merge and refactor later, also we can fix the issue later since it's not a regression

Also your tests revealed, when $server_nfsv4_servicehelper is undef we can't do a "delete($client_nfsv4_services, $server_nfsv4_servicehelper)". Could you please add a test of $server_nfsv4_servicehelper in init.pp on line 237:
if $server_nfsv4_servicehelper != undef {
  $effective_nfsv4_client_services = delete($client_nfsv4_services, $server_nfsv4_servicehelper)
} else {
  $effective_nfsv4_client_services = $client_nfsv4_services
}

I left some comments, could you please check them and update your PR. I think testing then should be work.
Thanks!

About the spec tests, I tried this:
  if $nfs_v4_root_export_tag != undef  {
    validate_string($nfs_v4_root_export_tag)
  }

  if $server_nfsv4_servicehelper != undef {
    $effective_nfsv4_client_services = delete($client_nfsv4_services, $server_nfsv4_servicehelper)
  } else {
    $effective_nfsv4_client_services = $client_nfsv4_services
  }

  if $server_enabled {
    $effective_client_packages       = difference($client_packages, $server_packages)
    $effective_nfsv4_client_services = delete($client_nfsv4_services, $server_nfsv4_servicehelper)
    $effective_client_services       = $client_services
  } else {
    $effective_client_packages       = $client_packages
    $effective_nfsv4_client_services = $client_nfsv4_services
    $effective_client_services       = $client_services
  }

Is this the code you imagined? It creates a lot of new errors if I try that on my local system.

Sorry, that was a litllebit unclear, i thought of:
if $server_enabled {
$effective_client_packages       = difference($client_packages, $server_packages)
if $server_nfsv4_servicehelper != undef {
$effective_nfsv4_client_services = delete($client_nfsv4_services, $server_nfsv4_servicehelper)
} else {
$effective_nfsv4_client_services = $client_nfsv4_services
}
$effective_client_services       = $client_services
} else {
$effective_client_packages       = $client_packages
$effective_nfsv4_client_services = $client_nfsv4_services
$effective_client_services       = $client_services
}

worked local, lets see.

that stuff is green \o/

Great!
Could you please update the testing matrix (see my last comment).
Then i could do a merge. Version bump and new release on forge will follow tomorrow.

@derdanne done

Thank you for your hard work on this module!


Getting error while running on jetson tk1

The frame of ARM doesn't support a lot of libraries, so a simplification of the code helps a lot. Besides, the GCC compilers of ARM and x64 differ from each other in several ways, for example, "size_t" equals "unsigned long int" in x64 while equals "unsigned int" in ARM (maybe it's not very accurate).


Support wider range of client/server use cases

Small nit: This PR title does not quite match the contents since this is just back porting the verify and identity fixes.


Traffic Influence Release 0.9.1

Beta candidate release

this is the TI API Beta version, according to the discussion in Readiness Checklist step 6 update proposal #249 (https://github.com/camaraproject/WorkingGroups/issues/249)

@gunjald

thank you, I'm going to fix it
Zone ID and Region ID are defined by the Telco Operator who is sharing the Edge resources. My idea is that they are explained in the Marketplace portal where the TI API is sold. In the Portal the Developer can find a mapping among zones, regions and actual geographical locations. Maybe we can add this concept in the API Documentation. Anyway the same explanation should be also included in the other Edge Cloud APIs if zones and regions are used

The PUT operations typically affects the mutable attributes of a resource. Generally absence of such attributes in the PUT request is assumed by server implementation to remove or unset the given attribute.
In TI API i think we should also capture what are the mutable attributes and what are immutable attributes and that would also help server implementation to check and update only mutable attributes of the TI API resource. Or we can even think of using PATCH operation to selectively update the mutable attributes.

@gunjald it is a good suggestion. I would prefer to start reasoning on possible improvements still using the PUT method rather than introducing PATCH, if possible, to reduce the impact of the changes. So, still considering PUT as method, and because the API is based on the exchange between client and server of the whole Traffic Influence resource, are you suggesting to improve the documentation to specify which parameter can be modified in the PUT and which one are not? Or are you suggesting a revision of the code with the PUT not using the TI Resource?

@gunjald You suggestion was actually great. I have changed the PUT method into PATCH and I have defined two new resources, derived from the original TrafficInfluence Resource, for the method POST and PATCH. This two new resources just have the editable parameters allowed for those methods.

@gunjald You suggestion was actually great. I have changed the PUT method into PATCH and I have defined two new resources, derived from the original TrafficInfluence Resource, for the method POST and PATCH. This two new resources just have the editable parameters allowed for those methods. Please, have a look on the new version.

I think the PATCH methods added really helps in this form. I have two observations though,

The reference to "Partner OP" in the statement "Unique identifier generated by the partner OP to identify an instance of the application on a specific zone." Do you only mean to say "OP" and not the "Partner OP"?
In Patch request the one of the modifiable parameter is "Device" which could be MSISDN or the IP Address. For the modification purpose usage of the Device can result into different conditions e.g. that the POST request contains the MSISDN while the PATCH contains the IP Address or vice versa. So do we really want to support such situations is there is something missing in my understanding?

@gunjald

I just copied the InstanceIdentifier definition from the EdgeCloudApi: https://github.com/camaraproject/EdgeCloud/blob/main/code/API_definitions/Resource Management/EdgeCloudApi_v0.0.5.yaml.    I don't have any problem changing the text, it is important to have the the APIs aligned in the attributes definition though.
I don't see any problem changing the Device type, it can be totally different, maybe even another user. Which kind of problem  do you foresee?

@gunjald I have fixed the typo related to your request for changes. Can you verify and approve it?

@gunjald about the parameter "applicationId" in the TI API.
That parameter is provided by the EdgeCloudAPI.
I just noticed that the definition for that parameter is changed in the current version of the EdgeCloudAPI.
Now it is "AppIdentifier". Am I right?
If so we should align the TI API code.

@gunjald about the parameter "applicationId" in the TI API.
That parameter is provided by the EdgeCloudAPI (https://github.com/camaraproject/EdgeCloud/blob/main/code/API_definitions/Resource Management/EdgeCloudApi_v0.0.5.yaml).
I just noticed that the definition for that parameter is changed in the current version of the EdgeCloudAPI.
Now it is "AppIdentifier". Am I right?
If so we should align the TI API code.
I think lets keep it as is for now. We are still having more alignments based on CAMARA API design guidelines and some of the definitions may undergo change. Till that point i would suggest to keep it as is and once all contribution for resource management and orchestration will be updated then we can take this up at that point.

about the parameter "applicationId", I totally agree.
Anyway this version (v0.9.1) is not relevant anymore and we can close the PR


Added rb files for 1.4.0 release

@ShivanshGahlot @priyanshi-yb  - could it be possible to automate this process similar to what I did for the CLI: https://github.com/yugabyte/homebrew-tap/blob/master/bump_ybm_cli_latest.sh ?


HTTPResponseCompressor's API doesn't support selective compression

The current HTTPResponseCompressor API doesn't support selective compression:
https://github.com/apple/swift-nio/blob/ed28803a78b187e202c27a62c7a497fbe9cfbbd7/Sources/NIOHTTP1/HTTPResponseCompressor.swift#L59-L63
It's a duplex handler because it needs to grep the accept-encoding header from the request out in order to compress the response. The problem is that if the client says it supports compression the response compressor will then always compress...
The only way that I can see to not compress a certain response is to remove the responsecompressor just before sending a response and then to immediately create a new compressor that then needs to be added to the pipeline. And that will also only work without pipelining (or with the pipeline helper enabled). Don't think the current API is good enough tbh.

CC @kjessup

Yeah the current API is definitely limited: unfortunately, that limitation basically comes from the fact that there doesn't appear to be a really wonderful set of API choices that work nicely.
The most obvious alternative API design is to follow the pattern established in the protocol upgrader, which is that you'd have a constructor like this:
public init(_ shouldCompress: (HTTPRequestHead, HTTPResponseHead) -> Bool)

This would, for each response head, ask whether the response itself should be compressed. This is a strict improvement over the current model, but has the disadvantage of requiring the user do some awkward state coordination if they can't determine whether they should compress based purely on the header block. It's unquestionably an improvement over the current API, but it's not necessarily a great fit.
More generally this handler is not a good fit for many projects. It has a bunch of other limitations:

no support for offline compression
no support for lazy offline compression of resources
blocks event loop to run compression, causing performance hits
frequently changes content-length-delimited responses to chunked responses

While we can design a better API for this handler, it's not clear to me that we should. In general for web frameworks I'd say that compression of resources is something the framework itself should be handling, and that it should not be part of the channel pipeline. Frameworks should support offline compression of static resources into multiple compressed formats such that those compressed responses can be served from disk, and should allow compression of dynamic resources based on meta-knowledge of the resource itself. This handler is not so much a general solution to that problem as it is an example, and something that can be used in situations where you are confident that all resources can reasonably be compressed (e.g. you only ship JSON responses).

I don't have a great idea either for an API either. Instead of a ChannelHandler maybe we want to provide convenience functions of the form (HTTPResponsePart) -> Future<HTTPResponsePart> that do the compression. These could come with options for example whether to compress on or off the event loop etc. That way we're moving it into the web framework itself but it's super low overhead for them to support it. To mimic the current behaviour the web framework could just replace
ctx.write(...(responsePart))

with
compressBody(responsePart).flatMap { ctx.write(...($0) }

and if they want to only selectively compress
(shouldCompress(reqHead) ? compressBody : identity)(responsePart).flatMap { ctx.write(...($0)) }

or something along those lines. So I agree we probably want to take this out of the pipeline.

I think that raises a follow-on question for me: should we just be providing an encapsulation for compression in general? At this stage we're basically just wrapping zlib, so should we lean into that and just provide a useful API to wrapping zlib?

I haven't been following this closely, but IMO compressing and decompressing channels are useful for many verbose HTTP APIs, e.g. WebDAV or anything JSON. This is separate to compressing (and storing/caching) large resources like say PDFs or images.
I'm not sure (and didn't do tests on that in the last 15 years or so), but I assume the compression overhead for API requests should be negligible and you wouldn't want to dispatch the compression outside the event loop. If anything, it should be faster than not having compression.

@helje5 Definitely agreed, we're mostly just trying to work out what the set of primitives NIO provides should be, vs what frameworks should be handling themselves.
I see the questions as being as follows:

Is the HTTPResponseCompressor with the behaviour as written today worth preserving?
Should it be replaced by something smarter built in to NIO? If so, what should that look like?
Should we provide better APIs to compression libraries to allow users to build this thing?

My current set of answers is:

Probably yes, IMO it works nicely when you know you only have dynamic textual responses being passed around.
Probably not: I struggle to conceive of an API that will be nice enough to drive from a web framework, which is the entity that ultimately needs to decide whether to apply compression or not.
Probably no: we aren't in the business of shipping compression libraries.

But I don't hold any of these positions strongly, which is why I'm interested in kicking the idea around here and seeing what others think. I'm happy to be swayed on any of those answers.

The more you think about it, the harder it gets. There is also the API issues around TE vs Content-Encoding (and the effects of the latter, e.g. potentially different ETags, ranges etc).
A channel which always compresses the whole host/port really just doesn't feel right and might encourage doing the wrong thing (much like the "back pressure" handler, sorry 😬).
My feeling is that you would definitely want compression handlers in NIO. But to make it work, I think you would need to be able to create stacked pipelines? So that you can create a new one which is just active for the current request and add the compression handler if necessary. So I wonder whether the API discussion is more an issue with the current "pipeline API" (e.g. in Node you can just freely nest streams).
(don't you have to do some form of nested pipeline for HTTP/2 anyways?)

After further discussion with @helje5, I think a more useful construction may be this:

Deprecate HTTPResponseCompressor.

Write a new HTTPResponseCompressor that is "one-shot".
Specifically, this will change the HTTPResponseCompressor to only ever be able to compress one response. It will also be explicitly told which compression algorithm to use to compress the response, rather than deploying its current compression detection logic.

Write a new HTTP channel handler that creates a sub-channel per request.
This would make it much easier to write things that look roughly like "middlewares", but that operate in the context of the channel pipeline. Rather than put them into the main channel pipeline and worry about how to handle that, they could be placed into the sub-channel pipeline, knowing full-well that the sub-channel will live for one and only one HTTP request.
This handler would probably require the use of the HTTPServerPipelineHandler to keep code complexity down.

How do people feel about this approach?

Sounds quite good but we need to assess how many allocations etc that'll cause per request.

Thats is actually a fair point. So maybe some "should-I-do-my-job-callback" API is the better way to go.

CC @normanmaurer


fix(outline-dot): default to small, not large

Coverage increased (+1.06%) to 100.0% when pulling f21f45219a967cd32b5ccd8e2ab8d3473a38d5d6 on fix/outline-dot into e68c872c0f933f2d08ddb2830222d764e6d707de on master.


/etc/hosts not consistently populated when using --x-networking

Description of problem:
When starting a small cluster of consul server nodes using docker-compose, the /etc/hosts file is not being populated with the containers in the compose file in docker v1.9.1 but in docker v1.9.0 it works with no issues.
docker version:
works
Client:
Version:      1.9.0
API version:  1.21
Go version:   go1.4.2
Git commit:   76d6bc9
Built:        Tue Nov  3 17:43:42 UTC 2015
OS/Arch:      linux/amd64
Server:
Version:      1.9.0
API version:  1.21
Go version:   go1.4.2
Git commit:   76d6bc9
Built:        Tue Nov  3 17:43:42 UTC 2015
OS/Arch:      linux/amd64
does not work
Client:
Version:      1.9.1
API version:  1.21
Go version:   go1.4.2
Git commit:   a34a1d5
Built:        Fri Nov 20 13:12:04 UTC 2015
OS/Arch:      linux/amd64
Server:
Version:      1.9.1
API version:  1.21
Go version:   go1.4.2
Git commit:   a34a1d5
Built:        Fri Nov 20 13:12:04 UTC 2015
OS/Arch:      linux/amd64
docker info:
works
Containers: 12
Images: 267
Server Version: 1.9.0
Storage Driver: aufs
Root Dir: /var/lib/docker/aufs
Backing Filesystem: extfs
Dirs: 291
Dirperm1 Supported: false
Execution Driver: native-0.2
Logging Driver: json-file
Kernel Version: 3.13.0-65-generic
Operating System: Ubuntu 14.04.3 LTS
CPUs: 1
Total Memory: 1.961 GiB
Name: entcon-dev
ID: 36BW:5BP7:WN6J:KRNT:WVUO:IG7I:7X3J:SCCU:ZLA5:MUI2:TV3Y:U4ES
WARNING: No swap limit support
does not work
Containers: 0
Images: 203
Server Version: 1.9.1
Storage Driver: aufs
Root Dir: /var/lib/docker/aufs
Backing Filesystem: extfs
Dirs: 203
Dirperm1 Supported: false
Execution Driver: native-0.2
Logging Driver: json-file
Kernel Version: 3.13.0-62-generic
Operating System: Ubuntu 14.04.3 LTS
CPUs: 1
Total Memory: 1.961 GiB
Name: entcon-dev
ID: FI5A:ABI5:2UXI:LSID:OS76:FP5F:SI3H:IKUV:ENDV:CBIB:Z3UH:YN4N
WARNING: No swap limit support
uname -a:
Linux entcon-dev 3.13.0-65-generic #105-Ubuntu SMP Mon Sep 21 18:50:58 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux
Environment details (AWS, VirtualBox, physical, etc.):
Virtualbox v5
How reproducible:
Using the following docker-compose.yml file:
consul1:
  container_name: consul1
  build: .
  command: "agent -join consul3 -config-dir=/config"
  ports:
    - "8301"
    - "8302"
    - "8400"
    - "8500"
    - "8600"

consul2:
  container_name: consul2
  build: .
  command: "agent -join consul3 -config-dir=/config"
  ports:
    - "8301"
    - "8302"
    - "8400"
    - "8500"
    - "8600"

consul3:
  container_name: consul3
  build: .
  command: "agent -bootstrap-expect 3 -config-dir=/config"
  ports:
    - "8301"
    - "8302"
    - "8400"
    - "8500"
    - "8600"

Dockerfile:
FROM alpine:3.2

ENV CONSUL_VERSION 0.5.2
ENV GOMAXPROCS 2

RUN apk --update add curl ca-certificates \
   && curl -Ls https://circle-artifacts.com/gh/andyshinn/alpine-pkg-glibc/6/artifacts/0/home/ubuntu/alpine-pkg-glibc/packages/x86_64/glibc-2.21-r2.apk > /tmp/glibc-
2.21-r2.apk \
   && apk add --allow-untrusted /tmp/glibc-2.21-r2.apk \
   && curl -Ls https://dl.bintray.com/mitchellh/consul/${CONSUL_VERSION}_linux_amd64.zip > /tmp/consul.zip \
   && cd /bin \
   && unzip /tmp/consul.zip \
   && chmod +x /bin/consul \
   && rm -rf \
       /tmp/glibc-2.21-r2.apk \
       /tmp/consul.zip \
       /var/cache/apk/*

EXPOSE 8300 8301 8301/udp 8302 8302/udp 8400 8500 8600 8600/udp
ENV DNS_RESOLVES consul
ENV DNS_PORT 8600

ENTRYPOINT ["/bin/consul"]

COPY consul.json /config/

config.json
{
 "data_dir": "/data",
 "server": true,
 "dns_config": {
       "allow_stale": true,
       "max_stale": "1s"
   }
}

Steps to Reproduce:

docker-compose build
docker-compose --x-networking up -d

Actual Results:
on Docker v1.9.0:
Creating network "consul" with driver "None"
Creating consul3
Creating consul2
Creating consul1

 Name                Command               State                                                                                Ports
----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
consul1   /bin/consul agent -join co ...   Up      8300/tcp, <IP_ADDRESS>:32782->8301/tcp, 8301/udp, <IP_ADDRESS>:32781->8302/tcp, 8302/udp, <IP_ADDRESS>:32780->8400/tcp, <IP_ADDRESS>:32779->8500/tcp, <IP_ADDRESS>:32778->8600/tcp, 8600/udp
consul2   /bin/consul agent -join co ...   Up      8300/tcp, <IP_ADDRESS>:32777->8301/tcp, 8301/udp, <IP_ADDRESS>:32776->8302/tcp, 8302/udp, <IP_ADDRESS>:32775->8400/tcp, <IP_ADDRESS>:32774->8500/tcp, <IP_ADDRESS>:32773->8600/tcp, 8600/udp
consul3   /bin/consul agent -bootstr ...   Up      8300/tcp, <IP_ADDRESS>:32772->8301/tcp, 8301/udp, <IP_ADDRESS>:32771->8302/tcp, 8302/udp, <IP_ADDRESS>:32770->8400/tcp, <IP_ADDRESS>:32769->8500/tcp, <IP_ADDRESS>:32768->8600/tcp, 8600/udp

on Docker v1.9.1:
Creating network "consul" with driver "None"
Creating consul3
Creating consul2
Creating consul1

                 Name                                   Command                                   State                                    Ports
-----------------------------------------------------------------------------------------------------------------------------------------------------------------
consul1                                  /bin/consul agent -join co ...           Exit 1
consul2                                  /bin/consul agent -join co ...           Exit 1
consul3                                  /bin/consul agent -bootstr ...           Up                                       8300/tcp, <IP_ADDRESS>:32772->8301/tcp,
                                                                                8301/udp, <IP_ADDRESS>:32771->8302/tcp,
                                                                                8302/udp, <IP_ADDRESS>:32770->8400/tcp,
                                                                                <IP_ADDRESS>:32769->8500/tcp,
                                                                                <IP_ADDRESS>:32768->8600/tcp, 8600/udp

Attaching to consul1
consul1 | ==> Starting Consul agent...
consul1 | ==> Starting Consul agent RPC...
consul1 | ==> Joining cluster...
consul1 | ==> lookup consul3: no such host
Attaching to consul2
consul2 | ==> Starting Consul agent...
consul2 | ==> Starting Consul agent RPC...
consul2 | ==> Joining cluster...
consul2 | ==> lookup consul3: no such host
vagrant@entcon-dev:~/entcon/authstore/consul$ sudo cat /var/lib/docker/containers/7a893027b200b11b33051f41c42e4e5f895d6bd2ff83941e10b255437b534e70/hosts
<IP_ADDRESS>      7a893027b200
<IP_ADDRESS>       localhost
::1     localhost ip6-localhost ip6-loopback
fe00::0 ip6-localnet
ff00::0 ip6-mcastprefix
ff02::1 ip6-allnodes
ff02::2 ip6-allrouters
vagrant@entcon-dev:~/entcon/authstore/consul$ sudo cat /var/lib/docker/containers/3e9caf3414c60d5bd0a8428f8a66b84ec0f3469949171d6e4c74c8f1a719bf0b/hosts
<IP_ADDRESS>      3e9caf3414c6
<IP_ADDRESS>       localhost
::1     localhost ip6-localhost ip6-loopback
fe00::0 ip6-localnet
ff00::0 ip6-mcastprefix
ff02::1 ip6-allnodes
ff02::2 ip6-allrouters

Expected Results:
Creating network "consul" with driver "None"
Creating consul3
Creating consul2
Creating consul1

 Name                Command               State                                                                                Ports
----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
consul1   /bin/consul agent -join co ...   Up      8300/tcp, <IP_ADDRESS>:32782->8301/tcp, 8301/udp, <IP_ADDRESS>:32781->8302/tcp, 8302/udp, <IP_ADDRESS>:32780->8400/tcp, <IP_ADDRESS>:32779->8500/tcp, <IP_ADDRESS>:32778->8600/tcp, 8600/udp
consul2   /bin/consul agent -join co ...   Up      8300/tcp, <IP_ADDRESS>:32777->8301/tcp, 8301/udp, <IP_ADDRESS>:32776->8302/tcp, 8302/udp, <IP_ADDRESS>:32775->8400/tcp, <IP_ADDRESS>:32774->8500/tcp, <IP_ADDRESS>:32773->8600/tcp, 8600/udp
consul3   /bin/consul agent -bootstr ...   Up      8300/tcp, <IP_ADDRESS>:32772->8301/tcp, 8301/udp, <IP_ADDRESS>:32771->8302/tcp, 8302/udp, <IP_ADDRESS>:32770->8400/tcp, <IP_ADDRESS>:32769->8500/tcp, <IP_ADDRESS>:32768->8600/tcp, 8600/udp

Additional info:

#https://github.com/docker/compose/issues/2445

ping @aboch @mavenugo @mrjana PTAL, possible regression in 1.9.1

@kenjones-cisco can you please also provide the docker logs ?

@mavenugo  Just to clarify, are you referring to the docker daemon logs?

@kenjones-cisco this seems very specific to the way compose launches the containers and the way consul expects the /etc/hosts resolution to have happened when it boots up.
Since we have 3 containers with 2 of them depending on consul3 container and expects the /etc/hosts of consul1 and consul2 to be populated with consul3., It must be compose's responsibility to launch consul3 first before consul1 & consul2 so that the docker engine knows the availability of the container named consul3.
Also, consul's behavior on failing if /etc/hosts update is not done is very random and timing related.
the reproduction is completely random & I need to understand how Compose sequentialize the containers starts. With links, it is evident. But with the new networking feature, it isnt clear.
Lets have the discussion in the compose project as I dont see this as engine specific nor it seems like 1.9.1 related.

I will close this for now and discuss the issue in compose project.
We can reopen this if we learn more.


Added common HeaderKey values

Adds a set of common HeaderKey values as static variables. This will protect developers from mis-typing common header key values, and adds them to the auto-complete list in Xcode (or other IDEs).
Only header values that are considered "permanent" are included.

Thanks!


New bug: enabling a new user leads to an error

Error!
Request method 'POST' not supported

@AlexHartveld @darioseidl
The problem occur because of a single random user that has a value of null.
PLEASE If you want to use the system correctly then we have to secure the registration (NEW PARTICIPANT REGISTRATION).
The system right now acts like a toy that can be broken with any unknown rule set from the user.
** This is a basic rule in programming **
Plan --> Study scenarios and possibilities --> Then program your plan
We are here missing the second phases.
Otherwise it is just playing around.


keyboard input: support alt/shift/ctrl modifiers

also prevent key events to bubble up to browser so that the game can use keys like TAB, F5, ...

Look good to me


Laravel 11 support

Could you please add support for the newest Laravel version? Kind regards

Yep, thanks for the nudge ☺


Add a ball event raised during multiball when at max ball count causes issues once all balls drained from playfield

I have a multiball configured at the start to be the maximum for the machine - 6 balls. There are add a ball events. If an add a ball event is triggered when the maximum number of balls are active on the playfield a warning is raised in the log file (which is correct), but there is an undesirable effect on the game logic after all balls drained (which can be seen in one of my game unit tests).
I have confirmed before the ball drains that there are no active ball saves.
I would assume that the engine would handle this logic (as opposed to placing conditions around the add-a-ball event). Would this be safe to assume?
If this description is sufficient I'll leave it as that, otherwise if further information is required, I'll setup a test MPF project to replicate the problem.

This is expected behavior, because the conditions of add-a-ball during multiball are not obvious one way or the other. In some situations (like yours) the add-a-ball should only add up to a certain number of balls, but in other situations the added balls should be saved so that the player still earns them and reaps the benefits.

Therefore in your situation, a condition on the add-a-ball is appropriate. I would set the condition based on the balls_in_play value rather than max_balls, for the reason noted above.

Thanks... that makes sense and I am happy to add the guard condition (which is what I did as my workaround after I posted), but I still have this major issue...
If I miss a guard condition on the add a ball event when it fires, a warning is raised (expected behavior)...
But... during that multiball once balls start draining, I have had numerous problems (which is repeatable in every case) where it would act as if all balls have drained even when multiple balls are still active on the playfield and then ends the multiball prematurely and the current ball resulting in a ball_ending event.
This I do believe to be an issue.

That's entirely likely, MPF is known to have some challenges when it comes to counting balls.  Thanks!


[BUG]: Fix feature names for sklearn API

This PR fixes the bug described in #1082.
Indeed, current UMAP scikit-learn compatible class does not support using pandas dataframes as it will output the input features names.
The fix is to use the ClassNamePrefixFeaturesOutMixin and set the _n_features_out attribute after fitting.
This will give feature names umap0, umap1, etc... following what scikit-learn does for the dimensionality reduction transformers.

This looks good. A couple of catches -- the tests seem to be failing right now; you may have to amend the tests for feature name related things to call "fit" (it currently doesn't), and possibly a few other fixes. The other thing is that dosctrings should be in numpy format if possible. Any chance you can fix this so we can merge this?

Hello @fraimondo! Thanks for updating this PR. We checked the lines you've touched for PEP 8 issues, and found:

In the file umap/tests/test_umap_get_feature_names_out.py:

Line 41:77: W291 trailing whitespace

This looks good. A couple of catches -- the tests seem to be failing right now; you may have to amend the tests for feature name related things to call "fit" (it currently doesn't), and possibly a few other fixes. The other thing is that dosctrings should be in numpy format if possible. Any chance you can fix this so we can merge this?

Just fixed the tests.
Regarding docstrings, I did not make any change that would require modifying or adding docstrings. I'll wait for the CI to see if I'm missing something.

Ready to merge!

Thanks!


Pvc cleaner initial

Add initial impimentation.
Small demo: https://www.youtube.com/watch?v=757esM4pR74

Hmm, now I noticed that it is not global, it has to be installed in each namespace. That's probably not matching our usecase since it should cleanup all namespaces managed by appstudio.

@Michkov: Hmm, now I noticed that it is not global, it has to be installed in each namespace. That's probably not matching our usecase since it should cleanup all namespaces managed by appstudio.

On the Thursday standup meeting @jduimovich asked "Can we merge current solution for current staging and then improve code to cover all namespaces mode?". I said, yes, we can. I can created separated issue for that...

Yes, the issue in staging was the pv's for dogfooding are filling up, so use this current solution per NS, and extend to support all NS.


Document the security policy policy for Jenkinsfile Runner beta releases

As discussed with @daniel-beck today, Jenkinsfile Runner releases are not coordinated with the Jenkins Security release process. In practice it means that the Jenkinsfile Runner distributions may include the Jenkins core and plugins with known vulnerabilities once released by the Jenkins project. Not all Jenkins vulnerabilities are applicable to Jenkinsfile Runner (e.g. all WebUI-related issues like CSRF), but it might be a concern in some cases.
It would be great to add a security disclaimer for the beta releases.

FTR #416 is a final fix for 1.0


Latest update in media manager

https://github.com/bludit/bludit/blob/0657c55191c40f4dc9b2f519058915522405a131/bl-kernel/admin/themes/booty/html/media.php#L4
DS cause error on IIS, because it is used in javascript.
Fix:
if (IMAGE_RESTRICT) {
	$imagesDirectory = (IMAGE_RELATIVE_TO_ABSOLUTE? '' : HTML_PATH_UPLOADS_PAGES.$uuid.'/');
	$thumbnailDirectory = PATH_UPLOADS_PAGES.$uuid.DS.'thumbnails'.DS;
	$thumbnailHTML = HTML_PATH_UPLOADS_PAGES.$uuid.'/thumbnails/';
} ...

Implemented in Bludit v3.1.0. Thanks!


GRS replication for cloud witness

Hi Team,
Com customers want to use GRS replication for the storage account, this documentation only supports LRS and ZRS.
I have contacted Azure Storage SME, Windows SHA PTA and SQL escalation engineer and all of the, stated that customer can use GRS to store the witness because it will work fine.
If you can verify this info, please, change the documentation in order to support those customers using GRS storage account.
If GRS is not a good option and it is not supported, please, include in the documentation the reason why in order for us to be able to explain it to the customers.
Appreciate your help.
Have a good day,
Priscila Bilek.

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

ID: 7e6da99e-a148-b5ea-224d-8a4c48604945
Version Independent ID: a6a90a1f-870c-3501-ce6e-fbf52f802dfb
Content: Deploy a cloud witness for a failover cluster in Windows Server
Content Source: WindowsServerDocs/failover-clustering/deploy-cloud-witness.md
Service: windows-server
Sub-service: failover-clustering
GitHub Login: @JasonGerend
Microsoft Alias: jgerend

Hi Team,
Could you please update on this , we also need to configure the same if GRS is a supported configuration as a cloud witness

We hugely appreciate your contribution, feedback, and support to our technical documentation.
We’ve phased out GitHub Issues on this repository as the feedback mechanism for content and have replaced it with a new feedback system. For more information see, Content User Feedback. As part of this rollout, we are migrating your issue where our team will use your comments to improve the documentation experience. Unfortunately, this does mean you won't be able to access this issue after the migration is complete.
All issues will be migrated by Thursday 29th August 2024.
Once again, thank you for your valuable feedback, we hope you’ll continue to contribute using our new feedback system.


[Bug]: Failed build does not return the right exit code

Which Remix packages are impacted?

[X] remix (Remix core)
[ ] create-remix
[ ] @remix-run/architect
[ ] @remix-run/cloudflare-workers
[ ] @remix-run/dev
[ ] @remix-run/express
[ ] @remix-run/netlify
[ ] @remix-run/node
[ ] @remix-run/react
[ ] @remix-run/serve
[ ] @remix-run/server-runtime
[ ] @remix-run/vercel

What version of Remix are you using?
1.1.3
What version of Node are you using? Minimum supported version is 14.
16.13.2
Steps to Reproduce

Write code that should break (e.g. import a missing file)
Run npm run build

Expected Behavior
Since the build script returns "Build failed with [...] errors:", I expect it to throw a proper exit code. I'm building my Remix app with GitHub actions, but the script doesn't stop even if the build breaks.
Actual Behavior
It doesn't throw the right exit code and processes like GitHub actions continue with the broken/missing build.

Oof yeah, just ran into this on 1.3.4 as well, I'll take a stab at a PR if nobody is working on this yet

Looks like https://github.com/remix-run/remix/pull/1822 should fix it

Fixed by #1822


Allow more flexible type checks on duration

The current way of checking int and float cannot handle numpy's data types, such as np.int64 and np.float64, which requires extra effort to convert a numpy element into int or float to pass the check.
Using numeric ABCs solves the problem and allows more flexible "implementations" of integers and real numbers. (Better than the approach in #224, no extra dependencies needed)
=== Updated ===
Tests can be passed locally.
CI seems to complain something about repo_token and marked them as failed.

thanks @zzrcxb!


Implemented frontend users

Oh yeah the country issue is known to me, the backend does currently not merge the country into the address and I was hoping for a fix from the backend for this. But I can provide a workaround until then

If it is up to the backend then I suggest you merge this and make a JIRA issue on CORE :)