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


[Feature] Support WSI analysis

[x] Add a WSI reader (read a wsi into Xarray and then transform to a SpatialData object)
[x] Add whole tissue segmentation + conversion to a shapely polygon
[x] Support multi-polygon ROI in segmentation (or anything that uses ROI.KEY)
[ ] Add hover-net to the segmentation methods (or CellVit?) @loic-lb
[ ] [stergioc] Tile embedding in order to encode tile-wise phenotypical information (with different pretrained models e.g., ResNet or in-domain representation learning models). The could be used in a similar fashion to spatial transcriptomics but they will be much sparser.
[ ] [stergioc] Tile clustering in order to generate cluster-maps with similar phenotypical characteristics. This clustering might need to be cohort specific instead of slide specific (TBD).
[x] Add the new dependencies into a new wsi extra

That could be a great feature add, thanks @quentinblampey for creating this issue!
So here are some additional features that could also be considered:

Tile embedding in order to encode tile-wise phenotypical information (with different pretrained models e.g., ResNet or in-domain representation learning models). The could be used in a similar fashion to spatial transcriptomics but they will be much sparser.
Tile clustering in order to generate cluster-maps with similar phenotypical characteristics. This clustering might need to be cohort specific instead of slide specific (TBD).

I can take a look on how to implement the IO for WSI and come back with a suggestion. :)

What segmentation method should we use? CellViT? Hover-net?
@HakimBenkirane is also using something else, called HistomicsTK
The method needs to have the following characteristics:

few dependencies, easy to install (e.g., no openslide dependency)
the method performs well, is well-validated and widely used
not too slow

While trying to make the whole patch embedding pipeline faster I have added the openslide backend at PR #26 . After some tests it is clear that openslide is much faster as a backend. After a bit of digging I found this is issue that it might be related: https://github.com/Bayer-Group/tiffslide/issues/72, I am adding it here just for reference atm.

Ok, thanks for investigating @stergioc! Since openslide is a heavy dependency, I think I will not add it inside the openslide extra: therefore, users that use openslide backend will need to install openslide themselves. What do you think? We can show a nice log if a user tries to use the openslide backend when it's not installed

Hello @stergioc, do you have any updates on the openslide backend?

Hi @quentinblampey, I don't have any updates yet but I have planned some time for this next week. I will post it as soon as I have something. ;)

Ok thanks! I'm merging the dev branch into the wsi branch, since a lot of things changed since our last push on the wsi branch

Hi @stergioc, thanks again for your contributions, I'm closing this issue since we finished all tasks!
Feel free to open again if you want to see a new feature


Ensure the correct version is reported by the build process

Hi! This is the friendly automated conda-forge-webservice.
I've started rerendering the recipe as instructed in #103.
If I find any needed changes to the recipe, I'll push them to this PR shortly. Thank you for waiting!
Here's a checklist to do before merging.

[ ] Bump the build number if needed

Fixes #103

Hi! This is the friendly automated conda-forge-linting service.
I just wanted to let you know that I linted all conda-recipes in your PR (recipe/meta.yaml) and found it was in an excellent condition.
I do have some suggestions for making it better though...
For recipe/meta.yaml:

ℹ The recipe is not parsable by parser conda-souschef (grayskull). Your recipe may not receive automatic updates and/or may not be compatible with conda-forge's infrastructure. Please check the logs for more information and ensure your recipe can be parsed.
ℹ The recipe is not parsable by parser conda-recipe-manager. Your recipe may not receive automatic updates and/or may not be compatible with conda-forge's infrastructure. Please check the logs for more information and ensure your recipe can be parsed.

This message was generated by GitHub Actions workflow run https://github.com/conda-forge/conda-forge-webservices/actions/runs/12334045970. Examine the logs at this URL for more detail.

So I think ffmpeg changed some of its interface in 7.1 which caused me grief. It is also possible that pyav changed things in version 14.
So many things….

Looking at the logs it seems like av’s usage needs to be patched
Hopefully just in the tests so we can avoid repo data patches

@conda-forge-admin please rerender

Need to back port
https://github.com/pytorch/vision/pull/8776

Hi! This is the friendly conda-forge automerge bot!
I considered the following status checks when analyzing this PR:

linter: passed
azure: failed

Thus the PR was not passing and not merged.

Hi! This is the friendly conda-forge automerge bot!
Commits were made to this PR after the automerge label was added. For security reasons, I have disabled automerge by removing the automerge label. Please add the automerge label again (or ask a maintainer to do so) if you'd like to enable automerge again!

Hi! This is the friendly conda-forge automerge bot!
Commits were made to this PR after the automerge label was added. For security reasons, I have disabled automerge by removing the automerge label. Please add the automerge label again (or ask a maintainer to do so) if you'd like to enable automerge again!

@conda-forge-admin please rerender

Hi! This is the friendly automated conda-forge-webservice.
I tried to rerender for you, but it looks like there was nothing to do.
This message was generated by GitHub Actions workflow run https://github.com/conda-forge/conda-forge-webservices/actions/runs/12340046148. Examine the logs at this URL for more detail.

Do you know how to address the arch failure?

@conda-forge-admin please rerender

@conda-forge-admin please rerender

Thanks!
libwebp was found by the package inspection, we should add it as a host dependency.

@conda-forge-admin please rerender

thank you so much for your help. going to add automerge.

thank you so much for your help. going to add automerge.

 :)
I'd like to try removing your work-arounds though; they shouldn't be necessary anymore AFAIU.


Allow passing differ to watcher

Lets make this an actual option in an option map, ie { differ }

Awesome! Lets keep this undocumented also


Chore/dependencies

Explanation
This draft PR is experimental for discussion about the idea of using PNPM more effectively and efficiently regarding the disk space of the node_modules.
I moved all the common dependencies between the packages into the root, below are sizes of node_modules in each package after and before.
Before:
1.root => 990 M
2. app => 476 K
3. providers => 148 K
4. demo => 72 K
5. zk => 140 K
6. types => 88 K
7. e2e => 128 K
After:
1.root => 990 M (No change)
2. app => 372 K
3. providers => 48 K
4. demo => 48 K
5. zk => 52 K
6. types => 36 K
7. e2e => 84 K
Conclusion:

It would be more efficient to use that since it makes it faster to pnpm install.
It makes it easier to trace a specific shared dependency version, for example: rlnjs was used twice in demo/package.json and inside app/package.json. If we needed in this case to update rlnjs we will need to update it twice in two different places but rather its better to have it one place to its easier to handle and observe.

