 Instead, I get:
INFO Waiting for snap.lxd.daemon.unix.socket to stop.
(Repeat 20 times)
INFO Waiting for snap.lxd.daemon.service to stop.
(Repeat 20 times)
INFO snap.lxd.daemon.service refused to stop, killing.
2020-06-08T11:54:35-05:00 ERROR snap.lxd.daemon.unix.socket failed to stop:
timeout
error: cannot perform the following tasks:

Mount snap "lxd" (15359) (snap-lxd-15359.mount failed to stop: timeout)
Stop snap "lxd" services (snap.lxd.daemon.unix.socket failed to stop: timeout)

Also, I lose the unix socket and have to manually restart with "systemctl start snap.lxd.activate.service"
I've tried manually downloading the snap and mounting it, then copying lxd to lxd.debug
"cp /mnt/bin/lxd /var/snap/lxd/common/lxd.debug" and running lxd --debug --group lxd. The debug runs and nothing out of the ordinary shows up but "snap refresh lxd" still gives the same result.
Steps to reproduce

run "snap refresh lxd"

debug output:
LXD 4.1 is starting in normal mode       path=/var/snap/lxd/common/lxd
INFO[06-08|12:13:33] Kernel uid/gid map:
INFO[06-08|12:13:33]  - u 0 0<PHONE_NUMBER>
INFO[06-08|12:13:33]  - g 0 0<PHONE_NUMBER>
INFO[06-08|12:13:33] Configured LXD uid/gid map:
INFO[06-08|12:13:33]  - u 0 1000000<PHONE_NUMBER>
INFO[06-08|12:13:33]  - g 0 1000000<PHONE_NUMBER>
INFO[06-08|12:13:33] Kernel features:
INFO[06-08|12:13:33]  - netnsid-based network retrieval: no
INFO[06-08|12:13:33]  - pidfds: no
INFO[06-08|12:13:33]  - uevent injection: no
INFO[06-08|12:13:33]  - seccomp listener: no
INFO[06-08|12:13:33]  - seccomp listener continue syscalls: no
INFO[06-08|12:13:33]  - unprivileged file capabilities: yes
INFO[06-08|12:13:33]  - cgroup layout: hybrid
WARN[06-08|12:13:33]  - Couldn't find the CGroup memory swap accounting, swap limits will be ignored
INFO[06-08|12:13:33]  - shiftfs support: no
INFO[06-08|12:13:33] Initializing local database
DBUG[06-08|12:13:33] Initializing database gateway
DBUG[06-08|12:13:33] Start database node                      id=1 address= role=voter
INFO[06-08|12:13:34] Starting /dev/lxd handler:
INFO[06-08|12:13:34]  - binding devlxd socket                 socket=/var/snap/lxd/common/lxd/devlxd/sock
INFO[06-08|12:13:34] REST API daemon:
INFO[06-08|12:13:34]  - binding Unix socket                   socket=/var/snap/lxd/common/lxd/unix.socket
INFO[06-08|12:13:34] Initializing global database
DBUG[06-08|12:13:34] Dqlite: attempt 0: server 1: connected
DBUG[06-08|12:13:35] Firewall detected "nftables" incompatibility: Kernel version does not meet minimum requirement of 5
DBUG[06-08|12:13:35] Firewall xtables detected iptables is in use
INFO[06-08|12:13:35] Firewall loaded driver "xtables"
INFO[06-08|12:13:35] Initializing storage pools
DBUG[06-08|12:13:35] Initializing and checking storage pool "lxd"
DBUG[06-08|12:13:35] Mount started                            driver=dir pool=lxd
DBUG[06-08|12:13:35] Mount finished                           driver=dir pool=lxd
DBUG[06-08|12:13:35] Initializing and checking storage pool "lxcpool"
DBUG[06-08|12:13:35] Mount started                            driver=zfs pool=lxcpool
DBUG[06-08|12:13:35] Mount finished                           driver=zfs pool=lxcpool
DBUG[06-08|12:13:35] Initializing and checking storage pool "rfast"
DBUG[06-08|12:13:35] Mount started                            driver=zfs pool=rfast
DBUG[06-08|12:13:35] Mount finished                           driver=zfs pool=rfast
INFO[06-08|12:13:35] Initializing daemon storage mounts
INFO[06-08|12:13:35] Initializing networks
DBUG[06-08|12:13:35] New task Operation: a147a5c8-c828-4c58-94f0-2b29acc59cd4
INFO[06-08|12:13:35] Pruning leftover image files
DBUG[06-08|12:13:35] Started task operation: a147a5c8-c828-4c58-94f0-2b29acc59cd4
INFO[06-08|12:13:35] Done pruning leftover image files
INFO[06-08|12:13:35] Loading daemon configuration
DBUG[06-08|12:13:35] Success for task operation: a147a5c8-c828-4c58-94f0-2b29acc59cd4
DBUG[06-08|12:13:35] Initialized inotify with file descriptor 22
DBUG[06-08|12:13:35] New task Operation: 905b923a-30f1-4a44-b767-01a72b432745
INFO[06-08|12:13:35] Pruning expired images
DBUG[06-08|12:13:35] Started task operation: 905b923a-30f1-4a44-b767-01a72b432745
INFO[06-08|12:13:35] Done pruning expired images
DBUG[06-08|12:13:35] New task Operation: e417d343-1d4e-4278-b005-4496ef0fcd12
DBUG[06-08|12:13:35] Success for task operation: 905b923a-30f1-4a44-b767-01a72b432745
INFO[06-08|12:13:35] Pruning expired instance backups
DBUG[06-08|12:13:35] Started task operation: e417d343-1d4e-4278-b005-4496ef0fcd12
INFO[06-08|12:13:35] Done pruning expired instance backups
DBUG[06-08|12:13:35] Success for task operation: e417d343-1d4e-4278-b005-4496ef0fcd12
DBUG[06-08|12:13:35] New task Operation: 6d39d630-8b67-40c8-8e5f-231405e8085c
DBUG[06-08|12:13:35] New task Operation: 5f4b38f0-1a3a-4982-a87d-1115adda6c4c
DBUG[06-08|12:13:35] New task Operation: 7b4bf1a8-461f-4310-b1e8-c7a73e83063d
INFO[06-08|12:13:35] Updating images
DBUG[06-08|12:13:35] Started task operation: 5f4b38f0-1a3a-4982-a87d-1115adda6c4c
INFO[06-08|12:13:35] Updating instance types
DBUG[06-08|12:13:35] Started task operation: 7b4bf1a8-461f-4310-b1e8-c7a73e83063d
INFO[06-08|12:13:35] Expiring log files
DBUG[06-08|12:13:35] Started task operation: 6d39d630-8b67-40c8-8e5f-231405e8085c
INFO[06-08|12:13:35] Done updating images
INFO[06-08|12:13:35] Done expiring log files
INFO[06-08|12:13:35] Done updating instance types
DBUG[06-08|12:13:35] Success for task operation: 6d39d630-8b67-40c8-8e5f-231405e8085c
DBUG[06-08|12:13:35] Processing image                         fp=d125be3eded77d54fdeb2971e25b7f98b8e80a71f365353def505ac0c7c63803 server=https://images.linuxcontainers.org protocol=simplestreams alias=ubuntu/bionic/amd64
DBUG[06-08|12:13:35] Connecting to a remote simplestreams server
DBUG[06-08|12:13:36] Scheduler: network: vethb1196dee has been added: updating network priorities
DBUG[06-08|12:13:36] Scheduler: network: veth7cc89c56 has been added: updating network priorities
DBUG[06-08|12:13:36] MountInstance started                    driver=zfs pool=lxcpool project=default instance=apache
DBUG[06-08|12:13:36] Mounted ZFS dataset                      driver=zfs pool=lxcpool dev=rpool/lxc/containers/apache path=/var/snap/lxd/common/lxd/storage-pools/lxcpool/containers/apache
DBUG[06-08|12:13:36] MountInstance finished                   driver=zfs pool=lxcpool project=default instance=apache
DBUG[06-08|12:13:36] UpdateInstanceBackupFile started         driver=zfs pool=lxcpool project=default instance=apache
DBUG[06-08|12:13:36] UpdateInstanceBackupFile finished        driver=zfs pool=lxcpool project=default instance=apache
DBUG[06-08|12:13:36] MountInstance started                    driver=zfs pool=lxcpool project=default instance=apache
DBUG[06-08|12:13:36] MountInstance finished                   driver=zfs pool=lxcpool project=default instance=apache
INFO[06-08|12:13:36] Starting container                       used=2020-06-08T11:01:38-0500 stateful=false project=default name=apache action=start created=2020-04-09T15:03:04-0500 ephemeral=false
DBUG[06-08|12:13:37] Handling                                 method=GET url=/internal/containers/55/onstart ip=@ user=
DBUG[06-08|12:13:37] MountInstance started                    driver=zfs pool=lxcpool project=default instance=apache
DBUG[06-08|12:13:37] MountInstance finished                   driver=zfs pool=lxcpool project=default instance=apache
DBUG[06-08|12:13:37] Scheduler: container apache started: re-balancing
INFO[06-08|12:13:37] Started container                        action=start created=2020-04-09T15:03:04-0500 ephemeral=false used=2020-06-08T11:01:38-0500 stateful=false project=default name=apache
DBUG[06-08|12:13:37] MountCustomVolume started                driver=zfs pool=rfast project=default volName=mysql-data
DBUG[06-08|12:13:37] Mounted ZFS dataset                      driver=zfs pool=rfast dev=rfast/custom/default_mysql-data path=/var/snap/lxd/common/lxd/storage-pools/rfast/custom/default_mysql-data
DBUG[06-08|12:13:37] MountCustomVolume finished               driver=zfs pool=rfast project=default volName=mysql-data
DBUG[06-08|12:13:37] MountCustomVolume started                driver=zfs pool=rfast project=default volName=mysql-log
DBUG[06-08|12:13:37] Mounted ZFS dataset                      driver=zfs pool=rfast path=/var/snap/lxd/common/lxd/storage-pools/rfast/custom/default_mysql-log dev=rfast/custom/default_mysql-log
DBUG[06-08|12:13:37] MountCustomVolume finished               driver=zfs pool=rfast project=default volName=mysql-log
DBUG[06-08|12:13:37] Scheduler: network: veth1f6bc0bd has been added: updating network priorities
DBUG[06-08|12:13:37] Scheduler: network: vethfa763dd8 has been added: updating network priorities
DBUG[06-08|12:13:37] MountInstance started                    pool=rfast driver=zfs project=default instance=mysql
DBUG[06-08|12:13:37] Mounted ZFS dataset                      pool=rfast driver=zfs path=/var/snap/lxd/common/lxd/storage-pools/rfast/containers/mysql dev=rfast/containers/mysql
DBUG[06-08|12:13:37] MountInstance finished                   pool=rfast driver=zfs project=default instance=mysql
DBUG[06-08|12:13:37] UpdateInstanceBackupFile started         pool=rfast driver=zfs project=default instance=mysql
DBUG[06-08|12:13:37] UpdateInstanceBackupFile finished        pool=rfast driver=zfs project=default instance=mysql
DBUG[06-08|12:13:37] MountInstance started                    pool=rfast driver=zfs project=default instance=mysql
DBUG[06-08|12:13:37] MountInstance finished                   pool=rfast driver=zfs project=default instance=mysql
INFO[06-08|12:13:37] Starting container                       project=default name=mysql action=start created=2020-05-31T23:45:31-0500 ephemeral=false used=2020-06-08T11:01:39-0500 stateful=false
DBUG[06-08|12:13:37] Handling                                 method=GET url=/internal/containers/56/onstart ip=@ user=
DBUG[06-08|12:13:37] MountInstance started                    driver=zfs pool=rfast project=default instance=mysql
DBUG[06-08|12:13:37] MountInstance finished                   driver=zfs pool=rfast project=default instance=mysql
DBUG[06-08|12:13:37] Scheduler: container mysql started: re-balancing
INFO[06-08|12:13:37] Started container                        stateful=false project=default name=mysql action=start created=2020-05-31T23:45:31-0500 ephemeral=false used=2020-06-08T11:01:39-0500
DBUG[06-08|12:13:37] Scheduler: network: veth99fe1ce7 has been added: updating network priorities
DBUG[06-08|12:13:37] Scheduler: network: veth9cc2130c has been added: updating network priorities
DBUG[06-08|12:13:37] MountInstance started                    driver=zfs pool=lxcpool project=default instance=nflfan
DBUG[06-08|12:13:37] Mounted ZFS dataset                      driver=zfs pool=lxcpool dev=rpool/lxc/containers/nflfan path=/var/snap/lxd/common/lxd/storage-pools/lxcpool/containers/nflfan
DBUG[06-08|12:13:37] MountInstance finished                   driver=zfs pool=lxcpool project=default instance=nflfan
DBUG[06-08|12:13:37] UpdateInstanceBackupFile started         driver=zfs pool=lxcpool project=default instance=nflfan
DBUG[06-08|12:13:38] UpdateInstanceBackupFile finished        driver=zfs pool=lxcpool project=default instance=nflfan
DBUG[06-08|12:13:38] MountInstance started                    driver=zfs pool=lxcpool project=default instance=nflfan
DBUG[06-08|12:13:38] MountInstance finished                   driver=zfs pool=lxcpool project=default instance=nflfan
INFO[06-08|12:13:38] Starting container                       ephemeral=false used=2020-06-08T11:01:39-0500 stateful=false project=default name=nflfan action=start created=2020-04-09T14:52:12-0500
DBUG[06-08|12:13:38] Handling                                 url=/internal/containers/53/onstart ip=@ user= method=GET
DBUG[06-08|12:13:38] MountInstance started                    driver=zfs pool=lxcpool project=default instance=nflfan
DBUG[06-08|12:13:38] MountInstance finished                   driver=zfs pool=lxcpool project=default instance=nflfan
DBUG[06-08|12:13:38] Scheduler: container nflfan started: re-balancing
INFO[06-08|12:13:38] Started container                        stateful=false project=default name=nflfan action=start created=2020-04-09T14:52:12-0500 ephemeral=false used=2020-06-08T11:01:39-0500
DBUG[06-08|12:13:38] Scheduler: network: veth513b28d7 has been added: updating network priorities
DBUG[06-08|12:13:38] Scheduler: network: vetha064dfec has been added: updating network priorities
DBUG[06-08|12:13:38] MountInstance started                    driver=zfs pool=lxcpool instance=nginx project=default
DBUG[06-08|12:13:38] Mounted ZFS dataset                      driver=zfs pool=lxcpool dev=rpool/lxc/containers/nginx path=/var/snap/lxd/common/lxd/storage-pools/lxcpool/containers/nginx
DBUG[06-08|12:13:38] MountInstance finished                   driver=zfs pool=lxcpool instance=nginx project=default
DBUG[06-08|12:13:38] UpdateInstanceBackupFile started         driver=zfs pool=lxcpool project=default instance=nginx
DBUG[06-08|12:13:38] UpdateInstanceBackupFile finished        driver=zfs pool=lxcpool project=default instance=nginx
DBUG[06-08|12:13:38] MountInstance started                    driver=zfs pool=lxcpool project=default instance=nginx
DBUG[06-08|12:13:38] MountInstance finished                   driver=zfs pool=lxcpool project=default instance=nginx
INFO[06-08|12:13:38] Starting container                       ephemeral=false used=2020-06-08T11:01:40-0500 stateful=false project=default name=nginx action=start created=2020-04-09T14:57:01-0500
DBUG[06-08|12:13:38] Handling                                 method=GET url=/internal/containers/54/onstart ip=@ user=
DBUG[06-08|12:13:38] MountInstance started                    driver=zfs pool=lxcpool project=default instance=nginx
DBUG[06-08|12:13:38] MountInstance finished                   driver=zfs pool=lxcpool project=default instance=nginx
DBUG[06-08|12:13:38] Scheduler: container nginx started: re-balancing
INFO[06-08|12:13:38] Started container                        used=2020-06-08T11:01:40-0500 stateful=false project=default name=nginx action=start created=2020-04-09T14:57:01-0500 ephemeral=false
DBUG[06-08|12:13:38] Scheduler: network: vethdb76a6fb has been added: updating network priorities
DBUG[06-08|12:13:38] Scheduler: network: veth37c487e6 has been added: updating network priorities
DBUG[06-08|12:13:38] MountInstance started                    driver=zfs pool=lxcpool project=default instance=postfix
DBUG[06-08|12:13:38] Mounted ZFS dataset                      driver=zfs pool=lxcpool dev=rpool/lxc/containers/postfix path=/var/snap/lxd/common/lxd/storage-pools/lxcpool/containers/postfix
DBUG[06-08|12:13:38] MountInstance finished                   driver=zfs pool=lxcpool project=default instance=postfix
DBUG[06-08|12:13:38] UpdateInstanceBackupFile started         driver=zfs pool=lxcpool project=default instance=postfix
DBUG[06-08|12:13:38] UpdateInstanceBackupFile finished        driver=zfs pool=lxcpool project=default instance=postfix
DBUG[06-08|12:13:38] MountInstance started                    driver=zfs pool=lxcpool project=default instance=postfix
DBUG[06-08|12:13:38] MountInstance finished                   driver=zfs pool=lxcpool project=default instance=postfix
INFO[06-08|12:13:38] Starting container                       project=default name=postfix action=start created=2020-04-08T23:12:14-0500 ephemeral=false used=2020-06-08T11:01:40-0500 stateful=false
DBUG[06-08|12:13:39] Handling                                 method=GET url=/internal/containers/52/onstart ip=@ user=
DBUG[06-08|12:13:39] MountInstance started                    driver=zfs pool=lxcpool project=default instance=postfix
DBUG[06-08|12:13:39] MountInstance finished                   driver=zfs pool=lxcpool project=default instance=postfix
DBUG[06-08|12:13:39] Scheduler: container postfix started: re-balancing
INFO[06-08|12:13:39] Started container                        project=default name=postfix action=start created=2020-04-08T23:12:14-0500 ephemeral=false used=2020-06-08T11:01:40-0500 stateful=false
DBUG[06-08|12:13:39] Scheduler: network: vethe4522a89 has been added: updating network priorities
DBUG[06-08|12:13:39] Scheduler: network: vethdf45e64b has been added: updating network priorities
DBUG[06-08|12:13:39] MountInstance started                    driver=dir pool=lxd project=default instance=tinydns-net
DBUG[06-08|12:13:39] MountInstance finished                   driver=dir pool=lxd project=default instance=tinydns-net
DBUG[06-08|12:13:39] UpdateInstanceBackupFile started         driver=dir pool=lxd project=default instance=tinydns-net
DBUG[06-08|12:13:39] UpdateInstanceBackupFile finished        driver=dir pool=lxd project=default instance=tinydns-net
DBUG[06-08|12:13:39] MountInstance started                    driver=dir pool=lxd project=default instance=tinydns-net
DBUG[06-08|12:13:39] MountInstance finished                   driver=dir pool=lxd project=default instance=tinydns-net
INFO[06-08|12:13:39] Starting container                       used=2020-06-08T11:01:41-0500 stateful=false project=default name=tinydns-net action=start created=2017-04-13T12:29:00-0500 ephemeral=false
DBUG[06-08|12:13:39] Handling                                 url=/internal/containers/7/onstart ip=@ user= method=GET
DBUG[06-08|12:13:39] MountInstance started                    driver=dir pool=lxd project=default instance=tinydns-net
DBUG[06-08|12:13:39] MountInstance finished                   driver=dir pool=lxd project=default instance=tinydns-net
DBUG[06-08|12:13:39] Scheduler: container tinydns-net started: re-balancing
INFO[06-08|12:13:40] Started container                        name=tinydns-net action=start created=2017-04-13T12:29:00-0500 ephemeral=false used=2020-06-08T11:01:41-0500 stateful=false project=default
DBUG[06-08|12:13:40] Success for task operation: 7b4bf1a8-461f-4310-b1e8-c7a73e83063d
DBUG[06-08|12:13:40] Image already exists in the db           image=d125be3eded77d54fdeb2971e25b7f98b8e80a71f365353def505ac0c7c63803
DBUG[06-08|12:13:40] Image already exists on storage pool "rfast"
DBUG[06-08|12:13:40] Already up to date                       fp=d125be3eded77d54fdeb2971e25b7f98b8e80a71f365353def505ac0c7c63803
DBUG[06-08|12:13:40] Success for task operation: 5f4b38f0-1a3a-4982-a87d-1115adda6c4c
Thanks in advance for your help!

