Govee devices are unavailable after update to version 2024.01.09-ab0af6b7

You have 2024.01.07-92fb55e0 installed. Click update to update to version 2024.01.09-ab0af6b7
I rolled back to 2024.01.07-92fb55e0 and all is well.
s6-rc: info: service s6rc-oneshot-runner: starting
s6-rc: info: service s6rc-oneshot-runner successfully started
s6-rc: info: service fix-attrs: starting
s6-rc: info: service fix-attrs successfully started
s6-rc: info: service legacy-cont-init: starting
s6-rc: info: service legacy-cont-init successfully started
s6-rc: info: service legacy-services: starting
s6-rc: info: service legacy-services successfully started
GOVEE_API_KEY=REDACTED
GOVEE_MQTT_HOST=core-mosquitto
GOVEE_EMAIL=REDACTED
GOVEE_PASSWORD=REDACTED
GOVEE_MQTT_PASSWORD=REDACTED
GOVEE_MQTT_USER=addons
GOVEE_MQTT_PORT=1883
++ cd /app
++ exec /app/govee serve
[2024-01-09T16:02:41 INFO  govee::commands::serve] Starting service. version 2024.01.07-92fb55e0
[2024-01-09T16:02:41 INFO  govee::commands::serve] Querying platform API for device list
[2024-01-09T16:02:42 INFO  govee::commands::serve] Querying undocumented API for device + room list
[2024-01-09T16:02:43 INFO  govee::service::iot] Connected to IoT: CONNACK code 0: Connection Accepted.
[2024-01-09T16:02:43 INFO  govee::commands::serve] Starting LAN discovery
[2024-01-09T16:02:43 INFO  govee::service::iot] IoT (re)connected with status CONNACK code 0: Connection Accepted.
[2024-01-09T16:02:47 INFO  govee::commands::serve] Devices returned from Govee's APIs
[2024-01-09T16:02:47 INFO  govee::commands::serve] Smart Flood Lights 2 (D4:97:D7:39:32:33:38:7D) sku=H7062
[2024-01-09T16:02:47 INFO  govee::commands::serve]   LAN API: ip=<IP_ADDRESS>
[2024-01-09T16:02:47 INFO  govee::commands::serve]   Platform API: devices.types.light. supports_rgb=true supports_brightness=true
[2024-01-09T16:02:47 INFO  govee::commands::serve]                 color_temp=Some((2000, 9000)) segment_rgb=Some(0..2)
[2024-01-09T16:02:47 INFO  govee::commands::serve]   Undoc: room=Some("Outside") supports_iot=true ble_only=false
[2024-01-09T16:02:47 INFO  govee::commands::serve]   Quirk: Quirk { sku: "H7062", icon: "mdi:light-flood-down", supports_rgb: true, supports_brightness: true, color_temp_range: Some((2000, 9000)), avoid_platform_api: false, ble_only: false, lan_api_capable: true }
[2024-01-09T16:02:47 INFO  govee::commands::serve]
[2024-01-09T16:02:47 INFO  govee::commands::serve] Smart Flood Lights 1 (14:0F:D1:39:32:33:1D:23) sku=H7062
[2024-01-09T16:02:47 INFO  govee::commands::serve]   LAN API: ip=<IP_ADDRESS>
[2024-01-09T16:02:47 INFO  govee::commands::serve]   Platform API: devices.types.light. supports_rgb=true supports_brightness=true
[2024-01-09T16:02:47 INFO  govee::commands::serve]                 color_temp=Some((2000, 9000)) segment_rgb=Some(0..2)
[2024-01-09T16:02:47 INFO  govee::commands::serve]   Undoc: room=Some("Outside") supports_iot=true ble_only=false
[2024-01-09T16:02:47 INFO  govee::commands::serve]   Quirk: Quirk { sku: "H7062", icon: "mdi:light-flood-down", supports_rgb: true, supports_brightness: true, color_temp_range: Some((2000, 9000)), avoid_platform_api: false, ble_only: false, lan_api_capable: true }
[2024-01-09T16:02:47 INFO  govee::commands::serve]
[2024-01-09T16:02:47 INFO  govee::commands::serve] Diffuser (1C:F5:60:74:F4:17:65:72) sku=H7162
[2024-01-09T16:02:47 INFO  govee::commands::serve]   Platform API: devices.types.aroma_diffuser. supports_rgb=false supports_brightness=false
[2024-01-09T16:02:47 INFO  govee::commands::serve]                 color_temp=None segment_rgb=None
[2024-01-09T16:02:47 INFO  govee::commands::serve]   Undoc: room=None supports_iot=true ble_only=false
[2024-01-09T16:02:47 INFO  govee::commands::serve]
[2024-01-09T16:02:48 INFO  govee::service::http] http server addr is <IP_ADDRESS>:8056
[2024-01-09T16:02:54 INFO  govee::service::hass] MQTT connected with status=CONNACK code 0: Connection Accepted.
[2024-01-09T16:03:07 INFO  govee::commands::serve] requesting update via IoT MQTT Diffuser (1C:F5:60:74:F4:17:65:72) None
[2024-01-09T16:19:07 INFO  govee::commands::serve] requesting update via IoT MQTT Diffuser (1C:F5:60:74:F4:17:65:72) Some(DeviceState { on: false, online: None, kelvin: 0, color: DeviceColor { r: 0, g: 0, b: 0 }, brightness: 0, scene: None, source: "AWS IoT API", updated: 2024-01-09T22:03:07.307091663Z })

Please share the logs from the version that isn't working for you

Just updated today and 3 of 3 Govee items are unavailable.   2 flood lights and 1 diffuser
s6-rc: info: service s6rc-oneshot-runner: starting
s6-rc: info: service s6rc-oneshot-runner successfully started
s6-rc: info: service fix-attrs: starting
s6-rc: info: service fix-attrs successfully started
s6-rc: info: service legacy-cont-init: starting
s6-rc: info: service legacy-cont-init successfully started
s6-rc: info: service legacy-services: starting
s6-rc: info: service legacy-services successfully started
GOVEE_API_KEY=REDACTED
GOVEE_MQTT_HOST=core-mosquitto
GOVEE_EMAIL=REDACTED
GOVEE_PASSWORD=REDACTED
GOVEE_MQTT_PASSWORD=REDACTED
GOVEE_MQTT_USER=addons
GOVEE_MQTT_PORT=1883
++ cd /app
++ exec /app/govee serve
[2024-01-10T09:41:27 INFO  govee::commands::serve] Starting service. version 2024.01.10-a8f0a956
[2024-01-10T09:41:27 INFO  govee::commands::serve] Querying platform API for device list
[2024-01-10T09:41:27 INFO  govee::commands::serve] Querying undocumented API for device + room list
[2024-01-10T09:41:28 INFO  govee::service::iot] Connected to IoT: CONNACK code 0: Connection Accepted.
[2024-01-10T09:41:28 INFO  govee::commands::serve] Starting LAN discovery
[2024-01-10T09:41:28 INFO  govee::service::iot] IoT (re)connected with status CONNACK code 0: Connection Accepted.
[2024-01-10T09:41:28 INFO  govee::commands::serve] Waiting 10 seconds for LAN API discovery
[2024-01-10T09:41:38 INFO  govee::commands::serve] Devices returned from Govee's APIs
[2024-01-10T09:41:38 INFO  govee::commands::serve] Smart Flood Lights 2 (D4:97:D7:39:32:33:38:7D) sku=H7062
[2024-01-10T09:41:38 INFO  govee::commands::serve]   LAN API: ip=<IP_ADDRESS>
[2024-01-10T09:41:38 INFO  govee::commands::serve]   Platform API: devices.types.light. supports_rgb=true supports_brightness=true
[2024-01-10T09:41:38 INFO  govee::commands::serve]                 color_temp=Some((2000, 9000)) segment_rgb=Some(0..2)
[2024-01-10T09:41:38 INFO  govee::commands::serve]   Undoc: room=Some("Outside") supports_iot=true ble_only=false
[2024-01-10T09:41:38 INFO  govee::commands::serve]   Quirk { sku: "H7062", icon: "mdi:light-flood-down", supports_rgb: true, supports_brightness: true, color_temp_range: Some((2000, 9000)), avoid_platform_api: false, ble_only: false, lan_api_capable: true, device_type: Light, supports_scenes: None }
[2024-01-10T09:41:38 INFO  govee::commands::serve]
[2024-01-10T09:41:38 INFO  govee::commands::serve] Smart Flood Lights 1 (14:0F:D1:39:32:33:1D:23) sku=H7062
[2024-01-10T09:41:38 INFO  govee::commands::serve]   LAN API: ip=<IP_ADDRESS>
[2024-01-10T09:41:38 INFO  govee::commands::serve]   Platform API: devices.types.light. supports_rgb=true supports_brightness=true
[2024-01-10T09:41:38 INFO  govee::commands::serve]                 color_temp=Some((2000, 9000)) segment_rgb=Some(0..2)
[2024-01-10T09:41:38 INFO  govee::commands::serve]   Undoc: room=Some("Outside") supports_iot=true ble_only=false
[2024-01-10T09:41:38 INFO  govee::commands::serve]   Quirk { sku: "H7062", icon: "mdi:light-flood-down", supports_rgb: true, supports_brightness: true, color_temp_range: Some((2000, 9000)), avoid_platform_api: false, ble_only: false, lan_api_capable: true, device_type: Light, supports_scenes: None }
[2024-01-10T09:41:38 INFO  govee::commands::serve]
[2024-01-10T09:41:38 INFO  govee::commands::serve] Diffuser (1C:F5:60:74:F4:17:65:72) sku=H7162
[2024-01-10T09:41:38 INFO  govee::commands::serve]   Platform API: devices.types.aroma_diffuser. supports_rgb=false supports_brightness=false
[2024-01-10T09:41:38 INFO  govee::commands::serve]                 color_temp=None segment_rgb=None
[2024-01-10T09:41:38 INFO  govee::commands::serve]   Undoc: room=None supports_iot=true ble_only=false
[2024-01-10T09:41:38 INFO  govee::commands::serve]
[2024-01-10T09:41:38 INFO  govee::service::http] http server addr is <IP_ADDRESS>:8056
[2024-01-10T09:41:43 WARN  govee::hass_mqtt::enumerator] Do something about Mode presetScene for Diffuser (1C:F5:60:74:F4:17:65:72) DeviceCapability { kind: Mode, instance: "presetScene", parameters: Some(Enum { options: [EnumOption { name: "Morning", value: Number(82291), extras: {} }, EnumOption { name: "Heat Around a Fireplace", value: Number(82292), extras: {} }, EnumOption { name: "Creek", value: Number(82293), extras: {} }, EnumOption { name: "Good Night Kiss", value: Number(82294), extras: {} }, EnumOption { name: "Night Light", value: Number(82295), extras: {} }, EnumOption { name: "Meditation", value: Number(82296), extras: {} }, EnumOption { name: "Firework Party", value: Number(82297), extras: {} }, EnumOption { name: "Deep Thought", value: Number(82298), extras: {} }, EnumOption { name: "Rainbow Bubble", value: Number(82299), extras: {} }, EnumOption { name: "Autumn Rain Hitting Leaves", value: Number(82300), extras: {} }, EnumOption { name: "Space Walk", value: Number(82301), extras: {} }, EnumOption { name: "Crossing the Field", value: Number(82302), extras: {} }] }), alarm_type: None, event_state: None }
[2024-01-10T09:41:43 INFO  govee::service::hass] Wait 550ms for hass to settle on 11 entity configs
[2024-01-10T09:41:44 INFO  govee::service::hass] MQTT connected with status=CONNACK code 0: Connection Accepted.
[2024-01-10T09:41:56 INFO  govee::service::hass] Home Assistant status changed: offline
[2024-01-10T09:41:56 WARN  govee::hass_mqtt::enumerator] Do something about Mode presetScene for Diffuser (1C:F5:60:74:F4:17:65:72) DeviceCapability { kind: Mode, instance: "presetScene", parameters: Some(Enum { options: [EnumOption { name: "Morning", value: Number(82291), extras: {} }, EnumOption { name: "Heat Around a Fireplace", value: Number(82292), extras: {} }, EnumOption { name: "Creek", value: Number(82293), extras: {} }, EnumOption { name: "Good Night Kiss", value: Number(82294), extras: {} }, EnumOption { name: "Night Light", value: Number(82295), extras: {} }, EnumOption { name: "Meditation", value: Number(82296), extras: {} }, EnumOption { name: "Firework Party", value: Number(82297), extras: {} }, EnumOption { name: "Deep Thought", value: Number(82298), extras: {} }, EnumOption { name: "Rainbow Bubble", value: Number(82299), extras: {} }, EnumOption { name: "Autumn Rain Hitting Leaves", value: Number(82300), extras: {} }, EnumOption { name: "Space Walk", value: Number(82301), extras: {} }, EnumOption { name: "Crossing the Field", value: Number(82302), extras: {} }] }), alarm_type: None, event_state: None }
[2024-01-10T09:41:56 INFO  govee::service::hass] Wait 550ms for hass to settle on 11 entity configs
[2024-01-10T09:41:58 INFO  govee::service::state] requesting update via Platform API Diffuser (1C:F5:60:74:F4:17:65:72) None
[2024-01-10T09:41:58 WARN  govee::hass_mqtt::enumerator] Do something about Mode presetScene for Diffuser (1C:F5:60:74:F4:17:65:72) DeviceCapability { kind: Mode, instance: "presetScene", parameters: Some(Enum { options: [EnumOption { name: "Morning", value: Number(82291), extras: {} }, EnumOption { name: "Heat Around a Fireplace", value: Number(82292), extras: {} }, EnumOption { name: "Creek", value: Number(82293), extras: {} }, EnumOption { name: "Good Night Kiss", value: Number(82294), extras: {} }, EnumOption { name: "Night Light", value: Number(82295), extras: {} }, EnumOption { name: "Meditation", value: Number(82296), extras: {} }, EnumOption { name: "Firework Party", value: Number(82297), extras: {} }, EnumOption { name: "Deep Thought", value: Number(82298), extras: {} }, EnumOption { name: "Rainbow Bubble", value: Number(82299), extras: {} }, EnumOption { name: "Autumn Rain Hitting Leaves", value: Number(82300), extras: {} }, EnumOption { name: "Space Walk", value: Number(82301), extras: {} }, EnumOption { name: "Crossing the Field", value: Number(82302), extras: {} }] }), alarm_type: None, event_state: None }
[2024-01-10T09:42:54 INFO  govee::service::hass] Home Assistant status changed: online
[2024-01-10T09:42:54 WARN  govee::hass_mqtt::enumerator] Do something about Mode presetScene for Diffuser (1C:F5:60:74:F4:17:65:72) DeviceCapability { kind: Mode, instance: "presetScene", parameters: Some(Enum { options: [EnumOption { name: "Morning", value: Number(82291), extras: {} }, EnumOption { name: "Heat Around a Fireplace", value: Number(82292), extras: {} }, EnumOption { name: "Creek", value: Number(82293), extras: {} }, EnumOption { name: "Good Night Kiss", value: Number(82294), extras: {} }, EnumOption { name: "Night Light", value: Number(82295), extras: {} }, EnumOption { name: "Meditation", value: Number(82296), extras: {} }, EnumOption { name: "Firework Party", value: Number(82297), extras: {} }, EnumOption { name: "Deep Thought", value: Number(82298), extras: {} }, EnumOption { name: "Rainbow Bubble", value: Number(82299), extras: {} }, EnumOption { name: "Autumn Rain Hitting Leaves", value: Number(82300), extras: {} }, EnumOption { name: "Space Walk", value: Number(82301), extras: {} }, EnumOption { name: "Crossing the Field", value: Number(82302), extras: {} }] }), alarm_type: None, event_state: None }
[2024-01-10T09:42:54 INFO  govee::service::hass] Wait 550ms for hass to settle on 11 entity configs
[2024-01-10T09:56:58 INFO  govee::service::state] requesting update via Platform API Diffuser (1C:F5:60:74:F4:17:65:72) Some(DeviceState { on: false, online: Some(true), kelvin: 0, color: DeviceColor { r: 0, g: 0, b: 0 }, brightness: 0, scene: None, source: "PLATFORM API", updated: 2024-01-10T15:41:58.351584899Z })
[2024-01-10T09:56:58 WARN  govee::hass_mqtt::enumerator] Do something about Mode presetScene for Diffuser (1C:F5:60:74:F4:17:65:72) DeviceCapability { kind: Mode, instance: "presetScene", parameters: Some(Enum { options: [EnumOption { name: "Morning", value: Number(82291), extras: {} }, EnumOption { name: "Heat Around a Fireplace", value: Number(82292), extras: {} }, EnumOption { name: "Creek", value: Number(82293), extras: {} }, EnumOption { name: "Good Night Kiss", value: Number(82294), extras: {} }, EnumOption { name: "Night Light", value: Number(82295), extras: {} }, EnumOption { name: "Meditation", value: Number(82296), extras: {} }, EnumOption { name: "Firework Party", value: Number(82297), extras: {} }, EnumOption { name: "Deep Thought", value: Number(82298), extras: {} }, EnumOption { name: "Rainbow Bubble", value: Number(82299), extras: {} }, EnumOption { name: "Autumn Rain Hitting Leaves", value: Number(82300), extras: {} }, EnumOption { name: "Space Walk", value: Number(82301), extras: {} }, EnumOption { name: "Crossing the Field", value: Number(82302), extras: {} }] }), alarm_type: None, event_state: None }
[2024-01-10T10:11:58 INFO  govee::service::state] requesting update via Platform API Diffuser (1C:F5:60:74:F4:17:65:72) Some(DeviceState { on: false, online: Some(true), kelvin: 0, color: DeviceColor { r: 0, g: 0, b: 0 }, brightness: 0, scene: None, source: "PLATFORM API", updated: 2024-01-10T15:56:58.636469123Z })
[2024-01-10T10:11:58 WARN  govee::hass_mqtt::enumerator] Do something about Mode presetScene for Diffuser (1C:F5:60:74:F4:17:65:72) DeviceCapability { kind: Mode, instance: "presetScene", parameters: Some(Enum { options: [EnumOption { name: "Morning", value: Number(82291), extras: {} }, EnumOption { name: "Heat Around a Fireplace", value: Number(82292), extras: {} }, EnumOption { name: "Creek", value: Number(82293), extras: {} }, EnumOption { name: "Good Night Kiss", value: Number(82294), extras: {} }, EnumOption { name: "Night Light", value: Number(82295), extras: {} }, EnumOption { name: "Meditation", value: Number(82296), extras: {} }, EnumOption { name: "Firework Party", value: Number(82297), extras: {} }, EnumOption { name: "Deep Thought", value: Number(82298), extras: {} }, EnumOption { name: "Rainbow Bubble", value: Number(82299), extras: {} }, EnumOption { name: "Autumn Rain Hitting Leaves", value: Number(82300), extras: {} }, EnumOption { name: "Space Walk", value: Number(82301), extras: {} }, EnumOption { name: "Crossing the Field", value: Number(82302), extras: {} }] }), alarm_type: None, event_state: None }

