IR camera flashes a couple times and stops

Ouput of cat /var/local/log/linux-enable-ir-emitter/linux-enable-ir-emitter.log
[17:56:55] [debug] Executing configure command.
[17:56:55] [info] Stand in front of and close to the camera and make sure the room is well lit.
[17:56:55] [info] Ensure to not use the camera during the execution.
[17:56:55] [debug] Checking if /dev/video0 is a grayscale camera.
[17:56:57] [debug] Checking if /dev/video1 is a grayscale camera.
[17:56:57] [debug] Checking if /dev/video2 is a grayscale camera.
[17:56:58] [debug] /dev/video2 is a grayscale camera.
[17:56:58] [info] Configuring the camera /dev/video2.
[17:56:58] [debug] yaml error: bad file: /etc/linux-enable-ir-emitter/pci-0000:04:00.3-usb-0:4:1.2-video-index0.ini.
[17:56:58] [debug] No previous configuration found.
[17:56:59] [debug] Configuration for /dev/video2 saved here: /etc/linux-enable-ir-emitter/pci-0000:04:00.3-usb-0:4:1.2-video-index0.ini.
[17:57:07] [error] The emitter is already working, skipping the configuration.
[18:57:12] [debug] Executing configure command.
[18:57:12] [info] Stand in front of and close to the camera and make sure the room is well lit.
[18:57:12] [info] Ensure to not use the camera during the execution.
[18:57:12] [debug] Checking if /dev/video0 is a grayscale camera.
[18:57:14] [debug] Checking if /dev/video1 is a grayscale camera.
[18:57:14] [debug] Checking if /dev/video2 is a grayscale camera.
[18:57:16] [debug] /dev/video2 is a grayscale camera.
[18:57:16] [info] Configuring the camera /dev/video2.
[18:57:16] [debug] Previous configuration found.
[18:57:28] [debug] Instruction applied: unit: 14, selector: 6, control: 1 3 2 0 0 0 0 0 0.
[18:57:30] [debug] The instruction is not valid.
[18:57:30] [debug] Instruction applied: unit: 14, selector: 6, control: 1 3 3 0 0 0 0 0 0.
[18:57:31] [debug] The instruction is not valid.
[18:57:31] [debug] Reseting to the instruction: unit: 14, selector: 6, control: 1 3 1 0 0 0 0 0 0.
[18:57:31] [debug] Instruction applied: unit: 14, selector: 9, control: 1 0 0 0.
[18:57:32] [debug] The instruction is not valid.
[18:57:32] [debug] Reseting to the instruction: unit: 14, selector: 9, control: 1 0 0 0.
[18:57:32] [error] The configuration failed.
[18:57:32] [info] Please retry in manual mode by adding the '-m' option.
[18:57:32] [info] Do not hesitate to visit the GitHub!
[18:57:32] [info] https://github.com/EmixamPP/linux-enable-ir-emitter/blob/master/docs/README.md
[19:01:46] [debug] Executing configure command.
[19:01:46] [info] Stand in front of and close to the camera and make sure the room is well lit.
[19:01:46] [info] Ensure to not use the camera during the execution.
[19:01:46] [debug] Checking if /dev/video0 is a grayscale camera.
[19:01:47] [debug] Checking if /dev/video1 is a grayscale camera.
[19:01:47] [debug] Checking if /dev/video2 is a grayscale camera.
[19:01:49] [debug] /dev/video2 is a grayscale camera.
[19:01:49] [info] Configuring the camera /dev/video2.
[19:01:49] [debug] Previous configuration found.
[19:01:58] [debug] Instruction applied: unit: 14, selector: 6, control: 1 3 2 0 0 0 0 0 0.
[19:01:59] [debug] The instruction is not valid.
[19:01:59] [debug] Instruction applied: unit: 14, selector: 6, control: 1 3 3 0 0 0 0 0 0.
[19:02:01] [debug] The instruction is not valid.
[19:02:01] [debug] Reseting to the instruction: unit: 14, selector: 6, control: 1 3 1 0 0 0 0 0 0.
[19:02:01] [debug] Instruction applied: unit: 14, selector: 9, control: 1 0 0 0.
[19:02:02] [debug] The instruction is not valid.
[19:02:02] [debug] Reseting to the instruction: unit: 14, selector: 9, control: 1 0 0 0.
[19:02:02] [error] The configuration failed.
[19:02:02] [info] Please retry in manual mode by adding the '-m' option.
[19:02:02] [info] Do not hesitate to visit the GitHub!
[19:02:02] [info] https://github.com/EmixamPP/linux-enable-ir-emitter/blob/master/docs/README.md
[19:02:09] [debug] Executing configure command.
[19:02:09] [info] Stand in front of and close to the camera and make sure the room is well lit.
[19:02:09] [info] Ensure to not use the camera during the execution.
[19:02:09] [debug] Checking if /dev/video0 is a grayscale camera.
[19:02:09] [debug] Checking if /dev/video1 is a grayscale camera.
[19:02:09] [debug] Checking if /dev/video2 is a grayscale camera.
[19:02:10] [debug] /dev/video2 is a grayscale camera.
[19:02:10] [info] Configuring the camera /dev/video2.
[19:02:10] [debug] Previous configuration found.
[19:02:14] [debug] Instruction applied: unit: 14, selector: 6, control: 1 3 2 0 0 0 0 0 0.
[19:02:17] [debug] The instruction is not valid.
[19:02:17] [debug] Instruction applied: unit: 14, selector: 6, control: 1 3 3 0 0 0 0 0 0.
[19:02:20] [debug] The instruction is not valid.
[19:02:20] [debug] Reseting to the instruction: unit: 14, selector: 6, control: 1 3 1 0 0 0 0 0 0.
[19:02:20] [debug] Instruction applied: unit: 14, selector: 9, control: 1 0 0 0.
[19:02:23] [debug] The instruction is not valid.
[19:02:23] [debug] Reseting to the instruction: unit: 14, selector: 9, control: 1 0 0 0.
[19:02:23] [error] The configuration failed.
[19:02:23] [info] Please retry in manual mode by adding the '-m' option.
[19:02:23] [info] Do not hesitate to visit the GitHub!
[19:02:23] [info] https://github.com/EmixamPP/linux-enable-ir-emitter/blob/master/docs/README.md
[13:44:08] [debug] Executing configure command.
[13:44:08] [info] Stand in front of and close to the camera and make sure the room is well lit.
[13:44:08] [info] Ensure to not use the camera during the execution.
[13:44:08] [debug] Checking if /dev/video0 is a grayscale camera.
[13:44:10] [debug] Checking if /dev/video1 is a grayscale camera.
[13:44:10] [debug] Checking if /dev/video2 is a grayscale camera.
[13:44:12] [debug] /dev/video2 is a grayscale camera.
[13:44:12] [info] Configuring the camera /dev/video2.
[13:44:12] [debug] Previous configuration found.
[13:44:15] [error] The emitter is already working, skipping the configuration.
[02:51:54] [debug] Executing configure command.
[02:51:54] [info] Stand in front of and close to the camera and make sure the room is well lit.
[02:51:54] [info] Ensure to not use the camera during the execution.
[02:51:54] [debug] Checking if /dev/video0 is a grayscale camera.
[02:51:56] [debug] Checking if /dev/video1 is a grayscale camera.
[02:51:56] [debug] Checking if /dev/video2 is a grayscale camera.
[02:51:58] [debug] /dev/video2 is a grayscale camera.
[02:51:58] [info] Configuring the camera /dev/video2.
[02:51:58] [debug] Previous configuration found.
[02:52:01] [debug] Instruction applied: unit: 14, selector: 6, control: 1 3 2 0 0 0 0 0 0.
[02:52:02] [debug] The instruction is not valid.
[02:52:02] [debug] Instruction applied: unit: 14, selector: 6, control: 1 3 3 0 0 0 0 0 0.
[02:52:04] [debug] The instruction is not valid.
[02:52:04] [debug] Reseting to the instruction: unit: 14, selector: 6, control: 1 3 1 0 0 0 0 0 0.
[02:52:04] [debug] Instruction applied: unit: 14, selector: 9, control: 1 0 0 0.
[02:52:05] [debug] The instruction is not valid.
[02:52:05] [debug] Reseting to the instruction: unit: 14, selector: 9, control: 1 0 0 0.
[02:52:05] [error] The configuration failed.
[02:52:05] [info] Please retry in manual mode by adding the '-m' option.
[02:52:05] [info] Do not hesitate to visit the GitHub!
[02:52:05] [info] https://github.com/EmixamPP/linux-enable-ir-emitter/blob/master/docs/README.md
[02:52:37] [debug] Executing configure command.
[02:52:37] [info] Stand in front of and close to the camera and make sure the room is well lit.
[02:52:37] [info] Ensure to not use the camera during the execution.
[02:52:37] [debug] Checking if /dev/video0 is a grayscale camera.
[02:52:37] [debug] Checking if /dev/video1 is a grayscale camera.
[02:52:37] [debug] Checking if /dev/video2 is a grayscale camera.
[02:52:38] [debug] /dev/video2 is a grayscale camera.
[02:52:38] [info] Configuring the camera /dev/video2.
[02:52:38] [debug] Previous configuration found.
[02:52:41] [debug] Instruction applied: unit: 14, selector: 6, control: 1 3 2 0 0 0 0 0 0.
[02:52:43] [debug] The instruction is not valid.
[02:52:43] [debug] Instruction applied: unit: 14, selector: 6, control: 1 3 3 0 0 0 0 0 0.
[02:52:44] [debug] The instruction is not valid.
[02:52:44] [debug] Reseting to the instruction: unit: 14, selector: 6, control: 1 3 1 0 0 0 0 0 0.
[02:52:44] [debug] Instruction applied: unit: 14, selector: 9, control: 1 0 0 0.
[02:52:46] [debug] The instruction is not valid.
[02:52:46] [debug] Reseting to the instruction: unit: 14, selector: 9, control: 1 0 0 0.
[02:52:46] [error] The configuration failed.
[02:52:46] [info] Please retry in manual mode by adding the '-m' option.
[02:52:46] [info] Do not hesitate to visit the GitHub!
[02:52:46] [info] https://github.com/EmixamPP/linux-enable-ir-emitter/blob/master/docs/README.md
[03:02:49] [debug] Executing configure command.
[03:02:49] [info] Stand in front of and close to the camera and make sure the room is well lit.
[03:02:49] [info] Ensure to not use the camera during the execution.
[03:02:49] [debug] Checking if /dev/video0 is a grayscale camera.
[03:02:50] [debug] Checking if /dev/video1 is a grayscale camera.
[03:02:50] [debug] Checking if /dev/video2 is a grayscale camera.
[03:02:52] [debug] /dev/video2 is a grayscale camera.
[03:02:52] [info] Configuring the camera /dev/video2.
[03:02:52] [debug] Previous configuration found.
[03:02:57] [debug] Instruction applied: unit: 14, selector: 6, control: 1 3 2 0 0 0 0 0 0.
[03:02:59] [debug] The instruction is not valid.
[03:02:59] [debug] Instruction applied: unit: 14, selector: 6, control: 1 3 3 0 0 0 0 0 0.
[03:03:00] [debug] The instruction is not valid.
[03:03:00] [debug] Reseting to the instruction: unit: 14, selector: 6, control: 1 3 1 0 0 0 0 0 0.
[03:03:00] [debug] Instruction applied: unit: 14, selector: 9, control: 1 0 0 0.
[03:03:02] [debug] The instruction is not valid.
[03:03:02] [debug] Reseting to the instruction: unit: 14, selector: 9, control: 1 0 0 0.
[03:03:02] [error] The configuration failed.
[03:03:02] [info] Please retry in manual mode by adding the '-m' option.
[03:03:02] [info] Do not hesitate to visit the GitHub!
[03:03:02] [info] https://github.com/EmixamPP/linux-enable-ir-emitter/blob/master/docs/README.md
[03:16:43] [debug] Executing configure command.
[03:16:43] [info] Stand in front of and close to the camera and make sure the room is well lit.
[03:16:43] [info] Ensure to not use the camera during the execution.
[03:16:43] [debug] Checking if /dev/video0 is a grayscale camera.
[03:16:45] [debug] Checking if /dev/video1 is a grayscale camera.
[03:16:45] [debug] Checking if /dev/video2 is a grayscale camera.
[03:16:47] [debug] /dev/video2 is a grayscale camera.
[03:16:47] [info] Configuring the camera /dev/video2.
[03:16:47] [debug] Previous configuration found.
[03:16:52] [debug] Instruction applied: unit: 14, selector: 6, control: 1 3 2 0 0 0 0 0 0.
[03:16:54] [debug] The instruction is not valid.
[03:16:54] [debug] Instruction applied: unit: 14, selector: 6, control: 1 3 3 0 0 0 0 0 0.
[03:16:55] [debug] The instruction is not valid.
[03:16:55] [debug] Reseting to the instruction: unit: 14, selector: 6, control: 1 3 1 0 0 0 0 0 0.
[03:16:55] [debug] Instruction applied: unit: 14, selector: 9, control: 1 0 0 0.
[03:16:57] [debug] The instruction is not valid.
[03:16:57] [debug] Reseting to the instruction: unit: 14, selector: 9, control: 1 0 0 0.
[03:16:57] [error] The configuration failed.
[03:16:57] [info] Please retry in manual mode by adding the '-m' option.
[03:16:57] [info] Do not hesitate to visit the GitHub!
[03:16:57] [info] https://github.com/EmixamPP/linux-enable-ir-emitter/blob/master/docs/README.md
[03:17:01] [debug] Executing configure command.
[03:17:01] [info] Stand in front of and close to the camera and make sure the room is well lit.
[03:17:01] [info] Ensure to not use the camera during the execution.
[03:17:01] [debug] Checking if /dev/video0 is a grayscale camera.
[03:17:02] [debug] Checking if /dev/video1 is a grayscale camera.
[03:17:02] [debug] Checking if /dev/video2 is a grayscale camera.
[03:17:02] [debug] /dev/video2 is a grayscale camera.
[03:17:02] [info] Configuring the camera /dev/video2.
[03:17:02] [debug] Previous configuration found.
[03:17:04] [debug] Instruction applied: unit: 14, selector: 6, control: 1 3 2 0 0 0 0 0 0.
[03:17:06] [debug] The instruction is not valid.
[03:17:06] [debug] Instruction applied: unit: 14, selector: 6, control: 1 3 3 0 0 0 0 0 0.
[03:17:07] [debug] The instruction is not valid.
[03:17:07] [debug] Reseting to the instruction: unit: 14, selector: 6, control: 1 3 1 0 0 0 0 0 0.
[03:17:07] [debug] Instruction applied: unit: 14, selector: 9, control: 1 0 0 0.
[03:17:09] [debug] The instruction is not valid.
[03:17:09] [debug] Reseting to the instruction: unit: 14, selector: 9, control: 1 0 0 0.
[03:17:09] [error] The configuration failed.
[03:17:09] [info] Please retry in manual mode by adding the '-m' option.
[03:17:09] [info] Do not hesitate to visit the GitHub!
[03:17:09] [info] https://github.com/EmixamPP/linux-enable-ir-emitter/blob/master/docs/README.md
[03:17:32] [debug] Executing configure command.
[03:17:32] [info] Stand in front of and close to the camera and make sure the room is well lit.
[03:17:32] [info] Ensure to not use the camera during the execution.
[03:17:32] [debug] Checking if /dev/video0 is a grayscale camera.
[03:17:33] [debug] Checking if /dev/video1 is a grayscale camera.
[03:17:33] [debug] Checking if /dev/video2 is a grayscale camera.
[03:17:33] [debug] /dev/video2 is a grayscale camera.
[03:17:33] [info] Configuring the camera /dev/video2.
[03:17:33] [debug] Previous configuration found.
[03:17:36] [debug] Instruction applied: unit: 14, selector: 6, control: 1 3 2 0 0 0 0 0 0.
[03:17:37] [debug] The instruction is not valid.
[03:17:37] [debug] Instruction applied: unit: 14, selector: 6, control: 1 3 3 0 0 0 0 0 0.
[03:17:39] [debug] The instruction is not valid.
[03:17:39] [debug] Reseting to the instruction: unit: 14, selector: 6, control: 1 3 1 0 0 0 0 0 0.
[03:17:39] [debug] Instruction applied: unit: 14, selector: 9, control: 1 0 0 0.
[03:17:40] [debug] The instruction is not valid.
[03:17:40] [debug] Reseting to the instruction: unit: 14, selector: 9, control: 1 0 0 0.
[03:17:40] [error] The configuration failed.
[03:17:40] [info] Please retry in manual mode by adding the '-m' option.
[03:17:40] [info] Do not hesitate to visit the GitHub!
[03:17:40] [info] https://github.com/EmixamPP/linux-enable-ir-emitter/blob/master/docs/README.md
[03:29:42] [debug] Executing configure command.
[03:29:42] [info] Stand in front of and close to the camera and make sure the room is well lit.
[03:29:42] [info] Ensure to not use the camera during the execution.
[03:29:42] [debug] Checking if /dev/video0 is a grayscale camera.
[03:29:43] [debug] Checking if /dev/video1 is a grayscale camera.
[03:29:43] [debug] Checking if /dev/video2 is a grayscale camera.
[03:29:45] [debug] /dev/video2 is a grayscale camera.
[03:29:45] [info] Configuring the camera /dev/video2.
[03:29:45] [debug] yaml error: bad file: /etc/linux-enable-ir-emitter/pci-0000:04:00.3-usb-0:4:1.2-video-index0.ini.
[03:29:45] [debug] No previous configuration found.
[03:29:45] [debug] Configuration for /dev/video2 saved here: /etc/linux-enable-ir-emitter/pci-0000:04:00.3-usb-0:4:1.2-video-index0.ini.
[03:29:48] [debug] Instruction applied: unit: 14, selector: 6, control: 1 3 2 0 0 0 0 0 0.
[03:29:49] [debug] The instruction is not valid.
[03:29:49] [debug] Instruction applied: unit: 14, selector: 6, control: 1 3 3 0 0 0 0 0 0.
[03:29:51] [debug] The instruction is not valid.
[03:29:51] [debug] Reseting to the instruction: unit: 14, selector: 6, control: 1 3 1 0 0 0 0 0 0.
[03:29:51] [debug] Instruction applied: unit: 14, selector: 9, control: 1 0 0 0.
[03:29:52] [debug] The instruction is not valid.
[03:29:52] [debug] Reseting to the instruction: unit: 14, selector: 9, control: 1 0 0 0.
[03:29:52] [error] The configuration failed.
[03:29:52] [info] Please retry in manual mode by adding the '-m' option.
[03:29:52] [info] Do not hesitate to visit the GitHub!
[03:29:52] [info] https://github.com/EmixamPP/linux-enable-ir-emitter/blob/master/docs/README.md
[03:29:57] [debug] Executing configure command.
[03:29:57] [info] Stand in front of and close to the camera and make sure the room is well lit.
[03:29:57] [info] Ensure to not use the camera during the execution.
[03:29:57] [debug] Checking if /dev/video0 is a grayscale camera.
[03:29:58] [debug] Checking if /dev/video1 is a grayscale camera.
[03:29:58] [debug] Checking if /dev/video2 is a grayscale camera.
[03:29:58] [debug] /dev/video2 is a grayscale camera.
[03:29:58] [info] Configuring the camera /dev/video2.
[03:29:58] [debug] Previous configuration found.
[03:30:01] [debug] Instruction applied: unit: 14, selector: 6, control: 1 3 2 0 0 0 0 0 0.
[03:30:02] [debug] The instruction is not valid.
[03:30:02] [debug] Instruction applied: unit: 14, selector: 6, control: 1 3 3 0 0 0 0 0 0.
[03:30:04] [debug] The instruction is not valid.
[03:30:04] [debug] Reseting to the instruction: unit: 14, selector: 6, control: 1 3 1 0 0 0 0 0 0.
[03:30:04] [debug] Instruction applied: unit: 14, selector: 9, control: 1 0 0 0.
[03:30:05] [debug] The instruction is not valid.
[03:30:05] [debug] Reseting to the instruction: unit: 14, selector: 9, control: 1 0 0 0.
[03:30:05] [error] The configuration failed.
[03:30:05] [info] Please retry in manual mode by adding the '-m' option.
[03:30:05] [info] Do not hesitate to visit the GitHub!
[03:30:05] [info] https://github.com/EmixamPP/linux-enable-ir-emitter/blob/master/docs/README.md
[03:58:18] [debug] Executing configure command.
[03:58:18] [info] Stand in front of and close to the camera and make sure the room is well lit.
[03:58:18] [info] Ensure to not use the camera during the execution.
[03:58:18] [debug] Checking if /dev/video0 is a grayscale camera.
[03:58:19] [debug] Checking if /dev/video1 is a grayscale camera.
[03:58:19] [debug] Checking if /dev/video2 is a grayscale camera.
[03:58:21] [debug] /dev/video2 is a grayscale camera.
[03:58:21] [info] Configuring the camera /dev/video2.
[03:58:21] [debug] Previous configuration found.
[03:58:29] [debug] Instruction applied: unit: 14, selector: 6, control: 1 3 2 0 0 0 0 0 0.
[03:58:30] [debug] The instruction is not valid.
[03:58:30] [debug] Instruction applied: unit: 14, selector: 6, control: 1 3 3 0 0 0 0 0 0.
[03:58:31] [debug] The instruction is not valid.
[03:58:31] [debug] Reseting to the instruction: unit: 14, selector: 6, control: 1 3 1 0 0 0 0 0 0.
[03:58:31] [debug] Instruction applied: unit: 14, selector: 9, control: 1 0 0 0.
[03:58:33] [debug] The instruction is not valid.
[03:58:33] [debug] Reseting to the instruction: unit: 14, selector: 9, control: 1 0 0 0.
[03:58:33] [error] The configuration failed.
[03:58:33] [info] Please retry in manual mode by adding the '-m' option.
[03:58:33] [info] Do not hesitate to visit the GitHub!
[03:58:33] [info] https://github.com/EmixamPP/linux-enable-ir-emitter/blob/master/docs/README.md
[03:58:37] [debug] Executing configure command.
[03:58:37] [info] Stand in front of and close to the camera and make sure the room is well lit.
[03:58:37] [info] Ensure to not use the camera during the execution.
[03:58:37] [debug] Checking if /dev/video0 is a grayscale camera.
[03:58:38] [debug] Checking if /dev/video1 is a grayscale camera.
[03:58:38] [debug] Checking if /dev/video2 is a grayscale camera.
[03:58:38] [debug] /dev/video2 is a grayscale camera.
[03:58:38] [info] Configuring the camera /dev/video2.
[03:58:38] [debug] Previous configuration found.
[03:58:41] [debug] Instruction applied: unit: 14, selector: 6, control: 1 3 2 0 0 0 0 0 0.
[03:58:42] [debug] The instruction is not valid.
[03:58:42] [debug] Instruction applied: unit: 14, selector: 6, control: 1 3 3 0 0 0 0 0 0.
[03:58:44] [debug] The instruction is not valid.
[03:58:44] [debug] Reseting to the instruction: unit: 14, selector: 6, control: 1 3 1 0 0 0 0 0 0.
[03:58:44] [debug] Instruction applied: unit: 14, selector: 9, control: 1 0 0 0.
[03:58:46] [debug] The instruction is not valid.
[03:58:46] [debug] Reseting to the instruction: unit: 14, selector: 9, control: 1 0 0 0.
[03:58:46] [error] The configuration failed.
[03:58:46] [info] Please retry in manual mode by adding the '-m' option.
[03:58:46] [info] Do not hesitate to visit the GitHub!
[03:58:46] [info] https://github.com/EmixamPP/linux-enable-ir-emitter/blob/master/docs/README.md

