Updated to latest beta failing to connect

HA recommended an update for this, after waiting a few days I hit the trigger. Since then there seems to be no communication from HA.
Any help would be appreciated 👍
HA Addon log
2024/10/26 08:15:48 [info] 372#372: *621 epoll_wait() reported that client prematurely closed connection, so upstream connection is closed too while sending request to upstream, client: <IP_ADDRESS>, server: , request: "GET /apiv1/json HTTP/1.1", upstream: "http://<IP_ADDRESS>:7813/apiv1/json", host: "<IP_ADDRESS>:8099"
2024/10/26 08:17:18 [info] 372#372: *623 epoll_wait() reported that client prematurely closed connection, so upstream connection is closed too while sending request to upstream, client: <IP_ADDRESS>, server: , request: "GET /apiv1/json HTTP/1.1", upstream: "http://<IP_ADDRESS>:7813/apiv1/json", host: "<IP_ADDRESS>:8099"
2024/10/26 08:18:48 [info] 372#372: *625 epoll_wait() reported that client prematurely closed connection, so upstream connection is closed too while sending request to upstream, client: <IP_ADDRESS>, server: , request: "GET /apiv1/json HTTP/1.1", upstream: "http://<IP_ADDRESS>:7813/apiv1/json", host: "<IP_ADDRESS>:8099"
2024/10/26 08:20:18 [info] 372#372: *627 epoll_wait() reported that client prematurely closed connection, so upstream connection is closed too while sending request to upstream, client: <IP_ADDRESS>, server: , request: "GET /apiv1/json HTTP/1.1", upstream: "http://<IP_ADDRESS>:7813/apiv1/json", host: "<IP_ADDRESS>:8099"
2024/10/26 08:21:48 [info] 372#372: *629 epoll_wait() reported that client prematurely closed connection, so upstream connection is closed too while sending request to upstream, client: <IP_ADDRESS>, server: , request: "GET /apiv1/json HTTP/1.1", upstream: "http://<IP_ADDRESS>:7813/apiv1/json", host: "<IP_ADDRESS>:8099"
2024/10/26 08:23:18 [info] 372#372: *631 epoll_wait() reported that client prematurely closed connection, so upstream connection is closed too while sending request to upstream, client: <IP_ADDRESS>, server: , request: "GET /apiv1/json HTTP/1.1", upstream: "http://<IP_ADDRESS>:7813/apiv1/json", host: "<IP_ADDRESS>:8099"
2024/10/26 08:24:48 [info] 372#372: *633 epoll_wait() reported that client prematurely closed connection, so upstream connection is closed too while sending request to upstream, client: <IP_ADDRESS>, server: , request: "GET /apiv1/json HTTP/1.1", upstream: "http://<IP_ADDRESS>:7813/apiv1/json", host: "<IP_ADDRESS>:8099"
2024/10/26 08:26:18 [info] 372#372: *635 epoll_wait() reported that client prematurely closed connection, so upstream connection is closed too while sending request to upstream, client: <IP_ADDRESS>, server: , request: "GET /apiv1/json HTTP/1.1", upstream: "http://<IP_ADDRESS>:7813/apiv1/json", host: "<IP_ADDRESS>:8099"
2024/10/26 08:27:41 [info] 372#372: *637 epoll_wait() reported that client prematurely closed connection, so upstream connection is closed too while sending request to upstream, client: <IP_ADDRESS>, server: , request: "GET /apiv1/json HTTP/1.1", upstream: "http://<IP_ADDRESS>:7813/apiv1/json", host: "<IP_ADDRESS>:8099"
2024/10/26 08:29:19 [info] 372#372: *639 epoll_wait() reported that client prematurely closed connection, so upstream connection is closed too while sending request to upstream, client: <IP_ADDRESS>, server: , request: "GET /apiv1/json HTTP/1.1", upstream: "http://<IP_ADDRESS>:7813/apiv1/json", host: "<IP_ADDRESS>:8099"
2024/10/26 08:29:51 [info] 372#372: *641 epoll_wait() reported that client prematurely closed connection, so upstream connection is closed too while sending request to upstream, client: <IP_ADDRESS>, server: , request: "GET /apiv1/json HTTP/1.1", upstream: "http://<IP_ADDRESS>:7813/apiv1/json", host: "<IP_ADDRESS>:8099"
2024/10/26 08:30:32 [info] 372#372: *643 epoll_wait() reported that client prematurely closed connection, so upstream connection is closed too while sending request to upstream, client: <IP_ADDRESS>, server: , request: "GET /apiv1/json HTTP/1.1", upstream: "http://<IP_ADDRESS>:7813/apiv1/json", host: "<IP_ADDRESS>:8099"
s6-rc: info: service legacy-services: stopping
s6-rc: info: service legacy-services successfully stopped
s6-rc: info: service nginx: stopping
2024/10/26 08:30:58 [notice] 310#310: signal 15 (SIGTERM) received from 27, exiting
2024/10/26 08:30:58 [notice] 372#372: exiting
2024/10/26 08:30:58 [notice] 372#372: exit
2024/10/26 08:30:58 [notice] 310#310: signal 17 (SIGCHLD) received from 372
2024/10/26 08:30:58 [notice] 310#310: worker process 372 exited with code 0
2024/10/26 08:30:58 [notice] 310#310: exit
[08:30:58] INFO: Service NGINX exited with code 0 (by signal 0)
s6-rc: info: service nginx successfully stopped
s6-rc: info: service init-nginx: stopping
s6-rc: info: service interface: stopping
s6-rc: info: service init-nginx successfully stopped
s6-rc: info: service s6rc-oneshot-runner: starting
s6-rc: info: service s6rc-oneshot-runner successfully started
s6-rc: info: service base-addon-banner: starting
-----------------------------------------------------------

 Add-on: Bepacom BACnet/IP Interface Development Version
 Bepacom BACnet/IP interface for the Bepacom EcoPanel. Allows BACnet/IP devices to be available to Home Assistant through an API
-----------------------------------------------------------
 Add-on version: 1.6.0b1
 You are running the latest version of this add-on.
 System: Home Assistant OS 13.0  (amd64 / qemux86-64)
 Home Assistant Core: 2024.10.2
 Home Assistant Supervisor: 2024.10.3
-----------------------------------------------------------
 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-log-level: starting
s6-rc: info: service fix-attrs successfully started
s6-rc: info: service base-addon-log-level successfully started
s6-rc: info: service legacy-cont-init: starting
s6-rc: info: service legacy-cont-init successfully started
s6-rc: info: service init-nginx: starting
s6-rc: info: service init-interface: starting
[08:31:11] INFO: Running init-interface.
[08:31:11] INFO: Running init-nginx.
[08:31:11] INFO: Allowed addresses for NGINX: <IP_ADDRESS> <IP_ADDRESS> <IP_ADDRESS> <IP_ADDRESS>
[08:31:12] INFO: Generated ingress configuration successfully!
s6-rc: info: service init-nginx successfully started
[BACpypes]
objectName: D-BACS
address: <IP_ADDRESS>/24
objectIdentifier: 420
maxApduLengthAccepted: 1476
segmentation: segmentedBoth
vendorIdentifier: 15
foreignBBMD: -
foreignTTL: 255
maxSegmentsAccepted: 64
loglevel: INFO
defaultPriority: 15
s6-rc: info: service init-interface successfully started
s6-rc: info: service interface: starting
s6-rc: info: service interface successfully started
s6-rc: info: service nginx: starting
s6-rc: info: service nginx successfully started
s6-rc: info: service legacy-services: starting
[08:31:13] INFO: Running interface
s6-rc: info: service legacy-services successfully started
[08:31:20]|INFO     |server.py         ->_serve                              : Started server process [305]
[08:31:20]|INFO     |on.py             ->startup                             : Waiting for application startup.
[08:31:20]|INFO     |BACnetIOHandler.py->do_IAmRequest                       : I Am from device,0
[08:31:20]|INFO     |BACnetIOHandler.py->read_multiple_objects               : Reading objects from objectList of device,0...
[08:31:25]|INFO     |on.py             ->startup                             : Application startup complete.
[08:31:25]|INFO     |server.py         ->_log_started_message                : Uvicorn running on http://<IP_ADDRESS>:7813 (Press CTRL+C to quit)
[08:31:25] INFO: Running NGINX
[08:31:25]|WARNING  |h11_impl.py       ->handle_events                       : Invalid HTTP request received.
2024/10/26 08:31:25 [notice] 310#310: using the "epoll" event method
2024/10/26 08:31:25 [notice] 310#310: nginx/1.26.2
2024/10/26 08:31:25 [notice] 310#310: OS: Linux 6.6.44-haos
2024/10/26 08:31:25 [notice] 310#310: getrlimit(RLIMIT_NOFILE):<PHONE_NUMBER>:1073741816
2024/10/26 08:31:25 [notice] 310#310: start worker processes
2024/10/26 08:31:25 [notice] 310#310: start worker process 372
[08:31:28]|ERROR    |BACnetIOHandler.py->create_poll_task                    : Failed to create polling task device,0, all
[08:31:28]|WARNING  |BACnetIOHandler.py->create_poll_task                    : device,0 notification-class,3 failed to read: property: unknown-property
[08:31:28]|INFO     |BACnetIOHandler.py->create_poll_task                    : device,0 notification-class,3 won't get polled.
2024/10/26 08:32:09 [info] 372#372: *1 epoll_wait() reported that client prematurely closed connection, so upstream connection is closed too while sending request to upstream, client: <IP_ADDRESS>, server: , request: "GET /apiv1/json HTTP/1.1", upstream: "http://<IP_ADDRESS>:7813/apiv1/json", host: "<IP_ADDRESS>:8099"
2024/10/26 08:33:06 [info] 372#372: *3 epoll_wait() reported that client prematurely closed connection, so upstream connection is closed too while sending request to upstream, client: <IP_ADDRESS>, server: , request: "GET /apiv1/json HTTP/1.1", upstream: "http://<IP_ADDRESS>:7813/apiv1/json", host: "<IP_ADDRESS>:8099"
2024/10/26 08:33:41 [info] 372#372: *5 epoll_wait() reported that client prematurely closed connection, so upstream connection is closed too while sending request to upstream, client: <IP_ADDRESS>, server: , request: "GET /apiv1/json HTTP/1.1", upstream: "http://<IP_ADDRESS>:7813/apiv1/json", host: "<IP_ADDRESS>:8099"
2024/10/26 08:34:22 [info] 372#372: *7 epoll_wait() reported that client prematurely closed connection, so upstream connection is closed too while sending request to upstream, client: <IP_ADDRESS>, server: , request: "GET /apiv1/json HTTP/1.1", upstream: "http://<IP_ADDRESS>:7813/apiv1/json", host: "<IP_ADDRESS>:8099"
2024/10/26 08:35:12 [info] 372#372: *9 epoll_wait() reported that client prematurely closed connection, so upstream connection is closed too while sending request to upstream, client: <IP_ADDRESS>, server: , request: "GET /apiv1/json HTTP/1.1", upstream: "http://<IP_ADDRESS>:7813/apiv1/json", host: "<IP_ADDRESS>:8099"
2024/10/26 08:36:22 [info] 372#372: *11 epoll_wait() reported that client prematurely closed connection, so upstream connection is closed too while sending request to upstream, client: <IP_ADDRESS>, server: , request: "GET /apiv1/json HTTP/1.1", upstream: "http://<IP_ADDRESS>:7813/apiv1/json", host: "<IP_ADDRESS>:8099"

