text:
P110 not obtaining Energy or runtime data with V2 integration

Version of the integration
NAME = "tapo"
DOMAIN = "tapo"
VERSION = "2.0.0"
Configuration
Device info
P110
by TP-Link
Firmware: 1.2.3 Build 230425 Rel.142542
Hardware: 1.0
Describe the bug
Updated to the new version and now all existing entries are not reading any energy or runtime data.
Tried removing a device and adding it again. Device appears but with only 8 entities where it had 10 previously. Still no energy or runtime data.
Sensors:
Chest Freezer (Switch is available)
Current power Unknown
Month energy Unknown
Month runtime Unknown
Overheat False
Signal level -52 dBm
Today energy Unknown
Today runtime Unknown
I can still control the device as a switch.
Debug log
File "aiohttp/_http_parser.pyx", line 551, in aiohttp._http_parser.HttpParser.feed_data
aiohttp.http_exceptions.BadStatusLine: 400, message="Bad status line 'Expected CRLF after version'"
2023-07-06 09:46:04.482 ERROR (MainThread) [aiohttp.server] Error handling request
Traceback (most recent call last):
File "/usr/local/lib/python3.11/site-packages/aiohttp/web_protocol.py", line 332, in data_received
messages, upgraded, tail = self._request_parser.feed_data(data)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "aiohttp/_http_parser.pyx", line 551, in aiohttp._http_parser.HttpParser.feed_data
aiohttp.http_exceptions.BadStatusLine: 400, message="Bad status line 'Expected CRLF after version'"
2023-07-06 09:46:05.389 ERROR (MainThread) [aiohttp.server] Error handling request
Traceback (most recent call last):
File "/usr/local/lib/python3.11/site-packages/aiohttp/web_protocol.py", line 332, in data_received
messages, upgraded, tail = self._request_parser.feed_data(data)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "aiohttp/_http_parser.pyx", line 551, in aiohttp._http_parser.HttpParser.feed_data
aiohttp.http_exceptions.BadStatusLine: 400, message="Bad status line 'Expected CRLF after version'"
2023-07-06 09:46:06.536 DEBUG (MainThread) [custom_components.tapo.coordinators] Finished fetching tapo data in 0.239 seconds (success: True)
2023-07-06 09:46:09.242 DEBUG (MainThread) [custom_components.tapo.coordinators] Finished fetching tapo data in 0.030 seconds (success: True)
2023-07-06 09:46:11.309 DEBUG (MainThread) [custom_components.tapo.coordinators] Finished fetching tapo data in 0.242 seconds (success: True)
2023-07-06 09:46:16.312 DEBUG (MainThread) [custom_components.tapo.coordinators] Finished fetching tapo data in 0.029 seconds (success: True)
2023-07-06 09:46:16.323 DEBUG (MainThread) [custom_components.tapo.coordinators] Finished fetching tapo data in 0.028 seconds (success: True)
2023-07-06 09:46:16.340 DEBUG (MainThread) [custom_components.tapo.coordinators] Finished fetching tapo data in 0.054 seconds (success: True)
2023-07-06 09:46:16.344 DEBUG (MainThread) [custom_components.tapo.coordinators] Finished fetching tapo data in 0.030 seconds (success: True)
2023-07-06 09:46:16.373 ERROR (MainThread) [aiohttp.server] Error handling request
Traceback (most recent call last):
File "/usr/local/lib/python3.11/site-packages/aiohttp/web_protocol.py", line 332, in data_received
messages, upgraded, tail = self._request_parser.feed_data(data)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "aiohttp/_http_parser.pyx", line 551, in aiohttp._http_parser.HttpParser.feed_data
aiohttp.http_exceptions.BadStatusLine: 400, message="Bad status line 'Expected CRLF after version'"
2023-07-06 09:46:16.417 DEBUG (MainThread) [custom_components.tapo.coordinators] Finished fetching tapo data in 0.039 seconds (success: True)
2023-07-06 09:46:16.442 DEBUG (MainThread) [custom_components.tapo.coordinators] Finished fetching tapo data in 0.023 seconds (success: True)
2023-07-06 09:46:16.454 DEBUG (MainThread) [custom_components.tapo.coordinators] Finished fetching tapo data in 0.089 seconds (success: True)
2023-07-06 09:46:16.496 DEBUG (MainThread) [custom_components.tapo.coordinators] Finished fetching tapo data in 0.297 seconds (success: True)
2023-07-06 09:46:16.508 DEBUG (MainThread) [custom_components.tapo.coordinators] Finished fetching tapo data in 0.239 seconds (success: True)
2023-07-06 09:46:16.541 DEBUG (MainThread) [custom_components.tapo.coordinators] Finished fetching tapo data in 0.275 seconds (success: True)
2023-07-06 09:46:16.546 DEBUG (MainThread) [custom_components.tapo.coordinators] Finished fetching tapo data in 0.176 seconds (success: True)
2023-07-06 09:46:17.338 DEBUG (MainThread) [custom_components.tapo.coordinators] Finished fetching tapo data in 0.044 seconds (success: True)
2023-07-06 09:46:17.487 DEBUG (MainThread) [custom_components.tapo.coordinators] Finished fetching tapo data in 0.032 seconds (success: True)
2023-07-06 09:46:17.538 DEBUG (MainThread) [custom_components.tapo.coordinators] Finished fetching tapo data in 0.240 seconds (success: True)
2023-07-06 09:46:17.636 DEBUG (MainThread) [custom_components.tapo.coordinators] Finished fetching tapo data in 0.240 seconds (success: True)
2023-07-06 09:46:17.717 DEBUG (MainThread) [custom_components.tapo.coordinators] Finished fetching tapo data in 0.275 seconds (success: True)
2023-07-06 09:46:19.428 DEBUG (MainThread) [custom_components.tapo.coordinators] Finished fetching tapo data in 0.034 seconds (success: True)
2023-07-06 09:46:19.617 WARNING (MainThread) [custom_components.localtuya.common] [bfe...nvk] Failed to connect to 192.168.1.151: [Errno 113] Connect call failed ('192.168.1.151', 6668)
2023-07-06 09:46:19.620 WARNING (MainThread) [custom_components.localtuya.common] [bff...aut] Failed to connect to 192.168.1.116: [Errno 113] Connect call failed ('192.168.1.116', 6668)
2023-07-06 09:46:25.424 ERROR (MainThread) [aiohttp.server] Error handling request
Traceback (most recent call last):
File "/usr/local/lib/python3.11/site-packages/aiohttp/web_protocol.py", line 332, in data_received
messages, upgraded, tail = self._request_parser.feed_data(data)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "aiohttp/_http_parser.pyx", line 551, in aiohttp._http_parser.HttpParser.feed_data
aiohttp.http_exceptions.BadStatusLine: 400, message="Bad status line 'Expected CRLF after version'"
2023-07-06 09:46:25.506 ERROR (MainThread) [aiohttp.server] Error handling request
Traceback (most recent call last):
File "/usr/local/lib/python3.11/site-packages/aiohttp/web_protocol.py", line 332, in data_received
messages, upgraded, tail = self._request_parser.feed_data(data)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "aiohttp/_http_parser.pyx", line 551, in aiohttp._http_parser.HttpParser.feed_data
aiohttp.http_exceptions.BadStatusLine: 400, message="Bad status line 'Expected CRLF after version'"
2023-07-06 09:46:26.401 ERROR (MainThread) [aiohttp.server] Error handling request
Traceback (most recent call last):
File "/usr/local/lib/python3.11/site-packages/aiohttp/web_protocol.py", line 332, in data_received
messages, upgraded, tail = self._request_parser.feed_data(data)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "aiohttp/_http_parser.pyx", line 551, in aiohttp._http_parser.HttpParser.feed_data
aiohttp.http_exceptions.BadStatusLine: 400, message="Bad status line 'Expected CRLF after version'"
2023-07-06 09:46:26.505 ERROR (MainThread) [aiohttp.server] Error handling request
Traceback (most recent call last):
File "/usr/local/lib/python3.11/site-packages/aiohttp/web_protocol.py", line 332, in data_received
messages, upgraded, tail = self._request_parser.feed_data(data)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "aiohttp/_http_parser.pyx", line 551, in aiohttp._http_parser.HttpParser.feed_data
aiohttp.http_exceptions.BadStatusLine: 400, message="Bad status line 'Expected CRLF after version'"
2023-07-06 09:46:27.386 ERROR (MainThread) [aiohttp.server] Error handling request
Traceback (most recent call last):
File "/usr/local/lib/python3.11/site-packages/aiohttp/web_protocol.py", line 332, in data_received
messages, upgraded, tail = self._request_parser.feed_data(data)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "aiohttp/_http_parser.pyx", line 551, in aiohttp._http_parser.HttpParser.feed_data
aiohttp.http_exceptions.BadStatusLine: 400, message="Bad status line 'Expected CRLF after version'"
2023-07-06 09:46:27.475 ERROR (MainThread) [aiohttp.server] Error handling request
Traceback (most recent call last):
File "/usr/local/lib/python3.11/site-packages/aiohttp/web_protocol.py", line 332, in data_received
messages, upgraded, tail = self._request_parser.feed_data(data)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "aiohttp/_http_parser.pyx", line 551, in aiohttp._http_parser.HttpParser.feed_data
aiohttp.http_exceptions.BadStatusLine: 400, message="Bad status line 'Expected CRLF after version'"
2023-07-06 09:46:28.421 ERROR (MainThread) [aiohttp.server] Error handling request
Traceback (most recent call last):
File "/usr/local/lib/python3.11/site-packages/aiohttp/web_protocol.py", line 332, in data_received
messages, upgraded, tail = self._request_parser.feed_data(data)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "aiohttp/_http_parser.pyx", line 551, in aiohttp._http_parser.HttpParser.feed_data
aiohttp.http_exceptions.BadStatusLine: 400, message="Bad status line 'Expected CRLF after version'"
2023-07-06 09:46:28.505 ERROR (MainThread) [aiohttp.server] Error handling request
Traceback (most recent call last):
File "/usr/local/lib/python3.11/site-packages/aiohttp/web_protocol.py", line 332, in data_received
messages, upgraded, tail = self._request_parser.feed_data(data)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "aiohttp/_http_parser.pyx", line 551, in aiohttp._http_parser.HttpParser.feed_data
aiohttp.http_exceptions.BadStatusLine: 400, message="Bad status line 'Expected CRLF after version'"
2023-07-06 09:46:29.407 ERROR (MainThread) [aiohttp.server] Error handling request
Traceback (most recent call last):
File "/usr/local/lib/python3.11/site-packages/aiohttp/web_protocol.py", line 332, in data_received
messages, upgraded, tail = self._request_parser.feed_data(data)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "aiohttp/_http_parser.pyx", line 551, in aiohttp._http_parser.HttpParser.feed_data
aiohttp.http_exceptions.BadStatusLine: 400, message="Bad status line 'Expected CRLF after version'"
2023-07-06 09:46:29.494 ERROR (MainThread) [aiohttp.server] Error handling request
Traceback (most recent call last):
File "/usr/local/lib/python3.11/site-packages/aiohttp/web_protocol.py", line 332, in data_received
messages, upgraded, tail = self._request_parser.feed_data(data)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "aiohttp/_http_parser.pyx", line 551, in aiohttp._http_parser.HttpParser.feed_data
aiohttp.http_exceptions.BadStatusLine: 400, message="Bad status line 'Expected CRLF after version'"
2023-07-06 09:46:30.433 ERROR (MainThread) [aiohttp.server] Error handling request
Traceback (most recent call last):
File "/usr/local/lib/python3.11/site-packages/aiohttp/web_protocol.py", line 332, in data_received
messages, upgraded, tail = self._request_parser.feed_data(data)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "aiohttp/_http_parser.pyx", line 551, in aiohttp._http_parser.HttpParser.feed_data
aiohttp.http_exceptions.BadStatusLine: 400, message="Bad status line 'Expected CRLF after version'"
2023-07-06 09:46:30.517 ERROR (MainThread) [aiohttp.server] Error handling request
Traceback (most recent call last):
File "/usr/local/lib/python3.11/site-packages/aiohttp/web_protocol.py", line 332, in data_received
messages, upgraded, tail = self._request_parser.feed_data(data)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "aiohttp/_http_parser.pyx", line 551, in aiohttp._http_parser.HttpParser.feed_data
aiohttp.http_exceptions.BadStatusLine: 400, message="Bad status line 'Expected CRLF after version'"
2023-07-06 09:46:31.388 ERROR (MainThread) [aiohttp.server] Error handling request
Traceback (most recent call last):
File "/usr/local/lib/python3.11/site-packages/aiohttp/web_protocol.py", line 332, in data_received
messages, upgraded, tail = self._request_parser.feed_data(data)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "aiohttp/_http_parser.pyx", line 551, in aiohttp._http_parser.HttpParser.feed_data
aiohttp.http_exceptions.BadStatusLine: 400, message="Bad status line 'Expected CRLF after version'"
2023-07-06 09:46:31.504 ERROR (MainThread) [aiohttp.server] Error handling request
Traceback (most recent call last):
File "/usr/local/lib/python3.11/site-packages/aiohttp/web_protocol.py", line 332, in data_received
messages, upgraded, tail = self._request_parser.feed_data(data)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "aiohttp/_http_parser.pyx", line 551, in aiohttp._http_parser.HttpParser.feed_data
aiohttp.http_exceptions.BadStatusLine: 400, message="Bad status line 'Expected CRLF after version'"
2023-07-06 09:46:32.436 ERROR (MainThread) [aiohttp.server] Error handling request
Traceback (most recent call last):
File "/usr/local/lib/python3.11/site-packages/aiohttp/web_protocol.py", line 332, in data_received
messages, upgraded, tail = self._request_parser.feed_data(data)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "aiohttp/_http_parser.pyx", line 551, in aiohttp._http_parser.HttpParser.feed_data
aiohttp.http_exceptions.BadStatusLine: 400, message="Bad status line 'Expected CRLF after version'"
2023-07-06 09:46:32.524 ERROR (MainThread) [aiohttp.server] Error handling request
Traceback (most recent call last):
File "/usr/local/lib/python3.11/site-packages/aiohttp/web_protocol.py", line 332, in data_received
messages, upgraded, tail = self._request_parser.feed_data(data)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "aiohttp/_http_parser.pyx", line 551, in aiohttp._http_parser.HttpParser.feed_data
aiohttp.http_exceptions.BadStatusLine: 400, message="Bad status line 'Expected CRLF after version'"
2023-07-06 09:46:36.303 ERROR (MainThread) [aiohttp.server] Error handling request
Traceback (most recent call last):
File "/usr/local/lib/python3.11/site-packages/aiohttp/web_protocol.py", line 332, in data_received
messages, upgraded, tail = self._request_parser.feed_data(data)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "aiohttp/_http_parser.pyx", line 551, in aiohttp._http_parser.HttpParser.feed_data
aiohttp.http_exceptions.BadStatusLine: 400, message="Bad status line 'Expected CRLF after version'"
2023-07-06 09:46:36.309 ERROR (MainThread) [aiohttp.server] Error handling request
Traceback (most recent call last):
File "/usr/local/lib/python3.11/site-packages/aiohttp/web_protocol.py", line 332, in data_received
messages, upgraded, tail = self._request_parser.feed_data(data)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "aiohttp/_http_parser.pyx", line 551, in aiohttp._http_parser.HttpParser.feed_data
aiohttp.http_exceptions.BadStatusLine: 400, message="Bad status line 'Expected CRLF after version'"
2023-07-06 09:46:36.325 ERROR (MainThread) [aiohttp.server] Error handling request
Traceback (most recent call last):
File "/usr/local/lib/python3.11/site-packages/aiohttp/web_protocol.py", line 332, in data_received
messages, upgraded, tail = self._request_parser.feed_data(data)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "aiohttp/_http_parser.pyx", line 551, in aiohttp._http_parser.HttpParser.feed_data
aiohttp.http_exceptions.BadStatusLine: 400, message="Bad status line 'Expected CRLF after version'"
2023-07-06 09:46:36.328 ERROR (MainThread) [aiohttp.server] Error handling request
Traceback (most recent call last):
File "/usr/local/lib/python3.11/site-packages/aiohttp/web_protocol.py", line 332, in data_received
messages, upgraded, tail = self._request_parser.feed_data(data)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "aiohttp/_http_parser.pyx", line 551, in aiohttp._http_parser.HttpParser.feed_data
aiohttp.http_exceptions.BadStatusLine: 400, message="Bad status line 'Expected CRLF after version'"
2023-07-06 09:46:36.330 ERROR (MainThread) [aiohttp.server] Error handling request
Traceback (most recent call last):
File "/usr/local/lib/python3.11/site-packages/aiohttp/web_protocol.py", line 332, in data_received
messages, upgraded, tail = self._request_parser.feed_data(data)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "aiohttp/_http_parser.pyx", line 551, in aiohttp._http_parser.HttpParser.feed_data
aiohttp.http_exceptions.BadStatusLine: 400, message="Bad status line 'Expected CRLF after version'"
2023-07-06 09:46:36.333 ERROR (MainThread) [aiohttp.server] Error handling request
Traceback (most recent call last):
File "/usr/local/lib/python3.11/site-packages/aiohttp/web_protocol.py", line 332, in data_received
messages, upgraded, tail = self._request_parser.feed_data(data)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "aiohttp/_http_parser.pyx", line 551, in aiohttp._http_parser.HttpParser.feed_data
aiohttp.http_exceptions.BadStatusLine: 400, message="Bad status line 'Expected CRLF after version'"
2023-07-06 09:46:36.334 ERROR (MainThread) [aiohttp.server] Error handling request
Traceback (most recent call last):
File "/usr/local/lib/python3.11/site-packages/aiohttp/web_protocol.py", line 332, in data_received
messages, upgraded, tail = self._request_parser.feed_data(data)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "aiohttp/_http_parser.pyx", line 551, in aiohttp._http_parser.HttpParser.feed_data
aiohttp.http_exceptions.BadStatusLine: 400, message="Bad status line 'Expected CRLF after version'"
2023-07-06 09:46:36.424 ERROR (MainThread) [aiohttp.server] Error handling request
Traceback (most recent call last):
File "/usr/local/lib/python3.11/site-packages/aiohttp/web_protocol.py", line 332, in data_received
messages, upgraded, tail = self._request_parser.feed_data(data)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "aiohttp/_http_parser.pyx", line 551, in aiohttp._http_parser.HttpParser.feed_data
aiohttp.http_exceptions.BadStatusLine: 400, message="Bad status line 'Expected CRLF after version'"
2023-07-06 09:46:36.516 ERROR (MainThread) [aiohttp.server] Error handling request
Traceback (most recent call last):
File "/usr/local/lib/python3.11/site-packages/aiohttp/web_protocol.py", line 332, in data_received
messages, upgraded, tail = self._request_parser.feed_data(data)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "aiohttp/_http_parser.pyx", line 551, in aiohttp._http_parser.HttpParser.feed_data
aiohttp.http_exceptions.BadStatusLine: 400, message="Bad status line 'Expected CRLF after version'"
2023-07-06 09:46:36.573 DEBUG (MainThread) [custom_components.tapo.coordinators] Finished fetching tapo data in 0.253 seconds (success: True)
2023-07-06 09:46:37.442 ERROR (MainThread) [aiohttp.server] Error handling request
Traceback (most recent call last):
File "/usr/local/lib/python3.11/site-packages/aiohttp/web_protocol.py", line 332, in data_received
messages, upgraded, tail = self._request_parser.feed_data(data)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "aiohttp/_http_parser.pyx", line 551, in aiohttp._http_parser.HttpParser.feed_data
aiohttp.http_exceptions.BadStatusLine: 400, message="Bad status line 'Expected CRLF after version'"
2023-07-06 09:46:37.523 ERROR (MainThread) [aiohttp.server] Error handling request
Traceback (most recent call last):
File "/usr/local/lib/python3.11/site-packages/aiohttp/web_protocol.py", line 332, in data_received
messages, upgraded, tail = self._request_parser.feed_data(data)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "aiohttp/_http_parser.pyx", line 551, in aiohttp._http_parser.HttpParser.feed_data
aiohttp.http_exceptions.BadStatusLine: 400, message="Bad status line 'Expected CRLF after version'"
2023-07-06 09:46:38.412 ERROR (MainThread) [aiohttp.server] Error handling request
Traceback (most recent call last):
File "/usr/local/lib/python3.11/site-packages/aiohttp/web_protocol.py", line 332, in data_received
messages, upgraded, tail = self._request_parser.feed_data(data)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "aiohttp/_http_parser.pyx", line 551, in aiohttp._http_parser.HttpParser.feed_data
aiohttp.http_exceptions.BadStatusLine: 400, message="Bad status line 'Expected CRLF after version'"
2023-07-06 09:46:38.491 ERROR (MainThread) [aiohttp.server] Error handling request
Traceback (most recent call last):
File "/usr/local/lib/python3.11/site-packages/aiohttp/web_protocol.py", line 332, in data_received
messages, upgraded, tail = self._request_parser.feed_data(data)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "aiohttp/_http_parser.pyx", line 551, in aiohttp._http_parser.HttpParser.feed_data
aiohttp.http_exceptions.BadStatusLine: 400, message="Bad status line 'Expected CRLF after version'"
2023-07-06 09:46:39.243 DEBUG (MainThread) [custom_components.tapo.coordinators] Finished fetching tapo data in 0.030 seconds (success: True)
2023-07-06 09:46:39.435 ERROR (MainThread) [aiohttp.server] Error handling request
Traceback (most recent call last):
File "/usr/local/lib/python3.11/site-packages/aiohttp/web_protocol.py", line 332, in data_received
messages, upgraded, tail = self._request_parser.feed_data(data)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "aiohttp/_http_parser.pyx", line 551, in aiohttp._http_parser.HttpParser.feed_data
aiohttp.http_exceptions.BadStatusLine: 400, message="Bad status line 'Expected CRLF after version'"
2023-07-06 09:46:39.523 ERROR (MainThread) [aiohttp.server] Error handling request
Traceback (most recent call last):
File "/usr/local/lib/python3.11/site-packages/aiohttp/web_protocol.py", line 332, in data_received
messages, upgraded, tail = self._request_parser.feed_data(data)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "aiohttp/_http_parser.pyx", line 551, in aiohttp._http_parser.HttpParser.feed_data
aiohttp.http_exceptions.BadStatusLine: 400, message="Bad status line 'Expected CRLF after version'"
2023-07-06 09:46:40.398 ERROR (MainThread) [aiohttp.server] Error handling request
Traceback (most recent call last):
File "/usr/local/lib/python3.11/site-packages/aiohttp/web_protocol.py", line 332, in data_received
messages, upgraded, tail = self._request_parser.feed_data(data)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "aiohttp/_http_parser.pyx", line 551, in aiohttp._http_parser.HttpParser.feed_data
aiohttp.http_exceptions.BadStatusLine: 400, message="Bad status line 'Expected CRLF after version'"
2023-07-06 09:46:40.517 ERROR (MainThread) [aiohttp.server] Error handling request
Traceback (most recent call last):
File "/usr/local/lib/python3.11/site-packages/aiohttp/web_protocol.py", line 332, in data_received
messages, upgraded, tail = self._request_parser.feed_data(data)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "aiohttp/_http_parser.pyx", line 551, in aiohttp._http_parser.HttpParser.feed_data
aiohttp.http_exceptions.BadStatusLine: 400, message="Bad status line 'Expected CRLF after version'"
2023-07-06 09:46:41.306 DEBUG (MainThread) [custom_components.tapo.coordinators] Finished fetching tapo data in 0.238 seconds (success: True)
2023-07-06 09:46:42.440 ERROR (MainThread) [aiohttp.server] Error handling request
Traceback (most recent call last):
File "/usr/local/lib/python3.11/site-packages/aiohttp/web_protocol.py", line 332, in data_received
messages, upgraded, tail = self._request_parser.feed_data(data)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "aiohttp/_http_parser.pyx", line 551, in aiohttp._http_parser.HttpParser.feed_data
aiohttp.http_exceptions.BadStatusLine: 400, message="Bad status line 'Expected CRLF after version'"
2023-07-06 09:46:42.537 ERROR (MainThread) [aiohttp.server] Error handling request
Traceback (most recent call last):
File "/usr/local/lib/python3.11/site-packages/aiohttp/web_protocol.py", line 332, in data_received
messages, upgraded, tail = self._request_parser.feed_data(data)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "aiohttp/_http_parser.pyx", line 551, in aiohttp._http_parser.HttpParser.feed_data
aiohttp.http_exceptions.BadStatusLine: 400, message="Bad status line 'Expected CRLF after version'"
2023-07-06 09:46:43.415 ERROR (MainThread) [aiohttp.server] Error handling request
Traceback (most recent call last):
File "/usr/local/lib/python3.11/site-packages/aiohttp/web_protocol.py", line 332, in data_received
messages, upgraded, tail = self._request_parser.feed_data(data)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "aiohttp/_http_parser.pyx", line 551, in aiohttp._http_parser.HttpParser.feed_data
aiohttp.http_exceptions.BadStatusLine: 400, message="Bad status line 'Expected CRLF after version'"
2023-07-06 09:46:44.079 ERROR (MainThread) [aiohttp.server] Error handling request
Traceback (most recent call last):
File "/usr/local/lib/python3.11/site-packages/aiohttp/web_protocol.py", line 332, in data_received
messages, upgraded, tail = self._request_parser.feed_data(data)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "aiohttp/_http_parser.pyx", line 551, in aiohttp._http_parser.HttpParser.feed_data
aiohttp.http_exceptions.BadStatusLine: 400, message="Bad status line 'Expected CRLF after version'"
2023-07-06 09:46:44.419 ERROR (MainThread) [aiohttp.server] Error handling request
Traceback (most recent call last):
File "/usr/local/lib/python3.11/site-packages/aiohttp/web_protocol.py", line 332, in data_received
messages, upgraded, tail = self._request_parser.feed_data(data)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "aiohttp/_http_parser.pyx", line 551, in aiohttp._http_parser.HttpParser.feed_data
aiohttp.http_exceptions.BadStatusLine: 400, message="Bad status line 'Expected CRLF after version'"
2023-07-06 09:46:44.494 ERROR (MainThread) [aiohttp.server] Error handling request
Traceback (most recent call last):
File "/usr/local/lib/python3.11/site-packages/aiohttp/web_protocol.py", line 332, in data_received
messages, upgraded, tail = self._request_parser.feed_data(data)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "aiohttp/_http_parser.pyx", line 551, in aiohttp._http_parser.HttpParser.feed_data
aiohttp.http_exceptions.BadStatusLine: 400, message="Bad status line 'Expected CRLF after version'"
2023-07-06 09:46:45.444 ERROR (MainThread) [aiohttp.server] Error handling request
Traceback (most recent call last):
File "/usr/local/lib/python3.11/site-packages/aiohttp/web_protocol.py", line 332, in data_received
messages, upgraded, tail = self._request_parser.feed_data(data)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "aiohttp/_http_parser.pyx", line 551, in aiohttp._http_parser.HttpParser.feed_data
aiohttp.http_exceptions.BadStatusLine: 400, message="Bad status line 'Expected CRLF after version'"
2023-07-06 09:46:45.530 ERROR (MainThread) [aiohttp.server] Error handling request
Traceback (most recent call last):
File "/usr/local/lib/python3.11/site-packages/aiohttp/web_protocol.py", line 332, in data_received
messages, upgraded, tail = self._request_parser.feed_data(data)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "aiohttp/_http_parser.pyx", line 551, in aiohttp._http_parser.HttpParser.feed_data
aiohttp.http_exceptions.BadStatusLine: 400, message="Bad status line 'Expected CRLF after version'"
2023-07-06 09:46:46.312 DEBUG (MainThread) [custom_components.tapo.coordinators] Finished fetching tapo data in 0.027 seconds (success: True)
2023-07-06 09:46:46.320 DEBUG (MainThread) [custom_components.tapo.coordinators] Finished fetching tapo data in 0.032 seconds (success: True)
2023-07-06 09:46:46.326 DEBUG (MainThread) [custom_components.tapo.coordinators] Finished fetching tapo data in 0.032 seconds (success: True)
2023-07-06 09:46:46.347 DEBUG (MainThread) [custom_components.tapo.coordinators] Finished fetching tapo data in 0.033 seconds (success: True)
2023-07-06 09:46:46.396 DEBUG (MainThread) [custom_components.tapo.coordinators] Finished fetching tapo data in 0.029 seconds (success: True)
2023-07-06 09:46:46.401 DEBUG (MainThread) [custom_components.tapo.coordinators] Finished fetching tapo data in 0.031 seconds (success: True)
2023-07-06 09:46:46.433 ERROR (MainThread) [aiohttp.server] Error handling request
Traceback (most recent call last):
File "/usr/local/lib/python3.11/site-packages/aiohttp/web_protocol.py", line 332, in data_received
messages, upgraded, tail = self._request_parser.feed_data(data)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "aiohttp/_http_parser.pyx", line 551, in aiohttp._http_parser.HttpParser.feed_data
aiohttp.http_exceptions.BadStatusLine: 400, message="Bad status line 'Expected CRLF after version'"
2023-07-06 09:46:46.449 DEBUG (MainThread) [custom_components.tapo.coordinators] Finished fetching tapo data in 0.034 seconds (success: True)
2023-07-06 09:46:46.476 DEBUG (MainThread) [custom_components.tapo.coordinators] Finished fetching tapo data in 0.098 seconds (success: True)
2023-07-06 09:46:46.482 DEBUG (MainThread) [custom_components.tapo.coordinators] Finished fetching tapo data in 0.282 seconds (success: True)
2023-07-06 09:46:46.507 DEBUG (MainThread) [custom_components.tapo.coordinators] Finished fetching tapo data in 0.236 seconds (success: True)
2023-07-06 09:46:46.524 ERROR (MainThread) [aiohttp.server] Error handling request
Traceback (most recent call last):
File "/usr/local/lib/python3.11/site-packages/aiohttp/web_protocol.py", line 332, in data_received
messages, upgraded, tail = self._request_parser.feed_data(data)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "aiohttp/_http_parser.pyx", line 551, in aiohttp._http_parser.HttpParser.feed_data
aiohttp.http_exceptions.BadStatusLine: 400, message="Bad status line 'Expected CRLF after version'"
2023-07-06 09:46:46.689 DEBUG (MainThread) [custom_components.tapo.coordinators] Finished fetching tapo data in 0.424 seconds (success: True)
2023-07-06 09:46:47.325 DEBUG (MainThread) [custom_components.tapo.coordinators] Finished fetching tapo data in 0.032 seconds (success: True)
2023-07-06 09:46:47.448 ERROR (MainThread) [aiohttp.server] Error handling request
Traceback (most recent call last):
File "/usr/local/lib/python3.11/site-packages/aiohttp/web_protocol.py", line 332, in data_received
messages, upgraded, tail = self._request_parser.feed_data(data)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "aiohttp/_http_parser.pyx", line 551, in aiohttp._http_parser.HttpParser.feed_data
aiohttp.http_exceptions.BadStatusLine: 400, message="Bad status line 'Expected CRLF after version'"
2023-07-06 09:46:47.485 DEBUG (MainThread) [custom_components.tapo.coordinators] Finished fetching tapo data in 0.029 seconds (success: True)
2023-07-06 09:46:47.523 ERROR (MainThread) [aiohttp.server] Error handling request
Traceback (most recent call last):
File "/usr/local/lib/python3.11/site-packages/aiohttp/web_protocol.py", line 332, in data_received
messages, upgraded, tail = self._request_parser.feed_data(data)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "aiohttp/_http_parser.pyx", line 551, in aiohttp._http_parser.HttpParser.feed_data
aiohttp.http_exceptions.BadStatusLine: 400, message="Bad status line 'Expected CRLF after version'"
2023-07-06 09:46:47.533 DEBUG (MainThread) [custom_components.tapo.coordinators] Finished fetching tapo data in 0.235 seconds (success: True)
2023-07-06 09:46:47.638 DEBUG (MainThread) [custom_components.tapo.coordinators] Finished fetching tapo data in 0.242 seconds (success: True)
2023-07-06 09:46:47.686 DEBUG (MainThread) [custom_components.tapo.coordinators] Finished fetching tapo data in 0.244 seconds (success: True)
2023-07-06 09:46:48.419 ERROR (MainThread) [aiohttp.server] Error handling request
Traceback (most recent call last):
File "/usr/local/lib/python3.11/site-packages/aiohttp/web_protocol.py", line 332, in data_received
messages, upgraded, tail = self._request_parser.feed_data(data)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "aiohttp/_http_parser.pyx", line 551, in aiohttp._http_parser.HttpParser.feed_data
aiohttp.http_exceptions.BadStatusLine: 400, message="Bad status line 'Expected CRLF after version'"
2023-07-06 09:46:48.510 ERROR (MainThread) [aiohttp.server] Error handling request
Traceback (most recent call last):
File "/usr/local/lib/python3.11/site-packages/aiohttp/web_protocol.py", line 332, in data_received
messages, upgraded, tail = self._request_parser.feed_data(data)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "aiohttp/_http_parser.pyx", line 551, in aiohttp._http_parser.HttpParser.feed_data
aiohttp.http_exceptions.BadStatusLine: 400, message="Bad status line 'Expected CRLF after version'"
2023-07-06 09:46:49.431 DEBUG (MainThread) [custom_components.tapo.coordinators] Finished fetching tapo data in 0.038 seconds (success: True)
2023-07-06 09:46:49.444 ERROR (MainThread) [aiohttp.server] Error handling request
Traceback (most recent call last):
File "/usr/local/lib/python3.11/site-packages/aiohttp/web_protocol.py", line 332, in data_received
messages, upgraded, tail = self._request_parser.feed_data(data)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "aiohttp/_http_parser.pyx", line 551, in aiohttp._http_parser.HttpParser.feed_data
aiohttp.http_exceptions.BadStatusLine: 400, message="Bad status line 'Expected CRLF after version'"
2023-07-06 09:46:49.528 ERROR (MainThread) [aiohttp.server] Error handling request
Traceback (most recent call last):
File "/usr/local/lib/python3.11/site-packages/aiohttp/web_protocol.py", line 332, in data_received
messages, upgraded, tail = self._request_parser.feed_data(data)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "aiohttp/_http_parser.pyx", line 551, in aiohttp._http_parser.HttpParser.feed_data
aiohttp.http_exceptions.BadStatusLine: 400, message="Bad status line 'Expected CRLF after version'"
2023-07-06 09:46:50.455 ERROR (MainThread) [aiohttp.server] Error handling request
Traceback (most recent call last):
File "/usr/local/lib/python3.11/site-packages/aiohttp/web_protocol.py", line 332, in data_received
messages, upgraded, tail = self._request_parser.feed_data(data)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "aiohttp/_http_parser.pyx", line 551, in aiohttp._http_parser.HttpParser.feed_data
aiohttp.http_exceptions.BadStatusLine: 400, message="Bad status line 'Expected CRLF after version'"
2023-07-06 09:46:50.533 ERROR (MainThread) [aiohttp.server] Error handling request
Traceback (most recent call last):
File "/usr/local/lib/python3.11/site-packages/aiohttp/web_protocol.py", line 332, in data_received
messages, upgraded, tail = self._request_parser.feed_data(data)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "aiohttp/_http_parser.pyx", line 551, in aiohttp._http_parser.HttpParser.feed_data
aiohttp.http_exceptions.BadStatusLine: 400, message="Bad status line 'Expected CRLF after version'"
2023-07-06 09:46:51.441 ERROR (MainThread) [aiohttp.server] Error handling request
Traceback (most recent call last):
File "/usr/local/lib/python3.11/site-packages/aiohttp/web_protocol.py", line 332, in data_received
messages, upgraded, tail = self._request_parser.feed_data(data)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "aiohttp/_http_parser.pyx", line 551, in aiohttp._http_parser.HttpParser.feed_data
aiohttp.http_exceptions.BadStatusLine: 400, message="Bad status line 'Expected CRLF after version'"
2023-07-06 09:46:51.516 ERROR (MainThread) [aiohttp.server] Error handling request
Traceback (most recent call last):
File "/usr/local/lib/python3.11/site-packages/aiohttp/web_protocol.py", line 332, in data_received
messages, upgraded, tail = self._request_parser.feed_data(data)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "aiohttp/_http_parser.pyx", line 551, in aiohttp._http_parser.HttpParser.feed_data
aiohttp.http_exceptions.BadStatusLine: 400, message="Bad status line 'Expected CRLF after version'"
2023-07-06 09:46:52.445 ERROR (MainThread) [aiohttp.server] Error handling request
Traceback (most recent call last):
File "/usr/local/lib/python3.11/site-packages/aiohttp/web_protocol.py", line 332, in data_received
messages, upgraded, tail = self._request_parser.feed_data(data)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "aiohttp/_http_parser.pyx", line 551, in aiohttp._http_parser.HttpParser.feed_data
aiohttp.http_exceptions.BadStatusLine: 400, message="Bad status line 'Expected CRLF after version'"
2023-07-06 09:46:52.525 ERROR (MainThread) [aiohttp.server] Error handling request
Traceback (most recent call last):
File "/usr/local/lib/python3.11/site-packages/aiohttp/web_protocol.py", line 332, in data_received
messages, upgraded, tail = self._request_parser.feed_data(data)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "aiohttp/_http_parser.pyx", line 551, in aiohttp._http_parser.HttpParser.feed_data
aiohttp.http_exceptions.BadStatusLine: 400, message="Bad status line 'Expected CRLF after version'"
2023-07-06 09:46:55.998 ERROR (MainThread) [aiohttp.server] Error handling request
Traceback (most recent call last):
File "/usr/local/lib/python3.11/site-packages/aiohttp/web_protocol.py", line 332, in data_received
messages, upgraded, tail = self._request_parser.feed_data(data)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "aiohttp/_http_parser.pyx", line 551, in aiohttp._http_parser.HttpParser.feed_data
aiohttp.http_exceptions.BadStatusLine: 400, message="Bad status line 'Expected CRLF after version'"
2023-07-06 09:46:56.008 ERROR (MainThread) [aiohttp.server] Error handling request
Traceback (most recent call last):
File "/usr/local/lib/python3.11/site-packages/aiohttp/web_protocol.py", line 332, in data_received
messages, upgraded, tail = self._request_parser.feed_data(data)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "aiohttp/_http_parser.pyx", line 551, in aiohttp._http_parser.HttpParser.feed_data
aiohttp.http_exceptions.BadStatusLine: 400, message="Bad status line 'Expected CRLF after version'"
2023-07-06 09:46:56.009 ERROR (MainThread) [aiohttp.server] Error handling request
Traceback (most recent call last):
File "/usr/local/lib/python3.11/site-packages/aiohttp/web_protocol.py", line 332, in data_received
messages, upgraded, tail = self._request_parser.feed_data(data)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "aiohttp/_http_parser.pyx", line 551, in aiohttp._http_parser.HttpParser.feed_data
aiohttp.http_exceptions.BadStatusLine: 400, message="Bad status line 'Expected CRLF after version'"
2023-07-06 09:46:56.012 ERROR (MainThread) [aiohttp.server] Error handling request
Traceback (most recent call last):
File "/usr/local/lib/python3.11/site-packages/aiohttp/web_protocol.py", line 332, in data_received
messages, upgraded, tail = self._request_parser.feed_data(data)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "aiohttp/_http_parser.pyx", line 551, in aiohttp._http_parser.HttpParser.feed_data
aiohttp.http_exceptions.BadStatusLine: 400, message="Bad status line 'Expected CRLF after version'"
2023-07-06 09:46:56.014 ERROR (MainThread) [aiohttp.server] Error handling request
Traceback (most recent call last):
File "/usr/local/lib/python3.11/site-packages/aiohttp/web_protocol.py", line 332, in data_received
messages, upgraded, tail = self._request_parser.feed_data(data)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "aiohttp/_http_parser.pyx", line 551, in aiohttp._http_parser.HttpParser.feed_data
aiohttp.http_exceptions.BadStatusLine: 400, message="Bad status line 'Expected CRLF after version'"
2023-07-06 09:46:56.017 ERROR (MainThread) [aiohttp.server] Error handling request
Traceback (most recent call last):
File "/usr/local/lib/python3.11/site-packages/aiohttp/web_protocol.py", line 332, in data_received
messages, upgraded, tail = self._request_parser.feed_data(data)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "aiohttp/_http_parser.pyx", line 551, in aiohttp._http_parser.HttpParser.feed_data
aiohttp.http_exceptions.BadStatusLine: 400, message="Bad status line 'Expected CRLF after version'"
2023-07-06 09:46:56.443 ERROR (MainThread) [aiohttp.server] Error handling request
Traceback (most recent call last):
File "/usr/local/lib/python3.11/site-packages/aiohttp/web_protocol.py", line 332, in data_received
messages, upgraded, tail = self._request_parser.feed_data(data)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "aiohttp/_http_parser.pyx", line 551, in aiohttp._http_parser.HttpParser.feed_data
aiohttp.http_exceptions.BadStatusLine: 400, message="Bad status line 'Expected CRLF after version'"
2023-07-06 09:46:56.527 ERROR (MainThread) [aiohttp.server] Error handling request
Traceback (most recent call last):
File "/usr/local/lib/python3.11/site-packages/aiohttp/web_protocol.py", line 332, in data_received
messages, upgraded, tail = self._request_parser.feed_data(data)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "aiohttp/_http_parser.pyx", line 551, in aiohttp._http_parser.HttpParser.feed_data
aiohttp.http_exceptions.BadStatusLine: 400, message="Bad status line 'Expected CRLF after version'"
2023-07-06 09:46:57.421 ERROR (MainThread) [aiohttp.server] Error handling request
Traceback (most recent call last):
File "/usr/local/lib/python3.11/site-packages/aiohttp/web_protocol.py", line 332, in data_received
messages, upgraded, tail = self._request_parser.feed_data(data)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "aiohttp/_http_parser.pyx", line 551, in aiohttp._http_parser.HttpParser.feed_data
aiohttp.http_exceptions.BadStatusLine: 400, message="Bad status line 'Expected CRLF after version'"
2023-07-06 09:46:57.515 ERROR (MainThread) [aiohttp.server] Error handling request
Traceback (most recent call last):
File "/usr/local/lib/python3.11/site-packages/aiohttp/web_protocol.py", line 332, in data_received
messages, upgraded, tail = self._request_parser.feed_data(data)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "aiohttp/_http_parser.pyx", line 551, in aiohttp._http_parser.HttpParser.feed_data
aiohttp.http_exceptions.BadStatusLine: 400, message="Bad status line 'Expected CRLF after version'"
2023-07-06 09:46:58.443 ERROR (MainThread) [aiohttp.server] Error handling request
Traceback (most recent call last):
File "/usr/local/lib/python3.11/site-packages/aiohttp/web_protocol.py", line 332, in data_received
messages, upgraded, tail = self._request_parser.feed_data(data)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "aiohttp/_http_parser.pyx", line 551, in aiohttp._http_parser.HttpParser.feed_data
aiohttp.http_exceptions.BadStatusLine: 400, message="Bad status line 'Expected CRLF after version'"
2023-07-06 09:46:58.515 ERROR (MainThread) [aiohttp.server] Error handling request
Traceback (most recent call last):
File "/usr/local/lib/python3.11/site-packages/aiohttp/web_protocol.py", line 332, in data_received
messages, upgraded, tail = self._request_parser.feed_data(data)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "aiohttp/_http_parser.pyx", line 551, in aiohttp._http_parser.HttpParser.feed_data
aiohttp.http_exceptions.BadStatusLine: 400, message="Bad status line 'Expected CRLF after version'"
2023-07-06 09:46:59.460 ERROR (MainThread) [aiohttp.server] Error handling request
Traceback (most recent call last):
File "/usr/local/lib/python3.11/site-packages/aiohttp/web_protocol.py", line 332, in data_received
messages, upgraded, tail = self._request_parser.feed_data(data)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "aiohttp/_http_parser.pyx", line 551, in aiohttp._http_parser.HttpParser.feed_data
aiohttp.http_exceptions.BadStatusLine: 400, message="Bad status line 'Expected CRLF after version'"
2023-07-06 09:46:59.537 ERROR (MainThread) [aiohttp.server] Error handling request
Traceback (most recent call last):
File "/usr/local/lib/python3.11/site-packages/aiohttp/web_protocol.py", line 332, in data_received
messages, upgraded, tail = self._request_parser.feed_data(data)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "aiohttp/_http_parser.pyx", line 551, in aiohttp._http_parser.HttpParser.feed_data
aiohttp.http_exceptions.BadStatusLine: 400, message="Bad status line 'Expected CRLF after version'"

