text:
Sensors unavailable

System Health details
System Information

version
core-2024.1.3

installation_type
Home Assistant OS

dev
false

hassio
true

docker
true

user
root

virtualenv
false

python_version
3.11.6

os_name
Linux

os_version
6.1.63-haos-raspi

arch
aarch64

timezone
Europe/Amsterdam

config_dir
/config

Home Assistant Community Store

GitHub API
ok

GitHub Content
ok

GitHub Web
ok

GitHub API Calls Remaining
4993

Installed Version
1.33.0

Stage
running

Available Repositories
1385

Downloaded Repositories
31

HACS Data
ok

Home Assistant Cloud

logged_in
false

can_reach_cert_server
ok

can_reach_cloud_auth
ok

can_reach_cloud
ok

Home Assistant Supervisor

host_os
Home Assistant OS 11.4

update_channel
stable

supervisor_version
supervisor-2023.12.0

agent_version
1.6.0

docker_version
24.0.7

disk_total
13.7 GB

disk_used
8.2 GB

healthy
true

supported
true

board
rpi4-64

supervisor_api
ok

version_api
ok

installed_addons
ESPHome (2023.12.6)

Dashboards

dashboards
4

resources
24

views
6

mode
storage

Recorder

oldest_recorder_run
January 8, 2024 at 15:57

current_recorder_run
January 14, 2024 at 22:53

estimated_db_size
214.23 MiB

database_engine
sqlite

database_version
3.41.2

Checklist

[X] I have read the FAQ to see if there is a known solution to my problem.
[X] I have enabled debug logging for my installation.
[X] I have filled out the issue template to the best of my ability.
[X] This issue only contains 1 issue (if you have multiple issues, open one issue for each issue).
[X] This issue is not a duplicate issue of currently previous issues..

Describe the issue
Device power sensors are unavailable when device is offline, even when "Ignore unavailable state" is enabled.
Reproduction steps

Make sure Ignore unavailable state is enabled
Let device go offline
See sensors go unavailable too