Output of sudo linux-enable-ir-emitter tweak
Tweaking the camera /dev/video2
Caution, you could break the camera.

0) unit: 14, selector: 6, control: 1 3 1 0 0 0 0 0 0
1) unit: 14, selector: 9, control: 1 0 0 0
2) exit

Output of v4l2-ctl --list-devices
HP Wide Vision 5MP Camera: HP W (usb-0000:04:00.3-4):
	/dev/video0
	/dev/video1
	/dev/video2
	/dev/video3
	/dev/media0
	/dev/media1

Ouput of for dev in /dev/video*; do echo $dev && v4l2-ctl -d $dev --list-formats-ext; done
/dev/video0
ioctl: VIDIOC_ENUM_FMT
	Type: Video Capture

	[0]: 'MJPG' (Motion-JPEG, compressed)
		Size: Discrete 2592x1944
			Interval: Discrete 0.033s (30.000 fps)
		Size: Discrete 1280x720
			Interval: Discrete 0.033s (30.000 fps)
		Size: Discrete 640x360
			Interval: Discrete 0.033s (30.000 fps)
		Size: Discrete 640x480
			Interval: Discrete 0.033s (30.000 fps)
		Size: Discrete 640x640
			Interval: Discrete 0.033s (30.000 fps)
		Size: Discrete 1280x960
			Interval: Discrete 0.033s (30.000 fps)
		Size: Discrete 1920x1080
			Interval: Discrete 0.033s (30.000 fps)
		Size: Discrete 2560x1440
			Interval: Discrete 0.033s (30.000 fps)
		Size: Discrete 2592x1728
			Interval: Discrete 0.033s (30.000 fps)
	[1]: 'YUYV' (YUYV 4:2:2)
		Size: Discrete 640x480
			Interval: Discrete 0.033s (30.000 fps)
		Size: Discrete 640x360
			Interval: Discrete 0.033s (30.000 fps)
