Addon stops to work "MaxRetryError"

Describe the bug what do have
since some weeks the addon stops to work after a while. manual restarts helps. sometimes for 6 hours an more. watchdog is enabled but seems not to help.
configuration "wait" was 60 and 300.
Log details
2024-05-18 14:15:46,651 __init__.py:640 INFO - state_topic: hmd/sensor/Viessmann-Gridbox/SelfSupply/state
2024-05-18 14:15:46,651 __init__.py:671 DEBUG - Creating mqtt client (None) for core-mosquitto:1883
2024-05-18 14:15:46,651 __init__.py:711 DEBUG - Connecting to core-mosquitto:1883 without SSL
2024-05-18 14:15:46,651 __init__.py:639 INFO - config_topic: homeassistant/sensor/Viessmann-Gridbox/SelfConsumptionRate/config
2024-05-18 14:15:46,651 __init__.py:640 INFO - state_topic: hmd/sensor/Viessmann-Gridbox/SelfConsumptionRate/state
2024-05-18 14:15:46,651 __init__.py:671 DEBUG - Creating mqtt client (None) for core-mosquitto:1883
2024-05-18 14:15:46,651 __init__.py:711 DEBUG - Connecting to core-mosquitto:1883 without SSL
2024-05-18 14:15:46,652 __init__.py:639 INFO - config_topic: homeassistant/sensor/Viessmann-Gridbox/SelfSufficiencyRate/config
2024-05-18 14:15:46,652 __init__.py:640 INFO - state_topic: hmd/sensor/Viessmann-Gridbox/SelfSufficiencyRate/state
2024-05-18 14:15:46,652 __init__.py:671 DEBUG - Creating mqtt client (None) for core-mosquitto:1883
2024-05-18 14:15:46,652 __init__.py:711 DEBUG - Connecting to core-mosquitto:1883 without SSL
2024-05-18 14:15:46,653 connectionpool.py:1055 DEBUG - Starting new HTTPS connection (1): gridx.eu.auth0.com:443
Traceback (most recent call last):
  File "/usr/local/lib/python3.10/site-packages/urllib3/connection.py", line 198, in _new_conn
    sock = connection.create_connection(
  File "/usr/local/lib/python3.10/site-packages/urllib3/util/connection.py", line 85, in create_connection
    raise err
  File "/usr/local/lib/python3.10/site-packages/urllib3/util/connection.py", line 73, in create_connection
    sock.connect(sa)
OSError: [Errno 113] Host is unreachable

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

Traceback (most recent call last):
  File "/usr/local/lib/python3.10/site-packages/urllib3/connectionpool.py", line 793, in urlopen
    response = self._make_request(
  File "/usr/local/lib/python3.10/site-packages/urllib3/connectionpool.py", line 491, in _make_request
    raise new_e
  File "/usr/local/lib/python3.10/site-packages/urllib3/connectionpool.py", line 467, in _make_request
    self._validate_conn(conn)
  File "/usr/local/lib/python3.10/site-packages/urllib3/connectionpool.py", line 1099, in _validate_conn
    conn.connect()
  File "/usr/local/lib/python3.10/site-packages/urllib3/connection.py", line 616, in connect
    self.sock = sock = self._new_conn()
  File "/usr/local/lib/python3.10/site-packages/urllib3/connection.py", line 213, in _new_conn
    raise NewConnectionError(
urllib3.exceptions.NewConnectionError: <urllib3.connection.HTTPSConnection object at 0x7f57c6257b80>: Failed to establish a new connection: [Errno 113] Host is unreachable

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

Traceback (most recent call last):
  File "/usr/local/lib/python3.10/site-packages/requests/adapters.py", line 486, in send
    resp = conn.urlopen(
  File "/usr/local/lib/python3.10/site-packages/urllib3/connectionpool.py", line 847, in urlopen
    retries = retries.increment(
  File "/usr/local/lib/python3.10/site-packages/urllib3/util/retry.py", line 515, in increment
    raise MaxRetryError(_pool, url, reason) from reason  # type: ignore[arg-type]
urllib3.exceptions.MaxRetryError: HTTPSConnectionPool(host='gridx.eu.auth0.com', port=443): Max retries exceeded with url: /oauth/token (Caused by NewConnectionError('<urllib3.connection.HTTPSConnection object at 0x7f57c6257b80>: Failed to establish a new connection: [Errno 113] Host is unreachable'))

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/usr/local/lib/python3.10/runpy.py", line 196, in _run_module_as_main
    return _run_code(code, main_globals, None,
  File "/usr/local/lib/python3.10/runpy.py", line 86, in _run_code
    exec(code, run_globals)
  File "/build/GridboxConnector/__main__.py", line 42, in <module>
    gridboxConnector = GridboxConnector(data)
  File "/usr/local/lib/python3.10/site-packages/gridbox_connector/GridboxConnector.py", line 11, in __init__
    self.init_auth()
  File "/usr/local/lib/python3.10/site-packages/gridbox_connector/GridboxConnector.py", line 14, in init_auth
    self.get_token()
  File "/usr/local/lib/python3.10/site-packages/gridbox_connector/GridboxConnector.py", line 19, in get_token
    response = requests.post(self.login_url, self.login_body)
  File "/usr/local/lib/python3.10/site-packages/requests/api.py", line 115, in post
    return request("post", url, data=data, json=json, **kwargs)
  File "/usr/local/lib/python3.10/site-packages/requests/api.py", line 59, in request
    return session.request(method=method, url=url, **kwargs)
  File "/usr/local/lib/python3.10/site-packages/requests/sessions.py", line 589, in request
    resp = self.send(prep, **send_kwargs)
  File "/usr/local/lib/python3.10/site-packages/requests/sessions.py", line 703, in send
    r = adapter.send(request, **kwargs)
  File "/usr/local/lib/python3.10/site-packages/requests/adapters.py", line 519, in send
    raise ConnectionError(e, request=request)
requests.exceptions.ConnectionError: HTTPSConnectionPool(host='gridx.eu.auth0.com', port=443): Max retries exceeded with url: /oauth/token (Caused by NewConnectionError('<urllib3.connection.HTTPSConnection object at 0x7f57c6257b80>: Failed to establish a new connection: [Errno 113] Host is unreachable'))
2024-05-18 14:15:46,690 __init__.py:853 DEBUG - Shutting down MQTT client
2024-05-18 14:15:46,690 __init__.py:853 DEBUG - Shutting down MQTT client
2024-05-18 14:15:46,690 __init__.py:853 DEBUG - Shutting down MQTT client
2024-05-18 14:15:46,690 __init__.py:853 DEBUG - Shutting down MQTT client
2024-05-18 14:15:46,690 __init__.py:853 DEBUG - Shutting down MQTT client
2024-05-18 14:15:46,690 __init__.py:853 DEBUG - Shutting down MQTT client
2024-05-18 14:15:46,690 __init__.py:853 DEBUG - Shutting down MQTT client
2024-05-18 14:15:46,690 __init__.py:853 DEBUG - Shutting down MQTT client
2024-05-18 14:15:46,690 __init__.py:853 DEBUG - Shutting down MQTT client
2024-05-18 14:15:46,690 __init__.py:853 DEBUG - Shutting down MQTT client
2024-05-18 14:15:46,690 __init__.py:853 DEBUG - Shutting down MQTT client
2024-05-18 14:15:46,690 __init__.py:853 DEBUG - Shutting down MQTT client
2024-05-18 14:15:46,690 __init__.py:853 DEBUG - Shutting down MQTT client
2024-05-18 14:15:46,690 __init__.py:853 DEBUG - Shutting down MQTT client
2024-05-18 14:15:46,690 __init__.py:853 DEBUG - Shutting down MQTT client
[14:15:46] INFO: Service gridboxconnector exited with code 1 (by signal 0)
s6-rc: info: service legacy-services: stopping
s6-rc: info: service legacy-services successfully stopped
s6-rc: info: service gridboxconnector: stopping
s6-rc: info: service gridboxconnector successfully stopped
s6-rc: info: service legacy-cont-init: stopping
s6-rc: info: service legacy-cont-init successfully stopped
s6-rc: info: service fix-attrs: stopping
s6-rc: info: service fix-attrs successfully stopped
s6-rc: info: service s6rc-oneshot-runner: stopping
s6-rc: info: service s6rc-oneshot-runner successfully stopped
------------------

----------
2024-05-20 10:21:08,248 __init__.py:640 INFO - state_topic: hmd/sensor/Viessmann-Gridbox/SelfSupply/state
2024-05-20 10:21:08,248 __init__.py:671 DEBUG - Creating mqtt client (None) for core-mosquitto:1883
2024-05-20 10:21:08,248 __init__.py:711 DEBUG - Connecting to core-mosquitto:1883 without SSL
2024-05-20 10:21:08,248 __init__.py:639 INFO - config_topic: homeassistant/sensor/Viessmann-Gridbox/SelfConsumptionRate/config
2024-05-20 10:21:08,249 __init__.py:640 INFO - state_topic: hmd/sensor/Viessmann-Gridbox/SelfConsumptionRate/state
2024-05-20 10:21:08,249 __init__.py:671 DEBUG - Creating mqtt client (None) for core-mosquitto:1883
2024-05-20 10:21:08,249 __init__.py:711 DEBUG - Connecting to core-mosquitto:1883 without SSL
2024-05-20 10:21:08,249 __init__.py:639 INFO - config_topic: homeassistant/sensor/Viessmann-Gridbox/SelfSufficiencyRate/config
2024-05-20 10:21:08,249 __init__.py:640 INFO - state_topic: hmd/sensor/Viessmann-Gridbox/SelfSufficiencyRate/state
2024-05-20 10:21:08,249 __init__.py:671 DEBUG - Creating mqtt client (None) for core-mosquitto:1883
2024-05-20 10:21:08,249 __init__.py:711 DEBUG - Connecting to core-mosquitto:1883 without SSL
2024-05-20 10:21:08,251 connectionpool.py:1055 DEBUG - Starting new HTTPS connection (1): gridx.eu.auth0.com:443
Traceback (most recent call last):
  File "/usr/local/lib/python3.10/site-packages/urllib3/connection.py", line 198, in _new_conn
    sock = connection.create_connection(
  File "/usr/local/lib/python3.10/site-packages/urllib3/util/connection.py", line 85, in create_connection
    raise err
  File "/usr/local/lib/python3.10/site-packages/urllib3/util/connection.py", line 73, in create_connection
    sock.connect(sa)
OSError: [Errno 113] Host is unreachable

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

Traceback (most recent call last):
  File "/usr/local/lib/python3.10/site-packages/urllib3/connectionpool.py", line 793, in urlopen
    response = self._make_request(
  File "/usr/local/lib/python3.10/site-packages/urllib3/connectionpool.py", line 491, in _make_request
    raise new_e
  File "/usr/local/lib/python3.10/site-packages/urllib3/connectionpool.py", line 467, in _make_request
    self._validate_conn(conn)
  File "/usr/local/lib/python3.10/site-packages/urllib3/connectionpool.py", line 1099, in _validate_conn
    conn.connect()
  File "/usr/local/lib/python3.10/site-packages/urllib3/connection.py", line 616, in connect
    self.sock = sock = self._new_conn()
  File "/usr/local/lib/python3.10/site-packages/urllib3/connection.py", line 213, in _new_conn
    raise NewConnectionError(
urllib3.exceptions.NewConnectionError: <urllib3.connection.HTTPSConnection object at 0x7f354c34fb80>: Failed to establish a new connection: [Errno 113] Host is unreachable

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

Traceback (most recent call last):
  File "/usr/local/lib/python3.10/site-packages/requests/adapters.py", line 486, in send
    resp = conn.urlopen(
  File "/usr/local/lib/python3.10/site-packages/urllib3/connectionpool.py", line 847, in urlopen
    retries = retries.increment(
  File "/usr/local/lib/python3.10/site-packages/urllib3/util/retry.py", line 515, in increment
    raise MaxRetryError(_pool, url, reason) from reason  # type: ignore[arg-type]
urllib3.exceptions.MaxRetryError: HTTPSConnectionPool(host='gridx.eu.auth0.com', port=443): Max retries exceeded with url: /oauth/token (Caused by NewConnectionError('<urllib3.connection.HTTPSConnection object at 0x7f354c34fb80>: Failed to establish a new connection: [Errno 113] Host is unreachable'))

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/usr/local/lib/python3.10/runpy.py", line 196, in _run_module_as_main
    return _run_code(code, main_globals, None,
  File "/usr/local/lib/python3.10/runpy.py", line 86, in _run_code
    exec(code, run_globals)
  File "/build/GridboxConnector/__main__.py", line 42, in <module>
    gridboxConnector = GridboxConnector(data)
  File "/usr/local/lib/python3.10/site-packages/gridbox_connector/GridboxConnector.py", line 11, in __init__
    self.init_auth()
  File "/usr/local/lib/python3.10/site-packages/gridbox_connector/GridboxConnector.py", line 14, in init_auth
    self.get_token()
  File "/usr/local/lib/python3.10/site-packages/gridbox_connector/GridboxConnector.py", line 19, in get_token
    response = requests.post(self.login_url, self.login_body)
  File "/usr/local/lib/python3.10/site-packages/requests/api.py", line 115, in post
    return request("post", url, data=data, json=json, **kwargs)
  File "/usr/local/lib/python3.10/site-packages/requests/api.py", line 59, in request
    return session.request(method=method, url=url, **kwargs)
  File "/usr/local/lib/python3.10/site-packages/requests/sessions.py", line 589, in request
    resp = self.send(prep, **send_kwargs)
  File "/usr/local/lib/python3.10/site-packages/requests/sessions.py", line 703, in send
    r = adapter.send(request, **kwargs)
  File "/usr/local/lib/python3.10/site-packages/requests/adapters.py", line 519, in send
    raise ConnectionError(e, request=request)
requests.exceptions.ConnectionError: HTTPSConnectionPool(host='gridx.eu.auth0.com', port=443): Max retries exceeded with url: /oauth/token (Caused by NewConnectionError('<urllib3.connection.HTTPSConnection object at 0x7f354c34fb80>: Failed to establish a new connection: [Errno 113] Host is unreachable'))
2024-05-20 10:21:08,286 __init__.py:853 DEBUG - Shutting down MQTT client
2024-05-20 10:21:08,287 __init__.py:853 DEBUG - Shutting down MQTT client
2024-05-20 10:21:08,287 __init__.py:853 DEBUG - Shutting down MQTT client
2024-05-20 10:21:08,287 __init__.py:853 DEBUG - Shutting down MQTT client
2024-05-20 10:21:08,287 __init__.py:853 DEBUG - Shutting down MQTT client
2024-05-20 10:21:08,287 __init__.py:853 DEBUG - Shutting down MQTT client
2024-05-20 10:21:08,287 __init__.py:853 DEBUG - Shutting down MQTT client
2024-05-20 10:21:08,287 __init__.py:853 DEBUG - Shutting down MQTT client
2024-05-20 10:21:08,287 __init__.py:853 DEBUG - Shutting down MQTT client
2024-05-20 10:21:08,287 __init__.py:853 DEBUG - Shutting down MQTT client
2024-05-20 10:21:08,287 __init__.py:853 DEBUG - Shutting down MQTT client
2024-05-20 10:21:08,287 __init__.py:853 DEBUG - Shutting down MQTT client
2024-05-20 10:21:08,287 __init__.py:853 DEBUG - Shutting down MQTT client
2024-05-20 10:21:08,287 __init__.py:853 DEBUG - Shutting down MQTT client
2024-05-20 10:21:08,287 __init__.py:853 DEBUG - Shutting down MQTT client
[10:21:08] INFO: Service gridboxconnector exited with code 1 (by signal 0)
s6-rc: info: service legacy-services: stopping
s6-rc: info: service legacy-services successfully stopped
s6-rc: info: service gridboxconnector: stopping
s6-rc: info: service gridboxconnector successfully stopped
s6-rc: info: service legacy-cont-init: stopping
s6-rc: info: service legacy-cont-init successfully stopped
s6-rc: info: service fix-attrs: stopping
s6-rc: info: service fix-attrs successfully stopped
s6-rc: info: service s6rc-oneshot-runner: stopping
s6-rc: info: service s6rc-oneshot-runner successfully stopped

------v2.3.0
2024-05-23 19:08:18,921 __init__.py:640 INFO - state_topic: hmd/sensor/Viessmann-Gridbox/Photovoltaic/state
2024-05-23 19:08:18,922 __init__.py:639 INFO - config_topic: homeassistant/sensor/Viessmann-Gridbox/Battery-sum-Level/config
2024-05-23 19:08:18,922 __init__.py:640 INFO - state_topic: hmd/sensor/Viessmann-Gridbox/Battery-sum-Level/state
2024-05-23 19:08:18,923 __init__.py:639 INFO - config_topic: homeassistant/sensor/Viessmann-Gridbox/Battery-sum-Capacity/config
2024-05-23 19:08:18,924 __init__.py:640 INFO - state_topic: hmd/sensor/Viessmann-Gridbox/Battery-sum-Capacity/state
2024-05-23 19:08:18,925 __init__.py:639 INFO - config_topic: homeassistant/sensor/Viessmann-Gridbox/Battery-sum-Power/config
2024-05-23 19:08:18,925 __init__.py:640 INFO - state_topic: hmd/sensor/Viessmann-Gridbox/Battery-sum-Power/state
2024-05-23 19:08:18,926 __init__.py:639 INFO - config_topic: homeassistant/sensor/Viessmann-Gridbox/Battery-sum-Remaining-Charge/config
2024-05-23 19:08:18,926 __init__.py:640 INFO - state_topic: hmd/sensor/Viessmann-Gridbox/Battery-sum-Remaining-Charge/state
2024-05-23 19:08:18,927 __init__.py:639 INFO - config_topic: homeassistant/sensor/Viessmann-Gridbox/Consumption/config
2024-05-23 19:08:18,927 __init__.py:640 INFO - state_topic: hmd/sensor/Viessmann-Gridbox/Consumption/state
2024-05-23 19:08:18,928 __init__.py:639 INFO - config_topic: homeassistant/sensor/Viessmann-Gridbox/Total-Consumption/config
2024-05-23 19:08:18,928 __init__.py:640 INFO - state_topic: hmd/sensor/Viessmann-Gridbox/Total-Consumption/state
2024-05-23 19:08:18,928 __init__.py:639 INFO - config_topic: homeassistant/sensor/Viessmann-Gridbox/DirectConsumptionHousehold/config
2024-05-23 19:08:18,929 __init__.py:640 INFO - state_topic: hmd/sensor/Viessmann-Gridbox/DirectConsumptionHousehold/state
2024-05-23 19:08:18,929 __init__.py:639 INFO - config_topic: homeassistant/sensor/Viessmann-Gridbox/DirectConsumptionHeatPump/config
2024-05-23 19:08:18,929 __init__.py:640 INFO - state_topic: hmd/sensor/Viessmann-Gridbox/DirectConsumptionHeatPump/state
2024-05-23 19:08:18,930 __init__.py:639 INFO - config_topic: homeassistant/sensor/Viessmann-Gridbox/DirectConsumptionEV/config
2024-05-23 19:08:18,930 __init__.py:640 INFO - state_topic: hmd/sensor/Viessmann-Gridbox/DirectConsumptionEV/state
2024-05-23 19:08:18,931 __init__.py:639 INFO - config_topic: homeassistant/sensor/Viessmann-Gridbox/DirectConsumptionRate/config
2024-05-23 19:08:18,931 __init__.py:640 INFO - state_topic: hmd/sensor/Viessmann-Gridbox/DirectConsumptionRate/state
2024-05-23 19:08:18,932 __init__.py:639 INFO - config_topic: homeassistant/sensor/Viessmann-Gridbox/SelfSupply/config
2024-05-23 19:08:18,932 __init__.py:640 INFO - state_topic: hmd/sensor/Viessmann-Gridbox/SelfSupply/state
2024-05-23 19:08:18,932 __init__.py:639 INFO - config_topic: homeassistant/sensor/Viessmann-Gridbox/SelfConsumptionRate/config
2024-05-23 19:08:18,932 __init__.py:640 INFO - state_topic: hmd/sensor/Viessmann-Gridbox/SelfConsumptionRate/state
2024-05-23 19:08:18,933 __init__.py:639 INFO - config_topic: homeassistant/sensor/Viessmann-Gridbox/SelfSufficiencyRate/config
2024-05-23 19:08:18,933 __init__.py:640 INFO - state_topic: hmd/sensor/Viessmann-Gridbox/SelfSufficiencyRate/state
Traceback (most recent call last):
  File "/usr/local/lib/python3.10/site-packages/urllib3/connection.py", line 198, in _new_conn
    sock = connection.create_connection(
  File "/usr/local/lib/python3.10/site-packages/urllib3/util/connection.py", line 85, in create_connection
    raise err
  File "/usr/local/lib/python3.10/site-packages/urllib3/util/connection.py", line 73, in create_connection
    sock.connect(sa)
OSError: [Errno 113] Host is unreachable

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

Traceback (most recent call last):
  File "/usr/local/lib/python3.10/site-packages/urllib3/connectionpool.py", line 793, in urlopen
    response = self._make_request(
  File "/usr/local/lib/python3.10/site-packages/urllib3/connectionpool.py", line 491, in _make_request
    raise new_e
  File "/usr/local/lib/python3.10/site-packages/urllib3/connectionpool.py", line 467, in _make_request
    self._validate_conn(conn)
  File "/usr/local/lib/python3.10/site-packages/urllib3/connectionpool.py", line 1099, in _validate_conn
    conn.connect()
  File "/usr/local/lib/python3.10/site-packages/urllib3/connection.py", line 616, in connect
    self.sock = sock = self._new_conn()
  File "/usr/local/lib/python3.10/site-packages/urllib3/connection.py", line 213, in _new_conn
    raise NewConnectionError(
urllib3.exceptions.NewConnectionError: <urllib3.connection.HTTPSConnection object at 0x7f616dbfbfd0>: Failed to establish a new connection: [Errno 113] Host is unreachable

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

Traceback (most recent call last):
  File "/usr/local/lib/python3.10/site-packages/requests/adapters.py", line 486, in send
    resp = conn.urlopen(
  File "/usr/local/lib/python3.10/site-packages/urllib3/connectionpool.py", line 847, in urlopen
    retries = retries.increment(
  File "/usr/local/lib/python3.10/site-packages/urllib3/util/retry.py", line 515, in increment
    raise MaxRetryError(_pool, url, reason) from reason  # type: ignore[arg-type]
urllib3.exceptions.MaxRetryError: HTTPSConnectionPool(host='gridx.eu.auth0.com', port=443): Max retries exceeded with url: /oauth/token (Caused by NewConnectionError('<urllib3.connection.HTTPSConnection object at 0x7f616dbfbfd0>: Failed to establish a new connection: [Errno 113] Host is unreachable'))

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/usr/local/lib/python3.10/runpy.py", line 196, in _run_module_as_main
    return _run_code(code, main_globals, None,
  File "/usr/local/lib/python3.10/runpy.py", line 86, in _run_code
    exec(code, run_globals)
  File "/build/GridboxConnector/__main__.py", line 42, in <module>
    gridboxConnector = GridboxConnector(data)
  File "/usr/local/lib/python3.10/site-packages/gridbox_connector/GridboxConnector.py", line 11, in __init__
    self.init_auth()
  File "/usr/local/lib/python3.10/site-packages/gridbox_connector/GridboxConnector.py", line 14, in init_auth
    self.get_token()
  File "/usr/local/lib/python3.10/site-packages/gridbox_connector/GridboxConnector.py", line 19, in get_token
    response = requests.post(self.login_url, self.login_body)
  File "/usr/local/lib/python3.10/site-packages/requests/api.py", line 115, in post
    return request("post", url, data=data, json=json, **kwargs)
  File "/usr/local/lib/python3.10/site-packages/requests/api.py", line 59, in request
    return session.request(method=method, url=url, **kwargs)
  File "/usr/local/lib/python3.10/site-packages/requests/sessions.py", line 589, in request
    resp = self.send(prep, **send_kwargs)
  File "/usr/local/lib/python3.10/site-packages/requests/sessions.py", line 703, in send
    r = adapter.send(request, **kwargs)
  File "/usr/local/lib/python3.10/site-packages/requests/adapters.py", line 519, in send
    raise ConnectionError(e, request=request)
requests.exceptions.ConnectionError: HTTPSConnectionPool(host='gridx.eu.auth0.com', port=443): Max retries exceeded with url: /oauth/token (Caused by NewConnectionError('<urllib3.connection.HTTPSConnection object at 0x7f616dbfbfd0>: Failed to establish a new connection: [Errno 113] Host is unreachable'))
[19:08:19] INFO: Service gridboxconnector exited with code 1 (by signal 0)
s6-rc: info: service legacy-services: stopping
s6-rc: info: service legacy-services successfully stopped
s6-rc: info: service gridboxconnector: stopping
s6-rc: info: service gridboxconnector successfully stopped
s6-rc: info: service legacy-cont-init: stopping
s6-rc: info: service legacy-cont-init successfully stopped
s6-rc: info: service fix-attrs: stopping
s6-rc: info: service fix-attrs successfully stopped
s6-rc: info: service s6rc-oneshot-runner: stopping
s6-rc: info: service s6rc-oneshot-runner successfully stopped
------
2024-05-24 11:45:51,642 __init__.py:640 INFO - state_topic: hmd/sensor/Viessmann-Gridbox/Photovoltaic/state
2024-05-24 11:45:51,643 __init__.py:639 INFO - config_topic: homeassistant/sensor/Viessmann-Gridbox/Battery-sum-Level/config
2024-05-24 11:45:51,643 __init__.py:640 INFO - state_topic: hmd/sensor/Viessmann-Gridbox/Battery-sum-Level/state
2024-05-24 11:45:51,643 __init__.py:639 INFO - config_topic: homeassistant/sensor/Viessmann-Gridbox/Battery-sum-Capacity/config
2024-05-24 11:45:51,643 __init__.py:640 INFO - state_topic: hmd/sensor/Viessmann-Gridbox/Battery-sum-Capacity/state
2024-05-24 11:45:51,644 __init__.py:639 INFO - config_topic: homeassistant/sensor/Viessmann-Gridbox/Battery-sum-Power/config
2024-05-24 11:45:51,644 __init__.py:640 INFO - state_topic: hmd/sensor/Viessmann-Gridbox/Battery-sum-Power/state
2024-05-24 11:45:51,644 __init__.py:639 INFO - config_topic: homeassistant/sensor/Viessmann-Gridbox/Battery-sum-Remaining-Charge/config
2024-05-24 11:45:51,644 __init__.py:640 INFO - state_topic: hmd/sensor/Viessmann-Gridbox/Battery-sum-Remaining-Charge/state
2024-05-24 11:45:51,645 __init__.py:639 INFO - config_topic: homeassistant/sensor/Viessmann-Gridbox/Consumption/config
2024-05-24 11:45:51,645 __init__.py:640 INFO - state_topic: hmd/sensor/Viessmann-Gridbox/Consumption/state
2024-05-24 11:45:51,645 __init__.py:639 INFO - config_topic: homeassistant/sensor/Viessmann-Gridbox/Total-Consumption/config
2024-05-24 11:45:51,645 __init__.py:640 INFO - state_topic: hmd/sensor/Viessmann-Gridbox/Total-Consumption/state
2024-05-24 11:45:51,645 __init__.py:639 INFO - config_topic: homeassistant/sensor/Viessmann-Gridbox/DirectConsumptionHousehold/config
2024-05-24 11:45:51,645 __init__.py:640 INFO - state_topic: hmd/sensor/Viessmann-Gridbox/DirectConsumptionHousehold/state
2024-05-24 11:45:51,646 __init__.py:639 INFO - config_topic: homeassistant/sensor/Viessmann-Gridbox/DirectConsumptionHeatPump/config
2024-05-24 11:45:51,646 __init__.py:640 INFO - state_topic: hmd/sensor/Viessmann-Gridbox/DirectConsumptionHeatPump/state
2024-05-24 11:45:51,646 __init__.py:639 INFO - config_topic: homeassistant/sensor/Viessmann-Gridbox/DirectConsumptionEV/config
2024-05-24 11:45:51,646 __init__.py:640 INFO - state_topic: hmd/sensor/Viessmann-Gridbox/DirectConsumptionEV/state
2024-05-24 11:45:51,646 __init__.py:639 INFO - config_topic: homeassistant/sensor/Viessmann-Gridbox/DirectConsumptionRate/config
2024-05-24 11:45:51,646 __init__.py:640 INFO - state_topic: hmd/sensor/Viessmann-Gridbox/DirectConsumptionRate/state
2024-05-24 11:45:51,647 __init__.py:639 INFO - config_topic: homeassistant/sensor/Viessmann-Gridbox/SelfSupply/config
2024-05-24 11:45:51,647 __init__.py:640 INFO - state_topic: hmd/sensor/Viessmann-Gridbox/SelfSupply/state
2024-05-24 11:45:51,647 __init__.py:639 INFO - config_topic: homeassistant/sensor/Viessmann-Gridbox/SelfConsumptionRate/config
2024-05-24 11:45:51,647 __init__.py:640 INFO - state_topic: hmd/sensor/Viessmann-Gridbox/SelfConsumptionRate/state
2024-05-24 11:45:51,647 __init__.py:639 INFO - config_topic: homeassistant/sensor/Viessmann-Gridbox/SelfSufficiencyRate/config
2024-05-24 11:45:51,647 __init__.py:640 INFO - state_topic: hmd/sensor/Viessmann-Gridbox/SelfSufficiencyRate/state
Traceback (most recent call last):
  File "/usr/local/lib/python3.10/site-packages/urllib3/connection.py", line 198, in _new_conn
    sock = connection.create_connection(
  File "/usr/local/lib/python3.10/site-packages/urllib3/util/connection.py", line 85, in create_connection
    raise err
  File "/usr/local/lib/python3.10/site-packages/urllib3/util/connection.py", line 73, in create_connection
    sock.connect(sa)
OSError: [Errno 113] Host is unreachable

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

Traceback (most recent call last):
  File "/usr/local/lib/python3.10/site-packages/urllib3/connectionpool.py", line 793, in urlopen
    response = self._make_request(
  File "/usr/local/lib/python3.10/site-packages/urllib3/connectionpool.py", line 491, in _make_request
    raise new_e
  File "/usr/local/lib/python3.10/site-packages/urllib3/connectionpool.py", line 467, in _make_request
    self._validate_conn(conn)
  File "/usr/local/lib/python3.10/site-packages/urllib3/connectionpool.py", line 1099, in _validate_conn
    conn.connect()
  File "/usr/local/lib/python3.10/site-packages/urllib3/connection.py", line 616, in connect
    self.sock = sock = self._new_conn()
  File "/usr/local/lib/python3.10/site-packages/urllib3/connection.py", line 213, in _new_conn
    raise NewConnectionError(
urllib3.exceptions.NewConnectionError: <urllib3.connection.HTTPSConnection object at 0x7f186e947fd0>: Failed to establish a new connection: [Errno 113] Host is unreachable

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

Traceback (most recent call last):
  File "/usr/local/lib/python3.10/site-packages/requests/adapters.py", line 486, in send
    resp = conn.urlopen(
  File "/usr/local/lib/python3.10/site-packages/urllib3/connectionpool.py", line 847, in urlopen
    retries = retries.increment(
  File "/usr/local/lib/python3.10/site-packages/urllib3/util/retry.py", line 515, in increment
    raise MaxRetryError(_pool, url, reason) from reason  # type: ignore[arg-type]
urllib3.exceptions.MaxRetryError: HTTPSConnectionPool(host='gridx.eu.auth0.com', port=443): Max retries exceeded with url: /oauth/token (Caused by NewConnectionError('<urllib3.connection.HTTPSConnection object at 0x7f186e947fd0>: Failed to establish a new connection: [Errno 113] Host is unreachable'))

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/usr/local/lib/python3.10/runpy.py", line 196, in _run_module_as_main
    return _run_code(code, main_globals, None,
  File "/usr/local/lib/python3.10/runpy.py", line 86, in _run_code
    exec(code, run_globals)
  File "/build/GridboxConnector/__main__.py", line 42, in <module>
    gridboxConnector = GridboxConnector(data)
  File "/usr/local/lib/python3.10/site-packages/gridbox_connector/GridboxConnector.py", line 11, in __init__
    self.init_auth()
  File "/usr/local/lib/python3.10/site-packages/gridbox_connector/GridboxConnector.py", line 14, in init_auth
    self.get_token()
  File "/usr/local/lib/python3.10/site-packages/gridbox_connector/GridboxConnector.py", line 19, in get_token
    response = requests.post(self.login_url, self.login_body)
  File "/usr/local/lib/python3.10/site-packages/requests/api.py", line 115, in post
    return request("post", url, data=data, json=json, **kwargs)
  File "/usr/local/lib/python3.10/site-packages/requests/api.py", line 59, in request
    return session.request(method=method, url=url, **kwargs)
  File "/usr/local/lib/python3.10/site-packages/requests/sessions.py", line 589, in request
    resp = self.send(prep, **send_kwargs)
  File "/usr/local/lib/python3.10/site-packages/requests/sessions.py", line 703, in send
    r = adapter.send(request, **kwargs)
  File "/usr/local/lib/python3.10/site-packages/requests/adapters.py", line 519, in send
    raise ConnectionError(e, request=request)
requests.exceptions.ConnectionError: HTTPSConnectionPool(host='gridx.eu.auth0.com', port=443): Max retries exceeded with url: /oauth/token (Caused by NewConnectionError('<urllib3.connection.HTTPSConnection object at 0x7f186e947fd0>: Failed to establish a new connection: [Errno 113] Host is unreachable'))
[11:45:51] INFO: Service gridboxconnector exited with code 1 (by signal 0)
s6-rc: info: service legacy-services: stopping
s6-rc: info: service legacy-services successfully stopped
s6-rc: info: service gridboxconnector: stopping
s6-rc: info: service gridboxconnector successfully stopped
s6-rc: info: service legacy-cont-init: stopping
s6-rc: info: service legacy-cont-init successfully stopped
s6-rc: info: service fix-attrs: stopping
s6-rc: info: service fix-attrs successfully stopped
s6-rc: info: service s6rc-oneshot-runner: stopping
s6-rc: info: service s6rc-oneshot-runner successfully stopped

Version
2.3.0

@Bollgarbop can you tell me more information? its look like on your side the address is not reachable

Are you using any network traffic analyzer to check your network ?
Maybe the repeat time was to often.
I am using 60seconds and it still working without any issues,

so far no traffic analyzer check done. it seems to be stable with 180sec

Will fix it later this day sorry it worked correctly by me, did you set an log level?

oh. i used "Viessmann Gridbox Connector" and there is no option to set the loglevel.  with edge it seems to work and there are also the options for the loglevel.
it was not clear to me what version to use

@Bollgarbop fixed now

oh. i used "Viessmann Gridbox Connector" and there is no option to set the loglevel. with edge it seems to work and there is also the options for the loglevel. it was not clear to me what version to use

you can set info


POL-445: RDS Rightsizing Policy: Update next instance size logic to account for missing size

Description
This update fixes the logic in the policy that calculates the next instance size to reflect "N/A" as opposed to failing if the next instance size is not captured in the instance_types.json mapping file.
Issues Resolved
[List any existing issues this PR resolves]
Contribution Check List

[x] All tests pass.
[x] New functionality includes testing.
[x] New functionality has been documented in the README if applicable
[x] New functionality has been documented in CHANGELOG.MD

          1 Warning

:warning:
Should this include readme changes

  Generated by :no_entry_sign: Danger


Data analytics : Analysis on udemy cources

💥 Proposal
(A clear and concise description of what the proposal is.)
It consist of different types of question to do analysis using various python modules like numpy , pandas etc

Please assign me this @ImranNawar !! asap so I can start working

@theyashwanthsai please look on this !!

@khusheekapoor and @theyashwanthsai any update? kindly assign this issue asap

@Abhinavcode13 - you can go ahead! We are assigning you 21 days for this project, after which it will be assigned to someone else if not completed. All the best!  Name the file as: algorithm_dataset.ipynb and link it in the readme of the labeled directory as algorithm - dataset.


Blockwebdevs blockaids

Project Abstract

Please replace these instructions with a brief description of your project summarising key points (1-2 paragraphs).
If your application is a follow-up to a previous grant, please mention which one in the first line of the abstract and include a link to previous pull requests if applicable.

Grant level

[ ] Level 1:  Up to $10,000, 2 approvals
[x] Level 2:  Up to $30,000, 3 approvals
[ ] Level 3:  Unlimited, 5 approvals (for >$100k: Web3 Foundation Council approval)

Application Checklist

[x] The application template has been copied and aptly renamed (project_name.md).
[x] I have read the application guidelines.
[x] Payment details have been provided (bank details via email or BTC, Ethereum (USDC/DAI) or Polkadot/Kusama (USDT) address in the application).
[x] The software delivered for this grant will be released under an open-source license specified in the application.
[x] The initial PR contains only one commit (squash and force-push if needed).
[x] The grant will only be announced once the first milestone has been accepted (see the announcement guidelines).
[ ] I prefer the discussion of this application to take place in a private Element/Matrix channel. My username is: @_______:matrix.org (change the homeserver if you use a different one)

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.

Thanks for the application. But you are also deleting the application template as part of the PR. Could you please update this?

Hi! We've added the file application template as part of the PR. Is this what You've requested?

Thanks for the update. This is correct. Regarding the application itself, I have a few questions/comments:

You don't seem to develop any unique smart contract features or something similar as part of the first milestone. Is this correct?
Regarding the token, see our guidelines: "Applications must not mention a specific token. Furthermore, the focus of the application should lie on the software that is being implemented/research being carried out as part of the grant, and less on your project/venture/operation. For the purpose of the application and delivery, think about how others might also benefit from your work."
How do you ensure the privacy of your solution and that you comply with the regulatory requirements? (GDPR, HIPAA, etc.)

Thank You for Your questions. The answers:

We are going to develop unique smart contract features (governance token, different mechanisms of governance and rewarding tokens accrual, etc.), but probably not under this proposal. We launched intentionally a small grant proposal so that our team could start building on  Substrate / Polkadot / Kusama and see how the integration works. Afterward, we are planning to upgrade our small project to a parachain, and bring on it all those advanced features, that are planned in our Terms of Reference: https://docs.google.com/document/d/1Ns4etjjm6Efolr0h8DGbJVwkmqVHDuiEKwTXAuM3Q6w/edit?usp=sharing
We committed the changes to our grant application. The AIDS token was replaced with the "Fungible Token". Is this ok?
We have an insourced legal team, which ensures compliance with regulations. Currently, all our users are from Moldova, and complete compliance with local regulations is in place already. Then, we will expand to Ukraine, Georgia, Kazakhstan, and Kyrgyzstan). The partnerships with local organizations from these countries are established, which includes legal support. Thus, we are going to scale our product gradually, ensuring compliance with regulations country-by-country. Additionally, we are officially supported by UNAIDS, the leading global HIV organization, which supports us on solving legal issues in global scale.

Hi @blockwebdevs. Thanks for the application. Can you elaborate what you mean by "Ink! smart contracts for implementing the logic of the Loyalty and Reward Electronic System"? My initial impression was that you simply initiate a token transfer from your backend whenever someone completes an incentive on your website. Is there more to it? What data and logic is handled in the smart contract?

Ink! smart contracts for implementing the logic of the Loyalty and Reward Electronic System will ensure that:

Users (patients) get locked tokens after completing an incentive on our web app
The tokens are unlocked after the incentive is confirmed by the doctor/consultant
Users (patients) get governance tokens after completing an incentive on our web app that will allow them to benefit from additional functionality (vote for initiatives, create discussions and proposals in our Forum/DAO, etc.)

There is much more functionality upcoming (i.e. medical data on the blockchain), under future proposals.

Users (patients) get governance tokens after completing an incentive on our web app

Unless there is some more complex logic involved that's not being mentioned, this is a simple token transfer. Basic fungible and non-fungible token templates already exist, you would just need a backend that initiates the transfer.

The tokens are unlocked after the incentive is confirmed by the doctor/consultant

How do you verify this? I cannot imagine a doctor doing the leg work to confirm someone's information on-chain.
I think this might be a useful project, but in its current state, the application is not a good fit for the grants program. We are looking for technical novelty, and the technical implementation of what you are proposing is not novel. Therefore, I won't approve the application. However, I will share it with the rest of the committee, who might have other thoughts, questions, or comments.

@semuelle thank You for Your questions!

How do you verify this? I cannot imagine a doctor doing the leg work to confirm someone's information on-chain.

We have social assistance managers (consultants), whose job is to make connections between doctors and patients (the leg work). Additionally, the rewarding platform works in both directions: All those who are doing the right actions shall be rewarded (including doctors/consultants/patients/volunteers, etc.).

Unless there is some more complex logic involved that's not being mentioned, this is a simple token transfer

Probably, I didn't explain well enough. Let me try again.
We are building a Loyalty and Reward Electronic System that will allow users in our ecosystem (patients, doctors/consultants, social activists, volunteers, etc.):

to create challenges or bounties in a decentralized manner (i.e. doctor/consultant creates a list of incentives that a patient needs to adhere to - i.e. take pills, undergo analysis, visit a support group, and a therapist. An incentive could be a small one or a big one. For example, one of the incentives on our list now is to launch an NFT collection (similar to those displayed here
https://nft.blockaids.world/collections), that will help to get crowdfunding for 10k Ukrainian women who had to leave their home country because of the war. And we would like to have a mechanism to reward the team doing this incentive.
We are going to implement categories of users (Global, Active community, Management, Builders, etc.) that will have different roles in our ecosystem
We will have the mechanisms allowing determining whether or not a given incentive has been completed and, secondly, to use it to initiate a payout of reward on-chain

In simple words, we are building a platform that allows the creation of in-system economies/mechanisms to attract users, via rewards, and other participants (doctors/consultants/volunteers/influencers/leaders of opinion/etc.), via engagement and rewards).
Now, I understand that most of these things are not included in our application. The reason: We started a small grant proposal so that our team could start building on Substrate / Polkadot / Kusama and see how the integration works. That is why we left inside the application so far: the fungible token generation, balance display, token transfer, token unlock mechanisms (after consultants/doctor approval), and the backend (as You mentioned) that is quite heavy (incentives manager, dual interaction between patients and doctors/consultants, notifications system and reach admin panel.
As we are going to implement the Loyalty and Reward Electronic System, I can add some of the advanced features mentioned above in the current proposal, so that the technical novelty of our project becomes obvious.
@semuelle Please, let me know if You consider this a good idea. Thank You!

Thanks for the clarification, @blockwebdevs. I understand that this is a serious, real-world application that you are building. As grant evaluators, we mostly look at applications from a technical point of view, though, which is why I described the incentive program as a "simple" token transfer. The reason is that, putting the type of users and their background aside, the workflow you are describing is not a technical novelty and there are a lot of centralised entities at work in the architecture. At the same time, I understand that you don't want to overburden your users with architectural complexities. Therefore, it's challenging to make it suitable for our grants program.
You mention some interesting developments in the application, such as "decentralized identity solutions allows users to securely access their health records". However, it would need a technical description of how this would be achieved, because that is not a trivial problem. But I'll let the rest of the committee chime in.

Thanks for the clarification, @blockwebdevs. I understand that this is a serious, real-world application that you are building. As grant evaluators, we mostly look at applications from a technical point of view, though, which is why I described the incentive program as a "simple" token transfer. The reason is that, putting the type of users and their background aside, the workflow you are describing is not a technical novelty and there are a lot of centralised entities at work in the architecture. At the same time, I understand that you don't want to overburden your users with architectural complexities. Therefore, it's challenging to make it suitable for our grants program. You mention some interesting developments in the application, such as "decentralized identity solutions allows users to securely access their health records". However, it would need a technical description of how this would be achieved, because that is not a trivial problem. But I'll let the rest of the committee chime in.

Hi @semuelle
Below is the short description of DID solution:
Decentralized ID (DID) functionality is a concept that leverages blockchain technology to provide individuals with self-sovereign digital identities. It allows individuals to have control over their personal data and selectively share it with trusted entities, ensuring privacy, security, and autonomy. DIDs are created and managed by individuals themselves, eliminating the need for centralized authorities or intermediaries.
How and for what we are going to use DID technology for BlockAIDS project:

Access to Records: Each individual participating in the BlockAIDS Electronic System Project would have their own unique DID. This DID would serve as their digital identity and provide access to their medical records, treatment history, and other relevant information securely stored on the blockchain. By using their DID, individuals can access their records anytime and anywhere, reducing the barriers to healthcare services.
Treatment Tracking: The web app developed as part of the BlockAIDS Electronic System Project utilize DIDs to track treatment progress. Individuals can log their medication intake, appointments, and other relevant information using their digital identity
Ownership of Medical Data: With DIDs, individuals have ownership and control over their medical data. They can selectively share their information with healthcare providers, researchers, or other entities they trust. This empowers individuals to manage their data and ensures their privacy rights are respected.
Anonymity and Confidentiality: DIDs provide a means to preserve anonymity while still enabling access to necessary services. Participants in the BlockAIDS Electronic System Project can interact with healthcare providers, support organizations, or other stakeholders without revealing their real-world identities. This ensures that individuals can seek the help they need without fear of stigmatization or discrimination.

You can find the full version of our ToR (including the description of development of DID technology) by the link: https://docs.google.com/document/d/1Ns4etjjm6Efolr0h8DGbJVwkmqVHDuiEKwTXAuM3Q6w/edit?usp=sharing
@semuelle is there any action from our side needed to be done, i.e. signing the CLA or adding additional information?

Thanks for your message, @blockwebdevs. I am familiar with DIDs. The question isn't so much what technologies are being used, but what is being developed with the grant. Since I have worked in medical informatics for quite a while, I am quite sceptical about any project wanting to put medically relevant information on-chain or connecting it to a public identifier. That being said, the things you describe in your comment currently aren't part of the application document, so not really part of the review.
I will ping the rest of the committee once more to check if they have any questions or opinions to share.

Thanks for the application @blockwebdevs a I have a couple of comments:

Do you intend to create your own DID solution or utilize an existing one? I'm not seeing much info about DIDs in the application. As my colleague mentioned, is the DID system supposed to be a part of the review?
Are there any docs for the current Power BI app? I'm not sure how to use it or what I'm looking at exactly.
I agree that more technical details could be added into the milestone tables regarding the ink! contracts. For example, what will the main functions be for each?
I agree with my colleagues that although the project is noble, it may not be unique enough to the Polkadot/Kusama ecosystem. The existing Solidity contracts that you link to are only for the ERC721 token itself. Can you expand on the technical novelties of the smart contracts? Is the plan to fully migrate the Power BI data into a new app based on smart contracts?
You mentioned Flutter for mobile; do you plan on creating a separate mobile app, and is this out of the scope of this initial grant?
Regarding your Solana token, am I to understand that you don't plan to conduct any token sales? Please note our guidelines regarding this.
I'm not seeing much activity on the team repo or personal repos. Can you point to any other open-source projects your team has completed in the past?

Thanks again for the application, @blockwebdevs. However, I am sorry to say that the committee has decided not to support it at this point.
We hope that this doesn't prevent you from pursuing it further and we hope to still see you around the ecosystem in the future. In any case, best of luck going forward!


XMLPackage issue in 4.2.1

Hi,
I'm passing this command via a TS.  The script itself runs fine, but when it queries the XML file created using the DAT I get an error
-XMLPackage -XMLDeploymentType PreCache -TargetOSName 'Windows 10' -TargetOSVersion 22H2 -TargetOSArchitecture x64 -DriverInstallMode Recurse
Error is "Retrieved a total of '0' driver packages from XML Package Logic file matching operational mode: Production"
PreCache works when querying the Admin Service, but for operational reasons I need to PreCache drivers ready for OSUpgrade where the Admin Service cannot be queried.
Is there something wrong with the logic file, or do I need to tell the script where there drivers are located in some way?

Found the solution.  The XML file generated by the DAT isn't formatted in the way that the Driver Package script wants it.
Interim solution found here:
https://www.woernd.li/posts/dat-xmllogicpackage-workaround


[ISSUE] Website requests CSS on insecure connection

Describe the bug
The gh-pages branch does not render with any stylesheets. the  sections in the HEAD have plain http instead of https. This should be fixed in the theme's twig.
To Reproduce
Steps to reproduce the behavior:

Go to 'https://karetsu.github.io/woffle'
See error

Expected behavior
Stylesheets should be applied
Screenshots

Desktop (please complete the following information):

OS: macOS
Python version: NA
Makefile installation: Yes

Additional context
NA

Fixed in  14e1414


Update build to use travis

Update CI to use Travis and use improvements from containerd Makefile

LGTM

Good to go @dmcgowan
Can you deal with the aftermath of this?


Refactor Code

Used constants and removed unnecessary code to improve performance and readability

Also fixed Progress output in the console. Works in Windows atleast.

Thanks for your contribution arnabanimesh.


Add hs.finalcutpro:browser:isPlaying()

It would be great to have a function in hs.finalcutpro that tells you if the user is currently playing something in the browser. I guess the only way to do this is to track the browser playhead position?

I liked into this pretty hard when working on Scrolling Timeline/Playhead
Lock. We can create a watcher to try and determine if the playhead is
moving, but it's difficult to determine if it's just the mouse clicking
around or if it's playing. I had something which would take a guess, but it
wasn't too reliable and used a fair bit of CPU...
On Thu, 12 Jan 2017 at 11:06 pm, Chris Hocking<EMAIL_ADDRESS>wrote:

Assigned #202 https://github.com/fcpxhacks/fcpxhacks/issues/202 to
@randomeizer https://github.com/randomeizer.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/fcpxhacks/fcpxhacks/issues/202#event-920684275, or mute
the thread
https://github.com/notifications/unsubscribe-auth/ADbEw_b5--4bzMr7LzjJDoty8mxtKBN8ks5rRiVPgaJpZM4Lhup2
.

Ah, right - no worries!
It's annoying that Apple don't just change the menubar item from "Play" to "Stop"!

Yeah, I know. And the play button doesn't change either...
On Thu, 12 Jan 2017 at 11:16 pm, Chris Hocking<EMAIL_ADDRESS>wrote:

Ah, right - no worries!
It's annoying that Apple don't just change the menubar item from "Play" to
"Stop"!
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/fcpxhacks/fcpxhacks/issues/202#issuecomment-272160424,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ADbEwxABFf4nKxe4oc4ijVlb8jpVQnQ6ks5rRieqgaJpZM4Lhup2
.

Although it does change appearance - so there might be a way to detect that?
Maybe using a similar technique to Interface Inspector?

Cool app! I have no idea how they do their magic though. I'm guessing that
it involves the .nib files, although the fact that they can actually modify
properties live indicates there's something else going on too...
On Thu, 12 Jan 2017 at 11:24 pm, Chris Hocking<EMAIL_ADDRESS>wrote:

Although it does change appearance - so there might be a way to detect
that?
Maybe using a similar technique to Interface Inspector
https://www.interface-inspector.com/?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/fcpxhacks/fcpxhacks/issues/202#issuecomment-272162069,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ADbEw4ww_KO9zX86QkuGVWbrIGHLln3Xks5rRimCgaJpZM4Lhup2
.

Related to #64


Document that routable services need to expose Port 80

Ran into some trouble today using the router until i figured out that the routable service needed to have
  - name: http
    port: 80
    targetPort: 3000

instead of just
  - name: http
    port: 3000

I'll assume that if you're running into this, you're using the router independent of the rest of Deis Workflow... which is awesome!  We've been hoping people would indeed find this useful beyond Workflow.
I would agree that this needs to be documented.

Yes. We are currently using this outside of the rest of the Deis stack as a replacement for our current solution / in preparation for upgrading to deis 2.0

Indeed, I was facepalming myself when I red this, yesterday I was fighting with the router as it was always giving me a 502 and was left wondering why :)


Fix ci breaking due to new dependencies and cargo warnings

Failing on windows due to an extra function call before main (in Rust) on windows only


Duplicated key when loading assembly.

Dear,
I have created a small example with 2 plugins. But it cause duplicated key exception when loading first plugin dll with PluginLoader.CreateFromAssemblyFile().
Could you please check the sample and point out some things wrong?
Please refer attached file for the solution.
Thank so much.
Tuan Ha
PlugEx.zip

I tried running your sample bug didn't get any errors. Can you provide more details?

Correction: I tried running your sample but** didn't get any errors. Can you provide more details?

Dear Nate,
On my PC, it throw exception at the first loading as below image.

Can you share a stack trace and a process dump?

Dear Nate,
Please find the dump file as below link:
https://drive.google.com/open?id=1qgpjm7xRqeF9h65s3PQ241WZp6sCQsIo
And stack trace:
at System.ThrowHelper.ThrowAddingDuplicateWithKeyArgumentException[T](T key)
at System.Collections.Generic.Dictionary2.TryInsert(TKey key, TValue value, InsertionBehavior behavior)    at System.Runtime.Loader.AssemblyDependencyResolver..ctor(String componentAssemblyPath)    at McMaster.NETCore.Plugins.Loader.ManagedLoadContext..ctor(String mainAssemblyPath, IReadOnlyDictionary2 managedAssemblies, IReadOnlyDictionary2 nativeLibraries, IReadOnlyCollection1 privateAssemblies, IReadOnlyCollection1 defaultAssemblies, IReadOnlyCollection1 additionalProbingPaths, IReadOnlyCollection1 resourceProbingPaths, Boolean preferDefaultLoadContext, Boolean isCollectible, Boolean loadInMemory)    at McMaster.NETCore.Plugins.Loader.AssemblyLoadContextBuilder.Build()    at McMaster.NETCore.Plugins.PluginLoader..ctor(PluginConfig config)    at McMaster.NETCore.Plugins.PluginLoader.CreateFromAssemblyFile(String assemblyFile, Action1 configure)
at McMaster.NETCore.Plugins.PluginLoader.CreateFromAssemblyFile(String assemblyFile, Type[] sharedTypes, Action`1 configure)
at McMaster.NETCore.Plugins.PluginLoader.CreateFromAssemblyFile(String assemblyFile, Type[] sharedTypes)
at PlugEx.Startup.LoadLibrary(String pluginFile) in D:\Working\PlugEx\PlugEx\Startup.cs:line 32
at PlugEx.Startup..ctor(IConfiguration configuration) in D:\Working\PlugEx\PlugEx\Startup.cs:line 26

So, the bug is being thrown from a .NET Core API itself, so this is beyond my control to help you with. I would recommend opening this issue at https://github.com/dotnet/runtime. Make sure to include the .deps.json file that should be at "D:\Working\PlugEx\Plug1\bin\Debug\netstandard2.0\plug1.deps.json"
System.Runtime.Loader.AssemblyDependencyResolver..ctor(String componentAssemblyPath)

Oh, and by the way, you should be able to reproduce this independently of my library with this code.
var resolver = new System.Runtime.Loader.AssemblyDependencyResolver(@"D:\Working\PlugEx\Plug1\bin\Debug\netstandard2.0\plug1.dll");

Thank you, Nake.

Closing as this issue is external to this project, so there isn't an action I can take on this.


http request smuggling check

Hi @joohoi
is http request smuggling check in your to-do list for this tool ?
Please add this as other tools lacks concurrency options.
Thanks !

HOW DOES THAT HAVE ANYTHING TO DO WITH A CONTENT DISCOVERY TOOL ( ╯°□°)╯︵ ┻━┻

Hi @attacker007 , as you may deduct from the reactions to this issue, HTTP request smuggling is a completely different beast in means of detection and exploitation and as such, falls out of scope of ffuf. There are tools available for checking this explicitly however.
I'll close the issue, but in case you disagree, feel free to comment and we'll see if there's a reason to reopen it.

Hi @joohoi Thanks for the response. Completely agree.. Yes, there are tools but they lack Concurrency though.
Thanks !!

HOW DOES THAT HAVE ANYTHING TO DO WITH A CONTENT DISCOVERY TOOL ( ╯°□°)╯︵ ┻━┻

I thought its a bigger project than just content discovery. Apologies !


JAVA-3041 Guava session - cloud bundle support. replaced deprecated constructors

Guava session - cloud bundle support
Hey from ThingsBoard team!
I want to share my experience connecting Datastax Astra DB cloud with GuavaSession using Thingsboard.
The old GuavaSession implementation does not connect with cloud Astra DB.
This is because deprecated constructors were in place.
The paper that describes how to implement GuavaSession instead CqlSession is here:
https://docs.datastax.com/en/developer/java-driver/4.4/manual/developer/request_execution/
Here are the screenshots before I tried to connect with the old version:

com.datastax.oss.driver.api.core.AllNodesFailedException: Could not reach any contact point, make sure you've provided valid addresses (showing first 3 nodes, use getAllErrors() for more): Node(endPoint=8ca57896-18c4-4a61-bb26-e2fc05985081-europe-west1.db.astra.datastax.com:29042:a837fe38-9fd5-49a6-958e-7f7ca71ae890, hostId=null, hashCode=30c14db4): [com.datastax.oss.driver.api.core.connection.ConnectionInitException: [s0|control|id: 0x70374974, L:/<IP_ADDRESS>:19408 - R:8ca57896-18c4-4a61-bb26-e2fc05985081-europe-west1.db.astra.datastax.com/<IP_ADDRESS>:29042] Protocol initialization request, step 1 (OPTIONS): unexpected failure (com.datastax.oss.driver.api.core.connection.ClosedConnectionException: Lost connection to remote peer)], Node(endPoint=8ca57896-18c4-4a61-bb26-e2fc05985081-europe-west1.db.astra.datastax.com:29042:ba266e06-dfa4-4171-88cb-75758881bcba, hostId=null, hashCode=4ea6381e): [com.datastax.oss.driver.api.core.connection.ConnectionInitException: [s0|control|id: 0xd498c0a3, L:/<IP_ADDRESS>:12650 - R:8ca57896-18c4-4a61-bb26-e2fc05985081-europe-west1.db.astra.datastax.com/<IP_ADDRESS>:29042] Protocol initialization request, step 1 (OPTIONS): unexpected failure (com.datastax.oss.driver.api.core.connection.ClosedConnectionException: Lost connection to remote peer)], Node(endPoint=8ca57896-18c4-4a61-bb26-e2fc05985081-europe-west1.db.astra.datastax.com:29042:b16cc260-ee81-4017-b6cf-6b793a5b9935, hostId=null, hashCode=61928b01): [com.datastax.oss.driver.api.core.connection.ConnectionInitException: [s0|control|id: 0x0509e0f8, L:/<IP_ADDRESS>:39028 - R:8ca57896-18c4-4a61-bb26-e2fc05985081-europe-west1.db.astra.datastax.com/<IP_ADDRESS>:29042] Protocol initialization request, step 1 (OPTIONS): unexpected failure (com.datastax.oss.driver.api.core.connection.ClosedConnectionException: Lost connection to remote peer)]

	at com.datastax.oss.driver.api.core.AllNodesFailedException.copy(AllNodesFailedException.java:141)
	at com.datastax.oss.driver.internal.core.util.concurrent.CompletableFutures.getUninterruptibly(CompletableFutures.java:149)
	at com.datastax.oss.driver.api.core.session.SessionBuilder.build(SessionBuilder.java:835)
	at com.datastax.oss.driver.core.session.GuavaToAstraConnectTest.astraConnectWithGuava(GuavaToAstraConnectTest.java:59)
...
	Suppressed: com.datastax.oss.driver.api.core.connection.ConnectionInitException: [s0|control|id: 0x70374974, L:/<IP_ADDRESS>:19408 - R:8ca57896-18c4-4a61-bb26-e2fc05985081-europe-west1.db.astra.datastax.com/<IP_ADDRESS>:29042] Protocol initialization request, step 1 (OPTIONS): unexpected failure (com.datastax.oss.driver.api.core.connection.ClosedConnectionException: Lost connection to remote peer)
		at com.datastax.oss.driver.internal.core.channel.ProtocolInitHandler$InitRequest.fail(ProtocolInitHandler.java:356)
		at com.datastax.oss.driver.internal.core.channel.ChannelHandlerRequest.onFailure(ChannelHandlerRequest.java:104)
		at com.datastax.oss.driver.internal.core.channel.InFlightHandler.fail(InFlightHandler.java:381)
		at com.datastax.oss.driver.internal.core.channel.InFlightHandler.abortAllInFlight(InFlightHandler.java:371)
		at com.datastax.oss.driver.internal.core.channel.InFlightHandler.abortAllInFlight(InFlightHandler.java:353)
		at com.datastax.oss.driver.internal.core.channel.InFlightHandler.channelInactive(InFlightHandler.java:331)
...
	Caused by: com.datastax.oss.driver.api.core.connection.ClosedConnectionException: Lost connection to remote peer

Now it works like a charm.

Here is the code example of how I tested the Astra cloud connection with CqlSession and guavaSession
package com.datastax.oss.driver.core.session;

import com.datastax.oss.driver.api.core.CqlSession;
import com.datastax.oss.driver.api.core.cql.AsyncResultSet;
import com.datastax.oss.driver.api.core.cql.ResultSet;
import com.datastax.oss.driver.api.core.cql.Row;
import com.datastax.oss.driver.example.guava.api.GuavaSession;
import com.datastax.oss.driver.example.guava.api.GuavaSessionUtils;
import org.junit.Test;

import java.nio.file.Path;
import java.nio.file.Paths;
import java.util.concurrent.ExecutionException;

public class GuavaToAstraConnectTest {

  static final Path CLOUD_CONFIG_PATH = Paths.get("/home/your_user/projects/astra/secure-connect-thingsboard.zip");
  static final String CLIENT_ID = "tQPHMztQPHMztQPHMztQPHMz";
  static final String SECRET_ID = "5ejkcF9F.j6f64j71Sr.tiRe0Fsq25ejkcF9F.j6f64j71Sr.tiRe0Fsq25ejkcF9F.j6f64j71Sr.tiRe0Fsq2";

  @Test
  public void astraConnectCqlSession() {
    try (CqlSession session = CqlSession.builder()
            .withCloudSecureConnectBundle(CLOUD_CONFIG_PATH)
            .withAuthCredentials(CLIENT_ID, SECRET_ID)
            .build()) {
      ResultSet rs = session.execute("select release_version from system.local");
      Row row = rs.one();

      if (row != null) {
        System.out.println(row.getString("release_version"));
      } else {
        System.out.println("An error occurred.");
      }
    }
  }

  @Test
  public void astraConnectWithGuava() throws ExecutionException, InterruptedException {
    try (GuavaSession session = GuavaSessionUtils.builder()
            .withCloudSecureConnectBundle(CLOUD_CONFIG_PATH)
            .withAuthCredentials(CLIENT_ID, SECRET_ID)
            .build()) {
      AsyncResultSet rs = session.executeAsync("select release_version from system.local").get();
      Row row = rs.one();
      if (row != null) {
        System.out.println(row.getString("release_version"));
      } else {
        System.out.println("An error occurred.");
      }
    }
  }
}

Hello, @smatvienko-tb. Mica brought this to our attention. Thanks for submitting a PR. And thanks for completing the contributor license agreement (CLA).
Just wondering if you've logged a jira for this. I tried to do a search but couldn't find one. You can log a ticket here and link the PR.
We're a little behind but I'll get someone to do a review and let you know. Cheers! 🍻

Hi, @ErickRamirezAU!
Thanks for the feedback!
Here is the new Jira ticket for this PR: https://datastax-oss.atlassian.net/browse/JAVA-3041
Stay tuned!

Here is the new Jira ticket for this PR: https://datastax-oss.atlassian.net/browse/JAVA-3041

Thanks! 👍

So what appears to be happening here is that the necessary config vals for Astra aren't passed through by the old constructor-based mechanism.  SessionBuilder.buildContext() will prefer to use the constructor option if it returns a non-null value; this allows subclasses to define their own context impls.  Problem is that the constructor option doesn't allow for every option to be passed; it looks to have been deprecated before some were added, most relevant to our case before the Astra config values were updated.  And the calling code in this case builds up most of it's data in programmatic arguments before calling buildContext().  So if buildContext() doesn't have every value to be preserved passed as an argument it won't be able to create a ProgrammaticBuilder instance that includes them.  Upshot: any values that aren't passed as args to buildContext() are basically left out.
To prove this out try the following change:
diff --git a/core/src/main/java/com/datastax/oss/driver/api/core/session/SessionBuilder.java b/core/src/main/java/com/datastax/oss/driver/api/core/session/SessionBuilder.java
index 966372fa2..a6eaa0c99 100644
--- a/core/src/main/java/com/datastax/oss/driver/api/core/session/SessionBuilder.java
+++ b/core/src/main/java/com/datastax/oss/driver/api/core/session/SessionBuilder.java
@@ -60,6 +60,7 @@ import java.util.Collections;
 import java.util.HashSet;
 import java.util.List;
 import java.util.Map;
+import java.util.Optional;
 import java.util.Set;
 import java.util.UUID;
 import java.util.concurrent.Callable;
@@ -900,8 +901,10 @@ public abstract class SessionBuilder<SelfT extends SessionBuilder, SessionT> {
             CqlIdentifier.fromCql(defaultConfig.getString(DefaultDriverOption.SESSION_KEYSPACE));
       }

+      DriverContext ctx = buildContext(configLoader, programmaticArguments);
+      Optional<SslEngineFactory> sslFactory = ctx.getSslEngineFactory();
       return DefaultSession.init(
-          (InternalDriverContext) buildContext(configLoader, programmaticArguments),
+              (InternalDriverContext) ctx,
           contactPoints,
           keyspace);

Take a look at sslFactory in a debugger.  When using the current 4.14.1 impl this value is an empty option; the SSL factory configs aren't preserved in the args passed to GuavaSessionBuilder.buildSession().  Applying the changes in this PR you'll see that the SSL factory option is now a non-empty value.  This also explains the observed error; because the SSL configs aren't included Astra hangs up before we even get a chance to pass in an OPTIONS message.
Note that it's the combination of the Guava session with Astra that brings out the problem here.  The example in the docs should work fine if Astra isn't involved.
Need to think a bit about the best way to address this problem.  It's probably okay to make the change contained in this PR but at a minimum we'll also want to update the docs at the same time.

You are right. If the Guava uses the old super constructor and returns non-null, the new features are not reachable.

The documentation seems to be fine. It does not expose the details and refers directly to the git repo. Probably updating the repo is just fine for this page: https://docs.datastax.com/en/developer/java-driver/4.4/manual/developer/request_execution/

Connecting to the Astra example is welcomed.
We found that cloud Keyspace has to be created manually, and install scripts have to not create keyspace for the cloud.
It is ok, but not clear when we have a first experience with the cloud.
And for the cloud we should not use the local DC, keyspace, URL, and SSL parameters that come from the cloud.
It is also not clear on the first steps after using the local Cassandra.
Probably, the better compatibility with the install scripts for local Cassandra will be accepting "CREATE KEYSPACE IF NOT EXISTS" and report success if the keyspace already exists.

Apologies @smatvienko-tb , I've been off working on other projects for the past little while. :(
It's the docs you cite above that originally had me concerned.  Note the ambiguity of the "buildContext(...)" call in the sample code you cited:
public class GuavaSessionBuilder extends SessionBuilder<GuavaSessionBuilder, GuavaSession> {

  @Override
  protected DriverContext buildContext( ... ) { ... }

  @Override
  protected GuavaSession wrap(CqlSession defaultSession) {
    return new DefaultGuavaSession(defaultSession);
  }

My concern was that this code wasn't clearly steering users towards the ProgrammaticArguments version introduced in JAVA-2315.  The more I look at it there more I'm inclined to agree with you, though; I think the docs are probably fine.  They point users at the buildContext() method generally, and from there it should be fairly clear which method should be overridden... especially if our sample code now uses the correct method (which it does with your changes in this PR).
I may still rethink this and change the docs later to show an explicit override of buildContext(ProgrammaticArguments) but it's probably okay for now.

Thanks for the contribution (and for the dialogue) @smatvienko-tb !


feat(tutorial): complete step 2 - Hursley

Closes #
{{short description}}
Changelog
New

{{new thing}}

Changed

{{change thing}}

Removed

{{removed thing}}

:+1::skin-tone-2:   Looks good - I have recorded your completion of this step!

Thanks @lee-chase I must have gotten excited and missed that paragraph. I've fixed and squashed the two commits.

:+1::skin-tone-2:   Looks good - I have recorded your completion of this step!


auro-banner: flip the image and text area

Is your feature request related to a problem? Please describe.
The banner doesn't allow the image and text to be flipped (image on the left and text on the right)
Describe the solution you'd like
A way to flip a banner without creating a specific variant that just flips the banner.
Describe alternatives you've considered
Create an additional variant
Additional context

Work on this update is postponed until the competition of a new auro-[image] element. The concept being that it's better to place all the image features into a nested element versus adding complexity to the auro-banner/cards elements.


Help Wanted: Can I get an example of DaysConfig used inside CalendarComponentOptions?

I am trying to write an application with CalendarComponentOptions.
Nothing happens when I put below piece of code. I see 14 Nov is neither disabled nor displays any text below it.
Help is appreciated!!
<ion-calendar [(ngModel)]="dateMulti"
(onChange)="onChange($event)"
[options]="optionsMulti"  [format]="'YYYY-MM-DD'">

optionsMulti: CalendarComponentOptions = {
pickMode: 'multi',
daysConfig: [{
date: new Date(2018, 11, 14),
subTitle: 'Dummy title'  ,
marked: true,
disable: true
}]
};

Any Help is very much appreciated. I am also trying to disable the all days in the start wee. Don't know how to do it... Please help

Also need this feature on CalendarComponent.


remove sofa runtime context aware

remove sofa runtime context aware

Pull Request Test Coverage Report for Build 219

2 of 2 (100.0%)  changed or added relevant lines in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage decreased (-0.1%) to 67.941%

Totals

Change from base Build 215:
-0.1%

Covered Lines:
2026

Relevant Lines:
2982

💛  - Coveralls

Pull Request Test Coverage Report for Build 219

2 of 2 (100.0%)  changed or added relevant lines in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage decreased (-0.1%) to 67.941%

Totals

Change from base Build 215:
-0.1%

Covered Lines:
2026

Relevant Lines:
2982

💛  - Coveralls


in activemq plugin do client validate and it can not send MQTTReasonCodes.CLIENT_IDENTIFIER_NOT_VALID to mqtt client

in activemq plugin do client validate and it can not send MQTTReasonCodes.CLIENT_IDENTIFIER_NOT_VALID to mqtt client

As with your other PR I dont see any actual useful change here, simply merging existing commits. If you have some changes you should add those to your own branch and raise a PR from it.
You should raise a JIRA for an issue you are looking to address, and then reference it in the commit message (see: most previous commits).
PRs should also target main unless first discussed otherwise, not branches like 2.23.x, as fixes will be picked from main where appropriate. There almost certainly wont be any more 2.23.x releases though as 2.24.0 is almost out, perhaps even late today, having been under release vote for a couple of days already.


Chrome plugin icon not displaying anything

I tried to click on the SL icon in the Chrome toolbar, and it appears to be trying to do something (showing blank popups for parts of the second and then closing them), but in the end nothing happens.

In theory it copypaste into the buffer password generated just for website you're on right now.
But i got reports that it's confusing and think about removing any old-style-pw related stuff entirely. It is indeed confusing.


Cannot install resin-cli on Alpine linux (docker base image)

resin-cli version: 7.5.2
Operating system and architecture: mac os x (docker: Alpine linux), i386

When I try to install the resin-cli latest version on docker base image, which is an Alpine Linux distribution, it fails:
../deps/e2fsprogs/lib/ext2fs/getsectsize.c:34:22: fatal error: linux/fd.h: No such file or directory
 #include <linux/fd.h>
                      ^
compilation terminated.
make: *** [ext2fs.target.mk:179: Release/obj.target/ext2fs/deps/e2fsprogs/lib/ext2fs/getsectsize.o] Error 1
make: Leaving directory '/usr/lib/node_modules/resin-cli/node_modules/ext2fs/build'
gyp ERR! build error
gyp ERR! stack Error: `make` failed with exit code: 2
gyp ERR! stack     at ChildProcess.onExit (/usr/lib/node_modules/npm/node_modules/node-gyp/lib/build.js:258:23)
gyp ERR! stack     at emitTwo (events.js:126:13)
gyp ERR! stack     at ChildProcess.emit (events.js:214:7)
gyp ERR! stack     at Process.ChildProcess._handle.onexit (internal/child_process.js:198:12)
gyp ERR! System Linux 4.9.87-linuxkit-aufs
gyp ERR! command "/usr/bin/node" "/usr/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js" "rebuild"
gyp ERR! cwd /usr/lib/node_modules/resin-cli/node_modules/ext2fs
gyp ERR! node -v v8.9.3
gyp ERR! node-gyp -v v3.6.2
gyp ERR! not ok
npm WARN optional SKIPPING OPTIONAL DEPENDENCY<EMAIL_ADDRESS>(node_modules/resin-cli/node_modules/removedrive):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for<EMAIL_ADDRESS>wanted {"os":"win32","arch":"any"} (current: {"os":"linux","arch":"x64"})
npm WARN optional SKIPPING OPTIONAL DEPENDENCY<EMAIL_ADDRESS>(node_modules/resin-cli/node_modules/macmount):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for<EMAIL_ADDRESS>wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"x64"})

npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR<EMAIL_ADDRESS>install: `prebuild-install || node-gyp rebuild`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the<EMAIL_ADDRESS>install script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

npm ERR! A complete log of this run can be found in:
npm ERR!     /root/.npm/_logs/2018-06-13T06_39_20_427Z-debug.log

Probably, the problem is related with musl and glibc. I read that glibc is the standard default library in most of the linux distributions, but in Alpine musl is used. I attach the Dockerfile that I am using:
FROM docker

RUN apk --update --no-cache add bash git python python3 make openssh g++ nodejs nodejs-npm yarn
RUN npm install resin-cli -g --production --unsafe-perm

 Front conversations

Hi @jcozar87. Can you post more of the install log here? What should happen is that npm installs use prebuild releases of ext2fs, which avoid the need to manage the build environment. The built binaries are hosted here: https://github.com/resin-io/node-ext2fs/releases/. There'll probably be an error somewhere in the logs where it tries to look up some specific configuration from there which doesn't exist.
In addition, as an alternative, we also have a prebuilt standalone build which avoids the need to use node & npm directly entirely. See 'standalone install' in the readme. Does that work for you? It's not quite as stable yet, but long term we're planning on moving in that direction and moving away from npm installs entirely, to avoid exactly these kind of problems.

@jcozar87 I think that means something went wrong in the unzipping process, and the binary has the wrong permissions. If you run chmod +x ./resin-cli/resin, you should be able to run it as resin directly. Does that work for you?
The zip itself includes the permissions metadata that should do that for you, so I suspect this means you've done something unusual in unzipping the build. In future we'll have a proper installer, so you won't even need to think about that.

I'm going to close this - the original issue here was actually caused by a partially failed publish of ext2fs (https://github.com/resin-io/node-ext2fs/issues/30), which is why you had to do a native install in the first place.
You should be able to reinstall from scratch with npm and have everything work now, or you can continue using the standalone build as above instead if it's working nicely for you. Thanks for reporting this!


Suspicious lifetime of C++ exception messages

I've just spotted the following pattern in many functions:
int CEXR_InputFile_from_stream(CEXR_IStream *stream, int threads, CEXR_InputFile **out, const char **err_out) {
    try {
        *out = reinterpret_cast<CEXR_InputFile *>(new InputFile(*reinterpret_cast<IStream *>(stream), threads));
    } catch(const std::exception &e) {
        *err_out = e.what();
        return 1;
    }

    return 0;
}

At the call site:
        let mut error_out = ptr::null();
        let error = unsafe { CEXR_InputFile_from_stream(istream_ptr, 1, &mut out, &mut error_out) };
        if error != 0 {
            let msg = unsafe { CStr::from_ptr(error_out) };
            Err(Error::Generic(msg.to_string_lossy().into_owned()))
        } else {
...

It looks highly suspicious as the string pointed by error_out at the point of use is outside its "owner's" lifetime (the exception object).
The original exception object should be destroyed at the exit of the catch block, making the pointer coming out of it a dangling reference.
I wonder how this Could Have Possibly Ever Worked™. Am I missing something? I hope I am wrong here because, otherwise, the security implications would be huge.

I think this is indeed a serious bug, and has worked historically the same way use-after-free usually does; the memory just hadn't been clobbered yet. Each instance of this pattern should be replaced with copying the exception string into a rust-allocated buffer.

Bummer. Looks like a Russian roulette bug.

A convenient approach might be to have rust code define a constructor function returning a pointer from Vec::into_raw and callable from C inside the exception handler, and then pass the resulting value right back to rust where the value can be recovered with from_raw.


Failed to execute goal com.github.eirslett:frontend-maven-plugin

Hi,
Thanks for this repo.
Running mvn clean install generates the following error:
[ERROR] Failed to execute goal com.github.eirslett:frontend-maven-plugin:1.7.6:npm (npm run build) on project frontend: Failed to run task: 'npm run build' failed. org.apache.commons
.exec.ExecuteException: Process exited with an error: 1 (Exit value: 1) -> [Help 1]
org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal com.github.eirslett:frontend-maven-plugin:1.7.6:npm (npm run build) on project frontend: Failed to run
task

My work environment:
$ npm -v
6.10.2

$ node -v
v10.16.0

What could the problem be?
Nikk

Hi,
I can't replicate this error in my environment. I found this issue, where somebody fixed a similar issue by removing eirslett from their m2 repository.
Your local version of npm should not be a problem, as the plugin installs the version given in the frontend pom.xml file.
As for the Maven and JDK, right now I use:
mvn --version Apache Maven 3.6.0 Maven home: /usr/share/maven Java version: 11, vendor: Oracle Corporation, runtime: /usr/lib/jvm/jdk-11 Default locale: en_US, platform encoding: UTF-8 OS name: "linux", version: "4.15.0-55-generic", arch: "amd64", family: "unix"
But the project is built correctly also on the environment with Java8 ($ export JAVA_HOME=/usr/lib/jvm/java-1.8.0-openjdk-amd64).
I pushed an updated project on the develop branch (updates in pom and package.json), you can try to check out to develop, pull my changes (with the https://github.com/little-pinecone/spring-boot-angular-scaffolding/commit/7991398aac11c6a926cf0d83967a2322f600c8d1 commit) and try to run $mvn clean install there. The npm audit finds no vulnerabilities on the develop branch:
`spring-boot-angular-scaffolding/frontend/src/main/angular$ npm audit
                   === npm audit security report ===

found 0 vulnerabilities
in 19178 scanned packages
 Below you can find my output when I build the frontend manually ($ npm run build):spring-boot-angular-scaffolding/frontend/src/main/angular$ npm run build

<EMAIL_ADDRESS>build /home/little_pinecone/projects/spring_boot_with_angular/spring-boot-angular-scaffolding/frontend/src/main/angular
ng build --prod

Date: 2019-07-29T15:54:16.404Z
Hash: 2de0e7bda2ba18566052
Time: 14824ms
chunk {0} runtime-es5.741402d1d47331ce975c.js (runtime) 1.41 kB [entry] [rendered]
chunk {1} main-es5.d83c89f8f3b162ef8cc9.js (main) 154 kB [initial] [rendered]
chunk {2} polyfills-es5.ba12c162d5f93eae9902.js (polyfills) 111 kB [initial] [rendered]
Date: 2019-07-29T15:54:28.053Z
Hash: 75c6d914add26ca98e9c
Time: 11627ms
chunk {0} runtime-es2015.858f8dd898b75fe86926.js (runtime) 1.41 kB [entry] [rendered]
chunk {1} main-es2015.fa43b540cb63890bbc07.js (main) 134 kB [initial] [rendered]
chunk {2} polyfills-es2015.444f9ad7571234916d9d.js (polyfills) 36.4 kB [initial] [rendered]
chunk {3} styles.09e2c710755c8867a460.css (styles) 0 bytes [initial] [rendered]
`
In my case everything is correct, but, maybe in your case, you will see more specific errors when trying to run $ npm run build from the console.

I have same error here and even deleting ~/m2/repository/com/github/eirslett and rebuild does not solve my problem.

I have same error here and even deleting ~/m2/repository/com/github/eirslett and rebuild does not solve my problem.

My problem was that I am using an old version of intellij with bundled maven (3.0.5).
Making the IDEA uses the last version of maven solves my problem.

Unfortunately, I'm unable to replicate this issue. Running:mvn clean install works in my case.
Does running commands like npm audit or npm run build gives you any warnings or errors? If not, it may be an issue with the frontend-maven-plugin library. You can find great documentation and usage examples in the project README.
There was a new release for this library, 11 days ago - 1.8.0. You can find all releases under the https://repo1.maven.org/maven2/com/github/eirslett/frontend-maven-plugin/ link.
You can find similar issues in the repo Issues tab - like issue 740 or issue 378.
I closed this issue accidentally. I will keep it open for some time in case any new feedback.

i have the same error :
Failed to execute goal com.github.eirslett:frontend-maven-plugin:1.12.0:npm (npm build) on project front
end: Failed to run task: 'npm run-script build' failed. org.apache.commons.exec.ExecuteException: Process exited
with an error: -4058 (Exit value: -4058)
I need help

com.github.eirslett
frontend-maven-plugin
1.12.0

v14.15.4
6.14.11
https://npm.taobao.org/mirrors/node/

install node and npm

install-node-and-npm

generate-resources

npm install

npm

install

npm build

npm

generate-resources

run-script build

Unfortunately, I'm unable to replicate this issue.
I updated the frontend-maven-plugin version to 1.12.0 and ran mvn clean install command. The project builds correctly according to my log output:
[INFO] --- frontend-maven-plugin:1.12.0:npm (npm run build) @ frontend ---
[INFO] Running 'npm run build' in /home/littlepinecone/projects/spring-boot-angular-scaffolding/frontend/src/main/angular
[INFO]
[INFO] ><EMAIL_ADDRESS>build
[INFO] > ng build --configuration production
[INFO]
[INFO] - Generating browser application bundles (phase: setup)...
[INFO] ✔ Browser application bundle generation complete.
[INFO] ✔ Browser application bundle generation complete.
[INFO] - Copying assets...
[INFO] ✔ Copying assets complete.
[INFO] - Generating index html...
[INFO] ✔ Index html generation complete.
…
[INFO] Build at: 2021-08-20T07:19:51.314Z - Hash: d85f6a49f83e3271dd67 - Time: 12342ms

However, I found the frontend-maven-plugin when it runs npm run build can't find package.json file issue on StackOverflow where the errno -4058 was caused by the package.json location not given in the workingDirectory property.
Maybe the error you're seeing has something to do with the way you configured the plugin in your pom.xml file? Can you see in your logs what caused the error?
I would recommend consulting the Optional configuration section in the plugin documentation.
Furthermore, make sure that the Node.js version you use is compatible with your Angular version. Angular requires an active or maintenance LTS version of Node.js.

I am facing the same issue not in my local but when I push my code in the github the build is failed Can anyone suggest any changes I can make. Thanks


feat(tooltip): adds tooltip support for restMs and delay properties

implements #589

[x] I have followed the Your First Code Contribution section of the Contributing guide

This change adds support for floating-ui's useHover restMs and delay props to the Tooltip component to enable delayed opening/closing of tooltips.

I understand the practical appeal, but this functionality isn't available in the upstream library at flowbite.com, so I'm not sure if we should add it here.
@zoltanszogyenyi I defer to you on this one - it seems like this would be a useful feature, and it's also pretty difficult to create a wrapper of our component to achieve this. You would probably be forced to patch flowbite-react to do so.

It looks like the upstream has support for trigger="none" and exposes show(), hide(), and toggle() functions for custom triggers. It just seems kind of wasteful to have to reimplement  delay when it's supported by the underlying floating-ui implementation.

Nice one! It only needs re-build since we now have new monorepo structure (see #1264).
If u feel like u don't have the time, I can take it from here, just let me know! 🤝

@SutuSebastian I doubt I'll have time for this in the near-term. Feel free to pick it up if you'd like.


[Task]: Document guidelines for how version guards should be specified for Beam dependencies

What needs to happen?
We should document this in install_requires and potentially  in contributor guide and/or release guide sections of developer docs and have some process that enforces absence of obvious mistakes such as:

depending on an exact version of a dependency.
specifying '<=' in upper bound instead of a strict '<'.
omitting explanations for non-obvious choices, such as a too open or too narrow range.

It might be possible to have a unit test or release validation script that automatically verifies some of that.
Issue Priority
Priority: 2 (default / most normal work should be filed as P2)
Issue Components

[X] Component: Python SDK
[ ] Component: Java SDK
[ ] Component: Go SDK
[ ] Component: Typescript SDK
[ ] Component: IO connector
[ ] Component: Beam examples
[ ] Component: Beam playground
[ ] Component: Beam katas
[ ] Component: Website
[ ] Component: Spark Runner
[ ] Component: Flink Runner
[ ] Component: Samza Runner
[ ] Component: Twister2 Runner
[ ] Component: Hazelcast Jet Runner
[ ] Component: Google Cloud Dataflow Runner

subtask of #25652

related: https://beam.apache.org/contribute/dependencies/

Content (for self reference) https://docs.google.com/document/d/1euZogGjbW4VZNJMFrA5AL1keR5gZO5l45H9b9CoQ0SI/edit


[You can't ban users, that aren't in your room] Spam Bots...

Spam bots are now in DogeHouse! Yay!!! /s

This bot joins, chats, then leaves all at the same time.

You can't ban users, that aren't in your room.

same here i approve this issue

Click on their name in-room chat? which gives you the ban button.

@nadirabbas

You can't ban users, that aren't in your room.
The image above that line, is me clicking on their name in chat.

this issue is on the new design too, and it shows "no audio consumer for some reason" for people who had left the room and said something in chat.

@vishy-dev is shows no audio consumer for everyone...

Thank you for the idea. Will get to coding immediately after class.

Spam bots are now in DogeHouse! Yay!!! /s

This bot joins, chats, then leaves all at the same time.

You can't ban users, that aren't in your room.

Yeah this was turned off, never meant for it to do this. issue since fixed

This issue should be closed as it has been fixed


Test if continuous integration is faulty

Continuous integration builds began failing due to Julia errors. I suspected that this did not have to do with actual code in the pipeline, but with some update to julia versions behind the scenes, resulting in package incompatibilities when creating the julia environment during testing. To test this, I created a branch from main, added an empty file and opened a pul request to initiate continuous integration tests.

Fixing the julia version in the continuous integration .yaml file to match the Manifest.toml file fixed this error and allowed continuous integration to complete successfully.

https://github.com/TARGENE/targene-pipeline/issues/209


CI: Replace deprecated pypy3 with pypy-3.8

pypy3 is deprecated and is not available in newer images:
https://github.com/actions/setup-python/issues/244#issuecomment-925966022
Instead explicitly specify the version:
https://github.com/actions/setup-python#specifying-a-pypy-version
Committed via https://github.com/asottile/all-repos

Merged in https://github.com/jazzband/django-pipeline/pull/759 🚀


Enchantment: Re ranking client.

PR Contains the Following Changes
Re-Ranking Cohere Client
This update introduces a new interface ReRankInterface for the re-ranking client:
type ReRankInterface interface {
	reRank(request reRankRequest) (*[]reRankResult, error)
}

This interface is added to the BaseLocatr struct:
type BaseLocatr struct {
       // other fields
	reRankClient  ReRankInterface
}

There is no default re-rank client creation mechanism. To create a Cohere client, call locatr.NewCohereClient and pass the object returned from it to locatr.BaseLocatrOptions.

The default Cohere model we are using is rerank-english-v3.0.
The re-rank score threshold for a result to be included in the final result is 0.9.

Chunking Algorithm

To perform chunking for re-ranking, a new function SplitHtml has been added.
The function is borrowed from Langchain's RecursiveCharacterTextSplitter.
The maximum number of characters in a chunk to be included is 4000, as the RecursiveCharacterTextSplitter does the same.

Examples Addition

The following example files have been added: default-llm-client, rerank.

Minor File Structure Changes

Moved all cache-related functions to cache.go.
A new constants.go file has been created to store constants.
Removed doc.go as we are adding documentation in the README. Maintaining two sets of documentation is unnecessary.
Removed meta/locate_element.prompt and created a constant LOCATR_PROMPT.

#13

Instead of sending only the chunks with higher than 0.9 relevance score. Send the TOP_K reranked-chunks to LLM, and retry if the LLM fails in finding the locator.
Send the TOP_K chunks in first try, chunks[TOP_K: TOP_K*2] chunks in the second and chunks[TOP_K*2:] in the third. For the first retry you can send the next TOP_K chunks but if you don't find the element in the retry; for the send retry send the entire remaining chunks to save time.

Rather than changing the algorithm to use TOP_K chunks instead of RELEVANCE_THRESHOLD, let's evaluate which uses less_tokens, is_faster, retry_count, fail_rate. This should be done for multiple sites and multiple examples including the cases where reranker may not be able to fully infer the required chunk.
Once we get back the results, we can finalize which algorithm is the better option. @Neeraj319


About Swift package

i am highly requested to this team please add swift package . thanks

@R3l0ad3d Thanks for the suggestion. I will add it in the next release.

@R3l0ad3d I released Mantis 1.0.0 with swift package support. You can check if it works for you.

thanks .


avdecc-lib Compile error

error C2079: “avdecc_lib::audio_unit_descriptor_imp::audio_unit_desc”uses undefined struct“avdecc_lib::jdksavdecc_descriptor_audio”
2>  audio_map_descriptor_imp.cpp
How to slove this，thanks

What operating system?
What branch are you building?

windows7
which branch should I build?
I am not good at English, I am sorry.

On 8/3/2015 9:49 AM, liruilyrics wrote:

windows7
which branch should I build?
I am not good at English, I am sorry.
—
Reply to this email directly or view it on GitHub
https://github.com/audioscience/avdecc-lib/issues/213#issuecomment-127241324.

W7 32-bit or 64-bit?
What compiler?
--
Andrew Elder
AudioScience, Inc.
+1-585-271-8870
www.audioscience.com

W7 64-bit
VS2013

Is this still an issue?

Close - no response


llvm_8, llvm_9, llvm_10: apply upstream fix for gcc-11

On gcc-11 build fails due to missing  include.
The fix pulls upstream change as is.

What about llvm_5, llvm_6, llvm_7? Is this not required?
(For llvm_12 and llvm_13 I already checked these contain the patch).

Other llvm versions build without this change. Tested locally as: nix build -f . --no-link llvm_{5..13}.
llvm_5 needs slightly different tweak: https://github.com/NixOS/nixpkgs/pull/139008


Twitch tracks are not playing

Hello, I'm using your Lavaplayer fork @ 1.3.94 (haven't tested this on .95 yet) in a Lavalink.jar and playing a Twitch url seems to drop the track immediately after queueing. On Lavalink I see a play op with the track, and then a stop op occurs right after it. I've been testing this on various nodes in the EU and East US and it seems consistent across all of them so far.

Sorry for the trouble, it seems like it's working again on all of my test bots... I'm just going to blame Twitch on this one. I was testing with both a Lavalink CI jar from the dev branch (#1252) and also a Lavalink.jar built from https://github.com/Walkyst/lavalink-fork and neither were working, so I had assumed that it was lavaplayer causing the issue.


Update version #'s for default modules and packages for version 09.04.00

Closes #2678

Closes #2678
Summary

Closing due to #2667


'redirect_mismatch' error with hosted UI

Note: If your question is regarding the AWS Amplify Console service, please log it in the
official AWS Amplify Console forum

** Which Category is your question related to? **
Auth / Hosted UI
** What AWS Services are you utilizing? **
Cognito, Amplify Console
** Provide additional details e.g. code snippets **
Hi,
My auth work flow worked fine with the hosted UI when I was only using http://localhost:3000/ as the sign in/sign out url. When amplify console created a dev build, it hosted the frontend on a different url (https://dev.<some_id>.amplifyapp.com/ in my case). When opening the hosted UI from this url, it complained "redirect_mismatch", which is understandable since I only have localhost configured in cognito at this point.
I ran amplify update auth to add the console provided app url to the sign in/sign out urls, amplify push then git commit & git push to make the amplify console pick up the changes. However, the console hosted app still gave me "redirect_mismatch" error. I checked the aws-export.js file and cognito console, the redirect urls are exactly the same ("http://localhost:3000/,https://dev.<some_id>.amplifyapp.com/"). I used Chrome's inspection tool to check the actual redirect_uri string in the HTTP request, also exactly the same. I have no idea why the hosted UI is complaining mismatch.
Then I found out the app stopped working on my localhost, too. Same "redirect_mismatch" error. :(

Any help will be appreciated!

@YangMann do you've a repro project you could share with us?

@attilah sorry the repo I'm working on is private. But I can share the details about redirect URLs.
After having two sign-in/sign-out redirect URLs in amplify auth, amplify push, the generated "redirect link" to the hosted UI page is
https://<app_id>.auth.us-east-1.amazoncognito.com/login?
redirect_uri=http%3A%2F%2Flocalhost%3A3000%2F%2Chttps%3A%2F%2Fdev.<app_id>.amplifyapp.com%2F
&response_type=code&client_id=<client_id>
&identity_provider=COGNITO
&scopes=phone%2Cemail%2Copenid%2Cprofile%2Caws.cognito.signin.user.admin
&state=<state_string>
&code_challenge=<challenge>
&code_challenge_method=S256

I think the problem is that the redirect_uri parameter here in the generated link contains two URLs. I kinda walked around this by

removing localhost from the sign-in/sign-out urls, keeping only the amplifyapp.com one
amplify push
modify /amplify/backend/auth/cognito<some_id>/parameters.json, add http://localhost:3000/ back to the CallbackURLS and LogoutURLs in oAuthMetadata
add http://localhost:3000/ to the callback URLs and logout URLs on Cognito Console

At this point, when I run on localhost, the generated link will only contain localhost in the redirect_uri parameter. I haven't tested my app on amplify domain yet, but I assume it should work.

@attilah I have a question: how is the redirect uri populated when calling Auth.federatedSignIn()?


Accessibility on bottom sheet.

Hi guys , this is more of a question than an issue.
I am making an react native app which supports accessibility ( Three finger swipe when voice-over is turned on , etc, etc) . Is there a way to make the bottom sheet accessible ?  Any suggestions would be highly appreciated.

You could wrap the header in a TouchableOpacity/TouchableHiglight and toggle the open and close when onPress. Hope this helped you

@BloodyBeans. Thank you for your suggestion. Turns out IOS way of dragging the bottom sheet it to double tap and hold the item until it is selected . Then , it can be dragged as necessary when voice over is running.