Debug logs
2024-01-16 09:36:36.695 DEBUG (MainThread) [custom_components.powercalc.sensors.power] Creating power sensor (entity_id=media_player.playstation_4 entity_category=None, sensor_name=Playstation 4 power strategy=fixed manufacturer= model= unique_id=powercalc_playstation_4)
2024-01-16 09:36:36.695 DEBUG (MainThread) [custom_components.powercalc.sensors.energy] Creating energy sensor: Playstation 4 energy
2024-01-16 09:36:36.697 DEBUG (MainThread) [custom_components.powercalc.sensors.abstract] Binding sensor.spot_werkkamer_1_power to device 7b39b115e9d059187336f0cba77d4863
2024-01-16 09:36:36.700 INFO (MainThread) [homeassistant.components.sensor] Setting up powercalc.sensor
2024-01-16 09:36:36.701 DEBUG (MainThread) [custom_components.powercalc.sensors.power] Creating power sensor (entity_id=media_player.sony_kd_49xf7596 entity_category=None, sensor_name=Sony TV power strategy=fixed manufacturer= model= unique_id=powercalc_sonytv)
2024-01-16 09:36:36.701 DEBUG (MainThread) [custom_components.powercalc.sensors.energy] Creating energy sensor: Sony TV energy
2024-01-16 09:36:36.703 DEBUG (MainThread) [custom_components.powercalc.sensors.abstract] Binding sensor.spot_werkkamer_2_power to device b72dc497f7c360ad3f0b3c2f5fe9ab7d
2024-01-16 09:36:36.708 INFO (MainThread) [homeassistant.components.sensor] Setting up powercalc.sensor
2024-01-16 09:36:36.709 DEBUG (MainThread) [custom_components.powercalc.discovery] light.lamp_boekenkast_1: Auto discovered model (manufacturer=MiBoxer, model=Single color LED controller (FUT036Z))
2024-01-16 09:36:36.709 DEBUG (MainThread) [custom_components.powercalc.sensors.power] Creating power sensor (entity_id=light.lamp_boekenkast_1 entity_category=None, sensor_name=Lamp Boekenkast power strategy=lut manufacturer=signify model=LWV002 unique_id=powercalc_lamp_boekenkast)
2024-01-16 09:36:36.710 DEBUG (MainThread) [custom_components.powercalc.strategy.lut] Loading LUT data file: /config/custom_components/powercalc/power_profile/../data/signify/LWV001/brightness.csv.gz
2024-01-16 09:36:36.714 DEBUG (MainThread) [custom_components.powercalc.strategy.lut] LUT file loaded: 255 lines
2024-01-16 09:36:36.716 DEBUG (MainThread) [custom_components.powercalc.sensors.abstract] Binding sensor.playstation_4_power to device a547c885db99f7bcd10527293ffcedbe
2024-01-16 09:36:36.717 DEBUG (MainThread) [custom_components.powercalc.sensors.abstract] Binding sensor.playstation_4_energy to device a547c885db99f7bcd10527293ffcedbe
2024-01-16 09:36:36.725 INFO (MainThread) [homeassistant.components.sensor] Setting up powercalc.sensor
2024-01-16 09:36:36.726 DEBUG (MainThread) [custom_components.powercalc.sensors.energy] Forced energy sensor generation for the power sensor 'sensor.dream_router_flex_mini_meterkast_poe_power'
2024-01-16 09:36:36.726 DEBUG (MainThread) [custom_components.powercalc.sensors.energy] Creating energy sensor: Flex Mini (Meterkast) energy
2024-01-16 09:36:36.728 DEBUG (MainThread) [custom_components.powercalc.sensors.abstract] Binding sensor.sony_tv_power to device 66a3d8f41ad0765593749a4dccdd3cd3
2024-01-16 09:36:36.730 DEBUG (MainThread) [custom_components.powercalc.sensors.abstract] Binding sensor.sony_tv_energy to device 66a3d8f41ad0765593749a4dccdd3cd3
2024-01-16 09:36:36.738 INFO (MainThread) [homeassistant.components.sensor] Setting up powercalc.sensor
2024-01-16 09:36:36.738 DEBUG (MainThread) [custom_components.powercalc.sensors.energy] Forced energy sensor generation for the power sensor 'sensor.dream_router_flex_mini_woonkamer_poe_power'
2024-01-16 09:36:36.739 DEBUG (MainThread) [custom_components.powercalc.sensors.energy] Creating energy sensor: Flex Mini (Woonkamer) energy
2024-01-16 09:36:36.740 DEBUG (MainThread) [custom_components.powercalc.sensors.abstract] Binding sensor.lamp_boekenkast_power to device b1d67908f52d0729b51c0e60edd229b9
2024-01-16 09:36:36.748 INFO (MainThread) [homeassistant.components.sensor] Setting up powercalc.sensor
2024-01-16 09:36:36.749 DEBUG (MainThread) [custom_components.powercalc.discovery] media_player.soundtouch_300_2: Auto discovered model (manufacturer=Bose Corporation, model=SoundTouch 300)
2024-01-16 09:36:36.755 DEBUG (MainThread) [custom_components.powercalc.sensors.power] Creating power sensor (entity_id=media_player.soundtouch_300_2 entity_category=None, sensor_name=SoundTouch 300 power strategy=linear manufacturer=bose model=767520-2100 unique_id=Powercalc_soundtouch_300)
2024-01-16 09:36:36.756 DEBUG (MainThread) [custom_components.powercalc.sensors.energy] Creating energy sensor: SoundTouch 300 energy
2024-01-16 09:36:36.757 DEBUG (MainThread) [custom_components.powercalc.sensors.abstract] Binding sensor.flex_mini_meterkast_energy to device a695df2ab1955ced2f5fa56d66a3059d
2024-01-16 09:36:36.764 INFO (MainThread) [homeassistant.components.sensor] Setting up powercalc.sensor
2024-01-16 09:36:36.765 DEBUG (MainThread) [custom_components.powercalc.discovery] media_player.soundtouch_keuken_2: Auto discovered model (manufacturer=Bose Corporation, model=SoundTouch 10)
2024-01-16 09:36:36.765 DEBUG (MainThread) [custom_components.powercalc.sensors.power] Creating power sensor (entity_id=media_player.soundtouch_keuken_2 entity_category=None, sensor_name=SoundTouch Keuken power strategy=linear manufacturer=bose model=416776 unique_id=Powercalc_soundtouch_keuken)
2024-01-16 09:36:36.766 DEBUG (MainThread) [custom_components.powercalc.sensors.energy] Creating energy sensor: SoundTouch Keuken energy
2024-01-16 09:36:36.768 DEBUG (MainThread) [custom_components.powercalc.sensors.abstract] Binding sensor.flex_mini_woonkamer_energy to device a695df2ab1955ced2f5fa56d66a3059d
2024-01-16 09:36:36.776 INFO (MainThread) [homeassistant.components.sensor] Setting up powercalc.sensor
2024-01-16 09:36:36.777 DEBUG (MainThread) [custom_components.powercalc.discovery] media_player.soundtouch_werkkamer_2: Auto discovered model (manufacturer=Bose Corporation, model=SoundTouch 10)
2024-01-16 09:36:36.777 DEBUG (MainThread) [custom_components.powercalc.sensors.power] Creating power sensor (entity_id=media_player.soundtouch_werkkamer_2 entity_category=None, sensor_name=SoundTouch Werkkamer power strategy=linear manufacturer=bose model=416776 unique_id=Powercalc_soundtouch_werkkamer)
2024-01-16 09:36:36.777 DEBUG (MainThread) [custom_components.powercalc.sensors.energy] Creating energy sensor: SoundTouch Werkkamer energy
2024-01-16 09:36:36.779 DEBUG (MainThread) [custom_components.powercalc.sensors.abstract] Binding sensor.soundtouch_300_power to device fea85c34e6d7a95e44c26a75fd05a59a
2024-01-16 09:36:36.785 DEBUG (MainThread) [custom_components.powercalc.sensors.abstract] Binding sensor.soundtouch_300_energy to device fea85c34e6d7a95e44c26a75fd05a59a
2024-01-16 09:36:36.791 INFO (MainThread) [homeassistant.components.sensor] Setting up powercalc.sensor
2024-01-16 09:36:36.792 DEBUG (MainThread) [custom_components.powercalc.discovery] light.spot_wc_1: Auto discovered model (manufacturer=Signify Netherlands B.V., model=Hue white GU10 bluetooth (LWG004))
2024-01-16 09:36:36.793 DEBUG (MainThread) [custom_components.powercalc.sensors.power] Creating power sensor (entity_id=light.spot_wc_1 entity_category=None, sensor_name=Spot WC (1) power strategy=lut manufacturer=signify model=LWG004 unique_id=pc_0x00178801083c6d51_light_zigbee2mqtt)
2024-01-16 09:36:36.793 DEBUG (MainThread) [custom_components.powercalc.sensors.energy] Creating energy sensor: Spot WC (1) energy
2024-01-16 09:36:36.794 DEBUG (MainThread) [custom_components.powercalc.sensors.abstract] Binding sensor.soundtouch_keuken_power to device 4e50cf55892148f8e8224b909649a989
2024-01-16 09:36:36.800 DEBUG (MainThread) [custom_components.powercalc.sensors.abstract] Binding sensor.soundtouch_keuken_energy to device 4e50cf55892148f8e8224b909649a989
2024-01-16 09:36:36.802 DEBUG (MainThread) [custom_components.powercalc.sensors.group] sensor.speakers_energy: Recalculate, current value: 14
2024-01-16 09:36:36.803 DEBUG (MainThread) [custom_components.powercalc.sensors.group] skipping state for sensor.woonkamer_energy, sensor unavailable or unknown
2024-01-16 09:36:36.803 DEBUG (MainThread) [custom_components.powercalc.sensors.group] delta for entity sensor.soundtouch_keuken_energy: 0.0003, prev=3.2726, cur=3.2729
2024-01-16 09:36:36.803 DEBUG (MainThread) [custom_components.powercalc.sensors.group] skipping state for sensor.soundtouch_300_energy, sensor unavailable or unknown
2024-01-16 09:36:36.803 DEBUG (MainThread) [custom_components.powercalc.sensors.group] sensor.speakers_energy: New value: 14.7370
2024-01-16 09:36:36.805 INFO (MainThread) [homeassistant.components.sensor] Setting up powercalc.sensor
2024-01-16 09:36:36.806 DEBUG (MainThread) [custom_components.powercalc.discovery] switch.lsc_stekker: Auto discovered model (manufacturer=Tuya, model=Tuya generic (bfccd4355128c7862bwdgj))
2024-01-16 09:36:36.806 DEBUG (MainThread) [custom_components.powercalc.sensors.power] Creating power sensor (entity_id=switch.lsc_stekker entity_category=None, sensor_name=LSC Stekker Device Power strategy=fixed manufacturer=tuya model=TS011F unique_id=powercalc_lsc_stekker)
2024-01-16 09:36:36.807 DEBUG (MainThread) [custom_components.powercalc.sensors.energy] Creating energy sensor: LSC Stekker Device Energy
2024-01-16 09:36:36.808 DEBUG (MainThread) [custom_components.powercalc.sensors.abstract] Binding sensor.soundtouch_werkkamer_power to device 4fd595c83b32f2ce1847abb9918c17b8
2024-01-16 09:36:36.813 DEBUG (MainThread) [custom_components.powercalc.sensors.abstract] Binding sensor.soundtouch_werkkamer_energy to device 4fd595c83b32f2ce1847abb9918c17b8
2024-01-16 09:36:36.821 INFO (MainThread) [homeassistant.components.sensor] Setting up powercalc.sensor
2024-01-16 09:36:36.821 DEBUG (MainThread) [custom_components.powercalc.sensors.energy] Forced energy sensor generation for the power sensor 'sensor.lsc_stekker_vermogen'
2024-01-16 09:36:36.821 DEBUG (MainThread) [custom_components.powercalc.sensors.energy] Creating energy sensor: Oven energy
2024-01-16 09:36:36.823 DEBUG (MainThread) [custom_components.powercalc.sensors.abstract] Binding sensor.spot_wc_1_power to device 77b936d659f77a644e27270b4bb8bf39
2024-01-16 09:36:36.824 DEBUG (MainThread) [custom_components.powercalc.sensors.abstract] Binding sensor.spot_wc_1_energy to device 77b936d659f77a644e27270b4bb8bf39
2024-01-16 09:36:36.828 INFO (MainThread) [homeassistant.components.sensor] Setting up powercalc.sensor
2024-01-16 09:36:36.829 DEBUG (MainThread) [custom_components.powercalc.sensors.group] Creating grouped power sensor: Outlets power (entity_id=sensor.outlets_power)
2024-01-16 09:36:36.829 DEBUG (MainThread) [custom_components.powercalc.sensors.group] Creating grouped energy sensor: Outlets energy (entity_id=sensor.outlets_energy)
2024-01-16 09:36:36.830 DEBUG (MainThread) [custom_components.powercalc.sensors.abstract] Binding sensor.lsc_stekker_device_power to device 555885bcea4342ecfb9a0abd7cbe2439
2024-01-16 09:36:36.833 DEBUG (MainThread) [custom_components.powercalc.sensors.abstract] Binding sensor.lsc_stekker_device_energy to device 555885bcea4342ecfb9a0abd7cbe2439
2024-01-16 09:36:36.837 DEBUG (MainThread) [custom_components.powercalc.sensors.power] Creating power sensor (entity_id=light.stekker_1 entity_category=None, sensor_name=Stekker power strategy=fixed manufacturer= model= unique_id=Powercalc_Stekker)
2024-01-16 09:36:36.837 DEBUG (MainThread) [custom_components.powercalc.sensors.energy] Creating energy sensor: Stekker energy
2024-01-16 09:36:36.838 DEBUG (MainThread) [custom_components.powercalc.sensors.abstract] Binding sensor.oven_energy to device 555885bcea4342ecfb9a0abd7cbe2439
2024-01-16 09:36:36.845 DEBUG (MainThread) [custom_components.powercalc.sensors.group] sensor.outlets_energy: Restoring state: 0.0644
2024-01-16 09:36:36.852 DEBUG (MainThread) [custom_components.powercalc.sensors.abstract] Binding sensor.stekker_power to device d7f1ac1c6199f19accbdd84ea97946c3
2024-01-16 09:36:36.854 DEBUG (MainThread) [custom_components.powercalc.sensors.abstract] Binding sensor.stekker_energy to device d7f1ac1c6199f19accbdd84ea97946c3
2024-01-16 09:36:36.862 INFO (MainThread) [homeassistant.components.device_tracker] Setting up ibeacon.device_tracker
2024-01-16 09:36:36.863 INFO (MainThread) [homeassistant.components.sensor] Setting up ibeacon.sensor
2024-01-16 09:36:36.877 INFO (MainThread) [homeassistant.components.sensor] Setting up nest.sensor
2024-01-16 09:36:36.878 INFO (MainThread) [homeassistant.components.camera] Setting up nest.camera
2024-01-16 09:36:36.879 INFO (MainThread) [homeassistant.components.climate] Setting up nest.climate
2024-01-16 09:36:37.025 INFO (MainThread) [homeassistant.bootstrap] Home Assistant initialized in 34.26s
2024-01-16 09:36:37.026 INFO (MainThread) [homeassistant.core] Starting Home Assistant
2024-01-16 09:36:37.062 INFO (MainThread) [custom_components.hacs] Stage changed: startup
2024-01-16 09:36:37.063 DEBUG (MainThread) [custom_components.powercalc.sensors.power] light.lamp_eettafel_1: Source entity has an invalid state, setting power sensor to unavailable
2024-01-16 09:36:37.063 DEBUG (MainThread) [custom_components.powercalc.sensors.power] light.spot_woonkamer_1: Source entity has an invalid state, setting power sensor to unavailable
2024-01-16 09:36:37.064 DEBUG (MainThread) [custom_components.powercalc.sensors.power] light.lamp_woonkamer_1: Source entity has an invalid state, setting power sensor to unavailable
2024-01-16 09:36:37.064 DEBUG (MainThread) [custom_components.powercalc.sensors.power] media_player.woonkamer: State changed to "off". Power:1.65
2024-01-16 09:36:37.065 DEBUG (MainThread) [custom_components.powercalc.sensors.power] device_tracker.dream_router: State changed to "home". Power:14.30
2024-01-16 09:36:37.065 DEBUG (MainThread) [custom_components.powercalc.sensors.power] light.rgb_slaapkamer_1: Source entity has an invalid state, setting power sensor to unavailable
2024-01-16 09:36:37.066 DEBUG (MainThread) [custom_components.powercalc.sensors.power] light.rgb_spiegel_1: Source entity has an invalid state, setting power sensor to unavailable
2024-01-16 09:36:37.066 DEBUG (MainThread) [custom_components.powercalc.sensors.power] light.rgb_tv_1: Source entity has an invalid state, setting power sensor to unavailable
2024-01-16 09:36:37.067 DEBUG (MainThread) [custom_components.powercalc.sensors.power] light.spot_keuken_1: Source entity has an invalid state, setting power sensor to unavailable
2024-01-16 09:36:37.067 DEBUG (MainThread) [custom_components.powercalc.sensors.power] light.spot_keuken_2: Source entity has an invalid state, setting power sensor to unavailable
2024-01-16 09:36:37.067 DEBUG (MainThread) [custom_components.powercalc.sensors.power] light.spot_hal_1: Source entity has an invalid state, setting power sensor to unavailable
2024-01-16 09:36:37.067 DEBUG (MainThread) [custom_components.powercalc.sensors.power] light.spot_hal_2: Source entity has an invalid state, setting power sensor to unavailable
2024-01-16 09:36:37.068 DEBUG (MainThread) [custom_components.powercalc.sensors.power] light.spot_hal_3: Source entity has an invalid state, setting power sensor to unavailable
2024-01-16 09:36:37.068 DEBUG (MainThread) [custom_components.powercalc.sensors.power] light.spot_werkkamer_1: Source entity has an invalid state, setting power sensor to unavailable
2024-01-16 09:36:37.068 DEBUG (MainThread) [custom_components.powercalc.sensors.power] light.spot_werkkamer_2: Source entity has an invalid state, setting power sensor to unavailable
2024-01-16 09:36:37.069 DEBUG (MainThread) [custom_components.powercalc.sensors.power] media_player.playstation_4: Source entity has an invalid state, setting power sensor to unavailable
2024-01-16 09:36:37.069 DEBUG (MainThread) [custom_components.powercalc.sensors.power] media_player.sony_kd_49xf7596: State changed to "off". Power:2.50
2024-01-16 09:36:37.069 DEBUG (MainThread) [custom_components.powercalc.sensors.power] light.lamp_boekenkast_1: Source entity has an invalid state, setting power sensor to unavailable
2024-01-16 09:36:37.070 DEBUG (MainThread) [custom_components.powercalc.sensors.power] media_player.soundtouch_300_2: State changed to "off". Power:1.50
2024-01-16 09:36:37.083 DEBUG (MainThread) [custom_components.powercalc.sensors.power] media_player.soundtouch_keuken_2: State changed to "off". Power:1.50
2024-01-16 09:36:37.084 DEBUG (MainThread) [custom_components.powercalc.sensors.power] media_player.soundtouch_werkkamer_2: State changed to "off". Power:1.50
2024-01-16 09:36:37.085 DEBUG (MainThread) [custom_components.powercalc.sensors.power] light.spot_wc_1: Source entity has an invalid state, setting power sensor to unavailable
2024-01-16 09:36:37.085 DEBUG (MainThread) [custom_components.powercalc.sensors.power] switch.lsc_stekker: State changed to "on". Power:0.39
2024-01-16 09:36:37.086 DEBUG (MainThread) [custom_components.powercalc.sensors.power] light.stekker_1: Source entity has an invalid state, setting power sensor to unavailable
2024-01-16 09:36:37.553 DEBUG (MainThread) [custom_components.powercalc.sensors.group] sensor.network_energy: Recalculate, current value: 26
2024-01-16 09:36:37.553 DEBUG (MainThread) [custom_components.powercalc.sensors.group] delta for entity sensor.dream_router_energy: 0.0000, prev=26.0135, cur=26.0135
2024-01-16 09:36:37.554 DEBUG (MainThread) [custom_components.powercalc.sensors.group] sensor.network_energy: New value: 26.0137
2024-01-16 09:36:37.662 INFO (MainThread) [custom_components.hacs] Loading removed repositories
2024-01-16 09:36:38.061 INFO (MainThread) [homeassistant.components.automation.script] Initialized trigger script
2024-01-16 09:36:38.114 DEBUG (MainThread) [custom_components.powercalc.sensors.power] light.spot_keuken_2: Source entity has an invalid state, setting power sensor to unavailable
2024-01-16 09:36:38.115 DEBUG (MainThread) [custom_components.powercalc.sensors.power] light.lamp_boekenkast_1: Source entity has an invalid state, setting power sensor to unavailable
2024-01-16 09:36:38.115 DEBUG (MainThread) [custom_components.powercalc.sensors.power] light.rgb_tv_1: Source entity has an invalid state, setting power sensor to unavailable
2024-01-16 09:36:38.116 DEBUG (MainThread) [custom_components.powercalc.sensors.power] light.rgb_slaapkamer_1: Source entity has an invalid state, setting power sensor to unavailable
2024-01-16 09:36:38.116 DEBUG (MainThread) [custom_components.powercalc.sensors.power] light.spot_keuken_1: Source entity has an invalid state, setting power sensor to unavailable
2024-01-16 09:36:38.116 DEBUG (MainThread) [custom_components.powercalc.sensors.power] light.spot_woonkamer_1: Source entity has an invalid state, setting power sensor to unavailable
2024-01-16 09:36:38.117 DEBUG (MainThread) [custom_components.powercalc.sensors.power] light.spot_hal_1: Source entity has an invalid state, setting power sensor to unavailable
2024-01-16 09:36:38.117 DEBUG (MainThread) [custom_components.powercalc.sensors.power] light.spot_hal_2: Source entity has an invalid state, setting power sensor to unavailable
2024-01-16 09:36:38.117 DEBUG (MainThread) [custom_components.powercalc.sensors.power] light.spot_hal_3: Source entity has an invalid state, setting power sensor to unavailable
2024-01-16 09:36:38.118 DEBUG (MainThread) [custom_components.powercalc.sensors.power] light.spot_werkkamer_1: Source entity has an invalid state, setting power sensor to unavailable
2024-01-16 09:36:38.118 DEBUG (MainThread) [custom_components.powercalc.sensors.power] light.spot_werkkamer_2: Source entity has an invalid state, setting power sensor to unavailable
2024-01-16 09:36:38.118 DEBUG (MainThread) [custom_components.powercalc.sensors.power] light.lamp_woonkamer_1: Source entity has an invalid state, setting power sensor to unavailable
2024-01-16 09:36:38.119 DEBUG (MainThread) [custom_components.powercalc.sensors.power] light.lamp_eettafel_1: Source entity has an invalid state, setting power sensor to unavailable
2024-01-16 09:36:38.119 DEBUG (MainThread) [custom_components.powercalc.sensors.power] light.rgb_spiegel_1: Source entity has an invalid state, setting power sensor to unavailable
2024-01-16 09:36:38.119 DEBUG (MainThread) [custom_components.powercalc.sensors.power] light.spot_wc_1: Source entity has an invalid state, setting power sensor to unavailable
2024-01-16 09:36:38.150 DEBUG (MainThread) [custom_components.powercalc.sensors.power] light.stekker_1: State changed to "off". Power:0.23
2024-01-16 09:36:38.223 INFO (SyncWorker_10) [homeassistant.loader] Loaded zha from homeassistant.components.zha
2024-01-16 09:36:38.310 INFO (MainThread) [homeassistant.components.sensor] Setting up powercalc.sensor
2024-01-16 09:36:38.317 INFO (SyncWorker_3) [homeassistant.loader] Loaded soundtouch from homeassistant.components.soundtouch
2024-01-16 09:36:38.344 DEBUG (MainThread) [custom_components.powercalc.sensors.energy] Creating energy sensor: All standby energy
2024-01-16 09:36:38.355 INFO (MainThread) [custom_components.hacs] Loading known repositories
2024-01-16 09:36:49.429 INFO (MainThread) [zigpy.serial] Using pyserial-asyncio-fast in place of pyserial-asyncio
2024-01-16 09:36:52.421 INFO (MainThread) [custom_components.hacs] Stage changed: running
2024-01-16 09:36:53.311 INFO (SyncWorker_0) [homeassistant.loader] Loaded androidtv_remote from homeassistant.components.androidtv_remote
2024-01-16 09:36:53.324 INFO (SyncWorker_10) [homeassistant.loader] Loaded unifiprotect from homeassistant.components.unifiprotect
2024-01-16 09:37:02.371 DEBUG (MainThread) [custom_components.powercalc.sensors.power] switch.lsc_stekker: State changed to "on". Power:0.39
2024-01-16 09:37:11.734 WARNING (MainThread) [homeassistant.components.ps4.media_player] PS4 could not be reached
2024-01-16 09:37:13.406 DEBUG (MainThread) [custom_components.powercalc.sensors.power] switch.lsc_stekker: State changed to "on". Power:0.39
2024-01-16 09:37:15.700 DEBUG (MainThread) [custom_components.powercalc.sensors.power] light.spot_hal_1: State changed to "off". Power:0.44
2024-01-16 09:37:15.756 DEBUG (MainThread) [custom_components.powercalc.sensors.power] light.spot_keuken_1: State changed to "off". Power:0.44
2024-01-16 09:37:15.809 DEBUG (MainThread) [custom_components.powercalc.sensors.power] light.spot_hal_2: State changed to "off". Power:0.44
2024-01-16 09:37:15.824 DEBUG (MainThread) [custom_components.powercalc.sensors.power] light.spot_hal_3: State changed to "off". Power:0.44
2024-01-16 09:37:15.825 DEBUG (MainThread) [custom_components.powercalc.sensors.power] light.spot_werkkamer_2: State changed to "off". Power:0.44
2024-01-16 09:37:16.108 DEBUG (MainThread) [custom_components.powercalc.sensors.power] light.spot_keuken_2: State changed to "off". Power:0.44
2024-01-16 09:37:16.128 DEBUG (MainThread) [custom_components.powercalc.sensors.power] light.lamp_eettafel_1: State changed to "off". Power:0.27
2024-01-16 09:37:16.144 DEBUG (MainThread) [custom_components.powercalc.sensors.power] light.rgb_tv_1: State changed to "off". Power:1.05
2024-01-16 09:37:16.296 DEBUG (MainThread) [custom_components.powercalc.sensors.power] light.spot_werkkamer_1: State changed to "off". Power:0.44
2024-01-16 09:37:16.510 DEBUG (MainThread) [custom_components.powercalc.sensors.power] light.spot_woonkamer_1: State changed to "off". Power:0.25
2024-01-16 09:37:16.525 DEBUG (MainThread) [custom_components.powercalc.sensors.power] light.rgb_spiegel_1: State changed to "off". Power:1.05
2024-01-16 09:37:16.543 DEBUG (MainThread) [custom_components.powercalc.sensors.power] light.lamp_woonkamer_1: State changed to "off". Power:0.27
2024-01-16 09:37:16.804 DEBUG (MainThread) [custom_components.powercalc.sensors.power] light.lamp_boekenkast_1: State changed to "off". Power:0.50
2024-01-16 09:37:16.809 DEBUG (MainThread) [custom_components.powercalc.sensors.power] light.rgb_slaapkamer_1: State changed to "off". Power:1.05
2024-01-16 09:37:24.612 INFO (MainThread) [homeassistant.components.automation.motion_entrance_start] Motion Entrance: Running automation actions
2024-01-16 09:37:24.616 DEBUG (MainThread) [custom_components.powercalc.sensors.power] light.spot_wc_1: State changed to "off". Power:0.25
2024-01-16 09:37:24.624 INFO (MainThread) [homeassistant.components.automation.motion_entrance_start] Motion Entrance: If at step 1: Running automation actions
2024-01-16 09:37:24.629 DEBUG (MainThread) [custom_components.powercalc.sensors.group] sensor.lights_energy: Recalculate, current value: 0
2024-01-16 09:37:24.630 DEBUG (MainThread) [custom_components.powercalc.sensors.group] delta for entity sensor.stekker_energy: 0.0001, prev=0.0262, cur=0.0263
2024-01-16 09:37:24.630 DEBUG (MainThread) [custom_components.powercalc.sensors.group] delta for entity sensor.spot_wc_1_energy: 0.0000, prev=0.1494, cur=0.1494
2024-01-16 09:37:24.630 DEBUG (MainThread) [custom_components.powercalc.sensors.group] sensor.lights_energy: New value: 0.2088
2024-01-16 09:37:57.253 INFO (SyncWorker_3) [homeassistant.loader] Loaded shopping_list from homeassistant.components.shopping_list
2024-01-16 09:37:57.258 INFO (SyncWorker_3) [homeassistant.loader] Loaded dlna_dmr from homeassistant.components.dlna_dmr
2024-01-16 09:37:57.534 DEBUG (MainThread) [custom_components.powercalc.sensors.power] switch.lsc_stekker: State changed to "on". Power:0.39
2024-01-16 09:38:08.577 DEBUG (MainThread) [custom_components.powercalc.sensors.power] switch.lsc_stekker: State changed to "on". Power:0.39
2024-01-16 09:38:19.622 DEBUG (MainThread) [custom_components.powercalc.sensors.power] switch.lsc_stekker: State changed to "on". Power:0.39
2024-01-16 09:38:30.656 DEBUG (MainThread) [custom_components.powercalc.sensors.power] switch.lsc_stekker: State changed to "on". Power:0.39
2024-01-16 09:38:52.754 DEBUG (MainThread) [custom_components.powercalc.sensors.power] switch.lsc_stekker: State changed to "on". Power:0.39
2024-01-16 09:39:13.830 DEBUG (MainThread) [custom_components.powercalc.sensors.power] switch.lsc_stekker: State changed to "on". Power:0.39