/dev/video1
ioctl: VIDIOC_ENUM_FMT
	Type: Video Capture

/dev/video2
ioctl: VIDIOC_ENUM_FMT
	Type: Video Capture

	[0]: 'GREY' (8-bit Greyscale)
		Size: Discrete 640x480
			Interval: Discrete 0.067s (15.000 fps)
/dev/video3
ioctl: VIDIOC_ENUM_FMT
	Type: Video Capture

Output of ls -l /dev/v4l/by-path
totale 0
lrwxrwxrwx. 1 root root 12 28 set 03.29 pci-0000:04:00.3-usb-0:4:1.0-video-index0 -> ../../video0
lrwxrwxrwx. 1 root root 12 28 set 03.29 pci-0000:04:00.3-usb-0:4:1.0-video-index1 -> ../../video1
lrwxrwxrwx. 1 root root 12 28 set 03.29 pci-0000:04:00.3-usb-0:4:1.2-video-index0 -> ../../video2
lrwxrwxrwx. 1 root root 12 28 set 03.29 pci-0000:04:00.3-usb-0:4:1.2-video-index1 -> ../../video3
lrwxrwxrwx. 1 root root 12 28 set 03.29 pci-0000:04:00.3-usbv2-0:4:1.0-video-index0 -> ../../video0
lrwxrwxrwx. 1 root root 12 28 set 03.29 pci-0000:04:00.3-usbv2-0:4:1.0-video-index1 -> ../../video1
lrwxrwxrwx. 1 root root 12 28 set 03.29 pci-0000:04:00.3-usbv2-0:4:1.2-video-index0 -> ../../video2
lrwxrwxrwx. 1 root root 12 28 set 03.29 pci-0000:04:00.3-usbv2-0:4:1.2-video-index1 -> ../../video3

Give more information if you have
IR camera (/dev/video2) flashes briefly for about half a second and then stops working showing only a black screen in the preview. This happens everytime it is llaunched.
One time I forgot to close a camera app that was using the normal webcam, on that occasion the ir camera was warking fine and can consistently reproduce this.
I'm new-ish to Linux so my apologies if something is missing, let me know if you need anything else :)
Additional info

Computer (or camera) model: HP Envy x360 15-fh0002nl, sometimes known as fh0000 or fh0xxx
Linux distribution: Ultramarine Linux 40, based on Fedora 40
Version of linux-enable-ir-emitter:  6.0.3

Execute

sudo linux-enable-ir-emitter -v tweak
input 2
input 1 3 2 0 0 0 0 0 0
look at the video feedback and the ir emitter, does it work?
if not retry with 1 3 3 0 0 0 0 0 0
does it work?
if not paste output here

Executing tweak command.
Checking if /dev/video0 is a grayscale camera.
Checking if /dev/video1 is a grayscale camera.
Checking if /dev/video2 is a grayscale camera.
/dev/video2 is a grayscale camera.
Tweaking the camera /dev/video2
Caution, you could break the camera.
Previous configuration found.
0) unit: 14, selector: 6, control: 1 3 1 0 0 0 0 0 0
1) unit: 14, selector: 9, control: 1 0 0 0
2) exit
Choose an instruction to tweak: 0
minimum:
maximum: 1 3 3 0 0 0 0 0 0
initial: 1 3 1 0 0 0 0 0 0
current: 1 3 1 0 0 0 0 0 0
status: enable
new current or status:  1 3 2 0 0 0 0 0 0
Invalid value for the instruction.
0) unit: 14, selector: 6, control: 1 3 1 0 0 0 0 0 0
1) unit: 14, selector: 9, control: 1 0 0 0
2) exit
Choose an instruction to tweak: terminate called after throwing an instance of 'cv::Exception'
  what():  OpenCV(4.10.0) /home/runner/work/linux-enable-ir-emitter/linux-enable-ir-emitter/.github/workflows/deps/build/opencv/src/opencv/modules/highgui/src/window.cpp:973: error: (-215:Assertion failed) size.width>0 && size.height>0 in function 'imshow'

zsh: IOT instruction  sudo linux-enable-ir-emitter -v tweak

Seems that I can't change the configuration, am I doing something wrong?

Could you retry with the new v6.0.4? I think it should work now; I fixed a bug that you reported here!

I tried to uninstall the old version and installed the new one and the camera was working correctly without changing any setting for some reason? Then I installed Howdy and it did the same thing that I described the other day with a few flashes and then the black preview.
Went back to try with your solution of the other day and now it changes the settings correctly, but it still doesn't work properly.
Also tried to uninstall Howdy and its dependencies to see if was some kind of conflict with something, but the problem is still there

First using the tweak command assign the value 1 3 2 0 0 0 0 0 0 to the instruction 0
Then exit and:

execute linux-enable-ir-emitter -d /dev/video2 test does the emitter flash?
execute linux-enable-ir-emitter -d /dev/video2 test does the emitter flash?
execute linux-enable-ir-emitter run
execute linux-enable-ir-emitter -d /dev/video2 test does the emitter flash?
execute linux-enable-ir-emitter -d /dev/video2 test does the emitter flash?

We will determine if the applying of the instruction is permanent or not

Sorry for the late answer, followed your instructions and it's the same thing as always, some flashes and then black screen

I just want to let you know that I am working on a kernel space solution (instead of user space as currently), this should solve this kind of issue (I think).


Error in NL API, 'Sentiment' object has no attribute 'score'

Upon executing the following code on GCE & locally I'm getting 'score' not found error locally while it works on GCE.
def analyze_text(text):
    language_client = language.Client()
    document = language_client.document_from_text(text)
    annotations = document.annotate_text(include_sentiment=True)
    print(annotations.sentiment.score)
    print (annotations.sentiment.magnitude)

Only difference I can find is on GCE, the gcloud version is different than the local
GCE gcloud
gcloud --version
Google Cloud SDK 145.0.0
alpha 2017.02.21
app-engine-python 1.9.50
beta 2017.02.21
bq 2.0.24
bq-nix 2.0.24
core 2017.02.21
core-nix 2017.02.21
gcloud
gcloud-deps 2017.02.21
gcloud-deps-linux-x86_64 2017.02.21
gsutil 4.22
gsutil-nix 4.22
Local gcloud
gcloud --version
Google Cloud SDK 148.0.1
bq 2.0.24
bq-nix 2.0.24
core 2017.03.24
core-nix 2016.11.07
gcloud
gcloud-deps 2017.03.17
gcloud-deps-darwin-x86_64 2017.02.21
gsutil 4.23
gsutil-nix 4.19
Debugging locally, the response from NL API consist of polarity property and not score.

So, any idea about this?

That most likely means that the API is inconsistent. I can make it not KeyError; you will just get a None. I will do that now while I am thinking about it.


Suggestion: Add nativescript-camera plugin

Since using the camera is a pretty common scenario, it would be great if the nativescript-camera plugin could be added to the Preview app.

@rdlauer thanks for the suggestion. We have planned to include this plugin along with some others (nativescript-fresco, nativescript-intl, nativescript-iqkeyboardmanager, nativescript-social-share and the latest split pro UI packages) in the next version of the Preview app.

Awesome. @tjvantoll for visibility into this as well.

A new version of the Preview app containing those plugins is now available in the app stores.


New pull, run command from README: slapd failed with status 50