What do you mean by unavailable? Are they not present at all in Home Assistant?
Are they greyed out?
What does home assistant log about these devices?

They exist but are appear as unavailable.
IM going back to the Jan 7 version again to get it working but will upgrade again and get more logs for you, stand by

Here is what the Govee2MQTT logs look like when its working
s6-rc: info: service s6rc-oneshot-runner: starting
s6-rc: info: service s6rc-oneshot-runner successfully started
s6-rc: info: service fix-attrs: starting
s6-rc: info: service fix-attrs successfully started
s6-rc: info: service legacy-cont-init: starting
s6-rc: info: service legacy-cont-init successfully started
s6-rc: info: service legacy-services: starting
s6-rc: info: service legacy-services successfully started
GOVEE_API_KEY=REDACTED
GOVEE_MQTT_HOST=core-mosquitto
GOVEE_EMAIL=REDACTED
GOVEE_PASSWORD=REDACTED
GOVEE_MQTT_PASSWORD=REDACTED
GOVEE_MQTT_USER=addons
GOVEE_MQTT_PORT=1883
++ cd /app
++ exec /app/govee serve
[2024-01-10T10:55:46 INFO  govee::commands::serve] Starting service. version 2024.01.07-92fb55e0
[2024-01-10T10:55:46 INFO  govee::commands::serve] Querying platform API for device list
[2024-01-10T10:55:47 INFO  govee::commands::serve] Querying undocumented API for device + room list
[2024-01-10T10:55:48 INFO  govee::service::iot] Connected to IoT: CONNACK code 0: Connection Accepted.
[2024-01-10T10:55:48 INFO  govee::commands::serve] Starting LAN discovery
[2024-01-10T10:55:48 INFO  govee::service::iot] IoT (re)connected with status CONNACK code 0: Connection Accepted.
[2024-01-10T10:55:52 INFO  govee::commands::serve] Devices returned from Govee's APIs
[2024-01-10T10:55:52 INFO  govee::commands::serve] Smart Flood Lights 2 (D4:97:D7:39:32:33:38:7D) sku=H7062
[2024-01-10T10:55:52 INFO  govee::commands::serve]   LAN API: ip=<IP_ADDRESS>
[2024-01-10T10:55:52 INFO  govee::commands::serve]   Platform API: devices.types.light. supports_rgb=true supports_brightness=true
[2024-01-10T10:55:52 INFO  govee::commands::serve]                 color_temp=Some((2000, 9000)) segment_rgb=Some(0..2)
[2024-01-10T10:55:52 INFO  govee::commands::serve]   Undoc: room=Some("Outside") supports_iot=true ble_only=false
[2024-01-10T10:55:52 INFO  govee::commands::serve]   Quirk: Quirk { sku: "H7062", icon: "mdi:light-flood-down", supports_rgb: true, supports_brightness: true, color_temp_range: Some((2000, 9000)), avoid_platform_api: false, ble_only: false, lan_api_capable: true }
[2024-01-10T10:55:52 INFO  govee::commands::serve]
[2024-01-10T10:55:52 INFO  govee::commands::serve] Smart Flood Lights 1 (14:0F:D1:39:32:33:1D:23) sku=H7062
[2024-01-10T10:55:52 INFO  govee::commands::serve]   LAN API: ip=<IP_ADDRESS>
[2024-01-10T10:55:52 INFO  govee::commands::serve]   Platform API: devices.types.light. supports_rgb=true supports_brightness=true
[2024-01-10T10:55:52 INFO  govee::commands::serve]                 color_temp=Some((2000, 9000)) segment_rgb=Some(0..2)
[2024-01-10T10:55:52 INFO  govee::commands::serve]   Undoc: room=Some("Outside") supports_iot=true ble_only=false
[2024-01-10T10:55:52 INFO  govee::commands::serve]   Quirk: Quirk { sku: "H7062", icon: "mdi:light-flood-down", supports_rgb: true, supports_brightness: true, color_temp_range: Some((2000, 9000)), avoid_platform_api: false, ble_only: false, lan_api_capable: true }
[2024-01-10T10:55:52 INFO  govee::commands::serve]
[2024-01-10T10:55:52 INFO  govee::commands::serve] Diffuser (1C:F5:60:74:F4:17:65:72) sku=H7162
[2024-01-10T10:55:52 INFO  govee::commands::serve]   Platform API: devices.types.aroma_diffuser. supports_rgb=false supports_brightness=false
[2024-01-10T10:55:52 INFO  govee::commands::serve]                 color_temp=None segment_rgb=None
[2024-01-10T10:55:52 INFO  govee::commands::serve]   Undoc: room=None supports_iot=true ble_only=false
[2024-01-10T10:55:52 INFO  govee::commands::serve]
[2024-01-10T10:55:52 INFO  govee::service::http] http server addr is <IP_ADDRESS>:8056
[2024-01-10T10:55:58 INFO  govee::service::hass] MQTT connected with status=CONNACK code 0: Connection Accepted.
[2024-01-10T10:56:12 INFO  govee::commands::serve] requesting update via IoT MQTT Diffuser (1C:F5:60:74:F4:17:65:72) None