Can you show ps fauxww and snap changes?

snap changes:
ID   Status  Spawn                   Ready                   Summary
268  Error   yesterday at 17:11 CDT  yesterday at 17:32 CDT  Auto-refresh snap "lxd"
269  Error   yesterday at 20:51 CDT  yesterday at 21:12 CDT  Auto-refresh snap "lxd"
270  Error   today at 01:10 CDT      today at 01:31 CDT      Refresh "lxd" snap
271  Error   today at 01:34 CDT      today at 01:54 CDT      Remove "lxd" snap
272  Error   today at 03:00 CDT      today at 03:20 CDT      Refresh "lxd" snap
273  Error   today at 03:56 CDT      today at 04:17 CDT      Auto-refresh snap "lxd"
274  Error   today at 07:41 CDT      today at 08:01 CDT      Auto-refresh snap "lxd"
275  Error   today at 10:02 CDT      today at 10:23 CDT      Refresh "lxd" snap
276  Done    today at 10:30 CDT      today at 10:30 CDT      Running service command
277  Error   today at 10:34 CDT      today at 11:07 CDT      Refresh "lxd" snap
278  Error   today at 11:07 CDT      today at 11:28 CDT      Install "lxd" snap from file "lxd_15359.snap"
279  Error   today at 11:34 CDT      today at 11:54 CDT      Refresh "lxd" snap
280  Done    today at 11:55 CDT      today at 11:55 CDT      Running service command
281  Done    today at 12:05 CDT      today at 12:05 CDT      Running service command
282  Error   today at 12:14 CDT      today at 12:34 CDT      Refresh "lxd" snap
283  Error   today at 13:07 CDT      today at 13:27 CDT      Auto-refresh snap "lxd"
284  Error   today at 16:27 CDT      today at 16:27 CDT      Running service command
285  Done    today at 16:28 CDT      today at 16:28 CDT      Running service command
286  Done    today at 16:30 CDT      today at 16:30 CDT      Running service command
ps.fauxww.txt

So one thing that may not be helping is that you have a side-loaded LXD binary at /var/snap/lxd/common/lxd.debug.
You probably should remove that, then do systemctl reload snap.lxd.daemon, check ps fauxww again to confirm that LXD did get restarted and isn't using lxd.debug anymore, then attempt the refresh again.

