No video feed at system boot

Bug report, debug log and your config file (FULL LOGS ARE MANDATORY)

2024-05-14T05:54:58.076Z [CORE] TTY is not attached to the log output
2024-05-14T05:54:58.129Z [MAIN] Database path: '/home/andrea/.hyperhdr/db/hyperhdr.db', readonlyMode = disabled
2024-05-14T05:54:58.132Z [MAIN] Starting HyperHdr - <IP_ADDRESS>, (HEAD detached at v<IP_ADDRESS>) (awawa-dev-9e960c9/52f12b4-1711236142), built: Mar 23 2024:23:58:38
2024-05-14T05:54:58.132Z [MAIN] Set user data path to '/home/andrea/.hyperhdr'
2024-05-14T05:54:58.135Z [INSTANCE_CFG] Loading instance configuration
2024-05-14T05:54:58.193Z [DB] Database opened: /home/andrea/.hyperhdr/db/hyperhdr.db
2024-05-14T05:54:58.229Z [INSTANCE_CFG] Settings database initialized
2024-05-14T05:54:58.251Z [SOUND_GRABBER] Sound device is disabled
2024-05-14T05:54:58.362Z [JSONSERVER] (JsonServer.cpp:26) Created new instance
2024-05-14T05:54:58.366Z [JSONSERVER] Started on port 19444
2024-05-14T05:54:58.367Z [SSDP] (SSDPHandler.cpp:31) SSDPHandler is initialized
2024-05-14T05:54:58.309Z [V4L2:USB3.0 UHD: US] (GrabberWrapper.cpp:55) Starting the grabber wrapper
2024-05-14T05:54:58.309Z [V4L2:USB3.0 UHD: US] Found capture device: /dev/video15
2024-05-14T05:54:58.309Z [V4L2:USB3.0 UHD: US] Found capture device: /dev/video21
2024-05-14T05:54:58.310Z [V4L2:USB3.0 UHD: US] Found capture device: /dev/video14
2024-05-14T05:54:58.310Z [V4L2:USB3.0 UHD: US] Found capture device: /dev/video22
2024-05-14T05:54:58.311Z [X11_SYSTEM:AUTO] Loaded X11 proxy library for screen capturing
2024-05-14T05:54:58.315Z [HYPERHDR0] Starting the instance
2024-05-14T05:54:58.315Z [DAEMON] The system doesn't support the X11 system grabber
2024-05-14T05:54:58.315Z [INSTANCE_CFG0] Loading instance configuration
2024-05-14T05:54:58.316Z [DAEMON] The system doesn't support the framebuffer system grabber
2024-05-14T05:54:58.316Z [DB] Database opened: /home/andrea/.hyperhdr/db/hyperhdr.db
2024-05-14T05:54:58.316Z [X11_SYSTEM:auto] (SystemWrapper.cpp:71) Closing grabber: X11_SYSTEM:auto
2024-05-14T05:54:58.316Z [FRAMEBUF_SYSTEM:auto] (SystemWrapper.cpp:71) Closing grabber: FRAMEBUF_SYSTEM:auto
2024-05-14T05:54:58.372Z [INSTANCE_CFG0] Settings database initialized
2024-05-14T05:54:58.372Z [COMPONENTCTRL0] (ComponentController.cpp:31) ComponentController is initialized. Components are ENABLED
2024-05-14T05:54:58.375Z [MUXER0] (Muxer.cpp:55) Muxer initialized
2024-05-14T05:54:58.375Z [BLACKBORDER] Set mode to: default
2024-05-14T05:54:58.375Z [COMPONENTCTRL0] Blackborder detector: enabled
2024-05-14T05:54:58.376Z [IMAGETOLED_MNG0] (ImageToLedManager.cpp:192) Set LED mapping type to advanced
2024-05-14T05:54:58.376Z [IMAGETOLED_MNG0] (ImageToLedManager.cpp:176) setSparseProcessing to 0
2024-05-14T05:54:58.376Z [IMAGETOLED_MNG0] (ImageToLedManager.cpp:103) ImageToLedManager initialized
2024-05-14T05:54:58.379Z [COLORSPACE_CALIBRATION0] classicMode: no, gammas:[1.50, 1.50, 1.50], saturation: 1.00, luminance: 1.00, backLight: [enabled, threshold: 0, colored: no]
2024-05-14T05:54:58.379Z [LED_CALIBRATION0] (LedCalibration.cpp:101) Calibration config '0' for LED segment: [0, 223]
2024-05-14T05:54:58.381Z [HYPERHDR0] Led strip RGB order is: rgb
2024-05-14T05:54:58.382Z [SMOOTHING0] High resolution clock is NOT STEADY!
2024-05-14T05:54:58.382Z [SMOOTHING0] Clearing queued colors before: enabling
2024-05-14T05:54:58.382Z [SMOOTHING0] Smoothing queue is cleared
2024-05-14T05:54:58.382Z [COMPONENTCTRL0] Smoothing: enabled
2024-05-14T05:54:58.382Z [SMOOTHING0] Creating config (0) => type: Alternative, dirMode: false, pause: false, settlingTime: 150ms, interval: 10ms (100Hz), antiFlickTres: 32, antiFlickStep: 2, antiFlickTime: 250
2024-05-14T05:54:58.382Z [SMOOTHING0] Clearing queued colors before: enabling. Smoothing configuration changed: restarting timer.
2024-05-14T05:54:58.382Z [SMOOTHING0] Smoothing queue is cleared
2024-05-14T05:54:58.382Z [SMOOTHING0] Selecting config (0) => type: Alternative, directMode: false, pause: false, settlingTime: 150ms, interval: 10ms (100Hz), antiFlickTres: 32, antiFlickStep: 2, antiFlickTime: 250
2024-05-14T05:54:58.382Z [SMOOTHING0] Selecting config (0) => type: Alternative, directMode: false, pause: false, settlingTime: 150ms, interval: 10ms (100Hz), antiFlickTres: 32, antiFlickStep: 2, antiFlickTime: 250
2024-05-14T05:54:58.383Z [LEDDEVICE0_AWA_SPI] Start LedDevice 'awa_spi'.
2024-05-14T05:54:58.383Z [LEDDEVICE0_AWA_SPI] (LedDevice.cpp:337) deviceConfig: [{"colorOrder":"rgb","currentLedCount":224,"invert":false,"output":"/dev/spidev0.0","rate":25000000,"refreshTime":10,"smoothingRefreshTime":10,"spitype":"esp32","type":"awa_spi","white_channel_calibration":false}]
2024-05-14T05:54:58.383Z [LEDDEVICE0_AWA_SPI] Ignoring user LED refresh rate. Forcing smoothing refresh rate = 100.00 Hz
2024-05-14T05:54:58.383Z [LEDDEVICE0_AWA_SPI] (LedDevice.cpp:423) Refresh rate = 100.00 Hz
2024-05-14T05:54:58.383Z [LEDDEVICE0_AWA_SPI] (LedDevice.cpp:373) Device is not ready to start a timer
2024-05-14T05:54:58.383Z [LEDDEVICE0_AWA_SPI] (LedDevice.cpp:433) Refresh interval updated to 10ms
2024-05-14T05:54:58.383Z [LEDDEVICE0_AWA_SPI] (ProviderSpi.cpp:52) Speed: 25000000, Type: esp32
2024-05-14T05:54:58.383Z [LEDDEVICE0_AWA_SPI] (ProviderSpi.cpp:53) Inverted: no, Mode: 0
2024-05-14T05:54:58.383Z [LEDDEVICE0_AWA_SPI] The refresh timer is enabled ('Refresh time' > 0) and may limit the performance of the LED driver. Ignore this error if you set it on purpose for some reason (but you almost never need it).
2024-05-14T05:54:58.383Z [LEDDEVICE0_AWA_SPI] (LedDeviceAWA_spi.cpp:52) SPI driver with data integration check AWA protocol
2024-05-14T05:54:58.383Z [LEDDEVICE0_AWA_SPI] (LedDeviceAWA_spi.cpp:60) SPI header for 224 leds: Awa 0x00 0xdf 0x8a
2024-05-14T05:54:58.383Z [LEDDEVICE0_AWA_SPI] (LedDevice.cpp:247) Enable the device
2024-05-14T05:54:58.384Z [LEDDEVICE0_AWA_SPI] (LedDevice.cpp:64) Switch on
2024-05-14T05:54:58.384Z [LEDDEVICE0_AWA_SPI] (LedDevice.cpp:140) Power On
2024-05-14T05:54:58.384Z [LEDDEVICE0_AWA_SPI] (LedDevice.cpp:367) Starting timer with interval = 10ms
2024-05-14T05:54:58.384Z [HYPER_MANAGER] HyperHDR instance 'Blacky' has been started
2024-05-14T05:54:58.384Z [HYPERHDR0] The instance is running
2024-05-14T05:54:58.384Z [MUXER0] Register new input 'System/VIDEOGRABBER' with priority 240 as inactive
2024-05-14T05:54:58.384Z [COMPONENTCTRL0] Video capture device: enabled
2024-05-14T05:54:58.384Z [COMPONENTCTRL0] LED device: enabled
2024-05-14T05:54:58.384Z [SMOOTHING0] Using alternative smoothing input (0)
2024-05-14T05:54:58.404Z [SMOOTHING0] Using alternative smoothing procedure (0)
2024-05-14T05:54:58.421Z [V4L2:USB3.0 UHD: US] Found capture device: /dev/video0
2024-05-14T05:54:58.434Z [V4L2:USB3.0 UHD: US] (V4L2Grabber.cpp:406) Device has 'brightness' control => min: 0, max: 100, default: 50
2024-05-14T05:54:58.449Z [V4L2:USB3.0 UHD: US] (V4L2Grabber.cpp:412) Device has 'contrast' control => min: 0, max: 100, default: 50
2024-05-14T05:54:58.462Z [V4L2:USB3.0 UHD: US] (V4L2Grabber.cpp:418) Device has 'saturation' control => min: 0, max: 100, default: 50
2024-05-14T05:54:58.475Z [V4L2:USB3.0 UHD: US] (V4L2Grabber.cpp:424) Device has 'hue' control => min: 0, max: 100, default: 50
2024-05-14T05:54:58.476Z [V4L2:USB3.0 UHD: US] USB3.0 UHD: USB3.0 UHD (video0) [/dev/video0] 1920 x 1080 @ 60 fps yuyv input 0
2024-05-14T05:54:58.476Z [V4L2:USB3.0 UHD: US] USB3.0 UHD: USB3.0 UHD (video0) [/dev/video0] 1920 x 1080 @ 50 fps yuyv input 0
2024-05-14T05:54:58.476Z [V4L2:USB3.0 UHD: US] USB3.0 UHD: USB3.0 UHD (video0) [/dev/video0] 1920 x 1080 @ 30 fps yuyv input 0
2024-05-14T05:54:58.476Z [V4L2:USB3.0 UHD: US] USB3.0 UHD: USB3.0 UHD (video0) [/dev/video0] 1920 x 1080 @ 20 fps yuyv input 0
2024-05-14T05:54:58.476Z [V4L2:USB3.0 UHD: US] USB3.0 UHD: USB3.0 UHD (video0) [/dev/video0] 1920 x 1080 @ 10 fps yuyv input 0
2024-05-14T05:54:58.476Z [V4L2:USB3.0 UHD: US] USB3.0 UHD: USB3.0 UHD (video0) [/dev/video0] 1600 x 1200 @ 60 fps yuyv input 0
2024-05-14T05:54:58.476Z [V4L2:USB3.0 UHD: US] USB3.0 UHD: USB3.0 UHD (video0) [/dev/video0] 1600 x 1200 @ 50 fps yuyv input 0
2024-05-14T05:54:58.476Z [V4L2:USB3.0 UHD: US] USB3.0 UHD: USB3.0 UHD (video0) [/dev/video0] 1600 x 1200 @ 30 fps yuyv input 0
2024-05-14T05:54:58.476Z [V4L2:USB3.0 UHD: US] USB3.0 UHD: USB3.0 UHD (video0) [/dev/video0] 1600 x 1200 @ 20 fps yuyv input 0
2024-05-14T05:54:58.476Z [V4L2:USB3.0 UHD: US] USB3.0 UHD: USB3.0 UHD (video0) [/dev/video0] 1600 x 1200 @ 10 fps yuyv input 0
2024-05-14T05:54:58.476Z [V4L2:USB3.0 UHD: US] USB3.0 UHD: USB3.0 UHD (video0) [/dev/video0] 1360 x 768 @ 60 fps yuyv input 0
2024-05-14T05:54:58.476Z [V4L2:USB3.0 UHD: US] USB3.0 UHD: USB3.0 UHD (video0) [/dev/video0] 1360 x 768 @ 50 fps yuyv input 0
2024-05-14T05:54:58.476Z [V4L2:USB3.0 UHD: US] USB3.0 UHD: USB3.0 UHD (video0) [/dev/video0] 1360 x 768 @ 30 fps yuyv input 0
2024-05-14T05:54:58.476Z [V4L2:USB3.0 UHD: US] USB3.0 UHD: USB3.0 UHD (video0) [/dev/video0] 1360 x 768 @ 20 fps yuyv input 0
2024-05-14T05:54:58.476Z [V4L2:USB3.0 UHD: US] USB3.0 UHD: USB3.0 UHD (video0) [/dev/video0] 1360 x 768 @ 10 fps yuyv input 0
2024-05-14T05:54:58.476Z [V4L2:USB3.0 UHD: US] USB3.0 UHD: USB3.0 UHD (video0) [/dev/video0] 1280 x 1024 @ 60 fps yuyv input 0
2024-05-14T05:54:58.476Z [V4L2:USB3.0 UHD: US] USB3.0 UHD: USB3.0 UHD (video0) [/dev/video0] 1280 x 1024 @ 50 fps yuyv input 0
2024-05-14T05:54:58.476Z [V4L2:USB3.0 UHD: US] USB3.0 UHD: USB3.0 UHD (video0) [/dev/video0] 1280 x 1024 @ 30 fps yuyv input 0
2024-05-14T05:54:58.476Z [V4L2:USB3.0 UHD: US] USB3.0 UHD: USB3.0 UHD (video0) [/dev/video0] 1280 x 1024 @ 20 fps yuyv input 0
2024-05-14T05:54:58.478Z [V4L2:USB3.0 UHD: US] USB3.0 UHD: USB3.0 UHD (video0) [/dev/video0] 1280 x 1024 @ 10 fps yuyv input 0
2024-05-14T05:54:58.478Z [V4L2:USB3.0 UHD: US] USB3.0 UHD: USB3.0 UHD (video0) [/dev/video0] 1280 x 960 @ 60 fps yuyv input 0
2024-05-14T05:54:58.478Z [V4L2:USB3.0 UHD: US] USB3.0 UHD: USB3.0 UHD (video0) [/dev/video0] 1280 x 960 @ 50 fps yuyv input 0
2024-05-14T05:54:58.478Z [V4L2:USB3.0 UHD: US] USB3.0 UHD: USB3.0 UHD (video0) [/dev/video0] 1280 x 960 @ 30 fps yuyv input 0
2024-05-14T05:54:58.478Z [V4L2:USB3.0 UHD: US] USB3.0 UHD: USB3.0 UHD (video0) [/dev/video0] 1280 x 960 @ 20 fps yuyv input 0
2024-05-14T05:54:58.478Z [V4L2:USB3.0 UHD: US] USB3.0 UHD: USB3.0 UHD (video0) [/dev/video0] 1280 x 960 @ 10 fps yuyv input 0
2024-05-14T05:54:58.478Z [V4L2:USB3.0 UHD: US] USB3.0 UHD: USB3.0 UHD (video0) [/dev/video0] 1280 x 720 @ 60 fps yuyv input 0
2024-05-14T05:54:58.478Z [V4L2:USB3.0 UHD: US] USB3.0 UHD: USB3.0 UHD (video0) [/dev/video0] 1280 x 720 @ 50 fps yuyv input 0
2024-05-14T05:54:58.478Z [V4L2:USB3.0 UHD: US] USB3.0 UHD: USB3.0 UHD (video0) [/dev/video0] 1280 x 720 @ 30 fps yuyv input 0
2024-05-14T05:54:58.478Z [V4L2:USB3.0 UHD: US] USB3.0 UHD: USB3.0 UHD (video0) [/dev/video0] 1280 x 720 @ 20 fps yuyv input 0
2024-05-14T05:54:58.478Z [V4L2:USB3.0 UHD: US] USB3.0 UHD: USB3.0 UHD (video0) [/dev/video0] 1280 x 720 @ 10 fps yuyv input 0
2024-05-14T05:54:58.478Z [V4L2:USB3.0 UHD: US] USB3.0 UHD: USB3.0 UHD (video0) [/dev/video0] 1024 x 768 @ 60 fps yuyv input 0
2024-05-14T05:54:58.478Z [V4L2:USB3.0 UHD: US] USB3.0 UHD: USB3.0 UHD (video0) [/dev/video0] 1024 x 768 @ 50 fps yuyv input 0
2024-05-14T05:54:58.478Z [V4L2:USB3.0 UHD: US] USB3.0 UHD: USB3.0 UHD (video0) [/dev/video0] 1024 x 768 @ 30 fps yuyv input 0
2024-05-14T05:54:58.478Z [V4L2:USB3.0 UHD: US] USB3.0 UHD: USB3.0 UHD (video0) [/dev/video0] 1024 x 768 @ 20 fps yuyv input 0
2024-05-14T05:54:58.478Z [V4L2:USB3.0 UHD: US] USB3.0 UHD: USB3.0 UHD (video0) [/dev/video0] 1024 x 768 @ 10 fps yuyv input 0
2024-05-14T05:54:58.478Z [V4L2:USB3.0 UHD: US] USB3.0 UHD: USB3.0 UHD (video0) [/dev/video0] 800 x 600 @ 60 fps yuyv input 0
2024-05-14T05:54:58.478Z [V4L2:USB3.0 UHD: US] USB3.0 UHD: USB3.0 UHD (video0) [/dev/video0] 800 x 600 @ 50 fps yuyv input 0
2024-05-14T05:54:58.478Z [V4L2:USB3.0 UHD: US] USB3.0 UHD: USB3.0 UHD (video0) [/dev/video0] 800 x 600 @ 30 fps yuyv input 0
2024-05-14T05:54:58.478Z [V4L2:USB3.0 UHD: US] USB3.0 UHD: USB3.0 UHD (video0) [/dev/video0] 800 x 600 @ 20 fps yuyv input 0
2024-05-14T05:54:58.478Z [V4L2:USB3.0 UHD: US] USB3.0 UHD: USB3.0 UHD (video0) [/dev/video0] 800 x 600 @ 10 fps yuyv input 0
2024-05-14T05:54:58.478Z [V4L2:USB3.0 UHD: US] USB3.0 UHD: USB3.0 UHD (video0) [/dev/video0] 720 x 576 @ 60 fps yuyv input 0
2024-05-14T05:54:58.478Z [V4L2:USB3.0 UHD: US] USB3.0 UHD: USB3.0 UHD (video0) [/dev/video0] 720 x 576 @ 50 fps yuyv input 0
2024-05-14T05:54:58.478Z [V4L2:USB3.0 UHD: US] USB3.0 UHD: USB3.0 UHD (video0) [/dev/video0] 720 x 576 @ 30 fps yuyv input 0
2024-05-14T05:54:58.478Z [V4L2:USB3.0 UHD: US] USB3.0 UHD: USB3.0 UHD (video0) [/dev/video0] 720 x 576 @ 20 fps yuyv input 0
2024-05-14T05:54:58.478Z [V4L2:USB3.0 UHD: US] USB3.0 UHD: USB3.0 UHD (video0) [/dev/video0] 720 x 576 @ 10 fps yuyv input 0
2024-05-14T05:54:58.478Z [V4L2:USB3.0 UHD: US] USB3.0 UHD: USB3.0 UHD (video0) [/dev/video0] 720 x 480 @ 60 fps yuyv input 0
2024-05-14T05:54:58.478Z [V4L2:USB3.0 UHD: US] USB3.0 UHD: USB3.0 UHD (video0) [/dev/video0] 720 x 480 @ 50 fps yuyv input 0
2024-05-14T05:54:58.478Z [V4L2:USB3.0 UHD: US] USB3.0 UHD: USB3.0 UHD (video0) [/dev/video0] 720 x 480 @ 30 fps yuyv input 0
2024-05-14T05:54:58.478Z [V4L2:USB3.0 UHD: US] USB3.0 UHD: USB3.0 UHD (video0) [/dev/video0] 720 x 480 @ 20 fps yuyv input 0
2024-05-14T05:54:58.478Z [V4L2:USB3.0 UHD: US] USB3.0 UHD: USB3.0 UHD (video0) [/dev/video0] 720 x 480 @ 10 fps yuyv input 0
2024-05-14T05:54:58.478Z [V4L2:USB3.0 UHD: US] USB3.0 UHD: USB3.0 UHD (video0) [/dev/video0] 640 x 480 @ 60 fps yuyv input 0
2024-05-14T05:54:58.478Z [V4L2:USB3.0 UHD: US] USB3.0 UHD: USB3.0 UHD (video0) [/dev/video0] 640 x 480 @ 50 fps yuyv input 0
2024-05-14T05:54:58.478Z [V4L2:USB3.0 UHD: US] USB3.0 UHD: USB3.0 UHD (video0) [/dev/video0] 640 x 480 @ 30 fps yuyv input 0
2024-05-14T05:54:58.478Z [V4L2:USB3.0 UHD: US] USB3.0 UHD: USB3.0 UHD (video0) [/dev/video0] 640 x 480 @ 20 fps yuyv input 0
2024-05-14T05:54:58.478Z [V4L2:USB3.0 UHD: US] USB3.0 UHD: USB3.0 UHD (video0) [/dev/video0] 640 x 480 @ 10 fps yuyv input 0
2024-05-14T05:54:58.478Z [V4L2:USB3.0 UHD: US] Restarting video grabber is now blocked due to reloading of the configuration
2024-05-14T05:54:58.478Z [V4L2:USB3.0 UHD: US] Cropping image: width=0 height=0; crop: left=0 right=0 top=0 bottom=0
2024-05-14T05:54:58.478Z [V4L2:USB3.0 UHD: US] (GrabberWrapper.cpp:126) CEC keycode. Start: 0, stop: 0
2024-05-14T05:54:58.478Z [V4L2:USB3.0 UHD: US] (Grabber.cpp:159) Set new width: 1280, height: 720 for capture
2024-05-14T05:54:58.478Z [V4L2:USB3.0 UHD: US] (Grabber.cpp:335) setWidthHeight preparing to restarting video grabber 0
2024-05-14T05:54:58.478Z [V4L2:USB3.0 UHD: US] Delayed restart of the grabber due to change of the capturing resolution
2024-05-14T05:54:58.478Z [V4L2:USB3.0 UHD: US] Delayed restart of the grabber due to change of the framerate
2024-05-14T05:54:58.479Z [V4L2:USB3.0 UHD: US] (Grabber.cpp:273) setBrightnessContrastSaturationHue nothing changed
2024-05-14T05:54:58.479Z [V4L2:USB3.0 UHD: US] setHdrToneMappingMode to: enable, but the LUT file is currently unloaded
2024-05-14T05:54:58.479Z [V4L2:USB3.0 UHD: US] (Grabber.cpp:182) setFpsSoftwareDecimation to: 1
2024-05-14T05:54:58.479Z [SIGNAL_OLD] (DetectionManual.cpp:84) Signal detection area set to: 0.250000,0.250000 x 0.750000,0.750000
2024-05-14T05:54:58.479Z [SIGNAL_OLD] (DetectionManual.cpp:74) Signal threshold set to: {0, 0, 0} and frames: 50
2024-05-14T05:54:58.479Z [SIGNAL_AUTO] (DetectionAutomatic.cpp:375) Automatic signal detection -> errorTolerance: 9, modelTolerance: 90, sleepTime: 1000, wakeTime: 0
2024-05-14T05:54:58.479Z [V4L2:USB3.0 UHD: US] (Grabber.cpp:380) setDeviceVideoStandard preparing to restart video grabber. Old: '' new: 'USB3.0 UHD: USB3.0 UHD (video0)'
2024-05-14T05:54:58.479Z [V4L2:USB3.0 UHD: US] Delayed restart of the grabber due to change of selected device
2024-05-14T05:54:58.479Z [V4L2:USB3.0 UHD: US] (Grabber.cpp:200) Force encoding to: yuyv (old: NO_CHANGE)
2024-05-14T05:54:58.479Z [V4L2:USB3.0 UHD: US] Delayed restart of the grabber due to change of the video encoding format
2024-05-14T05:54:58.479Z [V4L2:USB3.0 UHD: US] setQFrameDecimation is now: disabled
2024-05-14T05:54:58.479Z [V4L2:USB3.0 UHD: US] Multithreading for V4L2 is enabled. Available thread's count 3
2024-05-14T05:54:58.479Z [V4L2:USB3.0 UHD: US] Found capture device: /dev/video15
2024-05-14T05:54:58.479Z [WEBSERVER] Initialize Webserver
2024-05-14T05:54:58.479Z [COMPONENTCTRL0] HDR (global): enabled
2024-05-14T05:54:58.480Z [V4L2:USB3.0 UHD: US] Found capture device: /dev/video21
2024-05-14T05:54:58.481Z [V4L2:USB3.0 UHD: US] Found capture device: /dev/video14
2024-05-14T05:54:58.481Z [V4L2:USB3.0 UHD: US] Found capture device: /dev/video22
2024-05-14T05:54:58.481Z [FLATBUFSERVER] Started on port 19400
2024-05-14T05:54:58.481Z [V4L2:USB3.0 UHD: US] Found capture device: /dev/video0
2024-05-14T05:54:58.481Z [V4L2:USB3.0 UHD: US] (V4L2Grabber.cpp:406) Device has 'brightness' control => min: 0, max: 100, default: 50
2024-05-14T05:54:58.481Z [V4L2:USB3.0 UHD: US] (V4L2Grabber.cpp:412) Device has 'contrast' control => min: 0, max: 100, default: 50
2024-05-14T05:54:58.481Z [V4L2:USB3.0 UHD: US] (V4L2Grabber.cpp:418) Device has 'saturation' control => min: 0, max: 100, default: 50
2024-05-14T05:54:58.481Z [V4L2:USB3.0 UHD: US] (V4L2Grabber.cpp:424) Device has 'hue' control => min: 0, max: 100, default: 50
2024-05-14T05:54:58.481Z [FLATBUFSERVER] Started local domain socket server: 'hyperhdr-domain'
2024-05-14T05:54:58.482Z [V4L2:USB3.0 UHD: US] (V4L2Grabber.cpp:213) Searching for USB3.0 UHD: USB3.0 UHD (video0) 1280 x 720 @ 60 fps, input: -1 (yuyv)
2024-05-14T05:54:58.482Z [V4L2:USB3.0 UHD: US] *************************************************************************************************
2024-05-14T05:54:58.482Z [V4L2:USB3.0 UHD: US] Starting V4L2 grabber. Selected: USB3.0 UHD: USB3.0 UHD (video0) [/dev/video0] 1280 x 720 @ 60 fps yuyv input -1
2024-05-14T05:54:58.482Z [V4L2:USB3.0 UHD: US] *************************************************************************************************
2024-05-14T05:54:58.482Z [V4L2:USB3.0 UHD: US] (V4L2Grabber.cpp:826) Hardware cropping is not supported: ignoring
2024-05-14T05:54:58.482Z [V4L2:USB3.0 UHD: US] Set device input to: Camera 1
2024-05-14T05:54:58.482Z [NETFORWARDER] Forwarder has changed state to disabled
2024-05-14T05:54:58.499Z [V4L2:USB3.0 UHD: US] Set resolution to: 1280 x 720
2024-05-14T05:54:58.516Z [V4L2:USB3.0 UHD: US] Set framerate to 60 FPS
2024-05-14T05:54:58.519Z [V4L2:USB3.0 UHD: US] Brightness set to: 50 (default)
2024-05-14T05:54:58.523Z [V4L2:USB3.0 UHD: US] Contrast set to: 50 (default)
2024-05-14T05:54:58.526Z [V4L2:USB3.0 UHD: US] Saturation set to: 50 (default)
2024-05-14T05:54:58.529Z [V4L2:USB3.0 UHD: US] Hue set to: 50 (default)
2024-05-14T05:54:58.529Z [V4L2:USB3.0 UHD: US] (V4L2Grabber.cpp:105) LUT folder location: '/usr/share/hyperhdr/lut'
2024-05-14T05:54:58.529Z [V4L2:USB3.0 UHD: US] (Grabber.cpp:458) LUT file found: /home/andrea/.hyperhdr/lut_lin_tables.3d
2024-05-14T05:54:58.529Z [V4L2:USB3.0 UHD: US] (Grabber.cpp:468) Index 1 for HDR YUV
2024-05-14T05:54:58.637Z [MUXER0] Set visible priority to 255
2024-05-14T05:54:58.637Z [HYPERHDR0] New priority[255], previous [255]
2024-05-14T05:54:58.637Z [HYPERHDR0] No source left -> switch LED-Device off
2024-05-14T05:54:58.637Z [SMOOTHING0] Clearing queued colors before: disabling
2024-05-14T05:54:58.637Z [SMOOTHING0] Smoothing queue is cleared
2024-05-14T05:54:58.637Z [COLORSPACE_CALIBRATION0] (ColorSpaceCalibration.cpp:225) setBackLightEnabled: 0
2024-05-14T05:54:58.637Z [LEDDEVICE0_AWA_SPI] (LedDevice.cpp:297) Disable the device
2024-05-14T05:54:58.637Z [LEDDEVICE0_AWA_SPI] (LedDevice.cpp:381) Stopping refresh timer
2024-05-14T05:54:58.637Z [LEDDEVICE0_AWA_SPI] (LedDevice.cpp:90) Switch off
2024-05-14T05:54:58.637Z [LEDDEVICE0_AWA_SPI] (LedDevice.cpp:126) Power Off
2024-05-14T05:54:58.637Z [LEDDEVICE0_AWA_SPI] (LedDevice.cpp:544) Set LED strip to black/power off
2024-05-14T05:54:58.638Z [LEDDEVICE0_AWA_SPI] (ProviderSpi.cpp:135) Closing SPI interface
2024-05-14T05:54:58.638Z [COMPONENTCTRL0] LED device: disabled
2024-05-14T05:54:59.414Z [WEBSERVER] Apply Webserver settings
2024-05-14T05:54:59.414Z [WEBSERVER] Set document root to: :/www
2024-05-14T05:54:59.414Z [WEBSERVER] Started: 'HyperHDR WebServer (HTTP)' on port: 8090
2024-05-14T05:54:59.414Z [SSDP] (SSDPHandler.cpp:93) The local address is empty
2024-05-14T05:54:59.414Z [WEBSERVER] Initialize Webserver
2024-05-14T05:54:59.414Z [WEBSERVER] Apply Webserver settings
2024-05-14T05:54:59.414Z [WEBSERVER] Set document root to: :/www
2024-05-14T05:54:59.805Z [WEBSERVER] Setup SSL certificate
2024-05-14T05:54:59.807Z [WEBSERVER] Setup private SSL key
2024-05-14T05:54:59.808Z [WEBSERVER] Started: 'HyperHDR WebServer (HTTPS)' on port: 8092
2024-05-14T05:54:59.808Z [SSDP] (SSDPHandler.cpp:42) SSDPHandler is initializing
2024-05-14T05:54:59.808Z [SSDP] Could not obtain the local address. Retry later (1/10)
2024-05-14T05:54:59.808Z [SSDP] (SSDPServer.cpp:95) Initialize the SSDP server
2024-05-14T05:54:59.808Z [SSDP] (SSDPHandler.cpp:93) The local address is empty
2024-05-14T05:54:59.890Z [V4L2:USB3.0 UHD: US] Found and loaded LUT: '/home/andrea/.hyperhdr/lut_lin_tables.3d'
2024-05-14T05:54:59.890Z [V4L2:USB3.0 UHD: US] Video pixel format is set to: YUYV
2024-05-14T05:54:59.898Z [V4L2:USB3.0 UHD: US] Started
2024-05-14T05:54:59.935Z [V4L2:USB3.0 UHD: US] (V4L2Grabber.cpp:1164) Worker's thread count  = 3
2024-05-14T05:54:59.941Z [MUXER0] Priority 240 is now active
2024-05-14T05:54:59.941Z [MUXER0] Set visible priority to 240
2024-05-14T05:54:59.941Z [HYPERHDR0] New priority[240], previous [255]
2024-05-14T05:54:59.941Z [HYPERHDR0] New source available -> switch LED-Device on
2024-05-14T05:54:59.941Z [SMOOTHING0] Clearing queued colors before: enabling
2024-05-14T05:54:59.941Z [SMOOTHING0] Smoothing queue is cleared
2024-05-14T05:54:59.941Z [COLORSPACE_CALIBRATION0] (ColorSpaceCalibration.cpp:225) setBackLightEnabled: 1
2024-05-14T05:54:59.941Z [LEDDEVICE0_AWA_SPI] (LedDevice.cpp:247) Enable the device
2024-05-14T05:54:59.942Z [LEDDEVICE0_AWA_SPI] (LedDevice.cpp:64) Switch on
2024-05-14T05:54:59.942Z [LEDDEVICE0_AWA_SPI] (LedDevice.cpp:140) Power On
2024-05-14T05:54:59.942Z [LEDDEVICE0_AWA_SPI] (LedDevice.cpp:367) Starting timer with interval = 10ms
2024-05-14T05:54:59.944Z [IMAGETOLED_MNG0] Total index number is: 240640 (memory: 240640). User sparse processing is: disabled, image size: 1280 x 720, area number: 224
2024-05-14T05:54:59.946Z [COMPONENTCTRL0] LED device: enabled
2024-05-14T05:54:59.947Z [SMOOTHING0] Using alternative smoothing input (0)
2024-05-14T05:54:59.962Z [SMOOTHING0] Using alternative smoothing procedure (0)
2024-05-14T05:55:00.951Z [NET_DISCOVERY] Found ESP board at ttyACM0:-1 (USB Single Serial)
2024-05-14T05:55:00.916Z [SERVICE_mDNS] Starting the network discovery thread
2024-05-14T05:55:03.944Z [MUXER0] Priority 240 is now inactive
2024-05-14T05:55:03.945Z [MUXER0] Set visible priority to 255
2024-05-14T05:55:03.945Z [HYPERHDR0] New priority[255], previous [240]
2024-05-14T05:55:03.945Z [HYPERHDR0] No source left -> switch LED-Device off
2024-05-14T05:55:03.945Z [SMOOTHING0] Clearing queued colors before: disabling
2024-05-14T05:55:03.945Z [SMOOTHING0] Smoothing queue is cleared
2024-05-14T05:55:03.945Z [LEDDEVICE0_AWA_SPI] (LedDevice.cpp:297) Disable the device
2024-05-14T05:55:03.945Z [COLORSPACE_CALIBRATION0] (ColorSpaceCalibration.cpp:225) setBackLightEnabled: 0
2024-05-14T05:55:03.945Z [LEDDEVICE0_AWA_SPI] (LedDevice.cpp:381) Stopping refresh timer
2024-05-14T05:55:03.945Z [LEDDEVICE0_AWA_SPI] (LedDevice.cpp:90) Switch off
2024-05-14T05:55:03.945Z [LEDDEVICE0_AWA_SPI] (LedDevice.cpp:126) Power Off
2024-05-14T05:55:03.945Z [LEDDEVICE0_AWA_SPI] (LedDevice.cpp:544) Set LED strip to black/power off
2024-05-14T05:55:03.946Z [LEDDEVICE0_AWA_SPI] (ProviderSpi.cpp:135) Closing SPI interface
2024-05-14T05:55:03.946Z [COMPONENTCTRL0] LED device: disabled
2024-05-14T05:55:29.771Z [SSDP] (SSDPHandler.cpp:42) SSDPHandler is initializing
2024-05-14T05:55:29.772Z [SSDP] (SSDPHandler.cpp:183) The local address is: <IP_ADDRESS>
2024-05-14T05:55:29.772Z [SSDP] (SSDPServer.cpp:95) Initialize the SSDP server
2024-05-14T05:55:29.772Z [WEBSERVER] (StaticFileServing.cpp:68) SSDP description is set up
2024-05-14T05:55:29.773Z [SSDP] Starting the SSDP server
2024-05-14T05:56:04.259Z [WEBSOCKET] (WebSocketClient.cpp:39) New connection from ::ffff:<IP_ADDRESS>
2024-05-14T05:56:14.853Z [WEBSOCKET] (HyperAPI.cpp:1109) message: [{"command":"leddevice","ledDeviceType":"awa_spi","subcommand":"discover","tan":937}]
2024-05-14T05:56:14.854Z [LEDDEVICE_AWA_SPI] (ProviderSpi.cpp:319) SPI devices discovered: [{"devices":[{"name":"/dev/spidev0.0","value":"/dev/spidev0.0"},{"name":"/dev/spidev0.1","value":"/dev/spidev0.1"}],"ledDeviceType":"awa_spi"}]
2024-05-14T05:56:14.854Z [WEBSOCKET] (HyperAPI.cpp:1133) response: [{"devices":[{"name":"/dev/spidev0.0","value":"/dev/spidev0.0"},{"name":"/dev/spidev0.1","value":"/dev/spidev0.1"}],"ledDeviceType":"awa_spi"}]
2024-05-14T05:57:41.600Z [WEBSOCKET] (HyperAPI.cpp:957) log streaming activated for client ::ffff:<IP_ADDRESS>

