No uvcvideo module loaded at boot

Hi, I install the library on my jetson tx1, almost everything turnout well but the qt installation from the trusty repositories, I managed to install qt anyway and the library compiled but at restart the uvcvideo is not loaded, therefore when I run a builded example from the library it says no camera is detected.
My specs:
Kernel: 4.4.38-jetsonbot-v0.2
Camera model: sr300
Operating System & Version: Ubuntu 16.04 (Linux for Tegra 28.1)
My installation went like follows:
`You are in 'detached HEAD' state. You can look around, make experimental
changes and commit them, and you can discard any commits you make in this
state without impacting any branches by performing another checkout.
If you want to create a new branch to retain commits you create, you may
do so (now or later) by using -b with the checkout command again. Example:
git checkout -b
HEAD is now at 7332eca... Bump version
patching file src/uvc-v4l2.cpp
Hit:1 http://ports.ubuntu.com/ubuntu-ports xenial InRelease
Ign:2 http://archive.ubuntu.com/ubuntu trusty InRelease
Hit:3 http://ports.ubuntu.com/ubuntu-ports xenial-updates InRelease
Hit:5 http://ports.ubuntu.com/ubuntu-ports xenial-security InRelease
Get:4 http://archive.ubuntu.com/ubuntu trusty Release [58.5 kB]
Get:6 http://archive.ubuntu.com/ubuntu trusty Release.gpg [933 B]
Hit:7 http://packages.ros.org/ros/ubuntu xenial InRelease
Ign:8 http://archive.ubuntu.com/ubuntu trusty/main arm64 Packages
Ign:9 http://archive.ubuntu.com/ubuntu trusty/universe arm64 Packages
Ign:8 http://archive.ubuntu.com/ubuntu trusty/main arm64 Packages
Ign:9 http://archive.ubuntu.com/ubuntu trusty/universe arm64 Packages
Err:8 http://archive.ubuntu.com/ubuntu trusty/main arm64 Packages
404  Not Found [IP: <IP_ADDRESS> 80]
Ign:9 http://archive.ubuntu.com/ubuntu trusty/universe arm64 Packages
Fetched 59.4 kB in 0s (71.7 kB/s)
Reading package lists... Done
E: Failed to fetch http://archive.ubuntu.com/ubuntu/dists/trusty/main/binary-arm64/Packages  404  Not Found [IP: <IP_ADDRESS> 80]
E: Some index files failed to download. They have been ignored, or old ones used instead.
-- Info: REALSENSE_VERSION_STRING=1.12.1
-- The C compiler identification is GNU 5.4.0
-- The CXX compiler identification is GNU 5.4.0
-- Check for working C compiler: /usr/bin/cc
-- Check for working C compiler: /usr/bin/cc -- works
-- Detecting C compiler ABI info
-- Detecting C compiler ABI info - done
-- Detecting C compile features
-- Detecting C compile features - done
-- Check for working CXX compiler: /usr/bin/c++
-- Check for working CXX compiler: /usr/bin/c++ -- works
-- Detecting CXX compiler ABI info
-- Detecting CXX compiler ABI info - done
-- Detecting CXX compile features
-- Detecting CXX compile features - done
-- Performing Test COMPILER_SUPPORTS_CXX11
-- Performing Test COMPILER_SUPPORTS_CXX11 - Success
-- Performing Test COMPILER_SUPPORTS_CXX0X
-- Performing Test COMPILER_SUPPORTS_CXX0X - Success
-- Found PkgConfig: /usr/bin/pkg-config (found version "0.29.1")
-- Looking for pthread.h
-- Looking for pthread.h - found
-- Looking for pthread_create
-- Looking for pthread_create - not found
-- Looking for pthread_create in pthreads
-- Looking for pthread_create in pthreads - not found
-- Looking for pthread_create in pthread
-- Looking for pthread_create in pthread - found
-- Found Threads: TRUE
-- Checking for one of the modules 'libusb-1.0'
-- Found OpenGL: /usr/lib/aarch64-linux-gnu/libGL.so
-- Configuring done
-- Generating done
-- Build files have been written to: /home/nvidia/librealsense/build
Scanning dependencies of target realsense
[  1%] Building CXX object CMakeFiles/realsense.dir/src/archive.cpp.o
[  2%] Building CXX object CMakeFiles/realsense.dir/src/context.cpp.o
[  3%] Building CXX object CMakeFiles/realsense.dir/src/device.cpp.o
[  4%] Building CXX object CMakeFiles/realsense.dir/src/ds-device.cpp.o
[  5%] Building CXX object CMakeFiles/realsense.dir/src/ds-private.cpp.o
[  6%] Building CXX object CMakeFiles/realsense.dir/src/f200.cpp.o
[  7%] Building CXX object CMakeFiles/realsense.dir/src/hw-monitor.cpp.o
[  9%] Building CXX object CMakeFiles/realsense.dir/src/image.cpp.o
[ 10%] Building CXX object CMakeFiles/realsense.dir/src/ivcam-private.cpp.o
[ 11%] Building CXX object CMakeFiles/realsense.dir/src/ivcam-device.cpp.o
[ 12%] Building CXX object CMakeFiles/realsense.dir/src/log.cpp.o
[ 13%] Building CXX object CMakeFiles/realsense.dir/src/motion-module.cpp.o
[ 14%] Building CXX object CMakeFiles/realsense.dir/src/r200.cpp.o
[ 15%] Building CXX object CMakeFiles/realsense.dir/src/rs.cpp.o
[ 17%] Building CXX object CMakeFiles/realsense.dir/src/sr300.cpp.o
[ 18%] Building CXX object CMakeFiles/realsense.dir/src/stream.cpp.o
[ 19%] Building CXX object CMakeFiles/realsense.dir/src/sync.cpp.o
[ 20%] Building CXX object CMakeFiles/realsense.dir/src/timestamps.cpp.o
[ 21%] Building CXX object CMakeFiles/realsense.dir/src/types.cpp.o
[ 22%] Building CXX object CMakeFiles/realsense.dir/src/uvc-libuvc.cpp.o
[ 23%] Building CXX object CMakeFiles/realsense.dir/src/uvc-v4l2.cpp.o
[ 25%] Building CXX object CMakeFiles/realsense.dir/src/uvc-wmf.cpp.o
[ 26%] Building CXX object CMakeFiles/realsense.dir/src/uvc.cpp.o
[ 27%] Building C object CMakeFiles/realsense.dir/src/verify.c.o
[ 28%] Building CXX object CMakeFiles/realsense.dir/src/zr300.cpp.o
[ 29%] Building C object CMakeFiles/realsense.dir/src/libuvc/ctrl.c.o
[ 30%] Building C object CMakeFiles/realsense.dir/src/libuvc/dev.c.o
[ 31%] Building C object CMakeFiles/realsense.dir/src/libuvc/diag.c.o
[ 32%] Building C object CMakeFiles/realsense.dir/src/libuvc/frame.c.o
[ 34%] Building C object CMakeFiles/realsense.dir/src/libuvc/init.c.o
[ 35%] Building C object CMakeFiles/realsense.dir/src/libuvc/stream.c.o
[ 36%] Linking CXX shared library librealsense.so
[ 36%] Built target realsense
Scanning dependencies of target cpp-capture
[ 37%] Building CXX object examples/CMakeFiles/cpp-capture.dir/cpp-capture.cpp.o
[ 38%] Linking CXX executable cpp-capture
[ 38%] Built target cpp-capture
Scanning dependencies of target cpp-enumerate-devices
[ 39%] Building CXX object examples/CMakeFiles/cpp-enumerate-devices.dir/cpp-enumerate-devices.cpp.o
[ 40%] Linking CXX executable cpp-enumerate-devices
[ 40%] Built target cpp-enumerate-devices
Scanning dependencies of target cpp-pointcloud
[ 42%] Building CXX object examples/CMakeFiles/cpp-pointcloud.dir/cpp-pointcloud.cpp.o
[ 43%] Linking CXX executable cpp-pointcloud
[ 43%] Built target cpp-pointcloud
Scanning dependencies of target cpp-tutorial-3-pointcloud
[ 44%] Building CXX object examples/CMakeFiles/cpp-tutorial-3-pointcloud.dir/cpp-tutorial-3-pointcloud.cpp.o
[ 45%] Linking CXX executable cpp-tutorial-3-pointcloud
[ 45%] Built target cpp-tutorial-3-pointcloud
Scanning dependencies of target c-tutorial-3-pointcloud
[ 46%] Building C object examples/CMakeFiles/c-tutorial-3-pointcloud.dir/c-tutorial-3-pointcloud.c.o
[ 47%] Linking C executable c-tutorial-3-pointcloud
[ 47%] Built target c-tutorial-3-pointcloud
Scanning dependencies of target cpp-alignimages
[ 48%] Building CXX object examples/CMakeFiles/cpp-alignimages.dir/cpp-alignimages.cpp.o
[ 50%] Linking CXX executable cpp-alignimages
[ 50%] Built target cpp-alignimages
Scanning dependencies of target c-tutorial-1-depth
[ 51%] Building C object examples/CMakeFiles/c-tutorial-1-depth.dir/c-tutorial-1-depth.c.o
[ 52%] Linking C executable c-tutorial-1-depth
[ 52%] Built target c-tutorial-1-depth
Scanning dependencies of target cpp-callback-2
[ 53%] Building CXX object examples/CMakeFiles/cpp-callback-2.dir/cpp-callback-2.cpp.o
[ 54%] Linking CXX executable cpp-callback-2
[ 54%] Built target cpp-callback-2
Scanning dependencies of target c-tutorial-2-streams
[ 55%] Building C object examples/CMakeFiles/c-tutorial-2-streams.dir/c-tutorial-2-streams.c.o
[ 56%] Linking C executable c-tutorial-2-streams
[ 56%] Built target c-tutorial-2-streams
Scanning dependencies of target cpp-stride
[ 57%] Building CXX object examples/CMakeFiles/cpp-stride.dir/cpp-stride.cpp.o
[ 59%] Linking CXX executable cpp-stride
[ 59%] Built target cpp-stride
Scanning dependencies of target cpp-tutorial-2-streams
[ 60%] Building CXX object examples/CMakeFiles/cpp-tutorial-2-streams.dir/cpp-tutorial-2-streams.cpp.o
[ 61%] Linking CXX executable cpp-tutorial-2-streams
[ 61%] Built target cpp-tutorial-2-streams
Scanning dependencies of target cpp-tutorial-1-depth
[ 62%] Building CXX object examples/CMakeFiles/cpp-tutorial-1-depth.dir/cpp-tutorial-1-depth.cpp.o
[ 63%] Linking CXX executable cpp-tutorial-1-depth
[ 63%] Built target cpp-tutorial-1-depth
Scanning dependencies of target cpp-config-ui
[ 64%] Building CXX object examples/CMakeFiles/cpp-config-ui.dir/cpp-config-ui.cpp.o
[ 65%] Linking CXX executable cpp-config-ui
[ 65%] Built target cpp-config-ui
Scanning dependencies of target cpp-headless
[ 67%] Building CXX object examples/CMakeFiles/cpp-headless.dir/cpp-headless.cpp.o
[ 68%] Linking CXX executable cpp-headless
[ 68%] Built target cpp-headless
Scanning dependencies of target cpp-callback
[ 69%] Building CXX object examples/CMakeFiles/cpp-callback.dir/cpp-callback.cpp.o
[ 70%] Linking CXX executable cpp-callback
[ 70%] Built target cpp-callback
Scanning dependencies of target cpp-motion-module
[ 71%] Building CXX object examples/CMakeFiles/cpp-motion-module.dir/cpp-motion-module.cpp.o
[ 72%] Linking CXX executable cpp-motion-module
[ 72%] Built target cpp-motion-module
Scanning dependencies of target cpp-restart
[ 73%] Building CXX object examples/CMakeFiles/cpp-restart.dir/cpp-restart.cpp.o
[ 75%] Linking CXX executable cpp-restart
[ 75%] Built target cpp-restart
Scanning dependencies of target cpp-multicam
[ 76%] Building CXX object examples/CMakeFiles/cpp-multicam.dir/cpp-multicam.cpp.o
[ 77%] Linking CXX executable cpp-multicam
[ 77%] Built target cpp-multicam
Scanning dependencies of target SR300-live-test
[ 78%] Building CXX object unit-tests/CMakeFiles/SR300-live-test.dir/unit-tests-live.cpp.o
[ 79%] Building CXX object unit-tests/CMakeFiles/SR300-live-test.dir/unit-tests-live-sr300.cpp.o
[ 80%] Linking CXX executable SR300-live-test
[ 80%] Built target SR300-live-test
Scanning dependencies of target R200-live-test
[ 81%] Building CXX object unit-tests/CMakeFiles/R200-live-test.dir/unit-tests-live.cpp.o
[ 82%] Building CXX object unit-tests/CMakeFiles/R200-live-test.dir/unit-tests-live-ds-common.cpp.o
[ 84%] Building CXX object unit-tests/CMakeFiles/R200-live-test.dir/unit-tests-live-r200.cpp.o
[ 85%] Linking CXX executable R200-live-test
[ 85%] Built target R200-live-test
Scanning dependencies of target F200-live-test
[ 86%] Building CXX object unit-tests/CMakeFiles/F200-live-test.dir/unit-tests-live.cpp.o
[ 87%] Building CXX object unit-tests/CMakeFiles/F200-live-test.dir/unit-tests-live-f200.cpp.o
[ 88%] Linking CXX executable F200-live-test
[ 88%] Built target F200-live-test
Scanning dependencies of target ZR300-live-test
[ 89%] Building CXX object unit-tests/CMakeFiles/ZR300-live-test.dir/unit-tests-live.cpp.o
[ 90%] Building CXX object unit-tests/CMakeFiles/ZR300-live-test.dir/unit-tests-live-ds-common.cpp.o
[ 92%] Building CXX object unit-tests/CMakeFiles/ZR300-live-test.dir/unit-tests-live-zr300.cpp.o
[ 93%] Linking CXX executable ZR300-live-test
[ 93%] Built target ZR300-live-test
Scanning dependencies of target offline-test
[ 94%] Building CXX object unit-tests/CMakeFiles/offline-test.dir/unit-tests-offline.cpp.o
[ 95%] Linking CXX executable offline-test
[ 95%] Built target offline-test
Scanning dependencies of target LR200-live-test
[ 96%] Building CXX object unit-tests/CMakeFiles/LR200-live-test.dir/unit-tests-live.cpp.o
[ 97%] Building CXX object unit-tests/CMakeFiles/LR200-live-test.dir/unit-tests-live-ds-common.cpp.o
[ 98%] Building CXX object unit-tests/CMakeFiles/LR200-live-test.dir/unit-tests-live-lr200.cpp.o
[100%] Linking CXX executable LR200-live-test
[100%] Built target LR200-live-test
[ 36%] Built target realsense
[ 38%] Built target cpp-capture
[ 40%] Built target cpp-enumerate-devices
[ 43%] Built target cpp-pointcloud
[ 45%] Built target cpp-tutorial-3-pointcloud
[ 47%] Built target c-tutorial-3-pointcloud
[ 50%] Built target cpp-alignimages
[ 52%] Built target c-tutorial-1-depth
[ 54%] Built target cpp-callback-2
[ 56%] Built target c-tutorial-2-streams
[ 59%] Built target cpp-stride
[ 61%] Built target cpp-tutorial-2-streams
[ 63%] Built target cpp-tutorial-1-depth
[ 65%] Built target cpp-config-ui
[ 68%] Built target cpp-headless
[ 70%] Built target cpp-callback
[ 72%] Built target cpp-motion-module
[ 75%] Built target cpp-restart
[ 77%] Built target cpp-multicam
[ 80%] Built target SR300-live-test
[ 85%] Built target R200-live-test
[ 88%] Built target F200-live-test
[ 93%] Built target ZR300-live-test
[ 95%] Built target offline-test
[100%] Built target LR200-live-test
Install the project...[ 4665.177906] usb 1-3.1: new high-speed USB device number 5 using xhci-tegra
[ 4665.201105] usb 1-3.1: New USB device found, idVendor=05e3, idProduct=0610
[ 4665.208011] usb 1-3.1: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[ 4665.215614] usb 1-3.1: Product: USB2.0 Hub
[ 4665.219795] usb 1-3.1: Manufacturer: GenesysLogic
[ 4665.226986] hub 1-3.1:1.0: USB hub found
[ 4665.233103] hub 1-3.1:1.0: 2 ports detected
[ 4666.442082] usb 1-3.1.2: new full-speed USB device number 6 using xhci-tegra
[ 4666.563638] usb 1-3.1.2: config 1 has an invalid interface number: 3 but max is 2
[ 4666.571578] usb 1-3.1.2: config 1 has no interface number 2
[ 4666.652361] usb 1-3.1.2: New USB device found, idVendor=041e, idProduct=409b
[ 4666.659676] usb 1-3.1.2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 4666.668871] usb 1-3.1.2: Product: BlasterX Senz3D VF0810
[ 4666.674961] usb 1-3.1.2: Manufacturer: Creative Technology Ltd
[ 4666.681494] usb 1-3.1.2: SerialNumber:<PHONE_NUMBER>25
[ 4666.789400] input: Creative Technology Ltd BlasterX Senz3D VF0810 as /devices/70090000.xusb/usb1/1-3/1-3.1/1-3.1.2/1-3.1.2:1.3/0003:041E:409B.0003/input/input5
[ 4666.874843] hid-generic 0003:041E:409B.0003: input,hiddev0,hidraw2: USB HID v1.11 Device [Creative Technology Ltd BlasterX Senz3D VF0810] on usb-70090000.xusb-3.1.2/input3
-- Install configuration: ""
-- Installing: /usr/local/lib/librealsense.so.1.12.1
-- Up-to-date: /usr/local/lib/librealsense.so.1
-- Up-to-date: /usr/local/lib/librealsense.so
-- Up-to-date: /usr/local/include/librealsense
-- Installing: /usr/local/include/librealsense/rs.h
-- Installing: /usr/local/include/librealsense/rs.hpp
-- Installing: /usr/local/include/librealsense/rsutil.h
-- Installing: /usr/local/include/librealsense/rscore.hpp
-- Installing: /usr/local/bin/c-tutorial-1-depth
-- Set runtime path of "/usr/local/bin/c-tutorial-1-depth" to ""
-- Installing: /usr/local/bin/c-tutorial-2-streams
-- Set runtime path of "/usr/local/bin/c-tutorial-2-streams" to ""
-- Installing: /usr/local/bin/c-tutorial-3-pointcloud
-- Set runtime path of "/usr/local/bin/c-tutorial-3-pointcloud" to ""
-- Installing: /usr/local/bin/cpp-tutorial-1-depth
-- Set runtime path of "/usr/local/bin/cpp-tutorial-1-depth" to ""
-- Installing: /usr/local/bin/cpp-tutorial-2-streams
-- Set runtime path of "/usr/local/bin/cpp-tutorial-2-streams" to ""
-- Installing: /usr/local/bin/cpp-tutorial-3-pointcloud
-- Set runtime path of "/usr/local/bin/cpp-tutorial-3-pointcloud" to ""
-- Installing: /usr/local/bin/cpp-alignimages
-- Set runtime path of "/usr/local/bin/cpp-alignimages" to ""
-- Installing: /usr/local/bin/cpp-callback
-- Set runtime path of "/usr/local/bin/cpp-callback" to ""
-- Installing: /usr/local/bin/cpp-callback-2
-- Set runtime path of "/usr/local/bin/cpp-callback-2" to ""
-- Installing: /usr/local/bin/cpp-capture
-- Set runtime path of "/usr/local/bin/cpp-capture" to ""
-- Installing: /usr/local/bin/cpp-config-ui
-- Set runtime path of "/usr/local/bin/cpp-config-ui" to ""
-- Installing: /usr/local/bin/cpp-enumerate-devices
-- Set runtime path of "/usr/local/bin/cpp-enumerate-devices" to ""
-- Installing: /usr/local/bin/cpp-headless
-- Set runtime path of "/usr/local/bin/cpp-headless" to ""
-- Installing: /usr/local/bin/cpp-motion-module
-- Set runtime path of "/usr/local/bin/cpp-motion-module" to ""
-- Installing: /usr/local/bin/cpp-multicam
-- Set runtime path of "/usr/local/bin/cpp-multicam" to ""
-- Installing: /usr/local/bin/cpp-pointcloud
-- Set runtime path of "/usr/local/bin/cpp-pointcloud" to ""
-- Installing: /usr/local/bin/cpp-restart
-- Set runtime path of "/usr/local/bin/cpp-restart" to ""
-- Installing: /usr/local/bin/cpp-stride
-- Set runtime path of "/usr/local/bin/cpp-stride" to ""`
My dmesg when I plug the camera:
[ 4665.177906] usb 1-3.1: new high-speed USB device number 5 using xhci-tegra
[ 4665.201105] usb 1-3.1: New USB device found, idVendor=05e3, idProduct=0610
[ 4665.208011] usb 1-3.1: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[ 4665.215614] usb 1-3.1: Product: USB2.0 Hub
[ 4665.219795] usb 1-3.1: Manufacturer: GenesysLogic
[ 4665.226986] hub 1-3.1:1.0: USB hub found
[ 4665.233103] hub 1-3.1:1.0: 2 ports detected
[ 4666.442082] usb 1-3.1.2: new full-speed USB device number 6 using xhci-tegra
[ 4666.563638] usb 1-3.1.2: config 1 has an invalid interface number: 3 but max is 2
[ 4666.571578] usb 1-3.1.2: config 1 has no interface number 2
[ 4666.652361] usb 1-3.1.2: New USB device found, idVendor=041e, idProduct=409b
[ 4666.659676] usb 1-3.1.2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 4666.668871] usb 1-3.1.2: Product: BlasterX Senz3D VF0810
[ 4666.674961] usb 1-3.1.2: Manufacturer: Creative Technology Ltd
[ 4666.681494] usb 1-3.1.2: SerialNumber:<PHONE_NUMBER>25
[ 4666.789400] input: Creative Technology Ltd BlasterX Senz3D VF0810 as /devices/70090000.xusb/usb1/1-3/1-3.1/1-3.1.2/1-3.1.2:1.3/0003:041E:409B.0003/input/input5
[ 4666.874843] hid-generic 0003:041E:409B.0003: input,hiddev0,hidraw2: USB HID v1.11 Device [Creative Technology Ltd BlasterX Senz3D VF0810] on usb-70090000.xusb-3.1.2/input3
uvcvideo module is not on the file /etc/modules-load.d/modules.conf
Thanks for any help