Did
rm /var/snap/lxd/common/lxd.debug
systemctl reload snap.lxd.daemon
check with ps and lxd shows running as
lxd --logfile /var/snap/lxd/common/lxd/logs/lxd.log --group lxd --debug
(I had set debug to true from before)
same result as before:
INFO Waiting for snap.lxd.activate.service to stop.
2020-06-08T21:23:54-05:00 INFO snap.lxd.activate.service refused to stop, killing.
2020-06-08T21:24:00-05:00 INFO Waiting for snap.lxd.daemon.unix.socket to stop
last command repeats 20 times, etc., same as before
Wondering if there is a problem with the systemd files.  Here's what I've got in /etc/systemd/system:
snap-core18-1705.mount            snap-lxd-14890.mount     snap-lxd-15272.mount
snap-core18-1754.mount            snap-lxd-14954.mount     snap-lxd-15359.mount
snap-core-9066.mount                snap-lxd-15067.mount     snap.lxd.activate.service
snap-core-9289.mount                snap-lxd-15138.mount     snap.lxd.daemon.service
'snap-hello\x2dworld-27.mount'   snap-lxd-15161.mount     snap.lxd.daemon.unix.socket
'snap-hello\x2dworld-29.mount'   snap-lxd-15223.mount
Last three all point to Requires=snap-lxd-14954.mount
What signals a successful exit to "INFO Waiting for snap.lxd.daemon.unix.socket to stop" because the socket file is still there:
srw-rw----  1 root lxd      0 Jun  8 21:20 unix.socket

Oh, hold on, the error is about snap.lxd.active, not about the LXD daemon...

This morning the lxd daemon had stopped again, I assume as the result of an auto-refresh.  I had to restart the daemon with:
systemctl start snap.lxd.activate.service
and it answered back with:
Job for snap.lxd.activate.service canceled.
But the daemon did start at least. This is from the last log from the night before:
t=2020-06-09T00:17:37-0500 lvl=info msg="Received 'terminated signal', exiting"
t=2020-06-09T00:17:37-0500 lvl=info msg="Starting shutdown sequence"
t=2020-06-09T00:17:37-0500 lvl=info msg="Stopping REST API handler:"
t=2020-06-09T00:17:37-0500 lvl=info msg=" - closing socket" socket=/var/snap/lxd/common/lxd/unix.socket
t=2020-06-09T00:17:37-0500 lvl=info msg="Stopping /dev/lxd handler:"
t=2020-06-09T00:17:37-0500 lvl=info msg=" - closing socket" socket=/var/snap/lxd/common/lxd/devlxd/sock
t=2020-06-09T00:17:37-0500 lvl=info msg="Closing the database"
t=2020-06-09T00:17:37-0500 lvl=dbug msg="Stop database gateway"
t=2020-06-09T00:17:38-0500 lvl=dbug msg="Not unmounting temporary filesystems (containers are still running)"

Can you show systemctl -a?

The activate unit should only start once per system boot and should not be started manually, so I'm a bit confused as to why it seems to be holding the refresh.

My only thought is some kind of failure to note the destruction of the socket file. Does it have something to do with the containers still running? I can see that it is not being destroyed while snap.lxd.daemon.unix.socket is trying to stop.
systemctl.a.txt

Seems like I could just destroy the socket file manually and somehow have the systemd file stop command read as /bin/true but not sure exactly how to do that. I tried it and it didn't work but again, not sure what I'm doing there.

Ah yeah, that system isn't in a great shape here... Normally lxd.activate should be inactive/exited, unix.socket should always be active and service should be active if LXD is running.
Can you try:

echo "reload" > /var/snap/lxd/common/state
systemctl stop snap.lxd.daemon
systemctl start snap.lxd.daemon.unix.socket
systemctl start snap.lxd.activate

That should let you stop LXD without stopping any of the containers, then getting the unix socket back to working order and finally running activate as it would on startup which should then start LXD and get all 3 units in the desired state.

Did
echo "reload" > /var/snap/lxd/common/state
systemctl stop snap.lxd.daemon
systemctl start snap.lxd.daemon.unix.socket
systemctl start snap.lxd.activate
Answer:
Job for snap.lxd.activate.service canceled.
Attached is new sysctl -a after the above commands
systemctl.a.new.txt

Ok, systemd looks quite confused by that unit...
Can you show systemctl status snap.lxd.activate.service, journalctl -u snap.lxd.activate.service -n 30 and systemctl cat snap.lxd.activate.service?

Attached.  BTW, I had changed the TimeoutStopSec=10 on the snap.lxd.activate.service file.
cat.snap.lxd.activate.service.txt
journalctl.txt
status.snap.lxd.activate.service.txt

Are any of PID 1170 or 1087 still unning?

*running

Neither one is running. "lxc list" gives
Error: Get "http://unix.socket/1.0": dial unix /var/snap/lxd/common/lxd/unix.socket: connect: connection refused
but the unix.socket file is still there
looks like it went down about 90 minutes ago
t=2020-06-09T11:22:40-0500 lvl=info msg="Received 'terminated signal', exiting"
t=2020-06-09T11:22:40-0500 lvl=info msg="Starting shutdown sequence"
t=2020-06-09T11:22:40-0500 lvl=info msg="Stopping REST API handler:"
t=2020-06-09T11:22:40-0500 lvl=info msg=" - closing socket" socket=/var/snap/lxd/common/lxd/unix.socket
t=2020-06-09T11:22:40-0500 lvl=info msg="Stopping /dev/lxd handler:"
t=2020-06-09T11:22:40-0500 lvl=info msg=" - closing socket" socket=/var/snap/lxd/common/lxd/devlxd/sock
t=2020-06-09T11:22:40-0500 lvl=info msg="Closing the database"
t=2020-06-09T11:22:40-0500 lvl=dbug msg="Stop database gateway"
t=2020-06-09T11:22:40-0500 lvl=dbug msg="Not unmounting temporary filesystems (containers are still running)"

Can you show:

systemctl -a | grep lxd
netstat -lnp | grep unix.socket

OK, this is without restarting the daemon:
netstat -lnp | grep unix.socket is null, nothing returned
systemctl file is attached
systemctl.noreload.txt

Here's an ls of /var/snap/lxd
drwxr-xr-x 2 root root  2 Jun 12  2018 14954
drwxr-xr-x 2 root root  2 Jun 12  2018 14890
lrwxrwxrwx 1 root root  5 May  5 21:57 current -> 14954
drwxr-xr-x 7 root root 12 Jun  9 09:10 common

Ok, can you confirm that there is no LXD daemon running according to ps fauxww?
If there isn't, then in one terminal try running: lxd --debug --group lxd which should start LXD and then just hang as it's running.
With that running, in another terminal run lxd activateifneeded --debug to see if they can communicate and if there's anything weird going on there.

OK, no lxd was running, started as per instruction. Ran "lxd activateifneeded --debug" got
DBUG[06-09|15:12:45] Daemon has auto-started instances, activating...
DBUG[06-09|15:12:45] Connecting to a local LXD over a Unix socket
DBUG[06-09|15:12:45] Sending request to LXD method=GET url=http://unix.socket/1.0 etag=
DBUG[06-09|15:12:45] Got response struct from LXD
and then a json dump of the config file

Ok, so that looks correct.
Try:

Kill that manually started debug LXD daemon
systemctl start snap.lxd.daemon.unix.socket
lxc info

This should enable socket activation and then have lxc info trigger it, causing the daemon to start before it shows you the daemon info.

OK, got the text version of the config file. Shall I try "snap refresh lxd" ?

Well I went ahead and tried "snap refresh lxd" and still got the same results as my first post.

Looks like there's something really wrong with systemd...
If it's an option, a reboot may clear up whatever broken state there is.
If not, you may want to try systemctl mask snap.lxd.activate.service to get rid of that service which may or may not help snapd. But you'll need to remember to unmask it or LXD won't start on reboot.

Maybe this is some help:
If I run "snap stop lxd", lxd will exit, but if I try "snap start lxd" I get :
error: cannot perform the following tasks:

start of [lxd.activate lxd.daemon] (# systemctl start snap.lxd.activate.service snap.lxd.daemon.service

and them some messages like
Got message type=signal sender=org.freedesktop.systemd1 destination=n/a path=/org/freedesktop/systemd1 interface=org.freedesktop.systemd1.Manager member=JobRemoved cookie=12 reply_cookie=0 signature=uoss error-name=n/a error-message=n/a
Got result done/Resource temporarily unavailable for job snap.lxd.daemon.service
...more messages of the same with freedesktop.etc,etc
and then
Job for snap.lxd.activate.service canceled.
Got result canceled/Operation canceled for job snap.lxd.activate.service
Bus n/a: changing state RUNNING → CLOSED
)

start of [lxd.activate lxd.daemon] (exit status 1)

but the lxd daemon runs.
Also, this process remains:
/bin/sh /snap/lxd/14954/commands/daemon.start
and killing it just causes it to respawn
Any ideas?

Yeah, would need root access to poke at LXD and see what's up with it.
ssh-ed25519 AAAAC3NzaC1lZDI1NTE5AAAAIOhdeiF51bz5W+mPtpRYnXQRuLqimMPE5PBD1ab8APt6 cardno:000611576019

I'm OK with doing that but going to try one last thing. For whatever reason, I've got some apt sources for the old lxcfs daemon, et al running:
liblxc-common                3.0.3-0ubuntu1~18.04.1
liblxc1                             3.0.3-0ubuntu1~18.04.1
lxc                                   3.0.3-0ubuntu1~18.04.1
lxc-common                    2.1.1-0ubuntu1~ubuntu16.04.1~ppa1
lxc-desktop                     0.1
lxc-templates                  3.0.0-0ubuntu1
lxc-utils                           3.0.3-0ubuntu1~18.04.1
lxc1                                 3.0.0-0ubuntu2~ubuntu16.04.1~ppa1
Do you think this might have anything to do with my problems? If I purge them, will the snap version of those packages takeover? I've got a few containers left running under the old system but fairly confident I can move them over.
Thanks
lxcfs                                  3.0.3-0ubuntu1~18.04.2
python3-lxc                            3.0.1-0ubuntu1

No, having those packages would be harmless. You can certainly purge them as they would be completely unused right now, but they also can't really conflict with anything.

I'd like to try one last thing: manually removing all traces of snap and its elements and then reloading.  Tell me if this is right:
backup /var/snap/lxd/common/lxd
backup lxd config file
stop all lxc and lxd processes
apt purge snap
remove /var/snap directory
remove all systemd snap files
And then
Reinstall snap and lxd
reinitialize lxd from backup config file
stop snap, lxd
restore backup /var/snap/lxd/common/lxd
restart snap, lxd
cross fingers
Am I missing anything?
Thanks

Yeah, that should work assuming you're not using something too weird as a storage backend.

I manually removed all traces of snap from my system, redid all of my containers and all was going well until
snapd[9206]: storehelpers.go:438: cannot refresh: snap has no updates available: "core18", "snapd
"
And now I'm back to the same problem.
I had systemd debugging on so I'm including about 80 seconds of syslog from that point. It appears that something is triggering systemd to reload but it can't find the files and lxd is never restarted
lxc info gives
Error: Get "http://unix.socket/1.0": dial unix /var/snap/lxd/common/lxd/unix.socket: connect: connection refused
and snap refresh lxd gives repeated
2020-06-15T21:28:36-05:00 INFO Waiting for snap.lxd.daemon.unix.socket to stop.
and then repeated
2020-06-15T21:38:36-05:00 INFO Waiting for snap.lxd.daemon.service to stop.
Ending with
error: cannot perform the following tasks:

Mount snap "lxd" (15564) (snap-lxd-15564.mount failed to stop: timeout)
Stop snap "lxd" services (snap.lxd.daemon.unix.socket failed to stop: timeout)

I can restart the service with service snap.lxd.daemon start
I'm attaching 80 seconds worth of the syslog so you can see what systemd is doing.
Thanks for any advice!
syslog.80sec.txt