Steps to reproduce
just boot the system
What is expected?
to have a working video feed
What is actually happening?
there's no video feed until a restart of hyperhdr service
System

HyperHDR Server:
- Build:           (HEAD detached at v<IP_ADDRESS>) (awawa-dev-9e960c9/52f12b4-1711236142)
- Build time:      Mar 23 2024 23:55:32
- Git Remote:      https://github.com/awawa-dev/HyperHDR
- Version:         <IP_ADDRESS>
- UI Lang:         auto (BrowserLang: en-US)
- Avail Capt:      Linux (V4L2)
- Database:        read/write

HyperHDR Server OS:
- Distribution:   Debian GNU/Linux 12 (bookworm)
- Architecture:   arm64
- CPU Type:       Raspberry Pi 4 Model B Rev 1.5
- CPU Hardware:   c03115
- Kernel:         linux (6.6.20+rpt-rpi-v8 (WS: 64))
- Qt Version:     5.15.8
- Browser:        Mozilla/5.0 (X11; Linux x86_64; rv:125.0) Gecko/20100101 Firefox/125.0

Hi
I don't see an issue in this log related to HyperHDR. The grabber is initialed fine without any errors but it won't provide any video stream and that's why video priority is removed after some time. A bit strange symptom is a pause while listing available grabbers which may indicate a hardware problem with the grabber or USB connection (hub, broken cable etc). Or dying SD card causing core modules to take long to initialize. But in such cases video grabber always refuses to inilized properly in HyperHDR and throws an error. You can try to add a delay to HyperHDR service as a workaround (search repo for similar problem) and see it it helps. And you must verify dmesg logs. Anyway it's not a HyperHDR issue.