I have the same problem.

I'm not sure about all your exceptions, but your symptoms match #423

I'm not sure about all your exceptions, but your symptoms match #423

Yes, you are right

yes same issue. Will try the fix.
On Thu, 6 Jul 2023, 10:41 Simon Roberts, @.***> wrote:

I'm not sure about all your exceptions, but your symptoms match #423
https://github.com/petretiandrea/home-assistant-tapo-p100/issues/423
—
Reply to this email directly, view it on GitHub
https://github.com/petretiandrea/home-assistant-tapo-p100/issues/425#issuecomment-1623359811,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AYRF456FI3YOJGMDWLT64HDXO2B3DANCNFSM6AAAAAA2ADTXOY
.
You are receiving this because you authored the thread.Message ID:
@.***>

same problem here

Fix in #423


text:
Add P125M switch support

Looks like it just needed an entry in const.py!

I tried it, it did not work. It still doesn't show the load.

This just added support for core switching functionality, not load. I couldn't get that working either.

By load I mean switch control.  (Switching of the load).  I only see two items overload and wifi signal.

By load I mean switch control. (Switching of the load). I only see two items overload and wifi signal.

Oh I see. That may have to do with how you load custom components. To get this working for me I had to manually edit the file. I didn't touch the repo or anything. And then I restarted the server. I'm unsure how to do this more legitimately and it's  probably different across setups (docker, hass OS, etc).