It appears as if you are using a USB 2.0 hub. The RealSense requires USB 3.0 or else uvcvideo does not recognize if.

Thank you to answer so fast, that was the mistake, it works like a charm.


Unable to install Doppler on Amazon Linux 2023 image

How did you install the Amplify CLI?
na
If applicable, what version of Node.js are you using?
18
Amplify CLI Version
latest
What operating system are you using?
Mac
Did you make any manual changes to the cloud resources managed by Amplify? Please describe the changes made.
None
Describe the bug
This is my amplify.yml:
version: 1
frontend:
  phases:
    preBuild:
      commands:
        - curl -Ls https://cli.doppler.com/install.sh | sh && doppler setup --no-interactive
        - doppler run -- npm ci
    build:
      commands:
        - doppler run -- npm run build
  artifacts:
    baseDirectory: .next
    files:
      - '**/*'
  cache:
    paths:
      - node_modules/**/*

Error message is:
# Starting phase: preBuild
2023-11-22T05:20:54.641Z [INFO]: # Executing command: curl -Ls https://cli.doppler.com/install.sh | sh && doppler setup --no-interactive
2023-11-22T05:20:55.048Z [WARNING]: Downloading Doppler CLI
2023-11-22T05:20:57.374Z [WARNING]: Verifying signature
2023-11-22T05:20:57.810Z [WARNING]: Installing...
2023-11-22T05:20:59.693Z [WARNING]: error: can't create transaction lock on /var/lib/rpm/.rpm.lock (Permission denied)
2023-11-22T05:20:59.695Z [WARNING]: ERROR: script failed during execution