Diagnostics dump or YAML config
{
"home_assistant": {
"installation_type": "Home Assistant OS",
"version": "2024.1.3",
"dev": false,
"hassio": true,
"virtualenv": false,
"python_version": "3.11.6",
"docker": true,
"arch": "aarch64",
"timezone": "Europe/Amsterdam",
"os_name": "Linux",
"os_version": "6.1.63-haos-raspi",
"supervisor": "2023.12.0",
"host_os": "Home Assistant OS 11.4",
"docker_version": "24.0.7",
"chassis": "embedded",
"run_as_root": true
},
"custom_components": {
"battery_notes": {
"version": "1.4.0",
"requirements": []
},
"powercalc": {
"version": "v1.9.17",
"requirements": [
"numpy>=1.21.1"
]
},
"hacs": {
"version": "1.33.0",
"requirements": [
"aiogithubapi>=22.10.1"
]
}
},
"integration_manifest": {
"after_dependencies": [
"integration",
"utility_meter"
],
"codeowners": [
"@bramstroker"
],
"config_flow": true,
"dependencies": [
"light",
"group",
"template",
"select",
"utility_meter"
],
"documentation": "https://github.com/bramstroker/homeassistant-powercalc",
"domain": "powercalc",
"iot_class": "local_polling",
"issue_tracker": "https://github.com/bramstroker/homeassistant-powercalc/issues",
"name": "Powercalc",
"requirements": [
"numpy>=1.21.1"
],
"version": "v1.9.17",
"is_built_in": false
},
"data": {
"entry": {
"entry_id": "932e3139863d11d68a99ce4a69bbbfdd",
"version": 2,
"minor_version": 1,
"domain": "powercalc",
"title": "Playstation 4",
"data": {
"mode": "fixed",
"create_energy_sensor": true,
"create_utility_meters": false,
"entity_id": "media_player.playstation_4",
"name": "Playstation 4",
"unique_id": "powercalc_playstation_4",
"standby_power": 1.3,
"fixed": {
"states_power": {
"playing": 75.2,
"paused": 41.8,
"idle": 41.8,
"unknown": 0.2,
"Unknown": 0.2
}
},
"ignore_unavailable_state": true,
"energy_integration_method": "left",
"unavailable_power": 0.2,
"sensor_type": "virtual_power",
"_power_entity": "sensor.playstation_4_power",
"_energy_entity": "sensor.playstation_4_energy"
},
"options": {},
"pref_disable_new_entities": false,
"pref_disable_polling": false,
"source": "user",
"unique_id": "powercalc_playstation_4",
"disabled_by": null
}
}
}

Let's focus on single entity first, as I'm not sure reading your bug report which entity you are experiencing the issue with.
The config entry (diagnostics) you shared is about the media_player.playstation_4.

Let's focus on single entity first, as I'm not sure reading your bug report which entity you are experiencing the issue with.
The config entry (diagnostics) you shared is about the media_player.playstation_4.

That is correct, the PlayStation gives the problem.
When it is in "sleep mode" its working fine. But when it is off, the network connection is inactive and the power sensor goes to unavailable.

I have made a small change. Could you try again by installing the master branch? You can do that in HACS by clicking reinstall, and select master from the list. Also check the "beta" checkbox.
When still not working please also share the actual state of media_player.playstation_4 when you experience the issue. You can find the current state in Developer tools, left menu.

It looks like it is working now.
The media_player.playstation_4 is now showing 0.2 watts (the unavailable power from the settings).

Ok, that's great. Will be released in next version. closing this issue

authors: Jordo-o bramstroker

repo: bramstroker/homeassistant-powercalc


text:
Add Exception instance for TOMLError

Resolves #13.
Hi! First, thanks for the great library. The API is excellent.
I am happy to discover this issue, as I thought of the same thing when using it :slightly_smiling_face:.

Codecov Report

Merging #15 (d44448c) into main (86b0e2c) will decrease coverage by 0.08%.
The diff coverage is 0.00%.

@@            Coverage Diff             @@
##             main      #15      +/-   ##
==========================================
- Coverage   57.72%   57.63%   -0.09%
==========================================
  Files           6        6
  Lines         693      694       +1
  Branches       19       19