hi, same problem:
[15:12:18]|WARNING  |BACnetIOHandler.py->dict_updater                        : Ignoring property: device,18911, analog-value,61, min-pres-value... Inf value: -inf
[15:12:18]|WARNING  |BACnetIOHandler.py->dict_updater                        : Ignoring property: device,18911, analog-value,61, max-pres-value... Inf value: inf
[15:12:18]|WARNING  |BACnetIOHandler.py->dict_updater                        : Ignoring property: device,18911, analog-value,62, min-pres-value... Inf value: -inf
[15:12:18]|WARNING  |BACnetIOHandler.py->dict_updater                        : Ignoring property: device,18911, analog-value,62, max-pres-value... Inf value: inf
[15:12:18]|WARNING  |BACnetIOHandler.py->dict_updater                        : Ignoring property: device,18911, analog-value,63, min-pres-value... Inf value: -inf
[15:12:18]|WARNING  |BACnetIOHandler.py->dict_updater                        : Ignoring property: device,18911, analog-value,63, max-pres-value... Inf value: inf
[15:12:18]|WARNING  |BACnetIOHandler.py->dict_updater                        : Ignoring property: device,18911, analog-value,64, min-pres-value... Inf value: -inf
[15:12:18]|WARNING  |BACnetIOHandler.py->dict_updater                        : Ignoring property: device,18911, analog-value,64, max-pres-value... Inf value: inf
[15:12:18]|WARNING  |BACnetIOHandler.py->dict_updater                        : Ignoring property: device,18911, analog-value,65, min-pres-value... Inf value: -inf
[15:12:18]|WARNING  |BACnetIOHandler.py->dict_updater                        : Ignoring property: device,18911, analog-value,65, max-pres-value... Inf value: inf
[15:12:18]|WARNING  |BACnetIOHandler.py->dict_updater                        : Ignoring property: device,18911, analog-value,66, min-pres-value... Inf value: -inf
[15:12:18]|WARNING  |BACnetIOHandler.py->dict_updater                        : Ignoring property: device,18911, analog-value,66, max-pres-value... Inf value: inf
[15:12:18]|WARNING  |BACnetIOHandler.py->dict_updater                        : Ignoring property: device,18911, analog-value,67, min-pres-value... Inf value: -inf
[15:12:18]|WARNING  |BACnetIOHandler.py->dict_updater                        : Ignoring property: device,18911, analog-value,67, max-pres-value... Inf value: inf
[15:12:18]|WARNING  |BACnetIOHandler.py->dict_updater                        : Ignoring property: device,18911, analog-value,68, min-pres-value... Inf value: -inf
[15:12:18]|WARNING  |BACnetIOHandler.py->dict_updater                        : Ignoring property: device,18911, analog-value,68, max-pres-value... Inf value: inf
[15:12:18]|WARNING  |BACnetIOHandler.py->dict_updater                        : Ignoring property: device,18911, analog-value,69, min-pres-value... Inf value: -inf
[15:12:18]|WARNING  |BACnetIOHandler.py->dict_updater                        : Ignoring property: device,18911, analog-value,69, max-pres-value... Inf value: inf
[15:12:18]|WARNING  |BACnetIOHandler.py->dict_updater                        : Ignoring property: device,18911, analog-value,70, min-pres-value... Inf value: -inf
[15:12:18]|WARNING  |BACnetIOHandler.py->dict_updater                        : Ignoring property: device,18911, analog-value,70, max-pres-value... Inf value: inf
[15:12:18]|WARNING  |BACnetIOHandler.py->dict_updater                        : Ignoring property: device,18911, analog-value,71, min-pres-value... Inf value: -inf
[15:12:18]|WARNING  |BACnetIOHandler.py->dict_updater                        : Ignoring property: device,18911, analog-value,71, max-pres-value... Inf value: inf
[15:12:18]|WARNING  |BACnetIOHandler.py->dict_updater                        : Ignoring property: device,18911, analog-value,72, min-pres-value... Inf value: -inf
[15:12:18]|WARNING  |BACnetIOHandler.py->dict_updater                        : Ignoring property: device,18911, analog-value,72, max-pres-value... Inf value: inf
[15:12:18]|WARNING  |BACnetIOHandler.py->dict_updater                        : Ignoring property: device,18911, analog-value,73, min-pres-value... Inf value: -inf
[15:12:18]|WARNING  |BACnetIOHandler.py->dict_updater                        : Ignoring property: device,18911, analog-value,73, max-pres-value... Inf value: inf
[15:12:18]|WARNING  |BACnetIOHandler.py->dict_updater                        : Ignoring property: device,18911, analog-value,74, min-pres-value... Inf value: -inf
[15:12:18]|WARNING  |BACnetIOHandler.py->dict_updater                        : Ignoring property: device,18911, analog-value,74, max-pres-value... Inf value: inf
[15:12:18]|WARNING  |BACnetIOHandler.py->dict_updater                        : Ignoring property: device,18911, analog-value,75, min-pres-value... Inf value: -inf
[15:12:18]|WARNING  |BACnetIOHandler.py->dict_updater                        : Ignoring property: device,18911, analog-value,75, max-pres-value... Inf value: inf
[15:12:18]|WARNING  |BACnetIOHandler.py->dict_updater                        : Ignoring property: device,18911, analog-value,76, min-pres-value... Inf value: -inf
[15:12:18]|WARNING  |BACnetIOHandler.py->dict_updater                        : Ignoring property: device,18911, analog-value,76, max-pres-value... Inf value: inf
[15:12:18]|WARNING  |BACnetIOHandler.py->dict_updater                        : Ignoring property: device,18911, analog-value,77, min-pres-value... Inf value: -inf
[15:12:18]|WARNING  |BACnetIOHandler.py->dict_updater                        : Ignoring property: device,18911, analog-value,77, max-pres-value... Inf value: inf
[15:12:18]|WARNING  |BACnetIOHandler.py->dict_updater                        : Ignoring property: device,18911, analog-value,78, min-pres-value... Inf value: -inf
[15:12:18]|WARNING  |BACnetIOHandler.py->dict_updater                        : Ignoring property: device,18911, analog-value,78, max-pres-value... Inf value: inf
[15:12:18]|WARNING  |BACnetIOHandler.py->dict_updater                        : Ignoring property: device,18911, analog-value,79, min-pres-value... Inf value: -inf
[15:12:18]|WARNING  |BACnetIOHandler.py->dict_updater                        : Ignoring property: device,18911, analog-value,79, max-pres-value... Inf value: inf
[15:12:18]|WARNING  |BACnetIOHandler.py->dict_updater                        : Ignoring property: device,18911, analog-value,80, min-pres-value... Inf value: -inf
[15:12:18]|WARNING  |BACnetIOHandler.py->dict_updater                        : Ignoring property: device,18911, analog-value,80, max-pres-value... Inf value: inf
[15:12:18]|WARNING  |BACnetIOHandler.py->dict_updater
.....
[15:12:21] INFO: Running NGINX
2024/10/26 15:12:21 [notice] 313#313: using the "epoll" event method
2024/10/26 15:12:21 [notice] 313#313: nginx/1.26.2
2024/10/26 15:12:21 [notice] 313#313: OS: Linux 6.6.31-haos-raspi
2024/10/26 15:12:21 [notice] 313#313: getrlimit(RLIMIT_NOFILE):<PHONE_NUMBER>:1073741816
2024/10/26 15:12:21 [notice] 313#313: start worker processes
2024/10/26 15:12:21 [notice] 313#313: start worker process 362
[15:12:22]|WARNING  |BACnetIOHandler.py->create_poll_task                    : device,18911 network-port,1 failed to read: property: unknown-property
[15:12:24]|WARNING  |BACnetIOHandler.py->create_poll_task                    : device,18911 trend-log,100907 failed to read: property: unknown-property
[15:12:24]|WARNING  |BACnetIOHandler.py->create_poll_task                    : device,18911 trend-log,100908 failed to read: property: unknown-property
2024/10/26 15:12:58 [info] 362#362: *1 epoll_wait() reported that client prematurely closed connection, so upstream connection is closed too while sending request to upstream, client: <IP_ADDRESS>, server: , request: "GET /apiv1/json HTTP/1.1", upstream: "http://<IP_ADDRESS>:7813/apiv1/json", host: "<IP_ADDRESS>:8099"
2024/10/26 15:14:48 [info] 362#362: *3 epoll_wait() reported that client prematurely closed connection, so upstream connection is closed too while sending request to upstream, client: <IP_ADDRESS>, server: , request: "GET /apiv1/json HTTP/1.1", upstream: "http://<IP_ADDRESS>:7813/apiv1/json", host: "<IP_ADDRESS>:8099"
2024/10/26 15:16:39 [info] 362#362: *5 epoll_wait() reported that client prematurely closed connection, so upstream connection is closed too while sending request to upstream, client: <IP_ADDRESS>, server: , request: "GET /apiv1/json HTTP/1.1", upstream: "http://<IP_ADDRESS>:7813/apiv1/json", host: "<IP_ADDRESS>:8099"
2024/10/26 15:18:29 [info] 362#362: *7 epoll_wait() reported that client prematurely closed connection, so upstream connection is closed too while sending request to upstream, client: <IP_ADDRESS>, server: , request: "GET /apiv1/json HTTP/1.1", upstream: "http://<IP_ADDRESS>:7813/apiv1/json", host: "<IP_ADDRESS>:8099"
2024/10/26 15:20:19 [info] 362#362: *9 epoll_wait() reported that client prematurely closed connection, so upstream connection is closed too while sending request to upstream, client: <IP_ADDRESS>, server: , request: "GET /apiv1/json HTTP/1.1", upstream: "http://<IP_ADDRESS>:7813/apiv1/json", host: "<IP_ADDRESS>:8099"
2024/10/26 15:22:10 [info] 362#362: *11 epoll_wait() reported that client prematurely closed connection, so upstream connection is closed too while sending request to upstream, client: <IP_ADDRESS>, server: , request: "GET /apiv1/json HTTP/1.1", upstream: "http://<IP_ADDRESS>:7813/apiv1/json", host: "<IP_ADDRESS>:8099"
2024/10/26 15:24:00 [info] 362#362: *13 epoll_wait() reported that client prematurely closed connection, so upstream connection is closed too while sending request to upstream, client: <IP_ADDRESS>, server: , request: "GET /apiv1/json HTTP/1.1", upstream: "http://<IP_ADDRESS>:7813/apiv1/json", host: "<IP_ADDRESS>:8099"
2024/10/26 15:25:50 [info] 362#362: *15 epoll_wait() reported that client prematurely closed connection, so upstream connection is closed too while sending request to upstream, client: <IP_ADDRESS>, server: , request: "GET /apiv1/json HTTP/1.1", upstream: "http://<IP_ADDRESS>:7813/apiv1/json", host: "<IP_ADDRESS>:8099"
2024/10/26 15:27:40 [info] 362#362: *17 epoll_wait() reported that client prematurely closed connection, so upstream connection is closed too while sending request to upstream, client: <IP_ADDRESS>, server: , request: "GET /apiv1/json HTTP/1.1", upstream: "http://<IP_ADDRESS>:7813/apiv1/json", host: "<IP_ADDRESS>:8099"
2024/10/26 15:29:31 [info] 362#362: *19 epoll_wait() reported that client prematurely closed connection, so upstream connection is closed too while sending request to upstream, client: <IP_ADDRESS>, server: , request: "GET /apiv1/json HTTP/1.1", upstream: "http://<IP_ADDRESS>:7813/apiv1/json", host: "<IP_ADDRESS>:8099"
2024/10/26 15:31:21 [info] 362#362: *21 epoll_wait() reported that client prematurely closed connection, so upstream connection is closed too while sending request to upstream, client: <IP_ADDRESS>, server: , request: "GET /apiv1/json HTTP/1.1", upstream: "http://<IP_ADDRESS>:7813/apiv1/json", host: "<IP_ADDRESS>:8099"
2024/10/26 15:33:11 [info] 362#362: *23 epoll_wait() reported that client prematurely closed connection, so upstream connection is closed too while sending request to upstream, client: <IP_ADDRESS>, server: , request: "GET /apiv1/json HTTP/1.1", upstream: "http://<IP_ADDRESS>:7813/apiv1/json", host: "<IP_ADDRESS>:8099"
2024/10/26 15:35:02 [info] 362#362: *25 epoll_wait() reported that client prematurely closed connection, so upstream connection is closed too while sending request to upstream, client: <IP_ADDRESS>, server: , request: "GET /apiv1/json HTTP/1.1", upstream: "http://<IP_ADDRESS>:7813/apiv1/json", host: "<IP_ADDRESS>:8099"
2024/10/26 15:36:52 [info] 362#362: *27 epoll_wait() reported that client prematurely closed connection, so upstream connection is closed too while sending request to upstream, client: <IP_ADDRESS>, server: , request: "GET /apiv1/json HTTP/1.1", upstream: "http://<IP_ADDRESS>:7813/apiv1/json", host: "<IP_ADDRESS>:8099"
2024/10/26 15:38:42 [info] 362#362: *29 epoll_wait() reported that client prematurely closed connection, so upstream connection is closed too while sending request to upstream, client: <IP_ADDRESS>, server: , request: "GET /apiv1/json HTTP/1.1", upstream: "http://<IP_ADDRESS>:7813/apiv1/json", host: "<IP_ADDRESS>:8099"
2024/10/26 15:40:33 [info] 362#362: *31 epoll_wait() reported that client prematurely closed connection, so upstream connection is closed too while sending request to upstream, client: <IP_ADDRESS>, server: , request: "GET /apiv1/json HTTP/1.1", upstream: "http://<IP_ADDRESS>:7813/apiv1/json", host: "<IP_ADDRESS>:8099"
something wrong also in cpu usage:

If you run regular version v1.5.1, does the communication come back? If so, there might be some packages that don't play nice after the update. Please let me know if the stable version runs well.

I restored back to 1.5.1 and all seems to be working on again 💪

me too

Great, could you guys test to see if v1.6.0b2 also has this same issue?
I restored the old versions of all the updated packages in the hope that it's one of those that's causing the issue.

hi, with v1.6.0b2 values can be read but the cpu usage is the same than v1.6.0b1:

with the v1.5.1 the cpu usage is minimal:

the device setup is in both case the default:

deviceID: all
CoV_lifetime: 600
CoV_list:

all
quick_poll_rate: 5
quick_poll_list: []
slow_poll_rate: 600
slow_poll_list:
all
resub_on_iam: true
reread_on_iam: false

Here v1.6.0b2 log:
[23:35:33]|WARNING  |BACnetIOHandler.py->dict_updater                        : Ignoring property: device,18911, analog-value,51, min-pres-value... Inf value: -inf
[23:35:33]|WARNING  |BACnetIOHandler.py->dict_updater                        : Ignoring property: device,18911, analog-value,51, max-pres-value... Inf value: inf
[23:35:33]|WARNING  |BACnetIOHandler.py->dict_updater                        : Ignoring property: device,18911, analog-value,52, min-pres-value... Inf value: -inf
[23:35:33]|WARNING  |BACnetIOHandler.py->dict_updater                        : Ignoring property: device,18911, analog-value,52, max-pres-value... Inf value: inf
[23:35:33]|WARNING  |BACnetIOHandler.py->dict_updater                        : Ignoring property: device,18911, analog-value,53, min-pres-value... Inf value: -inf
[23:35:33]|WARNING  |BACnetIOHandler.py->dict_updater                        : Ignoring property: device,18911, analog-value,53, max-pres-value... Inf value: inf
[23:35:33]|WARNING  |BACnetIOHandler.py->dict_updater                        : Ignoring property: device,18911, analog-value,54, min-pres-value... Inf value: -inf
[23:35:33]|WARNING  |BACnetIOHandler.py->dict_updater                        : Ignoring property: device,18911, analog-value,54, max-pres-value... Inf value: inf
[23:35:34]|WARNING  |BACnetIOHandler.py->dict_updater                        : Ignoring property: device,18911, analog-value,55, min-pres-value... Inf value: -inf
[23:35:34]|WARNING  |BACnetIOHandler.py->dict_updater                        : Ignoring property: device,18911, analog-value,55, max-pres-value... Inf value: inf
[23:35:34]|WARNING  |BACnetIOHandler.py->dict_updater                        : Ignoring property: device,18911, analog-value,56, min-pres-value... Inf value: -inf
[23:35:34]|WARNING  |BACnetIOHandler.py->dict_updater                        : Ignoring property: device,18911, analog-value,56, max-pres-value... Inf value: inf
[23:35:34]|WARNING  |BACnetIOHandler.py->dict_updater                        : Ignoring property: device,18911, analog-value,57, min-pres-value... Inf value: -inf
[23:35:34]|WARNING  |BACnetIOHandler.py->dict_updater                        : Ignoring property: device,18911, analog-value,57, max-pres-value... Inf value: inf
[23:35:34]|WARNING  |BACnetIOHandler.py->dict_updater                        : Ignoring property: device,18911, analog-value,58, min-pres-value... Inf value: -inf
[23:35:34]|WARNING  |BACnetIOHandler.py->dict_updater                        : Ignoring property: device,18911, analog-value,58, max-pres-value... Inf value: inf
[23:35:34]|WARNING  |BACnetIOHandler.py->dict_updater                        : Ignoring property: device,18911, analog-value,59, min-pres-value... Inf value: -inf
[23:35:34]|WARNING  |BACnetIOHandler.py->dict_updater                        : Ignoring property: device,18911, analog-value,59, max-pres-value... Inf value: inf
[23:35:34]|WARNING  |BACnetIOHandler.py->dict_updater                        : Ignoring property: device,18911, analog-value,60, min-pres-value... Inf value: -inf
[23:35:34]|WARNING  |BACnetIOHandler.py->dict_updater                        : Ignoring property: device,18911, analog-value,60, max-pres-value... Inf value: inf
[23:35:34]|WARNING  |BACnetIOHandler.py->dict_updater                        : Ignoring property: device,18911, analog-value,61, min-pres-value... Inf value: -inf
[23:35:34]|WARNING  |BACnetIOHandler.py->dict_updater                        : Ignoring property: device,18911, analog-value,61, max-pres-value... Inf value: inf
[23:35:34]|WARNING  |BACnetIOHandler.py->dict_updater                        : Ignoring property: device,18911, analog-value,62, min-pres-value... Inf value: -inf
[23:35:34]|WARNING  |BACnetIOHandler.py->dict_updater                        : Ignoring property: device,18911, analog-value,62, max-pres-value... Inf value: inf
[23:35:34]|WARNING  |BACnetIOHandler.py->dict_updater                        : Ignoring property: device,18911, analog-value,63, min-pres-value... Inf value: -inf
[23:35:34]|WARNING  |BACnetIOHandler.py->dict_updater                        : Ignoring property: device,18911, analog-value,63, max-pres-value... Inf value: inf
[23:35:34]|WARNING  |BACnetIOHandler.py->dict_updater                        : Ignoring property: device,18911, analog-value,64, min-pres-value... Inf value: -inf
[23:35:34]|WARNING  |BACnetIOHandler.py->dict_updater                        : Ignoring property: device,18911, analog-value,64, max-pres-value... Inf value: inf
[23:35:34]|WARNING  |BACnetIOHandler.py->dict_updater                        : Ignoring property: device,18911, analog-value,65, min-pres-value... Inf value: -inf
[23:35:34]|WARNING  |BACnetIOHandler.py->dict_updater                        : Ignoring property: device,18911, analog-value,65, max-pres-value... Inf value: inf
[23:35:34]|WARNING  |BACnetIOHandler.py->dict_updater                        : Ignoring property: device,18911, analog-value,66, min-pres-value... Inf value: -inf
[23:35:34]|WARNING  |BACnetIOHandler.py->dict_updater                        : Ignoring property: device,18911, analog-value,66, max-pres-value... Inf value: inf
[23:35:34]|WARNING  |BACnetIOHandler.py->dict_updater                        : Ignoring property: device,18911, analog-value,67, min-pres-value... Inf value: -inf
[23:35:34]|WARNING  |BACnetIOHandler.py->dict_updater                        : Ignoring property: device,18911, analog-value,67, max-pres-value... Inf value: inf
[23:35:34]|WARNING  |BACnetIOHandler.py->dict_updater                        : Ignoring property: device,18911, analog-value,68, min-pres-value... Inf value: -inf
[23:35:34]|WARNING  |BACnetIOHandler.py->dict_updater                        : Ignoring property: device,18911, analog-value,68, max-pres-value... Inf value: inf
[23:35:34]|WARNING  |BACnetIOHandler.py->dict_updater                        : Ignoring property: device,18911, analog-value,69, min-pres-value... Inf value: -inf
[23:35:34]|WARNING  |BACnetIOHandler.py->dict_updater                        : Ignoring property: device,18911, analog-value,69, max-pres-value... Inf value: inf
[23:35:34]|WARNING  |BACnetIOHandler.py->dict_updater                        : Ignoring property: device,18911, analog-value,70, min-pres-value... Inf value: -inf
[23:35:34]|WARNING  |BACnetIOHandler.py->dict_updater                        : Ignoring property: device,18911, analog-value,70, max-pres-value... Inf value: inf
[23:35:34]|WARNING  |BACnetIOHandler.py->dict_updater                        : Ignoring property: device,18911, analog-value,71, min-pres-value... Inf value: -inf
[23:35:34]|WARNING  |BACnetIOHandler.py->dict_updater                        : Ignoring property: device,18911, analog-value,71, max-pres-value... Inf value: inf
[23:35:34]|WARNING  |BACnetIOHandler.py->dict_updater                        : Ignoring property: device,18911, analog-value,72, min-pres-value... Inf value: -inf
[23:35:34]|WARNING  |BACnetIOHandler.py->dict_updater                        : Ignoring property: device,18911, analog-value,72, max-pres-value... Inf value: inf
[23:35:34]|WARNING  |BACnetIOHandler.py->dict_updater                        : Ignoring property: device,18911, analog-value,73, min-pres-value... Inf value: -inf
[23:35:34]|WARNING  |BACnetIOHandler.py->dict_updater                        : Ignoring property: device,18911, analog-value,73, max-pres-value... Inf value: inf
[23:35:34]|WARNING  |BACnetIOHandler.py->dict_updater                        : Ignoring property: device,18911, analog-value,74, min-pres-value... Inf value: -inf
[23:35:34]|WARNING  |BACnetIOHandler.py->dict_updater                        : Ignoring property: device,18911, analog-value,74, max-pres-value... Inf value: inf
[23:35:34]|WARNING  |BACnetIOHandler.py->dict_updater                        : Ignoring property: device,18911, analog-value,75, min-pres-value... Inf value: -inf
[23:35:34]|WARNING  |BACnetIOHandler.py->dict_updater                        : Ignoring property: device,18911, analog-value,75, max-pres-value... Inf value: inf
[23:35:34]|WARNING  |BACnetIOHandler.py->dict_updater                        : Ignoring property: device,18911, analog-value,76, min-pres-value... Inf value: -inf
[23:35:34]|WARNING  |BACnetIOHandler.py->dict_updater                        : Ignoring property: device,18911, analog-value,76, max-pres-value... Inf value: inf
[23:35:34]|WARNING  |BACnetIOHandler.py->dict_updater                        : Ignoring property: device,18911, analog-value,77, min-pres-value... Inf value: -inf
[23:35:34]|WARNING  |BACnetIOHandler.py->dict_updater                        : Ignoring property: device,18911, analog-value,77, max-pres-value... Inf value: inf
[23:35:34]|WARNING  |BACnetIOHandler.py->dict_updater                        : Ignoring property: device,18911, analog-value,78, min-pres-value... Inf value: -inf
[23:35:34]|WARNING  |BACnetIOHandler.py->dict_updater                        : Ignoring property: device,18911, analog-value,78, max-pres-value... Inf value: inf
[23:35:34]|WARNING  |BACnetIOHandler.py->dict_updater                        : Ignoring property: device,18911, analog-value,79, min-pres-value... Inf value: -inf
[23:35:34]|WARNING  |BACnetIOHandler.py->dict_updater                        : Ignoring property: device,18911, analog-value,79, max-pres-value... Inf value: inf
[23:35:34]|WARNING  |BACnetIOHandler.py->dict_updater                        : Ignoring property: device,18911, analog-value,80, min-pres-value... Inf value: -inf
[23:35:34]|WARNING  |BACnetIOHandler.py->dict_updater                        : Ignoring property: device,18911, analog-value,80, max-pres-value... Inf value: inf
[23:35:34]|WARNING  |BACnetIOHandler.py->dict_updater                        : Ignoring property: device,18911, analog-value,81, min-pres-value... Inf value: -inf
[23:35:34]|WARNING  |BACnetIOHandler.py->dict_updater                        : Ignoring property: device,18911, analog-value,81, max-pres-value... Inf value: inf
[23:35:34]|WARNING  |BACnetIOHandler.py->dict_updater                        : Ignoring property: device,18911, analog-value,82, min-pres-value... Inf value: -inf
[23:35:34]|WARNING  |BACnetIOHandler.py->dict_updater                        : Ignoring property: device,18911, analog-value,82, max-pres-value... Inf value: inf
[23:35:34]|WARNING  |BACnetIOHandler.py->dict_updater                        : Ignoring property: device,18911, analog-value,83, min-pres-value... Inf value: -inf
[23:35:34]|WARNING  |BACnetIOHandler.py->dict_updater                        : Ignoring property: device,18911, analog-value,83, max-pres-value... Inf value: inf
[23:35:34]|WARNING  |BACnetIOHandler.py->dict_updater                        : Ignoring property: device,18911, analog-value,84, min-pres-value... Inf value: -inf
[23:35:34]|WARNING  |BACnetIOHandler.py->dict_updater                        : Ignoring property: device,18911, analog-value,84, max-pres-value... Inf value: inf
[23:35:34]|WARNING  |BACnetIOHandler.py->dict_updater                        : Ignoring property: device,18911, analog-value,85, min-pres-value... Inf value: -inf
[23:35:34]|WARNING  |BACnetIOHandler.py->dict_updater                        : Ignoring property: device,18911, analog-value,85, max-pres-value... Inf value: inf
[23:35:34]|WARNING  |BACnetIOHandler.py->dict_updater                        : Ignoring property: device,18911, analog-value,86, min-pres-value... Inf value: -inf
[23:35:34]|WARNING  |BACnetIOHandler.py->dict_updater                        : Ignoring property: device,18911, analog-value,86, max-pres-value... Inf value: inf
[23:35:34]|WARNING  |BACnetIOHandler.py->dict_updater                        : Ignoring property: device,18911, analog-value,87, min-pres-value... Inf value: -inf
[23:35:34]|WARNING  |BACnetIOHandler.py->dict_updater                        : Ignoring property: device,18911, analog-value,87, max-pres-value... Inf value: inf
[23:35:34]|WARNING  |BACnetIOHandler.py->dict_updater                        : Ignoring property: device,18911, analog-value,88, min-pres-value... Inf value: -inf
[23:35:34]|WARNING  |BACnetIOHandler.py->dict_updater                        : Ignoring property: device,18911, analog-value,88, max-pres-value... Inf value: inf
[23:35:34]|WARNING  |BACnetIOHandler.py->dict_updater                        : Ignoring property: device,18911, analog-value,89, min-pres-value... Inf value: -inf
[23:35:34]|WARNING  |BACnetIOHandler.py->dict_updater                        : Ignoring property: device,18911, analog-value,89, max-pres-value... Inf value: inf
[23:35:34]|WARNING  |BACnetIOHandler.py->dict_updater                        : Ignoring property: device,18911, analog-value,90, min-pres-value... Inf value: -inf
[23:35:34]|WARNING  |BACnetIOHandler.py->dict_updater                        : Ignoring property: device,18911, analog-value,90, max-pres-value... Inf value: inf
[23:35:34]|WARNING  |BACnetIOHandler.py->dict_updater                        : Ignoring property: device,18911, analog-value,91, min-pres-value... Inf value: -inf
[23:35:34]|WARNING  |BACnetIOHandler.py->dict_updater                        : Ignoring property: device,18911, analog-value,91, max-pres-value... Inf value: inf
[23:35:34]|WARNING  |BACnetIOHandler.py->dict_updater                        : Ignoring property: device,18911, analog-value,92, min-pres-value... Inf value: -inf
[23:35:34]|WARNING  |BACnetIOHandler.py->dict_updater                        : Ignoring property: device,18911, analog-value,92, max-pres-value... Inf value: inf
[23:35:34]|WARNING  |BACnetIOHandler.py->dict_updater                        : Ignoring property: device,18911, analog-value,93, min-pres-value... Inf value: -inf
[23:35:34]|WARNING  |BACnetIOHandler.py->dict_updater                        : Ignoring property: device,18911, analog-value,93, max-pres-value... Inf value: inf
[23:35:34]|WARNING  |BACnetIOHandler.py->dict_updater                        : Ignoring property: device,18911, analog-value,94, min-pres-value... Inf value: -inf
[23:35:34]|WARNING  |BACnetIOHandler.py->dict_updater                        : Ignoring property: device,18911, analog-value,94, max-pres-value... Inf value: inf
[23:35:36] INFO: Running NGINX
[23:35:36]|WARNING  |h11_impl.py       ->handle_events                       : Invalid HTTP request received.
2024/10/26 23:35:36 [notice] 313#313: using the "epoll" event method
2024/10/26 23:35:36 [notice] 313#313: nginx/1.26.2
2024/10/26 23:35:36 [notice] 313#313: OS: Linux 6.6.31-haos-raspi
2024/10/26 23:35:36 [notice] 313#313: getrlimit(RLIMIT_NOFILE):<PHONE_NUMBER>:1073741816
2024/10/26 23:35:36 [notice] 313#313: start worker processes
2024/10/26 23:35:36 [notice] 313#313: start worker process 362
[23:35:38]|WARNING  |BACnetIOHandler.py->create_poll_task                    : device,18911 network-port,1 failed to read: property: unknown-property
[23:35:40]|WARNING  |BACnetIOHandler.py->create_poll_task                    : device,18911 trend-log,100907 failed to read: property: unknown-property
[23:35:40]|WARNING  |BACnetIOHandler.py->create_poll_task                    : device,18911 trend-log,100908 failed to read: property: unknown-property
2024/10/26 23:36:32 [info] 362#362: *1 epoll_wait() reported that client prematurely closed connection, so upstream connection is closed too while sending request to upstream, client: <IP_ADDRESS>, server: , request: "GET /apiv1/json HTTP/1.1", upstream: "http://<IP_ADDRESS>:7813/apiv1/json", host: "<IP_ADDRESS>:8099"