I have run the command from the osixia/docker-openldap image README (modified to remove detach), yet get the message that slapd failed with status 50.
What am I doing wrong? Running on a Mac.
docker run -p 389:389 -p 636:636 --name my-openldap-container --rm osixia/openldap:1.5.0
Unable to find image 'osixia/openldap:1.5.0' locally
1.5.0: Pulling from osixia/openldap
45b42c59be33: Pull complete
ae7fb8f59730: Pull complete
55443d9da5d5: Pull complete
062b29194b6e: Pull complete
613ba832a7d4: Pull complete
48562e0b854d: Pull complete
3731e12f1fa4: Pull complete
b1feb4016881: Pull complete
d2744e887776: Pull complete
Digest: sha256:18742e9c449c9c1afe129d3f2f3ee15fb34cc43e5f940a20f3399728f41d7c28
Status: Downloaded newer image for osixia/openldap:1.5.0
***  INFO   | 2021-06-04 14:40:13 | CONTAINER_LOG_LEVEL = 3 (info)
***  INFO   | 2021-06-04 14:40:13 | Search service in CONTAINER_SERVICE_DIR = /container/service :
***  INFO   | 2021-06-04 14:40:13 | link /container/service/:ssl-tools/startup.sh to /container/run/startup/:ssl-tools
***  INFO   | 2021-06-04 14:40:13 | link /container/service/slapd/startup.sh to /container/run/startup/slapd
***  INFO   | 2021-06-04 14:40:13 | link /container/service/slapd/process.sh to /container/run/process/slapd/run
***  INFO   | 2021-06-04 14:40:13 | Environment files will be proccessed in this order :
Caution: previously defined variables will not be overriden.
/container/environment/99-default/default.yaml
/container/environment/99-default/default.startup.yaml

To see how this files are processed and environment variables values,
run this container with '--loglevel debug'
***  INFO   | 2021-06-04 14:40:13 | Running /container/run/startup/:ssl-tools...
***  INFO   | 2021-06-04 14:40:13 | Running /container/run/startup/slapd...
***  INFO   | 2021-06-04 14:40:13 | openldap user and group adjustments
***  INFO   | 2021-06-04 14:40:13 | get current openldap uid/gid info inside container
***  INFO   | 2021-06-04 14:40:13 | -------------------------------------
***  INFO   | 2021-06-04 14:40:13 | openldap GID/UID
***  INFO   | 2021-06-04 14:40:13 | -------------------------------------
***  INFO   | 2021-06-04 14:40:13 | User uid: 911
***  INFO   | 2021-06-04 14:40:13 | User gid: 911
***  INFO   | 2021-06-04 14:40:14 | uid/gid changed: false
***  INFO   | 2021-06-04 14:40:14 | -------------------------------------
***  INFO   | 2021-06-04 14:40:14 | updating file uid/gid ownership
***  INFO   | 2021-06-04 14:40:14 | Database and config directory are empty...
***  INFO   | 2021-06-04 14:40:14 | Init new ldap server...
  Backing up /etc/ldap/slapd.d in /var/backups/slapd-2.4.57+dfsg-1~bpo10+1... done.
  Creating initial configuration... done.
  Creating LDAP directory... done.
invoke-rc.d: could not determine current runlevel
invoke-rc.d: policy-rc.d denied execution of restart.
***  INFO   | 2021-06-04 14:40:14 | Start OpenLDAP...
***  INFO   | 2021-06-04 14:40:14 | Waiting for OpenLDAP to start...
***  INFO   | 2021-06-04 14:40:14 | Add bootstrap schemas...
config file testing succeeded
***  INFO   | 2021-06-04 14:40:14 | Add image bootstrap ldif...
***  ERROR  | 2021-06-04 14:40:14 | /container/run/startup/slapd failed with status 50

***  INFO   | 2021-06-04 14:40:14 | Killing all processes...

My error. I turned on debugging and docker was running out of space to write to the drive.
Bad user on device!


Disable legacy authz runtime.

 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.Thanuja seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.You have signed the CLA already but the status is still pending? Let us recheck it.


ImportError: cannot import name get_apps

Hi.
I try to install ReadTheDocs on Ubuntu 14.04 LTS however,  as the docs says that I need to run ./managepy syncdb - there is no such command syncdb, it is sync data. When I run this, I get the bellow error. Can you tell  me what is wrong and update your docs so I can install this? Thanks!
./manage.py syncdata
[11/Jul/2017 02:26:33] root:120[13211]: INFO Generating grammar tables from /usr/lib/python2.7/lib2to3/Grammar.txt
[11/Jul/2017 02:26:33] root:120[13211]: INFO Generating grammar tables from /usr/lib/python2.7/lib2to3/PatternGrammar.txt
Traceback (most recent call last):
File "./manage.py", line 11, in
execute_from_command_line(sys.argv)
File "/opt/rtd/local/lib/python2.7/site-packages/django/core/management/init.py", line 353, in execute_from_command_line
utility.execute()
File "/opt/rtd/local/lib/python2.7/site-packages/django/core/management/init.py", line 345, in execute
self.fetch_command(subcommand).run_from_argv(self.argv)
File "/opt/rtd/local/lib/python2.7/site-packages/django/core/management/base.py", line 348, in run_from_argv
self.execute(*args, **cmd_options)
File "/opt/rtd/local/lib/python2.7/site-packages/django/core/management/base.py", line 399, in execute
output = self.handle(*args, **options)
File "/opt/rtd/local/lib/python2.7/site-packages/django_extensions/management/utils.py", line 58, in inner
ret = func(self, *args, **kwargs)
File "/opt/rtd/local/lib/python2.7/site-packages/django/utils/decorators.py", line 184, in inner
return func(*args, **kwargs)
File "/opt/rtd/local/lib/python2.7/site-packages/django_extensions/management/commands/syncdata.py", line 67, in handle
from django.db.models import get_apps
ImportError: cannot import name get_apps

Thanks for working to get Read the Docs into your organization. We currently don't have time to support local installs for free as a core team. This is explained in more depth here: http://docs.readthedocs.io/en/latest/open-source-philosophy.html#unsupported -- I will close this issue because of this policy.
We do offer paid hosting for companies at readthedocs.com, as well as paid support for local installs.


Unknown typings dependency es6-shim

I am trying to update my project based off your template with the change you make as you make them.
With the most recent changes, I am running npm install and getting:
typings ERR! message Unknown dependency: registry:dt/es6-shim#0.31.2+20160317120654

typings ERR! cwd /Users/sam/Code/groupinn
typings ERR! system Darwin 15.4.0
typings ERR! command "/usr/local/Cellar/node/5.10.1/bin/node" "/Users/sam/Code/groupinn/node_modules/typings/dist/bin/typings-install.js"
typings ERR! node -v v5.10.1
typings ERR! typings -v 0.6.10

typings ERR! If you need help, you may report this error at:
typings ERR!   <https://github.com/typings/typings/issues>

Not sure why it's an unknown dependency, since I can do npm install es6-shim --ambient --save and it adds the exact same version number to typings.json.

My bad, I put that typings with a modern installation and this project had an old typings.


Fix compilation on asm! for Rust nightly.

Add use core::arch::asm; in source files that use asm!, to fix
compilation on the latest Rust nightly.

Thanks!


Add a blog(with essay,photo and video features) to the website.

Yeah,it will be inspiring as people out there will understand #ASKnet activities.

Do we want/need/maintain a Blog on the Page?


Is the tex source of the book also available?

Is the tex source of the book also available? If not, why is that? (Considering the book itself is freely accessible.)

No, sorry, it is not.


Add a way to pre-expand a single ShowCardAction in HostConfig

@dclaux,
Thanks for your contribution as a Microsoft full-time employee or intern. You do not need to sign a CLA.
Thanks,
Microsoft Pull Request Bot


Remove the longhorn-upgrade attacher type and refactor the upgrade path

longhorn/longhorn#6139

Waiting for e2e test run before marking this PR ready for review

@mergify backport v1.5.x

@innobead The test is still running here https://ci.longhorn.io/job/private/job/longhorn-tests-regression/4256/

The test result looks good. There some failing one but they doesn't seems related to the PR. Except for the one test_migration_with_unscheduled_replica. I am retesting test_migration_with_unscheduled_replica manually

Update: test_migration_with_unscheduled_replica passed when testing manually. Maybe the test case was a bit flaky.
Suggesting merging the PR. Thank you very much @innobead

cc @longhorn/qa for the flaky test case

@mergify backport v1.5.x


fix: use zwave-js guessFirmwareFileFormat function

Pull Request Test Coverage Report for Build 547535486

0 of 3 (0.0%)  changed or added relevant lines in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.04%) to 20.78%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

lib/ZwaveClient.js
0
3
0.0%

Totals

Change from base Build 547442057:
0.04%

Covered Lines:
1996

Relevant Lines:
9844

💛  - Coveralls


#[146759947]  Bump the UAA release version to v30.4

What
update  the UAA release, to protect us
against the CVE-2017-4994[1].
[1] https://www.cloudfoundry.org/cve-2017-4994/
How to review
Code review. I've applied this in a dev env and the tests pass.
Who can review
Anyone but me

I don't think you meant to commit the spec/examples.txt files. These should probably be in the .gitignore file.


[$1000] iOS/iPad - Buttons to add attachments, delete workspace, and upload an avatar are unrepsonsive

If you haven’t already, check out our contributing guidelines for onboarding and email<EMAIL_ADDRESS>to request to join our Slack channel!

Action Performed:

Start iOS / iPad App and login in any account
Go to Settings > Profile or Settings > Workspaces > Any workspace > General settings
Tap to avatar
Tap to 'Upload photo'
===
Go to any chat
Tap on [ + ] on composer
Tap to 'Add attachments'
===
Start iOS / iPad App
Login with any accounts - gmail or expensifail.
Create workspace or goto new workspace.
Tap '2 dots' button and tap 'Delete workspace'

Expected Result:

User can select and upload photo for avatar.
User can select and upload file in chat.
Workspace deleted. User is on the 'Create new workspace' page.

Actual Result:

Nothing happens. 'Upload photo' button is not working.
Nothing happens. 'Add attachment' button is not working.
The user cannot delete the workspace. After clicking on 'Delete workspace', the application freezes. The workspace is not deleted.

Workaround:
Can the user still use Expensify without this being fixed? Have you informed them of the workaround?
Platforms:

Which of our officially supported platforms is this issue occurring on?

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

Version Number: <IP_ADDRESS>
Reproducible in staging?: y
Reproducible in production?: y
If this was caught during regression testing, add the test name, ID and link from TestRail:
Email or phone of affected tester (no customers):
Logs: https://stackoverflow.com/c/expensify/questions/4856
Notes/Photos/Videos: Any additional supporting documentation
https://github.com/Expensify/App/assets/43996225/e6bd5ee4-421e-4789-83d9-250b914ee2aa
https://github.com/Expensify/App/assets/43996225/752c82a5-f616-4bfc-8bc6-eef21862f6e6
Expensify/Expensify Issue URL:
Issue reported by: Applause internal team
Slack conversation:
View all open jobs on GitHub
Upwork Automation - Do Not Edit

Upwork Job URL: https://www.upwork.com/jobs/~01d61f5eb9f4d23355
Upwork Job ID:<PHONE_NUMBER>863924736
Last Price Increase: 2023-05-20

Reviewing

I reproduced this on an iPad via Browserstack:
https://github.com/Expensify/App/assets/29386373/75edb36a-9c06-48f8-9b52-c00492d6c161

Added the unresponsive delete workspace button from https://github.com/Expensify/App/issues/19312