Expected behavior
This script USED to work on Amazon Linux 2.
Reproduction steps
Just set up doppler to run as per the yml file.
Project Identifier
dndoxjh0wdkex
Log output

                                 # Starting phase: preBuild
2023-11-22T05:20:54.641Z [INFO]: # Executing command: curl -Ls https://cli.doppler.com/install.sh | sh && doppler setup --no-interactive
2023-11-22T05:20:55.048Z [WARNING]: Downloading Doppler CLI
2023-11-22T05:20:57.374Z [WARNING]: Verifying signature
2023-11-22T05:20:57.810Z [WARNING]: Installing...
2023-11-22T05:20:59.693Z [WARNING]: error: can't create transaction lock on /var/lib/rpm/.rpm.lock (Permission denied)
2023-11-22T05:20:59.695Z [WARNING]: ERROR: script failed during execution

Additional information
I tried doing sudo su but the Build step hangs and refuses to go further. This is also an anti-pattern and we should not need to manually drop into super privileges just to install Doppler.
Before submitting, please confirm:

[X] I have done my best to include a minimal, self-contained set of instructions for consistently reproducing the issue.
[X] I have removed any sensitive information from my code snippets and submission.

Hey @isaacrowntree, 👋 thanks for raising this! I'm going to transfer this over to our hosting repository for better assistance 🙂.


⚠ Bofrost.be has degraded performance

In b748df6, Bofrost.be (https://www.bofrost.be) experienced degraded performance:

HTTP code: 200
Response time: 1667 ms

Resolved: Bofrost.be performance has improved in dcba07a after 6 minutes.


Fix clippy warnings

First of all, sorry for the huge pull request without a warning upfront. It's just that this looked like a small cleanup at first which kept me busy for a while and before you know, it becomes this monstrosity...
I added two commits. The first basically runs the following commands:
cargo fix --all
cargo fix -Z unstable-options --clippy --allow-dirty  --allow-staged --all

Which comes down to the automated fixing which can be done by clippy/rust lints.
Next, I added some #[allow(...)] attributes to big functions and places where clippy went a bit too wild. I didn't know clippy can even change Vec<Box> to Vec for all references of a type.
For the second commit, I just added a bunch of manual steps to further satisfy clippy (which works like a charm using rust-analyzer).
Most changes are purely syntactical, but some changes were applied to improve performance:

Change pass-by-reference for simple enums to pass-by-value where possible.
Wrap JSXElement in a box in Expr, because it was increasing Expr's size too much.

Also note that there are still clippy warnings remaining, but they seem like minor nit's and not worth the effort. At least these can now be fixed case-by-case in the future.
As for the size of this PR - sorry again 😄, I can understand if this is not mergeable in its current form. It does look like it's worth the effort to increase the maintainability of the repo from my point of view.

I did an extra effort to upgrade the crates to 2018 edition which were still on 2015. This required some path changes for the macros, but I got the tests working again.

I merged it. Thank you very much!!


dist_async slower than dist_sync

Hi, I tested the speed of multi-machine training with the following command:
../../tools/launch.py -n 2 -H hosts python train_imagenet.py --data-dir /mnt/ficushaiti/zzhang/data/mxnet/imagenet/rec/ --gpus 0,1,2,3,4,5 --batch-size 960 --kv-store dist_(a)sync

And I found that with "dist_sync", the total speed is 1070 samples/s, but with "dist_async" the speed is 860 samples/s.
Then I tried to fix the problem. I changed the code in src/kvstore/kvstore_dist_server.h from
      } else {
        // async push
        exec_.Exec([this, key, &recved, &stored](){
            CHECK(updater_);
            updater_(key, recved, &stored);
          });
        server->Response(req_meta);
        stored.WaitToRead();
      }
    } else {
      // pull

to
        } else {
          NDArray temp_data = recved.Copy(Context());
          // async push
          exec_.Exec([this, key, temp_data, &stored](){
              CHECK(updater_);
              updater_(key, temp_data, &stored);
            });
          server->Response(req_meta);
          stored.WaitToRead();
        }
      } else {
        // pull

then the problem was solved ( 'dist_async' gets the same speed as 'dist_sync' ).
So I wonder
(1) why is 'dist_async' slower than 'dist_sync'?
(2) Is my change right?
The environment:
2 Server with Ubuntu 12.04, each with 6 TitanX
Network is 1Gbps

Could you propose your change as a PR and we'll review it.
Thanks.
@mli

i think your codes are right if Copy do the actually memory copy, rather than just pass the pointer.
the reason might due to the updater's overhead is not small. in sync_dist, there is only one update for each layer in a minibatch, while for async, there are 12 updates. copying recved decouples the updating on the same key and therefore improve the performance.
however, your method might only improve the performance if that layer size is small, e.g. convolution layer. while for big layers such as fully connected, the extra memory copy might be pretty big.
a possible solution is, copy only if the recved size is < bigarray_bound_, which is defined at https://github.com/dmlc/mxnet/blob/master/src/kvstore/kvstore_local.h#L28
could you please do the following two things

confirm that .Copy will do the actual memory copy
propose a PR to enable your trick if recved.size < bigarray_bound_

thanks


Add Traditional Chinese Translation

Fixes #9667

Thanks @meowmeowmeowcat! Looks like you have a linting error here.

I have already fixed the linting error :)


ZBCurtain Unsupported Message into LOGS

What issue do you have? Please be as thorough and explicit as possible.
Logs shows unsupported message and got instructions to fill this to an issue request.
Details of your setup.

Do you use (1) Homebridge UI-X (2) Homebridge CLI or (3) HOOBS?

Homebridge in a Raspberry Pi 4

Which version of Homebridge/HOOBS do you have?
v1.6.1

Which platform do you run Homebridge/HOOBS on (e.g. Raspberry Pi/Windows/HOOBS Box)? Please also mention your version of Node.js/NPM if known.

Raspeberry Pi 4
-node: v18.17.1

Which version of this plugin (homebridge-ewelink) do you have? Has the issue started since upgrading from a previous version?
v11.02

Which eWeLink devices do you have that are causing issues? Please include product models if applicable.

Sonoff ZBCurtain.
Please paste any relevant logs below.
[ZBCurtain] is not supported, do create a GitHub issue with the following info:
[7006] {"bindInfos":{},"subDevId":"3de0de29004b12007006","parentid":"1001dc7574","fwVersion":"2.0.7","battery":72,"trigTime":"1693702276000","supportPowConfig":1,"curPercent":100,"motorDir":"reverse","motorClb":"normal","curtainAction":"close","openPercent":100}.
-->

Hi @ivansardo
Please update to the beta version of the plugin
https://github.com/bwp91/homebridge-ewelink/wiki/Beta-Version
Let me know if this device works well or not, as I have based the commands on a different motor model.

hi ,
Thanks for your help... this is what happened after update to the beta version:
"it works and HomeKit showed properly, I tried to open and close the curtain and it works... just it showing as opened when its already closed and vice versa".

Also, I got the Curtain offline suddenly and I need to restart home bridge.

Hi @ivansardo
Thanks for the feedback, please can you try 11.0.3-beta.1?

Hello Ben,
I really appreciate your time and help, it seems to be working properly. I justo found out there is a discrepancies between information within Ewelink App and HomeKit.
When I have open the curtan it shows closed into Homekit but in the eWelink app its show open, maybe it is because the change of the motor, which in my case it is inverted and the plugin is reading another status?
Thank a lot in advance.

Hi, me again… for any reason we still having issues, also in HomeKit always says opening.. and for any reason there is no response anymore around 2-3 days after, I need to restart homebridge

Hi!
Downloaded the beta plugin - Installed: v12.1.1-beta.4
ZBCurtain is visible in the app and totally controllable. but says "No Response" which then means automations do not work.
what can i provide to assist?


installing keras and tensorflow

Hi, thanks for such a great project. But, while running the ultasound classification notebook, keras is needed. But, after installing keras. It throws this error:

Even after searching through the support forums, I could not install tensorflow.
I am using pynq-z2.
Please help me. How did you install all these libraries? or can you share the keras+ tensorflow installed pynq z2 image if possible.
Really awaiting your reply.
Thanks

You can use the terminal of the pynq-z2 board to install all packages via pip in python. Also, you should first connect the pynq-z2 board to the Internet through a network cable.

Hi,
I tried that but not able to install tensorflow so cannot proceed further.

Moreover, pynq support forum says that pynq-z2 does not support tensorflow:

How did you do that?
Please help me .. what am I missing? It is very important for me.
Please can you share your email id

You can try to change the backend of keras from tensorflow to theano in the Keras configuration file. You can find it at this location: $HOME/.keras/keras.json. The installation of theano is supported by pynq-z2.
The modified configuration file is as follows:.
{
"image_data_format": "channels_last",
"epsilon": 1e-07,
"floatx": "float32",
"backend": "theano"
}
Hope this helps.

You can try to change the backend of keras from tensorflow to theano in the Keras configuration file. You can find it at this location: $HOME/.keras/keras.json. The installation of theano is supported by pynq-z2.
The modified configuration file is as follows:. { "image_data_format": "channels_last", "epsilon": 1e-07, "floatx": "float32", "backend": "theano" }
Hope this helps.

Thanks, following your instructions and changing Keras version to 2.2.4 solved the issue.
But, now following error is there:

Changing index to 0 in [x_test, y_test] = val_generator[] gives following output which seems OK.

Can you confirm, if this is because you uploaded fewer test images and is not an issue for further execution?

Yes, you're right.

You can try to change the backend of keras from tensorflow to theano in the Keras configuration file. You can find it at this location: $HOME/.keras/keras.json. The installation of theano is supported by pynq-z2.
The modified configuration file is as follows:. { "image_data_format": "channels_last", "epsilon": 1e-07, "floatx": "float32", "backend": "theano" }
Hope this helps.

Hi @ZhaoqxCN
I have tried to install keras but there was keras.json file to edit the code. can you please help me to solve this ?

You can try to change the backend of keras from tensorflow to theano in the Keras configuration file. You can find it at this location: $HOME/.keras/keras.json. The installation of theano is supported by pynq-z2.
The modified configuration file is as follows:. { "image_data_format": "channels_last", "epsilon": 1e-07, "floatx": "float32", "backend": "theano" }
Hope this helps.

Thanks, following your instructions and changing Keras version to 2.2.4 solved the issue.
But, now following error is there:
Changing index to 0 in [x_test, y_test] = val_generator[] gives following output which seems OK.

Can you confirm, if this is because you uploaded fewer test images and is not an issue for further execution?

Hi @shobhitt10
I am also facing same issues. did you solve it ? can you please share your email? that would be nice

Hi @ZhaoqxCN
if possible can you please share the detailed information about keras installation on PYNQ.
Thanks

You can try to change the backend of keras from tensorflow to theano in the Keras configuration file. You can find it at this location: $HOME/.keras/keras.json. The installation of theano is supported by pynq-z2.
The modified configuration file is as follows:. { "image_data_format": "channels_last", "epsilon": 1e-07, "floatx": "float32", "backend": "theano" }
Hope this helps.

Hi @ZhaoqxCN
I have tried to install keras but there was no keras.json file to edit the code. can you please help me to solve this ?

Maybe you can find this file after running it once.

Hi,
Thank you for providing the good resources on github. Currently, I am using
your HLS and Python code for implementing deep-learning algorithms on an
FPGA.
Can you explain to me how you calculated the out_buffer?
Actually, the batch_size has a value in the HLS. Why did you mention
it again?
"out_buffer = Xlnk(). cma_array(shape=(8 + output_chbatch_sizeoutput_dim*
output_dim), dtype=np.int16)"
I am trying to replicate your design according to my algorithm, and when I
load my data, it keeps running without showing any result. If you can
explain it to me, then I can finish my project. Your suggestions will be
really helpful to me.
[image: image.png]
Best Regards,
Nagendra
On Mon, 18 Apr 2022 at 20:35, ZhaoqxCN @.***> wrote:

Reopened #5 https://github.com/ZhaoqxCN/PYNQ-CNN-ATTEMPT/issues/5.
—
Reply to this email directly, view it on GitHub
https://github.com/ZhaoqxCN/PYNQ-CNN-ATTEMPT/issues/5#event-6447735249,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AMGG2PEBMNDU6H3TFRNIEOTVFVJHPANCNFSM5NQ5ZU2Q
.
You are receiving this because you commented.Message ID:
@.***>


refactor: use Deno.Command instead of Deno.run

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.


Traefik (1.6.5 and 1.7.1) stops watching file after it detects Marathon is down

Do you want to request a feature or report a bug?
Bug
What did you do?
I'm trying to use the file.watch feature. The idea is to be able to reload SSL certificates without restaring traefik.
I have the TLS config on a separated file, and here is my main config file (the part that matters):
[file]
watch = true
fileName = "/etc/ssl.toml"

I have two copies of "/etc/ssl.toml", each one with a different certificate, like this:
ssl1.toml:
[[tls]]
  entryPoints = ["https"]
  [tls.certificate]
      certFile = "/etc/cert1/fullchain.pem"
      keyFile = "/etc/cert1/privkey.pem"

and ssl2.toml:
[[tls]]
  entryPoints = ["https"]
  [tls.certificate]
      certFile = "/etc/cert2/fullchain.pem"
      keyFile = "/etc/cert2/privkey.pem"

And then what I do is just a simple cp, like this:
cd /etc
cp ssl2.toml ssl.toml
cp ssl1.toml ssl.toml

And check the certificates were reloaded with a simple curl to localhost.
What did you expect to see?
I expected to see traefik change the certificates every time I did the cp.
What did you see instead?
Traefik changes the certificates correctly, until this message appears in the debug log:
ERRO[2018-10-03T09:45:23-03:00] Failed to retrieve Marathon applications: all the Marathon hosts are presently down

As soon as this message appears, traefik does not detect the file change anymore and then the certificates stop being reloaded.
Output of traefik version: (What version of Traefik are you using?)
Version:      v1.6.5
Codename:     tetedemoine
Go version:   go1.10.3
Built:        2018-07-10_03:54:03PM
OS/Arch:      linux/amd64

The version here is 1.6.5 but this same behavior happens with 1.7.1.
What is your environment & configuration (arguments, toml, provider, platform, ...)?
{
 "LifeCycle": {
  "RequestAcceptGraceTimeout": 0,
  "GraceTimeOut": 0
 },
 "GraceTimeOut": 0,
 "Debug": false,
 "CheckNewVersion": true,
 "SendAnonymousUsage": false,
 "AccessLogsFile": "",
 "AccessLog": null,
 "TraefikLogsFile": "",
 "TraefikLog": null,
 "Tracing": null,
 "LogLevel": "",
 "EntryPoints": {},
 "Cluster": null,
 "Constraints": [],
 "ACME": null,
 "DefaultEntryPoints": [
  "http"
 ],
 "ProvidersThrottleDuration":<PHONE_NUMBER>,
 "MaxIdleConnsPerHost": 200,
 "IdleTimeout": 0,
 "InsecureSkipVerify": false,
 "RootCAs": null,
 "Retry": null,
 "HealthCheck": {
  "Interval":<PHONE_NUMBER>0
 },
 "RespondingTimeouts": null,
 "ForwardingTimeouts": null,
 "AllowMinWeightZero": false,
 "Web": null,
 "Docker": null,
 "File": null,
 "Marathon": null,
 "Consul": null,
 "ConsulCatalog": null,
 "Etcd": null,
 "Zookeeper": null,
 "Boltdb": null,
 "Kubernetes": null,
 "Mesos": null,
 "Eureka": null,
 "ECS": null,
 "Rancher": null,
 "DynamoDB": null,
 "ServiceFabric": null,
 "Rest": null,
 "API": null,
 "Metrics": null,
 "Ping": null,
 "ConfigFile": ""
}

If applicable, please paste the log output at DEBUG level (--logLevel=DEBUG switch)
INFO[2018-10-03T09:55:35-03:00] Starting provider *file.Provider {"Watch":true,"Filename":"/etc/ssl.toml","Constraints":null,"Trace":false,"TemplateVersion":0,"DebugLogGeneratedTemplate":fal
se,"Directory":"","TraefikFile":"/home/daltonmatos/sievegroup/sieve/docker-traefik/config.toml"}
WARN[2018-10-03T09:55:35-03:00] clientTLS is nil
DEBU[2018-10-03T09:55:35-03:00] Configuration received from provider file: {"tls":[{"EntryPoints":["https"],"Certificate":{"CertFile":"/etc/cert1/fullchain.pem","KeyFile":"/etc/cert1/privkey.pem"}}]}
DEBU[2018-10-03T09:55:35-03:00] Add certificate for domains *.<redacted>.com.br
INFO[2018-10-03T09:55:35-03:00] Server configuration reloaded on :8082
INFO[2018-10-03T09:55:35-03:00] Server configuration reloaded on :80
INFO[2018-10-03T09:55:35-03:00] Server configuration reloaded on :443
DEBU[2018-10-03T09:55:50-03:00] Configuration received from provider file: {"tls":[{"EntryPoints":["https"],"Certificate":{"CertFile":"/etc/cert2/fullchain.pem","KeyFile":"/etc/cert2/privkey.pem"}}]}
DEBU[2018-10-03T09:55:50-03:00] Add certificate for domains *.<redacted>.com.br
INFO[2018-10-03T09:55:50-03:00] Server configuration reloaded on :80
INFO[2018-10-03T09:55:50-03:00] Server configuration reloaded on :443
INFO[2018-10-03T09:55:50-03:00] Server configuration reloaded on :8082
DEBU[2018-10-03T09:55:54-03:00] Configuration received from provider file: {"tls":[{"EntryPoints":["https"],"Certificate":{"CertFile":"/etc/cert1/fullchain.pem","KeyFile":"/etc/cert1/privkey.pem"}}]}
DEBU[2018-10-03T09:55:56-03:00] Add certificate for domains *.<redacted>.com.br
INFO[2018-10-03T09:55:56-03:00] Server configuration reloaded on :80
INFO[2018-10-03T09:55:56-03:00] Server configuration reloaded on :443
INFO[2018-10-03T09:55:56-03:00] Server configuration reloaded on :8082
ERRO[2018-10-03T09:57:35-03:00] Failed to retrieve Marathon applications: all the Marathon hosts are presently down