Fix the incorrect measurement with InprocessBenchmark.

Description
The existing code was sending messages not to the EchoActor but the PingActor itself after the first batch. This change makes the benchmark seem a lot worse in terms of performance, but it is a lot more realistic than an actor sending messages to itself only. However, I believe this benchmark could be improved a little bit to yield more messages/sec; by changing the batching idea a bit so that there would be 2 batches in progress at any given time, not just one.
Purpose
This pull request is a:

[X] Bugfix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)

Checklist

[X] I have added tests that prove my fix is effective or that my feature works
[X] I have added necessary documentation (if appropriate)

You are correct! many thanks for spotting this


FromHeader and FromParams panic on nil request

Pull Request Report
Description
I've added nil checks to both FromHeader and FromParams functions for the http.Request argument.
Discovered during internal testing that if the request object is nil it causes a panic.
As a result of the check I created a new error value to be returned - ErrNilRequest that returns if the checks fail.
Type of change

[x] Bug fix (fix to an issue)
[ ] New feature (changes to functionality)
[ ] Big change (fix or feature that would cause existing functionality to work as expected)

Testing
I've added tests to confirm this fix but you can remove the nil checks and run the tests to see trigger the panic.
Test Configuration

Framework version:
Language version: 1.11.4
Browser version:

Additional info

[x] I have performed a self-review of my own code
[ ] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation
[ ] My changes generate no new warnings and errors
[x] I have added tests that prove my fix is effective or that my feature works
[x] New and existing unit tests pass locally with my changes

Coverage increased (+0.1%) to 95.154% when pulling d6893cc3bf003cf1ddeeb600a536f3938c78982d on dgparker:validate-nilRequest-fix into 1ef6062669aac7d00fe03069d5fb37a7eff1bde1 on auth0-community:master.

Thanks a lot for that contribution @dgparker !


Handled DLS/FLS/Field masking for Cross cluster replication

opensearch-security pull request intake form
Please provide as much details as possible to get feedback/acceptance on your PR quickly

Category: (Enhancement, New feature, Bug fix, Test fix, Refactoring, Maintenance, Documentation)

Github Issue # or road-map entry, if available:

Description of changes:

Why these changes are required?

What is the old behavior before changes and new behavior after changes? (Please add any example/logs/screen-shot if available)

Testing done: (Please provide details of testing done: Unit testing, integration testing and manual testing)