After discussion:
> It would be more efficient to use that since it makes it faster to pnpm install.
Nx tool should help on that with caching.
> It makes it easier to trace a specific shared dependency version, for example: rlnjs was used twice in demo/package.json and inside app/package.json. If we needed in this case to update rlnjs we will need to update it twice in two different places but rather its better to have it one place to its easier to handle and observe.
Dependabot will take care of updating the dependencies in all the packages.


[ISSUE #7545] [RIP-65] Support efficient random index for massive messages

…sages

Which Issue(s) This PR Fixes

Support #7545
Brief Description

How Did You Test This Change?

Codecov Report
Attention: 171 lines in your changes are missing coverage. Please review.

Comparison is base (46962c2) 42.97% compared to head (723a7b9) 43.28%.
 Consider uploading reports for the commit 5438490 to get more accurate results

Files
Patch %
Lines

...che/rocketmq/tieredstore/index/IndexStoreFile.java
77.50%
35 Missing and 19 partials :warning:

.../rocketmq/tieredstore/index/IndexStoreService.java
74.86%
32 Missing and 14 partials :warning:

...che/rocketmq/tieredstore/TieredMessageFetcher.java
0.00%
28 Missing :warning:

...main/java/org/apache/rocketmq/store/CommitLog.java
59.09%
7 Missing and 11 partials :warning:

...a/org/apache/rocketmq/store/MessageExtEncoder.java
78.26%
3 Missing and 7 partials :warning:

.../java/org/apache/rocketmq/store/MultiDispatch.java
87.09%
0 Missing and 4 partials :warning:

...rocketmq/common/message/MessageExtBrokerInner.java
25.00%
3 Missing :warning:

...org/apache/rocketmq/common/utils/MessageUtils.java
88.00%
0 Missing and 3 partials :warning:

...cketmq/tieredstore/file/TieredFlatFileManager.java
72.72%
1 Missing and 2 partials :warning:

...pache/rocketmq/store/queue/MultiDispatchUtils.java
0.00%
1 Missing :warning:

... and 1 more

Additional details and impacted files
@@              Coverage Diff              @@
##             develop    #7546      +/-   ##
=============================================
+ Coverage      42.97%   43.28%   +0.31%
- Complexity      9677     9789     +112
=============================================
  Files           1158     1162       +4
  Lines          83987    84223     +236
  Branches       10917    10933      +16
=============================================
+ Hits           36093    36460     +367
+ Misses         43399    43245     -154
- Partials        4495     4518      +23

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


Feature request - clearly state this will download a binary

Thanks for this great extension.
Please also provide a notification beforehand in the description for this extension + digital signature for the file being downloaded and/or how to verify integrity for this download.
Very useful extension otherwise. Would prefer without download but if the download can be verified this makes sense.

Hi, your request makes sense. It is fair to notify the user before starting the download.
However, I'm checking the downloaded resources https://github.com/davidnussio/vscode-jq-playground/blob/master/src%2Fconfigs.ts#L3


Add datacenter_info metric

Contains limited metadata about datacenters. Closes #79.

If it's values, that means adding two new static timeseries per datacenter. That doesn't seem like a cost worth the benefit. It's gotta be possible with labels, right?

I'll promote https://github.com/peterbourgon/fastly-exporter/releases/tag/v7.0.0-beta.1 to v7.0.0 in a day or two, please give it a test and report any issues! /cc @mrnetops @SuperQ


PodSecurityPolicy support

Hi,
Thanks for this superdope guide to understanding and building a k8s-cluster 'the hard way'.
I would love to have added a section about PodSecurityPolicies, how to make sure you setup a cluster where the default kube-system deployments are done 'secure' with the correct policies - would that be appropriate in this guide?
Regards,
Wietse

I'm trying to keep things a simple as possible and focus on the core of Kubernetes and set the stage for people to explore additional concepts such as PodSecurityPolicies on their own.


Various small improvements

Optimize images to make the site load faster
Upgrade to Next.js 13 and React 18

This required swapping and removing some dependencies (including @testausserveri/react-testausid)

Improve SEO and HTML semantics, this significantly improved Google Lighthouse scores on most pages
Add ESLint
Switch from Babel to SWC, which is currently the recommended compiler by Next.js
Removed some unused dependencies

React-testausid should not be removed, but for now it'll have to do. Is it possible that you could do some housekeeping there too @Eldemarkki? The documentation should be easy enough to interpret. There's quite a bit of housekeeping to do there though.

Also there are some conflicts in this PR atm.

@Esinko Fixed the conflicts. And yes I agree, react-testausid should not be removed, but it was slowing down development (due to not supporting React 18) and I decided it was appropriate to remove it because it wasn't even used in production.
I've tried to fix https://github.com/Testausserveri/react-testausid/issues/2 a few times, but I've had many problems with setting up the development environment. I can try again when I have more time (likely within a 1-2 weeks).

Sorry abt the close (misclick)
Anyhow, LGTM!
Merge? @ahnl


Ctu 1

Docs Build status updates of commit 78e08e9:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

teams/teams-ps/teams/Get-CsTeamsAcsFederationConfiguration.md
:white_check_mark:Succeeded
View (teams-ps)

teams/teams-ps/teams/Set-CsTeamsAcsFederationConfiguration.md
:white_check_mark:Succeeded
View (teams-ps)

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

#sign-off

@chrisda can you please help me merging this updated documentation?


Design Review Meeting for Doc 153

Design Doc for Doc 153
Review meeting for the Proposal to flatten immutable arguments within the DisputeGame, so that new deployments can use proxies instead of requiring full redeployments of the proofs system.
Date, Time and Duration
Design Doc 153
Tuesday, November 26
10:00-10:30am EST
Video call link: https://meet.google.com/hhm-gwjj-xtb
Or dial: (TH) +66 2 844 9331 PIN: 819<PHONE_NUMBER>#
More phone numbers: https://tel.meet/hhm-gwjj-xtb?pin=8194165033020
Link to design doc
#153
Additional Context
Multiple implementations were discussed, at first the proposal was to flatten all constructor arguments as immutable args provided by the factory and stored in an associated config mapping. However, due to Solidity's limitations, this would be a generic blob of bytes, to which an IExtraDataFiller contract was suggested to properly store the args, before Creator contracts were settled on to deploy new DisputeGames.
Requested Attendees
@ajsutton @clabby @maurelian @smartcontracts

I don't think this was added to the calendar yet, maybe because @op-aaron wasn't assigned? (Is that the process @op-aaron?) Should we push it back a day to give enough time for people? Or are people already planning to go anyway?

We have 3 people RSVP'ed from it, and I invited everyone from this thread to it. I thought I set the google meet option to public on the calendar, and it is linked here. I can delay it if there is anyone who wants to attend that can't make it, but I think all relevant people should be notified?

Oh I see, you created an event, got it. Normally they go into the public calendar

I'd keep just keep it this time then if enough of the right people will be there.

Meeting recording can be found here

Hi All - It looks like this one is taken care of but just to clarify:  If you use the Design Review template when creating the issue it should auto-assign the issue to me and then I can get it on the calendar.  @ControlCplusControlV let me know if you used the template and it failed to assign me and I can look into it.  That said, when there is less than 24hr notice it may be more expedient to just book it yourself so that I do not become a roadblock due to timezone, etc ...  Please let me know if you have any questions and thank you for handling!  I will get this recording to Amanda to post on our youtube shortly.

Ah, I had used the template but took it upon myself to make the meeting which is where I think it went wrong. I did check everybody's calendar though to ensure no conflicts, but the meeting settings may have been a bit off, will keep this in mind for future meetings though!


bad working with a particular URL

Hi,
the following link entered in the terminal window returns :
ERROR: Unsupported URL: http://replay.publicsenat.fr/vod/documentaire/a-la-recherche-de-bernard-maris,-l-anti-economiste/192668
What is your advice ? thanks
db

OK, very good indeed !
thanks


No effect on output beyond slight noise.

It doesn't seem to actually do anything.
Enabled, with no text prompt, two negative embeddings, and a controlnet pose:

Not enabled, with no text prompt, same two negative embeddings, same controlnet pose:

Did you select the main diffuser?


Only working on first "login"

Hi,
I just opened a market on my eBay account and now I cannot get ebay_rest to work properly.
I don't really know if the two thing are related or something else changed since I last used my software...
It worked flawlessly for months, but now it trows
Error number96011. user_token.access_token is None. In ebay_rest.json, check refresh_token and refresh_token_expiry.
when I, for example, call sell_inventory_get_inventory_item.
In token.py, I can see that the response from ebay is
b'{"error":"invalid_grant","error_description":"the provided authorization refresh token is invalid or was issued to another client"}'

However, if I delete refresh_token and refresh_token_expiry from ebay_reay.json and I complete the login procedure through chromedriver it works. Then I close my software, save refresh_token and refresh_token_expiry in ebay_reay.json and it doesn't work.
Using ebay_rest 0.0.16, also tried 0.0.15 but nothing changed.
The API is working fine in the eBay's API Explorer
Edit: now it's not even letting me login.. in the chromedriver windows i get {"error_id":"invalid_request","error_description":"Input request parameters are invalid.","http_status_code":400}
(Fixed the edit by generating a new redirect URI, main problem still persists)

Now it's working... Maybe something was updating in my eBay account after creating the market. Weird

It would appear that eBay had a temporary problem with their system.  Good to hear that the library works well for you most of the time.


Values precedence in helm 3.13.1

With this commit (https://github.com/helm/helm/pull/12480) the precedence was changed to:
1. User specified values (e.g CLI)
2. Sub-chart values
3. Imported values
4. Parent chart values
This makes it only possible to add new values to sub-charts from parent or imported values. Modify existing values is no longer possible. In helm versions 3.8.2-3.12.3 it was possible to fill in empty or null values in the sub-charts from imports or parent chart.  This is no longer possible in helm 3.13.1
In helm 3.13.0, it was possible to change any value in sub-charts from the imported or parent charts.
Is the precedence in helm 3.13.1 the final word on this?

Can you give an example of what you're trying to achieve with expected input and output?

I need a way to set values in the sub-charts from the parent chart.
Prior to 3.8.2 and in 3.13.0 it is possible to import values in the parent and apply those to sub-charts.
In 3.8.2-3.12 it is possible to set values from an import in the sub-charts if those had null or empty definitions in the sub-charts.
In 3.13.1, it is no longer possible to either update values in sub-charts from the parent or from imports in the parent. Default value, null or empty remains. The only option is when the sub-chart does not have the parameter names defined.

If you give an example of what you're trying and what's not working as you expect, that would help. The functionality here should still work: https://helm.sh/docs/chart_template_guide/subcharts_and_globals/#overriding-values-from-a-parent-chart

Here an import is done with three helm versions. With three different outcome:
Charts:
$ cat mychart/values.yaml
favorite:
drink: coffee
food: pizza
pizzaToppings:

mushrooms
cheese
peppers
onions

profile:
myimport: true
mysubchart:
dessert: ice cream

$ cat mychart/charts/mysubchart/values.yaml
dessert: cake
topping:
$ cat mychart/Chart.yaml
apiVersion: v2
appVersion: "1.0"
name: test
version: 1.0.0
description: test
dependencies:

condition: profile.myimport
import-values:

myimport
name: myimport
repository: file://../charts/myimport
version: 1.2.3

name: mysubchart
repository: file://../charts/mysubchart
version: 0.1.0

$ cat mychart/charts/mysubchart/templates/configmap.yaml
apiVersion: v1
kind: ConfigMap
metadata:
name: {{ .Release.Name }}-cfgmap2
data:
dessert: {{ .Values.dessert }}
topping: {{ .Values.topping }}
servedon: {{ .Values.servedon }}
$ cat mychart/charts/myimport/values.yaml
exports:
myimport:
mysubchart:
dessert: mousse
topping: sugar
servedon: plate
$ ./helm-3.13.1 install --generate-name --dry-run --debug mychart
install.go:214: [debug] Original chart version: ""
install.go:231: [debug] CHART PATH: /home/epktojo/helmtest/mychart
NAME: mychart-1698132901
LAST DEPLOYED: Tue Oct 24 09:35:02 2023
NAMESPACE: default
STATUS: pending-install
REVISION: 1
TEST SUITE: None
USER-SUPPLIED VALUES:
{}
COMPUTED VALUES:
favorite:
drink: coffee
food: pizza
myimport:
exports:
myimport:
mysubchart:
dessert: mousse
servedon: plate
topping: sugar
global: {}
mysubchart:
dessert: ice cream
global: {}
servedon: plate
pizzaToppings:

mushrooms
cheese
peppers
onions
profile:
myimport: true

HOOKS:
MANIFEST:
Source: test/charts/mysubchart/templates/configmap.yaml
apiVersion: v1
kind: ConfigMap
metadata:
name: mychart-1698132901-cfgmap2
data:
dessert: ice cream
topping:
servedon: plate
Tests:
$ ./helm-3.13.0 install --generate-name --dry-run --debug mychart
install.go:214: [debug] Original chart version: ""
install.go:231: [debug] CHART PATH: /home/epktojo/helmtest/mychart
NAME: mychart-1698132934
LAST DEPLOYED: Tue Oct 24 09:35:35 2023
NAMESPACE: default
STATUS: pending-install
REVISION: 1
TEST SUITE: None
USER-SUPPLIED VALUES:
{}
COMPUTED VALUES:
favorite:
drink: coffee
food: pizza
myimport:
exports:
myimport:
mysubchart:
dessert: mousse
servedon: plate
topping: sugar
global: {}
mysubchart:
dessert: mousse
global: {}
servedon: plate
topping: sugar
pizzaToppings:

mushrooms
cheese
peppers
onions
profile:
myimport: true

HOOKS:
MANIFEST:
Source: test/charts/mysubchart/templates/configmap.yaml
apiVersion: v1
kind: ConfigMap
metadata:
name: mychart-1698132934-cfgmap2
data:
dessert: mousse
topping: sugar
servedon: plate
$ ./helm-3.8.2 install --generate-name --dry-run --debug mychart
install.go:178: [debug] Original chart version: ""
install.go:195: [debug] CHART PATH: /home/epktojo/helmtest/mychart
NAME: mychart-1698132978
LAST DEPLOYED: Tue Oct 24 09:36:18 2023
NAMESPACE: default
STATUS: pending-install
REVISION: 1
TEST SUITE: None
USER-SUPPLIED VALUES:
{}
COMPUTED VALUES:
favorite:
drink: coffee
food: pizza
myimport:
exports:
myimport:
mysubchart:
dessert: mousse
servedon: plate
topping: sugar
global: {}
mysubchart:
dessert: ice cream
global: {}
servedon: plate
topping: sugar
pizzaToppings:

mushrooms
cheese
peppers
onions
profile:
myimport: true

HOOKS:
MANIFEST:
Source: test/charts/mysubchart/templates/configmap.yaml
apiVersion: v1
kind: ConfigMap
metadata:
name: mychart-1698132978-cfgmap2
data:
dessert: ice cream
topping: sugar
servedon: plate

Can you upload this test harness as a gist?
I think you have a couple of options to get the behavior you want.
I believe library charts maintain the behavior you want. Try can get what you want here by marking type: library in myimport/Chart.yaml.
The other thing I think you could do to maintain similar behavior is use the global values.

Not sure how to upload the complete package. Anyway there is no difference if I add type: library in the myimport Chart.yaml

I created this:
https://gist.github.com/intetinte/93b57e71e1173c0bcc262363b7020f57

I was looking into this test:
func TestProcessDependencyImportValuesMultiLevelPrecedence(t *testing.T) {
c := loadChart(t, "testdata/three-level-dependent-chart/umbrella")
e := make(map[string]string)

// The order of precedence should be:
// 1. User specified values (e.g CLI)
// 2. Parent chart values
// 3. Imported values
// 4. Sub-chart values
// The 4 app charts here deal with things differently:
// - app1 has a port value set in the umbrella chart. It does not import any
//   values so the value from the umbrella chart should be used.
// - app2 has a value in the app chart and imports from the library. The
//   app chart value should take precedence.
// - app3 has no value in the app chart and imports the value from the library
//   chart. The library chart value should be used.
// - app4 has a value in the app chart and does not import the value from the
//   library chart. The app charts value should be used.

For app2 it states that "has a value in the app chart and imports from the library. The app chart value should take precedence." That makes the order of precedence for imports to be lower than the sub.charts values. Contradicts the value precedence in the initial text.
For app3 it states that "app3 has no value in the app chart and imports the value from the library chart. The library chart value should be used.". What is considered as no value here? In the test chart the key "service.port" is missing. It could however have an empty definition or have null/nil value. Is that also considered as a value? Hence, that "value" overrides the library?

" In helm versions 3.8.2-3.12.3 it was possible to fill in empty or null values in the sub-charts from imports or parent chart. This is no longer possible in helm 3.13.1"
Same use case here. After upgrading to 3.13.2 we are not able to override value to subchart from parent chart.

I actually fixed the problem and did a test verifying it.
helm_changes.patch
helm_testdata.patch
Please check and see if this is something that could be used.

We are facing the exact same problem with Helm ver 3.13.1, that is being reported by @intetinte .
Seems like the patch could fix the issues.

@xkiranj

We are facing the exact same problem with Helm ver 3.13.1, that is being reported by @intetinte .
Seems like the patch could fix the issues.

Can you please retry with Helm 3.13.2 or higher. https://github.com/helm/helm/pull/12480 was the fix applied to Helm 3.13.2. And report if you still encounter unexpected behavior.

@intetinte -- I apologize, Ive been trying to find time to get to the bottom of this issue. Helm 3.13 series did try to fix bugs in the import-values process (https://github.com/helm/helm/pull/12162, then fix/patch: https://github.com/helm/helm/pull/12480).
It would help me greatly if the reproducing your issue was easily accessible. In particular, the gist doesn't accurately represent a chart file structure. It would be very helpful if I could do something like:
$ git clone https://gist.github.com/intetinte/93b57e71e1173c0bcc262363b7020f57
$ helm template 93b57e71e1173c0bcc262363b7020f57/ # command to reproduce issue

@gjenkins8
With the gist package I get these results from the different helm versions:
helm-3.12.3 template 93b57e71e1173c0bcc262363b7020f57
Source: test/charts/mysubchart/templates/configmap.yaml
apiVersion: v1
kind: ConfigMap
metadata:
name: release-name-cfgmap2
data:
dessert: ice cream
topping: sugar
servedon: plate
helm-3.13.0 template 93b57e71e1173c0bcc262363b7020f57
Source: test/charts/mysubchart/templates/configmap.yaml
apiVersion: v1
kind: ConfigMap
metadata:
name: release-name-cfgmap2
data:
dessert: mousse
topping: sugar
servedon: plate
helm-3.13.1 template 93b57e71e1173c0bcc262363b7020f57
Source: test/charts/mysubchart/templates/configmap.yaml
apiVersion: v1
kind: ConfigMap
metadata:
name: release-name-cfgmap2
data:
dessert: ice cream
topping:
servedon: plate
I did a pull request that fix the issue without interfering with the other recent fixes with imports:
https://github.com/helm/helm/pull/12590

Initial data that the import-function starts with in helm:

The flow in the current helm (from 3.13.1):

The data referred in the flow above:

The suggested flow:

Data in suggested flow:

The suggested above makes imports on top-level take precedence of the values in the subcharts. This is what the documentation for helm suggests. The change is backwards compatible (i.e don't interfere with other updates done in the import area).
This can be verified in the pull request https://github.com/helm/helm/pull/12590

We are facing the same issues that are reported here by @intetinte and checked that, with his version the charts are rendered as expected (import values taking precedence of the sub-chart values), as it's documented.

/nostale


Make contributing new azure resource types simplier / self contained.

I wanted to start up a conversation about making the codebase friendlier to implementing new azure resources. Right now it looks like there are some files that require all of the resources to be included, for example the Luis Model has all the resources included in a single json file (https://github.com/Microsoft/AzureBot/blob/master/AzureBot/LuisModel/AzureBot.json) which will make contributing new resources challenging.  Other class types are organized by how the bot uses the objects so as a result, adding a new azure resource to the bot means sprinkling new classes through out the codebase.  I wanted to see if the team is open to some refactoring that would make it easier to add new resources, or at least make it easier to support a fork that includes new resources in case the team does not want to accept a pull request.

We already have plans to make this cleaner to implement new Azure resource providers. @nzthiago is currently working on this with this branch https://github.com/nzthiago/azurebot/tree/nzthiago/addextensibility
Each resource provider will have its own .csproj and LUIS models with dialogues passed down from the root LUIS model.

Great to hear. I am very interested in contributing. At least to the resources that we are using as part of our daily devops activity.

Thanks @erichexter, great to see you also thought of the scenario of making it easier to add more services and have multiple LUIS models.
As @dtzar mentioned I started the work on that branch; Would be very happy to have your help, we can add you as contributor or just send PRs.
I've just pushed the latest changes to that branch, basically splitting the current big model into four (the four json files are in the code there too), let me know if you can get it going on your own dev environment.
I'm also looking at the internal bot framework IScorable interface and how it might help with the back and forth between the dialogs, but none of that is in the code yet

Note: have added a new branch to the main repo with the code and removed my fork:
https://github.com/Microsoft/AzureBot/tree/addextensibility

What scenarios are left to get working or what scenarios are working from the existing functionality with this branch currently?

I haven't tested forms or the long running commands. And from the root dialog to decide which of the others to go to is not being made by LUIS but instead there's a couple of temp if / else statements looking for key words. Need to make this a little cleaner, and maybe the Scorable interface can help

Re: the nested ifs, you could make an interface that each resource must
implement that we could scan , find all implementations of and then loop
over and look for the resource name and the associated dialogs
Eric Hexter
blog | http://Hex.LosTechies.com
info | http://www.linkedin.com/in/erichexter
On Wed, Sep 7, 2016 at 10:30 AM, Thiago Almeida<EMAIL_ADDRESS>wrote:

I haven't tested forms or the long running commands. And from the root
dialog to decide which of the others to go to is not being made by LUIS but
instead there's a couple of temp if / else statements looking for key
words
https://github.com/Microsoft/AzureBot/blob/addextensibility/AzureBot/Dialogs/RootDialog.cs#L231-L235.
Need to make this a little cleaner, and maybe the Scorable interface can
help
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/Microsoft/AzureBot/issues/109#issuecomment-245318973,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAHABFWzETtn6ujxTsgdZ6inz_T8PpGJks5qntiqgaJpZM4J17b3
.

Yes indeed, the current if/else was just to test that the back and forth between the dialogs worked before we got any further.
Are you interested/available to implement the change you're recommending?

yes, I make a pull request so that you can see what this looks like
concretely and then you can decide if you like the approach.

Awesome, thanks @erichexter! Look forward to it

I made the minimal changes I could to demonstrate how this would work.
Here is the commit
I added a new project Azurebot.Types so that I could break the dependency from Azurebot to each of the implementations.
Each resource then needs to implement the interface

    public interface IResourceDialog
    {
        bool CanHandle(string query);
        IDialog<string> Create();
    }

I am by not means attached to this implementation, but this demonstrates how we can isolate the resources in a way that supports the Open Close Principal. Let me know what you think . I have not tested any of this yet. but I wanted to stub out the structure of the classes first.

@erichexter cool, looks like a great start! Please do a pull request, this branch isn't hooked up to CI/CD yet, it's still in experimental phase :).  In the DetermineResourceAsync we'll just add a check in case the dialog comes back null from the factory and then send to the Help context instead of forwarding, seems like an ok way to go about it if none of the dialogs can handle it.

Hay sounds great and please know I am totally open to feedback on the code.
The class names I picked stink but I wanted to just get the basic factory
structure in place. That way we have something concert to consider. So yes
anything you want to change is totally cool with me, I will not be offended
I promise that.
The help dialog seems so obvious now that you said it. I could also imagine
in the future we could enumerate all of the available resources and their
help text
--
Eric Hexter
blog | http://Hex.LosTechies.com
info | http://www.linkedin.com/in/erichexter

Great! Do send through the Pull Request when you're ready

What can I do to help next? Manually test out the branch to make sure it works? Write unit tests?  something else?

Cool - yes, getting your dev environment set up so you can try it locally would be the first step. You'd have 4 different Luis applications (create them in luis.ai by instead of creating from scratch import the json files in the [LuisModel folder] (https://github.com/Microsoft/AzureBot/tree/addextensibility/AzureBot/LuisModel). Then in each of the Dialog files update the luis attributes at the top to reflect your 4 luis applications.
There's some more set up steps [here] (https://github.com/Microsoft/AzureBot/blob/gh-pages/docs/DeveloperSetup.md).
Once you have it going, a great next step for us would be to add support for another part of Azure. The Resource Group one that we have started could do with a few more, then there's Azure SQL Db, Azure Web Apps, etc, let us know if there's any you'd be comfortable with.

@erichexter will close this bug now that we have added your contribution to the extensibility branch.


RealmSwift & objectivec

Hello, please help me understand the following. From the RealmSwift documentation :

If you’re looking to use Realm from Objective‑C, or from mixed Objective‑C & Swift apps please see Realm Objective‑C instead.
The Realm Objective‑C and Realm Swift APIs are not interoperable and using them together is not supported.

ABFRealmSearchViewController uses internal RBQFetchedResultsController. As far as I understand, at least according to XCode, RBQFetchedResultsController is a bunch of objective-c files so it must use objective-c api.
Can you share your thoughts with me about this issue?
Thank you

I am droping Realm for my current project. sorry about bothering you

Sorry to hear this! The documentation point is specifically addressing the interoperability of the Realm Swift and ObjC APIs. However, technically, Realm Swift is simply an API that follows more Swift design patterns but underneath it uses the ObjC API. As a result, technically Realm Swift and Realm ObjC work together, you just can't take a Realm Object from Swift and use it in place of a RLMObject in ObjC.
RBQFRC works off of Realm's ObjC API directly, but then similar to Realm Swift, I built a Swift friendly API on top of it that uses the Realm Swift objects vs the Realm ObjC objects.
Would be curious to know why you are dropping Realm!

I've had many small problems with Realm, like the NSDate is truncated to the second combined with lack of auto-incrementing properties and limits regarding to indexing and primary keys. Finally, I've used some  reusable components recommended on realm website and I find them not quite suitable to my use case.  I didn't particularly like this lack of clarity about Swift and Objective-C compatibility. In the end if I need to replicate CoreData so why just not use CoreData ? Maybe next project when things will mature or I will have more time.


Remove resources block in values.yaml

Longhorn #4601
Signed-off-by: Ray Chang<EMAIL_ADDRESS>Self-test: Check that the Longhorn system can start normally without errors:

@weizhe0422 not here, you can make the change to longhorn/longhorn repo instead. longhorn/charts is for the longhorn chart release purpose, so it will use the changes from longhorn/longhorn during the release.

@weizhe0422 not here, you can make the change to longhorn/longhorn repo instead. longhorn/charts is for the longhorn chart release purpose, so it will use the changes from longhorn/longhorn during the release.

@innobead  Got it, I will update the values.yaml which is under longhorn/longhorn repo.
https://github.com/longhorn/longhorn/blob/ff9b19bbf55233dae14e17306485b5c1a73d4457/chart/values.yaml#L198-L209


Dynamically handles L3 misses with vxlan backend

Since L2 misses are still handled statically DOVE extensions are
no longer required.routes.go maintains the mappings. devices.go now monitors for L3 misses and vxlan is
updated to handleL3Misses.
Fixes #203

LGTM


Update channels.csv

Added Avang TV to country IR

Simply edit existing entry and change it's broadcasting area to c/US;c/IR

I want it to be seen in both Iran and America
On Sun, Jul 28, 2024 at 01:27 Dum4G @.***> wrote:

Simply edit existing entry and change it's broadcasting area to c/US;c/IR
—
Reply to this email directly, view it on GitHub
https://github.com/iptv-org/database/pull/12886#issuecomment-2254270032,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/A5PINLNBKEX23IKMG7GR5H3ZOQNENAVCNFSM6AAAAABLF6DUR6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDENJUGI3TAMBTGI
.
You are receiving this because you authored the thread.Message ID:
@.***>


vscode: remove Rename Chat functionality

Being ruthless with this feature. We will be moving chat history to the backend, synchronizing it, etc. Being able to rename chats will add complexity. We can always add it back once we do all that.
Test Plan: CI. Ran manually and the edit title button was gone.
More context at https://sourcegraph.slack.com/archives/C0748TDGT29/p1717162754194119?thread_ts=1717160259.281599&cid=C0748TDGT29

I used it a lot, because the last question never reflects the overall topic about the context.
In one of my one projects, I let AI summarize the very first question into a 3-5 word sentence.

@PriNova Thanks for the feedback. If we used AI-generated titles instead of letting you manually rename them, would you be happy with that?

Absolutely. If I chat with Cody, I always focus on bounded context of topic/concern. For example, fixing a bug or implementing a feature, etc.

Hi, So you have removed the ability to change the chat name?


Add typeahead for languages that support syntax highlighting

This new feature, as suggested in #4111, is an addition to typeahead which autocompletes a programming language that has support for syntax highlighting in code blocks. Upon pushing enter, the closing backticks are also autocompleted, and the cursor is put in the middle:

Note that the sorting is not just alphabetical, but it attempts to arrange the options in order of popularity. The popularity ratings are generally based of the TIOBE index, with a bit of manual tweaking to improve performance. Based on lang.json, which contains these rankings, a Javascript file containing the dictionary of languages is constructed by a Python script and saved in static/generated/pygment_data.js.
It's basically fully functional, but needs a few more additions before I'll remove the [WIP].

Have not added support for ~~~ yet (currently only triple backtick)
Have not yet added unit tests for the new typeahead

I'm particularly looking for feedback on the JavaScript generator script, because I'm not sure if there is a more "proper" way to handle it than what I'm currently doing. (I also question the quality of any code I write past 5 am)

Automated message from Dropbox CLA bot
@cory2067, it looks like you've already signed the Dropbox CLA. Thanks!

In addition to ~~~, you'll also want to add a special case for ~~~ quote, which we don't handle through pygments, but which we provide support for.

I checked this out, and the experience of using it is pretty good!

Ok, I addressed all the things discussed above.
Triple tilde now works, and unit tests were added.
Also, I decided to allow an extra whitespace to permit stuff like ~``` py~

@cory2067 this looks great!  I noticed one bug, which is that code blocks are only valid at the start of the a line, while your highlighting logic pops up the typeahead in situations like this:

Your tests look like they're checking for this, but clearly they don't have the right context or something :).
Other than that, I think you can squash the commits together and write a nice commit message for the overall change, and this will be ready to merge.  Thanks @cory2067!

Ah, I hadn't realized the code blocks needed to start at the beginning of a line. My test cases were actually testing the opposite (the tests expected the typeahead to pop up for foo ```py).
Fixed that and adjusted the test cases appropriately.

Posted one comment, otherwise looks great!

Nice, merged, thanks @cory2067!  Congrats on your first big feature being merged :).


SFTP Save error

If I set in settings some path to load on connect, it seems, that synapse cann't save anything after that

update now please try 1.1.1

Nope, now I just can do nothig - can not edit server properties, can not connect. Just blank Synapse window. I can see my servers, but everything underneath is blank.


Document style guide for docs

What happened?
While it seems that documentation site and Github repos use a style guide, this is not documented explicitly neither at the site or Github

What did you expect to happen?
Documenting the style guide could be helpful for individuals willing to contribute to documentation/site content

Previous art
Velero style guide adapted from the Kubernetes one: https://github.com/vmware-tanzu/velero/blob/main/site/content/docs/v1.5/style-guide.md

I would love love LOVE to see this for our project!


Attack signatures in GET requests not detected

This is in reference to the issue which I created recently here .
The GET requests containing attack signatures are not detected. However the same signatures sent over POST are detected.
Im using
latest modsecurity version with owasp CRS 3.0 and my environment is setup correct.
I'm facing this issue since I pulled this commit

Hi @Goron,
Sorry for the delay. The commit 96fbca43a49c977d12f2a86e2a5ba722b04f0597 was reverted, you should be set now.

Hi @zimmerle
But this commit was supposed to be a fix for POST body handling. However, I reverted the commit and the GET attack signatures were detected.
That means, I could expect a proper fix in near future for POST attack signatures right?

Yes, however it may take a while. Keep in mind that the Apache connector is still in beta. For Apache in production, we still recommend the 2.x family.

ok thanks


Hex Color code generator

I would like to add a hex color code generator. Add the hactoberfest label and assign this to me.

This Project is not labelled under Hacktober, so it is counted in it or not

it's labelled with hacktoberfest check carefully

See it is showing not yet


Implement eip-165 for input relays

I agree. Just like ICartesiDApp inherits from IERC1155Receiver which inherits from IERC165


410 Client Error: Gone for url: https://api.mainnet-beta.solana.com/

This occur when I trying to place order or fatch open orders.
market.place_order()
market.find_open_orders_accounts_for_owner()

@LeeChunHao2000 I'm facing the same issue. How did you resolve it?

@LeeChunHao2000 I'm facing the same issue. How did you resolve it?

Yes, maybe you can try this https://solana-api.projectserum.com

Thanks. This works.

I tried project serum but now i am getting error timed out


Reference to tastypie still exists

hs_core/hydroshare/users.py still has reference to tastypie

You'll need to be more specific. I have a fresh checkout of develop and all references in that module have been removed. Perhaps you're looking at master, where the purge branch has not been merged yet?

I am referring to line#282 to 286 in hs_core/hydroshare/users.py.  I am assuming those are tastypie related.

The function in question doesn't seemed to be invoked from anywhere. Do you know if it will need to be used or if it can be removed?

Not sure whether this refers to the function get_user_info(user) which imports UserResource from hs_core.api, which does not exist in the code base. This get_user_info() is not used in the code base (only used by test script). @pkdash @selimnairb @ironfroggy Can this get_user_info() be removed safely or it is used implicitly somehow by REST API?

@hyi Using PyCharm I found that function get_user_info() (defined in hs_core.hydroshare.users.py) is used only in unit tests. The unit tests where it is being used are marked to be skipped from unit test run. It should be safe to remove this function.

@pkdash That is what I found using PyCharm as well. I think if we remove this function, we should remove the corresponding unit test as well. Could you take care of removing this as well as the corresponding test as part of clean-up in conjunction with bringing in coverage test to our development and deployment workflow? Thanks!

The pull request was merged into develop and tested on dev; nothing is broken due to this removal, so closing.


preserveDanglingCloseParenthesis support for method signatures

preserveDanglingCloseParenthesis  is a cool feature but it does not seem to work for method signatures
Example:
def sum(
  a: Float,
  b: Float
): Float

will be formatted to
def sum(
  a: Float,
  b: Float): Float

This is also the case for class declarations where
case class Foo(
   property1 : String,
   property2 : String
) extends SomeLongClassName

is formatted to
case class Foo(
   property1 : String,
   property2 : String) extends SomeLongClassName

even with preserveDanglingCloseParenthesis enabled.

+1

This should work with the new danglingCloseParenthesis option.

Do you have updated the code related to this option ?
I'm using the Scala IDE 4.30 and this behavior is still here when I format the code.

Scala IDE still uses an older version of scalariform and this won't change until a new version of scalariform is released.

Ok. Thank you for the fix !


fix: [#165]  Slot of six-icon was not centered

🔗 Linked issue

❓ Type of change

[ ] 📖 Documentation (updates to the documentation, readme or JSdoc annotations)
[x] 🐞 Bug fix (a non-breaking change that fixes an issue)
[ ] 👌 Enhancement (improving an existing functionality like performance)
[ ] ✨ New feature (a non-breaking change that adds functionality)
[ ] 🧹 Chore (updates to the build process or auxiliary tools and libraries)
[ ] ⚠ Breaking change (fix or feature that would cause existing functionality to change)

📚 Description

📝 Checklist

[x] I have linked an issue or discussion.
[x] It's submitted to the main branch
[x] When resolving a specific issue, it's referenced in the PR's title (e.g. fix #xxx[,#xxx], where "xxx" is the issue number)
[ ] I have updated the documentation accordingly.
[x] All tests are passing
[ ] New/updated tests are included
[x] I have updated the "upcoming" section inside docs/changelog.md explaining the changes I contributed

If adding a new feature, the PR's description includes:

[ ] A convincing reason for adding this feature (to avoid wasting your time, it's best to open a suggestion issue first and wait for approval before working on it)

Other information:
Before:

After:

Proof that it is centered:

@davidemarcoli there are a couple of places where the icon alignments are now misplaced. For example inside the file upload component or when you want to add a six-icon next to text. Could you please check across the six-webcomponents documentation if you find any other misalignments beside the six-file-upload?
Thanks!

@davidemarcoli there are a couple of places where the icon alignments are now misplaced. For example inside the file upload component or when you want to add a six-icon next to text. Could you please check across the six-webcomponents documentation if you find any other misalignments beside the six-file-upload?
Thanks!

Aside the compact six-file-upload, there was also a small alignment issue in the six-file-item-list. I have fixed it in #177


update dependencies

Codecov Report

Merging #1715 (c93a336) into master (aca1aaf) will decrease coverage by 0.51%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master    #1715      +/-   ##
==========================================
- Coverage   73.11%   72.60%   -0.52%
==========================================
  Files          46       46
  Lines        4471     4471
==========================================
- Hits         3269     3246      -23
- Misses        864      884      +20
- Partials      338      341       +3


Uncaught Error

If an expression begins or ends with an operator, instead of throwing an Exception the Fatal error occurs (the only working scenario is when the expression begins with the minus sign).
For example:
echo $calculator->execute('*1+2'); or echo $calculator->execute('1+2-');.
Also, in case when the expression begins with the plus sign it should be evaluated:
echo $calculator->execute('+1+2');
The error message:

Fatal error: Uncaught Error: Call to a member function getValue() on null in ...\vendor\nxp\math-executor\src\NXP\Classes\Token\TokenPlus.php on line 50
Error: Call to a member function getValue() on null in ...\vendor\nxp\math-executor\src\NXP\Classes\Token\TokenPlus.php on line 50

I will have a fix for this shortly.  It will solve the 1+2- issue (or 1+2+-* type things).  It will not the +1+2 issue as I don't think that is really a valid expression.  -1+2 does work as -1 is a valid value. For +2, the plus is not really needed.  If you still have an issue after the upcoming fix, please submit a PR and we can look at it.

Why do you think "+2" is not a valid espression. In this case "+" is the sign of the number which indicates a positive number, and it's perfectly valid. I don't know of any language/application/calculator which to not accept this.
Wikipedia says:

The positivity of a number may be emphasized by placing a plus sign before it, e.g. +3. In general, the negativity or positivity of a number is referred to as its sign.

Positive numbers are generally not signed. But I will look into adding this.
Got into my old email account, but switched git hub over to my Gmail.  Should have an update shortly.
Will try to find the invite as well.
On Thursday, October 25, 2018 Aleksandar Dlabač<EMAIL_ADDRESS>wrote:
Why do you think "+2" is not a valid expression? In this case "+" is the sign of the number which indicates a positive number, and it's perfectly valid. I don't know of any language/application/calculator which to not accept this.
Wikipedia says:
The positivity of a number may be emphasized by placing a plus sign before it, e.g. +3. In general, the negativity or positivity of a number is referred to as its sign.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or mute the thread.

This is fixed in the latest version.


Coerce lazy-seq as list node

@lread Bumped into this in https://github.com/clj-kondo/clj-kondo/issues/1779

Awesome, thanks @borkdude! Very similar to the support you added for Cons a while back.


[AIML-ADC-8475] Configuration history with rollback functionality

Issue #, if available:: AIML-ADC-8475
Description of changes:

Add table with list of previous configurations
Include button in table to rollback to previous configuration

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

New modal accepting change reason


[vue] [slider] SliderMarker does not align with SliderThumb correctly

Description
On a 0 to 100 slider, if I set the value to 75, I hope that SliderThumb sits perfectly on top of the 75 SliderMaker.
Currently the SliderMarker Is not aligned with the SliderThumb.
Link to Reproduction
https://ark-ui.com/docs/vue/components/slider
Steps to reproduce
Just add a style background:red; to the marker elements. Note how even if the value is 75, the SliderMarker is not aligned with the SliderThumb

Ark UI Version
0.4.0
Framework

[ ] React
[ ] Solid
[X] Vue

Browser
all
Additional Information
Contrary to the SliderMaker, the SliderThumb is not positioned linearly. When the slider value is 75, the thumb is placed 75% left but it's offset by a ratio derived from its size.
This same offset needs to be applied to marks so that they align perfectly with the thumb.

This will align top-left edge of the SliderMaker bounding-box with the thumb, we would need to still apply transform: translateX(-50%)  to each SliderMaker to that its box aligns center with the SliderThumb. Here's a screenshot (hardcoded).

Code references @zag-js/slider:

Offset calculation fn
transformer

Thanks for such a detailed issue breakdown @renatodeleao.
I just pushed a fix for this. We'll release an update shortly.
If the issue persists after upgrading, I'll re-open it.

@segunadebayo thanks for the fix! Latest version of @ark-ui/vue (0.6.0) still installs<EMAIL_ADDRESS>I'll let you know when you guys cut a new release for ark-ui/vue.


build(app): optimize app docker image by use Next.js standalone output mode

I change a way to reduce app docker image size. Next.js can set output to standalone mode, which copies only the necessary files for a production deployment including select files in node_modules. So, the target docker image can only include the minimal necessary files to host the app.

If someone want to host it locally without docker, they can also simply run yarn build && node ./ui/.next/standalone/server.js

Hi, as I stated in your other PRs for optimizing the docker image I still don't think there is a need for this. We're not really going crazy on production, the speed is really great and the images and decent in size. This would more harder to maintain than the Dockerfile we provide.


Feature request: Forward ref to the input element

Motivation
I'm developing a feature where I wish to get the current value of the internal input.rti--input element.
Suppose the user starts typing the first tag in an empty tag input component. If the user forgets to press "Enter" to add the tag, the value state remains an empty array.

This can be problematic if the user submits the form now since we're submitting [] instead of ["papaya"] in the form data. I want to be more lenient by auto-inserting any value in the <input> element into the value state whenever the user submits.
Suggested API Change
I suggest that we can expose a new prop called ref, which will be forwarded to the <input> element of classname rti--input. So it would look something like:
const [selected, setSelected] = useState(["papaya"]);
const ref = useRef<HTMLInputElement>(null);  // 👈

<TagsInput
  ref={ref}  // 👈
  value={selected}
  onChange={setSelected}
  name="fruits"
  placeHolder="enter fruits"
/>

Update: I'm able to find a workaround by using onBlur to solve the above problem without the need of adding forward refs.
It may be still useful to implement forward ref even though my use case no longer needs it. Feel free to close this issue if you don't find this feature necessary :smile:

I can make use of onBlur prop to add any value in the <input> element to the array state whenever the input loses focus:

export default function App() {
  const [selected, setSelected] = useState(["papaya"]);
  return (

Add Fruits

{JSON.stringify(selected)}

      <TagsInput
        value={selected}
        onChange={setSelected}
        // 👇 Adds the value in input to `selected` when loses focus
        onBlur={(e) => {
          const value = e.target.value;
          if (!selected.includes(value) && value !== "") {
            setSelected([...selected, value]);
            e.target.value = "";
          }
        }}
        name="fruits"
        placeHolder="enter fruits"
      />
      press enter to add new tag

  );
}

Demo (the fruit is added automatically whenever I click away without pressing "Enter"):
https://user-images.githubusercontent.com/57580593/209638191-73a1e6ca-9d75-4d92-9aa2-cd4a3686f9d2.mp4

Forward ref will be really helpful because it can be integrated with libraries like form hooks