p2114o issues

Thank you for developing the dream vacuum
bug
1.Cleaning mode does not have sweep mode.
2.Request map data from cloud failed
Screenshots
1.
2.
Additional Information (please complete the following information)

Model Name  dreame.vacuum.p2114o
Firmware Version [e.g. 1156]: 4.3.3_1104
Home Assistant Version: Home Assistant 2022.10.4
Configuration Type [With or without map support]: with map
Errors or warnings shown in the HA logs (if applicable):

In the mihome app, can use sweeping mode while the mop pads attached
When I removed the mop pad, the sweep option came alive
Can't I use it if it's installed?

2022-10-16 18:00:42.284 INFO (Thread-7) [custom_components.dreame_vacuum.dreame.map] Request map from device [{'piid': 2, 'value': '{"req_type":1,"frame_type":"I","force_type":1}'}]
2022-10-16 18:00:42.442 INFO (Thread-7) [custom_components.dreame_vacuum.dreame.map] Response from device [{'piid': 1, 'value': ''}, {'piid': 3, 'value': '1653707108/1034063228/1,f4LEmacnepfZGvaF'}, {'piid': 5, 'value':<PHONE_NUMBER>869}]
2022-10-16 18:00:42.528 INFO (MainThread) [custom_components.dreame_vacuum.dreame.map] Render frame: 10:0 took: 1.95 at scale 4
2022-10-16 18:00:42.809 WARNING (Thread-7) [custom_components.dreame_vacuum.dreame.map] Request map data from cloud failed https://cnbj2.fds.api.xiaomi.com/dreame.vacuum.mc1808.info/1653707108/1034063228/1,f4LEmacnepfZGvaF?Expires=1665912642000&GalaxyAccessKeyId=EAK2SDFZGTODL&Signature=W0xEpLRpKoPFwbcS36jB4bfgISo=
2022-10-16 18:00:43.860 WARNING (MainThread) [homeassistant.components.number] custom_components.xiaomi_miot.number::MiotNumberSubEntity is overriding deprecated methods on an instance of NumberEntity, this is not valid and will be unsupported from Home Assistant 2022.10. Please report it to the custom integration author.
2022-10-16 18:00:43.866 WARNING (MainThread) [homeassistant.components.number] custom_components.xiaomi_miot.number::MiotNumberActionSubEntity is overriding deprecated methods on an instance of NumberEntity, this is not valid and will be unsupported from Home Assistant 2022.10. Please report it to the custom integration author.
2022-10-16 18:00:47.953 INFO (Thread-9) [custom_components.dreame_vacuum.dreame.map] Request map from device [{'piid': 2, 'value': '{"req_type":1,"frame_type":"I","force_type":1}'}]
2022-10-16 18:00:47.994 INFO (Thread-9) [custom_components.dreame_vacuum.dreame.map] Response from device [{'piid': 1, 'value': ''}, {'piid': 3, 'value': '1653707108/1034063228/1,f4LEmacnepfZGvaF'}, {'piid': 5, 'value':<PHONE_NUMBER>548}]
2022-10-16 18:00:49.927 WARNING (Thread-9) [custom_components.dreame_vacuum.dreame.map] Request map data from cloud failed https://cnbj2.fds.api.xiaomi.com/dreame.vacuum.mc1808.info/1653707108/1034063228/1,f4LEmacnepfZGvaF?Expires=1665912649000&GalaxyAccessKeyId=EAK2SDFZGTODL&Signature=J//exV3d0YFvLgSvDbfrb56/pEE=
2022-10-16 18:00:54.912 WARNING (MainThread) [homeassistant.components.sensor] Setup of sensor platform scrape is taking over 10 seconds.
2022-10-16 18:00:54.937 INFO (Thread-17) [custom_components.dreame_vacuum.dreame.map] Request map from device [{'piid': 2, 'value': '{"req_type":1,"frame_type":"I","force_type":1}'}]
2022-10-16 18:00:54.965 INFO (Thread-17) [custom_components.dreame_vacuum.dreame.map] Response from device [{'piid': 1, 'value': ''}, {'piid': 3, 'value': '1653707108/1034063228/1,f4LEmacnepfZGvaF'}, {'piid': 5, 'value':<PHONE_NUMBER>522}]
2022-10-16 18:00:55.018 ERROR (MainThread) [homeassistant.components.rest.data] Timeout while fetching data: https://m.map.kakao.com/actions/busStationInfo?busStopId=BS461784
2022-10-16 18:01:02.990 INFO (Thread-20) [custom_components.dreame_vacuum.dreame.map] Request map from device [{'piid': 2, 'value': '{"req_type":1,"frame_type":"I","force_type":1}'}]
2022-10-16 18:01:03.022 INFO (Thread-20) [custom_components.dreame_vacuum.dreame.map] Response from device [{'piid': 1, 'value': ''}, {'piid': 3, 'value': '1653707108/1034063228/1,f4LEmacnepfZGvaF'}, {'piid': 5, 'value':<PHONE_NUMBER>581}]
2022-10-16 18:01:08.962 WARNING (Thread-20) [custom_components.dreame_vacuum.dreame.map] Request map data from cloud failed https://cnbj2.fds.api.xiaomi.com/dreame.vacuum.mc1808.info/1653707108/1034063228/1,f4LEmacnepfZGvaF?Expires=1665912668000&GalaxyAccessKeyId=EAK2SDFZGTODL&Signature=5CxrhIR+wlkjONugwrh79OVTp70=
2022-10-16 18:01:13.965 INFO (Thread-23) [custom_components.dreame_vacuum.dreame.map] Request map from device [{'piid': 2, 'value': '{"req_type":1,"frame_type":"I","force_type":1}'}]
2022-10-16 18:01:13.988 INFO (Thread-23) [custom_components.dreame_vacuum.dreame.map] Response from device [{'piid': 1, 'value': ''}, {'piid': 3, 'value': '1653707108/1034063228/1,f4LEmacnepfZGvaF'}, {'piid': 5, 'value':<PHONE_NUMBER>549}]
2022-10-16 18:01:14.254 WARNING (Thread-23) [custom_components.dreame_vacuum.dreame.map] Request map data from cloud failed https://cnbj2.fds.api.xiaomi.com/dreame.vacuum.mc1808.info/1653707108/1034063228/1,f4LEmacnepfZGvaF?Expires=1665912674000&GalaxyAccessKeyId=EAK2SDFZGTODL&Signature=7gaaFuFhXD/JBbnC8gQSCu1qBCM=
2022-10-16 18:01:19.257 INFO (Thread-25) [custom_components.dreame_vacuum.dreame.map] Request map from device [{'piid': 2, 'value': '{"req_type":1,"frame_type":"I","force_type":1}'}]
2022-10-16 18:01:19.422 INFO (Thread-25) [custom_components.dreame_vacuum.dreame.map] Response from device [{'piid': 1, 'value': ''}, {'piid': 3, 'value': '1653707108/1034063228/1,f4LEmacnepfZGvaF'}, {'piid': 5, 'value':<PHONE_NUMBER>849}]
2022-10-16 18:01:19.685 WARNING (Thread-25) [custom_components.dreame_vacuum.dreame.map] Request map data from cloud failed https://cnbj2.fds.api.xiaomi.com/dreame.vacuum.mc1808.info/1653707108/1034063228/1,f4LEmacnepfZGvaF?Expires=1665912679000&GalaxyAccessKeyId=EAK2SDFZGTODL&Signature=PmQXv0NX9A7JP8LSFrHHMUhLj4w=
2022-10-16 18:01:24.687 INFO (Thread-27) [custom_components.dreame_vacuum.dreame.map] Request map from device [{'piid': 2, 'value': '{"req_type":1,"frame_type":"I","force_type":1}'}]
2022-10-16 18:01:24.714 INFO (Thread-27) [custom_components.dreame_vacuum.dreame.map] Response from device [{'piid': 1, 'value': ''}, {'piid': 3, 'value': '1653707108/1034063228/1,f4LEmacnepfZGvaF'}, {'piid': 5, 'value':<PHONE_NUMBER>274}]
2022-10-16 18:01:25.109 WARNING (Thread-27) [custom_components.dreame_vacuum.dreame.map] Request map data from cloud failed https://cnbj2.fds.api.xiaomi.com/dreame.vacuum.mc1808.info/1653707108/1034063228/1,f4LEmacnepfZGvaF?Expires=1665912684000&GalaxyAccessKeyId=EAK2SDFZGTODL&Signature=CO/AMbqAxHRYYX6/ku8GYXHyLMU=
2022-10-16 18:01:30.112 INFO (Thread-29) [custom_components.dreame_vacuum.dreame.map] Request map from device [{'piid': 2, 'value': '{"req_type":1,"frame_type":"I","force_type":1}'}]
2022-10-16 18:01:30.138 INFO (Thread-29) [custom_components.dreame_vacuum.dreame.map] Response from device [{'piid': 1, 'value': ''}, {'piid': 3, 'value': '1653707108/1034063228/1,f4LEmacnepfZGvaF'}, {'piid': 5, 'value':<PHONE_NUMBER>695}]
2022-10-16 18:01:30.397 WARNING (Thread-29) [custom_components.dreame_vacuum.dreame.map] Request map data from cloud failed https://cnbj2.fds.api.xiaomi.com/dreame.vacuum.mc1808.info/1653707108/1034063228/1,f4LEmacnepfZGvaF?Expires=1665912690000&GalaxyAccessKeyId=EAK2SDFZGTODL&Signature=ntlEBfPy0AIs9YuliiL8OWO4mVA=
2022-10-16 18:01:35.400 INFO (Thread-31) [custom_components.dreame_vacuum.dreame.map] Request map from device [{'piid': 2, 'value': '{"req_type":1,"frame_type":"I","force_type":1}'}]
2022-10-16 18:01:35.570 INFO (Thread-31) [custom_components.dreame_vacuum.dreame.map] Response from device [{'piid': 1, 'value': ''}, {'piid': 3, 'value': '1653707108/1034063228/1,f4LEmacnepfZGvaF'}, {'piid': 5, 'value':<PHONE_NUMBER>997}]
2022-10-16 18:01:35.827 WARNING (Thread-31) [custom_components.dreame_vacuum.dreame.map] Request map data from cloud failed https://cnbj2.fds.api.xiaomi.com/dreame.vacuum.mc1808.info/1653707108/1034063228/1,f4LEmacnepfZGvaF?Expires=1665912695000&GalaxyAccessKeyId=EAK2SDFZGTODL&Signature=78S/3dtBxSREeg7l0y64Th3zEdc=
2022-10-16 18:01:40.830 INFO (Thread-34) [custom_components.dreame_vacuum.dreame.map] Request map from device [{'piid': 2, 'value': '{"req_type":1,"frame_type":"I","force_type":1}'}]
2022-10-16 18:01:40.863 INFO (Thread-34) [custom_components.dreame_vacuum.dreame.map] Response from device [{'piid': 1, 'value': ''}, {'piid': 3, 'value': '1653707108/1034063228/1,f4LEmacnepfZGvaF'}, {'piid': 5, 'value':<PHONE_NUMBER>424}]
2022-10-16 18:01:41.130 WARNING (Thread-34) [custom_components.dreame_vacuum.dreame.map] Request map data from cloud failed https://cnbj2.fds.api.xiaomi.com/dreame.vacuum.mc1808.info/1653707108/1034063228/1,f4LEmacnepfZGvaF?Expires=1665912700000&GalaxyAccessKeyId=EAK2SDFZGTODL&Signature=w3VdFc4/79PQOTO3vJrcErSpaGs=
2022-10-16 18:01:46.133 INFO (Thread-36) [custom_components.dreame_vacuum.dreame.map] Request map from device [{'piid': 2, 'value': '{"req_type":1,"frame_type":"I","force_type":1}'}]
2022-10-16 18:01:46.160 INFO (Thread-36) [custom_components.dreame_vacuum.dreame.map] Response from device [{'piid': 1, 'value': ''}, {'piid': 3, 'value': '1653707108/1034063228/1,f4LEmacnepfZGvaF'}, {'piid': 5, 'value':<PHONE_NUMBER>715}]
2022-10-16 18:01:46.421 WARNING (Thread-36) [custom_components.dreame_vacuum.dreame.map] Request map data from cloud failed https://cnbj2.fds.api.xiaomi.com/dreame.vacuum.mc1808.info/1653707108/1034063228/1,f4LEmacnepfZGvaF?Expires=1665912706000&GalaxyAccessKeyId=EAK2SDFZGTODL&Signature=WLwdctc65sFOmwT8+HwkUF7W5kA=

