Getting AssertionError message (Locator expected to be editable Actual value: <element(s) not found> )

I installed the add-on and
2024-08-18T10:24:11.530 INFO: Xfinity Internet Usage Starting
2024-08-18T10:24:11.538 INFO: Connected to MQTT Broker!
2024-08-18T10:24:22.657 INFO: Loading Internet Usage (URL: https://login.xfinity.com/login)
2024-08-18T10:24:22.801 INFO: Entering username (URL: https://login.xfinity.com/login)
2024-08-18T10:25:10.354 WARNING: Retrying main.run_playwright in 1.0 seconds as it raised AssertionError: Locator expected to be editable
Actual value: <element(s) not found>
Call log:
LocatorAssertions.to_be_editable with timeout 45000ms

waiting for locator("input#passwd")
.
2024-08-18T10:25:26.555 INFO: Loading Internet Usage (URL: https://login.xfinity.com/login)
2024-08-18T10:25:26.614 INFO: Entering username (URL: https://login.xfinity.com/login)
2024-08-18T10:26:14.447 WARNING: Retrying main.run_playwright in 2.0 seconds as it raised AssertionError: Locator expected to be editable
Actual value: <element(s) not found>
Call log:
LocatorAssertions.to_be_editable with timeout 45000ms
waiting for locator("input#passwd")
.

Does this happen every time you start the addon?
On Sun, Aug 18, 2024 at 10:32 AM Stan Lee Cee @.***>
wrote:

I installed the add-on and
2024-08-18T10:24:11.530 INFO: Xfinity Internet Usage Starting
2024-08-18T10:24:11.538 INFO: Connected to MQTT Broker!
2024-08-18T10:24:22.657 INFO: Loading Internet Usage (URL:
https://login.xfinity.com/login)
2024-08-18T10:24:22.801 INFO: Entering username (URL:
https://login.xfinity.com/login)
2024-08-18T10:25:10.354 WARNING: Retrying main.run_playwright in 1.0
seconds as it raised AssertionError: Locator expected to be editable
Actual value: <element(s) not found>
Call log:
LocatorAssertions.to_be_editable with timeout 45000ms

waiting for locator("input#passwd")
.
2024-08-18T10:25:26.555 INFO: Loading Internet Usage (URL:
https://login.xfinity.com/login)
2024-08-18T10:25:26.614 INFO: Entering username (URL:
https://login.xfinity.com/login)
2024-08-18T10:26:14.447 WARNING: Retrying main.run_playwright in 2.0
seconds as it raised AssertionError: Locator expected to be editable
Actual value: <element(s) not found>
Call log:
LocatorAssertions.to_be_editable with timeout 45000ms
waiting for locator("input#passwd")
.

—
Reply to this email directly, view it on GitHub
https://github.com/thor0215/hassio-xfinity-usage/issues/19, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AL7JXGKTQ2IQEZBL24LPY4LZSC47VAVCNFSM6AAAAABMWOTNYSVHI2DSMVQWIX3LMV43ASLTON2WKOZSGQ3TEMBSGY4TINQ
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>

Yes it happend everytime.  I tried restarting several times.

It seems to have worked itself out on its own.
2024-08-19T05:08:59.397 INFO: Updating Session Details
2024-08-19T05:09:01.322 INFO: Updating Plan Details
2024-08-19T05:09:03.660 INFO: Updating Usage Details
2024-08-19T05:09:04.303 INFO: Usage data retrieved and processed
2024-08-19T05:09:04.303 INFO: Updating MQTT topic homeassistant/sensor/xfinity_internet/config
2024-08-19T05:09:04.303 INFO: Updating MQTT topic homeassistant/sensor/xfinity_internet/state
2024-08-19T05:09:04.304 INFO: Updating MQTT topic homeassistant/sensor/xfinity_internet/attributes
2024-08-19T05:09:05.876 INFO: Sleeping for 900 seconds
2024-08-19T05:24:16.963 INFO: Loading Internet Usage (URL: https://login.xfinity.com/login)
2024-08-19T05:24:17.043 INFO: Entering username (URL: https://login.xfinity.com/login)
2024-08-19T05:24:20.154 INFO: Entering password (URL: https://login.xfinity.com/login)
2024-08-19T05:24:27.307 INFO: Updating Session Details
2024-08-19T05:24:29.448 INFO: Updating Plan Details
2024-08-19T05:24:29.812 INFO: Updating Usage Details
2024-08-19T05:24:30.253 INFO: Usage data retrieved and processed
2024-08-19T05:24:30.253 INFO: Updating MQTT topic homeassistant/sensor/xfinity_internet/config
2024-08-19T05:24:30.253 INFO: Updating MQTT topic homeassistant/sensor/xfinity_internet/state
2024-08-19T05:24:30.253 INFO: Updating MQTT topic homeassistant/sensor/xfinity_internet/attributes
2024-08-19T05:24:32.859 INFO: Sleeping for 900 seconds
2024-08-19T05:39:42.689 INFO: Loading Internet Usage (URL: https://login.xfinity.com/login)
2024-08-19T05:39:42.781 INFO: Entering username (URL: https://login.xfinity.com/login)
2024-08-19T05:39:45.968 INFO: Entering password (URL: https://login.xfinity.com/login)
2024-08-19T05:39:53.601 INFO: Updating Session Details
2024-08-19T05:39:55.353 INFO: Updating Plan Details
2024-08-19T05:39:56.886 INFO: Updating Usage Details
2024-08-19T05:39:57.504 INFO: Usage data retrieved and processed
2024-08-19T05:39:57.504 INFO: Updating MQTT topic homeassistant/sensor/xfinity_internet/config
2024-08-19T05:39:57.504 INFO: Updating MQTT topic homeassistant/sensor/xfinity_internet/state
2024-08-19T05:39:57.505 INFO: Updating MQTT topic homeassistant/sensor/xfinity_internet/attributes
2024-08-19T05:39:59.719 INFO: Sleeping for 900 seconds
2024-08-19T05:55:08.753 INFO: Loading Internet Usage (URL: https://login.xfinity.com/login)
2024-08-19T05:55:08.851 INFO: Entering username (URL: https://login.xfinity.com/login)
2024-08-19T05:55:11.984 INFO: Entering password (URL: https://login.xfinity.com/login)
2024-08-19T05:55:19.663 INFO: Updating Session Details
2024-08-19T05:55:24.592 INFO: Updating Usage Details
2024-08-19T05:55:25.367 INFO: Updating Plan Details
2024-08-19T05:55:25.685 INFO: Usage data retrieved and processed
2024-08-19T05:55:25.685 INFO: Updating MQTT topic homeassistant/sensor/xfinity_internet/config
2024-08-19T05:55:25.686 INFO: Updating MQTT topic homeassistant/sensor/xfinity_internet/state
2024-08-19T05:55:25.686 INFO: Updating MQTT topic homeassistant/sensor/xfinity_internet/attributes
2024-08-19T05:55:26.908 INFO: Sleeping for 900 seconds
2024-08-19T06:10:37.352 INFO: Loading Internet Usage (URL: https://login.xfinity.com/login)
2024-08-19T06:10:37.429 INFO: Entering username (URL: https://login.xfinity.com/login)
2024-08-19T06:10:40.561 INFO: Entering password (URL: https://login.xfinity.com/login)
2024-08-19T06:10:49.737 INFO: Updating Session Details
2024-08-19T06:10:51.632 INFO: Updating Plan Details
2024-08-19T06:10:53.088 INFO: Updating Usage Details
2024-08-19T06:10:59.157 INFO: Usage data retrieved and processed
2024-08-19T06:10:59.157 INFO: Updating MQTT topic homeassistant/sensor/xfinity_internet/config
2024-08-19T06:10:59.158 INFO: Updating MQTT topic homeassistant/sensor/xfinity_internet/state
2024-08-19T06:10:59.158 INFO: Updating MQTT topic homeassistant/sensor/xfinity_internet/attributes
2024-08-19T06:11:00.577 INFO: Sleeping for 900 seconds
2024-08-19T06:26:10.906 INFO: Loading Internet Usage (URL: https://login.xfinity.com/login)
2024-08-19T06:26:11.002 INFO: Entering username (URL: https://login.xfinity.com/login)
2024-08-19T06:26:14.218 INFO: Entering password (URL: https://login.xfinity.com/login)
2024-08-19T06:26:22.963 INFO: Updating Session Details
2024-08-19T06:26:24.717 INFO: Updating Plan Details
2024-08-19T06:26:25.104 INFO: Updating Usage Details
2024-08-19T06:26:25.775 INFO: Usage data retrieved and processed
2024-08-19T06:26:25.776 INFO: Updating MQTT topic homeassistant/sensor/xfinity_internet/config
2024-08-19T06:26:25.776 INFO: Updating MQTT topic homeassistant/sensor/xfinity_internet/state
2024-08-19T06:26:25.776 INFO: Updating MQTT topic homeassistant/sensor/xfinity_internet/attributes
2024-08-19T06:26:28.690 INFO: Sleeping for 900 seconds
2024-08-19T06:41:37.832 INFO: Loading Internet Usage (URL: https://login.xfinity.com/login)
2024-08-19T06:41:37.941 INFO: Entering username (URL: https://login.xfinity.com/login)
2024-08-19T06:41:41.124 INFO: Entering password (URL: https://login.xfinity.com/login)
2024-08-19T06:42:29.457 WARNING: Retrying main.run_playwright in 1.0 seconds as it raised TimeoutError: Timeout 45000ms exceeded.
=========================== logs ===========================
waiting for navigation to "https://www.xfinity.com/learn/internet-service/auth" until 'load'
navigated to "https://login.xfinity.com/login"
============================================================.
2024-08-19T06:42:40.192 INFO: Loading Internet Usage (URL: https://login.xfinity.com/login)
2024-08-19T06:42:40.312 INFO: Entering username (URL: https://login.xfinity.com/login)
2024-08-19T06:42:43.513 INFO: Entering password (URL: https://login.xfinity.com/login)
2024-08-19T06:42:50.661 INFO: Updating Session Details
2024-08-19T06:42:52.875 INFO: Updating Plan Details
2024-08-19T06:42:53.391 INFO: Updating Usage Details
2024-08-19T06:42:53.764 INFO: Usage data retrieved and processed
2024-08-19T06:42:53.765 INFO: Updating MQTT topic homeassistant/sensor/xfinity_internet/config
2024-08-19T06:42:53.765 INFO: Updating MQTT topic homeassistant/sensor/xfinity_internet/state
2024-08-19T06:42:53.765 INFO: Updating MQTT topic homeassistant/sensor/xfinity_internet/attributes
2024-08-19T06:42:56.605 INFO: Sleeping for 900 seconds
2024-08-19T06:58:06.213 INFO: Loading Internet Usage (URL: https://login.xfinity.com/login)
2024-08-19T06:58:06.313 INFO: Entering username (URL: https://login.xfinity.com/login)
2024-08-19T06:58:53.798 WARNING: Retrying main.run_playwright in 1.0 seconds as it raised AssertionError: Locator expected to be editable
Actual value: <element(s) not found>
Call log:
LocatorAssertions.to_be_editable with timeout 45000ms

waiting for locator("input#passwd")
.
2024-08-19T06:59:05.575 INFO: Loading Internet Usage (URL: https://login.xfinity.com/login)
2024-08-19T06:59:05.672 INFO: Entering username (URL: https://login.xfinity.com/login)
2024-08-19T06:59:09.905 INFO: Entering password (URL: https://login.xfinity.com/login)
2024-08-19T06:59:18.780 INFO: Updating Session Details
2024-08-19T06:59:20.923 INFO: Updating Plan Details
2024-08-19T06:59:22.680 INFO: Updating Usage Details
2024-08-19T06:59:23.117 INFO: Usage data retrieved and processed
2024-08-19T06:59:23.117 INFO: Updating MQTT topic homeassistant/sensor/xfinity_internet/config
2024-08-19T06:59:23.117 INFO: Updating MQTT topic homeassistant/sensor/xfinity_internet/state
2024-08-19T06:59:23.118 INFO: Updating MQTT topic homeassistant/sensor/xfinity_internet/attributes
2024-08-19T06:59:26.364 INFO: Sleeping for 900 seconds

It seems to have worked itself out.
2024-08-19T05:08:59.397 INFO: Updating Session Details
2024-08-19T05:09:01.322 INFO: Updating Plan Details
2024-08-19T05:09:03.660 INFO: Updating Usage Details
2024-08-19T05:09:04.303 INFO: Usage data retrieved and processed
2024-08-19T05:09:04.303 INFO: Updating MQTT topic homeassistant/sensor/xfinity_internet/config
2024-08-19T05:09:04.303 INFO: Updating MQTT topic homeassistant/sensor/xfinity_internet/state
2024-08-19T05:09:04.304 INFO: Updating MQTT topic homeassistant/sensor/xfinity_internet/attributes
2024-08-19T05:09:05.876 INFO: Sleeping for 900 seconds
2024-08-19T05:24:16.963 INFO: Loading Internet Usage (URL: https://login.xfinity.com/login)
2024-08-19T05:24:17.043 INFO: Entering username (URL: https://login.xfinity.com/login)
2024-08-19T05:24:20.154 INFO: Entering password (URL: https://login.xfinity.com/login)
2024-08-19T05:24:27.307 INFO: Updating Session Details
2024-08-19T05:24:29.448 INFO: Updating Plan Details
2024-08-19T05:24:29.812 INFO: Updating Usage Details
2024-08-19T05:24:30.253 INFO: Usage data retrieved and processed
2024-08-19T05:24:30.253 INFO: Updating MQTT topic homeassistant/sensor/xfinity_internet/config
2024-08-19T05:24:30.253 INFO: Updating MQTT topic homeassistant/sensor/xfinity_internet/state
2024-08-19T05:24:30.253 INFO: Updating MQTT topic homeassistant/sensor/xfinity_internet/attributes
2024-08-19T05:24:32.859 INFO: Sleeping for 900 seconds
2024-08-19T05:39:42.689 INFO: Loading Internet Usage (URL: https://login.xfinity.com/login)
2024-08-19T05:39:42.781 INFO: Entering username (URL: https://login.xfinity.com/login)
2024-08-19T05:39:45.968 INFO: Entering password (URL: https://login.xfinity.com/login)
2024-08-19T05:39:53.601 INFO: Updating Session Details
2024-08-19T05:39:55.353 INFO: Updating Plan Details
2024-08-19T05:39:56.886 INFO: Updating Usage Details
2024-08-19T05:39:57.504 INFO: Usage data retrieved and processed
2024-08-19T05:39:57.504 INFO: Updating MQTT topic homeassistant/sensor/xfinity_internet/config
2024-08-19T05:39:57.504 INFO: Updating MQTT topic homeassistant/sensor/xfinity_internet/state
2024-08-19T05:39:57.505 INFO: Updating MQTT topic homeassistant/sensor/xfinity_internet/attributes
2024-08-19T05:39:59.719 INFO: Sleeping for 900 seconds
2024-08-19T05:55:08.753 INFO: Loading Internet Usage (URL: https://login.xfinity.com/login)
2024-08-19T05:55:08.851 INFO: Entering username (URL: https://login.xfinity.com/login)
2024-08-19T05:55:11.984 INFO: Entering password (URL: https://login.xfinity.com/login)
2024-08-19T05:55:19.663 INFO: Updating Session Details
2024-08-19T05:55:24.592 INFO: Updating Usage Details
2024-08-19T05:55:25.367 INFO: Updating Plan Details
2024-08-19T05:55:25.685 INFO: Usage data retrieved and processed
2024-08-19T05:55:25.685 INFO: Updating MQTT topic homeassistant/sensor/xfinity_internet/config
2024-08-19T05:55:25.686 INFO: Updating MQTT topic homeassistant/sensor/xfinity_internet/state
2024-08-19T05:55:25.686 INFO: Updating MQTT topic homeassistant/sensor/xfinity_internet/attributes
2024-08-19T05:55:26.908 INFO: Sleeping for 900 seconds
2024-08-19T06:10:37.352 INFO: Loading Internet Usage (URL: https://login.xfinity.com/login)
2024-08-19T06:10:37.429 INFO: Entering username (URL: https://login.xfinity.com/login)
2024-08-19T06:10:40.561 INFO: Entering password (URL: https://login.xfinity.com/login)
2024-08-19T06:10:49.737 INFO: Updating Session Details
2024-08-19T06:10:51.632 INFO: Updating Plan Details
2024-08-19T06:10:53.088 INFO: Updating Usage Details
2024-08-19T06:10:59.157 INFO: Usage data retrieved and processed
2024-08-19T06:10:59.157 INFO: Updating MQTT topic homeassistant/sensor/xfinity_internet/config
2024-08-19T06:10:59.158 INFO: Updating MQTT topic homeassistant/sensor/xfinity_internet/state
2024-08-19T06:10:59.158 INFO: Updating MQTT topic homeassistant/sensor/xfinity_internet/attributes
2024-08-19T06:11:00.577 INFO: Sleeping for 900 seconds
2024-08-19T06:26:10.906 INFO: Loading Internet Usage (URL: https://login.xfinity.com/login)
2024-08-19T06:26:11.002 INFO: Entering username (URL: https://login.xfinity.com/login)
2024-08-19T06:26:14.218 INFO: Entering password (URL: https://login.xfinity.com/login)
2024-08-19T06:26:22.963 INFO: Updating Session Details
2024-08-19T06:26:24.717 INFO: Updating Plan Details
2024-08-19T06:26:25.104 INFO: Updating Usage Details
2024-08-19T06:26:25.775 INFO: Usage data retrieved and processed
2024-08-19T06:26:25.776 INFO: Updating MQTT topic homeassistant/sensor/xfinity_internet/config
2024-08-19T06:26:25.776 INFO: Updating MQTT topic homeassistant/sensor/xfinity_internet/state
2024-08-19T06:26:25.776 INFO: Updating MQTT topic homeassistant/sensor/xfinity_internet/attributes
2024-08-19T06:26:28.690 INFO: Sleeping for 900 seconds
2024-08-19T06:41:37.832 INFO: Loading Internet Usage (URL: https://login.xfinity.com/login)
2024-08-19T06:41:37.941 INFO: Entering username (URL: https://login.xfinity.com/login)
2024-08-19T06:41:41.124 INFO: Entering password (URL: https://login.xfinity.com/login)
2024-08-19T06:42:29.457 WARNING: Retrying main.run_playwright in 1.0 seconds as it raised TimeoutError: Timeout 45000ms exceeded.
=========================== logs ===========================
waiting for navigation to "https://www.xfinity.com/learn/internet-service/auth" until 'load'
navigated to "https://login.xfinity.com/login"
============================================================.
2024-08-19T06:42:40.192 INFO: Loading Internet Usage (URL: https://login.xfinity.com/login)
2024-08-19T06:42:40.312 INFO: Entering username (URL: https://login.xfinity.com/login)
2024-08-19T06:42:43.513 INFO: Entering password (URL: https://login.xfinity.com/login)
2024-08-19T06:42:50.661 INFO: Updating Session Details
2024-08-19T06:42:52.875 INFO: Updating Plan Details
2024-08-19T06:42:53.391 INFO: Updating Usage Details
2024-08-19T06:42:53.764 INFO: Usage data retrieved and processed
2024-08-19T06:42:53.765 INFO: Updating MQTT topic homeassistant/sensor/xfinity_internet/config
2024-08-19T06:42:53.765 INFO: Updating MQTT topic homeassistant/sensor/xfinity_internet/state
2024-08-19T06:42:53.765 INFO: Updating MQTT topic homeassistant/sensor/xfinity_internet/attributes
2024-08-19T06:42:56.605 INFO: Sleeping for 900 seconds
2024-08-19T06:58:06.213 INFO: Loading Internet Usage (URL: https://login.xfinity.com/login)
2024-08-19T06:58:06.313 INFO: Entering username (URL: https://login.xfinity.com/login)
2024-08-19T06:58:53.798 WARNING: Retrying main.run_playwright in 1.0 seconds as it raised AssertionError: Locator expected to be editable
Actual value: <element(s) not found>
Call log:
LocatorAssertions.to_be_editable with timeout 45000ms

waiting for locator("input#passwd")
.
2024-08-19T06:59:05.575 INFO: Loading Internet Usage (URL: https://login.xfinity.com/login)
2024-08-19T06:59:05.672 INFO: Entering username (URL: https://login.xfinity.com/login)
2024-08-19T06:59:09.905 INFO: Entering password (URL: https://login.xfinity.com/login)
2024-08-19T06:59:18.780 INFO: Updating Session Details
2024-08-19T06:59:20.923 INFO: Updating Plan Details
2024-08-19T06:59:22.680 INFO: Updating Usage Details
2024-08-19T06:59:23.117 INFO: Usage data retrieved and processed
2024-08-19T06:59:23.117 INFO: Updating MQTT topic homeassistant/sensor/xfinity_internet/config
2024-08-19T06:59:23.117 INFO: Updating MQTT topic homeassistant/sensor/xfinity_internet/state
2024-08-19T06:59:23.118 INFO: Updating MQTT topic homeassistant/sensor/xfinity_internet/attributes
2024-08-19T06:59:26.364 INFO: Sleeping for 900 seconds

The error has returned.  I haven't got any data in 3 days now.
`Home Assistant Supervisor: 2024.08.0
Please, share the above information when looking for help
or support in, e.g., GitHub, forums or the Discord chat.
s6-rc: info: service base-addon-banner successfully started
s6-rc: info: service fix-attrs: starting
s6-rc: info: service base-addon-timezone: starting
s6-rc: info: service base-addon-log-level: starting
s6-rc: info: service fix-attrs successfully started
[08:25:35] INFO: Configuring timezone (America/Chicago)...
s6-rc: info: service base-addon-log-level successfully started
s6-rc: info: service base-addon-timezone successfully started
s6-rc: info: service legacy-cont-init: starting
s6-rc: info: service legacy-cont-init successfully started
s6-rc: info: service legacy-services: starting
s6-rc: info: service legacy-services successfully started
MQTT addon is active on your system!
Add the MQTT details below to the addon configuration :
MQTT user : addons
MQTT password : eiquu8ieVahmaeghuZaiGiephuoBae8uo9teig9eighahbu8naer6Veivootuiku
MQTT Hostname : core-mosquitto
MQTT Port : 1883
2024-08-27T08:25:36.876 INFO: Xfinity Internet Usage Starting
2024-08-27T08:25:36.891 INFO: Connected to MQTT Broker!
2024-08-27T08:25:48.234 INFO: Loading Internet Usage (URL: https://login.xfinity.com/login)
2024-08-27T08:25:48.476 INFO: Entering username (URL: https://login.xfinity.com/login)
2024-08-27T08:27:33.129 WARNING: Retrying main.run_playwright in 1.0 seconds as it raised AssertionError: Locator expected to be attached
Actual value: <element(s) not found>
Call log:
LocatorAssertions.to_be_attached with timeout 100000ms

waiting for locator("input#passwd")
.
Number of retries: 1
2024-08-27T08:27:43.994 INFO: Loading Internet Usage (URL: https://login.xfinity.com/login)
2024-08-27T08:27:44.126 INFO: Entering username (URL: https://login.xfinity.com/login)
2024-08-27T08:29:28.673 WARNING: Retrying main.run_playwright in 2.0 seconds as it raised AssertionError: Locator expected to be attached
Actual value: <element(s) not found>
Call log:
LocatorAssertions.to_be_attached with timeout 100000ms
waiting for locator("input#passwd")
.
Number of retries: 2
2024-08-27T08:29:41.625 INFO: Loading Internet Usage (URL: https://login.xfinity.com/login)
2024-08-27T08:29:41.832 INFO: Entering username (URL: https://login.xfinity.com/login)
2024-08-27T08:31:26.377 WARNING: Retrying main.run_playwright in 4.0 seconds as it raised AssertionError: Locator expected to be attached
Actual value: <element(s) not found>
Call log:
LocatorAssertions.to_be_attached with timeout 100000ms
waiting for locator("input#passwd")
.
Number of retries: 3
2024-08-27T08:31:41.325 INFO: Loading Internet Usage (URL: https://login.xfinity.com/login)
2024-08-27T08:31:41.532 INFO: Entering username (URL: https://login.xfinity.com/login)
2024-08-27T08:33:26.435 WARNING: Retrying main.run_playwright in 8.0 seconds as it raised AssertionError: Locator expected to be attached
Actual value: <element(s) not found>
Call log:
LocatorAssertions.to_be_attached with timeout 100000ms
waiting for locator("input#passwd")
.
Number of retries: 4
2024-08-27T08:33:50.102 INFO: Loading Internet Usage (URL: https://login.xfinity.com/login)
2024-08-27T08:33:50.206 INFO: Entering username (URL: https://login.xfinity.com/login)
2024-08-27T08:35:35.442 WARNING: Retrying main.run_playwright in 15.0 seconds as it raised AssertionError: Locator expected to be attached
Actual value: <element(s) not found>
Call log:
LocatorAssertions.to_be_attached with timeout 100000ms
waiting for locator("input#passwd")
.
Number of retries: 5
2024-08-27T08:36:02.384 INFO: Loading Internet Usage (URL: https://login.xfinity.com/login)
2024-08-27T08:36:02.578 INFO: Entering username (URL: https://login.xfinity.com/login)
2024-08-27T08:37:47.144 WARNING: Retrying main.run_playwright in 15.0 seconds as it raised AssertionError: Locator expected to be attached
Actual value: <element(s) not found>
Call log:
LocatorAssertions.to_be_attached with timeout 100000ms
waiting for locator("input#passwd")
.
Number of retries: 6
2024-08-27T08:38:13.822 INFO: Loading Internet Usage (URL: https://login.xfinity.com/login)
2024-08-27T08:38:13.972 INFO: Entering username (URL: https://login.xfinity.com/login)
2024-08-27T08:39:58.604 WARNING: Retrying main.run_playwright in 15.0 seconds as it raised AssertionError: Locator expected to be attached
Actual value: <element(s) not found>
Call log:
LocatorAssertions.to_be_attached with timeout 100000ms
waiting for locator("input#passwd")
.
Number of retries: 7
2024-08-27T08:40:24.095 INFO: Loading Internet Usage (URL: https://login.xfinity.com/login)
2024-08-27T08:40:24.268 INFO: Entering username (URL: https://login.xfinity.com/login)
2024-08-27T08:42:08.924 WARNING: Retrying main.run_playwright in 15.0 seconds as it raised AssertionError: Locator expected to be attached
Actual value: <element(s) not found>
Call log:
LocatorAssertions.to_be_attached with timeout 100000ms
waiting for locator("input#passwd")
.
Number of retries: 8
2024-08-27T08:42:34.667 INFO: Loading Internet Usage (URL: https://login.xfinity.com/login)
2024-08-27T08:42:34.872 INFO: Entering username (URL: https://login.xfinity.com/login)`

I stopped and while restart in the morning.

Hi @thor0215 yes, that is correct. I've seen the edgesuite (AKA akamai bot scrapping) blocking the requests.
You either get the login page again or an AccessDenied. I did some tests with puppeteer and the puppeteer-extra-plugin-stealth and it worked great but also ended up being temporarily blocked after several tries so requests/hour also matter.
Let me know if you ever think about switching from playwright to puppeteer or if you want to take a look at the code with puppeteer-extra-plugin-stealth and puppeteer-screen-recorder.
I speak for myself but probably others here that would like to say thank you for your fast fix! I updated to the latest version (<IP_ADDRESS>) and it worked again, however going around Akamai bot detection will always be a struggle unfortunately.
One thing I did notice is that MQTT doesn't seem to work with secure mqtts (TLS 8833), only insecure 1883. I had to add a new entry point to treafik for the local traffic. Not end of the world but good to know.
Cheers!!


<EMAIL_ADDRESS>decompress error

Getting  this error for wingetui
PS C:\WINDOWS\system32> scoop install wingetui
Installing 'wingetui' (3.1.1) [64bit] from 'extras' bucket
Loading WingetUI.Installer.exe from cache
Checking hash of WingetUI.Installer.exe ... ok.
Extracting WingetUI.Installer.exe ... ERROR Exit code was 1!
Failed to extract files from C:\Users\andy\scoop\apps\wingetui\3.1.1\WingetUI.Installer.exe.
Log file:
  ~\scoop\apps\wingetui\3.1.1\innounp.log

Please try again or create a new issue by using the following link and paste your console output:
https://github.com/ScoopInstaller/Extras/issues/new?title=wingetui%403.1.1%3a+decompress+error

Installing scoop install<EMAIL_ADDRESS>works.

Duplicates #13709.


ValueConverter expressions: Are you really lazy?

https://github.com/aspnet/EntityFrameworkCore/blob/4f470638e0e98a8c60175c524e99792a72640986/src/EFCore/Storage/ValueConversion/ValueConverter`.cs#L61-L71
ctor initializes them already.

Looks like constructor is wrong here, but I guess we could go either way.


Add Minimize to Tray and Tray Icon

A brief summary of the behavior of the tray icon:

There will only ever be one tray icon representing all windows.
Left-Click on a Tray Icon brings up the MRU window.
Right-Click on a Tray Icon brings up a Context Menu:

Focus Terminal
----------------
Windows --> Window ID 1 - <unnamed window>
            Named Window
            Named Window Again

Focus Terminal will bring up the MRU window.
Clicking on any of the Window "names" in the submenu will summon the window.

Settings Changes
Two new global settings are introduced: alwaysShowTrayIcon and minimizeToTray. Here's a chart explaining the behavior with the two settings.

alwaysShowTrayIcon:true
alwaysShowTrayIcon:false

minimizeToTray:true
tray icon is always shown. minimize button will hide the window.
tray icon is always shown. minimize button will hide the window.

minimizeToTray:false
tray icon is always shown.
tray icon is not shown ever.

I've introduced a new keybinding also named minimizeToTray for convenience in case users perfer to minimize with a keybinding instead of having to click on the minimize button. Upon activation, the currently focused window will become hidden.
⚠Note that this will only work if you enable one of the two global settings (otherwise there might be a scenario where you hit the keybinding but have both alwaysShowTrayIcon and minimizeToTray as false.
Closes #5727
References
Spec for Minimize to Tray
Docs PR - MicrosoftDocs/terminal#352
#10448 - My list of TODOs

Make an "AlwaysShowTrayIcon" option so people can control if they want it in their tray or not by default.

This should be a requirement. So many applications provide this option that it should considered a defacto standard (like Xterm).

This should be a requirement. So many applications provide this option that it should considered a defacto standard (like Xterm).

Yep, there's already a whole spec with a section devoted to this idea.

Also, this won't close #5727?

This is slightly off topic, but idk where else to put it. We should consider how this plays with startOnUserLogin. Maybe that setting should now be in a 3-way state?

false/disabled: don't start when the user logs in
onlyTray: enabled, but only for the tray menu
true/enabled: add in the tray menu and a new window

We're not in a place where we can support this just yet right? We still need a window open for the tray to appear. But this might have some implications to your PR, idk.

Also, curious, how does/will this work when we have this feature in WT and WT Preview? Are we going to have 2 tray icons haha?

Yup! If someone were to run WT, WTD, and WT Preview all at the same time, there would be 3 different icons. 😄

We're not in a place where we can support this just yet right? We still need a window open for the tray to appear. But this might have some implications to your PR, idk.

Hmm I hadn't considered the startOnUserLogin setting. I can see the case for an onlyTray option where the tray icon is there and no windows are "active". It would technically mean that the window is created but hidden immediately (or even created hidden). I kinda like that option!
As for how it plays with the new settings, it would seem like in order for onlyTray to work, you would also need to have either one of minimizeToTray or alwaysShowTrayIcon to be true? Though that might start to get complicated to explain where you need to enable a bunch of other globals in order to get this option to work.

We should consider how this plays with startOnUserLogin

I have thoughts on this matter, esp regarding the global summon hotkeys. Something about a headless monarch. Pretty sure there's an issue tracking that. Obv, I'll elaborate more when I'm off break.

IIIIIIIIIII will need to consider what happens when someone makes a quake window/minimizes it but doesn't have any of the settings set to true (aka. "I don't want any tray icon ever and I will not want my windows to minimize to tray but the quake window kinda does its own thing where it'll hide itself anyway and we don't want a situation where a window is minimized and unable to be accessed through some way other than a keybind")

IIIIIIIIIII will need to consider what happens when someone makes a quake window/minimizes it but doesn't have any of the settings set to true (aka. "I don't want any tray icon ever and I will not want my windows to minimize to tray but the quake window kinda does its own thing where it'll hide itself anyway and we don't want a situation where a window is minimized and unable to be accessed through some way other than a keybind")

Let's try and envision that scenario through the lens of #9992 - the _quake window will just act like it's a window that's always got "minimizeToTray" set to true.
Though, I guess that's a weird "global" setting - it actually is a global setting (across windows), not just a per-window setting. Hmmmmmmmmm.
Nevermind then. If they really really don't want the tray icon, then fine, no icon, even for quake. That seems reasonable to me.

Nevermind then. If they really really don't want the tray icon, then fine, no icon, even for quake. That seems reasonable to me.

I was actually going to make it so that the quake mode window would be the exception. If you happen to have a quake window alive somewhere, the tray icon will show up as well.

I'm gonna tag this up for discussion today. Based on the existence of #10689, I'm thinking that there are gonna be folks that don't want the tray icon even with quake mode.
Though, it might make sense that they'd be better served by a combo of #9992 and creating another window that's "snapped to the top", but isn't named "_quake". Though, that does seem like a lot of work, cause that's
{
  "windows": {
    "not_quake": {
      "snapToSide": "top",
      "launchMode": "focus"
    }
  },
  "minimizeToTray": false,
  "actions": [
    { "keys": "win+`", "command": { "action": "globalSummon", "name": "not_quake", "dropdownDuration": 200 } }
  ],
  ...
}

THOUGH
if we make minimizeToTray affect the quake window too, then we'll immediately get rid of that behavior for quake. It'll default to false, so then even the quake window won't get it.
So yea, I think I'm in favor of "quake mode ignores minimizeToTray, always, and if you want quake mode without minimizing to the tray, then do {the above}"

I've introduced a new keybinding also named minimizeToTray for convenience in case users perfer to minimize with a keybinding instead of having to click on the minimize button. Upon activation, the currently focused window will become hidden.

wait uh, I don't think we need this. Win+down will minimize a window

wait uh, I don't think we need this. Win+down will minimize a window

Ah crap I didn't even know about this shortcut 😅
Ok so with this shortcut, the user can minimize to tray with the keyboard as long as minimizeToTray = true.
What about users who have minimizeToTray = false, alwaysShowTrayIcon = true? They may not want all minimize actions to minimizeToTray, but they'd likely want some way of sending the window to the tray considering they want the icon there. Perhaps it should be a system menu item? Or maybe it should be a tray icon menu item? 🤔

They may not want all minimize actions to minimizeToTray, but they'd likely want some way of sending the window to the tray considering they want the icon there.

Hmm. Interesting. Okay, I'm convinced. I kinda think it should be a separate PR, but it's already here so ¯\_(ツ)_/¯


On-chain dataHash :: BuiltinData -> BuiltinByteString

Describe the feature you'd like
I assume this is already implementable if you do the serialization on-chain, but it would be
wasteful compared to supporting it as a built-in function.
Describe alternatives you've considered
Is it perhaps possible to get the undeserialized datum for an input on-chain?
That would already cover some of the potential use cases.
Additional context / screenshots
Some times you want to be able to compute the hash of a transformation of some
data (e.g. a datum), without storing the transformation in the transaction, in order
to save space.

Thanks for the issue!
Yeah, this is a desired feature but not implemented yet.


Add tests for ApplicantProgramBlocksController#confirmAddress

Description
Please explain the changes you made here.
Release notes
The title of the pull request will be used as the default release notes description. If more detail is needed to communicate to partners the scope of the PR's changes, use this release notes section.
Checklist
General
Read the full guidelines for PRs here

[ ] Added the correct label: < feature | enhancement | bug | dependencies | infrastructure | ignore-for-release | database >
[ ] Assigned to a specific person, civiform/developers, or a more specific round-robin list.
[ ] Created unit and/or browser tests which fail without the change (if possible)
[ ] Performed manual testing (Chrome and Firefox if it includes front-end changes)
[ ] Extended the README / documentation, if necessary

Database evolutions
Read the guidelines here

[ ] Assigned two reviewers
[ ] Guarded against already existing resources using IF NOT EXISTS and IF EXISTS
[ ] Downs created to undo changes in Ups

User visible changes

[ ] Followed steps to internationalize new strings

[ ] Added context strings to new messages
[ ] Didn't use a message in applicant facing code that isn't translated yet (unless behind a flag)

[ ] Wrote browser tests using the validateAccessibility method
[ ] Tested on mobile view. See mobile device mode
[ ] Manually tested at 200% size
[ ] Manually evaluated tab order

New Features

[ ] Add new FeatureFlag env vars to server/conf/helper/feature-flags.conf
[ ] Conditioned new functionality on a FeatureFlag
[ ] Wrote browser tests with the feature flag off and on, etc.

Instructions for manual testing
If instructions are needed for manual testing by reviewers, include them here.
Issue(s) this completes
Fixes #<issue_number>; Fixes #<issue_number>...

[!WARNING]
This pull request is not mergeable via GitHub because a downstack PR is open. Once all requirements are satisfied, merge this PR as a stack on Graphite.
Learn more

Current dependencies on/for this PR:

main

PR #6563

PR #6544

PR #6580

PR #6547

PR #6610   👈
PR #6589

This stack of pull requests is managed by Graphite.

Thanks for re-approving Gwen! The only reason I haven't merged this yet is that it's stacked on top of https://github.com/civiform/civiform/pull/6547 so I want to submit that PR first (I think your old approval was still valid).

Github sent me a notification and indicated there was a file I hadn't seen, but I didn't notice anything different. Weird.


Add example mdBook to show off colourscheme

What
An example mdbook should live in the root directory of the repository. This book should also be deployed under GitHub Pages.
Why
Providing a visual preview of the colour scheme will significantly enhance the user experience and offer easy access to the latest version of the extension. We should use the domain mdbook.catppuccin.com
Acceptance Criteria

[ ] Example mdBook created with pages showcasing different types of highlights (headings, paragraphs, codeblocks etc)
[ ] GitHub Actions workflow for deploying to GitHub Pages
[ ] Page deployed under mdbook.catppuccin.com

Hey, I'm interested in this

Thanks for being interested in contributing! Feel free to ping me on discord if you need any help or have any questions, happy to help 👍


Publish a version for DioX

Would you consider forking the package or publishing a version compatible with DioX?
https://pub.dev/packages/diox

Would you consider forking the package or publishing a version compatible with DioX?
https://pub.dev/packages/diox

Perhaps. But what is this package? And what are the differences from dio?

#21 this will may help.

The package for DioX has been published as a prerelease! You can use it like this:
dio_smart_retry: ^2.0.0-diox

Please check this out.

@rodion-m  Diox has been archived.
The developper got the accesses of the Dio repo and will maintain Dio in 5.0.0

@iTEEECH PR is created, maybe you could compare it with your PR and review my changes? Thanks.

The new version with dio 5.0.0 support is available as dio_smart_retry: ^5.0.0.


Fixed input crashing after 51 character

The input stopped working after 51 character is typed, so  a newline is automatically entered.


Drag and drop

Pull Request Description

Closes https://github.com/enso-org/cloud-v2/issues/697

Adds infrastructure to support drag-and-drop
Implements drag-and-drop for deleting and undeleting assets
Implements drag-and-drop for moving assets to a new directory (or the root directory)

Also implements "cut" and "paste" context menu actions (and keyboard shortcuts) using the new endpoint for moving files

"Copy" and "duplicate" actions are not implemented, as I don't think there are backend endpoints for those yet.

Important Notes
Drag-and-drop for more situations are planned but intentionally not yet implemented:

Labels (backend is WIP, and blocked on the corresponding frontend PR)
Moving assets between folders (backend functionality does not yet exist)

Screencast
https://github.com/enso-org/enso/assets/4046547/28453c8f-8a49-47cf-96f3-81a3b3ee9250
Checklist
Please ensure that the following checklist has been satisfied before submitting the PR:

[x] The documentation has been updated, if necessary.
[x] Screenshots/screencasts have been attached, if there are any visual changes. For interactive or animated visual changes, a screencast is preferred.
[x] All code follows the
Scala,
Java,
and
Rust
style guides. In case you are using a language not listed above, follow the Rust style guide.
All code has been tested:

[x] Unit tests have been written where possible.
[x] If GUI codebase was changed, the GUI was tested when built using ./run ide build.

@PabloBuchu dnd to directories should work now. i've implemented cut-and-paste as well, because the backend endpoints (and logic for moving assets to the new location) are already here

whats this weird earth icon that flies to the cursor when drag something?

I can move directory and drop on itself making it disappear. Probably we need to fix both on be / fe this

very weird... the earth icon seems to maybe (?) be because i use a blank element as the drag image? no clue why that happens though, it doesn't happen for me on linux. as usual, still an issue but it means it will be difficult for me to debug. if there's no extra request for a nonexistent image i have no clue what it might be. i can try setting the div to 1px by 1px tomorrow, if macos doesn't like it when the placeholder drag element is 0px by 0px
will fix tomorrow.

Its flying towards my cursor :) no request for the image although there are 2 requests PATCH and 1 OPTIONS being send on drop
https://github.com/enso-org/enso/assets/2855109/24613f60-6d7b-413c-bc2e-ac6e3aff669a

note to self: i forgot to fade the icons out after they have been cut

oh, also being able to cancel a cut operation with Esc

@PabloBuchu a number of issues should be resolved now. as i'm not sure what's up with the safari issue, i can't confirm that it is fixed now, but i have implemented a potential fix. let me know if it is still an issue, and i can try implementing a different fix.

weirdly enough, i can't manage to find any info about this issue on the internet.

A glitch when dragging an object from nested structure. Also how hard would it be to add small higlight of the directory on which we are dropping (you want to do it with this PR or as seaprate, improvement?)

@PabloBuchu oh, didn't see this comment - glitch should now be addressed. as for the highlight, that should also be implemented - it was relatively easy as the frontend is already listening to drag events anyway, to determine when to show the cursor as being able to be dropped (the drag cursor with the (+))

Yeah the highlight works but the directory stays selected and it can not be unclicked untill I move something else.. @somebody1234 please can you QA your changes before reporting something is delivered? this should be caught before pushing..
https://github.com/enso-org/enso/assets/2855109/a34b1ccd-8e89-4422-b686-5f5f558983ed

@PabloBuchu yeah, sorry. normally i do try to QA the changes, but i probably do need to make sure i test them more thoroughly.
... on second thought maybe this is something the visual regression tests (playwright tests) would be useful for?

@somebody1234 this commit gives me the following error when I try to run ide with $ npm --workspace=enso-gui2 run dev. Do I need to clean something?
assetsTable.tsx:154 Uncaught TypeError: Cannot read properties of undefined (reading 'recent')
    at assetsTable.tsx:154:32
(anonymous) @ assetsTable.tsx:154

@4e6 i think so. you can try either rm -r node_modules/.cache/ (and potentially app/gui2/node_modules/.cache/ if it exists), and/or npm ci (or npm i), or ./run git-clean then npm ci/npm i as a last resort i guess

actually i can reproduce... i'll check what's going on

ah... seems like a circular import. i'll make a hotfix PR for this asap

Thank you! :heart:


Modbus Server returns data from addresses offset if starting register greater than zero

I'm submitting a ...
Problem

(x) bug report

Current behavior
Modbus server returns data from incorrect register addresses if the requested data does not start at register index zero.
Expected behavior
Modbus server returns correct register data
Minimal reproduction of the problem with instructions

Start with empty flow, drop in single Modbus Server node and deploy
Using Generic modbus client set first few registers with data (say equal to register address)
Using Generic modbus client read back data using non zero offset and note misalignment of data to register address.

node-red-contrib-modbus_server_error_testflow.txt
node-red-contrib_modbus_server_error.zip
Your Environment
Please tell us about your environment:

(x) I am using just the Node-RED package and got modbus-serial package installed with it

Device :

( ) macOS: v
(x) Linux: v Ubuntu 16.04 LTS
( ) Windows: v
( ) Raspbian: v
( ) Other:

Name:
Version:

Description of the connecting Modbus system:

Name   :Modbus test client is ModScan32
Version: v4
Vendor : WinTech
Link   : http://www.win-tech.com

node-red-contrib-modbus version: v4.0

Node: (min. 6.x)
node --version = v10.10.0

Just rolled-back the version of node-red-contrib-modbus to v3.6.1 and problem disappears.

Hi Steve,
could you test with the library simple server, please?
greetings,
Klaus

@stefanpoeter some known issue here?

@biancode what jsmodbus version are you using?

@biancode what jsmodbus version are you using?

@stefanpoeter "jsmodbus": "3.0.0"

Yes, 3.0.0 has some issues, use a newer version.

@stevereids please test v4.0.1

Hi Klaus,
I have just upgraded from 3.6.1 to 4.1.0 and everything looks good.  I need
to leave it running as I have had issues with memory leaks in earlier
versions.
Thanks.
Steve
On Thu, 8 Nov 2018 at 19:06, Klaus Landsdorf<EMAIL_ADDRESS>wrote:

@stevereids https://github.com/stevereids please test v4.0.1
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/biancode/node-red-contrib-modbus/issues/114#issuecomment-437118443,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AJXclWP6rIFB_ARZw1e0InhX-l4lJTwxks5utICZgaJpZM4XIN-j
.


Use --pure shells for ob run

ob repl already uses --pure. I ran into a situation where ob run would fail to build the app but ob repl worked fine. This makes them consistent and also more resilient to local configuration problems.

Do we ever not want --pure ? ob shell and ob doc seem to use False for isPure

I was asking myself that same question... That's a bigger change than I'd want to do in this PR. But it's pertinent.

I think we definitely don't want pure for ob shell.

@kmicklas Good point.

@3noch can you add a note to the changelog? once we have that, this looks good to go.


Fix new project root path not being used in CLI-launched GUI

Fixes #408

Tested & working both when there is and isn't a root parameter given.
Notable: currently this will prompt you to create the New Project as a folder within the folder from which you launched, rather than creating a new project with the folder itself. This might not be ideal but it's a separate issue - if you give no folder name, it should use the working directory as the root of the new project.


Upgrading from 1.13.0 to 1.13.2 causes Template Error

I'm submitting a bug report
Webpack version:
1.13.2
Please tell us about your environment:
OSX 10.x / Linux / Windows 10
Ubuntu 16.10
Current behavior:
When compiling, I see the following exception:
RROR in chunk main [entry]
projectFoo.js
No template for dependency: TemplateArgumentDependency
Error: No template for dependency: TemplateArgumentDependency
    at doDep (/home/ray/source/projectFoo/node_modules/webpack/lib/NormalModule.js:137:23)
    at Array.forEach (native)
    at doBlock (/home/ray/source/projectFoo/node_modules/webpack/lib/NormalModule.js:151:22)
    at DependenciesBlock.NormalModule.source (/home/ray/source/projectFoo/node_modules/webpack/lib/NormalModule.js:186:2)
    at Template.ModuleTemplate.render (/home/ray/source/projectFoo/node_modules/webpack/lib/ModuleTemplate.js:14:28)
    at Template.renderChunkModules (/home/ray/source/projectFoo/node_modules/webpack/lib/Template.js:103:31)
    at Template.<anonymous> (/home/ray/source/projectFoo/node_modules/webpack/lib/MainTemplate.js:30:22)
    at Template.applyPlugins [as applyPluginsWaterfall] (/home/ray/source/projectFoo/node_modules/webpack/node_modules/tapable/lib/Tapable.js:37:47)
    at Template.MainTemplate.render (/home/ray/source/projectFoo/node_modules/webpack/lib/MainTemplate.js:113:20)
    at Compilation.createChunkAssets (/home/ray/source/projectFoo/node_modules/webpack/lib/Compilation.js:843:33)
    at Compilation.<anonymous> (/home/ray/source/projectFoo/node_modules/webpack/lib/Compilation.js:557:8)
    at Compilation.applyPluginsAsync (/home/ray/source/projectFoo/node_modules/webpack/node_modules/tapable/lib/Tapable.js:60:69)
    at Compilation.seal (/home/ray/source/projectFoo/node_modules/webpack/lib/Compilation.js:525:7)
    at Compiler.<anonymous> (/home/ray/source/projectFoo/node_modules/webpack/lib/Compiler.js:397:15)
    at /home/ray/source/projectFoo/node_modules/webpack/node_modules/tapable/lib/Tapable.js:103:11
    at Compilation.<anonymous> (/home/ray/source/projectFoo/node_modules/webpack/lib/Compilation.js:445:10)
    at /home/ray/source/projectFoo/node_modules/webpack/lib/Compilation.js:417:12
    at /home/ray/source/projectFoo/node_modules/webpack/lib/Compilation.js:332:10
    at /home/ray/source/projectFoo/node_modules/webpack/node_modules/async/lib/async.js:52:16
    at done (/home/ray/source/projectFoo/node_modules/webpack/node_modules/async/lib/async.js:246:17)
    at /home/ray/source/projectFoo/node_modules/webpack/node_modules/async/lib/async.js:44:16
    at /home/ray/source/projectFoo/node_modules/webpack/lib/Compilation.js:332:10
    at /home/ray/source/projectFoo/node_modules/webpack/node_modules/async/lib/async.js:52:16
    at done (/home/ray/source/projectFoo/node_modules/webpack/node_modules/async/lib/async.js:246:17)
    at /home/ray/source/projectFoo/node_modules/webpack/node_modules/async/lib/async.js:44:16
    at /home/ray/source/projectFoo/node_modules/webpack/lib/Compilation.js:332:10
    at /home/ray/source/projectFoo/node_modules/webpack/node_modules/async/lib/async.js:52:16
    at done (/home/ray/source/projectFoo/node_modules/webpack/node_modules/async/lib/async.js:246:17)
    at /home/ray/source/projectFoo/node_modules/webpack/node_modules/async/lib/async.js:44:16
    at /home/ray/source/projectFoo/node_modules/webpack/lib/Compilation.js:332:10

This works fine in 1.13.0 but upgrading to 1.13.2 causes webpack to fail.

Can you provide a project to test against? I wonder what changed in between.

@raybooysen ping ^

I'm going to close this as this was from webpack 1.
If this is still an issue, please resubmit a new issue with the information listed in our issue template (version, repro repo, etc.)


adding file for German version of JOSM tools section of site.

@michael63-osm Sorry about the delay in adding this - my mistake & I've only just arrived somewhere with a better internet connection so I could correct my error.  Please note that I've renamed it de_tools_menu_sample.osm so that it does not conflict with the English version.
Reference #261
Regards
Nick


Autorest Regen Preview to 3.0.0-alpha.20230714.8 by Mike Harder from refs/pull/3593/merge

Triggered from https://github.com/Azure/autorest.csharp/pull/3593

API change check
APIView has identified API level changes in this PR and created following API reviews.
Azure.ResourceManager.DataFactory


How to setup i18n in Nuxt 3 - Help Needed [Beta 13]

Reproduction

Describe the bug
I am having trouble getting @formkit/i18n to work in my Nuxt 3 project. I am using @formkit/nuxt + TailwindCSS and have already setup a formkit.config.js for my tailwind theme (which is working as intended).
in formkit.config.js, I am doing the following:
import { de } from "@formkit/i18n";
import { generateClasses } from "@formkit/themes";
...
// my tailwind theme
const theme = { ... }

export default {
    config: {
        classes: generateClasses(theme),
        locales: { de },
        locale: "de",
    },
};

The result: the validation error messages are still displayed in English, instead of German. What am I missing? Any help would be greatly appreciated.
Environment
Formkit - Beta 13
Nuxt 3

Getting the same issue 👍🏼

Same issue on Beta 14

@fabiangfd Hey! So your locales and locale props should be one level higher, as a base prop of the defaultConfig, like this:
export default {   config: {     classes: generateClasses(theme),   },   locales: { de },   locale: "de", };
Can you give that a try?

Nice that works :-)
But am i the only one who finds the config very messy and confusing? Like why is there a "createProPlugin" and "createAutoAnimatePlugin" but not "createi18n", furthermore we do not have a createTheme but instead a "generateClasses". They are all on different levels in the config, and dont really have a system.

I think your critique here is valid — certainly we could try to make this more streamlined. That said, there is a logic and system behind what you are seeing.
The values you are setting up here are passed to defaultConfig — which does what it says on the tin, it is a default configuration but certainly not the only configuration. All the features you are refering to, like i18n is a plugin and does have a createi18nPlugin (for example: https://github.com/formkit/formkit/blob/master/packages/i18n/src/i18n.ts#L60).
However, since most people want to use these plugins on most projects, they are setup for you if you choose to use the defaultConfig. You can, of course, opt out of the defaultConfig and set these up for yourself which is great for tree shaking and performance tuning.
If you want to see what all defaultConfig is doing for you, you can take a peek here: https://github.com/formkit/formkit/blob/master/packages/vue/src/defaultConfig.ts#L45-L94


cleanup, add collectstatic, and blurb about builds

This commit aims to solve the problems encountered in issue #1867 revolving around frustrations with getting an on-premises server started and working.
I've done the following:

cleaned up the "step flow"...This now reads a lot more sane
added the step around collectstatic to ensure static assets are copied
inserted stanza warning about port assignment for builds to work successfully.

Thanks for the update here, looks great! :+1:


Added support to push VMGeneration in telemetry database

As we are moving to fully automate PowerBI reports, we need a support to view results with more granularity.
This PR adds one more such property to telemetry database -  "VMGeneration"

I think this has to wait until after the tree is reset.
Please sync with @juhlee-microsoft

I think this has to wait until after the tree is reset.
Please sync with @juhlee-microsoft

Sure.

Will re-open after syncing with @juhlee-microsoft


cleanup gobject destruction

I learned a lot about the gobject framework writing the tabrmd. I didn't get everything right though. One thing I got wrong is proper gobject destruction. Not that there isn't plenty of documentation out there: https://developer.gnome.org/gobject/stable/howto-gobject-destruction.html ... I just didn't "get it".
What I got wrong is the bit about using the dispose method to free / unref references to other gobjects. Instead I did this in the finalize function where all other resources are freed. This needs to be cleaned up.

Also a good opportunity to use g_clear_object and g_clear_pointer instead of g_object_unref and g_free directly.

this was resolved in #211


(3.8.0) problems installing

General information:
Project issue is for:
Launcher
Expected result:
The "Start Game" button in the Launcher starts the game (that is, it opens and stays open without any critical errors)
Actual result:
Upon pressing "Start Game", EFT very briefly opens, but then immediately closes. the log (see below) mentions that this is due to EscapeFromTarkov_BE.exe not existing.
FWIW I feel like I'm just missing a step from the setup (EFT_BE.exe is, apparently, supposed to be deleted after all), but I can't figure out which one that is: the only part of the manual install I skipped is the downgrade, which doesn't seem to be necessary, given I'm using the 3.8.0 branch of both the launcher and server repos, which seem to support the latest eft version.
How to reproduce:

Set up the server (which seems to be working fine)
copy live EFT install into a new directory (I'll just call it /SPT for simplicity)
copy build artifacts from the launcher repo into /SPT
3.5. as per the manual install guide, skip installing a downgrade patch, because as far as I can tell, 3.8.0 should support the current EFT version
run Aki.Launcher.exe
(attempt to) start the game

Log files:
Client: https://pastebin.com/7tm8Cgaj

Originally written by Azrael1123

mini-update: I've just tried installing SPT-AKI/Modules as well, in case that changes anything, and it apparently does not - still the same issue, no apparent changes.

Originally written by Azrael1123

The issue tracker isn't for install problems

Originally written by chomp


Diversity of the dataset predicates ?

Due to having QA-SRL dataset as a source, most of the OIE benchmark predicates are single worded verbs. In Open IE systems output relations might include other forms such as ( Nouns or Noun+prep) Are there any future work considering that ? (for ex: expanding the dataset with other available annotations such as AMR )
Thanks for the benchmark, great work!.

@hadyelsahar
That's definitely a property of the data set and the conversion method.
This is somewhat mitigated in the soft comparison metric we use when comparing OIE systems which usually differ.
I'm definitely interested in expanding this resource with more annotations.
One issue with using AMR for this purpose is that we don't have an annotation of the alignment between AMR concepts and the surface words.
BTW, if it's okay with you I might move this discussion to a wiki page, or if elsewhere if you have a better suggestion, as it's not really a short-term issue :)
Thanks!

BTW, @hadyelsahar, I just published a new version of the corpus which incorporates words from the question into the predicate, thus creating more diverse multi-word predicates. For example - the following predicate is created:
can be described as
can be equipped with

You can see the full predicate list here.
The comparisons of the different extractors do not change much following this change.

Thanks for handling that very quickly. Would be very interested to know more about how did u collect those new predicates. Or they are the same as the old ones with prepositions attached when possible ?

These come from the same QA-SRL dataset, but I've taken some care to pull out elements from the associated questions (auxiliaries,  copulas, negations, prepositions) to form multi-word predicates, where applicable.
For instance, in certain cases, the prepositions in questions actually belong in the argument rather than in the predicate.
Compare the following two automatic extractions from the corpus (predicate before argument in parentheses):

China 's parliament ousted two Hong Kong residents *from* a panel drafting a new constitution for the colony .
ousted  (China 's parliament, two Hong Kong residents,  *from* a panel drafting a new constitution for the colony China 's parliament)

The borrowing to raise these funds would be paid off as assets of sick thrifts are sold .
would be paid off  (The borrowing to raise these funds, as assets of sick thrifts are sold)

I hope these make sense.
In summary - this admittedly still misses some diversity in predicates, but I think it extends the previously mostly single-word predicates.


Change assets deprecation from error to warning

See ampedandwired/html-webpack-plugin/pull/45

Unfortunately the tests failed

Seems to be an issue with the build:
The command "eval npm install " failed 3 times.

I have seen this in serveral projects.. seems to be an io.js issue on travis


error on build on OSX

Could you help me out.
The build script is being run and i get this error.
Here is the terminal:
devsisters apple$ CGO_LDFLAGS="-L$GOPATH/src/github.com/devsisters/goquic/lib/darwin_amd64" go build $GOPATH/src/github.com/devsisters/gospdyquic/example/server.go
github.com/devsisters/goquic
goquic/init.go:10:30: error: unknown type name 'CRYPTO_THREADID'
extern void goquic_thread_id(CRYPTO_THREADID *id);
^
1 error generated.

BTW the path on the readme is wrong. Is missing the "src" before /github.com/....

Hello! Thank you for reporting this problem. Due to recent thread safety related patch to goquic, a working OpenSSL header is needed. We are still figuring out how we can deal with this new dependency.
Normally this would not be a problem because many developers have OpenSSL installed. But it seems you are using an older version of OpenSSL which does not have CRYPTO_THREADID type in the header. (You need at least OpenSSL 1.0.0) So you have two options.

You can install latest OpenSSL to mitigate this problem: brew install openssl
Fortunately, libquic repository has a latest version of BoringSSL, which includes all the headers you need. (And we link to BoringSSL anyways) So setting CGO_CFLAGS environment variable to the BoringSSL repository will solve this problem. Example: CGO_CFLAGS="/path/to/boringssl/include/" CGO_LDFLAGS="-L$GOPATH/src/github.com/devsisters/goquic/lib/darwin_amd64" go build $GOPATH/src/github.com/devsisters/gospdyquic/example/server.go

I've updated the README to add CGO_CFLAGS environment variable. Can you try it out and see if it works?
Thanks!


Three Data download IDs  and link are down!

please share a copy, sir, please!

Yup, the links are down, please do share them again!


Task 467-468: ParsiNLU-reading_comprehension

Based on the: https://arxiv.org/pdf/2012.06154.pdf

Looks good to me! I would suggest changing "Given a passage, generate a question based on it" to "Given a passage, generate a question based on the passage" in the README file. Both JSON files look good to me.

Thanks! I updated the README file.


Clean

Fixed most issues. However 'go test' has to be run inside /food.

Ok, I just cherry picked your commits to avoid ending up with the pkg and src directories in the history. Closing this since the changes are in, thanks for your great work!

Thanks for helping me through the whole process (still new to the open-source (and coding) world).
-Vikhyath Mondreti

On 25-Jun-2016, at 9:47 PM, sleepypikachu<EMAIL_ADDRESS>wrote:
Ok, I just cherry picked your commits to avoid ending up with the pkg and src directories in the history. Closing this since the changes are in, thanks for your great work!
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub https://github.com/sleepypikachu/still-good-food/pull/3#issuecomment-228553503, or mute the thread https://github.com/notifications/unsubscribe/ARHpBrYQUyQX8PrxXW2wKdgWmDLgWL2vks5qPVSygaJpZM4I-XlX.


Express period filtering in the URLs for the group extended view

It would be nice to have the periods users select in the group extended view also expressed in the URL, so we can maintain the history when moving across views. i.e. keep the same view when going back from the instances view for example.

@joaquimrocha this can be closed now

Closing. Thanks.


Create uk_ua.json

Contact us if you need anything else, our team is always ready to translate something nice <3


YOURLS MultiSite

Hi, I'm a retired computer programmer (new to GitHub, maybe too old to be writing programs, a couple dozen grandkids,  one of whom is an airplane pilot!).
A couple months ago I started a project and wanted to use YOURLS in a MultiSite mode (like WordPress). But YOURLS doesn't do MultiSite, Yet!  So I hacked the code and built my own. My YOURLS MultiSite Roadmap is at ** YOURLS MultiSite **
On that page, you can see a Proof-Of-Concept - some URLs that forward through this YOURLS MultiSite.  I am now building this into a production site.
On that page, I have addressed these topics...
YOURLS MultiSite Roadmap
YOURLS MultiSite is a Drop-In Replacement for YOURLS.
YOURLS MultiSite Proof-Of-Concept URLs - /s/ directory.
Works for a Single-Site or MultiSites.
Give YOURLS Its Own Directory, like WordPress!
Simple and Easy Configuration.
Easy to add more Domains to MultiSite.
Simple to use YOURLS MultiSite "Advanced" Configuration.
Easy to rename /admin directory.
Works with WordPress on the SAME Domain! (No Subdirectory needed!)
Testing YOURLS MultiSite.  What's Tested?
Update Readme file to be more dynamic.
Update XHTML to HTML5 standards. In Progress.
YOURLS MultiSite Production URLs - /yourls/ directory. Being Built!
YOURLS MultiSite Limitations.
Redirect YOURLS subdirectory to the main directory using .htaccess...
Plugins For YOURLS Should Work.
Tested Plugins.
These are all working now, either on my development server, or live in the Proof-Of-Concept.
YOURLS MultiSite uses about 99% of the original YOURLS code so I think it should be compatible with things like plugins.
I'm sorry if I am a little bit slow, or old, (50+ years of writing computer programs!), or don't pick up things as quickly as I did before.  But if anyone would like to see/use/modify this code, or merge it into the YOURLS project (it should be a drop in fit.)
Caution: I have not done the last few YOURLS modifications for the last couple months.  But I plan to!
The Proof-Of-Concept is running on shared hosting (Ubuntu) at Pair Network. You can check their site for the environment.
Anyone Interested?
Sincerely,
Pop VeKind
TuKod
(TuKod is a Filipino word meaning "Support!"  It is also the NuEnglish spelling of "To Code!")

Hello
It looks like an interesting project. Ideally though, you would package everything as a plugin instead of a standalone replacement that uses "99% of the original code", this would allow for future compatibility and ease of use
Also, did you check this plugin https://github.com/adigitalife/yourls-allow-aliases, it may be inspirational

Greetings from the Philippines!
I started out to build a multisite plugin.  Although most of the code stays the same, the strategic changes would mean copying most of the core functions into the plugin.  Just like when WP added MultiSite. The only truly viable way was to actually replace part of the WP core.  Originally WPMU was a drop in replacement for a large part of the WP core. Time proved the wisdom in this as WPMU was then merged into the WP core as MultiSite with only simple configuration from one to the other.
The same applies here, YOURLS MultiSite changes minor, but critical and strategic things, throughout the program.  By design, it will work as a single site with NO configuration changes.  Easy configuration changes would let the site admin add the features available for MultiSite.
Yes! I had looked at the Allow aliases for YOURLS plugin, even before I got started, as well as many other plugins.
"Aliases" simply allows you to address the same YOURLS keywords to different domains.  Effectively making two URLs with different domain names that go to the same place.  They both use the same MySQL Table, Making one domain's keywords to be aliases of another YOURLS domain.
Personally, I wouldn't do such a thing.  Not that the sky would fall or anything like that.  I am assuming each would do a 301.  I just personally don't like the idea of doing the same thing with different domains, it seems wasteful. Just a preference, not saying it is wrong.
YOURLS MultiSite is not that way at all.  It largely follows the WordPress MultiSite ideas (ok, I confess, I stole a lot of the idea from WP).  Each Domain name is a complete YOURLS site.  Like WP they use different sets of tables for completely separate sites. If you notice on ** YOURLS MultiSite ** there are six domain names configured in the Proof-Of-Concept demo.  Look closely and you will see that the six examples all use the keyword "54".  The same keyword in different domains, going to 6 different URLs. This produces the exact same result as loading six copies of YOURLS!  Each can be totally configured separately, yet reside in one physical location on the server.
YOURLS and WordPress together!
Down the page a bit you will find a section called:
YOURLS MultiSite Production URLs
Here I am building a production model for a new project I am working on.  You will notice that I am running both YOURLS and WordPress side by side in the document root of each domain.
Both YOURLS and more importantly WordPress is running independent of each other, with no restrictions on either.
Because I moved the YOURLS files to its own directory and split the site URLs from the location URLs, The location URL become self-aware for document root sites.  I was able to determine the different requirements of each program and merge them to work together.
This server is actually running about 50 small WordPress sites that are spread across a half-dozen WordPress MultiSite installs.  AND ONE YOURLS MultiSite running three sites now and will increase to six. You and I both know that 6 YOURLS cannot be loaded as is into one document root.  Likewise, adding even one WP site or WP MultiSite would break it. However, moving YOURLS completely off the document root allows me to demonstrate multiple YOURLS and multiple WP sites doing just that.
Finally, I would be the first to say this should be considered no more than beta software.  I am more than capable of maintaining my production sites and "going it alone."  Although it is working perfectly in my tests, I still need to work on the documentation and upgrade the XHTML to HTML5 (minor cleanup stuff). However, YOURLS MultiSite needs more and more varied testing.
I would like more people to test with me.  For example, all plugins and API need testing.  After the code proves itself you then may consider merging it into the YOURLS core.  Do you have a suggestion how I might proceed with this?  I am just learning about GitHub so forgive my ignorance. Would it be better to branch or fork this project?  I do believe YOURLS MultiSite can be merged into the YOURLS Master once it has proven itself.
I will be looking for your advice on how to proceed,
Pop VeKind
PS: A big THANK YOU for such a wonderful program.  It is very useful as is and also has great future potential.

When do you plan to give us look into the code you changed?
You stopped your first try https://github.com/TuKod/Allow-YOURLS-with-CMS 5 years ago.
or where did you fork it? any chance to get read access to your repository?

@grzchr15 - Sorry about the delay and the confusion, I will try to explain.
The project, including the MultiSite feature, we are referring to it as YOURLS-PV.
PV as in Pretty Valuable!
You can find all the information there is at yourls.y143.net  Configuration examples are under construction, however, you will likely be interested in...
The YOURLS Code Adjustments Page.
You Asked, "When do you plan to give us look into the code you changed?"
I answered this in-depth at https://github.com/YOURLS/YOURLS/issues/1611
Short Answer, the YOURLS-PV site has it now!

Humm... I understand the confusion.  The TuKod account belongs to the "TuKod Team".  Tukod sounds like "To Code" and means "Support" in the locally used language (one of about 90 languages used here in the Philippines).  The TuKod Team is a group of young people I teach and let use my computer and Internet connection.  Most of them come from very poor families who earn and live on about US$1.30 a day!  Per Family!  None has any chance of attending college.  However, one of them now has a job making websites, for about US$4 per 10 hour day.  The others call him "Rich!"
The TuKod Team made "the first attempt."  Likewise, I should not have borrowed their account to make my earlier YOURLS comments.  TuKod is back, exclusively, for their use.  PopVeKind is now my new retirement account. I'm sorry about the confusion.
You Asked,_ "any chance to get read access to your repository?"_
The top-right corner of yourls.y143.net  has a link to the correct GitHub repository (PopVeKind/YOURLS), which is both open-source and can be accessed by the public.
CAUTION:
In order to keep YOURLS-PV as drop-in compatible with all installations of YOURLS, and as small as possible, we have not changed the included documentation.  Nor did we change the .htaccess file that is automatically built.  In order to use the NEW Features of YOURLS-PV, you must follow the configuration examples being posted on the website for both the config.php file and the .htaccess file..
Enjoy,
Pop VeKind

Since the small YOURLS-PV Patch (formerly MultiSite) has matured and adjusted to the Config Class (Config.php).  I decided to close this issue.
Future YOURLS-PV Patch development has moved to a new issue:
Testers Needed - YOURLS-PV Patch https://github.com/YOURLS/YOURLS/issues/2320


Question about segment size

Is there any way to get the size of the segment that is being used for audio, video and text?

Would it be possible to only get the one that is currently playing or the last one that has been downloaded?

manifest.presentationTimeline.getMaxSegmentDuration() is not exported, but if it is exported I can access to the value with player.getManifest().presentationTimeline.getMaxSegmentDuration()
And it's enough for now.

@avelad Oh, I have actually just landed that same change. See if it works for you now!

Now it works!


Do linters run in parallel?

I'm having trouble navigating this project to get the answer I want. It looks like linters run in a separate thread, but if multiple linters run for a single file, do they run in series in that thread, or in parallel in multiple threads?

@groteworld perhaps you have a short answer for this?

They run in series, this order is defined by what linter registers with the persist module of SL3 first. The order of what plugin loads first, and whether that is a parallel race-condition or ordered by some means in serial, is above my knowledge of SublimeTest.

Neat!


Android Navigation Drawer Activity Template

Created initial template file based on Android Navigation Drawer Activity Project

fixed the issue. README.md and the LICENSE files have been added

From: Dr. Brian Bansenauer @.>
Sent: Wednesday, November 24, 2021 8:57 PM
To: MobileApps-Cascadia/campus-guidebook-android @.>
Cc: isaakwheeler @.>; Comment @.>
Subject: Re: [MobileApps-Cascadia/campus-guidebook-android] Android Navigation Drawer Activity Template (PR #22)
@Bansenauer-Cascadia requested changes on this pull request.
This looks good, but the current branch removes the README.md and the LICENSE files. Please add these back into your folder
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHubhttps://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FMobileApps-Cascadia%2Fcampus-guidebook-android%2Fpull%2F22%23pullrequestreview-815557626&data=04|01||34d0d00b66814e8c221208d9afd005f4|84df9e7fe9f640afb435aaaaaaaaaaaa|1|0|637734130303573366|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|3000&sdata=vbYK9kzWLY0DdG6fHuHULJgtV5%2BbcXX%2Fxj4r5SEtglw%3D&reserved=0, or unsubscribehttps://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FASO772M4JVKAJWWAPBGAHB3UNW6Z5ANCNFSM5IVDQTHA&data=04|01||34d0d00b66814e8c221208d9afd005f4|84df9e7fe9f640afb435aaaaaaaaaaaa|1|0|637734130303573366|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|3000&sdata=wE5FiXtBZH2sGouy%2FHMnJbCy5fKxRMYyfaBt4BbKDgM%3D&reserved=0.
Triage notifications on the go with GitHub Mobile for iOShttps://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fapps.apple.com%2Fapp%2Fapple-store%2Fid1477376905%3Fct%3Dnotification-email%26mt%3D8%26pt%3D524675&data=04|01||34d0d00b66814e8c221208d9afd005f4|84df9e7fe9f640afb435aaaaaaaaaaaa|1|0|637734130303583319|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|3000&sdata=WF0%2BnL7cCT5RGuNNwpOrHOTbdZ2acAe711OrYe5MM58%3D&reserved=0 or Androidhttps://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fplay.google.com%2Fstore%2Fapps%2Fdetails%3Fid%3Dcom.github.android%26referrer%3Dutm_campaign%253Dnotification-email%2526utm_medium%253Demail%2526utm_source%253Dgithub&data=04|01||34d0d00b66814e8c221208d9afd005f4|84df9e7fe9f640afb435aaaaaaaaaaaa|1|0|637734130303583319|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|3000&sdata=beI%2BgBNWcnrva7MDm3eNkGWBXfDTUXVEYuEWyuLVyBQ%3D&reserved=0.


feat: add client for nostr stalls/products

@LeeSmet when firing the script multiple times, the producs and stalls begin to duplicate on the server. Not sure what is going on here, but I thought you added some code that notifies the server if a stall or product needs to be updated?


Support for importing objects as custom environments

Clear and concise description of the problem

Starting from 0.23.0, you can create your own package to extend Vitest environment. To do so, create package with the name vitest-environment-${name}. That package should export an object with the shape of Environment:

Sometimes, custom environment is just a module file, I don't want to make it a npm package. Importing this module directly is a better option for me.
Suggested solution
Allows developers to use Environment type objects directly as custom environments.
// test/env/custom-env.ts
import type { Environment } from 'vitest'
export default <Environment>{
  name: 'custom',
  setup() {
    ...
    return {
      teardown() {
        ...
      }
    }
  }
}

// vitest.config.ts
import customEnv from './test/env/custom-env'
export default defineConfig({
  test: {
    environment: customEnv
  }
})

Alternative
No response
Additional context
No response
Validations

[x] Follow our Code of Conduct
[x] Read the Contributing Guidelines.
[x] Read the docs.
[x] Check that there isn't already an issue that request the same feature to avoid creating a duplicate.

Importing objects would not be possible. But we can allow importing any file.

But we can allow specifying a path to any file.

This is also a very good idea, and I would appreciate it if this feature could be supported in future version.

Importing objects would not be possible.

why? Is this technically impossible？

why? Is this technically impossible？

Yes, config is resolved in the main thread, but tests are running in worker threads, so we cannot passdown functions between them. And we don’t want to resolve config for each test because it’s expensive.

Importing objects would not be possible. But we can allow specifying a path to any file.

Relative path environment implemented via #3203 and released in v0.34.0


"Accessing PropTypes via the main React package is deprecated. Use the prop-types package from npm instead."

Looks like this library needs a small update! I currently get this error in console.

Thanks rublev! I'll make sure it gets some TLC soon.

Closed in commit 6c6d0a33a1c68ccf14e5ed9e6df9dfdc40dd20c8 and published in version 2.1.0.


Benchmark queries without caching

Adding variations of the query tests that disable the query cache. This
gives us an idea of what overhead is involved in query compilation.
For EF7 I'm using a null implementation of IMemoryCache, which means
that we still go through all the locking etc. in CompiledQueryCache.
This gives the best approximation of running a query where it does not
already exist in the cache.
For EF6 we need to use reflection to get the ObjectQuery to disable
caching :facepunch:.

:shipit:


Sync upstream

:tada: This PR is included in version 1.2.0 :tada:
Your semantic-release bot :package::rocket:


Dangerous global detection bypass with memo dict confusion

Info
The picklescan tool attempts to keep track of the memo dict by parsing the
memoize opcodes whenever seen. The binput and put instructions also
insert objects into the memo but are left unhandled. While a legitimate python3
pickle should never mix *put and memoize instructions, doing so is accepted
by pickle.load.
Malware can potentially set up the memo using a mix of these opcodes so that
picklescan thinks memo[0] contains a safe module name like torch._utils
when it actually contains a dangerous one. Used in conjunction with binget
and stack_global instructions and any arbitrary python import can be made to look
safe to picklescan.
Example
The following example uses radare2 (rasm2 and r2
commands) with the r2pickledec
plugin.
This following memo.asm file is commented to explain the bypass. Comments
start with ;.
;; Dangerous strings added to memo
binstring "os"      ;; module name for os.system
binput 0            ;; memo[0] = stack[-1] = "system"
binstring "system"  ;; function name for os.system
binput 1            ;; memo[1] = stack[-1] = "system"

;; Safe strings added to memmo
binstring "torch._utils"
memoize
binstring "_rebuild_tensor_v2"
memoize

;; State of memo
;; real memmo looks like
;;; memo = {0: "os", 1: "system", 2: "torch._utils", 3: "_rebuild_tensor_v2"}
;;; picklescan's memo looks like
;;; memo = {0: "torch._utils", 1: "_rebuild_tensor_v2"}

binget 0        ;; "os" but picklescan thinks it's "torch._utils"
binget 1        ;; "system" but picklescan thinks it's "_rebuild_tensor_v2"
stack_global    ;; really: "os.system" but Picklescan thinks this is "torch._utils._rebuild_tensor_v2"
stop

The pickle can be assembled with rasm2.
$ rasm2 -a pickle -Bf memo.asm > memo.pickle

Decompiling the pickle with r2 may help with understanding.
# r2 -a pickle -qqc 'pdP' memo.pickle
## VM stack start, len 5
## VM[4]
str_x0 = "os"
## VM[3]
str_x9 = "system"
## VM[2]
str_x16 = "torch._utils"
## VM[1]
str_x28 = "_rebuild_tensor_v2"
## VM[0] TOP
return _find_class(str_x0, str_x9)

The pickle will return os.system when loaded, proving access to a
dangerous function without a detection by picklescan.
$ python3 -m pickle memo.pickle
<built-in function system>

$ picklescan -p memo.pickle
----------- SCAN SUMMARY -----------
Scanned files: 1
Infected files: 0
Dangerous globals: 0

Fix
A legitimate pickle that uses memoize should not use binput or put. So
the simplest fix is to mark any pickle that contains a memoize instruction
and either a binput or put instructions as dangerous.
Attempting to parse the memo without a full AST is error prone. The
r2pickledec is the only tool I am aware of that will produce a
full AST for all python pickle instructions. Running pdPj will produce the
following JSON for the above pickle.
$ r2 -a pickle -qqc 'pdPj~{}' picks/memo.pickle
{
  "stack": [
    {
      "offset": 0,
      "type": "PY_STR",
      "value": "os"
    },
    {
      "offset": 9,
      "type": "PY_STR",
      "value": "system"
    },
    {
      "offset": 22,
      "type": "PY_STR",
      "value": "torch._utils"
    },
    {
      "offset": 40,
      "type": "PY_STR",
      "value": "_rebuild_tensor_v2"
    },
    {
      "offset": 68,
      "type": "PY_GLOB",
      "value": {
        "module": {
          "offset": 0,
          "type": "PY_STR",
          "prev_seen": ".stack[0]"
        },
        "name": {
          "offset": 9,
          "type": "PY_STR",
          "prev_seen": ".stack[1]"
        }
      }
    }
  ],
  "popstack": [
  ]
}

Using r2pickledec in picklescan is possible through r2pipe but would
require adding dependencies that are not trivially installed with just pip.
I am the author of the pickle architecture in r2 and the r2pickledec
plugin. So I can offer som help if desired.
A warning on using proto for a fix
Since the offending opcodes are protocol 2 instructions, it might be tempting
to only accept them when a pickle starts with proto 2. This won't work. A
pickle can redeclare it's protocol version at will without any unpickling
error. Additionally, a pickle that has declared itself as proto 2 still has
access to protocol 4 instructions.

A legitimate pickle that uses memoize should not use binput or put

If the pickle spec prohibits this, then the "simple fix" is what I'd go for.
I'll take a look on my side too!


Does this support other types of ACLs?

Love this so far. Just wondering, does this support standard ACL's and IPv6? It seems to only pickup IPv4 extended access-lists. Thanks in advance.

Great to know you're enjoying it!
While Standard ACL is supported, but it is implemented in a somewhat unconventional manner. In my experience, there have been no projects related to standard ACL to refine this package.
I don't plan to implement the new IPv6 feature in the near future, for the same reason, there are no projects requiring IPv6.
Example of a standard ACL.
import cisco_acl

config = """
ip access-list standard ACL
  permit <IP_ADDRESS> <IP_ADDRESS>
  permit <IP_ADDRESS> <IP_ADDRESS>
  permit <IP_ADDRESS> <IP_ADDRESS>
"""
acl = cisco_acl.Acl(line=config, type="standard")
print(acl)
# ip access-list standard ACL
#   permit <IP_ADDRESS> <IP_ADDRESS>
#   permit <IP_ADDRESS> <IP_ADDRESS>
#   permit <IP_ADDRESS> <IP_ADDRESS>

for ace in acl.items:
    print(f"{ace.srcaddr.prefix=}")
# ace.srcaddr.prefix='<IP_ADDRESS>/24'
# ace.srcaddr.prefix='<IP_ADDRESS>/24'
# ace.srcaddr.prefix='<IP_ADDRESS>/24'


Why is the implementation of Mamba so slow?

I haven't run the official version of Mamba, but I've run your implementation, and it seems that the training speed of this model is much slower than that of the Transformer.

I am also facing the similar issue. Are you able to find the reason for it?

that is mainly because there is something wrong which lead the loss.backward so slow

It's not meant to be fast! This repo is mostly only for educational purposes. I would suggest using the official repo to do any training: https://github.com/state-spaces/mamba

probably because mamba-ssm designed a GPU-adapted scanning operation based on C.

This model can only run on my CPU

This model can only run on my CPU
Python: 3.12.4
Pytorch: 2.3

I think the problem is embeding layer. D-layer is 50280, lol.


Commenting system ui check

If need to change UI for comments
Also add the snackbar on commenting.

Done


not working anymore

Description
everything loads but when trying to play anything you get Index:0 Size:0 error
Reproduction steps
everything loads but when trying to play anything you get Index:0 Size:0 error
App version
1.4.0
Operating system
Fire tv os 8 , os 7 , Android tv , Google tv 12
Logs
No response
Please confirm the following

[X] I have searched the existing issues and this is a new ticket, NOT a duplicate or related to another open issue.
[X] If related to a provider, I have checked the site and it works, but not the app.

Fixed on Release 1.4.1

Thank you so much for your continuous support


python310Packages.peaqevcore: 3.0.7 -> 3.1.3

Description of changes
Update to latest upstream release 3.1.3

Things done

Built on platform(s)

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

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

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

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

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

[x] Fits CONTRIBUTING.md.

Result of nixpkgs-review pr 180585 run on x86_64-linux 1

2 packages built:

python310Packages.peaqevcore
python39Packages.peaqevcore


stats: add unit support to histogram

Signed-off-by: Taras Roshko<EMAIL_ADDRESS>Description: Add unit to the histogram type so that the stat sinks can disambiguate among various types of histograms (some Metric stores support timer vs non-timer histograms and generally speaking there already are histograms measuring bytes and microseconds, but it's all assumed to be millis on flush
Risk Level: Low
Testing: Unit tests
Docs Changes: N/A
Release Notes: Included
Fixes: #8164

@jmarantz
Release builds are failing due to stat size checking tests:
StatsThreadLocalStoreTestNoFixture.MemoryWithoutTlsFakeSymbolTable and StatsThreadLocalStoreTestNoFixture.MemoryWithTlsFakeSymbolTable are 16 bytes off
ClusterMemoryTestRunner.MemoryLargeClusterSizeWithFakeSymbolTable and
ClusterMemoryTestRunner.MemoryLargeClusterSizeWithRealSymbolTable are 32 bytes off
I don't know exactly how these are computed but a small size difference is expected, let me know if I can adjust the asserts.
Other things I'd like your opinion on:

HistogramCompletableTimespan is kind of ugly with these asserts, one thing I was thinking of is to introduce a method on histogram like quantity() returning an enum with values Unspecified, Information, Time and assert on quantity == Time instead of the switch in the ctor.
Multiple null histograms cached in fields in ThreadLocalStoreImpl vs enum to null histogram map (this requires either a copy ctor on the null histogram class or a move ctor which seemed like a bad trade off so I stored them in fields in this PR)
I'd like to update the metrics service to send the unit along with the bucket data, this is a forward/backward compatible change and should not break anyone.

Yes if you are adding some stat data of value, like an enum to a histogram, that seems totally worth it and you should just bump the limit.
You can also test locally with 'blaze test -c opt --test_env=ENVOY_MEMORY_TEST_EXACT=true' so you can get the test working locally before pushing to CI.
I will start reviewing your PR; sorry for the delay.

Thanks a bunch for taking the time to review this @jmarantz!
I think I addressed the comments (minus the release messaging and some questions I had).
Let me know what your thoughts are on the questions 1-3, I think we should at least update the metric service contract to send the unit.

Oh sorry I missed the 3 questions:

HistogramCompletableTimespan is kind of ugly with these asserts, one thing I was thinking of is to introduce a method on histogram like quantity() returning an enum with values Unspecified, Information, Time and assert on quantity == Time instead of the switch in the ctor.

I didn't notice asserts in there. Maybe I'm missing something?

Multiple null histograms cached in fields in ThreadLocalStoreImpl vs enum to null histogram map (this requires either a copy ctor on the null histogram class or a move ctor which seemed like a bad trade off so I stored them in fields in this PR)

I think what you have is OK, but I wanted to take one more shot at simplifying the null histograms. Can you just change the asserts to allow for the case of a null histogram? Say, by having an isNull() pure method in the Histogram interface that you can check?

I'd like to update the metrics service to send the unit along with the bucket data, this is a forward/backward compatible change and should not break anyone.

ok sounds fine to me then.
My main blocker is I'd like to hear from @envoyproxy/senior-maintainers about the breaking changes to monitoring and how to message that and/or phase it.

Leaving the names as-is sounds good to me. You could whitelist any existing names that are in violation; there's a few similar patterns in check_format.py.

I didn't notice asserts in there. Maybe I'm missing something?

Oh sorry I missed the 3 questions:

HistogramCompletableTimespan is kind of ugly with these asserts, one thing I was thinking of is to introduce a method on histogram like quantity() returning an enum with values Unspecified, Information, Time and assert on quantity == Time instead of the switch in the ctor.

I didn't notice asserts in there. Maybe I'm missing something?

Multiple null histograms cached in fields in ThreadLocalStoreImpl vs enum to null histogram map (this requires either a copy ctor on the null histogram class or a move ctor which seemed like a bad trade off so I stored them in fields in this PR)

I think what you have is OK, but I wanted to take one more shot at simplifying the null histograms. Can you just change the asserts to allow for the case of a null histogram? Say, by having an isNull() pure method in the Histogram interface that you can check?

I'd like to update the metrics service to send the unit along with the bucket data, this is a forward/backward compatible change and should not break anyone.

ok sounds fine to me then.
My main blocker is I'd like to hear from @envoyproxy/senior-maintainers about the breaking changes to monitoring and how to message that and/or phase it.

Tagged you directly in the diff to explain what I was thinking in more detail.
Simplified the null histograms as per your suggestion (I was thinking about similar approach but was not sure you'd be fine with a virtual marker, I made it more generally useful so it does not look like a hack, let me know if that's what you meant)
Will push a separate commit to plumb through the metric service

Finally as per Matt's suggestion I'm reverting the name changes altogether and will leave a TODO in statsd for the maintainers to consider scaling unsuffixed histograms reported not in millis as these are a usability disaster for the users (statsd thinks it's millis, users think it's millis, the name has no indication it's not, but it's not). This will ensure backward-compat. Will tune the check_format to give everything existing a pass and bark about any future suffixes.

macOS test failure seems intermittent (a timeout), other than that I think I've addressed everything. Will not be changing metric service as this is uses Prometheus proto contract so out of scope.

Sorry looks like it needs a master merge.
/wait

@troshko111 friendly request to please never force push, just merge master and push commits. Thank you!

@troshko111 friendly request to please never force push, just merge master and push commits. Thank you!

Ah my bad! I thought merge conflicts were ok to rebase, I now see that GitHub makes it painful to review when the history changes (does not store snapshots to compare to), sorry for that.

@troshko111
hi, I'm trying to add new envoy histograms in this PR https://github.com/envoyproxy/nighthawk/pull/378, e.g. HISTOGRAM(latency_on_success_req_us, Microseconds)
I got check_format error because of the unit in the definition
"Don't suffix histogram names with the unit symbol, it's already part of the histogram object and unit-supporting sinks can use this information natively, other sinks can add the suffix automatically on flush should they prefer to do so."
However build failed after I removed the unit from the definition HISTOGRAM(latency_on_success_req_us)
because GENERATE_HISTOGRAM_STRUCT(NAME, UNIT) requires unit in the histogram definition
So I'm confused, is the check_format rule outdated? If not, what is the recommended way to define histogram?
Thanks!


unresolved buildin $macro

e.g.: $type

I'm not familiar with this feature.  Is $type supposed to be a substitution variable? (i.e. an instantiation of a macro?)  What is $type supposed to resolve to?
Can you provide a complete example?

@EBatTiVo I guess it's a "shortcut" for Type.typeOf

http://haxe.org/manual/type-system-type-inference.html

So, it looks like we need to let $ resolve as a local variable name inside of macro functions, and also add the keyword/function $type as a resolvable global function. Are there other uses of a dollar-sign prefix?

There's another feature which uses the dollar sign ($):
http://haxe.org/manual/macro-reification-expression.html

Our parser allows dollar-identifiers in most places but they usually fail at typing-level (which you shouldn't have to worry about). I think you can safely accept $ as a leading character for any identifier without introducing syntactic ambiguities.
Other than macro reification there's also string interpolation where $ has special semantics: http://haxe.org/manual/lf-string-interpolation.html


Add constructor to RsaSecurityKey that takes E, N

this would remove the need to use RSAParameters for this simple case.

@henrik-me we can probably live without this.


Tup does not track new files

test_deployer.go isn't picked up, and flynn-test isn't recompiled, so the suite is not ran.
https://s3.amazonaws.com/flynn-ci-logs/20141217042017-5e287fe5-build-313c6b19d4652f63d5e564e6c4955111888812f4-2014-12-17-04-29-30.txt

Obsoleted by #3817.


Add Reading Time Recipe needs to be update to reflect new render method.

📚 Subject area/topic
Recipes
📋 Page(s) affected (or suggested, for new content)
https://docs.astro.build/en/recipes/reading-time/
📋 Description of content that is out-of-date or incorrect
The line const { Content, remarkPluginFrontmatter } = await entry.render(); in the code sample for dynamically generated pages needs to be updated to const { Content, remarkPluginFrontmatter } = await render(entry); to reflect the new use of render.
params: { slug: entry.slug }, should be updated to params: { slug: entry.id },.
I'm willing to do a PR to correct.
🖥 Reproduction in StackBlitz (if reporting incorrect content or code samples)
https://codesandbox.io/p/devbox/billowing-fast-flypqx?workspaceId=ws_G4yXD7UznkG3Cy1arhHtf1

Thank you for spotting this! We would be happy to have a contribution to update the recipe for the current version of content collections, (and note that I think you'll need to now include render in the import statement, too).
I'll add the tag help wanted which means we're happy to have a PR!


Solution webview doesn't highlight python3 language

🐛 Bug Report
The highlight.js seems unable to recognize python3, and will not highlight the code fences.
To Reproduce
Execute Show Top Voted Solution on any problem with language python3, then we'll get

Expected behavior
Alter Solution.lang: python3 to python when passed to highlight.js.

@Vigilans I think this should be fixed in #224, right?

@jdneo Yes, I have tested it.


TypeError: Cannot read property 'null' of undefined

I couldn't reproduce the issue in a plunk, therefore I made a screenshot from the browser console:

This happens for some reasons in one of our projects.
The problem is in scale.time.js:
getPixelForTick: function(index, includeOffset) {
    return this.getPixelForValue(this.tickMoments[index], null, null, includeOffset);
},

null,null is passed to: this.getLabelMoment(datasetIndex, index); here:
getPixelForValue: function(value, index, datasetIndex, includeOffset) {
    var labelMoment = value && value.isValid && value.isValid() ? value : this.getLabelMoment(datasetIndex, index);

and then this.labelMoments[null][null] failed:
getLabelMoment: function(datasetIndex, index) {
    return this.labelMoments[datasetIndex][index];
}

Going to post a pull request for that tomorrow.

This happens no matter what i set the value in getPixelForValue on line 169
chart_test.txt

So this seems to work:
ctx.fillRect(xaxis.getPixelForValue("THIS IS IGNORED",13,1), yaxis.top, xaxis.getPixelForValue("THIS IS IGNORED",10,1)-xaxis.getPixelForValue("THIS IS IGNORED",13,1), yaxis.bottom);
So you have to do getPixelForValue("THIS DOESN'T MATTER", ,  )
Ideally we should be able to call getPixelForValue( new Date [.....])

@zpriddy Sorry, I forgot about this issue. I'm going to post a pull request with a fix as soon as I can.


Similar products sample

@kgrashad is this conflicting with your previous pull request?  Do you mind updating it?

@willportnoy Done


if scroll the window, the contextmenu will not visible

I have modified the bug, please merge it, thanks: https://github.com/jnotnull/react-contextmenu/commit/774f05420905a90504a247b694d5f55fc5d851ef
Version
1.2.0
Test Case
http://jsbin.com/sacerobuxi/edit?html,js,output
Steps to reproduce
Expected Behavior
Actual Behavior

Can you provide more details? this is not helpful

How this will work and its merged or not

Closing due to no response


remake exporting to csv filters fetch

Related to: https://github.com/Giveth/impact-graph/issues/1002
But also a bug fix, after updating adminjs, all routes changed and express middlewares were no longer accesible.
Removed Redis and instead used the rawHeaders attributes directly to fetch filter params

Export example with fake data, including the userscore and qfroundId, fromwalletaddress,projectId, toWalletaddress, network id and transaction hash are all included like before.