Proposal
Please re-state the problem that we are trying to solve in this issue.
Buttons to add attachments, delete workspace, and upload an avatar are unrepsonsive
What is the root cause of that problem?
It was passing props for showing modal while animating for dismissing of PopoverMenu like Delete Workspace, Upload Avatar, Add Attachment. So during proceeding for dismissing of PopoverMenu, showing animation of modal was being ignored.
What changes do you think we should make in order to solve the problem?
We need to add timeout to show main modal during dismissing PopoverMenu.

https://github.com/Expensify/App/assets/17315937/8d280ba2-4854-4c5d-b825-ec85efbd5449
What alternative solutions did you explore? (Optional)
None

Proposal
Please re-state the problem that we are trying to solve in this issue.
'Upload photo', 'Add attachment',  'Delete workspace' buttons are not working.
What is the root cause of that problem?
It's here https://github.com/Expensify/App/blob/737862677811acc2b05c68209a56ecd58bee59f3/src/components/PopoverMenu/index.js#L47 where we're calling selectedItem.onSelected() right inside selectItem, which is called when the MenuItem is pressed.
For the case of 'Upload photo', 'Add attachment',  'Delete workspace' menu items, when the button is pressed it will open another modal when the current PopoverMenu modal doesn't hide completely yet. 2 modals opening at the same time will cause screen freezing in iOS, and the second modal will not show.
This likely comes from this PR where we refactor the PopoverMenu from a class component to a function component.
What changes do you think we should make in order to solve the problem?

We need to call selectedItem.onSelected only inside onModalHide, which is exactly the approach taken in the class component before the mentioned PR is merged.
We need to:

Introduce a new state like selectedItemIndex and set it inside here https://github.com/Expensify/App/blob/737862677811acc2b05c68209a56ecd58bee59f3/src/components/PopoverMenu/index.js#LL44C7-L44C7
In onModalHide, we check if the selectedItemIndex is not null, if yes we call the onSelected of the menu item

props.menuItems[selectedItemIndex].onSelected();

What alternative solutions did you explore? (Optional)
NA

I’m happy to open a PR immediately if assigned.

sure I’ll get a PR up now 💪

@rushatgabhane The PR is ready for review!

PR on staging

@puneetlath @rushatgabhane - Can either of you clarify why this was deployed twice (thus creating two automated Melvin payment hold/checklist posts?) I'm sure it's something obvious but I couldn't really tell looking at the PR

I believe this is a bug when we CPed the PR to staging, speeding up the deployment process. i saw it happen couple of times but the logic there is quite finicky to try to fix this.
You can take the earlier date as valid here

Word, thanks Vit!

Working on finalizing this one today (back from holiday)

That is ... weird. I will try again.


Bad indentation in rasa X 0.42.x documentation

Rasa Open Source version
3.2.2
Rasa SDK version
No response
Python version
3.8
What operating system are you using?
Windows
What happened?
In the Postgres Database Storage section of this page : https://legacy-docs-rasa-x.rasa.com/docs/rasa-x/0.42.x/installation-and-setup/install/docker-compose/#docker-compose-manual-install
The docker docker-compose.override.yml is badly indented and it should be like this :
version: "3.4"
services:
   db:
      volumes:
         - db-volume:/bitnami/postgresql
volumes:
   db-volume:
      name: db-volume

it is also the case for other versions like 1.0.x for example
Command / Request
No response
Relevant log output
No response

Hi @Aymoelle, thanks for pointing this out. Because this is a legacy version of Rasa X that is not maintained anymore, we won't be updating the documentation anymore.


policy: Fix bug with multiple podSelectors in a single section.

Kubernetes network policy allows multiple ingresses (or
multiple egresses) sections. In each ingress section,
it allows multiple podSelectors (it is not clear why it
supports this, as a single podSelector could have multiple
labels instead).
Our current code had a bug when there are multiple
podSelectors in a single ingress section (or egress section).
This was because we were maintaining separate datastructure
that represented each podSelector and held IP addresses of
the pods selected by that podSelector. Each of this would
then write to the same addressSet in OVN database over-writing
each other.
This commit fixes it by providing a single datastructure for
all podSelectors in a ingress (or egress) section. And each
data structure has a one-one relationship with the addressSet
that represents that ingress (or egress) section's peer
podSelectors
Signed-off-by: Gurucharan Shetty<EMAIL_ADDRESS>

/lgtm

Changed the variable names. Merging...


build error: appc/spec/discovery changed InsecureHttp to InsecureHTTP

Error
# github.com/coreos/rkt/rkt/pubkey
rkt/pubkey/pubkey.go:158: undefined: discovery.InsecureHttp

The reason
Some build-errors like this are showing up. This is due to InsecureHttp being called InsecureHTTP. The same goes for InsecureTls, and it's a problem in multiple files within this project.
Some background info
See also https://github.com/appc/spec/commit/761315bba714a0658551d9e4777d42ca7c48e28e
The fix
Replacing all instances of discovery.InsecureHttp to discovery.InsecureHTTP, and discovery.InsecureTls to discovery.InsecureTLS.

I noticed that rkt is using Godeps, which might be why I'm experiencing these build failures, and no-one else is.

Using go build that way may not produce a working binary anyway, because

we are passing a bunch of linker flags to the build setting some variables to some initial values inferred from configuration step
we are using our own GOPATH

Please use ./autogen.sh && ./configure && make -j4. Please refer to https://github.com/coreos/rkt/blob/master/Documentation/build-configure.md for ./configure flags.

There is also a Building rkt section in the Hacking docs, referred from the README.md.
@EtienneBruines Does this work for you?

@alban Once I get #2157 figured out, I think this will work.
Closing this now.


Technologies.DistrictHeatingNetworks.Examples

Both examples have some errors:
checkModel("BuildingSystems.Technologies.DistrictHeatingNetworks.Examples.DistrictHeatingNetwork_dp");
checkModel("BuildingSystems.Technologies.DistrictHeatingNetworks.Examples.DistrictHeatingNetwork_m_flow");

The heat ports of the buildings are not connected properly, might be part of the problem.

closed with 0984591


upgrade mermaid

Is your feature request related to a problem? Please describe.
gantt.sectionFontSize doesn't work for me in mermaid = 8.5.0
Describe the solution you'd like
Allow newer minor version of mermaid, e.g.  ^8.10.1
Describe alternatives you've considered
using a combination of setup/mermaid.ts and !important style rules

Currently we are having some issue with the integration of mermaid greater than v8.5. If you want, maybe you can give it a try and I am more than happy to review the PR. Thanks

But you cannot use gantt.sectionFontSize because the types for mermaid are outdated, or?
Can't you just use this in your stylesheet instead?
.mermaid .sectionTitle > tspan {
  @apply text-sm;
}

the mermaid css is scoped and thus its theme takes precedence. It's possible to use theme: 'null' in mermaid config and link a custom mermaid style in slidev theme, though.


Broken Icons

Application version: 2.6.0
OS: Windows 10

Steps to Reproduce:

Add an application to view the issue. Affected icons include:

Pitchbook
Aircall
Calendly
Outlook Calendar
Scrapbox
Google News
Chromium Code Search
CharlieHR
HireSweet
Payfit
Recruitee
ClickUp
HubStaff
Tinder

Screenshots:
Example of a broken icon shown below:

Thank you for your report.
It's known issue. It will be fixed in 2.7.0

#237


Terminating multiprocessing.Process's with pyzmq in the mix

Hello,
I'm currently using pyzmq to perform some basic distributed computing. To that end, I'm running code that looks something like this:
#!/usr/bin/env python

import sys
import time
import enum
import collections
import socket
import multiprocessing
import zmq

HOSTNAME = socket.gethostname()
WORK = range(10)
TOTAL = len(WORK)

def producer():
    print("Running as producer...")
    context = zmq.Context()
    socket = context.socket(zmq.REP)
    socket.bind("tcp://*:{}".format(5555))
    for idx, i in enumerate(WORK):
        # Wait for a consumer to ask for work.
        socket.recv_pyobj()
        socket.send_pyobj(i)
        sys.stdout.write("\r{} of {} jobs distributed".format(idx + 1, TOTAL))
        sys.stdout.flush()

def consumer():
    def inner():
        print("Running as consumer for `{}`...".format(HOSTNAME))
        context = zmq.Context()
        # Create a socket to receive work items.
        socket_task = context.socket(zmq.REQ)
        socket_task.connect(
            "tcp://{host}:{port}".format(host=HOSTNAME, port=5555))
        # Create a socket to push results downstream.
        socket_result = context.socket(zmq.PUSH)
        socket_result.connect(
            "tcp://{host}:{port}".format(host=HOSTNAME, port=5556))

        # Subscribe to the command socket.
        socket_command = context.socket(zmq.SUB)
        socket_command.connect(
            "tcp://{host}:{port}".format(host=HOSTNAME, port=5557))
        socket_command.setsockopt_string(zmq.SUBSCRIBE, "")

        # Set up a poller to receive tasks/commands.
        poller = zmq.Poller()
        poller.register(socket_task, zmq.POLLIN)
        poller.register(socket_command, zmq.POLLIN)

        while True:
            # Request work.
            socket_task.send_pyobj(None)
            # Poll for requests.
            sockets = dict(poller.poll())
            # Handle a task.
            if sockets.get(socket_task) == zmq.POLLIN:
                # Retrieve work and run the computation.
                params = socket_task.recv_pyobj()
                time.sleep(1)
                result = params
                # Send the result downstream.
                socket_result.send_pyobj(result)
            # Handle a command.
            if sockets.get(socket_command) == zmq.POLLIN:
                cmd = socket_command.recv_pyobj()
                if cmd == "stop":
                    print("Stop command received")
                    # FIXME: Child processes don't seem to terminate here.
                    break

    def Process():
        proc = multiprocessing.Process(target=inner)
        proc.daemon = True
        proc.start()
        return proc
    pool = [Process() for i in range(8)]
    # Zombies are bad for your health.
    for proc in pool:
        proc.join()

def collector():
    print("Running as collector...")

    context = zmq.Context()
    socket_result = context.socket(zmq.PULL)
    socket_result.bind("tcp://*:{}".format(5556))

    socket_command = context.socket(zmq.PUB)
    socket_command.bind("tcp://*:{}".format(5557))

    n_results = 0
    while True:
        result = socket_result.recv_pyobj()
        n_results += 1
        sys.stdout.write(
            "\r{} of {} results collected".format(n_results, TOTAL))
        sys.stdout.flush()
        if n_results == TOTAL:
            break

    # Broadcast a stop instruction to shut down worker processes.
    socket_command.send_pyobj("stop")

def main():
    role = sys.argv[1]
    if role == "producer":
        producer()
    elif role == "collector":
        collector()
    elif role == "consumer":
        consumer()
    else:
        raise SystemExit("Invalid role")

if __name__ == "__main__":
    main()

If I run this on my local machine using
$ python sim.py producer
$ python sim.py collector
$ python sim.py consumer

(in three different terminals of course), everything works fine for the most part. Each process is receiving its work items, and each process successfully transmits its results to the collector. The problem occurs when shutting down the worker processes, which never get joined for some reason. Interrupting the consumer process shows that it is hanging at pid, sts = os.waitpid(self.pid, flag) in multiprocessing/popen_fork.py. The issue seems to be that the producer and collector terminate before the consumer(s) get a chance to. If I add a simple timeout at the end of the producer and consumer functions, every process terminates properly.
Could somebody explain to me why that is, and possibly suggest a more reliable solution than adding a random timeout?

