Tapo exception: Returned unknown error_code: 1003 msg: No message

Version of the integration
Version Installed: 2.12.0
Installed via: HACS
Configuration
Mixed:
Tapo P100 & P110
Firmware: 1.3.0 build 230905 Ref 152200

Logger: custom_components.tapo.coordinators
Source: custom_components/tapo/coordinators.py:156
Integration: TP-Link Tapo (documentation, issues)
First occurred: 03:26:50 (6807 occurrences)
Last logged: 20:49:03

Tapo exception: Returned unknown error_code: 1003 msg: No message

Describe the bug
Unknown - Repeated errors with error code 1003 msg: No Message provided, almost every second.
Debug log

2023-12-02 20:15:03.631 ERROR (MainThread) [custom_components.tapo.coordinators] Tapo exception: Returned unknown error_code: 1003  msg: No message
2023-12-02 20:15:33.632 ERROR (MainThread) [custom_components.tapo.coordinators] Tapo exception: Returned unknown error_code: 1003  msg: No message
2023-12-02 20:16:03.632 ERROR (MainThread) [custom_components.tapo.coordinators] Tapo exception: Returned unknown error_code: 1003  msg: No message
2023-12-02 20:16:33.637 ERROR (MainThread) [custom_components.tapo.coordinators] Tapo exception: Returned unknown error_code: 1003  msg: No message
2023-12-02 20:17:03.633 ERROR (MainThread) [custom_components.tapo.coordinators] Tapo exception: Returned unknown error_code: 1003  msg: No message
2023-12-02 20:17:33.645 ERROR (MainThread) [custom_components.tapo.coordinators] Tapo exception: Returned unknown error_code: 1003  msg: No message
2023-12-02 20:18:03.633 ERROR (MainThread) [custom_components.tapo.coordinators] Tapo exception: Returned unknown error_code: 1003  msg: No message
2023-12-02 20:18:33.670 ERROR (MainThread) [custom_components.tapo.coordinators] Tapo exception: Returned unknown error_code: 1003  msg: No message
2023-12-02 20:19:03.632 ERROR (MainThread) [custom_components.tapo.coordinators] Tapo exception: Returned unknown error_code: 1003  msg: No message
2023-12-02 20:19:33.649 ERROR (MainThread) [custom_components.tapo.coordinators] Tapo exception: Returned unknown error_code: 1003  msg: No message
2023-12-02 20:20:03.644 ERROR (MainThread) [custom_components.tapo.coordinators] Tapo exception: Returned unknown error_code: 1003  msg: No message
2023-12-02 20:20:33.632 ERROR (MainThread) [custom_components.tapo.coordinators] Tapo exception: Returned unknown error_code: 1003  msg: No message
2023-12-02 20:21:03.636 ERROR (MainThread) [custom_components.tapo.coordinators] Tapo exception: Returned unknown error_code: 1003  msg: No message
2023-12-02 20:21:33.633 ERROR (MainThread) [custom_components.tapo.coordinators] Tapo exception: Returned unknown error_code: 1003  msg: No message
2023-12-02 20:22:03.632 ERROR (MainThread) [custom_components.tapo.coordinators] Tapo exception: Returned unknown error_code: 1003  msg: No message
2023-12-02 20:22:33.640 ERROR (MainThread) [custom_components.tapo.coordinators] Tapo exception: Returned unknown error_code: 1003  msg: No message
2023-12-02 20:23:03.639 ERROR (MainThread) [custom_components.tapo.coordinators] Tapo exception: Returned unknown error_code: 1003  msg: No message
2023-12-02 20:23:33.653 ERROR (MainThread) [custom_components.tapo.coordinators] Tapo exception: Returned unknown error_code: 1003  msg: No message
2023-12-02 20:24:03.641 ERROR (MainThread) [custom_components.tapo.coordinators] Tapo exception: Returned unknown error_code: 1003  msg: No message
2023-12-02 20:24:33.638 ERROR (MainThread) [custom_components.tapo.coordinators] Tapo exception: Returned unknown error_code: 1003  msg: No message
2023-12-02 20:25:03.645 ERROR (MainThread) [custom_components.tapo.coordinators] Tapo exception: Returned unknown error_code: 1003  msg: No message
2023-12-02 20:25:33.645 ERROR (MainThread) [custom_components.tapo.coordinators] Tapo exception: Returned unknown error_code: 1003  msg: No message
2023-12-02 20:25:53.375 ERROR (MainThread) [custom_components.tapo.coordinators] Tapo exception: Returned unknown error_code: 1003  msg: No message
2023-12-02 20:25:53.376 ERROR (MainThread) [custom_components.tapo.coordinators] Error fetching tapo data: Error tapo exception: Returned unknown error_code: 1003  msg: No message
2023-12-02 20:26:03.637 ERROR (MainThread) [custom_components.tapo.coordinators] Tapo exception: Returned unknown error_code: 1003  msg: No message
2023-12-02 20:26:23.367 ERROR (MainThread) [custom_components.tapo.coordinators] Tapo exception: Returned unknown error_code: 1003  msg: No message
2023-12-02 20:26:32.756 ERROR (MainThread) [custom_components.tapo.coordinators] Tapo exception: Returned unknown error_code: 1003  msg: No message
2023-12-02 20:26:32.756 ERROR (MainThread) [custom_components.tapo.coordinators] Error fetching tapo data: Error tapo exception: Returned unknown error_code: 1003  msg: No message
2023-12-02 20:26:33.633 ERROR (MainThread) [custom_components.tapo.coordinators] Tapo exception: Returned unknown error_code: 1003  msg: No message
2023-12-02 20:26:53.381 ERROR (MainThread) [custom_components.tapo.coordinators] Tapo exception: Returned unknown error_code: 1003  msg: No message
2023-12-02 20:27:02.755 ERROR (MainThread) [custom_components.tapo.coordinators] Tapo exception: Returned unknown error_code: 1003  msg: No message
2023-12-02 20:27:03.641 ERROR (MainThread) [custom_components.tapo.coordinators] Tapo exception: Returned unknown error_code: 1003  msg: No message
2023-12-02 20:27:23.364 ERROR (MainThread) [custom_components.tapo.coordinators] Tapo exception: Returned unknown error_code: 1003  msg: No message
2023-12-02 20:27:32.770 ERROR (MainThread) [custom_components.tapo.coordinators] Tapo exception: Returned unknown error_code: 1003  msg: No message
2023-12-02 20:27:33.640 ERROR (MainThread) [custom_components.tapo.coordinators] Tapo exception: Returned unknown error_code: 1003  msg: No message
2023-12-02 20:27:38.662 ERROR (MainThread) [custom_components.tapo.coordinators] Tapo exception: Returned unknown error_code: 1003  msg: No message
2023-12-02 20:27:38.662 ERROR (MainThread) [custom_components.tapo.coordinators] Error fetching tapo data: Error tapo exception: Returned unknown error_code: 1003  msg: No message
2023-12-02 20:27:50.364 ERROR (MainThread) [custom_components.tapo.coordinators] Tapo exception: Returned unknown error_code: 1003  msg: No message
2023-12-02 20:27:50.364 ERROR (MainThread) [custom_components.tapo.coordinators] Error fetching tapo data: Error tapo exception: Returned unknown error_code: 1003  msg: No message
2023-12-02 20:27:53.371 ERROR (MainThread) [custom_components.tapo.coordinators] Tapo exception: Returned unknown error_code: 1003  msg: No message
2023-12-02 20:27:57.511 ERROR (MainThread) [custom_components.tapo.coordinators] Tapo exception: Returned unknown error_code: 1003  msg: No message
2023-12-02 20:27:57.511 ERROR (MainThread) [custom_components.tapo.coordinators] Error fetching tapo data: Error tapo exception: Returned unknown error_code: 1003  msg: No message
2023-12-02 20:28:02.753 ERROR (MainThread) [custom_components.tapo.coordinators] Tapo exception: Returned unknown error_code: 1003  msg: No message
2023-12-02 20:28:03.633 ERROR (MainThread) [custom_components.tapo.coordinators] Tapo exception: Returned unknown error_code: 1003  msg: No message
2023-12-02 20:28:08.699 ERROR (MainThread) [custom_components.tapo.coordinators] Tapo exception: Returned unknown error_code: 1003  msg: No message
2023-12-02 20:28:12.324 WARNING (MainThread) [homeassistant.helpers.entity] Update of media_player.lg_webos_tv_uk6750pld is taking over 10 seconds
2023-12-02 20:28:12.324 WARNING (MainThread) [homeassistant.components.media_player] Updating webostv media_player took longer than the scheduled update interval 0:00:10
2023-12-02 20:28:20.361 ERROR (MainThread) [custom_components.tapo.coordinators] Tapo exception: Returned unknown error_code: 1003  msg: No message
2023-12-02 20:28:22.326 WARNING (MainThread) [homeassistant.components.media_player] Updating webostv media_player took longer than the scheduled update interval 0:00:10
2023-12-02 20:28:23.365 ERROR (MainThread) [custom_components.tapo.coordinators] Tapo exception: Returned unknown error_code: 1003  msg: No message
2023-12-02 20:28:27.520 ERROR (MainThread) [custom_components.tapo.coordinators] Tapo exception: Returned unknown error_code: 1003  msg: No message
2023-12-02 20:28:32.327 WARNING (MainThread) [homeassistant.components.media_player] Updating webostv media_player took longer than the scheduled update interval 0:00:10
2023-12-02 20:28:32.753 ERROR (MainThread) [custom_components.tapo.coordinators] Tapo exception: Returned unknown error_code: 1003  msg: No message
2023-12-02 20:28:33.635 ERROR (MainThread) [custom_components.tapo.coordinators] Tapo exception: Returned unknown error_code: 1003  msg: No message
2023-12-02 20:28:38.674 ERROR (MainThread) [custom_components.tapo.coordinators] Tapo exception: Returned unknown error_code: 1003  msg: No message
2023-12-02 20:28:42.329 WARNING (MainThread) [homeassistant.components.media_player] Updating webostv media_player took longer than the scheduled update interval 0:00:10
2023-12-02 20:28:50.354 ERROR (MainThread) [custom_components.tapo.coordinators] Tapo exception: Returned unknown error_code: 1003  msg: No message
2023-12-02 20:28:52.329 WARNING (MainThread) [homeassistant.components.media_player] Updating webostv media_player took longer than the scheduled update interval 0:00:10
2023-12-02 20:28:53.364 ERROR (MainThread) [custom_components.tapo.coordinators] Tapo exception: Returned unknown error_code: 1003  msg: No message
2023-12-02 20:28:57.512 ERROR (MainThread) [custom_components.tapo.coordinators] Tapo exception: Returned unknown error_code: 1003  msg: No message
2023-12-02 20:29:02.330 WARNING (MainThread) [homeassistant.components.media_player] Updating webostv media_player took longer than the scheduled update interval 0:00:10
2023-12-02 20:29:02.764 ERROR (MainThread) [custom_components.tapo.coordinators] Tapo exception: Returned unknown error_code: 1003  msg: No message
2023-12-02 20:29:03.642 ERROR (MainThread) [custom_components.tapo.coordinators] Tapo exception: Returned unknown error_code: 1003  msg: No message
2023-12-02 20:29:08.658 ERROR (MainThread) [custom_components.tapo.coordinators] Tapo exception: Returned unknown error_code: 1003  msg: No message
2023-12-02 20:29:12.331 WARNING (MainThread) [homeassistant.components.media_player] Updating webostv media_player took longer than the scheduled update interval 0:00:10
2023-12-02 20:29:20.355 ERROR (MainThread) [custom_components.tapo.coordinators] Tapo exception: Returned unknown error_code: 1003  msg: No message
2023-12-02 20:29:22.332 WARNING (MainThread) [homeassistant.components.media_player] Updating webostv media_player took longer than the scheduled update interval 0:00:10
2023-12-02 20:29:23.370 ERROR (MainThread) [custom_components.tapo.coordinators] Tapo exception: Returned unknown error_code: 1003  msg: No message
2023-12-02 20:29:27.527 ERROR (MainThread) [custom_components.tapo.coordinators] Tapo exception: Returned unknown error_code: 1003  msg: No message
2023-12-02 20:29:32.333 WARNING (MainThread) [homeassistant.components.media_player] Updating webostv media_player took longer than the scheduled update interval 0:00:10
2023-12-02 20:29:32.758 ERROR (MainThread) [custom_components.tapo.coordinators] Tapo exception: Returned unknown error_code: 1003  msg: No message
2023-12-02 20:29:33.641 ERROR (MainThread) [custom_components.tapo.coordinators] Tapo exception: Returned unknown error_code: 1003  msg: No message
2023-12-02 20:29:38.662 ERROR (MainThread) [custom_components.tapo.coordinators] Tapo exception: Returned unknown error_code: 1003  msg: No message
2023-12-02 20:29:42.334 WARNING (MainThread) [homeassistant.components.media_player] Updating webostv media_player took longer than the scheduled update interval 0:00:10
2023-12-02 20:29:50.355 ERROR (MainThread) [custom_components.tapo.coordinators] Tapo exception: Returned unknown error_code: 1003  msg: No message
2023-12-02 20:29:52.335 WARNING (MainThread) [homeassistant.components.media_player] Updating webostv media_player took longer than the scheduled update interval 0:00:10
2023-12-02 20:29:53.373 ERROR (MainThread) [custom_components.tapo.coordinators] Tapo exception: Returned unknown error_code: 1003  msg: No message
2023-12-02 20:29:57.512 ERROR (MainThread) [custom_components.tapo.coordinators] Tapo exception: Returned unknown error_code: 1003  msg: No message
2023-12-02 20:30:02.335 WARNING (MainThread) [homeassistant.components.media_player] Updating webostv media_player took longer than the scheduled update interval 0:00:10
2023-12-02 20:30:02.753 ERROR (MainThread) [custom_components.tapo.coordinators] Tapo exception: Returned unknown error_code: 1003  msg: No message
2023-12-02 20:30:03.642 ERROR (MainThread) [custom_components.tapo.coordinators] Tapo exception: Returned unknown error_code: 1003  msg: No message
2023-12-02 20:30:08.698 ERROR (MainThread) [custom_components.tapo.coordinators] Tapo exception: Returned unknown error_code: 1003  msg: No message
2023-12-02 20:30:12.337 WARNING (MainThread) [homeassistant.components.media_player] Updating webostv media_player took longer than the scheduled update interval 0:00:10
2023-12-02 20:30:20.347 ERROR (MainThread) [custom_components.tapo.coordinators] Tapo exception: Returned unknown error_code: 1003  msg: No message
2023-12-02 20:30:22.337 WARNING (MainThread) [homeassistant.components.media_player] Updating webostv media_player took longer than the scheduled update interval 0:00:10
2023-12-02 20:30:23.366 ERROR (MainThread) [custom_components.tapo.coordinators] Tapo exception: Returned unknown error_code: 1003  msg: No message
2023-12-02 20:30:27.521 ERROR (MainThread) [custom_components.tapo.coordinators] Tapo exception: Returned unknown error_code: 1003  msg: No message
2023-12-02 20:30:32.339 WARNING (MainThread) [homeassistant.components.media_player] Updating webostv media_player took longer than the scheduled update interval 0:00:10
2023-12-02 20:30:32.753 ERROR (MainThread) [custom_components.tapo.coordinators] Tapo exception: Returned unknown error_code: 1003  msg: No message
2023-12-02 20:30:33.635 ERROR (MainThread) [custom_components.tapo.coordinators] Tapo exception: Returned unknown error_code: 1003  msg: No message
2023-12-02 20:30:38.669 ERROR (MainThread) [custom_components.tapo.coordinators] Tapo exception: Returned unknown error_code: 1003  msg: No message
2023-12-02 20:30:42.340 WARNING (MainThread) [homeassistant.components.media_player] Updating webostv media_player took longer than the scheduled update interval 0:00:10
2023-12-02 20:30:50.348 ERROR (MainThread) [custom_components.tapo.coordinators] Tapo exception: Returned unknown error_code: 1003  msg: No message
2023-12-02 20:30:52.340 WARNING (MainThread) [homeassistant.components.media_player] Updating webostv media_player took longer than the scheduled update interval 0:00:10
2023-12-02 20:30:53.364 ERROR (MainThread) [custom_components.tapo.coordinators] Tapo exception: Returned unknown error_code: 1003  msg: No message
2023-12-02 20:30:57.511 ERROR (MainThread) [custom_components.tapo.coordinators] Tapo exception: Returned unknown error_code: 1003  msg: No message
2023-12-02 20:31:02.342 WARNING (MainThread) [homeassistant.components.media_player] Updating webostv media_player took longer than the scheduled update interval 0:00:10
2023-12-02 20:31:02.762 ERROR (MainThread) [custom_components.tapo.coordinators] Tapo exception: Returned unknown error_code: 1003  msg: No message
2023-12-02 20:31:03.634 ERROR (MainThread) [custom_components.tapo.coordinators] Tapo exception: Returned unknown error_code: 1003  msg: No message
2023-12-02 20:31:08.698 ERROR (MainThread) [custom_components.tapo.coordinators] Tapo exception: Returned unknown error_code: 1003  msg: No message
2023-12-02 20:31:12.344 WARNING (MainThread) [homeassistant.components.media_player] Updating webostv media_player took longer than the scheduled update interval 0:00:10
2023-12-02 20:31:20.358 ERROR (MainThread) [custom_components.tapo.coordinators] Tapo exception: Returned unknown error_code: 1003  msg: No message
2023-12-02 20:31:22.346 WARNING (MainThread) [homeassistant.components.media_player] Updating webostv media_player took longer than the scheduled update interval 0:00:10
2023-12-02 20:31:23.368 ERROR (MainThread) [custom_components.tapo.coordinators] Tapo exception: Returned unknown error_code: 1003  msg: No message
2023-12-02 20:31:27.525 ERROR (MainThread) [custom_components.tapo.coordinators] Tapo exception: Returned unknown error_code: 1003  msg: No message
2023-12-02 20:31:32.347 WARNING (MainThread) [homeassistant.components.media_player] Updating webostv media_player took longer than the scheduled update interval 0:00:10
2023-12-02 20:31:32.752 ERROR (MainThread) [custom_components.tapo.coordinators] Tapo exception: Returned unknown error_code: 1003  msg: No message
2023-12-02 20:31:33.644 ERROR (MainThread) [custom_components.tapo.coordinators] Tapo exception: Returned unknown error_code: 1003  msg: No message
2023-12-02 20:31:38.658 ERROR (MainThread) [custom_components.tapo.coordinators] Tapo exception: Returned unknown error_code: 1003  msg: No message
2023-12-02 20:31:42.348 WARNING (MainThread) [homeassistant.components.media_player] Updating webostv media_player took longer than the scheduled update interval 0:00:10
2023-12-02 20:31:50.357 ERROR (MainThread) [custom_components.tapo.coordinators] Tapo exception: Returned unknown error_code: 1003  msg: No message
2023-12-02 20:31:52.349 WARNING (MainThread) [homeassistant.components.media_player] Updating webostv media_player took longer than the scheduled update interval 0:00:10
2023-12-02 20:31:53.363 ERROR (MainThread) [custom_components.tapo.coordinators] Tapo exception: Returned unknown error_code: 1003  msg: No message
2023-12-02 20:31:57.513 ERROR (MainThread) [custom_components.tapo.coordinators] Tapo exception: Returned unknown error_code: 1003  msg: No message
2023-12-02 20:32:02.350 WARNING (MainThread) [homeassistant.components.media_player] Updating webostv media_player took longer than the scheduled update interval 0:00:10
2023-12-02 20:32:02.768 ERROR (MainThread) [custom_components.tapo.coordinators] Tapo exception: Returned unknown error_code: 1003  msg: No message
2023-12-02 20:32:03.640 ERROR (MainThread) [custom_components.tapo.coordinators] Tapo exception: Returned unknown error_code: 1003  msg: No message
2023-12-02 20:32:08.703 ERROR (MainThread) [custom_components.tapo.coordinators] Tapo exception: Returned unknown error_code: 1003  msg: No message
2023-12-02 20:32:12.352 WARNING (MainThread) [homeassistant.components.media_player] Updating webostv media_player took longer than the scheduled update interval 0:00:10
2023-12-02 20:32:20.360 ERROR (MainThread) [custom_components.tapo.coordinators] Tapo exception: Returned unknown error_code: 1003  msg: No message
2023-12-02 20:32:22.354 WARNING (MainThread) [homeassistant.components.media_player] Updating webostv media_player took longer than the scheduled update interval 0:00:10
2023-12-02 20:32:23.364 ERROR (MainThread) [custom_components.tapo.coordinators] Tapo exception: Returned unknown error_code: 1003  msg: No message
2023-12-02 20:32:27.534 ERROR (MainThread) [custom_components.tapo.coordinators] Tapo exception: Returned unknown error_code: 1003  msg: No message
2023-12-02 20:32:32.355 WARNING (MainThread) [homeassistant.components.media_player] Updating webostv media_player took longer than the scheduled update interval 0:00:10
2023-12-02 20:32:32.752 ERROR (MainThread) [custom_components.tapo.coordinators] Tapo exception: Returned unknown error_code: 1003  msg: No message
2023-12-02 20:32:33.632 ERROR (MainThread) [custom_components.tapo.coordinators] Tapo exception: Returned unknown error_code: 1003  msg: No message
2023-12-02 20:32:38.657 ERROR (MainThread) [custom_components.tapo.coordinators] Tapo exception: Returned unknown error_code: 1003  msg: No message
2023-12-02 20:32:42.356 WARNING (MainThread) [homeassistant.components.media_player] Updating webostv media_player took longer than the scheduled update interval 0:00:10
2023-12-02 20:32:50.363 ERROR (MainThread) [custom_components.tapo.coordinators] Tapo exception: Returned unknown error_code: 1003  msg: No message
2023-12-02 20:32:52.357 WARNING (MainThread) [homeassistant.components.media_player] Updating webostv media_player took longer than the scheduled update interval 0:00:10
2023-12-02 20:32:53.363 ERROR (MainThread) [custom_components.tapo.coordinators] Tapo exception: Returned unknown error_code: 1003  msg: No message
2023-12-02 20:32:57.528 ERROR (MainThread) [custom_components.tapo.coordinators] Tapo exception: Returned unknown error_code: 1003  msg: No message
2023-12-02 20:33:02.358 WARNING (MainThread) [homeassistant.components.media_player] Updating webostv media_player took longer than the scheduled update interval 0:00:10
2023-12-02 20:33:02.755 ERROR (MainThread) [custom_components.tapo.coordinators] Tapo exception: Returned unknown error_code: 1003  msg: No message
2023-12-02 20:33:03.633 ERROR (MainThread) [custom_components.tapo.coordinators] Tapo exception: Returned unknown error_code: 1003  msg: No message
2023-12-02 20:33:08.696 ERROR (MainThread) [custom_components.tapo.coordinators] Tapo exception: Returned unknown error_code: 1003  msg: No message
2023-12-02 20:33:12.359 WARNING (MainThread) [homeassistant.components.media_player] Updating webostv media_player took longer than the scheduled update interval 0:00:10
2023-12-02 20:33:20.358 ERROR (MainThread) [custom_components.tapo.coordinators] Tapo exception: Returned unknown error_code: 1003  msg: No message
2023-12-02 20:33:22.360 WARNING (MainThread) [homeassistant.components.media_player] Updating webostv media_player took longer than the scheduled update interval 0:00:10
2023-12-02 20:33:23.365 ERROR (MainThread) [custom_components.tapo.coordinators] Tapo exception: Returned unknown error_code: 1003  msg: No message
2023-12-02 20:33:27.518 ERROR (MainThread) [custom_components.tapo.coordinators] Tapo exception: Returned unknown error_code: 1003  msg: No message
2023-12-02 20:33:32.361 WARNING (MainThread) [homeassistant.components.media_player] Updating webostv media_player took longer than the scheduled update interval 0:00:10
2023-12-02 20:33:32.761 ERROR (MainThread) [custom_components.tapo.coordinators] Tapo exception: Returned unknown error_code: 1003  msg: No message
2023-12-02 20:33:33.637 ERROR (MainThread) [custom_components.tapo.coordinators] Tapo exception: Returned unknown error_code: 1003  msg: No message
2023-12-02 20:33:38.662 ERROR (MainThread) [custom_components.tapo.coordinators] Tapo exception: Returned unknown error_code: 1003  msg: No message
2023-12-02 20:33:42.361 WARNING (MainThread) [homeassistant.components.media_player] Updating webostv media_player took longer than the scheduled update interval 0:00:10
2023-12-02 20:33:50.352 ERROR (MainThread) [custom_components.tapo.coordinators] Tapo exception: Returned unknown error_code: 1003  msg: No message
2023-12-02 20:33:52.362 WARNING (MainThread) [homeassistant.components.media_player] Updating webostv media_player took longer than the scheduled update interval 0:00:10
2023-12-02 20:33:53.367 ERROR (MainThread) [custom_components.tapo.coordinators] Tapo exception: Returned unknown error_code: 1003  msg: No message
2023-12-02 20:33:57.520 ERROR (MainThread) [custom_components.tapo.coordinators] Tapo exception: Returned unknown error_code: 1003  msg: No message
2023-12-02 20:34:02.363 WARNING (MainThread) [homeassistant.components.media_player] Updating webostv media_player took longer than the scheduled update interval 0:00:10
2023-12-02 20:34:02.763 ERROR (MainThread) [custom_components.tapo.coordinators] Tapo exception: Returned unknown error_code: 1003  msg: No message
2023-12-02 20:34:03.634 ERROR (MainThread) [custom_components.tapo.coordinators] Tapo exception: Returned unknown error_code: 1003  msg: No message
2023-12-02 20:34:08.698 ERROR (MainThread) [custom_components.tapo.coordinators] Tapo exception: Returned unknown error_code: 1003  msg: No message
2023-12-02 20:34:12.364 WARNING (MainThread) [homeassistant.components.media_player] Updating webostv media_player took longer than the scheduled update interval 0:00:10
2023-12-02 20:34:20.357 ERROR (MainThread) [custom_components.tapo.coordinators] Tapo exception: Returned unknown error_code: 1003  msg: No message
2023-12-02 20:34:22.365 WARNING (MainThread) [homeassistant.components.media_player] Updating webostv media_player took longer than the scheduled update interval 0:00:10
2023-12-02 20:34:23.382 ERROR (MainThread) [custom_components.tapo.coordinators] Tapo exception: Returned unknown error_code: 1003  msg: No message
2023-12-02 20:34:27.510 ERROR (MainThread) [custom_components.tapo.coordinators] Tapo exception: Returned unknown error_code: 1003  msg: No message
2023-12-02 20:34:32.366 WARNING (MainThread) [homeassistant.components.media_player] Updating webostv media_player took longer than the scheduled update interval 0:00:10
2023-12-02 20:34:32.753 ERROR (MainThread) [custom_components.tapo.coordinators] Tapo exception: Returned unknown error_code: 1003  msg: No message
2023-12-02 20:34:33.633 ERROR (MainThread) [custom_components.tapo.coordinators] Tapo exception: Returned unknown error_code: 1003  msg: No message
2023-12-02 20:34:38.657 ERROR (MainThread) [custom_components.tapo.coordinators] Tapo exception: Returned unknown error_code: 1003  msg: No message
2023-12-02 20:34:42.368 WARNING (MainThread) [homeassistant.components.media_player] Updating webostv media_player took longer than the scheduled update interval 0:00:10
2023-12-02 20:34:50.351 ERROR (MainThread) [custom_components.tapo.coordinators] Tapo exception: Returned unknown error_code: 1003  msg: No message
2023-12-02 20:34:52.369 WARNING (MainThread) [homeassistant.components.media_player] Updating webostv media_player took longer than the scheduled update interval 0:00:10
2023-12-02 20:34:53.372 ERROR (MainThread) [custom_components.tapo.coordinators] Tapo exception: Returned unknown error_code: 1003  msg: No message
2023-12-02 20:34:57.517 ERROR (MainThread) [custom_components.tapo.coordinators] Tapo exception: Returned unknown error_code: 1003  msg: No message
2023-12-02 20:35:02.370 WARNING (MainThread) [homeassistant.components.media_player] Updating webostv media_player took longer than the scheduled update interval 0:00:10
2023-12-02 20:35:02.762 ERROR (MainThread) [custom_components.tapo.coordinators] Tapo exception: Returned unknown error_code: 1003  msg: No message
2023-12-02 20:35:03.633 ERROR (MainThread) [custom_components.tapo.coordinators] Tapo exception: Returned unknown error_code: 1003  msg: No message
2023-12-02 20:35:08.703 ERROR (MainThread) [custom_components.tapo.coordinators] Tapo exception: Returned unknown error_code: 1003  msg: No message
2023-12-02 20:35:12.371 WARNING (MainThread) [homeassistant.components.media_player] Updating webostv media_player took longer than the scheduled update interval 0:00:10
2023-12-02 20:35:20.348 ERROR (MainThread) [custom_components.tapo.coordinators] Tapo exception: Returned unknown error_code: 1003  msg: No message
2023-12-02 20:35:22.371 WARNING (MainThread) [homeassistant.components.media_player] Updating webostv media_player took longer than the scheduled update interval 0:00:10
2023-12-02 20:35:23.374 ERROR (MainThread) [custom_components.tapo.coordinators] Tapo exception: Returned unknown error_code: 1003  msg: No message
2023-12-02 20:35:27.512 ERROR (MainThread) [custom_components.tapo.coordinators] Tapo exception: Returned unknown error_code: 1003  msg: No message
2023-12-02 20:35:32.372 WARNING (MainThread) [homeassistant.components.media_player] Updating webostv media_player took longer than the scheduled update interval 0:00:10
2023-12-02 20:35:32.755 ERROR (MainThread) [custom_components.tapo.coordinators] Tapo exception: Returned unknown error_code: 1003  msg: No message
2023-12-02 20:35:33.653 ERROR (MainThread) [custom_components.tapo.coordinators] Tapo exception: Returned unknown error_code: 1003  msg: No message
2023-12-02 20:35:38.660 ERROR (MainThread) [custom_components.tapo.coordinators] Tapo exception: Returned unknown error_code: 1003  msg: No message
2023-12-02 20:35:42.373 WARNING (MainThread) [homeassistant.components.media_player] Updating webostv media_player took longer than the scheduled update interval 0:00:10
2023-12-02 20:35:50.357 ERROR (MainThread) [custom_components.tapo.coordinators] Tapo exception: Returned unknown error_code: 1003  msg: No message
2023-12-02 20:35:52.375 WARNING (MainThread) [homeassistant.components.media_player] Updating webostv media_player took longer than the scheduled update interval 0:00:10
2023-12-02 20:35:53.365 ERROR (MainThread) [custom_components.tapo.coordinators] Tapo exception: Returned unknown error_code: 1003  msg: No message
2023-12-02 20:35:57.520 ERROR (MainThread) [custom_components.tapo.coordinators] Tapo exception: Returned unknown error_code: 1003  msg: No message
2023-12-02 20:36:02.375 WARNING (MainThread) [homeassistant.components.media_player] Updating webostv media_player took longer than the scheduled update interval 0:00:10
2023-12-02 20:36:02.754 ERROR (MainThread) [custom_components.tapo.coordinators] Tapo exception: Returned unknown error_code: 1003  msg: No message
2023-12-02 20:36:03.633 ERROR (MainThread) [custom_components.tapo.coordinators] Tapo exception: Returned unknown error_code: 1003  msg: No message
2023-12-02 20:36:08.689 ERROR (MainThread) [custom_components.tapo.coordinators] Tapo exception: Returned unknown error_code: 1003  msg: No message
2023-12-02 20:36:12.376 WARNING (MainThread) [homeassistant.components.media_player] Updating webostv media_player took longer than the scheduled update interval 0:00:10
2023-12-02 20:36:20.356 ERROR (MainThread) [custom_components.tapo.coordinators] Tapo exception: Returned unknown error_code: 1003  msg: No message
2023-12-02 20:36:22.377 WARNING (MainThread) [homeassistant.components.media_player] Updating webostv media_player took longer than the scheduled update interval 0:00:10
2023-12-02 20:36:23.371 ERROR (MainThread) [custom_components.tapo.coordinators] Tapo exception: Returned unknown error_code: 1003  msg: No message
2023-12-02 20:36:27.511 ERROR (MainThread) [custom_components.tapo.coordinators] Tapo exception: Returned unknown error_code: 1003  msg: No message
2023-12-02 20:36:32.378 WARNING (MainThread) [homeassistant.components.media_player] Updating webostv media_player took longer than the scheduled update interval 0:00:10
2023-12-02 20:36:32.753 ERROR (MainThread) [custom_components.tapo.coordinators] Tapo exception: Returned unknown error_code: 1003  msg: No message
2023-12-02 20:36:33.642 ERROR (MainThread) [custom_components.tapo.coordinators] Tapo exception: Returned unknown error_code: 1003  msg: No message
2023-12-02 20:36:38.658 ERROR (MainThread) [custom_components.tapo.coordinators] Tapo exception: Returned unknown error_code: 1003  msg: No message
2023-12-02 20:36:42.378 WARNING (MainThread) [homeassistant.components.media_player] Updating webostv media_player took longer than the scheduled update interval 0:00:10
2023-12-02 20:36:50.350 ERROR (MainThread) [custom_components.tapo.coordinators] Tapo exception: Returned unknown error_code: 1003  msg: No message
2023-12-02 20:36:52.379 WARNING (MainThread) [homeassistant.components.media_player] Updating webostv media_player took longer than the scheduled update interval 0:00:10
2023-12-02 20:36:53.364 ERROR (MainThread) [custom_components.tapo.coordinators] Tapo exception: Returned unknown error_code: 1003  msg: No message
2023-12-02 20:36:57.515 ERROR (MainThread) [custom_components.tapo.coordinators] Tapo exception: Returned unknown error_code: 1003  msg: No message
2023-12-02 20:37:02.380 WARNING (MainThread) [homeassistant.components.media_player] Updating webostv media_player took longer than the scheduled update interval 0:00:10
2023-12-02 20:37:02.762 ERROR (MainThread) [custom_components.tapo.coordinators] Tapo exception: Returned unknown error_code: 1003  msg: No message
2023-12-02 20:37:03.633 ERROR (MainThread) [custom_components.tapo.coordinators] Tapo exception: Returned unknown error_code: 1003  msg: No message
2023-12-02 20:37:08.707 ERROR (MainThread) [custom_components.tapo.coordinators] Tapo exception: Returned unknown error_code: 1003  msg: No message
2023-12-02 20:37:12.383 WARNING (MainThread) [homeassistant.components.media_player] Updating webostv media_player took longer than the scheduled update interval 0:00:10
2023-12-02 20:37:20.347 ERROR (MainThread) [custom_components.tapo.coordinators] Tapo exception: Returned unknown error_code: 1003  msg: No message
2023-12-02 20:37:22.384 WARNING (MainThread) [homeassistant.components.media_player] Updating webostv media_player took longer than the scheduled update interval 0:00:10
2023-12-02 20:37:23.374 ERROR (MainThread) [custom_components.tapo.coordinators] Tapo exception: Returned unknown error_code: 1003  msg: No message
2023-12-02 20:37:27.514 ERROR (MainThread) [custom_components.tapo.coordinators] Tapo exception: Returned unknown error_code: 1003  msg: No message
2023-12-02 20:37:32.386 WARNING (MainThread) [homeassistant.components.media_player] Updating webostv media_player took longer than the scheduled update interval 0:00:10
2023-12-02 20:37:32.754 ERROR (MainThread) [custom_components.tapo.coordinators] Tapo exception: Returned unknown error_code: 1003  msg: No message
2023-12-02 20:37:33.634 ERROR (MainThread) [custom_components.tapo.coordinators] Tapo exception: Returned unknown error_code: 1003  msg: No message
2023-12-02 20:37:38.668 ERROR (MainThread) [custom_components.tapo.coordinators] Tapo exception: Returned unknown error_code: 1003  msg: No message
2023-12-02 20:37:42.386 WARNING (MainThread) [homeassistant.components.media_player] Updating webostv media_player took longer than the scheduled update interval 0:00:10
2023-12-02 20:37:50.361 ERROR (MainThread) [custom_components.tapo.coordinators] Tapo exception: Returned unknown error_code: 1003  msg: No message
2023-12-02 20:37:52.386 WARNING (MainThread) [homeassistant.components.media_player] Updating webostv media_player took longer than the scheduled update interval 0:00:10
2023-12-02 20:37:53.364 ERROR (MainThread) [custom_components.tapo.coordinators] Tapo exception: Returned unknown error_code: 1003  msg: No message
2023-12-02 20:37:57.519 ERROR (MainThread) [custom_components.tapo.coordinators] Tapo exception: Returned unknown error_code: 1003  msg: No message
2023-12-02 20:38:02.387 WARNING (MainThread) [homeassistant.components.media_player] Updating webostv media_player took longer than the scheduled update interval 0:00:10
2023-12-02 20:38:02.771 ERROR (MainThread) [custom_components.tapo.coordinators] Tapo exception: Returned unknown error_code: 1003  msg: No message
2023-12-02 20:38:03.634 ERROR (MainThread) [custom_components.tapo.coordinators] Tapo exception: Returned unknown error_code: 1003  msg: No message
2023-12-02 20:38:08.664 ERROR (MainThread) [custom_components.tapo.coordinators] Tapo exception: Returned unknown error_code: 1003  msg: No message
2023-12-02 20:38:12.388 WARNING (MainThread) [homeassistant.components.media_player] Updating webostv media_player took longer than the scheduled update interval 0:00:10
2023-12-02 20:38:20.346 ERROR (MainThread) [custom_components.tapo.coordinators] Tapo exception: Returned unknown error_code: 1003  msg: No message
2023-12-02 20:38:22.389 WARNING (MainThread) [homeassistant.components.media_player] Updating webostv media_player took longer than the scheduled update interval 0:00:10
2023-12-02 20:38:23.364 ERROR (MainThread) [custom_components.tapo.coordinators] Tapo exception: Returned unknown error_code: 1003  msg: No message
2023-12-02 20:38:27.514 ERROR (MainThread) [custom_components.tapo.coordinators] Tapo exception: Returned unknown error_code: 1003  msg: No message
2023-12-02 20:38:32.389 WARNING (MainThread) [homeassistant.components.media_player] Updating webostv media_player took longer than the scheduled update interval 0:00:10
2023-12-02 20:38:32.761 ERROR (MainThread) [custom_components.tapo.coordinators] Tapo exception: Returned unknown error_code: 1003  msg: No message
2023-12-02 20:38:33.641 ERROR (MainThread) [custom_components.tapo.coordinators] Tapo exception: Returned unknown error_code: 1003  msg: No message
2023-12-02 20:38:38.658 ERROR (MainThread) [custom_components.tapo.coordinators] Tapo exception: Returned unknown error_code: 1003  msg: No message
2023-12-02 20:38:42.391 WARNING (MainThread) [homeassistant.components.media_player] Updating webostv media_player took longer than the scheduled update interval 0:00:10
2023-12-02 20:38:50.352 ERROR (MainThread) [custom_components.tapo.coordinators] Tapo exception: Returned unknown error_code: 1003  msg: No message
2023-12-02 20:38:52.393 WARNING (MainThread) [homeassistant.components.media_player] Updating webostv media_player took longer than the scheduled update interval 0:00:10
2023-12-02 20:38:53.405 ERROR (MainThread) [custom_components.tapo.coordinators] Tapo exception: Returned unknown error_code: 1003  msg: No message
2023-12-02 20:38:57.520 ERROR (MainThread) [custom_components.tapo.coordinators] Tapo exception: Returned unknown error_code: 1003  msg: No message
2023-12-02 20:39:02.393 WARNING (MainThread) [homeassistant.components.media_player] Updating webostv media_player took longer than the scheduled update interval 0:00:10
2023-12-02 20:39:02.753 ERROR (MainThread) [custom_components.tapo.coordinators] Tapo exception: Returned unknown error_code: 1003  msg: No message
2023-12-02 20:39:03.631 ERROR (MainThread) [custom_components.tapo.coordinators] Tapo exception: Returned unknown error_code: 1003  msg: No message
2023-12-02 20:39:08.656 ERROR (MainThread) [custom_components.tapo.coordinators] Tapo exception: Returned unknown error_code: 1003  msg: No message
2023-12-02 20:39:12.394 WARNING (MainThread) [homeassistant.components.media_player] Updating webostv media_player took longer than the scheduled update interval 0:00:10
2023-12-02 20:39:20.359 ERROR (MainThread) [custom_components.tapo.coordinators] Tapo exception: Returned unknown error_code: 1003  msg: No message
2023-12-02 20:39:22.395 WARNING (MainThread) [homeassistant.components.media_player] Updating webostv media_player took longer than the scheduled update interval 0:00:10
2023-12-02 20:39:23.378 ERROR (MainThread) [custom_components.tapo.coordinators] Tapo exception: Returned unknown error_code: 1003  msg: No message
2023-12-02 20:39:27.511 ERROR (MainThread) [custom_components.tapo.coordinators] Tapo exception: Returned unknown error_code: 1003  msg: No message
2023-12-02 20:39:32.396 WARNING (MainThread) [homeassistant.components.media_player] Updating webostv media_player took longer than the scheduled update interval 0:00:10
2023-12-02 20:39:32.753 ERROR (MainThread) [custom_components.tapo.coordinators] Tapo exception: Returned unknown error_code: 1003  msg: No message
2023-12-02 20:39:33.642 ERROR (MainThread) [custom_components.tapo.coordinators] Tapo exception: Returned unknown error_code: 1003  msg: No message
2023-12-02 20:39:38.674 ERROR (MainThread) [custom_components.tapo.coordinators] Tapo exception: Returned unknown error_code: 1003  msg: No message
2023-12-02 20:39:42.396 WARNING (MainThread) [homeassistant.components.media_player] Updating webostv media_player took longer than the scheduled update interval 0:00:10
2023-12-02 20:39:50.348 ERROR (MainThread) [custom_components.tapo.coordinators] Tapo exception: Returned unknown error_code: 1003  msg: No message
2023-12-02 20:39:52.397 WARNING (MainThread) [homeassistant.components.media_player] Updating webostv media_player took longer than the scheduled update interval 0:00:10
2023-12-02 20:39:53.364 ERROR (MainThread) [custom_components.tapo.coordinators] Tapo exception: Returned unknown error_code: 1003  msg: No message
2023-12-02 20:39:57.512 ERROR (MainThread) [custom_components.tapo.coordinators] Tapo exception: Returned unknown error_code: 1003  msg: No message
2023-12-02 20:40:02.397 WARNING (MainThread) [homeassistant.components.media_player] Updating webostv media_player took longer than the scheduled update interval 0:00:10
2023-12-02 20:40:02.755 ERROR (MainThread) [custom_components.tapo.coordinators] Tapo exception: Returned unknown error_code: 1003  msg: No message
2023-12-02 20:40:03.634 ERROR (MainThread) [custom_components.tapo.coordinators] Tapo exception: Returned unknown error_code: 1003  msg: No message
2023-12-02 20:40:08.691 ERROR (MainThread) [custom_components.tapo.coordinators] Tapo exception: Returned unknown error_code: 1003  msg: No message
2023-12-02 20:40:12.400 WARNING (MainThread) [homeassistant.components.media_player] Updating webostv media_player took longer than the scheduled update interval 0:00:10
2023-12-02 20:40:20.347 ERROR (MainThread) [custom_components.tapo.coordinators] Tapo exception: Returned unknown error_code: 1003  msg: No message
2023-12-02 20:40:21.600 DEBUG (MainThread) [custom_components.tapo.coordinators] Finished fetching tapo data in 0.034 seconds (success: True)
2023-12-02 20:40:21.643 DEBUG (MainThread) [custom_components.tapo.coordinators] Finished fetching tapo data in 0.120 seconds (success: True)
2023-12-02 20:40:22.400 WARNING (MainThread) [homeassistant.components.media_player] Updating webostv media_player took longer than the scheduled update interval 0:00:10
2023-12-02 20:40:23.373 ERROR (MainThread) [custom_components.tapo.coordinators] Tapo exception: Returned unknown error_code: 1003  msg: No message
2023-12-02 20:40:23.373 DEBUG (MainThread) [custom_components.tapo.coordinators] Finished fetching tapo data in 0.031 seconds (success: False)
2023-12-02 20:40:27.512 ERROR (MainThread) [custom_components.tapo.coordinators] Tapo exception: Returned unknown error_code: 1003  msg: No message
2023-12-02 20:40:27.512 DEBUG (MainThread) [custom_components.tapo.coordinators] Finished fetching tapo data in 0.023 seconds (success: False)
2023-12-02 20:40:30.011 DEBUG (MainThread) [custom_components.tapo.coordinators] Finished fetching tapo data in 0.154 seconds (success: True)
2023-12-02 20:40:30.502 DEBUG (MainThread) [custom_components.tapo.coordinators] Finished fetching tapo data in 0.043 seconds (success: True)
2023-12-02 20:40:32.401 WARNING (MainThread) [homeassistant.components.media_player] Updating webostv media_player took longer than the scheduled update interval 0:00:10
2023-12-02 20:40:32.759 ERROR (MainThread) [custom_components.tapo.coordinators] Tapo exception: Returned unknown error_code: 1003  msg: No message
2023-12-02 20:40:32.759 DEBUG (MainThread) [custom_components.tapo.coordinators] Finished fetching tapo data in 0.027 seconds (success: False)
2023-12-02 20:40:32.791 DEBUG (MainThread) [custom_components.tapo.coordinators] Finished fetching tapo data in 0.159 seconds (success: True)
2023-12-02 20:40:33.633 ERROR (MainThread) [custom_components.tapo.coordinators] Tapo exception: Returned unknown error_code: 1003  msg: No message
2023-12-02 20:40:33.633 DEBUG (MainThread) [custom_components.tapo.coordinators] Finished fetching tapo data in 0.022 seconds (success: False)
2023-12-02 20:40:33.727 DEBUG (MainThread) [custom_components.tapo.coordinators] Finished fetching tapo data in 0.038 seconds (success: True)
2023-12-02 20:40:38.634 DEBUG (MainThread) [custom_components.tapo.coordinators] Finished fetching tapo data in 0.133 seconds (success: True)
2023-12-02 20:40:38.662 ERROR (MainThread) [custom_components.tapo.coordinators] Tapo exception: Returned unknown error_code: 1003  msg: No message
2023-12-02 20:40:38.662 DEBUG (MainThread) [custom_components.tapo.coordinators] Finished fetching tapo data in 0.027 seconds (success: False)
2023-12-02 20:40:38.897 DEBUG (MainThread) [custom_components.tapo.coordinators] Finished fetching tapo data in 0.533 seconds (success: True)
2023-12-02 20:40:42.404 WARNING (MainThread) [homeassistant.components.media_player] Updating webostv media_player took longer than the scheduled update interval 0:00:10
2023-12-02 20:40:42.614 DEBUG (MainThread) [custom_components.tapo.coordinators] Finished fetching tapo data in 0.154 seconds (success: True)
2023-12-02 20:40:48.452 DEBUG (MainThread) [custom_components.tapo.coordinators] Finished fetching tapo data in 0.069 seconds (success: True)
2023-12-02 20:40:50.356 ERROR (MainThread) [custom_components.tapo.coordinators] Tapo exception: Returned unknown error_code: 1003  msg: No message
2023-12-02 20:40:50.357 DEBUG (MainThread) [custom_components.tapo.coordinators] Finished fetching tapo data in 0.033 seconds (success: False)
2023-12-02 20:40:51.601 DEBUG (MainThread) [custom_components.tapo.coordinators] Finished fetching tapo data in 0.036 seconds (success: True)
2023-12-02 20:40:51.654 DEBUG (MainThread) [custom_components.tapo.coordinators] Finished fetching tapo data in 0.131 seconds (success: True)
2023-12-02 20:40:52.405 WARNING (MainThread) [homeassistant.components.media_player] Updating webostv media_player took longer than the scheduled update interval 0:00:10
2023-12-02 20:40:53.375 ERROR (MainThread) [custom_components.tapo.coordinators] Tapo exception: Returned unknown error_code: 1003  msg: No message
2023-12-02 20:40:53.375 DEBUG (MainThread) [custom_components.tapo.coordinators] Finished fetching tapo data in 0.032 seconds (success: False)
2023-12-02 20:40:57.523 ERROR (MainThread) [custom_components.tapo.coordinators] Tapo exception: Returned unknown error_code: 1003  msg: No message
2023-12-02 20:40:57.523 DEBUG (MainThread) [custom_components.tapo.coordinators] Finished fetching tapo data in 0.035 seconds (success: False)
2023-12-02 20:40:59.996 DEBUG (MainThread) [custom_components.tapo.coordinators] Finished fetching tapo data in 0.139 seconds (success: True)
2023-12-02 20:41:00.505 DEBUG (MainThread) [custom_components.tapo.coordinators] Finished fetching tapo data in 0.045 seconds (success: True)
2023-12-02 20:41:02.406 WARNING (MainThread) [homeassistant.components.media_player] Updating webostv media_player took longer than the scheduled update interval 0:00:10
2023-12-02 20:41:02.755 ERROR (MainThread) [custom_components.tapo.coordinators] Tapo exception: Returned unknown error_code: 1003  msg: No message
2023-12-02 20:41:02.756 DEBUG (MainThread) [custom_components.tapo.coordinators] Finished fetching tapo data in 0.024 seconds (success: False)
2023-12-02 20:41:02.773 DEBUG (MainThread) [custom_components.tapo.coordinators] Finished fetching tapo data in 0.142 seconds (success: True)
2023-12-02 20:41:03.633 ERROR (MainThread) [custom_components.tapo.coordinators] Tapo exception: Returned unknown error_code: 1003  msg: No message
2023-12-02 20:41:03.633 DEBUG (MainThread) [custom_components.tapo.coordinators] Finished fetching tapo data in 0.022 seconds (success: False)
2023-12-02 20:41:03.722 DEBUG (MainThread) [custom_components.tapo.coordinators] Finished fetching tapo data in 0.032 seconds (success: True)
2023-12-02 20:41:08.689 DEBUG (MainThread) [custom_components.tapo.coordinators] Finished fetching tapo data in 0.153 seconds (success: True)
2023-12-02 20:41:08.696 ERROR (MainThread) [custom_components.tapo.coordinators] Tapo exception: Returned unknown error_code: 1003  msg: No message
2023-12-02 20:41:08.696 DEBUG (MainThread) [custom_components.tapo.coordinators] Finished fetching tapo data in 0.062 seconds (success: False)
2023-12-02 20:41:08.833 DEBUG (MainThread) [custom_components.tapo.coordinators] Finished fetching tapo data in 0.468 seconds (success: True)
2023-12-02 20:41:12.408 WARNING (MainThread) [homeassistant.components.media_player] Updating webostv media_player took longer than the scheduled update interval 0:00:10
2023-12-02 20:41:12.607 DEBUG (MainThread) [custom_components.tapo.coordinators] Finished fetching tapo data in 0.147 seconds (success: True)
2023-12-02 20:41:18.424 DEBUG (MainThread) [custom_components.tapo.coordinators] Finished fetching tapo data in 0.040 seconds (success: True)
2023-12-02 20:41:20.353 ERROR (MainThread) [custom_components.tapo.coordinators] Tapo exception: Returned unknown error_code: 1003  msg: No message
2023-12-02 20:41:20.353 DEBUG (MainThread) [custom_components.tapo.coordinators] Finished fetching tapo data in 0.029 seconds (success: False)
2023-12-02 20:41:21.634 DEBUG (MainThread) [custom_components.tapo.coordinators] Finished fetching tapo data in 0.058 seconds (success: True)
2023-12-02 20:41:21.683 DEBUG (MainThread) [custom_components.tapo.coordinators] Finished fetching tapo data in 0.159 seconds (success: True)
2023-12-02 20:41:22.408 WARNING (MainThread) [homeassistant.components.media_player] Updating webostv media_player took longer than the scheduled update interval 0:00:10
2023-12-02 20:41:23.371 ERROR (MainThread) [custom_components.tapo.coordinators] Tapo exception: Returned unknown error_code: 1003  msg: No message
2023-12-02 20:41:23.372 DEBUG (MainThread) [custom_components.tapo.coordinators] Finished fetching tapo data in 0.029 seconds (success: False)
2023-12-02 20:41:27.526 ERROR (MainThread) [custom_components.tapo.coordinators] Tapo exception: Returned unknown error_code: 1003  msg: No message
2023-12-02 20:41:27.526 DEBUG (MainThread) [custom_components.tapo.coordinators] Finished fetching tapo data in 0.037 seconds (success: False)
2023-12-02 20:41:29.993 DEBUG (MainThread) [custom_components.tapo.coordinators] Finished fetching tapo data in 0.135 seconds (success: True)
2023-12-02 20:41:30.494 DEBUG (MainThread) [custom_components.tapo.coordinators] Finished fetching tapo data in 0.033 seconds (success: True)
2023-12-02 20:41:32.409 WARNING (MainThread) [homeassistant.components.media_player] Updating webostv media_player took longer than the scheduled update interval 0:00:10
2023-12-02 20:41:32.762 ERROR (MainThread) [custom_components.tapo.coordinators] Tapo exception: Returned unknown error_code: 1003  msg: No message
2023-12-02 20:41:32.762 DEBUG (MainThread) [custom_components.tapo.coordinators] Finished fetching tapo data in 0.030 seconds (success: False)
2023-12-02 20:41:32.765 DEBUG (MainThread) [custom_components.tapo.coordinators] Finished fetching tapo data in 0.134 seconds (success: True)
2023-12-02 20:41:33.644 ERROR (MainThread) [custom_components.tapo.coordinators] Tapo exception: Returned unknown error_code: 1003  msg: No message
2023-12-02 20:41:33.644 DEBUG (MainThread) [custom_components.tapo.coordinators] Finished fetching tapo data in 0.033 seconds (success: False)
2023-12-02 20:41:33.720 DEBUG (MainThread) [custom_components.tapo.coordinators] Finished fetching tapo data in 0.032 seconds (success: True)
2023-12-02 20:41:38.639 DEBUG (MainThread) [custom_components.tapo.coordinators] Finished fetching tapo data in 0.138 seconds (success: True)
2023-12-02 20:41:38.662 ERROR (MainThread) [custom_components.tapo.coordinators] Tapo exception: Returned unknown error_code: 1003  msg: No message
2023-12-02 20:41:38.662 DEBUG (MainThread) [custom_components.tapo.coordinators] Finished fetching tapo data in 0.028 seconds (success: False)
2023-12-02 20:41:38.806 DEBUG (MainThread) [custom_components.tapo.coordinators] Finished fetching tapo data in 0.444 seconds (success: True)
2023-12-02 20:41:42.410 WARNING (MainThread) [homeassistant.components.media_player] Updating webostv media_player took longer than the scheduled update interval 0:00:10
2023-12-02 20:41:42.589 DEBUG (MainThread) [custom_components.tapo.coordinators] Finished fetching tapo data in 0.129 seconds (success: True)
2023-12-02 20:41:48.433 DEBUG (MainThread) [custom_components.tapo.coordinators] Finished fetching tapo data in 0.050 seconds (success: True)
2023-12-02 20:41:50.364 ERROR (MainThread) [custom_components.tapo.coordinators] Tapo exception: Returned unknown error_code: 1003  msg: No message
2023-12-02 20:41:50.364 DEBUG (MainThread) [custom_components.tapo.coordinators] Finished fetching tapo data in 0.041 seconds (success: False)
2023-12-02 20:41:51.606 DEBUG (MainThread) [custom_components.tapo.coordinators] Finished fetching tapo data in 0.040 seconds (success: True)
2023-12-02 20:41:51.660 DEBUG (MainThread) [custom_components.tapo.coordinators] Finished fetching tapo data in 0.136 seconds (success: True)
2023-12-02 20:41:52.410 WARNING (MainThread) [homeassistant.components.media_player] Updating webostv media_player took longer than the scheduled update interval 0:00:10
2023-12-02 20:41:53.398 ERROR (MainThread) [custom_components.tapo.coordinators] Tapo exception: Returned unknown error_code: 1003  msg: No message
2023-12-02 20:41:53.399 DEBUG (MainThread) [custom_components.tapo.coordinators] Finished fetching tapo data in 0.056 seconds (success: False)
2023-12-02 20:41:57.529 ERROR (MainThread) [custom_components.tapo.coordinators] Tapo exception: Returned unknown error_code: 1003  msg: No message
2023-12-02 20:41:57.529 DEBUG (MainThread) [custom_components.tapo.coordinators] Finished fetching tapo data in 0.039 seconds (success: False)
2023-12-02 20:42:00.062 DEBUG (MainThread) [custom_components.tapo.coordinators] Finished fetching tapo data in 0.187 seconds (success: True)
2023-12-02 20:42:00.504 DEBUG (MainThread) [custom_components.tapo.coordinators] Finished fetching tapo data in 0.044 seconds (success: True)
2023-12-02 20:42:02.412 WARNING (MainThread) [homeassistant.components.media_player] Updating webostv media_player took longer than the scheduled update interval 0:00:10
2023-12-02 20:42:02.756 DEBUG (MainThread) [custom_components.tapo.coordinators] Finished fetching tapo data in 0.126 seconds (success: True)
2023-12-02 20:42:02.758 ERROR (MainThread) [custom_components.tapo.coordinators] Tapo exception: Returned unknown error_code: 1003  msg: No message
2023-12-02 20:42:02.759 DEBUG (MainThread) [custom_components.tapo.coordinators] Finished fetching tapo data in 0.027 seconds (success: False)
2023-12-02 20:42:03.634 ERROR (MainThread) [custom_components.tapo.coordinators] Tapo exception: Returned unknown error_code: 1003  msg: No message
2023-12-02 20:42:03.634 DEBUG (MainThread) [custom_components.tapo.coordinators] Finished fetching tapo data in 0.022 seconds (success: False)
2023-12-02 20:42:03.728 DEBUG (MainThread) [custom_components.tapo.coordinators] Finished fetching tapo data in 0.039 seconds (success: True)
2023-12-02 20:42:08.695 DEBUG (MainThread) [custom_components.tapo.coordinators] Finished fetching tapo data in 0.159 seconds (success: True)
2023-12-02 20:42:08.698 ERROR (MainThread) [custom_components.tapo.coordinators] Tapo exception: Returned unknown error_code: 1003  msg: No message
2023-12-02 20:42:08.699 DEBUG (MainThread) [custom_components.tapo.coordinators] Finished fetching tapo data in 0.066 seconds (success: False)
2023-12-02 20:42:08.828 DEBUG (MainThread) [custom_components.tapo.coordinators] Finished fetching tapo data in 0.465 seconds (success: True)
2023-12-02 20:42:12.414 WARNING (MainThread) [homeassistant.components.media_player] Updating webostv media_player took longer than the scheduled update interval 0:00:10
2023-12-02 20:42:12.629 DEBUG (MainThread) [custom_components.tapo.coordinators] Finished fetching tapo data in 0.169 seconds (success: True)
2023-12-02 20:42:18.433 DEBUG (MainThread) [custom_components.tapo.coordinators] Finished fetching tapo data in 0.050 seconds (success: True)
2023-12-02 20:42:20.364 ERROR (MainThread) [custom_components.tapo.coordinators] Tapo exception: Returned unknown error_code: 1003  msg: No message
2023-12-02 20:42:20.364 DEBUG (MainThread) [custom_components.tapo.coordinators] Finished fetching tapo data in 0.041 seconds (success: False)
2023-12-02 20:42:21.606 DEBUG (MainThread) [custom_components.tapo.coordinators] Finished fetching tapo data in 0.041 seconds (success: True)
2023-12-02 20:42:21.670 DEBUG (MainThread) [custom_components.tapo.coordinators] Finished fetching tapo data in 0.147 seconds (success: True)
2023-12-02 20:42:22.416 WARNING (MainThread) [homeassistant.components.media_player] Updating webostv media_player took longer than the scheduled update interval 0:00:10
2023-12-02 20:42:23.379 ERROR (MainThread) [custom_components.tapo.coordinators] Tapo exception: Returned unknown error_code: 1003  msg: No message
2023-12-02 20:42:23.379 DEBUG (MainThread) [custom_components.tapo.coordinators] Finished fetching tapo data in 0.037 seconds (success: False)
2023-12-02 20:42:27.519 ERROR (MainThread) [custom_components.tapo.coordinators] Tapo exception: Returned unknown error_code: 1003  msg: No message
2023-12-02 20:42:27.519 DEBUG (MainThread) [custom_components.tapo.coordinators] Finished fetching tapo data in 0.031 seconds (success: False)