For now on, even changing the contents of /etc/ssl.toml, traefik does not detect this change and does not reload the certificates.
Important Note: I was only able to reproduce this when I started Traefik with Marathon Turned off. When I started traefik with Matathon already started, all works. Even when I remove every app from Marathon and then stop it. but if I later start marathon, Traefik does not start to detect the file changes, although it receives new updates from Marathon:
ERRO[2018-10-03T10:19:02-03:00] Failed to retrieve Marathon applications: all the Marathon hosts are presently down
DEBU[2018-10-03T10:19:45-03:00] Received provider event type: deployment_info, event: &{deployment_info %!s(*marathon.StepActions=&{[{ScaleApplication  /sleep}]}) 2018-10-03T13:19:45.729Z %!s(*marathon.DeploymentPlan=&{8ebc3a31-cf6c-4c71-8a1e-b081de2af445 2018-10-03T13:19:45.599Z 0xc4200205a0 0xc420020600 [0xc4204e6120]})}
DEBU[2018-10-03T10:19:45-03:00] originLabelsmap[]
DEBU[2018-10-03T10:19:45-03:00] allLabelsmap[:map[]]
DEBU[2018-10-03T10:19:45-03:00] originLabelsmap[]
DEBU[2018-10-03T10:19:45-03:00] allLabelsmap[:map[]]

Let me see if you need any new information and I will provide it.

Hi @daltonmatos,
could you provide us your complete logs? They seem truncated.

Here is the raw log, just copied from the terminal.
All I changed was to redact the domain name.
sudo ./traefi-1.6.5 -c config.toml
INFO[2018-10-03T12:32:47-03:00] Using TOML configuration file /home/daltonmatos/sievegroup/sieve/docker-traefik/config.toml
INFO[2018-10-03T12:32:47-03:00] Traefik version v1.6.5 built on 2018-07-10_03:54:03PM
INFO[2018-10-03T12:32:47-03:00]
Stats collection is disabled.
Help us improve Traefik by turning this feature on :)
More details on: https://docs.traefik.io/basics/#collected-data

DEBU[2018-10-03T12:32:47-03:00] Global configuration loaded {"LifeCycle":{"RequestAcceptGraceTimeout":0,"GraceTimeOut":10000000000},"GraceTimeOut":0,"Debug":false,"CheckNewVersion":true,"SendAnonymousUsage":false,"AccessLogsFile":"","AccessLog":null,"TraefikLogsFile":"","TraefikLog":null,"Tracing":null,"LogLevel":"debug","EntryPoints":{"http":{"Address":":80","TLS":null,"Redirect":null,"Auth":null,"WhitelistSourceRange":null,"WhiteList":null,"Compress":false,"ProxyProtocol":null,"ForwardedHeaders":{"Insecure":true,"TrustedIPs":null}},"https":{"Address":":443","TLS":{"MinVersion":"","CipherSuites":null,"Certificates":null,"ClientCAFiles":null,"ClientCA":{"Files":null,"Optional":false}},"Redirect":null,"Auth":null,"WhitelistSourceRange":null,"WhiteList":null,"Compress":false,"ProxyProtocol":null,"ForwardedHeaders":{"Insecure":true,"TrustedIPs":null}},"traefik":{"Address":":8082","TLS":null,"Redirect":null,"Auth":null,"WhitelistSourceRange":null,"WhiteList":null,"Compress":false,"ProxyProtocol":null,"ForwardedHeaders":{"Insecure":true,"TrustedIPs":null}}},"Cluster":null,"Constraints":[],"ACME":null,"DefaultEntryPoints":["http"],"ProvidersThrottleDuration":2000000000,"MaxIdleConnsPerHost":10000,"IdleTimeout":0,"InsecureSkipVerify":false,"RootCAs":null,"Retry":null,"HealthCheck":{"Interval":30000000000},"RespondingTimeouts":null,"ForwardingTimeouts":null,"AllowMinWeightZero":false,"Web":null,"Docker":null,"File":{"Watch":true,"Filename":"/etc/ssl.toml","Constraints":null,"Trace":false,"TemplateVersion":0,"DebugLogGeneratedTemplate":false,"Directory":"","TraefikFile":"/home/daltonmatos/sievegroup/sieve/docker-traefik/config.toml"},"Marathon":{"Watch":true,"Filename":"","Constraints":[],"Trace":false,"TemplateVersion":2,"DebugLogGeneratedTemplate":false,"Endpoint":"http://<IP_ADDRESS>:8080","Domain":"marathon","ExposedByDefault":true,"GroupsAsSubDomains":true,"DCOSToken":"","MarathonLBCompatibility":false,"FilterMarathonConstraints":false,"TLS":null,"DialerTimeout":60000000000,"KeepAlive":10000000000,"ForceTaskHostname":false,"Basic":null,"RespectReadinessChecks":false},"Consul":null,"ConsulCatalog":null,"Etcd":null,"Zookeeper":null,"Boltdb":null,"Kubernetes":null,"Mesos":null,"Eureka":null,"ECS":null,"Rancher":null,"DynamoDB":null,"ServiceFabric":null,"Rest":null,"API":{"EntryPoint":"traefik","Dashboard":true,"Debug":false,"CurrentConfigurations":null,"Statistics":null},"Metrics":{"Prometheus":{"Buckets":[0.1,0.3,1.2,5],"EntryPoint":"traefik"},"Datadog":null,"StatsD":null,"InfluxDB":null},"Ping":null}
DEBU[2018-10-03T12:32:47-03:00] Configured Prometheus metrics
INFO[2018-10-03T12:32:47-03:00] Preparing server https &{Address::443 TLS:0xc4204e4080 Redirect:<nil> Auth:<nil> WhitelistSourceRange:[] WhiteList:<nil> Compress:false ProxyProtocol:<nil> ForwardedHeaders:0xc4200356c0} with readTimeout=0s writeTimeout=0s idleTimeout=3m0s
INFO[2018-10-03T12:32:47-03:00] Preparing server traefik &{Address::8082 TLS:<nil> Redirect:<nil> Auth:<nil> WhitelistSourceRange:[] WhiteList:<nil> Compress:false ProxyProtocol:<nil> ForwardedHeaders:0xc420035700} with readTimeout=0s writeTimeout=0s idleTimeout=3m0s
INFO[2018-10-03T12:32:47-03:00] Starting server on :443
INFO[2018-10-03T12:32:47-03:00] Preparing server http &{Address::80 TLS:<nil> Redirect:<nil> Auth:<nil> WhitelistSourceRange:[] WhiteList:<nil> Compress:false ProxyProtocol:<nil> ForwardedHeaders:0xc420035680} with readTimeout=0s writeTimeout=0s idleTimeout=3m0s
INFO[2018-10-03T12:32:47-03:00] Starting server on :80
INFO[2018-10-03T12:32:47-03:00] Starting provider configuration.providerAggregator {}
INFO[2018-10-03T12:32:47-03:00] Starting server on :8082
INFO[2018-10-03T12:32:47-03:00] Starting provider *marathon.Provider {"Watch":true,"Filename":"","Constraints":[],"Trace":false,"TemplateVersion":2,"DebugLogGeneratedTemplate":false,"Endpoint":"http://<IP_ADDRESS>:8080","Domain":"marathon","ExposedByDefault":true,"GroupsAsSubDomains":true,"DCOSToken":"","MarathonLBCompatibility":false,"FilterMarathonConstraints":false,"TLS":null,"DialerTimeout":60000000000,"KeepAlive":10000000000,"ForceTaskHostname":false,"Basic":null,"RespectReadinessChecks":false}
INFO[2018-10-03T12:32:47-03:00] Starting provider *file.Provider {"Watch":true,"Filename":"/etc/ssl.toml","Constraints":null,"Trace":false,"TemplateVersion":0,"DebugLogGeneratedTemplate":false,"Directory":"","TraefikFile":"/home/daltonmatos/sievegroup/sieve/docker-traefik/config.toml"}
WARN[2018-10-03T12:32:47-03:00] clientTLS is nil
DEBU[2018-10-03T12:32:47-03:00] Configuration received from provider file: {"tls":[{"EntryPoints":["https"],"Certificate":{"CertFile":"/etc/letsencrypt-second-cert-2018-10-02/live/<redacted>/fullchain.pem","KeyFile":"/etc/letsencrypt-second-cert-2018-10-02/live/<redacted>/privkey.pem"}}]}
DEBU[2018-10-03T12:32:47-03:00] Add certificate for domains *.<redacted>.com.br
INFO[2018-10-03T12:32:47-03:00] Server configuration reloaded on :8082
INFO[2018-10-03T12:32:47-03:00] Server configuration reloaded on :80
INFO[2018-10-03T12:32:47-03:00] Server configuration reloaded on :443
DEBU[2018-10-03T12:32:49-03:00] Configuration received from provider file: {"tls":[{"EntryPoints":["https"],"Certificate":{"CertFile":"/etc/letsencrypt-first-cert-2018-10-01/live/<redacted>/fullchain.pem","KeyFile":"/etc/letsencrypt-first-cert-2018-10-01/live/<redacted>/privkey.pem"}}]}
DEBU[2018-10-03T12:32:49-03:00] Configuration received from provider file: {"tls":[{"EntryPoints":["https"],"Certificate":{"CertFile":"/etc/letsencrypt-first-cert-2018-10-01/live/<redacted>/fullchain.pem","KeyFile":"/etc/letsencrypt-first-cert-2018-10-01/live/<redacted>/privkey.pem"}}]}
DEBU[2018-10-03T12:32:49-03:00] Add certificate for domains *.<redacted>.com.br
INFO[2018-10-03T12:32:49-03:00] Server configuration reloaded on :443
INFO[2018-10-03T12:32:49-03:00] Server configuration reloaded on :8082
INFO[2018-10-03T12:32:49-03:00] Server configuration reloaded on :80
ERRO[2018-10-03T12:32:50-03:00] Failed to retrieve Marathon applications: all the Marathon hosts are presently down

Every cp I did after this (to change the contents of /etc/ssl.toml) didn't trigger the reload.

@daltonmatos could you provide the full content (redacted) of your config.toml file?

Hello @ldez,
Here is the config:
MaxIdleConnsPerHost = 10000
logLevel = "debug"

[lifeCycle]
graceTimeOut = 10

defaultEntryPoints = ["http"]
[entryPoints]
  [entryPoints.http]
  address = ":80"

  [entryPoints.https]
  address = ":443"
  [entryPoints.https.tls]

  [entryPoints.traefik]
  address = ":8082"

[file]
watch = true
fileName = "/etc/ssl.toml"

[api]
  dashboard = true

[metrics]
  [metrics.prometheus]
    entrypoint = "traefik"
    buckets = [0.1,0.3,1.2,5.0]

[marathon]
endpoint = "http://<IP_ADDRESS>:8080"
watch = true
domain = "marathon"
groupsAsSubDomains = true