that's an awesome insight, thank you for the quick feedback!
I was keeping the service delay workaround as my last resolve, but I might go for it seeing that could be something not so trivial, that probably worths a lot of troubleshooting time.

ps: after I manually restart the service it start working as I wrote bit it logs "Frame too small" errors too
2024-05-14T08:26:42.962Z [V4L2:USB3.0 UHD: US] Video pixel format is set to: YUYV
2024-05-14T08:26:42.970Z [V4L2:USB3.0 UHD: US] Started
2024-05-14T08:26:42.971Z [V4L2:USB3.0 UHD: US] Frame too small: 0 != 1843200
2024-05-14T08:26:42.972Z [V4L2:USB3.0 UHD: US] Frame too small: 0 != 1843200
2024-05-14T08:26:42.972Z [V4L2:USB3.0 UHD: US] Frame too small: 0 != 1843200
2024-05-14T08:26:42.972Z [V4L2:USB3.0 UHD: US] Frame too small: 0 != 1843200
2024-05-14T08:26:42.988Z [V4L2:USB3.0 UHD: US] (V4L2Grabber.cpp:1164) Worker's thread count  = 3
2024-05-14T08:26:42.995Z [MUXER0] Priority 240 is now active
2024-05-14T08:26:42.995Z [MUXER0] Set visible priority to 240