We're going to need to look at such a system directly, clearly none of the usual logs and stuff we looked at are particularly useful and you're the only one who has ever reported this so it's not something we can reproduce on our side.

@bakerjalexander any update on this?

Closing for inactivity. I've had a colleague run into something very very similar where snapd was stating "Waiting for XYZ to stop" yet all units were in the correct stopped state already. This suggests some kind of bug in snapd.
We'll have the snapd team investigate that colleague's system so they can hopefully sort this out.
If anyone else hits this, feel free to comment here so we can get an idea of the scale of the problem.
Also if you found a way around it, please let us know :)

Thanks. Yeah I gave up on this.  Apparently the refresh issue is a problem
for many.  I found a post on how to stop the thing from refreshing on its
own and I'll pass it along for anybody that stumbles on this post.
Add
1 1 1 * * /usr/bin/snap set system refresh.hold="2030-01-01T01:00:00-01:00"
To your crontab
I'm going to work on a script to manually download and install the newest
version of lxd without using snap refresh.  It appears that the only thing
that need happen is to update a systemd file, rsync everything but the
config/db files to /var/snap/lxd and change a symlink.
I really wish snap could just duplicate "apt purge" or "apt install
--reinstall." When I did snap remove myself I ran into the same issue with
the waiting on the socket to close thing.
Snap should be very useful to lxd and linux in general, but it's definitely
got issues.
Anyways, I appreciate the time you put in on this and I'm sorry it was
fruitless.
John
On Fri, Jun 26, 2020 at 2:11 PM Stéphane Graber<EMAIL_ADDRESS>wrote:

Closing for inactivity. I've had a colleague run into something very very
similar where snapd was stating "Waiting for XYZ to stop" yet all units
were in the correct stopped state already. This suggests some kind of bug
in snapd.
We'll have the snapd team investigate that colleague's system so they can
hopefully sort this out.
If anyone else hits this, feel free to comment here so we can get an idea
of the scale of the problem.
Also if you found a way around it, please let us know :)
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/lxc/lxd/issues/7500#issuecomment-650349465, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AEW6VU7CPDYHRL6YO45DNGLRYTXENANCNFSM4NYTOCTQ
.

After working with the snappy team, the issue I was seeing was found that it's due to having debug in the kernel command line.
https://bugs.launchpad.net/snapd/+bug/1885597

Can confirm. Removed debug from the kernel command line and all is well!
Thanks!
On Tue, Jun 30, 2020 at 8:44 AM Chris Johnston<EMAIL_ADDRESS>wrote:

After working with the snappy team, the issue I was seeing was found that
it's due to having debug in the kernel command line.
https://bugs.launchpad.net/snapd/+bug/1885597
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/lxc/lxd/issues/7500#issuecomment-651800013, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AEW6VU4O2I75WV4N5AKNWCTRZHT37ANCNFSM4NYTOCTQ
.

For anyone looking for a work around that allows keeping debug as a kernel parameter see this comment on the above mentioned bug report. The key is to use systemd.log_level=info on the commandline to override systemd interpretation of the debug parameter.


Add deprecation warning

per discussion on https://github.com/docker/libtrust/issues/55#issuecomment-230529319

LGTM

ping @dmcgowan ptal

Preferred waiting until we had some migration but I suppose the language is suitable for the current state.
LGTM

oh, thanks! yeah, makes sense, but I think it doesn't hurt to have a notice at least


User default browser when opening file:/// URLs of HTML pages

Windows Terminal version
1.18.3181.0
Windows build number
10.0.19045.3693
Steps to reproduce
Ctrl+Click a file:/// URL that points to an HTML page
Expected Behavior
file:/// URLs of HTML pages should be launched in the default browser, not some other
Actual Behavior
If you have an http:// URL, the default browser is properly launched.
But if you have a file:/// URL, a different browser is launched.
If you for example run a Gradle build with failing tests, you get a file:/// URL pointing at the test report HTML.
Opening this starts not the default browser, but a different browser.

Thanks for filing!
Terminal just tells the desktop shell to open the file. Because it points at a file, it will use the file handler associated with .html files. It will not use the default handler for http and https URLs, because it is not one of those.
You can configure the default handler for .html files in Settings. Search for "choose a default app for each type of file".

Oh, thanks, you are fully right, sorry.
Unfortunately, the BrowserSelector App is not selectable there, but I guess its author needs to do something for that.


ChRoMiUm EmBeDdEd FrAmEwOrK wAs NeVeR iNiTiAlIzEd.


Remove unnecessary check for nil CString

@noxiouz points out that we don't need to check for a nil result from
C.CString(), since an out-of-memory condition causes a runtime panic
instead.
Signed-off-by: Nalin Dahyabhai<EMAIL_ADDRESS>(github: nalind)

LGTM

LGTM

LGTM


[Bug]  sol macro doesn't handle solidity idents that are rust keywords

Component
json-abi, sol! macro, syn-solidity
What version of Alloy are you on?
No response
Operating System
None
Describe the bug

https://etherscan.io/address/0xdef1c0ded9bec7f1a1670819833240f027b25eff#code

Requires a bigger refactor, will be fixed with #82