The hang is caused by LINGER behavior on socket_task. At the beginning of every loop, socket_task is sending a ping to request new tasks. The last request from one or more workers is going out after the producer has closed its socket. This means that the request for a new task is waiting in a queue on the workers. The default LINGER behavior is to block Context.term until undelivered messages can be sent. If you set socket_task.linger = 0, it will immediately discard unsent messages.
If you change
socket_task = context.socket(zmq.REQ)

to
socket_task = context.socket(zmq.REQ)
socket_task.linger = 0

you should be set.

That did it! Thanks for the explanation.


Help, what could be the possible reasons for image distortion?

First of all, thank you very much to the author for the open source project! I am facing an issue right now.
I can access the image normally when using front-end resources, but after uploading it to the backend server, when I try to move the view a second time, the image distorts into concentric circles.
Does the image resource need to be returned by a specific service? The backend stores the images in a static resource folder, and I am accessing the folder directly via the backend domain.
normal

error

I've never seen anything that's looked quite like that before. Are there any errors printed to the browser console? Have you tried loading it on different computers or different browsers?

Does the image resource need to be returned by a specific service?

As long as the image can be loaded with JavaScript (e.g., you don't have CORS issues), there's nothing specific.

Apologies for the late response.
The console does not report any errors when the image distorts into a concentric circle. I have tried different browsers and computers, and the issue remains the same.
During debugging, I placed the image in two different locations, both under the ng domain pointing to folders.
One folder is the Vue project where I placed the image in the public directory, and it rotates normally when placed here. The other is a regular folder with no service, just a static folder. When requesting the image resource from this location, the image becomes distorted.
I suspected that it might be due to ng configuring gzip, but the header information and returned image sizes of requests from both paths are consistent.

The browser shows these warnings, but they also appear when the image rotates normally.

While I've never seen perfect concentric circles before, I have seen stripes before. The issue this reminded me of was #323, although it's unrelated, as it was caused by some sort of GPU driver issue, which clearly isn't the case here, since it works for you in some cases and is persistent across devices. In searching for that issue, I did find #852, which shows partial circles. Thinking about it more, I was able to reproduce your circles, by setting yaw to NaN and pitch to -90 (the -90 pitch is what turns the stripes into circles). I also found #757, which while I didn't identify the issue at the time, had similar artifacts caused by setting yaw to a String (since that's what a URL parameter is) instead of a Number, as required.
Based on this and the fact that you reported that the issue only arises when you try to move the view, I don't think it has anything to do with where the image is hosted. I suspect something else is changing in your web app, although somehow triggered by the changing the image hosting location.
What methods have you tried to use to rotate the image? Your screenshots appear to be from a phone, so I assume you've used touch input, but have you also tried to use mouse input or keyboard input?
Do the getYaw() and getPitch() methods return NaN and -90, respectively, as I'm hypothesizing is the case?


--ip-masq should also add masquerade from outer net to flannel net

From email discussion with @thockin:

When accessing a pod (overlay) from a node (native), the routing decision is made before we ever see the packet.  We can add routes for every service as described in prev. email or we can just MASQUERADE. Note that this SNATs to the .0 of the source host.
iptables -t nat -A POSTROUTING -d $FLANNEL_NETWORK ! -s $FLANNEL_SUBNET -j MASQUERADE

In what flannel release can we depend on this fix?
On Mon, Sep 28, 2015 at 10:23 AM, Eugene Yakubovich <
<EMAIL_ADDRESS>wrote:

Closed #318 https://github.com/coreos/flannel/issues/318 via #327
https://github.com/coreos/flannel/pull/327.
—
Reply to this email directly or view it on GitHub
https://github.com/coreos/flannel/issues/318#event-420996333.

@thockin The next one :) There has been a lot of movement in key parts lately (related to more multi-network features) so we need to re-stabilize head and then cut a release. I'm hoping to do a release mid-October.

FYI: there may be unintended consequences to this PR
https://github.com/coreos/flannel/issues/433#issuecomment-222380448


If running 'sudo bp run example.json' Raspberry PI seems sluggish and loses wifi connection

I've installed BiblioPixel 3.4.30 and I have a virtualenv with python 3.5.3 installed. I'm also using the ws281x driver. If it run the test program 'sudo ./test' that came with the ws281x driver I have no issues. However, if I run 'sudo bp run example.json' then the LEDs flash as they should, but I lose my wifi connection after awhile (or immediately if using a VNC connection). When using a keyboard and monitor connected to the Raspberry PI I can still access the OS, but it seems sluggish but bp is still only using 25% cpu and 3% memory. If I Ctrl-C and kill the program it will stop blinking the leds, but the terminal becomes unresponsive. I have to reboot the Raspberry PI to resolve the issue.
example.json file contents:
{
    "animation": {
        "typename": "BiblioPixelAnimations.strip.Rainbows.RainbowCycle"
    },
    "run": {
        "fps": 30
    },
    "driver": {
        "typename": "pi_ws281x",
        "gpio": 18,
        "c_order": "RGB",
        "num": 64
    },
    "layout": {
        "typename": "strip",
        "brightness": 128
    }
 }

Ah, this is a bit disturbing!  Thanks for a nice clear trouble report.  Oh,
and good move with the virtualenv.
I edited the JSON to make Github recognize it as such, hope you don't
mind!  (It's picky - needs a blank line first, and then everything needs to
be indented at least four spaces.)
You're the first report of this.    So lots of questions.

Which Raspberry Pi is it?  Which version of Raspbian is it?

Your frame rate is pretty low right now, and you don't have a huge
number of LEDs - but can you change the fps to a miserable 15 and rerun
it?  This is probably futile but I'd like to see what happens.

bp is still only using 25% cpu and 3% memory.

That's about what I would have expected for this small-ish project.
Basically, bp should take very roughly about 15-20% of a RPi CPU when
"doing nothing", and then an extra 5-10% for this 1920 pixel/second (30fps

64 pixels) animation.  1920 pixels/second sounds like a lot when written
that way, but I've routinely run animations with ~20k pixels/second on a
newer RPI with no troubles.

Blah blah.  tl; dr: "We probably aren't running out of resources, and
that's bad, because it's some unknown systemic issue".
Question:  you are running sudo because this is needed for the ws281x
driver and it won't work otherwise?
Question:  what else have you installed on your system that might
conceivably be running and talking or just listening to the same hardware?
My guess is that there's some sort other process, program, or lock, or
something so both bp and it are trying to talk to the same thing.

Oh, and you can pare down your JSON considerably with the "shape" field,
which 95% of the time means you don't need "layout":
{
    "animation": "$bpa.strip.Rainbows.RainbowCycle",
    "run": {
        "fps": 30
    },
    "driver": {
        "typename": "pi_ws281x",
        "gpio": 18,
        "c_order": "RGB",
    },
    "shape": 64
}

Or if you want to use YAML:
animation: $bpa.strip.Rainbows.RainbowCycle

run:
  fps: 30

driver:
  typename: pi_ws281x
  gpio: 18
  c_order: RGB

shape: 64

--
/t
https://tom.ritchford.com https://tom.ritchford.com
https://tom.swirly.com https://tom.swirly.com

Definitely stay with the virtualenv.  It's the only way to have
reproducible environments, it's a must!
On an RPI, for any hardware project I start with a fresh install because
it's so littel effort just to burn a new card.  And this is definitely
non-usual.
If this fails for you with a known os install, then I'll install exactly
the same version and try to reproduce it!  We do test on RPi but I have one
here with I think almost exactly the same hardware too, so I should be able
to work it out...
On Sat, Oct 27, 2018 at 6:23 PM bmccoard<EMAIL_ADDRESS>wrote:

I'll reload a fresh install of Raspberry PI and see if that helps. Maybe
try without a virtualenv first?

Raspbian GNU/Linux 9 (stretch)
Raspberry PI 3 B+
Yes I'm running sudo because the ws281x driver requires it.
I changed to 10 fps last night but no change.
I had a Django server running, but I've stopped the service and
rebooted but that didn't help. I don't remember installing anything other
than stuff in a virtualenv.

Further observations:

It seems to be messing with the OS and not necessarily a WiFi issue.
After a while I can't click the menu bar at the top of the Rasbian GUI and
some commands stop working like 'ifconfig' and 'sudo halt' and even
'reboot' acts weird because it will halt the system, but not reboot (I have
to power off and back on). Everything works at first, but over little bit
of time OS features seem to die off. Interestingly VNC seems to bring down
WiFi immediately, but if you look at the VNC status bar on Rasbian it shows
everything is ok.

Thanks
—
You are receiving this because you were assigned.
Reply to this email directly, view it on GitHub
https://github.com/ManiacalLabs/BiblioPixel/issues/1027#issuecomment-433634499,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAPdsvQTwqMk6Zuk0-1Q1kBd9ICYS92-ks5upIiEgaJpZM4X9No8
.

--
/t
https://tom.ritchford.com https://tom.ritchford.com
https://tom.swirly.com https://tom.swirly.com

Ok I went super simple. I only installed the latest Rasbian Lite (current download version 9 stretch) using NOOBS. Everything runs fine however my ssh connection dropped out and I can't reconnect after running bp for a few minutes (see exact command at bottom of post). Note rainbowcycle.json contains the exact json code you posted earlier. I made an attempt to document exactly what I did and hopefully I didn't miss a step:
// Followed directions on https://www.raspberrypi.org/forums/viewtopic.php?t=142166 to setup ssh
// Create a SSHFLAG file in /etc
sudo touch /etc/SSHFLAG
// Inserted the following code into etc/rc.local just above the exit 0 line.
if [ -e /etc/SSHFLAG ]; then
/usr/sbin/update-rc.d -f ssh defaults
/bin/rm /etc/SSHFLAG
/sbin/shutdown -r now
fi
// raspberry will reboot then started the ssh service
sudo /etc/init.d/ssh start
// Install apps
sudo apt-get install virtualenv
sudo apt-get install python3-pip
sudo apt-get install git
sudo apt-get install python-dev swig scons
// Create a virtual environment
virtualenv -p /usr/bin/python3 py3env
source py3env/bin/activate
// Install BiblioPixel
pip3 install bibliopixel
// Install rpi_ws281x driver
git clone https://github.com/jgarff/rpi_ws281x.git
cd rpi_ws281x
Run test 'sudo ./test
cd python
// Run sudo in a virtual env
sudo sh -c ". /home/pi/py3env/bin/activate ; python setup.py install"
sudo sh -c ". /home/pi/py3env/bin/activate ; python examples/strandtest.py"
// Now run bp program
cd ~
sudo sh -c ". /home/pi/py3env/bin/activate ; bp run rainbowcycle.json"

Dammit!  (Thanks again for a good trouble report, btw...)
That's so weird.  I was going to write "What does the lighting have to do
with networking?" but then I remembered that all networking goes through
the same hardware that handles USB.  Still, we haven't seen this very
effect before at all.
OK - two other things to try that occurred to me.
Number one, probably pointless but worth asking - do you have enough power
on your Pi?  Are the LEDs being separately powered for sure?
In my experience with this project, a good 80% of the "unexplained
dropouts" problem have to do with inadequate power.  Unfortunately, if you
don't power your LEDs it will often be the case that the LEDs steal power
from the RPi through the USB bus, and then you get weirdnesses.  The usual
first symptom is keyboard issues, and you often see a lightning bolt icon
in your menu bar, but not always.
Number two:  could it be just a problem with the networking itself?
Consider this: https://www.raspberrypi.org/forums/viewtopic.php?t=188891 or
this:
https://raspberrypi.stackexchange.com/questions/79359/ethernet-interface-interrupts-connection
You might want to apply at least the "disable wifi power saving" because
what advantage is that to you anyway?
Funny, we went two months without any bug reports, and now we have three in
the pipeline.  More, at least the other two problems have been there for
many releases, so we didn't have a "regression".
I'll probably have time to deal with this tomorrow.  Sorry I don't have a
good solution yet.
On Sun, Oct 28, 2018 at 12:03 AM bmccoard<EMAIL_ADDRESS>wrote:

Ok I went super simple. I only installed the latest Rasbian Lite (current
download version 9 stretch) using NOOBS. Everything runs fine however my
ssh connection dropped out and I can't reconnect after running bp for a few
minutes (see exact command at bottom of post). Note rainbowcycle.json
contains the exact json code you posted earlier. I made an attempt to
document exactly what I did and hopefully I didn't miss a step:
// Followed directions on
https://www.raspberrypi.org/forums/viewtopic.php?t=142166 to setup ssh
// Create a SSHFLAG file in /etc
sudo touch /etc/SSHFLAG
// Inserted the following code into etc/rc.local just above the exit 0
line.
if [ -e /etc/SSHFLAG ]; then
/usr/sbin/update-rc.d -f ssh defaults
/bin/rm /etc/SSHFLAG
/sbin/shutdown -r now
fi
// raspberry will reboot then started the ssh service
sudo /etc/init.d/ssh start
// Install apps
sudo apt-get install virtualenv
sudo apt-get install python3-pip
sudo apt-get install git
sudo apt-get install python-dev swig scons
// Create a virtual environment
virtualenv -p /usr/bin/python3 py3env
source py3env/bin/activate
// Install BiblioPixel
pip3 install bibliopixel
// Install rpi_ws281x driver
git clone https://github.com/jgarff/rpi_ws281x.git
cd rpi_ws281x
Run test 'sudo ./test
cd python
// Run sudo in a virtual env
sudo sh -c ". /home/pi/py3env/bin/activate ; python setup.py install"
sudo sh -c ". /home/pi/py3env/bin/activate ; python examples/strandtest.py"
// Now run bp program
cd ~
sudo sh -c ". /home/pi/py3env/bin/activate ; bp run rainbowcycle.json"
—
You are receiving this because you were assigned.
Reply to this email directly, view it on GitHub
https://github.com/ManiacalLabs/BiblioPixel/issues/1027#issuecomment-433658648,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAPdsiStrGMaBeGSJwiLC29erCmX3AaFks5upNg1gaJpZM4X9No8
.

--
/t
https://tom.ritchford.com https://tom.ritchford.com
https://tom.swirly.com https://tom.swirly.com

Now, you're sure sure that the RPi is getting enough amps, and the lights
are pulling their own power separately and not through the CPU?
Lack of power is still the only thing I can think of that could cause such
systemic horror - that you turn the lights on and the whole system browns
out and the voltage sags and suddenly system components on the RPi don't
work.
The networking and serial code we use to get information around is pretty
vanilla.  We aren't peeking and poking random memory spots so it's hard to
see how else our code would go Kaiju Big Battel on your whole system!
That would also explain the inability to reboot.  You turn on the lights,
and they stay in an on position (because they don't need a server refresh,
they lock).
I'm going to nip out hopefully this afternoon and get a new card to burn a
copy of your system, I need a new card anyway.
On Mon, Oct 29, 2018 at 12:23 AM bmccoard<EMAIL_ADDRESS>wrote:

I added the following to /etc/rc.local
sleep 10
sudo iwconfig wlan0 power off
I also ran the test with the LEDs disconnected but the system still goes
down. Again this seems larger than just a WiFi issue because as I've said
before other commands have issues. Before I run bp and lose the WiFi
connection the 'sudo reboot' command works fine, but afterward the system
will go down but will not follow through with a reboot. Is it possible this
is a DMA issue? Its interesting that running the 'top' command over a
remote terminal almost instantly brings the ssh connection down. Much like
VNC brought the system down immediately with the full version of Raspian.
—
You are receiving this because you were assigned.
Reply to this email directly, view it on GitHub
https://github.com/ManiacalLabs/BiblioPixel/issues/1027#issuecomment-433752246,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAPdsuqCfKu5c85kQhOS-9xKPePDieOmks5upjyDgaJpZM4X9No8
.

--
/t
https://tom.ritchford.com https://tom.ritchford.com
https://tom.swirly.com https://tom.swirly.com

I ran bp w/out the LEDs connected during my last test. I guess its possible RPi has a bad power supply, but i don't have another one. No overclocking either.

All right, it's up to me to reproduce it or not!  Stay tuned...
On Tue, Oct 30, 2018 at 1:05 AM bmccoard<EMAIL_ADDRESS>wrote:

I ran bp w/out the LEDs connected during my last test. I guess its
possible RPi has a bad power supply, but i don't have another one. No
overclocking either.
—
You are receiving this because you were assigned.
Reply to this email directly, view it on GitHub
https://github.com/ManiacalLabs/BiblioPixel/issues/1027#issuecomment-434124985,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAPdsot8Ze0r6NkTEz8FG8lfk8dgSGG3ks5up5eygaJpZM4X9No8
.

--
/t
https://tom.ritchford.com https://tom.ritchford.com
https://tom.swirly.com https://tom.swirly.com

I keep telling you (see above post) that the problem occurs when NO LEDS ARE CONNECTED - I'm sorry I'm yelling. Meaning the LEDs are not connected in any way to the Raspberry Pi and don't draw any power from it. Even under these circumstances ssh drops out after a few minutes :(. Run the 'top' command in a remote ssh console and ssh seem to die almost immediately. Please see my above post for my EXACT setup. Thanks. Again I'm sorry for yelling. I know you do this pro pono.

I haven't tried out your updated software. I'll try to test that out later today or tomorrow. Thx


CANopenNode on MBED os 5

Hi
I'm working with MBED os 5 on a STM32F091RC (NUCLEO-F091RC) and I'm searching for a CANopenNode implementation which is compatible with MBED os 5.
Or is it possible to just use this configuration: https://github.com/CANopenNode/CANopenNode/blob/master/stack/STM32/CO_driver.c ?
I'm unsure because on the homepage in the table: Microcontroller support there is no status known for STM32.
All tips and tricks are welcome.
Thank you in advance.

Hi,
If you need any pointers to get you started, you can have a look at the LPC1768 implementation which is compatible with Mbed 5.
https://github.com/CANopenNode/CANopenNode/blob/master/stack/LPC1768/CO_driver.cpp
On Fri, Apr 5, 2019 at 4:24 PM +0200, "geobruce"<EMAIL_ADDRESS>wrote:
Hi
I'm working with MBED os 5 on a STM32F091RC (NUCLEO-F091RC) and I'm searching for a CANopenNode implementation which is compatible with MBED os 5.
Or is it possible to just use this configuration: https://github.com/CANopenNode/CANopenNode/blob/master/stack/STM32/CO_driver.c ?
I'm unsure because on the homepage in the table: Microcontroller support there is no status known for STM32.
All tips and tricks are welcome.
Thank you in advance.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.

Hi, If you need any pointers to get you started, you can have a look at the LPC1768 implementation which is compatible with Mbed 5. https://github.com/CANopenNode/CANopenNode/blob/master/stack/LPC1768/CO_driver.cpp

Thank you I'll have a look at it. Is there somewhere else some documentation on how to use the library?

Issue is covered here: https://github.com/Alphatronics/CANopenNode/tree/mbedSTM32
please close

please add your driver to the wiki https://github.com/CANopenNode/CANopenNode/wiki when finished, so others can find it.


Code cleanup

I got all excited and couldn't help myself... This does some general code cleanup/maintenance in preparation for some actual fixes and changes. I think the commit names captured what it does pretty well, but pleonasm is a fun word, so here's a repeat:

Format code using latest version of elm-format
Run elm-analyze and fix all errors
Replace krisajenkins/elm-exts with local code and elm-community/maybe-extra (sorry :innocent: )

Worth noting that the build failed due to an HTTP request failing, not because the code is necessarily broken. I can't trigger rebuilds, so can't make the check succeed, but make exits correctly on my local system.
Error: The following HTTP request failed.
<https://github.com/elm-community/elm-test/zipball/3.1.0/>
FailedConnectionException "github.com" 443


Images are not being placed

I'm unable to get any of the generators to place an image on the artboard or in a group. I've tried on Yosemite and Mavericks with the latest version of Sketch.

@nolastan This is likely due to changes in the Sketch Plugin format in the latest–3.3 version. I'm taking a look at what is needed to get it updated.

@nolastan This is fixed in 2.0.0 https://github.com/tylergaw/day-player/releases/tag/v2.0.0


Suggestion to use Closure Compiler for Ahead of Time Compilation

Suggestion to use Closure Compiler for Ahead of Time Compilation after generating ngfactory files.
OS?
Windows 10
Versions
angular-cli: 1.0.0-beta.19
node: 6.9.1
I am sure Angular CLI team is working hard on the features like AoT with support for Lazy Loading.
While you finalize this feature, I wanted to suggest you to use Closure Compiler after generating ngfactory files using ngc, because it seems to be the only tool that would transpile the ES2015 Rollup Bundle to ES5 with 100% reliability.
While compiling large projects with ngc (after generating ngfactory), it returns Heep Errors. Please have a look at:
https://github.com/angular/angular/issues/12184
I came across this repository, https://github.com/steveblue/angular2-rollup and in Production notes it explains why Closure Compile is a better option. Please have a look at:
https://github.com/steveblue/angular2-rollup#production
When using Angular CLI in my current project:
If I use lazy loading and build with --prod --aot, it just generate main bundle and when I run it returns missing module error.
If I remove lazyloading and build with --prod --aot, its returns same heep error which I mentioned above.

+1 recorded.
Some related discussion from the Angular repo https://github.com/angular/angular/issues/8550

@filipesilva is there a short or long term plan to support closure's advanced optimization?

We've been looking at ways we can add it but so far there isn't any viable solution.

If you are interested in following the progress, better subscribe to the Closure support issue in Angular itself (https://github.com/angular/angular/issues/8550).
I suppose nothing can happen here before that is closed and released.

4.0 just announced experimental support for closure compiler for the framework itself I suppose...

Yes, here are the details, http://angularjs.blogspot.com/2017/03/angular-400-now-available.html .
But it says that "All of our code now has Closure annotations" are they referring to the angular code or the code aot compiler generates. Does it mean that our custom components, directives etc should also have closure Annotations? and same goes for the angular plugins as well?

The only reason I refuse to use the CLI for Enterprise projects is because it does not support ClosureCompiler. During ng-conf it was announced that internal teams at Google validate the latest versions of Angular and these teams are using ClosureCompiler. I would feel way more comfortable using a similar build process that replicates how teams at Google bundle Angular web apps. Webpack may be the popular option, but there could be smaller bundles produced through other methods and more optimal code splitting. The core team is already experimenting with going straight from AOT => ClosureCompiler (https://github.com/alexeagle/closure-compiler-angular-bundling). It would be nice if the CLI would support this and Code Splitting.

hope we can see this one day in cli, actually bundle i know there is gzip but even

It seems like it is working not with rxjs https://github.com/angular/closure-demo

There is limited support for AOT => ClosureCompiler and third party libraries ATM but that will change over time.

Hi everyone, any updates on this?
https://github.com/angular/angular/issues/8550 was closed early this year.
I see all the demo repos but they use ngc directly, and not angular-cli. Is there a way to include closure compiler on the building pipe?
Cheers!

+1 on the request for updates. After all the work that went into Closure support and fanfare around it during the 4.0 release, I was surprised to see The Past, Present, and Future of the Angular CLI not even acknowledge this.

We're reworking the entire build chain, so closing this.

@hansl could you give us some related issues to the refactoring the team is working on? I've been following this for a while and would like to see where it goes. :)

Any update on this?


How to generate a set of UML diagrams of an existing project in Enterprise-Architect?

How to generate a set of UML diagrams of an existing project in Enterprise-Architect?
For example, I took a project.
https://github.com/NBull92/Northwind-MVVM-Survival-Guide/
I get the result as in the picture.
This is Class Diagrams.
How to generate diagrams:

Activity Diagrams
Component Diagrams
Sequence Diagrams
Use Case Diagrams

How do I generate all or part of the charts?
I didn't find the Enterprise-Architect documentation where it was well described.
I couldn't quite figure it out.
=== === === === === === === ===
Note.
Sorry for writing to you by Email.
I found your Email by the principle: github.com > mdd4all.de
I am studying C# programming.
I'm trying to deal with Enterprise-Architect.
Pic1

I am super confused by your question as it has nothing to do with this repository... You might better ask this question in the Enterprise Architect forums.
You cannot automatically generate diagrams from thin air, how is that supposed to work? In order to create a new diagram, you can simply click the "New Diagram" button at the top of the project browser (left in your screenshot). Then select your diagram type and start modeling.
But I cannot give any more help here as it's completely unrelated to this repo and I am thus closing this issue. As I said, you might better ask this question in the Enterprise Architect forums.


Patch not showing up for some missions

Closing this issue because it wasn't my code but the picture was just unavailable at the time from api.


Update cookie anytime getUser is called.

Description
I made few changes to user's metadata by supabase.auth.api.updateUserById. Then to refresh changes tried with supabase.auth.refreshSession.
This refreshes the supabase.auth.token in localstorage, but the user returned from useSupaUser still has data from cached JWT.

Note: supabase-auth-helper returns a note - Get latest user data instead of stale one from cached JWT use getUser in serverside context. I can able to get new user, but shouldn't the expected behaviour also refreshes the cached JWT if I called getUser ?

As per the note, you will need to call getUser to force a refresh of the cached user cookie.

As per the note, you will need to call getUser to force a refresh of the cached user cookie.

Yes, I have tried using getUser in server side context via help note returned. I can able to get the update user_metadata in the current page. But when I navigate to the next page, I still get the old data. Should the cache be invalidated since I invoked getUser in the previous page?

Should the cache be invalidated since I invoked getUser in the previous page?

Yes, calling getUser should set the cookie, but I just checked and it only sets the cookie when the access token is expired, we need to update this to also set the cookie when the access token is still valid: https://github.com/supabase-community/supabase-auth-helpers/blob/next/src/nextjs/utils/getUser.ts#L84-L90
thanks for flagging!

Actually, unfortunately we won't get the new access token until it is getting refreshed. Therefore You'd need to always call getUser when you need up validate the user_metadata.
Alternatively, from version 1.4.0 onward you will be able to call supabase.auth.refreshSession() client-side to refresh the JWT & user object throughout.


[Core]: Relevance Score Scaling Issue

Thank you for contributing to LangChain!
Description:
- The normalization of scores for different Distance Strategies sometimes results in values less than 0, which raises the warning that relevance scores should be between 0 and 1. To address this issue, I have modified the relevance score normalization process to ensure that it never produces values less than zero for every Distance Strategy. I am uncertain about the reason behind the normalized score becoming less than zero, but it was observed to occur in the FIAAS Vector store, as highlighted in the reported issue.
Issue:  #18709

This will require a deeper investigation before we can merge.
I don't think that we actually want to apply max/min to scores since that throws out information unless there's a valid reason why that makes sense to do

@eyurtsev should I keep the PR opened or close it then?

I agree with @eyurtsev - we should not discard information through truncation. Unexpected values are usually a sign of an incorrect assumption somewhere, and that root cause should be fixed.
For FAISS, the negative relevance scores occur because FAISS returns distance-squared values, which Langchain's default distance-to-relevance equation handles incorrectly. I posted the required distance-squared remapping function here.
Chroma DB also has this issue. I updated #18709 accordingly.


Snapshot pg_stat_progres_* views?

The (current) list of views is:

pg_stat_progress_vacuum (9.6+)
pg_stat_progress_create_index (12+)
pg_stat_progress_cluster (12+)
pg_stat_progress_analyze (13+)
pg_stat_progress_basebackup (13+)

Should we snapshot all of them?  Note that they only expose oids, so without a remote database access from UI (or a copy of the remote database's catalog), I'm afraid that it won't be that useful.

Hi rjuju,
On a first though, I don't find this feature very useful. Maybe it's helpful to know that you have a VACUUM or CREATE INDEX running for a long time and having a performance impact on the production. But this can be achieved with some other monitoring system (check_pga, etc.).
Hope it helps

Yeah, same point of view for me. I don't feel this belongs to powa, it's going to be hard to integrate to what the tool is right now

Ok, I'll close this as wonfix then.  Thanks for the feedback.


Implement persistent CursorManager

Based on etcd, redis or a relational db. Should also allow coordination between multiple nodes reading from different partitions.

Implemented PersistentCursorManager. Coordination between nodes has to be handled outside the library for now.


Bug: cyclic dependency with tomli==1.2.1 and flit_core==3.2.0

I can not download tomli because there is a cyclic dependency with flit_core.
Reproducer:
python3.9 -m venv test
./test/bin/pip download --no-binary=":all:"  tomli  # fails
./test/bin/pip download --no-binary=":all:" flit_core # fails

Example output:
Collecting tomli
  File was already downloaded XXX/tomli-1.2.1.tar.gz
  Installing build dependencies ... error
  ERROR: Command errored out with exit status 2:
   command: XXX/test/lib/python3.9/site-packages/pip install --ignore-installed --no-user --prefix /tmp/pip-build-env-91g152mw/overlay --no-warn-script-location --no-binary :all: --only-binary :none: -i https://pypi.org/simple -- 'flit_core>=3.2.0,<4'
       cwd: None
  Complete output (31 lines):
  Collecting flit_core<4,>=3.2.0
    Downloading flit_core-3.4.0.tar.gz (27 kB)
    Getting requirements to build wheel: started
    Getting requirements to build wheel: finished with status 'done'
      Preparing wheel metadata: started
      Preparing wheel metadata: finished with status 'done'
  Collecting tomli
    Downloading tomli-1.2.1.tar.gz (14 kB)
  ERROR: Exception:
  Traceback (most recent call last):
    File "XXX/test/lib/python3.9/site-packages/pip/_internal/cli/base_command.py", line 186, in _main
      status = self.run(options, args)
    File "XXX/test/lib/python3.9/site-packages/pip/_internal/commands/install.py", line 357, in run
      resolver.resolve(requirement_set)
    File "XXX/test/lib/python3.9/site-packages/pip/_internal/legacy_resolve.py", line 177, in resolve
      discovered_reqs.extend(self._resolve_one(requirement_set, req))
    File "XXX/test/lib/python3.9/site-packages/pip/_internal/legacy_resolve.py", line 333, in _resolve_one
      abstract_dist = self._get_abstract_dist_for(req_to_install)
    File "XXX/test/lib/python3.9/site-packages/pip/_internal/legacy_resolve.py", line 282, in _get_abstract_dist_for
      abstract_dist = self.preparer.prepare_linked_requirement(req)
    File "XXX/test/lib/python3.9/site-packages/pip/_internal/operations/prepare.py", line 515, in prepare_linked_requirement
      abstract_dist = _get_prepared_distribution(
    File "XXX/test/lib/python3.9/site-packages/pip/_internal/operations/prepare.py", line 94, in _get_prepared_distribution
      with req_tracker.track(req):
    File "/usr/lib/python3.9/contextlib.py", line 117, in __enter__
      return next(self.gen)
    File "XXX/test/lib/python3.9/site-packages/pip/_internal/req/req_tracker.py", line 148, in track
      self.add(req)
    File "XXX/test/lib/python3.9/site-packages/pip/_internal/req/req_tracker.py", line 115, in add
      raise LookupError(message)
  LookupError: https://files.pythonhosted.org/packages/75/50/973397c5ba854445bcc396b593b5db1958da6ab8d665b27397daa1497018/tomli-1.2.1.tar.gz#sha256=a5b75cb6f3968abb47af1b40c1819dc519ea82bcc065776a866e8d74c5ca9442 (from https://pypi.org/simple/tomli/) (requires-python:>=3.6) is already being built: tomli from https://files.pythonhosted.org/packages/75/50/973397c5ba854445bcc396b593b5db1958da6ab8d665b27397daa1497018/tomli-1.2.1.tar.gz#sha256=a5b75cb6f3968abb47af1b40c1819dc519ea82bcc065776a866e8d74c5ca9442
  ----------------------------------------
ERROR: Command errored out with exit status 2: XXX/test/bin/python3.9 XXX/test/lib/python3.9/site-packages/pip install --ignore-installed --no-user --prefix /tmp/pip-build-env-91g152mw/overlay --no-warn-script-location --no-binary :all: --only-binary :none: -i https://pypi.org/simple -- 'flit_core>=3.2.0,<4' Check the logs for full command output.

I don't think this is a Tomli issue. You may want to look into bootstraping the foundational build/installer packages https://flit.readthedocs.io/en/latest/bootstrap.html

I agree, to some extend this is a problem with pip download installing build-dependencies even though I only requested to download a source-package (without building it).
But even installing flit_core does not help. The following still reproduces the problem. Only --no-build-isolation helps.
~ ➤ python3.9 -m venv test
~ ➤ ./test/bin/pip install flit_core
~ ➤ ./test/bin/pip download --no-binary=":all:" tomli # fails
~ ➤ ./test/bin/pip download --no-binary=":all:" tomli --no-build-isolation # works

But I am fine with having this closed. Although some part of me wishes for stricter dependency requirements so that problems like this don't happen again.


Added a side column for skills

I added a template version with a side column (1/4 of the page) containing the skills for a more heterogeneous visualization and to fit more content in a page.
I kept the old and new visualizations of the skills separate, as well as the cv templates (the new one named cv_twocol.tex under examples).
Please let me know if you appreciate the idea or if you think anything should be improved.

This commit adds a large left margin on all the pages in the document. I don't think this is desired behaviour.