To Add - it has been <24 hours and more than 16,500 error messages are now present. I may have to disable this integration soon as it is generating so many errors.

I have the same issue, i had some P115 that auto updated from 1.2.3 Build 230425 Rel.142542 to 1.3.0
That broke the Integration

@pleasedtohavemetyou fyi

I will add a banner into readme


[new locale] mt: Maltese language

Months and days names, long and short format, time format for the Maltese Language

About the build error: https://github.com/rollup/rollup/issues/1587

@alesma  thank you!
@JLHwung thank you too :)


Add camera functionlity for ROS2

This pull request makes it possible to use the raspberrry pi camera on waffle_pi's in ROS2. Some items to note:

During testing, we had trouble subscribing to uncompressed image topics on the remote workstation, possibly because the bandwidth was too high over the wifi connection.  Instead, we are using the republish tool in the image_transport package to uncompress the compressed image stream on the workstation. This significantly reduces image bandwidth over wifi. The image_transport.launch.py launch file needs to be launched on the workstation.
The camera calibration yaml file in this pull request was calibrated locally.  We've tested it by localizing aruco markers, and it seems to be working correctly.  We didn't have good results using the yaml file from the main branch.

@spragunr
Thank you for your contribution.
we will merge after testing PR
Thank you.


Add dart example