==========================================
  Hits          400      400
- Misses        287      288       +1
  Partials        6        6

Impacted Files
Coverage Δ

src/TOML/Error.hs
81.81% <0.00%> (-1.91%)
:arrow_down:

Help us with your feedback. Take ten seconds to tell us how you rate us.

Thanks!

source: gharchive/pull-request

license_type: permissive

license_source: github-api


text:
SSH timeout

Hi there :)
I'm having some trouble with the ssh connection, this is what i'm getting.
Build vsphere-iso' errored after 21 minutes 41 seconds: timeout waiting for SSH
Any clue?
Thanks!
`

same issue, have you found anything on it?

source: gharchive/issue

authors: AkashRajvanshi redfishstix

repo: brandonleegit/PackerBuilds


text:
Unsure why but since .22 by build fails:

I had some @apply 's not working and so I clumsily uninstalled, installed trying to see if maybe I did something wrong - and now it wont build at all.
Totally removed- will build ok.
Add this plugin and follow  https://gridsome.org/docs/assets-css/#tailwind
and now I get
Failed to render /news-story/august
---/node_modules/tailwindcss/tailwind.css:1
(function (exports, require, module, __filename, __dirname) { @tailwind base;
Thought it was the source- so deleted the post and it errored on the next.

Just tested it here on a fresh Gridsome app, and it built without issue. Send a link to your repo.

Ok maybe something I've done. I'll report back

authors: Kainkainkain brandonpittman

license: MIT


text:
Implements chrome.windows.create

Initial work to add support for chrome.windows.create.
Resolves https://github.com/brave/browser-laptop/issues/6789

master:
2fe761f10d1488e1b1f3437c25f088567982c7d5
4.5.x+62.0.3202.38
ea9f8c5a219893ee13c4b899b7fb177d685413c4
4.4.x+61.0.3163.100
eaac5c263b391776c80a77b62afd36f54859a07c

authors: bbondy jonathansampson

repo: brave/muon

license: mit

license_source: bigquery


text:
Refactor Endpoints to Follow RESTful Conventions

Issue Description:
Currently, several endpoints in the route files do not follow standard RESTful conventions. To improve clarity, scalability, and maintainability of the API, these routes should be refactored to follow RESTful best practices.
In REST, the endpoints should be more intuitive and represent resources, using appropriate HTTP methods (GET, POST, PUT, DELETE) to indicate the action being performed.
Proposed Refactor:
We should refactor these endpoints to follow RESTful conventions by:

Use HTTP methods like POST for creation, GET for reading, PUT/PATCH for updating, and DELETE for removal.
Follow resource-oriented URLs, such as /users/{id}, /posts/{id}, and associated actions (e.g., likes, comments) as sub-resources.

Refactor Suggestions:

Follow/Unfollow User:

Current: POST /users/follow
Proposed: POST /users/:userId/follow

Delete User Account:

Current: POST /users/delete
Proposed: DELETE /users/:userId

Create New Post:

Current: POST /posts/newpost
Proposed: POST /posts

Delete Post:

Current: POST /posts/deletepost
Proposed: DELETE /posts/:postId

Like a Post:

Current: POST /posts/likepost
Proposed: POST /posts/:postId/like

Add Comment to a Post:

Current: POST /posts/comment
Proposed: POST /posts/:postId/comments

Delete Comment from a Post:

Current: POST /posts/deletecomment
Proposed: DELETE /posts/:postId/comments/:commentId

Benefits:

Consistency: These changes would align with standard REST principles, making the API easier to understand and use for developers.
Intuitiveness: Each URL would clearly represent the action being performed on a resource.

Yes please

This issue has been assigned to you.

authors: ardatosun braydenidzenga

repo: braydenidzenga/Dev-Dialogue


text:
Run version script for Flutter

This PR updates the outdated versions on podspec for resource resolution..
This script should be run part of pre-release process.

#417

@erdemyerebasmaz  I merged v0.2.1 branch so I think this is no longer necessary.

authors: erdemyerebasmaz roeierez

repo: breez/breez-sdk-liquid


text:
Receive onchain: validate and select fee params

Improve conversion between models::OpeningFeeParams and grpc::OpeningFeeParams

with custom serde parsing into DateTime for easier time operations

Select and validate fee params in receive_onchain
Address TODO in get_longest_valid_opening_fee_params

filter fees that are valid for at least 48h, choose the cheapest

Looks good. I'm not really seeing the full picture yet, will we do a PR of the dynamic_fees branch when we're done?

Yes, there will be a general review of the dynamic_fees branch once all subtasks are complete.

I had to change valid_until back to String, because having it as DateTime caused trouble with uniffi.
I did add however a utility method to convert to date when needed: OpeningFeeParams::valid_until_date().

Added by the last commit:

Require a mandatory OpeningFeeParams arg for BTCReceiveSwap::create_swap_address.
This can come either from the caller (as an arg to receive_onchain or can be looked-up from the LSP.

repo: breez/breez-sdk


text:
bam_filter and count_reads broken by API update

record.qual was deprecated in hts-nim in favor of record.mapping_quality (https://github.com/brentp/hts-nim/issues/14), which requires updates to bam_filter and count_reads. That's the only fix it takes to compile, but are there other field renames that affect these tools?

Thanks for pointing this out. That's all the change that's required. Please let me know any other issues.

authors: brentp filidi

repo: brentp/hts-nim-tools


text:
[core] add missing license headers.

#1249 missed headers when moving things out of Client.java
#1242 missed header on a properties file is added
#1286 missed header on the new pom file

thanks!

repo: brianfrankcooper/YCSB


text:
Added tests for Solr binding

Relies on PR #574. Relates to @busbey  comment about testing the Solr binding https://github.com/brianfrankcooper/YCSB/pull/574#issuecomment-170245724. Will most likely need to be rebased after #574 is merged.

Dammit, did I comment on the wrong PR? Assume all my comments go to the other one then, if so. Sorry. :(

@busbey addressed comments about putting reference to Solr config files and configuring log4j to go to stderr.

@madrob no worries I added links to them in PR #574

@madrob @risdenk addressed in PR #574
cheers

thanks!

authors: busbey ghaughian madrob risdenk


text:
refactor: replace deprecated template provider usage

In Terraform v0.12 and above the terraform_file resource that is part
of the template provider has been replaced with a built-in function
templatefile that is simpler to use.  You can see this mentioned in
the docs at:
https://registry.terraform.io/providers/hashicorp/template/latest/docs/data-sources/file
You can also see that the template provider itself has been
archived: https://github.com/hashicorp/terraform-provider-template
There will therefore be no further updates or builds for it which
becomes a problem for Mac users on the new Apple Silicon chips, it
means that wherever the old and deprecated template provider is used
anyone on an Apple machine with M1 chip will not be able to
successfully run terraform init.
I'm not sure if there is a better way to iterate over all the
variables that need to be passed into the templatefile function as a
map.

LGTM, @JamesWoolfenden PTAL

authors: nimrodkor rosstimson


text:
Project Pulse

I am considering using this library, but I have noticed that there hasn't been any activity for about 7 months or so. Are you still actively maintaining this project?
I have a need which this library does not seem to support. In my app, I create a separate, versioned bundle of my dependencies, so the bundle string looks something like this: 'jquery + lodash + moment'. This plugin seems to only support passing in a vinyl stream file using gulp.src() (which would not work for my use case, as I am directly bundling deps), but I think it would be useful to provide access to the jspm object itself for more custom needs. I could submit a PR for this, but, as I mentioned before, it does not seem like you are reviewing any recent PRs in this project. Please advise.

Thanks for creating the issue.
I indeed don't maintain gulp-jspm anymore, see issue #45 - Looking for a maintainer / fork.

authors: Smolations brillout

repo: brillout/gulp-jspm


text:
Error when importing telefunc that is outside sub-project root in monorepo (metro already configured, and RN is 0.72 which supports symlink)

Folder structure:

project-new-expo/apps has two sub folders:
func -> contains just telefunc files
expo -> contains the expo code which imports the telefunc file

error: ../func/hello.telefunc.ts: /Users/pencilcheck/Projects/project-new-expo/apps/func/hello.telefunc.ts: [telefunc@0.1.67][Bug] You stumbled upon a bug in Telefunc's source code. Reach out at https://github.com/brillout/telefunc/issues/new or https://discord.com/invite/3DYWwk4xRQ and include this error stack (the error stack is usually enough to fix the problem). A maintainer will fix the bug (usually under 24 hours). Don't hesitate to reach out as it makes Telefunc more robust.
Error: [telefunc@0.1.67][Bug] You stumbled upon a bug in Telefunc's source code. Reach out at https://github.com/brillout/telefunc/issues/new or https://discord.com/invite/3DYWwk4xRQ and include this error stack (the error stack is usually enough to fix the problem). A maintainer will fix the bug (usually under 24 hours). Don't hesitate to reach out as it makes Telefunc more robust.
    at transformTelefuncFileClientSideSync (/Users/pencilcheck/Projects/project-new-expo/apps/expo/node_modules/telefunc/dist/cjs/node/transformer/transformTelefuncFileClientSideSync.js:10:24)
    at PluginPass.Program (/Users/pencilcheck/Projects/project-new-expo/apps/expo/node_modules/telefunc/dist/cjs/node/babel/plugin.js:69:115)
    at newFn (/Users/pencilcheck/Projects/project-new-expo/apps/expo/node_modules/@babel/traverse/lib/visitors.js:160:14)
    at NodePath._call (/Users/pencilcheck/Projects/project-new-expo/apps/expo/node_modules/@babel/traverse/lib/path/context.js:46:20)
    at NodePath.call (/Users/pencilcheck/Projects/project-new-expo/apps/expo/node_modules/@babel/traverse/lib/path/context.js:36:17)
    at NodePath.visit (/Users/pencilcheck/Projects/project-new-expo/apps/expo/node_modules/@babel/traverse/lib/path/context.js:82:31)
    at TraversalContext.visitQueue (/Users/pencilcheck/Projects/project-new-expo/apps/expo/node_modules/@babel/traverse/lib/context.js:86:16)
    at TraversalContext.visitSingle (/Users/pencilcheck/Projects/project-new-expo/apps/expo/node_modules/@babel/traverse/lib/context.js:65:19)
    at TraversalContext.visit (/Users/pencilcheck/Projects/project-new-expo/apps/expo/node_modules/@babel/traverse/lib/context.js:109:19)
    at traverseNode (/Users/pencilcheck/Projects/project-new-expo/apps/expo/node_modules/@babel/traverse/lib/traverse-node.js:22:17)
    at traverse (/Users/pencilcheck/Projects/project-new-expo/apps/expo/node_modules/@babel/traverse/lib/index.js:52:34)
    at transformFile (/Users/pencilcheck/Projects/project-new-expo/apps/expo/node_modules/@babel/core/lib/transformation/index.js:82:31)
    at transformFile.next (<anonymous>)
    at run (/Users/pencilcheck/Projects/project-new-expo/apps/expo/node_modules/@babel/core/lib/transformation/index.js:24:12)
    at run.next (<anonymous>)
    at /Users/pencilcheck/Projects/project-new-expo/apps/expo/node_modules/@babel/core/lib/transform-ast.js:23:33
    at Generator.next (<anonymous>)
    at evaluateSync (/Users/pencilcheck/Projects/project-new-expo/apps/expo/node_modules/gensync/index.js:251:28)
    at sync (/Users/pencilcheck/Projects/project-new-expo/apps/expo/node_modules/gensync/index.js:89:14)
    at stopHiding - secret - don't use this - v1 (/Users/pencilcheck/Projects/project-new-expo/apps/expo/node_modules/@babel/core/lib/errors/rewrite-stack-trace.js:47:12)
    at transformFromAstSync (/Users/pencilcheck/Projects/project-new-expo/apps/expo/node_modules/@babel/core/lib/transform-ast.js:43:83)
    at Object.transform (/Users/pencilcheck/Projects/project-new-expo/apps/expo/node_modules/metro-react-native-babel-transformer/src/index.js:201:20)
    at transformJSWithBabel (/Users/pencilcheck/Projects/project-new-expo/apps/expo/node_modules/metro-transform-worker/src/index.js:330:45)
    at transform (/Users/pencilcheck/Projects/project-new-expo/apps/expo/node_modules/metro-transform-worker/src/index.js:461:18)
    at transform (/Users/pencilcheck/Projects/project-new-expo/apps/expo/node_modules/react-native-css-interop/dist/metro/transformer.js:15:16)
    at Object.transform (/Users/pencilcheck/Projects/project-new-expo/apps/expo/node_modules/nativewind/dist/metro/transformer.js:25:40)
    at transformFile (/Users/pencilcheck/Projects/project-new-expo/apps/expo/node_modules/metro/src/DeltaBundler/Worker.flow.js:73:36)
    at Object.transform (/Users/pencilcheck/Projects/project-new-expo/apps/expo/node_modules/metro/src/DeltaBundler/Worker.flow.js:48:10)
    at execFunction (/Users/pencilcheck/Projects/project-new-expo/apps/expo/node_modules/jest-worker/build/workers/processChild.js:137:17)
    at execHelper (/Users/pencilcheck/Projects/project-new-expo/apps/expo/node_modules/jest-worker/build/workers/processChild.js:116:5)
    at execMethod (/Users/pencilcheck/Projects/project-new-expo/apps/expo/node_modules/jest-worker/build/workers/processChild.js:120:5)
    at process.messageListener (/Users/pencilcheck/Projects/project-new-expo/apps/expo/node_modules/jest-worker/build/workers/processChild.js:38:7)

Insert the following line before line 10 of /Users/pencilcheck/Projects/project-new-expo/apps/expo/node_modules/telefunc/dist/cjs/node/transformer/transformTelefuncFileClientSideSync.js and report back the log results.
    const telefuncFilePath = '/' + path_1.posix.relative(appRootDir, id);
+   console.log('telefuncFilePath', telefuncFilePath);
    (0, utils_1.assert)(!telefuncFilePath.startsWith('/.'));

transform[stdout]: telefuncFilePath /../func/hello.telefunc.mjs
Android Bundling failed 1937ms
error: ../func/hello.telefunc.mjs: /Users/pencilcheck/Projects/project-new-expo/apps/func/hello.telefunc.mjs: [telefunc@0.1.67][Bug] You stumbled upon a bug in Telefunc's source code. Reach out at https://github.com/brillout/telefunc/issues/new or https://discord.com/invite/3DYWwk4xRQ and include this error stack (the error stack is usually enough to fix the problem). A maintainer will fix the bug (usually under 24 hours). Don't hesitate to reach out as it makes Telefunc more robust.

Fixed. You should now get an helpful error message instead.

authors: brillout pencilcheck

repo: brillout/telefunc


text:
Lazy loading children when parent is opened

Hi, I have a large set of parents and children. I was wondering if there a way to load children nodes only when parent is clicked to open.
Interactions in a nutshell:

All parents are in collapsed state at the beginning
User clicks a parent item
A loading animation appears under that parent
Then the children of that parent are fetched in the "background"
When that request resolves, the fetched children are rendered inside that parent

Is it possible to achieve these interactions using current features of this package?

Yup, it is possible. I don't have an example of it yet, but you have all the pieces in this package to do it.

@waliurjs how you did it?

Any update?

authors: holy-dev jameskerr waliurjs

repo: brimdata/react-arborist


text:
Additional fixes to Zed lake design doc

The Zed lake design doc has come along far enough that I felt like a table of contents is justified. Then I ran it through a spell/grammar checker and found a bunch more things to fix.

The failure of the markdown link checker appears to be due to the wrccdc pcap archive site currently being unreachable. Hopefully just a temporary outage.

repo: brimdata/zed


text:
Add a couple section headers in language overview doc

I added mention of the Zed language // comment syntax back in #4308 after a community user reported not realizing this concept existed (#4302). Another community user just pointed out via https://github.com/brimdata/zed/issues/4310#issuecomment-2214786576 that the way it's covered in the docs now doesn't currently bubble up nicely in the search results. I'm not 100% certain if their proposed change of adding a section header would improve that, but rather than investing time into setting up a test sandbox to investigate, I spent some time re-reading the page to see if adding a header makes sense regardless.
Looking at it through that lens, indeed, I can see that the coverage as it's been feels a little "tacked on", but I was always had trouble coming up with a better idea. Having a wholly separate page under "Language" at the same level as "Expressions", "Operators" etc. just to briefly mention comments feels like overkill. I also don't see a different existing page into which it would graft nicely as a header-worthy section, though I'm open to suggestion.
The "Overview" page should surely be brief, so I respect the urge to avoid lots of section headers there. However, I did ultimately find that adding a "Search and Analytics" header feels pretty natural to me, so once I've got that, the header for Comments feels a bit more natural, too.
As for the user's point in #4302  about if we should divulge the gotcha here about multi-line /* */ comment syntax being available in ZSON but not Zed language, I'm holding off on that for the moment in hopes it might be easier to just enhance the parser. 🤞

Now that this has been merged and the Zed docs site has been re-indexed by our search tool, I'm pleased to say that a search for "comment" is indeed now showing the top hit being the section in the Language Overview page. 🎉   Thanks for the idea @chrismo!

(Alas, at this moment that's only true if the "Next" docs revision is selected in the drop-down, since these changes weren't in the docs tagged for the most recent GA release. But I do hope to have a new release out quite soon, so this'll continue to improve.)

Looks great!

authors: chrismo philrz


text:
AFP-267 Fix broken images

This will need the absolute paths in the tangerine mdx for images to change to relative paths to work.

Nice work with this!

authors: Noviny qburst-aparna

repo: brisk-docs/brisk-docs


text:
Replace gnomad-public bucket in resource paths

Files in gnomad-public were moved to gnomad-public-requester-pays.
https://gnomad.broadinstitute.org/news/2021-08-gnomad-hosted-public-files-moved-to-requester-pays-bucket/
This replaces gnomad-public with gnomad-public-requester-pays in resource paths. While going through the resources, I noticed a few (such as VCFs and coverage TSVs) that no longer exist in gnomad-public-requester-pays. We'll have to figure out what to do about those, but that can be done afterward. This at least fixes most of the resource paths.
Resolves #400

did you make an issue with the paths that no longer exist?

Good call. Opened #402.


text:
broccolijs.com speaks of node 0.10.x as the latest stable version of node

From http://broccolijs.com/:

If you don't currently have it installed, you'll need to get the latest stable version of node (v0.10.x). We recommend using NVM. Test to make sure you have node and npm installed by running the following commands and checking that your output is similar:
~ $  node --version
v0.10.x
~ $  npm --version
1.4.x

Node v0.10.x hasn’t been the latest stable version of Node for 2¾ years.
Seeing this made me initially assume that Broccoli was unsupported—not the impression I imagine you want to make.

Thank you for reporting!!! We need to track down which repo is used to deploy there (I’m not 100% who set it up), and get it updated.
@stefanpenner / @joliss - do y’all know who set it up (and which repo)?

no clue

@joliss I would gladly take over on-going maintenance of broccolijs.com site/domain.

Looks like the site is also having some DNS troubles. (for me)

#222 ?

@tsing80 thats old, the issue was resolved since then. Looks like a new issue cropped up.

Although I turned over the domain to Jo, the registrar still points to my old DNS (which is hosting https://github.com/folz/broccoli-site - the repo you're looking for, although I recommend you don't try to reuse it). You would need her to update her registrar's DNS settings.
Also, I wanted to let you know that I'll soon be closing down the account which hosts the old website. Since broccolijs.com still points there, it will stop resolving once I close my account. What's a good timeline to give you all the time needed to set up a new site?

THe current minimum supported node version is 8.
Closing this issue now, please reopen if this is still a problem.

authors: chris-morgan folz oligriffiths rwjblue stefanpenner tsing80

repo: broccolijs/broccoli


text:
Add createCacheDirectory capability.

See https://github.com/broccolijs/broccoli-plugin/pull/19 for more details.
Requires merging and release of the following PR's:

[ ] https://github.com/broccolijs/broccoli-node-info/pull/1
[ ] https://github.com/broccolijs/broccoli-plugin/pull/19
[x] Update documentation

The code looks good to me! I think it's good to merge! (Modulo your notes above, obviously. And there's a minor conflict, because we got rid of broccoli-kitchen-sink-helpers in the meantime.)

authors: joliss rwjblue


text:
newline is '\n' by GetValue for multiline

I want to keep the newline is \r\n in windows, but now each line is delimited by a single '\n' character,so how do i do that?

Internally, all newlines use \n. When you save to disk, all newlines will use either \n or \r\n as necessary.
If you want to work with a multiline value then it will use \n only. You would need to convert it back to \r\n if that is what you want.

Internally, all newlines use \n. When you save to disk, all newlines will use either \n or \r\n as necessary.
If you want to work with a multiline value then it will use \n only. You would need to convert it back to \r\n if that is what you want.

thank you

authors: brofield jackeykong

repo: brofield/simpleini


text:
[Bug]: T8900 on HomeBase3 error on open/close events

Version
1.3.0
Node version
unsure, HAOS 9.5, Core 2023.2.1
Operating System type
Linux
Operating system version
HAOS 9.5
Describe the bug
Every time my T8900 sensor is opened or closed, I get the following error.  Connected to HomeBase3.
2023-01-29 03:55:56.986  ERROR Station T8030P1322420A34 - CMD_NOTIFY_PAYLOAD Error:  {   error: SyntaxError: Unexpected token  in JSON at position 35       at JSON.parse (<anonymous>)       at P2PClientProtocol.handleDataControl (/usr/src/app/node_modules/eufy-security-client/build/p2p/session.js:1450:43)       at P2PClientProtocol.handleData (/usr/src/app/node_modules/eufy-security-client/build/p2p/session.js:1043:18)       at P2PClientProtocol.parseDataMessage (/usr/src/app/node_modules/eufy-security-client/build/p2p/session.js:1031:26)       at P2PClientProtocol.handleMsg (/usr/src/app/node_modules/eufy-security-client/build/p2p/session.js:868:26)       at Socket.<anonymous> (/usr/src/app/node_modules/eufy-security-client/build/p2p/session.js:1732:56)       at Socket.emit (node:events:513:28)       at UDP.onMessage [as onmessage] (node:dgram:930:8),   payload: '{"cmd":1550,"payload":{"status":1}}\x00' }
To reproduce
Happens every time T8900 sensor is opened or closed.
Screenshots & Logfiles
2023-01-29 03:55:56.986  ERROR Station T8030P1322420A34 - CMD_NOTIFY_PAYLOAD Error:  {   error: SyntaxError: Unexpected token  in JSON at position 35       at JSON.parse (<anonymous>)       at P2PClientProtocol.handleDataControl (/usr/src/app/node_modules/eufy-security-client/build/p2p/session.js:1450:43)       at P2PClientProtocol.handleData (/usr/src/app/node_modules/eufy-security-client/build/p2p/session.js:1043:18)       at P2PClientProtocol.parseDataMessage (/usr/src/app/node_modules/eufy-security-client/build/p2p/session.js:1031:26)       at P2PClientProtocol.handleMsg (/usr/src/app/node_modules/eufy-security-client/build/p2p/session.js:868:26)       at Socket.<anonymous> (/usr/src/app/node_modules/eufy-security-client/build/p2p/session.js:1732:56)       at Socket.emit (node:events:513:28)       at UDP.onMessage [as onmessage] (node:dgram:930:8),   payload: '{"cmd":1550,"payload":{"status":1}}\x00' }
Additional context
Was testing on a VM install but then fully rebuilt on bare metal with latest HAOS and I still get the error.  I've seen others with the same error, possibly with different devices, all appear to be connected to HomeBase3.

Got the same problem but I am not using a HomeBase 3 but a HomeBase2 instead.

Same on my end wiem homebase2 on firmware :3.2.6.7

This is a bug that will be fixed in the next version.

Fixed in release 1.3.1 .

Still broken for me

Fixed in release 1.3.1 .

Still broken

authors: Actesis BalanceBreaker KillaDreams bropat fliespl

repo: bropat/eufy-security-ws


text:
[Bug]: [ERR_UNKNOWN_FILE_EXTENSION]: Unknown file extension ".ts"

Version
1.8.0
Node version
v22.1.0
Operating System type
Linux
Operating system version
Linux Mint 20 Ulyana
Describe the bug
ts-node suggested in tryitout.md does not work
using tsx as suggested here does
To reproduce

clone repo
change into eufy-security-ws
create a config.json file
issues this command:  ts-node src/bin/server.ts

Screenshots & Logfiles
node:58101) [DEP0180] DeprecationWarning: fs.Stats constructor is deprecated.
(Use node --trace-deprecation ... to show where the warning was created)
TypeError [ERR_UNKNOWN_FILE_EXTENSION]: Unknown file extension ".ts" for /data_8000/eufy/eufy-security-ws/src/bin/server.ts
at Object.getFileProtocolModuleFormat [as file:] (node:internal/modules/esm/get_format:176:9)
at defaultGetFormat (node:internal/modules/esm/get_format:219:36)
at defaultLoad (node:internal/modules/esm/load:143:22)
at async nextLoad (node:internal/modules/esm/hooks:750:22)
at async nextLoad (node:internal/modules/esm/hooks:750:22)
at async Hooks.load (node:internal/modules/esm/hooks:383:20)
at async MessagePort.handleMessage (node:internal/modules/esm/worker:199:18) {
code: 'ERR_UNKNOWN_FILE_EXTENSION'
}
Additional context
No response

Maybe suggesting to use tsx src/bin/server.ts might be simplest fix?


text:
[Question]:  Why is the adapter hogging that much memory?

Ask your question
Hello. I am using the eusec adapter with only 2 cameras connected. Nevertheless, the adapter is hogging above 300MB of memory compared to the ~50MB of all other adapters. Even the havascript adapter with honestly a LOT of scripts only consumes 250MB.
Is there a particiular reason or even a bug connected to this?

Bei mir hat der Adapter nur 134 MB. Der Admi Adapter hat bei mir 180 und jede der drei JavaInstanzen so zwischen 250 und 300 MB.
Ich habe weitere Adapter die um die 130MB brauchen. Scheint also zumindest bei mir nicht auffällig viel Speicher zu sein.

Try latest version 0.9.10.

authors: Baenker bropat seb2010


text:
create working service

Code to this repository is transferring from personal repository and this code does not still compile nor working.
Implement or transfer:

[x] prepare database
[x] http handler to start find new public hearings
[x] fetch hearings data from bga32.ru site
[x] save raw data and links to database
[x] handle raw data to hearings data: extract title, place, date

ad8bc2a

repo: brurbanko/mercury


text:
Error with the Calendar integration

Describe the bug

It seems like there is a bug that was introduced with the most recent update (3.09) running on 0.118.2 (see error message below). The sensors themselves seem to work fine -- this seems to be isolated to Home Assistant's Calendar.
Configuration
Do you configure the integration in YAML or Config Flow (GUI)? :  YAML

garbage_collection:
  sensors:
    # Bio
    - name: "Garbage Biogut"
      frequency: "even-weeks"
      expire_after: '12:00'
      collection_days:
        - mon
      first_month: "may"
      last_month: "dec"
      exclude_dates:
        - '2020-12-21'
      include_dates:
        - '2020-12-19'
      verbose_state: true
      move_country_holidays: DE
      state: BE
      holiday_in_week_move: true

Error log/debug information

Logger: homeassistant.components.calendar
Source: components/calendar/__init__.py:61
Integration: Calendar (documentation, issues)
First occurred: 8:32:07 AM (2 occurrences)
Last logged: 8:32:07 AM

Error adding entities for domain calendar with platform garbage_collection
Error while setting up garbage_collection platform for calendar
Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/helpers/entity_platform.py", line 316, in async_add_entities
    await asyncio.gather(*tasks)
  File "/usr/src/homeassistant/homeassistant/helpers/entity_platform.py", line 507, in _async_add_entity
    await entity.add_to_platform_finish()
  File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 531, in add_to_platform_finish
    self.async_write_ha_state()
  File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 296, in async_write_ha_state
    self._async_write_ha_state()
  File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 320, in _async_write_ha_state
    sstate = self.state
  File "/usr/src/homeassistant/homeassistant/components/calendar/__init__.py", line 161, in state
    event = normalize_event(event)
  File "/usr/src/homeassistant/homeassistant/components/calendar/__init__.py", line 72, in normalize_event
    start = get_date(start) if start is not None else None
  File "/usr/src/homeassistant/homeassistant/components/calendar/__init__.py", line 61, in get_date
    dt.dt.datetime.combine(dt.parse_date(date["date"]), dt.dt.time.min)
TypeError: combine() argument 1 must be datetime.date, not None

Screenshots

Version
Integration version: 3.09
Home Assistant version: 0.118.2

That is weird. I copied your exact configuration and it works fine here (0.118.2). No errors.

I can confirm this error too.
Integration version: 3.09
Home Assistant version: 0.118.3
Logger: homeassistant.components.calendar
Source: components/calendar/init.py:61
Integration: Calendar (documentation, issues)
First occurred: 6:42:44 PM (2 occurrences)
Last logged: 6:42:44 PM
Error adding entities for domain calendar with platform garbage_collection
Error while setting up garbage_collection platform for calendar

Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/helpers/entity_platform.py", line 316, in async_add_entities
await asyncio.gather(*tasks)
File "/usr/src/homeassistant/homeassistant/helpers/entity_platform.py", line 507, in _async_add_entity
await entity.add_to_platform_finish()
File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 531, in add_to_platform_finish
self.async_write_ha_state()
File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 296, in async_write_ha_state
self._async_write_ha_state()
File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 320, in _async_write_ha_state
sstate = self.state
File "/usr/src/homeassistant/homeassistant/components/calendar/init.py", line 161, in state
event = normalize_event(event)
File "/usr/src/homeassistant/homeassistant/components/calendar/init.py", line 72, in normalize_event
start = get_date(start) if start is not None else None
File "/usr/src/homeassistant/homeassistant/components/calendar/init.py", line 61, in get_date
dt.dt.datetime.combine(dt.parse_date(date["date"]), dt.dt.time.min)
TypeError: combine() argument 1 must be datetime.date, not None

I temporaryily fixed that in 3.10. Plese test 3.11-beta, that should fix it  permanently, and show the expiry time correctly.

3.11-beta appears to be working OK after first reboot. No errors in log with HA version 0.118.3. Data is showing in calendar panel as it is supposed to. Vaclav, thank you for taking care of that and educating us in your videos. Much appreciated.

I don't see an issue in 3.11-beta either. Seems to work so far!


text:
2021.12.b0 device_state_attributes warnings

Describe the bug

The Home Assistant 2021.12.b0 beta version generates the following warnings:
2021-12-04 13:05:45 WARNING (MainThread) [homeassistant.helpers.entity] Entity sensor.waste (<class 'custom_components.garbage_collection.sensor.GarbageCollection'>) implements device_state_attributes. Please report it to the custom component author.
2021-12-04 13:05:45 WARNING (MainThread) [homeassistant.helpers.entity] Entity sensor.recycling (<class 'custom_components.garbage_collection.sensor.GarbageCollection'>) implements device_state_attributes. Please report it to the custom component author.

Configuration
Do you configure the integration in YAML or Config Flow (GUI)? :
YAML

garbage_collection:
  sensors:
  - name: "Waste" # Each week on Monday
    frequency: "weekly"
    collection_days: "mon"
    hidden: true
  - name: "Recycling" # Bi-weekly on Monday
    frequency: "every-n-days"
    period: 14
    first_date: '2020-07-13'
    hidden: true

Error log/debug information

Screenshots

Version
Integration version: 3.2.0
Home Assistant version: 2021.12.b0

Same warning for me using Config Flow (GUI)

Tring to fix it while traveling, can you please check if the pre-release 3.21-beta1 fixes it. Thanks!

Logger: homeassistant.setup
Source: setup.py:153
First occurred: 12:34:36 PM (1 occurrences)
Last logged: 12:34:36 PM
Setup failed for garbage_collection: Integration not found.

Yeah can confirm.
Logger: homeassistant.setup
Source: setup.py:153
First occurred: 10:29:35 (1 occurrences)
Last logged: 10:29:35

Setup failed for garbage_collection: Integration not found.

Ok, should be fixed in 3.21. I'd appreciate the confirmation. Thanks

Can confirm that it's now fixed!

Thanks

authors: bruxy70 tomlut tteck


text:
Adjust tab header scaling issues

In line with the work being done to scale Oni's layout there's an issue that has been bothering me for some time.
If you use a bigger font size the tab header will not scale well, see:

One possible solution is to use scalable units for the height and max-width of the tab element, I can take a stab at this if necessary.

Ah yes, thanks for logging this! It's a similiar issue to what we saw with the status bar - there are a few hardcoded px values Tabs.less:
https://github.com/bryphe/oni/blob/1ad48df21ea1b62fcb51cd15df8c9a34420fdb4b/browser/src/UI/components/Tabs.less#L44
I think if we change the max-height, min-height, and height values to use em instead of px, that should solve the problem.
If you want to give it a go @badosu , that would be great! I'll assign it to you for now - but LMK if you have any questions

I merged in #832 - with the following configuration settings:

tabs.height - set the size of individual tabs
tabs.maxWidth - set the maximum width a tab can expand to
tabs.wrap - set to true if you want the tabs to wrap, otherwise there will be a horizontal scrollbar for overflow.

I'll close for now, but keep me posted if they aren't behaving as expected. Thanks for the PR and brainstorming around this, @badosu !

authors: badosu bryphe

repo: bryphe/oni


text:
Outlook 2013 doesn't need a re-enable of Edit Mode when reattaching, before editing text

Best guess is that OL 2013 automatically enables Edit Mode when the file being reattached is added to the list of attachments.
Regardless, the .CommandBars.ExecuteMso("EditMessage") invocation appears to be universally not needed for OL 2013, so a test needs to be added to skip this .ExecuteMso if Left(Application.Version, 2) = "15"

Fixed at f5baed5.
A more general solution might just be to ignore any exceptions raised (or, perhaps, the specific RTE thrown when the Inspector is already in edit mode) on the CommandBars.ExecuteMso("EditMessage") call, since the only anticipated exception condition is when it's already in edit mode, in which case no action needs to be taken.

repo: bskinn/outlook-vba-atchmgr


text:
Document box group events

v3 light is pain.

Spotted broken links which I will fix soon:tm:.

Parameters f and d should have values 1 or 2 not 0 or 1
Else there isn't anything that is wrong in terms of a data standpoint, but some of the parameter names could be improved, for instance Use previous event rotation could be named Previous event rotation transition to make a clearer statement for what it's actually doing

Updated links and data.

repo: bsmg/wiki


text:
Parameters to excludes custom words

Thanks for this action!
I would like to use something similar for https://github.com/simple-icons/simple-icons
It would be really beneficial if we could filter some words of the algo. For example, we have a lot of request that looks like Request: brandname icon. There would be a lot of false positive if we use your action as-is. But if we could exclude specific words like Request and icon, it could probably be able to catch a good amount of duplicate.

@service-paradis filter input is supported in the next release. Any newly created issue would stop detection when it's title match the filter. And filter can be a string or space separated strings work with https://www.npmjs.com/package/anymatch.

@bubkoo Thanks for your work and the follow up!
The changes is great. It is not exactly what I need though.
This is an examples.

if I open Request Ubuntu icon and Request Fedora icon, they will be flagged as potential duplicates

I would like the algo to exclude a custom list of words before comparing the title. For example, having something like:
excludes:
  - Request
  - icon

This way, the algo will compare Request Ubuntu icon with Request Fedora icon. They wont be flagged as potential duplicates
If I have a title Ubuntu icon and Request Ubuntu icon, the algo will compare Ubuntu icon with Request Ubuntu icon. They will be flagged as potential duplicates

@service-paradis config like this
jobs:
  run:
    runs-on: ubuntu-latest
    steps:
      - uses: bubkoo/potential-duplicates@v1
        with:
          GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
          filter: 'Request ** icon'

And this is my tested issues #15 #16

Thanks again @bubkoo 😄
Since people are not that disciplined, would it also work for other derivation than the current filter?
Example, people can request icons using these kind of title:

Request Ubuntu icon
Request Ubuntu
Add Ubuntu icon
Add Ubuntu
Ubuntu icon
Ubuntu

@service-paradis You can specify multi filters in each line, such as
jobs:
  run:
    runs-on: ubuntu-latest
    steps:
      - uses: bubkoo/potential-duplicates@v1
        with:
          GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
          filter: |
            Request ** icon
            Add ** icon
            ** icon **
            ** Ubuntu **

Sorry @bubkoo, but this is not what we need.
If I'm not mistaken, when an issue is opened, if match with, at least, one filter (if their title is "valid") will not be checked for potential duplicates. We need that, regardless of the opened issue title (without "validate it"), remove from it the words that are not needed and, comparing with other titles, of these other titles would be also removed certain words to improve the match between titles.
As @service-paradis pointed, we need an "exclude" function. Is something that you will plan to include or not?

@mondeja @service-paradis Keyworlds specified in exclude will be replaced with empty string before detecting.
jobs:
  run:
    runs-on: ubuntu-latest
    steps:
      - uses: bubkoo/potential-duplicates@v1
        with:
          GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
          exclude: |
            request
            icon
            add
            ubuntu

What about remove them instead of replace with empty strings? Empty string will be compared also, increasing the possibility of false positives. Check this test, the action is comparing "" Ansys "" with "" Ubuntu "" and is raising false positives. What is the point of replacing the exclusions with empty strings?

Thanks again for your work on this @bubkoo
Unfortunately, I dont think the changes you made will totally solve the previous problem with unnecessary spaces.
For example, if we want to exclude "Request" and "icon" from "Request Ubuntu icon"
before:
  .reduce((memo, keyworld) => memo.replace(keyworld, ' '), title)

gives "⎵⎵Ubuntu⎵⎵"
after
  .reduce((memo, keyworld) => memo.replace(keyworld, ''), title)
  .replace(/\s+/, ' ')

gives "⎵Ubuntu⎵"
For the comparison, you are creating arrays using split(' '). We can see a slight improvements as it'll compare ["", "Ubuntu", ""] instead of ["", "", "Ubuntu", "", ""]. But it still can bring false positives.
Maybe trimming leading and trailing spaces before splitting would solve the above.

Thanks again for your work on this @bubkoo
Unfortunately, I dont think the changes you made will totally solve the previous problem with unnecessary spaces.
For example, if we want to exclude "Request" and "icon" from "Request Ubuntu icon"
before:
  .reduce((memo, keyworld) => memo.replace(keyworld, ' '), title)

gives "⎵⎵Ubuntu⎵⎵"
after
  .reduce((memo, keyworld) => memo.replace(keyworld, ''), title)
  .replace(/\s+/, ' ')

gives "⎵Ubuntu⎵"
For the comparison, you are creating arrays using split(' '). We can see a slight improvements as it'll compare ["", "Ubuntu", ""] instead of ["", "", "Ubuntu", "", ""]. But it still can bring false positives.
Maybe trimming leading and trailing spaces before splitting would solve the above.

@service-paradis It now will trimming leading and trailing spaces before return.
  export function formatTitle(title: string) {
    const exclude = core.getInput('exclude')
    if (exclude) {
      return exclude
        .split(/[\s\n]+/)
        .map((keyworld) => keyworld.trim())
        .filter((keyworld) => keyworld.length > 0)
        .reduce((memo, keyworld) => memo.replace(keyworld, ''), title)
        .replace(/\s+/, ' ')
        .trim()
    }
    return title
  }

@service-paradis It now will trimming leading and trailing spaces before return.
  export function formatTitle(title: string) {
    const exclude = core.getInput('exclude')
    if (exclude) {
      return exclude
        .split(/[\s\n]+/)
        .map((keyworld) => keyworld.trim())
        .filter((keyworld) => keyworld.length > 0)
        .reduce((memo, keyworld) => memo.replace(keyworld, ''), title)
        .replace(/\s+/, ' ')
        .trim()
    }
    return title
  }

Would it makes sense to make the list of excluded words case insensitive?
(Also, keyworld should probably be keyword, not sure if you copied this snippet straight from the source.)

Would it makes sense to make the list of excluded words case insensitive?
(Also, keyworld should probably be keyword, not sure if you copied this snippet straight from the source.)

Thank you for your work @bubkoo!

Would it makes sense to make the list of excluded words case insensitive?

I agree that it would be better if the exclusions were case insensitive. What do you think @bubkoo?
Yes, the typo comes from the source itself.

Thank you for your work @bubkoo!

Would it makes sense to make the list of excluded words case insensitive?

I agree that it would be better if the exclusions were case insensitive. What do you think @bubkoo?
Yes, the typo comes from the source itself.

@service-paradis Thanks for your tips and suggestions.

@service-paradis Thanks for your tips and suggestions.

@bubkoo I see that you added case insensitivity to math titles.
It would be also great to add case insensitivity to remove excluded words. For example, here, I need to add every words in different cases (ex. request and Request).

@bubkoo I see that you added case insensitivity to math titles.
It would be also great to add case insensitivity to remove excluded words. For example, here, I need to add every words in different cases (ex. request and Request).

authors: bubkoo ericcornelissen mondeja service-paradis

repo: bubkoo/potential-duplicates


text:
update: model/eventmanager/asset add field

创建事件资产：https://open.oceanengine.com/labels/7/docs/1709792943937547
请求参数：quick_app_asset 和 app_asset 都有 name
获取已创建资产列表：https://open.oceanengine.com/labels/7/docs/1705976384784395
应答字段：app 有 app_name

创建橙子建站站点：https://open.oceanengine.com/labels/7/docs/1696710617712640
应答字段：site_id 是 string 类型，不然 json 解析会报错

更改橙子建站站点状态：https://open.oceanengine.com/labels/7/docs/1696710618884096
请求参数：status 站点操作状态有 4 个

repo: bububa/oceanengine


text:
build: add debuginfo image and documentation

This commit adds the building of a second image for debuginfo which is
intended to be used in an OpenShift environment. The image is used to
start a container in the same cluster as a running application and to
be able to remote debug the node application using gdb.
Documentation has been added to a new docs directory as a suggestion and
contains instructions to set this up.

I've looked into using a sidecar instead of the current solution and I can't see that a sidecar would be a good fit. The goal here is to not have to modify the existing pod, we don't want to always include a container with the debuginfo but only when/if a problem occurs would it be used. I'll dig a little deeper but do think that current solution option is the most user friendly so far.
@lance Do you know if there is something I've missed here with regards to how sidecars work? I does not look like they can be added to an existing pod as far as I can tell.

Hi Dan
I think you are correct that sidecars cannot be injected into a running
pod. But a new build is not required for the application. It should be
possible to inject the sidecar into a new pod with a new container of the
existing image. (I hope this makes sense). This may still be non-optimal
since it does require a new deployment of a pod.
Lance
On Wed, Oct 10, 2018 at 6:16 AM Daniel Bevenius notifications@github.com
wrote:

I've looked into using a sidecar instead of the current solution and I
can't see that a sidecar would be a good fit. The goal here is to not have
to modify the existing pod, we don't want to always include a container
with the debuginfo but only when/if a problem occurs would it be used. I'll
dig a little deeper but do think that current solution option is the most
user friendly so far.
@lance https://github.com/lance Do you know if there is something I've
missed here with regards to how sidecars work? I does not look like they
can be added to an existing pod as far as I can tell.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/bucharest-gold/centos7-s2i-nodejs/pull/147#issuecomment-428517886,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAA-UGOf_6ksVv4QeXKb1RIiKc-_TE62ks5ujckOgaJpZM4XSXWS
.

--
-- Lance Ball -- Sent from my magic rectangle that I carry in my pocket.
Crazy, huh?

Nope, that is a typo :( Thanks I’ll fix that.
ons 10 okt. 2018 kl. 16:14 skrev Lucas Holmquist notifications@github.com:

@lholmquist commented on this pull request.
In doc/gdb-debugging.md
https://github.com/bucharest-gold/centos7-s2i-nodejs/pull/147#discussion_r224094042
:

+#### Start/attach to the running process
+First step is to start the gdbserver on the pod that is the target of the debugging session:
+ +$ oc rsh nodejs-rest-http-1-nw7hz +$ gdbserver 172.17.0.6:7777 --attach 23 +Attached; pid = 23 +Listening on port 7777 +
+In the above case we are creating a new process, but this could also just be the process id of a process running on the pod.
+
+#### Start the debuginfo image
+The next step is to start a container with the debuginfo image in the same cluster.
+
+```console
+$ oc run -i -t nodejs-debuginfo --image=bucharestgold/centos7-s2i-nodejs2-debuginfo:10.x --restart=Never
is that 2 suppose to be at the end of nodejs?
—
You are receiving this because you were assigned.
Reply to this email directly, view it on GitHub
https://github.com/bucharest-gold/centos7-s2i-nodejs/pull/147#pullrequestreview-163378047,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAaY3wPQ-IzPW9XJAgfLr7jgHbAzBSYSks5ujgCxgaJpZM4XSXWS
.