HA logs show this when its working (Filtered by "Govee"
Home Assistant Core
2024-01-10 10:38:46.587 WARNING (SyncWorker_1) [homeassistant.loader] We found a custom integration govee which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant

Govee Logs using the Jan 10 version
s6-rc: info: service s6rc-oneshot-runner: starting
s6-rc: info: service s6rc-oneshot-runner successfully started
s6-rc: info: service fix-attrs: starting
s6-rc: info: service fix-attrs successfully started
s6-rc: info: service legacy-cont-init: starting
s6-rc: info: service legacy-cont-init successfully started
s6-rc: info: service legacy-services: starting
s6-rc: info: service legacy-services successfully started
GOVEE_API_KEY=REDACTED
GOVEE_MQTT_HOST=core-mosquitto
GOVEE_EMAIL=REDACTED
GOVEE_PASSWORD=REDACTED
GOVEE_MQTT_PASSWORD=REDACTED
GOVEE_MQTT_USER=addons
GOVEE_MQTT_PORT=1883
++ cd /app
++ exec /app/govee serve
[2024-01-10T11:00:35 INFO  govee::commands::serve] Starting service. version 2024.01.10-a8f0a956
[2024-01-10T11:00:35 INFO  govee::commands::serve] Querying platform API for device list
[2024-01-10T11:00:35 INFO  govee::commands::serve] Querying undocumented API for device + room list
[2024-01-10T11:00:36 INFO  govee::service::iot] Connected to IoT: CONNACK code 0: Connection Accepted.
[2024-01-10T11:00:36 INFO  govee::commands::serve] Starting LAN discovery
[2024-01-10T11:00:36 INFO  govee::commands::serve] Waiting 10 seconds for LAN API discovery
[2024-01-10T11:00:36 INFO  govee::service::iot] IoT (re)connected with status CONNACK code 0: Connection Accepted.
[2024-01-10T11:00:46 INFO  govee::commands::serve] Devices returned from Govee's APIs
[2024-01-10T11:00:46 INFO  govee::commands::serve] Smart Flood Lights 1 (14:0F:D1:39:32:33:1D:23) sku=H7062
[2024-01-10T11:00:46 INFO  govee::commands::serve]   LAN API: ip=<IP_ADDRESS>
[2024-01-10T11:00:46 INFO  govee::commands::serve]   Platform API: devices.types.light. supports_rgb=true supports_brightness=true
[2024-01-10T11:00:46 INFO  govee::commands::serve]                 color_temp=Some((2000, 9000)) segment_rgb=Some(0..2)
[2024-01-10T11:00:46 INFO  govee::commands::serve]   Undoc: room=Some("Outside") supports_iot=true ble_only=false
[2024-01-10T11:00:46 INFO  govee::commands::serve]   Quirk { sku: "H7062", icon: "mdi:light-flood-down", supports_rgb: true, supports_brightness: true, color_temp_range: Some((2000, 9000)), avoid_platform_api: false, ble_only: false, lan_api_capable: true, device_type: Light, supports_scenes: None }
[2024-01-10T11:00:46 INFO  govee::commands::serve]
[2024-01-10T11:00:46 INFO  govee::commands::serve] Smart Flood Lights 2 (D4:97:D7:39:32:33:38:7D) sku=H7062
[2024-01-10T11:00:46 INFO  govee::commands::serve]   LAN API: ip=<IP_ADDRESS>
[2024-01-10T11:00:46 INFO  govee::commands::serve]   Platform API: devices.types.light. supports_rgb=true supports_brightness=true
[2024-01-10T11:00:46 INFO  govee::commands::serve]                 color_temp=Some((2000, 9000)) segment_rgb=Some(0..2)
[2024-01-10T11:00:46 INFO  govee::commands::serve]   Undoc: room=Some("Outside") supports_iot=true ble_only=false
[2024-01-10T11:00:46 INFO  govee::commands::serve]   Quirk { sku: "H7062", icon: "mdi:light-flood-down", supports_rgb: true, supports_brightness: true, color_temp_range: Some((2000, 9000)), avoid_platform_api: false, ble_only: false, lan_api_capable: true, device_type: Light, supports_scenes: None }
[2024-01-10T11:00:46 INFO  govee::commands::serve]
[2024-01-10T11:00:46 INFO  govee::commands::serve] Diffuser (1C:F5:60:74:F4:17:65:72) sku=H7162
[2024-01-10T11:00:46 INFO  govee::commands::serve]   Platform API: devices.types.aroma_diffuser. supports_rgb=false supports_brightness=false
[2024-01-10T11:00:46 INFO  govee::commands::serve]                 color_temp=None segment_rgb=None
[2024-01-10T11:00:46 INFO  govee::commands::serve]   Undoc: room=None supports_iot=true ble_only=false
[2024-01-10T11:00:46 INFO  govee::commands::serve]
[2024-01-10T11:00:46 INFO  govee::service::http] http server addr is <IP_ADDRESS>:8056
[2024-01-10T11:00:51 WARN  govee::hass_mqtt::enumerator] Do something about Mode presetScene for Diffuser (1C:F5:60:74:F4:17:65:72) DeviceCapability { kind: Mode, instance: "presetScene", parameters: Some(Enum { options: [EnumOption { name: "Morning", value: Number(82291), extras: {} }, EnumOption { name: "Heat Around a Fireplace", value: Number(82292), extras: {} }, EnumOption { name: "Creek", value: Number(82293), extras: {} }, EnumOption { name: "Good Night Kiss", value: Number(82294), extras: {} }, EnumOption { name: "Night Light", value: Number(82295), extras: {} }, EnumOption { name: "Meditation", value: Number(82296), extras: {} }, EnumOption { name: "Firework Party", value: Number(82297), extras: {} }, EnumOption { name: "Deep Thought", value: Number(82298), extras: {} }, EnumOption { name: "Rainbow Bubble", value: Number(82299), extras: {} }, EnumOption { name: "Autumn Rain Hitting Leaves", value: Number(82300), extras: {} }, EnumOption { name: "Space Walk", value: Number(82301), extras: {} }, EnumOption { name: "Crossing the Field", value: Number(82302), extras: {} }] }), alarm_type: None, event_state: None }
[2024-01-10T11:00:51 INFO  govee::service::hass] Wait 550ms for hass to settle on 11 entity configs
[2024-01-10T11:00:51 INFO  govee::service::hass] MQTT connected with status=CONNACK code 0: Connection Accepted.
[2024-01-10T11:01:06 INFO  govee::service::state] requesting update via Platform API Diffuser (1C:F5:60:74:F4:17:65:72) None
[2024-01-10T11:01:06 WARN  govee::hass_mqtt::enumerator] Do something about Mode presetScene for Diffuser (1C:F5:60:74:F4:17:65:72) DeviceCapability { kind: Mode, instance: "presetScene", parameters: Some(Enum { options: [EnumOption { name: "Morning", value: Number(82291), extras: {} }, EnumOption { name: "Heat Around a Fireplace", value: Number(82292), extras: {} }, EnumOption { name: "Creek", value: Number(82293), extras: {} }, EnumOption { name: "Good Night Kiss", value: Number(82294), extras: {} }, EnumOption { name: "Night Light", value: Number(82295), extras: {} }, EnumOption { name: "Meditation", value: Number(82296), extras: {} }, EnumOption { name: "Firework Party", value: Number(82297), extras: {} }, EnumOption { name: "Deep Thought", value: Number(82298), extras: {} }, EnumOption { name: "Rainbow Bubble", value: Number(82299), extras: {} }, EnumOption { name: "Autumn Rain Hitting Leaves", value: Number(82300), extras: {} }, EnumOption { name: "Space Walk", value: Number(82301), extras: {} }, EnumOption { name: "Crossing the Field", value: Number(82302), extras: {} }] }), alarm_type: None, event_state: None }
[2024-01-10T11:02:57 INFO  govee::service::hass] Command for Smart Flood Lights 1 (14:0F:D1:39:32:33:1D:23): {"state":"ON"}
[2024-01-10T11:02:57 INFO  govee::service::state] Using LAN API to set Smart Flood Lights 1 (14:0F:D1:39:32:33:1D:23) power state
[2024-01-10T11:02:59 INFO  govee::service::hass] Command for Smart Flood Lights 1 (14:0F:D1:39:32:33:1D:23): {"state":"OFF"}
[2024-01-10T11:02:59 INFO  govee::service::state] Using LAN API to set Smart Flood Lights 1 (14:0F:D1:39:32:33:1D:23) power state
[2024-01-10T11:03:57 INFO  govee::service::hass] Command for Smart Flood Lights 1 (14:0F:D1:39:32:33:1D:23): {"state":"ON"}
[2024-01-10T11:03:57 INFO  govee::service::state] Using LAN API to set Smart Flood Lights 1 (14:0F:D1:39:32:33:1D:23) power state
[2024-01-10T11:03:58 INFO  govee::service::hass] Command for Smart Flood Lights 1 (14:0F:D1:39:32:33:1D:23): {"state":"OFF"}
[2024-01-10T11:03:58 INFO  govee::service::state] Using LAN API to set Smart Flood Lights 1 (14:0F:D1:39:32:33:1D:23) power state
[2024-01-10T11:04:37 INFO  govee::service::hass] Home Assistant status changed: offline
[2024-01-10T11:04:37 WARN  govee::hass_mqtt::enumerator] Do something about Mode presetScene for Diffuser (1C:F5:60:74:F4:17:65:72) DeviceCapability { kind: Mode, instance: "presetScene", parameters: Some(Enum { options: [EnumOption { name: "Morning", value: Number(82291), extras: {} }, EnumOption { name: "Heat Around a Fireplace", value: Number(82292), extras: {} }, EnumOption { name: "Creek", value: Number(82293), extras: {} }, EnumOption { name: "Good Night Kiss", value: Number(82294), extras: {} }, EnumOption { name: "Night Light", value: Number(82295), extras: {} }, EnumOption { name: "Meditation", value: Number(82296), extras: {} }, EnumOption { name: "Firework Party", value: Number(82297), extras: {} }, EnumOption { name: "Deep Thought", value: Number(82298), extras: {} }, EnumOption { name: "Rainbow Bubble", value: Number(82299), extras: {} }, EnumOption { name: "Autumn Rain Hitting Leaves", value: Number(82300), extras: {} }, EnumOption { name: "Space Walk", value: Number(82301), extras: {} }, EnumOption { name: "Crossing the Field", value: Number(82302), extras: {} }] }), alarm_type: None, event_state: None }
[2024-01-10T11:04:37 INFO  govee::service::hass] Wait 550ms for hass to settle on 11 entity configs
[2024-01-10T11:05:31 INFO  govee::service::hass] Home Assistant status changed: online
[2024-01-10T11:05:31 WARN  govee::hass_mqtt::enumerator] Do something about Mode presetScene for Diffuser (1C:F5:60:74:F4:17:65:72) DeviceCapability { kind: Mode, instance: "presetScene", parameters: Some(Enum { options: [EnumOption { name: "Morning", value: Number(82291), extras: {} }, EnumOption { name: "Heat Around a Fireplace", value: Number(82292), extras: {} }, EnumOption { name: "Creek", value: Number(82293), extras: {} }, EnumOption { name: "Good Night Kiss", value: Number(82294), extras: {} }, EnumOption { name: "Night Light", value: Number(82295), extras: {} }, EnumOption { name: "Meditation", value: Number(82296), extras: {} }, EnumOption { name: "Firework Party", value: Number(82297), extras: {} }, EnumOption { name: "Deep Thought", value: Number(82298), extras: {} }, EnumOption { name: "Rainbow Bubble", value: Number(82299), extras: {} }, EnumOption { name: "Autumn Rain Hitting Leaves", value: Number(82300), extras: {} }, EnumOption { name: "Space Walk", value: Number(82301), extras: {} }, EnumOption { name: "Crossing the Field", value: Number(82302), extras: {} }] }), alarm_type: None, event_state: None }
[2024-01-10T11:05:31 INFO  govee::service::hass] Wait 550ms for hass to settle on 11 entity configs

Logs using the latest version  HA Core and Supervisor.  No other logs have entries that contain "Govee"
Home Assistant Core
2024-01-10 11:04:45.132 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration govee which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant
Home Assistant Supervisor
24-01-10 10:55:34 INFO (MainThread) [supervisor.addons.addon] Restore config for addon b9845f46_govee2mqtt
24-01-10 10:55:34 INFO (SyncWorker_6) [supervisor.docker.manager] Stopping addon_b9845f46_govee2mqtt application
24-01-10 10:55:38 INFO (SyncWorker_6) [supervisor.docker.manager] Cleaning addon_b9845f46_govee2mqtt application
24-01-10 10:55:38 INFO (MainThread) [supervisor.addons.addon] Restore/Install of image for addon b9845f46_govee2mqtt
24-01-10 10:55:38 INFO (MainThread) [supervisor.docker.interface] Downloading docker image ghcr.io/wez/govee2mqtt-aarch64 with tag 2024.01.07-92fb55e0.
24-01-10 10:55:42 INFO (SyncWorker_7) [supervisor.docker.manager] Cleanup images: ['ghcr.io/wez/govee2mqtt-aarch64:2024.01.09-c0925c04']
24-01-10 10:55:42 INFO (MainThread) [supervisor.addons.addon] Restoring data and config for addon b9845f46_govee2mqtt
24-01-10 10:55:42 INFO (MainThread) [supervisor.docker.addon] Starting Docker add-on ghcr.io/wez/govee2mqtt-aarch64 with version 2024.01.07-92fb55e0
24-01-10 10:55:42 INFO (MainThread) [supervisor.addons.addon] Finished restore for add-on b9845f46_govee2mqtt
24-01-10 10:57:42 WARNING (MainThread) [supervisor.addons.addon] Timeout while waiting for addon Govee to MQTT Bridge to start, took more than 120 seconds
24-01-10 11:00:21 INFO (MainThread) [supervisor.addons.addon] Building backup for add-on b9845f46_govee2mqtt
24-01-10 11:00:21 INFO (MainThread) [supervisor.addons.addon] Finish backup for addon b9845f46_govee2mqtt
24-01-10 11:00:21 INFO (MainThread) [supervisor.docker.addon] Updating image ghcr.io/wez/govee2mqtt-aarch64:2024.01.07-92fb55e0 to ghcr.io/wez/govee2mqtt-aarch64:2024.01.10-a8f0a956
24-01-10 11:00:21 INFO (MainThread) [supervisor.docker.interface] Downloading docker image ghcr.io/wez/govee2mqtt-aarch64 with tag 2024.01.10-a8f0a956.
24-01-10 11:00:27 INFO (SyncWorker_7) [supervisor.docker.manager] Stopping addon_b9845f46_govee2mqtt application
24-01-10 11:00:30 INFO (SyncWorker_7) [supervisor.docker.manager] Cleaning addon_b9845f46_govee2mqtt application
24-01-10 11:00:30 INFO (MainThread) [supervisor.addons.addon] Add-on 'b9845f46_govee2mqtt' successfully updated
24-01-10 11:00:30 INFO (SyncWorker_3) [supervisor.docker.manager] Cleanup images: ['ghcr.io/wez/govee2mqtt-aarch64:2024.01.07-92fb55e0']
24-01-10 11:00:31 INFO (MainThread) [supervisor.docker.addon] Starting Docker add-on ghcr.io/wez/govee2mqtt-aarch64 with version 2024.01.10-a8f0a956
24-01-10 11:02:31 WARNING (MainThread) [supervisor.addons.addon] Timeout while waiting for addon Govee to MQTT Bridge to start, took more than 120 seconds
24-01-10 11:02:31 INFO (MainThread) [supervisor.store.git] Update add-on https://github.com/wez/govee2mqtt repository
24-01-10 11:04:50 INFO (MainThread) [supervisor.store.git] Update add-on https://github.com/wez/govee2mqtt repository

Note that from Home Assistant's perspective, this addon appears to work via the MQTT integration.  The Govee integration is not related to this one aside from the associated brand of devices.

Your logs appear to show Home Assistant as going offline and then coming back online.  Are you restarting Home Assistant?
Can you try restarting just the govee2mqtt addon without restarting home assistant?

When looking at the home assistant looks, look for gv2mqtt or mqtt. I suspect there is something in there that will reveal more about what is happening.

The devices appear to work find until a reboot after the upgrade upgrade.
Post reboot Supervisor logs filtered by MQTT
24-01-10 11:29:56 WARNING (MainThread) [supervisor.addons.options] Unknown option 'base_topic' for Zigbee2MQTT (45df7312_zigbee2mqtt)
24-01-10 11:34:56 WARNING (MainThread) [supervisor.addons.options] Unknown option 'base_topic' for Zigbee2MQTT (45df7312_zigbee2mqtt)
24-01-10 11:39:56 WARNING (MainThread) [supervisor.addons.options] Unknown option 'base_topic' for Zigbee2MQTT (45df7312_zigbee2mqtt)
24-01-10 11:44:56 WARNING (MainThread) [supervisor.addons.options] Unknown option 'base_topic' for Zigbee2MQTT (45df7312_zigbee2mqtt)
24-01-10 11:49:56 WARNING (MainThread) [supervisor.addons.options] Unknown option 'base_topic' for Zigbee2MQTT (45df7312_zigbee2mqtt)
24-01-10 11:54:15 INFO (MainThread) [supervisor.addons.addon] Building backup for add-on b9845f46_govee2mqtt
24-01-10 11:54:24 INFO (MainThread) [supervisor.addons.addon] Finish backup for addon b9845f46_govee2mqtt
24-01-10 11:54:24 INFO (MainThread) [supervisor.docker.addon] Updating image ghcr.io/wez/govee2mqtt-aarch64:2024.01.07-92fb55e0 to ghcr.io/wez/govee2mqtt-aarch64:2024.01.10-a8f0a956
24-01-10 11:54:24 INFO (MainThread) [supervisor.docker.interface] Downloading docker image ghcr.io/wez/govee2mqtt-aarch64 with tag 2024.01.10-a8f0a956.
24-01-10 11:54:27 INFO (SyncWorker_3) [supervisor.docker.manager] Stopping addon_b9845f46_govee2mqtt application
24-01-10 11:54:31 INFO (SyncWorker_3) [supervisor.docker.manager] Cleaning addon_b9845f46_govee2mqtt application
24-01-10 11:54:31 INFO (MainThread) [supervisor.addons.addon] Add-on 'b9845f46_govee2mqtt' successfully updated
24-01-10 11:54:31 INFO (SyncWorker_6) [supervisor.docker.manager] Cleanup images: ['ghcr.io/wez/govee2mqtt-aarch64:2024.01.07-92fb55e0']
24-01-10 11:54:32 INFO (MainThread) [supervisor.docker.addon] Starting Docker add-on ghcr.io/wez/govee2mqtt-aarch64 with version 2024.01.10-a8f0a956
24-01-10 11:54:56 WARNING (MainThread) [supervisor.addons.options] Unknown option 'base_topic' for Zigbee2MQTT (45df7312_zigbee2mqtt)
24-01-10 11:56:32 WARNING (MainThread) [supervisor.addons.addon] Timeout while waiting for addon Govee to MQTT Bridge to start, took more than 120 seconds
24-01-10 11:56:32 INFO (MainThread) [supervisor.store.git] Update add-on https://github.com/zigbee2mqtt/hassio-zigbee2mqtt repository
24-01-10 11:56:32 INFO (MainThread) [supervisor.store.git] Update add-on https://github.com/wez/govee2mqtt repository
24-01-10 11:56:32 INFO (MainThread) [supervisor.store.git] Update add-on https://github.com/adamoutler/mqtt-explorer repository
24-01-10 11:56:35 WARNING (MainThread) [supervisor.addons.options] Unknown option 'base_topic' for Zigbee2MQTT (45df7312_zigbee2mqtt)
24-01-10 12:01:34 WARNING (MainThread) [supervisor.addons.options] Unknown option 'base_topic' for Zigbee2MQTT (45df7312_zigbee2mqtt)
24-01-10 12:06:34 WARNING (MainThread) [supervisor.addons.options] Unknown option 'base_topic' for Zigbee2MQTT (45df7312_zigbee2mqtt)
24-01-10 12:11:34 WARNING (MainThread) [supervisor.addons.options] Unknown option 'base_topic' for Zigbee2MQTT (45df7312_zigbee2mqtt)
24-01-10 12:16:34 WARNING (MainThread) [supervisor.addons.options] Unknown option 'base_topic' for Zigbee2MQTT (45df7312_zigbee2mqtt)
24-01-10 12:21:34 WARNING (MainThread) [supervisor.addons.options] Unknown option 'base_topic' for Zigbee2MQTT (45df7312_zigbee2mqtt)
24-01-10 12:26:34 WARNING (MainThread) [supervisor.addons.options] Unknown option 'base_topic' for Zigbee2MQTT (45df7312_zigbee2mqtt)
24-01-10 12:27:58 INFO (MainThread) [supervisor.store.git] Update add-on https://github.com/zigbee2mqtt/hassio-zigbee2mqtt repository
24-01-10 12:27:58 INFO (MainThread) [supervisor.store.git] Update add-on https://github.com/wez/govee2mqtt repository
24-01-10 12:27:58 INFO (MainThread) [supervisor.store.git] Update add-on https://github.com/adamoutler/mqtt-explorer repository
24-01-10 12:28:06 WARNING (MainThread) [supervisor.addons.options] Unknown option 'base_topic' for Zigbee2MQTT (45df7312_zigbee2mqtt)
Post reboot Supervisor logs filtered by Govee
24-01-10 11:54:15 INFO (MainThread) [supervisor.addons.addon] Building backup for add-on b9845f46_govee2mqtt
24-01-10 11:54:24 INFO (MainThread) [supervisor.addons.addon] Finish backup for addon b9845f46_govee2mqtt
24-01-10 11:54:24 INFO (MainThread) [supervisor.docker.addon] Updating image ghcr.io/wez/govee2mqtt-aarch64:2024.01.07-92fb55e0 to ghcr.io/wez/govee2mqtt-aarch64:2024.01.10-a8f0a956
24-01-10 11:54:24 INFO (MainThread) [supervisor.docker.interface] Downloading docker image ghcr.io/wez/govee2mqtt-aarch64 with tag 2024.01.10-a8f0a956.
24-01-10 11:54:27 INFO (SyncWorker_3) [supervisor.docker.manager] Stopping addon_b9845f46_govee2mqtt application
24-01-10 11:54:31 INFO (SyncWorker_3) [supervisor.docker.manager] Cleaning addon_b9845f46_govee2mqtt application
24-01-10 11:54:31 INFO (MainThread) [supervisor.addons.addon] Add-on 'b9845f46_govee2mqtt' successfully updated
24-01-10 11:54:31 INFO (SyncWorker_6) [supervisor.docker.manager] Cleanup images: ['ghcr.io/wez/govee2mqtt-aarch64:2024.01.07-92fb55e0']
24-01-10 11:54:32 INFO (MainThread) [supervisor.docker.addon] Starting Docker add-on ghcr.io/wez/govee2mqtt-aarch64 with version 2024.01.10-a8f0a956
24-01-10 11:56:32 WARNING (MainThread) [supervisor.addons.addon] Timeout while waiting for addon Govee to MQTT Bridge to start, took more than 120 seconds
24-01-10 11:56:32 INFO (MainThread) [supervisor.store.git] Update add-on https://github.com/wez/govee2mqtt repository
24-01-10 12:27:58 INFO (MainThread) [supervisor.store.git] Update add-on https://github.com/wez/govee2mqtt repository

MQTT Explorer Addon looks like this after a reboot

gv2mqtt availability = offline

Maybe this helps too

Thanks for the context.
Is the addon actually running?
The availability topic is set to online as soon as the delay mentioned in:
[2024-01-10T11:05:31 INFO govee::service::hass] Wait 550ms for hass to settle on 11 entity configs

has expired.
That event should get triggered both on startup and whenever home assistant's own status (published via the homeassistant/status topic) changes, or if we reconnect to the mqtt broker for some reason.
The availability topic is never explicitly set to offline by govee2mqtt, but it does configure the mqtt session with a "last will" message that will set it to offline if the broker connection is closed.

based on your last comment I rebooted a second time and the devices are now available again.

I made a change to the way the last-will message is handled that might possibly help prevent this from being strange.  I do think that in your case, there was something a bit borked with the broker due to the restarting.
I'm going to close this issue as I don't think there is anything that govee2mqtt could do better in the situation you described, but do please let me know if you see something strange here again in the future.


Fixed reqHeadTimestamp and reqHistogramData

Adapted the encoding of a contract to match the code of the Java client. Fixed the order of values in reqHeadTimestamp and reqHistogramData to match the Java client.
I added unit tests, which work, but I could not get the full test suite to pass locally (e.g. requesting News). Probably some account restrictions.

Thanks for your PR, I will review it.


lua entry thread aborted

Summary
[error] 59#0: *471611 lua entry thread aborted: runtime error: .../share/lua/5.1/kong/db/strategies/postgres/connector.lua:343: attempt to perform arithmetic on local 'num_queries' (a nil value)
Steps To Reproduce

failed to connect postgres

4
Additional Details & Logs

Kong version ($ kong version)

1.3.0

Kong debug-level startup logs ($ kong start --vv)

debug

Kong error logs (<KONG_PREFIX>/logs/error.log)

Kong configuration (the output of a GET request to Kong's Admin port - see
https://docs.konghq.com/latest/admin-api/#retrieve-node-information)

Operating system
Linux deployment-automizely-api-gateway-85f8746555-gnxlb 4.14.137+ #1 SMP Wed Aug 7 22:33:44 PDT 2019 x86_64 x86_64 x86_64 GNU/Linux

Hi,
Please provide more detailed error logs when this occurs, so we can help troubleshoot. There is not enough detail here to be able to assist you. Thanks!

I think this is fixed with 1.4.0:
https://github.com/Kong/kong/commit/3f37ade432b0cf848e37c089df71ec0f622576e1#diff-126f4d3eab7dd01ac7ab193d1eb7f847R344
Thus closing this. @chensunny, please report back if you still have issue with it with Kong >= 1.4.0.


The quotes of the config are inconsistent in the "GitHub Configuration" node and the .yaml file

OS: Mac
Build Version: 20210707.11
Repro Steps:

Create a static web app.
Expand all "GitHub Configuration" nodes -> Check the config.
Click the children of all "GitHub Configuration" nodes to open the .yaml file -> Check the config.
Check whether the quotes of the config are consistent in the "GitHub Configuration" node and the .yaml file.

Expect:
The quotes of the config are consistent in the "GitHub Configuration" node and the .yaml file.

Actual:
The quotes of the config are inconsistent in the "GitHub Configuration" node and the .yaml file.

More Info:
This issue only reproduces for some GitHub Configurations of the static web app.

The way the settings are displayed on the tree item don't take the quotes into consideration.  This is because the yaml file will accept all three as valid settings:
app_location : 'app'
api_location: "api"
output_location: output

It doesn't seem worth the effort to display all three of these different possibilities.


Adopt plugin-scm-filter-branch-pr

Description
Adopt plugin-scm-filter-branch-pr https://github.com/jenkinsci/scm-filter-branch-pr-plugin
Adoption was confirmed by @samrocketman on this PR https://github.com/jenkinsci/scm-filter-branch-pr-plugin/pull/9/files
Submitter checklist for adding or changing permissions

Always

[x] Add link to plugin/component Git repository in description above

When enabling automated releases (cd: true)

[ ] Add a link to the pull request, which enables continuous delivery for your plugin or component.
Follow the documentation to ensure, your pull request is set up properly.

When adding new uploaders (this includes newly created permissions files)

[x] Make sure to @mention an existing maintainer to confirm the permissions request, if applicable
[x] Use the Jenkins community (LDAP) account name in the YAML file, not the GitHub account name
[x] Make sure to @mention the users being added so their GitHub account names are known if they require GitHub merge access (see below).
[x] All newly added users have logged in to Artifactory and Jira at least once

Reviewer checklist (not for requesters!)

[ ] Check this if newly added person also needs to be given merge permission to the GitHub repo (please @ the people/person with their GitHub username in this issue as well). If needed, it can be done using an IRC Bot command
[ ] Check that the $pluginId Developers team has Admin permissions while granting the access.
[ ] In the case of plugin adoption, ensure that the Jenkins Jira default assignee is either removed or changed to the new maintainer.
[ ] If security contacts are changed (this includes add/remove), ping the security officer (currently @Wadeck) in this pull request. If an email contact is changed, wait for approval from the security officer.

There are IRC Bot commands for it

Posed on dev list : https://groups.google.com/u/1/g/jenkinsci-dev/c/2oVS41hk_5k

Looks the content of the YAML file doesn't match actual maintainer (maybe they were added by hand on the permissions ?)
@sag47 Can you confirm ?

@NotMyFault I got approval on the PR https://github.com/jenkinsci/scm-filter-branch-pr-plugin/pull/9
Can we skip the wait period ? Thanks

LGTM


Javascript ES6

What is the possibility of added javascript capabilities to this project? It would open a lot of doors. I'm thinking shared libraries between react or react-native libraries.
Is there any plan for this?

I wish there was something like Babel that would generate Roku code somehow ... lol or something like ReactNative that generated Roku code.  I'd love to see an abstraction like this.  Would be sick.

The Roku runtime only supports writing apps in BrightScript. There have been a few attempts at creating a Javascript-to-BrightScript transpiler (see https://github.com/mattaylor/rokuJs and https://github.com/slheavner/js-to-bs for example - no affiliation) but nothing official.
Even ReactNative uses the Javascript runtime behind the scenes, and since Roku devices have no JS runtime, a transpiler that emits BrightScript is the only possibly technical solution.


Problems with saving the configuration

First, this looks like a gamechanger :-) so many people looking for it.
SO, i installed the Addon today, went to Configuration and set some of my settings.
But after click on "save" i got error warnings.
This is good if there is something wrong, but there are in my eyes "all" fields noted.

Any idea how to solve it? Here the yaml, as i sayed, just a few first changes to my data and will not save.
hass_url: empty OR <IP_ADDRESS> OR [localhost] OR http://homeassistant.local:8123/ tried all
long_lived_token: >-
xxxxxxxxxxxxxxxxxxxxxxxxxxxxx
costfun: self-consumption
logging_level: DEBUG
optimization_time_step: 30
historic_days_to_retrieve: 2
method_ts_round: nearest
set_total_pv_sell: false
lp_solver: COIN_CMD
lp_solver_path: /usr/bin/cbc
set_nocharge_from_grid: false
set_nodischarge_to_grid: false
set_battery_dynamic: false
battery_dynamic_max: 0.9
battery_dynamic_min: -0.9
load_forecast_method: naive
sensor_power_photovoltaics: sensor.total_dc_power
sensor_power_load_no_var_loads: sensor.load_power
number_of_deferrable_loads: 2
list_nominal_power_of_deferrable_loads:

nominal_power_of_deferrable_loads: 3000
nominal_power_of_deferrable_loads: 750
list_operating_hours_of_each_deferrable_load:
operating_hours_of_each_deferrable_load: 5
operating_hours_of_each_deferrable_load: 8
list_peak_hours_periods_start_hours:
peak_hours_periods_start_hours: "05:54"
peak_hours_periods_start_hours: 624
list_peak_hours_periods_end_hours:
peak_hours_periods_end_hours: "09:24"
peak_hours_periods_end_hours: 714
list_treat_deferrable_load_as_semi_cont:
treat_deferrable_load_as_semi_cont: true
treat_deferrable_load_as_semi_cont: true
load_peak_hours_cost: 0.1907
load_offpeak_hours_cost: 0.1419
photovoltaic_production_sell_price: 0.065
maximum_power_from_grid: 9000
list_pv_module_model:
pv_module_model: CSUN_Eurasia_Energy_Systems_Industry_and_Trade_CSUN295_60M
list_pv_inverter_model:
pv_inverter_model: Fronius_International_GmbH__Fronius_Primo_5_0_1_208_240__240V_
list_surface_tilt:
surface_tilt: 30
list_surface_azimuth:
surface_azimuth: 205
list_modules_per_string:
modules_per_string: 16
list_strings_per_inverter:
strings_per_inverter: 1
set_use_battery: true
battery_discharge_power_max: 1000
battery_charge_power_max: 1000
battery_discharge_efficiency: 0.95
battery_charge_efficiency: 0.95
battery_nominal_energy_capacity: 5000
battery_minimum_state_of_charge: 0.3
battery_maximum_state_of_charge: 0.9
battery_target_state_of_charge: 0.6

Thx, Oliver

Just released a new version. Try to update later. It should be solved.

Just released a new version. Try to update later. It should be solved.

Thanks, but same again.

This is related to #50
Any chance you can post the full log error? It is truncated. Go to the supervisor logger.
Also you have commas in your values: "0,3" should be "0.3"

This commas are there, i did not changed it.
Will see to get full error

I just took a copy of the yaml from this:
https://community.home-assistant.io/t/emhass-add-on-an-energy-management-optimization-add-on-for-home-assistant-os-and-supervised/405649/136?u=copadewe
and it work with this when I paste and copy it to my System.
I can also make changes, no idea why but it work with this now.
Have other problem - will first feed all my details and come back with another issue.
Oliver

THX @davidusb-geek

This is still an ongoing issue. Reopening it...

Same issue here..  default values, changing load and solar sensors: does not work.

Just check peak_hours_periods_start_hours and peak_hours_periods_end_hours format and save configuration and it should work. But I agree there is an annoyinbg issue changing this automatically to the wrong format

yes indeed .. working now..
it's not (yet) easy to understand how it works in detail .. need to study it a bit more. :-)
Would like to  ( based on consumption, weather/sun / battery Soc /dynamic energy pricing)
When to load battery and when to sell again and make profit:
High level:
charge between 03:00 and 06:00 6kW ( full battery)
discharge between 06 and 08 4kW ( or more if solar is expected)
Load again in the afternoon based on SoC and consumption planning make sure to have enough to cover peak and evening ( till 02 or 03 depending on when the low prices are planned)
Also trigger invertor when utilization is > 2500 W ( we have peak taxes in belgium if we consume > 2500 W avg for over 15minutes) -> now already done via automation

This should be solved with latests versions... Feel free to reopen otherwise


Pallab/group invite

Date: 28/9/2024

Developer Name: @pallabez

Issue Ticket Number
#238
Description
Invite someone to discord group using slash commands
Documentation Updated?

[x] Yes
[ ] No

Under Feature Flag

[x] Yes
[ ] No

Database Changes

[ ] Yes
[x] No

Breaking Changes

[ ] Yes
[x] No

Development Tested?

[x] Yes
[ ] No

Screenshots

Screenshot 1

Test Coverage

Screenshot 1

Additional Notes

Can you change the title of this PR?


cmd/compile: use better code for slicing

func f(s []int, i int) []int {
    return s[i]
}

The assembly starts out with
MOVQ	"".i+32(FP), AX
MOVQ	"".s+16(FP), CX
CMPQ	AX, CX
JHI	$0, 60
SUBQ	AX, CX

The CMP and SUB are almost redundant.  Instead, we could do
MOVQ	"".i+32(FP), AX
MOVQ	"".s+16(FP), CX
SUBQ	AX, CX
JHI	$0, 60

We just need a subtract that also generates flags. (We have a 32-bit one for synthesizing 64-bit ops.  We need a 64-bit one also.)

Typo in code snippet?

Thanks, fixed.


Roughness and Specular maps seem to be off

When exporting a .glb from blender I am coming across the issue of the material being extremely metallic See image 1

In the first version of GLTFKit it seems to be working.  image 2

It also seems to be working in the online gltfviewer image 3

Any advice on what might be wrong?
p.s here is the blender material node

If you're using a specular-glossiness workflow, that isn't fully supported. I'm still curious why it appears so shiny by default. If you can share this model or another model that exhibits this issue privately to<EMAIL_ADDRESS>I'll take a closer look.

I’ll send you the models tonight! Appreciate the help!

Thanks for sending those over; they made it much easier to track down. It turns out that we weren't mapping the PBR metallic/roughness factors over to SceneKit correctly. This should be looking much better as of 589ef13.

Wow, that was fast! We are pulling now and going to test. Really appreciate the help <3

This issue will be automatically closed in 7 days if no further reply is received.

Worked perfectly!
https://twitter.com/benmayorwhite/status/1517094376001970176?s=20&t=QQXyXqVufTLzYL6aMshMRw

Brilliant!


Add support for Rocky8, Rocky9, Ubuntu build

Add dependency installation scripts to support CentOS 7, Rocky8, Rocky9, and Ubuntu 22 build
Update README to reflect changes
Minor changes to support newer GCC compiler
Add dockerfiles for each supported distro / OS

NKV cli changes look good to me.


(Windows 10) Add ability to point a config directory.

What would you like to be added:
In windows 10, it's not immediately obvious where I need to store the config file in order for Lens to auto-detect it when adding a new cluster. It would be cool if I had an option to point to another folder that contains the config.
Why is this needed:
DigitalOcean configs expire after 7 days, so I have a weekly cron that runs on a machine on my home network which is responsible for refreshing it with their doctl utility. Unfortunately  I can't point Lens to the path where this config gets generated on my network and I can't create a shortcut to it either. Not only that, I'm not sure where this file would live on Windows for Lens to automatically detect it. I find it a bit inconvenient that I have to remove/add my cluster weekly.
Environment you are Lens application on:
Not sure I understand this question

Kubernetes distribution: [EKS, AKS, GKE, Rancher, ...] Whatever DigitalOcean provides. I'm unsure.
Desktop OS: Windows 10. I don't have this issue under Linux.

Or just add option general option to point to any existing config file. For example, eks has option to generate kubeconfig as .kube/eksctl/clusters/, currently you need to copy-paste content of this file to connect to cluster.

Lens currently saves the file location that you pass it if you add the cluster by "file-picking" the config file.
Would you be able to clarify what you mean by "for Lens to auto-detect it". As long as your cron job recreates the same file name then Lens will just continue to work.


Update containerd config to fix ImagePullBackOff error

What this PR does / why we need it:
Currently, make kind-up uses plugins."io.containerd.grpc.v1.cri".registry.mirrors to configure local image registry. However, this is deprecated and causes ImagePullBackOff error.
To fix this, update registry configs to use plugins."io.containerd.grpc.v1.cri".registry, set config_path, and add hosts.toml file. (registry configuration docs)
Which issue(s) this PR fixes:
Fixes #3152
Does this PR introduce a user-facing change?:

NONE

You make my day! 💯
I have just left a nit. Please fix it then
/lgtm

I fixed!

Nice 🙌
/approve

Great job!
/lgtm


Performance issues on 5.0.4

This last release seems to have made it worse, but when I first open the app, there's always a delay of at least 10 seconds before the list of articles is populated. Now with 5.0.4, it goes a step further and beachballs during that time. I'm on a 2018 MacBook Pro (2.2gz 6-core Intel i7) with 16GB of ram with at least 4GB free when I open the app.

Since updating to 5.0.4, I also am seeing a longer delay at launch, and once it got completely stuck with a beachball (sample attached).
Sample of NetNewsWire.txt

@michaeljtsai Your sample is very, very strange. Do you have any idea what could cause runaway com.apple.network.boringssl.metrics_queue serial queues?

@sgoodwin @michaeljtsai Are you using Feedbin syncing or On My Mac? Or both?

What NetNewsWire messages are appearing in Console?

@brentsimmons I'm using Feedbin and On My Mac. Is it perhaps using one queue per feed? I have about 1,500 local feeds.

@michaeljtsai If you disable the On My Mac account (you can turn it off in preferences, and turn it back on later), then re-launch, does this still happen?

Another thing to try — turn off sharing Mac analytics, then re-launch NetNewsWire and see if it still happens.
Here’s where the pref is. (Turned on in this screenshot.)

@brentsimmons I’ve always had the analytics off. If I disable the local accounts, it launches and refreshes almost instantly. With the local accounts, 5.0.3 takes about 56s to refresh, while 5.0.4 takes about 67s. It seemed like a bigger difference before I timed it because the progress bars behave differently. With 5.0.3, it moves very quickly up to about feed 1472 and then gradually finishes. With 5.0.4, it gets stuck for almost the entire time displaying a feed in the early 1300s and then instantly zooms to the end. This is not a big deal for me because I can still browse feeds and articles while it’s refreshing. I only posted here because of the beach ball hang (which hasn’t recurred) and because the release notes said that fetching was faster, which wasn’t what I was seeing.

By “fetching” I meant fetching from the database. That should have been made more clear.

I suspect the beachballing had to do with some new database cleanup code. The databases hadn’t really been kept clean, so with a large number of feeds it’s likely that this code took a while to do its thing the first few times.
The problem should go away, and refreshing-feeds performance should be pretty much the same as 5.0.3.
I’m going to close this. I’ll reopen it if it turns out to be a chronic issue.

I'm using local-only feeds. Here's a screenshot of the logs because I couldn't remember how to save just the bits from NNW:


Build Caffe2 on windows failed

I was trying to install Caffe2 on Windows Server 2016 (VM) with CMake, Visual Studio 2017 Community Edition, Python 3.5 (Anaconda 4.2.0) installed. When running Script\Build_Windows.bat, got the following error:
"C:\Users\sqlpythonadmin\Source\Repos\caffe2\build\ALL_BUILD.vcxproj" (default target) (1) ->
"C:\Users\sqlpythonadmin\Source\Repos\caffe2\build\caffe2\Caffe2_CPU.vcxproj" (default target) (3) ->
"C:\Users\sqlpythonadmin\Source\Repos\caffe2\build\caffe2\proto\Caffe2_PROTO.vcxproj" (default target) (4) ->
(ClCompile target) ->
C:\Users\sqlpythonadmin\Source\Repos\caffe2\build\caffe2/proto/caffe2.pb.h(12): fatal error C1189: #error:  This file
was generated by a newer version of protoc which is [C:\Users\sqlpythonadmin\Source\Repos\caffe2\build\caffe2\proto\Ca
ffe2_PROTO.vcxproj]
C:\Users\sqlpythonadmin\Source\Repos\caffe2\build\caffe2/proto/caffe2_legacy.pb.h(12): fatal error C1189: #error:  Th
is file was generated by a newer version of protoc which is [C:\Users\sqlpythonadmin\Source\Repos\caffe2\build\caffe2\p
roto\Caffe2_PROTO.vcxproj]
C:\Users\sqlpythonadmin\Source\Repos\caffe2\build\caffe2/proto/hsm.pb.h(12): fatal error C1189: #error:  This file wa
s generated by a newer version of protoc which is [C:\Users\sqlpythonadmin\Source\Repos\caffe2\build\caffe2\proto\Caffe
2_PROTO.vcxproj]
C:\Users\sqlpythonadmin\Source\Repos\caffe2\build\caffe2/proto/metanet.pb.h(12): fatal error C1189: #error:  This fil
e was generated by a newer version of protoc which is [C:\Users\sqlpythonadmin\Source\Repos\caffe2\build\caffe2\proto\C
affe2_PROTO.vcxproj]
C:\Users\sqlpythonadmin\Source\Repos\caffe2\build\caffe2/proto/predictor_consts.pb.h(12): fatal error C1189: #error:
This file was generated by a newer version of protoc which is [C:\Users\sqlpythonadmin\Source\Repos\caffe2\build\caffe
2\proto\Caffe2_PROTO.vcxproj]
"C:\Users\sqlpythonadmin\Source\Repos\caffe2\build\ALL_BUILD.vcxproj" (default target) (1) ->
"C:\Users\sqlpythonadmin\Source\Repos\caffe2\build\caffe2\Caffe2_CPU.vcxproj" (default target) (3) ->
"C:\Users\sqlpythonadmin\Source\Repos\caffe2\build\caffe\proto\Caffe_PROTO.vcxproj" (default target) (5) ->
C:\Users\sqlpythonadmin\Source\Repos\caffe2\build\caffe/proto/caffe.pb.h(12): fatal error C1189: #error:  This file w
as generated by a newer version of protoc which is [C:\Users\sqlpythonadmin\Source\Repos\caffe2\build\caffe\proto\Caffe
_PROTO.vcxproj]
6 Warning(s)
6 Error(s)

How could I resolve these errors?
To give some context, initially I installed protobuf using command:
conda install -c conda-forge protobuf=3.2.0
but when running build script, it reports a CMake Error: The source directory "C:/Users/sqlpythonadmin/Source/Repos/caffe2/third_party/protobuf/cmake" does not exist. Hence end up build protobuf locally using .sln in Visual Studio 2017

Do you have ran
git clone --recursive https://github.com/caffe2/caffe2.git ?
And check out your C:/Users/sqlpythonadmin/Source/Repos/caffe2/third_party path, where protobuf source code exists.

yes, I did, by using Git Plugin in Visual Studio with "recursive clone submodules" checked.
Is there a way to remove all existing caffe2 stuff and restart the process again? Would remove C:/Users/sqlpythonadmin/Source/Repos/caffe2 folder be enough?

After remove caffe2 folder, and another folder where protobuf was installed using conda install, rerun build_windows.bat, the issue with protobuf seems gone. But came another issue:
C:\Users\sqlpythonadmin\Source\Repos\caffe2\python\pybind_state.cc(194): error C3861: 'PyString_AsString': identifier
not found [C:\Users\sqlpythonadmin\Source\caffe2\build\caffe2\caffe2_pybind11_state.vcxproj]
C:\Users\sqlpythonadmin\Source\Repos\caffe2\python\pybind_state.cc(196): error C3861: 'PyString_AsString': identifier
not found [C:\Users\sqlpythonadmin\Source\caffe2\build\caffe2\caffe2_pybind11_state.vcxproj]
C:\Users\sqlpythonadmin\Source\Repos\caffe2\python\pybind_state.cc(314): error C3861: 'PyString_Check': identifier not
found [C:\Users\sqlpythonadmin\Source\caffe2\build\caffe2\caffe2_pybind11_state.vcxproj]
C:\Users\sqlpythonadmin\Source\Repos\caffe2\python\pybind_state.cc(819): error C3861: 'PyString_Check': identifier not
found [C:\Users\sqlpythonadmin\Source\caffe2\build\caffe2\caffe2_pybind11_state.vcxproj]
pybind_state_mkl.cc
Generating Code...
Done Building Project "C:\Users\sqlpythonadmin\Source\caffe2\build\caffe2\caffe2_pybind11_state.vcxproj" (default targe
ts) -- FAILED.
A quick search indicates "PyString_AsString" is defined in Python2, but I have installed Python3.5.2. Does it mean Caffe2 only works with Python2? Thanks.

Yes, you get it.
Caffe2 doesn't support Python3 yet. You could use Anaconda2 instead.

Thank you ezineo! I managed to replace some deprecated Python2 methods with Python3 ones. and the caffe2 build pass. But when trying to import Caffe2 in Python:
from caffe2.python import core, workspace
from caffe2.proto import caffe2_pb2
it reported an error "ImportError: No module named 'caffe2'". Some discussion mentioned about pycaffe, but I was not able to find pycaffe in the build. Did I miss installing something?

Could you recursively list the files under the build folder, and especially where all the .so files are located?

There is no .so files under \build.
Attaching the output
Caffe2 build folder files-recursive listing.txt

Search results showed that even Caffe2.exe was not existing. So the "Build succeeded" message must be a false positive one.
Attaching the build output message. Could you help figure out what is missing? Is it due to I am using Python 3?
build_windows_bat_outpu-fixedProtobuft_fixedPyString_AsString.txt
Thanks!

Ah yeah, right now C2 does not support python3 yet, stay tuned - that is coming in the near future. For now switching to python 2.7 might be the easiest option.

Thank you Yangqing for the confirmation. I actually tried to install Caffe2 on another VM (windows server 2016 with Python2.7 (Anaconda2), VS2017Community). But it was not able to build caffe2.exe either, with CMakeError like:

C:\Users\pythonadmin\Source\Repos\caffe2\build\CMakeFiles\CMakeTmp\CheckIncludeFile.c(1): fatal error C1083: Cannot open include file: 'pthread.h': No such file or directory [C:\Users\pythonadmin\Source\Repos\caffe2\build\CMakeFiles\CMakeTmp\cmTC_71456.vcxproj]
C:\Users\pythonadmin\Source\Repos\caffe2\build\CMakeFiles\CMakeTmp\Debug\cmTC_01d7c.exe : fatal error LNK1120: 1 unresolved externals [C:\Users\pythonadmin\Source\Repos\caffe2\build\CMakeFiles\CMakeTmp\cmTC_01d7c.vcxproj]
C:\Users\pythonadmin\Source\Repos\caffe2\build\CMakeFiles\CMakeTmp\src.cxx(4): error C3861: '__builtin_cpu_supports': identifier not found [C:\Users\pythonadmin\Source\Repos\caffe2\build\CMakeFiles\CMakeTmp\cmTC_a31f6.vcxproj]
C:\Users\pythonadmin\Source\Repos\caffe2\build\CMakeFiles\CMakeTmp\src.cxx(1): fatal error C1083: Cannot open include file: 'glog/stl_logging.h': No such file or directory [C:\Users\pythonadmin\Source\Repos\caffe2\build\CMakeFiles\CMakeTmp\cmTC_22aa6.vcxproj]

Did you experience similar errors while testing on Windows? Any suggestions on how to resolve it?

Hmm, these all seem to be normal cmake check errors, other than the last line which seems to suggest that glog/stl_logging.h cannot be found. Are you building with glog on Windows? That is a path we have not verified before, so I wonder if you pass in -DUSE_GLOG=OFF things can pass.

Thanks for your suggestion Yangqing. Finally figured out, I missed an environment variable PYTHONPATH, after adding it, caffe2 works.

Can you please specify which "PYTHONPATH" you are refering. Is it Anaconda PythonPath or Caffe Python folder path

I have Ananconda Python running from $USER\AppData\Local\Continuum\Anaconda2\python.exe ( on Windows 10 machine) so that is my PATH and PYTHONPATH sys env variable
I have also copied "caffe2_pybind11_state.pyd" and "caffe2_pybind11_state_gpu.pyd" copied from "caffe2\build\caffe2\python\Release" folder to "$USER\AppData\Local\Continuum\Anaconda2\DLLs"...
I've restarted the machine, but when I try to import caffe2 module
">>from caffe2.python import core".....it still throws the error "No module named caffe2.python"

Can you please specify which PYTHONPATH have you added.... I have anaconda installed in "$USER\AppData\Local\Continuum\Anaconda2\python.exe" which is my PYTHONPATH in Windows 10 Desktop.
Also I can confirm that I have copied "caffe2_pybind11_state*.pyd" files to "$USER\AppData\Local\Continuum\Anaconda2\DLLs"
But no luck when I try to import caffe2  ">>from caffe2.python import core"
"ImportError: No Module named caffe2.python"

Add caffe2/build path to your PYTHONPATH. It was mentioned in the install tutorial for Ubuntu. Perhaps worth mentioning in the windows version too.

Thanks....it works for me now

I also have this question, when I try to import caffe2 ">>from caffe2.python import core"
"ImportError: No Module named caffe2.python",I have add caffe2/build PYTHONPATH in windows environment,but it didn't work,how can i do?


What is the value of N?

I can't seem to be able to find the value of N := number of points per frame.

I see there are 17 frames for training and testing
You use 512 randomly sampled points from the P_t point cloud to backprop

I would like to know what you're comparing the 10K point cloud with when you compute the Chamfer Distance at test time.
How many points go in, how many come out?
Thanks for any help.

Hi LoreBerli,
Sorry for late reply as I'm having many deadlines.
The value of N is 300 points which is same as other methods setting. You can find it here.
I don't get the point of "10K point cloud", could you elaborate it?
As mentioned in the paper, we stated that "For calculating the losses during training, we randomly sampled a fixed number of 512 points in 3D space and time interval for reconstruction loss, and uniformly sampled trajectories of 100 points for flow estimation loss. More details can be found in our supplied code."
Hope it helps you. Please feel free to ask questions and I will try to answer it asap.

Hi and thank you for the response.
I was referring to this line but i probably misunderstood

This issue is now closed as it has been resolved; however, you are welcome to reopen it if you have any further inquiries.


[Story] Push OC images to GHCR

What projects is this story for?
OpenChallenges
As a user, I want
As a DevOps, I want the OC images to be pushed to GHCR as part of the CI/CD workflow.
Description
See #1695 for additional context
UPDATE: This ticket initially aimed to push images to Docker Hub. After evaluation, GHCR seems to be a better fit in terms of least privileges access.
Acceptance criteria

The OC images are pushed to GHCR as part of the CI/CD workflow

Tasks

[ ] Do a quick research spike on how to assign a version number to the OC images
[ ] Update the CI/CD workflow to push the images to Sage Docker Hub account

Anything else?
No response
Have you linked this story to a GitHub Project?

[X] I have linked this story to a GitHub Project and set its metadata.

There are a few images that have be exclude because of the max storage space available to the GH runner. The remaining images will be built in a subsequent PR.


Contribution to "Remote code injection in Log4j"

Updates

CVSS
Description
References
Severity

Hi @HendarMoko! Thank you so much for being one of the first folks to submit a community contribution! We value you making our database better.
I'd love to learn more about your use case.
Would be interested in chatting with me for 30 minutes in the next month via Zoom? If so, please follow the link below to schedule a time that works best for us both. In recognition of your time, we’ll send you a $60 gift card/cash card/credit for the GitHub Swag store.
https://calendly.com/security-advisories-ux-calls/25min?back=1&month=2022-03


BUG REPORT: Typographical error for dot script for MacOS, extra comma char instead of space in dot script

Apparently, there's an extra comma character , added into the command issued via the dot command within MacOS. The error reads:
"dot -Tpng,/var/folders/to/temporary/text/file" failed, Error: spawn dot ENOENT

Instead of [space], a comma , is inserted between the option -Tpng and the path-to-tmp-file causing the error.
I tried to issue the appropriate command and was able to produce the appropriate file. A  copy-paste of the same command above results to an error with -Tpng,/var/folders... as an error flag options. The comma character seems to be considered by the dot as included in the whole options.
For reference, here are my technical details.

dot version

dot - graphviz version 10.0.1 (20240210.2158)

Obsidian version

Version 1.5.8 (Installer 1.5.3)

MacOS

Macbook Air 23.3.0 Darwin Kernel Version 23.3.0: Wed Dec 20 21:28:58 PST 2023;
root:xnu-10002.81.5~7/RELEASE_X86_64 x86_64

There should be a way to edit the Graphviz plugin to change the comma into a space. I believe it will workout fine.

Did you find a fix ? I have the same issue on Linux (PopOS), and can't find where the comma is inserted in the js file...


Mistake in code example in Interactive.hs

Hi,
At the top of the Interactive.hs file there is a code example using mouse events, but the function onMouseDown used there only takes an action, while the actual function also needs a button type. A consequence of an API change, I suppose. This pull request should fix it.

Thanks!


[Block] - Floor Plan Links

This block will be authored by providing a table with two column.  The first row will always link to the
interactive floor plan.  The first column of the first row should provide the label of the button, the second
column will be the link to the interactive floor plan.
Subsequent rows will be rendered as buttons, that will cause the action to open in a new window.  For
example, second row, first column has the text "Floor Plan Handout", the second row, second column has a
link to the pdf document like /documents/floorplans/Emerald_Plan%20Handout%202023%2010-01.pdf

Action Buttons resolved in - https://github.com/aemsites/hubblehomes-com/pull/119


Create a Bootstrap Headline

Not really sure what I am doing wrong.  I saw another post on this.  I closed off the H3 tag.  Any suggestions?

I can see that you have used, capitalizes h in the tags as in

 and our tests are looking for h3.
The former may not be a standard practice is perfectly valid code. Keeping in tune with freeCodeCamp philosophy we focus on teaching concepts and not best/practice in the regular challenges, hence this valid code should be allowed.
I think we should allow the tests to accept this, but this would mean a change to all of the challenges. I am okay to open this up for a fix, but will wait for @freeCodeCamp/moderators to have a view as well.

Stop
On Wed, Feb 15, 2017 at 10:16 AM mrugesh mohapatra<EMAIL_ADDRESS>wrote:

I can see that you have used, capitalizes h in the tags as in
and our tests are looking for h3.
The former may not be a standard practice is perfectly valid code. Keeping
in tune with freeCodeCamp philosophy we focus on teaching concepts and not
best/practice in the regular challenges, hence this valid code should be
allowed.
I think we should allow the tests to accept this, but this would mean a
change to all of the challenges. I am okay to open this up for a fix, but
will wait for @freeCodeCamp/moderators
https://github.com/orgs/freeCodeCamp/teams/moderators to have a view as
well.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/freeCodeCamp/freeCodeCamp/issues/13362#issuecomment-280037759,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AYjYuxLflZYrXTv5PvhbEk6SaaxvA3_Hks5rcxbggaJpZM4MB0OA
.

Okay that was simple.  Brand new to coding.  Thanks for the correction.

Hello @amandacsim !
Looks like you may have accidentally subscribed to all notifications for the freeCodeCamp repository. To stop receiving notifications please visit the
https://github.com/FreeCodeCamp/FreeCodeCamp/subscription
We are sorry for your inconvenience!


Automate visualization of results

Generate a quick overview of the results of CI for each tools and each design

Example: (it doesn't need to look like this): https://docs.google.com/spreadsheets/d/1QpC63sSstD-53h1ux2F3AhdR2M1DnBZSVzGGfWIOYQw/edit#gid=0
I suggest using Colab, because it's quick and can be commented on and presented, but feel free to suggest other options.

Colab examples: https://drive.google.com/drive/folders/1bYENID_88n9Xw2FQLQORz2IC59xiK3Y9?usp=sharing

Example data: dataframe.json.zip
@acomodi Is there a public link for the dataframe.json files generated by CI?

@HackerFoo After each CI run on master/PR an artifact is produced with the dataframe.json. An example is here: https://storage.cloud.google.com/fpga-tool-perf/artifacts/prod/foss-fpga-tools/fpga-tool-perf/continuous/47/20200617-104132/github/fpga-tool-perf/build/dataframe.json

@acomodi Is there a good way to programmatically get the latest link? I'm guessing it's https://.../47/${date}-${hash-or-sequential-id}/.../dataframe.json, but I'm not sure how to get hash-or-sequential-id.

@HackerFoo I think that is a question for @mithro as I am unsure on how the kokoro instance does upload the artifacts on GCS. If there was the possibility to have a latest link, it would be great.

Are the columns in the example sheet all the important metrics? Do the metrics you want to display vary between runs?

@TypingKoala those are a good start, but the design should be flexible enough to add more metrics if needed. Once we have a good overview of the most important metrics, we can create issues to track improvements (such as tracking trends over time.)

@HackerFoo I've created a proof-of-concept here that ingests from Hydra or GCS, cleans, normalizes, and outputs the information as a CSV that can be exported directly to Google Sheets. Is this along the lines of what you are looking for? Is there any color coding that would be helpful in the output?
https://colab.research.google.com/drive/1NXLYCYtY4YOslg0lbGryRfGdjKIeYZ1V?usp=sharing
https://docs.google.com/spreadsheets/d/1woQR-Ag2jQCDWpQE5ko89d5jdvkZswYSxb4DmHlBE5o/edit?usp=sharing

@TypingKoala Could you embed a table into the Colab instead of generating CSV? Like this.
Color coding might be nice, with the vendor toolchain (e.g. Vivado) as the baseline, red for worse, green for better.

@HackerFoo I've implemented those changes. Please take a look at the colab now. I've added an embedded table with styling to reflect the relative performance compared to the Vivado toolchain for every project.

Development is in progress in a separate repo. Once issue #10 is resolved in that repo, this issue can be closed.


[minor] name change for sparse-sparse case

I am not sure, whether I am correct. Because, even with out the change, your changeset is correct. Thanks.
BTW, I am trying to fix the udf in expressions[1444] from last 24 hrs. But, still trying to figure a way out. Thanks.
cc @mboehm7

LGTM - thanks for catching this.

Also, for my understanding why are we assuming the b have likely less zeros.

Can you give an example matrix, I will try to understand this operation. So, that I will try to use this as base for the coming operations.  cc @mboehm7 .

well, all combinations of sparse and dense are relevant but its more common to have sparse (filters), at least in the applications I've seen so far.

This operation is actually nothing else than (X > 0) * dout but Niketan added an operator to avoid the allocation and materialization of the intermediate. Once codegen is enabled by default (and supported by the GPU backend), we could actually remove this custom fused operators. If you like, you can start with SYSTEMML-2110 that aims to support relu_backward in codegen (in row and cell templates, simply compiled to > and * operations at CPlan level).


Pyspark script does not terminate with SynapseML[BUG]

SynapseML version
"com.microsoft.azure:synapseml_2.12:0.9.5-13-d1b51517-SNAPSHOT",
System information

Language version
python 3.8, scala 2.12
Spark Version (e.g. 3.2.3):
Spark Platform (e.g. Dataproc):

Describe the problem
The Spark script completes all the operation but the script is not terminated.
Even if I call spark.stop() the context is not stopped and the job does not terminate
Code to reproduce issue
It's a normal fit operation with SynapseML, can't reporoduce the data anyway.
I have 100 M rows with ~30 features
Other info / logs
No response
What component(s) does this bug affect?

[ ] area/cognitive: Cognitive project
[ ] area/core: Core project
[ ] area/deep-learning: DeepLearning project
[ ] area/lightgbm: Lightgbm project
[ ] area/opencv: Opencv project
[ ] area/vw: VW project
[ ] area/website: Website
[ ] area/build: Project build system
[ ] area/notebooks: Samples under notebooks folder
[ ] area/docker: Docker usage
[ ] area/models: models related issue

What language(s) does this bug affect?

[ ] language/scala: Scala source code
[ ] language/python: Pyspark APIs
[ ] language/r: R APIs
[ ] language/csharp: .NET APIs
[ ] language/new: Proposals for new client languages

What integration(s) does this bug affect?

[ ] integrations/synapse: Azure Synapse integrations
[ ] integrations/azureml: Azure ML integrations
[ ] integrations/databricks: Databricks integrations

Thanks for reaching out @acastelli1, could you share the application and a sample dataset where it hangs. Try fitting on a subset of data first and seeing where in the scale up procedure breaks it

I'd also recommended a newer version.  com.microsoft.azure:synapseml_2.12:0.10.2


WIP: MAISTRA-2309 create CRD for FederationStatus

Signed-off-by: rcernich<EMAIL_ADDRESS>

Hey @luksa, if you have time, can you review the new FederationStatus type in this PR?  This resource is intended to be created by istiod, providing feedback related to mesh federation for each istiod pod (e.g. meshes it's connected to, services exported/imported, etc.).  The lifecycle of the resource is tied to the lifecycle of the istiod pod, as there is no centralized controller for federation, I thought it was important to provide details for each istiod.  Other than the list of inbound connections from other meshes, if the other details differ across the pods, it could imply issues with federation, which could lead to inconsistencies in the mesh, depending on which sidecars are getting registry info from which istiod.


Switch to Next.js

Next.js is a react framework for production.
It has some intresting features listed down below:

SEO Friendly
Image Optimization
Server side rendering
File system routing
And many more.

Head over to https://nextjs.org/ for more.

I looked at next.js and decided not to use it because it needs pre-processing to generate static files. It's not well suited for fully serverless blogs like Moogle. Happy to be corrected if you know something about next.js that I don't.

Not exactly. You don't need to generate static files. NextJs supports dynamic rendering. Have a look at this https://nextjs.org/docs/basic-features/data-fetching.
For example if you want that, data should be fetched from server on every request, next.js has getServerSideProps.
If you want to revalidate after a certain time next.js has getStaticProps.
Next.js only generates static files for those pages in which no dynamic data is fetched from server or database. For example Home page, About page etc. Even you can use getStaticProps on those pages so that it'll revalidate after certain time as data might not be going to change/update very frequently.
BTW it's your choice 🙂

In case you have any further doubt you can connect me on telegram or via email.


Save DateTimes in ISO8601

Never save dates in a "culture specific" format. Always use ISO8601 as a culture invariant. You deserailize the date from that format and THEN output it specific to the user's machine in the view.

Fixed in #29


hi

hi, do you have discord?

Hi,
Yes I do. Is there anything specific you need to discuss?
On Sun, Sep 29, 2024, 03:32 nikoblessd @.***> wrote:

hi, do you have discord?
—
Reply to this email directly, view it on GitHub
https://github.com/xhsu/metamod-AmxModules/issues/1, or unsubscribe
https://github.com/notifications/unsubscribe-auth/AH55XVSP43U3AQOQRNF7HIDZY3R2XAVCNFSM6AAAAABPAZRFCWVHI2DSMVQWIX3LMV43ASLTON2WKOZSGU2TINBRHA4TKOA
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>

I am afraid if it can't be discussed publicly, I have nothing to say to a
unknown person on internet.
Unless, of course, it's a blackmail or relatating to my IRL identity.😆
On Sun, Sep 29, 2024, 09:07 nikoblessd @.***> wrote:

yes, I wanted to ask you a question privately.
—
Reply to this email directly, view it on GitHub
https://github.com/xhsu/metamod-AmxModules/issues/1#issuecomment-2381018852,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AH55XVUITFMRZWD4EAOQIODZY4ZCPAVCNFSM6AAAAABPAZRFCWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGOBRGAYTQOBVGI
.
You are receiving this because you commented.Message ID:
@.***>

It's pretty cool and my pleasure to receive such an invitation, but I am no
professional programmer but an enthusiastic for CSCZ/CS1.6 (not even CSGO!)
You sure about that?
On Sun, Sep 29, 2024, 09:28 nikoblessd @.***> wrote:

Well, I just wanted to ask you for a job, obviously paid. I don't know if
it's possible.
—
Reply to this email directly, view it on GitHub
https://github.com/xhsu/metamod-AmxModules/issues/1#issuecomment-2381022606,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AH55XVTOZOJPK2WO4NB3KLTZY43SBAVCNFSM6AAAAABPAZRFCWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGOBRGAZDENRQGY
.
You are receiving this because you commented.Message ID:
@.***>

Alright, should you wish to discuss it privately then DM me on discord:
anthocyanidin
On Sun, Sep 29, 2024, 09:43 nikoblessd @.***> wrote:

Sure, it's about an amxx module, I don't think it's complicated for you.
—
Reply to this email directly, view it on GitHub
https://github.com/xhsu/metamod-AmxModules/issues/1#issuecomment-2381025470,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AH55XVSOYLFOJMAQQGLHC5DZY45JVAVCNFSM6AAAAABPAZRFCWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGOBRGAZDKNBXGA
.
You are receiving this because you commented.Message ID:
@.***>

#fd9a158
Module published for free.


Init not working on a rest-server on UnRAID

Output of restic version
restic 0.14.0 compiled with go1.19 on linux/amd64
How did you run restic exactly?
root@EDITH:/mnt/user/appdata/autorestic# DEBUG_FILES=* restic -r rest:http://<IP_ADDRESS>:8000/mnt/user/storage init
debug enabled
restic/main.go:95       main.main       1       main []string{"restic", "-r", "rest:http://<IP_ADDRESS>:8000/mnt/user/storage", "init"}
restic/main.go:96       main.main       1       restic 0.14.0 compiled with go1.19 on linux/amd64
enter password for new repository:
enter password again:
restic/global.go:768    main.create     1       parsing location rest:http://<IP_ADDRESS>:8000/mnt/user/storage
restic/global.go:673    main.parseConfig        1       opening rest repository at rest.Config{URL:(*url.URL)(0xc00011c120), Connections:0x5}
debug/round_tripper.go:94       debug.loggingRoundTripper.RoundTrip     1       ------------  HTTP REQUEST -----------
HEAD /mnt/user/storage/config HTTP/1.1
Host: <IP_ADDRESS>:8000
User-Agent: Go-http-client/1.1
Accept: application/vnd.x.restic.rest.v2

debug/round_tripper.go:111      debug.loggingRoundTripper.RoundTrip     1       ------------  HTTP RESPONSE ----------
HTTP/1.1 404 Not Found
Content-Length: 10
Content-Type: text/plain; charset=utf-8
Date: Wed, 21 Dec 2022 05:19:44 GMT
X-Content-Type-Options: nosniff

debug/round_tripper.go:94       debug.loggingRoundTripper.RoundTrip     1       ------------  HTTP REQUEST -----------
POST /mnt/user/storage/?create=true HTTP/1.1
Host: <IP_ADDRESS>:8000
User-Agent: Go-http-client/1.1
Content-Length: 0
Content-Type: binary/octet-stream
Accept-Encoding: gzip

debug/round_tripper.go:111      debug.loggingRoundTripper.RoundTrip     1       ------------  HTTP RESPONSE ----------
HTTP/1.1 404 Not Found
Content-Length: 10
Content-Type: text/plain; charset=utf-8
Date: Wed, 21 Dec 2022 05:19:44 GMT
X-Content-Type-Options: nosniff

Fatal: create repository at rest:http://<IP_ADDRESS>:8000/mnt/user/storage/ failed: Fatal: server response unexpected: 404 Not Found (404)

What backend/server/service did you use to store the repository?
rest-server
Expected behavior
init the repo
Actual behavior
the issue described above
Steps to reproduce the behavior
using unraid the folder is a SMB Share, but i'm unsure if this is actually a share as i'm not exporting it in unraid.
Do you have any idea what may have caused this?
no
Do you have an idea how to solve the issue?
no

NVM! I made a mistake on this. I was calling the wrong directory.


pointer: Only write the encoded pointer information to Stdout

This allows to create a pointer file by redirecting Stdout like
$ git lfs pointer --file=path/to/file > pointer-to-file

Before this change, "pointer-to-file" would also contain the line saying
"Git LFS pointer for path/to/file"

which makes the pointer file invalid.

Please can you agree to the Contributor License Agreement since we can't merge this until you do (I think there's a link to do it if you click Details by the error above).
Apart from that this looks good to me but I'd like @technoweenie to OK it as well before merging.

@sinbad Unfortunately, until I saw the bot check I wasn't aware a CLA is required. I need to get the CLA reviewed by our legal department which might take some some.

On a related note, I just had a discussion in upstream Git about what kind of information should go to Stdout vs. Stderr, and here are some good answers:

"Anything that is not the primary output of the program should go to stdout.": http://article.gmane.org/gmane.comp.version-control.git/289512
"I think the stance of Git is to write only machine readable stuff to stdout [...]": http://article.gmane.org/gmane.comp.version-control.git/289514

Yep, I think that's a pretty good guide.

Hey @sschuberth, thanks for submitting this. I'm certainly not a linux expert, and will usually defer to whatever Git does in cases like this. I think those guidelines make sense for git plumbing commands, but not git porcelain commands.
$ git status 2>/dev/null
On branch lfs-repo-usage
Your branch is based on 'origin/lfs-repo-usage', but the upstream is gone.
  (use "git branch --unset-upstream" to fixup)
nothing to commit, working directory clean

The default git status output isn't designed for machine readable content. So, my interpretation is that those guidelines are only for porcelain commands.
It looks like this PR declares git lfs pointer as a plumbing command, while sending some user output to STDERR so it's still readable to humans. Is that common with linux commands? Are there weird edge cases with commands returning STDERR output and a 0 exit code? Based on your profile, I'm assuming you know what you're talking about. I want to make sure that I understand this correctly ;)

I wouldn't say I'm a Linux expert either (I was mostly working on Git for Windows), but the discussion I was referring to is about git submodule, which is a porcelain command. Also, the referred commit message by @peff says

Putting messages like "Cloning into.." and "done" on stdout is un-Unix and uselessly clutters the stdout channel.

Note how he says "un-Unix", not "un-git-ish" or the like.
Your counter-example of git status is a good one, but on the other hand @gitster says (also in my linked thread):

We may not have been very strict in code reviews to enfore it, and
especially on the fringes of the system it may be easy to find
violators, though.

Finally, even if this PR would declare git lfs pointer as a plumbing command I'd argue that's a correct thing to do as git-lfs itself lists git lfs pointer under "Low level commands" in its command line help.

Nice counter point with git submodule. SOLD :+1:
Any idea what it'll take to get the CLA approved? Seems silly to hold up a trivial patch like this. I can totally ninja-merge this, or recreate the changes personally, but I'd rather not so you can get the sweet credit, and potentially contribute in the future ;)
If you can't, or don't feel like going through the hassle, that's totally OK too. I'll just recreate the patch. In the future, you can just open issues for us.

Yeah, I think you can get into pretty vague, opinionated arguments on stdout vs stderr. Basically, we should strive for usefulness. So if something is the "main" output of a command (as it is with git status), it should go to stdout, regardless of whether it is machine readable or not.  If it is extra chattiness that would otherwise make the stdout output harder to parse or reuse, then it should go to stderr (so I think @sschuberth's example shows that).
Something like clone is in a weird no-man's land, because it doesn't really produce a "main" output in the first place. Its function is to do something, and all output is basically human-readable chat.
I don't think we have to care about plumbing versus porcelain when making this distinction.

Are there weird edge cases with commands returning STDERR output and a 0 exit code?

tcl is notorious for treating anything on stderr like an error. IMHO that is just insane.

Any idea what it'll take to get the CLA approved?

@technoweenie I just need to push our legal department a bit. Give me a few more days. My patch is not super-urgent, and I'd like to get this sorted out anyway.

tcl is notorious for treating anything on stderr like an error. IMHO that is just insane.

@peff Just FYI, PowerShell does the same. But I don't think it's insane per se. It's called standard error after all.

Honestly, it doesn't sound insane to me either. That's why I wanted to clarify. Should we file a PR to change STDERR to STDUSER or something? :trollface:
@sschuberth no worries, I'll wait patiently :)

This is such a common sticking point...in SourceTree for quite a while we coloured stderr output red because it was usually best way to highlight errors in large output based on observed Git behaviour, but it could be confusing when people had verbose mode on but the result code was successful. Our eventual solution was to display everything in standard text while the command runs but remembering which was stdout & stderr & applying the highlighting only when the result code was non-zero. Occasionally we highlight more than required in that case but most of the time in fatal cases it does pick out just the bad stuff. If only there were 3 defined output streams... :)

@technoweenie I was able to accept the CLA now :-)

Thanks! I should've asked about tests. But since I didn't, you get a free ride this time.


[CCTRI-2252] - Daily requests for Event API

Split 7-day default request to few daily requests for Event API. Searching for the last 100 events.

Could you please link this issue to pull request? Instructions


Avoid infinite recursion when renaming #3326

See the ticket for more info.
@Kartones please review

Frontend tests were OK :+1: (details)

:+1:  Apart from that exception_to_raise only used for notification and not actual raising

Frontend tests were OK :+1: (details)

I tested 2e1d70e but in the end I prefer to keep the CartoDB::notify_exception so that it appends the user info to the trace. In case of weirdness it can greatly help us reconstruct what happened.

Frontend tests were OK :+1: (details)