TO-DOs, if any: (Please describe pending items and provide Github issues# for each of them)

Is it backport from main branch? (If yes, please add backport PR # and commits #)

By making a contribution to this project, I certify that:
(a) The contribution was created in whole or in part by me and I
have the right to submit it under the open source license
indicated in the file; or
(b) The contribution is based upon previous work that, to the best
of my knowledge, is covered under an appropriate open source
license and I have the right under that license to submit that
work with modifications, whether created in whole or in part
by me, under the same open source license (unless I am
permitted to submit under a different license), as indicated
in the file; or
(c) The contribution was provided directly to me by some other
person who certified (a), (b) or (c) and I have not modified
it.
(d) I understand and agree that this project and the contribution
are public and that a record of the contribution (including all
personal information I submit with it, including my sign-off) is
maintained indefinitely and may be redistributed consistent with
this project or the open source license(s) involved.
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

Codecov Report

Merging #1334 (d5e22d0) into main (2e21d59) will decrease coverage by 45.02%.
The diff coverage is 75.00%.

@@              Coverage Diff              @@
##               main    #1334       +/-   ##
=============================================
- Coverage     64.74%   19.71%   -45.03%
+ Complexity     3194      808     -2386
=============================================
  Files           247      247
  Lines         17230    17235        +5
  Branches       3045     3047        +2
=============================================
- Hits          11155     3398     -7757
- Misses         4526    13167     +8641
+ Partials       1549      670      -879

Impacted Files
Coverage Δ

...rch/security/configuration/DlsFlsRequestValve.java
0.00% <ø> (ø)

...search/security/configuration/DlsFlsValveImpl.java
6.87% <66.66%> (-61.88%)
:arrow_down:

...org/opensearch/security/filter/SecurityFilter.java
35.26% <100.00%> (-42.78%)
:arrow_down:

...org/opensearch/security/ssl/util/CertFromFile.java
0.00% <0.00%> (-100.00%)
:arrow_down:

...rg/opensearch/security/ssl/util/CertFileProps.java
0.00% <0.00%> (-100.00%)
:arrow_down:

...ensearch/security/action/whoami/WhoAmIRequest.java
0.00% <0.00%> (-100.00%)
:arrow_down:

...rch/security/http/SecurityHttpServerTransport.java
0.00% <0.00%> (-100.00%)
:arrow_down:

...rch/security/ssl/transport/DualModeSSLHandler.java
0.00% <0.00%> (-100.00%)
:arrow_down:

...h/security/dlic/rest/validation/NoOpValidator.java
0.00% <0.00%> (-100.00%)
:arrow_down:

...ecurity/auth/limiting/AddressBasedRateLimiter.java
0.00% <0.00%> (-100.00%)
:arrow_down:

... and 195 more

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 2e21d59...d5e22d0. Read the comment docs.


Verbose mode

It would be great to have a verbose mode that shows if aria2 is being used or not. I don't see that large of a performance difference after installing it. So I'm curious if it is indeed using aria2 or if there is something wrong on my end.

I'm going to close this one as we currently show a "Downloading with urlSession - for faster downloads install aria2 (brew install aria2``  if you aren't using aria2


Define the API that TIKI will use to communicate between Rewards app and the backend services

duplicate tiki/apps#32


Error when nvim-treesitter is added as opt package in packer

Hi, thanks for the awesome plugin. Neovim shows an error when nvim-treesitter is made an optional package in packer.nvim.
Here's the error message

Relevant Packer config

Treesitter config
vim.cmd[[packadd nvim-treesitter]]

local ts_config = require('nvim-treesitter.configs')

ts_config.setup({
  -- ensure_installed = 'maintained',
  highlight = { enable = true },
  incremental_selection = { enable = true },
  indent = { enable = true },

  context_commentstring = { enable = true },

})

Hey @hiddenruins! Unfortunately, I don't know too much about opt packages. Is it correct that the only difference is that you need to packadd mypackage for it to be registered/started?
Would it make sense to make nvim-ts-context-commenstring a dependency of nvim-treesitter?
use {
  'nvim-treesitter/nvim-treesitter',
  opt = true,
  run = ':TSUpdate',
  requires = {'JoosepAlviste/nvim-ts-context-commentstring'},
}

Then, Packer should make this plugin opt as well if I understand correctly (transitive_opt = true, -- Make dependencies of opt plugins also opt by default in Packer default conf) and load it when nvim-treesitter is loaded. Does that work for you?
I'm not sure what could be done in this plugin. Do you have any ideas?

I think what you want is wants to make sure nvim-treesitter is loaded before ntcc (your plugin's name is too long :P):
use {
'JoosepAlviste/nvim-ts-context-commentstring, cmd = '...',
wants = 'nvim-treesitter'
}

(Presumably you want to lazy-load this plugin (which implies opt, so no need to specify it), otherwise there is no point in putting this -- and nvim-treesitter, which is a hard requirement -- in opt instead of start.)

Thank you @clason @JoosepAlviste . Adding after="nvim-treesitter" in use seemed to do the trick.


Flickering LED when pixel is too dark.

request stuff here!
Saturation calculation is a bit janky atm. Saturation takes a RGB value and if saturation is 0 or the brightest RGB value is 0, then it returns the pixel as pitch black. This is probably what's causing it.
// ...
if max != 0.0 {
    saturation = delta / max;
} else {
    return RGB(0, 0, 0)
}

// ...
if saturation == 0.0 {
    return RGB(0, 0, 0)
}

This issue is no longer open as it has been fixed in c86410e


Forbid propTypes/defaultProps entirely

I have a use-case where I need to forbid propTypes/defaultProps entirely, on certain files.
Forbidding proptypes entirely can be done in a bit of a hacky way:
"react/forbid-prop-types": [ "error", { "forbid": [
  "any", "array", "bool", "func", "number",
  "object", "string", "node", "element", "symbol",
  "elementType", "instanceOf", "oneOf", "oneOfType",
  "arrayOf", "objectOf", "shape", "exact"
] } ]

Basically forbidding every known propType type. However, this doesn't forbid the presence of propTypes alltogether. It also gives a misleading message when it is encountered as an linting error.
There also doesn't seem to be a way to forbid defaultProps entirely. Am I missing something?

What is this use case?

We have several components that are named after a certain pattern, in our case their names end in Section. These are meant to be used by Sitecore JSS. These "section" components are nothing but proxies of another component. The props to these components are passed in by JSS in a single prop called fields.
We don't want any propTypes there, because it would mean doubling them up. The proxied component are already enriched with propTypes, so any checking is done there. It would also mean we'd have to do some trickery to avoid having to redefine all those props in a fields shape.
In short, these "section" components do not need propTypes. They are completely useless.
And the same would go for the corresponding defaultProps.

In my experience with these kind of components, it's very valuable to hoist the propTypes from the wrapped component onto the wrapper component, so that they do trigger propType warnings, even when shallow rendered.
There's even a package for doing it easily: https://www.npmjs.com/package/hoist-non-react-statics

I would guess that even with that package, it would become even less useful to not write explicit propTypes in those proxy components. But eslint would still warn about them not being there.

Sure, but in the rare cases where you're doing this, you can use an eslint override comment.

They are not rare. It's one kind of file, but there are many of them.

You could also name them with a convention, and use eslint's "overrides" with a glob to impose the no-restricted-syntax rule and configure it to block any assignment to .propTypes.

Didn't know about that one. Thanks. I'll check it out.


How to evaluate wav2vec2 model without language model?

What is your question?
I have finetuned a wav2vec2 model and in the file log the validation wer and wer-raw are present and it gives consistent numbers. I have not installed flashlight python bindings and I think that the wer is calculated without language model. Is this true or is it not working properly? Now I am not able to install flashlight, so how to evaluate the finetuned model without a lnaguage model and produce similar numbers to the ones that appear during the finetunig?
This is an example of the finetuning file log output:
[2021-03-24 11:54:34,370][fairseq_cli.train][INFO] - begin validation on "dev_other" subset
[2021-03-24 11:54:43,717][dev_other][INFO] - {"epoch": 81, "dev_other_loss": "10.401", "dev_other_ntokens": "1244.28", "dev_other_nsentences": "6.88372", "dev_other_nll_loss": "0.058", "dev_other_uer": "1.088", "dev_other_wer": "3.966", "dev_other_raw_wer": "3.966", "dev_other_wps": "6007.8", "dev_other_wpb": "1244.3", "dev_other_bsz": "6.9", "dev_other_num_updates": "80000", "dev_other_best_wer": "3.856"}

@alexeib

use "viterbi" decoder - but for this you still need to install flashlight
or you can copy the code from ctc.py that does argmax decoding and adapt something like infer.py to use that instead of flashlight decoders

use "viterbi" decoder - but for this you still need to install flashlight
or you can copy the code from ctc.py that does argmax decoding and adapt something like infer.py to use that instead of flashlight decoders

Same question here: with the default setup from Readme, how is the "dev_other_wer" calculated without flashlight in the log? Thanks.

"raw_wer" is computed with some simple code - this is the same as viterbi decoding, i just didnt get around to implementing it without depending on flashlight
"wer" is the same as "raw_wer" unless you provide ngram lm in the config, in which case it will in fact use flashlight decoder

@alexeib quick question: apart from "wer" and "raw_wer", what does "best_wer" mean here?
[2022-01-18 05:41:02,006][fairseq_cli.train][INFO] - begin validation on "test" subset[2022-01-18 05:43:26,995][test][INFO] -
 {"epoch": 150, "test_loss": "24.118", "test_ntokens": "674.778", "test_nsentences": "13.3364",
  "test_nll_loss": "0.477", "test_uer": "7.599", "test_wer": "22.706", "test_raw_wer": "22.706",
  "test_wps": "1999.9", "test_wpb": "674.8", "test_bsz": "13.3", "test_num_updates": "20000",
  "test_best_wer": "14.46"}

I haven't installed any language model in my setup nor flashlight itself. Must be some oracle WER?


Is this plugin outdated?

I found the official document for GraphCMS 2.0. According to that, it seems only need the official plugin named gatsby-source-graphql.
Is this plugin outdated? Or what difference between the official plugin and this?

It looks like gatsby-source-graphql will be the way to go. As far as I understand, the intention is to make it compatible to any GraphQL API provider by stitching their schema to Gatsby's, as opposed to having each provider developing their own. But... I might be wrong

Thank you for the answer!
I replaced gatsby-source-graphql from this plugin. And I haven't any problem for now.
Please tell me if you find any issues using gatsby-source-graphql .

Yeah, that's about right!
I haven't had much time to respond to these, sorry! gatsby-source-graphql is the way to go. This was written in the time before, when gatsby source plugins were the wild west 😉

I got it! Thank you!


feat(pixels): add my new pixel

Checklist

[x] I ran npm test locally and it passed without errors.

[x] I only edited the _data/pixels.json file.

[x] I entered the username in the pixels.json that I'm also using to create this pull request.
[x] I acknowledge that all my contributions will be made under the project's license.

hello I want to be a collaborator I am new


fix(when-document-visible): export the whenDocumentVisible operator…

… from the ngxtension/when-document-visible entry point
fixes #424

@nartc I've found why the build keeps failing (at least for me)... the CI pipeline requested to install pnpm v8 when the lockfile version was for pnpm v9 (as requested by the packageManager field in package.json).
I've update the ci.yml file to not request a specific version of pnpm. So it will install the one requested by packageManager in package.json

@all-contributors please add @FabienDehopre for code

Thanks @FabienDehopre


这是我见过最没用的文档和代码示例

+1

+10086 代码示例不知道写了个啥

that examples are all no-friendly!!!!!  no code,no description! :anger:

You might want to checkout code here: https://github.com/clauderic/dnd-kit/tree/master/stories


Does not process jaxb element properly

Below is the rest service method. InternalReq was generated from xsd by JAXB
    @POST
    @Path("/iternal")
    public String getInternalThing(InternalReq req) {
        return getInteral(req);
    }

see the xsd document:
<xs:element name="InternalReq">
		<xs:complexType>
			<xs:sequence>
				<xs:element maxOccurs="1" minOccurs="1" ref="tns:Id" />
				<xs:element maxOccurs="1" minOccurs="0" ref="tns:InternalName" />
				<xs:element maxOccurs="1" minOccurs="0" ref="tns:Description" />
			</xs:sequence>
		</xs:complexType>
	</xs:element>

the InternalReq class generated by JAXB
@XmlAccessorType(XmlAccessType.FIELD)
@XmlType(name = "", propOrder = {
    "id",
    "internalName",
    "description"
})
@XmlRootElement(name = "InternalReq")
public class InternalReq
    implements Serializable
{

    @XmlElement(name = "Id", required = true)
    protected String id;
    @XmlElement(name = "InternalName")
    protected String internalName;
    @XmlElement(name = "Description")
    protected String description;
..
}

The actual swagger document is generated as following:
"InternalReqType" : {
      "type" : "object",
      "required" : [ "id" ],
      "properties" : {
        "id" : {
          "type" : "string",
          "xml" : {
            "name" : "Id"
          }
        },
        "internalName" : {
          "type" : "string",
          "xml" : {
            "name" : "InternalName"
          }
        },
        "description" : {
          "type" : "string",
          "xml" : {
            "name" : "Description"
          }
        },
}

which I am expecting
The properties name should match to the name @XmlElement(name = "Id")
"InternalReqType" : {
      "type" : "object",
      "required" : [ "Id" ],
      "properties" : {
        "Id" : {
          "type" : "string",
          "xml" : {
            "name" : "Id"
          }
        },
        "InternalName" : {
          "type" : "string",
          "xml" : {
            "name" : "InternalName"
          }
        },
        "Description" : {
          "type" : "string",
          "xml" : {
            "name" : "Description"
          }
        },
}

I was told that swagger isusing jackson as the  default annotation processor and jaxb does not default supported, so can this plug-in support to specify the annotation processor?

I'm having the same issue. Have a look at this:
https://github.com/swagger-api/swagger-core/issues/960
Apparently, one can work around this with registering the jaxb annotation module like that:
Json.mapper().registerModule(new JaxbAnnotationModule());
Yaml.mapper().registerModule(new JaxbAnnotationModule());
I still haven't managed to get this to work in my forked repo but as soon as I realize how to fix it I will provide a pull request.

I am wandering if it is possible that we add a new configuration element to support jaxb :
like below adding a new the element  in the box, when system is setup the ObjectMapper then check if useJAXBAnnotationProcessor element is configured as true, if yes, then execute this two lines code:
Json.mapper().registerModule(new JaxbAnnotationModule());
Yaml.mapper().registerModule(new JaxbAnnotationModule());
otherwise just do the thing as what it is doing currently- default to use jackson as the processor.
<plugin>
    <groupId>com.github.kongchen</groupId>
    <artifactId>swagger-maven-plugin</artifactId>
    <version>3.0.0</version>
    <configuration>
-----------------------------------------------------------------------
| <useJAXBAnnotationProcessor>true</useJAXBAnnotationProcessor>|
-----------------------------------------------------------------------
        <apiSources>
            <apiSource>
                <springmvc>true</springmvc>
                <locations>com.wordnik.swagger.sample</locations>
                <schemes>http,https</schemes>
                <host>www.example.com:8080</host>
                <basePath>/api</basePath>
                <info>
                    <title>Swagger Maven Plugin Sample</title>
                    <version>v1</version>
                    <description>
                        This is a sample.
                    </description>
                    <termsOfService>
                        http://www.github.com/kongchen/swagger-maven-plugin
                    </termsOfService>
                    <contact>
<EMAIL_ADDRESS>                        <name>Kong Chen</name>
                        <url>http://kongch.com</url>
                    </contact>
                    <license>
                        <url>http://www.apache.org/licenses/LICENSE-2.0.html</url>
                        <name>Apache 2.0</name>
                    </license>
                </info>
            </apiSource>
        </apiSources>
    </configuration>
    <executions>
        <execution>
            <phase>compile</phase>
            <goals>
                <goal>generate</goal>
            </goals>
        </execution>
    </executions>
</plugin>

@mdzhigarov Thanks for the PR!
@Jerrrrrrry Please pull source from master and test the PR by adding this to your ApiSource node:
<useJAXBAnnotationProcessor>true</useJAXBAnnotationProcessor>

It works fine. great job guys


NameError (uninitialized constant) for a Namespace model

Hi,
I have a model like this.
class Classifieds::Category < ActiveRecord::Base
  belongs_to :parent , :class_name=>"Classifieds::Category", :foreign_key=>'parent_id'
end

and a active_admin file like this
ActiveAdmin.register Classifieds::Category do
  menu :label=>'Classifieds Categories'
end

it is generating this error
NameError (uninitialized constant Classifieds::Category):
  app/admin/classifieds_categories.rb:1:in `<top (required)>'
  config/routes.rb:5:in `block in <top (required)>'
  config/routes.rb:1:in `<top (required)>'

  Rendered<EMAIL_ADDRESS>(2.9ms)
  Rendered<EMAIL_ADDRESS>(1.4ms)
  Rendered<EMAIL_ADDRESS>within rescues/layout (13.6ms)
```

How can we fix this. I had tested it in console it is working fine.

Can you try to register your model as ::Classifieds::Category and see if you get the same error?

Great! It works. Thanks a lot.

I just restarted my system and it occurs again. Tried every possible solution but can't find it.

it was a major mistake. Some how during auto refactoring the file for ::Classifieds::Category has been named to categories.rb which was causing issue to load it. Renamed it back to category.rb and every things works well now.


Change Structure

Change the structure to match the one of QuantShapeCol-001

SPR is included as a template in the new npm-version


ionic4 vue.js bindings

Ionic version:
[ ] 2.x
[ ] 3.x
[X ] 4.x
I'm submitting a ...
[ ] bug report
[X] feature request
Current behavior:
The 4.X version will promise framework agnostic UI components, because of ionic components will be also web components, but if we want to use in a production-ready app we would need a vue-binding, which:
Firs, avoid ignoring elements in vue.js, like this:
Vue.config.ignoredElements = [
  'ion-app',
  'ion-page',
  'ion-header',
  'ion-toolbar',
  'ion-title',
  'ion-content',
  'ion-list',
  'ion-item',
  'ion-label',
  'ion-button',
  'ion-searchbar',
]
new Vue({
  el: '#app',
  render: h => h(App)
})

Second, be able to listen and emit the ionic component's events, deriving the web components events to the vue components.
Expected behavior:
As OnSen UI does, we would need wrapping all the ionic components, again, as OnSen UI does, so the use of ionic components in vue apps would be something like this:
import Vue from 'vue';
import VueIonic from 'vue-ionic';

Vue.use(VueIonic);

And use the components in vue files like this:
<template>
  <v-ion-app>
    <v-ion-page class="show-page">
      <v-ion-header>
        <v-ion-toolbar>
          <v-ion-searchbar @input="handleInput"></ion-searchbar>
        </v-ion-toolbar>
      </v-ion-header>
      <v-ion-content class="content" padding>
          <v-ion-list>
            <v-ion-item v-for="user of users" v-bind:key="user.id">
              <v-ion-label full>{{user.name}}</v-ion-label>
            </v-ion-item>
          </v-ion-list>
      </v-ion-content>
    </v-ion-page>
  </v-ion-app>
</template>

<script>
import axios from 'axios';
export default {
  name: 'app',
  data () {
    return {
      users: []
    }
  },
  created() {
      axios.get('http://foo.com/users.json')
      .then(response => {
        this.users = response.data
      })
  },
  methods: {
    handleInput(evt) {
      // handle input
    }
  }
}
</script>

<style>

</style>

I'd like to collaborate in this binding if you give me that honor.

Hello! I'm going to move this issue over to our internal list of feature requests just to clear it out of this list here.
Roadmap wise, the first release of v4 will likely just have the Angular bindings, but supporting other Frameworks such as Vue.js is certainly on our radar.
Also, thank-you for your offer to collaborate with us on this. We will keep that in mind when we start the Vue.js support effort.

This issue was moved to ionic-team/ionic-feature-requests#329

@kensodemann I think even if you will not work on this right now, we could work together on stencil to be ready for other frameworks outside the TS world.
For example I'd like to derive all the ionic's components events to Vue.js events to may wrap ionic components inside vue.js ones. But I think there is no an easy way to access the registered events.
But I don't know if we can inspect enough info about the web components events. Here is a fragment of my current code:
export const deriveEvents = {
  computed: {
    unrecognizedListeners() {
      // remove vue prefix 'v-' from the tag name
      // so 'v-ion-button' will be 'ion-button'
      const tagName = this.$options._componentTag.slice(2);

      // TODO: what's the correct expression?
      // Ionic.components[tagName.toUpperCase()].foo?
      // customElements.get(tagName).events ?
      const ionComponentEvents = ...;

      return Object.keys(this.$listeners || {})
        .filter(k => (ionComponentEvents || []).indexOf(k) === -1)
        .reduce((r, k) => {
          r[k] = this.$listeners[k];
          return r;
        }, {});
    }
  },
  ...

How can I do this? Do you think I should open an issue for that in stencil github issue tracker?

@kensodemann Just for comparison, OnSen UI does this explícitly on the custom elements definition, like here: https://github.com/OnsenUI/OnsenUI/blob/master/core/src/elements/ons-pull-hook.js#L461

@msaelices - right now the whole team is basically heads down on the initial @ionic/angular and @ionic/core v4 efforts. However, I am sure your input would be welcomed. It seems the Stencil repo would make the most sense based on my reading of your question above.


Helm push error

Output of helm version:

Output of kubectl version:

Cloud Provider/Platform (AKS, GKE, Minikube etc.):

Please do as the error says


When weight_initial is NULL then new_weight will fail

In ops.cc method new_weight, current logic is when weight_initial != NULL, then allocate_memory, else weight_ptr would be null ptr.
I don't know whether this logic is what we wanted, but there is an exception about it.
When look into ops_cudnn.cu:allocate_memory, there is a null condition inside actually.
So I think even we don't check weight_initial in ops.cc:new_weight, the logic still holds and no exception.

Actually in this scenario, this tensor has a dimension of 0

Thanks for pointing out the issue. The bug should have been fixed in 6b884.
The logic for new_weight is that TASO will always allocate a device memory for the new weight. If weight_initial is provided, the allocated memory will be initialized using the given value.
The logic should work for 0-d tensors as well, though we haven't explicitly test TASO with 0-d tensors. Let me know if you observe any other issues with 0-d tensors.

noop.cc: create_weight, there is an assertion as well.

I have replaced the assertion in noop.cc to a warning message in commit c78e82b8.
Presumably, when TASO encounters an uninitialized weight tensor, it is likely due to a bug in previous layers, and we should report a warning message to users.


fixed typo

oldName -> newName

Docs Build status updates of commit b49ae08:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

Language/Reference/User-Interface-Help/name-statement.md
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel

@grahampcharles Good catch! Thank you very much!


Add option to synchronize theme with frontend

I'll add the two new Quartz themes when the new 7.70 beta version is available. It makes more sense then to have the option to sync the abapGit theme selection with the SAP GUI theme selection. Could also maybe set it as the default then.
Note you need to re-logon to the system after a frontend theme change for get_themename to report the new one (even if you force refresh the cache).

thanks 👍


Support more features

This PR is a series of small fixes to support more rust code.

The corresponding charon fix is ready


Update emojiland.html

Strengths

Clear Structure: The HTML and CSS are well-organized, making the code readable and maintainable.
Interactive Features: Emojis are generated at random positions, and audio plays on hover, enhancing user engagement.
Dynamic Animation: The welcome message animates character-by-character, creating an appealing introduction.
Memory Management: The use of timeouts helps prevent memory leaks by clearing out emojis after a set duration.

Areas for Improvement

Audio Preloading: Currently, audio files aren’t preloaded, which could cause delays in playback.
Accessibility: The implementation lacks ARIA roles and labels, which would improve accessibility for screen readers.
Mobile Responsiveness: The hover effects may not work well on touch devices; adapting interactions for mobile users could enhance usability.
Configuration Management: Hardcoding emojis and audio could be improved by using a configuration object or JSON for easier updates.

Which issue did you work upon, please mention the issue number


Use vue

Seems to be slow... Compare with current version and see if it's always been like this, or if vue is clogging things up.

Using the profiler, discovered that most of the processing is from vue dev tools: Turn that off, and it's snappy! The vue dev tools slow down the old, non-vue version, and really slow down the vue version: ~4 seconds for re-render.
Lots still to do, but a good start.


Improvements to query API

The query API currently allows a user to query the FileCatalog table in the IMAP SDC database.  There are some improvements we could make to this:

Add support for querying the other database tables (e.g. UniversalSpinTable, Version, etc.)
Enable some common queries, e.g.:

https://api.dev.imap-mission.com/query?today could return all files that were acquired in the last 24 hours)
https://api.dev.imap-mission.com/query?days_ago=N could return all files that were acquired in the last N days)
https://api.dev.imap-mission.com/query?version=latest could return the latest version (i.e. highest version number) of files)
https://api.dev.imap-mission.com/query?show_metadata could show file metadata in the results (e.g. file sizes, the start and end time that the data in the file covers, when the file was created, etc.)

Thank you to @joeymukherjee for some ideas on this!

The code that handles the API calls is under here: https://github.com/IMAP-Science-Operations-Center/sds-data-manager/tree/dev/sds_data_manager/lambda_code/SDSCode


Update analysis vignette heat trees.

The analysis vignette has an error:
#line 132
heat_tree_plots <- heat_tree_plots(metacoder_obj,
                                       rank_list = c("Phylum", "Class", "Order", "Family", "Genus", "Species"),
                                       node_label = ifelse(wilcox_p_value > 0.05, taxon_ids, NA),
                                       node_label_size = 2,
                                       node_label_color = c("darkgreen"))

"wilcox_p_value > 0.05" should be "wilcox_p_value < 0.05"

Resolved by #78


[IZPACK-1277]  in ShortcutSpec.xml is ignored

@hiteshbosamiya could you rebase this PR pls..

@reinhapa, rebased the PR.


added link for illegal prime decoding

Added link to my very short code bit

:+1: thanks for the PR and the presentation!

It's always nice to see how BHNT encourages people to finally publish their nice hacks. :-)


[BUG] Actions breaks if folders use parenthesis in the names

Is there an existing issue for this?

[X] I have searched the existing issues

Does this issue exist in the latest version?

[X] I'm using the latest release

Describe the bug?
SvelteKit has an advanced routing feature called layout groups: https://kit.svelte.dev/docs/advanced-routing#advanced-layouts-group - when a file within one of these folders is changed (e.g. src/routes/(app)/+page.svelte) then this action will incorrectly escape the parenthesis ending up with: INPUT_CHANGED_FILES: src/routes/\(app\)/+page.svelte and eslint will not error because it didn't find any files with that filename.
To Reproduce
In any of your examples, add parenthesis into a folder name and then commit to GitHub to see the action run and break.
What OS are you seeing the problem on?
ubuntu-latest or ubuntu-22.04
Expected behavior?
Action only runs lint on changed files and doesn't break.
Relevant log output
There is no log archive to download, but this section of the workflow run is applicable as you can see the correct filepath before the changed-files-patterns group runs but then it's wrong afterwards.
##[debug]Fetching target branch...
  /usr/bin/git fetch -q --no-tags --prune -u --progress --deepen=50 origin +refs/heads/main:refs/remotes/origin/main
  remote: Total 0 (delta 0), reused 0 (delta 0), pack-reused 0
  Completed fetching more history.
  ##[debug]Getting current SHA...
  /usr/bin/git rev-parse --verify defa9e3ed1dab59e06e66688997ed2532c36bdf2^{commit}
  defa9e3ed1dab59e06e66688997ed2532c36bdf2
  /usr/bin/git rev-parse --verify defa9e3ed1dab59e06e66688997ed2532c36bdf2^{commit}
  defa9e3ed1dab59e06e66688997ed2532c36bdf2
  ##[debug]Current SHA: defa9e3ed1dab59e06e66688997ed2532c36bdf2
  /usr/bin/git merge-base 18db55d30244cc161d9885c65a42ffc8b2d497f5 defa9e3ed1dab59e06e66688997ed2532c36bdf2
  18db55d30244cc161d9885c65a42ffc8b2d497f5
  /usr/bin/git log --format=%H 18db55d30244cc161d9885c65a42ffc8b2d497f5..defa9e3ed1dab59e06e66688997ed2532c36bdf2
  defa9e3ed1dab59e06e66688997ed2532c36bdf2
  /usr/bin/git merge-base 18db55d30244cc161d9885c65a42ffc8b2d497f5 defa9e3ed1dab59e06e66688997ed2532c36bdf2
  18db55d30244cc161d9885c65a42ffc8b2d497f5
  /usr/bin/git log --format=%H 18db55d30244cc161d9885c65a42ffc8b2d497f5..defa9e3ed1dab59e06e66688997ed2532c36bdf2
  defa9e3ed1dab59e06e66688997ed2532c36bdf2
  /usr/bin/git rev-parse --verify 18db55d30244cc161d9885c65a42ffc8b2d497f5^{commit}
  18db55d30244cc161d9885c65a42ffc8b2d497f5
  ##[debug]Previous SHA: 18db55d30244cc161d9885c65a42ffc8b2d497f5
  /usr/bin/git merge-base 18db55d30244cc161d9885c65a42ffc8b2d497f5 defa9e3ed1dab59e06e66688997ed2532c36bdf2
  18db55d30244cc161d9885c65a42ffc8b2d497f5
  /usr/bin/git log --format=%H 18db55d30244cc161d9885c65a42ffc8b2d497f5..defa9e3ed1dab59e06e66688997ed2532c36bdf2
  defa9e3ed1dab59e06e66688997ed2532c36bdf2
  Retrieving changes between 18db55d30244cc161d9885c65a42ffc8b2d497f5 (main) → defa9e3ed1dab59e06e66688997ed2532c36bdf2 (debug-lint)
  /usr/bin/git diff --name-status --ignore-submodules=all --diff-filter=ACDMRTUX 18db55d30244cc161d9885c65a42ffc8b2d497f5...defa9e3ed1dab59e06e66688997ed2532c36bdf2
  M	site/src/routes/[mother=locale]/[learning=locale]/(app)/account/+page.svelte
  ##[debug]All diff files: {"A":[],"C":[],"D":[],"M":["site/src/routes/[mother=locale]/[learning=locale]/(app)/account/+page.svelte"],"R":[],"T":[],"U":[],"X":[]}
  All Done!
  ::endgroup::
::group::changed-files-patterns
changed-files-patterns
##[debug]Node Action run completed with exit code 0
##[debug]Set output added_files =
##[debug]Set output added_files_count = 0
##[debug]Set output copied_files =
##[debug]Set output copied_files_count = 0
##[debug]Set output modified_files = site/src/routes/[mother=locale]/[learning=locale]/\(app\)/account/+page.svelte
##[debug]Set output modified_files_count = 1
##[debug]Set output renamed_files =
##[debug]Set output renamed_files_count = 0
##[debug]Set output type_changed_files =
##[debug]Set output type_changed_files_count = 0
##[debug]Set output unmerged_files =
##[debug]Set output unmerged_files_count = 0
##[debug]Set output unknown_files =
##[debug]Set output unknown_files_count = 0
##[debug]Set output all_changed_and_modified_files = site/src/routes/[mother=locale]/[learning=locale]/\(app\)/account/+page.svelte
##[debug]Set output all_changed_and_modified_files_count = 1
##[debug]Set output all_changed_files = site/src/routes/[mother=locale]/[learning=locale]/\(app\)/account/+page.svelte
##[debug]Set output all_changed_files_count = 1
##[debug]Set output any_changed = true
##[debug]Set output only_changed = true
##[debug]Set output other_changed_files =
##[debug]Set output other_changed_files_count = 0
##[debug]Set output all_modified_files = site/src/routes/[mother=locale]/[learning=locale]/\(app\)/account/+page.svelte
##[debug]Set output all_modified_files_count = 1
##[debug]Set output any_modified = true
##[debug]Set output only_modified = true
##[debug]Set output other_modified_files =
##[debug]Set output other_modified_files_count = 0
##[debug]Set output deleted_files =
##[debug]Set output deleted_files_count = 0
##[debug]Set output any_deleted = false
##[debug]Set output only_deleted = false
##[debug]Set output other_deleted_files =
##[debug]Set output other_deleted_files_count = 0
##[debug]Finished: run

Has all relevant logs been included?

[X] I've included all relevant logs

Anything else?
No response
Code of Conduct

[X] I agree to follow this project's Code of Conduct

I guess the real issue is in https://github.com/tj-actions/changed-files/blob/main/src/changedFiles.ts - I'll try to add a failing test there and see if I can't submit a PR to fix it.

This passes just fine so no issue here:
// Tests that getFilteredChangedFiles correctly handles parenthesis in folder names
    it('should not escape parenthesis in folder names', async () => {
      const allDiffFiles = {
        [ChangeTypeEnum.Added]: [],
        [ChangeTypeEnum.Copied]: [],
        [ChangeTypeEnum.Deleted]: [],
        [ChangeTypeEnum.Modified]: [
          'src/routes/[learning=locale]/(app)/+page.svelte'
        ],
        [ChangeTypeEnum.Renamed]: [],
        [ChangeTypeEnum.TypeChanged]: [],
        [ChangeTypeEnum.Unmerged]: [],
        [ChangeTypeEnum.Unknown]: []
      }
      const filePatterns = ['**/*.svelte']
      const filteredFiles = await getFilteredChangedFiles({
        allDiffFiles,
        filePatterns
      })
      expect(filteredFiles[ChangeTypeEnum.Modified]).toEqual([
        'src/routes/[learning=locale]/(app)/+page.svelte'
      ])
    })

The issue happens in this block. So either in the inputs.escapeJson or the JSON.stringify or the getChangeTypeFiles function. That's about as far as I can debug. But yes, definitely this issue should be moved to https://github.com/tj-actions/changed-files as the issue is either in that package or me not knowing how to use the settings properly.

Hi @jacob-8 This issue has been resolved in the latest release.
You'll need to set the escape_paths input to false explicitly
      - name: Run ESLint on changed files
        uses: tj-actions/eslint-changed-files@v25
        with:
          ...
          escape_paths: false
          ...


ARROW-3546: [Python] Provide testing setup to verify wheel binaries work in one or more common Linux distributions

Waiting for builds https://github.com/kszucs/crossbow/branches/all?utf8=✓&query=build-338-wheel-linux

So the problem with this is that the build environment and the test environment are the same. Would this have caught ARROW-3514?

Oh I see it's a different environment. We need to demonstrate that the ARROW-3514 bug reproduces

I've tried it locally:
$ docker run -it python:3.6-slim bash
root@cf561b62da5a:/# pip install pyarrow
root@cf561b62da5a:/# python

Python 3.6.6 (default, Oct 16 2018, 07:20:07)
[GCC 6.3.0 20170516] on linux
Type "help", "copyright", "credits" or "license" for more information.
>>> import io
>>> import pyarrow as pa
>>> import pyarrow.parquet as pq
>>>
>>> table = pa.Table.from_arrays([pa.array(['abc', 'def'])], ['some_col'])
>>> f = io.BytesIO()
>>> pq.write_table(table, f, compression='gzip')
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
  File "/usr/local/lib/python3.6/site-packages/pyarrow/parquet.py", line 1125, in write_table
    writer.write_table(table, row_group_size=row_group_size)
  File "/usr/local/lib/python3.6/site-packages/pyarrow/parquet.py", line 376, in write_table
    self.writer.write_table(table, row_group_size=row_group_size)
  File "pyarrow/_parquet.pyx", line 934, in pyarrow._parquet.ParquetWriter.write_table
  File "pyarrow/error.pxi", line 83, in pyarrow.lib.check_status
pyarrow.lib.ArrowIOError: Arrow error: IOError: zlib deflate failed, output buffer too small

OK, great, thank you!

Codecov Report

Merging #2781 into master will increase coverage by 1.46%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master    #2781      +/-   ##
==========================================
+ Coverage   87.61%   89.08%   +1.46%
==========================================
  Files         403       12     -391
  Lines       62403     1621   -60782
==========================================
- Hits        54674     1444   -53230
+ Misses       7659      177    -7482
+ Partials       70        0      -70

Impacted Files
Coverage Δ

python/pyarrow/ipc.pxi

cpp/src/parquet/column_page.h

cpp/src/parquet/bloom_filter-test.cc

cpp/src/plasma/client.cc

cpp/src/arrow/io/test-common.h

cpp/src/arrow/ipc/metadata-internal.h

cpp/src/arrow/python/io.cc

python/pyarrow/hdfs.py

cpp/src/parquet/column_scanner.cc

python/pyarrow/lib.pxd

... and 381 more

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 56e72ba...981af44. Read the comment docs.

I've removed the centos test images because there is a total u vs mu chaos in dockerland.


[Feature] add satellite.earth on Nostr section

Feature description
Hi, add https://satellite.earth/ on Nostr section
Describe the solution
Add https://satellite.earth/ on Nostr section.
Describe alternatives
No response
Additional context
No response
Are you working on this?
No

I would like to work on this


How could we launch this work?

Hello, I hope you are doing well.
Could you tell me how I can run this repository to train your method on the MVTec AD/LOCO? To simplify things, let's assume that the datasets are at the project's root as "mvtec_anomaly_detection" and "mvtec_loco_anomaly_detection".
Regards.

Hello, buddy.
Thank you for your continued attention to this work. If you want to run this method, you can directly run the fuse_main.py script. However, please note that DADF is a two-stage training model, which includes reconstruction and likelihood. The fuse_main.py script annotates the reconstruction training and needs to be modified.
 I don’t have much time to organize it, so it may cause some trouble for your reproduction. Thank you for your understanding.

So you first train a CNN (reconstructor) to reconstruct images and then use the Normalizing Flow to estimate the negative log-likelihood of that CNN. Am I right?
If it is feasible for you, it would be great to have some hints hints which part should be fixed. Thanks very much for your attention.

Hello,
I am having the following issue:
FileNotFoundError: [Errno 2] No such file or directory: 'weights/pushpins/WResnet50_pushpins_CC.pth'
how can I generate the .pth file?


[ES] Initial spanish language support

Fixes #47

Was my first MR on home assistant. Thank you!!!


ci: Removed user input from proto_sync.py

Signed-off-by: Manish Kumar<EMAIL_ADDRESS>Removed user input from proto_sync.py.
Fixes #16835

CC @phlax


Update .trigger-openshift-ci

https://github.com/open-cluster-management/build-harness-extensions/pull/122

/lgtm


Migrate code to ES6(update RN to v0.27.2 & update react-native-vector-icons to v2.0.3)

First,Thanks for the awesome project,I learn a lot form this.
After go review the code,I decide to migrate it to ES6, and update it to the latest RN-0.27.2.

Awesome, thanks for the PR. I will review this very soon.

Hey @iSimar are you going to merge this request, because if you do, we might create pull request over top of it to make some improvements


Failing on busybox 1.26, incorrect flags passed to find

See: https://circleci.com/gh/riyazdf/cli/1900 (last step "Upload to Codecov")
==> Circle CI detected.
    project root: .
    Yaml found at: codecov.yml
==> Running gcov in . (disable via -X gcov)
==> Python coveragepy not found
==> Searching for coverage reports in:
    + .
    -> Found 1 reports
==> Detecting git/mercurial file structure
==> Reading reports
    + ./coverage.txt bytes=447884
==> Appending adjustments
    http://docs.codecov.io/docs/fixing-reports
find: unrecognized: ./vendor/golang.org
BusyBox v1.26.2 (2017-06-11 06:38:32 GMT) multi-call binary.

Usage: find [-HL] [PATH]... [OPTIONS] [ACTIONS]

It finds no files to upload, so the reports are empty.

Thanks for reporting. This find error is during report fixes and is odd. I'll have to review it more.
Meanwhile try this:
bash <(curl -s https://codecov.io/bash) -X fixes

I'm seeing this error as well, however it succeeded with the report upload. I'm on node:12-alpine, having used apk add --no-cache git curl bash to be able to run codecov-bash. Adding findutils fixed this for me.

I can confirm adding findutils fixes and resolves this issue.

Similar error on our end with another flag:
==> Running gcov in . (disable via -X gcov)
find: unrecognized: -execdir
BusyBox v1.31.1 () multi-call binary.

Hi @Maxwell2022, if this is still an issue, please open a ticket in our community boards.


Object representation of map validation failures

Previously, map validation failures were represented as English strings for
display in the admin UI. But in the API, we'll need to turn them into
machine-readable values.
Add validation failure types for all the validation checks in PlantingSiteModel
and PlantingZoneModel, and change those classes to return a list of failure
objects rather than a list of strings.
Shapefile validation failures are still represented as English strings since
shapefile upload is going to remain an admin UI function. But to make the
distinction between map validation and shapefile validation clearer, the
exception that's thrown for shapefile problems is renamed to
ShapefilesInvalidException.

[!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

#2042
#2041
#2040  👈
#2039
main

This stack of pull requests is managed by Graphite. Learn more about stacking.

Join @sgrimm and the rest of your teammates on  Graphite

I like this changes! The problems types/enums are much easier to follow! Thanks Steve!

Merge activity

Jun 5, 6:01 PM EDT: @sgrimm started a stack merge that includes this pull request via Graphite.


Ansible module for chef-runner

The main goal of chef-runner is to provision remote machines via SSH. Ansible works in a similar way. So let's combine both to create the easiest Chef provisioner there is.
I already spiked an Ansible module which allows to provision a Vagrant machine. Here's a sample playbook:
---
- hosts: localhost
  connection: local
  gather_facts: no
  tasks:
    - name: Provision system with chef-runner
      chef_runner:
        vagrant_machine: default
        install_chef: "true"
        executable: "/usr/local/bin/chef-runner"
        working_dir: "/Users/mlafeldt/devel/projects/practicing-ruby-cookbook"
        run_list:
          - recipe[apt::default]
          - practicingruby::_deploy_user

This basically works, but I lack the knowledge to complete it the way I want.
Problem 1
In particular, I don't know how to best support all the target systems chef-runner supports:

Vagrant machines
Test Kitchen instances
plain SSH
provision host system

I don't like the idea of having a separate configuration variable, e.g. vagrant_machine, for every supported system.
Problem 2
To implement the most obvious use case with Ansible -- plain SSH -- I'd somehow have to pass Ansible's SSH connection settings (hostname, user, and other SSH options) to chef-runner. For this, I need to know if it's possible to access SSH connection settings for a host from Ansible modules.
(Instead of running chef-runner locally, I could instead run it on the remote host that is going to be provisioned. Unfortunately, this would require other Ruby tools to be installed on the remote host as well, e.g. for resolving cookbook dependencies. That's why I prefer connection: local here.)

@gildegoma Maybe you can help me here?

Need to check these:

http://docs.ansible.com/playbooks_variables.html#information-discovered-from-systems-facts
http://docs.ansible.com/intro_inventory.html#list-of-behavioral-inventory-parameters

As for problem 2, I found out that I can pass the SSH parameters from the hosts file to the modules, e.g.:
- hosts: practicingruby
  connection: local
  gather_facts: no
  tasks:
    - name: Provision system with chef-runner
      chef_runner:
        host: "{{ ansible_ssh_user }}@{{ ansible_ssh_host }}"
        ssh_options:
          - "StrictHostKeyChecking no"
          - "IdentityFile {{ ansible_ssh_private_key_file }}"
          - "UserKnownHostsFile /dev/null"
        install_chef: "true"
        executable: "/usr/local/bin/chef-runner"
        working_dir: "/Users/mlafeldt/devel/projects/practicing-ruby-cookbook"
        run_list:
          - recipe[apt::default]
          - practicingruby::_deploy_user

However, I would still prefer retrieving these parameters inside the Ansible module. Still don't know how to do this, though.


Add support to a date system

A date system would be very useful when including other features other features such as the stock market. Adding a date system would make the game a real world experience. We are planning to use my Timers library to implement this. Here are the things that should be changed under this issue

[x] Supporting a date system (which probably change dates periodically)
[ ] Use the new date system to implement other features (including stock market and jackpot support)

Here's how the new timer looks like in the map

Probably need some UI updates


Add LSM6DSO support

Hey @ginkage,
Thank you for this awesome little project!
Unfortunately, the BMI160 is currently hard to get, so I added support for the LSM6DSOTR (LSM6DSO lib).
I also got rid of the checked-in external dependencies and moved them to submodules inside the /lib/ folder.
Additionally, I added some logic to select the correct library by scanning the I2C addresses.
I would be happy if you could merge the changes back into your repo and update the app or let me know if you have any suggestions.
The changes are only tested with LSM6DSOTR.
Cheers!

Hi!
Thanks, this looks nice. I'll review and add comments as I go (sorry in advance if it will be a tad slow), but at a first glance it does look good. We'll also need to bump the app version in the Flipper store, plus I want to add a warning if the app was launched without a connected module, but all in all I'm happy to adopt this change.

Looks like all the driver files now have the imu_ prefix, so probably worth just dropping it (that could make reviewing changes a tad trickier, but I can always just look at the specific commit with renaming).
Sorry, there are quite a few comments now, but I believe the whole thing will look significantly cleaner, and that'll make it a bit easier to add other IMUs like MPU6050 in the future.

No rush, and thank you once again for the PR!

I hope I got everything.
I also added a shortcut in the IMU detection / I2C scanning. We just need to test the known addresses.

Thanks, looking cleaner now!
Just a couple more comments (basically, the idea is that .h files define an API used by other modules, so they shouldn't contain things that aren't used in other .c files).

Oh well, I guess I'll clean up the rest myself. Thanks again.

Sorry, I didn't have time to refactor it. Thank you for taking over.


A character gets skipped here and there in the output, using any model, over any tunnel

What is the issue?
Hello,
Here is the output:
**The Art of Ball Handling: Mastering Control on and off the Court**

When it comes to various sports, mastering ball handling is a aspect that separates the good players from the great ones. Whether you're playing basketball, soccer, or tennis, controlling the ball with precision finesse can make all the difference in your game.

**The Fundamentals of Ball**

Ball handling begins with understanding the basics.'s not just about throwing the ball from one hand to another; it's about developing muscle memory and coordination that allows you to control the with ease. To improve your ball handling, practice basic drills such as:

*   **Stationary Dribbling:** Start by standing and dribbling the ball with both hands. Focus on keeping your head up, staying low, and using different parts of your hand to the ball.
*   **Figure-Eights:** Draw a figure-eight pattern on the ground with your non-dominant foot while keeping ball close to your body. Switch directions and repeat with your dominant foot.

**Advanced Ball Handling Techniques**

As you become more comfortable with drills, it's time to move on to advanced techniques that will take your game to the next level:

*   **Behind-the- Dribble:** This technique involves dribbling the ball behind your back while keeping it close to your body. Start by standing still and move into a crouch position.
*   **Between-the-Legs Dribble:** Similar to the behind-the-back dribble, technique involves dribbling the ball between your legs while keeping it close to your body.

**Tips for Improving Ball Handling**

Mastering handling takes time, patience, and dedication. Here are some additional tips to help you improve:

*   **Practice Regularly:** Cons is key when it comes to improving ball handling. Aim to practice at least 30 minutes a day.
*   **Stay Relaxed Tension in your arms and hands can lead to sloppy ball handling. Practice relaxing while keeping control of the ball.

**Ball Handling for Sports**

While the fundamentals of ball handling remain the same across various sports, there are some specific techniques that apply to each game:

* **Basketball:** In basketball, ball handling is critical for creating scoring opportunities and breaking down defenses.
*   **Soccer:** Ball in soccer involves using different parts of your foot to trap, dribble, and pass the ball.

**Conclusion**

Mastering ball handling time and practice, but with dedication and patience, you can develop the skills needed to dominate on the court. Whether you're playing basketball soccer, or tennis, remember to stay relaxed, focus on proper technique, and practice regularly.

---

###  **Additional Resources:**

   [Basketball Ball Handling Drills](https://www.basketball-drills.com/ball-handling/)
*   [S Ball Control Tips](https://www.soccer-training.org/soccer-ball-control-tips/)

###  **Books on Ball Handling:**

   "The Art of Dribbling" by Kevin Durant
*   "Ball Control for Soccer" by Pep Guardiola

NoteKeep in mind that these books and resources are subject to change, so be sure to verify the information before using them.

By following the and techniques outlined above, you can improve your ball handling skills and take your game to the next level. Remember to practice regularly, stay, and focus on proper technique. Happy practicing!

As you can see there are a couple of errors here, for instance

**Stay Relaxed

is missing an extra ** at the end.
Everything seem to work fine over local (http://localhost:11434) but once I try it over a Cloudlare tunnel it seems to skip characters here and there.
Why could this be, is there a possible fix?
Thanks
OS
Windows
GPU
Nvidia
CPU
Intel
Ollama version
0.3.4

What interface are you using to connect to ollama?  API, ollama run, open-webui, etc?  What model and prompt from your example?