TPI parameters are not set when creating a new over_climate with valve regulation - 6.8.0Beta9

Description:
I wanted to try the new "Direct control of valve" feature in the beta
After I updated to the latest 6.8.0Beta9 I added a central configuration.
Then I tried to add a "Thermostat over a climate".

Set the Name, Temperature, Climate entity, removed fan mode
add the Direct control of valve
Then I added the opening, closing degrees and the offset
After that I clicked All done

Now V-Therm didn't create a new climate entity
Then I tried to add one with no self regulation, this worked
Then I tried to edit this working device to add the valve control.
After that the climate entity was removed again, as in the image

I uploaded the photo, because I did not know how to exactly to get the yaml.
Should I copy every attribute from every entity?
Also, if you edit the V-Therm and want to remove the Direct control of valve you get the following error.
And if you try to remove the valves manually before that, you get the same error too.
The number of valve entities for valve regulation should be equal to the number of underlyings
Debug log

2024-11-26 19:03:38.234 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration hacs which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant
2024-11-26 19:03:38.234 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration better_thermostat which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant
2024-11-26 19:03:38.235 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration spook_inverse which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant
2024-11-26 19:03:38.235 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration versatile_thermostat which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant
2024-11-26 19:03:38.235 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration spook which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant
2024-11-26 19:03:38.235 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration scheduler which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant
2024-11-26 19:03:38.603 INFO (MainThread) [homeassistant.setup] Setting up system_log
2024-11-26 19:03:38.641 INFO (MainThread) [homeassistant.setup] Setup of domain logger took 0.04 seconds
2024-11-26 19:03:38.641 INFO (MainThread) [homeassistant.setup] Setup of domain system_log took 0.04 seconds
2024-11-26 19:03:38.641 INFO (MainThread) [homeassistant.bootstrap] Setting up frontend: {'frontend'}
2024-11-26 19:03:38.641 INFO (MainThread) [homeassistant.setup] Setting up http
2024-11-26 19:03:38.641 INFO (MainThread) [homeassistant.setup] Setting up device_automation
2024-11-26 19:03:38.641 INFO (MainThread) [homeassistant.setup] Setup of domain device_automation took 0.00 seconds
2024-11-26 19:03:38.644 INFO (MainThread) [homeassistant.setup] Setup of domain http took 0.00 seconds
2024-11-26 19:03:38.645 INFO (MainThread) [homeassistant.setup] Setting up auth
2024-11-26 19:03:38.645 INFO (MainThread) [homeassistant.setup] Setup of domain auth took 0.00 seconds
2024-11-26 19:03:38.645 INFO (MainThread) [homeassistant.setup] Setting up config
2024-11-26 19:03:38.646 INFO (MainThread) [homeassistant.setup] Setup of domain config took 0.00 seconds
2024-11-26 19:03:38.646 INFO (MainThread) [homeassistant.setup] Setting up diagnostics
2024-11-26 19:03:38.647 INFO (MainThread) [homeassistant.setup] Setup of domain diagnostics took 0.00 seconds
2024-11-26 19:03:38.647 INFO (MainThread) [homeassistant.setup] Setting up file_upload
2024-11-26 19:03:38.647 INFO (MainThread) [homeassistant.setup] Setup of domain file_upload took 0.00 seconds
2024-11-26 19:03:38.647 INFO (MainThread) [homeassistant.setup] Setting up image_upload
2024-11-26 19:03:38.647 INFO (MainThread) [homeassistant.setup] Setup of domain image_upload took 0.00 seconds
2024-11-26 19:03:38.647 INFO (MainThread) [homeassistant.setup] Setting up repairs
2024-11-26 19:03:38.648 INFO (MainThread) [homeassistant.setup] Setup of domain repairs took 0.00 seconds
2024-11-26 19:03:38.648 INFO (MainThread) [homeassistant.setup] Setting up websocket_api
2024-11-26 19:03:38.648 INFO (MainThread) [homeassistant.setup] Setup of domain websocket_api took 0.00 seconds
2024-11-26 19:03:38.648 INFO (MainThread) [homeassistant.setup] Setting up api
2024-11-26 19:03:38.648 INFO (MainThread) [homeassistant.setup] Setup of domain api took 0.00 seconds
2024-11-26 19:03:38.648 INFO (MainThread) [homeassistant.setup] Setting up person
2024-11-26 19:03:38.649 INFO (MainThread) [homeassistant.setup] Setting up search
2024-11-26 19:03:38.649 INFO (MainThread) [homeassistant.setup] Setup of domain search took 0.00 seconds
2024-11-26 19:03:38.649 INFO (MainThread) [homeassistant.setup] Setup of domain person took 0.00 seconds
2024-11-26 19:03:38.649 INFO (MainThread) [homeassistant.setup] Setting up onboarding
2024-11-26 19:03:38.649 INFO (MainThread) [homeassistant.setup] Setup of domain onboarding took 0.00 seconds
2024-11-26 19:03:38.650 INFO (MainThread) [homeassistant.setup] Setting up lovelace
2024-11-26 19:03:38.650 INFO (MainThread) [homeassistant.setup] Setup of domain lovelace took 0.00 seconds
2024-11-26 19:03:38.650 INFO (MainThread) [homeassistant.setup] Setting up frontend
2024-11-26 19:03:38.653 INFO (MainThread) [homeassistant.setup] Setup of domain frontend took 0.00 seconds
2024-11-26 19:03:38.654 INFO (MainThread) [homeassistant.bootstrap] Setting up recorder: {'recorder'}
2024-11-26 19:03:38.654 INFO (MainThread) [homeassistant.setup] Setting up recorder
2024-11-26 19:03:38.655 INFO (MainThread) [homeassistant.components.http] Now listening on port 8123
2024-11-26 19:03:38.656 INFO (MainThread) [homeassistant.setup] Setup of domain http took 0.00 seconds
2024-11-26 19:03:38.699 INFO (MainThread) [homeassistant.setup] Setup of domain recorder took 0.04 seconds
2024-11-26 19:03:38.699 INFO (MainThread) [homeassistant.bootstrap] Setting up stage 1: {'hassio', 'network', 'websocket_api', 'webhook', 'bluetooth', 'http', 'usb', 'repairs', 'api', 'auth', 'zeroconf', 'ssdp', 'cloud', 'dhcp'}
2024-11-26 19:03:38.699 INFO (MainThread) [homeassistant.setup] Setting up hassio
2024-11-26 19:03:38.700 INFO (MainThread) [homeassistant.setup] Setting up network
2024-11-26 19:03:38.700 INFO (MainThread) [homeassistant.setup] Setup of domain network took 0.00 seconds
2024-11-26 19:03:38.700 INFO (MainThread) [homeassistant.setup] Setting up webhook
2024-11-26 19:03:38.700 INFO (MainThread) [homeassistant.setup] Setup of domain webhook took 0.00 seconds
2024-11-26 19:03:38.708 INFO (MainThread) [homeassistant.setup] Setting up usb
2024-11-26 19:03:38.708 INFO (MainThread) [homeassistant.setup] Setup of domain usb took 0.00 seconds
2024-11-26 19:03:38.772 INFO (MainThread) [homeassistant.setup] Setting up zeroconf
2024-11-26 19:03:38.775 INFO (MainThread) [homeassistant.components.zeroconf] Starting Zeroconf broadcast
2024-11-26 19:03:38.775 INFO (MainThread) [homeassistant.setup] Setup of domain zeroconf took 0.00 seconds
2024-11-26 19:03:38.788 INFO (MainThread) [homeassistant.setup] Setting up ssdp
2024-11-26 19:03:38.790 INFO (MainThread) [homeassistant.setup] Setup of domain ssdp took 0.00 seconds
2024-11-26 19:03:38.872 INFO (MainThread) [homeassistant.setup] Setup of domain hassio took 0.17 seconds
2024-11-26 19:03:38.897 INFO (MainThread) [homeassistant.setup] Setting up binary_sensor
2024-11-26 19:03:38.897 INFO (MainThread) [homeassistant.setup] Setup of domain binary_sensor took 0.00 seconds
2024-11-26 19:03:38.897 INFO (MainThread) [homeassistant.components.binary_sensor] Setting up hassio.binary_sensor
2024-11-26 19:03:38.898 INFO (MainThread) [homeassistant.setup] Setting up sensor
2024-11-26 19:03:38.898 INFO (MainThread) [homeassistant.setup] Setup of domain sensor took 0.00 seconds
2024-11-26 19:03:38.898 INFO (MainThread) [homeassistant.components.sensor] Setting up hassio.sensor
2024-11-26 19:03:38.899 INFO (MainThread) [homeassistant.setup] Setting up update
2024-11-26 19:03:38.899 INFO (MainThread) [homeassistant.setup] Setup of domain update took 0.00 seconds
2024-11-26 19:03:38.900 INFO (MainThread) [homeassistant.components.update] Setting up hassio.update
2024-11-26 19:03:38.926 INFO (MainThread) [homeassistant.setup] Setting up cloud
2024-11-26 19:03:38.927 INFO (MainThread) [homeassistant.setup] Setting up ffmpeg
2024-11-26 19:03:38.927 INFO (MainThread) [homeassistant.setup] Setup of domain ffmpeg took 0.00 seconds
2024-11-26 19:03:38.927 INFO (MainThread) [homeassistant.setup] Setting up tts
2024-11-26 19:03:38.927 INFO (MainThread) [homeassistant.setup] Setup of domain cloud took 0.00 seconds
2024-11-26 19:03:38.929 INFO (MainThread) [homeassistant.setup] Setup of domain tts took 0.00 seconds
2024-11-26 19:03:39.199 INFO (MainThread) [homeassistant.setup] Setting up dhcp
2024-11-26 19:03:39.199 INFO (MainThread) [homeassistant.setup] Setup of domain dhcp took 0.00 seconds
2024-11-26 19:03:39.225 INFO (MainThread) [homeassistant.setup] Setting up bluetooth
2024-11-26 19:03:39.239 INFO (MainThread) [homeassistant.setup] Setup of domain bluetooth took 0.01 seconds
2024-11-26 19:03:39.239 INFO (MainThread) [homeassistant.bootstrap] Setting up stage 2: {'ffmpeg', 'select', 'tag', 'mobile_app', 'sun', 'schedule', 'stream', 'default_config', 'script', 'application_credentials', 'counter', 'ipp', 'blueprint', 'device_automation', 'input_number', 'config', 'input_text', 'diagnostics', 'input_button', 'number', 'onboarding', 'file_upload', 'lovelace', 'history', 'person', 'input_select', 'wake_word', 'tts', 'assist_pipeline', 'energy', 'my', 'shopping_list', 'scheduler', 'google_translate', 'media_source', 'hardware', 'go2rtc', 'conversation', 'timer', 'input_datetime', 'versatile_thermostat', 'met', 'camera', 'input_boolean', 'spook', 'automation', 'intent', 'openweathermap', 'radio_browser', 'stt', 'search', 'image_upload', 'hacs', 'homeassistant_alerts', 'system_health', 'logbook', 'analytics', 'trace', 'scene', 'backup', 'persistent_notification', 'homeassistant', 'mqtt', 'zone'}
2024-11-26 19:03:39.239 INFO (MainThread) [homeassistant.setup] Setting up select
2024-11-26 19:03:39.240 INFO (MainThread) [homeassistant.setup] Setup of domain select took 0.00 seconds
2024-11-26 19:03:39.240 INFO (MainThread) [homeassistant.setup] Setting up camera
2024-11-26 19:03:39.241 INFO (MainThread) [homeassistant.setup] Setup of domain camera took 0.00 seconds
2024-11-26 19:03:39.241 INFO (MainThread) [homeassistant.setup] Setting up stt
2024-11-26 19:03:39.241 INFO (MainThread) [homeassistant.setup] Setup of domain stt took 0.00 seconds
2024-11-26 19:03:39.241 INFO (MainThread) [homeassistant.setup] Setting up number
2024-11-26 19:03:39.242 INFO (MainThread) [homeassistant.setup] Setup of domain number took 0.00 seconds
2024-11-26 19:03:39.242 INFO (MainThread) [homeassistant.setup] Setting up scene
2024-11-26 19:03:39.242 INFO (MainThread) [homeassistant.components.scene] Setting up homeassistant.scene
2024-11-26 19:03:39.243 INFO (MainThread) [homeassistant.setup] Setup of domain scene took 0.00 seconds
2024-11-26 19:03:39.243 INFO (MainThread) [homeassistant.setup] Setting up wake_word
2024-11-26 19:03:39.243 INFO (MainThread) [homeassistant.setup] Setup of domain wake_word took 0.00 seconds
2024-11-26 19:03:39.243 INFO (MainThread) [homeassistant.setup] Setting up history
2024-11-26 19:03:39.243 INFO (MainThread) [homeassistant.setup] Setup of domain history took 0.00 seconds
2024-11-26 19:03:39.243 INFO (MainThread) [homeassistant.setup] Setting up media_source
2024-11-26 19:03:39.244 INFO (MainThread) [homeassistant.setup] Setup of domain media_source took 0.00 seconds
2024-11-26 19:03:39.244 INFO (MainThread) [homeassistant.setup] Setting up stream
2024-11-26 19:03:39.244 INFO (MainThread) [homeassistant.setup] Setting up logbook
2024-11-26 19:03:39.245 INFO (MainThread) [homeassistant.setup] Setup of domain logbook took 0.00 seconds
2024-11-26 19:03:39.245 INFO (MainThread) [homeassistant.setup] Setting up blueprint
2024-11-26 19:03:39.245 INFO (MainThread) [homeassistant.setup] Setup of domain blueprint took 0.00 seconds
2024-11-26 19:03:39.245 INFO (MainThread) [homeassistant.setup] Setting up trace
2024-11-26 19:03:39.245 INFO (MainThread) [homeassistant.setup] Setup of domain trace took 0.00 seconds
2024-11-26 19:03:39.245 INFO (MainThread) [homeassistant.setup] Setting up script
2024-11-26 19:03:39.246 INFO (MainThread) [homeassistant.setup] Setup of domain script took 0.00 seconds
2024-11-26 19:03:39.246 INFO (MainThread) [homeassistant.setup] Setting up timer
2024-11-26 19:03:39.246 INFO (MainThread) [homeassistant.setup] Setup of domain timer took 0.00 seconds
2024-11-26 19:03:39.247 INFO (MainThread) [homeassistant.setup] Setting up input_boolean
2024-11-26 19:03:39.247 INFO (MainThread) [homeassistant.setup] Setting up input_number
2024-11-26 19:03:39.247 INFO (MainThread) [homeassistant.setup] Setup of domain input_number took 0.00 seconds
2024-11-26 19:03:39.248 INFO (MainThread) [homeassistant.setup] Setting up input_select
2024-11-26 19:03:39.249 INFO (MainThread) [homeassistant.setup] Setup of domain input_select took 0.00 seconds
2024-11-26 19:03:39.249 INFO (MainThread) [homeassistant.setup] Setting up zone
2024-11-26 19:03:39.250 INFO (MainThread) [homeassistant.setup] Setup of domain zone took 0.00 seconds
2024-11-26 19:03:39.251 INFO (MainThread) [homeassistant.setup] Setting up input_button
2024-11-26 19:03:39.251 INFO (MainThread) [homeassistant.setup] Setup of domain input_button took 0.00 seconds
2024-11-26 19:03:39.251 INFO (MainThread) [homeassistant.setup] Setting up system_health
2024-11-26 19:03:39.251 INFO (MainThread) [homeassistant.setup] Setup of domain system_health took 0.00 seconds
2024-11-26 19:03:39.252 INFO (MainThread) [homeassistant.setup] Setup of domain input_boolean took 0.01 seconds
2024-11-26 19:03:39.281 INFO (MainThread) [homeassistant.setup] Setting up intent
2024-11-26 19:03:39.281 INFO (MainThread) [homeassistant.setup] Setup of domain intent took 0.00 seconds
2024-11-26 19:03:39.282 INFO (MainThread) [homeassistant.setup] Setting up conversation
2024-11-26 19:03:39.282 INFO (MainThread) [homeassistant.setup] Setup of domain conversation took 0.00 seconds
2024-11-26 19:03:39.282 INFO (MainThread) [homeassistant.setup] Setting up assist_pipeline
2024-11-26 19:03:39.283 INFO (MainThread) [homeassistant.setup] Setup of domain assist_pipeline took 0.00 seconds
2024-11-26 19:03:39.298 INFO (MainThread) [homeassistant.setup] Setting up energy
2024-11-26 19:03:39.298 INFO (MainThread) [homeassistant.setup] Setup of domain energy took 0.00 seconds
2024-11-26 19:03:39.299 INFO (MainThread) [homeassistant.setup] Setting up my
2024-11-26 19:03:39.299 INFO (MainThread) [homeassistant.setup] Setup of domain my took 0.00 seconds
2024-11-26 19:03:39.311 INFO (MainThread) [homeassistant.setup] Setting up shopping_list
2024-11-26 19:03:39.311 INFO (MainThread) [homeassistant.setup] Setup of domain shopping_list took 0.00 seconds
2024-11-26 19:03:39.318 INFO (MainThread) [homeassistant.setup] Setup of domain stream took 0.07 seconds
2024-11-26 19:03:39.323 INFO (MainThread) [homeassistant.setup] Setting up scheduler
2024-11-26 19:03:39.323 INFO (MainThread) [homeassistant.setup] Setup of domain scheduler took 0.00 seconds
2024-11-26 19:03:39.324 INFO (MainThread) [homeassistant.setup] Setting up tag
2024-11-26 19:03:39.325 INFO (MainThread) [homeassistant.setup] Setup of domain tag took 0.00 seconds
2024-11-26 19:03:39.327 INFO (MainThread) [homeassistant.setup] Setting up sun
2024-11-26 19:03:39.327 INFO (MainThread) [homeassistant.setup] Setup of domain sun took 0.00 seconds
2024-11-26 19:03:39.328 INFO (MainThread) [homeassistant.components.sensor] Setting up sun.sensor
2024-11-26 19:03:39.329 INFO (MainThread) [homeassistant.setup] Setting up google_translate
2024-11-26 19:03:39.329 INFO (MainThread) [homeassistant.setup] Setup of domain google_translate took 0.00 seconds
2024-11-26 19:03:39.332 INFO (MainThread) [homeassistant.setup] Setting up schedule
2024-11-26 19:03:39.333 INFO (MainThread) [homeassistant.setup] Setup of domain schedule took 0.00 seconds
2024-11-26 19:03:39.336 INFO (MainThread) [homeassistant.setup] Setting up hardware
2024-11-26 19:03:39.430 INFO (MainThread) [homeassistant.setup] Setting up go2rtc
2024-11-26 19:03:39.439 INFO (MainThread) [homeassistant.setup] Setting up homeassistant_alerts
2024-11-26 19:03:39.439 INFO (MainThread) [homeassistant.setup] Setup of domain homeassistant_alerts took 0.00 seconds
2024-11-26 19:03:39.439 INFO (MainThread) [homeassistant.setup] Setting up application_credentials
2024-11-26 19:03:39.439 INFO (MainThread) [homeassistant.setup] Setup of domain application_credentials took 0.00 seconds
2024-11-26 19:03:39.439 INFO (MainThread) [homeassistant.setup] Setup of domain hardware took 0.10 seconds
2024-11-26 19:03:39.439 INFO (MainThread) [homeassistant.setup] Setting up input_datetime
2024-11-26 19:03:39.440 INFO (MainThread) [homeassistant.setup] Setup of domain input_datetime took 0.00 seconds
2024-11-26 19:03:39.447 INFO (MainThread) [homeassistant.setup] Setting up versatile_thermostat
2024-11-26 19:03:39.447 INFO (MainThread) [custom_components.versatile_thermostat] Initializing versatile_thermostat integration with config: None
2024-11-26 19:03:39.447 INFO (MainThread) [custom_components.versatile_thermostat] No global config from configuration.yaml available
2024-11-26 19:03:39.447 INFO (MainThread) [homeassistant.setup] Setup of domain versatile_thermostat took 0.00 seconds
2024-11-26 19:03:39.451 INFO (MainThread) [homeassistant.setup] Setting up counter
2024-11-26 19:03:39.451 INFO (MainThread) [homeassistant.setup] Setup of domain counter took 0.00 seconds
2024-11-26 19:03:39.460 INFO (MainThread) [homeassistant.setup] Setting up ipp
2024-11-26 19:03:39.460 INFO (MainThread) [homeassistant.setup] Setup of domain ipp took 0.00 seconds
2024-11-26 19:03:39.466 INFO (MainThread) [homeassistant.setup] Setting up met
2024-11-26 19:03:39.466 INFO (MainThread) [homeassistant.setup] Setup of domain met took 0.00 seconds
2024-11-26 19:03:39.475 INFO (MainThread) [homeassistant.setup] Setting up spook
2024-11-26 19:03:39.475 INFO (MainThread) [homeassistant.setup] Setup of domain spook took 0.00 seconds
2024-11-26 19:03:39.475 INFO (MainThread) [homeassistant.setup] Setting up input_text
2024-11-26 19:03:39.476 INFO (MainThread) [homeassistant.setup] Setup of domain input_text took 0.00 seconds
2024-11-26 19:03:39.486 INFO (MainThread) [homeassistant.setup] Setting up openweathermap
2024-11-26 19:03:39.486 INFO (MainThread) [homeassistant.setup] Setup of domain openweathermap took 0.00 seconds
2024-11-26 19:03:39.486 INFO (MainThread) [pyopenweathermap.client.owm_client_factory] Initializing OWMClient with api type: v3.0
2024-11-26 19:03:39.731 INFO (SyncWorker_4) [homeassistant.loader] Loaded template from homeassistant.components.template
2024-11-26 19:03:39.733 INFO (MainThread) [homeassistant.setup] Setting up radio_browser
2024-11-26 19:03:39.733 INFO (MainThread) [homeassistant.setup] Setup of domain radio_browser took 0.00 seconds
2024-11-26 19:03:39.735 INFO (MainThread) [homeassistant.setup] Setup of domain go2rtc took 0.30 seconds
2024-11-26 19:03:39.747 INFO (MainThread) [homeassistant.setup] Setting up mqtt
2024-11-26 19:03:39.747 INFO (MainThread) [homeassistant.setup] Setup of domain mqtt took 0.00 seconds
2024-11-26 19:03:39.775 INFO (MainThread) [homeassistant.setup] Setting up hacs
2024-11-26 19:03:39.775 INFO (MainThread) [homeassistant.setup] Setup of domain hacs took 0.00 seconds
2024-11-26 19:03:39.775 INFO (MainThread) [custom_components.hacs]
-------------------------------------------------------------------
HACS (Home Assistant Community Store)