@lance @lholmquist I've updated the doc now to include a "real" example of debugging our nodejs-rest-http application. Please take a look and let me know if there are still things that are not clear.

I noticed something.  When i start the gdbserver on the running pod(using the oc rsh or just going to the openshift UI and going to the pods terminal), the readiness/liveness probes start to fail, which after a minute(?) maybe less(probably depends on the settings) the pod goes into a "not-ready" state(light blue circle on the UI)

I noticed something. When i start the gdbserver on the running pod(using the oc rsh or just going to the openshift UI and going to the pods terminal), the readiness/liveness probes start to fail, which after a minute(?) maybe less(probably depends on the settings) the pod goes into a "not-ready" state(light blue circle on the UI)

Oh, I did not notice. I'll take a closer look tomorrow.

@danbev i think everything looks good.
were you able to re-create that "pod not-ready status becuase of readyness/liveness probes" issue i was having?

were you able to re-create that "pod not-ready status becuase of readyness/liveness probes" issue i was having?

I've not looked into that yet though I was not really concerned about it, but perhaps I should be :) My reasoning here is that if someone is debugging there is probably an issue with the application anyway.

Yea, probably.  The probes only start to fail when the gdbserver starts, so it could be the way the probes are executed.  I'll try switching them to use "curl" and see if that makes a difference