It's a problem in the logic, I debuged and reproduce the issue. If the first configuration loaded in [1] is nil then the only way to reload the configuration is if the watcher loop in [2] fires by a Marathon change, like a new app been deployed.
The fix might be to add a loop trying to reload the first configuration from time to time if the initial was null and the watch is on.
I'll try make a pr for this change.
[1]
https://github.com/containous/traefik/blob/d3ae88f108f927201fffc310c61cd31cdf5e8ea8/provider/marathon/marathon.go#L153-L157
[2]
https://github.com/containous/traefik/blob/d3ae88f108f927201fffc310c61cd31cdf5e8ea8/provider/marathon/marathon.go#L134-L149

Closed by #4230.


Certificate Bound Access Tokens

Omejdn is occasionally used in a way that allows to bind transport certificates to the issued access tokens. This can be quite useful if access tokens are not to be reused by resource servers and other parties receiving such tokens.
One example usage: IDS-G defines transportCertsSha256
As Omejdn does not support detecting transport certificates (nor requests them), this parameter is usually configured though the attributes of clients or users, and subsequently included in the issued access tokens. This is quite inflexible and requires updates either via the API or manually.
Alternatives:

RFC 8705 provides a direct way to hint at the client's certificate used for TLS in the cnf.x5t#S256 claim of the access token. TLS Client authentication can also be made optional by providing specialized endpoints requiring it.

This is quite elegant but does require direct access to the TLS certificates. This may be done using NginX's features to convey them in a header, but this would possibly restrict the setups which may involve Omejdn.
We could also just do TLS inside Omejdn.

DPoP sends a Proof of Posession as an HTTP Header.

Easier to work with for Omejdn, but does require clients to have access to their keys at an application layer.

This is related to the JWT bearer client authentication. Currently, the clients have certificates configured which are used as public keys for verification of the JWT assertion in the authentication.
Theoretically, we could use the information from those certificates dynamically and include them in the tokens instead of having it statically configured in addition to the public key x509 certificate.
RFC8705 seems to be overkill as we really do not want to implement TLS client authentication. However, using the confirmation claim seems doable as it does not seem to be restricted to the client authentication method as far as I can see.
I don't see how DPoP can be used without opening a whole lot of other issues related to certificate trust validation.

My suggestion:

Strictly only use X.509 PEMs for the configured clients
Always put the X.509 thumbprints in the "cnf" claim as defined in https://www.iana.org/assignments/oauth-parameters/oauth-parameters.xhtml and RFC8705

The transportCertsSha256 is out of scope for omejdn itself. The IDS-G may at some point support cnf claims. Until then, the claim needs to be configured manually.

For those waiting for this issue to be addressed: This is a future enhancement and can automate how clients TLC certs can be mapped to the DAT. We currently also have the possibility to allow clients to insert selected claims via the request token so they can bind their identity to their TLS certificates.
@milux Can you provide details?

@gbrost I can: https://www.ietf.org/archive/id/draft-spencer-oauth-claims-01.txt is mostly implemented in Omejdn as a straightforward extension of OIDCC functionality. To dynamically include attributes in an Access Token (=DAT in the IDS context), one needs to:

Enable the Attribute Claim Mapper Plugin (Necessary for the DAPS anyway, done in omejdn-daps)
Allow the attribute to have dynamically requested values in clients.yml:

  - key: transportCertsSha256
    value: "default value here"
    dynamic: true

request values for the access_token sink according to the draft. Note that a) the claims parameter is not part of the client authentication token ("the request JWT") but a separate parameter (You should be using TLS, so that is not a security issue), and b) Omejdn in its default configuration always picks the first item in a values member. That part is up to the server though, so using the value member instead is recommended.

It may be best to collect any issues targeting the DAPS in particular here.
As for the method described in this issue: The main benefits to be had here are

Less setup for new clients at Omejdn
An implicit Proof of Posession for a client certificate related key by the client.

(Neither of which are of immediate benefit to the IDS ecosystem as far as I am aware)
I agree with @gbrost and @schanzen that this is a future enhancement which would probably require that either Omejdn comes with its own TLS implementation (unlikely) or special configuration of the reverse proxy to communicate the Client TLS certificate to Omejdn, from where it can be added to an access token by a claim_mapper plugin.


After logging out, the signout screen should go away

After logging out, the dropdown menu sticks around. It should go away if no context.accountId

i'll try to fix this


Allow for optional way to change the reference installation folder

https://github.com/appget/appget/blob/5b4c5463d85a7809638d876b07f5501271f32554/src/AppGet/HostSystem/PathResolver.cs#L28
This is a good default, but it would be nice if I could set this to a command line option override to install location.

Sounds pretty reasonable, we have some infra work to do for allowing and managing config settings. once that is done we can make this and a bunch of other things configurable.


Speed up download time with Webpack

I notice that the node_module folder is included in the tag of the publication and need it at run time, but it's very big. I modified to use Webpack to package the project, In my sel-hosted, the Set Up Job step saves 30 seconds. so I recommend using it and remove node_module from tag.

Hey @mayong43111. Thanks for the contribution. I want to understand your approach better. How are you able to accomplish the performance improvement. I could see some regexes are also being used.  Can you help us with that?

Hey @mayong43111. Thanks for the contribution. I want to understand your approach better. How are you able to accomplish the performance improvement. I could see some regexes are also being used. Can you help us with that?

Hi @BALAGA-GAYATRI , thanks for your commented . Webpack can scan 'require' in code and package it into one file. But the esprima.js component uses the ‘readfilesys’  method, which Webpack cannot package. So I modified his code in a regexes way. replace it with something Webpack accepts before packaging. Of course the best way is for him to fix the code, Instead of hacking it's code.

approved


升级到3.4.6后有getCurrentInstance() called inside a computed getter 和toRefs() expects a reactive object but received a plain one两个warning

[ ] I'm sure this does not appear in the issue list of the repository

Basic Info
What are the similar cases of this feature
Vue升级到3.4.6，arco design vue 2.54.1
What problem does this feature solve?
Vue升级到3.4.6有getCurrentInstance() called inside a computed getter 和toRefs() expects a reactive object but received a plain one两个warning

The warning has been reverted in Vue core
discussions
Vue 3.4.6
Vue 3.4.7 revert


istioctl verify-install related issues

This issue is to track istioctl verify-install related problems.
verify-install still fails on the master.
$ ./out/linux_amd64/istioctl verify-install
Error: could not load IstioOperator from cluster:
could not unmarshal: json: cannot unmarshal string into Go value of type map[string]json.RawMessage

[x] https://github.com/istio/istio/issues/26266 : reports 'Checked 0 custom resource definitions'
[x] https://github.com/istio/istio/issues/25830 : fails on parsing error on istio in 1.6.0
[x] https://github.com/istio/istio/issues/26070 : doesn't work with dev builds
[x] https://github.com/istio/istio/issues/25688 : fails on Kubernetes 1.18 fixed on Master by https://github.com/istio/istio/pull/28255 , still a problem on 1.8.x
[x] https://github.com/istio/istio/issues/26265 : Integration test for 'istioctl verify-install'
[ ] https://github.com/istio/istio/issues/25848 : nil pointer error with istioctl verify-install on v1.6.x
[x] https://github.com/istio/istio/issues/18855 : Enhance istioctl verify-install output
[x] https://github.com/istio/istio/issues/26276 : Asset charts/addons/grafana not found
[x] https://github.com/istio/istio/issues/28536 : does not work
[x] https://github.com/istio/istio/issues/29336 : should colorize output
[x] https://github.com/istio/istio/issues/29371 : output for canaried control plane and Istio Operator controller.
[ ] https://github.com/istio/istio/issues/29413 : should it wait for rollout?
[x] https://github.com/istio/istio/issues/29440 : does not work if the Istio is installed with --revision flag
[x] new https://github.com/istio/istio/issues/29607 : confusing message against external istiod data plane

@esnible Looks like we have covered and closed all the issues except https://github.com/istio/istio/issues/29413 one.

@esnible Looks like we have covered and closed all the issues except https://github.com/istio/istio/issues/29413 one.

I get
istio-1.8.3/bin/istioctl verify-install
Error: could not load IstioOperator from cluster: control plane revision "" not found.  Use --filename
after an otherwise successful install of
istio-1.8.3/manifests/charts/base
istio-1.8.3/manifests/charts/istio-control/istio-discovery
istio-1.8.3/manifests/charts/gateways/istio-ingress

istio-1.8.3/bin/istioctl verify-install
Error: could not load IstioOperator from cluster: control plane revision "" not found. Use --filename

@ldemailly thanks for reporting. I think it is fixed by https://github.com/istio/istio/pull/29442. I will cherry-pick it so it will be available in 1.8.4.

There is only one item left.  There is no point on having a tracking issue for one item.  Closing in favor of https://github.com/istio/istio/issues/29413

i'cant understand these problem

i'cant understand these problem

demo.yaml:
apiVersion: install.istio.io/v1alpha1
kind: IstioOperator
spec:
  meshConfig:
    accessLogFile: /dev/stdout
  components:
    egressGateways:
    - name: istio-egressgateway
      enabled: true
      k8s:
        resources:
          requests:
            cpu: 100m
            memory: 100Mi

    ingressGateways:
    - name: istio-ingressgateway
      enabled: true
      k8s:
        resources:
          requests:
            cpu: 100m
            memory: 100Mi
        service:
          ports:
            ## You can add custom gateway ports in user values overrides, but it must include those ports since helm replaces.
            # Note that AWS ELB will by default perform health checks on the first port
            # on this list. Setting this to the health check port will ensure that health
            # checks always work. https://github.com/istio/istio/issues/12503
            - port: 15021
              targetPort: 15021
              name: status-port
            - port: 80
              targetPort: 8080
              name: http2
            - port: 443
              targetPort: 8443
              name: https
            - port: 31400
              targetPort: 31400
              name: tcp
              # This is the port where sni routing happens
            - port: 15443
              targetPort: 15443
              name: tls

    pilot:
      k8s:
        env:
          - name: PILOT_TRACE_SAMPLING
            value: "100"
        resources:
          requests:
            cpu: 100m
            memory: 150Mi

  values:
    global:
      proxy:
        resources:
          requests:
            cpu: 1000m
            memory: 512Mi

    pilot:
      autoscaleEnabled: false

    gateways:
      istio-egressgateway:
        autoscaleEnabled: false
      istio-ingressgateway:
        autoscaleEnabled: false


Anchor generation and headers with HTML