Version: 2.0.1
This is a custom integration
If you have any issues with this you need to open an issue here:
https://github.com/hacs/integration/issues
-------------------------------------------------------------------

2024-11-26 19:03:39.782 INFO (MainThread) [custom_components.hacs] <HacsData restore> Restore started
2024-11-26 19:03:39.803 INFO (MainThread) [custom_components.hacs] <HacsData restore> Restore done
2024-11-26 19:03:39.803 INFO (MainThread) [custom_components.hacs] Enable category: integration
2024-11-26 19:03:39.803 INFO (MainThread) [custom_components.hacs] Enable category: plugin
2024-11-26 19:03:39.803 INFO (MainThread) [custom_components.hacs] Enable category: template
2024-11-26 19:03:39.804 INFO (MainThread) [custom_components.hacs] Enable category: theme
2024-11-26 19:03:39.807 INFO (MainThread) [homeassistant.setup] Setting up backup
2024-11-26 19:03:39.807 INFO (MainThread) [homeassistant.setup] Setup of domain backup took 0.00 seconds
2024-11-26 19:03:39.808 INFO (MainThread) [custom_components.hacs] Setting up plugin endpoint
2024-11-26 19:03:39.808 INFO (MainThread) [custom_components.hacs] <HacsFrontend> storage mode, cache for /hacsfiles/: True
2024-11-26 19:03:39.813 INFO (MainThread) [homeassistant.components.sensor] Setting up energy.sensor
2024-11-26 19:03:39.820 INFO (MainThread) [homeassistant.setup] Setting up analytics
2024-11-26 19:03:39.820 INFO (MainThread) [homeassistant.setup] Setup of domain analytics took 0.00 seconds
2024-11-26 19:03:39.822 INFO (MainThread) [homeassistant.setup] Setting up todo
2024-11-26 19:03:39.824 INFO (MainThread) [homeassistant.setup] Setup of domain todo took 0.00 seconds
2024-11-26 19:03:39.824 INFO (MainThread) [homeassistant.components.todo] Setting up shopping_list.todo
2024-11-26 19:03:39.911 INFO (MainThread) [homeassistant.setup] Setting up mobile_app
2024-11-26 19:03:39.911 INFO (MainThread) [homeassistant.setup] Setting up notify
2024-11-26 19:03:39.911 INFO (MainThread) [homeassistant.setup] Setup of domain notify took 0.00 seconds
2024-11-26 19:03:39.911 INFO (MainThread) [homeassistant.setup] Setup of domain mobile_app took 0.00 seconds
2024-11-26 19:03:39.912 INFO (MainThread) [homeassistant.components.binary_sensor] Setting up mobile_app.binary_sensor
2024-11-26 19:03:39.912 INFO (MainThread) [homeassistant.setup] Setting up device_tracker
2024-11-26 19:03:39.912 INFO (MainThread) [homeassistant.setup] Setup of domain device_tracker took 0.00 seconds
2024-11-26 19:03:39.912 INFO (MainThread) [homeassistant.components.device_tracker] Setting up mobile_app.device_tracker
2024-11-26 19:03:39.913 INFO (MainThread) [homeassistant.components.sensor] Setting up mobile_app.sensor
2024-11-26 19:03:39.914 INFO (MainThread) [homeassistant.components.notify] Setting up notify.mobile_app
2024-11-26 19:03:39.914 INFO (MainThread) [homeassistant.setup] Setting up default_config
2024-11-26 19:03:39.914 INFO (MainThread) [homeassistant.setup] Setup of domain default_config took 0.00 seconds
2024-11-26 19:03:39.918 INFO (MainThread) [homeassistant.setup] Setting up switch
2024-11-26 19:03:39.918 INFO (MainThread) [homeassistant.setup] Setup of domain switch took 0.00 seconds
2024-11-26 19:03:39.918 INFO (MainThread) [homeassistant.components.switch] Setting up scheduler.switch
2024-11-26 19:03:39.926 INFO (MainThread) [homeassistant.components.tts] Setting up google_translate.tts
2024-11-26 19:03:39.933 INFO (MainThread) [homeassistant.components.select] Setting up versatile_thermostat.select
2024-11-26 19:03:39.934 INFO (MainThread) [homeassistant.setup] Setting up climate
2024-11-26 19:03:39.934 INFO (MainThread) [homeassistant.setup] Setup of domain climate took 0.00 seconds
2024-11-26 19:03:39.935 INFO (MainThread) [homeassistant.components.climate] Setting up versatile_thermostat.climate
2024-11-26 19:03:39.935 INFO (MainThread) [homeassistant.components.sensor] Setting up versatile_thermostat.sensor
2024-11-26 19:03:39.935 INFO (MainThread) [homeassistant.components.number] Setting up versatile_thermostat.number
2024-11-26 19:03:39.936 INFO (MainThread) [homeassistant.components.binary_sensor] Setting up versatile_thermostat.binary_sensor
2024-11-26 19:03:39.936 INFO (MainThread) [homeassistant.components.switch] Setting up versatile_thermostat.switch
2024-11-26 19:03:39.937 INFO (MainThread) [homeassistant.components.select] Setting up versatile_thermostat.select
2024-11-26 19:03:39.937 INFO (MainThread) [homeassistant.components.climate] Setting up versatile_thermostat.climate
2024-11-26 19:03:39.937 INFO (MainThread) [custom_components.versatile_thermostat.base_thermostat] VersatileThermostat-V-Arbeitszimmer - Updating VersatileThermostat with infos {'ac_mode': False, 'auto_fan_mode': 'auto_fan_none', 'auto_regulation_dtemp': 0.5, 'auto_regulation_mode': 'auto_regulation_valve', 'auto_regulation_periode_min': 5, 'auto_regulation_use_device_temp': False, 'auto_start_stop_level': 'auto_start_stop_none', 'central_boiler_activation_service': None, 'central_boiler_deactivation_service': None, 'closing_degree_entity_ids': ['number.thermostat_arbeitszimmer_valve_closing_degree'], 'cycle_min': 5, 'device_power': 1.0, 'max_power_sensor_entity_id': None, 'motion_sensor_entity_id': None, 'name': 'V-Arbeitszimmer', 'offset_calibration_entity_ids': ['number.thermostat_arbeitszimmer_local_temperature_calibration'], 'opening_degree_entity_ids': ['number.thermostat_arbeitszimmer_valve_opening_degree'], 'power_sensor_entity_id': None, 'presence_sensor_entity_id': None, 'proportional_function': 'tpi', 'temperature_sensor_entity_id': 'sensor.th_sensor_arbeitszimmer_temperature', 'thermostat_type': 'thermostat_over_climate', 'underlying_entity_ids': ['climate.thermostat_arbeitszimmer'], 'use_advanced_central_config': True, 'use_auto_start_stop_feature': False, 'use_central_boiler_feature': False, 'use_central_mode': True, 'use_main_central_config': True, 'use_motion_central_config': False, 'use_motion_feature': False, 'use_power_central_config': False, 'use_power_feature': False, 'use_presence_central_config': False, 'use_presence_feature': False, 'use_presets_central_config': True, 'use_tpi_central_config': True, 'use_window_central_config': False, 'use_window_feature': False, 'used_by_controls_central_boiler': False, 'window_auto_close_threshold': None, 'window_auto_max_duration': None, 'window_auto_open_threshold': None, 'window_sensor_entity_id': None}
2024-11-26 19:03:39.937 INFO (MainThread) [custom_components.versatile_thermostat.base_thermostat] VersatileThermostat-V-Arbeitszimmer - The merged configuration is {'auto_start_stop_level': 'auto_start_stop_none', 'central_boiler_activation_service': None, 'central_boiler_deactivation_service': None, 'external_temperature_sensor_entity_id': 'sensor.openweathermap_temperature', 'max_power_sensor_entity_id': None, 'minimal_activation_delay': 10, 'motion_sensor_entity_id': None, 'name': 'V-Arbeitszimmer', 'power_sensor_entity_id': None, 'presence_sensor_entity_id': None, 'security_default_on_percent': 0.1, 'security_delay_min': 60, 'security_min_on_percent': 0.5, 'step_temperature': 0.1, 'temp_max': 35.0, 'temp_min': 7.0, 'thermostat_type': 'thermostat_over_climate', 'use_advanced_central_config': True, 'use_auto_start_stop_feature': False, 'use_central_boiler_feature': False, 'use_central_mode': True, 'use_main_central_config': True, 'use_motion_central_config': False, 'use_motion_feature': False, 'use_power_central_config': False, 'use_power_feature': False, 'use_presence_central_config': False, 'use_presence_feature': False, 'use_presets_central_config': True, 'use_tpi_central_config': True, 'use_window_central_config': False, 'use_window_feature': False, 'window_auto_close_threshold': None, 'window_auto_max_duration': None, 'window_auto_open_threshold': None, 'window_sensor_entity_id': None, 'ac_mode': False, 'auto_fan_mode': 'auto_fan_none', 'auto_regulation_dtemp': 0.5, 'auto_regulation_mode': 'auto_regulation_valve', 'auto_regulation_periode_min': 5, 'auto_regulation_use_device_temp': False, 'closing_degree_entity_ids': ['number.thermostat_arbeitszimmer_valve_closing_degree'], 'cycle_min': 5, 'device_power': 1.0, 'offset_calibration_entity_ids': ['number.thermostat_arbeitszimmer_local_temperature_calibration'], 'opening_degree_entity_ids': ['number.thermostat_arbeitszimmer_valve_opening_degree'], 'proportional_function': 'tpi', 'temperature_sensor_entity_id': 'sensor.th_sensor_arbeitszimmer_temperature', 'underlying_entity_ids': ['climate.thermostat_arbeitszimmer'], 'used_by_controls_central_boiler': False}
2024-11-26 19:03:39.937 INFO (MainThread) [custom_components.versatile_thermostat.base_thermostat] VersatileThermostat-V-Arbeitszimmer - Power management is not fully configured
2024-11-26 19:03:39.937 ERROR (MainThread) [custom_components.versatile_thermostat.prop_algorithm] V-Arbeitszimmer - configuration is wrong. function_type=tpi, entity_id is V-Arbeitszimmer, tpi_coef_int is None, tpi_coef_ext is None, cycle_min is 5, minimal_activation_delay is 10
2024-11-26 19:03:39.937 ERROR (MainThread) [homeassistant.components.climate] Error while setting up versatile_thermostat platform for climate
Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/helpers/entity_platform.py", line 365, in _async_setup_platform
    await asyncio.shield(awaitable)
  File "/config/custom_components/versatile_thermostat/climate.py", line 62, in async_setup_entry
    entity = ThermostatOverClimateValve(hass, unique_id, name, entry.data)
             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/config/custom_components/versatile_thermostat/thermostat_climate_valve.py", line 54, in __init__
    super().__init__(hass, unique_id, name, entry_infos)
  File "/config/custom_components/versatile_thermostat/thermostat_climate.py", line 91, in __init__
    super().__init__(hass, unique_id, name, entry_infos)
  File "/config/custom_components/versatile_thermostat/base_thermostat.py", line 242, in __init__
    self.post_init(entry_infos)
  File "/config/custom_components/versatile_thermostat/thermostat_climate_valve.py", line 80, in post_init
    self._prop_algorithm = PropAlgorithm(
                           ^^^^^^^^^^^^^^
  File "/config/custom_components/versatile_thermostat/prop_algorithm.py", line 66, in __init__
    raise TypeError(
TypeError: TPI parameters are not set correctly. VTherm will not work as expected. Please reconfigure it correctly. See previous log for values
2024-11-26 19:03:39.943 INFO (MainThread) [homeassistant.components.sensor] Setting up versatile_thermostat.sensor
2024-11-26 19:03:39.945 INFO (MainThread) [homeassistant.components.number] Setting up versatile_thermostat.number
2024-11-26 19:03:39.945 INFO (MainThread) [homeassistant.components.binary_sensor] Setting up versatile_thermostat.binary_sensor
2024-11-26 19:03:39.945 INFO (MainThread) [homeassistant.components.switch] Setting up versatile_thermostat.switch
2024-11-26 19:03:39.955 INFO (MainThread) [homeassistant.components.sensor] Setting up ipp.sensor
2024-11-26 19:03:40.085 INFO (MainThread) [homeassistant.components.switch] Setting up hacs.switch
2024-11-26 19:03:40.087 INFO (MainThread) [homeassistant.components.update] Setting up hacs.update
2024-11-26 19:03:40.089 INFO (MainThread) [custom_components.hacs] Stage changed: setup
2024-11-26 19:03:40.090 INFO (MainThread) [custom_components.hacs] Stage changed: waiting
2024-11-26 19:03:40.090 INFO (MainThread) [custom_components.hacs] Setup complete, waiting for Home Assistant before startup tasks starts
2024-11-26 19:03:40.092 INFO (MainThread) [homeassistant.setup] Setting up weather
2024-11-26 19:03:40.092 INFO (MainThread) [homeassistant.setup] Setup of domain weather took 0.00 seconds
2024-11-26 19:03:40.092 INFO (MainThread) [homeassistant.components.weather] Setting up met.weather
2024-11-26 19:03:40.094 INFO (MainThread) [homeassistant.components.sensor] Setting up openweathermap.sensor
2024-11-26 19:03:40.096 INFO (MainThread) [homeassistant.components.weather] Setting up openweathermap.weather
2024-11-26 19:03:40.127 INFO (MainThread) [homeassistant.components.sensor] Setting up mqtt.sensor
2024-11-26 19:03:40.128 INFO (MainThread) [homeassistant.components.switch] Setting up mqtt.switch
2024-11-26 19:03:40.128 INFO (MainThread) [homeassistant.components.select] Setting up mqtt.select
2024-11-26 19:03:40.128 INFO (MainThread) [homeassistant.setup] Setting up button
2024-11-26 19:03:40.128 INFO (MainThread) [homeassistant.setup] Setup of domain button took 0.00 seconds
2024-11-26 19:03:40.128 INFO (MainThread) [homeassistant.components.button] Setting up mqtt.button

Then there is another bug I guess.
In the main configuration both TPI values are set.
I unchecked use central configuration for that, and set them manual and now it is working.

Hello @Dave811 ,

In the main configuration both TPI values are set.

When you say in the main configuration, you mean in the central configuration ?
I think it is too late, but can you remember what steps you have done to reproduce this bug ?
In the first post it is written:

After I updated to the latest 6.8.0Beta9,
I added a central configuration. --> so haven't any central configuration yet. Did you remember to set the TPI parameters at this step or keep the default values ?
Then I tried to add a "Thermostat over a climate".     ---> I suppose you didn't check the 'use central configuration'. Did you remember if you have displayed the TPI menu

I'm looking for a way to reproduce.

I added the central configuration with most default settings and I didn't
touch the tpi settings, but they had the default values in there
The central configuration is checked by default, for the thermostat I
guess. I can try it later the day again
Jean-Marc Collin @.***> schrieb am Mi., 27. Nov. 2024,
08:15:

Hello @Dave811 https://github.com/Dave811 ,
In the main configuration both TPI values are set.
When you say in the main configuration, you mean in the central
configuration ?
I think it is too late, but can you remember what steps you have done to
reproduce this bug ?
In the first post it is written:

After I updated to the latest 6.8.0Beta9,
I added a central configuration. --> so haven't any central
configuration yet. Did you remember to set the TPI parameters at this step
or keep the default values ?
Then I tried to add a "Thermostat over a climate". ---> I suppose
you didn't check the 'use central configuration'. Did you remember if you
have displayed the TPI menu

I'm looking for a way to reproduce.
—
Reply to this email directly, view it on GitHub
https://github.com/jmcollin78/versatile_thermostat/issues/665#issuecomment-2503084144,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AFAUJLXALGKZSKLRK66RTZD2CVWPTAVCNFSM6AAAAABSRBWXX6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKMBTGA4DIMJUGQ
.
You are receiving this because you were mentioned.Message ID:
@.***>

Hello, i try many and many combinations without success to reproduce. If you find a way please tell me how you do.

I close this issue which is not reproduce. Feel free to reopen if needed.


Incorrect wordings in VMSS documentation about fault domains

The sentence "Virtual machine scale sets are created with five fault domains by default in Azure regions with no zones" is incorrect per my understanding. The number of fault domains on Azure at maximum is 3, and some regions (like East Asia) have only 2. I believe the word "fault domains" is referring to "update domains" instead. Please check. Thank you.

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

ID: 6a729a8a-23ea-094d-b96a-cb628832f730
Version Independent ID: 6bed91cd-1519-032d-e589-8ea826aa8b50
Content: Manage fault domains in Azure virtual machine scale sets - Azure Virtual Machine Scale Sets
Content Source: articles/virtual-machine-scale-sets/virtual-machine-scale-sets-manage-fault-domains.md
Service: virtual-machine-scale-sets
Sub-service: availability
GitHub Login: @mimckitt
Microsoft Alias: mimckitt

@nebula0248
Thanks for the feedback! I have assigned the issue to content author to check and update the document as appropriate.

@mimckitt
Can you please check and add your comments on this doc update request as applicable.

@nebula0248 thanks again for pointing this out. 3 is the default fault domain count. 5 is the default update domain count. I have updated the doc to address this. The changes will go live later this afternoon.
#please-close


Youtube-Upload documentation says one minute.

The google-youtube-upload component's documentation on the polymer-project website says "one minute".

Page?

https://elements.polymer-project.org/elements/google-youtube-upload

This issue tracker is for the Polymer core library, not elements built with it. We'll get this moved to an appropriate spot.

Sorry didn't notice.

This is interesting - I think this might be an issue with hydrolysis. Moving to that repo.

This issue was moved to Polymer/hydrolysis#132


Language Support

Hello. Is it possible to make settings/language support?
It can be storing cookies or saving them to a file.

Hey, it's definitely possible, but right now I'm not sure that I have that much time to implement that :(

Sadly, it may be a temporary solution to enable automatic loading of all languages and, depending on the language of the clipboard, switch.


Feat/from userinterface to esperienzautente

@Fupete porting completed for this branch (text part).
A question in this commit should be solved --> https://github.com/italia/manuale-operativo-design-docs/commit/cbb0d89e0d08503a9a651200c0428fe2db2c479d
@bfabio before merging I need to move 2 folders in to the new "esperienza-utente" directory: folders are "user-interface/images" and "prototyping/media" (user-interface and prototyping directories can be deleted)

A question in this commit should be solved --> cbb0d89

Yes, I think we should add https://github.com/italia/browserslist-config-design-italia in here and have it act as the living reference of supported browsers.

@bfabio before merging I need to move 2 folders in to the new "esperienza-utente" directory: folders are "user-interface/images" and "prototyping/media" (user-interface and prototyping directories can be deleted)

Done.
Reviewing the rest as we speak.

ok @bfabio browserlist config linked here --> https://github.com/italia/manuale-operativo-design-docs/commit/f4edf5000627ec7c839a69e6a208bf92f490635b for your approval


put all option docs build flavors on equal footing

Motivation for this change
in #142040 the option docs generation was changed to not sort options.xml in the nix build. in that spirit also stop generating ascii doc and MD doc in nix, and farm that out to scripts too. to make this easier we standardize on options.json as the primary source of options documentation, generating options.xml from options.json when needed. (hopefully docbook will go away soon :crossed_fingers:)
this may slightly slow down the system build. the optionsDocBook build is definitely impacted, but the full system build seems to not be (or within the noise level of our measurements).
Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
21.11 Release Notes (or backporting 21.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module
[ ] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[x] Fits CONTRIBUTING.md.

to set a stage for this a little, this is part of an effort to cache most of the options doc build as well. json is much easier to merge than the xml output nix produces, and caching parts of the doc build requires merging options descriptions. the MD and asciidoc changes happened to line up with the need to make json the primary export format for option docs so they ended up converted as well.

Breaks NixOS with Nix 2.3, see #147265.


[$500] Workspace switcher - Workspace filter is reset after killing app

If you haven’t already, check out our contributing guidelines for onboarding and email<EMAIL_ADDRESS>to request to join our Slack channel!

Version Number: v.1.4-39-0
Reproducible in staging?: y
Reproducible in production?: y
If this was caught during regression testing, add the test name, ID and link from TestRail:
Email or phone of affected tester (no customers):
Logs: https://stackoverflow.com/c/expensify/questions/4856
Expensify/Expensify Issue URL:
Issue reported by: Applause - Internal Team
Slack conversation:
Action Performed:
Precondition:

There is at least one workspace.

Launch New Expensify app.
Open workspace switcher.
Select a different workspace.
Kill the app.
Relaunch it.
Open workspace switcher.

Expected Result:
The workspace filter is preserved after closing and relaunching the app.
Actual Result:
The workspace filter is reset to Expensify.
Workaround:
Unknown
Platforms:

Which of our officially supported platforms is this issue occurring on?

[x] Android: Native
[ ] Android: mWeb Chrome
[x] iOS: Native
[ ] iOS: mWeb Safari
[ ] MacOS: Chrome / Safari
[ ] MacOS: Desktop

Screenshots/Videos
Add any screenshot/video evidence
https://github.com/Expensify/App/assets/93399543/12fd8451-cfad-458f-ba32-987ea3da2bbc
View all open jobs on GitHub
Upwork Automation - Do Not Edit

Upwork Job URL: https://www.upwork.com/jobs/~01ef1292b6f671eb4d
Upwork Job ID:<PHONE_NUMBER>892625920
Last Price Increase: 2024-02-09

We think that this bug might be related to #wave8-collect-admins
CC @zanyrenney

Discussion https://expensify.slack.com/archives/C01GTK53T8Q/p1707678505606889

also discussing this internally

closing as we discussed this as being the desired behaviour in the thread Hayata linked above!


Windows fix

Changes all related to Windows port:

Fixes for issues #5 and issue #6.   Tested on Win10/Node 8.9.1 and Win10/Electron 1.8.3beta.3
Updated package.json to stop using a deprecated 'prepublish' script name (see https://docs.npmjs.com/misc/scripts#deprecation-note)
skip tests which will aways fail on Windows due to OS behavior (see comment in test.ls)
added missing stub for mincore() on Windows and better error checking in common code

Note that fixing issue #6 requires a relatively new Node version.  For details see https://github.com/nodejs/node/issues/6369 and https://github.com/libuv/libuv/issues/1291

Thanks, I'll have a look tomorrow before the holiday craze continues :)


log autodownload

it would be very useful feature

Please give more details. What do you suppose would be a good time it should cycle through and try to automatically download?
Good idea, though.

I think the best would be if the server tries to download logs just after establishing a connection with client.

@ngbatnicdotmil That would really hurt performance if the host had many clients... It wouldn't be very good to have an action such as establishment of a connection to have such a side effect...

maybe a schedule would be better?


Document how to set this up with Portainer

See https://github.com/danecreekphotography/node-deepstackai-trigger/issues/144 for ideas.

Install Docker
Install Portainer

sudo docker volume create portainer sudo docker run -d -p 9000:9000 --name portainer --restart always -v /var/run/docker.sock:/var/run/docker.sock -v portainer_data:/data portainer/portainer
Connect to portainer via browser:
http://<host IP>:9000

Login

Click on "local"

Click on "Stacks" in newly presented left side bar

Click on "+ Add stack" button in right side bar >  Give the stack a name: ie. ai-trigger

Past into "Web Editor" section:

`---
version: "2"
services:
ai-trigger:
image: danecreekphotography/node-deepstackai-trigger:latest
container_name: ai-trigger
environment:
- PUID=1000
- PGID=1000
- TZ=America/New York
- DEEPSTACK_URI=http://deepstack:5000/
- VERBOSE=true
volumes:
- /aiinput:/aiinput
# Host:VM
- ai-trigger:/config
ports:
- 4242:4242
restart: unless-stopped
depends_on:
- deepstack
deepstack:
image: deepquestai/deepstack:latest
container_name: deepstack
environment:
- PUID=1000
- PGID=1000
- VISION-DETECTION=True
volumes:
- deepstack:/datastore
ports:
- 5000:5000
restart: unless-stopped`

Click on "Deploy the stack"

*** Do NOT navigate away from the browser window UNTIL the deployment had completed ***
On the docker host, navigate to the /var/lib/docker/volumes/ai-trigger/_data folder.
Edit & adjust:

settings.json
triggers.json
telegram.json
mqtt.json

Acquiring a new image:
Connect to portainer via browser:
http://<host IP>:9000

Login
Click on "local"
Click on "Containers" in newly presented left side bar
Select container "ai-trigger" > Stop > Remove
Click on "Images" in left side bar
Select image with tag "danecreekphotography/node-deepstackai-trigger:latest" > Remove
Click on "Stacks" in left side bar
Click on stack "ai-trigger" > Click on "Editor" tab > Click on "Update the stack"

*** Do NOT navigate away from the browser window UNTIL the deployment had completed ***
*** All setttings will be retained ***

FYI I've taken a stab at this in Portainer 1.24.0.  Since there's support only for V2 docker-compose files, sections such as secrets: are not supported.  Personally I think there's value in delaying this documentation until Portainer 2.0 is released upon which time V3 docker-compose format will be supported.

thank you so much for this guide.
i used proxmox.
i have one container with homeassistant with mqtt broker.  i already have a VM with blueiris.  i enabled aiinput folder to be shared with a username and password.
i created another container with ubuntu. set up ssh.
i used this guide here  to set up cifs share from windows VM to a linux container:
_https://steamforge.net/wiki/index.php/How_to_mount_a_Network_Share_in_a_Linux_Container_under_Proxmox_
i then set up docker, portainer using this guide:
_https://www.juanmtech.com/set-up-hassio-in-docker-and-in-an-ubuntu-server/_
apt update
apt upgrade

apt-get install \
  apt-transport-https \
  ca-certificates \
  curl \
  gnupg-agent \
  software-properties-common

curl -fsSL https://download.docker.com/linux/ubuntu/gpg | apt-key add -

apt-key fingerprint 0EBFCD88

add-apt-repository \
 "deb [arch=amd64] https://download.docker.com/linux/ubuntu \
 $(lsb_release -cs) \
 stable"

apt-get install docker-ce docker-ce-cli containerd.io

docker run hello-world

systemctl enable docker

docker volume create portainer_data

docker run -d -p 9000:9000 \
--name portainer \
--restart always \
-v /var/run/docker.sock:/var/run/docker.sock \
-v portainer_data:/data portainer/portainer

then as above, add a new stack in portainer and paste
version: "2"
services:
  ai-trigger:
    image: danecreekphotography/node-deepstackai-trigger:latest
    container_name: ai-trigger
    ports:
      - 4242:4242
    environment:
      - PUID=1000
      - PGID=1000
      - TZ=America/Los_Angeles
    volumes:
      - /mnt/winshare:/aiinput
# Host:VM
      - ai-trigger:/config
    restart: unless-stopped
    depends_on:
      - deepstack-ai

  deepstack-ai:
    image: deepquestai/deepstack:latest
    container_name: deepstack-ai
    restart: unless-stopped
    environment:
      - PUID=1000
      - PGID=1000
      - VISION-DETECTION=True
    volumes:
      - localstorage:/datastore
    ports:
      - 5000:5000

make sure to de-select “enable access control”
use SFTP
On the docker host, navigate to the /var/lib/docker/volumes/ai-trigger/_data folder
upload settings.json and triggers.json
go to portainer/ai-trigger container and review logs to make sure everything runs correctly.

Closing old issues.


Using the GH Wiki-pages

I think that we should put the wiki pages to some use (probably after #31 is solved). This could be useful to declutter the README.md, which otherwise might become too overwhelming for people reading about PhyloProfile for the first time.
Things that could go there:

More detailed how-tos for the different functions
Explanations of the file formats
the FAQ that's now inside PhyloProfile

I quickly drafted an Installation-guide, a how-to for the input formats as well as the FAQ. All based on the help.html and the README.md. It's all in the Wiki now.


Improved file/folder drag preview for filesystem dock

Fixes & small improvements to the labels shown when dragging files/folders from the file-system dock.

Fixed folders getting an empty string label (As mentioned in #11428 by Xgor)
Added icons for files/folders in drag preview
Improved logic in the labels that appear if you are dragging a large number of files/folders

Don't show "1 more file(s)" label, as this row could have been used to list the file.
Added check for dragging folders exclusively

Merged drag_files and drag_files_and_dirs to reduce code duplication.
Simplified get_drag_data_fw and removed commented out code

Preview of the new drag:

Favorite vs favourite is just American vs British spelling. Which one does Godot use?

Yep, I usually spell it favourite, but godot seems to use the american version without the 'u'.

Needs rebasing after #10261.

The misspelling of favorite would have caused a bug and not allowed favorite folder drag events from being accepted, so thanks for catching it @Cradmon . Fixed it now & rebased.


Update test-file-02.md

@jamarw : Wow! Thanks for your contribution! The author(s) have been notified to review your proposed change.

@jamarw : Thanks for your contribution! The author(s) have been notified to review your proposed change.


Magicoder-S-DS-6.7B gguf, gptq models are not working. Please could you provide quantize models. LM studio, text generation web ui is not is not working.

you should check out  these models work


feat/vechain-integration

📝 Description
The changes enable native vechain support for the Ledger Live application. Ledger Live users should be able to manage their vechain accounts, send/receive VET and VTHO and view their transaction history, crypto and fiat balances.
❓ Context

Impacted projects: ledgerjs, ledger-live-common, ledger-live-desktop, ledger-live-mobile

✅ Checklist

[x] Test coverage
[x] Atomic delivery
[x] No breaking changes

📸 Demo

https://user-images.githubusercontent.com/79703403/235187208-4b44f793-df15-4432-b1b2-620cdc182608.mp4
https://user-images.githubusercontent.com/79703403/235188233-a804d1e3-ff92-4462-b925-6b7f41a860d6.mp4
https://user-images.githubusercontent.com/79703403/235188701-e2df5b5d-7eb2-4401-a908-d97cd3dcf53d.mp4

🚀 Expectations to reach

Add VET currency
Add VTHO token, listed as ERC20 token
Syncing VET accounts and VTHO subaccounts with the blockchain displaying the correct balances and operations list (through cli/lld/llm)
Send VET or VTHO transaction (through cli/lld/llm)
Receive VET or VTHO
Hide the graph for VTHO
Correctly displaying all the transaction information with correct links to the explorer

Hi gre, we merged fixes for both your comments last Friday, Mirko can give some specific detail in line. Our icon colour has also changed as vechain has gone through a branding change, we were directed to change from purple token colour to green. A very minor change and the updated feature branch was smoked tested.
Thanks.

Changing to draft while this is still WIP.

Changing to draft while this is still WIP.

Ledger provided the reverse proxy last Tuesday 16/5 and it has been embedded in code in this PR. The PR is now complete and awaiting final review.

👋  ESLint config has been unified on develop after we merged https://github.com/LedgerHQ/ledger-live/pull/3622 – this will improve the project consistency, remove eslint dependencies duplicates, and overall simplify the maintenance. This comes with a prettier library upgrade and unification of the prettierrc too, so you likely have conflicts with develop.
Hopefully, here is the procedure to easily fix this. please proceed as follow:
Step 1: sync your branch with develop up to the config changes:
2 cases

if your branch were continuously rebased with develop and don't have any merge commit, you can do

git rebase aa1e0ebc0a0498b4350754899b6a368fbd42e811

otherwise prefer

git merge aa1e0ebc0a0498b4350754899b6a368fbd42e811

then, apply the config
pnpm i
pnpm lint:fix --force

if there are remaining errors that lint couldn't fix, please fix them and pnpm lint again.
then commit in your branch.
git commit -a -m "chore: lint fixes"

Step 2: finalize the rebase/merge with develop
2 cases

if your branch were continuously rebased with develop and don't have any merge commit, you can do

git pull --rebase origin develop

otherwise prefer

git merge origin/develop

you should now be up to date. 👍

Thanks and sorry for the inconvenience,
gre

FYI @gre @MirkoGenoni @haammar-ledger I've rebased the MR and I also committed the fix lint command

Hi @haammar-ledger @gre, could you please support Davide's request? There are now new conflicts and as much as we can dedicate time to keeping up to date, we do need to be able to commit to the PR branch once we have or the effort is pointless. Thanks.

Thanks @haammar-ledger . Just to inform, Mirko is no longer supporting this. Adding @davidecarpini @bitkris-dev

@davidecarpini @bitkris-dev it seems that the rebasing somehow didn't go well, the current diff includes way too many changes, most of which are on develop already.
Happened before, never sure of the best way to get out of this state, but I think cherry-picking your commits on top of a clean develop could be the easiest way to get this PR back on its feet (with a force push).

@haammar-ledger this MR can be closed,
I've opened a new MR https://github.com/LedgerHQ/ledger-live/pull/4607
so I can manage it because this one was created by Mirko (who is no more with us) and I can't  handle it correctly
FWI @BenMVeChain @bitkris-dev

Replaced with https://github.com/LedgerHQ/ledger-live/pull/4607


@HxPushUrl(true) now retreives the path from the request

When using @HxPushUrl without a value it pushes true in the url, instead of the fetched URL

Now the path gets retreived from the request.

@xhaggi @wimdeblauwe
Added changes


Default Page Attributes do not persist

After settings a default page attribute and adding a new page of the type the attribute was set on, the default attribute is gone.  Here's a video showing it exactly:
http://archebian.org/videos/attributes-not-persisting.mp4

I can confirm this.
Example:

On the Empty page type, set the Client attribute to "spicy meatball".
Create a new Empty page.
In the new page's attribute panel, you will see the Client attribute is set to "spicy meatball".
Publish the page.
Go back to the Empty page type attributes and Client is set to "none".
Create another new Empty page.
In the new page's attribute panel, you will see the Client attribute is selected, but empty.

So the attribute value appears to save, but after creating a page of that type, the value is cleared and displays as none. The attribute is still selected for additional pages of that type, just without a value.

Looks like my fix from the select attribute issue with default attributes has fixed this as well.

@aembler
I went through all the default attributes and they work correctly except for Topics and Express Entity attributes.
The default topic attribute value is not set on the newly created page type.
Example:

In the Empty page type attributes, set the Project Topics attribute to "Activities".
Create a new Empty page.
In the new page's attribute panel, you will see the Project Topics attribute is displayed, but does not have a value set.

The express entity attribute "Choose Entry" modal does not list entries.
Example:

Create an express entity attribute.
On the Empty page type attributes, set a default value.
When "Choose Entry" is clicked, the modal opened has no entries to choose from.

I think something is weird with your express setup; I can choose and persist an entry with no issue, and it works on the defaults and when copied out to the child pages.
There does appear to be an issue with the topics attribute working as a default attribute, however.

@aembler
Thanks for checking. Having all the attributes available for page type defaults will be incredibly useful.


Serialization feature

Hmm don't know how to deal with the conflicting push....

I think I fixed the relevant issues.


[Bug]: Old Play icons are broken

Describe the bug
i've been recently notice some bugs now. the "old" play icons are become broken now. especially happened with "play all" or sometimes mouse hover over the videos thumbnails etc. could you fix that?
one more thing is: don't forget about the issue #153 too.
Screenshots

What browser are you using?
latest version of browsers
What version of AdashimaaTube are you using?
latest version (v2.3.5)

Please let me know if v2.3.6 fixed this issue.

Please let me know if v2.3.6 fixed this issue.

it's fixed now. thanks so much. @sapondanaisriwan


Twitter 7daysold switchscraping

Description

Switch to scraping logic if Tweet is older than 7 days
The number of tweets on a thread in the common information on the pdf was incorrectly displayed as 1 - this was fixed

Attach Screenshot

Note 2 code reviewer approval needed. Approach in twitter group & discord channel.

@Mira-Alf I'm thinking it would be better to throw the errors, and catch them. the code you've pushed relies on the error that is returned along with the data.
I've made some modifications on my end that catch the error(rather than read the returned error). This decreases the surface area for bugs, make the code more elegent and idiomatic.
Are you OK if I propose those changes(catching rather than reading them)? I'll port the above code to use it.

Not sure I understand what exactly you mean. But go ahead and make the changes - I will take a look at it once your change is in place.


Short URLs

Use http://jac.pics/ to create short url aliases.
Something like:

jac.pics/albania => pics.jonathancross.com/pics/2012/2012-06-23_Albania/

Open question:

Should these be manually created (in the jcdsee database) or automatically?
How to handle multiple albums for same country?
Include date?

Solution: use first, case-insensitive string matched  in the sitemap. That will allow me to flexibly deal with similar names, add more details, or even rename folders if needed.

Code is not optimized, but seems to work well enough.


form_builder_phone_field update

Connection with issue(s)
Connected to #855
Testing and Review Notes

Test with Flutter 2.8.1 and 2.10.5

Next steps:

Publish to pub.dev with version 1.0.0

Screenshots or Videos

To Do

[ ] double check the original issue to confirm it is fully satisfied
[X] add testing notes and screenshots in PR description to help guide reviewers
[ ] request the "UX" team perform a design review (if/when applicable)

@deandreamatias are we done here?

Yes! Nice changes
After this, I will do another pull request to be compatible with last version of flutter_form_builder and Flutter 3.0. But this is the future...
This PR will be merge


Rename requirements-locked.txt to requirements.locked

Rename requirements-locked.txt to requirements.locked to workaround https://github.com/dependabot/dependabot-core/issues/10007

:warning: Please install the  to ensure uploads and comments are reliably processed by Codecov.
Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:
:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.

Flag
Coverage Δ

integration
?

unittests
99.96% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.
see 18 files with indirect coverage changes


Feature Request: Add Requires Python Version similar to Pipenv

I am always amazed with rust based tools made by Astral. Added Ruff more than a year ago and still loving it. During the course of years I had migrated few of my test projects from normal virtualenv to Pipenv when onboarding new team members we always had to double check the Python version through Chat or Readme file within project. Pipenv lock file includes the python version required along with pinned package version.
In my limited testing of uv and the performance is amazing and most of the packages are installed(unless it is bigger than my slow internet) in a blink of an eye which I had to double check by removing cached files twice and even passed no-cache argument.
Not sure if I'm being greedy with too much feature requests linked to uv lock format and asking to add Requires Python Version to make migration from pipenv easier.
It is alright if this feature is not in current roadmap but planned in future releases.
Thank you Charlie and team at Astral.

I think this may be resolved by #4970 but we probably won't support writing the pin to the lock file since it's not part of the lock. You could pin Requires-Python itself and it'll be encoded there though, if you're only using a single version.

Thanks. At the moment I'm not seeing doc in the cli nor on GitHub.

From: T-256 @.>
Sent: Thursday, July 11, 2024 8:13 PM
To: astral-sh/uv @.>
Cc: Vasudev @.>; Author @.>
Subject: Re: [astral-sh/uv] Feature Request: Add Requires Python Version similar to Pipenv (Issue #4963)
I think uv lock format would ask your needs since it also lock requires-python at top-level:
https://github.com/astral-sh/uv/blob/42cb2541b513a9d53d9c677610fd478e27162a74/crates/uv/tests/lock.rs#L45-L46
Also, it's gonna to support .python-version file and perhaps a specific keyhttps://github.com/astral-sh/uv/issues/4970 via pyproject.toml.
—
Reply to this email directly, view it on GitHubhttps://github.com/astral-sh/uv/issues/4963#issuecomment-2223123762, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ANCXKE4VQXHMFO47KJJ5JLDZL2KZPAVCNFSM6AAAAABKVFODV6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDEMRTGEZDGNZWGI.
You are receiving this because you authored the thread.Message ID: @.***>

Does uv accept yaml or will a simple .python-version file with following contents work just fine?
[requires]
python_version = "3.12"
With multiple versions being supported should it declared with || or simply pass it as an list or array for example: ["3.11.8", "3.12.3", "3.13rc1"]

Would love to hear your thoughts as I would like to make the migration to uv as simple as possible while maintaining compatibility with pipenv.

From: Zanie Blue @.>
Sent: Thursday, July 11, 2024 8:20 PM
To: astral-sh/uv @.>
Cc: Vasudev @.>; Author @.>
Subject: Re: [astral-sh/uv] Feature Request: Add Requires Python Version similar to Pipenv (Issue #4963)
I think this may be resolved by #4970https://github.com/astral-sh/uv/issues/4970 but we probably won't support writing the pin to the lock file since it's not part of the lock. You could pin Requires-Python itself and it'll be encoded there though, if you're only using a single version.
—
Reply to this email directly, view it on GitHubhttps://github.com/astral-sh/uv/issues/4963#issuecomment-2223141719, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ANCXKE4GDR32ZJBCGWNC6Y3ZL2LUDAVCNFSM6AAAAABKVFODV6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDEMRTGE2DCNZRHE.
You are receiving this because you authored the thread.Message ID: @.***>

We only support a .python-version file with a single line or a .python-versions file with a version per line right now. We don't support parsing YAML — what format is that?

YAML is used Docker compose and other config related to deployment.
Thanks for the insights. Much appreciated

From: Zanie Blue @.>
Sent: Thursday, July 11, 2024 9:12 PM
To: astral-sh/uv @.>
Cc: Vasudev @.>; Author @.>
Subject: Re: [astral-sh/uv] Feature Request: Add Requires Python Version similar to Pipenv (Issue #4963)
We only support a .python-version file with a single line or a .python-versions file with a version per line right now. We don't support parsing YAML — what format is that?
—
Reply to this email directly, view it on GitHubhttps://github.com/astral-sh/uv/issues/4963#issuecomment-2223279492, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ANCXKEYQNJII4JSXF25THLDZL2RV7AVCNFSM6AAAAABKVFODV6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDEMRTGI3TSNBZGI.
You are receiving this because you authored the thread.Message ID: @.***>

I believe this is now covered by .python-version.


Async function in useEffect causes loop when using the default namespace

In a situation where I set the default namespace as an argument of useTranslation to get t and monitor it with useEffect, I found that when I call asynchronous functions such as setTimeout in useEffect, the function keeps being called infinitely.
Here is the reproduction code.
import useTranslation from 'next-translate/useTranslation'
import { ReactElement, useEffect, useState } from 'react'

export default function I18nTest(): ReactElement {
  const { t } = useTranslation('common')
  const [text, setText] = useState('')
  useEffect(() => {
    const ts = setTimeout(() => {
      setText(new Date().toISOString())
    }, 1000)
    return () => clearTimeout(ts)
  }, [t])
  return (
    <div>{text}</div>
  )
}

Is this the expected behavior?
Environments
$ node --version
v14.18.2

"dependencies": {
  "next": "^12.0.10",
  "next-translate": "^1.3.3",
  "react": "^17.0.2"
}

This was solved in: https://github.com/vinissimus/next-translate/pull/574
And reverted to solve this bug with Component.layout: https://github.com/vinissimus/next-translate/issues/604
There is currently a PR proposal to put it again: https://github.com/vinissimus/next-translate/pull/743 ...
However you can memorize the t as workaround or use lang as dependency.

Thanks @aralroca for response, I know it's a bug,  then I'll take the work-arounds when it becomes an issue in my project until it is resolved.


tests: console: bootloader expecters: give the VMI enough time to start

What this PR does / why we need it:
The expecters working on BIOS/EFI logs are given a freshly created VMI, to maximize their chance of catching those early logs.
Therefore, they need an initial timeout long enough for the VMI to start, 10 seconds is just not enough.
Which issue(s) this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close the issue(s) when PR gets merged):
Fixes #
Special notes for your reviewer:
Release note:

NONE

/cherry-pick release-0.53


Inline entities as Unicode characters

Could you inline these entities as Unicode characters?
https://google.github.io/styleguide/htmlcssguide.html#Entity_References
Originally posted by @antmar in https://github.com/tttzach/step/pull/11

Can't use Unicode but HTML entities work


Problem wit Paypal express shipping methods AdyenPaypalUpdateOrder service

Describe the bug
Service AdyenPaypalUpdateOrder sent request to add shipping methods to Paypal express window but I got error. Problem on EMEA sites. Currently I am testing on GB locale with GBP pricebook
To Reproduce
Steps to reproduce the behavior:

Go to Cart (EMEA locales)
Click on PayPal express
Wait for Paypal window load
open service log
See error

Logs
INFO PipelineCallServlet|1557082651|Sites-***-emea-Site|Adyen-ShippingMethods|PipelineCall|IS56utOiOp custom.service.AdyenPaypalUpdateOrder.COMM []   Request: {     "pspReference": "J9483VK****",     "paymentData": "A*****",     "amount": {         "currency": "GBP",         "value": 18195     },     "deliveryMethods": [         {             "reference": "DPD5",             "description": "Standard Delivery",             "type": "Shipping",             "amount": {                 "currency": "GBP",                 "value": 395             },             "selected": true         },         {             "reference": "DPD1",             "description": "Next Day Delivery ",             "type": "Shipping",             "amount": {                 "currency": "GBP",                 "value": 595             },             "selected": false         },         {             "reference": "DPD2",             "description": "Saturday Delivery",             "type": "Shipping",             "amount": {                 "currency": "GBP",                 "value": 595             },             "selected": false         },         {             "reference": "FEDMP1",             "description": "Standard Delivery (2-4 weeks)",             "type": "Shipping",             "amount": {                 "currency": "GBP",                 "value": 0             },             "selected": false         }     ] }
INFO PipelineCallServlet|1557082651|Sites-***-emea-Site|Adyen-ShippingMethods|PipelineCall|IS56utOiOp custom.service.AdyenPaypalUpdateOrder.COMM []   Response: {     "status": 500,     "errorCode": "903",     "message": "Internal error",     "errorType": "internal",     "pspReference": "ZVD2S69BRRZPGS65" }

Hi @AVATOR ,
Thanks for reaching out to us.
Are you using the latest version of the plugin?
I tried reproducing the reported issue using the latest version of the plugin (v24.3.2), however I can't reproduce it.
Can you please open a support ticket with Adyen, including the plugin version you used and details related to the failing transaction?
In case the issue comes from a plugin perspective, the support team will reach out to us and we will take care of the problem.
With kind regards,
Zenit
Adyen

Hi @zenit2001
I am using cartridge version 24.3.1

Hi @AVATOR ,
Please open a support ticket for the reported issue and they will help you solve the issue. It seems to be a configuration problem on the merchant account side, more than in plugin itself.
You can attach this thread there also for reference.
With kind regards,
Zenit
Adyen

Thanks @zenit2001
Yes, it was a configuration issue.


Reset the input box value.

Right now it's not being reset and this is creating problems when used in conditionals.

Awesome, thanks!


Language detection and the File Highlight plugin

Thanks very much for Prism: it looks like it might be exactly what I need for including external code snippets on assignment pages for a course I'm teaching. Except for this one issue. :)
When I try to fetch a C++ header file, I use something like this:

After the File Highlight plugin runs, however, what I see in my Web Inspector is:
<pre class="language-cpp data-src="some-header.h"

        "/* ... */"

So, it looks like the language that I've specified on the pre isn't getting propagated to the dynamically-generated code element within it.

Maybe somewhere around line 25 the plugin should check "if my pre has a class that includes language-, let me copy that rather than using the extension"?

Yes, I totally agree with you. I'll see if I can make the change.

The new version works perfectly. Thank you!

Thank you for reporting!


Fips support on RHEL 8 and RHEL 9

Description
this PR aims to add fips support in cp-ansible. one pager
Fixes # ANSIENG-2253
Type of change

[ ] Bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[x] This change requires a documentation update

How Has This Been Tested?
testing ongoing.
Checklist:

[x] Any variable/code changes have been validated to be backwards compatible (doesn't break upgrade)
[x] I have added tests that prove my fix is effective or that my feature works
[ ] If required, I have ensured the changes can be discovered by cp-ansible discovery codebase
[x] My code follows the style guidelines of this project
[x] I have commented my code, particularly in hard-to-understand areas
[x] I have made corresponding changes to the documentation
[x] My changes generate no new warnings
[x] Any dependent changes have been merged and published in downstream modules

Please add some verification steps to ensure only FIPS compliant ciphers are used in certs and keys generations. Add some tests for TLS version wherever you have HTTPS connection. It has to be >= 1.2 You may also want to explicitly try different whitelisted ciphers while creating the keys and certs.

Could you please share any docs or commands if you have to refer?


[TACHYON-594] [TACHYON-851] Add Cache Promote Write Type

https://tachyon.atlassian.net/browse/TACHYON-594
https://tachyon.atlassian.net/browse/TACHYON-851

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins/job/Tachyon-Pull-Request-Builder/4944/
Test PASSed.

A bunch comments left. Thanks for re-enabling this cool feature!

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins/job/Tachyon-Pull-Request-Builder/4984/
Test PASSed.

Can you resolve the conflicts?

@yupeng9 @apc999
I've updated the PR, please take a look.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins/job/Tachyon-Pull-Request-Builder/5028/
Test PASSed.

Can you resolve the conflicts again?

@yupeng9 resolved again.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins/job/Tachyon-Pull-Request-Builder/5031/
Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins/job/Tachyon-Pull-Request-Builder/5036/
Test PASSed.

+1 LGTM

+1 LGTM


[master] Removing unnecessary ' from modified type, variable name after escaping special characters

Fix #https://github.com/wso2-enterprise/internal-support-ballerina/issues/360
PR: https://github.com/ballerina-platform/openapi-tools/pull/1430

@lnash94 Do we need a separate master branch PR? can't we sync the 1.7.x branch instead?

This PR was sent due to the master branch only include some particular test-related diagnostics that are not in 1.7.x. Since we backport the fix we will be able to sync via sync PR let me check.

close this PR with the favour with https://github.com/ballerina-platform/openapi-tools/pull/1429


Retreiving section ID, data and material data from rst file

Hi,
I was able to read nodal stresses of layered SHELL elements without any problems from a rst file. Really great!
Is there a possibility for postprocessing purpose to get as well the corresponding section ID? I saw that load_elements from the _binary_reader should be able to get this but the data is currently skipped. There is a working alternative to read the data from the .cdb file. But for that I would need to write a cdb file from Workbench - the dat file seems to be not readable. To get all the data from rst file would be a much nicer approach I think.
Further I would need to read the section data and the corresponding material data to be able to perform the postprocessing. I was not able to find a way for that - is there a possibility?
Thanks a lot for your help and the great work!

Nice source diving to see that I'm skipping the section data.  I can add that in.  Would you mind posting a result file here so I can include it for my unit testing?  The smaller the better, and if you wouldn't mind including the expected output from MAPDL that would be helpful as well.

Thanks for your reply! I will send the data on Monday.

Hi,
find attached a very small rst file, the corresponding input file as well as the expected output from MAPDL.
Please let me know if you need any additional information.
SHELL281.zip

Thanks for the sample file, it's exactly what I need to work on this.
ANSYS really buries the material properties and doesn't label everything.  Still, making progress, and I should have something in a few days.

Hi, perfect - thanks for your efforts!

I've gotten the material properties working.  There was enough information in the ANSYS header files included in the install that I could interpret the results for all material properties:
rst = pyansys.read_binary('file.rst')
rst.materials

{1: {'EX':<PHONE_NUMBER>0.0,
  'EY':<PHONE_NUMBER>0.0,
  'EZ':<PHONE_NUMBER>0.0,
  'NUXY': 0.07500000000000001,
  'NUYZ': 0.30000000000000004,
  'NUXZ': 0.07500000000000001,
  'GXY':<PHONE_NUMBER>.0,
  'GYZ':<PHONE_NUMBER>.0,
  'GXZ':<PHONE_NUMBER>.0,
  'PRXY': 0.30000000000000004,
  'PRYZ': 0.30000000000000004,
  'PRXZ': 0.30000000000000004},
 2: {'EX':<PHONE_NUMBER>0.0,
  'EY':<PHONE_NUMBER>0.0,
  'EZ':<PHONE_NUMBER>0.0,
  'NUXY': 0.07500000000000001,
  'NUYZ': 0.30000000000000004,
  'NUXZ': 0.07500000000000001,
  'GXY':<PHONE_NUMBER>.0,
  'GYZ':<PHONE_NUMBER>.0,
  'GXZ':<PHONE_NUMBER>.0,
  'PRXY': 0.30000000000000004,
  'PRYZ': 0.30000000000000004,
  'PRXZ': 0.30000000000000004}}

However, it's a different story for the section data.  Here's the raw output I've been able to read in:
for i, item in enumerate(rst.section_data[3]): print('%3d' % i, item)

  0 2.0
  1 538976288.0
  2 538976288.0
  3 0.003
  4 3.0
  5 9.0
  6 3.0
  7 1.0
  8 1.0
  9 0.0
 10 0.7825633252851375
 11 -1.103929041252917e-18
 12 0.6265587724551406
 13 1.0
 14 0.0
 15 0.0
 16 0.0
 17 0.0
 18 0.0
 19 0.0
 20 0.0
 21 0.0
 22 0.0
 23 1.0
 24 1.0
 25 1.0
 26 1.0
 27 0.0
 28 0.0
 29 0.001
 30 2.0
 31 0.0
 32 3.0
 33 0.001
 34 2.0
 35 45.0
 36 3.0
 37 0.001
 38 2.0
 39 -45.0
 40 3.0
 41 2.0
 42 2.0
 43 2.0
 44 2.0
 45 2.0
 46 2.0
 47 2.0
 48 2.0
 49 2.0
 50 1.0
 51 1.0
 52 1.0
 53 2.0
 54 2.0
 55 2.0
 56 3.0
 57 3.0
 58 3.0
 59 0.0
 60 0.0
 61 0.0
 62 45.0
 63 45.0
 64 45.0
 65 -45.0
 66 -45.0
 67 -45.0
 68 0.1111111111111111
 69 0.4444444444444444
 70 0.1111111111111111
 71 0.1111111111111111
 72 0.4444444444444444
 73 0.1111111111111111
 74 0.1111111111111111
 75 0.4444444444444444
 76 0.1111111111111111
 77 -1.0
 78 -0.6666666666666666
 79 -0.3333333333333333
 80 -0.3333333333333333
 81 0.0
 82 0.3333333333333333
 83 0.3333333333333333
 84 0.6666666666666666
 85 1.0
 86 -2.2205146933576494e-17
 87 0.5438245756189379
 88 0.784905128619397
 89 0.784905128619397
 90 0.7491814833845594
 91 0.5729093986365412
 92 0.5729093986365411
 93 0.3384154725112908
 94 -1.3372214807262066e-16
 95 -9.962450570801805e-18
 96 0.38281646048078116
 97 0.6298052964038664
 98 0.6298052964038664
 99 0.8837920249365444
100 0.8687141075226417
101 0.8687141075226417
102 0.5470920816260001
103 -1.4634568481518775e-17
104 0.0

Here's what I've been able to interpret so far:
# sec[3] # total thickness
# sec[4] # number of layers (?)
# sec[5] # total integration points (?)
# ...
# sec[29] # start of a layer (thickness)
# - MatID
# - Ori. Angle
# - Num Intg.
# sec[33] # start of another layer
# sec[37] # start of another layer

These indices probably only work for this section type (which I'm not sure where it's defined in the section data).  Will these work for you?  I'd really like to list the section data as a dictionary as with the result data, but there's no information in the header files about how the section data is written out.

Great work - Thanks a lot for the tremendous effort!
I had some problems compiling the code but now it's working perfectly.
Do you have an idea if the failure critieria data for the materials (see tblist,fcli,... in MAPDL.inp) could be accessed, too?


fix: l11, misc bugfixes

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

Project coverage is 96.42%. Comparing base (8d60f7c) to head (1b70ea5).
 Consider uploading reports for the commit 7c9a8ed to get more accurate results

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
Additional details and impacted files
@@             Coverage Diff              @@
##             master     #122      +/-   ##
============================================
+ Coverage     96.35%   96.42%   +0.07%
- Complexity       87       88       +1
============================================
  Files            10       10
  Lines           274      280       +6
============================================
+ Hits            264      270       +6
  Misses           10       10

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


Limit typesafe config conversion to metrics keys

@ibuenros and @sahilTakiar can you please review?
The change limits the conversion of properties to typesafe config only for keys that start with metrics.

LGTM other than small comment.


Unable to connect to kubelet

Please read the documentation on these issues and open a new issue should you find a problem.


Can't run sample code in Android Studio

Opening the directories sample/kotlin or sample/java with Android Studio will show an error saying that the plugin (and plugin test) was not found, even after running ./gradlew publishToMavenLocal on both gradle-plugin and gradle-plugin-test.
Here is the error:
A problem occurred configuring project ':app'.
> Could not resolve all artifacts for configuration ':app:classpath'.
   > Could not resolve io.github.andrefigas.rustjni:RustJNI:0.0.17.
     Required by:
         project :app > io.github.andrefigas.rustjni:io.github.andrefigas.rustjni.gradle.plugin:0.0.17
      > No matching variant of io.github.andrefigas.rustjni:RustJNI:0.0.17 was found. The consumer was configured to find a library for use during runtime, compatible with Java 17, packaged as a jar, and its dependencies declared externally, as well as attribute 'org.gradle.plugin.api-version' with value '8.7' but:
          - Variant 'apiElements' declares a library, packaged as a jar, and its dependencies declared externally:
              - Incompatible because this component declares a component for use during compile-time, compatible with Java 21 and the consumer needed a component for use during runtime, compatible with Java 17
              - Other compatible attribute:
                  - Doesn't say anything about org.gradle.plugin.api-version (required '8.7')
          - Variant 'javadocElements' declares a component for use during runtime, and its dependencies declared externally:
              - Incompatible because this component declares documentation and the consumer needed a library
              - Other compatible attributes:
                  - Doesn't say anything about its elements (required them packaged as a jar)
                  - Doesn't say anything about its target Java version (required compatibility with Java 17)
                  - Doesn't say anything about org.gradle.plugin.api-version (required '8.7')
          - Variant 'runtimeElements' declares a library for use during runtime, packaged as a jar, and its dependencies declared externally:
              - Incompatible because this component declares a component, compatible with Java 21 and the consumer needed a component, compatible with Java 17
              - Other compatible attribute:
                  - Doesn't say anything about org.gradle.plugin.api-version (required '8.7')
          - Variant 'sourcesElements' declares a component for use during runtime, and its dependencies declared externally:
              - Incompatible because this component declares documentation and the consumer needed a library
              - Other compatible attributes:
                  - Doesn't say anything about its elements (required them packaged as a jar)
                  - Doesn't say anything about its target Java version (required compatibility with Java 17)
                  - Doesn't say anything about org.gradle.plugin.api-version (required '8.7')
   > Could not resolve io.github.andrefigas.rustjni-test:RustJNI:0.0.1.
     Required by:
         project :app > io.github.andrefigas.rustjni-test:io.github.andrefigas.rustjni-test.gradle.plugin:0.0.1
      > No matching variant of io.github.andrefigas.rustjni-test:RustJNI:0.0.1 was found. The consumer was configured to find a library for use during runtime, compatible with Java 17, packaged as a jar, and its dependencies declared externally, as well as attribute 'org.gradle.plugin.api-version' with value '8.7' but:
          - Variant 'apiElements' declares a library, packaged as a jar, and its dependencies declared externally:
              - Incompatible because this component declares a component for use during compile-time, compatible with Java 21 and the consumer needed a component for use during runtime, compatible with Java 17
              - Other compatible attribute:
                  - Doesn't say anything about org.gradle.plugin.api-version (required '8.7')
          - Variant 'javadocElements' declares a component for use during runtime, and its dependencies declared externally:
              - Incompatible because this component declares documentation and the consumer needed a library
              - Other compatible attributes:
                  - Doesn't say anything about its elements (required them packaged as a jar)
                  - Doesn't say anything about its target Java version (required compatibility with Java 17)
                  - Doesn't say anything about org.gradle.plugin.api-version (required '8.7')
          - Variant 'runtimeElements' declares a library for use during runtime, packaged as a jar, and its dependencies declared externally:
              - Incompatible because this component declares a component, compatible with Java 21 and the consumer needed a component, compatible with Java 17
              - Other compatible attribute:
                  - Doesn't say anything about org.gradle.plugin.api-version (required '8.7')
          - Variant 'sourcesElements' declares a component for use during runtime, and its dependencies declared externally:
              - Incompatible because this component declares documentation and the consumer needed a library
              - Other compatible attributes:
                  - Doesn't say anything about its elements (required them packaged as a jar)
                  - Doesn't say anything about its target Java version (required compatibility with Java 17)
                  - Doesn't say anything about org.gradle.plugin.api-version (required '8.7')

Building the sample projects with  ./gradlew app:rust-jni-compile-test works, so this must be something with the IDE, maybe we need to add some configuration for it to work?

Closed by https://github.com/andrefigas/RustJNI/pull/12

Reopened this issue because the samples still don't work, but now for  different reasons.
I had to update the gradle versions used by the plugin and the samples, and now this code in gradle-plugin/build.gradle.kts does not work and shows this error: Unresolved reference: pluginBundle
pluginBundle {
    website = "https://github.com/andrefigas/RustJNI"
    vcsUrl = "https://github.com/andrefigas/RustJNI"
    description = "A Gradle plugin that simplifies the creation and compilation of Rust code integrated with Android applications via JNI."
    tags = listOf("rust", "jni", "android", "gradle-plugin", "native-code", "android-development", "rust-jni")
}

After removing this, I compile the plugin and it works. Then I try compiling the kotlin sample and got an error saying that it tried looking for the rust directory in ~/.gradle/<version>/app/src/main/rust
I cleaned all the project folders and without changing anything i recompiled them and the issue was gone and I haven't been able to recreate it since.
I also notice that when the plugin generates the jni code for the kotlin/java class the libname is empty: System.loadLibrary("")

Well I got the error again when compiling the kotlin sample
FAILURE: Build failed with an exception.

* What went wrong:
Execution failed for task ':app:rust-jni-compile'.
> Could not find 'rust_jni.rs' file at /home/marti/.gradle/daemon/8.9/./app/src/main/rust/src/rust_jni.rs

I was able to solve all these issues but I haven't been able to push all the changes and still need to check the tests

https://github.com/andrefigas/RustJNI/pull/14
Sounds be solved. Can you validate again, pls ?

yup, all good


Variable declaration list comments from async functions are removed

TypeScript Version:  2.2.1
Code
async function example() {
    // result.value will be promise
    const promise = Promise.resolve("foo");
    await promise;

    // result.value will be "foo"
    return "foo";
}

Expected behavior:
Ignoring __awaiter and __generator, the output should include // result.value will be promise
Actual behavior:
function example() {
    return __awaiter(this, void 0, void 0, function () {
        var promise;
        return __generator(this, function (_a) {
            switch (_a.label) {
                case 0:
                    promise = Promise.resolve("foo");
                    return [4 /*yield*/, promise];
                case 1:
                    _a.sent();
                    // result.value will be "foo"
                    return [2 /*return*/, "foo"];
            }
        });
    });
}

On further exploration, it looks like this is only happening when a comment appears before a variable declaration list.
async function example() {
    // test abc
    let abc;

    // test def
    let def,
        // ghi
        ghi;

    // result.value will be promise
    const promise = Promise.resolve("foo");
    await promise;

    // result.value will be "foo"
    return "foo";
}

...becomes:
function example() {
    return __awaiter(this, void 0, void 0, function () {
        var abc, def,
        // ghi
        ghi, promise;
        return __generator(this, function (_a) {
            switch (_a.label) {
                case 0:
                    promise = Promise.resolve("foo");
                    return [4 /*yield*/, promise];
                case 1:
                    _a.sent();
                    // result.value will be "foo"
                    return [2 /*return*/, "foo"];
            }
        });
    });
}

Talk with @rbuckton this turned out to be harder problem than it looks... Couple thing we need to figure out

Where should the comment go when there are two separate variable statement comment?

async function example() {
    // test abc
    let abc;

    // test def
    let def,
    ....
}

function example() {
    return __awaiter(this, void 0, void 0, function () {
     --- what should this comment be -----
        var abc, def,
    ....
}

how we currently transform variable statement and hoist it declaration doesn't easily allow us to pass in information about the original variable statement (which we need to get the comment back)

Where should the comment go when there are two separate variable statement comment?

Seems reasonable to separate variable declarations by comments the way they are now.
async function example() {
    // test abc
    let abc;

    // test def, ghi
    let def, ghi;

    // test jkl
    let jkl,
        // test mno
        mno;
    ...
}

Output by default:
function example() {
    return __awaiter(this, void 0, void 0, function () {
        // test abc
        var abc;
        // test def, ghi
        var def, ghi;
        // test jkl
        var jkl,
        // test mno
        mno;
        ...
}

Output with --removeComments:
function example() {
    return __awaiter(this, void 0, void 0, function () {
        var abc, def, ghi, jkl, mno;
        ...
}

@JoshuaKGoldberg, I think the example here is not clear. Consider this:
async function example() {
  // comment1
  let a = 1;
  // comment2
  let b;
}

Becomes:
function example() {
  return __awaiter(this, void 0, void 0, function () {
    var a, b;
    return __generator(this, function (_a) {
      switch (_a.label) {
        case 0:
          a = 1;
          return [2 /*return*/];
      }
    });
  });
}

As a result of the transformation, the declaration of a has been separated from its initializer, and the declaration of b has been hoisted and is no longer associated with related code from the source position.
For a, we could choose either the hoisted declaration or the initializer as the location to place comments. For b, we can either only choose the hoisted declaration or we would have to synthesize a NotEmittedStatement for that position so that we can associate its comment. Either choice could be considered reasonable by developers, so the situation is not quite so clear cut.
If we do opt to associate the comments with the declaration, it will require some non-trivial changes in the generators transform to emulate the comment emit in your recommendation.

As I see it, comments immediately before a variable declaration "should" always stay immediately before wherever that variable is declared:
Semantically:

The motivation behind having a comment above a variable declaration is to provide a description for that variable's intention, as with any documented construct (member property, function, etc.). Comments associated with a declaration should stick with that declaration.

Practically:
It is valid that we sometimes have to open compiled JS files in debuggers. Assuming that need is valid:

Intellisense in VS Code and others recognizes JSDoc-style comments above variable declarations. , and having the JSDoc-ed variables can be useful.
Comments often contain search terms used in find-all searching. Dropping comments that were intended to be found is frustrating.

@rbuckton using your example and applying the principle of keeping comments with declarations:
function example() {
  return __awaiter(this, void 0, void 0, function () {
    // comment1
    var a;
    // comment2
    var b;
    return __generator(this, function (_a) {
      switch (_a.label) {
        case 0:
          a = 1;
          return [2 /*return*/];
      }
    });
  });
}

If it were written with /** ... */ style comments, Intellisense would still work:
async function example() {
  /** comment1 */
  let a = 1;
  /** comment2 */
  let b;
}

function example() {
  return __awaiter(this, void 0, void 0, function () {
    /* comment1 */
    var a;
    /* comment2 */
    var b;
    return __generator(this, function (_a) {
      switch (_a.label) {
        case 0:
          a = 1;
          return [2 /*return*/];
      }
    });
  });
}

@yuit I disagree with the Working as Intended label. It's understandable if this is more effort than it's worth, but the way comments now can be dropped is not good IMO.

@JoshuaKGoldberg I agree that work as intended is not a good one. I will reopen and see what we can do


ENH: stats.crosstab: convert output tuple to bunch

Reference issue

https://github.com/scipy/scipy/issues/16364#issuecomment-1157012416
What does this implement/fix?

Converts crosstab to return a bunch rather than a plain tuple
Additional information

I think doc failure is now related to #16960? Do you want me to rebase and run again (just the doc build as the rest seems fine / unrelated)

You can just merge rather than rebasing. Add [skip actions] [skip azp] to the body of the commit message. (Those used to work, although not sure if azure is skipping now.)

Doc build now green and rendering correctly :smiley:

Thanks @j-bowhay!


i18n strings being to Wikidata focused

The i18n strings are intended to be reused for any Wikibase installation. As such catalog-title, catalog-description and dataset-live-title need to be made generic.
Whilst dataset-live-title might be rewritten the other two need to refer to the specific installation. As such, and to still be i18n-able they would probably have to live somewhere other than in the i18n or config files.

dataset-live-title now generalised

Fixed with merging of projectNeutral branch


Invalid syntax in line 54

faisal071@HP-EliteBook-2540p:~/Python---Email-Bomber$ python Email_Bomber.py   File "Email_Bomber.py", line 54     print(f'ERROR: {e}')                       ^ SyntaxError: invalid syntax

Try to use Python3 instead of Python

Try to use Python3 instead of Python

Even with Python 3, I still get errors, something to do with the ' instead if ". I think that managed to fix it on python 3, along with a few other minor changes. Just posted it on Github so it can be fixed rather then people having to fix it them selves

I will make a pull request changing the README so it will be easier for people

I did the Pull request, now its up to the dev to approve it now

F-strings are supported from python 3.6 or later.
So upgrading to the latest python version should do the trick


DbaSqlManagementObject - added remoting, fixed #1621

@dbaduck  - please check out the changes I made.

It'd be cool if we added a translator too -- allow them to pass in 2005 and change it to 9


Provide summary of curation of datasets

In GitLab by @marcrr on Oct 15, 2015, 11:55
Provide for each sample the following information: used in Bgee; not used because not "normal"; not used because not passing QC. This should showcase our curation efforts.

In GitLab by @marcrr on Jun 20, 2019, 08:57
moved to Roadmap suggestions

In GitLab by @marcrr on Jun 20, 2019, 08:57
closed


Fixes#1553 Explore activity & list of picture of the day added

Explore activity & picture of the day added
Fixes #1553
Description

Explore activity added for browse feature
Added tab layout and viewpager for exploring featured images, picture of the day.
Added ViewPager Adapter which will contain fragments.
2 instance of Category Image Fragment added in viewpager fragments (POTD, Featured)
Featured option is now replaced by Explore option in Navigation drawer

Also for search feature

Search, Explore Icon added in drawables.
Search Option is shown in toolbar of Explore activity.

I will add working on search feature in another PR.
Fixes #1553
{Describe the changes made and why they were made.}
Tests performed (required)
Manually tested on [API 25 Motog5S+] with ProdDebug
Please test on ProdDebug as betadebug variant doesn't have featured Images, POTD
Screenshots showing what changed

@nicolas-raoul @neslihanturan PR is ready for review.

This PR was having 2 features- explore (not needed now) and picture of the day list (we will add after Mathur's PR is merged) so that code can be reused. Also,  We can refractor the code of Category Image Activity instead of adding a new activity for explore. So this PR will not work. I have to remove everything to update the PR so i thought I should send a new one.

You can also work on your PR branch and push your changes. Then your PR will be updated automatically @ujjwalagrawal17 :)


Create EmailConfiguration class

Create an EmailConfiguration class similar to TwitterConfiguration  class.
Move getEmailService from NotifierPacktApplication class to the new one.

Done.