Yep, that fixed it.

By load I mean switch control. (Switching of the load). I only see two items overload and wifi signal.

Oh I see. That may have to do with how you load custom components. To get this working for me I had to manually edit the file. I didn't touch the repo or anything. And then I restarted the server. I'm unsure how to do this more legitimately and it's probably different across setups (docker, hass OS, etc).

I'm running with the same issue. What file more specifically you had to edit to make it work?

source: gharchive/pull-request

authors: cfurini irubnich wash3re

license: MIT

license_type: permissive

license_source: github-api


text:
Not all alarm_control_panel entities shown

hi! I'm struggling to have all my alarm_control_panel entities get listed in the device control list. I'm running the latest version of hikaxpro_hacs (2.1.5), home assist and HACS.
below is a screenshot of the Hikvison pro control unit:

As you can see there are 7 devices (movement sensors) connected, but only 5 are listed in the "controls". I've searched everywhere within Home Assist, and all entities of the 2 sensors seem to be listed, except the alarm_control_panel entities. Maybe someone here has a suggestion of what it could be? Below 2 screenshots of the sensors that, as far as I know, are exactly the same.

Controls are "zones" of your "AXPro".
Under it you have connected devices. Devices != zones.
The terminology is important.
You will not see every device as zone because zone can have multiple devices. You can configure this in your hikvision app or in Web interface of "AXPro".