could they be related to the problem?

No, this is usually fine when the capturing starts up. I often observe this when a callback returns then an empty frame (different grabbers). But after that it should no longer appear and the grabber's video source with priority 240 should not be removed (which proves that the correct frames are coming in)


Complex support for GPU SVD

For doing physics simulation (especially quantum physics) complex SVDs are done very often. It would be a big win for our team if we could get acceleration of this on GPU.

FWIW: in theory this is supported through https://docs.nvidia.com/cuda/cusolver/index.html (look for cusolverDnCgesvd)

Yeah that should make it much easier to implement. I think it was just the plumbing that had to be built?

Yes, this is mostly a matter of plugging the cuSolver implementation into JAX.
I will note that complex SVD is already available on CPU (via LAPACK), so you should be able to prototype that way even if it's slower.

+1

+1, see also https://github.com/google/jax/issues/825

+1

+1


Add Enumerable design for Items and Abilities

Currently there is no way to enumerate through the Items and Abilities, which hinder the .NET programming a lot (foreach, LINQ, IEnumerable<> extensions, etc...). This small change can make the development much quicker.

I will look at your PRs in greater detail later this week. Thank you for your contribution!


Pod overhead Translation to Indonesian Language

This pull, about translation to indonesia language in page Pod Overhead
/language id
/cc @girikuncoro

@sulaimantok Hi.. thank you for your contribution 🎉 , can you please rebase from master and ammend the commits into one? Thanks

/close
moved to #19249


Package is missing  - " Microsoft CRM Web API Query Data Sample (Client-side JavaScript)"

" Microsoft CRM Web API Query Data Sample (Client-side JavaScript)" package is missing

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

ID: c3ae32fb-348c-fe39-fc4a-6a4b0680a199
Version Independent ID: 9c1c528a-ff1e-d02c-5603-3071176ee85b
Content: Web API Query Data Sample (Client-side JavaScript) - Power Apps
Content Source: powerapps-docs/developer/data-platform/webapi/samples/query-data-client-side-javascript.md
Service: powerapps
GitHub Login: @JimDaly
Microsoft Alias: jdaly

@Nkrb
Nava -
Can you look into this please?
Not sure why these were not moved over to Github.
Could be that the were written before the Xrm.WebApi.online API existed.
Everything these samples could do should also be possible using that Xrm.WebApi.online.
These samples could be used in Web resources outside the context of a form.

@mso365 Seems to be there now. File another issue if you are still having trouble finding it.
https://github.com/microsoft/PowerApps-Samples/tree/master/cds/webapi/JS/WebAPIQueryData


[DRAFT][MB-14937] PPM Closeout Delete Modal Details

Jira ticket for this change
Summary
This PR adds additional detail to the delete modal that opens when a service member in PPM closeout is adding/removing Weight Tickets, Progear Expenses, or other Moving Expenses. Please see screenshots below for context.
This PR does not hook up to real API endpoints so the items will not actually be removed from the page when you click Delete. That work will be completed in MB-14179.
The React testing library docs on text match shows the usage of { exact : false } which may not be the best implementation of the test on line 399 in src/pages/MyMove/PPM/Closeout/Review/Review.test.jsx
Setup to Run Your Code

💻 You will need to use three separate terminals to test this locally.
Terminal 1
Start the Go server locally.
make server_run

Terminal 2
Start the UI locally.
make client_run

Terminal 3
Start the client tests locally.
make client_test

Additional steps

Access http://milmovelocal:3000/
Login as service member with email<EMAIL_ADDRESS>Scroll down to Manage your PPM and click Upload PPM Documents
Scroll down to Documents, click Delete on any of the Weight Tickets, Progear Expenses, or other Moving Expenses to see the modal in action

Verification Steps for Author
These are to be checked by the author.

[x] Tested in the Experimental environment (for changes to containers, app startup, or connection to data stores)
[x] Request review from a member of a different team.
[x] Have the Jira acceptance criteria been met for this change?

Verification Steps for Reviewers
These are to be checked by a reviewer.

Frontend

[ ] User facing changes have been reviewed by design.
[ ] There are no aXe warnings for UI.
[ ] This works in Supported Browsers and their phone views (Chrome, Firefox, IE, Edge).
[ ] There are no new console errors in the browser devtools
[ ] There are no new console errors in the test output
[ ] If this PR adds a new component to Storybook, it ensures the component is fully responsive, OR if it is intentionally not, a wrapping div using the officeApp class or custom min-width styling is used to hide any states the would not be visible to the user.

Backend

[ ] Code follows the guidelines for Logging
[ ] The requirements listed in Querying the Database Safely have been satisfied.

Database
Any new migrations/schema changes:

[ ] Follows our guidelines for Zero-Downtime Deploys
[ ] Have been communicated to #g-database
[ ] Secure migrations have been tested following the instructions in our docs

Screenshots
Review Items page

Weight ticket delete modal detail

Moving Expenses / Receipt delete modal detail

Messages

:book:
:link: MB-14937

  Generated by :no_entry_sign: dangerJS against 21be3364303f2e705a683c8f788bc5c3a7105368


arm: put saving of FPU context into its own file so it can be reused

Also, to ease readability.
Signed-off-by: Øyvind Rønningstad<EMAIL_ADDRESS>

@ioannisg  thanks, moved to arch/arm/aarch32/cortex_m like discussed offline. Moved the #ifdef CONFIG_ARM_NONSECURE_PREEMPTIBLE_SECURE_CALLS back to interface.c

@oyvindronningstad, it'd be nice if you could work on the commit messages a bit.  The subject line should be a summary of the body.  And the start of the body shouldn't be continuous from the subject.  It's always a good idea to write the body first and then summarize your message and put it in the subject line at the last.
https://docs.zephyrproject.org/latest/contribute/index.html#commit-guidelines

@yashi I updated now, please have a look.

@oyvindronningstad, thanks.  That's much better. :smiley:
I just noticed that your commit is actually a bug fix rather than moving a function for re-usability nor readability, no?  Why don't you create a commit before or after moving the code saying, "arm: Fix restore order for FPU regs" or something along the the line; so that your test case can be "arm: Test restore order for FPU regs" to go with it.
Hope I'm not asking too much.

I just noticed that your commit is actually a bug fix rather than moving a function for re-usability nor readability, no? Why don't you create a commit before or after moving the code saying, "arm: Fix restore order for FPU regs" or something along the the line; so that your test case can be "arm: Test restore order for FPU regs" to go with it.

If this is true (which it seems it is, since the vldmia is called with the same argument, AFAICS) I agree this should have the bug label.
@oyvindronningstad the nrf git tag is not needed here ;)

The bug fix has been moved to https://github.com/zephyrproject-rtos/zephyr/pull/35954

@oyvindronningstad can you rebase this PR now, to exclude the hotfix and keep only the refactoring work? (you'll need to work the commit messages, too :) )

@ioannisg Thanks, done


Use "peer network ls" by default besides list

Let peer network cmd support ls as default, besides list
Description

Change the default cmd from list to ls, which is popular in Linux.
To keep compatible with old version, still support list cmd, too.
Motivation and Context

No open issue.
How Has This Been Tested?

Passed make check, while the change needs no additional test cases.
Checklist:

[x] I have added a Signed-off-by
[x] Either no new documentation is required by this change, OR I added new documentation
[x] Either no new tests are required by this change, OR I added new tests
[x] I have run goimports, go vet, and golint. I have cleaned up all valid errors and warnings in code I have added or modified. These tools may generate false positives.  The goal is clean, consistent, and readable code.

Signed-off-by: Baohua Yang<EMAIL_ADDRESS>

Still no found error, and no restart ci button found ~~
Anyone could help?
Thanks!

From the raw log, it looks like this is the failure:
--- FAIL: TestReplicaPersistQSet (0.00s)
	pbft-core_test.go:1281: did not restore qset properly

Which I am guessing has nothing to do with your change, but we need to get a more definitive answer.

@corecode I recall you submitting a PR recently regarding Qset.  I am not sure if it was merged or not, but perhaps you might know what is going on in this test failure.

That is most puzzling.  I cannot reproduce this here.  Will have to investigate.

Timing issue with the test - should be fixed in master now.

@christo4ferris @binhn @jeffgarratt @srderson any opinion on this?

I personally prefer list over ls. The rest of our commands our full words so list also seems more consistent. If we do merge this, docs need to be updated. There's at least one location I found at https://github.com/hyperledger/fabric/blob/master/docs/API/CoreAPI.md#cli

If people want ls, maybe we could keep list as the default and make ls an alias?

@srderson Yes, your suggestion is a more mitigatory change, I can update first to see how other people like it.
Thanks!

I had the same thought as @srderson but as both forms are still valid, thought there was little harm. However, as @yeasy agreed to go along with @srderson's suggestion, it's all good.
LGTM

This LGTM now. Just going to leave it open over the weekend to see if there are any other comments. Thanks @yeasy

LGTM

@yeasy It looks like you did not run goimports (which runs gofmt) when submitting this change. Could you please run goimports on main.go and submit a new PR? Thanks.

@srderson aha, sorry for the missing.
A new PR is submitted at https://github.com/hyperledger/fabric/pull/1673.
Thanks!


fix(apps/prod/tekton/configs/tasks): not overwrite tiup nightly pkgs

Signed-off-by: wuhuizuo<EMAIL_ADDRESS>

/approve


Feature/flex 4823 extend da ws for measurements

SonarQube analysis reported 4 issues

 1 critical
 3 major

Watch the comments in this conversation to review them.
2 extra issues
Note: The following issues were found on lines that were not modified in the pull request. Because these issues can't be reported as line comments, they are summarized here:

 MonitoringService.java#L83: Method has 7 parameters, which is greater than 6 authorized.
 MonitoringService.java#L92: Remove this unused "exception" local variable.

SonarQube analysis reported 1 issue

 1 critical

Watch the comments in this conversation to review them.


f7-statusbar

In IOS f7-statusbar not working when i put it into body > div#app > f7-statusbar.  Is it possible add the f7-statusbar directly in body ?

Update to latest F7 and F7 Vue plugins, it is fixed there


Convert Function: Handle Large Files

User Story

As a sender of report to ReportStream,
I want to receive an error if the report size (either file size or message number) is too great for ReportStream to handle,
so that I can resubmit a smaller report that ReportStream can successfully process.
Description/Use Case

On Jan 25 SimpleReport sent two reports that both contained around 1500 messages and the convert step timed out several times trying to process them until they ended up in the poison queue. The two submitted reports were:

f4ea453d-e5c9-4493-944a-808560a2338f
de07b4d5-691d-475c-b4a9-b2a0397e7a1c

The receive (process) function should be updated to reject reports that are too large and/or  the Convert functions should be updated to be able to handle large reports.
Risks/Impacts/Considerations

Dev Notes

Acceptance Criteria

[ ] Receive function throws an error when a report is too large
OR
[ ] Convert function updated to better handle large reports

Hey team! Please add your planning poker estimate with Zenhub @arnejduranovic @jack-h-wang @jalbinson @JessicaWNava @JFU-NAVA-PBC @jimmyfagan @mkalish @thetaurean

Please add your planning poker estimate with Zenhub @brick-green

We should decide which path to take before bidding since the work varies a lot. Maybe we need a spike ticket to decide?

@chris-kuryak to discuss potential solutions with SR. Potential solutions have message monitoring and message processing implications.

Marking this as complete since we have had several PRs merged to speed up the convert step and have not seem a timeout failure in a while. Will re-open if issue comes back. @brandonnava @chris-kuryak @Andrey-Glazkv


Update README.md

[x] Have you signed the Contributor License Agreement?
[x] Have you checked that there aren't other open pull requests for the same manifest update/change?
[ ] Have you validated your manifest locally with winget validate --manifest <path>?
[ ] Have you tested your manifest locally with winget install --manifest <path>?
[ ] Does your manifest conform to the 1.0 schema?

Note: <path> is the name of the directory containing the manifest you're submitting.

Microsoft Reviewers: Open in CodeFlow

Why is it not merging? Does it need to have the Azure-Pipeline-Passed and Validation-Completed labels? It's not a manifest...

It requires manual review from someone with write access.
@KevinLaMS, can you take a look?

@jedieaston The note written here means that we should copy the script and run it where the manifests are to be created. But, we run the script in the Tools folder, thereby neither copying it anywhere else. I think it should be changed.

I don't think that's been updated since YAMLCreate.ps1 got smarter, so yeah, if you can change that it'd be great.

Well, I cannot think of any other sentence but it can be removed in order to avoid confusion for new contributors.
When I was new to this repository, I read the documentation and had copied the script where the manifests should be created. After that, I got to know that it has to be run from the same folder without copying it anywhere. That day, the whole directory structure corrupted the clone and I had to start over again. 😂

Thanks for helping with documentation!!!


Don't apply the unavailability of an extension to members imported from Clang

@swift-ci Please smoke test

…and a test case.

@swift-ci Please smoke test

@swift-ci Please smoke test


You are using an unsupported version of Python

I got Ubuntu 18.04
requirements
sudo wget https://github.com/yt-dlp/yt-dlp/releases/latest/download/yt-dlp -O /usr/local/bin/yt-dlp
sudo chmod a+rx /usr/local/bin/yt-dlp  # Make executable

sudo apt install ffmpeg

installation
mkdir test-project
cd test-project
git clone https://github.com/obra/Youtube2Webpage.git
cd Youtube2Webpage

first run
./yt-to-webpage.pl project-name "https://www.youtube.com/watch?v=jNQXAC9IVRw"

Traceback (most recent call last):
  File "/usr/lib/python3.6/runpy.py", line 193, in _run_module_as_main
    "__main__", mod_spec)
  File "/usr/lib/python3.6/runpy.py", line 85, in _run_code
    exec(code, run_globals)
  File "/usr/local/bin/yt-dlp/__main__.py", line 14, in <module>
  File "/usr/local/bin/yt-dlp/yt_dlp/__init__.py", line 5, in <module>