Okay. What should I do?
Should I register my vacuum cleaner on your account?

Okay. What should I do? Should I register my vacuum cleaner on your account?

There is a share option on the profile page. Which server region are you using right now? I will open a new account on your region and send you the mi account id.

I live in Korea, but you have to open it with a Chinese account

@jeongsik-kim i got what i need you can remove the device access.

Thank you for your help.

An error occurred when replacing with a test component.
2022-10-17 00:33:52.346 WARNING (MainThread) [homeassistant.components.websocket_api.http.connection] [140296194396496] Disconnected: Did not receive auth message within 10 seconds
2022-10-17 00:34:14.739 INFO (MainThread) [custom_components.dreame_vacuum.dreame.device] Initializing with host <IP_ADDRESS> (token 386b3...)
2022-10-17 00:34:14.743 INFO (SyncWorker_1) [custom_components.dreame_vacuum.dreame.device] Logging in...
2022-10-17 00:34:17.273 INFO (SyncWorker_1) [custom_components.dreame_vacuum.dreame.device] Connecting to device
2022-10-17 00:34:17.601 ERROR (MainThread) [custom_components.dreame_vacuum] Update failed: Traceback (most recent call last):
File "/config/custom_components/dreame_vacuum/coordinator.py", line 225, in _async_update_data
await self.hass.async_add_executor_job(self.device.update)
File "/usr/local/lib/python3.10/concurrent/futures/thread.py", line 58, in run
result = self.fn(*self.args, **self.kwargs)
File "/config/custom_components/dreame_vacuum/dreame/device.py", line 883, in update
self.connect_device()
File "/config/custom_components/dreame_vacuum/dreame/device.py", line 622, in connect_device
self._request_properties()
File "/config/custom_components/dreame_vacuum/dreame/device.py", line 258, in _request_properties
callback0
File "/config/custom_components/dreame_vacuum/dreame/device.py", line 346, in _water_tank_changed
if not self.status.started and not self.status.sweeping_with_mop_pad_available:
File "/config/custom_components/dreame_vacuum/dreame/device.py", line 2627, in sweeping_with_mop_pad_available
return bool(self.self_wash_base_available and self.get_property(DreameVacuumProperty.DUST_COLLECTION) is not None)
AttributeError: 'DreameVacuumDeviceStatus' object has no attribute 'get_property'
2022-10-17 00:34:17.602 WARNING (MainThread) [homeassistant.config_entries] Config entry 'robo' for dreame_vacuum integration not ready yet: 'DreameVacuumDeviceStatus' object has no attribute 'get_property'; Retrying in background
2022-10-17 00:34:22.605 INFO (MainThread) [custom_components.dreame_vacuum.dreame.device] Initializing with host <IP_ADDRESS> (token 386b3...)
2022-10-17 00:34:22.608 INFO (SyncWorker_0) [custom_components.dreame_vacuum.dreame.device] Logging in...
2022-10-17 00:34:25.320 INFO (SyncWorker_0) [custom_components.dreame_vacuum.dreame.device] Connecting to device
2022-10-17 00:34:25.495 ERROR (MainThread) [custom_components.dreame_vacuum] Update failed: Traceback (most recent call last):
File "/config/custom_components/dreame_vacuum/coordinator.py", line 225, in _async_update_data
await self.hass.async_add_executor_job(self.device.update)
File "/usr/local/lib/python3.10/concurrent/futures/thread.py", line 58, in run
result = self.fn(*self.args, **self.kwargs)
File "/config/custom_components/dreame_vacuum/dreame/device.py", line 883, in update
self.connect_device()
File "/config/custom_components/dreame_vacuum/dreame/device.py", line 622, in connect_device
self._request_properties()
File "/config/custom_components/dreame_vacuum/dreame/device.py", line 258, in _request_properties
callback0
File "/config/custom_components/dreame_vacuum/dreame/device.py", line 346, in _water_tank_changed
if not self.status.started and not self.status.sweeping_with_mop_pad_available:
File "/config/custom_components/dreame_vacuum/dreame/device.py", line 2627, in sweeping_with_mop_pad_available
return bool(self.self_wash_base_available and self.get_property(DreameVacuumProperty.DUST_COLLECTION) is not None)
AttributeError: 'DreameVacuumDeviceStatus' object has no attribute 'get_property'

I just updated the test and the cleaning mode is disabled

2022-10-17 14:34:18.795 ERROR (MainThread) [homeassistant.components.vacuum] Error while setting up dreame_vacuum platform for vacuum
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/helpers/entity_platform.py", line 281, in _async_setup_platform
await asyncio.shield(task)
File "/config/custom_components/dreame_vacuum/vacuum.py", line 403, in async_setup_entry
async_add_entities([DreameVacuum(coordinator)])
File "/config/custom_components/dreame_vacuum/vacuum.py", line 417, in init
self._set_attrs()
File "/config/custom_components/dreame_vacuum/vacuum.py", line 448, in _set_attrs
self.attr_extra_state_attributes = self.device.status.attributes
File "/config/custom_components/dreame_vacuum/dreame/device.py", line 2941, in attributes
value = self.cleaning_mode_name.replace("", " ").capitalize()
File "/config/custom_components/dreame_vacuum/dreame/device.py", line 2052, in cleaning_mode_name
return CLEANING_MODE_CODE_TO_NAME.get(self.cleaning_mode, STATE_UNKNOWN)
File "/config/custom_components/dreame_vacuum/dreame/device.py", line 2035, in cleaning_mode
if not self.status.sweeping_with_mop_pad_available:
AttributeError: 'DreameVacuumStatus' object has no attribute 'sweeping_with_mop_pad_available'

map data log:

2022-10-17 14:36:38.367 INFO (Thread-57) [custom_components.dreame_vacuum.dreame.map] Request map from device [{'piid': 2, 'value': '{"req_type":1,"frame_type":"I","force_type":1}'}]
2022-10-17 14:36:38.392 INFO (Thread-57) [custom_components.dreame_vacuum.dreame.map] Response from device [{'piid': 1, 'value': ''}, {'piid': 3, 'value': '1653707108/1034063228/1,f4LEmacnepfZGvaF'}, {'piid': 5, 'value':<PHONE_NUMBER>467}]
2022-10-17 14:36:38.565 INFO (Thread-57) [custom_components.dreame_vacuum.dreame.map] Encrypted Map Data: [encoded data, 10860 characters]
f4LEmacnepfZGvaF

Oh Cleaning Mode sweep is enabled.
Thank you.
But there is a little problem
The mopping and sweeping mode and the sweeping mode have been switched.
1.zip

Oh, finally, the map is working.
You're amazing Thank you very much.
Could you revise one more thing?
The start drying button does not work.