ok thanks for the reply @petrleocompel !
Check, I'm mixing up terminology. But I've configured the 2 living room sensors to be in the living room zone, and from the Hikvision app I can control them. But the alarm control entities for this area/zone don't show up in Hikvision, while they do for all others. Sorry to bother you this way, but I'm quite puzzled and stuck with this now.

You are still looking on "alarm_control_panel" aka "Zones" and you are looking on Entity tabs...
Just look on "devices" filter integration from "hikvision ax-pro".

hey, thanks again.
I guess that is the point I try to make. The 2 living room sensors do show up in the device list, but I somehow can't make the link to arm them

??? Living room sensor A and B ? are there.. 🤔
What sensors ?  what kind of sensors?

motion and temperature sensors. Somehow the arm status and the temperature are picked up, but I cant arm them.

If there is motion in front of the motion sensor you will not be able to arm them.
You can check the hikvision app why you cannot arm the zone it would tell you if you press "diagnose button".
I am trying my best to understand but. You cannot "arm them"?

I can the "living room" from my Hickvision app, so that works. I can't arm this zone/region in HA because arming the living room is not show in the dashboard.

You have there office twice and one entity ID is living room second one office.
Still think it is your naming of problem.

aha! YES! That's the problem, somewhere I mixed that up.
Thanks! sorry again for bothering you with this one, next time I'll report a real bug! :)