ImportError: You are using an unsupported version of Python. Only Python versions 3.8 and above are supported by yt-dlp
Can't open '<undef>' for reading: 'No such file or directory' at ./yt-to-webpage.pl line 21

in error versions 3.8 and above but I got python is 2.7* and python3 is 3.11, but which is used?
fixed python version
sudo apt install python3.8

updated ~/.bashrc
alias python='/usr/bin/python3.8'
alias python3='/usr/bin/python3.8'

then
source ~/.bashrc

and now
python --version
Python 3.8.0
python3 --version
Python 3.8.0

ok, again
./yt-to-webpage.pl project-name "https://www.youtube.com/watch?v=jNQXAC9IVRw"

Traceback (most recent call last):
  File "/usr/lib/python3.6/runpy.py", line 193, in _run_module_as_main
    "__main__", mod_spec)
  File "/usr/lib/python3.6/runpy.py", line 85, in _run_code
    exec(code, run_globals)
  File "/usr/local/bin/yt-dlp/__main__.py", line 14, in <module>
  File "/usr/local/bin/yt-dlp/yt_dlp/__init__.py", line 5, in <module>
ImportError: You are using an unsupported version of Python. Only Python versions 3.8 and above are supported by yt-dlp
Can't open '<undef>' for reading: 'No such file or directory' at ./yt-to-webpage.pl line 21

Please help me to understand how should it work?

You're seeing an issue with your install of yt-dlp, not this project. I'd suggest you report this to them.
On Mon, Jan 8, 2024, at 2:58 PM, RoninFromMoscow wrote:

I got Ubuntu 18.04
requirements
sudo wget https://github.com/yt-dlp/yt-dlp/releases/latest/download/yt-dlp -O /usr/local/bin/yt-dlp
sudo chmod a+rx /usr/local/bin/yt-dlp  # Make executable
sudo apt install ffmpeg
installation
mkdir test-project
cd test project
git clone https://github.com/obra/Youtube2Webpage.git
cd Youtube2Webpage
first run
./yt-to-webpage.pl project-name "https://www.youtube.com/watch?v=jNQXAC9IVRw"
Traceback (most recent call last):
File "/usr/lib/python3.6/runpy.py", line 193, in _run_module_as_main
"main", mod_spec)
File "/usr/lib/python3.6/runpy.py", line 85, in _run_code
exec(code, run_globals)
File "/usr/local/bin/yt-dlp/main.py", line 14, in
File "/usr/local/bin/yt-dlp/yt_dlp/init.py", line 5, in
ImportError: You are using an unsupported version of Python. Only Python versions 3.8 and above are supported by yt-dlp
Can't open '' for reading: 'No such file or directory' at ./yt-to-webpage.pl line 21
in error versions 3.8 and above but I got python is 2.7* and python3 is 3.11, but which is used?
fixed python version
sudo apt install python3.8
updated ~/.bashrc
alias python='/usr/bin/python3.8' alias python3='/usr/bin/python3.8'
then
source ~/.bashrc
and now
python --version
Python 3.8.0
python3 --version
Python 3.8.0
ok, again
./yt-to-webpage.pl project-name "https://www.youtube.com/watch?v=jNQXAC9IVRw"
Traceback (most recent call last):
File "/usr/lib/python3.6/runpy.py", line 193, in _run_module_as_main
"main", mod_spec)
File "/usr/lib/python3.6/runpy.py", line 85, in _run_code
exec(code, run_globals)
File "/usr/local/bin/yt-dlp/main.py", line 14, in
File "/usr/local/bin/yt-dlp/yt_dlp/init.py", line 5, in
ImportError: You are using an unsupported version of Python. Only Python versions 3.8 and above are supported by yt-dlp
Can't open '' for reading: 'No such file or directory' at ./yt-to-webpage.pl line 21
Please help me to understand how it should work?
—
Reply to this email directly, view it on GitHub https://github.com/obra/Youtube2Webpage/issues/25, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAALC2A7UZS72Z7BR5XH5W3YNR2XRAVCNFSM6AAAAABBSF64K6VHI2DSMVQWIX3LMV43ASLTON2WKOZSGA3TCMZVG44DOOI.
You are receiving this because you are subscribed to this thread.Message ID: @.***>

ok, but what version of yt-dlp is used for Youtube2Webpage to work?

We don't have a specific requirements. Anything recentish should be fine


arrayKey start at 1

Hello,
The API that receives my files only processes the files that start at file1, file2 etc. Is there a way that I can make the iterator start at 1 and not at 0?
thanks

Yes make your file array to start from 1 index. For example
files = [];
files[1] = file1;
files[2] = file2;


multiple definitions of method fails in c code, not cython

In version 1474:7f1b96cad687, defining multiple versions of the same method using def fails in c code, but not cython.  Specifically, the following code fails:
cdef class A:
    def a(self): pass
    def a(self): pass

It produces this output:
running build_ext
cythoning mult_def.pyx to mult_def.c
building 'mult_def' extension
gcc -pthread -fno-strict-aliasing -DNDEBUG -O2 -march=i586 -mtune=i686 -fmessage-length=0 -Wall -D_FORTIFY_SOURCE=2 -fstack-protector -g -fwrapv -fPIC -I/home/hoytak/sysroot/lib/python2.5/site-packages/numpy/core/include -I/usr/include/python2.5 -c mult_def.c -o build/temp.linux-i686-2.5/mult_def.o
mult_def.c:229: error: redefinition of ‘__pyx_pf_8mult_def_1A_a’
mult_def.c:214: error: previous definition of ‘__pyx_pf_8mult_def_1A_a’ was here
error: command 'gcc' failed with exit status 1

instead of failing in cython.  If the def is replaced by cdef or cpdef, cython catches it.
--Hoyt
Migrated from http://trac.cython.org/ticket/157

This now compiles fine. It's slightly ambiguous which definition ends up being used (if seems to differ depending on binding) but it doesn't break anything.


Add array::downcast_ref and array::downcast_mut

This introduces array::downcast_ref() and array::downcast_mut() helpers, providing a nicer downcasting interface which makes use of errors, so you could e.g. (in a result-context)
downcast_ref(&my_arr)?.do_stuff()

Downstream, if you're using arrow2, chances are you're converting arrow2::error::Error into your errors already anyway somewhere along the line, and working with Result is nicer then Option most of the time, because otherwise you'll have to .ok_or_else() on every downcast call.

I am not sure about this. You can say something like this for any Option returning method. To me this feels something that needs to be resolved by the consumer of the arrow2 crate.

It's your call, but in my recent experiences as a daily arrow2 user, when you're dealing when reading lots of box-arrays from various sources (e.g. dealing with struct-like data and the like), it's downcasts all over the place. If you want to avoid unwraps, you will have to .ok_or_else() every single line to provide context on what just happened. Or just litter the code with unwraps because it's too much hassle otherwise.
The core difference between "just let the user figure it out, it's an option" here is that the array itself (both Array and MutableArray in fact) actually have access to the context, both "what you were trying to cast to" and "what the actual datatype is", because of .data_type(). So, we can assemble a nice error message just once here; chances are, if the user wanted to assemble an error message, they would do almost precisely the same (i.e., use the actual data type of the underlying array). This way, it's just ? in any Result-like contexts as long as your error type is convertible from arrow2's (which it probably already is). There's not many other Option-yielding core APIs aside from downcasts in the library, this is the only bit really sticking out.
A minor side effect here is that it unifies downcasting of both array/mutable-array, but that's not the most important part.


Organisational Page - Treasury [S]

Summary:
As a DHO user I would like to see an overview page about the Hypha Organization with links to organisational pages (e.g. treasury, archetypes, all projects, etc...) in order to understand the organisation better and navigate to pages with more info.
Description:
old URL:
new URL:
/organization
Treasury:

[ ] Headline: Treasury
[ ] Copy: none
[ ] HUSD, HYPHA, SEEDS
[ ] see more link (leads to /treasury)

Ressources:
Attachement:
https://docs.google.com/document/d/1KHC_6Cha8MC2NMKDV6XRXKuZGS7kPdVGuLtF_kSYvbU/edit
https://xd.adobe.com/view/a31415be-a724-49ad-8070-1a7d67dd6880-f647/screen/d4abf3d4-9283-4877-8d6d-8a80653bd50c?fullscreen

@jmgayosso hide "see more" for treasury and add copy "Overview of all Token in the {DAO NAME} Treasury". Actually I would prefer to hide the copy, if that is possible?

Overview of all Token in the {DAO NAME} Treasury"

I can do wherever you want, both options are too fast, what do you prefer??

Overview of all Token in the {DAO NAME} Treasury"

I can do wherever you want, both options are too fast, what do you prefer??

I prefer to hide it - gracias

Done


Installed .jar is missing some classes

Steps.

I've checked out this repo.
I've done a ./gradlew install
I can see the installed dependency:
.m2/repository/com/authenteq/java-crypto-conditions/0.1/java-crypto-conditions-0.1.jar

Shouldn't this be called java-bigchaindb-driver? I saw this.
I import the dependency in a maven project:
        <dependency>
            <groupId>com.authenteq</groupId>
            <artifactId>java-crypto-conditions</artifactId>
            <version>0.1</version>
        </dependency>

I'm not able to create a transaction, I get the following error:
Exception in thread "main" java.lang.NoClassDefFoundError: org/interledger/cryptoconditions/types/Ed25519Sha256Condition
	at com.authenteq.BigchaindbTransaction.buildTransactionJson(BigchaindbTransaction.java:83)
	at com.authenteq.BigchaindbTransaction.<init>(BigchaindbTransaction.java:59)
	at com.rezzonade.persistence.bigchaindb.Example.main(Example.java:52)
Caused by: java.lang.ClassNotFoundException: org.interledger.cryptoconditions.types.Ed25519Sha256Condition
	at java.net.URLClassLoader.findClass(URLClassLoader.java:381)
	at java.lang.ClassLoader.loadClass(ClassLoader.java:424)
	at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:331)
	at java.lang.ClassLoader.loadClass(ClassLoader.java:357)
	... 3 more

I can solve this by manually installing java-crypto-conditions-2.0.0-SNAPSHOT.jar by using:
mvn install:install-file -Dfile=yourClonedRepo/libs/java-crypto-conditions-2.0.0-SNAPSHOT.jar -DgroupId=org.interledger -DartifactId=java-crypto-conditions -Dversion=2.0.0-SNAPSHOT -Dpackaging=jar

Am I missing something or are these actual bugs?

Yeah, thanks for noting, another typo.

java crypto conditions lib is bundled in *.jar form, because it changed quite a lot in version 3 and these changes are not compatible with the current driver. This eases the handling, but yes, not a very clean way.

Thanks for clarifying. Looking forward for a stable version that will be added as a dependency.


fix: do not build again when running e2e

Do not clean up and build again when running e2e

:green_heart: Build Succeeded

the below badges are clickable and redirect to their specific view in the CI or DOCS

Expand to view the summary

Build stats

Start Time: 2022-11-14T14:43:50.076+0000

Duration: 8 min 0 sec

Test stats :test_tube:

Test
Results

Failed
0

Passed
6

Skipped
0

Total
6

:robot: GitHub comments
Expand to view the GitHub comments