Description
I've added an example for using the action within a dart repository

Motivation and Context
Faster workflows in any dart project.

How Has This Been Tested?
I've tested the same code snippet in the example in one of my projects and it ran as intended.

Screenshots (if appropriate):
Types of changes

[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)
[x] Documentation (add or update README or docs)

Checklist:

[x] My code follows the code style of this project.
[ ] My change requires a change to the documentation.
[ ] I have updated the documentation accordingly.
[x] I have read the CONTRIBUTING document.
[ ] I have added tests to cover my changes.
[x] All new and existing tests passed.

Nhan

Nhab

Trường Võ Văn Kiệt

If you use subosito/flutter-action@v2, the pub cache is in a different location:
# linux
FLUTTER_ROOT: /opt/hostedtoolcache/flutter/stable-3.10.6-x64
PUB_CACHE: /opt/hostedtoolcache/flutter/stable-3.10.6-x64/.pub-cache

# macos
FLUTTER_ROOT: /Users/runner/hostedtoolcache/flutter/stable-3.10.6-x64
PUB_CACHE: /Users/runner/hostedtoolcache/flutter/stable-3.10.6-x64/.pub-cache

# windows
FLUTTER_ROOT: C:\hostedtoolcache\windows\flutter\stable-3.10.6-x64
PUB_CACHE: C:\hostedtoolcache\windows\flutter\stable-3.10.6-x64/.pub-cache