Just following up on the probe issue i saw.  When i change the probes in my deployment config to use the "exec" type for the probes, everything works fine when starting the gdbServer,  so it must be something related to the "httpGet" way of doing probes.
Just as an FYI, this is what i changed my probes to look like in the example application
readinessProbe:
            exec:
              command:
              - curl
              - http://localhost:8080/api/greeting
          livenessProbe:
            exec:
              command:
              - curl
              - http://localhost:8080/api/greeting

@danbev @lholmquist I recommend just sticking with 10.x for now unless there is demand. Each version requires a new builder image...

I recommend just sticking with 10.x for now unless there is demand. Each version requires a new builder image...

Sounds good to me.
@lance Could you approve this if you think it is good to go? Thanks

Landed in bf73e307318442126458dd34888506220753ce75.

authors: danbev lance lholmquist


text:
Depends on bc

I got /usr/bin/typiskt: line 603: bc: command not found when finishing the test and got a whoppin' 0.00 WPM.
This is not required by anything else on my system so I wouldn't call this "have no dependencies".

Ah, yes, i use bc, forgot about that. I think it is necessary with a calculator that can do floating point numbers, but maybe i should use awk for this instead, since it is a more common package.

it's fixed now. also updated the AUR package.

authors: budRich kattjevfel

repo: budlabs/typiskt