hey, just to clarify my confusion. I've been struggling with this a bit longer, and it looks like I had 2 zones of 2 different alarm systems wrongly mixed up in home assistant. This explains why renaming certain devices had strange like renaming other devices also. After deleting and re-adding all devices everything worked as expected.
Thanks again for your time thinning with me.

source: gharchive/issue

authors: gijzelaerr petrleocompel


text:
Nextgh - The scraper takes one job from Moldova

ENVIROMENT: production
URL: https://scrapers.peviitor.ro/src/nextgh/index.html
Browser: Chrome
OS: Windows 10
STEPS TO REPRODUCE:

Open URL in browser
Click on 'Run Scraper' button
Check the Backend Developer (Node.js + Vue.js)

EXPECTED RESULTS:
The scraper only takes jobs from Romania
ACTUAL RESULTS:
The scraper takes one job from Moldova

Deprecated!

authors: AdiVanca lalalaurentiu


text:
"Limanu", "Hagieni" are listed in the drop-down menu

Description:
When user writes "Limanu", "Hagieni" the location appears in the drop-down menu next to the comune and the county which is a part according to the law
Precondition:
The website is up an running.

Step 1
Write in the search bar "Limanu"

Expected results
The location appears in the drop-down menu as "Sat Limanu, CONSTANȚA, (Limanu)"

Step 2
Press "x" button.

Expected results
The location was deleted from the search bar.

Step 3
Write in the search bar "Hagieni"

Expected results
The location appears in the drop-down menu as "Sat Hagieni, CONSTANȚA, (Limanu)"


text:
TC Dropdown "Personale Nr. joburi nepublicate (desc)" functionality

Description: Verify if selecting "Personale Nr. joburi nepublicate (desc)" from the dropdown list, leads to a specific page.
Preconditions: Go to https://admin.peviitor.ro/

Step 1: Navigate to the "Companii" page.
Expected result: The "Companii" page is available.

Step 2: Click on the dropdown component.
Expected result: The option is selectable.

repo: peviitor-ro/validator-ui


text:
Fix pylint check issues introduced in #165

This PR fixes some pylint complaints about rotary encoder code. Not sure how they got missed before #165 was merged in.

Interesting, I'm curious why it was not caught in build checks after I pushed it.

repo: pez-globo/pufferfish-vent-software


text:
Contribution guide and development policy

This PR adds a contribution guide and development policy to the document.

Codecov Report

Merging #87 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master      #87   +/-   ##
=======================================
  Coverage   68.35%   68.35%
=======================================
  Files          58       58
  Lines        2067     2067
=======================================
  Hits         1413     1413
  Misses        654      654

If possible, it may be nice to mention below briefly.

we recommend developers to follow flake8 & pep but it is not mandatory.
https://docs.chainer.org/en/stable/contribution.html#coding-guidelines
we use Google style docstring
http://sphinxcontrib-napoleon.readthedocs.io/en/latest/example_google.html

we recommend developers to follow flake8 & pep but it is not mandatory.

Could you discuss if we should ask developers to follow it?

LGTM.

LGTM!

authors: codecov-io corochann delta2323 mottodora

repo: pfnet-research/chainer-chemistry


text:
Fix an example for tensorflow==1.15.0.

examples/tensorflow_eager_simple.py fails in Python 2.7 and 3.7 since tensorflow==1.15.0 has been released.
[W 2019-10-17 15:12:58,389] Setting status of trial#0 as TrialState.FAIL because of the following error: AttributeError("'module' object has no attribute 'metrics'",)
Traceback (most recent call last):
  File "/home/circleci/project/venv/lib/python2.7/site-packages/optuna/study.py", line 503, in _run_trial
    result = func(trial)
  File "examples/tensorflow_eager_simple.py", line 118, in objective
    learn(model, optimizer, train_ds, 'train')
  File "examples/tensorflow_eager_simple.py", line 71, in learn
    accuracy = tfe.metrics.Accuracy('accuracy', dtype=tf.float32)
AttributeError: 'module' object has no attribute 'metrics'
WARNING:tensorflow:From examples/tensorflow_eager_simple.py:66: The name tf.train.AdamOptimizer is deprecated. Please use tf.compat.v1.train.AdamOptimizer instead.

I'm not sure but the cause seems to be the change of the package structure related to tensorflow.contrib. When I change the way to import tensorflow.contrib.eager, examples/tensorflow_eager_simple.py can be successfully executed.

Thanks for the PR. I couldn't reproduce the error locally on my macOS Python 3.7.4 so cannot verify the fix but the changes LGTM!

authors: hvy toshihikoyanase

repo: pfnet/optuna


text:
Issue #294 Finish app styling WIP

Let's get the ball rolling on this PR. This commit: d1fbc3a is likely to be the most significant change for this story and represents the new look of the Task Detail screen. See #294 for links to designs for Task Detail.
Note: I realize the path to the new task detail services screen isn't the most natural. I think we'll likely want a pattern like task/:taskId/services but I need to rejig the parameter substitution function to get this working so I've left it like task-services/:taskId for the time being.

I only have very minor comments on this PR. I want to get this in so that we get lined up for Friday, so I'm merging it now. If you want to address some of these comments and you have time, then you can do that in a new PR under the same story.

authors: bensinjin rasmus-storjohann-PG

repo: pg-irc/pathways-frontend

license_source: bigquery


text:
Error: DEPTH_ZERO_SELF_SIGNED_CERT - when running test

I am using 10.38 node.js , do you know why I got this ?
thanks in advance,
Running "mochaTest:test" (mochaTest) task
17  -----------,------,
3   -----------|   /_/
0   -----------^|__( o .o)
-----------  ""  ""
✖ 3 of 31 tests failed:

Server once started should accept TLS connections on the configured port, assign an external port for forwarding and emit an event:
Error: DEPTH_ZERO_SELF_SIGNED_CERT
at SecurePair. (tls.js:1381:32)

I think this commit was supposed to work around problems with self signed certs.
https://github.com/pghalliday/tls-tunnel/commit/d42f63ae37a08d87cccd9936b5671b53a24787bf
maybe you found another problem - i can't check now though. Maybe tomorrow

