HyperHDR color calibration setting not persisting across reboot

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

2024-05-13T22:57:31.923Z [CORE] TTY is not attached to the log output
2024-05-13T22:57:31.981Z [MAIN] Database path: '/home/pi/.hyperhdr/db/hyperhdr.db', readonlyMode = disabled
2024-05-13T22:57:31.985Z [MAIN] Starting HyperHdr - <IP_ADDRESS>, (HEAD detached at v<IP_ADDRESS>) (awawa-dev-9e960c9/52f12b4-1711236142), built: Mar 23 2024:23:54:53
2024-05-13T22:57:31.985Z [MAIN] Set user data path to '/home/pi/.hyperhdr'
2024-05-13T22:57:31.987Z [INSTANCE_CFG] Loading instance configuration
2024-05-13T22:57:32.037Z [DB] Database opened: /home/pi/.hyperhdr/db/hyperhdr.db
2024-05-13T22:57:32.114Z [INSTANCE_CFG] Settings database initialized
2024-05-13T22:57:32.120Z [SOUND_GRABBER] Sound device is disabled
2024-05-13T22:57:32.199Z [JSONSERVER] (JsonServer.cpp:26) Created new instance
2024-05-13T22:57:32.205Z [JSONSERVER] Started on port 19444
2024-05-13T22:57:32.207Z [SSDP] (SSDPHandler.cpp:31) SSDPHandler is initialized
2024-05-13T22:57:32.171Z [V4L2:USB3.0 UHD: US] (GrabberWrapper.cpp:55) Starting the grabber wrapper
2024-05-13T22:57:32.172Z [V4L2:USB3.0 UHD: US] Found capture device: /dev/video15
2024-05-13T22:57:32.172Z [HYPERHDR0] Starting the instance
2024-05-13T22:57:32.172Z [INSTANCE_CFG0] Loading instance configuration
2024-05-13T22:57:32.172Z [V4L2:USB3.0 UHD: US] Found capture device: /dev/video21
2024-05-13T22:57:32.172Z [DB] Database opened: /home/pi/.hyperhdr/db/hyperhdr.db
2024-05-13T22:57:32.173Z [V4L2:USB3.0 UHD: US] Found capture device: /dev/video14
2024-05-13T22:57:32.173Z [V4L2:USB3.0 UHD: US] Found capture device: /dev/video22
2024-05-13T22:57:32.175Z [HYPERHDR1] Starting the instance
2024-05-13T22:57:32.175Z [X11_SYSTEM:AUTO] Loaded X11 proxy library for screen capturing
2024-05-13T22:57:32.182Z [DAEMON] The system doesn't support the X11 system grabber
2024-05-13T22:57:32.182Z [DAEMON] The system doesn't support the framebuffer system grabber
2024-05-13T22:57:32.182Z [X11_SYSTEM:auto] (SystemWrapper.cpp:71) Closing grabber: X11_SYSTEM:auto
2024-05-13T22:57:32.182Z [FRAMEBUF_SYSTEM:auto] (SystemWrapper.cpp:71) Closing grabber: FRAMEBUF_SYSTEM:auto
2024-05-13T22:57:32.231Z [INSTANCE_CFG0] Settings database initialized
2024-05-13T22:57:32.231Z [INSTANCE_CFG1] Loading instance configuration
2024-05-13T22:57:32.231Z [COMPONENTCTRL0] (ComponentController.cpp:31) ComponentController is initialized. Components are ENABLED
2024-05-13T22:57:32.231Z [DB] Database opened: /home/pi/.hyperhdr/db/hyperhdr.db
2024-05-13T22:57:32.234Z [MUXER0] (Muxer.cpp:55) Muxer initialized
2024-05-13T22:57:32.234Z [BLACKBORDER] Set mode to: letterbox
2024-05-13T22:57:32.234Z [COMPONENTCTRL0] Blackborder detector: enabled
2024-05-13T22:57:32.234Z [IMAGETOLED_MNG0] (ImageToLedManager.cpp:192) Set LED mapping type to advanced
2024-05-13T22:57:32.234Z [IMAGETOLED_MNG0] (ImageToLedManager.cpp:176) setSparseProcessing to 0
2024-05-13T22:57:32.235Z [IMAGETOLED_MNG0] (ImageToLedManager.cpp:103) ImageToLedManager initialized
2024-05-13T22:57:32.240Z [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-13T22:57:32.240Z [LED_CALIBRATION0] (LedCalibration.cpp:101) Calibration config '0' for LED segment: [0, 259]
2024-05-13T22:57:32.242Z [HYPERHDR0] Led strip RGB order is: bgr
2024-05-13T22:57:32.243Z [SMOOTHING0] High resolution clock is NOT STEADY!
2024-05-13T22:57:32.243Z [SMOOTHING0] Clearing queued colors before: enabling
2024-05-13T22:57:32.243Z [SMOOTHING0] Smoothing queue is cleared
2024-05-13T22:57:32.243Z [COMPONENTCTRL0] Smoothing: enabled
2024-05-13T22:57:32.243Z [SMOOTHING0] Creating config (0) => type: Alternative, dirMode: false, pause: false, settlingTime: 150ms, interval: 11ms (90Hz), antiFlickTres: 0, antiFlickStep: 0, antiFlickTime: 0
2024-05-13T22:57:32.243Z [SMOOTHING0] Clearing queued colors before: enabling. Smoothing configuration changed: restarting timer.
2024-05-13T22:57:32.243Z [SMOOTHING0] Smoothing queue is cleared
2024-05-13T22:57:32.243Z [SMOOTHING0] Selecting config (0) => type: Alternative, directMode: false, pause: false, settlingTime: 150ms, interval: 11ms (90Hz), antiFlickTres: 0, antiFlickStep: 0, antiFlickTime: 0
2024-05-13T22:57:32.243Z [SMOOTHING0] Selecting config (0) => type: Alternative, directMode: false, pause: false, settlingTime: 150ms, interval: 11ms (90Hz), antiFlickTres: 0, antiFlickStep: 0, antiFlickTime: 0
2024-05-13T22:57:32.244Z [LEDDEVICE0_SK9822] Start LedDevice 'sk9822'.
2024-05-13T22:57:32.244Z [LEDDEVICE0_SK9822] (LedDevice.cpp:337) deviceConfig: [{"colorOrder":"bgr","currentLedCount":260,"globalBrightnessControlMaxLevel":30,"globalBrightnessControlThreshold":255,"invert":false,"output":"/dev/spidev0.0","rate":2000000,"refreshTime":11,"smoothingRefreshTime":11,"type":"sk9822"}]
2024-05-13T22:57:32.244Z [LEDDEVICE0_SK9822] Ignoring user LED refresh rate. Forcing smoothing refresh rate = 90.91 Hz
2024-05-13T22:57:32.244Z [LEDDEVICE0_SK9822] (LedDevice.cpp:423) Refresh rate = 90.91 Hz
2024-05-13T22:57:32.244Z [LEDDEVICE0_SK9822] (LedDevice.cpp:373) Device is not ready to start a timer
2024-05-13T22:57:32.244Z [LEDDEVICE0_SK9822] (LedDevice.cpp:433) Refresh interval updated to 11ms
2024-05-13T22:57:32.244Z [LEDDEVICE0_SK9822] (ProviderSpi.cpp:52) Speed: 2000000, Type:
2024-05-13T22:57:32.244Z [LEDDEVICE0_SK9822] (ProviderSpi.cpp:53) Inverted: no, Mode: 0
2024-05-13T22:57:32.244Z [LEDDEVICE0_SK9822] 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-13T22:57:32.244Z [LEDDEVICE0_SK9822] [SK9822] Using global brightness control with threshold of 255 and max level of 30
2024-05-13T22:57:32.244Z [LEDDEVICE0_SK9822] (LedDevice.cpp:247) Enable the device
2024-05-13T22:57:32.244Z [LEDDEVICE0_SK9822] (LedDevice.cpp:64) Switch on
2024-05-13T22:57:32.244Z [LEDDEVICE0_SK9822] (LedDevice.cpp:140) Power On
2024-05-13T22:57:32.244Z [LEDDEVICE0_SK9822] (LedDevice.cpp:367) Starting timer with interval = 11ms
2024-05-13T22:57:32.245Z [HYPER_MANAGER] HyperHDR instance 'First LED instance' has been started
2024-05-13T22:57:32.245Z [HYPERHDR0] The instance is running
2024-05-13T22:57:32.245Z [MUXER0] Register new input 'System/VIDEOGRABBER' with priority 240 as inactive
2024-05-13T22:57:32.245Z [COMPONENTCTRL0] Video capture device: enabled
2024-05-13T22:57:32.245Z [CEC] Opening libCEC library.
2024-05-13T22:57:32.245Z [CEC] CEC object created
2024-05-13T22:57:32.245Z [CEC] Starting CEC handler.
2024-05-13T22:57:33.798Z [CEC] Success. CEC adapter type 'Linux' is ready (/dev/cec0, /sys/devices/platform/soc/fef00700.hdmi/cec0)
2024-05-13T22:57:33.799Z [CEC] Success: libCEC library loaded.
2024-05-13T22:57:32.245Z [COMPONENTCTRL0] LED device: enabled
2024-05-13T22:57:32.245Z [SMOOTHING0] Using alternative smoothing input (0)
2024-05-13T22:57:32.245Z [EFFECTENGINE0] Run effect "Rainbow swirl" on channel 254
2024-05-13T22:57:32.267Z [SMOOTHING0] Using alternative smoothing procedure (0)
2024-05-13T22:57:32.276Z [INSTANCE_CFG1] Settings database initialized
2024-05-13T22:57:32.276Z [COMPONENTCTRL1] (ComponentController.cpp:31) ComponentController is initialized. Components are ENABLED
2024-05-13T22:57:32.278Z [MUXER1] (Muxer.cpp:55) Muxer initialized
2024-05-13T22:57:32.278Z [BLACKBORDER] Set mode to: default
2024-05-13T22:57:32.278Z [COMPONENTCTRL1] Blackborder detector: enabled
2024-05-13T22:57:32.278Z [IMAGETOLED_MNG1] (ImageToLedManager.cpp:192) Set LED mapping type to advanced
2024-05-13T22:57:32.278Z [IMAGETOLED_MNG1] (ImageToLedManager.cpp:176) setSparseProcessing to 0
2024-05-13T22:57:32.278Z [IMAGETOLED_MNG1] (ImageToLedManager.cpp:103) ImageToLedManager initialized
2024-05-13T22:57:32.279Z [COLORSPACE_CALIBRATION1] classicMode: no, gammas:[1.50, 1.50, 1.50], saturation: 1.00, luminance: 1.00, backLight: [enabled, threshold: 0, colored: no]
2024-05-13T22:57:32.279Z [LED_CALIBRATION1] (LedCalibration.cpp:101) Calibration config '0' for LED segment: [0, 102]
2024-05-13T22:57:32.280Z [HYPERHDR1] Led strip RGB order is: rgb
2024-05-13T22:57:32.280Z [EFFECTENGINE0] (EffectEngine.cpp:92) Start the effect: name [Rainbow swirl]
2024-05-13T22:57:32.280Z [MUXER0] Register new input 'System/EFFECT' with priority 254 as inactive
2024-05-13T22:57:32.280Z [SMOOTHING1] High resolution clock is NOT STEADY!
2024-05-13T22:57:32.280Z [SMOOTHING1] Clearing queued colors before: enabling
2024-05-13T22:57:32.280Z [SMOOTHING1] Smoothing queue is cleared
2024-05-13T22:57:32.280Z [COMPONENTCTRL1] Smoothing: enabled
2024-05-13T22:57:32.280Z [SMOOTHING1] Creating config (0) => type: Alternative, dirMode: false, pause: false, settlingTime: 150ms, interval: 16ms (62Hz), antiFlickTres: 0, antiFlickStep: 0, antiFlickTime: 0
2024-05-13T22:57:32.280Z [SMOOTHING1] Clearing queued colors before: enabling. Smoothing configuration changed: restarting timer.
2024-05-13T22:57:32.280Z [HYPERHDR0] Background effect: animation set to 'Rainbow swirl' [started]
2024-05-13T22:57:32.280Z [SMOOTHING1] Smoothing queue is cleared
2024-05-13T22:57:32.280Z [SMOOTHING1] Selecting config (0) => type: Alternative, directMode: false, pause: false, settlingTime: 150ms, interval: 16ms (62Hz), antiFlickTres: 0, antiFlickStep: 0, antiFlickTime: 0
2024-05-13T22:57:32.280Z [SMOOTHING1] Selecting config (0) => type: Alternative, directMode: false, pause: false, settlingTime: 150ms, interval: 16ms (62Hz), antiFlickTres: 0, antiFlickStep: 0, antiFlickTime: 0
2024-05-13T22:57:32.281Z [V4L2:USB3.0 UHD: US] Found capture device: /dev/video0
2024-05-13T22:57:32.281Z [EFFECTENGINE0] Run effect "Rainbow swirl" on channel 0
2024-05-13T22:57:32.281Z [EFFECTENGINE0] (EffectEngine.cpp:92) Start the effect: name [Rainbow swirl]
2024-05-13T22:57:32.281Z [MUXER0] Register new input 'System/EFFECT' with priority 0 as inactive
2024-05-13T22:57:32.281Z [LEDDEVICE1_ADALIGHT] Start LedDevice 'adalight'.
2024-05-13T22:57:32.281Z [LEDDEVICE1_ADALIGHT] (LedDevice.cpp:337) deviceConfig: [{"awa_mode":true,"colorOrder":"rgb","currentLedCount":103,"espHandshake":true,"forceSerialDetection":true,"maxRetry":0,"output":"ttyACM0","rate":2000000,"refreshTime":16,"smoothingRefreshTime":16,"type":"adalight","white_channel_calibration":false}]
2024-05-13T22:57:32.281Z [LEDDEVICE1_ADALIGHT] Ignoring user LED refresh rate. Forcing smoothing refresh rate = 62.50 Hz
2024-05-13T22:57:32.281Z [HYPERHDR0] Boot effect: animation set to 'Rainbow swirl' [started]
2024-05-13T22:57:32.281Z [LEDDEVICE1_ADALIGHT] (LedDevice.cpp:423) Refresh rate = 62.50 Hz
2024-05-13T22:57:32.281Z [LEDDEVICE1_ADALIGHT] (LedDevice.cpp:373) Device is not ready to start a timer
2024-05-13T22:57:32.281Z [LEDDEVICE1_ADALIGHT] (LedDevice.cpp:433) Refresh interval updated to 16ms
2024-05-13T22:57:32.281Z [LEDDEVICE1_ADALIGHT] (ProviderSerial.cpp:50) DeviceType   : adalight
2024-05-13T22:57:32.281Z [LEDDEVICE1_ADALIGHT] (ProviderSerial.cpp:51) LedCount     : 103
2024-05-13T22:57:32.281Z [LEDDEVICE1_ADALIGHT] (ProviderSerial.cpp:52) RefreshTime  : 16
2024-05-13T22:57:32.281Z [LEDDEVICE1_ADALIGHT] (ProviderSerial.cpp:67) Device name   : ttyACM0
2024-05-13T22:57:32.281Z [LEDDEVICE1_ADALIGHT] (ProviderSerial.cpp:68) Auto selection: 0
2024-05-13T22:57:32.281Z [LEDDEVICE1_ADALIGHT] (ProviderSerial.cpp:69) Baud rate     : 2000000
2024-05-13T22:57:32.281Z [LEDDEVICE1_ADALIGHT] (ProviderSerial.cpp:70) ESP handshake : ON
2024-05-13T22:57:32.281Z [LEDDEVICE1_ADALIGHT] (ProviderSerial.cpp:71) Force ESP/Pico Detection : ON
2024-05-13T22:57:32.281Z [LEDDEVICE1_ADALIGHT] (ProviderSerial.cpp:72) Delayed open  : 0
2024-05-13T22:57:32.281Z [LEDDEVICE1_ADALIGHT] (ProviderSerial.cpp:73) Retry limit   : 0
2024-05-13T22:57:32.281Z [LEDDEVICE1_ADALIGHT] 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-13T22:57:32.281Z [LEDDEVICE1_ADALIGHT] (LedDeviceAdalight.cpp:79) Adalight driver with activated high speeed & data integration check AWA protocol
2024-05-13T22:57:32.281Z [LEDDEVICE1_ADALIGHT] (LedDeviceAdalight.cpp:88) Adalight header for 103 leds: Awa 0x00 0x66 0x33
2024-05-13T22:57:32.281Z [LEDDEVICE1_ADALIGHT] (LedDevice.cpp:247) Enable the device
2024-05-13T22:57:32.281Z [LEDDEVICE1_ADALIGHT] Opening UART: ttyACM0
2024-05-13T22:57:32.281Z [LEDDEVICE1_ADALIGHT] (ProviderSerial.cpp:209) _serialPort.open(QIODevice::ReadWrite): ttyACM0, Baud rate [2000000]bps
2024-05-13T22:57:33.799Z [HYPER_MANAGER] HyperHDR instance 'WLED Cabinet' has been started
2024-05-13T22:57:32.282Z [HYPERHDR1] The instance is running
2024-05-13T22:57:32.282Z [MUXER1] Register new input 'System/VIDEOGRABBER' with priority 240 as inactive
2024-05-13T22:57:32.282Z [COMPONENTCTRL1] Video capture device: enabled
2024-05-13T22:57:32.282Z [EFFECTENGINE1] Run effect "Waves with Color" on channel 254
2024-05-13T22:57:32.283Z [EFFECTENGINE1] (EffectEngine.cpp:92) Start the effect: name [Waves with Color]
2024-05-13T22:57:32.283Z [MUXER1] Register new input 'System/EFFECT' with priority 254 as inactive
2024-05-13T22:57:32.283Z [HYPERHDR1] Background effect: animation set to 'Waves with Color' [started]
2024-05-13T22:57:32.292Z [EFFECT1(Waves ...)] Begin playing the effect with priority: 254
2024-05-13T22:57:32.292Z [EFFECT0(Rainbo...)] Begin playing the effect with priority: 254
2024-05-13T22:57:32.293Z [EFFECT0(Rainbo...)] Begin playing the effect with priority: 0
2024-05-13T22:57:32.293Z [V4L2:USB3.0 UHD: US] (V4L2Grabber.cpp:406) Device has 'brightness' control => min: 0, max: 100, default: 50
2024-05-13T22:57:32.296Z [MUXER1] Priority 254 is now active
2024-05-13T22:57:32.296Z [MUXER1] Set visible priority to 254
2024-05-13T22:57:32.296Z [HYPERHDR1] New priority[254], previous [255]
2024-05-13T22:57:32.296Z [HYPERHDR1] New source available -> switch LED-Device on
2024-05-13T22:57:32.296Z [SMOOTHING1] Clearing queued colors before: enabling
2024-05-13T22:57:32.296Z [SMOOTHING1] Smoothing queue is cleared
2024-05-13T22:57:32.296Z [COLORSPACE_CALIBRATION1] (ColorSpaceCalibration.cpp:225) setBackLightEnabled: 0
2024-05-13T22:57:32.296Z [IMAGETOLED_MNG1] Total index number is: 412 (memory: 412). User sparse processing is: disabled, image size: 80 x 45, area number: 103
2024-05-13T22:57:32.304Z [MUXER0] Priority 254 is now active
2024-05-13T22:57:32.304Z [MUXER0] Set visible priority to 254
2024-05-13T22:57:32.304Z [SMOOTHING0] Clearing queued colors before: enabling. Smoothing configuration changed: restarting timer.
2024-05-13T22:57:32.304Z [SMOOTHING0] Smoothing queue is cleared
2024-05-13T22:57:32.304Z [SMOOTHING0] Selecting config (2) => type: Linear, directMode: false, pause: false, settlingTime: 200ms, interval: 40ms (25Hz), antiFlickTres: 0, antiFlickStep: 0, antiFlickTime: 0
2024-05-13T22:57:32.304Z [LEDDEVICE0_SK9822] (LedDevice.cpp:381) Stopping refresh timer
2024-05-13T22:57:32.304Z [SMOOTHING0] Using linear smoothing input (2)
2024-05-13T22:57:32.304Z [HYPERHDR0] New priority[254], previous [255]
2024-05-13T22:57:32.304Z [HYPERHDR0] New source available -> switch LED-Device on
2024-05-13T22:57:32.304Z [LEDDEVICE0_SK9822] Ignoring user LED refresh rate. Forcing smoothing refresh rate = 25.00 Hz
2024-05-13T22:57:32.304Z [SMOOTHING0] Clearing queued colors before: enabling
2024-05-13T22:57:32.304Z [LEDDEVICE0_SK9822] (LedDevice.cpp:423) Refresh rate = 25.00 Hz
2024-05-13T22:57:32.305Z [SMOOTHING0] Smoothing queue is cleared
2024-05-13T22:57:32.305Z [LEDDEVICE0_SK9822] (LedDevice.cpp:367) Starting timer with interval = 40ms
2024-05-13T22:57:32.305Z [LEDDEVICE0_SK9822] (LedDevice.cpp:433) Refresh interval updated to 40ms
2024-05-13T22:57:32.305Z [LEDDEVICE0_SK9822] (LedDevice.cpp:448) LED refresh interval adjustment caused by smoothing configuration change to 40ms (proposed: 40ms)
2024-05-13T22:57:32.305Z [LEDDEVICE0_SK9822] (LedDevice.cpp:247) Enable the device
2024-05-13T22:57:32.305Z [COLORSPACE_CALIBRATION0] (ColorSpaceCalibration.cpp:225) setBackLightEnabled: 0
2024-05-13T22:57:32.305Z [IMAGETOLED_MNG0] Total index number is: 1040 (memory: 1040). User sparse processing is: disabled, image size: 80 x 45, area number: 260
2024-05-13T22:57:32.305Z [SMOOTHING0] Using linear smoothing input (2)
2024-05-13T22:57:32.305Z [MUXER0] Priority 0 is now active
2024-05-13T22:57:32.305Z [MUXER0] Set visible priority to 0
2024-05-13T22:57:32.305Z [HYPERHDR0] New priority[0], previous [254]
2024-05-13T22:57:32.306Z [V4L2:USB3.0 UHD: US] (V4L2Grabber.cpp:412) Device has 'contrast' control => min: 0, max: 100, default: 50
2024-05-13T22:57:32.320Z [V4L2:USB3.0 UHD: US] (V4L2Grabber.cpp:418) Device has 'saturation' control => min: 0, max: 100, default: 50
2024-05-13T22:57:32.321Z [LEDDEVICE1_ADALIGHT] (ProviderSerial.cpp:214) portName:          ttyACM0
2024-05-13T22:57:32.321Z [LEDDEVICE1_ADALIGHT] (ProviderSerial.cpp:215) systemLocation:    /dev/ttyACM0
2024-05-13T22:57:32.321Z [LEDDEVICE1_ADALIGHT] (ProviderSerial.cpp:216) description:       Pico
2024-05-13T22:57:32.321Z [LEDDEVICE1_ADALIGHT] (ProviderSerial.cpp:217) manufacturer:      Raspberry Pi
2024-05-13T22:57:32.321Z [LEDDEVICE1_ADALIGHT] (ProviderSerial.cpp:218) productIdentifier: 0xa
2024-05-13T22:57:32.321Z [LEDDEVICE1_ADALIGHT] (ProviderSerial.cpp:219) vendorIdentifier:  0x2e8a
2024-05-13T22:57:32.322Z [LEDDEVICE1_ADALIGHT] (ProviderSerial.cpp:220) serialNumber:      E660D4A0A78B4931
2024-05-13T22:57:32.324Z [LEDDEVICE1_ADALIGHT] Detected Rp2040 type board. HyperHDR skips the reset. State: 1, 1
2024-05-13T22:57:32.325Z [LEDDEVICE1_ADALIGHT] DETECTED DEVICE USING HyperSerialEsp8266/HyperSerialESP32/HyperSerialPico FIRMWARE (HyperHDR frames: 0 (FPS), receiv.: 0, good: 0, incompl.: 0, mem1: 0, mem2: 460, heap: 123232  Welcome! Awa driver 9.) at 2 msec
2024-05-13T22:57:32.326Z [LEDDEVICE1_ADALIGHT] (LedDevice.cpp:64) Switch on
2024-05-13T22:57:32.326Z [LEDDEVICE1_ADALIGHT] (LedDevice.cpp:140) Power On
2024-05-13T22:57:32.326Z [LEDDEVICE1_ADALIGHT] (LedDevice.cpp:367) Starting timer with interval = 16ms
2024-05-13T22:57:32.326Z [COMPONENTCTRL1] LED device: enabled
2024-05-13T22:57:32.326Z [LEDDEVICE1_ADALIGHT] (LedDevice.cpp:247) Enable the device
2024-05-13T22:57:32.326Z [SMOOTHING1] Clearing queued colors before: enabling. Smoothing configuration changed: restarting timer.
2024-05-13T22:57:32.326Z [SMOOTHING1] Smoothing queue is cleared
2024-05-13T22:57:32.326Z [SMOOTHING1] Selecting config (2) => type: Linear, directMode: false, pause: false, settlingTime: 200ms, interval: 40ms (25Hz), antiFlickTres: 0, antiFlickStep: 0, antiFlickTime: 0
2024-05-13T22:57:32.326Z [SMOOTHING1] Using linear smoothing input (2)
2024-05-13T22:57:32.326Z [LEDDEVICE1_ADALIGHT] (LedDevice.cpp:381) Stopping refresh timer
2024-05-13T22:57:32.326Z [LEDDEVICE1_ADALIGHT] Ignoring user LED refresh rate. Forcing smoothing refresh rate = 25.00 Hz
2024-05-13T22:57:32.326Z [LEDDEVICE1_ADALIGHT] (LedDevice.cpp:423) Refresh rate = 25.00 Hz
2024-05-13T22:57:32.326Z [LEDDEVICE1_ADALIGHT] (LedDevice.cpp:367) Starting timer with interval = 40ms
2024-05-13T22:57:32.326Z [LEDDEVICE1_ADALIGHT] (LedDevice.cpp:433) Refresh interval updated to 40ms
2024-05-13T22:57:32.326Z [LEDDEVICE1_ADALIGHT] (LedDevice.cpp:448) LED refresh interval adjustment caused by smoothing configuration change to 40ms (proposed: 40ms)
2024-05-13T22:57:32.326Z [EFFECTENGINE1] Run effect "Rainbow waves" on channel 0
2024-05-13T22:57:32.326Z [EFFECTENGINE1] (EffectEngine.cpp:92) Start the effect: name [Rainbow waves]
2024-05-13T22:57:32.326Z [MUXER1] Register new input 'System/EFFECT' with priority 0 as inactive
2024-05-13T22:57:32.327Z [HYPERHDR1] Boot effect: animation set to 'Rainbow waves' [started]
2024-05-13T22:57:32.327Z [EFFECT1(Rainbo...)] Begin playing the effect with priority: 0
2024-05-13T22:57:32.327Z [MUXER1] Priority 0 is now active
2024-05-13T22:57:32.327Z [MUXER1] Set visible priority to 0
2024-05-13T22:57:32.327Z [HYPERHDR1] New priority[0], previous [254]
2024-05-13T22:57:32.332Z [V4L2:USB3.0 UHD: US] (V4L2Grabber.cpp:424) Device has 'hue' control => min: 0, max: 100, default: 50
2024-05-13T22:57:32.333Z [V4L2:USB3.0 UHD: US] USB3.0 UHD: USB3.0 UHD (video0) [/dev/video0] 1920 x 1080 @ 60 fps yuyv input 0
2024-05-13T22:57:32.333Z [V4L2:USB3.0 UHD: US] USB3.0 UHD: USB3.0 UHD (video0) [/dev/video0] 1920 x 1080 @ 50 fps yuyv input 0
2024-05-13T22:57:32.333Z [V4L2:USB3.0 UHD: US] USB3.0 UHD: USB3.0 UHD (video0) [/dev/video0] 1920 x 1080 @ 30 fps yuyv input 0
2024-05-13T22:57:32.333Z [V4L2:USB3.0 UHD: US] USB3.0 UHD: USB3.0 UHD (video0) [/dev/video0] 1920 x 1080 @ 20 fps yuyv input 0
2024-05-13T22:57:32.333Z [V4L2:USB3.0 UHD: US] USB3.0 UHD: USB3.0 UHD (video0) [/dev/video0] 1920 x 1080 @ 10 fps yuyv input 0
2024-05-13T22:57:32.333Z [V4L2:USB3.0 UHD: US] USB3.0 UHD: USB3.0 UHD (video0) [/dev/video0] 1600 x 1200 @ 60 fps yuyv input 0
2024-05-13T22:57:32.333Z [V4L2:USB3.0 UHD: US] USB3.0 UHD: USB3.0 UHD (video0) [/dev/video0] 1600 x 1200 @ 50 fps yuyv input 0
2024-05-13T22:57:32.333Z [V4L2:USB3.0 UHD: US] USB3.0 UHD: USB3.0 UHD (video0) [/dev/video0] 1600 x 1200 @ 30 fps yuyv input 0
2024-05-13T22:57:32.333Z [V4L2:USB3.0 UHD: US] USB3.0 UHD: USB3.0 UHD (video0) [/dev/video0] 1600 x 1200 @ 20 fps yuyv input 0
2024-05-13T22:57:32.333Z [V4L2:USB3.0 UHD: US] USB3.0 UHD: USB3.0 UHD (video0) [/dev/video0] 1600 x 1200 @ 10 fps yuyv input 0
2024-05-13T22:57:32.333Z [V4L2:USB3.0 UHD: US] USB3.0 UHD: USB3.0 UHD (video0) [/dev/video0] 1360 x 768 @ 60 fps yuyv input 0
2024-05-13T22:57:32.333Z [V4L2:USB3.0 UHD: US] USB3.0 UHD: USB3.0 UHD (video0) [/dev/video0] 1360 x 768 @ 50 fps yuyv input 0
2024-05-13T22:57:32.333Z [V4L2:USB3.0 UHD: US] USB3.0 UHD: USB3.0 UHD (video0) [/dev/video0] 1360 x 768 @ 30 fps yuyv input 0
2024-05-13T22:57:32.333Z [V4L2:USB3.0 UHD: US] USB3.0 UHD: USB3.0 UHD (video0) [/dev/video0] 1360 x 768 @ 20 fps yuyv input 0
2024-05-13T22:57:32.333Z [V4L2:USB3.0 UHD: US] USB3.0 UHD: USB3.0 UHD (video0) [/dev/video0] 1360 x 768 @ 10 fps yuyv input 0
2024-05-13T22:57:32.333Z [V4L2:USB3.0 UHD: US] USB3.0 UHD: USB3.0 UHD (video0) [/dev/video0] 1280 x 1024 @ 60 fps yuyv input 0
2024-05-13T22:57:32.333Z [V4L2:USB3.0 UHD: US] USB3.0 UHD: USB3.0 UHD (video0) [/dev/video0] 1280 x 1024 @ 50 fps yuyv input 0
2024-05-13T22:57:32.333Z [V4L2:USB3.0 UHD: US] USB3.0 UHD: USB3.0 UHD (video0) [/dev/video0] 1280 x 1024 @ 30 fps yuyv input 0
2024-05-13T22:57:32.333Z [V4L2:USB3.0 UHD: US] USB3.0 UHD: USB3.0 UHD (video0) [/dev/video0] 1280 x 1024 @ 20 fps yuyv input 0
2024-05-13T22:57:32.333Z [V4L2:USB3.0 UHD: US] USB3.0 UHD: USB3.0 UHD (video0) [/dev/video0] 1280 x 1024 @ 10 fps yuyv input 0
2024-05-13T22:57:32.333Z [V4L2:USB3.0 UHD: US] USB3.0 UHD: USB3.0 UHD (video0) [/dev/video0] 1280 x 960 @ 60 fps yuyv input 0
2024-05-13T22:57:32.333Z [V4L2:USB3.0 UHD: US] USB3.0 UHD: USB3.0 UHD (video0) [/dev/video0] 1280 x 960 @ 50 fps yuyv input 0
2024-05-13T22:57:32.333Z [V4L2:USB3.0 UHD: US] USB3.0 UHD: USB3.0 UHD (video0) [/dev/video0] 1280 x 960 @ 30 fps yuyv input 0
2024-05-13T22:57:32.333Z [V4L2:USB3.0 UHD: US] USB3.0 UHD: USB3.0 UHD (video0) [/dev/video0] 1280 x 960 @ 20 fps yuyv input 0
2024-05-13T22:57:32.333Z [V4L2:USB3.0 UHD: US] USB3.0 UHD: USB3.0 UHD (video0) [/dev/video0] 1280 x 960 @ 10 fps yuyv input 0
2024-05-13T22:57:32.333Z [V4L2:USB3.0 UHD: US] USB3.0 UHD: USB3.0 UHD (video0) [/dev/video0] 1280 x 720 @ 60 fps yuyv input 0
2024-05-13T22:57:32.333Z [V4L2:USB3.0 UHD: US] USB3.0 UHD: USB3.0 UHD (video0) [/dev/video0] 1280 x 720 @ 50 fps yuyv input 0
2024-05-13T22:57:32.333Z [V4L2:USB3.0 UHD: US] USB3.0 UHD: USB3.0 UHD (video0) [/dev/video0] 1280 x 720 @ 30 fps yuyv input 0
2024-05-13T22:57:32.333Z [V4L2:USB3.0 UHD: US] USB3.0 UHD: USB3.0 UHD (video0) [/dev/video0] 1280 x 720 @ 20 fps yuyv input 0
2024-05-13T22:57:32.333Z [V4L2:USB3.0 UHD: US] USB3.0 UHD: USB3.0 UHD (video0) [/dev/video0] 1280 x 720 @ 10 fps yuyv input 0
2024-05-13T22:57:32.333Z [V4L2:USB3.0 UHD: US] USB3.0 UHD: USB3.0 UHD (video0) [/dev/video0] 1024 x 768 @ 60 fps yuyv input 0
2024-05-13T22:57:32.333Z [V4L2:USB3.0 UHD: US] USB3.0 UHD: USB3.0 UHD (video0) [/dev/video0] 1024 x 768 @ 50 fps yuyv input 0
2024-05-13T22:57:32.333Z [V4L2:USB3.0 UHD: US] USB3.0 UHD: USB3.0 UHD (video0) [/dev/video0] 1024 x 768 @ 30 fps yuyv input 0
2024-05-13T22:57:32.333Z [V4L2:USB3.0 UHD: US] USB3.0 UHD: USB3.0 UHD (video0) [/dev/video0] 1024 x 768 @ 20 fps yuyv input 0
2024-05-13T22:57:32.333Z [V4L2:USB3.0 UHD: US] USB3.0 UHD: USB3.0 UHD (video0) [/dev/video0] 1024 x 768 @ 10 fps yuyv input 0
2024-05-13T22:57:32.333Z [V4L2:USB3.0 UHD: US] USB3.0 UHD: USB3.0 UHD (video0) [/dev/video0] 800 x 600 @ 60 fps yuyv input 0
2024-05-13T22:57:32.333Z [V4L2:USB3.0 UHD: US] USB3.0 UHD: USB3.0 UHD (video0) [/dev/video0] 800 x 600 @ 50 fps yuyv input 0
2024-05-13T22:57:32.334Z [V4L2:USB3.0 UHD: US] USB3.0 UHD: USB3.0 UHD (video0) [/dev/video0] 800 x 600 @ 30 fps yuyv input 0
2024-05-13T22:57:32.334Z [V4L2:USB3.0 UHD: US] USB3.0 UHD: USB3.0 UHD (video0) [/dev/video0] 800 x 600 @ 20 fps yuyv input 0
2024-05-13T22:57:32.334Z [V4L2:USB3.0 UHD: US] USB3.0 UHD: USB3.0 UHD (video0) [/dev/video0] 800 x 600 @ 10 fps yuyv input 0
2024-05-13T22:57:32.334Z [V4L2:USB3.0 UHD: US] USB3.0 UHD: USB3.0 UHD (video0) [/dev/video0] 720 x 576 @ 60 fps yuyv input 0
2024-05-13T22:57:32.334Z [V4L2:USB3.0 UHD: US] USB3.0 UHD: USB3.0 UHD (video0) [/dev/video0] 720 x 576 @ 50 fps yuyv input 0
2024-05-13T22:57:32.334Z [V4L2:USB3.0 UHD: US] USB3.0 UHD: USB3.0 UHD (video0) [/dev/video0] 720 x 576 @ 30 fps yuyv input 0
2024-05-13T22:57:32.334Z [V4L2:USB3.0 UHD: US] USB3.0 UHD: USB3.0 UHD (video0) [/dev/video0] 720 x 576 @ 20 fps yuyv input 0
2024-05-13T22:57:32.334Z [V4L2:USB3.0 UHD: US] USB3.0 UHD: USB3.0 UHD (video0) [/dev/video0] 720 x 576 @ 10 fps yuyv input 0
2024-05-13T22:57:32.334Z [V4L2:USB3.0 UHD: US] USB3.0 UHD: USB3.0 UHD (video0) [/dev/video0] 720 x 480 @ 60 fps yuyv input 0
2024-05-13T22:57:32.334Z [V4L2:USB3.0 UHD: US] USB3.0 UHD: USB3.0 UHD (video0) [/dev/video0] 720 x 480 @ 50 fps yuyv input 0
2024-05-13T22:57:32.334Z [V4L2:USB3.0 UHD: US] USB3.0 UHD: USB3.0 UHD (video0) [/dev/video0] 720 x 480 @ 30 fps yuyv input 0
2024-05-13T22:57:32.334Z [V4L2:USB3.0 UHD: US] USB3.0 UHD: USB3.0 UHD (video0) [/dev/video0] 720 x 480 @ 20 fps yuyv input 0
2024-05-13T22:57:32.334Z [V4L2:USB3.0 UHD: US] USB3.0 UHD: USB3.0 UHD (video0) [/dev/video0] 720 x 480 @ 10 fps yuyv input 0
2024-05-13T22:57:32.334Z [V4L2:USB3.0 UHD: US] USB3.0 UHD: USB3.0 UHD (video0) [/dev/video0] 640 x 480 @ 60 fps yuyv input 0
2024-05-13T22:57:32.334Z [V4L2:USB3.0 UHD: US] USB3.0 UHD: USB3.0 UHD (video0) [/dev/video0] 640 x 480 @ 50 fps yuyv input 0
2024-05-13T22:57:32.334Z [V4L2:USB3.0 UHD: US] USB3.0 UHD: USB3.0 UHD (video0) [/dev/video0] 640 x 480 @ 30 fps yuyv input 0
2024-05-13T22:57:32.334Z [V4L2:USB3.0 UHD: US] USB3.0 UHD: USB3.0 UHD (video0) [/dev/video0] 640 x 480 @ 20 fps yuyv input 0
2024-05-13T22:57:32.334Z [V4L2:USB3.0 UHD: US] USB3.0 UHD: USB3.0 UHD (video0) [/dev/video0] 640 x 480 @ 10 fps yuyv input 0
2024-05-13T22:57:32.334Z [V4L2:USB3.0 UHD: US] Restarting video grabber is now blocked due to reloading of the configuration
2024-05-13T22:57:32.334Z [V4L2:USB3.0 UHD: US] Cropping image: width=0 height=0; crop: left=0 right=0 top=0 bottom=0
2024-05-13T22:57:32.334Z [V4L2:USB3.0 UHD: US] (GrabberWrapper.cpp:126) CEC keycode. Start: 0, stop: 0
2024-05-13T22:57:32.334Z [V4L2:USB3.0 UHD: US] (Grabber.cpp:159) Set new width: 1280, height: 720 for capture
2024-05-13T22:57:32.334Z [V4L2:USB3.0 UHD: US] (Grabber.cpp:335) setWidthHeight preparing to restarting video grabber 0
2024-05-13T22:57:32.334Z [V4L2:USB3.0 UHD: US] Delayed restart of the grabber due to change of the capturing resolution
2024-05-13T22:57:32.334Z [V4L2:USB3.0 UHD: US] Delayed restart of the grabber due to change of the framerate
2024-05-13T22:57:32.334Z [V4L2:USB3.0 UHD: US] (Grabber.cpp:273) setBrightnessContrastSaturationHue nothing changed
2024-05-13T22:57:32.334Z [V4L2:USB3.0 UHD: US] (V4L2Grabber.cpp:125) setHdrToneMappingMode to: Disabled
2024-05-13T22:57:32.334Z [V4L2:USB3.0 UHD: US] (Grabber.cpp:182) setFpsSoftwareDecimation to: 1
2024-05-13T22:57:32.334Z [SIGNAL_OLD] (DetectionManual.cpp:84) Signal detection area set to: 0.250000,0.250000 x 0.750000,0.750000
2024-05-13T22:57:32.334Z [SIGNAL_OLD] (DetectionManual.cpp:74) Signal threshold set to: {0, 0, 0} and frames: 50
2024-05-13T22:57:32.334Z [SIGNAL_AUTO] (DetectionAutomatic.cpp:375) Automatic signal detection -> errorTolerance: 9, modelTolerance: 90, sleepTime: 1000, wakeTime: 0
2024-05-13T22:57:32.334Z [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-13T22:57:32.334Z [V4L2:USB3.0 UHD: US] Delayed restart of the grabber due to change of selected device
2024-05-13T22:57:32.334Z [V4L2:USB3.0 UHD: US] (Grabber.cpp:200) Force encoding to: yuyv (old: NO_CHANGE)
2024-05-13T22:57:32.334Z [V4L2:USB3.0 UHD: US] Delayed restart of the grabber due to change of the video encoding format
2024-05-13T22:57:32.334Z [V4L2:USB3.0 UHD: US] setQFrameDecimation is now: enabled
2024-05-13T22:57:32.336Z [V4L2:USB3.0 UHD: US] Multithreading for V4L2 is enabled. Available thread's count 3
2024-05-13T22:57:32.337Z [V4L2:USB3.0 UHD: US] Found capture device: /dev/video15
2024-05-13T22:57:32.337Z [V4L2:USB3.0 UHD: US] Found capture device: /dev/video21
2024-05-13T22:57:32.338Z [V4L2:USB3.0 UHD: US] Found capture device: /dev/video14
2024-05-13T22:57:32.338Z [V4L2:USB3.0 UHD: US] Found capture device: /dev/video22
2024-05-13T22:57:32.338Z [V4L2:USB3.0 UHD: US] Found capture device: /dev/video0
2024-05-13T22:57:32.338Z [V4L2:USB3.0 UHD: US] (V4L2Grabber.cpp:406) Device has 'brightness' control => min: 0, max: 100, default: 50
2024-05-13T22:57:32.338Z [V4L2:USB3.0 UHD: US] (V4L2Grabber.cpp:412) Device has 'contrast' control => min: 0, max: 100, default: 50
2024-05-13T22:57:32.338Z [V4L2:USB3.0 UHD: US] (V4L2Grabber.cpp:418) Device has 'saturation' control => min: 0, max: 100, default: 50
2024-05-13T22:57:32.338Z [V4L2:USB3.0 UHD: US] (V4L2Grabber.cpp:424) Device has 'hue' control => min: 0, max: 100, default: 50
2024-05-13T22:57:32.339Z [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-13T22:57:32.339Z [V4L2:USB3.0 UHD: US] *************************************************************************************************
2024-05-13T22:57:32.339Z [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-13T22:57:32.339Z [V4L2:USB3.0 UHD: US] *************************************************************************************************
2024-05-13T22:57:32.339Z [V4L2:USB3.0 UHD: US] (V4L2Grabber.cpp:826) Hardware cropping is not supported: ignoring
2024-05-13T22:57:32.339Z [V4L2:USB3.0 UHD: US] Set device input to: Camera 1
2024-05-13T22:57:32.355Z [V4L2:USB3.0 UHD: US] Set resolution to: 1280 x 720
2024-05-13T22:57:32.366Z [CEC] CEC library warning: CLinuxCECAdapterCommunication::Open - physical address is invalid
2024-05-13T22:57:32.372Z [V4L2:USB3.0 UHD: US] Set framerate to 60 FPS
2024-05-13T22:57:32.375Z [V4L2:USB3.0 UHD: US] Brightness set to: 50 (default)
2024-05-13T22:57:32.378Z [V4L2:USB3.0 UHD: US] Contrast set to: 50 (default)
2024-05-13T22:57:32.381Z [V4L2:USB3.0 UHD: US] Saturation set to: 50 (default)
2024-05-13T22:57:32.385Z [V4L2:USB3.0 UHD: US] Hue set to: 50 (default)
2024-05-13T22:57:32.385Z [V4L2:USB3.0 UHD: US] (V4L2Grabber.cpp:105) LUT folder location: '/usr/share/hyperhdr/lut'
2024-05-13T22:57:32.385Z [SMOOTHING0] Using linear smoothing procedure (2)
2024-05-13T22:57:32.385Z [V4L2:USB3.0 UHD: US] (Grabber.cpp:458) LUT file found: /home/pi/.hyperhdr/lut_lin_tables.3d
2024-05-13T22:57:32.385Z [V4L2:USB3.0 UHD: US] (Grabber.cpp:473) Index 2 for YUV
2024-05-13T22:57:32.406Z [SMOOTHING1] Using linear smoothing procedure (2)
2024-05-13T22:57:32.941Z [CEC] CEC library signaling error: CLinuxCECAdapterCommunication::Write - ioctl CEC_TRANSMIT failed - tx_status=00 errno=64
2024-05-13T22:57:32.941Z [CEC] CEC library signaling error: CLinuxCECAdapterCommunication::Write - ioctl CEC_TRANSMIT failed - tx_status=00 errno=64
2024-05-13T22:57:33.227Z [CEC] CEC library signaling error: CLinuxCECAdapterCommunication::Write - ioctl CEC_TRANSMIT failed - tx_status=00 errno=64
2024-05-13T22:57:33.227Z [CEC] CEC library signaling error: CLinuxCECAdapterCommunication::Write - ioctl CEC_TRANSMIT failed - tx_status=00 errno=64
2024-05-13T22:57:33.488Z [V4L2:USB3.0 UHD: US] Found and loaded LUT: '/home/pi/.hyperhdr/lut_lin_tables.3d'
2024-05-13T22:57:33.488Z [V4L2:USB3.0 UHD: US] Video pixel format is set to: YUYV
2024-05-13T22:57:33.496Z [V4L2:USB3.0 UHD: US] Started
2024-05-13T22:57:33.534Z [V4L2:USB3.0 UHD: US] (V4L2Grabber.cpp:1164) Worker's thread count  = 3
2024-05-13T22:57:33.536Z [MUXER1] Priority 240 is now active
2024-05-13T22:57:33.536Z [MUXER0] Priority 240 is now active
2024-05-13T22:57:33.800Z [WEBSERVER] Initialize Webserver
2024-05-13T22:57:33.800Z [FLATBUFSERVER] Started on port 19400
2024-05-13T22:57:33.801Z [FLATBUFSERVER] Started local domain socket server: 'hyperhdr-domain'
2024-05-13T22:57:33.802Z [NETFORWARDER] Forwarder has changed state to disabled
2024-05-13T22:57:33.896Z [WEBSERVER] Apply Webserver settings
2024-05-13T22:57:33.896Z [WEBSERVER] Set document root to: :/www
2024-05-13T22:57:33.897Z [WEBSERVER] Started: 'HyperHDR WebServer (HTTP)' on port: 8090
2024-05-13T22:57:33.897Z [SSDP] (SSDPHandler.cpp:93) The local address is empty
2024-05-13T22:57:33.897Z [WEBSERVER] Initialize Webserver
2024-05-13T22:57:33.897Z [WEBSERVER] Apply Webserver settings
2024-05-13T22:57:33.897Z [WEBSERVER] Set document root to: :/www
2024-05-13T22:57:33.922Z [WEBSERVER] Setup SSL certificate
2024-05-13T22:57:33.923Z [WEBSERVER] Setup private SSL key
2024-05-13T22:57:33.923Z [WEBSERVER] Started: 'HyperHDR WebServer (HTTPS)' on port: 8092
2024-05-13T22:57:33.923Z [SSDP] (SSDPHandler.cpp:42) SSDPHandler is initializing
2024-05-13T22:57:33.924Z [SSDP] Could not obtain the local address. Retry later (1/10)
2024-05-13T22:57:33.924Z [SSDP] (SSDPServer.cpp:95) Initialize the SSDP server
2024-05-13T22:57:33.924Z [SSDP] (SSDPHandler.cpp:93) The local address is empty
2024-05-13T22:57:35.442Z [NET_DISCOVERY] Found Pico/RP2040 at ttyACM0:-1 (Pico)
2024-05-13T22:57:35.400Z [SERVICE_mDNS] Starting the network discovery thread
2024-05-17T20:21:25.955Z [EFFECT0(Rainbo...)] The effect quits with priority: 0
2024-05-17T20:21:25.955Z [MUXER0] Removed source priority 0
2024-05-17T20:21:25.955Z [MUXER0] Set visible priority to 240
2024-05-17T20:21:25.955Z [SMOOTHING0] Clearing queued colors before: enabling. Smoothing configuration changed: restarting timer.
2024-05-17T20:21:25.955Z [SMOOTHING0] Smoothing queue is cleared
2024-05-17T20:21:25.955Z [SMOOTHING0] Selecting config (0) => type: Alternative, directMode: false, pause: false, settlingTime: 150ms, interval: 11ms (90Hz), antiFlickTres: 0, antiFlickStep: 0, antiFlickTime: 0
2024-05-17T20:21:25.955Z [SMOOTHING0] Using alternative smoothing input (0)
2024-05-17T20:21:25.955Z [LEDDEVICE0_SK9822] (LedDevice.cpp:381) Stopping refresh timer
2024-05-17T20:21:25.955Z [HYPERHDR0] New priority[240], previous [0]
2024-05-17T20:21:25.955Z [LEDDEVICE0_SK9822] Ignoring user LED refresh rate. Forcing smoothing refresh rate = 90.91 Hz
2024-05-17T20:21:25.955Z [LEDDEVICE0_SK9822] (LedDevice.cpp:423) Refresh rate = 90.91 Hz
2024-05-17T20:21:25.955Z [COLORSPACE_CALIBRATION0] (ColorSpaceCalibration.cpp:225) setBackLightEnabled: 1
2024-05-17T20:21:25.955Z [LEDDEVICE0_SK9822] (LedDevice.cpp:367) Starting timer with interval = 11ms
2024-05-17T20:21:25.955Z [EFFECTENGINE0] Effect 'Rainbow swirl' has finished.
2024-05-17T20:21:25.955Z [LEDDEVICE0_SK9822] (LedDevice.cpp:433) Refresh interval updated to 11ms
2024-05-17T20:21:25.955Z [LEDDEVICE0_SK9822] (LedDevice.cpp:448) LED refresh interval adjustment caused by smoothing configuration change to 11ms (proposed: 11ms)
2024-05-17T20:21:25.955Z [EFFECT0(Rainbo...)] Effect named: 'Rainbow swirl' is deleted
2024-05-17T20:21:25.960Z [IMAGETOLED_MNG0] Total index number is: 60160 (memory: 60160). User sparse processing is: disabled, image size: 640 x 360, area number: 260
2024-05-17T20:21:25.963Z [EFFECT1(Rainbo...)] The effect quits with priority: 0
2024-05-17T20:21:25.963Z [MUXER1] Removed source priority 0
2024-05-17T20:21:25.963Z [MUXER1] Set visible priority to 240
2024-05-17T20:21:25.963Z [SMOOTHING1] Clearing queued colors before: enabling. Smoothing configuration changed: restarting timer.
2024-05-17T20:21:25.963Z [SMOOTHING1] Smoothing queue is cleared
2024-05-17T20:21:25.963Z [SMOOTHING1] Selecting config (0) => type: Alternative, directMode: false, pause: false, settlingTime: 150ms, interval: 16ms (62Hz), antiFlickTres: 0, antiFlickStep: 0, antiFlickTime: 0
2024-05-17T20:21:25.963Z [SMOOTHING1] Using alternative smoothing input (0)
2024-05-17T20:21:25.963Z [HYPERHDR1] New priority[240], previous [0]
2024-05-17T20:21:25.963Z [LEDDEVICE1_ADALIGHT] (LedDevice.cpp:381) Stopping refresh timer
2024-05-17T20:21:25.963Z [COLORSPACE_CALIBRATION1] (ColorSpaceCalibration.cpp:225) setBackLightEnabled: 1
2024-05-17T20:21:25.963Z [EFFECTENGINE1] Effect 'Rainbow waves' has finished.
2024-05-17T20:21:25.963Z [LEDDEVICE1_ADALIGHT] Ignoring user LED refresh rate. Forcing smoothing refresh rate = 62.50 Hz
2024-05-17T20:21:25.963Z [EFFECT1(Rainbo...)] Effect named: 'Rainbow waves' is deleted
2024-05-17T20:21:25.963Z [LEDDEVICE1_ADALIGHT] (LedDevice.cpp:423) Refresh rate = 62.50 Hz
2024-05-17T20:21:25.963Z [LEDDEVICE1_ADALIGHT] (LedDevice.cpp:367) Starting timer with interval = 16ms
2024-05-17T20:21:25.963Z [LEDDEVICE1_ADALIGHT] (LedDevice.cpp:433) Refresh interval updated to 16ms
2024-05-17T20:21:25.963Z [LEDDEVICE1_ADALIGHT] (LedDevice.cpp:448) LED refresh interval adjustment caused by smoothing configuration change to 16ms (proposed: 16ms)
2024-05-17T20:21:25.976Z [IMAGETOLED_MNG1] Total index number is: 18560 (memory: 18560). User sparse processing is: disabled, image size: 640 x 360, area number: 103
2024-05-17T20:21:25.978Z [SMOOTHING0] Using alternative smoothing procedure (0)
2024-05-17T20:21:25.996Z [SMOOTHING1] Using alternative smoothing procedure (0)
2024-05-17T20:21:28.003Z [SSDP] (SSDPHandler.cpp:42) SSDPHandler is initializing
2024-05-17T20:21:28.004Z [SSDP] (SSDPHandler.cpp:183) The local address is: <IP_ADDRESS>
2024-05-17T20:21:28.004Z [SSDP] (SSDPServer.cpp:95) Initialize the SSDP server
2024-05-17T20:21:28.004Z [WEBSERVER] (StaticFileServing.cpp:68) SSDP description is set up
2024-05-17T20:21:28.004Z [SSDP] Starting the SSDP server
2024-05-17T20:22:03.763Z [IMAGETOLED_MNG0] Total index number is: 49792 (memory: 49792). User sparse processing is: disabled, image size: 640 x 360, area number: 260
2024-05-17T20:22:55.287Z [V4L2:USB3.0 UHD: US] Video cache: size: 1, hits: 7089, needed: 1, cleanup: 0, limit: 8
2024-05-17T20:22:55.292Z [PERFORMANCE] [USB: FPS = 60.03, decoding = 2ms, frames = 3601, invalid = 0, mode = direct], [INSTANCE0: FPS = 60.03, processed = 3601], [LED0: FPS = 90.91, send = 5454, processed = 5454, dropped = 0], [INSTANCE1: FPS = 60.02, processed = 3601], [LED1: FPS = 62.50, send = 3750, processed = 3750, dropped = 0]
2024-05-17T20:23:55.297Z [PERFORMANCE] [USB: FPS = 60.03, decoding = 2ms, frames = 3602, invalid = 0, mode = direct], [INSTANCE0: FPS = 60.03, processed = 3602], [LED0: FPS = 90.91, send = 5455, processed = 5455, dropped = 0], [INSTANCE1: FPS = 60.03, processed = 3602], [LED1: FPS = 62.50, send = 3750, processed = 3750, dropped = 0]
2024-05-17T20:24:55.301Z [PERFORMANCE] [USB: FPS = 60.03, decoding = 2ms, frames = 3602, invalid = 0, mode = direct], [INSTANCE0: FPS = 60.03, processed = 3601], [LED0: FPS = 90.91, send = 5454, processed = 5454, dropped = 0], [INSTANCE1: FPS = 60.03, processed = 3601], [LED1: FPS = 62.50, send = 3750, processed = 3750, dropped = 0]
2024-05-17T20:25:36.820Z [IMAGETOLED_MNG0] Total index number is: 60160 (memory: 60160). User sparse processing is: disabled, image size: 640 x 360, area number: 260
2024-05-17T20:25:45.000Z [IMAGETOLED_MNG1] Total index number is: 18560 (memory: 18560). User sparse processing is: disabled, image size: 640 x 360, area number: 103
2024-05-17T20:25:45.000Z [IMAGETOLED_MNG0] Total index number is: 60160 (memory: 60160). User sparse processing is: disabled, image size: 640 x 360, area number: 260
2024-05-17T20:25:55.297Z [PERFORMANCE] [USB: FPS = 60.03, decoding = 2ms, frames = 3601, invalid = 0, mode = direct], [INSTANCE0: FPS = 60.02, processed = 3602], [LED0: FPS = 90.91, send = 5455, processed = 5455, dropped = 0], [INSTANCE1: FPS = 60.02, processed = 3602], [LED1: FPS = 62.50, send = 3750, processed = 3750, dropped = 0]
2024-05-17T20:26:55.297Z [PERFORMANCE] [USB: FPS = 60.03, decoding = 3ms, frames = 3602, invalid = 0, mode = direct], [INSTANCE0: FPS = 60.03, processed = 3602], [LED0: FPS = 90.91, send = 5455, processed = 5455, dropped = 0], [INSTANCE1: FPS = 60.03, processed = 3602], [LED1: FPS = 62.50, send = 3750, processed = 3750, dropped = 0]
2024-05-17T20:27:55.301Z [PERFORMANCE] [USB: FPS = 60.03, decoding = 3ms, frames = 3602, invalid = 0, mode = direct], [INSTANCE0: FPS = 60.03, processed = 3601], [LED0: FPS = 90.91, send = 5454, processed = 5454, dropped = 0], [INSTANCE1: FPS = 60.03, processed = 3601], [LED1: FPS = 62.50, send = 3750, processed = 3750, dropped = 0]
2024-05-17T20:28:55.295Z [PERFORMANCE] [USB: FPS = 60.03, decoding = 3ms, frames = 3601, invalid = 0, mode = direct], [INSTANCE0: FPS = 60.03, processed = 3602], [LED0: FPS = 90.91, send = 5455, processed = 5455, dropped = 0], [INSTANCE1: FPS = 60.03, processed = 3602], [LED1: FPS = 62.50, send = 3750, processed = 3750, dropped = 0]
2024-05-17T20:29:55.301Z [PERFORMANCE] [USB: FPS = 60.03, decoding = 3ms, frames = 3602, invalid = 0, mode = direct], [INSTANCE0: FPS = 60.03, processed = 3602], [LED0: FPS = 90.91, send = 5454, processed = 5454, dropped = 0], [INSTANCE1: FPS = 60.03, processed = 3602], [LED1: FPS = 62.50, send = 3750, processed = 3750, dropped = 0]
2024-05-17T20:30:55.293Z [PERFORMANCE] [USB: FPS = 60.03, decoding = 3ms, frames = 3601, invalid = 0, mode = direct], [INSTANCE0: FPS = 60.03, processed = 3601], [LED0: FPS = 90.91, send = 5455, processed = 5455, dropped = 0], [INSTANCE1: FPS = 60.03, processed = 3601], [LED1: FPS = 62.50, send = 3750, processed = 3750, dropped = 0]
2024-05-17T20:31:55.299Z [PERFORMANCE] [USB: FPS = 60.02, decoding = 3ms, frames = 3602, invalid = 0, mode = direct], [INSTANCE0: FPS = 60.02, processed = 3601], [LED0: FPS = 90.91, send = 5454, processed = 5454, dropped = 0], [INSTANCE1: FPS = 60.02, processed = 3601], [LED1: FPS = 62.50, send = 3750, processed = 3750, dropped = 0]
2024-05-17T20:32:55.294Z [PERFORMANCE] [USB: FPS = 60.03, decoding = 3ms, frames = 3601, invalid = 0, mode = direct], [INSTANCE0: FPS = 60.03, processed = 3602], [LED0: FPS = 90.91, send = 5455, processed = 5455, dropped = 0], [INSTANCE1: FPS = 60.03, processed = 3602], [LED1: FPS = 62.50, send = 3750, processed = 3750, dropped = 0]
2024-05-17T20:33:35.656Z [WEBSOCKET] (WebSocketClient.cpp:39) New connection from ::ffff:<IP_ADDRESS>
2024-05-17T20:33:46.059Z [WEBSOCKET] (HyperAPI.cpp:957) log streaming activated for client ::ffff:<IP_ADDRESS>
2024-05-17T20:33:55.296Z [V4L2:USB3.0 UHD: US] Video cache: size: 2, hits: 3601, needed: 1, cleanup: 0, limit: 8
2024-05-17T20:33:55.301Z [PERFORMANCE] [USB: FPS = 60.03, decoding = 3ms, frames = 3602, invalid = 0, mode = direct], [INSTANCE0: FPS = 60.03, processed = 3602], [LED0: FPS = 90.91, send = 5454, processed = 5454, dropped = 0], [INSTANCE1: FPS = 60.03, processed = 3602], [LED1: FPS = 62.50, send = 3750, processed = 3750, dropped = 0]
2024-05-17T20:34:14.338Z [WEBSOCKET] (HyperAPI.cpp:966) log streaming deactivated for client  ::ffff:<IP_ADDRESS>
2024-05-17T20:34:17.100Z [WEBSOCKET] (HyperAPI.cpp:1109) message: [{"command":"leddevice","ledDeviceType":"sk9822","subcommand":"discover","tan":500}]
2024-05-17T20:34:17.102Z [LEDDEVICE_SK9822] (ProviderSpi.cpp:319) SPI devices discovered: [{"devices":[{"name":"/dev/spidev0.0","value":"/dev/spidev0.0"},{"name":"/dev/spidev0.1","value":"/dev/spidev0.1"}],"ledDeviceType":"sk9822"}]
2024-05-17T20:34:17.102Z [WEBSOCKET] (HyperAPI.cpp:1133) response: [{"devices":[{"name":"/dev/spidev0.0","value":"/dev/spidev0.0"},{"name":"/dev/spidev0.1","value":"/dev/spidev0.1"}],"ledDeviceType":"sk9822"}]
2024-05-17T20:34:27.735Z [IMAGETOLED_MNG0] Total index number is: 27264 (memory: 27264). User sparse processing is: disabled, image size: 640 x 360, area number: 260
2024-05-17T20:34:27.873Z [WEBSOCKET] (HyperAPI.cpp:1109) message: [{"command":"leddevice","ledDeviceType":"","params":{},"subcommand":"hasLedClock","tan":1}]
2024-05-17T20:34:28.584Z [IMAGETOLED_MNG1] Total index number is: 3822 (memory: 3822). User sparse processing is: disabled, image size: 640 x 360, area number: 103
2024-05-17T20:34:29.951Z [IMAGETOLED_MNG1] Total index number is: 18560 (memory: 18560). User sparse processing is: disabled, image size: 640 x 360, area number: 103
2024-05-17T20:34:29.951Z [IMAGETOLED_MNG0] Total index number is: 60160 (memory: 60160). User sparse processing is: disabled, image size: 640 x 360, area number: 260
2024-05-17T20:34:50.935Z [WEBSOCKET] (HyperAPI.cpp:1109) message: [{"command":"leddevice","ledDeviceType":"sk9822","subcommand":"discover","tan":407}]
2024-05-17T20:34:50.938Z [LEDDEVICE_SK9822] (ProviderSpi.cpp:319) SPI devices discovered: [{"devices":[{"name":"/dev/spidev0.0","value":"/dev/spidev0.0"},{"name":"/dev/spidev0.1","value":"/dev/spidev0.1"}],"ledDeviceType":"sk9822"}]
2024-05-17T20:34:50.938Z [WEBSOCKET] (HyperAPI.cpp:1133) response: [{"devices":[{"name":"/dev/spidev0.0","value":"/dev/spidev0.0"},{"name":"/dev/spidev0.1","value":"/dev/spidev0.1"}],"ledDeviceType":"sk9822"}]
2024-05-17T20:34:55.292Z [PERFORMANCE] [USB: FPS = 60.03, decoding = 3ms, frames = 3601, invalid = 0, mode = direct], [INSTANCE0: FPS = 60.03, processed = 3601], [LED0: FPS = 90.91, send = 5455, processed = 5455, dropped = 0], [INSTANCE1: FPS = 60.03, processed = 3601], [LED1: FPS = 62.50, send = 3750, processed = 3750, dropped = 0]
2024-05-17T20:34:56.450Z [V4L2:USB3.0 UHD: US] (V4L2Grabber.cpp:125) setHdrToneMappingMode to: Fullscreen
2024-05-17T20:34:56.450Z [V4L2:USB3.0 UHD: US] (V4L2Grabber.cpp:131) setHdrToneMappingMode replacing LUT and restarting
2024-05-17T20:34:56.450Z [V4L2:USB3.0 UHD: US] (V4L2Grabber.cpp:105) LUT folder location: '/usr/share/hyperhdr/lut'
2024-05-17T20:34:56.450Z [V4L2:USB3.0 UHD: US] (Grabber.cpp:458) LUT file found: /home/pi/.hyperhdr/lut_lin_tables.3d
2024-05-17T20:34:56.450Z [V4L2:USB3.0 UHD: US] (Grabber.cpp:468) Index 1 for HDR YUV
2024-05-17T20:34:57.552Z [V4L2:USB3.0 UHD: US] Found and loaded LUT: '/home/pi/.hyperhdr/lut_lin_tables.3d'
2024-05-17T20:34:57.552Z [COMPONENTCTRL0] HDR (global): enabled
2024-05-17T20:34:57.552Z [COMPONENTCTRL1] HDR (global): enabled
2024-05-17T20:35:00.667Z [WEBSOCKET] (HyperAPI.cpp:1109) message: [{"command":"leddevice","ledDeviceType":"sk9822","subcommand":"discover","tan":640}]
2024-05-17T20:35:00.670Z [LEDDEVICE_SK9822] (ProviderSpi.cpp:319) SPI devices discovered: [{"devices":[{"name":"/dev/spidev0.0","value":"/dev/spidev0.0"},{"name":"/dev/spidev0.1","value":"/dev/spidev0.1"}],"ledDeviceType":"sk9822"}]
2024-05-17T20:35:00.671Z [WEBSOCKET] (HyperAPI.cpp:1133) response: [{"devices":[{"name":"/dev/spidev0.0","value":"/dev/spidev0.0"},{"name":"/dev/spidev0.1","value":"/dev/spidev0.1"}],"ledDeviceType":"sk9822"}]
2024-05-17T20:35:04.549Z [WEBSOCKET] (HyperAPI.cpp:1109) message: [{"command":"leddevice","ledDeviceType":"","params":{},"subcommand":"hasLedClock","tan":1}]
2024-05-17T20:35:11.919Z [IMAGETOLED_MNG0] (ImageToLedManager.cpp:176) setSparseProcessing to 0
2024-05-17T20:35:11.920Z [COLORSPACE_CALIBRATION0] classicMode: yes, gammas:[1.50, 1.50, 1.50], saturation: 1.00, luminance: 1.00, backLight: [enabled, threshold: 0, colored: no]
2024-05-17T20:35:11.920Z [LED_CALIBRATION0] (LedCalibration.cpp:101) Calibration config '0' for LED segment: [0, 259]
2024-05-17T20:35:11.920Z [LED_CALIBRATION0] (LedCalibration.cpp:96) LedCalibration is released
2024-05-17T20:35:15.958Z [IMAGETOLED_MNG0] (ImageToLedManager.cpp:176) setSparseProcessing to 0
2024-05-17T20:35:15.958Z [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-17T20:35:15.958Z [LED_CALIBRATION0] (LedCalibration.cpp:101) Calibration config '0' for LED segment: [0, 259]
2024-05-17T20:35:15.958Z [LED_CALIBRATION0] (LedCalibration.cpp:96) LedCalibration is released
2024-05-17T20:35:22.251Z [COLORSPACE_CALIBRATION0] (ColorSpaceCalibration.cpp:241) setBrightness: 100
2024-05-17T20:35:22.252Z [COLORSPACE_CALIBRATION0] (ColorSpaceCalibration.cpp:252) setBrightnessCompensation: 60
2024-05-17T20:35:22.253Z [CHANNEL_CYAN0] (ChannelCalibration.cpp:70) setAdjustment: [0, 255, 255, active]
2024-05-17T20:35:22.254Z [CHANNEL_MAGENTA0] (ChannelCalibration.cpp:70) setAdjustment: [255, 0, 255, active]
2024-05-17T20:35:22.256Z [CHANNEL_BLUE0] (ChannelCalibration.cpp:80) setCorrection: 255
2024-05-17T20:35:22.258Z [CHANNEL_GREEN0] (ChannelCalibration.cpp:80) setCorrection: 255
2024-05-17T20:35:22.259Z [CHANNEL_RED0] (ChannelCalibration.cpp:80) setCorrection: 255
2024-05-17T20:35:22.261Z [CHANNEL_WHITE0] (ChannelCalibration.cpp:70) setAdjustment: [255, 255, 255, active]
2024-05-17T20:35:22.262Z [CHANNEL_YELLOW0] (ChannelCalibration.cpp:70) setAdjustment: [255, 255, 0, active]
2024-05-17T20:35:23.515Z [COLORSPACE_CALIBRATION0] (ColorSpaceCalibration.cpp:241) setBrightness: 100
2024-05-17T20:35:23.516Z [COLORSPACE_CALIBRATION0] (ColorSpaceCalibration.cpp:252) setBrightnessCompensation: 60
2024-05-17T20:35:23.517Z [CHANNEL_CYAN0] (ChannelCalibration.cpp:70) setAdjustment: [0, 255, 255, active]
2024-05-17T20:35:23.518Z [CHANNEL_MAGENTA0] (ChannelCalibration.cpp:70) setAdjustment: [255, 0, 255, active]
2024-05-17T20:35:23.520Z [CHANNEL_BLUE0] (ChannelCalibration.cpp:80) setCorrection: 255
2024-05-17T20:35:23.521Z [CHANNEL_GREEN0] (ChannelCalibration.cpp:80) setCorrection: 255
2024-05-17T20:35:23.522Z [CHANNEL_RED0] (ChannelCalibration.cpp:80) setCorrection: 255
2024-05-17T20:35:23.523Z [CHANNEL_WHITE0] (ChannelCalibration.cpp:70) setAdjustment: [255, 255, 255, active]
2024-05-17T20:35:23.524Z [CHANNEL_YELLOW0] (ChannelCalibration.cpp:70) setAdjustment: [255, 255, 0, active]
2024-05-17T20:35:35.456Z [WEBSOCKET] (HyperAPI.cpp:957) log streaming activated for client ::ffff:<IP_ADDRESS>
HyperHDR-<IP_ADDRESS>-Backup-2024-05-17.json
Steps to reproduce
Have 'Classic hyperHDR color calibration' unticked
Change brightness compensation to something like %60
Restart
Turn hdr on
Observe brightness compensation be unchanged
tick Classic hyperHDR color calibration and then un-tick it
observer brightness compensation be applied.
What is expected?
Brightness compensation should be always applied across restart?
What is actually happening?
I have noticed that the brigtness compensation effect isnt applying properly across reboots. I have a sk9822 which is showing red on max brightness and use backlight compensation to reduce brightness output on white colours. However since updating to v20 from one of the v20 beta versions the brightness compensation value doesnt apply across reboot. It requires me to tick classic colour calibration and then re-tick it for it to apply depsite the ui saying its already unticked.
This seems to be a bug in UI? Is this happenening for all others?
System

HyperHDR Server:

Build:           (HEAD detached at v<IP_ADDRESS>) (awawa-dev-9e960c9/52f12b4-1711236142)
Build time:      Mar 23 2024 23:52:04
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 11 (bullseye)
Architecture:   arm64
CPU Type:       Raspberry Pi 4 Model B Rev 1.4
CPU Hardware:   b03114
Kernel:         linux (5.15.61-v8+ (WS: 64))
Qt Version:     5.15.2
Browser:        Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:125.0) Gecko/20100101 Firefox/125.0

Hi
In which tab you apply the  the brightness compensation? There are 2 places: the processing and the remote control tab.

If it's the processing tab try to change any component a bit by ex. one. Any of them: white, red, blue. Just one, not all.

And test if it helps across reboot.

Thanks just tested this by changing the white value by one in the image processing tab and looks to have done the trick based on the quick check. I will check further tomorrow, but looks to be working correctly.
Thanks for that.

Ok, it's probably a bug and I will fix it, so no need to change color will be needed.


[docker] better defaults on many-core machines

Right now the defaults in our Docker image are not to fork collector plugins and collect 2 accounts simultaneously. This is great for testing Cloudkeeper on a personal Laptop but not for a many-core server. The image should detect the environment it is running in and the amount of resources available to it and automatically scale to higher settings by default.

Hi, I would like to help on this. Can you point me in what file these two operations (fork collector plugins and collect 2 accounts) are being done?

The best place is likely here:
https://github.com/someengineering/cloudkeeper/blob/main/docker/bootstrap#L143-L153
https://github.com/someengineering/cloudkeeper/blob/main/docker/defaults#L57
https://github.com/someengineering/cloudkeeper/blob/main/docker/common
Relevant ckworker variable names and their defaults are:
CKWORKER_FORK=false
CKWORKER_AWS_FORK=false
CKWORKER_GCP_FORK=false
CKWORKER_AWS_ACCOUNT_POOL_SIZE=5
CKWORKER_GCP_PROJECT_POOL_SIZE=5

In bootstrap export those variables, in common implement the number of CPU cores detection and in defaults set the ckworker variables to some sane values.
E.g.
num_cores=$(get_num_cores)
if [ $num_cores -gt 4 ]; then
    CKWORKER_FORK=${CKWORKER_FORK:-true}
    ...
    ...
else
    CKWORKER_FORK=${CKWORKER_FORK:-false}
    ...
    ...
fi

something along those lines. The pool size determines how many processes will be forked / how many accounts/projects will be collected in parallel.


Adding 'datetime' field type to field cause "invalid form" exception

I have profile with
nga.field('lastModifiedTs')

On edit view all works and profile easily could be edited. But after I change it to
nga.field('lastModifiedTs', 'datetime')

On edit view save I'm getting "invalid form" even I didn't change anything. Just opened from list view and pressed "Save Changes". If I choose date from date picker for that field no error and all works.

Works for me on master, can't reproduce the bug. Please retest with master. If you can provide a failing test in a JSFiddle, feel free to reopen.

Reproduced with master.

@fzaninotto I was able to localize a bit. It happens if field is int with timestamp. For instance<PHONE_NUMBER>836 did you check it? datetime field doesn't accept any date if it has seconds, hours or minutes. I can't reopen.

OK, now I can reproduce the bug. Reopening.

This is probably due to a bug in Angular ui's datepicker directive. We're using a not up-to-date version, but upgrading it means a lot of work and testing.
In the meantime, I suggest you add an element transformer to turn your timestamp into a string (e.g. "2015-12-08T23:00:00.000Z").

Ok. Thank you. I'll try that way.

No update on this for a while, I close it for now.
Feel free to reopen if you are still facing the issue.


Fix issue with dtors not being called + add more tests

Fix the issue with value's destructors not being called sometimes
Add more tests to catch similar issues in the future

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Comparison is base (7d001e9) 100.00% compared to head (371e9eb) 100.00%.

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
Additional details and impacted files
@@            Coverage Diff            @@
##              main       #11   +/-   ##
=========================================
  Coverage   100.00%   100.00%
=========================================
  Files            6         6
  Lines         1250      1336   +86
=========================================
+ Hits          1250      1336   +86

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


License confusin, the files says ICS but the file inside says public domain?

It would be nice if the library present a unified license picture?

The code is a port of some code that was placed in the public domain. Public domain isn't a real legal thing in most jurisdictions though.
I don't care. What do you want me to do?

I think it would if one of two things would happen:

remove the comments talking about license from the file so that the main LICENSE file speaks for the code base. https://gist.github.com/treeform/f202f8ed80cd7c2c96da089ee0af5196
make the comments says its under the ISC License rather then public domain + attribution.

Both are pretty simple.

👍 fixed


Update virtual-wan-p2s-gateway-include.md

updated RADIUS server info

Docs Build status updates of commit 1be3780:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

includes/virtual-wan-p2s-gateway-include.md
:white_check_mark:Succeeded

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel

#sign-off

@cherylmc,
Can you review the proposed changes?
IMPORTANT: When the changes are ready for publication, add a #sign-off comment to signal that the PR is ready for the review team to merge.
#label:"aq-pr-triaged"
@MicrosoftDocs/public-repo-pr-review-team

@cherylmc - Can you review this old PR and determine whether it needs to be closed or merged?
IMPORTANT: When the changes are ready for publication, add a #sign-off comment to signal that the PR is ready for the review team to merge.

Updating in a different PR. #please-close

#please-close


🧗 perf tuning cli

Describe your changes
Perf tuning cli.
E.g. for phi2-int4-cpu got from model builder, user can directly tuning the latency in cpu and cuda ep with:
olive perftuning --model model.onnx --device gpu --providers_list CUDA CPU --hf_model_name microsoft/phi-2
Checklist before requesting a review

[ ] Add unit tests for this change.
[ ] Make sure all tests can pass.
[ ] Update documents if necessary.
[ ] Lint and apply fixes to your code by running lintrunner -a
[ ] Is this a user-facing change? If yes, give a description of this change to be included in the release notes.
[ ] Is this PR including examples changes? If yes, please remember to update example documentation in a follow-up PR.

(Optional) Issue link

Can you add a documentation here?

Can you add a documentation here?

The cli document will be auto-generated by sphinx doc framework.


Fixed broken link for cryptographic policies

Great repository @konstruktoid! I noticed a small typo in the link for cryptographic policies within the readme. It seems the correct link should be this. This PR fixes it.

Thanks @markdumay! And thank you for this PR.

Thanks @markdumay! And thank you for this PR.


Use HTTP security headers

Add flask-talisman to the project to set up HTTP headers to improve security.  Add a content security policy which limits resources to those served by the Throat instance and its media servers. Block inline JavaScript in the CSP and fix the few places in the code which used it.
This CSP allows inline styles, which are a possible avenue of attack, but since there are about 100 places in the code that use inline styles, I made the CSP allow them for now and will open a separate issue for fixing them.

The most recent commits relax the CSP to allow images and media from any https site, and put the list of sites that can be embedded by Expando.js into the child-src policy.


Partial cleanup for adding golint

Fix golint errors in api/jsonapi.go.

Coverage increased (+0.004%) to 34.821% when pulling 94d11614d729dca8faa9785ed4dcc6b194de9685 on ianbibby:1204-golint-fixes-for-jsonapi into af969524d5e19e064a565d2850809f1367f4b9d8 on OpenBazaar:master.

Hey @ianbibby. Thanks for the submission... this a good progress. I think you'll realize there are some fields which will fail this lint rule. I would suggest staying away from the protobuf and other struct fields as some of those are exported out of the node. Function names and variables etc should not be a problem. I would welcome more of these small PRs toward getting golint's rule added to CI.

Closing in favor of #1250


[Bug]: Scroll sidebar in horizontal style

Preflight Checklist

[X] I have read the Contributing Guidelines for this project.
[X] I agree to follow the Code of Conduct that this project adheres to.
[X] I have searched the issue tracker for a feature request that matches the one I want to file, without success.

Ferdi Version
5.6.9
What operating system are you using?
Windows
Server
Ferdi
Operating System Version
Windows 11
What arch are you using?
x64
Last Known working version of Ferdi
No response
Git SHA and/or build date
No response
Steps to reproduce
I added a lot of services to Ferdi. If i don't use fullscreen mode and use my prefered horizontal style for the sidebar, i can't scroll to the services outside the visible area.

Enable horizontal style for sidebar
Try to scroll to a service outside the visible area

Expected Behavior
In vertical style i can use my scroll wheel to scroll the sidebar.
In horizontal style this is not working.
I also would expect arrow icons to click on to scroll.
Actual Behavior
There is no chance to go to a service outside the visible area of the sidebar in horizontal style.
Screenshots
No response
Debug information
No response
Testcase Gist URL
No response
Additional Information
No response

Let's address this in https://github.com/getferdi/ferdi/issues/2379.


WIP: Features/net6 apple sillicon support

What does the pull request do?

What is the current behavior?

What is the updated/expected behavior with this PR?

How was the solution implemented (if it's not obvious)?

Checklist

[ ] Added unit tests (if possible)?
[ ] Added XML documentation to any related classes?
[ ] Consider submitting a PR to https://github.com/AvaloniaUI/Avaloniaui.net with user documentation

Breaking changes

Obsoletions / Deprecations

Fixed issues

Hi, this should help you https://github.com/AvaloniaUI/Avalonia/pull/5415


Switch from Travis to GitHub actions

And from coveralls to codecov.

Codecov Report

:exclamation: No coverage uploaded for pull request base (main@1adfd0a). Click here to learn what that means.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main      #36   +/-   ##
=======================================
  Coverage        ?   89.01%
  Complexity      ?      109
=======================================
  Files           ?        9
  Lines           ?      273
  Branches        ?       60
=======================================
  Hits            ?      243
  Misses          ?       23
  Partials        ?        7

Continue to review full report at Codecov.

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


Fix issues with InlineFormset.save_as_new in Django 1.11

Django 1.11 now marks multipart POST data as immutable (Release notes section). This causes an issue with the private save_as_new feature in InlineFormsets: the set code in the conditional block worked on in this PR now throws an AttributeError because the data it's attempting to change is marked as immutable.
To restore previous behavior, this pull request turns off the immutability flag on the form data while the save_as_new functionality runs and turns immutability back on when the mutation code is complete.
Note that the mutable flag isn't set if there is no data, hence the hasattr code.
TRAC: https://code.djangoproject.com/ticket/28159

I'd like to add some tests for this. Any advice on where they should go?

grepping the tests directory for save_as_new shows model_formsets or model_formsets_regress as probable locations for a test.  (Ideally, we'll likely merge model_formsets_regress into model_formsets eventually, so it probably doesn't matter which one you choose.)


iOS 15 : Navigation Bar Background Color

UINavigationController

[ ] Default background color is black instead of blue

[ ] Popup background color is transparent instead of blue

[ ] When swiping popup content down the background blue color appears again

https://developer.apple.com/forums/thread/682420
https://developer.apple.com/forums/thread/683024


Color scheme doesn't show in insert mode.

VS Code Version: 1.41.1
MacOS 10.14.6
When in insert mode the text syntax color scheme is not applied until I escape to visual mode.
In insert mode:

After escaping to visual mode:

do you have any init.vim / vim plugins? try with empty init.vim. It looks like something like set cursorline kicks in

If I use a blank init.vim it works correctly. My init.vim is not complicated though. 🤷♂
let $NVIM_TUI_ENABLE_TRUE_COLOR=1
" dein.vim setup -- start
if &compatible
  set nocompatible
endif
" Add the dein installation directory into runtimepath
set runtimepath+=~/.cache/dein/repos/github.com/Shougo/dein.vim

if dein#load_state('~/.cache/dein')
  call dein#begin('~/.cache/dein')

  call dein#add('~/.cache/dein/repos/github.com/Shougo/dein.vim')
  call dein#add('Shougo/deoplete.nvim')
  call dein#add('morhetz/gruvbox')
  call dein#add('easymotion/vim-easymotion')
  call dein#add('airblade/vim-gitgutter')
  call dein#add('vim-airline/vim-airline')
  call dein#end()
  call dein#save_state()

  if dein#check_install()
    call dein#install()
  endif
endif

filetype plugin indent on
syntax enable
" dein.vim setup --end

colorscheme gruvbox
let mapleader=","
set cursorline

try to disable sequentially set cursorline/colorscheme gruvbox/vim-gitgutter plugin .
you can use if exists('g:vscode') to conditionally set settings/load plugins for both neovim/vscode (deoplete/airline/gitgutter/vim themes don't make sense with vscode)

That works. Thank you!!

vim themes don't make sense with vscode

@asvetliakov Will there be any way to use vim themes in vscode or won't be possible?

I am also having this problem.

The problem just started today, but I haven't made any recent changes to NeoVim configuration. I did make one change to the VS Code configuration yesterday. It shouldn't be related, but I tried removing that, too.
In settings.json
"editor.parameterHints.enabled": false,

My configuration was even simpler. I tried using a blank init.vim file but it didn't solve the problem for me.
init.vim
set runtimepath^=~/.vim runtimepath+=~/.vim/after
let &packpath = &runtimepath
source ~/.vimrc
set mouse=a

~/.vimrc
set guifont=FiraCode\ Nerd\ Font\ Medium\ 12
set shiftwidth=4
set tabstop=4
set expandtab
set number

My only package/plugin/extension is GitHub Copilot, in ~/.config/nvim/pack

Are you sure that's not just vscode's semantic highlighting greying out unused code? Since you return in the line after, array is never referenced.

@theol0403 removing GitHub Copilot solves the problem. I'd like to be able to use GitHub Copilot when I'm using NeoVim, of course, but I use VSCode more for writing code right now. It's an acceptable workaround for a problem that I hope will be fixed in the future.

@theol0403 removing GitHub Copilot solves the problem. I'd like to be able to use GitHub Copilot when I'm using NeoVim, of course, but I use VSCode more for writing code right now. It's an acceptable workaround for a problem that I hope will be fixed in the future.

Use the vscode copilot extension when using vscode-neovim and the nvim copilot plugin when using nvim. You can conditionally enable plugins.

Potentially related on Stack Overflow: Changing "editor.foreground" color in VS Code does not seem to be working in all cases


Adds an output to docs files

Proposed changes
This experimental PR adds an output section to the docs files. It would depend on an "output" annotation, which would use the template already defined in each file (listTemplate, describeTemplate, etc) that reflects the output in the CLI itself.
I tested this locally and I am including screenshots of create, delete, list, and describe commands after a local test with these changes. I also included a screenshot of what the annotation looks like.
Additionally, this PR removes the work from my last PR that added a line for requiredRole because we implemented that as part of the long descriptions instead (just to prevent use of this annotation by mistake)

Jira ticket:
N/A
Checklist

[] I have signed the MongoDB CLA
[] I have added tests that prove my fix is effective or that my feature works
[] I have added any necessary documentation (if appropriate)
[] I have run make fmt and formatted my code

@gssbzn, could you take a look at this PR when you have time and let me know if the Go code looks ok?
@melissamahoney-mongodb, let me know what you think about making this change to add an output to the docs/whether you have any copy suggestions. It won't take long to add the required annotations, I added them for all create commands while testing.
Thank you both!!

@gssbzn @melissamahoney-mongodb Ready for another look! I made both of your suggested changes and I fixed the formatting on the responses with columns. Updated screenshots of the results are in the PR description. Thanks!


Malformed config file

The config file created by euporie lack a } at the end. Then euporie will give warnings when it starts.

I can't reproduce this. I tried deleting my configuration file, running euporie-notebook, then changing a setting. The configuration file created at is valid JSON, and no warning is shown.
Euporie doesn't create a config file unless you change a setting through the menus or the command palette. Was there a particular configuration change you made through the UI which caused this issue?
You might just need to manually fix your config file if it is broken.

You are right.
For some reason cat doesn't show the last }.
But opening the file in a text editor shows it.
It's a bug in cat???? 😲

I suspect that's because there is no new-line at the end of the config file, and your shell overwrites the last time of output in your terminal to display your prompt.

I have to report it to fish shell? To starship prompt?
I don't understand.
Is it normal that it throws out relevant information because "I have to display the prompt"?


Added support for target wasm32-wasi

This allows the tar to work in a browser, wasmer and WASI platforms.

Thanks for the PR here, but I would prefer to not add support here by sprinkling a lot of #[cfg] throughout the code. I think it's fine for wasm32-wasi to behave a bit differently for example by having different defaults for unpacking and similar. For example not preserving mtime and avoiding xattrs seem like reasonable defaults for wasi, but otherwise I don't think it's necessary to #[cfg] away the code. Can you speak more to why canonicalize is necessary to specialize?
Would it be possible to add tests for this as well?

canonicalize is not implemented in the standard library for wasi so it panics [cry]
https://github.com/rust-lang/rust/blob/master/library/std/src/sys/wasi/fs.rs#L609
Yeah I don't like the #[cfg] macros either - I can try and remove some but its not easy to be honest - alternative is to fork tar-rs until WASI gets more support - or maybe you have another idea - still not cracked this problem myself.
Testing WASI is not very easy at the moment as its quite hard to get unit tests to run without panicing - the good thing is that the basics of the toolchain are there already and its more the lack of support in the standard library thats holding it back, basically you can test by running:
cargo wasi test

But it fails with this:
Caused by:
    0: failed to invoke command default
    1: wasm trap: unreachable
       wasm backtrace:
           0: 0x178c2d - <unknown>!__rust_start_panic
           1: 0x13e951 - <unknown>!rust_panic
           2: 0xcadf1 - <unknown>!std::panicking::rust_panic_with_hook::h308937c11f14a0b0
           3: 0x17647b - <unknown>!std::panicking::begin_panic::{{closure}}::hebc9643fe2b695d7
           4: 0x1753f7 - <unknown>!std::sys_common::backtrace::__rust_end_short_backtrace::he2536be214bafdb9
           5: 0x17644e - <unknown>!std::panicking::begin_panic::hd2671e09b3b4e5c3
           6: 0x178762 - <unknown>!std::sys::wasi::os::temp_dir::hbc626cdbc609eb38
           7: 0x178b02 - <unknown>!std::env::temp_dir::h25ed3bd578de46c3
           8: 0x166ba2 - <unknown>!tempfile::Builder::tempdir::h702dce260a633d0d
           9: 0x60aa5 - <unknown>!all::append_dir_all_blank_dest::h888625bbe2adcd99
          10: 0x17180e - <unknown>!all::append_dir_all_blank_dest::{{closure}}::h2f896a4f4c3d3da9
          11: 0x1735cd - <unknown>!core::ops::function::FnOnce::call_once::h9d99a1526320ffc5
          12: 0x176de4 - <unknown>!test::__rust_begin_short_backtrace::h44c13f5e334be418
          13: 0x178a5d - <unknown>!core::ops::function::FnOnce::call_once{{vtable.shim}}::h99a922c74aed367b
          14: 0x92f6b - <unknown>!test::run_test::run_test_inner::h60a67529b5c5db98
          15: 0x88c1a - <unknown>!test::run_test::h2251c1b970756ec5
          16: 0x2c99e - <unknown>!test::console::run_tests_console::h3dae2ea08348f81f
          17: 0x8e102 - <unknown>!test::test_main::h29ec7696c5542e21
          18: 0x12da49 - <unknown>!test::test_main_static::hcf5afa2aa7e5d486
          19: 0x177f7f - <unknown>!all::main::hd66e46cbdbfb7162
          20: 0x17121a - <unknown>!core::ops::function::FnOnce::call_once::hf6aa8f732d7f16b7
          21: 0x17054f - <unknown>!std::sys_common::backtrace::__rust_begin_short_backtrace::habdcb39f4c03c5cb
          22: 0x16ca05 - <unknown>!std::rt::lang_start::{{closure}}::h61f52bbcf039bda5
          23: 0x12e68d - <unknown>!std::rt::lang_start_internal::hcfff2f9346b7fb75
          24: 0x15c6b3 - <unknown>!std::rt::lang_start::hf92037ed41a12602
          25: 0x177ef0 - <unknown>!__original_main
          26: 0x178407 - <unknown>!_start
          27: 0x178ae9 - <unknown>!_start.command_export
       note: using the `WASMTIME_BACKTRACE_DETAILS=1` environment variable to may show more debugging information

error: failed to execute "wasmtime" "--" "/prog/tar-rs/target/wasm32-wasi/debug/deps/all-c4ccc64a95c19939.wasm"
    status: exit code: 13

Reason is the tempfs is not implemented in the std library either - this I've worked around in other projects and hopefully the rust std library developers will patch this soon and the unit tests will come back online.
For now the best we can do without manual testing or rewriting the unit tests (which will be for nothing when they fix up the last bits of the std library) is to run a basic compile test
cargo wasi build

If you'd prefer to fork that's ok by me, but if you'd like to contribute to this upstream I'd like items in review to be taken care of (such as cutting down on #[cfg]). There's various ways to do that, such as having one helper method that's defined differnetly for wasi/else, instead of having a #[cfg]-per-use.
For tests I think it's ok to not have the whole test suite working, but presumably you care about something working and if you want that to keep working over time I'd recommend adding tests to CI.

Don't get me wrong - I think its always better to work and contribute on the upstream and my comment was only a request if you really didn't like WASI due to its "new-ness" then I understand.
Let me take a look at the #[cfg]'s and see what I can do to reduce them.
For the test suite the only way I can get it to work is if I disable a chunk of them for WASI and try to get one or two of them working but I don't know a way to do that without the #[cfg] macros.
Totally open to suggestions
Cheers

So I did another commit and addressed the concerns you raised.
Basically I reduced the number of #[cfg] lines dropped in and made it more cleaner by splitting out the canonicalize function and mocking another implementation of it for WASI.
Second I worked through the list of unit tests and got 28 of the total working with the WASI test so while it does not give good coverage on the file system level (given WASI isn't there yet anyway) but the rest of the tar functionality has some decent coverage. To integrate with your CI/CD you need to run the "cargo wasi test" command... you should get this:
cargo wasi test -- --nocapture
   Compiling tar v0.4.37 (/prog/tar-rs)
    Finished test [unoptimized + debuginfo] target(s) in 0.70s
     Running unittests (target/wasm32-wasi/debug/deps/tar-6fd696d6c645a524.wasm)
     Running tests/all.rs (target/wasm32-wasi/debug/deps/all-d49bb81736cacecb.wasm)
     Running tests/entry.rs (target/wasm32-wasi/debug/deps/entry-1fc4c15213d03354.wasm)
     Running `/prog/tar-rs/target/wasm32-wasi/debug/deps/tar-6fd696d6c645a524.wasm --nocapture`

running 0 tests

test result: ok. 0 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out

     Running `/prog/tar-rs/target/wasm32-wasi/debug/deps/all-d49bb81736cacecb.wasm --nocapture`

running 28 tests
test append_long_multibyte ... ok
test header::byte_slice_conversion ... ok
test header::default_gnu ... ok
test header::dev_major_minor ... ok
test header::extended_numeric_format ... ok
test header::goto_old ... ok
test header::goto_ustar ... ok
test header::mtime ... ok
test header::set_ustar_path_hard ... ok
test header::user_and_group_name ... ok
test header_impls ... ok
test header_impls_missing_last_header ... ok
test header_size_overflow ... ok
test links ... ok
test long_linkname_trailing_nul ... ok
test long_name_trailing_nul ... ok
test octal_spaces ... ok
test pax_linkpath ... ok
test pax_path ... ok
test pax_simple ... ok
test pax_size ... ok
test reading_entries ... ok
test reading_entries_with_seek ... ok
test reading_files ... ok
test reading_sparse ... ok
test simple_concat ... ok
test skipping_entries_with_seek ... ok
test sparse_with_trailing ... ok

test result: ok. 28 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out

     Running `/prog/tar-rs/target/wasm32-wasi/debug/deps/entry-1fc4c15213d03354.wasm --nocapture`

running 0 tests

test result: ok. 0 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out

Thanks! Can CI also be updated with compiling to wasi and running tests?

Sure - its a simple change for you to implement
Just use this for builds...
cargo wasi build

...and use this for tests....
cargo wasi test -- --nocapture

The tool-chain can be installed with this command...
cargo install cargo-wasi

There we go... added some lovely WASI unit tests in the CI/CD
When you merge this will you also publish? There are some downstream projects depending on this.

I'm out of investment tokens on this one now... not enough hours in the day unfortunately so will only be able to do minimal updates from here. I am sure others can help you though now that its well commented, tested and you have CI/CD.
Cheers

Ok no worries, if someone else wants to come pick this up then this can be reopened.

If you're willing to go through the rigamarole of publishing a whole new fork on crates.io I'd ask again if you're willing to address the final few comments on review. If you would prefer to publish a fork I have no preference on the name.

I told you I have a preference for merging upstream but I'm not going to iterate over and over on few really minor points that don't make any real difference, my hours in the day are extremely precious to me and I've put a ton of work into this already so it's not like I didn't try.
 I'm cool with that... so why don't you just accept the merge and change the lines to be exactly how you want them to meet your particular style of coding? I do it all the time - it's often easier.
Anyhow I'll go publish on cargo tomorrow and if you accept the merge later just let me know and I'll yank it out and kill it... its better to clean up the copied packages for the communities sake. Ultimately though there are downstream WASI projects that also need help that I need to work on urgently.

How about I give it one last try tomorrow; we both put effort into this and we should try our best to get it over the line - what are the last changes you would like me to make as prescriptively as possible.


json-ld representation of sentences

read/write json-ld from the internal sentence structure.

Another possibility is the http://jsonlines.org/

also move the json support from the read-write.lisp for another file and/or package.


Exporting comments

Suppose that I want to move to another commenting system, how do I export the existing comments?
Maybe this seems trivial because I own the database and I can query it, but I don't have any experience with sqlight. Instead, it should not be very difficult to create a script that exports all the comments in XML or JSON format.

Duplicate of #183.

No it is not.
I mean a dump of the database in XML or JSON or CSV format (if possible).

To export the comments (with thread information) into a file called export.csv in bash, use:
echo -e '"page: URI","page: title","ID","mode","created on","modified on","author: name","author: email","author: website","author: IP","likes","dislikes","voters","text"\n'"$(sqlite3 /path/to/your/isso.db -csv 'SELECT threads.uri, threads.title, comments.id, comments.mode, datetime(comments.created, "unixepoch", "localtime"), datetime(comments.modified, "unixepoch", "localtime"), comments.author, comments.email, comments.website, comments.remote_addr, comments.likes, comments.dislikes, comments.voters,comments.text FROM comments INNER JOIN threads ON comments.tid=threads.id')" > export.csv

Don’t forget to put the correct path to your database in!
If you want the UNIX timestamps instead of a datetime string, omit the datetime function:
echo -e '"page: URI","page: title","ID","mode","created on","modified on","author: name","author: email","author: website","author: IP","likes","dislikes","voters","text"\n'"$(sqlite3 /path/to/your/isso.db -csv 'SELECT threads.uri, threads.title, comments.id, comments.mode, comments.created, comments.modified, comments.author, comments.email, comments.website, comments.remote_addr, comments.likes, comments.dislikes, comments.voters,comments.text FROM comments INNER JOIN threads ON comments.tid=threads.id')" > export.csv

FWIW, I made this: https://github.com/angristan/isso-to-disqus. It exports the comments to the Disqus XML format, but can be easily adapted for something else.


modify mwaa plugin url and release label

Modified mwaa plugin version in README file
I modified the EMR release label version since the version EMR serverless support for SPARK is 'emr-6.6.0'
https://docs.aws.amazon.com/emr/latest/EMR-Serverless-UserGuide/release-versions.html

Derp, thank you for catching those! Appreciate the PR. 🙏


ssb-server: 13 > 14

Motivation for this change
the scuttlebot was deprecated at 13.0.0, it's new name is ssb-server, which currently is at 14.1.7.
Things done

[ ] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS)
Built on platform(s)

[x] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nox --run "nox-review wip"
[x] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Assured whether relevant documentation is up to date
[x] Fits CONTRIBUTING.md.

rebased to fix the merge conflicts.

Do you mind rebasing this again? @cryptix

@mmahut done

@GrahamcOfBorg build ssb-server

Looks like this has been included in fae732edb11876800db7b9f1eebbc7c553a9c99b?

Yep


'conversion from size_t to US, possible losss of data' warning at line 574 in cxxopts.hpp

A 'conversion from size_t to US, possible loss of data' compiler warning is raised at line 574 in cxxopts.hpp when compiling with Visual Studio 2017 and the /W4 warning level.

Which commit is this for?

I get this on v2.1.2

This is actually fixed in the latest revision, where "digit" now matches the template type. You can close this


initialize

[ ] Package manager

[ ] List all versions of candidate
[ ] Install a specific version
[ ] Remove specific version
[ ] Switch between version

[ ] Integrate with ChatGPT/Gemini so user can chat directly with these tools on cmd

[ ] Other common tools for dev

https://github.com/warpy-ai/rustubble/tree/main


Increase Credibility

[x] Add powered by SatoshiPay
[x] Add footer similar to LP

Closes https://github.com/pendulum-chain/tasks/issues/435

@pendulum-chain/devs Ready for revies ✅

I think we should reduce the bottom margin of the 'powered by' message in the form. Also, the app is a little scrollable for me. It would be better if it fits on the whole 100vh of space. I'm not sure if we need to have 'Powered by SatoshiPay' twice on the screen, although technically that's how it was specified in https://github.com/pendulum-chain/tasks/issues/435. @pendulum-chain/product is this intended?

@Sharqiewicz please don't forget to link to the relevant ticket in the description of your PRs. Even if it's a task ticket. I added that link now.

Maybe we should adjust the left margin on mobile a bit and make it align with the swap form.


Airbyte integration

Describe the solution you'd like
A custom soda-sql integration for Airbyte.
Additional context
Airbyte roadmap mentions Airflow support is coming within a few weeks / months. Soda-sql Airflow operator could then be used until an independent soda-sql integration is developed .
Soda SQL Version:
Soda CLI version 2.0.0b21

I don't think this will be important enough for us in the coming months.  If you think different, please reopen en elaborate.


how to do n controlled physic steps per every control step

I want to do e.g. 10 "controlled" steps per every policy action output, that is, I compute 10 motor targets for the next 10 physic steps for every action that the policy sends.
I put my opt_timestep=0.002 and n_frames=1.
based on the MJX example, I tried to do it by modifing the pipeline_step. The original:
  def pipeline_step(self, pipeline_state: Any, action: jax.Array) -> base.State:
    """Takes a physics step using the physics pipeline."""

    def f(state, _):
      return (
          self._pipeline.step(self.sys, state, action, self._debug),
          None,
      )

    return jax.lax.scan(f, pipeline_state, (), self._n_frames)[0]

and mine:
    def pipeline_step(self, pipeline_state: Any, motor_targets_times: jax.Array) -> base.State:
        """Takes a physics step using the physics pipeline."""

        def f(state, motor_targets):
            return (
              self._pipeline.step(self.sys, state, motor_targets, self._debug),
              None,
            )

        return jax.lax.scan(f, pipeline_state, motor_targets_times)[0]

The leading axis of motor_targets_times is 10.
This seems to work, however it is introducing a notable speed decrease about 1.5x~2x.
Don't know why this is happening. Is this expected or am I doing something wrong, and is there a better way to do this?

FWIU, the way to do "10 repeated actions" is to use action_repeat with the EpisodeWrapper.
Closing this to create a discussion thread


Systemcmds tests posix

Rebased on master and fixed missing header file for posix build.
Should the file getopt_long.c be deleted? It is not used anywhere.

Hm, let me have a look at the file. Thanks!


When I use it in React，get error “Uncaught TypeError: Cannot set properties of undefined (setting 'getPropertyValue')”

Hello，我是林昕，我已收到来信~

Yes, Vue also has this problem。

Hello，我是林昕，我已收到来信~

I seem to know why this is happening. When installing dependencies, some will install wow.js, while others will install wowjs. That's where my problem lies. It should be installing wow.js

Hello，我是林昕，我已收到来信~


Confusing Hyper-V Documentation

Hi Team,
The documentation around Hyper-V Migrations is a little confusing and there seems to be continued references to VMware.  For example, the section around agentless dependency analysis is only applicable to VMware (at this time).  Yet there includes details such as the following:

VMware tools
VMware Tools (later than 10.2) must be installed and running on each VM you want to analyze.

vCenter Server
Dependency visualization needs a vCenter Server account with read-only access, and privileges enabled for Virtual Machines > Guest Operations.ESXi hosts: On ESXi hosts running VMs you want to analyze, the Azure Migrate appliance must be able to connect to TCP port 443.

I think we should be removing any detail around agentless dependency analysis for Hyper-V at this time.  I appreciate it may be coming down the line, but this only serves to confuse at this point.

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

ID: 7a61ef28-eb20-d9a4-fa46-f21acfaa2f6d
Version Independent ID: b422adbb-c672-d283-ac69-2ed9639b10db
Content: Support for Hyper-V assessment in Azure Migrate - Azure Migrate
Content Source: articles/migrate/migrate-support-matrix-hyper-v.md
Service: azure-migrate
GitHub Login: @rayne-wiselman
Microsoft Alias: raynew

Thanks for your feedback! We already  have a work item open for this and the change will show up in the next day or two.

@chrisdoofer Thanks for the feedback! We will review and update accordingly.

Thanks for your feedback. This is now fixed.
#please-close


Fix error propagation

Errors do not propagate to front-end; most everything that's not caught results in a mysterious 500, internal server error.

:+1: In the few places where we display error messages to users - the frontend has to guess what caused the error.

It seems like errors do now propagate to users thanks to some of your PRs (and it's a much better experience for users) so I'm closing this.


[add] file store cache of ajax part

Coverage decreased (-0.009%) to 84.59% when pulling 069cd1418e36f5b36edeceee1d694448e417ef71 on pr-ajax-part-cache into abde4d1fc9b3bfe45d9a7c8ed4c94ab07908a857 on master.


The selected service is not available to residential destinations.

Getting this error: "The selected service is not available to residential destinations."
Destination is not residential and I have not included any "residential" indicators.
{
  "ShipmentRequest": {
    "Request": {
      "SubVersion": "2205",
      "RequestOption": "validate",
      "TransactionReference": {
        "CustomerContext": "order#"
      }
    },
    "Shipment": {
      "Description": "stuff",
      "Shipper": {
        "Name": "xxxxx",
        "AttentionName": "Shipping",
        "Phone": {
          "Number": "xxx",
        },
        "ShipperNumber": "xxxx",
        "Address": {
          "AddressLine": [
            "xxxxx"
          ],
          "City": "xxxx",
          "StateProvinceCode": "xx",
          "PostalCode": "xxxx",
          "CountryCode": "US"
        },
        "EmailAddress": "shipping@"
      },
      "ShipTo": {
        "Name": "xxxxx",
        "AttentionName": "xxxx",
        "Phone": {
          "Number": "xxx",
        },
        "Address": {
          "AddressLine": [
            "xxxx"
          ],
          "City": "NEWHALL",
          "StateProvinceCode": "CA",
          "PostalCode": "xxx",
          "CountryCode": "US"
        },
        "EmailAddress": "xxxx"
      },
      "PaymentInformation": {
        "ShipmentCharge": {
          "Type": "01",
          "BillShipper": {
            "AccountNumber": "xxxx"
          }
        }
      },
      "Service": {
        "Code": "12"
      },
      "Package": {
        "Packaging": {
          "Code": "02"
        },
        "Dimensions": {
          "UnitOfMeasurement": {
            "Code": "IN"
          },
          "Length": "30",
          "Width": "10",
          "Height": "20"
        },
        "PackageWeight": {
          "UnitOfMeasurement": {
            "Code": "LBS"
          },
          "Weight": "5"
        },
        "ReferenceNumber": {
          "Code": "O",
          "Value": "IN:555555;"
        }
      },
      "PackageID": "0",
      "PackageIDBarcodeIndicator": "X",
      "ShipmentServiceOptions": {
        "SaturdayDeliveryIndicator": "X"
      }
    }
  }
}

Hi, for US shipments, address classification is conducted. In this case, the system believes the given address is residential. If you believe the address is not residential, please reach out to the UPS Helpdesk: https://developer.ups.com/contactus


refactor(in-memory-db): initial change for migrating in-memory-db to …

…an nx repository
Far from ready now, build, test and e2e are working yet

@DominikPieper going to merge so we can iterate


how the input image is normalized? what is the mean and the std?

mean = [0.485, 0.456, 0.406]
std = [0.229, 0.224,m 0.225]

Please see the updated README, Thanks!


Fixed OpenH264 linking

Added the dll link library name to hints

+1

What this definitely changes is that now always the dynamic version is used if found which is a change in behavior. Not sure if this was intended.

Since openh264 can't be shipped anyway +1


YOLO NAS PREDICTION ERROR IMAGEDETECTIONOBJECT is not iterable

🐛 Describe the bug
result = list(best_model.predict(img_url, conf=0.35))[0]
[2024-01-27 13:09:10] INFO - pipelines.py - Fusing some of the model's layers. If this takes too much memory, you can deactivate it by setting fuse_model=False
TypeError                                 Traceback (most recent call last)
 in <cell line: 1>()
----> 1 result = list(best_model.predict(img_url, conf=0.35))[0]
TypeError: 'ImageDetectionPrediction' object is not iterable
for image_prediction in images_predictions:
class_names = image_prediction.class_names
labels = image_prediction.prediction.labels
confidence = image_prediction.prediction.confidence
bboxes = image_prediction.prediction.bboxes_xyxy
for i, (label, conf, bbox) in enumerate(zip(labels, confidence, bboxes)):
    print("prediction: ", i)
    print("label_id: ", label)
    print("label_name: ", class_names[int(label)])
    print("confidence: ", conf)
    print("bbox: ", bbox)
    print("--" * 10)

TypeError                                 Traceback (most recent call last)
 in <cell line: 1>()
----> 1 for image_prediction in images_predictions:
2     class_names = image_prediction.class_names
3     labels = image_prediction.prediction.labels
4     confidence = image_prediction.prediction.confidence
5     bboxes = image_prediction.prediction.bboxes_xyxy
TypeError: 'ImageDetectionPrediction' object is not iterable
Versions
wget https://raw.githubusercontent.com/pytorch/pytorch/main/torch/utils/collect_env.py
For security purposes, please check the contents of collect_env.py before running it.
python collect_env.py

I dont understand i am running notebook on colab, before colab was executing the prediction part code without error but now it is not , am using yolo nas but to access prediction result it is throwing error. Colab was giving output before but it is producing error now.

is this the issue of colab

Do you mind specifying what colab notebook are you attempting to run?

https://github.com/Deci-AI/super-gradients/issues/1801#issuecomment-1916521475 Proper way of using prediction for single image. Please update your notebook .


Bug: middle click not working properly

In views with movies and shows I can middle click with the mouse on the text of a show and (as expected) that item gets opened in a new tab. If I click on the description text the new tab isn't opened. Also, the item is now stuck in the "bigger mode", even when I stop hovering it.
https://github.com/user-attachments/assets/4fe02675-0cea-447a-a64e-e28b62feb51c

Hey @AlexPerathoner, good catch, I can look into fixing this shortly when I find some time.


Add --version option to each tool [feature request]

Thanks!

Most tools now support this, but I've used -S / --spec as the flag. How do we feel about this? -v / -V might be a natural choice for a --verbose flag that outputs what gfakluge is currently doing to stderr.

I would suggest --version and --help, which is the de facto standard. Short single-character options are not needed.

The --version <X> flag now works. Thanks for the suggestions, @sjackman !

This is now done ---version will show a version message any time it is passed. No immediate plans to support graphviz, but that's an excellent idea. Will close this for now.

abyss-todot (included with ABySS, and now a misnomer) can convert between GraphViz, GFA1, and GFA2. It can read the GraphViz, GFA1, and GFA2 output by ABySS, but not necessarily all valid GraphViz, GFA1, and GFA2 files.


Hard-Coded URI's

There are several hard-coded URI's in the frontend and the pipeline. These should be moved to configuration, but for now they are easy enough to change in my own fork. However, there is another source of hard-coded URI's that I can't locate. My production pipeline (installed as a GH app) is failing. It's giving this warning:
current.github [WARNING] Set d4hines/marigold-tezos
                           refs/heads/master
                           902910d2/ocaml-benchmarks to
                           {"state":"failure","description":"Command \"docker\" \"run\" \"--security-opt\" \"seccomp=./aslr_seccomp.json\" \n\"--tmpfs\" \"/dev/shm:rw,noexec,nosuid,size=4g\" \"--rm\" \"-i\" \"sha256:98a","target_url":"http://autumn.ocamllabs.io/d4hines/marigold-tezos"} failed: 403 Forbidden
                           {"message":"Resource not accessible by integration","documentation_url":"https://docs.github.com/rest/reference/repos#create-a-commit-status"}

I can't track down where it's getting the URL http://autumn.ocamllabs.io/d4hines/marigold-tezos from. Any ideas?

http://autumn.ocamllabs.io is the URL we display frontend on, are you running benchmarks for marigold-tezos? It should be coming from here: https://github.com/ocurrent/current-bench/blob/main/pipeline/lib/pipeline.ml#L62