log:
2022-10-17 23:41:17.020 ERROR (MainThread) [homeassistant.components.websocket_api.http.connection] [140117730163296] 'DreameVacuumDevice' object has no attribute 'start_drying'
Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/components/websocket_api/commands.py", line 202, in handle_call_service
    await hass.services.async_call(
  File "/usr/src/homeassistant/homeassistant/core.py", line 1738, in async_call
    task.result()
  File "/usr/src/homeassistant/homeassistant/core.py", line 1775, in _execute_service
    await cast(Callable[[ServiceCall], Awaitable[None]], handler.job.target)(
  File "/usr/src/homeassistant/homeassistant/helpers/entity_component.py", line 207, in handle_service
    await service.entity_service_call(
  File "/usr/src/homeassistant/homeassistant/helpers/service.py", line 678, in entity_service_call
    future.result()  # pop exception if have
  File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 931, in async_request_call
    await coro
  File "/usr/src/homeassistant/homeassistant/helpers/service.py", line 715, in _handle_entity_call
    await result
  File "/usr/src/homeassistant/homeassistant/components/button/__init__.py", line 116, in _async_press_action
    await self.async_press()
  File "/config/custom_components/dreame_vacuum/button.py", line 204, in async_press
    await self._try_command(
  File "/config/custom_components/dreame_vacuum/entity.py", line 115, in _try_command
    await self.hass.async_add_executor_job(partial(func, *args, **kwargs))
  File "/usr/local/lib/python3.10/concurrent/futures/thread.py", line 58, in run
    result = self.fn(*self.args, **self.kwargs)
  File "/config/custom_components/dreame_vacuum/button.py", line 148, in <lambda>
    action_fn=lambda device: device.start_drying(),
AttributeError: 'DreameVacuumDevice' object has no attribute 'start_drying'

The start drying button is activated. The Stop Drying button is not active.

Is this log okay?
2022-10-18 00:16:34.766 WARNING (Thread-433) [custom_components.dreame_vacuum.dreame.map] Map update Failed: Traceback (most recent call last):
  File "/config/custom_components/dreame_vacuum/dreame/map.py", line 939, in update
    if not self._request_map_from_cloud():
  File "/config/custom_components/dreame_vacuum/dreame/map.py", line 191, in _request_map_from_cloud
    raise DeviceUpdateFailedException(
custom_components.dreame_vacuum.dreame.exceptions.DeviceUpdateFailedException: get_device_property failed

2022-10-18 00:16:34.772 ERROR (Thread-433) [custom_components.dreame_vacuum] Error requesting dreame_vacuum data: get_device_property failed
2022-10-18 00:17:07.134 INFO (Thread-438) [custom_components.dreame_vacuum.dreame.map] Update callback
2022-10-18 00:18:39.717 WARNING (Thread-455) [custom_components.dreame_vacuum.dreame.map] Map update Failed: Traceback (most recent call last):
  File "/config/custom_components/dreame_vacuum/dreame/map.py", line 939, in update
    if not self._request_map_from_cloud():
  File "/config/custom_components/dreame_vacuum/dreame/map.py", line 191, in _request_map_from_cloud
    raise DeviceUpdateFailedException(
custom_components.dreame_vacuum.dreame.exceptions.DeviceUpdateFailedException: get_device_property failed

2022-10-18 00:18:39.719 ERROR (Thread-455) [custom_components.dreame_vacuum] Error requesting dreame_vacuum data: get_device_property failed
2022-10-18 00:19:03.712 INFO (Thread-460) [custom_components.dreame_vacuum.dreame.map] Update callback

The start drying button is activated. The Stop Drying button is not active.

Stop drying button is only active when drying is active.

Is this log okay?

I will try to understand the reason of these logs.

Yes, I started drying, but I can't stop drying.

i'm trying to set up automation vacuum
but dreame vacuum select first service dose not working
log:
TypeError: DreameVacuumSelectEntity.async_first() missing 1 required positional argument: 'cycle'
2022-10-18 12:59:33.935 ERROR (MainThread) [homeassistant.components.websocket_api.http.connection] [140588560395008] Error handling message: Unknown error (unknown_error)
Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/components/websocket_api/decorators.py", line 27, in _handle_async_response
    await func(hass, connection, msg)
  File "/usr/src/homeassistant/homeassistant/components/websocket_api/commands.py", line 648, in handle_execute_script
    await script_obj.async_run(msg.get("variables"), context=context)
  File "/usr/src/homeassistant/homeassistant/helpers/script.py", line 1524, in async_run
    await asyncio.shield(run.async_run())
  File "/usr/src/homeassistant/homeassistant/helpers/script.py", line 409, in async_run
    await self._async_step(log_exceptions=False)
  File "/usr/src/homeassistant/homeassistant/helpers/script.py", line 453, in _async_step
    self._handle_exception(
  File "/usr/src/homeassistant/homeassistant/helpers/script.py", line 476, in _handle_exception
    raise exception
  File "/usr/src/homeassistant/homeassistant/helpers/script.py", line 451, in _async_step
    await getattr(self, handler)()
  File "/usr/src/homeassistant/homeassistant/helpers/script.py", line 684, in _async_call_service_step
    await service_task
  File "/usr/src/homeassistant/homeassistant/core.py", line 1738, in async_call
    task.result()
  File "/usr/src/homeassistant/homeassistant/core.py", line 1775, in _execute_service
    await cast(Callable[[ServiceCall], Awaitable[None]], handler.job.target)(
  File "/usr/src/homeassistant/homeassistant/helpers/entity_platform.py", line 769, in handle_service
    await service.entity_service_call(
  File "/usr/src/homeassistant/homeassistant/helpers/service.py", line 678, in entity_service_call
    future.result()  # pop exception if have
  File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 931, in async_request_call
    await coro
  File "/usr/src/homeassistant/homeassistant/helpers/service.py", line 709, in _handle_entity_call
    result = hass.async_run_job(partial(getattr(entity, func), **data))  # type: ignore[arg-type]
  File "/usr/src/homeassistant/homeassistant/core.py", line 615, in async_run_job
    return self.async_run_hass_job(HassJob(target), *args)
  File "/usr/src/homeassistant/homeassistant/core.py", line 570, in async_run_hass_job
    return self.async_add_hass_job(hassjob, *args)
  File "/usr/src/homeassistant/homeassistant/core.py", line 473, in async_add_hass_job
    task = self.loop.create_task(hassjob.target(*args))
TypeError: DreameVacuumSelectEntity.async_first() missing 1 required positional argument: 'cycle'
2022-10-18 13:01:47.795 ERROR (MainThread) [homeassistant.helpers.script.websocket_api_script] websocket_api script: Error executing script. Unexpected error for call_service at pos 1: DreameVacuumSelectEntity.async_first() missing 1 required positional argument: 'cycle'
Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/helpers/script.py", line 451, in _async_step
    await getattr(self, handler)()
  File "/usr/src/homeassistant/homeassistant/helpers/script.py", line 684, in _async_call_service_step
    await service_task
  File "/usr/src/homeassistant/homeassistant/core.py", line 1738, in async_call
    task.result()
  File "/usr/src/homeassistant/homeassistant/core.py", line 1775, in _execute_service
    await cast(Callable[[ServiceCall], Awaitable[None]], handler.job.target)(
  File "/usr/src/homeassistant/homeassistant/helpers/entity_platform.py", line 769, in handle_service
    await service.entity_service_call(
  File "/usr/src/homeassistant/homeassistant/helpers/service.py", line 678, in entity_service_call
    future.result()  # pop exception if have
  File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 931, in async_request_call
    await coro
  File "/usr/src/homeassistant/homeassistant/helpers/service.py", line 709, in _handle_entity_call
    result = hass.async_run_job(partial(getattr(entity, func), **data))  # type: ignore[arg-type]
  File "/usr/src/homeassistant/homeassistant/core.py", line 615, in async_run_job
    return self.async_run_hass_job(HassJob(target), *args)
  File "/usr/src/homeassistant/homeassistant/core.py", line 570, in async_run_hass_job
    return self.async_add_hass_job(hassjob, *args)
  File "/usr/src/homeassistant/homeassistant/core.py", line 473, in async_add_hass_job
    task = self.loop.create_task(hassjob.target(*args))

I removed the robot cleaner from the miot, but I am using a different device.
Is there a conflict?

Sometimes an error appears, but there is no problem
Stop drying, select first works well
I think it's working perfectly now
Thank you very much
2022-10-18 14:51:37.651 ERROR (Thread-150) [custom_components.dreame_vacuum.dreame.protocol] Execute api call failed: HTTPSConnectionPool(host='api.io.mi.com', port=443): Read timed out. (read timeout=3)
2022-10-18 14:51:37.659 WARNING (Thread-150) [custom_components.dreame_vacuum.dreame.map] Map update Failed: Traceback (most recent call last):
  File "/config/custom_components/dreame_vacuum/dreame/map.py", line 938, in update
    if not self._request_map_from_cloud():
  File "/config/custom_components/dreame_vacuum/dreame/map.py", line 198, in _request_map_from_cloud
    raise DeviceUpdateFailedException(
custom_components.dreame_vacuum.dreame.exceptions.DeviceUpdateFailedException: get_device_property failed

Of course, I just updated it.
2022-10-18 15:31:12.079 INFO (SyncWorker_6) [custom_components.dreame_vacuum.dreame.device] Logging in...
2022-10-18 15:31:14.136 INFO (SyncWorker_6) [custom_components.dreame_vacuum.dreame.device] Connecting to device
2022-10-18 15:31:14.555 INFO (SyncWorker_6) [custom_components.dreame_vacuum.dreame.map] Get Map List:<PHONE_NUMBER>/1034063228/9
2022-10-18 15:31:16.069 INFO (SyncWorker_6) [custom_components.dreame_vacuum.dreame.map] Request map from device [{'piid': 2, 'value': '{"req_type":1,"frame_type":"I","force_type":1}'}]
2022-10-18 15:31:16.230 INFO (SyncWorker_6) [custom_components.dreame_vacuum.dreame.map] Response from device [{'piid': 1, 'value': ''}, {'piid': 3, 'value': '1653707108/1034063228/1,MBTJR8vAmKToIeKT'}, {'piid': 5, 'value':<PHONE_NUMBER>815}]
2022-10-18 15:31:17.395 INFO (SyncWorker_6) [custom_components.dreame_vacuum.dreame.map] Decode I map 3 24
2022-10-18 15:31:17.397 INFO (SyncWorker_6) [custom_components.dreame_vacuum.dreame.device] Get Cleaning History
2022-10-18 15:31:22.590 WARNING (MainThread) [homeassistant.components.sensor] Setup of sensor platform scrape is taking over 10 seconds.
2022-10-18 15:31:22.595 WARNING (MainThread) [homeassistant.components.sensor] Setup of sensor platform scrape is taking over 10 seconds.
2022-10-18 15:31:22.597 WARNING (MainThread) [homeassistant.components.sensor] Setup of sensor platform scrape is taking over 10 seconds.
2022-10-18 15:31:22.602 WARNING (MainThread) [homeassistant.components.sensor] Setup of sensor platform scrape is taking over 10 seconds.
2022-10-18 15:31:22.603 WARNING (MainThread) [homeassistant.components.weather] Setup of weather platform naver_weather is taking over 10 seconds.
2022-10-18 15:31:23.174 WARNING (MainThread) [homeassistant.config_entries] Config entry 'MiBedsideLamp2-D31C' for homekit_controller integration not ready yet: Timeout while waiting for connection to device <IP_ADDRESS>:80; Retrying in background
2022-10-18 15:31:25.613 INFO (MainThread) [custom_components.dreame_vacuum] Update map
2022-10-18 15:31:27.706 INFO (MainThread) [custom_components.dreame_vacuum.dreame.map] Render frame: 10:0 took: 1.95 at scale 4
2022-10-18 15:31:30.031 INFO (MainThread) [custom_components.dreame_vacuum.dreame.map] Render frame: 3:24 took: 2.04 at scale 4
2022-10-18 15:31:35.042 WARNING (MainThread) [homeassistant.components.number] custom_components.xiaomi_miot.number::MiotNumberSubEntity is overriding deprecated methods on an instance of NumberEntity, this is not valid and will be unsupported from Home Assistant 2022.10. Please report it to the custom integration author.
2022-10-18 15:31:35.068 WARNING (MainThread) [homeassistant.components.number] custom_components.xiaomi_miot.number::MiotNumberActionSubEntity is overriding deprecated methods on an instance of NumberEntity, this is not valid and will be unsupported from Home Assistant 2022.10. Please report it to the custom integration author.
2022-10-18 15:32:54.884 INFO (Thread-52) [custom_components.dreame_vacuum.dreame.device] STATUS Changed: 14 -> 6
2022-10-18 15:32:54.885 INFO (Thread-52) [custom_components.dreame_vacuum.dreame.device] AUTO_EMPTY_STATUS Changed: 0 -> 1
2022-10-18 15:32:57.874 INFO (MainThread) [custom_components.dreame_vacuum] Update map
2022-10-18 15:32:58.920 INFO (MainThread) [custom_components.dreame_vacuum.dreame.map] Render frame: 3:24 took: 1.04 at scale 4
2022-10-18 15:33:05.010 INFO (Thread-56) [custom_components.dreame_vacuum.dreame.device] AUTO_EMPTY_STATUS Changed: 1 -> 0
2022-10-18 15:33:18.460 ERROR (Thread-60) [custom_components.dreame_vacuum.dreame.protocol] Execute api call failed: HTTPSConnectionPool(host='api.io.mi.com', port=443): Read timed out. (read timeout=3)
2022-10-18 15:33:18.467 WARNING (Thread-60) [custom_components.dreame_vacuum.dreame.map] Map update Failed: Traceback (most recent call last):
  File "/config/custom_components/dreame_vacuum/dreame/map.py", line 938, in update
    if not self._request_map_from_cloud():
  File "/config/custom_components/dreame_vacuum/dreame/map.py", line 198, in _request_map_from_cloud
    raise DeviceUpdateFailedException(
custom_components.dreame_vacuum.dreame.exceptions.DeviceUpdateFailedException: get_device_property failed

2022-10-18 15:33:18.468 ERROR (Thread-60) [custom_components.dreame_vacuum] Error requesting dreame_vacuum data: get_device_property failed
2022-10-18 15:33:24.502 INFO (Thread-62) [custom_components.dreame_vacuum.dreame.map] Update callback
2022-10-18 15:33:35.492 INFO (Thread-72) [custom_components.dreame_vacuum.dreame.map] Request map from device [{'piid': 2, 'value': '{"req_type":1,"frame_type":"I","force_type":1}'}]
2022-10-18 15:33:35.578 INFO (Thread-72) [custom_components.dreame_vacuum.dreame.map] Response from device [{'piid': 1, 'value': ''}, {'piid': 3, 'value': '1653707108/1034063228/1,hcmZ3Jrzvm4yK8m7'}, {'piid': 5, 'value':<PHONE_NUMBER>194}]
2022-10-18 15:33:36.678 INFO (Thread-72) [custom_components.dreame_vacuum.dreame.map] Decode I map 3 26
2022-10-18 15:33:36.679 INFO (Thread-72) [custom_components.dreame_vacuum.dreame.map] Update callback
2022-10-18 15:33:36.702 INFO (Thread-72) [custom_components.dreame_vacuum] Coordinator update: 26
2022-10-18 15:33:36.702 INFO (Thread-72) [custom_components.dreame_vacuum] Update map
2022-10-18 15:33:38.425 INFO (MainThread) [custom_components.dreame_vacuum.dreame.map] Render frame: 3:26 took: 1.71 at scale 4

Thanks to you, I implemented an automation that allows me to clean the mopping after the sweep cleaning is completed.

And thanks to you, i have implemented map decryption support for other new Mijia robots too and couldn't do it without the map data you sent. I have released a new version for the integration and you should use this instead of testing branch to keep track of new features and fixes. I will fix the unicode room name rendering and add the AI obstacle detection settings for this device later.

Thank you very much.
May I ask one more question? The p2114o model is very similar to the dreame s10 model. Almost identical. Can you implement the features found on the s10 model station?
In the case of the s10 model, after taking out the robot vacuum cleaner from the station, water can come out to clean the rail inside the station.
for example:
https://user-images.githubusercontent.com/61031808/196409780-2757d726-b958-42a9-a44b-21ec584ecf3c.mp4

It works as a station button. I asked just in case.
The error log continues to occur in the new version.
No need to worry?
2022-10-18 20:11:50.003 ERROR (Thread-379) [custom_components.dreame_vacuum.dreame.protocol] Execute api call failed: HTTPSConnectionPool(host='api.io.mi.com', port=443): Read timed out. (read timeout=5)
2022-10-18 20:11:50.009 WARNING (Thread-379) [custom_components.dreame_vacuum.dreame.map] Getting object_name from cloud failed


Use entry-points instead of scripts

The recommended approach to create launch scripts is to use entry_points
and console_scripts.
xref:
https://packaging.python.org/guides/distributing-packages-using-setuptools/#scripts

Looks great indeed, thanks for that!


confirm time zones are consistent in 'time of day' plot

Are the time zones coming in in a standard format including w time zones? need to confirm we are doing any necessary conversion so that data is adjusted to a consistent time zone.

The time zone is set in the view, so it seems to depend on the location of whoever created the views.  Is it a big deal if they aren't all the same, as long as we note what the timezone is on the application page?  We would have to convert timezones locally.

User time zone doesn't seem to be an available dimension from google

For the record, time zone is in the view metadata returned by googleAnaltyticsR::ga_view


feat: add launch action for AILabel icon in icon library

Closes #4323
Changelog
New

add launch action to open component in React storybook for AILabel icon
update to latest icons and gatsby-theme

Testing
Check that AILabel in icon library doesn't have download option, but has launch icon instead that links to storybook

@alisonjoseph The preview isn't working


Issue with clipboard and text doubles.

Apparently YAT always copy both strings to clipboard. Because of this 3rd party translation programs are messed up and text hard to read.
Can it be fixed or I do something wrong?
Here example https://i.imgur.com/789TYwt.png

Greetings! Pardon the prolonged wait for such a minor fix -- some other projects are taking their own time.
The issue was a minor one and caused by YAT itself -- it passed those pesky template strings (the ones with [HF] and [SF]). Since they are not what you most likely want, YAT will now only copy final strings (with all names inserted).


[error]Error Code: ERROR_FILE_IN_USE (relates to sharp package)

Question about an existing feature
What are you trying to achieve?
I'm deploying an Nodejs application via Azure DevOps (Pipelines & Realease) and getting an error. [error]Error Code: ERROR_FILE_IN_USE. I've google'd but it all relates to MSDeploy & I don't make use of it. Anyone seen this before and/or have a fix for this?
When you searched for similar issues, what did you find that might be related?
I'm deploying to Windows IIS, here is documentation I've done on the setup > https://jvdwesthuizen.medium.com/deploying-strapi-on-a-windows-iis-server-with-azure-devops-a0f4a21dd7c2#467b-85772ee5107d
Please provide a minimal, standalone code sample, without other dependencies, that demonstrates this question
All the details are mentioned in the link above ^^
Please provide sample image(s) that help explain this question

I've google'd but it all relates to MSDeploy & I don't make use of it.

The screenshot you've attached shows an error from msdeploy.exe, which looks suspiciously like MSDeploy.
My best guess would be that there's an existing process running that is using the DLLs you're trying to overwrite and this is not really a sharp problem.

Thanks, I see what you mean but I didn't specify nor using msdeploy.exe in my pipeline, you can view that in the link I shared.
I'll see what I can get and share the outcome here.

@dotjohann Were you able to make any progress with this?

Closing due to inactivity but please feel free to reopen with more details if further help is required.


implmenet foreach loops

This one is actually rather annoying to think about, as it's complex control flow.
I think, since foreach is determanisticly sized, we can basically implement it as something like:
Block(..., condition(on_true: self, on_false: next)

where the on true (more iterations required) we loop back to self, but on false (break, continue, end of loop) we jump to the next block. This could of course be very annoying to code due to unique_ptr

To make this more complicated than when I first wrote the issue, we have a range() function now, which means that while the number of iterations of a foreach loop is bounded, it can be practically unbounded when using range(), since you could write:
foreach f : range(100000000000000000000000000)
   ...
endforeach

Which is both easy to write, and could be a problem if we unrolled the whole loop
Although we might run into issues with the maximum size of numbers too...

I think for a first pass we just want to unroll. That might require some reworking for more complicated situations, but this should be sufficient for self-hosting, and for most real-world Meson programs

Foreach loops leak from their context, so in a case like:
a = 'b'
message(a)
foreach a : ['a']
  message(a)
endforeach
message(a)

the result will be:
b
a
a


Supporting import and history from Kraken

What kind of change does this PR introduce? (Bug fix, feature, docs update, ...)

The change brings the following:
(feature) Supporting import from Kraken, and update documentation to this effect
(bugfix/feature) Supporting history from the Kraken exchange
(bugfix) Adding BCH to the supported crypto asset list in the exchange module
(bugfix) Adding ETH to the backing currency list in the exchange module
(bugfix) Adding other special case currency identifiers to the "no prefix" list

What is the current behavior? (You can also link to an open issue here)

Could not import from Kraken
Could not properly trade some alt-coins with Kraken (EOS, DASH or GNO)
Could not import history for ETH backed pairs (though needed importing to be a problem)

What is the new behavior (if this is a feature change)?

You can now import the historical data from kraken supported currency pairs for backtesting, and should have no issues with live trading any supported pair for BCH, EOS, DASH or GNO.

Other information:

There are a lot of undocumented quirks with Kraken's API unfortunately, probably the reason why it was difficult to get historical trades in the past, I've added a couple of notes in the exchange code to this effect.
One such quirk is that Kraken appears to use a very precise timer for generating TIDs but does not expose that TID on historical trade data to the same degree of precision. For this reason requesting new timeframes of data can cause an overlap in the trades returned so a filter needs to be used to prevent re-inserting the same trade twice.
I've tested importing of 5-12 months of data for several pairs, including ETH-XBT, ETH-USD, XBT-BCH, XBT-EOS, USD-BCH, and live market watches for ETH-CAD and ETH-USD

Awesome stuff, will test! As for:

For this reason requesting new timeframes of data can cause an overlap in the trades returned so a filter needs to be used to prevent re-inserting the same trade twice.

This overlap should not be a problem for live gekkos nor for, since the tradeBatcher is already filtering out trades: https://github.com/askmike/gekko/blob/stable/core/budfox/tradeBatcher.js#L95

So after looking a bit more carefully at live trading, which I am unable to test right now, I'm pretty certain it is broken for BCH, EOS, GNO and DASH since they do not properly handle the prefix situation in commands around handling orders.
I also made a small error in the fix to getPortfolio. In the case of the non-prefixed currency pairs the API request sends the pair in the follow format XBTBCH but will receive balances in a format similar to this { [XXBT] => 1.0, [BCH] => 1.0 } where the currency is still prefixed, but the asset is not.
Since calls to get trade and importing work, and this was the intent of this pull request I've undone the change to getPortfolio. I'll issue a new pull request later on today to address specifically the outstanding live trading issues on those asset pairs.

@askmike About the overlapping trade results. Normally my position on this is that someone calling the API with an incrementing trade id wouldn't expect the same results to be called twice so I approach it from that perspective. If you think it is safe I will undo the filter, but do you think this could lead to unexpected side effects down the road?

I fixed a small error I made in the fix to getPortfolio. In the case of the non-prefixed currency pairs the API request sends the pair in the follow format XBTBCH but will receive balances in a format similar to this { [XXBT] => 1.0, [BCH] => 1.0 } where the currency is still prefixed, but the asset is not.

Normally my position on this is that someone calling the API with an incrementing trade id wouldn't expect the same results to be returned twice so I approach it from that perspective. If you think it is safe I will undo the filter, but do you think this could lead to unexpected side effects down the road?

The original idea was that calling getTrades is stateless. For example it is called twice on start (when running Gekko over the commandline, when the strategy needs a "warmup"): once for figuring out whether we can sync exchange data with history data and once to actually seed the strategy. Gekko expects both to return (roughly) the same data, if you filter all the traders on the second call this assumption does not work anymore.

If you think it is safe I will undo the filter, but do you think this could lead to unexpected side effects down the road?

It shouldn't especially if the TID is an ever increasing number, but with Kraken this is not the case. You can leave it for now as is and I'll give it a proper test ASAP.

Apologies for the slow response, and fair play for the work you put in! Major thanks! I've tested it and it works great. I might ping you once issues come up.


Do we need a logging functionality?

Several of our testers wished for a logging functionality that provides feedback about the number of new rows and/or variables being created when using a derive_*() function. I can certainly see the value of having this but certainly wouldn't want to have a "bloated" log as SAS does. Also, in terms of design we would have to carefully think how to implement this in a smart way. Adding loggin calls into every function is certainly not a good idea.

Is it possible to recommend users to another package?  I think tidylog can help with this although I have never tested or used it.
Maybe another exploration activity?

We cannot really redirect users to tidylog if they are using admiral. The only option would be for us to use tidylog internally. However, I don't think that's a viable solution either because that logs everytime you call select(), filter(), summarize() etc. which is often multiple times inside a single derivation. What I would envision is a single log line per derivation something like.
derive_summary_records()
  100 rows added to input datasets of 2000 rows. New total number of rows 2100.
derive_var_ady()
  Variable `ADY` added to input dataset. New total number of variables 11.

I think we need a logging functionality but I would not implement it now because there are too many open questions regarding the future development of admiral. For example

How is metadata used by admiral?
Should admiral offer grouping of derivations?
Should admiral provide a framework?

For these functionalities logging is crucial. Otherwise, the user does not know what was done and we get the black box problem.
However, we need to answer the questions first before we can discuss the logging functionality.
We should keep in mind that implementing logging requires to update all derivations, which is quite a lot of work. Thus I would invest more time in developing a concept which covers as many use cases as possible. I hope this avoids that we need to update all derivations again and again.


simplify deepwalk

Model can't have cycles so we don't need track visited nodes. Also win more lines

I don't think this works. While it can't have cycles, it can have diamonds.
A
|
|----
v.     v
B     C

.

v

D

agreed with @geohot, i had similar problem in my framework too :)
try with
x = a + b
y = x * a
y.backward()

Let's add that as a test

Yes, this would return duplicates nodes on such models (didn't know they exist), although still terminates. I've created a suggested test, however can't make it fail with this change. I suspect backward() logic is somehow resilient to duplicates. Investigating.
Once I have the test I'll abandon this PR since all useful stuff is already integrated.

The leaf nodes aren't visited, that may be the reason
On Wed, Dec 9, 2020, 3:53 PM Daulet<EMAIL_ADDRESS>wrote:

Yes, this would return duplicates nodes on such models (didn't know they
exist), although still terminates. I've created a suggested test, however
can't make it fail with this change. I suspect backward() logic is somehow
resilient to duplicates. Investigating.
Once I have the test I'll abandon this PR since all useful stuff is
already integrated.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/geohot/tinygrad/pull/165#issuecomment-741977205, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AN5SWAHELNVV3MIMKBHC5N3ST7BSPANCNFSM4UTHR64Q
.


Blazor Webassembly fails to publish if AOT compilation enabled due to NPOI

.NET 6 introduced AOT (ahead of time) compilation in order to speed up CPU intensive applications, since the default IL compilation in Blazor WASM is very slow.
Details can be seen here how to set it up but essentially I include the below line in the .csproj file, install some tools, and publish the project to release mode.
<RunAOTCompilation>true</RunAOTCompilation>
The publish fails with the following error:
Error		Precompiling failed for C:\Users\xd00028\source\repos\DataValidatorWeb\DataValidatorWeb\obj\Release\net6.0\linked\NPOI.OOXML.dll.
Mono Ahead of Time compiler - compiling assembly C:\Users\xd00028\source\repos\DataValidatorWeb\DataValidatorWeb\obj\Release\net6.0\linked\NPOI.OOXML.dll
Could not load signature of NPOI.POIFS.Crypt.Dsig.OOXMLURIDereferencer:dereference due to: Could not load file or assembly 'System.Security.Cryptography.Xml, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=cc7b13ffcd2ddd51' or one of its dependencies.
Could not load signature of NPOI.POIFS.Crypt.Dsig.IURIDereferencer:dereference due to: Could not load file or assembly 'System.Security.Cryptography.Xml, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=cc7b13ffcd2ddd51' or one of its dependencies.
Could not load signature of NPOI.POIFS.Crypt.Dsig.Facets.EnvelopedSignatureFacet:preSign due to: Could not load file or assembly 'System.Security.Cryptography.Xml, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=cc7b13ffcd2ddd51' or one of its dependencies.
Could not load signature of NPOI.POIFS.Crypt.Dsig.Facets.OOXMLSignatureFacet:preSign due to: Could not load file or assembly 'System.Security.Cryptography.Xml, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=cc7b13ffcd2ddd51' or one of its dependencies.
Could not load signature of NPOI.POIFS.Crypt.Dsig.Facets.OOXMLSignatureFacet:AddManifestObject due to: Could not load file or assembly 'System.Security.Cryptography.Xml, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=cc7b13ffcd2ddd51' or one of its dependencies.
Could not load signature of NPOI.POIFS.Crypt.Dsig.Facets.OOXMLSignatureFacet:AddManifestReferences due to: Could not load file or assembly 'System.Security.Cryptography.Xml, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=cc7b13ffcd2ddd51' or one of its dependencies.
Could not load signature of NPOI.POIFS.Crypt.Dsig.Facets.OOXMLSignatureFacet:AddSignatureInfo due to: Could not load file or assembly 'System.Security.Cryptography.Xml, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=cc7b13ffcd2ddd51' or one of its dependencies.
Could not load signature of NPOI.POIFS.Crypt.Dsig.Facets.SignatureFacet:preSign due to: Could not load file or assembly 'System.Security.Cryptography.Xml, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=cc7b13ffcd2ddd51' or one of its dependencies.
Could not load signature of NPOI.POIFS.Crypt.Dsig.Facets.SignatureFacet:newTransform due to: Could not load file or assembly 'System.Security.Cryptography.Xml, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=cc7b13ffcd2ddd51' or one of its dependencies.
Could not load signature of NPOI.POIFS.Crypt.Dsig.Facets.SignatureFacet:newReference due to: Could not load file or assembly 'System.Security.Cryptography.Xml, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=cc7b13ffcd2ddd51' or one of its dependencies.
Could not load signature of NPOI.POIFS.Crypt.Dsig.Facets.SignatureFacet:newReference due to: Could not load file or assembly 'System.Security.Cryptography.Xml, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=cc7b13ffcd2ddd51' or one of its dependencies.
Could not load signature of NPOI.POIFS.Crypt.Dsig.Facets.SignatureFacet:brokenJvmWorkaround due to: Could not load file or assembly 'System.Security.Cryptography.Xml, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=cc7b13ffcd2ddd51' or one of its dependencies.
Could not load signature of NPOI.POIFS.Crypt.Dsig.Facets.XAdESSignatureFacet:preSign due to: Could not load file or assembly 'System.Security.Cryptography.Xml, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=cc7b13ffcd2ddd51' or one of its dependencies.
Could not load signature of NPOI.POIFS.Crypt.Dsig.OOXMLURIDereferencer:dereference due to: Could not load file or assembly 'System.Security.Cryptography.Xml, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=cc7b13ffcd2ddd51' or one of its dependencies.
Could not load signature of NPOI.POIFS.Crypt.Dsig.IURIDereferencer:dereference due to: Could not load file or assembly 'System.Security.Cryptography.Xml, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=cc7b13ffcd2ddd51' or one of its dependencies.
Could not load signature of NPOI.POIFS.Crypt.Dsig.Facets.EnvelopedSignatureFacet:preSign due to: Could not load file or assembly 'System.Security.Cryptography.Xml, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=cc7b13ffcd2ddd51' or one of its dependencies.
Could not load signature of NPOI.POIFS.Crypt.Dsig.Facets.OOXMLSignatureFacet:preSign due to: Could not load file or assembly 'System.Security.Cryptography.Xml, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=cc7b13ffcd2ddd51' or one of its dependencies.
Could not load signature of NPOI.POIFS.Crypt.Dsig.Facets.OOXMLSignatureFacet:AddManifestObject due to: Could not load file or assembly 'System.Security.Cryptography.Xml, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=cc7b13ffcd2ddd51' or one of its dependencies.
Could not load signature of NPOI.POIFS.Crypt.Dsig.Facets.OOXMLSignatureFacet:AddManifestReferences due to: Could not load file or assembly 'System.Security.Cryptography.Xml, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=cc7b13ffcd2ddd51' or one of its dependencies.
Could not load signature of NPOI.POIFS.Crypt.Dsig.Facets.OOXMLSignatureFacet:AddSignatureInfo due to: Could not load file or assembly 'System.Security.Cryptography.Xml, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=cc7b13ffcd2ddd51' or one of its dependencies.
Could not load signature of NPOI.POIFS.Crypt.Dsig.Facets.SignatureFacet:preSign due to: Could not load file or assembly 'System.Security.Cryptography.Xml, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=cc7b13ffcd2ddd51' or one of its dependencies.
Could not load signature of NPOI.POIFS.Crypt.Dsig.Facets.SignatureFacet:newTransform due to: Could not load file or assembly 'System.Security.Cryptography.Xml, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=cc7b13ffcd2ddd51' or one of its dependencies.
Could not load signature of NPOI.POIFS.Crypt.Dsig.Facets.SignatureFacet:newReference due to: Could not load file or assembly 'System.Security.Cryptography.Xml, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=cc7b13ffcd2ddd51' or one of its dependencies.
Could not load signature of NPOI.POIFS.Crypt.Dsig.Facets.SignatureFacet:newReference due to: Could not load file or assembly 'System.Security.Cryptography.Xml, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=cc7b13ffcd2ddd51' or one of its dependencies.
Could not load signature of NPOI.POIFS.Crypt.Dsig.Facets.SignatureFacet:brokenJvmWorkaround due to: Could not load file or assembly 'System.Security.Cryptography.Xml, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=cc7b13ffcd2ddd51' or one of its dependencies.
Could not load signature of NPOI.POIFS.Crypt.Dsig.Facets.XAdESSignatureFacet:preSign due to: Could not load file or assembly 'System.Security.Cryptography.Xml, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=cc7b13ffcd2ddd51' or one of its dependencies.
Could not load signature of NPOI.POIFS.Crypt.Dsig.OOXMLURIDereferencer:dereference due to: Could not load file or assembly 'System.Security.Cryptography.Xml, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=cc7b13ffcd2ddd51' or one of its dependencies.
Could not load signature of NPOI.POIFS.Crypt.Dsig.IURIDereferencer:dereference due to: Could not load file or assembly 'System.Security.Cryptography.Xml, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=cc7b13ffcd2ddd51' or one of its dependencies.
Unable to compile method 'void NPOI.POIFS.Crypt.Dsig.SignatureConfig:Init (bool)' due to: 'Could not resolve the signature of a virtual method assembly:C:\Users\xd00028\source\repos\DataValidatorWeb\DataValidatorWeb\obj\Release\net6.0\linked\NPOI.OOXML.dll type:OOXMLURIDereferencer member:(null)'.
Could not load signature of NPOI.POIFS.Crypt.Dsig.Facets.OOXMLSignatureFacet:preSign due to: Could not load file or assembly 'System.Security.Cryptography.Xml, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=cc7b13ffcd2ddd51' or one of its dependencies.
Unable to compile method 'bool NPOI.POIFS.Crypt.Dsig.Facets.OOXMLSignatureFacet:IsSignedRelationship (string)' due to: 'VTable setup of type NPOI.POIFS.Crypt.Dsig.Facets.OOXMLSignatureFacet failed assembly:C:\Users\xd00028\source\repos\DataValidatorWeb\DataValidatorWeb\obj\Release\net6.0\linked\NPOI.OOXML.dll type:OOXMLSignatureFacet member:(null)'.
Unable to compile method 'void NPOI.POIFS.Crypt.Dsig.Facets.OOXMLSignatureFacet:.cctor ()' due to: 'Could not resolve field token 0x040004c0, due to: VTable setup of type NPOI.POIFS.Crypt.Dsig.Facets.OOXMLSignatureFacet failed assembly:C:\Users\xd00028\source\repos\DataValidatorWeb\DataValidatorWeb\obj\Release\net6.0\linked\NPOI.OOXML.dll type:OOXMLSignatureFacet member:(null)'.
Could not load signature of NPOI.POIFS.Crypt.Dsig.Facets.EnvelopedSignatureFacet:preSign due to: Could not load file or assembly 'System.Security.Cryptography.Xml, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=cc7b13ffcd2ddd51' or one of its dependencies.
Could not load signature of NPOI.POIFS.Crypt.Dsig.Facets.SignatureFacet:preSign due to: Could not load file or assembly 'System.Security.Cryptography.Xml, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=cc7b13ffcd2ddd51' or one of its dependencies.
Could not load signature of NPOI.POIFS.Crypt.Dsig.Facets.SignatureFacet:preSign due to: Could not load file or assembly 'System.Security.Cryptography.Xml, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=cc7b13ffcd2ddd51' or one of its dependencies.
Could not load signature of NPOI.POIFS.Crypt.Dsig.Facets.SignatureFacet:preSign due to: Could not load file or assembly 'System.Security.Cryptography.Xml, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=cc7b13ffcd2ddd51' or one of its dependencies.

If I publish the project without setting compilation to AOT it publishes fine. I've attached a sample project with AOT enabled, and if you try publish in Release mode you will see the error.
BlazorAOTApp.zip

I have no idea about this issue. But it looks to be a bug for blazor+AOT instead of NPOI itself. It looks System.Security.Cryptography is not supported on blazor since .NET 5 according to this doc


Live USB enhancement: Indicate start up progress, otherwise user confused that system hung

Is your feature request related to a problem? Please describe.
Booted the 0.5 Live USB on an old Thinkpad X230. On first attempt, system seemed to hang at the FreeBSD logo. Checked documentation and did the unset boot flag to turn on verbose logging and found out that the delay was due to the compressed filesystem being copied to memory. Without some sort of indication about what is happenning, user gets confused and assumes system hung.
USB ultimately booted to desktop after a few mins.
Describe the solution you'd like
Add some sort of minimal logging messages to show progress. Tell them briefly what is happenning with a Please wait message. Newcomers may not know about reading the docs and turning on verbose flags. Make it easy for newcomers to test the Live USB.
Describe alternatives you've considered
Add some text or a keyboard shortcut if user wants to see verbose logging during boot up
Additional context
This is an old Thinkpad X230 with coreboot/SeaBIOS, 16G RAM, 1 TB SSD, Gig ethernet and Atheros AR9462 Wi-Fi. Hardware - HW detection was flawless - detected everything and everything in the Live Session worked as indicated.
Brilliant job @probonopd and team! I am very excited by this system. I am next going to natively install the system and do more testing as a daily driver.

Hello @rsriniva.
We hope to speed up the Live ISO boot process as outlined in https://github.com/helloSystem/ISO/issues/4.
Agree it would be nice to have a progress animation (also known as a "spinner").
Unfortunately I am not aware that this is currently possible in FreeBSD. Probably someone would need to code one.

Ideally, we could combine https://github.com/helloSystem/ISO/issues/226 with a spinner.

I'm working on a PyQt-based Plymouth alternative for FreeBSD

Well... isn't PyQt available only once Xorg is up and running, which is way too late?

PyQt does rely on Xorg. Plymouth relies on linux libraries too (and systemd). I am currently in the process of making my FreeBSD look good and it does not seem possible at the moment sadly

PyQt doesn't rely on X specifically. It just relies on a QPA platform plugin. There's one called bsdfb that can bypass X and write straight to the framebuffer.

I'm pretty sure stuff in /etc/rc.conf like mouse_enable="YES" doesn't start during the boot process which would mean your plymouth like thing wouldn't work.

It does work.

I got it running in boot, and showing an animated splash screen. I just have to refine the animations a little.

Non-technical users tend to find boot messages confusing.

It's debatably more confusing to be given absolutely nothing (blackness without explanation) for an extended period.
From https://github.com/helloSystem/ISO/issues/43#issuecomment-751417524:

… silence as a default can make it more difficult to get feedback from testers …

I suggest showing startup progress. You can improve upon it in due course, but blackness and silence are not good – show something, anything.
Related: https://github.com/helloSystem/ISO/issues/187

@linuxkettle this is exciting, please let me know how to test it

Well you'll be delighted to here I forgot where I put it, but I should find it easy enough.

I know not how well it'll work without the display manager which is also in progress...
Maybe we might get a new login screen.

Exactly, and the display manager I'm using (and making) uses no X server.

So it might not go away

Can you please upload your solution so that we can try it out?

FreeBSD% find /usr/local/lib/qt5 | grep qbsdfb
/usr/local/lib/qt5/plugins/platforms/libqbsdfb.so

We do have libqbsdfb, but how do we make a Qt application use it?

Error reading framebuffer information (Inappropriate ioctl for device)
bsdfb: Failed to initialize screen
no screens available, assuming 24-bit color
Cannot create window: no screens available

I originally got this error too. You need to run it like this:
some_program -platform bsdfb &> /dev/console < /dev/console

Getting "Invalid null command" when trying to run this from csh, and getting "/dev/console: Device not configured" when trying to run this from bash.

Weird...
I'll take a look at it this afternoon.

Wait...
Are you using FreeBSD 12.x, maybe its because of that...

Okay, I got it running again, but sadly only from the command-line. I put the script in /usr/local/bin/splash and can run it with /usr/local/bin/splash -platform bsdfb from the shell. So, the logical next step was to make an rc.d file. Which I did. And it runs the exact same command, giving the error you saw above...

Okay, it works without the ampersand at the end but then it doesn't run in the background, so you have to push Ctrl+C to resume the boot process...

I'd like to know why updating Firefox updates LibreOffice and Thunderbird...

Argh, where's systemd when ya need it?

updating Firefox updates LibreOffice and Thunderbird...

What exactly was the upgrade command?

...and completely broke Qt :~(

If you mean that some preinstalled (non-packaged) applications ceased to work:

https://github.com/helloSystem/ISO/issues/51
https://github.com/helloSystem/ISO/issues/267#issuecomment-903155449

I'd like to know why updating Firefox updates LibreOffice and Thunderbird...
...and completely broke Qt :~(

Me too! https://github.com/helloSystem/ISO/issues/267#issuecomment-917651953
This is not how I'd like things to be but I fear only the Ports Maintainers can fix those issues.

those issues.

Can you describe the issues in any detail?
What exactly was the command that led to something unexpected?
Which version of helloSystem? And so on. Thanks.

Over there.

helloSystem will feature an entirely new Live boot system, which will load initgfx and Xorg and the desktop as soon as possible, while other services are still starting up in the background. So we don't really have time anymore to show a bootanimation before that.

Maybe fbv could be used, it supports animated gif.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=200901


Factor out support for query_arg binding from rest of router changes

Description
This is #1860 minus the following features:

"Mount" support.
State support.

It is based on #1891
Checklist

[ ] I have run cargo make pr-flow
[ ] I have reviewed my own code
[ ] I have added tests

Tests are now passing. The only remaining issue is the naming of "munchers".

Great, can you update the docs too? Those will need a good amount of updates.
Also, I will try to do the second round of review as soon as I get some time (pretty busy with other stuff right now)

👍

I've performed the renaming and updated the documentation. That should address everything you've brought up so far.

I feel like HistoryState and RouterState are too abstracted and complicated? Can we simplify those any more? Want me to give it a shot?

They both implement the same rules, which are as follows:

A given "state" object is either active or inactive.
When a "state" object is active, it stores the current value, and is subscribed to changes to that value.
When a "state" object is inactive, it stores no value, imposes no overhead and is not subscribed to any events.
When an active "state" object is notified of a change, and there are no downstream subscribers, it becomes inactive.
When any API call is made which relies on the "state" object, and it's currently inactive, it becomes active.

These rules ensure the router does the minimum amount of work for any sequence of calls to its API (since the current value will always be cached as long as it is still valid) whilst minimizing the overhead of the router when it is not in use, and ensuring that it cleans up after itself gracefully.
The difference between HistoryState and RouterState is that HistoryState is a singleton, whereas RouterState is parameterized by the user-defined Routable type, but otherwise they implement the same state machine.
The code maps 1:1 onto that state machine: the constructor is used to "activate" the state. The Drop imeplementation is used  to "deactivate" the state. The "update" method is called when an event is received.
If you can simplify the code whilst implementing the same state machine, and without breaking the 1:1 mapping between the code and the state machine it implements, then that would be worthwhile.

I was thinking of simplifying it in a way that the router's state is stored inside the router, not globally. Is that something that can happen? Locally managed state is better than global state.

I was thinking of simplifying it in a way that the router's state is stored inside the router, not globally.

The router API is global, so even if you were able to do that, you'd just be lying to users about where the state lives...
Regardless, I think this should be global state, since it is state which is derived from window.location, which is itself a global property.

I believe correct way of implementing this would be to to first contribute to route-recognizer and add proper query params parsing https://github.com/http-rs/route-recognizer/issues/47
Also I'm closing this PR as it is stale for a long time
@Diggsey  ping me if you make updates and want this reopened.


Send chosen category to the server and get the corresponding image for all players in the first round

54aceedb211d10a5dab790a707915c1e3621959c


Add file attribute upload to variant attributes

I want to merge this change because... it adds file attribute upload to variant attributes.
:warning: This PR contains changes from https://github.com/mirumee/saleor-dashboard/pull/888, which should be merged first.
Feature branch: https://github.com/mirumee/saleor-dashboard/pull/884

PR intended to be tested with API branch:  feature/file-uploads
https://github.com/mirumee/saleor/pull/6568
Screenshots

Pull Request Checklist

[ ] All visible strings are translated with proper context.
[ ] All data-formatting is locale-aware (dates, numbers, and so on).
[ ] Translated strings are extracted.
[ ] Number of API calls is optimized.
[ ] The changes are tested.
[ ] Data-test are added for new elements.
[ ] Type definitions are up to date.
[ ] Changes are mentioned in the changelog.

Test environment config

API_URI=https://feature-file-uploads.api.saleor.rocks/graphql/

Task linked: SALEOR-1825 Add suport for file selection and upload in variant attributes sections

Task linked: SALEOR-1351 Add separate section for attributes that are used in variant selection


How do I create new JSON objects ?!

Hello
I'm trying to create a JSON object like this
[   null,   {     "name": "nameExample",     "age": 45   },   {     "name": "anotherName",     "age": 55   } ]
And eventually get that JSON object as a string.
How can do so ?!

I am making some playground docs as #613 .
And I write the part of source that I used to make JSON.
var jsonArray: JSON = [
    "array": [12.34, 56.78],
    "users": [
        [
            "id": 987654,
            "info": [
                "name": "jack",
                "email"<EMAIL_ADDRESS>            ],
            "feeds": [98833, 23443, 213239, 23232]
        ],
        [
            "id": 654321,
            "info": [
                "name": "jeffgukang",
                "email"<EMAIL_ADDRESS>            ],
            "feeds": [12345, 56789, 12423, 12412]
        ]
    ]
]

There hasn't much activity on this issue for a while so I'll go ahead and consider it fixed. Let me know if you'd like me to reopen it. Thanks!


Add streaming support

Fixes #6
This is an alternative to #326 that is more flexible and introduces fewer new types.
Introduces a ChunkedEntities algebra defining request and response entities that use the chunked transfer-encoding.
Streamed entities are represented by a type Chunks[A] in the algebra. For instance, a streamed response entity containing chunks of type Event has type ResponseEntity[Chunks[Event]], and an endpoint returning such an entity has type Endpoint[Unit, Chunks[Event]].
The type Chunks[A] is an abstract type, which is fixed by interpreters. Both client and server interpreters currently fix it to Akka Stream’s Source[A, _].
Since Wiremock server does not support streaming, we use Akka-HTTP in tests to implement either a server (when testing client interpreters) or a client (when testing a server interpreter).
The type ResponseEntity of the Play server interpreter had to be adapted to support chunked transfer-encoding.
The chunked transfer-encoding works nice for long-running endpoints that intermittently return response items. It is a bit less adapted to file upload/download because the response Content-Length is unknown, which means that clients can not show a progress bar, for instance. The fact that we rely on a one to one mapping between low-level chunks and high-level Akka Stream’s Source items means that we need the underlying HTTP library to do no reframing process. This doesn’t seem to be the case of the Play-WS library, therefore the endpoints.play.client interpreters don’t support the ChunkedEntities algebra. The PR provides interpreters for endpoints.play.server, endpoints.akkahttp.client, endpoints.akkahttp.server, and endpoints.openapi.

@julienrf sorry for necro-bumping, but does this PR already allow to specify/use WebSockets, or would additional functionality be required?

This PR only allows us to describe (and interpret) HTTP endpoints that consume or return entities encoded using the Chunked Transfer-Encoding. So, no, this does not cover WebSockets.
Nevertheless, I believe that we could easily build WebSockets support on top of that. This would be a welcome contribution :)


[RIG EVAL] some css and feedback updates

dc response has no stat:

dc response has stat:

I'll merge for now.


hubot crashes on msg.send(null) when using irc adapter

Should the adapter do nothing, or send an empty string in this case? I have a patch ready for both options (easy fix).

My vote is to say what null is.. nothing :-)

you can't send an empty string... that'd be nonsense. IMHO

Okay, that's my vote too. See #7 for my pull request.


How to force a refresh of the web page via CLI

Hello,
is there a way to login via SSH and force a reload of the page?
Regards
Ralf

You could use the example of the hourly reload of the website as contained in the crontab of user pi
Example: Reload webpage every hour
0 * * * * xdotool key ctrl+R

Hi, thanks 1000 times. Script I added was:
reload.sh
#!/bin/bash

DISPLAY=:0 xdotool key ctrl+R

works like a charm.
Regards
Ralf

This works indeed (in most cases)!
BUT; it does not clear the cache, so i'm loading a webpage with a .mp4 file where only the video file (.mp4) changes.
Problem is, when we use the command like mentioned above, it keeps showing the same video.
Only after a reboot, or manual restart the chromium-browser it will show the new video.
I already tried the following:
DISPLAY=:0 xdotool key ctrl+shift+R

or
DISPLAY=:0 xdotool key F5

With both commands you see the page is reloading, but it does not load the new video file.
Anybody have an idea?


chore: deploy fastify example

This PR creates the necessary scripts and artifacts to build and deploy @scalar-examples/fastify-api-reference

creates a Dockerfile for containerizing the application
uses turbo to create an optimized docker image and does not depend on the base scalar image.
moves the base tsconfig.json file to it's own package so turbo can prune dependencies for a single package/example
cloudbuild steps to build and deploy the example to cloud run.

The TSConfig is an interesting one. I'm open but I'm not clear on the use case.
I don't want to move away from the base image. This was done to reduce CI time. We only ever need to build the whole project once an then each distribution can just copy the files it needs from the base. It's a very significant reduction in overall build time (and cost) and a very low complexity approach.


Add support for UIButton setBackgroundImage?

Is is possible to use the PINRemoteImage categories to set the background image of UIButtons? This is usually the primary use (at least in my experience) for images in UIButtons. Or do I have to use the PINRemoteImageManager to download and image and then set the image on the button's background on the main thread?

Happy to accept a pull request to add this support!

@garrettmoon Ok i submitted a PR (#178) to add this functionality (along with some additions to the example project to showcase the changes).

Thank you! I'll try and take a look soon.


Pitch Detection

I posted this under a previous issue but I assume sense the issue is entirely different a new branch is appropriate, please tell me if it is not.
Following your instructions HERE
I installed the dependencies into a new project manually and use the code. It seems to work (but doesnt do anything except print some info via terminal from the 'doSoemthing' Function) but am not sure how to go about creating a pitch detector on (I'm compiling for MacOS). I'm referencing Beethoven's Guitar Tuner Example
is this the best available project to reference or is there possibly a better one?

Correct, that would be a good starting point.
Alternatively, you could also check AudioKit which is a much more popular framework than this one (for all kinds of audio stuff), and see if it suits your needs better (they have plenty of examples online).


How to run proms program ?

Hi Proms community.
I tried to run proms program, unfortunately I have received an error message explaining me the program is not installed.
I use Ubuntu 18.
I followed the next steps:
florian@computer /tmp> pip install --upgrade proms
Requirement already satisfied: proms in /home/flonflon/.local/lib/python3.9/site-packages (1.0.5)
Collecting proms
  Using cached proms-1.0.5-py3-none-any.whl (25 kB)
  Using cached proms-1.0.4-py3-none-any.whl (20 kB)
Requirement already satisfied: scikit-learn in /home/flonflon/.local/lib/python3.9/site-packages (from proms) (0.24.1)
Requirement already satisfied: numpy in /home/flonflon/.local/lib/python3.9/site-packages (from proms) (1.20.2)
Requirement already satisfied: scikit-survival in /home/flonflon/.local/lib/python3.9/site-packages (from proms) (0.15.0.post0)
Requirement already satisfied: pandas in /home/flonflon/.local/lib/python3.9/site-packages (from proms) (1.2.3)
Requirement already satisfied: scipy in /home/flonflon/.local/lib/python3.9/site-packages (from proms) (1.6.2)
Requirement already satisfied: matplotlib in /usr/local/lib/python3.9/dist-packages (from proms) (3.2.0)
Requirement already satisfied: pyyaml in /home/flonflon/.local/lib/python3.9/site-packages (from proms) (5.4.1)
Requirement already satisfied: xgboost in /home/flonflon/.local/lib/python3.9/site-packages (from proms) (1.4.2)
Requirement already satisfied: kiwisolver>=1.0.1 in /usr/lib/python3/dist-packages (from matplotlib->proms) (1.3.1)
Requirement already satisfied: pyparsing!=2.0.4,!=2.1.2,!=2.1.6,>=2.0.1 in /usr/lib/python3/dist-packages (from matplotlib->proms) (2.4.7)
Requirement already satisfied: python-dateutil>=2.1 in /usr/lib/python3/dist-packages (from matplotlib->proms) (2.8.1)
Requirement already satisfied: cycler>=0.10 in /usr/lib/python3/dist-packages (from matplotlib->proms) (0.10.0)
Requirement already satisfied: pytz>=2017.3 in /usr/lib/python3/dist-packages (from pandas->proms) (2021.1)
Requirement already satisfied: joblib>=0.11 in /home/flonflon/.local/lib/python3.9/site-packages (from scikit-learn->proms) (1.0.1)
Requirement already satisfied: threadpoolctl>=2.0.0 in /home/flonflon/.local/lib/python3.9/site-packages (from scikit-learn->proms) (2.1.0)
Requirement already satisfied: ecos in /home/flonflon/.local/lib/python3.9/site-packages (from scikit-survival->proms) (2.0.7.post1)
Requirement already satisfied: numexpr in /home/flonflon/.local/lib/python3.9/site-packages (from scikit-survival->proms) (2.7.3)
Requirement already satisfied: osqp!=0.6.0,!=0.6.1 in /home/flonflon/.local/lib/python3.9/site-packages (from scikit-survival->proms) (0.6.2.post0)
Requirement already satisfied: qdldl in /home/flonflon/.local/lib/python3.9/site-packages (from osqp!=0.6.0,!=0.6.1->scikit-survival->proms) (0.1.5.post0)
florian@computer /tmp> proms_train -h
proms_train: command not found

Do you have any idea to help me to run it ?

It should be installed in the same directory where python is installed.   What is the output of
which python


[BUG] K3S 1.21.3-k3s1 - Issue with pods accessing PVCs

(Im not sure if this is an issue with K3D or an issue with the new K3S version or both of them together but I thought I'd start here ..)
What did you do
k3d cluster create -i rancher/k3s:v1.21.3-k3s1 --k3s-server-arg '--disable=traefik' --k3s-server-arg '--disable=metrics-server'
helm repo add elastic https://helm.elastic.co
helm upgrade --install elastic/elasticsearch elastic
{"type": "server", "timestamp": "2021-08-09T13:28:11,343Z", "level": "ERROR", "component": "o.e.b.ElasticsearchUncaughtExceptionHandler", "cluster.name": "elasticsearch", "node.name": "elasticsearch-master-0", "message": "uncaught exception in thread [main]",
"stacktrace": ["org.elasticsearch.bootstrap.StartupException: java.lang.IllegalStateException: Unable to access 'path.data' (/usr/share/elasticsearch/data)",

What did you expect to happen
The PVCs created as part of the Helm deployment do not have the correct permissions so the pods cannot access the data on them.
I have also tried this with other charts (e.g Redis / Neo4J / RabbitMQ etc .. anything that creates PVCs) so this is nothing to do with ElastiSearch directly .. it was just one of the broken parts of our deployment.
Switching to k3s:v1.21.2-k3s1 everything is fine and behaves as it should. Is this a regression in K3S ?
Screenshots or terminal output
(See above)
Which OS & Architecture

MacOS

Which version of k3d

k3d version v4.4.7

Which version of docker

Server: Docker Engine - Community
Engine:
Version:          20.10.7

This is a known bug in K3s which will be fixed in the next release. https://github.com/k3s-io/k3s/issues/3704

Hi @stephenpope , thanks for opening this issue! As @ChristianCiach pointed out (thank you!), this is a problem with k3s, which we cannot influence in k3d.
Due to this, I'll go ahead and close this issue here. Feel free to reopen if you think we can do something from our side :+1:

np .. I was going to close when the next 1.21 version was out of the door, but feel free to close :)


Missing backwards-compat. imports

mycroft.skills.intent_services.adapt_service.AdaptIntent is not backwards-compatible
https://github.com/NeonGeckoCom/NeonCore/pull/641#issuecomment-2035787446
mycroft.util.record is missing
https://github.com/NeonGeckoCom/NeonCore/pull/641#issuecomment-2035788147

related to https://github.com/OpenVoiceOS/ovos-core/issues/433


Log ongoing image pull progress

When an image is pulled:
2016/05/16 08:34:45 Pulling image docker.io/fedora:latest
...

there's no progress report.
We should log progress at constant intervals.

cc @enoodle @pweil-

seems like we will need to use https://github.com/docker/docker/blob/77237be0e23dfaba4d4d97a525c3ecc7fb819042/utils/jsonmessage.go
to get the json we will need to change https://github.com/openshift/image-inspector/blob/master/pkg/inspector/image-inspector.go#L74 to have an output stream and rawJSON.

OK, about how it should look like: every minute we log a line about the progress. (Not a real live progress bar which may break the terminal and the logging applications).

AFAIK The feedback that we get from docker is in this form so it will be difficult to know the exact percentage of the image that we already downloaded / extracted, but we can log something like "Pulling..." every minute, is that good enough ?

@enoodle and how that would be coping with kubernetes pods output logging?

@simon3z The first option not so much. The second one ( Pulling... ) will just show this multiple times in the log.

@simon3z The first option not so much. The second one ( Pulling... ) will just show this multiple times in the log.

@enoodle that's why I suggested the second one to begin with. I think that's the way to go. I think logging every minute is a good interval (cc @pweil- )

how about we just give the OutputStream in the ImagePullOptions and point to os.StdOut?  It's a simple change and looks like:
imagePullOption := docker.PullImageOptions{
			Repository: i.opts.Image,
			OutputStream: os.Stdout,
		}

https://gist.github.com/pweil-/9a6c4f3359d39837c657c2da40513d66

@pweil- Yes, This is what I ment in the first comment but I thought it distorts the terminal/log too much so I thought of adding this parser that docker uses. I would suggest going with just "Pulling..." with no progress bar over that.

how about we just give the OutputStream in the ImagePullOptions and point to os.StdOut? It's a simple change and looks like:

@pweil- @enoodle if there's an option to customize the output so that it's docker/kubernetes/openshift log-friendly, then it's ok with me.
The information I am interested in is what's the progress of the pull but I don't want a fancy output that is hard to understand over the logs and the console.
We can decide to log by time (e.g. every minute) or by progress (e.g. every 10%?).

Fixed by #16


[BUG] shlok page navbar is not working fine

when you scroll down and click on features in shlok page the dropdown gets distorted

Take reference from rejuvenate page https://akshitagupta15june.github.io/Moksh/Rejuvenate_page/rejuvenate.html

Can you assign this to me?

@akshitagupta15june   I would like to work on it

@akshitagupta15june  I would like to work on it

assigned!

@akshitagupta15june  but you told me that you would assign me an issue on priority on the behalf of a previous issues. So please assign it to me

check this https://github.com/akshitagupta15june/Moksh/issues/1091 @Developer-Swati

Ok thanks @akshitagupta15june


Configuration via environment variables

This PR allows us to configure vaultenv using environment variables (fixes #28). We support setting the following options:

--host
--port
--token
--secrets-file
--[no-]connect-tls
--[no-]validate-certs
--[no-]inherit-env
--retry-base-delay-milliseconds
--retry-attempts

Notes:

The first three are named after the corresponding variables which can be used to configure the official vault CLI: VAULT_HOST, VAULT_PORT, and VAULT_TOKEN.
The others are prefixed with VAULTENV.
The options which disable defaults are named VAULTENV_NO_*, because they explicitly disable the default behavior.
CLI arguments take precedence over environment variables.
Boolean settings are parsed from the strings "true" and "false". No other formats are supported.
Because some users might want to override VAULTENV_NO_* environment variables, I added in new options: --validate-certs, --inherit-env, --connect-tls, which are no-ops by default, but can override these environment variables. These options are mutually exclusive: vaultenv will throw an error when it encounters both --connect-tls and --no-connect-tls. (Although the error message isn't that great)

I believe I addressed all your comments. Some notes:

I moved the option handling to a separate Config module in src and added a library section to package.yaml
I renamed EnvSwitches to EnvFlags and documented them. The reason for the EnvVar type alias was just readability.
I didn't put the individual parsers to the toplevel. I opted to put them in the where clause instead. Otherwise I'd have to continue to pass in envFlags and envVars to most subparsers. This way, they are still part of the scope of optionsParser

Thanks for the reviews! I've taken your suggestions and the docs should be more clear now. Let me know if there's anything else!

Oh yeah, I didn't catch that because the -Wall and -Werror flags were set for the executable only. Fixed that in the latest commit


⚠ Bofrost.fr has degraded performance

In 961a783, Bofrost.fr (https://www.bofrost.fr) experienced degraded performance:

HTTP code: 200
Response time: 1640 ms

Resolved: Bofrost.fr performance has improved in 2aaa835 after 6 minutes.


Bugfix: strings must be XML-encoded ("escaped")

Hi @billstclair,
Thanks for this package. I noticed two issues while using it today.
Can you accept and publish PRs? That would be better than another version of the same package at package.elm-lang.org
One thing is that it does not escape < when encoding strings. Same problem at decoding.
This PR is just a quick fix / PoC but I could work on it.
The other issue is when encoding a list of objects. In that case, the object's keys are "inlined" but they should be surrounded by some "wrapper tag".

Another problem is that jsonToXml seems to shuffle the items in lists under certain circumstances (e.g. when the items are all like [ {item: {…}}, {item: {…}}, …]

Regarding character entities:
https://en.wikipedia.org/wiki/List_of_XML_and_HTML_character_entity_references

For encoding, it should be sufficient to only encode < and & in string
In tag names, I'm not sure what characters are allowed... it's probably best to throw an error for tag names with invalid characters.
For decoding, all five predefined entities must be decoded (this is required by the XML spec according to wikipedia).
Not sure if it makes sense to decode more than the five predefined entities…

I think, any function that creates a Tag should only create it if this yields valid XML.
Currently, only the object function creates a tag but it doesn't check the tag name for validity:
encode 1 <| object [("in>alid", Dict.empty, string "content")]
--> "<in>alid>content</in>alid>" : String

object could return Result String Value instead of Value. However that would be a major API change.

Found another bug in jsonToXml; I'll try to fix it later.

I've been sick, so I haven't done these yet. Hopefully soon.

I finally looked at this. I have very little mental energy these days, which is why I retired in September of 2020, though I appear to be slowly getting better.
I merged your pull branch into the base, and got the test error below. If you get the same thing, please fix it. Otherwise, I have some sort of configuration or merge error.
I am considering giving you commit permission on the repository (adding you as a collaborator), so that you can fix these things yourself.
As for the decoding of {"a": null}, I have no opinion. If you want to make it decode to Object [], I have no objection. The one advantage of decoding to Tag "a" Dict.empty (StrNode "") is that can re-encode to {"a": null} instead of {}, but I doubt anybody will care.
$ elm-test

elm-test 0.19.1-revision4
-------------------------

Running 28 tests. To reproduce these results, run: elm-test --fuzz 100 --seed<PHONE_NUMBER>57861

↓ Tests
↓ Encode test
↓ Find bug: json object with many fields is encoded as '' if one field is null
✗ encode object JSON object with one null field

    ""
    ╷
    │ Expect.equal
    ╵
    "<tag1></tag1>\n<tag2></tag2>"

TEST RUN FAILED

Duration: 251 ms
Passed:   27
Failed:   1

All the best and I hope you find back into a fun job when you feel right!
Yes, I'd love to bring the enhancements back to the elm community as a contributer to this project. Currently, I've symlinked the patched files of this repository into my project.
Regarding tests:
For this branch specifically, it seems that I forgot to push two commits. With this commits, the tests pass, though incomplete because of Test.skip (which I fixed in one of my other PRs).


wg_engine: webgpu engine optimization ideas

global vertex buffer instead of individual vertex buffer per mesh
AABB-based composition and blend
simplified path trianglulation for shapes without strokes
decompose blend, masked blend and composition shaders: single shader per blend and composition method

@SergeyLebedkin please update the progress or or close.


Call to undefined method Closure::fields()

Hello,
I'm running Grav v1.6.0-rc.4 - Admin v1.9.0-rc.4.
When trying to manage users created before the installation of your plugin, I get an error on those who have an admin privilege (I tried on a user with just site access, and it doesn't bug) :

Error
Call to undefined method Closure::fields()

The lines triggering the error are 154 to 157 of \system\src\Grav\Common\User\DataUser\User.php
:
public function getMediaFolder()
    {
        return $this->blueprints->fields()['avatar']['destination'] ?? 'user://accounts/avatars';
    }

I think the problem comes from the avatars of the users I tested. They have one defined, while the user that didn't triggered the error has no avatar.

Problem fixed here : https://github.com/getgrav/grav/issues/2422
You can close this issue.


Support "moduleResolution": "bundler" in tsconfig.json

Angular v18 now uses "moduleResolution": "bundler" (instead of "moduleResolution": "node") in tsconfig.json.
That causes compilation errors in AngularFire, which relies on rxfire.
See https://github.com/angular/angularfire/issues/3541#issuecomment-2139600513 and https://github.com/FirebaseExtended/rxfire/issues/100#issuecomment-2140857573.

Any news on this?

Should be addressed in v6.1


Figure 25 working for everyone?

I presume that the caption for Figure 25. **[Not building, but no error shows up?! May get fixed automatically]. can now be removed.

Yes, think so. I put it there weeks ago.

I removed it in and am closing.

Damn - beat me to it.

I'd already done it and just pushed - I'll fix any conflict and then push again.

Exact same edit - no conflict. Nice.


Automated Package Upgrade

:tada: This PR is included in version 2.0.16 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Write Build.tests()

When This gets merged https://github.com/Linaro/squad/pull/927, squad-client should have the same in the api.

Sounds great! Also, maybe duplicate of https://github.com/Linaro/squad-client/issues/5 ?

Wow, how fast 9 months goes by! It's definitely a duplicate. I was too excited to open this issue here I forgot to check it there was one already. I'm planning on doing this after all data is filled up in prod, probably mid next week

Closed in https://github.com/Linaro/squad-client/pull/98


Fix: set underlineColorAndroid properly

This PR fixes #6332
The issue is that Android Framework will return the same drawable instance for all requests if they request for the same resource. So the changes on the drawable instance will affect all users(TextInput in this case). The solution is very easy, call mutate() before change it will get a new drawable instance which make sure the change doesn't affect other users.

Is this good to merge?

Seems like a good fix, text inputs will consume a bit more memory since they will all have a different background drawable but it should be negligible.
@astreet are you fine with this change?

Seems fine to me, we only would be creating a new drawable when a color is actually set.

Unfortunately, I've had to unland this diff as we're hitting the AOSP bug described here: https://code.google.com/p/android/issues/detail?id=191754

(AFAICT, it looks like just checking if getConstantState returns null, which inherently means canConstantState returned false, and not calling mutate in that case would fix this)

Cool, good to know that. Will you fix this? @astreet

Yeah, I'm putting up a fix for it


Make test runner test against the first SHA of the day

Instead of having a scheduled job update the SHA all test runners should be testing against, we can just have all runners test against the first SHA committed that day.

I don't think this can be made robust. Whatever the condition for testing commits for "is today" is and whatever order one takes at merge commits, later (merge) commits could make it such that another commit is the first that matches the "is today" condition. This is just a problem with Git, and that one can't tell what the master branch has pointed to in the past.

Assuming each commit comes from a PR, you could find the first PR to merge today (whenever that is), and use the merge_commit_sha property to get the corresponding HEAD of master. It does add a dependency on the GitHub API though.

Yeah, something around PR status should be robust against later changes in Git history. curl https://api.github.com/repos/w3c/web-platform-tests/pulls/7233 has "merged_at": "2017-09-04T07:19:20Z",63763763ad8fc064ad03ec1fa" and as long as a PR isn't opened and merged again I guess that would never change.
I think one would have to inspect all 7000+ PRs, however, since any of the PRs could be the earliest one merged today, and agreeing on (say) 100 PRs but checking at different times could lead to different results.
Overall, I think it'd be less work for everyone to pick a commit per day and publish it somewhere. It would be fairly simple to set up a cron job that adds a new tag in the repo itself once per day, would that be better or worse than having the dashboard publish it?

I agree that your method is simpler. But something like:
curl 'https://api.github.com/search/issues?q=type:pr+repo:w3c/web-platform-tests+is:merged+merged:>=2017-09-04'

Can give you PRs that were merged today.

Ah, I guess as long as the number of PRs in a day never exceeds 100, no pagination code would be needed, and that'd be robust.
I think this choice is ultimately up to @bobholt and what @thejohnjansen would prefer to work with.

 No faffing around trying to figure out the "first commit of the day" or anything—just set it to be "one commit per day" with it chosen pretty arbitrarily.

simply store the "current test run commit" somewhere

The first part of what you mentioned was in the original design doc and I implemented it at some point then removed it in anticipation that #40 (this issue) would be a better solution. I resurrected the code from an old private fork of the repo and uploaded it to a branch in case it could come in useful.

@gsnedders, yep, just recording what master points to at a regular 24-hour interval is what I had in mind, and it looks like that's what @jeffcarp's resurrected code does.

@mattl, this is also related to the Q4 Consistent results for all browsers are updated every 24 hours OKR and https://github.com/w3c/wptdashboard/issues/138.

Seems to me that if you make this the behaviour, then https://github.com/w3c/wptdashboard/issues/138 becomes redundant (excepting errors) as the runs will all be against that hash.

@lukebjerring yes that's correct if the runs were successful 100% of the time, but #138 might still be necessary in order to lessen the impact of the occasional infra hiccup

@mattl - I'm under the impression that the way that you're choosing which SHA to use makes this issue relevant again.
Note that it was closed via https://github.com/w3c/wptdashboard/blob/master/run/shas.py


Real-time News Data Stream via WebSocket Subscription

Reopened this Feature in separate PR, due to renaming issues.

We are thinking to merge https://github.com/alpacahq/alpaca-py/pull/473
Therefore, please let me edit code same to avoid conflict after merging this PR.