authors: pghalliday smartmouse

repo: pghalliday/tls-tunnel

license: mit


text:
Add support for x-doctest-options

Resolves #9
I could still implement "magical" addition of -fobject-code if there is declared use of UnboxedTuples extension; but this approach seems more future proof and less magical.

test-suite doctests
  type:           exitcode-stdio-1.0
  main-is:        doctests.hs
  ghc-options:    -Wall -threaded
  hs-source-dirs: tests
  default-language: Haskell2010

  x-doctest-options: -fobject-code

  if !flag(test-doctests)
    buildable: False
  else
    build-depends:
      base,
      directory >= 1.0,
      doctest >= 0.9.1,
      filepath,
      parallel

I like it!
The code looks fine, but we need to document this feature somewhere, like in the Haddocks and/or README.

authors: RyanGlScott phadej

repo: phadej/cabal-doctest


text:
Add assiginees to pull requests

closes #248

@iphydf

@phadej no idea how to fix that last test. Sorry mate!

@GrayHatter I'll check this next week, and try to wrap up the release. Thanks!

@phadej thank you sir, ping me if you need anything else!

Any news here?

I'm investigating one mailfunction in our internal service. After that I'll go thru prs and issues and hopefully cut 0.15.0 today.

done in #251

authors: GrayHatter iphydf phadej

repo: phadej/github


text:
Applied fixes from StyleCI

This pull request applies code style fixes from an analysis carried out by StyleCI.

For more information, click here.

Hi,
I am a laravel developer. I have 2 yrs of experience in that i have 7
months of laravel experience. Want to join and work your project. If you
have any task please give me. I never work before in open source community.
I am very much interested to work with you.
Regards,
Hemraj Solanki
On Dec 27, 2015 7:37 PM, "Phan An" notifications@github.com wrote:

This pull request applies code style fixes from an analysis carried out by
StyleCI https://styleci.io.
For more information, click here https://styleci.io/analyses/qJ3pnz.
You can view, comment on, or merge this pull request online at:
https://github.com/phanan/koel/pull/147
Commit Summary

Applied fixes from StyleCI

File Changes

M app/Exceptions/Handler.php
https://github.com/phanan/koel/pull/147/files#diff-0 (4)

Patch Links:

https://github.com/phanan/koel/pull/147.patch
https://github.com/phanan/koel/pull/147.diff

—
Reply to this email directly or view it on GitHub
https://github.com/phanan/koel/pull/147.

repo: phanan/koel


text:
🛑 proxy index is down

In 71a688b, proxy index (https://index.phantomic.live/) was down:

HTTP code: 403
Response time: 418 ms

Resolved: proxy index is back up in 92eb248 after 10 minutes.


text:
platform agnostic for file path definition, to fix gulp-wrap-amd/issues/...

I have come up with solid solution to unify the platform filepath delimiter. It passes all tests. Do I need to add a test case for it?

A test case is needed for this.  I will probably be adding appveyor for windows testing also.

are you using split and join to avoid the global regex for a .replace?

First reason, 'templates\\application'.replace('\\', '/'), I was not sure that it would work as I expect because \\ look at skip '' or just double ''.
Second, using path.sep guarantee it would be platform agnostic, window, mac, firefox os, whatever... because node would pick up the platform and fill the value for the variable.
Third, I do not have a window computer to test it. l blind coded. :)

OK. Time to write some tests. :) after I play with new shining io.js

I am trying to write a test for the feature but I could not come up with a smart solution.
Here is what I need to test:  ( Testing the opts.name )
    opts.name = path.relative(opts.moduleRoot, opts.file.path).slice(0, -path.extname(opts.file.path).length);
    // platform agnostic for file path definition
    opts.name = opts.name.split(path.sep).join('/');

This is what I have currently: comment my question inside
test('should have a definition name with "/" separated path', function(t) {
  t.plan(1);

  gulp.src(filename)
    .pipe(task({
      moduleRoot: 'fixtures/',
      modulePrefix: 'rocks',

      // passing the `file.path` won't work, because it is caught inside
      // `opts.name = path.relative(opts.moduleRoot, opts.file.path).slice(0, -path.extname(opts.file.path).length);`
     // opts.file.path is always the value of what is `fixtures/helloworld` is being read from the disc.
      // I am using `mac` and do not have windows computer to test
     // How could I simulate or hard code the `opts.file.path` value in the test???

      file: {
        path: 'C:\\Windows\\wrapamd\\fixtures\\template\\helloworld1'
      }
    }))
    .pipe(expectStream(t, {
      name: 'rocks/helloworld1'
    }));
});

I don't think the expectStream pattern will work here, we will have to have a precompiled template with / instead of \\ and then run against windows (appveyor)

It sounds like that we could not do anything at this moment to get the test running unless that we have a physical windows machine to test the feature.
What do you want to do this PR?
Do you think it is safe to merge it and then we roll in the additional tests whenever windows server is ready?

I will hook up appveyor CI when we have a passing test

Sounds good. Thanks. Have a good weekend!

I wrote the failing test and ran it on appveyor - see https://ci.appveyor.com/project/phated/gulp-wrap-amd/build/2

Just merged your PR and the test, appveyor is running to make sure it's fixed and the test works.

Tests passing! https://ci.appveyor.com/project/phated/gulp-wrap-amd/build/3 Thanks!

Sweet!
The test's implementation is straight forward and is definitely inspired me to think further. ( well, I did not come out anything yesterday. )
I look at the line here. It needs one additional file ./expect/helloworld.js to read for comparing.
Here is something similar but one less file to create/read
t.equals(!!~String(file.contents).indexOf("rocks/helloworld"), true);

I am going to submit another PR. Take it or leave it, it is totally up to you.
Current implementation works just fine.

authors: mattma phated

repo: phated/gulp-wrap-amd


text:
Not all icons are rendered

I just followed the setup instructions of version 0.4.0. Some of the icons in the UI are not rendered correctly. Is there something I need to set up to make it work?

Interestingly, only the icon of the active item in this element is rendered.

When an icon has the class lsb the icon does not render correctly. When I remove the lsb class it renders fine.
Not sure if removing the class altogether is the right solution here, waiting for @cblavier's input here.

It's also the icons in the sidebar that aren't rendering correctly for me.

From my investigation, it's because the lsb class defines a font-family property which cascades down to the icon element and overrides the font-family of the fa-* classes. When I added !important to the fa-* font-family property, the icons render properly.

Hi all, thanks for your feedback !
There is indeed an issue, I made a design choice that turns out to be a wrong one 😅
Since you can customize all icons (including the theme picker referenced in #112) provided to the storybook with custom CSS classes (with the tuple {:fa, icon, style, css} I wanted the CSS bit to be interpreted within your sandbox. But it obviously raises more issues than it solves.
To fix this I think I will:

remove CSS sandbox around user provided icons (sidebar, tabs & theme picker)
correct the icons.md guide to let people know they must style their icons with storybook CSS classes (prefixed with  lsb-)
make sure the css bundled with storybook packages enough Tailwind styles to fit most icon styling use cases (w-* h-* p-* m-* and text-colors)

Until then, you can avoid overriding FontAwesome font-family with:
/* instead of * { ... } */
:not(i) {
  font-family: ...
}

WDYT?

Sounds good to me!

authors: benregn cblavier matthieuchabert woylie


text:
RC Test: Blackbody Spectrum 1.0.0-rc.3

@ariel-phet , @DianaTavares, @KatieWoe, blackbody-spectrum/1.0.0-rc.3 is ready for RC testing. This is a phet brand spot check. Document issues in https://github.com/phetsims/blackbody-spectrum/issues and link to this issue.
Assigning to @ariel-phet for prioritization.

General RC Test

What to Test

Click every single button.
Test all possible forms of input.

Test all mouse/trackpad inputs.
Test all touchscreen inputs.

If there is sound, make sure it works.
Make sure you can't lose anything.
Play with the sim normally.
Try to break the sim.
Test all query parameters on all platforms. (See QA Book for a list of query parameters.)
Download HTML on Chrome and iOS.
Make sure the iFrame version of the simulation is working as intended on all platforms.
Make sure the XHTML version of the simulation is working as intended on all platforms.
Complete the test matrix.
Don't forget to make sure the sim works with Legends of Learning.
Check this LoL spreadsheet and notify AR or AM if it not there.
If this is rc.1 please do a memory test.
When making an issue, check to see if it was in a previously published version

Issues to Verify

[ ] "K" should be translatable
[ ] Short strings should not be centered
[ ] Make the gray saved lines 1pt thinner

These issues should have the "status:ready-for-qa" label. Check these issues off and close them if they are fixed. Otherwise, post a comment in the issue saying that it wasn't fixed and link back to this issue. If the label is "status:ready-for-review" or "status:fixed-pending-deploy" then assign back to the developer when done, even if fixed.

Link(s)

Simulation
iFrame
XHTML
Test Matrix
Legends of Learning Harness

FAQs for QA Members

There are multiple tests in this issue... Which test should I do first?
Test in order! Test the first thing first, the second thing second, and so on.

How should I format my issue?
Here's a template for making issues:
  Test Device

  blah

  Operating System

  blah

  Browser

  blah

  Problem Description

  blah

  Steps to Reproduce

  blah

  Visuals

  blah

  Troubleshooting Information

  blah

Who should I assign?
We typically assign the developer who opened the issue in the QA repository.

My question isn't in here... What should I do?
You should:

Consult the QA Book.
Google it.
Ask Katie.
Ask a developer.
Google it again.
Cry.

Publishing sims is always good :). Marking high priority

QA is done

Sim is published, thanks everyone!

authors: KatieWoe ariel-phet arnabp

repo: phetsims/QA


text:
Added more specific instructions for nightly

@phil-opp might want to consider putting the -Z pre-linker flags in cargo.toml instead of passing it in manually

Thanks for the PR, @Immortalin! Not everyone wants to use nightly by default :).
bors r+

might want to consider putting the -Z pre-linker flags in cargo.toml instead of passing it in manually

I didn't know this was possible. However, we no longer need it in the following posts, so using the command line flag makes more sense to me in this case.

@phil-opp merge and close?

Seems like Travis timed out. Let's try again:
bors r+

Hmm, looks like bors still fails. Merging manually.
Sorry for the delay @Immortalin!

authors: Immortalin phil-opp


text:
MAKE the "Create Researvation" where users can Upload PDF Files.... (preferred nga mudisplay sad ang PDF file sa Preview section)

MAKE the "Create Researvation" where users can Upload PDF Files.... (preferred nga mudisplay sad ang PDF file sa Preview section)

Able to upload PDF files.. and can be previewed ... I like the PDF viewer as preview...


text:
Incorrect number / timeout

With just email and password set, the app only retrieves 181 vines. With --likes set, it times out. I have 995 posts and 11,940 likes.

Unable to reproduce without your Vine user name. Maybe you should try the --list option.

--list still gives me 181 vines. My user ID is 996123084295905280.

Vine api is not responding anymore, so I"m closing this.

authors: dotgodly phiphou

repo: phiphou/vine-backup


text:
is Transaction Ack Times correctly?