If you use subosito/flutter-action@v2, the pub cache is in a different location:
# linux
FLUTTER_ROOT: /opt/hostedtoolcache/flutter/stable-3.10.6-x64
PUB_CACHE: /opt/hostedtoolcache/flutter/stable-3.10.6-x64/.pub-cache

# macos
FLUTTER_ROOT: /Users/runner/hostedtoolcache/flutter/stable-3.10.6-x64
PUB_CACHE: /Users/runner/hostedtoolcache/flutter/stable-3.10.6-x64/.pub-cache

# windows
FLUTTER_ROOT: C:\hostedtoolcache\windows\flutter\stable-3.10.6-x64
PUB_CACHE: C:\hostedtoolcache\windows\flutter\stable-3.10.6-x64/.pub-cache

Wouldnt that be because flutter packages its own version of the dart sdk wouldnt it. That would definitely differ from just using dart. Not sure wether that needs to be specified or not.

Wouldnt that be because flutter packages its own version of the dart sdk wouldnt it.

It's just an environment variable set by flutter-action (see the code snippet).

Not sure wether that needs to be specified or not.

Since flutter and subosito/flutter-action are quite popular, maybe a separate Flutter section should be added alongside the Dart section? I feel like just having the dart section would cause some confusion

Since flutter and subosito/flutter-action are quite popular, maybe a separate Flutter section should be added alongside the Dart section? I feel like just having the dart section would cause some confusion