@DaniPopes I have a branch that deals with this workaround (using r# when needed in SolIdent) if you want me to push it up


Add experimental support for aggregate type declarations

This PR adds a type keyword that can be used to declare user-defined type symbols, as well as a parser and grammar for describing custom structure, typed array, and union types. The types that can be declared in a type statement (or as the type clause of a param statement) include:

literal types and literal type unions (e.g., true, 'fizz'|'buzz', 1|2|3, {foo: 'bar'}|{ping: 'pong'})type booleanLiteral = true
type integerLiteral = -100
type unionOfStringLiterals = 'fizz'|'buzz'|'pop'

typed arrays (including arrays of a mixed type but with strictly defined allowed values)type arrayOfInts = int[]
type intsBuriedUnderAnAvalancheOfArrays = int[][][][][][][][][][]
type mixedTypeArray = (1|false|null|{ping: 'pong'}|'It was the best of times'|'It was the worst of times')[]

objects with known properties and individual property schematatype myObject = {
    requiredProp: string
    optionalProp?: string[]
    recursiveProp?: myObject
    inlineObjectProperty: {
        nested: 'fizz'|'buzz'
    }
}

param inlineObjectParam {
    property: string
}

Types are included in the compiled ARM JSON template and will be enforced by the ARM runtime. Everything is disabled by default and requires an explicit feature flag to opt in. Also, map types and tuple types are not included in this PR. Given those caveats, this PR works towards #4158 but does not resolve it.
Microsoft Reviewers: Open in CodeFlow

Found an issue where assigning a value to a tagged union doesn't work:

Found an issue where assigning a value to a tagged union doesn't work:

Good catch! I should point out though that tagged unions aren't supported at all; unions have to be composed of literal values and are translated into allowedValues constraints. Tagged unions will probably use the same syntax in Bicep, but there's no backing representation in ARM JSON yet.

Found an edge case that makes me think maybe we should block using keywords as symbolic names:

Found an edge case that makes me think maybe we should block using keywords as symbolic names:

I can add an error for type resource = (similar to the error that is currently raised for type string = or type int =), but I'm not sure if I can get rid of the parser error. param myParam resource 'RP/resourceType@apiVersion' will parse just fine on the main branch, as the feature flag for resource-typed params and outputs isn't checked at the parser level but only in the type manager. The parser is hard coded to look for a resource type immediately following the resource keyword in a param statement's type clause, and the right hand side of the equals sign in a type declaration follows the same rules.

I can add an error for type resource = (similar to the error that is currently raised for type string = or type int =), but I'm not sure if I can get rid of the parser error. param myParam resource 'RP/resourceType@apiVersion' will parse just fine on the main branch, as the feature flag for resource-typed params and outputs isn't checked at the parser level but only in the type manager. The parser is hard coded to look for a resource type immediately following the resource keyword in a param statement's type clause, and the right hand side of the equals sign in a type declaration follows the same rules.

I think as long as type resource = is blocked, the parser error will be legit since there is no ambiguity.


Add support for delayed returns

It would be nice to have the ability to delay showing your function returns until after Clintons 33k emails have been revealed, or until America has been made sufficiently great.

See a76f078


Added Contact Page

Hello @akshitagupta15june ,
I have added the Contact Page
Screenshot -

It is ready to merge.

mention the issue number, were u assigned?

It's Issue No. #858

hey u were not assigned this issue so I am closing this pr
I have already said without being assigned please don't create pr

Okay


Add find.descendant API to support find descendants of an element by passing the current element finder and the finder of descendant.

A fix related to #7643.
Thanks for reviewing.

Yay, CLA bot is happy.
LGTM. Please feel free to push the "squash and merge" button once Travis goes green, or let me know if you don't see that button and I can do it for you.

I can't see the button, I guess because I don't have "write access".

Ok, I landed it for you! Thanks!

Thank you!


msi/gl62: init

This PR initialize support for MS-16J61 Laptop Motherboard with unified BIOS of E16J6IMS, which includes:

MSI GL62 6QD
MSI GL62 6QC
MSI CX62 6QD
MSI CR62 6M

Thanks. I included your change in https://github.com/NixOS/nixos-hardware/pull/422


Blog app: add API endpoints

Create an API endpoint to list all posts for a user.
Create an API endpoint to list all comments for a user's post.
Create an API endpoint to add a comment to a post. Remember that the owner of the comment is the user that makes it; it should not be set by passing a parameter.
Your API endpoints should receive JSON and respond JSON as well.

Link for Loading Posts: http://localhost:3000/api/v1/users/10/posts (User id :10)
Link for Loading Comments: http://localhost:3000/api/v1/users/10/posts/5/comments (User id :10, Post Id: 5)
Link for Posting(Use POST) Comments:  http://localhost:3000/api/v1/users/10/posts/5/comments (User id :10, Post Id: 5)
😄

@danmainah Thanks


Enrich and organize PUDL data dictionary

We have a simple data dictionary documenting the PUDL DB automatically generated in our docs build now. Using it a bit in writing some code already, so it's definitely useful!  Right now it's got:

[x] field name
[x] field type
[x] field description

I'm finding that it would also be helpful to have:

[x] Fields ordered alphabetically (it's kinda random right now)
[ ] But put primary key fields first, with some indication that they are primary key columns.

Once we get the new metadata system up and running this should pretty easy I think.

Primary key fields with some kind of indication for sure!
Suggest ordering PK based on datatype first, then alphabetically.
For fields, split into words using '_', then build lists based on word groupings (ignoring common works like "for", "of" etc).  Also break the first word on studlyCaps if they are present.   If there's a heavy use of a common word (typically first, second, or last), those fields should group together alphabetically.

we will need to fully redo this when we have our new metadata structure


403 error when trying to add integration

Version of the custom_component

v0.1.8
Installation method (hacs / manual)
HACS
Installation method of hass (venv, docker, hassio,...)
docker
Configuration
N/A, added via integration
Describe the bug
When trying to add the integration, it takes a couple of minutes and the logs subsequently show a 403 error. All added entities are "unavailable" and lots of them are missing (SoC etc).
I do also have the Cupra WeConnect integration installed for my other half's car, not sure if that's conflicting?
I have tried removing the integration, reinstalling it, restarting HA (also between removing and reinstalling) but to no avail. Anyone else have any idea how to fix this?
Debug log

Logger: homeassistant.components.number
Source: helpers/update_coordinator.py:258
Integration: Number (documentation, issues)
First occurred: 21:13:20 (1 occurrences)
Last logged: 21:13:20

Error while setting up volkswagen_we_connect_id platform for number
Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/helpers/update_coordinator.py", line 283, in _async_refresh
    self.data = await self._async_update_data()
                ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/helpers/update_coordinator.py", line 242, in _async_update_data
    return await self.update_method()
           ^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/config/custom_components/volkswagen_we_connect_id/__init__.py", line 53, in async_update_data
    await hass.async_add_executor_job(_we_connect.update)
  File "/usr/local/lib/python3.11/concurrent/futures/thread.py", line 58, in run
    result = self.fn(*self.args, **self.kwargs)
             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.11/site-packages/weconnect/weconnect.py", line 193, in update
    self.updateVehicles(updateCapabilities=updateCapabilities, updatePictures=updatePictures, force=force, selective=selective)
  File "/usr/local/lib/python3.11/site-packages/weconnect/weconnect.py", line 202, in updateVehicles
    data = self.fetchData(url, force)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.11/site-packages/weconnect/weconnect.py", line 388, in fetchData
    raise RetrievalError(f'Could not fetch data. Status Code was: {statusResponse.status_code}')
weconnect.errors.RetrievalError: Could not fetch data. Status Code was: 403

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

Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/helpers/entity_platform.py", line 353, in _async_setup_platform
    await asyncio.shield(task)
  File "/config/custom_components/volkswagen_we_connect_id/number.py", line 28, in async_setup_entry
    await coordinator.async_config_entry_first_refresh()
  File "/usr/src/homeassistant/homeassistant/helpers/update_coordinator.py", line 258, in async_config_entry_first_refresh
    raise ex
homeassistant.exceptions.ConfigEntryNotReady: Could not fetch data. Status Code was: 403

same for me

Same here. Even increasing the interval to 90s does not help. I have registered two accounts.

Hi same problem for me.
Isn't related to ? :

"We'd like to inform you that the ‘We Connect’ smartphone app will be deactivated and operations will cease on 08/11/2023.
From then on, you will be able to use the Volkswagen app to access We Connect functions previously run by the We Connect app. You can download the Volkswagen app here in the Google Play store or here in the Apple Store."

I’ve had the integration working for a long time, but am now seeing 403 error too.

Me too. Here are the logs I’ve got.
This error originated from a custom integration.

Logger: custom_components.volkswagen_we_connect_id
Source: helpers/update_coordinator.py:290
Integration: Volkswagen We Connect ID
First occurred: 06:22:04 (2 occurrences)
Last logged: 06:22:04

Unexpected error fetching volkswagen_we_connect_id data: Could not fetch data. Status Code was: 403
Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/helpers/update_coordinator.py", line 290, in _async_refresh
    self.data = await self._async_update_data()
                ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/helpers/update_coordinator.py", line 246, in _async_update_data
    return await self.update_method()
           ^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/config/custom_components/volkswagen_we_connect_id/__init__.py", line 53, in async_update_data
    await hass.async_add_executor_job(_we_connect.update)
  File "/usr/local/lib/python3.11/concurrent/futures/thread.py", line 58, in run
    result = self.fn(*self.args, **self.kwargs)
             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.11/site-packages/weconnect/weconnect.py", line 193, in update
    self.updateVehicles(updateCapabilities=updateCapabilities, updatePictures=updatePictures, force=force, selective=selective)
  File "/usr/local/lib/python3.11/site-packages/weconnect/weconnect.py", line 202, in updateVehicles
    data = self.fetchData(url, force)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.11/site-packages/weconnect/weconnect.py", line 388, in fetchData
    raise RetrievalError(f'Could not fetch data. Status Code was: {statusResponse.status_code}')
weconnect.errors.RetrievalError: Could not fetch data. Status Code was: 403

Same here. Lots of 403 errors since yesterday, and trying to set up the integration from scratch didn't help either:
Logger: custom_components.volkswagen_we_connect_id.config_flow
Source: custom_components/volkswagen_we_connect_id/config_flow.py:65
integration: Volkswagen We Connect ID
First occurred: 18:14:11 (1 occurrences)
Last logged: 18:14:11
Unexpected exception

Traceback (most recent call last):
  File "/config/custom_components/volkswagen_we_connect_id/config_flow.py", line 65, in async_step_user
    info = await validate_input(self.hass, user_input)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/config/custom_components/volkswagen_we_connect_id/config_flow.py", line 40, in validate_input
    await hass.async_add_executor_job(update, we_connect)
  File "/usr/local/lib/python3.12/concurrent/futures/thread.py", line 58, in run
    result = self.fn(*self.args, **self.kwargs)
             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/config/custom_components/volkswagen_we_connect_id/__init__.py", line 223, in update
    api.update(updatePictures=False)
  File "/usr/local/lib/python3.12/site-packages/weconnect/weconnect.py", line 194, in update
    self.updateVehicles(updateCapabilities=updateCapabilities, updatePictures=updatePictures, force=force, selective=selective)
  File "/usr/local/lib/python3.12/site-packages/weconnect/weconnect.py", line 232, in updateVehicles
    raise catchedRetrievalError
  File "/usr/local/lib/python3.12/site-packages/weconnect/weconnect.py", line 216, in updateVehicles
    vehicle = Vehicle(weConnect=self, vin=vin, parent=self.__vehicles, fromDict=vehicleDict, fixAPI=self.fixAPI,
              ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.12/site-packages/weconnect/elements/vehicle.py", line 133, in __init__
    self.update(fromDict, updateCapabilities=updateCapabilities, updatePictures=updatePictures, selective=selective)
  File "/usr/local/lib/python3.12/site-packages/weconnect/elements/vehicle.py", line 227, in update
    self.updateStatus(updateCapabilities=updateCapabilities, force=force, selective=selective)
  File "/usr/local/lib/python3.12/site-packages/weconnect/elements/vehicle.py", line 338, in updateStatus
    data: Optional[Dict[str, Any]] = self.weConnect.fetchData(url, force)
                                     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.12/site-packages/weconnect/weconnect.py", line 399, in fetchData
    raise RetrievalError(f'Could not fetch data. Status Code was: {statusResponse.status_code}')
weconnect.errors.RetrievalError: Could not fetch data. Status Code was: 403


Best way to trace cached LLM and tool calls

Hi!
In our application/framework, we have a feature that caches HTTP calls to external APIs (such as OpenAI or various APIs used by tools). It does so by monkey-patching HTTP clients, such as requests, so that when a request is made it caches the response, and next time it retrieves the response directly from cache.
We want such behavior to be visible in Lunary traces, e.g. when an LLM call is made and the response is taken from cache instead of the API, an additional item is appended to the trace:

Is it possible to achieve this by calling track_event() from the cache-managing function? How would it determine its parent?

Can it eg retrieve the id of the parent from the headers of the http request it's caching?
We are using Lunary wrappers for all the entities that generate the http calls we are caching, so there should always be a parent scope id, the question is how to get it to the caching layer

Here is the code where we think we can insert a track_event call: https://github.com/ShoggothAI/motleycrew/blob/main/motleycrew/caching/http_cache.py#L161
Entry point in case you need to run it: https://github.com/ShoggothAI/motleycrew/blob/main/examples/single_llama_index.py

Hi @whimo and @ZmeiGorynych,
I have updated our Python SDK to provide the latest run ID. You can use lunary.run_ctx.get() to retrieve it.
Regarding the implementation for cached calls on Lunary, we have decided to take a different approach. Instead of adding a child, we are considering displaying it like this:

(Please note that this design is not final)
In the latest version of the SDK, you can pass a metadata dictionary to track_event. To indicate a cached call, you can call track_event(..., metadata={"cache": True}) for the LLM end event. You can try this solution by upgrading lunary-py to version 1.0.10.
With this change, you will be able to see the metadata on the right:

If this approach works for you, we can implement the frontend today with a similar design as shown on the first screenshot above.
Please let me know your thoughts on this.

This looks great, thank you!
The only limitation I can think of is that we also support Langchain agents and use Lunary natively with them (no track_event calls). How shall we pass the metadata in this case?

Can you pass the metadata where you do the langchain invoke? It will be passed down to lunary automatically

I've added the UI for cached calls:

Please let me know if you can make it work, especially with Langchain.

Thank you! We'll try and get back to you

Hi @hughcrt, we ran into a problem with this approach which we didn't realize earlier. When an LLM call is made, we don't know beforehand if the cache will be hit, and moreover the agent (or LLM wrapper) has no info on whether the response was taken from cache. And I suspect that even if we could pass this info up the call stack, it would be painful and unreliable to implement it for every agent or LLM interaction library.
So we think that reporting cache hits directly from the caching manager via track_event() would be much more coherent and straightforward to implement. Regarding this,

We still like the pretty UI you implemented for indicating caching. Is it possible to marry it with this approach, maybe by reporting an event of a special type and merging it with its parent under the hood? Of course, we can still do without it, but your suggestions on which particular event type we should report are very welcome.
It seems a little hack-y to report the caching event start and immediately report its end via two separate track_event() calls. Again, it's not really a problem, but I believe it would be useful to support zero-time events.

Hi @whimo,
You only need to send the metadata in the track_event corresponding to the llm end event. You would know at that time if it was cached, right?
We could easily at support for zero-time events, but that would still require two calls: one for llm start, and one to update this event to say it was a cached event.
In my opinion, it's more straightforward to use llm end for that, especially because cache hits still take some time (0.01s in our example).
What do you think?

You only need to send the metadata in the track_event corresponding to the llm end event. You would know at that time if it was cached, right?

Technically we do know that, but I know no simple way to pass this knowledge to the point where we fire the llm-end or tool-end. The callbacks recieve limited data that is framework-specific and AFAIK does not include low-level request info. Also, we will have to manually support this for all variety of tools and LLMs that we cache.
The approach that I propose is much more universal. For example,
| track_event(llm start)
|| <request to e.g. OpenAI API happens>  // <- we don't control this part!
||| <cache hit occurs>
|||| track_event(cache start, parent=lunary.run_ctx.get())
|||| track_event(cache end)  // would be great to merge these two calls into one
||| <cached response is returned>
|| <cached response is returned>  // <- we don't control this part either
| track_event(llm end)

This would work regardless of the framework used and whether the events are fired manually or automatically e.g. via Langchain integration.

You can now use lunary.track_event("llm", "update", lunary.run_ctx.get(), metadata={"cache": True}). You don't need to update the SDK, we handle everything on the latest version of the server.
Please reopen the issue if you have any problem making it work.

🔥
Looks like what we needed, thank you!

Hi @hughcrt, we ran into one more problem, so I'm reopening this as you instructed.
Callback handlers use their own event queue (defined here). When we call track_event from the cache manager, it uses Lunary's global queue by default (defined here).
So the start and end events go into the callback handler's queue, and the update events with cache=True go into the global one. It seems like the update events are not linked correctly to their parents because they end up in different queues (everything works if we track the start/end events manually using the global queue).
So we need to figure out how to use same queue as the callback handler for reporting cache events. I see two possible ways:

To make LunaryCallbackHandler use the global queue (either by reusing it here or by allowing to provide queue as a constructor argument).
To store the queue in run_ctx so it can be accessed from our cache manager.

Please share your thoughts on this.

Oops, seems like I don't have the rights to reopen the issue, so I just hope you'll recieve a notification 😄

Hi @whimo, I will have a look and get back to you with a solution 🙂

Hi @hughcrt, have you figured anything out? :)

Hi @whimo, sorry the delay. In version 1.0.20, the callback handler now uses the global event queue. I will get back to you in a bit, when the update using context variables will be ready

@whimo, in version 1.0.21, the event queue is in a context var, so it should solve your problem. Let me know if that works for you 🙂

Hi @hughcrt, everything seems to be working as expected, thank you for your help!


Unexpected value 'SamplePipe' declared by the module 'AppModule'

When working on new Angular2.0 project (check project's package.json), it gives the error:

Unexpected value 'SamplePipe' declared by the module 'AppModule'

Project's dependencies:
"dependencies": {
    "@angular/common": "2.0.0",
    "@angular/compiler": "2.0.0",
    "@angular/core": "2.0.0",
    "@angular/forms": "2.0.0",
    "@angular/http": "2.0.0",
    "@angular/platform-browser": "2.0.0",
    "@angular/platform-browser-dynamic": "2.0.0",
    "@angular/router": "3.0.0",
    "core-js": "^2.4.1",
    "rxjs": "5.0.0-beta.12",
    "ts-helpers": "^1.1.1",
    "zone.js": "^0.6.23"
  },
  "devDependencies": {
    "@types/jasmine": "^2.2.30",
    "angular-cli": "1.0.0-beta.15",
    "codelyzer": "~0.0.26",
    "jasmine-core": "2.4.1",
    "jasmine-spec-reporter": "2.5.0",
    "karma": "1.2.0",
    "karma-chrome-launcher": "^2.0.0",
    "karma-cli": "^1.0.1",
    "karma-jasmine": "^1.0.2",
    "karma-remap-istanbul": "^0.2.1",
    "protractor": "4.0.5",
    "ts-node": "1.2.1",
    "tslint": "3.13.0",
    "typescript": "2.0.2"
  }

App Module's code:
import { BrowserModule } from '@angular/platform-browser';
import { NgModule } from '@angular/core';
import { FormsModule } from '@angular/forms';
import { HttpModule } from '@angular/http';

import { AppComponent } from './app.component';
import { PROVIDERS, PIPES } from 'new-library';
@NgModule({
  declarations: [
    AppComponent,
    PIPES
  ],
  imports: [
    BrowserModule,
    FormsModule,
    HttpModule
  ],
  providers: [PROVIDERS],
  bootstrap: [AppComponent]
})
export class AppModule { }

I didn't change anything in the files that were generated using the generators. Just used "npm link" to register locally, and then linked to the test project to test the library in development environment.

Im having the same issue with npm link

This seems to be an issue related to Webpack.
Angular CLI
If you use an Angular CLI generated project, you can resolve this manually by editing angular-cli/models/webpack-build-common.ts in your node_modules directory and adding the following line under the extensions key:
modules: [path.resolve(projectRoot, 'node_modules')]

You can read more details here. There seems to be a fix in the Angular CLI repository so a recent version of Angular CLI will probably fix this automatically.
Angular 2 Webpack Starter
If you are using Angular 2 Webpack Starter (instead of an Anguler CLI project) you can resolve it by changing:
modules: [helpers.root('src'), 'node_modules']

to:
modules: [helpers.root('src'), helpers.root('node_modules')]

in your Webpack configuration file.
You can read more details here.
Can you try and see if this works for you? Thanks!

Hi all,
Any idea how someone not using webpack (and using SystemJS instead) can solve that issue?
Cheers!
Sacha

Hi all,
Any idea how someone not using webpack (and using SystemJS instead) can solve that issue?
Cheers!
Sacha

@sachanacar — Have you found a solution yet for SystemJS? Thanks!

Version 8.1.0 of this generator has been released, aligning with the latest Angular Package Format, which should solve this issue.
Feel free to re-open and report back if you experience issues with v8.1.0.
Thanks again for your great feedback! 👍

I have an issue with "Unexpected value 'SampleModule' imported by the module 'AppModule'"(got here from https://github.com/jvandemo/generator-angular2-library/issues/22) with version 11.1.0.


Build system fixes on linux

Feature or improvement description
Fixes issues with installing and building on Linux, especially simulink interface
Impacted areas of the software
Build system
Additional supporting information
Installing the C++ interface failed on linux due to a typo in the file named SC.h in CMakeLists.txt I have changed it from SC.H -> SC.h
This problem probably doesn't show up on windows as it's file system is case insensitive
I also fixed an issued with building the simulink S-Function on linux. mex on linux does not use COMPFLAGS, you must use CFLAGS or CXXFLAGS, also the -MT option does something very different in gcc than visual studio C++

@bjonkman could you check out these changes to the Simulink API build system?

all tests passing on this branch for me see results here
Can we consider merging please

@reos-rcrozier, I'll merge this as soon as GH actions completes.  These changes should make no difference to GH since it is just in the create_sfunc.m that isn't run in testing.
I'm letting the tests run mostly to see if I can learn anything about why GH actions is failing for us.

OK, thanks!


Power BI custom visuals code unable to build successfully

Trying to explore the custom visuals code.
But getting error while building the solution as below -
The specified path, file name, or both are too long. The fully qualified file name must be less than 260 characters, and the directory name must be less than 248 characters.

If you are working in VS 2015 then do this (as described in instruction):
2.   Right click on the project root folder then select 'Property Pages'. In the window opened select 'Build' and then in 'Before running startup page' select 'No Build'.

Already done this as a part of the initial setup. But still facing this issue.


installation failed

PHP ver 7.3
Codeigniter ver 4.1.2
Problem 1
- Root composer.json requires hermawan/codeigniter4-datatables ^0.5.0 -> satisfiable by hermawan/codeigniter4-datatables[v0.5.0].
- hermawan/codeigniter4-datatables v0.5.0 requires codeigniter4/framework ^4 -> satisfiable by codeigniter4/framework[4.0.0, ..., v4.1.2] from composer repo (https://repo.packagist.org) but codeigniter4/framework[1.0.0+no-version-set] from root package repo has higher repository priority. The packages with higher priority do not match your constraint and are therefore not installable. See https://getcomposer.org/repoprio for details and assistance.

Do you have any suggestion how should composer.json?
It's look fine here. or maybe I'm not sure what you mean...


Can't delete unused strings files

I added the following to the end of my pod file:
prepare_command = <<-CMD
SUPPORTED_LOCALES="['base', 'sv', 'en']"
find . -type d ! -name "*$SUPPORTED_LOCALES.lproj" | grep .lproj | xargs rm -rf
CMD
But no .lproj files are deleted. Am I doing something wrong?
The .strings files seems to be located in FormatterKit/AddressFormatter/Resources/[lang].lproj. Is it possible that the delete script doesn't manage to find them?

I managed to solve it by using this script instead:
pre_install do |installer|
    supported_locales = ['base', 'sv', 'en']

    Dir.glob(File.join(installer.sandbox.pod_dir('FormatterKit'), '**', '*.lproj')).each do |bundle|
        if (!supported_locales.include?(File.basename(bundle, ".lproj").downcase))
            puts "Removing #{bundle}"
            FileUtils.rm_rf(bundle)
        end
    end
end


Added p5.js Tutorial 9.9 file, and a contribution

My contribution: Prim's Algorithm Visualized

Thank you for this!


Discussion: Netlify CMS Office Hours

In order to increase engagement with the community we would like to discuss the possibility of having office hours every week/two weeks.
Purpose
Provide people with an opportunity to ask questions, provide feedback and contribute to the protect.
Mechanism
Zoom?
Agenda Proposals

Collect questions before hand, answer the most upvoted ones.
Demos of community projects/new features.
Acknowledge contributors.

Code Of Conduct

Be nice to everyone :)
Always open to new people.
A single person should not take control of the conversation.

Technicalities

Share recordings and notes.

Not a

Support channel - we can use issues for that so due to meetings time restrictions and better long term documentation.

Thoughts? Ideas?

I think it's a great idea.

Yes a great idea!

So, when is this party going to start!? 🎉

I'll schedule something this week.

Does next Monday (April 13) at 5PM UTC work?

Works for me. What are we using? Zoom, Slack?

I’ll post a zoom link on the slack on Monday and link from here to avoid zoom bombing.

Does next Monday (April 13) at 5PM UTC work?

Let's push for 5:30PM UTC if that's ok.

Works for me 4/13/20 @ 5:30PM UTC

This is the google calendar event (still without the zoom link):
https://calendar.google.com/event?action=TEMPLATE&tmeid=NHFoNGU4NXUxamduNnM1YmZpNWswa3ZpaWkgZXJlekBuZXRsaWZ5LmNvbQ&tmsrc=erez%40netlify.com

Google Calendar event: https://calendar.google.com/event?action=TEMPLATE&tmeid=M2czbGJzczV2ZThxbzJoZjU4aWVtZm1xZDEgbmV0bGlmeS5jb21fODlnMGlnaGZjNTRmN2RoNXA0ZnFtdG10NDRAZw&tmsrc=netlify.com_89g0ighfc54f7dh5p4fqmtmt44%40group.calendar.google.com

Zoom link available here https://netlifycms.slack.com/archives/CPMJH823F/p1586798252119400

Notes and recording: https://drive.google.com/drive/folders/13hdsi1GBgtHaTlndEJr3YwFdLHmnzD9u

Is this still going on or did you guys wrap up? FYI, I can not see the zoom link @erezrokah posted because of not having access to the slack channel

Hi @paultannenbaum, the meeting was from 5:30 PM UTC to 6:00 PM UTC. You can join the slack here https://www.netlifycms.org/chat.
I don't want to post the link publicly here as to avoid zoom bombing.

I'd be open to joining one of these

@erezrokah Is the slack still publicly available? All the links around the site lead to a slack page that says the link is currently not active.

Thanks for raising this @Pearce-Ropion, let me check if anything changed there

Any scheduled meeting coming up soonish..?

Closing as stale and/or outdated.


add update cmd

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

0 of 17 (0.0%)  changed or added relevant lines in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage decreased (-0.1%) to 38.711%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

pkg/cli/cmd/update.go
0
17
0.0%

Totals

Change from base Build<PHONE_NUMBER>:
-0.1%

Covered Lines:
1147

Relevant Lines:
2963

💛  - Coveralls


More unit tests for exporter.go

Description
More unit tests for exporter.go
Type of change

Unit tests (no changes in the code)

Testing steps
Done on CI.
Checklist

[ ] make before_commit passes
[ ] updated documentation wherever necessary
[ ] added or modified tests if necessary
[ ] updated schemas and validators in insights-data-schemas in case of input/output change

Codecov Report

Merging #86 (d429526) into master (cf29399) will increase coverage by 3.58%.
The diff coverage is 50.00%.

@@            Coverage Diff             @@
##           master      #86      +/-   ##
==========================================
+ Coverage   46.78%   50.37%   +3.58%
==========================================
  Files           6        6
  Lines         669      671       +2
==========================================
+ Hits          313      338      +25
+ Misses        330      307      -23
  Partials       26       26

Impacted Files
Coverage Δ

exporter.go
30.50% <50.00%> (+13.93%)
:arrow_up:

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 cf29399...d429526. Read the comment docs.


Improvements to URL Asset import

Expected Behavior
When importing assets, I would like to know more about what assets are skipped and what row in the excel file listed them.
Actual Behavior
Some level of detail is provided, but nothing shows up for skipped assets in the detailed report.  Also, there are other cases which are completely unreported which would be helpful to determine if the file has bad data in it.

Found an NPE in another corner case.


Detect mongoid version to use correct method.

"default_session" is replaced with "default_client" in mongoid version >= 5.0.0
This would make database_cleaner run with older versions of Mongoid.

@P9GIT Great, thanks! 👍


Dataframe view: column visibility editor

Add hook to SpaceViewClass to allow adding "stuff" to the view title bar
Use it to display a list of check box for visibility control

Concept:

Icon next to the component to hide the column

https://github.com/user-attachments/assets/5b3d976d-6787-44c6-9c3c-23ab8fba37f1

To unhide (and also hide) use the btn in the title bar:

Decision making update:
Separate UI for visibility of components from visibility of components.
Implications for now:

It is only possible to add/remove entity via entity path section. This means there is no implicit show/hide functionality for entity (unless all components are hidden from one entity).
Visibility of components is only defined through show/hide UI. It is not the same as add/remove, neither it is connected or united with the entity path filter (so instead of having an option to ‘add/remove component AND hide/show component, to only use the latter for interacting with visibility in the UI. what exactly does it mean via DataOut-don't have an opinion there, but whatever it is - to only expose it as one action)
Pros:
Reduces complexity
Decoupling query from looks (if the show/hide is looks?)
Smaller changes will allow to add value faster (instead of coupling it with entity path etc)
Also valid for entities as rows in the future!
Cons:
Does not help forming a mental model for our data model through UI (hierarchical relations between entities and components (soon archetypes))

How?
Icon in the header of the Viewer
:white_check_mark: always visible!
:white_check_mark: no awkward interactions!
:x: a new interaction pattern for the viewer!!
:x: what if there are few tabs — might be weird if it appears/disappears
We'll embrace this weirdness in the context of an already seriously weird view and see how this feels/how users react :)


Possibility to disable elements?

Hi,
I have a table and for a specific reasons I have to use tbody as sortable items. So the container is the table and sortable items are tbody. I also have thead element in a table and when I sort tbody elements I can drop them above thead which is not what I want.
Is there way to prevent that? If not, that would be a nice feature to disable certain elements.

Hey, you can do that by setting non-drag-area-selector in the Container to some class like ".drag-disabled" and then setting the class conditionally in the Draggable.

Cool, I'll try that approach

Hey, you can do that by setting non-drag-area-selector in the Container to some class like ".drag-disabled" and then setting the class conditionally in the Draggable.

@dword-design Do you have an example?
I think with non-drag-area-selector you can just disable drag behaviour for certain elements eg. input. It doesn't prevent dragging items above/below elements.
I created a demo of my situation.
https://codesandbox.io/s/7w0k4xyqwj
Here's also a GIF that shows my issue.

By it's nature it is not possible to disable and make an item stay put in a sortable list. I could not even thinks how would it work. Why the table is Container ? Did you try tbody as container ?

@ispal Ah ok now I understand. But then it's the same question from me as @kutlugsahin said. tbody as a container should solve the problem.


Multi-tenancy

At the current state, only a single API can be effectively served from a database because queries have no way of filtering the relevant resources
I think of adding hydra:apiDocumentation </api> to resources and extending all queries with a filter so that only resources annotated as belonging to the current API would be found.
This would have to be an opt-in feature, so that single-tenant databases do not suffer the additional penalty of unnecessary filter.
The necessary changes:

[x] have all new resources implicitly annotated with hydra:apiDocumentation, without manual changes
[ ] apply filter automatically to queries (collection, resource)

In fact this may also be useful for a single tenant database, to exclude terms which may be found in external vocabularies

The second bullet can be implemented by #94


Feature/custom image tags

A rehash of #9 that just overrides the default tag - no fancy stuff for adding multiple tags.

@sjauld could I trouble you to flatten all those commits into a single one and rebase from master?

@lox Will do

Seems like a couple of strange commits got mixed in, I'll remove them

@lox should be good to go now!

@jufemaiz STOP MESSING MY BRANCH!

Looks good to me, @toolmantim?

@toolmantim what is the check that hasn't completed yet? :)

Thanks for the contribution @sjauld, and sorry for the slow review.
I've just poured over the code and looked at the original build.sh. It turns out the BUILDKITE_PIPELINE_SLUG doesn't contain the project slug (it did when it was BUILDBOX_PIPELINE_SLUG), so the whole image_file_name function is not needed. Which means a bunch of stuff could be removed, which I've done in #28
I also checked out the docker tag docs, and I think changing it to "image-name" rather than tag would be less confusing… because the tag will actually have the repository plugged on the front.
Let me know if #28 looks good, and perhaps we can go with that instead of this one?

I'll do a quick test now.

Looks good to be, I'll close this one

@sjauld cool! Thanks again for this… it wouldn't have happened without putting together this PR


This project needs a maintainer.

Hi,
This repository seems to lack maintenance, I propose myself as a new maintainer.
Could you give me the right to push in your repository or just transfer it on my account in github?
Thank you

Thank you for the offer. I just added you as a collaborator and as a maintainer on PyPI (https://pypi.python.org/pypi/django-phased).


[BUG] System.UnauthorizedAccessException: Access to the path 'C:\Users\gabri\AppData\Local\Bloxstrap\Versions\version-b71c150c7c1f40de\ucrtbase.dll' is denied.

Acknowledgement of preliminary instructions

[X] I have read the preliminary instructions, and I am certain that my problem has not already been addressed.
[X] I have thoroughly looked through the available Wiki articles and could not find a solution to my problem.
[X] I am using the latest version of Bloxstrap.
[ ] I did not answer truthfully to all the above checkboxes.

Bloxstrap Version
v2.8.4
What problem did you encounter?
não consigo iniciar o bloxstrap
Bloxstrap Log
N/A

Fixed in 2.8.5


BlocksByRange under WS

Is your feature request related to a problem? Please describe.

Implement this https://github.com/ethereum/eth2.0-specs/pull/2131/files
Part of #2530
Since it's quite isolated I make it a separate issue to avoid pulling us from being compliant to the whole spec

Detail

Since we only need to serve blocks within MIN_EPOCHS_FOR_BLOCK_REQUESTS  epochs, we can prune our db accordingly in order to avoid having our db grow forever
Validate beacon_blocks_by_range request accordingly
We have to backfill blocks if starting from a ws checkpoint

Don't need to get through state transition, just validate block proposer and parent-child relationship until recent block roots inside the ws state
Consider hooking into / add new sync type  https://github.com/ChainSafe/lodestar/blob/074649e35fe6a20a5aeab8898b67b73dca2e2900/packages/lodestar/src/sync/range/range.ts#L112

This new sync type can be actually fully independent from the other sync types. A node can be syncing forward at the same time it's backfilling.
I would create a new class BackfillSync that re-uses the SyncChain class which contains all the logic to download in parallel, load balance peers, etc. But with custom instantiation parameters
processChainSegment: (blocks) => {
  verifyParentChildSeg(blocks)
  db.blocks.put(blocks)
}

Also override the computeTarget function too to make it static and equal to the ws checkpoint

some conversation  context:


Local fonts not loading properly

Environment

System:

OS: macOS 10.14.6
CPU: (8) x64 Intel(R) Core(TM) i7-8569U CPU @ 2.80GHz
Memory: 517.05 MB / 16.00 GB
Shell: 5.3 - /bin/zsh

Binaries:

Node: 10.16.0 - /usr/local/bin/node
Yarn: 1.17.0 - /usr/local/bin/yarn
npm: 6.9.0 - /usr/local/bin/npm
Watchman: 4.9.0 - /usr/local/bin/watchman

npmPackages:

styled-components: 5.0.0-beta.8 => 5.0.0-beta.8

Reproduction
I'm getting weird issues fonts not always being applied to the components correctly. The whole font file is not loaded in some cases. In this example I was using 5.0.0-beta.8 but this happened with the latest 4.x too.
In the codesandbox below, I have a very simple example where I add a @font-face in createGlobalStyle and then reference that font in a styled.div component and the font is not loading.
This happened on my and co-workers machine as well in very basic CRA projects.
What am I missing here?
https://codesandbox.io/s/distracted-williams-y2s87
Steps to reproduce
Add a local font as a @font-face to createGlobalStyle and then apply that as a font-family on a styled component somewhere and the font isn't loading, at least not for me.
Expected Behavior
Font-families should be loading correctly when added in styled components.
Actual Behavior
Font family is not recognized and not even loaded down the wire according to the network tab.

Looks ok to me


Unknown fields {'payments_enabled'} in payload  (https://ob.nordigen.com/api/v2/institutions)

I think nordigen removed the "payments_enabled" in query string.
var query = new KeyValuePair<string, string>[] {new("country", country), new("payments_enabled", paymentsEnabled.ToString())};
We give back an error:
Unknown fields {'payments_enabled'} in payload
Would you remove from the querystring?

Thanks for reporting the issue, fixed with library version 6.0.1.

Thanks, working


gcloud Authentication Error

Describe the bug
When running reliably slo agent against an Objective integrated with a GCP Loadbalancer, we get the following error:
ERRO[0000] error processing objective: {ObjectiveAttributes}
error: error detected while getting indicator for objective: {ObjectiveAttributes}
No provider was able to compute the objective indicator
And when running reliably slo agent --verbose you get:
DEBU[0000] NewMetricClient: google: could not find default credentials
See https://developers.google.com/accounts/docs/application-default-credentials for more information
ERRO[0000] error processing objective: {ObjectiveAttributes}
error: error detected while getting indicator for objective: {ObjectiveAttributes}
No provider was able to compute the objective indicator
This is due to the fact that the user has not logged into the gcloud SDK using gcloud auth application-default login which isn't clear from the error and is still difficult to get from the link provided in the debug message
To Reproduce
Use gcloud auth revoke to revoke the credentials for your gcloud SDK account and then use gcloud auth login to log in again - the wrong way.
Then, set up a new Objective in a Manifest as such:

Then use reliably slo agent --manifest "manifest.yaml in a separate terminal and witness the error
To correct this, switch back to the original terminal and log in using gcloud auth application-default login
Then, go back and run reliably slo agent --manifest "manifest.yaml and no errors will be thrown
You can then use reliably slo report to view the current Objectives and their results
Expected behaviour
If authenticated in the wrong way, an intuitive error message should be displayed instead:
ERRO[0000] error processing objective: {ObjectiveAttributes}
Default credentials not found. See https://cloud.google.com/sdk/gcloud/reference/auth/application-default for more information
Or something similar ...

Useful for documentation


ARROW-10932: [C++] BinaryMemoTable::CopyOffsets access out-of-bound address when data is empty

The CI failures are unrelated, will merge.


Small issues with eigen_decomposition_of_Hermitian_matrix.ipynb notebook.

I was trying to run the eigen_decomposition_of_Hermitian_matrix.ipynb and ran into small technical issues.  Since notebooks are a bit weird with diffs, decided not to open a PR (but happy to do!).

First import fails due to a missing parla/tests/test_comps/__init__.py (not sure if it should be added or the import removed though).   (EDIT: This might be a bit related to how I installed the package locally.)
from parla.drivers.evd import * has to be "drivers" was from parla.comps.evd import * now
The signatures changed, I modified them to (not quite sure that is correct):

evd1(inner_num_pass=2, A=A0, k=target_rank, over=target_rank, tol=0.1, block_size=2, rng=123)
evd2(num_passes=3, A=A0, k=target_rank, over=target_rank, rng=123)

At least on SciPy 1.8rc1 it may be that some of the _ functions imported from scipy were renamed (or removed), that may need fixing, but Scipy 1.8 is not released yet so it doesn't matter.

Hi @seberg! Thanks so much for reporting this. We haven't done a good job of updating the notebooks as we've made changes to parla. I'll implement your suggested changes now.

@seberg these issues should be fixed. The notebook runs now, and I believe it runs correctly. I actually found (and fixed) a minor implementation error thanks to you reporting this issue!
I'll close this issue for now. Please feel free to post here again if it seems this isn't resolved.


Factor out query merging into a separate package

Now that we have transport batching built into the network interface, I think it's a good idea to move the query merging into a separate package. It'll be just as easy to use, but people don't need to load all of that code if they aren't using it.

I could line this up while fixing #559

I think this must be the reason we are banging our head against the wall...
from my understanding, 0.5.0-1 doesnt seem to have any ability to query batch.
Is there an ETA on this?  You guys are doing a super job and i really support the breaking change paradigm btw... so dont let this be a reason to feel like you're failing, you're doing INCREDIBLE stuff for the community!  just was curious if i was missing something ;)

@chaffeqa 0.5.0 will have transport batching, but by using a different network interface instead of passing an option to Apollo Client. If you relied on query merging, you'll have to continue using 0.4.22 until we fix up the query merging and release it as a separate package.


Could not find module 'EsewaSDK'

Could not find module 'EsewaSDK' for target 'arm64-apple-ios'; found: x86_64-apple-ios-simulator, arm64-apple-ios-simulator, at:
/ios/.symlinks/plugins/esewa_flutter_sdk/ios/EsewaSDK.framework/Modules/EsewaSDK.swiftmodule

Please add more detail, Flutter version, platform and reproduction steps if possible.

Hy @riteshghimire9090 I think you are stuck because of flutter_inappwebview package integration or pod install issue, make sure you have satisfied condition for flutter_inappwebview package impl, (like increase deployment target in Podfile : platform :ios, 'x' . or proper pod install.
Check-out example project for more.
I ran it in IOS simulator and real device and working perfectly fine, let me know if you have any further query.
Closing this issue for now.


Provide documentation for native use of SQLAlchemy signals

SQLAlchemy provides great documentation on signals.  What exactly would FSA be documenting?

I think this was in response to our work fixing and deprecating SQLALCHEMY_RECORD_QUERIES and SQLALCHEMY_TRACK_MODIFICATIONS, respectively. I'm not sure what exactly we wanted to document though, I think we may have discussed it in issue comments.


Optional Extension to Markdown

Thank you for a great plugin. Works perfectly.
I was wondering if it would be possible to extend these set of snippets to markdown. I use pandoc to convert markdown and rmarkdown to latex or pdf sometimes and used to use the same set of snippets with Ultisnips.
Following change to plugin options doesn't do the trick.
ft = {'tex', 'markdown'},

I checked packerstatus inside mardown file to verify if the plugin is loaded.

Try the markdown. There's probably some snippets that aren't suitable there. Feedback is appreciated.

Thank you. Markdown branch works perfectly. The beg keyword at beginning of line still triggers inside markdown but that is fine, I mainly use it for math snippets.

Such wonderful work. I just wonder how can it trigger the right branch? Or, how can the neovim detech the right block of the filetype and tried all the mathblock as tex filetype?

I just wonder how can it trigger the right branch? Or, how can the neovim detech the right block of the filetype and tried all the mathblock as tex filetype?

It can't detect whether we're in a math block or not. It mostly works by accident right now.
That's why Markdown isn't (yet) supported.
I suppose one could write a tree sitter query or a vim syntax file. Might be worth looking into https://github.com/preservim/vim-markdown#syntax-extensions


no miners in the web

hello my miners dont show in the web but the api is working what could be the problem?

Make sure that you have PHP 7.4 or above and that the database file is writable.

I have php 7.4 and the db folder has 755 permissions, but unamwebpanel.db is 644

Are you able to go to the "Configurations" tab and create a new configuration (enter {} as the data)? After creating it then check if you can see the configuration in the "Edit Configurations", if it's not there then it's not able to write to the DB.

yes i can create new configuration

Then DB is writable, where are you hosting the web panel and what are you entering into "API Endpoint URL"?

I'm hosting it on sprinthost.ru, I saw somewhere here that is free and works , in the api endpoint I enter:
http://mysite/api/endpoint.php

And it's not forcing https when you visit the site or anything?

No I don't think so, its http could that be a problem?

No, the only problem would be if your site is forcing https (redirecting from http to https) without having a certificate, visit your site in the browser and check if it's saying http.

Yeah its saying http, even when I login or go the api page its http

Run your miner and then the checker and post what it returns.

its been mining for 20 minutes and still nothing on web

Does your host have cloudflare or something that could be blocking it? Also check the __UNAM_LIB\Logs directory to see if there are any files other than dummy.

I don't think it has anything that could be blocking it, in logs folder there is only dummy
off topic question what other web server that I could use that is not 000webhost?

Not sure, I personally host everything myself and people only tell me when they find a bad web host and usually not when they find a good web host.
Only reasons I can really think of why it wouldn't work is either the https redirect or a security block. Try seeing if you can find any Apache access.log or anything somewhere in your web host.

it looks like its working now, I think there was some kind of issue with the miner it would start but die after some time.
By the way can I change my api link with pastebin? (api-endpoint": "url")
Because I tried and no miner is connecting but in pool it shows they are online

Yes you can change the link with "Remote Configuration" with "api-endpoint": "url", don't forget to format the JSON correctly as well with commas and such.

I see, thank you very much for helping.


backend: stop using renderer to get the buffer type

When picking a format, the backend needs to know whether the
buffers allocated by the allocator will be DMA-BUFs or shared
memory. So far, the backend used the renderer's supported
buffer types to guess this information.
This is pretty fragile: renderers in general don't care about the
SHM cap (they only care about the DATA_PTR one). Additionally,
nothing stops a renderer from supporting both DMA-BUFs and shared
memory, but this would break the backend's guess.
Instead, use wlr_allocator.buffer_caps. This is more reliable since
the buffers created with the allocator are guaranteed to have these
caps.
cc @bl4ckb0ne

Not a breaking change since wlr_allocator is still a private wlroots API.

LGTM


Update link in README and config file

Close #28

Codecov Report
Base: 72.15% // Head: 72.15% // No change to project coverage :thumbsup:

Coverage data is based on head (9b6f996) compared to base (6ee99e2).
Patch has no changes to coverable lines.

Additional details and impacted files
@@            Coverage Diff            @@
##             master      #29   +/-   ##
=========================================
  Coverage     72.15%   72.15%
  Complexity      399      399
=========================================
  Files            70       70
  Lines          1232     1232
  Branches        125      125
=========================================
  Hits            889      889
  Misses          311      311
  Partials         32       32

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

:umbrella: View full report at Codecov.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.


make data-service less chatty with Preferences not found for user. messages.

Data Service  (especially on startup) creates quite a few of these errors, but seems to be running fine:
[2024-06-06 07:33:58 +0000] [44] [ERROR] An unknown or unhandled exception occurred
Traceback (most recent call last):
  File "handle_request", line 102, in handle_request
    try:

  File "/app/env/lib/python3.12/site-packages/renku_data_services/base_api/auth.py", line 39, in decorated_function
    response = await f(request, user, *args, **kwargs)
               ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/app/env/lib/python3.12/site-packages/renku_data_services/user_preferences/blueprints.py", line 30, in _get
    user_preferences = await self.user_preferences_repo.get_user_preferences(user=user)
                       ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/app/env/lib/python3.12/site-packages/renku_data_services/user_preferences/db.py", line 47, in get_user_preferences
    raise errors.MissingResourceError(message="Preferences not found for user.")
renku_data_services.errors.errors.MissingResourceError: MissingResourceError: Preferences not found for user.

We should figure out what is actually calling this on a fresh deployment, and if we can fix this (can we just create default user preferences if there are none?)

This is most likely the result of the Cypress e2e tests creating a new user and loading the UI (which loads user preferences).
We should suppress expected errors anyway and just log the HTTP status, e.g.

404 not found
401 / 403
422 - invalid payload
A lot of these pollute the schemathesis logs as well, when the important logs (e.g. 500 are buried).

Reference: https://sanic.dev/en/guide/best-practices/exceptions.html#using-sanic-exceptions


Some URL segments 404

Right now https://angular.io/docs/ts/latest/api/router/index/ is a valid route but https://angular.io/docs/ts/latest/api/router/ 404s. Not a big deal, but if you're navigating by URL it's a little annoying. Ideally all the segments in the path would have some content or at least a redirect.

Right. FYI, a reorganization of the entries below api/ is planned; and this rework will address the issues you mention.
cc @naomiblack @IgorMinar @alexwolfe @ericjim


use nt service mssqlserver for svc acct

This fixes an edge case where:

New-DbaAvailabilityGroup is used to create an AG on the runner
The commands are being run in non-interactive PowerShell

When the service account being used is "NT AUTHORITY\SYSTEM" it is returned to the functions as "LocalSystem" which is treated as a SQL Login not an AD login, so a prompt results to ask for a password for the new login during AG permissioning.
By using this login instead, it should avoid this issue. I have a working example of this where I update the service account after install and am able to create an AG:
https://github.com/lowlydba/lowlydba.sqlserver/blob/b5ef43f6cf736b556ae736af01c70750e8e27de2/.github/workflows/ansible-test-windows.yml#L111-L114
Fixes #9 and then some

sweet, let's see if this works!


feat: change terminal time stamp color from bug bright red to improve readibility

Pull Request Type
Dictionary of Definitions here:
https://ben.balter.com/2015/12/08/types-of-pull-requests/

[] Just a heads up 🙆
[ ] Sanity check 🏃♂
[ ] Work in progress (WIP) 🏗
[ ] Early feedback ✍
[x] Line-by-line review 📝
[ ] Pull request to a pull request 🔀

Description
The terminal color change should improve Readability, reduced Confusion via by avoiding the use of red for timestamps, we can minimize the risk of false positives and streamline the debugging process, and overall abide by terminal UX best practices from what I understand about the objective of the time stamp purpose in the defang project.
This PR addresses this Github issue: https://github.com/DefangLabs/defang/issues/707
Caveats/Notes (optional)
I was not able to fully test the terminal UI as I did not run this specific defang version. Instructions on how to best run a local emulated version from VS code would be fantastic too!
Prompts (optional)
Screenshots (optional)
[Upload optional screenshots]
Checklist before requesting a review

[x] I have performed a self-review of my code
[x] If it is a core feature, I have added thorough tests.
[x] Extended the README / documentation, if necessary
[x] My changes generate no new warnings
[x] Is the code readable? Prefer to see more self-explanatory and consistency
[ ] Is the code tested properly? i.e. where appropriate, we're testing well-explained failures, behaviours, fixes, etc

I agree there's improvements to be made here. Timestamps are Red for error logs, which are the only ones you'll see when you omit --verbose.

@ve-varun-sharma closing this because we did make some changes around our verbosity. Also "cyan" was already used for another column. I think there's something to be said to make timestamps optional, then this would not be an issue.

@ve-varun-sharma closing this because we did make some changes around our verbosity. Also "cyan" was already used for another column. I think there's something to be said to make timestamps optional, then this would not be an issue.

That definitely makes sense to me! Thanks for the update here :) 🙏🏽


Witherspoon: RAS Reset Reload related automation scenarios

RAS Reset Reload related automation scenarios.

Inject checkstop through BMC and do reset reload.
Inject checkstop through HOST and do reset reload.
Do reset reload and inject checkstop through BMC when HOST is booting.

What about doing reset reload and then inject check-stop through BMC and host at runime
reverse case of #1 and 2

[ ] https://gerrit.openbmc-project.xyz/#/c/openbmc/openbmc-test-automation/+/27140/

Implemented & code is merged


Unstorage getKeys() returns [] in vercel

Environment
  nitro: {
    preset: "vercel",
  },

Reproduction
https://stackblitz.com/edit/nuxt-starter-sxrccq?file=server/routes/test.ts
Describe the bug
Unstorage works fine in local, but when I deploy to vercel, it shows empty array

Additional context
    "nuxt": "3.0.0-rc.6",
Logs
No response

Hi. There are no default mount points by default in the production and it is expected indeed. Please see my comment in https://github.com/unjs/nitro/issues/1941#issuecomment-1821877691