This may well be an edge case, but I’m making an issue anyway.
In my markdown, I sometimes want to customize the output a tad by adding HTML, such as adding an icon in front of a heading; # Heading text.
This works just fine, but the anchor generation is too stupid in this case, as it will generate the following output;
Heading text
. Hardly what I want and certainly not what I expect.
I made a renderer to get around the problem, but would prefer if Marked was smart enough to handle it all by itself. And without jQuery as a dependency, obviously.
renderer.heading = function(text, level)
{
    var stripped = $('
').html(text).text();
    var escaped = stripped.toLowerCase().replace(/[^\w]+/g, '-');
    return '<h' + level + ' id="' + escaped + '">' + text + '</h' + level + '>';
};

#981


ConcurrentModificationException bug

Describe the problem
I'm using single instance of Verifier
private static final Verification verifier = JWT.require(Algorithm.RSA256(getPublicKey("/keys/public.pem"), null));
and I'm getting ConcurrentModificationException from time to time during call verify method
java.util.ConcurrentModificationException at java.base/java.util.ArrayList$Itr.checkForComodification(ArrayList.java:1043) at java.base/java.util.ArrayList$Itr.next(ArrayList.java:997) at java.base/java.util.Collections$UnmodifiableCollection$1.next(Collections.java:1047) at com.auth0.jwt.JWTVerifier.verifyClaims(JWTVerifier.java:473) at com.auth0.jwt.JWTVerifier.verify(JWTVerifier.java:460) at com.auth0.jwt.JWTVerifier.verify(JWTVerifier.java:441
Environment
Version of this library used: java-jwt-4.0.0
Version of Java used: 11
OS: Ubuntu 20.04

Exception doesn't appear with previous lib version (3.19.2)

Hi @ppawlowski15, can you share the code snippet that is throwing this error as well?

`
private static final Verification verifier = JWT.require(Algorithm.RSA256(getPublicKey("/keys/public.pem"), null));
public DecodedJWT verifyToken(String token) {
return verifier.build().verify(token);
}
`
Maybe I should finalize builder of Verifier in first line to get JWTVerifier there once. Anyway the exception shouldn't be thrown, I think

Hi @ppawlowski15 I used your following code to reproduce this issue and tried it even with multiple threads and still not reproducing. Any help in reproducing this would be amazing
    private static final Verification verifier = JWT.require(Algorithm.HMAC256("your-256-bit-secret"));

    public static DecodedJWT verifyToken(String token){
        return verifier.build().verify(token);
    }

    public static void main(String[] args) {
        for (int i = 0; i < 10; i++) {
            new Thread(() -> {
                DecodedJWT a = verifyToken("eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJzdWIiOiIxMjM0NTY3ODkwIiwibmFtZSI6IkpvaG4gRG9lIiwiaWF0IjoxNTE2MjM5MDIyfQ.SflKxwRJSMeKKF2QT4fwpMeJf36POk6yJV_adQssw5c");
                System.out.println(a);
            }).start();
        }
    }

hi,
I encountered a similar problem. I think this is caused by the documentation being unclear about how to use the builder and build methods.
When the build method is called, there is an array of checks that are copied into the new JWTVerifier instance.
public static DecodedJWT verifyToken(String token){
    return verifier.build().verify(token);
}

Then in the new instance, the claims are copied:
        private void addMandatoryClaimChecks() {
            long expiresAtLeeway = getLeewayFor(RegisteredClaims.EXPIRES_AT);
            long notBeforeLeeway = getLeewayFor(RegisteredClaims.NOT_BEFORE);
            long issuedAtLeeway = getLeewayFor(RegisteredClaims.ISSUED_AT);

            expectedChecks.add(constructExpectedCheck(RegisteredClaims.EXPIRES_AT, (claim, decodedJWT) ->
                    assertValidInstantClaim(RegisteredClaims.EXPIRES_AT, claim, expiresAtLeeway, true)));
            expectedChecks.add(constructExpectedCheck(RegisteredClaims.NOT_BEFORE, (claim, decodedJWT) ->
                    assertValidInstantClaim(RegisteredClaims.NOT_BEFORE, claim, notBeforeLeeway, false)));
            if (!ignoreIssuedAt) {
                expectedChecks.add(constructExpectedCheck(RegisteredClaims.ISSUED_AT, (claim, decodedJWT) ->
                        assertValidInstantClaim(RegisteredClaims.ISSUED_AT, claim, issuedAtLeeway, false)));
            }
        }

This line creates new checks that are then added to the array:
           expectedChecks.add(constructExpectedCheck(RegisteredClaims.EXPIRES_AT, (claim, decodedJWT) ->
                    assertValidInstantClaim(RegisteredClaims.EXPIRES_AT, claim, expiresAtLeeway, true)));

Because this is calling expectedChecks.add on the JWTVerifier instance itself, this method is NOT thread-safe. I'm also not sure it's a good idea, because I think this would add the same item repeatedly? But I didn't debug to that point.
To make it safe, a new list should be created that's returned as part of the call and used to create the new instance, or something similar. The list inside the instance cannot be modified once it's created to be thread-safe, or a concurrent version of the list needs to be used
private final List<ExpectedCheckHolder> expectedChecks;

However, the solution is a lot simpler: the build() method should be called only once, to create a single JWTVerifier instance. I believe it can be re-used and is thread-safe once it's built.
In other words, the original bugs code should be more like
private static final JWTVerifer verifier = JWT.require(Algorithm.RSA256(getPublicKey("/keys/public.pem"), null)).build();

public DecodedJWT verifyToken(String token){ return verifier.verify(token); }

and the test instance should be
private static final JWTVerifier verifier = JWT.require(Algorithm.HMAC256("your-256-bit-secret")).build();

public static DecodedJWT verifyToken(String token){
    return verifier.verify(token);
}

This is what I'm using now, and I think it's thread-safe.
I think the test didn't find it because when the verifier tried to verify has to occur at the same time a build is happening, during the list copy portion, while the verified is reading the list. It would probably take more threads and instances to find it.

I think it would be helpful to split out the builder functionality into a separate builder class, which is more the common pattern you find out there. Because they are in the same class, it's not clear on how to use them.
It would also make it clear you can create a final JWTVerifier instance from the builder, and that could be clearly marked as thread-safe and final.

@poovamraj

@poovamraj

Thanks @ppawlowski15 and @kpmueller for the info.
@kpmueller is correct that you should create an instance of JWTVerifier using build() once, then reuse it.
@ppawlowski15 does doing that resolve the issue?
I also agree that the documentation needs to be improved, and if we can pull the builder out to its own class without introducing any breaking changes, we should do that.
Let us know @ppawlowski15 if building the verifier once addresses the problem, and we'll update the documentation and maybe pull out the builder class.
Thanks!

Thanks much! Your library is much appreciated :)

@jimmyjames
Yes, i've updated to 4.0.0 and change my code to build Verifier only once and no more errors spotted ;)

I've updated the documentation in #605. We can't split out the builder to its own class in the 4.x release as it would be a breaking change, but the additional documentation should help provide clarity. Thanks all for raising and providing all the good info! 🙇


A new pull request template for new integrations

I didn't realize that would be an option. Will check it out Monday! Thx

Can we close this?


bug report, incorrect center label

Hi guys,
I'd like to report a bug.
https://github.com/wayveai/fiery/blob/d8aad07bf20c9a284645d7a8208a4bc292a9e8dd/fiery/utils/instance.py#L33
This line here should be

Otherwise, the center label may miss the last one.
before change

after change

Hey Xinchao! Nice find, thanks for reporting the bug, it's now fixed in 746129c5fdb3ae7dd48daa5a9a46c4ab5fc6d6a9 :)


Apply fixes from StyleCI

This pull request applies code style fixes from an analysis carried out by StyleCI.

For more information, click here.

Codecov Report

Merging #2 (113051d) into main (3c6eb1e) will not change coverage.
The diff coverage is 100.00%.

@@             Coverage Diff             @@
##                main        #2   +/-   ##
===========================================
  Coverage     100.00%   100.00%
  Complexity        39        39
===========================================
  Files              2         2
  Lines             91        91
===========================================
  Hits              91        91

Impacted Files
Coverage Δ

src/Html/Attributes.php
100.00% <100.00%> (ø)

Continue to review full report at Codecov.

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


M25917: Possible missing verb

Hello, @ardalis,
Translator has reported possible source content issue.
Please, help to check my comment tag added into the article and reply with explanation if source text should be fixed, or it is by design. If fix is needed, please, let me know either if you would like me to fix it in this PR, or if you will fix it in another PR. In case of using another PR, please, let me know of your PR number, so we can confirm and close this PR.
Many thanks in advance.
Summary
Describe your changes here.
Fixes #Issue_Number (if available)

@ardalis @CESARDELATORRE @rachelappel can you guys with this fix? Not sure what we'd like to say here.
Should we say "that makes it simple to add real-time"?
The sentence does read a bit weird:
"ASP.NET Core SignalR is a library that makes it simple to kind of real-time server-to-client communication functionality to your applications."

@mairaw  "ASP.NET Core SignalR is a library that makes it simple to add real-time server-to-client communication functionality to your applications."

Rachel's update is good. Not sure where "kind of" came from...


gRPC gateway endpoint /cosmos/tx/v1beta1/txs/ is missing

Bug description

The gRPC gateway endpoint for querying tx is missing in morpheus-13001. The legacy API works.
Steps to reproduce

When query with
http://lcd.morpheus.desmos.network:1317/cosmos/tx/v1beta1/txs/6A6EE7B8F79358D1C1ACDA5792A39E439439B39690E23712D38AE29724009D38
returns Not Implemented.
However, the legacy API works
http://lcd.morpheus.desmos.network:1317/txs/6A6EE7B8F79358D1C1ACDA5792A39E439439B39690E23712D38AE29724009D38
Expected behavior

@kwunyeung Is this endpoint present on the Cosmos Hub?

@RiccardoM yes it is


add fields in geocapture tool to match the field guide

add fields from spreadsheet need to get access to this

https://docs.google.com/spreadsheets/d/1l3xf402kL-w9A-i9gkIVAdJu-4XM265_fyE3EhtvPZE/edit#gid=1739995734

As per latest conversation ...
Main category (dropdown)

Tangible Heritage
Intangible Heritage

Tangible Heritage subcategory (checkboxes, allow multiple)

Urban Staircase
Informal/ Publicly Used Space
Heritage Buildings
Vintage Hotels
Vintage Restaurants and cafes
Cinemas/theaters
Art and Culture
Institutions/associations
Vacant structures/plots
Public/open spaces
Transportations Hubs
Market Places/Specialized Markets
Street Names/vintage signs

Intangible Heritage subcategory (dropdown) -- waiting for confirm from Beth, as per Ali on 7/5: this may not be needed in the field, in which case I would recommend removing it from the geo-tool for now

Events
Networks
Informal Associations
Community/civil organization
Power Relations

as per Ali 7/5/2017
I'm not sure how much we'll be using this category in the field/ they are more likely to be defined and analysed in reference to a tangible category

Other information
Coordinates - automatically captured by tool
Name - text field
Address - text field
Block code - text field
Date of Construction/Foundation - text field for year
Architect/Designer - text field
Style - text field
Type - text field
Condition (dropdown: Good, Bad, Ruined)
Target Group - text field
Item Number - remove, use CMS assigned ID

Video of current tool: https://www.dropbox.com/s/d18e3fqz5jgthst/geoTool2.mp4?dl=0


KAFKA-9752; New member timeout can leave group rebalance stuck

Older versions of the JoinGroup rely on a new member timeout to keep the group from growing indefinitely in the case of client disconnects and retrying. The logic for resetting the heartbeat expiration task following completion of the rebalance failed to account for an implicit expectation that shouldKeepAlive would return false the first time it is invoked when a heartbeat expiration is scheduled. This patch fixes the issue by making heartbeat satisfaction logic explicit.
Committer Checklist (excluded from commit message)

[ ] Verify design and implementation
[ ] Verify test coverage and CI build status
[ ] Verify documentation (including upgrade notes)

LGTM!

The build on jdk11 hit this issue: https://issues.apache.org/jira/browse/KAFKA-9470.

retest this please


Allow for combinations of display methods

We really prefer using the Boss Bar display for displaying the block you're looking at, with auto-display on, but it would be nice to be able to use say Crouch to display drops in chat or scoreboard in combination with using the Boss Bar normally.
So being able to define display conditions for a type would be useful, eg; something like the following
  bossbar:
    enabled: true
    condition: normal
    textcolor: WHITE
    barcolor: GREEN

  scoreboard:
    enabled: true
    condition: crouched

Condition could also cover using the right click item to have the display type only used if using the item

This has been implemented in 4b9cc98.
Available in latest dev build https://github.com/steve4744/WhatIsThis/releases/tag/v4.8-SNAPSHOT.18

I gave it all a good test and it seems to work perfectly, as long as you're using the stick.
With auto-display set to true, nothing shows regardless of which type I use or if sneak is enabled for it or not, unless I keep the stick enabled and use it.

That's strange as it works ok for me. The auto-display is triggered by a player move event, so you will need to move slightly for it to display anything. Holding shift and moving the mouse slightly over the targeted block should be enough for it to trigger.

Sorry that was my bad forgetting that a server restart was needed for the move event listener to be registered, it works perfectly after a restart.

No problem, and thanks for the suggestion. I think it adds a nice option to the plugin.


404 error on Mac air laptop

curl -sLk https://raw.githubusercontent.com/kevincobain2000/gobrew/master/git.io.sh | sh
Installing gobrew from: https://github.com/kevincobain2000/gobrew/releases/latest/download/gobrew-darwin-arm64 ...

Installed successfully to: /Users/apple/.gobrew/bin/gobrew
============================

gobrew 1.9.1

Usage:

    gobrew use <version>           Install and set <version>
    gobrew ls                      Alias for list
    gobrew ls-remote               List remote versions (including rc|beta versions)

    gobrew install <version>       Only install <version> (binary from official or GOBREW_REGISTRY env)
    gobrew uninstall <version>     Uninstall <version>
    gobrew list                    List installed versions
    gobrew self-update             Self update this tool
    gobrew prune                   Uninstall all go versions except current version
    gobrew version                 Show gobrew version
    gobrew help                    Show this message

Examples:
    gobrew use 1.16                # use go version 1.16
    gobrew use 1.16.1              # use go version 1.16.1
    gobrew use 1.16rc1             # use go version 1.16rc1

    gobrew use 1.16@latest         # use go version latest of 1.16

    gobrew use 1.16@dev-latest     # use go version latest of 1.16, including rc and beta
                                   # Note: rc and beta become no longer latest upon major release

    gobrew use mod                 # use go version listed in the go.mod file
    gobrew use latest              # use go version latest available
    gobrew use dev-latest          # use go version latest avalable, including rc and beta

Installation Path:

    # Add gobrew to your ~/.bashrc or ~/.zshrc
    export PATH="$HOME/.gobrew/current/bin:$HOME/.gobrew/bin:$PATH"
    export GOROOT="$HOME/.gobrew/current/go"

============================
apple@apples-MacBook-Pro ~ % gobrew use latest
==> [Info] Fetching remote versions

==> [Error] Cannot read response: 404 Not Foundpanic: runtime error: index out of range [-1]

goroutine 1 [running]:
github.com/kevincobain2000/gobrew.(*GoBrew).judgeVersion(0x14000166940?, {0x16f3774bb, 0x6})
	/home/runner/work/gobrew/gobrew/gobrew.go:437 +0x760
github.com/kevincobain2000/gobrew.(*GoBrew).Install(0x14000177e88, {0x16f3774bb?, 0x14000046768?})
	/home/runner/work/gobrew/gobrew/gobrew.go:367 +0x8c
main.main()
	/home/runner/work/gobrew/gobrew/cmd/gobrew/main.go:79 +0xfc
apple@apples-MacBook-Pro ~ % which gobrew
/Users/apple/.gobrew/bin/gobrew
apple@apples-MacBook-Pro ~ % gobrew ls
==> [Info] Nothing installed yet. Run `gobrew use latest` to install a latest version of Go.
apple@apples-MacBook-Pro ~ % gobrew ls-remote
==> [Info] Fetching remote versions

==> [Error] Cannot read response: 404 Not Found%

for now I just went with "brew install go" so I can work.

I think I know what’s happening. Will investigate tomorrow morning. Thanks for reporting.

Everything is fine, I can't reproduce the error. Probably you have an older version of gobrew installed.
╰─$ gobrew version
[INFO] gobrew version is 1.9.1

Mhh weird
I used the curl command in the Readme on a new laptop


Refactor cluster registry to use Secret to store kubeconf

Was PR #4370
This PR refactors cluster registry to use k8s Secret object to store kubeconf files of member clusters.
apiVersion: v1
kind: ConfigMap
metadata:
  name: clusterregistry
  namespace: istio-system
data:
  kube-3.yaml: |-
    apiVersion: clusterregistry.k8s.io/v1alpha1
    kind: Cluster
    metadata:
      name: "kube-3"
      annotations:
        config.istio.io/pilotEndpoint: "<IP_ADDRESS>:9080"
        config.istio.io/platform: "Kubernetes"
        config.istio.io/pilotCfgStore: True
        config.istio.io/accessConfigSecret: "kube-3.conf"   < ---   Name of Secret which stores kube-3 kubeconf config
        config.istio.io/accessConfigSecretNamespace: "istio-system"   < ---   Namespace where secrets will be stored.

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by:
To fully approve this pull request, please assign additional approvers.
We suggest the following additional approver: kyessenov
Assign the PR to them by writing /assign @kyessenov in a comment when ready.
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

pilot/OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@sbezverk: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-unit-tests.sh
76e8ef6d2356a14d5731c47409de8cc22af95e40
link
/test istio-unit-tests

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@sbezverk: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-unit-tests.sh
76e8ef6d2356a14d5731c47409de8cc22af95e40
link
/test istio-unit-tests

prow/e2e-simpleTests.sh
76e8ef6d2356a14d5731c47409de8cc22af95e40
link
/test e2e-simple

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@sbezverk: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-unit-tests.sh
76e8ef6d2356a14d5731c47409de8cc22af95e40
link
/test istio-unit-tests

prow/e2e-simpleTests.sh
76e8ef6d2356a14d5731c47409de8cc22af95e40
link
/test e2e-simple

prow/e2e-bookInfoTests.sh
76e8ef6d2356a14d5731c47409de8cc22af95e40
link
/test e2e-bookInfo

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@sbezverk: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-unit-tests.sh
76e8ef6d2356a14d5731c47409de8cc22af95e40
link
/test istio-unit-tests

prow/e2e-simpleTests.sh
76e8ef6d2356a14d5731c47409de8cc22af95e40
link
/test e2e-simple

prow/e2e-bookInfoTests.sh
76e8ef6d2356a14d5731c47409de8cc22af95e40
link
/test e2e-bookInfo

prow/istio-pilot-e2e-v1alpha3.sh
76e8ef6d2356a14d5731c47409de8cc22af95e40
link
/test istio-pilot-e2e-v1alpha3

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@sbezverk: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-unit-tests.sh
76e8ef6d2356a14d5731c47409de8cc22af95e40
link
/test istio-unit-tests

prow/e2e-simpleTests.sh
76e8ef6d2356a14d5731c47409de8cc22af95e40
link
/test e2e-simple

prow/e2e-bookInfoTests.sh
76e8ef6d2356a14d5731c47409de8cc22af95e40
link
/test e2e-bookInfo

prow/istio-pilot-e2e-v1alpha3.sh
76e8ef6d2356a14d5731c47409de8cc22af95e40
link
/test istio-pilot-e2e-v1alpha3

prow/istio-pilot-e2e.sh
76e8ef6d2356a14d5731c47409de8cc22af95e40
link
/test istio-pilot-e2e

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

/hold

waiting for multicluster CI PRs to merge (reason for hold).

/test e2e-bookInfo

@sbezverk: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-unit-tests.sh
76e8ef6d2356a14d5731c47409de8cc22af95e40
link
/test istio-unit-tests

prow/e2e-simpleTests.sh
76e8ef6d2356a14d5731c47409de8cc22af95e40
link
/test e2e-simple

prow/istio-pilot-e2e-v1alpha3.sh
76e8ef6d2356a14d5731c47409de8cc22af95e40
link
/test istio-pilot-e2e-v1alpha3

prow/istio-pilot-e2e.sh
76e8ef6d2356a14d5731c47409de8cc22af95e40
link
/test istio-pilot-e2e

prow/e2e-bookInfoTests.sh
76e8ef6d2356a14d5731c47409de8cc22af95e40
link
/test e2e-bookInfo

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by:
To fully approve this pull request, please assign additional approvers.
We suggest the following additional approver: costinm
Assign the PR to them by writing /assign @costinm in a comment when ready.
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

pilot/OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@sbezverk: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/e2e-bookInfoTests.sh
76e8ef6d2356a14d5731c47409de8cc22af95e40
link
/test e2e-bookInfo

prow/istio-pilot-e2e-v1alpha3.sh
b55ec17e4492a5d61dc982ca0780df175ba2f9ae
link
/test istio-pilot-e2e-v1alpha3

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@sbezverk: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-pilot-e2e.sh
76829821e6ca9c50ef8fd5d3f7c78da68e2eab3f
link
/test istio-pilot-e2e

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

/test istio-pilot-e2e

@sbezverk: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-pilot-e2e.sh
76829821e6ca9c50ef8fd5d3f7c78da68e2eab3f
link
/test istio-pilot-e2e

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

/hold cancel

/test istio-pilot-e2e-v1alpha3

/retest

@sbezverk: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-pilot-e2e.sh
6a83e7ca904e86c85dc3ab0567ea63c2ad6f7148
link
/test istio-pilot-e2e

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

/test istio-pilot-e2e

/ok-to-test

@sbezverk: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-pilot-e2e.sh
6a83e7ca904e86c85dc3ab0567ea63c2ad6f7148
link
/test istio-pilot-e2e

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

Close as Circle CI by some reason refuses to test this PR.