hello bro,
I trace the source ,when it comes to transaction-ack,i found that if a transaction is acked,add it in a block, so ,didn't a transaction should be acked 6times?
and every transaction create a block?
and ,I do not trace the source totally, just in transaction ack, I wonder if the sample is like bitcoin totally, the logic is complete to what the bitcoin is

I'm not sure I understand the question.

thx for replay ,I'm not good at English, I will trace the source code for more information, thx so much!!!!

No problem, if you can give me an example in code (our universal language) it may be easier for me to understand.


text:
Remove Removex

Hi, I tried the Removex link, but it seems broken.
https://removex.io/

There's also these lists of link that doesn't work anymore:

Day-O
Fmail Light
Switch Host
Monal

repo: phmullins/awesome-macos


text:
Fix Cannot read property 'replace' of undefined

Resolves issue #212

I can confirm: this fixed my problem! Thank you!

5.0.13 fixes this problem already I believe.
I assume you encountered this in a Cordova project?
If so, can you do a cd platforms/ios/cordova && npm install ios-sim@latest from #212 to see if that fixes the problem

This does indeed fix this problem but I have to redo this every time I delete the platform

Yup I know, see #210 for an interim platform you can download until the new platform release comes out. I was wondering more whether this fix in this PR is for a similar, but different problem

Thanks mate!

Can confirm that this PR fixes the issue.

When this will be merged with cordava ?
We should not face this issue again , research & add this patch .

This needs to be merged, please merge it. It passed all checks and for sure fixes the issue.
Thanks

See https://github.com/phonegap/ios-sim/pull/213#issuecomment-308561256
5.0.13 and cordova-ios@4.5.0 fixes this. Confirm this in your tests.
I'm not going to pull in a fix if its already fixed.

Nice little fix! Updating the the ios-sim version didn't worked for me so I searched for another solution and yours worked 👍

@shazron I don't know but I used Terminal to download it, following the Getting Started Guide.
I'm new to GitHub, sorry

I think the issue is already solved and we can close this one. If not then please explain asap.

authors: Hirbod ThomasHambach brodybits devansh1110 eykjs lakinmohapatra shazron thomas-alrek

repo: phonegap/ios-sim


text:
Phaser.Text is using Object.assign, which is an ES6 feature

This Issue is about (delete as applicable)

Compatibility with older browsers

Without any polyfill, this will fail on some older browsers (e.g. Android 4.4 default browser/webview).
We should change the use of Object.assign to Phaser.Util.extend instead.

As of #83 is merged, this issue can be closed.

authors: Dreaded-Gnu kenfoo

repo: photonstorm/phaser-ce


text:
Phaser 3.4.0 - new animation event emit forever

The new animation event sprite.on('animationcomplete') should only emit once, but keep emiting forever.

Want to back this issue? Post a bounty on it! We accept bounties via Bountysource.

Can you provide a code example using JSBin or Codepen?

Agreed, as I can't replicate this yet. There must be some specific way to trigger it happening.

Seems fixed in dev build.
v3.4.1-beta
v3.4.0

Its fixed on 3.5.0, thanks!

authors: hexus murteira photonstorm samid737

repo: photonstorm/phaser


text:
'gameout' event doesn't get fired

Version

Phaser Version: 3.16.1

Operating system: Windows

Browser:

Description

Callback registered to the 'gameout' event via this.input.on(Phaser.Input.Events.GAME_OUT, callback) from a scene is never invoked when mouse leaves canvas or moves to an overlay. 'gameover' event works fine, though.
Example Test Code

Additional Information

I can confirm this too.

Same problem for me. macOS / Safari.

Thank you for submitting this issue. We have fixed this and the fix has been pushed to the master branch. It will be part of the next release. If you get time to build and test it for yourself we would appreciate that.

authors: BigZaphod RademCZ gammafp photonstorm


text:
renderTexture.fill() doesn't properly fill the texture

Version

Phaser Version: 16.1

Operating system: Window 10

Browser: Chrome

Description

When filling a renderTexture (with fill()), the fill doesn't appear at the right coordinates.
Example Test Code
It works in version 15.1, as can be seen in this fiddle, which shows the intended behavior.
It doesn't work properly in version 16.1 anymore, as can be seen in this fiddle (the black area should touch the white one).

Thank you for submitting this issue. We have fixed this and the fix has been pushed to the master branch. It will be part of the next release. If you get time to build and test it for yourself we would appreciate that.

23.0 is showing some more fill positioning issues https://jsfiddle.net/f2maodx9/

authors: Jerenaux LorenzoBoccaccia photonstorm


text:
Keep receiving the error 'Matrix is singular'

I'm using the LeastSquares library and I'm getting the error 'Matrix is singular'. To test I created a function with this code:
	for ($i=0; $i < 12; $i++) {
		$samples[] = [
			rand(200, 1000),
			rand(200, 1000),
			rand(200, 1000),
			rand(200, 1000),
			rand(200, 1000),
			rand(200, 1000),
			rand(200, 1000),
			rand(200, 1000),
			rand(200, 1000),
			rand(200, 1000),
			rand(200, 1000),
			rand(200, 1000),
			rand(200, 1000),
			rand(200, 1000),
			rand(200, 1000)
		];
		$targets[] = 1000;
	}

	$regression2 = new LeastSquares();
	$regression2->train($samples, $targets);

I wrote this code with random values only to test. Sometimes I get the error mentioned and sometimes I don't.

Sorry for this issue! All I had to do was study more math!

Hello.
How do you fix the error?
I have this one too.
Thank you.

How do you fix this error?
study more math!

authors: GustMartins Petyay p0on

repo: php-ai/php-ml


text:
Make underlying http client also public when configured

Q
A

Bug fix?
no

New feature?
yes

BC breaks?
no

Deprecations?
no

Related tickets
follow up of https://github.com/php-http/HttplugBundle/pull/280

Documentation
not needed

License
MIT

What's in this PR?
This makes the underlying http client also public when configured.
Why?
Something I didn't add in #280 but need when using mocks. This is needed for https://github.com/php-http/HttplugBundle/pull/286.
Checklist

[x] Updated CHANGELOG.md
[ ] Documentation: no need to update

i closed #286 because i don't see the use case. similar here, i don't see the use in having this internal service be public. if you really need it to be public for a special test setup, i suggest that you add a compiler pass in your application that finds the corresponding services and changes them to public after this bundle has defined them as private.

authors: dbu ruudk

repo: php-http/HttplugBundle


text:
Fix #518  - Properly saving Chat IDs

#518

I mean #518, now #513 - that was a mistake
I'm a noob at github :|

Thanks @no-nevis for this PR 👍

authors: no-nevis noplanman

repo: php-telegram-bot/core


text:
Perf: improve BdfTokenStream logic

Key changes:

Introduced a new method skipWhile() that doesn't make new allocations (unlike takeWhile(), which does with $taken).
One fewer call to $this->current() in takeWhile() on every iteration.

looks good, this library will be split into a separate package at some point. if you want to add a lib/bdf/tests/Benchmark/BdfParserBench.php or whatever feel free.
also note this probably isn't that performance sensitive. fonts should be loaded once and not on every cycle.

@dantleech Got it. That's sounds good. Sure! I'll add this test and let you know. :)

btw you can change the phpbench.json to sepcify multiple paths instead of one IIRC "path": ["test/Benchmark", "lib/bdf/tests/Benchmark"]

Bench results:
1: <current> 2: main

Table
=====

<current>
+----------------+-----------------------+---------+----------+----------+----------+--------+-----------+
| benchmark      | subject               | memory  | min      | max      | mode     | rstdev | stdev     |
+----------------+-----------------------+---------+----------+----------+----------+--------+-----------+
| BdfParserBench | benchParseRealFont () | 6.031mb | 35.239ms | 37.176ms | 35.443ms | ±2.09% | 753.487μs |
+----------------+-----------------------+---------+----------+----------+----------+--------+-----------+

main
+----------------+---------------------------+---------+----------+----------+----------+--------+-----------+
| benchmark      | subject                   | memory  | min      | max      | mode     | rstdev | stdev     |
+----------------+---------------------------+---------+----------+----------+----------+--------+-----------+
| BdfParserBench | benchParseRealFont ()     | 6.031mb | 38.240ms | 41.477ms | 39.279ms | ±2.42% | 960.798μs |
+----------------+---------------------------+---------+----------+----------+----------+--------+-----------+

Memory: Both versions use the same amount of memory (6.031mb).
Min: <current> is faster by 3.001ms (from 38.240ms down to 35.239ms).
Max: <current> is faster by 4.301ms (from 41.477ms down to 37.176ms).
Mode: <current> is faster by 3.836ms (from 39.279ms down to 35.443ms).
Rstdev: The <current> version is slightly more stable with a 2.09% relative standard deviation compared to 2.42% in the main.
Stdev: The standard deviation is lower in the <current> version by 207.311μs, indicating more consistent performance.

nice!

authors: KennedyTedesco dantleech

repo: php-tui/php-tui


text:
Blank screen after successfull promotion of a usergroup

Title says it all. Seems that there is a blank screen after the successfull promotion of a group. The group is saved and emails are send but the redirect doesn't seem to work. Has been reported by @stefanotorresi

This has been already fixed.


text:
phpdocumentor cant install in thread safe version php

i have try thread safe php5.5.25(the official zip package),pear install is ok,but when i install phpdocumentor ,i get an error,unable to unpack path_to_temp_pear_download\phpdocumentor-2.8.2.tgz.
and i have try all the non thread safe php version(the official zip package of 5.4、5.5、5.6)，all is success.
all of above is under win7 x64
is this a bug?or maybe i lost something?

Closing because these phpversions are not supported any more.
Feel free to open a new issue when applicable

authors: dilidilidi jaapio


text:
🛑 phpMyFAQ Password Hash Generator Tool is down