yes, i also feel like there should be separate section for flutter but idk if this is allowed. if one of the maintainers replied maybe something could be done.


Add support for generating specs2 Pact with DslPart

I hope I'm using it right 😄

Thanks for the PR! Looks good to me. I might modify it slightly, because you're change is converting the matchers to Scala collections, and then calling the previous method which converts it back again.

Oh, good point. Thanks.


AppiumLocalService starts duplicate application windows

Hello,
I am testing a Windows application using AppiumLocalService.
The problem is that Appium will start duplicate app windows which will cause the tests to fail.
Any idea how to remedy that?
Here is the Appium setup code:
`
{
         var appiumServiceBuilder = new AppiumServiceBuilder().UsingPort(4723).Build();
         appiumServiceBuilder.Start();

         var appiumOptions = new AppiumOptions();
         appCapabilities.AddAdditionalCapability("app", "appPath");
         appCapabilities.AddAdditionalCapability("fullReset", true);
         appCapabilities.AddAdditionalCapability("newCommandTimeout", 60);

         //This line causes duplicate app launches
         WindowsDriver<WindowsElement> session = new WindowsDriver<WindowsElement>
         (appiumServiceBuilder, appiumOptions);

}
`

You are directly passing the appium service builder. This is how it should work:
`
var appiumServiceBuilder = new AppiumServiceBuilder().UsingPort(4723).Build();
appiumServiceBuilder.Start();
     var appiumOptions = new AppiumOptions();
     appCapabilities.AddAdditionalCapability("app", "appPath");
     appCapabilities.AddAdditionalCapability("fullReset", true);
     appCapabilities.AddAdditionalCapability("newCommandTimeout", 60);

     //This line causes duplicate app launches
     WindowsDriver<WindowsElement> session = new WindowsDriver<WindowsElement>
     ("http://<IP_ADDRESS>:4723", appiumOptions);

`

