Govee to MQTT Bridge issue with Home Assistant

Govee Device SKU
H619A & H6097
Govee2MQTT Version
2024.07.13-82ddc6e9
Describe the issue
I am trying to install Govee to MQTT Bridge to Home Assistant but it gives me error. I did everything what ever its written in the installation page. Here is my logs:
Startup Diagnostics
no
Additional Logs
Error: Cannot bind to UDP Port 4002, which is required for the Govee LAN API to function. Most likely cause is that you are running another integration (perhaps `Govee LAN Control`, or `homebridge-govee`) that is already bound to that port. Both cannot run on the same machine at the same time. Consider disabling `Govee LAN Control` or setting `lanDisable` in `homebridge-govee`.

```
GOVEE_API_KEY=REDACTED
GOVEE_MQTT_HOST=core-mosquitto
GOVEE_TEMPERATURE_SCALE=C
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-11-11T11:11:30 INFO  govee::commands::serve] Starting service. version 2024.07.13-82ddc6e9
[2024-11-11T11:11:30 INFO  govee::commands::serve] Querying platform API for device list
[2024-11-11T11:11:30 INFO  govee::commands::serve] Querying undocumented API for device + room list
[2024-11-11T11:11:30 INFO  govee::service::iot] Connected to IoT: CONNACK code 0: Connection Accepted.
[2024-11-11T11:11:30 INFO  govee::commands::serve] Starting LAN discovery
[2024-11-11T11:11:30 INFO  govee::service::iot] IoT (re)connected with status CONNACK code 0: Connection Accepted.
Error: Cannot bind to UDP Port 4002, which is required for the Govee LAN API to function. Most likely cause is that you are running another integration (perhaps `Govee LAN Control`, or `homebridge-govee`) that is already bound to that port. Both cannot run on the same machine at the same time. Consider disabling `Govee LAN Control` or setting `lanDisable` in `homebridge-govee`.
Caused by:
Address in use (os error 98)
Stack backtrace:
0: std::backtrace::Backtrace::create
1: govee::lan_api::Client::new::{{closure}}
2: govee::commands::serve::ServeCommand::run::{{closure}}
3: govee::Args::run::{{closure}}
4: tokio::runtime::park::CachedParkThread::block_on
5: tokio::runtime::context::runtime::enter_runtime
6: tokio::runtime::runtime::Runtime::block_on
7: govee::main
8: std::sys_common::backtrace::__rust_begin_short_backtrace
9: std::rt::lang_start::{{closure}}
10: std::rt::lang_start_internal
11: main
s6-rc: info: service legacy-services: stopping
s6-rc: info: service legacy-services successfully stopped
s6-rc: info: service legacy-cont-init: stopping
s6-rc: info: service legacy-cont-init successfully stopped
s6-rc: info: service fix-attrs: stopping
s6-rc: info: service fix-attrs successfully stopped
s6-rc: info: service s6rc-oneshot-runner: stopping
s6-rc: info: service s6rc-oneshot-runner successfully stopped
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_TEMPERATURE_SCALE=C
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-11-11T11:16:25 INFO  govee::commands::serve] Starting service. version 2024.07.13-82ddc6e9
[2024-11-11T11:16:25 INFO  govee::commands::serve] Querying platform API for device list
[2024-11-11T11:16:25 INFO  govee::commands::serve] Querying undocumented API for device + room list
[2024-11-11T11:16:26 INFO  govee::service::iot] Connected to IoT: CONNACK code 0: Connection Accepted.
[2024-11-11T11:16:26 INFO  govee::commands::serve] Starting LAN discovery
[2024-11-11T11:16:26 INFO  govee::service::iot] IoT (re)connected with status CONNACK code 0: Connection Accepted.
Error: Cannot bind to UDP Port 4002, which is required for the Govee LAN API to function. Most likely cause is that you are running another integration (perhaps Govee LAN Control, or homebridge-govee) that is already bound to that port. Both cannot run on the same machine at the same time. Consider disabling Govee LAN Control or setting lanDisable in homebridge-govee.
Caused by:
Address in use (os error 98)
Stack backtrace:
0: std::backtrace::Backtrace::create
1: govee::lan_api::Client::new::{{closure}}
2: govee::commands::serve::ServeCommand::run::{{closure}}
3: govee::Args::run::{{closure}}
4: tokio::runtime::park::CachedParkThread::block_on
5: tokio::runtime::context::runtime::enter_runtime
6: tokio::runtime::runtime::Runtime::block_on
7: govee::main
8: std::sys_common::backtrace::__rust_begin_short_backtrace
9: std::rt::lang_start::{{closure}}
10: std::rt::lang_start_internal
11: main
s6-rc: info: service legacy-services: stopping
s6-rc: info: service legacy-services successfully stopped
s6-rc: info: service legacy-cont-init: stopping
s6-rc: info: service legacy-cont-init successfully stopped
s6-rc: info: service fix-attrs: stopping
s6-rc: info: service fix-attrs successfully stopped
s6-rc: info: service s6rc-oneshot-runner: stopping
s6-rc: info: service s6rc-oneshot-runner successfully stopped
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_TEMPERATURE_SCALE=C
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-11-11T11:17:18 INFO  govee::commands::serve] Starting service. version 2024.07.13-82ddc6e9
[2024-11-11T11:17:18 INFO  govee::commands::serve] Querying platform API for device list
[2024-11-11T11:17:18 INFO  govee::commands::serve] Querying undocumented API for device + room list
[2024-11-11T11:17:18 INFO  govee::service::iot] Connected to IoT: CONNACK code 0: Connection Accepted.
[2024-11-11T11:17:18 INFO  govee::commands::serve] Starting LAN discovery
[2024-11-11T11:17:18 INFO  govee::service::iot] IoT (re)connected with status CONNACK code 0: Connection Accepted.
Error: Cannot bind to UDP Port 4002, which is required for the Govee LAN API to function. Most likely cause is that you are running another integration (perhaps Govee LAN Control, or homebridge-govee) that is already bound to that port. Both cannot run on the same machine at the same time. Consider disabling Govee LAN Control or setting lanDisable in homebridge-govee.
Caused by:
Address in use (os error 98)
Stack backtrace:
0: std::backtrace::Backtrace::create
1: govee::lan_api::Client::new::{{closure}}
2: govee::commands::serve::ServeCommand::run::{{closure}}
3: govee::Args::run::{{closure}}
4: tokio::runtime::park::CachedParkThread::block_on
5: tokio::runtime::context::runtime::enter_runtime
6: tokio::runtime::runtime::Runtime::block_on
7: govee::main
8: std::sys_common::backtrace::__rust_begin_short_backtrace
9: std::rt::lang_start::{{closure}}
10: std::rt::lang_start_internal
11: main
s6-rc: info: service legacy-services: stopping
s6-rc: info: service legacy-services successfully stopped
s6-rc: info: service legacy-cont-init: stopping
s6-rc: info: service legacy-cont-init successfully stopped
s6-rc: info: service fix-attrs: stopping
s6-rc: info: service fix-attrs successfully stopped
s6-rc: info: service s6rc-oneshot-runner: stopping
s6-rc: info: service s6rc-oneshot-runner successfully stopped
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=<IP_ADDRESS>
GOVEE_TEMPERATURE_SCALE=C
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-11-11T11:25:46 INFO  govee::commands::serve] Starting service. version 2024.07.13-82ddc6e9
[2024-11-11T11:25:46 INFO  govee::commands::serve] Querying platform API for device list
[2024-11-11T11:25:46 INFO  govee::commands::serve] Querying undocumented API for device + room list
[2024-11-11T11:25:47 INFO  govee::service::iot] Connected to IoT: CONNACK code 0: Connection Accepted.
[2024-11-11T11:25:47 INFO  govee::service::iot] IoT (re)connected with status CONNACK code 0: Connection Accepted.
[2024-11-11T11:25:47 INFO  govee::commands::serve] Starting LAN discovery
Error: Cannot bind to UDP Port 4002, which is required for the Govee LAN API to function. Most likely cause is that you are running another integration (perhaps Govee LAN Control, or homebridge-govee) that is already bound to that port. Both cannot run on the same machine at the same time. Consider disabling Govee LAN Control or setting lanDisable in homebridge-govee.
Caused by:
Address in use (os error 98)
Stack backtrace:
0: std::backtrace::Backtrace::create
1: govee::lan_api::Client::new::{{closure}}
2: govee::commands::serve::ServeCommand::run::{{closure}}
3: govee::Args::run::{{closure}}
4: tokio::runtime::park::CachedParkThread::block_on
5: tokio::runtime::context::runtime::enter_runtime
6: tokio::runtime::runtime::Runtime::block_on
7: govee::main
8: std::sys_common::backtrace::__rust_begin_short_backtrace
9: std::rt::lang_start::{{closure}}
10: std::rt::lang_start_internal
11: main
s6-rc: info: service legacy-services: stopping
s6-rc: info: service legacy-services successfully stopped
s6-rc: info: service legacy-cont-init: stopping
s6-rc: info: service legacy-cont-init successfully stopped
s6-rc: info: service fix-attrs: stopping
s6-rc: info: service fix-attrs successfully stopped
s6-rc: info: service s6rc-oneshot-runner: stopping
s6-rc: info: service s6rc-oneshot-runner successfully stopped
Home Assistant Logs
2024-11-11 10:17:40.837 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration vesync 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
2024-11-11 10:17:40.841 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration pirateweather 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
2024-11-11 10:17:40.843 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration portainer 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
2024-11-11 10:17:40.846 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration meross_cloud 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
2024-11-11 10:17:40.849 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration kia_uvo 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
2024-11-11 10:17:40.852 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration hacs 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
2024-11-11 10:17:40.854 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration watchman 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
2024-11-11 10:17:40.857 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration ui_lovelace_minimalist 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
2024-11-11 10:17:40.860 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration extended_openai_conversation 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
2024-11-11 10:17:40.863 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration govee_lan 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
2024-11-11 10:17:40.867 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration tcl_tv_remote 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
2024-11-11 10:17:40.870 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration icloud3 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
2024-11-11 10:17:40.875 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration browser_mod 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
2024-11-11 10:18:03.746 WARNING (MainThread) [custom_components.meross_cloud]
Meross Cloud Custom component
Developed by Alberto Geniola
Low level library version: <IP_ADDRESS>
This custom component is under development and not yet ready for production use.
In case of errors/misbehave, please report it here:
https://github.com/albertogeniola/meross-homeassistant/issues
If you like this extension and you want to support it, please consider donating.
List of devices reported by HTTP API:

Buhar (mod150) - OnlineStatus.OFFLINE
===============================
2024-11-11 10:18:03.912 WARNING (MainThread) [homeassistant.helpers.frame] Detected that custom integration 'meross_cloud' calls async_forward_entry_setup for integration, meross_cloud with title: https://iot.meross.com and entry_id: 1485ba22f9fd869dcaf4fc1aa1d7699f, which is deprecated and will stop working in Home Assistant 2025.6, await async_forward_entry_setups instead at custom_components/meross_cloud/init.py, line 426: hass.async_create_task(, please create a bug report at https://github.com/albertogeniola/meross-homeassistant
2024-11-11 10:18:09.372 WARNING (MainThread) [homeassistant.setup] Setup of telegram_bot is taking over 10 seconds.
2024-11-11 10:18:19.836 WARNING (MainThread) [custom_components.vesync.common] Found the following devices: {'fans': [{'manager': <pyvesync.vesync.VeSync object at 0x7f7c0f7b90>, 'device_name': 'Buhar', 'device_image': 'https://image.vesync.com/defaultImages/deviceDefaultImages/wifibtonboardingnotify_airhumidifier_classic300s_us_240.png', 'cid': 'REDACTED', 'connection_status': 'online', 'connection_type': 'WiFi+BTOnboarding+BTNotify', 'device_type': 'Classic300S', 'type': 'wifi-air', 'uuid': 'REDACTED', 'config_module': 'WiFiBTOnboardingNotify_AirHumidifier_Classic300S_US', 'mac_id': 'REDACTED', 'mode': None, 'speed': None, 'extension': None, 'current_firm_version': None, 'device_region': 'US', 'pid': None, 'sub_device_no': None, 'config': {'auto_target_humidity': 60, 'display': False, 'automatic_stop': False}, 'device_status': 'off', 'enabled': False, '_config_dict': {'module': 'VeSyncHumid200300S', 'models': ['Classic300S', 'LUH-A601S-WUSB'], 'features': ['nightlight'], 'mist_modes': ['auto', 'sleep', 'manual'], 'mist_levels': [1, 2, 3, 4, 5, 6, 7, 8, 9]}, 'mist_levels': [1, 2, 3, 4, 5, 6, 7, 8, 9], 'mist_modes': ['auto', 'sleep', 'manual'], '_features': ['nightlight'], 'warm_mist_feature': False, 'warm_mist_levels': [], 'night_light': True, 'details': {'humidity': 44, 'mist_virtual_level': 9, 'mist_level': 3, 'mode': 'manual', 'water_lacks': False, 'humidity_high': False, 'water_tank_lifted': False, 'display': False, 'automatic_stop_reach_target': False, 'night_light_brightness': 0}, '_api_modes': ['getHumidifierStatus', 'setAutomaticStop', 'setSwitch', 'setNightLightBrightness', 'setVirtualLevel', 'setTargetHumidity', 'setHumidityMode', 'setDisplay', 'setLevel']}], 'outlets': [], 'switches': [], 'bulbs': [], 'kitchen': []}
2024-11-11 10:18:19.864 WARNING (MainThread) [homeassistant.helpers.frame] Detected that custom integration 'vesync' calls async_forward_entry_setup for integration, vesync with title<EMAIL_ADDRESS>and entry_id: 01JARPK1C5BTCMQQA6K4S0HRQJ, which is deprecated and will stop working in Home Assistant 2025.6, await async_forward_entry_setups instead at custom_components/vesync/init.py, line 95: hass.async_create_task(forward_setup(config_entry, p)), please create a bug report at https://github.com/micahqcade/custom_vesync
2024-11-11 10:18:27.410 WARNING (MainThread) [kasa.discover] Got unsupported connection type: {'device_family': 'SMART.IPCAMERA', 'encryption_type': 'AES', 'https': True}
2024-11-11 10:18:27.543 WARNING (MainThread) [kasa.discover] Got unsupported connection type: {'device_family': 'SMART.IPCAMERA', 'encryption_type': 'AES', 'https': True}
2024-11-11 10:18:27.612 WARNING (MainThread) [kasa.discover] Got unsupported connection type: {'device_family': 'SMART.IPCAMERA', 'encryption_type': 'AES', 'https': True}
2024-11-11 10:18:31.970 WARNING (MainThread) [homeassistant.helpers.frame] Detected code that calls async_forward_entry_setup for integration meross_cloud with title: https://iot.meross.com and entry_id: 1485ba22f9fd869dcaf4fc1aa1d7699f, during setup without awaiting async_forward_entry_setup, which can cause the setup lock to be released before the setup is done. This will stop working in Home Assistant 2025.1. Please report this issue.
Stack (most recent call last):
File "", line 198, in _run_module_as_main
File "", line 88, in _run_code
File "/usr/src/homeassistant/homeassistant/main.py", line 223, in
sys.exit(main())
File "/usr/src/homeassistant/homeassistant/main.py", line 209, in main
exit_code = runner.run(runtime_conf)
File "/usr/src/homeassistant/homeassistant/runner.py", line 189, in run
return loop.run_until_complete(setup_and_run_hass(runtime_config))
File "/usr/local/lib/python3.12/asyncio/base_events.py", line 674, in run_until_complete
self.run_forever()
File "/usr/local/lib/python3.12/asyncio/base_events.py", line 641, in run_forever
self._run_once()
File "/usr/local/lib/python3.12/asyncio/base_events.py", line 1990, in _run_once
handle._run()
File "/usr/local/lib/python3.12/asyncio/events.py", line 88, in _run
self._context.run(self._callback, *self._args)
File "/usr/src/homeassistant/homeassistant/config_entries.py", line 2318, in async_forward_entry_setup
_report_non_awaited_platform_forwards(entry, "async_forward_entry_setup")
File "/usr/src/homeassistant/homeassistant/config_entries.py", line 1194, in _report_non_awaited_platform_forwards
report(
File "/usr/src/homeassistant/homeassistant/helpers/frame.py", line 156, in report
_LOGGER.warning(msg, stack_info=True)
2024-11-11 10:18:31.979 WARNING (MainThread) [homeassistant.helpers.frame] Detected code that calls async_forward_entry_setup for integration meross_cloud with title: https://iot.meross.com and entry_id: 1485ba22f9fd869dcaf4fc1aa1d7699f, during setup without awaiting async_forward_entry_setup, which can cause the setup lock to be released before the setup is done. This will stop working in Home Assistant 2025.1. Please report this issue.
Stack (most recent call last):
File "", line 198, in _run_module_as_main
File "", line 88, in _run_code
File "/usr/src/homeassistant/homeassistant/main.py", line 223, in
sys.exit(main())
File "/usr/src/homeassistant/homeassistant/main.py", line 209, in main
exit_code = runner.run(runtime_conf)
File "/usr/src/homeassistant/homeassistant/runner.py", line 189, in run
return loop.run_until_complete(setup_and_run_hass(runtime_config))
File "/usr/local/lib/python3.12/asyncio/base_events.py", line 674, in run_until_complete
self.run_forever()
File "/usr/local/lib/python3.12/asyncio/base_events.py", line 641, in run_forever
self._run_once()
File "/usr/local/lib/python3.12/asyncio/base_events.py", line 1990, in _run_once
handle._run()
File "/usr/local/lib/python3.12/asyncio/events.py", line 88, in _run
self._context.run(self._callback, *self._args)
File "/usr/src/homeassistant/homeassistant/config_entries.py", line 2318, in async_forward_entry_setup
_report_non_awaited_platform_forwards(entry, "async_forward_entry_setup")
File "/usr/src/homeassistant/homeassistant/config_entries.py", line 1194, in _report_non_awaited_platform_forwards
report(
File "/usr/src/homeassistant/homeassistant/helpers/frame.py", line 156, in report
_LOGGER.warning(msg, stack_info=True)
2024-11-11 10:18:31.989 WARNING (MainThread) [homeassistant.helpers.frame] Detected code that calls async_forward_entry_setup for integration meross_cloud with title: https://iot.meross.com and entry_id: 1485ba22f9fd869dcaf4fc1aa1d7699f, during setup without awaiting async_forward_entry_setup, which can cause the setup lock to be released before the setup is done. This will stop working in Home Assistant 2025.1. Please report this issue.
Stack (most recent call last):
File "", line 198, in _run_module_as_main
File "", line 88, in _run_code
File "/usr/src/homeassistant/homeassistant/main.py", line 223, in
sys.exit(main())
File "/usr/src/homeassistant/homeassistant/main.py", line 209, in main
exit_code = runner.run(runtime_conf)
File "/usr/src/homeassistant/homeassistant/runner.py", line 189, in run
return loop.run_until_complete(setup_and_run_hass(runtime_config))
File "/usr/local/lib/python3.12/asyncio/base_events.py", line 674, in run_until_complete
self.run_forever()
File "/usr/local/lib/python3.12/asyncio/base_events.py", line 641, in run_forever
self._run_once()
File "/usr/local/lib/python3.12/asyncio/base_events.py", line 1990, in _run_once
handle._run()
File "/usr/local/lib/python3.12/asyncio/events.py", line 88, in _run
self._context.run(self._callback, *self._args)
File "/usr/src/homeassistant/homeassistant/config_entries.py", line 2318, in async_forward_entry_setup
_report_non_awaited_platform_forwards(entry, "async_forward_entry_setup")
File "/usr/src/homeassistant/homeassistant/config_entries.py", line 1194, in _report_non_awaited_platform_forwards
report(
File "/usr/src/homeassistant/homeassistant/helpers/frame.py", line 156, in report
_LOGGER.warning(msg, stack_info=True)
2024-11-11 10:18:32.007 WARNING (MainThread) [homeassistant.helpers.frame] Detected code that calls async_forward_entry_setup for integration meross_cloud with title: https://iot.meross.com and entry_id: 1485ba22f9fd869dcaf4fc1aa1d7699f, during setup without awaiting async_forward_entry_setup, which can cause the setup lock to be released before the setup is done. This will stop working in Home Assistant 2025.1. Please report this issue.
Stack (most recent call last):
File "", line 198, in _run_module_as_main
File "", line 88, in _run_code
File "/usr/src/homeassistant/homeassistant/main.py", line 223, in
sys.exit(main())
File "/usr/src/homeassistant/homeassistant/main.py", line 209, in main
exit_code = runner.run(runtime_conf)
File "/usr/src/homeassistant/homeassistant/runner.py", line 189, in run
return loop.run_until_complete(setup_and_run_hass(runtime_config))
File "/usr/local/lib/python3.12/asyncio/base_events.py", line 674, in run_until_complete
self.run_forever()
File "/usr/local/lib/python3.12/asyncio/base_events.py", line 641, in run_forever
self._run_once()
File "/usr/local/lib/python3.12/asyncio/base_events.py", line 1990, in _run_once
handle._run()
File "/usr/local/lib/python3.12/asyncio/events.py", line 88, in _run
self._context.run(self._callback, *self._args)
File "/usr/src/homeassistant/homeassistant/config_entries.py", line 2318, in async_forward_entry_setup
_report_non_awaited_platform_forwards(entry, "async_forward_entry_setup")
File "/usr/src/homeassistant/homeassistant/config_entries.py", line 1194, in _report_non_awaited_platform_forwards
report(
File "/usr/src/homeassistant/homeassistant/helpers/frame.py", line 156, in report
_LOGGER.warning(msg, stack_info=True)
2024-11-11 10:18:32.016 WARNING (MainThread) [homeassistant.helpers.frame] Detected code that calls async_forward_entry_setup for integration meross_cloud with title: https://iot.meross.com and entry_id: 1485ba22f9fd869dcaf4fc1aa1d7699f, during setup without awaiting async_forward_entry_setup, which can cause the setup lock to be released before the setup is done. This will stop working in Home Assistant 2025.1. Please report this issue.
Stack (most recent call last):
File "", line 198, in _run_module_as_main
File "", line 88, in _run_code
File "/usr/src/homeassistant/homeassistant/main.py", line 223, in
sys.exit(main())
File "/usr/src/homeassistant/homeassistant/main.py", line 209, in main
exit_code = runner.run(runtime_conf)
File "/usr/src/homeassistant/homeassistant/runner.py", line 189, in run
return loop.run_until_complete(setup_and_run_hass(runtime_config))
File "/usr/local/lib/python3.12/asyncio/base_events.py", line 674, in run_until_complete
self.run_forever()
File "/usr/local/lib/python3.12/asyncio/base_events.py", line 641, in run_forever
self._run_once()
File "/usr/local/lib/python3.12/asyncio/base_events.py", line 1990, in _run_once
handle._run()
File "/usr/local/lib/python3.12/asyncio/events.py", line 88, in _run
self._context.run(self._callback, *self._args)
File "/usr/src/homeassistant/homeassistant/config_entries.py", line 2318, in async_forward_entry_setup
_report_non_awaited_platform_forwards(entry, "async_forward_entry_setup")
File "/usr/src/homeassistant/homeassistant/config_entries.py", line 1194, in _report_non_awaited_platform_forwards
report(
File "/usr/src/homeassistant/homeassistant/helpers/frame.py", line 156, in report
_LOGGER.warning(msg, stack_info=True)
2024-11-11 10:18:32.988 WARNING (MainThread) [homeassistant.helpers.frame] Detected code that calls async_forward_entry_setup for integration vesync with title<EMAIL_ADDRESS>and entry_id: 01JARPK1C5BTCMQQA6K4S0HRQJ, during setup without awaiting async_forward_entry_setup, which can cause the setup lock to be released before the setup is done. This will stop working in Home Assistant 2025.1. Please report this issue.
Stack (most recent call last):
File "", line 198, in _run_module_as_main
File "", line 88, in _run_code
File "/usr/src/homeassistant/homeassistant/main.py", line 223, in
sys.exit(main())
File "/usr/src/homeassistant/homeassistant/main.py", line 209, in main
exit_code = runner.run(runtime_conf)
File "/usr/src/homeassistant/homeassistant/runner.py", line 189, in run
return loop.run_until_complete(setup_and_run_hass(runtime_config))
File "/usr/local/lib/python3.12/asyncio/base_events.py", line 674, in run_until_complete
self.run_forever()
File "/usr/local/lib/python3.12/asyncio/base_events.py", line 641, in run_forever
self._run_once()
File "/usr/local/lib/python3.12/asyncio/base_events.py", line 1990, in _run_once
handle._run()
File "/usr/local/lib/python3.12/asyncio/events.py", line 88, in _run
self._context.run(self._callback, *self._args)
File "/usr/src/homeassistant/homeassistant/config_entries.py", line 2318, in async_forward_entry_setup
_report_non_awaited_platform_forwards(entry, "async_forward_entry_setup")
File "/usr/src/homeassistant/homeassistant/config_entries.py", line 1194, in _report_non_awaited_platform_forwards
report(
File "/usr/src/homeassistant/homeassistant/helpers/frame.py", line 156, in report
_LOGGER.warning(msg, stack_info=True)
2024-11-11 10:18:33.002 WARNING (MainThread) [homeassistant.helpers.frame] Detected code that calls async_forward_entry_setup for integration vesync with title<EMAIL_ADDRESS>and entry_id: 01JARPK1C5BTCMQQA6K4S0HRQJ, during setup without awaiting async_forward_entry_setup, which can cause the setup lock to be released before the setup is done. This will stop working in Home Assistant 2025.1. Please report this issue.
Stack (most recent call last):
File "", line 198, in _run_module_as_main
File "", line 88, in _run_code
File "/usr/src/homeassistant/homeassistant/main.py", line 223, in
sys.exit(main())
File "/usr/src/homeassistant/homeassistant/main.py", line 209, in main
exit_code = runner.run(runtime_conf)
File "/usr/src/homeassistant/homeassistant/runner.py", line 189, in run
return loop.run_until_complete(setup_and_run_hass(runtime_config))
File "/usr/local/lib/python3.12/asyncio/base_events.py", line 674, in run_until_complete
self.run_forever()
File "/usr/local/lib/python3.12/asyncio/base_events.py", line 641, in run_forever
self._run_once()
File "/usr/local/lib/python3.12/asyncio/base_events.py", line 1990, in _run_once
handle._run()
File "/usr/local/lib/python3.12/asyncio/events.py", line 88, in _run
self._context.run(self._callback, *self._args)
File "/usr/src/homeassistant/homeassistant/config_entries.py", line 2318, in async_forward_entry_setup
_report_non_awaited_platform_forwards(entry, "async_forward_entry_setup")
File "/usr/src/homeassistant/homeassistant/config_entries.py", line 1194, in _report_non_awaited_platform_forwards
report(
File "/usr/src/homeassistant/homeassistant/helpers/frame.py", line 156, in report
_LOGGER.warning(msg, stack_info=True)
2024-11-11 10:18:33.016 WARNING (MainThread) [homeassistant.helpers.frame] Detected code that calls async_forward_entry_setup for integration vesync with title<EMAIL_ADDRESS>and entry_id: 01JARPK1C5BTCMQQA6K4S0HRQJ, during setup without awaiting async_forward_entry_setup, which can cause the setup lock to be released before the setup is done. This will stop working in Home Assistant 2025.1. Please report this issue.
Stack (most recent call last):
File "", line 198, in _run_module_as_main
File "", line 88, in _run_code
File "/usr/src/homeassistant/homeassistant/main.py", line 223, in
sys.exit(main())
File "/usr/src/homeassistant/homeassistant/main.py", line 209, in main
exit_code = runner.run(runtime_conf)
File "/usr/src/homeassistant/homeassistant/runner.py", line 189, in run
return loop.run_until_complete(setup_and_run_hass(runtime_config))
File "/usr/local/lib/python3.12/asyncio/base_events.py", line 674, in run_until_complete
self.run_forever()
File "/usr/local/lib/python3.12/asyncio/base_events.py", line 641, in run_forever
self._run_once()
File "/usr/local/lib/python3.12/asyncio/base_events.py", line 1990, in _run_once
handle._run()
File "/usr/local/lib/python3.12/asyncio/events.py", line 88, in _run
self._context.run(self._callback, *self._args)
File "/usr/src/homeassistant/homeassistant/config_entries.py", line 2318, in async_forward_entry_setup
_report_non_awaited_platform_forwards(entry, "async_forward_entry_setup")
File "/usr/src/homeassistant/homeassistant/config_entries.py", line 1194, in _report_non_awaited_platform_forwards
report(
File "/usr/src/homeassistant/homeassistant/helpers/frame.py", line 156, in report
_LOGGER.warning(msg, stack_info=True)
2024-11-11 10:18:33.023 WARNING (MainThread) [homeassistant.helpers.frame] Detected code that calls async_forward_entry_setup for integration vesync with title<EMAIL_ADDRESS>and entry_id: 01JARPK1C5BTCMQQA6K4S0HRQJ, during setup without awaiting async_forward_entry_setup, which can cause the setup lock to be released before the setup is done. This will stop working in Home Assistant 2025.1. Please report this issue.
Stack (most recent call last):
File "", line 198, in _run_module_as_main
File "", line 88, in _run_code
File "/usr/src/homeassistant/homeassistant/main.py", line 223, in
sys.exit(main())
File "/usr/src/homeassistant/homeassistant/main.py", line 209, in main
exit_code = runner.run(runtime_conf)
File "/usr/src/homeassistant/homeassistant/runner.py", line 189, in run
return loop.run_until_complete(setup_and_run_hass(runtime_config))
File "/usr/local/lib/python3.12/asyncio/base_events.py", line 674, in run_until_complete
self.run_forever()
File "/usr/local/lib/python3.12/asyncio/base_events.py", line 641, in run_forever
self._run_once()
File "/usr/local/lib/python3.12/asyncio/base_events.py", line 1990, in _run_once
handle._run()
File "/usr/local/lib/python3.12/asyncio/events.py", line 88, in _run
self._context.run(self._callback, *self._args)
File "/usr/src/homeassistant/homeassistant/config_entries.py", line 2318, in async_forward_entry_setup
_report_non_awaited_platform_forwards(entry, "async_forward_entry_setup")
File "/usr/src/homeassistant/homeassistant/config_entries.py", line 1194, in _report_non_awaited_platform_forwards
report(
File "/usr/src/homeassistant/homeassistant/helpers/frame.py", line 156, in report
_LOGGER.warning(msg, stack_info=True)
2024-11-11 10:18:33.035 WARNING (MainThread) [homeassistant.helpers.frame] Detected code that calls async_forward_entry_setup for integration vesync with title<EMAIL_ADDRESS>and entry_id: 01JARPK1C5BTCMQQA6K4S0HRQJ, during setup without awaiting async_forward_entry_setup, which can cause the setup lock to be released before the setup is done. This will stop working in Home Assistant 2025.1. Please report this issue.
Stack (most recent call last):
File "", line 198, in _run_module_as_main
File "", line 88, in _run_code
File "/usr/src/homeassistant/homeassistant/main.py", line 223, in
sys.exit(main())
File "/usr/src/homeassistant/homeassistant/main.py", line 209, in main
exit_code = runner.run(runtime_conf)
File "/usr/src/homeassistant/homeassistant/runner.py", line 189, in run
return loop.run_until_complete(setup_and_run_hass(runtime_config))
File "/usr/local/lib/python3.12/asyncio/base_events.py", line 674, in run_until_complete
self.run_forever()
File "/usr/local/lib/python3.12/asyncio/base_events.py", line 641, in run_forever
self._run_once()
File "/usr/local/lib/python3.12/asyncio/base_events.py", line 1990, in _run_once
handle._run()
File "/usr/local/lib/python3.12/asyncio/events.py", line 88, in _run
self._context.run(self._callback, *self._args)
File "/usr/src/homeassistant/homeassistant/config_entries.py", line 2318, in async_forward_entry_setup
_report_non_awaited_platform_forwards(entry, "async_forward_entry_setup")
File "/usr/src/homeassistant/homeassistant/config_entries.py", line 1194, in _report_non_awaited_platform_forwards
report(
File "/usr/src/homeassistant/homeassistant/helpers/frame.py", line 156, in report
_LOGGER.warning(msg, stack_info=True)
2024-11-11 10:18:33.075 WARNING (MainThread) [homeassistant.helpers.frame] Detected code that calls async_forward_entry_setup for integration meross_cloud with title: https://iot.meross.com and entry_id: 1485ba22f9fd869dcaf4fc1aa1d7699f, during setup without awaiting async_forward_entry_setup, which can cause the setup lock to be released before the setup is done. This will stop working in Home Assistant 2025.1. Please report this issue.
Stack (most recent call last):
File "", line 198, in _run_module_as_main
File "", line 88, in _run_code
File "/usr/src/homeassistant/homeassistant/main.py", line 223, in
sys.exit(main())
File "/usr/src/homeassistant/homeassistant/main.py", line 209, in main
exit_code = runner.run(runtime_conf)
File "/usr/src/homeassistant/homeassistant/runner.py", line 189, in run
return loop.run_until_complete(setup_and_run_hass(runtime_config))
File "/usr/local/lib/python3.12/asyncio/base_events.py", line 674, in run_until_complete
self.run_forever()
File "/usr/local/lib/python3.12/asyncio/base_events.py", line 641, in run_forever
self._run_once()
File "/usr/local/lib/python3.12/asyncio/base_events.py", line 1990, in _run_once
handle._run()
File "/usr/local/lib/python3.12/asyncio/events.py", line 88, in _run
self._context.run(self._callback, *self._args)
File "/usr/src/homeassistant/homeassistant/config_entries.py", line 2318, in async_forward_entry_setup
_report_non_awaited_platform_forwards(entry, "async_forward_entry_setup")
File "/usr/src/homeassistant/homeassistant/config_entries.py", line 1194, in _report_non_awaited_platform_forwards
report(
File "/usr/src/homeassistant/homeassistant/helpers/frame.py", line 156, in report
_LOGGER.warning(msg, stack_info=True)
2024-11-11 10:18:33.100 WARNING (MainThread) [homeassistant.helpers.frame] Detected code that calls async_forward_entry_setup for integration vesync with title<EMAIL_ADDRESS>and entry_id: 01JARPK1C5BTCMQQA6K4S0HRQJ, during setup without awaiting async_forward_entry_setup, which can cause the setup lock to be released before the setup is done. This will stop working in Home Assistant 2025.1. Please report this issue.
Stack (most recent call last):
File "", line 198, in _run_module_as_main
File "", line 88, in _run_code
File "/usr/src/homeassistant/homeassistant/main.py", line 223, in
sys.exit(main())
File "/usr/src/homeassistant/homeassistant/main.py", line 209, in main
exit_code = runner.run(runtime_conf)
File "/usr/src/homeassistant/homeassistant/runner.py", line 189, in run
return loop.run_until_complete(setup_and_run_hass(runtime_config))
File "/usr/local/lib/python3.12/asyncio/base_events.py", line 674, in run_until_complete
self.run_forever()
File "/usr/local/lib/python3.12/asyncio/base_events.py", line 641, in run_forever
self._run_once()
File "/usr/local/lib/python3.12/asyncio/base_events.py", line 1990, in _run_once
handle._run()
File "/usr/local/lib/python3.12/asyncio/events.py", line 88, in _run
self._context.run(self._callback, *self._args)
File "/usr/src/homeassistant/homeassistant/config_entries.py", line 2318, in async_forward_entry_setup
_report_non_awaited_platform_forwards(entry, "async_forward_entry_setup")
File "/usr/src/homeassistant/homeassistant/config_entries.py", line 1194, in _report_non_awaited_platform_forwards
report(
File "/usr/src/homeassistant/homeassistant/helpers/frame.py", line 156, in report
_LOGGER.warning(msg, stack_info=True)
2024-11-11 10:18:34.391 WARNING (MainThread) [homeassistant.util.loop] Detected blocking call to load_verify_locations with args (<ssl.SSLContext object at 0x7f4905add0>,) inside the event loop by custom integration 'extended_openai_conversation' at custom_components/extended_openai_conversation/helpers.py, line 146: client = AsyncOpenAI( (offender: /usr/local/lib/python3.12/site-packages/httpx/_config.py, line 149: context.load_verify_locations(cafile=cafile)), please create a bug report at https://github.com/jekalmin/extended_openai_conversation/issues
For developers, please see https://developers.home-assistant.io/docs/asyncio_blocking_operations/#load_verify_locations
Traceback (most recent call last):
File "", line 198, in _run_module_as_main
File "", line 88, in _run_code
File "/usr/src/homeassistant/homeassistant/main.py", line 223, in
sys.exit(main())
File "/usr/src/homeassistant/homeassistant/main.py", line 209, in main
exit_code = runner.run(runtime_conf)
File "/usr/src/homeassistant/homeassistant/runner.py", line 189, in run
return loop.run_until_complete(setup_and_run_hass(runtime_config))
File "/usr/local/lib/python3.12/asyncio/base_events.py", line 674, in run_until_complete
self.run_forever()
File "/usr/local/lib/python3.12/asyncio/base_events.py", line 641, in run_forever
self._run_once()
File "/usr/local/lib/python3.12/asyncio/base_events.py", line 1990, in _run_once
handle._run()
File "/usr/local/lib/python3.12/asyncio/events.py", line 88, in _run
self._context.run(self._callback, *self._args)
File "/usr/src/homeassistant/homeassistant/setup.py", line 165, in async_setup_component
result = await _async_setup_component(hass, domain, config)
File "/usr/src/homeassistant/homeassistant/setup.py", line 461, in async_setup_component
await asyncio.gather(
File "/usr/src/homeassistant/homeassistant/setup.py", line 463, in
create_eager_task(
File "/usr/src/homeassistant/homeassistant/util/async.py", line 45, in create_eager_task
return Task(coro, loop=loop, name=name, eager_start=True)
File "/usr/src/homeassistant/homeassistant/config_entries.py", line 783, in async_setup_locked
await self.async_setup(hass, integration=integration)
File "/usr/src/homeassistant/homeassistant/config_entries.py", line 546, in async_setup
await self.__async_setup_with_context(hass, integration)
File "/usr/src/homeassistant/homeassistant/config_entries.py", line 635, in __async_setup_with_context
result = await component.async_setup_entry(hass, self)
File "/config/custom_components/extended_openai_conversation/init.py", line 100, in async_setup_entry
await validate_authentication(
File "/config/custom_components/extended_openai_conversation/helpers.py", line 146, in validate_authentication
client = AsyncOpenAI(

2024-11-11 10:18:34.467 WARNING (MainThread) [homeassistant.util.loop] Detected blocking call to open with args ('/etc/os-release',) inside the event loop by custom integration 'extended_openai_conversation' at custom_components/extended_openai_conversation/helpers.py, line 150: await client.models.list(timeout=10) (offender: /usr/local/lib/python3.12/site-packages/distro/distro.py, line 1099: with open(self.os_release_file, encoding="utf-8") as release_file:), please create a bug report at https://github.com/jekalmin/extended_openai_conversation/issues
For developers, please see https://developers.home-assistant.io/docs/asyncio_blocking_operations/#open
Traceback (most recent call last):
File "", line 198, in _run_module_as_main
File "", line 88, in _run_code
File "/usr/src/homeassistant/homeassistant/main.py", line 223, in
sys.exit(main())
File "/usr/src/homeassistant/homeassistant/main.py", line 209, in main
exit_code = runner.run(runtime_conf)
File "/usr/src/homeassistant/homeassistant/runner.py", line 189, in run
return loop.run_until_complete(setup_and_run_hass(runtime_config))
File "/usr/local/lib/python3.12/asyncio/base_events.py", line 674, in run_until_complete
self.run_forever()
File "/usr/local/lib/python3.12/asyncio/base_events.py", line 641, in run_forever
self._run_once()
File "/usr/local/lib/python3.12/asyncio/base_events.py", line 1990, in _run_once
handle._run()
File "/usr/local/lib/python3.12/asyncio/events.py", line 88, in _run
self._context.run(self._callback, *self._args)
File "/usr/src/homeassistant/homeassistant/setup.py", line 165, in async_setup_component
result = await _async_setup_component(hass, domain, config)
File "/usr/src/homeassistant/homeassistant/setup.py", line 461, in async_setup_component
await asyncio.gather(
File "/usr/src/homeassistant/homeassistant/setup.py", line 463, in
create_eager_task(
File "/usr/src/homeassistant/homeassistant/util/async.py", line 45, in create_eager_task
return Task(coro, loop=loop, name=name, eager_start=True)
File "/usr/src/homeassistant/homeassistant/config_entries.py", line 783, in async_setup_locked
await self.async_setup(hass, integration=integration)
File "/usr/src/homeassistant/homeassistant/config_entries.py", line 546, in async_setup
await self.__async_setup_with_context(hass, integration)
File "/usr/src/homeassistant/homeassistant/config_entries.py", line 635, in __async_setup_with_context
result = await component.async_setup_entry(hass, self)
File "/config/custom_components/extended_openai_conversation/init.py", line 100, in async_setup_entry
await validate_authentication(
File "/config/custom_components/extended_openai_conversation/helpers.py", line 150, in validate_authentication
await client.models.list(timeout=10)
2024-11-11 10:18:36.852 WARNING (MainThread) [homeassistant.components.homekit] The bridge Televizyon has entity media_player.televizyon. For best performance, and to prevent unexpected unavailability, create and pair a separate HomeKit instance in accessory mode for this entity
2024-11-11 10:20:19.512 ERROR (MainThread) [homeassistant.components.automation.google_drive_backup_otomasyonu] Google Drive Backup Otomasyonu: Error executing script. Error for call_service at pos 1: Device not connected to local push notifications
2024-11-11 10:20:19.516 ERROR (MainThread) [homeassistant.components.automation.google_drive_backup_otomasyonu] Error while executing automation automation.google_drive_backup_otomasyonu: Device not connected to local push notifications
2024-11-11 10:20:19.546 ERROR (MainThread) [homeassistant.components.automation.google_drive_backup_otomasyonu] Google Drive Backup Otomasyonu: Error executing script. Error for call_service at pos 1: Device not connected to local push notifications
2024-11-11 10:20:19.547 ERROR (MainThread) [homeassistant.components.automation.google_drive_backup_otomasyonu] Error while executing automation automation.google_drive_backup_otomasyonu: Device not connected to local push notifications
2024-11-11 10:23:32.688 ERROR (MainThread) [homeassistant.components.hassio] Failed to to call /addons/b9845f46_govee2mqtt/stats - Container addon_b9845f46_govee2mqtt is not running
2024-11-11 10:24:24.777 WARNING (MainThread) [homeassistant.helpers.frame] Detected that custom integration 'govee_lan' calls async_forward_entry_setup for integration, govee_lan with title: govee_lan and entry_id: 01JCDX6YSSZH8F7REJX5DB0PMM, which is deprecated and will stop working in Home Assistant 2025.6, await async_forward_entry_setups instead at custom_components/govee_lan/init.py, line 32: hass.async_create_task(, please create a bug report at https://github.com/wez/govee-lan-hass/issues
2024-11-11 10:24:24.821 WARNING (MainThread) [homeassistant.util.loop] Detected blocking call to load_verify_locations with args (<ssl.SSLContext object at 0x7f3e2b4d50>, '/usr/local/lib/python3.12/site-packages/certifi/cacert.pem', None, None) inside the event loop by custom integration 'govee_lan' at custom_components/govee_lan/light.py, line 150: await controller.query_http_devices() (offender: /usr/local/lib/python3.12/ssl.py, line 708: context.load_verify_locations(cafile, capath, cadata)), please create a bug report at https://github.com/wez/govee-lan-hass/issues
For developers, please see https://developers.home-assistant.io/docs/asyncio_blocking_operations/#load_verify_locations
Traceback (most recent call last):
File "", line 198, in _run_module_as_main
File "", line 88, in _run_code
File "/usr/src/homeassistant/homeassistant/main.py", line 223, in
sys.exit(main())
File "/usr/src/homeassistant/homeassistant/main.py", line 209, in main
exit_code = runner.run(runtime_conf)
File "/usr/src/homeassistant/homeassistant/runner.py", line 189, in run
return loop.run_until_complete(setup_and_run_hass(runtime_config))
File "/usr/local/lib/python3.12/asyncio/base_events.py", line 674, in run_until_complete
self.run_forever()
File "/usr/local/lib/python3.12/asyncio/base_events.py", line 641, in run_forever
self._run_once()
File "/usr/local/lib/python3.12/asyncio/base_events.py", line 1990, in _run_once
handle._run()
File "/usr/local/lib/python3.12/asyncio/events.py", line 88, in _run
self._context.run(self._callback, *self._args)
File "/usr/src/homeassistant/homeassistant/config_entries.py", line 2314, in async_forward_entry_setup
result = await self._async_forward_entry_setup(entry, domain, True)
File "/usr/src/homeassistant/homeassistant/config_entries.py", line 2348, in _async_forward_entry_setup
await entry.async_setup(self.hass, integration=integration)
File "/usr/src/homeassistant/homeassistant/config_entries.py", line 546, in async_setup
await self.__async_setup_with_context(hass, integration)
File "/usr/src/homeassistant/homeassistant/config_entries.py", line 635, in __async_setup_with_context
result = await component.async_setup_entry(hass, self)
File "/usr/src/homeassistant/homeassistant/components/light/init.py", line 675, in async_setup_entry
return await hass.data[DATA_COMPONENT].async_setup_entry(entry)
File "/usr/src/homeassistant/homeassistant/helpers/entity_component.py", line 197, in async_setup_entry
return await self._platforms[key].async_setup_entry(config_entry)
File "/usr/src/homeassistant/homeassistant/helpers/entity_platform.py", line 332, in async_setup_entry
return await self._async_setup_platform(async_create_setup_awaitable)
File "/usr/src/homeassistant/homeassistant/helpers/entity_platform.py", line 362, in async_setup_platform
awaitable = create_eager_task(awaitable, loop=hass.loop)
File "/usr/src/homeassistant/homeassistant/util/async.py", line 45, in create_eager_task
return Task(coro, loop=loop, name=name, eager_start=True)
File "/config/custom_components/govee_lan/light.py", line 150, in async_setup_entry
await controller.query_http_devices()
2024-11-11 10:24:24.996 WARNING (MainThread) [homeassistant.components.light] None (<class 'custom_components.govee_lan.light.GoveLightEntity'>) sets invalid supported color modes {<ColorMode.RGB: 'rgb'>, <ColorMode.BRIGHTNESS: 'brightness'>, <ColorMode.COLOR_TEMP: 'color_temp'>}, this will stop working in Home Assistant Core 2025.3, please create a bug report at https://github.com/wez/govee-lan-hass/issues
2024-11-11 10:24:25.021 WARNING (MainThread) [homeassistant.helpers.frame] Detected code that calls async_forward_entry_setup for integration govee_lan with title: govee_lan and entry_id: 01JCDX6YSSZH8F7REJX5DB0PMM, during setup without awaiting async_forward_entry_setup, which can cause the setup lock to be released before the setup is done. This will stop working in Home Assistant 2025.1. Please report this issue.
Stack (most recent call last):
File "", line 198, in _run_module_as_main
File "", line 88, in _run_code
File "/usr/src/homeassistant/homeassistant/main.py", line 223, in
sys.exit(main())
File "/usr/src/homeassistant/homeassistant/main.py", line 209, in main
exit_code = runner.run(runtime_conf)
File "/usr/src/homeassistant/homeassistant/runner.py", line 189, in run
return loop.run_until_complete(setup_and_run_hass(runtime_config))
File "/usr/local/lib/python3.12/asyncio/base_events.py", line 674, in run_until_complete
self.run_forever()
File "/usr/local/lib/python3.12/asyncio/base_events.py", line 641, in run_forever
self._run_once()
File "/usr/local/lib/python3.12/asyncio/base_events.py", line 1990, in _run_once
handle._run()
File "/usr/local/lib/python3.12/asyncio/events.py", line 88, in _run
self._context.run(self._callback, *self._args)
File "/usr/src/homeassistant/homeassistant/config_entries.py", line 2318, in async_forward_entry_setup
_report_non_awaited_platform_forwards(entry, "async_forward_entry_setup")
File "/usr/src/homeassistant/homeassistant/config_entries.py", line 1194, in _report_non_awaited_platform_forwards
report(
File "/usr/src/homeassistant/homeassistant/helpers/frame.py", line 156, in report
_LOGGER.warning(msg, stack_info=True)
2024-11-11 10:33:25.779 WARNING (MainThread) [kasa.discover] Got unsupported connection type: {'device_family': 'SMART.IPCAMERA', 'encryption_type': 'AES', 'https': True}
2024-11-11 10:33:25.885 WARNING (MainThread) [kasa.discover] Got unsupported connection type: {'device_family': 'SMART.IPCAMERA', 'encryption_type': 'AES', 'https': True}
2024-11-11 10:33:26.047 WARNING (MainThread) [kasa.discover] Got unsupported connection type: {'device_family': 'SMART.IPCAMERA', 'encryption_type': 'AES', 'https': True}
2024-11-11 10:34:25.021 WARNING (MainThread) [homeassistant.util.loop] Detected blocking call to load_verify_locations with args (<ssl.SSLContext object at 0x7f4757de50>, '/usr/local/lib/python3.12/site-packages/certifi/cacert.pem', None, None) in /usr/local/lib/python3.12/ssl.py, line 708: context.load_verify_locations(cafile, capath, cadata) inside the event loop; This is causing stability issues. Please create a bug report at https://github.com/home-assistant/core/issues?q=is%3Aopen+is%3Aissue
For developers, please see https://developers.home-assistant.io/docs/asyncio_blocking_operations/#load_verify_locations
Traceback (most recent call last):
File "", line 198, in _run_module_as_main
File "", line 88, in _run_code
File "/usr/src/homeassistant/homeassistant/main.py", line 223, in
sys.exit(main())
File "/usr/src/homeassistant/homeassistant/main.py", line 209, in main
exit_code = runner.run(runtime_conf)
File "/usr/src/homeassistant/homeassistant/runner.py", line 189, in run
return loop.run_until_complete(setup_and_run_hass(runtime_config))
File "/usr/local/lib/python3.12/asyncio/base_events.py", line 674, in run_until_complete
self.run_forever()
File "/usr/local/lib/python3.12/asyncio/base_events.py", line 641, in run_forever
self._run_once()
File "/usr/local/lib/python3.12/asyncio/base_events.py", line 1990, in _run_once
handle._run()
File "/usr/local/lib/python3.12/asyncio/events.py", line 88, in _run
self._context.run(self._callback, *self._args)
File "/usr/local/lib/python3.12/site-packages/govee_led_wez/govee.py", line 717, in _http_poller
await self.query_http_devices()
File "/usr/local/lib/python3.12/site-packages/govee_led_wez/govee.py", line 239, in query_http_devices
devices = await http_get_devices(self.api_key)
File "/usr/local/lib/python3.12/site-packages/govee_led_wez/http.py", line 37, in http_get_devices
ssl_context = ssl.create_default_context(cafile=certifi.where())
File "/usr/local/lib/python3.12/ssl.py", line 708, in create_default_context
context.load_verify_locations(cafile, capath, cadata)
2024-11-11 10:48:25.788 WARNING (MainThread) [kasa.discover] Got unsupported connection type: {'device_family': 'SMART.IPCAMERA', 'encryption_type': 'AES', 'https': True}
2024-11-11 10:48:25.933 WARNING (MainThread) [kasa.discover] Got unsupported connection type: {'device_family': 'SMART.IPCAMERA', 'encryption_type': 'AES', 'https': True}
2024-11-11 10:48:26.160 WARNING (MainThread) [kasa.discover] Got unsupported connection type: {'device_family': 'SMART.IPCAMERA', 'encryption_type': 'AES', 'https': True}
2024-11-11 11:03:25.783 WARNING (MainThread) [kasa.discover] Got unsupported connection type: {'device_family': 'SMART.IPCAMERA', 'encryption_type': 'AES', 'https': True}
2024-11-11 11:03:25.950 WARNING (MainThread) [kasa.discover] Got unsupported connection type: {'device_family': 'SMART.IPCAMERA', 'encryption_type': 'AES', 'https': True}
2024-11-11 11:03:25.960 WARNING (MainThread) [kasa.discover] Got unsupported connection type: {'device_family': 'SMART.IPCAMERA', 'encryption_type': 'AES', 'https': True}
2024-11-11 11:12:24.779 ERROR (MainThread) [homeassistant.components.hassio] Failed to to call /addons/b9845f46_govee2mqtt/stats - Container addon_b9845f46_govee2mqtt is not running
2024-11-11 11:12:40.660 ERROR (MainThread) [homeassistant.components.govee_light_local.config_flow] Start failed, errno: 98
2024-11-11 11:18:25.806 WARNING (MainThread) [kasa.discover] Got unsupported connection type: {'device_family': 'SMART.IPCAMERA', 'encryption_type': 'AES', 'https': True}
2024-11-11 11:18:25.887 WARNING (MainThread) [kasa.discover] Got unsupported connection type: {'device_family': 'SMART.IPCAMERA', 'encryption_type': 'AES', 'https': True}
2024-11-11 11:18:26.410 WARNING (MainThread) [kasa.discover] Got unsupported connection type: {'device_family': 'SMART.IPCAMERA', 'encryption_type': 'AES', 'https': True}
2024-11-11 11:25:55.996 ERROR (MainThread) [homeassistant.components.hassio] Failed to to call /addons/b9845f46_govee2mqtt/stats - Container addon_b9845f46_govee2mqtt is not running
</summary>

### Anything else?

_No response_

The error message seems quite clear to me:

Error: Cannot bind to UDP Port 4002, which is required for the Govee LAN API to function. Most likely cause is that you are running another integration (perhaps Govee LAN Control, or homebridge-govee) that is already bound to that port. Both cannot run on the same machine at the same time. Consider disabling Govee LAN Control or setting lanDisable in homebridge-govee.

I’m not running either of those and I get that message. To my knowledge nothing is running on that port on that system.


Allow optimizer hints - Backport to 0.21

Backport of #4243 to 0.21

Thanks! Now let's see if CI passes. If Travis will be acting up, I'll backport the GA CI.

Thanks! Now let's see if CI passes. If Travis will be acting up, I'll backport the GA CI.

@kibertoad CI seems passed.

@kibertoad CI seems passed.

Thanks! Will release new version shortly.

Thanks! Will release new version shortly.


Small bugs in scaling constants in qdetector

Hi Joseph,
I've been reviewing the qdetector, and I believe I have found a fairly small bug in  https://github.com/jgaeddert/liquid-dsp/blob/master/src/framing/src/qdetector_cccf.c#L392-L393 .
This scaling factor appears to be right in almost all cases, but for the first time through the qdetector, the first half of the buffer is empty (silence). Imagine that our noise floor is -60 dB and we have 0 dB SNR. Normally, -60dB noise will occupy the entire buffer, but on the very first time through, the first half is empty and doesn't contribute.
In practice, I don't think this really matters since you normally move through this phase very quickly, but I think this may affect some of the tests/examples which typically run the qdetector right away, without priming it with samples. In particular, this seems to effectively reduce the detection threshold.
It looks like the fix is to check if _q->x2_sum_0 is 0, and if it is, change the scaling factor sqrtf((float)(_q->s_len) / (float)(_q->nfft)) to sqrtf((float)(_q->s_len) / (float)(_q->nfft / 2)). Keeping all these constants correct in my head is rather tricky, but I believe this one is supposed to account for the fraction of the buffer that the sequence occupies.
There's another small bug here in that g0 can easily be 0 if our received energy is 0. This leads to a division by 0 and g = inf. Curiously, this actually doesn't cause false detections because inf > inf is true, and the detector runs along until it declares the last index to have the highest correlation. Since that falls above nfft - s_len, the detector perpetually declares no detection. It might be sensible to just cap g0 at a lower bound of 1e-6 since I imagine there may be other numerical gremlins lurking at very small nonzero signal levels.

I've noticed one other thing that might be a bug. I need to confirm this more thoroughly, but I think that somehow, in some cases, when we see rxy_peak > _q->threshold but not rxy_index < _q->nfft - _q->s_len, detection somehow doesn't happen on the next block of samples. I'm not entirely sure how that might be. My best guess is that maybe FFT windowing messes with things a little, but that seems fairly unlikely, and I can't find any other possible causes.


Review and update schema references (5.0.0 -> 5.1.0)

There are many references to the schema specification and/or its sections that must be reviewed for potential updates. In most cases, this will be a simple change - replacing "5.0.0" with "5.1.0".
For example, search for 5.0.0 references.
Ensure that the following are updated:

Discover API
Contribute and Publish
Download UX Modal

complete


WHERE clause doesn't take effect when using mathematical function

WHERE clause doesn't take effect when using mathematical function in SELECT clause.
To re-produce this locally, follow the steps:

Setup Kuiper to an MQTT broker and make it run
docker run -p 9081:9081 -d --name kuiper -e MQTT_SOURCE__DEFAULT__SERVERS=[tcp://broker.emqx.io:1883] emqx/kuiper:1.1.2-alpine
Create a stream
bin/kuiper create stream events '()WITH (FORMAT="JSON", DATASOURCE="devices/+/messages")'
Create a rule
bin/kuiper query
Kuiper > select power(temperature,2) as pw_temp from events where temperature != nil
Publish data to topic devices/device_123/messages of server tcp://broker.emqx.io:1883
mosquitto_pub -h broker.emqx.io -m '{"humidity" : 20}' -t devices/device_123/messages
An error message should shows up on the bin/kuiper query window:
[{"error":"call func power error: only float64 & int type are supported"}]

Since the SQL statement has a WHERE clause for filtering, should the Humidity data be ignored?

Thanks for opeing the issue. The problem happens in the alias which is calculated before the where. We will fix this.
Currently, you can work by removing the alias select power(temperature,2) from events where temperature != nil


Short solution needed: "Get current hostname in CLI" (ubuntu)

Please help us write most modern and shortest code solution for this issue:
Get current hostname in CLI (technology: ubuntu)
Fast way
Just write the code solution in the comments.
Prefered way

Create pull request with a new code file inside inbox folder.
Don't forget to use comments to make solution explained.
Link to this issue in comments of pull request.

Get current hostname in CLI


CORE-2052 : dropAll failure on Postgres

On a Postgres database, dropAll tries to drop even views not owned by the
user, which causes errors.

Great. Thanks!!

The documentation is not quite right. DropAll shouldn't drop object based on the owner but instead drops everything in the configured schema(s). I updated the javadoc for 3.4.0.
Closing the pull request since it would change the functionality


How to escape space in GlobalOptions

Hi,
I use https://github.com/idocking/go-wkhtmltox docker container with wkhtmltopdf 0.12.5 (with patched qt).
I try to set GlobalOptions like this:
"converter": {
		"url": null,
		"extend": {
			"footer-left": "[date]",
			"footer-right": "Prepared [date] [page]/[topage]",
			"footer-font-size": "10",
			"margin-bottom": "20",
			"footer-spacing": "10"
		}
	},

I use space like in footer-right line I get error when convert to pdf:
open /tmp/go-wkhtmltox212187195/41f80aa7-be68-4437-9d43-27bb8f520780.pdf: no such file or directory

When I delete space in string line this "Prepared[date][page]/[topage]" everything work fine.
Any ideas how to escape space?

I will answer to myself:
Rebuild container without xvfb in alpine. Install into container wkhtmltopdf 0.12.5/6 (with patchet qt) and everything work fine.


list-group change in behavior between v4.3.1 and v4.4.0 for paragraph tag

Prerequisites

[X] I have searched for duplicate or closed issues
[X] I have validated any HTML to avoid common problems
[X] I have read the contributing guidelines

Describe the issue
https://getbootstrap.com/docs/4.0/components/list-group/ shows samples with both ul/li list tags and div with other tag types.
:heavy_check_mark: In version 3.4.1 of bootstrap (and earlier) paragraph/p tags work fine. See
bootstrap_431_working.html.txt

:x: However in v 4.4.0 (the next following version) the "boxes" don't connect and have gaps/holes. See
bootstrap_440_bad_lines.html.txt

:heavy_check_mark: Using list ul/li tags can be used as a workaround. See bootstrap_440_li_instead_of_p.html.txt

I think this is a bug, but from docs it's not clear on expected behavior for p tags but it used to work with the earlier versions.
NOTE I used https://validator.w3.org/nu/#file Version: 22.8.7 for validation
Reduced test cases
See attached, inline below:
<!DOCTYPE html>

    <meta charset="utf-8">
    <meta name="viewport" content="width=device-width, initial-scale=1">
    <title>bootstrap 5 issues</title>

    <link<EMAIL_ADDRESS>rel="stylesheet" crossorigin="anonymous">

                    tz : tanzania, united republic of

                    ae : united arab emirates

                    gb : united kingdom

                    us : united states

                    um : united states minor outlying islands

What operating system(s) are you seeing the problem on?
Windows, Android
What browser(s) are you seeing the problem on?
Firefox, Microsoft Edge
What version of Bootstrap are you using?
v3.3.6, v3.4.1, v4.4.0, v5.2.0

I skimmed https://github.com/twbs/bootstrap/compare/v4.3.1...v4.4.0 file diffs in the list-group files but nothing jumped out at me :crying_cat_face:

Both versions mentioned here are out of date and not actively maintained. Also, you're using
 elements which have margin-bottom by default, perhaps messing up the default .list-group styling. Generally speaking, you should be building this content with more semantic markup at the very least. Closing as a won't fix given all this.


fix: If there is no root, use angular from window

After using this with webpack, I was getting a "Cannot read angular of undefined" error when loading it in browser.
This small change checks if root is defined before trying to then access root.angular, otherwise falling back to window.angular.
As a side note, this logic is pretty much the same as before. It doesn't check if window exists before trying to access window.angular, but this check is unnecessary. In the previous code, if both root.angular and window were undefined, then angular would be undefined, quickly causing an error.
EDIT: I ran the tests locally and all passed - it looks like there may be an issue with the CI server

LGTM
I'll get it merged into the new release by next weekend, thanks for the PR!


[Sign-up]Error message is not displayed for 'First name' field.

Environment: Windows 10 Pro/ Google Chrome 81.0.4044.129
Reproducible: always
Build found: commit 7439e88
Steps to reproduce:
1)Go to GreenCity (https://ita-social-projects.github.io/GreenCityClient/#/welcome);
2)Click on "Sign up" button;
3)Leave the 'First name' field empty;
4)Enter valid email, Password and Confirm Password (field requirements in #385)
5)Click on 'Sing-up' button
Actual result: Error message 'First name is required' is not displayed for 'First name' field.
Expected result: Error-message 'First name is required' is displayed.
User story: #385
Test case: https://jira.softserve.academy/browse/GC-210

Fixed


[rglfw] Wayland support

In raylib-go I added support recently for Wayland, see https://github.com/gen2brain/raylib-go/issues/24 and https://github.com/gen2brain/raylib-go/issues/25. Some headers are generated with https://github.com/gen2brain/raylib-go/blob/master/raylib/external/scripts/glfw-generate-wayland.sh script, but you can just pick them from raylib-go.
Also, i added if defined(_GLFW_X11) here https://github.com/gen2brain/raylib-go/blob/master/raylib/core.c#L720 and https://github.com/gen2brain/raylib-go/blob/master/raylib/core.c#L733 .
Btw, I updated GLFW sources to latest from master, there are couple of new files to include, details are in cgo_linux.go, cgo_darwin, etc. On Linux (X11), there is no need anymore to link to -lXrandr -lXinerama -lXi -lXxf86vm -lXcursor , they are now dlopen-ed.

Thanks for the info @gen2brain, I'll update it ASAP! :)

Initial work on Wayland support in commit https://github.com/raysan5/raylib/commit/5ae2c0d15b349ce59425c319165505bda8298a6c
Looking for a way to expose it from raylib because it only has PLATFORM_DESKTOPflag and it defaults to X11 windowing system on Linux.

Look on this info about mlib (GUI toolkit of AzPainter) porting from X11 to Wayland

http://azsky2.html.xdomain.jp/note/wayland/index.html

P.S.: https://github.com/raysan5/raylib/issues/426

Hi @Symbian9, thank you very much for the reference.
Actually, raylib uses internally glfw library to manage Windowing and inputs, that library is used to implement support for Wayland.


Add spanish language support

Adding Spanish language support...

@llstarscreamll I'm really not sure if this should be merged. I feel this should be within your project only. Unless you have different opinion.

Anyway I'm gonna merge this and #119. We'll remove them later if we found they shouldn't be part of the project.

@Mahmoudz, no problem, you're the boss here!! but please, when you have a short free time take a look on #116, thank you in advance!!


Wascally does not re-subscribe to manually started subscriptions on reconnection

If subscribe is set to false on a queue when it's defined, then wascally will not automatically re-establish a subscription to the queue if the connection to Rabbit (or the subscriber channel) is lost.
This leads to unexpected behavior that looks like consumers "just dropping" because wascally will transparently re-establish the connection, exchanges, queues and bindings without issues.
Subscriptions should get automatically re-established regardless of how they were created.

This is handled in rabbot.

Are the changes/additions from arobson/rabbot going to make it back into wascally, or are they diverging at this point?

@openam they're diverging. For the most part the APIs are compatible, the reason for the divergence is that wascally has very different failure semantics (it tries to recover always from everything). With rabbot, I'm scaling back the "magic" so folks using it need to own how their service behaves in the face of some kinds of failures.


Change hints color pallet to match Vomnibar and other HUD elements

The orange/yellow color for the hints looks off place compared to the other UI elements so I changed the foreground, background and border of the hints to match Vomnibar and other HUD elements color pallet.

@gajaza I would like to know which website you used for the screenshots so that I can replicated it in this pull request


Resolve block device symlinks

This allows mounts of devices like /dev/mapper/xxx, which are typically symlinks to /dev/dm-N, to be supported.

Awesome - thank you!


crash after last update

Bugsnag:  TypeError: cb is not a function
at Request. (/home/cerbervs/geartrack-website/node_modules/geartrack/src/correosOldTracker.js:33:13)
at Request._callback (/home/cerbervs/geartrack-website/node_modules/lodash/lodash.js:10067:25)
at Request.requestRetryReply [as reply] (/home/cerbervs/geartrack-website/node_modules/requestretry/index.js:105:19)
at Request. (/home/cerbervs/geartrack-website/node_modules/requestretry/index.js:133:10)
at Request.self.callback (/home/cerbervs/geartrack-website/node_modules/request/request.js:188:22)
at emitTwo (events.js:106:13)
at Request.emit (events.js:194:7)
at Request. (/home/cerbervs/geartrack-website/node_modules/request/request.js:1171:10)
at emitOne (events.js:96:13)
at Request.emit (events.js:191:7)
at IncomingMessage. (/home/cerbervs/geartrack-website/node_modules/request/request.js:1091:12)
at Object.onceWrapper (events.js:293:19)
at emitNone (events.js:91:20)
at IncomingMessage.emit (events.js:188:7)
at endReadableNT (_stream_readable.js:975:12)
at _combinedTickCallback (internal/process/next_tick.js:80:11)
at process._tickDomainCallback (internal/process/next_tick.js:128:9)
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR<EMAIL_ADDRESS>start: node ./bin/www
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the<EMAIL_ADDRESS>start script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
npm ERR! A complete log of this run can be found in:
npm ERR!     /home/cerbervs/.npm/_logs/2017-05-22T10_06_46_305Z-debug.log

Hi,
Try to update the geartrack package: npm install.
Check the package.json to see if the version is correct, geartrack is at version 2..

Hello again, it's working now, for some reason wasn't doing anything on npm install but it's working now, tnks.


Koko running on Linux

Hi everyone,
I'm trying to start the app in Ubuntu 16.04, after running npm install

awk@awk:~/Documents/koko-master$ npm start
npm ERR! Linux 4.4.0-22-generic
npm ERR! argv "/usr/bin/nodejs" "/usr/bin/npm" "start"
npm ERR! node v4.2.6
npm ERR! npm  v3.5.2

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

npm ERR! Please include the following file with any support request:

And the following file (npm-debug.log) would be:
0 info it worked if it ends with ok
1 verbose cli [ '/usr/bin/nodejs', '/usr/bin/npm', 'start' ]
2 info using<EMAIL_ADDRESS>3 info using<EMAIL_ADDRESS>4 verbose stack Error: missing script: start
4 verbose stack     at run (/usr/share/npm/lib/run-script.js:147:19)
4 verbose stack     at /usr/share/npm/lib/run-script.js:57:5
4 verbose stack     at /usr/share/npm/node_modules/read-package-json/read-json.js:345:5
4 verbose stack     at checkBinReferences_ (/usr/share/npm/node_modules/read-package-json/read-json.js:309:45)
4 verbose stack     at final (/usr/share/npm/node_modules/read-package-json/read-json.js:343:3)
4 verbose stack     at then (/usr/share/npm/node_modules/read-package-json/read-json.js:113:5)
4 verbose stack     at /usr/share/npm/node_modules/read-package-json/read-json.js:232:12
4 verbose stack     at /usr/share/npm/node_modules/graceful-fs/graceful-fs.js:76:16
4 verbose stack     at FSReqWrap.readFileAfterClose [as oncomplete] (fs.js:380:3)
5 verbose cwd /home/awk/Documents/koko-master
6 error Linux 4.4.0-22-generic
7 error argv "/usr/bin/nodejs" "/usr/bin/npm" "start"
8 error node v4.2.6
9 error npm  v3.5.2
10 error missing script: start
11 error If you need help, you may report this error at:
11 error     <https://github.com/npm/npm/issues>
12 verbose exit [ 1, true ]

And if I run electron command, it throws:
awk@awk:~/Documents$ electron koko-master
Error opening app
The app provided is not a valid Electron app, please read the docs on how to write one:
https://github.com/electron/electron/tree/v0.37.8/docs

Error: Cannot find module './build/browser/app'

Does anyone have a clue how can I get this running on Ubuntu?
Thanks.

i'm running it fine on arch linux. run npm install && make run

Running, but not running so good though.
I'm sure is just me.. it connects, but to switch between channels, or embed video like the screenshot, or someother features seems to be missing.

is this a copy of #3?

@matikbird I packed a deb_x64 version of koko. It's working fine here.
Elementary OS 0.4.1 Loki - based on Ubuntu 16.04 Xenial. I installed it using Eddy.
It would be great if you could test it. koko_0.2.1_amd64.deb


Waiting compiler done before server listen

Is there a way to await Webpack compiler success before start listening fastify server ?

Hi! Thanks for checking this out!
Can you give a simple example just to be sure I understand correctly? Which version?
I've never tried this - if I understand it correctly - first thing come into my mind, is to use after or ready lifecycle hooks of fastify server.

Sorry, I got a misunderstanding, close question now


feat(test): move logic from Start to New for exporting apiserver cmd and options

Sometimes, we will add FlagConfigFuncs in customize apiserver's StartOptions. This will be blocked while using pkg/test package since there's no StartOptions being registered in the TestEnvironment. Also, if we want to control flags of apiserver, we need to have access permission of the test apiserver's cobra command.
Moreover, lots of operations in the Start function of TestEnvironment seem to do a initialization. I think they should be moved into NewTestEnvironment so that we can export the ApiserverCobraCmd and ApiserverOptions to user to customize their test logic.

/assign @directxman12

No output has been received in the last 10m0s, this potentially indicates a stalled build or something wrong with the build itself.
Check the details on how to adjust your build configuration on: https://docs.travis-ci.com/user/common-build-problems/#build-times-out-because-no-output-was-received

seems it's stucking somewhere at the tests, is it working locally for you?

Fixed a small bug in code, now the ci can be passed


home page updates

Description
Please provide a summary of the pull request and the issue it fixes. Please add necessary details, context, dependencies, explanation of when review is needed (see next section), etc.
Fixes #(add issue number here and remove parentheses)
Review Time Estimate
Please give your idea of how soon this pull request needs to be reviewed by selecting one of the options below. This can be based on the criticality of the issue at hand and/or other relevant factors.

[ ] Immediately
[ ] Within a week
[ ] When possible

Type of changes
Please select a relevant option:

[ ] Bug fix (non-breaking change which fixes an issue).
[ ] New feature (non-breaking change which adds functionality).
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected).
[ ] Other (any another change that does not fall in one of the above categories.)

Checklist:
Please select all applicable options:

[ ] I have signed the Rokwire Contributor License Agreement (CLA). (Any contributor who is not an employee of the University of Illinois whose official duties include contributing to the Rokwire software, or who is not paid by the Rokwire project, needs to sign the CLA before their contribution can be accepted.)
[ ] I have updated the CHANGELOG.
[ ] I have read the Contributor Guidelines.
[ ] I have performed a self-review of my own code.
[ ] I have commented my code, particularly in hard-to-understand areas.
[ ] My change requires updating the documentation.
[ ] I have made necessary changes to the documentation.
[ ] I have added tests related to my changes.
[ ] My changes generate no new warnings.
[ ] New and existing unit tests pass locally with my changes.
[ ] Any dependent changes have been merged and published in downstream modules.

Please fix the merge conflict. Thanks.

There is an error when installing the requirements.txt. Please see the details below:
ERROR: Cannot install -r requirements.txt (line 18) and MarkupSafe==1.1.1 because these package versions have conflicting dependencies.

The conflict is caused by:
    The user requested MarkupSafe==1.1.1
    jinja2 3.0.3 depends on MarkupSafe>=2.0

To fix this you could try to:
1. loosen the range of package versions you've specified
2. remove package versions to allow pip attempt to solve the dependency conflict

ERROR: ResolutionImpossible: for help visit https://pip.pypa.io/en/latest/topics/dependency-resolution/#dealing-with-dependency-conflicts

According to this, updating the MarkupSafe version is the solution. Thanks..

Hi, @bingzhang, the URL redirection is working fine. We can merge this PR after you have had a chance to go through the above comments. Thanks.

-r requirements.txt

sure, can you check it again?

Thanks, Bing. The pip install error is now gone.

Thanks. Merging this PR.


Improving UI of examples grid

The grid of example activities with their demos is not centered which leaves unnecessary empty space on the right side. See here:

I have centered the grid and also made all Demo buttons aligned in a row. This gives a more uniform and professional look to this section.
Result:

Please review @llaske and let me know any changes required.

You're right, it's better like that. Thanks.


Workflow to validate Terraform status for all environments

Is your feature request related to a problem? Please describe.
Terraform environments may drift out of sync (manual/emergency fixes, etc). Terraform validation monitoring will help track if drift occurs.
Describe the solution you'd like
Run terraform plan against test, staging, and prod to see if any changes are pending and/or have occurred outside terraform.

Likely duplicate. Waiting to find original.


Travis CI tests

This is currently configured to run only for pull-requests, not for every push.
Because the tests use /tmp, they cannot run in Docker on Travis, so I had to use sudo. It takes several extra minutes to acquire a machine with sudo access. We'll worry about that some other time.

This passed for me, so it should pass here too. It just takes a long time because of 'sudo'.


ci: fetch full history when cloning for commitlint job

In case the history of the branch is needed (commitlint job), add an
option --history to skip cloning the repository with --depth=1.
See-also: #1395 (was not sufficient)

/test commitlint

/test commitlint


Incomplete Index Component System (ICS)

I have created the basic implementation of indexes and components along with their tests in this PR.
The CMakeLists file has also been split up. Each subdirectory of sim/src will have its own CMakeLists file. Each subdirectory represents a library that is supposed to be independent of any other adjacent directories. Currently I have ics which stores the core ics concepts and structs and util which stores utility types.
Each subdirectory is interpreted as a library in the main CMakeLists file.

LGTM :+1: . Merge at will


Can i use Kirki for wp.org free theme repo and wp.com premium theme repo?

Hi,
Can i use kirki framework in a theme for uploading to wp.org and wp.com?
All the functions and backend things are developed based on review team best practices and code guide lines?
Thanks! 👍

Hey there!
Yes, you can use the plugin in a theme hosted on w.org
You can see instructions on https://aristath.github.io/kirki/docs/advanced/integration.html

Ok, thanks! :)


dont-break hoodie-app-tracker

Instead of having own test, we want to use our new starter application’s test suite using dont-break.
Unfortunately things don’t work yet. @bahmutov could you maybe help us to get it working? That’d be super helpful :)

Interestingly, this fails locally on my Mac, but it seems to work on Travis, all tests pass, but at the end there is some symlink issue: https://travis-ci.org/hoodiehq/hoodie/builds/125444809#L1135
But I can’t get it to work locally on my mac, here’s the log: https://gist.github.com/8d6c65172ad7462cceba47d0c4d07373

Hi @gr2m !
I encounter the same issue when running npm test with node v5.9.1 (npm v3.8.6).
For me, it works when using node v4.4.3 (npm v2.15.1) though.
Since you are using node v4.2.2 and npm v3.8.6 and it fails, it might be an issue with the v3 npm?

Thanks Jan for looking into it!

This got closed due to merge of hoodie-server and hoodie. I’ll reopen it again later


A new release 1.0.3 to support Swift Packages

The new Swift package support has not been released. I wonder if it is possible to make a 1.0.3 release so that the Package.swift version is available?
Thanks in advance.

hello sir, Due to the details that you mentioned version 1.0.3 is required to publish with changes to support the new Swift package.

sure, as soon as possible

Hello, sir. I have just released version 1.0.3, which now includes support for SPM and addresses the uppercase issues in methods. I apologize for the delayed response; I was deeply immersed in developing the PassGuard framework, which was just published yesterday. I would greatly appreciate your feedback and any advice you may have regarding the PassGuard framework. Thank you!
https://github.com/mehrankmlf/PassGuard

Thank you. I will check out PassGuard.

On Sep 9, 2023, at 3:33 AM, Mehran Kamalifard @.***> wrote:
Hello, sir. I have just released version 1.0.3, which now includes support for SPM and addresses the uppercase issues in methods. I apologize for the delayed response; I was deeply immersed in developing the PassGuard framework, which was just published yesterday. I would greatly appreciate your feedback and any advice you may have regarding the PassGuard framework. Thank you!
https://github.com/mehrankmlf/PassGuard
—
Reply to this email directly, view it on GitHub https://github.com/mehrankmlf/SecurityKit/issues/5#issuecomment-1712479706, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAAPEW2B4JGBWLUDPQUHJZDXZRAW3ANCNFSM6AAAAAA4DVXWSE.
You are receiving this because you authored the thread.


The Helm mixin does not allow you to run the --devel flag

In the schema for the mixin I could find no way to set the helm flag --devel allowing me to run dev versions of charts.

Fixed by #38


CAS Client: Use BatchUpdateBlobs

See original issue on GitLab
In GitLab by [Gitlab user @juergbi] on Sep 25, 2018, 09:45
The Remote Execution API includes a BatchUpdateBlobs method for efficient upload of multiple small blobs. The CAS client currently does not use this. We should implement this to improve artifact push performance, especially across high latency network connections.
This depends on server-side support #676. The implementation should gracefully fallback to non-batch upload if the server does not support batch upload.

In GitLab by [Gitlab user @juergbi] on Sep 25, 2018, 09:46
marked this issue as related to #676

In GitLab by [Gitlab user @juergbi] on Sep 30, 2018, 17:13
mentioned in commit 1ebf3ba8a0982303c2b6425eb1679baa8620fd75

In GitLab by [Gitlab user @juergbi] on Sep 30, 2018, 17:17
mentioned in merge request !839

In GitLab by [Gitlab user @juergbi] on Sep 30, 2018, 17:21
assigned to [Gitlab user @juergbi]

In GitLab by [Gitlab user @juergbi] on Oct 1, 2018, 15:58
mentioned in commit f47895c0818059859a2133ce98e1abdc0be00ad3

In GitLab by [Gitlab user @juergbi] on Oct 1, 2018, 16:32
closed via merge request !839

In GitLab by [Gitlab user @juergbi] on Oct 1, 2018, 16:32
mentioned in commit cf00c0a1317dddbab08859dd02c41b38eb35b9b9

In GitLab by [Gitlab user @juergbi] on Oct 1, 2018, 17:19
mentioned in commit 1964ebeba23b6036e5348e3f6cd8ff85737896dd

In GitLab by [Gitlab user @juergbi] on Oct 3, 2018, 08:35
mentioned in commit f585b23314535af51fbd1eb80d695550188cfa99


Add helldivers2 extension

Description

Screencast

Checklist

[x] I read the extension guidelines
[x] I read the documentation about publishing
[x] I ran npm run build and tested this distribution build in Raycast
[x] I checked that files in the assets folder are used by the extension itself
[x] I checked that assets used by the README are placed outside of the metadata folder

@pernielsentikaer Hello! Could you review this one please?

@pernielsentikaer Hello! Thank you for feedback. I tried using built-in use Fetch but it have some problem, i need staggered loading in many places (e.g fetching status requires fetching current season) and it seems impossible to implement with default hook. So i written my own use Fetch that just do nothing if url is undefined. Regarding useCachedPromise i doubt if it actually needed, the info updates very frequently and showing cached information may worse user experience (i think so). But if you think that's really needed i will implement it, no problem

One command is crashing for me, can you look into what's going on

09:03:58.744 TypeError: Cannot read properties of undefined (reading 'setting')
    at Command (/Users/pernielsentikaer/.config/raycast/extensions/helldivers2/major-orders.js:13766:52)
    at Wl (/Applications/Raycast.app/Contents/Resources/RaycastNodeExtensions_RaycastNodeExtensions.bundle/Contents/Resources/api/node_modules/react-reconciler/react-reconciler.production.min.js:5:21246)
    at Kl (/Applications/Raycast.app/Contents/Resources/RaycastNodeExtensions_RaycastNodeExtensions.bundle/Contents/Resources/api/node_modules/react-reconciler/react-reconciler.production.min.js:7:3134)
    at ho (/Applications/Raycast.app/Contents/Resources/RaycastNodeExtensions_RaycastNodeExtensions.bundle/Contents/Resources/api/node_modules/react-reconciler/react-reconciler.production.min.js:7:41965)
    at co (/Applications/Raycast.app/Contents/Resources/RaycastNodeExtensions_RaycastNodeExtensions.bundle/Contents/Resources/api/node_modules/react-reconciler/react-reconciler.production.min.js:7:36991)
    at Ds (/Applications/Raycast.app/Contents/Resources/RaycastNodeExtensions_RaycastNodeExtensions.bundle/Contents/Resources/api/node_modules/react-reconciler/react-reconciler.production.min.js:7:36922)
    at qr (/Applications/Raycast.app/Contents/Resources/RaycastNodeExtensions_RaycastNodeExtensions.bundle/Contents/Resources/api/node_modules/react-reconciler/react-reconciler.production.min.js:7:36779)
    at vu (/Applications/Raycast.app/Contents/Resources/RaycastNodeExtensions_RaycastNodeExtensions.bundle/Contents/Resources/api/node_modules/react-reconciler/react-reconciler.production.min.js:7:33275)
    at io (/Applications/Raycast.app/Contents/Resources/RaycastNodeExtensions_RaycastNodeExtensions.bundle/Contents/Resources/api/node_modules/react-reconciler/react-reconciler.production.min.js:7:32231)
    at Lu (/Applications/Raycast.app/Contents/Resources/RaycastNodeExtensions_RaycastNodeExtensions.bundle/Contents/Resources/api/node_modules/react-reconciler/react-reconciler.production.min.js:1:1694)
09:03:58.806
TypeError: Cannot read properties of undefined (reading 'setting')

Command:major-orders.tsx:33:37

---
30: };
31:
32: export default function Command() {
33:   const { isLoading, assignments } = useAssignments();
34:
35:   return (
36:     <Detail
---

_r:index.js:11:2490
    at ray-navigation-stack
Io:index.js:11:2088

@pernielsentikaer fixed


Despite encountering the error message 'Failed while: Wait for Condition: InitialRolesPopulated: True' during the creation of downstream EKS clusters in Rancher Manager, the downstream clusters are still created in AWS

Rancher Server Setup

Rancher version: 2.6.10
Installation option (Docker install/Helm Chart): Helm

If Helm Chart, Kubernetes Cluster and version (RKE1, RKE2, k3s, EKS, etc): RKE2

Issue Description:
The issue reported is related to the failure of creating a downstream EKS cluster from Rancher Manager. When attempting to create the cluster, the process fails with the error message "Failed while: Wait for Condition: InitialRolesPopulated: True". This issue  1 has been previously reported and is known to the Rancher Manager development team .
However, a new variation of the issue has been identified. In this case, the EKS cluster is created behind Rancher Manager without Rancher Manager's knowledge, but still shows the same error message. This presents a significant problem as it indicates that the issue is not isolated to the Rancher Manager's creation process, but also affects externally created EKS clusters.
This issue is affecting the functionality and reliability of the Rancher Manager.
Attaching Screenshots, rancher and eks controller logs.
eks-config-operator.log
Uploading rancher_pod.log…

Facing similar issue on Rancher 2.8.1 with Dashboard 2.8.0.


route_to doesn't work for post routes

I have an issue where I have a form in which I want to set the action to the post route using the route_to function. However, because the context of calling that route_to function is using the HTTPVerb that's not post, it doesn't find the route because they are excluded from the route collection. This seems like a common use case for using route_to.
<form action="<?=route_to('user/insert')?>" method="post">
...
</form>

Route Example:
$routes->post('admin/user/insert', 'UserController::insert', ['as' => 'user/insert']);

Well, damn, you're absolutely correct. Routing was one of the first items that was tackled, and the route_to function wasn't a twinkle in my eye just yet. :) I was ignoring any that weren't in the current method so there were fewer routes to have to parse, but it looks like we'll have to change that....
Any chance you want to make a PR for that?

Sure. The only thing I can think of as a fix is to simply remove HTTPVerb check which as you alluded to, may impact performance slightly.

Yup, that's exactly what I'd do. If we find it impacting performance we can refactor the matching process later.

Kind of a silly question, but how do you normally get the tests to run locally? I tried running phpunit in the root directory and nothing happens. Need to write a few for this update.

No worries. :) I install phpunit through Composer for this, since the Laravel projects I work on require different versions of phpunit. If it's installed that way, I always just do ./vendor/bin/phpunit from the root, because I'm too lazy to setup an alias. :)

I figured out my issues with running the test which had to do some modification I made to the Constants.php file which included other package Constants.
In thinking about this further, wont removing the HTTPVerb check potentially cause issues with GET/POST/DELETE routes with the same URI and causing you to possibly get say the "DELETE" route when doing a "GET" request?

I think the way you did it works great. My initial concern was the resources taken up by the potentially empty arrays for the methods, since arrays used to be fairly expensive.  I've seen some blog posts by Blackfire.io that show that these packed arrays are much cheaper in PHP 7.

Actually, after thinking about this implementation more, we could potentially have an issue if a route with the same URI uses add (which uses "*" array key) and another route uses say post and is declared before the add route. The add route would always be overwritten regardless of when it was added in the order because of the array_merge order. This is the line:
$collection = array_merge($this->routes['*'], $this->routes[$verb]);

I'm now thinking the string prefix approach may be better here. I'll work on it and send in a pull request for you to review.

I got pretty far on the string prefix implementation but am having second thoughts now. The implementation I'm working on is giving me issues with named route lookups which are putting me down a smelly code alley that may not be worth it. The pull request array implementation  just puts more importance on routes with a verb which may actually be better anyway.

It seems to me that one with a specific method should normally override the wildcard version. Though, if someone waned to take the easy way and use add to handle a couple of different verbs to the same controller/method, and then wanted to specify only one of them as a different target for say, POST, that should probably still work. Hmm....

I believe that scenario you describe would still work if you add the specific verb after the wildcard. It's when you add the wildcard after the verb that would be the issue if we are wanting the overall ordering of route declaration to determine which route is used. However, I'm now feeling that if you specify a specific route over a wildcard, no matter what the order, that should be used (which should be what's happening now).

Yeah, I agree. It should definitely check the specific verb collection first, and then check the wildcard grouping, and then fail. If that's what you've got, we should be good here, right?


Feature request: add 'uid' and 'gid' options to puppeteer.launch()

I would like to be able to specify uid and gid, i.e. which system user to use for launching the Chromium instance, when calling puppeteer.launch() -- just like if I were using child_process.spawn() directly.
(Or, instead, even just a system username, and puppeteer would resolve it to uid/gid itself.)
Thanks for making an awesome library!

@seeekr this has been already discussed and there's a workaround, see https://github.com/GoogleChrome/puppeteer/issues/745
However, I don't mind if you add the uid and gid to the launcher since you're not the first here already. Feel free to send a PR!


[Feature]: Improve statistics available for package authors

Related Problem
No response
The Elevator Pitch
We want to help package authors create better quality packages that will gain broader adoption in the ecosystem. As part of that, we provide some but not a large variety of statistics to package authors.
Additional Context and Details
What information do you want to see about your package, as a package author?
What parts of creating a quality/popular package are you not sure about?

A suggestion from https://github.com/NuGet/NuGetGallery/issues/8825:

I want to make a badge which would show the number of downloads per user/org.


provisioningProfiles duplicates

Question Checklist

[x] Updated fastlane to the latest version
[x] I read the Contribution Guidelines
[x] I read docs.fastlane.tools
[x] I searched for existing GitHub issues

Question Subject
What tool/action do you have a question about?
sigh & gym
Is this a question about documentation?
No
Is this a question about a third party plugin? (If so, please go to the plugin repository first)
No
Question Description

I have some while loop with sigh and gym inside. In first iteration gym outputs next:
[13:24:05]: Generated plist file with the following values:
[13:24:05]: ▸ -----------------------------------------
[13:24:05]: ▸ {
[13:24:05]: ▸   "signingStyle": "manual",
[13:24:05]: ▸   "method": "app-store",
[13:24:05]: ▸   "provisioningProfiles": {
[13:24:05]: ▸     "<bundle_id>": "<bundle_id> AppStore<PHONE_NUMBER>"
[13:24:05]: ▸   },
[13:24:05]: ▸   "teamID": "<team_id>"
[13:24:05]: ▸ }
[13:24:05]: ▸ -----------------------------------------
In second iteration gym outputs next:
[13:25:39]: Generated plist file with the following values:
[13:25:39]: ▸ -----------------------------------------
[13:25:39]: ▸ {
[13:25:39]: ▸   "signingStyle": "manual",
[13:25:39]: ▸   "method": "app-store",
[13:25:39]: ▸   "provisioningProfiles": {
[13:25:39]: ▸     "<another_bundle_id>": "<another_bundle_id> AppStore<PHONE_NUMBER>",
[13:25:39]: ▸    "<bundle_id>": "<bundle_id> AppStore<PHONE_NUMBER>"
[13:25:39]: ▸   },
[13:25:39]: ▸   "teamID": "<team_id>"
[13:25:39]: ▸ }
[13:25:39]: ▸ -----------------------------------------
So in 20th iteration it will contain 20 provisioning profiles.
How can I clean provisioningProfiles? Because they crashes command line with too much args after 20+ iterations

Can you please share your Fastfile with the lane that contains this while loop? This is probably a use case that wasn't considered when creating the code that includes the profiles here.

@janpio Sorry, but I have long afk period can't get into code base now. Currently can say how I've fixed it:
Actions.lane_context[SharedValues::SIGH_PROFILE_PATHS] = nil

@janpio Sorry, but I have long afk period can't get into code base now. Currently can say how I've fixed it:
Actions.lane_context[SharedValues::SIGH_PROFILE_PATHS] = nil

Yep, that's what I suspected - running sigh always adds the new paths to that array. We would have to find a way to have this reset on each new invocation - or similar. Please post your code when you get access back to it, then we can see if this would actually help here. (No pressure here, just respond to the issue when @fastlane-bot will try to close it in a month or two to keep it open.) Thanks!


Component variant switcher

User need:
A user needs to be able to see all the available variants to a component without having to scroll through the whole page.
Proposed solution:
Collapsing all the component example windows into 1, with an added component variant switcher in the form of a list of radio buttons to allow users to switch between different variants of the component. This also shortens our component pages significantly, so we avoid the loooong scroll.

FYI @designertyler @jeanservaas coz the previous issue on Component example window got closed :D

not stale

Audit of variant switchers in competitors
###Polaris

Salesforce
Turns out Salesforce just updated to list out all the variants instead, but providing an additional right side nav for selecting different variants.

Material
List out variants in the side nav, as the 3rd level.

Polaris also adds window sizing to allow users to see responsiveness of the component:

not stale

This is not stale!


Allow passing DDC module names on the CLI

Today we calculate module names based on the modulePath but we need to be able to specify a module name that doesn't match the path.

yeah, we definitely need to support this.
I believe it's covered by https://github.com/dart-lang/sdk/issues/32272 ... I'll add info to the description to make sure we cover this