text:
AddInventory() request throws System.Text.Json.JsonException

Creating an AddInventory() request & calling SendAsync() will execute the request correctly and the desired inventory will be created. No validation errors are received.
However, the call will respond with a System.Text.Json.JsonException parse exception, due to trying to parse a non-int string into an Int32 property (inventory_id). Is it
Attached a sample response & error output. All priceGroups & warehouses passed in the call are correctly added prior to the AddInventory() call.
baselinker_addinventory_request.json
baselinker_addinventory_response.json

What is inventory id format?

Very good question. I tested the method & got ints through the online interface, but I've also seen other ids in the api, where the type_id format is used.

Yeah well, in your case does it always return string for inventory id?

Also no time to go further, so opted for try catch & to move on since the call itself works & don't need the response. Appreciate your responses.

Re-opening this as this is a still an unsolved issue. If anyone wants to take time to work on this issue PRs are welcome. Unfortunately I'm busy with other things so this might not be solved soon...

authors: bugproof bzatrok

repo: bugproof/baselinker-dotnet


text:
docs(upgrading,react-native): iOS import statement

Goal

fix import statement
Design

Changeset

Testing

Hey @sharc7, good spot. Thanks for raising this PR.

Hey @sharc7, good spot. Thanks for raising this PR.

repo: bugsnag/bugsnag-js