In afbce3a, phpMyFAQ Password Hash Generator Tool (https://password.phpmyfaq.de) was down:

HTTP code: 0
Response time: 0 ms

Resolved: phpMyFAQ Password Hash Generator Tool is back up in a4402d9.


text:
🛑 phpMyFAQ API is down

In d51930a, phpMyFAQ API (https://api.phpmyfaq.de/versions) was down:

HTTP code: 0
Response time: 0 ms

Resolved: phpMyFAQ API is back up in e5cb45a.


text:
🛑 phpMyFAQ Password Hash Generator Tool is down

In 078f5fa, phpMyFAQ Password Hash Generator Tool (https://password.phpmyfaq.de) was down:

HTTP code: 0
Response time: 0 ms

Resolved: phpMyFAQ Password Hash Generator Tool is back up in a03111b.


text:
🛑 phpMyFAQ Demo is down

In 6c062fe, phpMyFAQ Demo (https://demo.phpmyfaq.de) was down:

HTTP code: 0
Response time: 0 ms

Resolved: phpMyFAQ Demo is back up in 5ef765e after 4 minutes.


text:
Support calls to functions with variadic parameters

Type: bugfix
Breaking change: no
Previously this would often fail on usage of sprintf() and other function that takes variadic parameters.

@AJenbo thanks for your PR, do you have the possibility to add a test that failed before this PR and is fixed with this PR?
I assign this PR to you, but feel free to say if you need help creating the tests.

Sure, will try and get around to it some time this week.

Oh, I forgot all about this one. I'll try come up with a same that show the issue.

No fair you guys merged another fix for this just a month later, and the didn't even trace down what the cause was :joy:
https://github.com/phpmd/phpmd/pull/818

Codecov Report

Merging #814 (f8ca95f) into master (87a0822) will increase coverage by 0.00%.
The diff coverage is 100.00%.

@@            Coverage Diff            @@
##             master     #814   +/-   ##
=========================================
  Coverage     88.65%   88.65%
  Complexity     1055     1055
=========================================
  Files            95       95
  Lines          2661     2663    +2
=========================================
+ Hits           2359     2361    +2
  Misses          302      302

Impacted Files
Coverage Δ

src/main/php/PHPMD/Rule/AbstractLocalVariable.php
91.20% <100.00%> (+0.19%)
:arrow_up:

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

Ok, I added a test, removed the "be quiet" fix, and made this one more explicit as to what it is doing. Hope that makes it good enough to merge :)

Hi, thanks to this I discovered that a parameter can be both variadic and reference 🤯
The test is good as it's what also missed in #818 but I did not succeed to find a case that would explain why we need specific stuff for PHP < 5.6 or why min() solution is better than isset()
I tried:
#973
PHP 5.3 result
#974
PHP 5.3 result
By the way I added there a test for variadic+reference but current fixes still don't support it, so we need an other fix for that.
class Test
{
    public function foo(string $format, mixed &...$values): string
    {
        $values[1] = 9;

        return sprintf($format, ...$values);
    }

    public function bar()
    {
        $variadic1 = 1;
        $this->print("Text %d", $variadic1, $variadic2);

        return $variadic2;
    }
}

$t = new Test();

echo $t->bar();

Without PHP < 5.6 it will fail because isVeriadic() is only available from PHP 5.6. I chose to use || in case someone is trying to analyze PHP 5.6 code in 5.5. But we could also set it to fail in that case using && instead.
min() allows you to know that it was the variadic paramter, and will correctly let you know if it is by reference. isset() simply ignores it and says it's not by reference even if it is.
I think it also better allow you to realize why the count might be higher, rather then just ignoring a case that appears like it should never happen.

min() allows you to know that it was the variadic paramter, and will correctly let you know if it is by reference. isset() simply ignores it and says it's not by reference even if it is.

That's also what I believe reading the code but as you can see here it's still producing a violation: #973

@AJenbo can this be updated to be mergable into 3.0.0?

Sure, though there isn't anything BC in it.

authors: AJenbo codecov-commenter kylekatarnls ravage84 tvbeek

repo: phpmd/phpmd


text:
[WIP] Support Doctrine MongoDB ODM

Fixes #26.
This PR introduces compatibility with MongoDB ODM. A quick summary:

All Entity* classes have been replaced by corresponding Object* classes. To avoid BC breaks, existing classes remain but throw a silenced deprecation warning so people can update their code if they extend those classes
ObjectManagerGetRepositoryDynamicReturnTypeExtension takes a managerClass constructor argument to be able to return different repository class names for ODM and ORM. The service configuration was updated to contain all three mappings for doctrine/persistence, doctrine/orm and doctrine/mongodb-odm.
BC break: The doctrine.repositoryClass parameter was renamed to doctrine.orm.repositoryClass to better differentiate it from the other class names. This can be reversed, although I'm not sure of a good way to throw a deprecation notice for this.

Todos:

[ ] Update tests to cover MongoDB ODM as well
[ ] Document functionality
[x] Add type extension for Doctrine\Common\Persistence\ManagerRegistry

@alcaeus May we help you on this ?

I've put work on hold since there are other PRs achieving the same thing and I haven't received any feedback from @ondrejmirtes on how to proceed. I'm not working on this until those questions are resolved to avoid doing work for nothing.

authors: alcaeus alterphp

repo: phpstan/phpstan-doctrine


text:
[Question] Is it a way to show it using a req.param?

Now the context editor is always showed, is it a way to just show it using a request param? Or with a specific URL subpath?
As
http://domain.com/?phraseEditor=true

Hey @atellezsazo!
Yea, I guess you could enable Phrase ICE based on query parameter. I would probably look into Next.js docs for this. Here is an article I found about getting query params from next.js router - probably it would point you in the correct direction.
From the perspective of Phrase ICE you would just need to pass either true or false in the configuration object.
Closing the issue as it's not connected with the scope of this package, but rather Next.js/React itself.

authors: FRSgit atellezsazo


text:
cannot install php modules: invoke-rc.d: policy-rc.d denied execution

I've following docker file:
RUN apt-get update
RUN DEBIAN_FRONTEND="noninteractive" apt-get install -y \
    nginx \
    nodejs npm \
    php7.0-cli php7.0-fpm php7.0-gd php7.0-mcrypt \
    redis-server

# This is a fix for
# ERROR: unable to bind listening socket for address '/run/php/php7.0-fpm.sock': No such file or directory (2)
# ERROR: FPM initialization failed
RUN service php7.0-fpm start

when I run it:
Creating config file /etc/php/7.0/cli/php.ini with new version
Setting up php7.0-fpm (7.0.8-0ubuntu0.16.04.1) ...

Creating config file /etc/php/7.0/fpm/php.ini with new version
invoke-rc.d: could not determine current run level
invoke-rc.d: policy-rc.d denied execution of start.
Setting up php7.0-gd (7.0.8-0ubuntu0.16.04.1) ...

Creating config file /etc/php/7.0/mods-available/gd.ini with new version
Setting up php7.0-mcrypt (7.0.8-0ubuntu0.16.04.1) ...

result is that no files are actually created in /etc/php/7.0/mods-available/

+1

@degaray I've fixed it: https://github.com/wearede/larawell

Thank you @sandrodz :)

@sandrodz  this is to be run on the host machine or inside the Dockerfile?

@austinmw https://github.com/wearede/larawell/blob/master/Dockerfile#L9

Is there something we can merge to make this permanent, this appears to be a repeat of #216

authors: Theaxiom austinmw degaray kingdonb sandrodz

repo: phusion/baseimage-docker


text:
How to deploy it on systemd?

ive tried to replace /usr/sbin/nginx with self compiled /home/nginx/objs/nginx in /usr/lib/systemd/system/nginx.service / /etc/systemd/system/nginx.service & got this error:
$:/home/nginx# systemctl daemon-reload
$:/home/nginx# service nginx restart
Job for nginx.service failed because the control process exited with error code.
See "systemctl status nginx.service" and "journalctl -xe" for details.
$:/home/nginx# systemctl status nginx.service
● nginx.service - A high performance web server and a reverse proxy server
     Loaded: loaded (/etc/systemd/system/nginx.service; enabled; vendor preset: enabled)
     Active: failed (Result: exit-code) since Sun 2023-04-16 10:45:05 MSK; 8s ago
       Docs: man:nginx(8)
    Process: 1385450 ExecStartPre=/home/nginx/objs/nginx -t -q -g daemon on; master_process on; (code=exited, status=1/FAILURE)
        CPU: 84ms

Apr 16 10:45:05 incredible-gmod nginx[1385450]: Direct leak of 1024 byte(s) in 1 object(s) allocated from:
Apr 16 10:45:05 incredible-gmod nginx[1385450]:     #0 0x7f7c1eaa4a3c in __interceptor_posix_memalign ../../../../src/libsanitizer/asan/asan_malloc_linux.cpp:226
Apr 16 10:45:05 incredible-gmod nginx[1385450]:     #1 0x55c5d1611556 in ngx_memalign src/os/unix/ngx_alloc.c:57
Apr 16 10:45:05 incredible-gmod nginx[1385450]:     #2 0x55c5d15a5138 in ngx_create_pool src/core/ngx_palloc.c:23
Apr 16 10:45:05 incredible-gmod nginx[1385450]:     #3 0x55c5d159feba in main src/core/nginx.c:253
Apr 16 10:45:05 incredible-gmod nginx[1385450]:     #4 0x7f7c1e78dd09 in __libc_start_main (/lib/x86_64-linux-gnu/libc.so.6+0x23d09)
Apr 16 10:45:05 incredible-gmod nginx[1385450]: SUMMARY: AddressSanitizer: 1024 byte(s) leaked in 1 allocation(s).
Apr 16 10:45:05 incredible-gmod systemd[1]: nginx.service: Control process exited, code=exited, status=1/FAILURE
Apr 16 10:45:05 incredible-gmod systemd[1]: nginx.service: Failed with result 'exit-code'.
Apr 16 10:45:05 incredible-gmod systemd[1]: Failed to start A high performance web server and a reverse proxy server.

whats iam doing wrong?

Hi @Be1zebub , this project already assumes that users are experienced users of nginx, so it does not provide the nginx integration and maintenance details.
The setup steps in Readme.md is just for testing and debugging, thanks again.

repo: phuslu/nginx-ssl-fingerprint


text:
Update/improve temporal filtering

Currently, I believe that there are hardcoded cutoffs for different modalities, but we probably want to be able to calculate cutoffs from sequence parameters as well. @62442katieb, I think this is your area of expertise.

I don't believe those modalities actually do anything right—I think they're vestiges from a former iteration of the codebase. I kept them as a reference for myself for what cutoffs were reasonable (though, as you accurately note, that will depend on sampling frequency!).
They could definitely be improved to actually do stuff, though!! 💯

I haven't familiarized myself with the codebase yet, but once I do, I'm definitely interested in looking through and adding/tweaking some filtering based on what I've been learning the past couple months!
+1 for actually doing stuff! 😄

The ReadTheDocs site is still live! Though I don't think any new changes will get pushed to that since it was hosted from my user account and not the physiopy org (I don't know how RTD handles ownership transfers 🤷♂).
Anyway, happy to help people orient themselves to peakdet! I won't be contributing anything new anytime soon (see: for the remainder of grad school 😅) but am happy to answer questions.

authors: 62442katieb rmarkello tsalo

repo: physiopy/peakdet


text:
🛑 YSF REF is down

In bc29943, YSF REF (https://ysf.freedmr.it) was down:

HTTP code: 500
Response time: 1073 ms

Resolved: YSF REF is back up in 3170f42 after 10 minutes.

repo: picchiosat/HBLink-Uptime


text:
InAppWebView alert() not work

HTML code:

function testClick() {
         alert("hello");
}

the code in Chrome work normally. but in InAppWebView do not work. do you know how to resolve the problem . Thanks

Now it should be fixed in 2.0.0. Also, this plugin changed its name to flutter_inappwebview. The current latest version now is 2.1.0+1. So, you can change your dependency influtter_inappwebview: ^2.1.0+1.


text:
'Player' has no member 'setUrl'

getting the error 'Player' has no member 'setUrl'. when copying the EXACT code in the example. I am using the 0.1.3 release, but it should be the same function? I even checked in the pod and the function exists. what am I doing wrong?

For the current version just do;
self.player.url = yourUrl

authors: mrfarukturgut uknowmeright

repo: piemonte/Player