To re-run your PR in the CI, just comment with:

/test : Re-trigger the build.

/test all : Re-trigger the build for all the stages.


Reconcile input element causes cursor to move

If a textbox has focus, then the Reconcile method results in the cursor moving to the end of the text. The cursor moves when we set the "value" property, here.
I've worked around the problem in my fork by not updating the value property if the element has focus, but this isn't a universal solution. If the value is updated without input from the user, the textbox won't be updated if it has focus.
This seems to be quite a common problem in the React world. I was wondering if anyone had any good solutions or ideas?

Yes, this occurs when setting the value property. The solution is to make sure that it only gets set when it has actually changed. Maybe we should go back to something similar to
if name == "value" {
    oldValue = e.node.Get("value").String()
}
if value != oldValue {

I can't remember exactly in which situation this solution failed... Needs some investigation.

Yes that's the first method I tried, but it wasn't perfect. My component fires the re-render if the value of the textbox hasn't changed 50ms after the last keyup. This worked fine until you start typing fast, at which point the cursor would start jumping.
I also tried saving the selectionStart and selectionEnd points of the textbox... This worked rather better, but with some keyboard mashing, the cursor would start moving around.
Perhaps these problems can be solved. I'll continue playing with it.

Here's an interesting idea... If we only update the value if the old value from the model matches the current value from the element, then we still get updates if the user isn't entering text, but it prevents it if the text is being entered...

Although, perhaps I'm forgetting this might not actually be the same textbox we're reconciling against...

@davelondon do you have any code on-hand that can reproduce the issue? I'd be curious to play around with potential solutions.
I also have some very old code which attempted to save/restore cursor selection, and it didn't have any drawbacks except one minor thing (when using shift+arrow keys to select text, it had potential to reverse the direction of your selection, i.e. swapping the origin of your selection with the current destination / cursor position). It might be adaptable if your interesting idea above doesn't pan out.

I can only repeat: The golden solution here is to not set the value property unless the content is actually being modified by some code. That way, the browser has no reason to discard the state of the selection, etc.

I don't have a simple test case... I'll see if I can come up with one today and we can all have a play.

If I'm not very much mistaken, the problem manifests itself in the todomvc example... Simply enter some text, reposition the cursor to the start of the entered text and add some more. The cursor immediately jumps to the end. I've pushed a couple of branches to my fork to show the issue and the fix, but perhaps it'll be easier to set it up yourself:
https://github.com/davelondon/vecty/tree/input
https://github.com/davelondon/vecty/tree/inputfixed

I've also added a red div to the bottom of the page. Mouse over this to add a character to the end of the textbox without losing focus... This is important for testing the use-case where the value is updated without the user entering text.

Hmmm @neelance it seems the simple solution you first proposed works fine in this example. I'l go back to my more complex code and work out why it's not working. It's possible I've made a mistake somewhere..

OK I've worked it out. Your simple code works fine. This was actually the first method I tried last week, but at the time my event handlers were dispatching an action containing the actual value, like this. This didn't work.
Since then I've updated it to pass a function that returns the current value, like this. This seems to work fine with your code.
I'll do a PR. We can discuss preserving the cursor position and selection in a different issue.


Possible CSS transforms instead of SVG paths?

The current library builds SVG paths. I'm assuming that CSS transforms were tested as well, how did those tests go?
I would assume CSS transforms would be faster to render on the client than SVG's beside being faster to calculate than custom SVG paths for each element. Just opening this for discussion because I don't see this topic mentioned anywhere in the project.

That's a great question. CSS transforms would definitely be faster. In fact PaperCSS does exactly that for the most part.
It has its limitations too. With wired the goal was to start from basics and the push the edges of how widgets are visually defined:

With wired-elements the rendering is unique every time -  emulating actual hand drawn shapes. Shapes vary quite differently over render instance

SVG allows more complex manipulations and you're not limited to borders. e.g

It uses algorithms defined Rough.js which can provide much more 'fill' and dynamic rendering options

With SVG we can take more liberty to create more interesting styles and patterns in the future. Which won't be as fast as CSS but definitely offers more creative opportunities

Having said that, there's another option for the future: CSS Houdini. This may be a long term alternative for rendering. All of the rendering would be pushed to CSS paint worklets giving excellent render performance. https://github.com/pshihn/rough-paint is a proof of concept that uses CSS houdini


"mktemp: too few X's in template"

I ran into this error with the recent updates. Easy enough to fix but was confused and had to Google. I wonder if linux and macOS mktemp behave differently? Seems likely. In any case, thought I'd open an issue. Thanks for this tool, Bill! Very useful.

What was the fix? Sorry I don't test on linux

thanks for the report, let me know if https://github.com/llimllib/gpt-bash-cli/commit/587b790d90b671876a8d9d08848c2370e87dd84b is a sensible fix

That was it! Next time I'll throw up a PR. Thanks again


feat: make renderer state initialization synchronous by default

Apart from implementing the synchronous initialisation, (and keeping the async one OPT-IN via options), I've also moved a bit a code to stand alone modules and added some more unit tests
resolves #278

@sapkra Here you go ;)

:tada: This PR is included in version 2.0.0-alpha.5 :tada:
The release is available on:

npm package (@alpha dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


WinRM does not work with Windows Server 2016 WinRM::WinRMAuthorizationError

After upgrade to W2k16 from W2K12R2 winrm no longer work - I always get WinRM::WinRMAuthorizationError.
I try to use ssl and negotiate with 1.7.3 and 2.1.0 version. I tested similar configuration on a nearby server W2k12. It works.

There are many factors that can influence this. Are you using a domain or local account? If using a local account, make sure you set LocalAccountTokenFilterPolicyat HKEY_LOCAL_MACHINE\software\Microsoft\Windows\CurrentVersion\Policies\system to 1.

Hi, I apologize for the delay. After a clean install of W2K12 everything worked as it should. Everything is OK.


Add RDM data to fixtures

We definitely don't want to duplicate everything from rdm.openlighting.org but we should be able to link to the respective page there and specify if a fixture supports RDM at all (also if there is no page in the RDM database). This includes at least the RDM model ID and the RDM personality ID.
See also #287

Hi @FloEdelmann ,
To match your personality to an RDM personality, you'll need the RDM manufacturer ID, RDM device model ID and RDM personality number. You may also want to log the software version ID, as in theory a manufacturer could release an updated firmware which adds/changes the fields in a personality. I suspect realistically they'd just add a new personality rather than risking breaking backwards compatibility.
That would be enough to link to the model page (if it exists). It would also be enough to match your fixture profile in your system to a live device on the RDM bus.

@peternewman It is merged!
Notable links:

https://open-fixture-library.herokuapp.com/martin
https://open-fixture-library.herokuapp.com/martin/mac-viper-wash
https://open-fixture-library.herokuapp.com/rdm
https://open-fixture-library.herokuapp.com/rdm?manufacturerId=21075&modelId=7

Thanks!
I left a few comments on the PR (even though you've merged it).
I think there may be some clever stuff we can do with URLs to source the manufacturer info from our end, but I need to have a ponder and some free time...

You're currently listing "RDM personality index: null" in a few places.
How about some anchors so we can jump to a particular RDM personality from the OLP RDM site on something like https://open-fixture-library.herokuapp.com/cameo/thunder-wash-600-rgb ?

Thanks for filing this bug; #297 removes these null references.
Adding anchors sounds like a good idea, maybe we can also include it in #297
Linking to a manufacturer page works by omitting the modelId parameter:
https://open-fixture-library.herokuapp.com/rdm?manufacturerId=21075
We could add these links in OpenLightingProject/rdm-app#128

Hi @fxedel ,
Thanks for sorting the nulls.
That sounds great in terms of the anchors. The other key thing that wants changing/extending is https://github.com/FloEdelmann/open-fixture-library/pull/291#discussion_r144633392
In terms of the manufacturer stuff, what I meant was we generate and use this:
https://github.com/OpenLightingProject/rdm-app/blob/master/data/manufacturer_data.py
By running this script:
https://github.com/OpenLightingProject/rdm-app/blob/master/tools/make_manufacturer_data.sh
If we also stored manufacturer URLs for RDM manufacturers on our side (which would benefit us too, as we could link to them not just their product URLs), then you could do a bulk import of the RDM manufacturer IDs, their official names in RDM terms and any URLs we've gathered.

Ah, you meant the manufacturers' websites, didn't you? Good idea on sharing collected data! That's also related to importing from rdm.openlighting.org (#287).

Yep. Your data for that is all in https://github.com/FloEdelmann/open-fixture-library/blob/master/fixtures/manufacturers.json isn't it?
We can then give you a list of every RDM capable manufacturer, along with their ID (and just allow your users to add manufacturers which can't do RDM. Although you may want to work out some mapping for short/pretty names and keys.
As I mentioned in #287 personally I'd actually be leaning towards using the RDM model collector direct from OLA and offering a translate/input option for that, rather than trying to send it through the RDM website (although we may be able to create some sort of basic bulk export for existing fixtures, but probably without the channel data etc for most of them, so it won't be much of a personality, just the personality name and how many channels.

Yes, all manufacturer-related data is in manufacturers.json.
Possibly, we could add a manufacturer property fullname, which is the same as the one registered at ESTA. I'd definitely like to keep the displayed names short and pretty and make the extended names optional. If we can do a bulk import of the manufacturer data, that prettifying happen manually sometime afterwards.
I guess the existing RDM fixture data wouldn't add too much benefit if we imported them now, so we should rather focus on the RDM model collector import plugin, which could prefill more fields.

The ESTA registered ones do change occasionally, which would slightly break that bit. I was considering the same thing at first, but I realised I missed the obvious, it can regenerate a list of RDM IDs and names occasionally, you can then merge any new ones in (and if you've renamed an old one, it can match based on the RDM ID and not overwrite the name).
The only exciting edge case, which probably needs manual eyeballing (or some predictive matching with one of the spelling type libraries) is if someone manually adds a new manufacturer (either before it has an RDM ID, or because they've missed the existing entry), at some point those two bits need linking together to remove the duplication.
As I mentioned in https://github.com/FloEdelmann/open-fixture-library/issues/287#issuecomment-336728996 , it may be worth extending your existing pre-population code to add RDM personality IDs and names, as well as fixture name and model ID if someone comes in via that route, but there probably isn't much benefit to bulk importing all our current data.


Add version information to catalog javadoc

Generated accessors for version catalogs now contain the version information for dependency and plugin entries.

Fixes #26741

Reviewing cheatsheet
Before merging the PR, comments starting with

❌ ❓must be fixed
🤔 💅 should be fixed
💭 may be fixed
🎉 celebrate happy things

@bot-gradle test this

I've triggered the following builds for you. Click here to see all build failures.

PullRequestFeedback build

@bot-gradle test and merge

Your PR is queued. See the queue page for details.

I've triggered a build for you. Click here to see all failures if there's any.

Pre-tested commit build failed. Click here to see all build failures.

Your PR is queued. See the queue page for details.

I've triggered a build for you. Click here to see all failures if there's any.


ROX-15907: Add E2E tests for declarative config

Description
This PR adds E2E tests for the declarative configuration feature.
Currently, it has the deletion PR as its parent, since it is not yet merged.
Within the tests, the following will be done:

A config map will be created, each resource type will be added to the config map.
The successful creation of the resources, including the health status for each, will be verified.
For each resource, an invalid update will be made (invalid meaning an error occurs during upserting the value within the respective datastore).
The update to the health status will be verified for each resource, including whether the resource still exists.
The config map will be deleted.
The successful deletion of the resources, including the health status for each, will be verified.

There's currently three TODO comments which apply and will be either addressed in a follow-up or within the parent PR of the deletion:

When an error occurs before the resource is upserted within the datastore (i.e. on first definition), the deletion will not remove the integration health status. This ought to be fixed in the parent PR, and an appropriate test case should be added here.
When an error occurs during upersting, the error has to occur at least 5 times before the health status is updated. Since the interval for reconciliation is one minute, it takes up to 5 minutes before the error is shown. We should either a) lower the error threshold to update the health status or b) run the
reconciliation more frequently.
When an error occurs during updating an existing auth provider, the previous version of the auth provider will be removed. We can think about using the registry.Upsert() function if applicable to avoid "locking" users out (imagine users will hose their declaratively created auth provider, which would
require to use basic password again).

Checklist

[ ] Investigated and inspected CI test results
[ ] Unit test and regression tests added
[ ] Evaluated and added CHANGELOG entry if required
[ ] Determined and documented upgrade steps
[ ] Documented user facing changes (create PR based on openshift/openshift-docs and merge into rhacs-docs)

If any of these don't apply, please comment below.
Testing Performed

see tests running and passing in CI.

Current dependencies on/for this PR:

master

PR #5185

PR #5186

PR #5266   👈

This comment was auto-generated by Graphite.

/retest

/retest


fix(check:policy): Exclude scripts that use tsc --watch from "check phase", not just "resolve phase"

Description
We thought we had fixed this before but only applied the new condition in the resolvers and missed this part. I confirmed locally that with this change, policy check now doesn't flag these scripts as failing policy after I removed them from the exclusions list. Will need to publish a version of build-tools with this fix and consume it in the client release group to actually remove those exclusions though.
Reviewer Guidance
The review process is outlined on this wiki page.

Probably not worth it at this point, but could/should this be a shared function?

Yeah, good point, I'll do that and then merge it.


feat: JSON view for query & datasource form components

Description
When writing JSON queries or documents, the experience is very bad since the formatting is not there and the size of the editor collapses when the focus is removed from the component. Adding a JSON formatter and editor for this can improve the experience for the end-user.
This change introduces a new key inputType for the form components to enable JSON view. This key will be used in the future for UQI forms to allow merging multiple component types into one.
Fixes #7533
Type of change

New feature (non-breaking change which adds functionality)

Checklist:

[x] My code follows the style guidelines of this project
[x] I have performed a self-review of my own code
[x] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation
[x] My changes generate no new warnings
[ ] I have added tests that prove my fix is effective or that my feature works
[x] New and existing unit tests pass locally with my changes

Test coverage results :test_tube:
:green_circle: Total coverage has increased
// Code coverage diff between base branch:release and head branch: fix/7533-json-view-for-forms

Status
File
% Stmts
% Branch
% Funcs
% Lines

:green_circle:
total
54.8 (0.01)
36.49 (0.01)
34.08 (0.01)
55.35 (0.01)

:green_circle:
app/client/src/components/formControls/DynamicInputTextControl.tsx
95.12 (-1.43)
66.67 (16.67)
83.33 (3.33)
95 (-0.83)

:red_circle:
app/client/src/utils/autocomplete/TernServer.ts
50.47 (-0.24)
38.26 (-0.87)
36.21 (0)
55.08 (-0.27)

/ok-to-test sha=f9d3a63

/ok-to-test sha=f9d3a63


Build Optimizer increasing build time excessively

From @filipesilva on November 30, 2017 14:47
In https://github.com/angular/angular-cli/issues/5618#issuecomment-345218811, @changLiuUNSW reported a 3x increase in build time (from ~3 to ~9 minutes) when using --build-optimizer:
Angular CLI  1.5.2 with Angular 5.0.1
ng build --prod
Time: 530465ms
chunk {0} polyfills.953b2ea9f096cadfdccc.bundle.js (polyfills) 147 kB [initial] [rendered]
chunk {1} main.e2cfa60d1ec303d72a6a.bundle.js (main) 1.77 MB [initial] [rendered]
chunk {2} styles.b49f8f5ee25381105567.bundle.css (styles) 108 kB [initial] [rendered]
chunk {3} inline.2ae12ef65c8a9f6162ba.bundle.js (inline) 1.49 kB [entry] [rendered]

ng build --prod --build-optimizer=false
Time: 163265ms
chunk {0} polyfills.cdff46cd9b1a8d656218.bundle.js (polyfills) 147 kB [initial] [rendered]
chunk {1} main.d1916123bd0e4aa2858f.bundle.js (main) 1.34 MB [initial] [rendered]
chunk {2} styles.d1f7c9f576103c62cb95.bundle.css (styles) 108 kB [initial] [rendered]
chunk {3} vendor.1fbdf23b6f274bb4005e.bundle.js (vendor) 639 kB [initial] [rendered]
chunk {4} inline.58b71d550a47f85197a5.bundle.js (inline) 1.5 kB [entry] [rendered]

https://github.com/angular/devkit/pull/304 has possibly improved this, but needs to be verified.
@changLiuUNSW can you try with Angular CLI 1.5.5 and let us know what's the current build time please?
Likely related to https://github.com/angular/devkit/issues/240.
Copied from original issue: angular/devkit#305

From @changLiuUNSW on December 1, 2017 4:19
Thanks @filipesilva. I will have a test tonight and get back to you ASAP.

Thanks for your hard work @filipesilva.
If we can make the difference within 1 minute , so much the better :)
Thanks again.

From @filipesilva on December 1, 2017 11:49
All credit goes to @clydin, he's the one working on reducing Build Optimizer run time and memory usage.

From @filipesilva on December 18, 2017 8:37
@caroline-church is your project open source or available for me to see somewhere?

From @caroline-church on December 14, 2017 16:17
Hi i am also having this issue but am not using angular-cli, any recomendations what i can do to make my build work with build-optimizer turned on. In my case it gets to around 50% then hangs forever

From @pjmolina on December 22, 2017 16:57
Hi everyone!
I have a case when building for production an ng app:
This hangs forever (it is not a memory problem, uses around 400Mb) but keeps consuming CPU and do not finish.
ng build -e prod -prod -aot --base-href x
This other one, disabling the build optimizer, works:
ng build -e prod -prod -aot --base-href x --build-optimizer=false
One particularity on the ng project is that it contains one big/medium file (a generated parser) of 108 Kb in size and this looks to be the hanging point.
Versions used:
Angular CLI: 1.6.2
Node: 8.6.0
OS: win32 x64
Angular: 5.1.2
@angular/cli: 1.6.2
@angular-devkit/build-optimizer: 0.0.36
@angular-devkit/core: 0.0.22
@angular-devkit/schematics: 0.0.42
@ngtools/json-schema: 1.1.0
@ngtools/webpack: 1.9.2
@schematics/angular: 0.1.11
typescript: 2.5.3
webpack: 3.10.0

The project is not open source, cannot share it as is. But I can prepare a private repro sample if requested.

From @caroline-church on December 18, 2017 9:16
@filipesilva  here is my branch https://github.com/caroline-church/fabric-composer/tree/improve-performance-2. Its a mono-repo so you have to run npm install in the top level directory. The package you want to look at is composer-playground.    I narrowed it down to that the problem was the composer-common dependency, but wasn't sure why it would cause a problem.

From @pjmolina on December 22, 2017 17:11
@filipesilva Yes, in a private way (not for public disclosure).
I can sent it to you by e-mail.

From @filipesilva on December 22, 2017 17:9
@pjmolina that's pretty interesting, the big file. Is the file itself something you can share?

From @filipesilva on December 28, 2017 17:28
@pjmolina thanks a bunch for putting that repro up! I'll have a look to see if there's a specific build optimizer optimization that's causing problems.
/cc @clydin

From @pjmolina on December 22, 2017 19:8
@filipesilva I just created a shared full repro sample.

From @filipesilva on December 28, 2017 18:29
Unsure... but something odd is happening here. I tried using the node inspector to get a CPU profile, and... it crashes.
I set a breakpoint right before Build Optimizer starts processing parser.ts and if I take a CPU profile then, for any amount of time (even something like 1s) and stop, the profiler will go up to 15gigs of ram trying to process it and crash chrome.
I might be related to that TS issue yes. Build Optimizer processes input files as JS files with allowJs. I double checked and it turns out the only applicable transform for the big file is prefix-classes so that's the one that ran. But now I tried forcing another transform for that file instead of prefix-classes and it also hangs.
So yeah, I think it boils down to https://github.com/Microsoft/TypeScript/issues/17033.

From @filipesilva on December 28, 2017 18:0
I ran some tests disabling each individual optimization that Build Optimizer does and the culprit seems to be https://github.com/angular/devkit/blob/master/packages/angular_devkit/build_optimizer/src/transforms/prefix-classes.ts.
We're probably doing something horribly inefficient there and it takes a long time on big files.

From @pjmolina on December 28, 2017 18:14
Just in case, if the TypeScript compiler/lib is involved, as an hypothesis: Could it be related to this other bug: TypeScript #17033 I reported on the TS compiler?

From @clydin on December 28, 2017 19:4
Did a quick test with PR #346 and a production build (ng build --prod) finishes in ~18 seconds.  The culprit appears to be the type analysis phase of the TS compiler.  The massive amount of nesting in the large parser file is probably the issue.

From @filipesilva on December 28, 2017 20:15
I think #346 is a great improvement, but worry about the sourcemap limitation. It means there are situations where having sourcemaps in production might mean extremely lengthy build. But that's the case now anyways.

Is there any course of action to fix this issue?

@dhilgarth are you seeing some disproportionate build time increase? Overall Build Optimizer is expected to take make builds take longer, as it adds another step to the build pipeline.
In the past we have found bugs caused a disproportionate increase in build time however. To the best of my knowledge all those are currently fixed. But there might be unknown ones.
If you're in such a situation can you open a new issue with a reproduction please? This issue itself should be closed though, in the year since it was open we have fixed all outstanding Build Optimizer performance bugs.

Thanks for the amazingly fast response.
Indeed, we are seeing build time increases by 200+% (14 minutes instead of 3), however, not consistently. And sometimes, it even seems to hang forever.
I am not sure if I can provide a repro as it is a rather big project. But, with the info that it should work, I will try to find the root cause and report it in a new issue.
Thanks so far

Can you show me your ng version output? I'd also be curious to know what the difference in bundle size is with and without Build Optimizer.
Although at this point if I had to bet on the root cause, it might be memory. If your builds are already close to the memory limit, anything that moves them closer will disproportionately increase build time due to GC churn. https://github.com/angular/angular-cli/issues/5618#issuecomment-450151214 contains instructions on how to increase this limit.

ng version on my developer machine:
Angular CLI: 7.2.3
Node: 8.9.4
OS: win32 x64
Angular: 7.2.3
... animations, cli, common, compiler, compiler-cli, core, forms
... http, platform-browser, platform-browser-dynamic
... platform-server, router

Package                           Version
-----------------------------------------------------------
@angular-devkit/architect         0.11.2
@angular-devkit/build-angular     0.11.2
@angular-devkit/build-optimizer   0.11.2
@angular-devkit/build-webpack     0.11.2
@angular-devkit/core              7.1.2
@angular-devkit/schematics        7.2.3
@angular/language-service         7.2.0
@ngtools/webpack                  7.1.2
@schematics/angular               7.2.3
@schematics/update                0.12.3
rxjs                              6.3.3
typescript                        3.1.6
webpack                           4.23.1

Build Agent, I currently have no way of getting that info, but it should be very similar as I am not aware that we installed angular-cli globally.
Thanks for the hint with memory. It might very well be the cause as our build agents are notoriously low on memory.

BTW, we already encountered issues with the node memory limit, so we are using this command to run our build:
npm run ng-high-memory -- build --base-href=/XYZ/ --configuration=production
with ng-high-memory being defined as:
"ng-high-memory": "node --max_old_space_size=8000 ./node_modules/@angular/cli/bin/ng"

I'd also update @angular-devkit/build-angular to the latest version btw. That's the actual build system. Memory is limited by NodeJS itself btw, so even on a machine with a lot of memory you won't be using it by default unless you use those scripts.
Also your total bundle might get quite smaller if you don't have the vendor bundle in production.
At the end of the day you do have over 8mb of code post optimizations... that's a lot of code. And it looks like the benefits from Build Optimizer might be marginal at for your code base. It is a reasonable option to turn it off if it's not worth the extra build time.

Thanks for the hints. We actually did experiment without the vendor chunk and the differences in size were marginal, even more than the difference with the build optimizer.
Regarding the overall size: You are correct, it's a lot. We are currently in the process of optimizing our dependencies, which hopefully shaves of some megabytes

Now I do have such a hanging build again, after I updated @angular-devkit/build-angular. And the strange thing is that the node process uses about 1.4GB but no CPU at all. It just sits there, and idles. What could cause such behaviour?

1.4gb is just at the memory limit. I'd say that's the reason.

OK, but we are using ng-high-memory. Shouldn't this solve those kinds of problems?

It should indeed. I'm not sure what's happening in your project :/
I know some older versions of node had memory issues as well, so maybe node 10 helps but... being stuck at 1.4 makes it really look like the node memory flag isn't being applied. I've also seen it referenced as  --max-old-space-size (dashes instead of underscore) but I'd be surprised if that was it.

It's so strange. I just saw the memory go well over that limit, so the option is working. And now, the build worked again. But at times, it just doesn't.
Thanks for your help. If I will ever find out what's going on I will let you know.

Are you using Windows with WSL? I saw something similar once with WSL, where it really looked like the linux kernel just decided to kill off all the Terser child processes or something and it just hung there, doing nothing.

Yes, I am currently on Windows 7, so there should be WSL there. And it matches what I saw:
When it worked, there was a child process that has been started and the main process had long stretches where it was idle.
When it didn't work, there was no child process, so it could very well be that it was killed. I will keep an eye on that.


fix gke/macos bug

Removing duplicated code that introduced #1050 for Macs.
fixes #1050

Can this be merged?


Updated stmt_block diagram

Updated stmt_block. This update is required for new diagrams to not break the build with broken links.

This change is

Online preview: http://cockroach-docs-review.s3-website-us-east-1.amazonaws.com/d142e135f7bb3200b85aed594e2374caec6cf04f/


Updates for functionality to directly add the address

Also, if someone can add support for directly adding ENS names, that would be great. Was trying to figure that out

This should be included in the Tip Party 2.0 updates


Homework 8

Screenshots:
https://docs.google.com/document/d/17wGdgoia1FKaVFxKI053dpdQF1dM-3YZOPf0aJEVlaQ/edit?usp=sharing
Lessons learnt:

Demonstrate GET, POST, PUT and DELETE requests.
Demonstrate the use of url and query params
Demonstrate the use of @RequestBody and @Valid annotations
Demonstrate the of ResponseEntity
Implement controller-service-repository project structure

Metric
Value

alert_status
:white_check_mark: OK

bugs
0

code_smells
13

reliability_rating
A (0 Bugs)Note: A being best, E being worst

security_rating
A (0 Vulnerabilities)Note: A being best, E being worst

vulnerabilities
0

Metric
Value

alert_status
:x: ERROR

bugs
0

code_smells
15

reliability_rating
A (0 Bugs)Note: A being best, E being worst

security_rating
A (0 Vulnerabilities)Note: A being best, E being worst

vulnerabilities
0


querydsl-mongodb: usage of concat gives illegal operation

Hi,
with querydsl-mongodb version 4.2.2 or 4.3.1 concatenating fields using
QNotification.notification.name2.concat(" ").concat(QNotification.notification.name1)          .containsIgnoreCase(searchString)
gives an StackTrace containing
Caused by: java.lang.UnsupportedOperationException: Illegal operation notification.name2 +   + notification.name1 	at org.springframework.data.mongodb.repository.support.MongodbDocumentSerializer.visit(MongodbDocumentSerializer.java:323) 	at org.springframework.data.mongodb.repository.support.MongodbDocumentSerializer.visit(MongodbDocumentSerializer.java:54)
when executing the query.

It seems as if the mongo db itself does not support this operation, so this not an issue with querydsl. My solution was to store name2 + '  ' + name1 as separate field in the database to be able to execute my desired query.


feat: adding support for webhook notifications

This will enable the use of webhook notifications within alerts using the recent SDK release.
Currently, you will receive an error if you set up alert rule notifications that use a custom webhook integration (for example, a Microsoft Teams integration data source) within Terraform.
Any feedback would be appreciated, thank you!
@joaomper-TE @shahid-te @pedro-te @phpinhei-te

@cbhoffman thanks for contributing. FYI the build is failing because of this:
https://github.com/thousandeyes/terraform-provider-thousandeyes?tab=readme-ov-file#maintainers
The docs/ folder should not be changed manually. Instead, if there are changes to the examples, inputs/outputs of any data_source or resource, you need to run go generate locally and commit the resulting changes to the .md files.

Ok thanks for letting me know, sorry about that! I'll fix this morning.

When possible, can someone approve the workflow please. @joaomper-TE @shahid-te

@cbhoffman release under v2.0.8 https://github.com/thousandeyes/terraform-provider-thousandeyes/releases/tag/v2.0.8


Revise tools scripts to be python3 compatible

Fixes python3 encoding compatibility problems in test262-harness.py
resolved the following issues:
"""
Traceback (most recent call last):
File "/usr/lib/python3.8/multiprocessing/pool.py", line 125, in worker
result = (True, func(*args, **kwds))
File "/home/runner/work/jerryscript/jerryscript/tools/runners/test262-harness.py", line 658, in test_case_run_process
return case.run()
File "/home/runner/work/jerryscript/jerryscript/tools/runners/test262-harness.py", line 623, in run
result = self.run_test_in(tmp)
File "/home/runner/work/jerryscript/jerryscript/tools/runners/test262-harness.py", line 617, in run_test_in
(code, out, err) = TestCase.execute(command)
File "/home/runner/work/jerryscript/jerryscript/tools/runners/test262-harness.py", line 605, in execute
err = stderr.read()
File "/home/runner/work/jerryscript/jerryscript/tools/runners/test262-harness.py", line 405, in read
return result.decode()
UnicodeDecodeError: 'utf-8' codec can't decode byte 0xf0 in position 255: invalid continuation byte
"""
Traceback (most recent call last):
File "C:\work\study\languages\typescript\jerryscript\tools\runners\test262-harness.py", line 933, in
sys.exit(main())
File "C:\work\study\languages\typescript\jerryscript\tools\runners\test262-harness.py", line 921, in main
code = test_suite.run(options.command, args,
File "C:\work\study\languages\typescript\jerryscript\tools\runners\test262-harness.py", line 821, in run
cases = self.enumerate_tests(tests, command_template)
File "C:\work\study\languages\typescript\jerryscript\tools\runners\test262-harness.py", line 768, in enumerate_tests
strict_case = TestCase(self, name, full_path, True, command_template)
File "C:\work\study\languages\typescript\jerryscript\tools\runners\test262-harness.py", line 486, in init
self.contents = file_desc.read()
UnicodeDecodeError: 'gbk' codec can't decode byte 0x93 in position 438: illegal multibyte sequence
=== Summary - updating excludelist ===
"""
Traceback (most recent call last):
File "C:\Python38\lib\multiprocessing\pool.py", line 125, in worker
result = (True, func(*args, **kwds))
File "C:\work\study\languages\typescript\jerryscript\tools\runners\test262-harness.py", line 658, in test_case_run_process
return case.run()
File "C:\work\study\languages\typescript\jerryscript\tools\runners\test262-harness.py", line 623, in run
result = self.run_test_in(tmp)
File "C:\work\study\languages\typescript\jerryscript\tools\runners\test262-harness.py", line 612, in run_test_in
tmp.write(self.get_source())
File "C:\work\study\languages\typescript\jerryscript\tools\runners\test262-harness.py", line 564, in get_source
self.get_additional_includes() +
File "C:\work\study\languages\typescript\jerryscript\tools\runners\test262-harness.py", line 548, in get_additional_includes
return '\n'.join([self.suite.get_include(include) for include in self.get_include_list()])
File "C:\work\study\languages\typescript\jerryscript\tools\runners\test262-harness.py", line 548, in
return '\n'.join([self.suite.get_include(include) for include in self.get_include_list()])
File "C:\work\study\languages\typescript\jerryscript\tools\runners\test262-harness.py", line 738, in get_include
contents = file_desc.read()
UnicodeDecodeError: 'gbk' codec can't decode byte 0xaa in position 33422: illegal multibyte sequence
"""
If the temp file are opened in text mode, when concat the js test
file, it's will alter the js content, especially about the raw literal string.
It's will alter the raw literal string result on Windows.
This is a partial fixes es2015 tests:
  built-ins/String/raw/special-characters.js
  language/expressions/template-literal/tv-line-continuation.js
  language/expressions/template-literal/tv-line-terminator-sequence.js

in https://github.com/jerryscript-project/jerryscript/issues/4384
Fixes https://github.com/lygstate/jerryscript/runs/1690221009?check_suite_focus=true
When use python2
Fix stdout encoding for python2 and python3
Traceback (most recent call last):
  File "C:\work\study\languages\typescript\jerryscript\tools\runners\test262-harness.py", line 1019, in <module>
    sys.exit(main())
  File "C:\work\study\languages\typescript\jerryscript\tools\runners\test262-harness.py", line 1009, in main
    code = test_suite.run(options.command, args,
  File "C:\work\study\languages\typescript\jerryscript\tools\runners\test262-harness.py", line 930, in run
    progress.has_run(result)
  File "C:\work\study\languages\typescript\jerryscript\tools\runners\test262-harness.py", line 753, in has_run
    result.report_outcome(True)
  File "C:\work\study\languages\typescript\jerryscript\tools\runners\test262-harness.py", line 492, in report_outcome
    self.write_output(sys.stdout)
  File "C:\work\study\languages\typescript\jerryscript\tools\runners\test262-harness.py", line 506, in write_output
    target.write("--- errors ---  \n %s" % error)
UnicodeEncodeError: 'gbk' codec can't encode character '\xab' in position 52: illegal multibyte sequence
...............................................=== Summary - updating excludelist ===

JerryScript-DCO-1.0-Signed-off-by: Yonggang Luo<EMAIL_ADDRESS>

Do we need it to be able to use our harness for ES5.1 version of test262? If yes, it would be great to mention it in the commit log at least.

Do we need it to be able to use our harness for ES5.1 version of test262? If yes, it would be great to mention it in the commit log at least.

During the review of the current version of the PR, I've found a potentially useful (and definitely interesting) approach to the problem, which may reduce the necessary code changes considerably. With just two lines of code (per tool), the unicode encode/decode errors can be disabled/hidden/ignored:
import codecs
codecs.register_error("strict", codecs.ignore_errors)

(source: https://stackoverflow.com/questions/9537356/can-i-make-decodeerrors-ignore-the-default-for-all-strings-in-a-python-2-7-p)
This would be worth a try. Then, no stdour/err would be necessary, no polluting of the code with encodes/decodes, no codecs.open instead of open, etc. (Hopefully.)

During the review of the current version of the PR, I've found a potentially useful (and definitely interesting) approach to the problem, which may reduce the necessary code changes considerably. With just two lines of code (per tool), the unicode encode/decode errors can be disabled/hidden/ignored:
import codecs
codecs.register_error("strict", codecs.ignore_errors)

(source: https://stackoverflow.com/questions/9537356/can-i-make-decodeerrors-ignore-the-default-for-all-strings-in-a-python-2-7-p)
This would be worth a try. Then, no stdour/err would be necessary, no polluting of the code with encodes/decodes, no codecs.open instead of open, etc. (Hopefully.)

Yeap, I know this method, but the following are still better.
def setup_stdio():
    (out_stream, err_stream) = (sys.stdout, sys.stderr)
    if sys.version_info.major >= 3:
        (out_stream, err_stream) = (sys.stdout.buffer, sys.stderr.buffer)
    # For tty using native encoding, otherwise (pipe) use 'utf-8'
    encoding = sys.stdout.encoding if sys.stdout.isatty() else 'utf-8'
    # Always override it to anvoid encode error
    sys.stdout = codecs.getwriter(encoding)(out_stream, 'ignore')
    sys.stderr = codecs.getwriter(encoding)(err_stream, 'ignore')

codec ignore is just hidden the error when output isatty, but when we do piping, we always using the 'utf8-8' encoding.
Otherwise the characters will lost in tests script :(
That's why setup_stdio are important, not just simple ignore it

During the review of the current version of the PR, I've found a potentially useful (and definitely interesting) approach to the problem, which may reduce the necessary code changes considerably. With just two lines of code (per tool), the unicode encode/decode errors can be disabled/hidden/ignored:
import codecs
codecs.register_error("strict", codecs.ignore_errors)

(source: https://stackoverflow.com/questions/9537356/can-i-make-decodeerrors-ignore-the-default-for-all-strings-in-a-python-2-7-p)
This would be worth a try. Then, no stdour/err would be necessary, no polluting of the code with encodes/decodes, no codecs.open instead of open, etc. (Hopefully.)

Yeap, I know this method, but the following are still better.
def setup_stdio():
    (out_stream, err_stream) = (sys.stdout, sys.stderr)
    if sys.version_info.major >= 3:
        (out_stream, err_stream) = (sys.stdout.buffer, sys.stderr.buffer)
    # For tty using native encoding, otherwise (pipe) use 'utf-8'
    encoding = sys.stdout.encoding if sys.stdout.isatty() else 'utf-8'
    # Always override it to anvoid encode error
    sys.stdout = codecs.getwriter(encoding)(out_stream, 'ignore')
    sys.stderr = codecs.getwriter(encoding)(err_stream, 'ignore')

codec ignore is just hidden the error when output isatty, but when we do piping, we always using the 'utf8-8' encoding.
Otherwise the characters will lost in tests script :(
That's why setup_stdio are important, not just simple ignore it

@ossy-szeged  any progress of the PR? after this, I can create PR that support python3 debugger


Solution to "require" css in sass

How to include css file in sass to get one output file and not break sourcemap?
I use two files now, one with sass and second with .css import.
For second file I use "gulp-cssimport".
And for production version, when sourcemap not needed, these files can be concatenated.
Is there any better solution? Some browserify for css or sprockets require syntax?

css is valid sass you could just import it as if it was sass? ;)

@import "file.css"
will be compiled to css import tag,
but I want to include content of file.css to one file.

And renaming to scss isnt very comfortable when using vendor components.

Found a way

create css file with @import requirements
use "gulp-cssimport" on it
use "gulp-rename" to rename file in stream to file to .scss
store it in generated folder
import generated scss file in main sass file, it will be concatenated as other and sourcemap works

Imported css files are from vendor components, so I'm not realy care of getting real sourcemap for them, concatenated file is ok.
It works, but may be there are cleaner way? Without generating scss file from requirements.
My experiments are there
https://github.com/ValeryVS/gulp-blank-project

This is a very common problem: https://github.com/sass/sass/issues/556
Personally I just copy, rename, and import as SCSS.

@ValeryVS You could just write a postinstall command in your package.json to copy the .css file to .scss within it's source folder.

Yeah, I tend to just change the extension to .scss as well. Valid css is valid scss, so there's no harm.


Disqus integration

From https://squidfunk.github.io/mkdocs-material/getting-started/#disqus-integation
Partial: https://github.com/squidfunk/mkdocs-material/blob/master/src/partials/disqus.html

I am closing this for now, because Disqus integation was removed:
https://squidfunk.github.io/mkdocs-material/changelog/#8.0.0

Removed Disqus integation – use customization


Update resources.txt

disable the main information resource and national bank of Kyrgyzstan, due to the support of the Russian authorities

Шіт, ми вже з трьома країнами воюємо?


Components / Intro page text should be left aligned (currently centered)

The text should be left aligned so it lines up with the image at the left, and the body copy should wrap at 640 pixels (currently narrower):

Can we also make the text wrap at 640 width? (currently like 540) to make it not so tall!!! THANK YOU!!!!!!!