I tried the suggestion like that:
WindowsDriver<WindowsElement> session = new WindowsDriver<WindowsElement>
         (new Uri("http://<IP_ADDRESS>:4723"), appiumOptions);

But I get an exception:
Message:
    OpenQA.Selenium.WebDriverException : Unexpected error. System.Net.WebException: Unable to connect to the remote server ---> System.Net.Sockets.SocketException: No connection could be made because the target machine actively refused it <IP_ADDRESS>:4723

Seems like you already have the local host with port 4723, try using some other port.

The port is being used only by Appium. At this point, this doesn't look like a solution.
Has anyone encountered the issue with the app being launched duplicate times?
I'd like to try any other suggestions.
Regards

@bonislav we keep are AppiumLocalService as a static class in our assemblyIntialization.  Consider changing the port and running a single test to test my hunch.

We tried a different port and tried moving the AppiumLocalService to a static class, the result was the same, the app would launch duplicate times for some reason.
We are using xUnit as the test framework, and have limited the threads to one.
Regards

My assumption is that because the app starts relatively slowly, there is some sort of retry mechanism within Appium that if it does not find the process it is starting it will launch it again. If this is the case is there a way to introduce a wait within the Appium start process, before it is retried?
Regards

Here is the logFile of 1 test that reproduced the issue:
AppiumTestLog-Failed-Test.txt
Regards

From the logs I can see that there is only one session created. Does not appear like a appium issue.

Can you please schedule a zoom call? if that is possible.

I could do a zoom call, but I cannot share any of the product information.
On another note, I was pointed to this Capability: "ms:waitForAppLaunch".
I set it with a value of 30 sec and it seems to be working, but I need more testing.
The downside is that it is a static wait and it will slow down the tests, whilst if it was dynamic and it could wait up to 30 seconds,
but at the same time continue if the check passes at let us say 15 seconds.
Regards


fix bug width|height = auto

when  then ![null]( =autoxauto)
after fix ![null]( =x)

Thank you very much @ggboy-shakalaka
Can you please add a testcase for this?

非常抱歉 @tivie 。我现在还不太会用github，这个 testcase 还需要你自己搞，我怕我弄错了。
感谢你的 “showdown”，给我带来和很多方便。
Can't speak English, the following is google translation
I am very sorry about @tivie. I don't really use github right now. This testcase still needs to be done by myself. I am afraid I am mistaken.
Thank you for your "showdown", which brings me a lot of convenience.

This testcase still needs to be done by myself(maybe yourself).
my english is bad.
meaning is you do that testcase,i don't do that.
bad translation


Fix bug in translation of call instruction

Code was checking caller signature instead of callee signature, leading to improper numbers of arguments in some boogie calls.

@bors-libra r=emmazzz

:pushpin: Commit 404c920 has been approved by emmazzz

:hourglass: Testing commit 404c920b1bf93d84a856efa0941b0007730e2ef5 with merge 7e74c1bb7b65a26be89ba0efbf1066ad2f6c96b4...

:sunny: Test successful - checks-circle_commit_workflow
Approved by: emmazzz
Pushing 7e74c1bb7b65a26be89ba0efbf1066ad2f6c96b4 to master...


chore(deps): update dependency @rollup/plugin-node-resolve to v15

This PR contains the following updates:

Package
Change
Age
Adoption
Passing
Confidence

@rollup/plugin-node-resolve (source)
11.2.1 -> 15.2.3

Release Notes

rollup/plugins (@rollup/plugin-node-resolve)
v15.2.3
Compare Source
2023-10-08
Bugfixes

fix: modulePaths default is not set #https://github.com/rollup/plugins/pull/1534l/1534)

v15.2.2
Compare Source
2023-10-05
Bugfixes

fix: ensure rollup 4 compatibility #https://github.com/rollup/plugins/pull/1595l/1595)

v15.2.1
Compare Source
2023-08-22
Bugfixes

fix: Implement package exports / imports resolution algorithm according to Node documentation #https://github.com/rollup/plugins/pull/1549l/1549)

v15.2.0
Compare Source
2023-08-17
Features

feat: pass original importee to secondary resolve #https://github.com/rollup/plugins/pull/1557l/1557)

v15.1.0
Compare Source
2023-05-30
Features

feat: Resolve js/jsx/mjs/cjs imports from TypeScript files #https://github.com/rollup/plugins/pull/1498l/1498)

v15.0.2
Compare Source
2023-04-04
Bugfixes

fix: bump is-builtin-module version, imports with a trailing slash #https://github.com/rollup/plugins/pull/1424l/1424)

v15.0.1
Compare Source
2022-10-21
Updates

chore: update rollup dependencies (3038271)

v15.0.0
Compare Source
2022-10-10
Breaking Changes

fix: prepare for Rollup 3 #https://github.com/rollup/plugins/pull/1288l/1288)

v14.1.0
Compare Source
2022-09-12
Features