text:
Get rid of a fuckton of warnings about loosing precision

The goal is to get rid of warnings and provide appropriate clamping.

generally speaking most of the encodes need a core::clamp

0.4 is an epsilon for clamping, isn't it good actually?

i guess it should be like
core::clamp(_input[i]+singf64(_input[i])*0.4, -32768.0, 32767.0)

where signf64() is some function returning -1.0 or 1.0 depending on sign of input

Actually its the clamp that should have the epsillon, its because lots of NPoT numbers are not exactly representable in IEE754, and floats round down.
Should be on the clamp, because it affects the clamp (make sure that i.e. 2^32-1 doesn't truncate lower)
But you are correct that floats truncate towards zero, so the clamp minimums less than 0.0 should have -0.4 added not 0.4

double signf64(double _x)
{
    constexpr double retval[2] { 1.0, -1.0 };
    const uint64_t& x = reinterprest_cast<uint64_t&>(_x);
    return retval[(x>>63)&1ull];
}

yeah, but there won't be a symmetry, so shader could get broken if you did it as you have written
there would not be a 0.0 in shader, but because of shift there would be arround +/- 1/128

i think u're talking about normalized formats where indeed AFAIK -128 should map to -1 (example for 8bit snorm), but [s|u]scaled formats are seen in shaders as just "static_cast(intval)"

Yeah "SCALED" formats need a larger minimum in the clamp.
"NORM" stays as is.

@devshgraphicsprogramming

Yeah "SCALED" formats need a larger minimum in the clamp.
"NORM" stays as is.

So NORM shouldn't have an epsilon at minimum? I mean, If there is uint8_t NORM, min = 0, max = 255 + epsilon

@AnastaZIuk NORM and SCALED clamp to the same values (because they are stored in the same integers)
The only difference is that the double value gets multiplied by the Max Positive Integer Value before the clamp for NORM and there is no mulitplication for SCALED before the clamp

I'm done If there is no function @devshgraphicsprogramming mentioned here https://github.com/buildaworldnet/IrrlichtBAW/pull/399#discussion_r347090520

does it build?

@devshgraphicsprogramming  section with encode builds, status: to merge

authors: AnastaZIuk devshgraphicsprogramming

repo: buildaworldnet/IrrlichtBAW


text:
Update plugin reference version to latest available

This will fix the build with the plugin linter so that tests will pass.

@pzeballos This will probably require a new release (🤡 2.0.0 🎉)

Awesome! LGTM!
If you want we can do it together tomorrow :)

authors: jeremybumsted pzeballos


text:
Fix some common artifact download bugs

Description
While investigating the artifact download process a bit more, I discovered some fairly low-hanging fruit in the existing downloader.
Context
Fixes #2774 by making one or another artifact the "winner", and printing a SHA256 sum of the content that it downloaded.
https://coda.io/d/_dHnUHNps1YO#View-3-of-Escalations-Table_tu3KF/r437&view=modal
Changes

Write to a temp file and move it to the destination name when ready
Check the error return from Close
Print a SHA256 sum of the content
Add ability to verify SHA256 checksum (not yet used)
Make error strings more Gothic

Testing

[x] Tests have run locally (with go test ./...). Buildkite employees may check this if the pipeline has run automatically.
[x] Code is formatted (with go fmt ./...)

This change has resulted in permissions changes of the artifacts where group and world permissions bits are lost/gone.
It used to use os.Create with combine 0666 with the UMASK, while os.CreateTemp will lock permissions down since temporary files are only accessible by the user creating them.
This caused an outage for us because our application build doesn't make sure the files have appropriate permissions on them.
See:
https://forum.buildkite.community/t/permissions-on-artifacts-changed-with-version-3-75-0-of-buildkite-agent/3803

Thanks for pointing this out @jim-barber-he, the permissions change was definitely unintentional. #2894 to fix it should be in the next release.

repo: buildkite/agent


text:
[REST API] pipeline visibility field?

Is there a REST equivalent to the GraphQL visibility field?

Hey @chrisdothtml, there is now! Thanks for highlighting its absence, we've added it to the REST API today. I'll leave this issue open until I get it added in to the docs too 👍🏻

authors: chrisdothtml harrietgrace

repo: buildkite/docs


text:
Update agent OS support policy

This changes the docs for each operating system (I only changed the agent v3 docs and didn’t touch the v2 ones) to steer folks towards which operating systems we support rather than the oldest operating system the agent can be installed on.
This doesn’t practically change where the agent can be installed, e.g. it probably still works on Windows XP we’re just saying that if it happens to we can’t guarantee support when it goes wrong as we have to focus our efforts.
For Debian, Red Hat, and Ubuntu we can also drop the docs for using Upstart, as presently in service and supported versions of these all use systemd 🎉

For Debian, Red Hat, and Ubuntu we can also drop the docs for using Upstart, as presently in service and supported versions of these all use systemd

the best

authors: keithduncan yob


text:
Amazon Linux 2022

Is your feature request related to a problem? Please describe.
I am having trouble with using node 18 with the default buildkite agent AMI on elastic stack version v5.16.1.
node: /lib64/libm.so.6: version `GLIBC_2.27' not found (required by node)
node: /lib64/libc.so.6: version `GLIBC_2.28' not found (required by node)

This is because amazon linux 2 doesn't support the latest LTS for nodejs.
https://docs.aws.amazon.com/sdk-for-javascript/v2/developer-guide/setting-up-node-on-ec2-instance.html
Amazon recommend using node 16 instead.
Describe the solution you'd like
Do you have any plans to upgrade to a newer version of amazon linux?
I'm happy to raise a PR if it would be helpful.
Describe alternatives you've considered
I am running docker in docker which is causing slow builds and build failures for various reasons.
I have considered installing glibc in the the host bootstrap script.
I am happy to try any alternative suggestions.
Additional context
Build failure using the following asdf plugin:

This is my .tool-versions:
terraform 1.0.10
terragrunt 0.35.5
nodejs 18.14.1

We actually just got bitten by this, and i was thinking the same (i could open a PR).  However, looking at the Packer config:
https://github.com/buildkite/elastic-ci-stack-for-aws/blob/8022cb599c3693fa741d0f5d9d11cf3fbe153b91/packer/linux/buildkite-ami.json#L14
And searching for AMIs in AWS Console, it looks as if it will in fact select the newest version? 🤔 I'm a bit confused, i'd have expected to see a 5.15 kernel available at least, since that's what you get when you docker run --rm -it amazonlinux:
bash-4.2# uname -a
Linux 5c241319d407 5.15.49-linuxkit #1 SMP PREEMPT Tue Sep 13 07:51:32 UTC 2022 aarch64 aarch64 aarch64 GNU/Linux

Ah right, AL2 is apparently being replaced by AL2022, but that's still in Release Candidate phase. TIL.

Ah right, AL2 is apparently being replaced by AL2022, but that's still in Release Candidate phase. TIL.

Yeah AL2022 one of these ones, I assume. It has been in preview since 2021, I don't see any indication of when they plan to GA though 😕.

Have you considered running node in a docker container?

As for the situation with AL2022, we can't commit to basing an Elastic CI Stack until it is GAed. We are also waiting for that to happen, but please ping us if it does, and we will get the ball rolling.

we just got bitten by this issue as well! some of our dependencies requires node18. We fallback to the docker approach but since we already have node setup on our agent. We will prefer using the from the agent instead.
Cant wait for amazon to release it soon

@triarius If I understand correctly ... AL2022 will be end of life in June and we will have to jump to 2023.

Not sure. AL2023 in some ways seems like a complete rename of AL2022. The repo is redirected, for example.
AL2 EOL has been extended to June 2025, however. Hopefully, AL202x will be GA by then.
See https://aws.amazon.com/amazon-linux-2/faqs/, https://aws.amazon.com/linux/amazon-linux-2023/faqs/

As mentioned in #998, Amazon Linux 2023 has been released now.

Nice one buildkite team :clap:
Any date on when it will go from beta (currently) to a proper release?

authors: ChrisLane GZLiew edify42 razbomi toothbrush triarius

repo: buildkite/elastic-ci-stack-for-aws


text:
Replace function refs with reffer refs

I totally forgot that I had published reffer and had intended to get it in here, since string refs aren’t around anymore, and throwing weird functions around always bugged me!

Interesting!
Looking at this code change made me wonder… is the real problem that we're using overly long arg names?
ref={(buildMessageTextField) => this.buildMessageTextField = buildMessageTextField}

vs just:
ref={(el) => this.buildMessageTextField = el}

vs referrer:
ref={this::reffer("buildMessageTextField")}

Reffer is less characters, but it's also less clear that it sets this.buildMessageTextField, which is what you need if you want to access it. And what you need to make sure you don't clobber/shadow with some other function.
Hrmm…

Doesn’t seem like there was much enthusiasm here, and that’s fair. Going to close this one!

authors: ticky toolmantim

repo: buildkite/frontend


text:
Kaggle Competition

Hi Everyone,
We had a small but great Kaggle-focused coworking session on Nov. 5. I believe there is enough interest that we can schedule a number of coworking session that focus on the Kaggle Competitions.
If you're interested in learning more about Kaggle Competitions or just learning more about data science, join us for these coworking session.
The next session will be Monday, November 9 from 5-7 in STO 442.
Best,
Tom

I will be there at 6 actually, and not 5 as I said earlier  because I have
an advisor meeting that was just scheduled.
On Fri, Nov 6, 2015 at 12:15 PM, Tom Hohenstein notifications@github.com
wrote:

Hi Everyone,
We had a small but great Kaggle-focused coworking session on Nov. 5. I
believe there is enough interest that we can schedule a number of coworking
session that focus on the Kaggle Competitions
https://www.kaggle.com/competitions.
If you're interested in learning more about Kaggle Competitions or just
learning more about data science, join us for these coworking session.
The next session will be Monday, November 9 from 5-7 in STO 442.
Best,
Tom
—
Reply to this email directly or view it on GitHub
https://github.com/bulib/studyGroup/issues/17.

No worries - we will see you then!
-Tom

On Nov 6, 2015, at 2:14 PM, legolagon notifications@github.com wrote:
I will be there at 6 actually, and not 5 as I said earlier because I have
an advisor meeting that was just scheduled.
On Fri, Nov 6, 2015 at 12:15 PM, Tom Hohenstein notifications@github.com
wrote:

Hi Everyone,
We had a small but great Kaggle-focused coworking session on Nov. 5. I
believe there is enough interest that we can schedule a number of coworking
session that focus on the Kaggle Competitions
https://www.kaggle.com/competitions.
If you're interested in learning more about Kaggle Competitions or just
learning more about data science, join us for these coworking session.
The next session will be Monday, November 9 from 5-7 in STO 442.
Best,
Tom
—
Reply to this email directly or view it on GitHub
https://github.com/bulib/studyGroup/issues/17.

—
Reply to this email directly or view it on GitHub https://github.com/bulib/studyGroup/issues/17#issuecomment-154504738.

I'll be there late as well. Probably around 5:30 pm.

I'm closing this for the new semester, however, we can continue this during the spring

authors: legolagon tomhohenstein tonygardella

repo: bulib/studyGroup