feat: add new option, modulePaths (#https://github.com/rollup/plugins/issues/1104s/1104))

v14.0.1
Compare Source
2022-09-08
Bugfixes

fix: handle circular commonjs (#https://github.com/rollup/plugins/issues/1259s/1259))

v14.0.0
2022-09-06
Breaking Changes

fix: preserve moduleSideEffects when re-resolving files (#https://github.com/rollup/plugins/issues/1245s/1245))

v13.3.0
2022-05-02
Features

feat: support node: protocol (#https://github.com/rollup/plugins/issues/1124s/1124))

v13.2.2
2022-05-02
Bugfixes

fix: Respect if other plugins resolve the resolution to a different id (#https://github.com/rollup/plugins/issues/1181s/1181))
fix: Revert respect if other plugins resolve the resolution to a different id (ae59ceb)
fix: Respect if other plugins resolve the resolution to a different id (f8d4c44)

v13.2.1
2022-04-15
Bugfixes

fix: update side effects logic to be deep when glob doesn’t contain / (#https://github.com/rollup/plugins/issues/1148s/1148))

v13.2.0
2022-04-11
Features

feat: Add the ability to pass a function into resolveOnly (#https://github.com/rollup/plugins/issues/1152s/1152))

v13.1.3
2022-01-05
Bugfixes

fix: use correct version when published (#https://github.com/rollup/plugins/issues/1063s/1063))

v13.1.2
2021-12-31
Bugfixes

fix: forward meta-information from other plugins (#https://github.com/rollup/plugins/issues/1062s/1062))

v13.1.1
2021-12-13
Updates

test: add tests for mixing custom exportConditions with browser: true (#https://github.com/rollup/plugins/issues/1043s/1043))

v13.1.0
2021-12-13
Features

feat: expose plugin version (#https://github.com/rollup/plugins/issues/1050s/1050))

v13.0.6
2021-10-19
Bugfixes

fix: pass on isEntry flag (#https://github.com/rollup/plugins/issues/1016s/1016))

v13.0.5
2021-09-21
Updates

docs: fix readme heading depth (#&#8203https://github.com/rollup/plugins/issues/999es/999))

v13.0.4
2021-07-24
Bugfixes

fix: Fix bug where JS import was converted to a TS import, resulting in an error when using export maps (#&#8203https://github.com/rollup/plugins/issues/921es/921))

v13.0.3
2021-07-24
Bugfixes

fix: handle browser-mapped paths correctly in nested contexts (#&#8203https://github.com/rollup/plugins/issues/920es/920))

v13.0.2
2021-07-15
Bugfixes

fix: handle "package.json" being in path (#&#8203https://github.com/rollup/plugins/issues/927es/927))

v13.0.1
2021-07-15
Updates

docs: Document how to get Node.js exports resolution (#&#8203https://github.com/rollup/plugins/issues/884es/884))

v13.0.0
2021-05-04
Breaking Changes

fix!: mark module as external if resolved module is external (#&#8203https://github.com/rollup/plugins/issues/799es/799))

Features

feat: Follow up to #&#8203https://github.com/rollup/plugins/issues/843es/843), refining exports and browser field interaction (#https://github.com/rollup/plugins/issues/866s/issues/866))

Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - "after 8am and before 4pm on tuesday" in timezone Etc/UTC.
🚦 Automerge: Enabled.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.

[ ] If you want to rebase/retry this PR, check this box

This PR has been generated by Renovate Bot.

Rolled up into https://github.com/apollographql/apollo-ios-dev/pull/170.


New method resolveModelPrefix() doesn't consider current module itself

https://github.com/theia-ide/yang-lsp/blob/de2e2371e7bc6c49f030bebb5a83db3e6f55776e/yang-lsp/io.typefox.yang/src/main/java/io/typefox/yang/scoping/xpath/XpathResolver.xtend#L345
In this method, the input linkName could also be current modules node name with current module's its own prefix. But the logic only consider imported module. See the example,
`module m_a {
  prefix ma;

  leaf lA {
        type leafref {
              path '/ma:lm/ma:state';
        }
  }

  container lm {
        leaf state {
              type string;
        }
  }

}`
Here in this example, prefix ma are actually point to current module m_a itself. But in resolveModelPrefix(), this prefix 'ma' couldn't be found in imported module.

Doesn't it work anyway? The logic should go on with the simple name then.

No, I don't think it works. Because the path will always be a proxy. I think Linker couldn't find the correct target node.

Fixed


Regularization

implementing general constrain nuisances
and example of regularization flow

To test it run: (ws, datacards, text2ws, fits)
python createWs.py

@nucleosynthesis, @ajgilbert
PR. is made for reference,
for the moment not discussed if should be merged.

@amarini - is this something we can merge into the 81x branch (instead of 74x)? I think this will make a very nice addition and we can consider merging it soon, for testing.
I think this is large enough of an addition to make a new tag (which would be v7.1.0) which would give some time to write a short documentation before making this the "recommended" tag.

@nucleosynthesis @vischia
Last time I checked the branch was mergeable both in 8x 7x branch.
I was trying to make an example and regularization studies here,
but I never complete all the studies I wanted to, nor the documentation.
In principle, we are able to do the SVD-RooUnfold and the TUnfold (generalized Tickonov) regularization, (with a bit of work) in any form, but no automatic way to scan the parameters.

Since this has been merged in 102x, I'm closing it.


Mark new discovered link references definition messages as fuzzy

Extracting messages with md2po, usually the link references are not translated, so copy their msgid into the msgstr and mark them as fuzzy.

Added in v0.3.48.


aci: fix ManifestFromImage to handle ./manifest

The tar Header.Name (for example with gnu tar) can start with ./ (for example
./manifest). In this case ManifestFromImage will fail.
Plus, I noticed that the error was strange: unexpected error EOF. This is due
to the io.EOF error not being handled. So I rewrote the code to handle it (now
it's similar to github.com/coreos/rocket/pkg/tar.ExtractTar).

oops, #189 never landed. Since this is slightly more comprehensive I'm going to merge this instead. Thanks!


Add italy.coronavirusinfections.org

Hi @soroushchehresa, thanks also for this addition!

@kenlog
Hi, thanks for your contribution!
Please read the contribution guidelines first.


Rename LICENSE to LICENSE.md

The extension allows the text to be displayed with text wrapping on github.

Sure, thanks!


SmartCash cryptocurrency support

Extend BitcoinLib with SmartCash support

Thank you :+1: :rocket: This should be up on NuGet in the next release.


Unable to fold/unfold sections of code in VS code

Off late, I am not able to fold/unfold segments of  python code. The icon similar to 'v' does not appear on the left. The strange thing is that I see this on json files.
There are no specific steps to reproduce this issue. It occurs randomly.

Can you provide screenshots?

This happens randomly after no specific trigger. How can I collect logs ?

For JSON files, I don't see this issue.

I used to be able to fold comments, but now that seems impossible.  This was a way for me to format large sets of code.  I also tried the #region but still no folding.  I would hate to lose the ability to fold on comments.

@abhi910 and @Hansander, are you perhaps using the Pylance vscode extension? I see that it added its own support for folding ranges recently. See the end of this thread. If you are using Pylance then I think that's why things have changed. In that case please post about the issue(s) at the Pylance repository..


NEW Allow installation against PHP 8

Haven't hit any issues with code compatibility, so this should be all that's required for PHP 8 support.

Looks good!


[Bug]: llama-index-vector-stores-lantern integration incompatible with latest LanternDB builds

Bug Description
Background:
As of Feb 21, 2024, the LanternDB team updated their project to stop supporting the postgres access method hnsw in favor of only supporting their own custom access_method, lantern_hnsw.
Prior to this, the LanternDB codebase supported hnsw and only used lantern_hnsw if hnsw was already being used by another extension, like PGVector (this can be seen in the removed code in the commit linked above).
This change was rolled out with the 0.2.3 version of Lantern, which was only released on April 9th, which is why this incompatibility has only recently emerged.
Issue:

llama_index's Lantern integration, llama-index-vector-stores-lantern is hardcoded to use access_method hnsw.
now that Lantern no longer supports hnsw, the current version of llama_index's Lantern integration is incompatible with LanterDB builds > 0.1.1.

The error:* If a later version of Lantern (v0.2.3 or v0.2.4) is used with llama_index, the database returns an error when trying to insert into (or query) the vector database. See error logs are included in logs section.
Solution:

In order to keep supporting LanternDB, this llama_index integration needs to be updated to use lantern_hnsw instead.
This appears fixable with a simple code change from hnsw to lantern_hnsw on line 115 of llama-index-integrations/vector_stores/llama-index-vector-stores-lantern/llama_index/vector_stores/lantern/base.py.
I will submit a PR with the fix once this issue is published.

Version
have encountered issue with 0.10.25 -> 0.10.31
Steps to Reproduce

Use llama_index's llama-index-vector-stores-lantern integration in a python project to insert a document into the LanternVectorStore   (suggest latest 0.10.31 version of llama_index)
Must use a vector database running the lantern postgres extension, with a build of Lantern  > v0.1.1, such as 0.2.3 or 0.2.4.
For example: this latest pg16 build, which is version 0.2.4
I have only used this setup with Docker. Can reproduce the issue 100% of the time if using latest version of LanternDB & latest llama-index.

Relevant Logs/Tracbacks
**Vector-db container logs:**

starting PostgreSQL 16.2 (Debian 16.2-1.pgdg120+2) on x86_64-pc-linux-gnu, compiled by gcc (Debian 12.2.0-14) 12.2.0, 64-bit
LOG:  listening on Unix socket "/var/run/postgresql/.s.PGSQL.5432"
LOG:  database system is ready to accept connections
server started
/usr/local/bin/docker-entrypoint.sh: running /docker-entrypoint-initdb.d/init.sql
psql:/docker-entrypoint-initdb.d/init.sql:5: NOTICE:  database "vector_db" does not exist, skipping
DROP DATABASE
CREATE DATABASE
You are now connected to database "vector_db" as user "postgres".
CREATE EXTENSION
PostgreSQL init process complete; ready for start up.

LOG:  starting PostgreSQL 16.2 (Debian 16.2-1.pgdg120+2) on x86_64-pc-linux-gnu, compiled by gcc (Debian 12.2.0-14) 12.2.0, 64-bit
LOG:  listening on IPv4 address "<IP_ADDRESS>", port 5432
LOG:  listening on IPv6 address "::", port 5432
LOG:  listening on Unix socket "/var/run/postgresql/.s.PGSQL.5432"
LOG:  database system is ready to accept connections
ERROR:  access method "hnsw" does not exist
STATEMENT:  CREATE INDEX sop_hnsw_idx ON public.data_sop USING hnsw (embedding dist_cos_ops) WITH (m = 16, ef_construction = 128, ef = 64, dim = 3)

**Logs from the service performing the insert into vector-db:

INFO:sqlalchemy.engine.Engine:CREATE EXTENSION IF NOT EXISTS lantern
INFO:sqlalchemy.engine.Engine:[generated in 0.00026s] {}
INFO:sqlalchemy.engine.Engine:COMMIT
INFO:sqlalchemy.engine.Engine:BEGIN (implicit)
INFO:sqlalchemy.engine.Engine:CREATE SCHEMA IF NOT EXISTS public
INFO:sqlalchemy.engine.Engine:[generated in 0.00026s] {}
INFO:sqlalchemy.engine.Engine:COMMIT
INFO:sqlalchemy.engine.Engine:BEGIN (implicit)
FROM pg_catalog.pg_class JOIN pg_catalog.pg_namespace ON pg_catalog.pg_namespace.oid = pg_catalog.pg_class.relnamespace
WHERE pg_catalog.pg_class.relname = %(table_name)s AND pg_catalog.pg_class.relkind = ANY (ARRAY[%(param_1)s, %(param_2)s, %(param_3)s, %(param_4)s, %(param_5)s]) AND pg_catalog.pg_namespace.nspname = %(nspname_1)s
INFO:sqlalchemy.engine.Engine:SELECT pg_catalog.pg_class.relname
FROM pg_catalog.pg_class JOIN pg_catalog.pg_namespace ON pg_catalog.pg_namespace.oid = pg_catalog.pg_class.relnamespace
WHERE pg_catalog.pg_class.relname = %(table_name)s AND pg_catalog.pg_class.relkind = ANY (ARRAY[%(param_1)s, %(param_2)s, %(param_3)s, %(param_4)s, %(param_5)s]) AND pg_catalog.pg_namespace.nspname = %(nspname_1)s
INFO:sqlalchemy.engine.Engine:[generated in 0.00034s] {'table_name': 'data_sop', 'param_1': 'r', 'param_2': 'p', 'param_3': 'f', 'param_4': 'v', 'param_5': 'm', 'nspname_1': 'public'}

INFO:sqlalchemy.engine.Engine:
CREATE TABLE public.data_sop (
INFO sqlalchemy.engine.Engine
CREATE TABLE public.data_sop (
	id BIGSERIAL NOT NULL,
	text VARCHAR NOT NULL,
	metadata_ JSON,
	node_id VARCHAR,
	embedding REAL[],
	PRIMARY KEY (id)
)

INFO:sqlalchemy.engine.Engine:[no key 0.00018s] {}
INFO:sqlalchemy.engine.Engine:CREATE INDEX sop_hnsw_idx ON public.data_sop USING hnsw (embedding dist_cos_ops) WITH (m = 16, ef_construction = 128, ef = 64, dim = 3)
INFO:sqlalchemy.engine.Engine:[no key 0.00023s] {}
INFO:sqlalchemy.engine.Engine:ROLLBACK
ERROR:server:Exception calling application: (psycopg2.errors.UndefinedObject) access method "hnsw" does not exist

[SQL: CREATE INDEX sop_hnsw_idx ON public.data_sop USING hnsw (embedding dist_cos_ops) WITH (m = 16, ef_construction = 128, ef = 64, dim = 3)]
(Background on this error at: https://sqlalche.me/e/20/f405)
Traceback (most recent call last):
  File "/usr/local/lib/python3.12/site-packages/sqlalchemy/engine/base.py", line 1971, in _exec_single_context
    self.dialect.do_execute(
  File "/usr/local/lib/python3.12/site-packages/sqlalchemy/engine/default.py", line 919, in do_execute
    cursor.execute(statement, parameters)
psycopg2.errors.UndefinedObject: access method "hnsw" does not exist

The above exception was the direct cause of the following exception:

Traceback (most recent call last):
  File "/usr/src/app/vectorization_servicer.py", line 35, in VectorizeDocument
    vector_store_uuid = self.vector_store.insert(request.document)
                        ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/app/vector_store.py", line 57, in insert
    self.index.insert(doc)
  File "/usr/local/lib/python3.12/site-packages/llama_index/core/indices/base.py", line 242, in insert
    self.insert_nodes(nodes, **insert_kwargs)
  File "/usr/local/lib/python3.12/site-packages/llama_index/core/indices/vector_store/base.py", line 330, in insert_nodes
    self._insert(nodes, **insert_kwargs)
  File "/usr/local/lib/python3.12/site-packages/llama_index/core/indices/vector_store/base.py", line 312, in _insert
    self._add_nodes_to_index(self._index_struct, nodes, **insert_kwargs)
  File "/usr/local/lib/python3.12/site-packages/llama_index/core/indices/vector_store/base.py", line 234, in _add_nodes_to_index
    new_ids = self._vector_store.add(nodes_batch, **insert_kwargs)
              ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.12/site-packages/llama_index/vector_stores/lantern/base.py", line 325, in add
    self._initialize()
  File "/usr/local/lib/python3.12/site-packages/llama_index/vector_stores/lantern/base.py", line 309, in _initialize
    self._create_tables_if_not_exists()
  File "/usr/local/lib/python3.12/site-packages/llama_index/vector_stores/lantern/base.py", line 293, in _create_tables_if_not_exists
    self._base.metadata.create_all(session.connection())
  File "/usr/local/lib/python3.12/site-packages/sqlalchemy/sql/schema.py", line 5825, in create_all
    bind._run_ddl_visitor(
  File "/usr/local/lib/python3.12/site-packages/sqlalchemy/engine/base.py", line 2461, in _run_ddl_visitor
    visitorcallable(self.dialect, self, **kwargs).traverse_single(element)
  File "/usr/local/lib/python3.12/site-packages/sqlalchemy/sql/visitors.py", line 664, in traverse_single
    return meth(obj, **kw)
           ^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.12/site-packages/sqlalchemy/sql/ddl.py", line 918, in visit_metadata
    self.traverse_single(
  File "/usr/local/lib/python3.12/site-packages/sqlalchemy/sql/visitors.py", line 664, in traverse_single
    return meth(obj, **kw)
           ^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.12/site-packages/sqlalchemy/sql/ddl.py", line 960, in visit_table
    self.traverse_single(index, create_ok=True)
  File "/usr/local/lib/python3.12/site-packages/sqlalchemy/sql/visitors.py", line 664, in traverse_single
    return meth(obj, **kw)
           ^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.12/site-packages/sqlalchemy/sql/ddl.py", line 997, in visit_index
    CreateIndex(index)._invoke_with(self.connection)
  File "/usr/local/lib/python3.12/site-packages/sqlalchemy/sql/ddl.py", line 314, in _invoke_with
    return bind.execute(self)
           ^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.12/site-packages/sqlalchemy/engine/base.py", line 1422, in execute
    return meth(
           ^^^^^
  File "/usr/local/lib/python3.12/site-packages/sqlalchemy/sql/ddl.py", line 180, in _execute_on_connection
    return connection._execute_ddl(
           ^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.12/site-packages/sqlalchemy/engine/base.py", line 1533, in _execute_ddl
    ret = self._execute_context(
          ^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.12/site-packages/sqlalchemy/engine/base.py", line 1850, in _execute_context
    return self._exec_single_context(
           ^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.12/site-packages/sqlalchemy/engine/base.py", line 1990, in _exec_single_context
    self._handle_dbapi_exception(
  File "/usr/local/lib/python3.12/site-packages/sqlalchemy/engine/base.py", line 2357, in _handle_dbapi_exception
    raise sqlalchemy_exception.with_traceback(exc_info[2]) from e
  File "/usr/local/lib/python3.12/site-packages/sqlalchemy/engine/base.py", line 1971, in _exec_single_context
    self.dialect.do_execute(
  File "/usr/local/lib/python3.12/site-packages/sqlalchemy/engine/default.py", line 919, in do_execute
    cursor.execute(statement, parameters)
sqlalchemy.exc.ProgrammingError: (psycopg2.errors.UndefinedObject) access method "hnsw" does not exist

[SQL: CREATE INDEX sop_hnsw_idx ON public.data_sop USING hnsw (embedding dist_cos_ops) WITH (m = 16, ef_construction = 128, ef = 64, dim = 3)]
(Background on this error at: https://sqlalche.me/e/20/f405)

Looking forward to the PR, thanks @nataliachodelski !


Fresh windows 10 install - ErrorHook issue

After using rustup and the following cmd >

cargo install --git https://github.com/foundry-rs/foundry foundry-cli anvil --bins --locked

when trying cmd >

forge init hello_foundry

I get :
Error: cannot install provided ErrorHook, a hook has already been installed
Location:
cli\src\handler.rs:62:9

any luck debugging this @k2riddim ?

hey, no sorry, I had to install wsl

Could reproduce, Windows 10 with a fresh VS 2022 install and using the same command as OP:
PS C:\Users\Daniel> forge -V
Error: cannot install provided ErrorHook, a hook has already been installed

Location:
    cli\src\handler.rs:62:9
PS C:\Users\Daniel> cast -V
Error: cannot install provided ErrorHook, a hook has already been installed

Location:
    cli\src\handler.rs:62:9
PS C:\Users\Daniel> anvil -V
anvil 0.1.0 (76be373 2022-09-06T19:36:52.9230886Z)
PS C:\Users\Daniel> rustup -V
rustup 1.25.1 (bb60b1e89 2022-07-12)
info: This is the version for the rustup toolchain manager, not the rustc compiler.
info: The currently active `rustc` version is `rustc 1.63.0 (4b91a6ea7 2022-08-08)`

Although building from source works just fine:
PS C:\Users\Daniel\Documents\GitHub\foundry-rs\foundry> cargo run --bin forge -- -V
    Finished dev [unoptimized] target(s) in 0.59s
     Running `target\debug\forge.exe -V`
forge 0.2.0 (a78aa49 2022-09-06T19:54:43.4517457Z)

this doesn't make any sense...

cast install --path .\cli\ foundry-cli --bins --locked, same command as OP but using local Foundry repo works:
    Replaced package `foundry-cli v0.2.0 (https://github.com/foundry-rs/foundry#76be373d)` with `foundry-cli v0.2.0 (C:\Users\Daniel\Documents\GitHub\foundry-rs\foundry\cli)` (executables `cast.exe`, `forge.exe`)
PS C:\Users\Daniel\Documents\GitHub\foundry-rs\foundry> forge -V
forge 0.2.0 (a78aa49 2022-09-06T20:12:12.3499251Z)

What could be added to docs is rustup update for windows that fixed it for me

hmm perhaps this is an issue with older rust versions, but still doesn't make much sense, since there's no call before
https://github.com/foundry-rs/foundry/blob/48d5d79a63acbd5cb454d39fa0c01c297de89559/cli/src/handler.rs#L62
that sets this...

I have replicated this, and I am still having the same issues, tried using different versions of Rust beta and nightly. Also installed from github and using OP commands. Workaround is to use WSL or MINGW64, but not ideal.

this is so weird to me ...
I guess we could make this not a hard error in windows as a workaround

perhaps this is related https://github.com/rust-lang/rust/issues/81408

@mattsse i removed the hook locally and is all good, so your fix does the trick

I ran into the same issue but instead of a fresh windows 10 os, I'm running linux.
You should be able to reproduce it using a VM or something. Compile from 67ef930 and move binaries to the new VM:
$ cast
Error: cannot install provided ErrorHook, a hook has already been installed

Location:
cli\src\handler.rs:70:13

I tried by setting FOUNDRY_DEBUG still no luck:
$ FOUNDRY_DEBUG= ./cast -V
Error: cannot install provided ErrorHook, a hook has already been installed

Location:
    /home/user/.cargo/registry/src/github.com-.../color-eyre-0.6.1/src/config.rs:686.9

it also ends up calling eyre_hook.install()?, any idea how to fix this @mattsse ?

Same thing happened to me using a debian container: anvil works fine but not forge and cast.
The solution was simply to install git.
FROM debian:bullseye-slim as foundry-install
RUN apt-get update -y && apt-get install -y curl git unzip wget
RUN curl -L https://foundry.paradigm.xyz | bash
RUN /root/.foundry/bin/foundryup
RUN cp -r /root/.foundry/bin/* /usr/local/bin

FROM debian:bookworm-slim
# RUN apt-get update -y && apt-get install -y git # solution
COPY --from=foundry-install /usr/local/bin /usr/local/bin

$ root@status:/# forge --version
bash: forge: command not found

$ root@status:/# cast --version
Error: cannot install provided ErrorHook, a hook has already been installed

Location:
    cli/src/handler.rs:70:13

$ anvil
# works as expected

Same thing happened to me using a debian container: anvil works fine but not forge and cast. The solution was simply to install git.
FROM debian:bullseye-slim as foundry-install
RUN apt-get update -y && apt-get install -y curl git unzip wget
RUN curl -L https://foundry.paradigm.xyz | bash
RUN /root/.foundry/bin/foundryup
RUN cp -r /root/.foundry/bin/* /usr/local/bin

FROM debian:bookworm-slim
# RUN apt-get update -y && apt-get install -y git # solution
COPY --from=foundry-install /usr/local/bin /usr/local/bin

$ root@status:/# forge --version
bash: forge: command not found

$ root@status:/# cast --version
Error: cannot install provided ErrorHook, a hook has already been installed

Location:
    cli/src/handler.rs:70:13

$ anvil
# works as expected

Thanks, this works on Alpine too. Strange error message but it makes sense since I guess git is used to search for the foundry.toml

This issue is not letting me use the tool in an airgapped computer. It is a pity since the tool is really good.


Add bio.tools for msstatstmt

Hi all,
This PR links the tools to its bio.tools entry: https://bio.tools/msstatstmt
It will be useful to get EDAM ontology annotations
Bérénice

Thanks


Duplicates in rss

Hi @JMousqueton, since you updated the rss to includes countries, there are a lot of duplicate notifications, one without the country and another include the country, for example: goldenc.com by Lockbit.

I've reverse the code.
But the xml file contained only one entry and Guid stay the same. Should be a reader/parser problem.

Thanks!
On Fri, Dec 22, 2023, 12:31 Julien Mousqueton @.***>
wrote:

I've reverse the code.
But the xml file contained only one entry and Guid stay the same. Should
be a reader/parser problem.
—
Reply to this email directly, view it on GitHub
https://github.com/JMousqueton/ransomware.live/issues/81#issuecomment-1867518725,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AMNVQ62VBJQ3PZ23JC75Z5DYKVOPXAVCNFSM6AAAAABA7UNZ46VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQNRXGUYTQNZSGU
.
You are receiving this because you authored the thread.Message ID:
@.***>

Now the country is in the category field of the RSS feed


PYI-183: Identity verification link

Whats changed

Adding in a link to the generic identity verification form.
Split out the adding identity evidence to its own function to keep next function tidy.
Added a comment where we should add a new method to post the identity verification to core-back.

As discussed, I don't think that logging approach will work in a production system as using a global singleton loses the ability to consistently log with per-request data (e.g. CorrelationIDs). But if this becomes an issue, it's easy enough to restore.


Missing dependencies in dream-mirage

I'm trying to set up a CI on ocaml-matrix, and encountered errors while building dream-mirage.
Here are the missing dependencies !

Thank you a lot


🚀 Feature: client-server relational DBMS

🔖 Feature description
Implement a connector so we can use a client-server relational DBMS like MySQL or PostgreSQL instead of SQLite.
🎤 Pitch
I started a HELM chart to deploy Pingvin Share on Kubernetes. This is for now just a proof of concept because the application currently lacks support for concurrent access from multiple clients to the database, so only one replica cans run at a given time.
In my opinion, it would be great to implement a client-server relational DBMS like PostgreSQL or MySQL. These databases would add scalability and permit multiple instances to run in parallel behind a load balancer.
That said, I must admit that I'm not familiar enough with the application to ascertain whether implementing this would be the only required feature to ensure the application to run smoothly with round-robin redirections of a client between Pingvin Share instances.

Thanks for the awesome app by the way !

Hey, yeah this is currently an issue of Pingvin Share. We are using the Prisma ORM and they don't allow to change the database provider because the migrations are written in the database specific syntax (see the docs).
But it's definitely important to be able to switch database providers. I have to find a solution. One solution would be to write an own migration engine but I'm not sure how difficult this is.
I don't know much about Kubernetes but it interests me how you would manage the stored files with multiple replicas.

You can actually use what is called a Kubernetes Persistent Volumes (PVs) to create a shared storage resource that can be accessed by multiple replicas of an application.
The PVs represent the actual storage, which can be hosted on cloud storage, network-attached storage (NFS), or other storage solutions. Kubernetes ensures that each replica gets access to the same shared storage. This way, all replicas can read and write data to a centralized storage location, enabling data sharing among them.
In my setup, I use a Persistent Volume to mount the directories /opt/app/frontend/public/img and /opt/app/backend/data and preserve data over redeployment. Additionally, I've configured the directories /home/node and /opt/app/frontend/.next/cache as ephemeral volumes to enable running the container's file system in read-only mode.
volumeMounts:
            - name: node-home
              mountPath: /home/node
            - name: frontend-cache
              mountPath: /opt/app/frontend/.next/cache
            - name: data
              mountPath: /opt/app/backend/data
              subPathExpr: data
            - name: data
              mountPath: /opt/app/frontend/public/img
              subPathExpr: img

Yeah you're right


Should recommend using OpenJDK instead of Oracle JDK

Issue Type
[x] Bug
[ ] Feature Request
Priority
[ ] Minor
[x] Major
[ ] Critical
[ ] Blocker
Environment

OS: all
Browser: WebKit

Description

As discussed in apache/cordova-android#637, updates to Oracle JDK 8 including security updates will not be licensed for commercial use after January 2019. Recommended solution should be to use OpenJDK, as discussed in apache/cordova-android#637.
Update is needed in the following section: https://github.com/apache/cordova-docs/blob/45ee7b28111928f5d81b9f463f6d273326067770/www/docs/en/dev/guide/platforms/android/index.md#java-development-kit-jdk
I think this should to be done before we make the next major release for Cordova 9 (apache/cordova#10).

I recently worked out all the steps to get OpenJDK 8 running for Cordova and Android Studio on a new mac, and I documented it all here — I'm adding it here so it may helps others find it, until the docs are updated.
https://github.com/apache/cordova-android/issues/637#issuecomment-514065674

Closing as stale.
But I think we should continue referencing the official Java source. It's opinionated to reference other java runtime implements over Oracle's JDK.

Downloading oracle jdk now requires an oracle account (nooooope!), so if openjdk works just as well, it will be easier for a new user to install openjdk

This is not an easy toolchain to get installed and running.  It took me all day yesterday to just get the basic sample building on android.
It would have saved me a lot of time yesterday if I knew I needed to install exactly open jdk 17 and not 20.  I don't know why you wouldn't document in the 'quick' install document the easiest steps to quickly install this toolset.  🙄
(Some of the install pain was also because it was not obvious in the install docs that I needed to install the android command line tools also.  Additionally confusion over what environment variables were supposed to be ANDROID_HOME / ANDROID_SDK_ROOT)
Excuse the frustration from a day wasted due to gaps in the documentation, but seeing the active avoidance of making your docs useful when people are pointing out exactly what needs to change to more easily onboard new users to your software is infuriating.