How to re-import zfs containers after blitzing the lxd db?

Required information

Distribution: 16.04  - 4.8.0-49-generic
Distribution version:
The output of "lxc info" or if that fails:

root@opti-bram-srv01:/var/lib/lxd/storage-pools/mirr1tb/containers/strongswan# lxc info
config: {}
api_extensions:

storage_zfs_remove_snapshots
container_host_shutdown_timeout
container_syscall_filtering
auth_pki
container_last_used_at
etag
patch
usb_devices
https_allowed_credentials
image_compression_algorithm
directory_manipulation
container_cpu_time
storage_zfs_use_refquota
storage_lvm_mount_options
network
profile_usedby
container_push
container_exec_recording
certificate_update
container_exec_signal_handling
gpu_devices
container_image_properties
migration_progress
id_map
network_firewall_filtering
network_routes
storage
file_delete
file_append
network_dhcp_expiry
storage_lvm_vg_rename
storage_lvm_thinpool_rename
network_vlan
image_create_aliases
container_stateless_copy
container_only_migration
storage_zfs_clone_copy
unix_device_rename
storage_lvm_use_thinpool
storage_rsync_bwlimit
network_vxlan_interface
api_status: stable
api_version: "1.0"
auth: trusted
public: false
environment:
addresses: []
architectures:

x86_64
i686
certificate: |
-----BEGIN CERTIFICATE-----
MIIFhzCCA2+gAwIBAgIRAPlQ+Rn7SHqtur/gi1/NGpgwDQYJKoZIhvcNAQELBQAw
PTEcMBoGA1UEChMTbGludXhjb250YWluZXJzLm9yZzEdMBsGA1UEAwwUcm9vdEBv
cHRpLWJyYW0tc3J2MDEwHhcNMTcwNDMwMTYwMzM4WhcNMjcwNDI4MTYwMzM4WjA9
MRwwGgYDVQQKExNsaW51eGNvbnRhaW5lcnMub3JnMR0wGwYDVQQDDBRyb290QG9w
dGktYnJhbS1zcnYwMTCCAiIwDQYJKoZIhvcNAQEBBQADggIPADCCAgoCggIBAKjm
dQPNTcmRHS6xWFFx6vnrDporneM9HFOnlv3t6JzuPOU+SYD6swlSiLolDhOHNoof
kxLVy2zr5gYSJjuK6u3hJMS7Vkx8WCoeGX+pE/mqlENhsii3jwBK5fSXqiOXI6Ea
nHG5bs0PY4jz1lPb6U2gO+lz4UaMRTtXeaylCwNC8u+z+Vu/DWq88K2xd1sruvJK
WT348eSg8/yTBVr5HeXWfsr1jdYC2O+AEcni1rYn0V5j7HGZXOqNNR5VRavrzVfc
C21uZOHTs5F3x1e29PpflC3eAq6Qpyh8jm9E3BpH35c4hNjUnUmSVlyWk1tqTIJ1
GZ2UtfHpvDl+2cqeanWameJSuNq0nZGlRpSYVhXJszIb9lFa9eH8ibBO3sL4Tn8t
Sq1rPzgou3Za9lXnegt8TkypCx8mPSxIlNcHdgfdy0nbKImcnVnIObdf9R9h3hTe
MdRedkTReHnEQ0cUMST4JWTo6GWbg11N+VZCCs7cqx5maEfpN+MDSbepP1YO3raO
+RzjH7KJMWK2195wEzQvLXFNK/Ci0RBPXS71o4S2HOv8Ru8mM7EQ9jHt2pIpCpRM
SFvPISgnlVXwBc2YySvOoHQVqxFIJ+OdQJY1bJchO+vyoQBDHhHZ02uE/ZPFFC6n
0C6ZsU8P3YwiDi7ANC3ioZ2/E9cZXKpz8PyesYznAgMBAAGjgYEwfzAOBgNVHQ8B
Af8EBAMCBaAwEwYDVR0lBAwwCgYIKwYBBQUHAwEwDAYDVR0TAQH/BAIwADBKBgNV
HREEQzBBgg9vcHRpLWJyYW0tc3J2MDGHBAoKWAqHBKwREGSHBAoKCwqHBAoKxwGH
BAo8yAqHBAoKYwGHBKwSAAGHBMCoegEwDQYJKoZIhvcNAQELBQADggIBADcAlg7U
FF4qcxp0hh4vXePpsGgGZm+VCdqwNYvMdZ9+3340Lkmu0/Wyvgayj5XN57M1DpkC
xbYHW5ElGOE8V2s2RHMYpM/lLSFQ51NhL5/lSs0ZZ5s++JK6mw6pCQoQ0EFLzaXH
5ibQElIo3ztMiDJSIp/QEDI+VXcnPF29Y49UCwd+mimUIdbaV/I0N6ZY3HM4ZnZo
jmYg6Hssx22/CiWAoA4pEaCmzv/e2J6Y2a5qj4aAG2jYgYAJRl1BYNG0KY3zV8Cg
hCuxKgNdsgsnzR5GYzCUXSy0csJqjcoA4EvUI1NIbDhFs4RJOCOt6dQx3Ta/5A8c
D51tDPJTCB4ywGvmZVH4JxT+KmnZG5YlMlfArLd4eyT9GOcThAFjBgJZIgRKtSQS
B3OGZEA5XSZnsnr2I2lPCpRmR0dC0coXlLjk9JwSWdcqzYjF3G0dN1Eou5K2m3Wi
FBDZRkpv66LVAO/sOq0VWTvwQl5DRxh+9R2xrlaM4iJJE47hKpo3KVLMw1ZfSMKF
MqqvOUm+8i7fDOmqHvtkN4p208qYtxS1wpiY6fTcRkbvOTd+2afCoyVvzJn1W8Ea
nvz4djbNv7x8mexTht23zAiPYwYP4aaTbcHczkz8nfJoy55hDio11dx3qx9Im2Xs
Bzr8cP+MSa/mAD1C+kgClGgmzBAOQhUn5L0f
-----END CERTIFICATE-----
certificate_fingerprint: 9997e229418451999ec250cf6a0e3bfd61a5c42a5c1c51222c3bc6c8312e4b16
driver: lxc
driver_version: 2.0.7
kernel: Linux
kernel_architecture: x86_64
kernel_version: 4.8.0-49-generic
server: lxd
server_pid: 2767
server_version: "2.13"
storage: ""
storage_version: ""

Storage backend in use:  ZFS

Issue description
Hi,
I mistakenly uninstalled LXD and I think destroyed the database, now lxd list is showing nothing.
I still have all my containers zfs storage intact so wondering how to import them into a fresh LXD install.
Tried a few things related to using "lxc storage" but struggling to actually get the containers back into LXD database.
Bit of a n00b here, network engineer by trade, trying to dabble in Linux!!!
Cheers!
Jon.
Steps to reproduce

Step one
root@opti-bram-srv01:/var/lib/lxd/storage-pools/mirr1tb/containers/strongswan# lxc list
+------+-------+------+------+------+-----------+
| NAME | STATE | IPV4 | IPV6 | TYPE | SNAPSHOTS |
+------+-------+------+------+------+----------

Step two
root@opti-bram-srv01:/var/lib/lxd/storage-pools/mirr1tb/containers/strongswan# zpool list
NAME       SIZE  ALLOC   FREE  EXPANDSZ   FRAG    CAP  DEDUP  HEALTH  ALTROOT
large1-5  1.36T   682G   710G         -    38%    48%  1.00x  ONLINE  -
mirr1tb    928G   122G   806G         -     6%    13%  1.00x  ONLINE  -
store500   464G   221M   464G         -     0%     0%  1.00x  ONLINE  -

Step three

Output of zfs list showing the actual storage is still there:
root@opti-bram-srv01:/var/lib/lxd/storage-pools/mirr1tb/containers/strongswan# zfs list
NAME                                                                                USED  AVAIL  REFER  MOUNTPOINT
large1-5                                                                                682G   667G   681G  /large1-5
mirr1tb                                                                                122G   777G    96K  none
mirr1tb/containers                                                                        107G   777G    96K  none
mirr1tb/containers/ansible                                                                459M  19.6G   860M  /var/lib/lxd/storage-pools/mirr1tb/containers/ansible
mirr1tb/containers/backup-alpinehub                                                      40.9M   777G  40.9M  /var/lib/lxd/storage-pools/mirr1tb/containers/backup-alpinehub
mirr1tb/containers/backup-alpinespoke                                                    40.6M   777G  40.6M  /var/lib/lxd/storage-pools/mirr1tb/containers/backup-alpinespoke
mirr1tb/containers/backup-vmhost-hub1-virl                                               20.4G   777G  20.4G  /var/lib/lxd/storage-pools/mirr1tb/containers/backup-vmhost-hub1-virl
mirr1tb/containers/backups                                                               8.85G  71.2G  9.42G  /var/lib/lxd/storage-pools/mirr1tb/containers/backups
mirr1tb/containers/containers                                                              96K   777G    96K  none
mirr1tb/containers/custom                                                                 192K   777G    96K  none
mirr1tb/containers/custom/lxdhome                                                          96K   777G    96K  /var/lib/lxd/storage-pools/pool1/custom/lxdhome
mirr1tb/containers/deleted                                                                 96K   777G    96K  none
mirr1tb/containers/dns                                                                    313M  19.7G   821M  /var/lib/lxd/storage-pools/mirr1tb/containers/dns
mirr1tb/containers/images                                                                  96K   777G    96K  none
mirr1tb/containers/nextcloud                                                             9.79G  10.2G  10.4G  /var/lib/lxd/storage-pools/mirr1tb/containers/nextcloud
mirr1tb/containers/nzb                                                                   34.5G   777G  35.0G  /var/lib/lxd/storage-pools/mirr1tb/containers/nzb
mirr1tb/containers/openstack2                                                            4.62M   777G   755M  /var/lib/lxd/containers/openstack2.zfs
mirr1tb/containers/ovpn                                                                  22.7M  20.0G  27.9M  /var/lib/lxd/storage-pools/mirr1tb/containers/ovpn
mirr1tb/containers/plex                                                                  3.13G  16.9G  2.71G  /var/lib/lxd/storage-pools/mirr1tb/containers/plex
mirr1tb/containers/pritunl                                                               1.99G  18.0G  2.09G  /var/lib/lxd/storage-pools/mirr1tb/containers/pritunl
mirr1tb/containers/smokeping                                                              932M  19.1G  1.31G  /var/lib/lxd/storage-pools/mirr1tb/containers/smokeping
mirr1tb/containers/strongswan                                                             415M  19.6G  1.00G  /var/lib/lxd/storage-pools/mirr1tb/containers/strongswan
mirr1tb/containers/unifi                                                                 7.13G  12.9G  7.55G  /var/lib/lxd/storage-pools/mirr1tb/containers/unifi
mirr1tb/containers/unimus                                                                 489M  19.5G  1.05G  /var/lib/lxd/storage-pools/mirr1tb/containers/unimus
mirr1tb/containers/vmhost                                                                16.9G  3.11G  17.3G  /var/lib/lxd/storage-pools/mirr1tb/containers/vmhost
mirr1tb/containers/vpn-ras                                                               2.11G  7.89G  1.53G  /var/lib/lxd/storage-pools/mirr1tb/containers/vpn-ras
Information to attach
dmesg.txt

[ ] any relevant kernel output (dmesg)
[ ] container log (lxc info NAME --show-log)
[ ] main daemon log (/var/log/lxd.log)
[ ] output of the client with --debug
[ ] output of the daemon with --debug

Think its related to this https://github.com/lxc/lxd/issues/3005
I've tried symlinking but still getting not found.
 lxd import strongswan error: not found

Can you show me the output of lxc storage list, please?

+------+-------+------+------+------+-----------+ root@opti-bram-srv01:/home/jon# lxc storage list +-------+--------+--------------------+---------+ | NAME  | DRIVER |       SOURCE       | USED BY | +-------+--------+--------------------+---------+ | lxd   | zfs    | mirr1tb/containers | 0       | +-------+--------+--------------------+---------+ | pool1 | zfs    | mirr1tb/containers | 0       | +-------+--------+--------------------+---------+

| lxd   | zfs    | mirr1tb/containers | 0       |
+-------+--------+--------------------+---------+
| pool1 | zfs    | mirr1tb/containers | 0       |
+-------+--------+--------------------+---------+

mirr1tb/containers/ansible                                                                459M  19.6G   860M  /var/lib/lxd/storage-pools/mirr1tb/containers/ansible mirr1tb/containers/backup-alpinehub                                                      40.9M   777G  40.9M  /var/lib/lxd/storage-pools/mirr1tb/containers/backup-alpinehub mirr1tb/containers/backup-alpinespoke                                                    40.6M   777G  40.6M  /var/lib/lxd/storage-pools/mirr1tb/containers/backup-alpinespoke mirr1tb/containers/backup-vmhost-hub1-virl                                               20.4G   777G  20.4G  /var/lib/lxd/storage-pools/mirr1tb/containers/backup-vmhost-hub1-virl mirr1tb/containers/backups                                                               8.85G  71.2G  9.42G  /var/lib/lxd/storage-pools/mirr1tb/containers/backups mirr1tb/containers/containers                                                              96K   777G    96K  none mirr1tb/containers/custom                                                                 192K   777G    96K  none mirr1tb/containers/custom/lxdhome                                                          96K   777G    96K  /var/lib/lxd/storage-pools/pool1/custom/lxdhome mirr1tb/containers/deleted                                                                 96K   777G    96K  none mirr1tb/containers/dns                                                                    313M  19.7G   821M  /var/lib/lxd/storage-pools/mirr1tb/containers/dns mirr1tb/containers/images                                                                  96K   777G    96K  none mirr1tb/containers/nextcloud                                                             9.79G  10.2G  10.4G  /var/lib/lxd/storage-pools/mirr1tb/containers/nextcloud mirr1tb/containers/nzb                                                                   34.5G   777G  35.0G  /var/lib/lxd/storage-pools/mirr1tb/containers/nzb mirr1tb/containers/openstack2                                                            4.55M   777G   676M  /var/lib/lxd/containers/openstack2.zfs mirr1tb/containers/ovpn                                                                  22.7M  20.0G  27.9M  /var/lib/lxd/storage-pools/mirr1tb/containers/ovpn mirr1tb/containers/plex                                                                  3.13G  16.9G  2.71G  /var/lib/lxd/storage-pools/mirr1tb/containers/plex mirr1tb/containers/pritunl                                                               1.99G  18.0G  2.09G  /var/lib/lxd/storage-pools/mirr1tb/containers/pritunl mirr1tb/containers/smokeping                                                              932M  19.1G  1.31G  /var/lib/lxd/storage-pools/mirr1tb/containers/smokeping mirr1tb/containers/strongswan                                                             415M  19.6G  1.00G  /var/lib/lxd/storage-pools/mirr1tb/containers/strongswan mirr1tb/containers/unifi                                                                 7.13G  12.9G  7.55G  /var/lib/lxd/storage-pools/mirr1tb/containers/unifi mirr1tb/containers/unimus                                                                 489M  19.5G  1.05G  /var/lib/lxd/storage-pools/mirr1tb/containers/unimus mirr1tb/containers/vmhost                                                                16.9G  3.11G  17.3G  /var/lib/lxd/storage-pools/mirr1tb/containers/vmhost mirr1tb/containers/vpn-ras                                                               2.11G  7.89G  1.53G  /var/lib/lxd/storage-pools/mirr1tb/containers/vpn-ras

Can you show me the output of cat /proc/1/mounts, please?

jon@opti-bram-srv01:~$ cat /proc/1/mounts sysfs /sys sysfs rw,nosuid,nodev,noexec,relatime 0 0 proc /proc proc rw,nosuid,nodev,noexec,relatime 0 0 udev /dev devtmpfs rw,nosuid,relatime,size=16303628k,nr_inodes=4075907,mode=755 0 0 devpts /dev/pts devpts rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=000 0 0 tmpfs /run tmpfs rw,nosuid,noexec,relatime,size=3264948k,mode=755 0 0 /dev/mapper/opti--bram--srv01--vg-root / ext4 rw,relatime,errors=remount-ro,data=ordered 0 0 securityfs /sys/kernel/security securityfs rw,nosuid,nodev,noexec,relatime 0 0 tmpfs /dev/shm tmpfs rw,nosuid,nodev 0 0 tmpfs /run/lock tmpfs rw,nosuid,nodev,noexec,relatime,size=5120k 0 0 tmpfs /sys/fs/cgroup tmpfs rw,mode=755 0 0 cgroup /sys/fs/cgroup/systemd cgroup rw,nosuid,nodev,noexec,relatime,xattr,release_agent=/lib/systemd/systemd-cgroups-agent,name=systemd 0 0 pstore /sys/fs/pstore pstore rw,nosuid,nodev,noexec,relatime 0 0 efivarfs /sys/firmware/efi/efivars efivarfs rw,nosuid,nodev,noexec,relatime 0 0 cgroup /sys/fs/cgroup/freezer cgroup rw,nosuid,nodev,noexec,relatime,freezer 0 0 cgroup /sys/fs/cgroup/cpu,cpuacct cgroup rw,nosuid,nodev,noexec,relatime,cpu,cpuacct 0 0 cgroup /sys/fs/cgroup/memory cgroup rw,nosuid,nodev,noexec,relatime,memory 0 0 cgroup /sys/fs/cgroup/perf_event cgroup rw,nosuid,nodev,noexec,relatime,perf_event,release_agent=/run/cgmanager/agents/cgm-release-agent.perf_event 0 0 cgroup /sys/fs/cgroup/net_cls,net_prio cgroup rw,nosuid,nodev,noexec,relatime,net_cls,net_prio 0 0 cgroup /sys/fs/cgroup/pids cgroup rw,nosuid,nodev,noexec,relatime,pids,release_agent=/run/cgmanager/agents/cgm-release-agent.pids 0 0 cgroup /sys/fs/cgroup/blkio cgroup rw,nosuid,nodev,noexec,relatime,blkio 0 0 cgroup /sys/fs/cgroup/cpuset cgroup rw,nosuid,nodev,noexec,relatime,cpuset,clone_children 0 0 cgroup /sys/fs/cgroup/devices cgroup rw,nosuid,nodev,noexec,relatime,devices 0 0 cgroup /sys/fs/cgroup/hugetlb cgroup rw,nosuid,nodev,noexec,relatime,hugetlb,release_agent=/run/cgmanager/agents/cgm-release-agent.hugetlb 0 0 systemd-1 /proc/sys/fs/binfmt_misc autofs rw,relatime,fd=27,pgrp=1,timeout=0,minproto=5,maxproto=5,direct,pipe_ino=12021 0 0 debugfs /sys/kernel/debug debugfs rw,relatime 0 0 mqueue /dev/mqueue mqueue rw,relatime 0 0 hugetlbfs /dev/hugepages hugetlbfs rw,relatime 0 0 sunrpc /run/rpc_pipefs rpc_pipefs rw,relatime 0 0 nfsd /proc/fs/nfsd nfsd rw,relatime 0 0 fusectl /sys/fs/fuse/connections fusectl rw,relatime 0 0 configfs /sys/kernel/config configfs rw,relatime 0 0 /dev/loop0 /snap/core/1577 squashfs ro,relatime 0 0 /dev/loop1 /snap/lxd/1743 squashfs ro,nodev,relatime 0 0 /dev/mapper/opti--bram--srv01--vg-root /export/CCTV ext4 rw,relatime,errors=remount-ro,data=ordered 0 0 /dev/loop2 /snap/frr/19 squashfs ro,relatime 0 0 /dev/sde2 /boot ext2 rw,relatime,block_validity,barrier,user_xattr,acl 0 0 /dev/sde1 /boot/efi vfat rw,relatime,fmask=0077,dmask=0077,codepage=437,iocharset=iso8859-1,shortname=mixed,errors=remount-ro 0 0 large1-5 /large1-5 zfs rw,relatime,xattr,noacl 0 0 mirr1tb/containers/openstack2 /var/lib/lxd/containers/openstack2.zfs zfs rw,relatime,xattr,noacl 0 0 mirr1tb/containers/ansible /var/lib/lxd/storage-pools/mirr1tb/containers/ansible zfs rw,relatime,xattr,noacl 0 0 mirr1tb/containers/backup-alpinehub /var/lib/lxd/storage-pools/mirr1tb/containers/backup-alpinehub zfs rw,relatime,xattr,noacl 0 0 mirr1tb/containers/backup-alpinespoke /var/lib/lxd/storage-pools/mirr1tb/containers/backup-alpinespoke zfs rw,relatime,xattr,noacl 0 0 mirr1tb/containers/backup-vmhost-hub1-virl /var/lib/lxd/storage-pools/mirr1tb/containers/backup-vmhost-hub1-virl zfs rw,relatime,xattr,noacl 0 0 mirr1tb/containers/backups /var/lib/lxd/storage-pools/mirr1tb/containers/backups zfs rw,relatime,xattr,noacl 0 0 mirr1tb/containers/dns /var/lib/lxd/storage-pools/mirr1tb/containers/dns zfs rw,relatime,xattr,noacl 0 0 mirr1tb/containers/nextcloud /var/lib/lxd/storage-pools/mirr1tb/containers/nextcloud zfs rw,relatime,xattr,noacl 0 0 mirr1tb/containers/nzb /var/lib/lxd/storage-pools/mirr1tb/containers/nzb zfs rw,relatime,xattr,noacl 0 0 mirr1tb/containers/ovpn /var/lib/lxd/storage-pools/mirr1tb/containers/ovpn zfs rw,relatime,xattr,noacl 0 0 mirr1tb/containers/plex /var/lib/lxd/storage-pools/mirr1tb/containers/plex zfs rw,relatime,xattr,noacl 0 0 mirr1tb/containers/pritunl /var/lib/lxd/storage-pools/mirr1tb/containers/pritunl zfs rw,relatime,xattr,noacl 0 0 mirr1tb/containers/smokeping /var/lib/lxd/storage-pools/mirr1tb/containers/smokeping zfs rw,relatime,xattr,noacl 0 0 mirr1tb/containers/strongswan /var/lib/lxd/storage-pools/mirr1tb/containers/strongswan zfs rw,relatime,xattr,noacl 0 0 mirr1tb/containers/unifi /var/lib/lxd/storage-pools/mirr1tb/containers/unifi zfs rw,relatime,xattr,noacl 0 0 mirr1tb/containers/unimus /var/lib/lxd/storage-pools/mirr1tb/containers/unimus zfs rw,relatime,xattr,noacl 0 0 mirr1tb/containers/vmhost /var/lib/lxd/storage-pools/mirr1tb/containers/vmhost zfs rw,relatime,xattr,noacl 0 0 mirr1tb/containers/vpn-ras /var/lib/lxd/storage-pools/mirr1tb/containers/vpn-ras zfs rw,relatime,xattr,noacl 0 0 mirr1tb/containers/custom/lxdhome /var/lib/lxd/storage-pools/pool1/custom/lxdhome zfs rw,relatime,xattr,noacl 0 0 tmpfs /run/snapd/ns tmpfs rw,nosuid,noexec,relatime,size=3264948k,mode=755 0 0 cgmfs /run/cgmanager/fs tmpfs rw,relatime,size=100k,mode=755 0 0 nsfs /run/snapd/ns/frr.mnt nsfs rw 0 0 nsfs /run/snapd/ns/lxd.mnt nsfs rw 0 0 lxcfs /var/lib/lxcfs fuse.lxcfs rw,nosuid,nodev,relatime,user_id=0,group_id=0,allow_other 0 0 binfmt_misc /proc/sys/fs/binfmt_misc binfmt_misc rw,relatime 0 0 /dev/mapper/opti--bram--srv01--vg-root /var/lib/docker/aufs ext4 rw,relatime,errors=remount-ro,data=ordered 0 0 tmpfs /var/lib/lxd/shmounts tmpfs rw,relatime,size=100k,mode=711 0 0 tmpfs /var/lib/lxd/devlxd tmpfs rw,relatime,size=100k,mode=755 0 0 tmpfs /run/user/1000 tmpfs rw,nosuid,nodev,relatime,size=3264948k,mode=700,uid=1000,gid=1000 0 0

Can you try lxd import strongswan --force and report back, please?

root@opti-bram-srv01:/home/jon# lxd import strongswan --force error: not found

Ok, I'll help you to recover from this. Can you please append or paste the contents of the file
/var/lib/lxd/storage-pools/mirr1tb/containers/strongswan/backup.yaml

here, please?

Ok thanks, here it is:
`root@opti-bram-srv01:/home/jon# cat /var/lib/lxd/storage-pools/mirr1tb/containers/strongswan/backup.yaml
container:
architecture: x86_64
config:
boot.autostart: "yes"
volatile.base_image: a221591e855f271769b3d780789c25d504b4062475c125f790b97d4afa0539f5
volatile.eth0.hwaddr: 00:16:3e:51:72:a8
volatile.idmap.base: "0"
volatile.idmap.next: '[{"Isuid":true,"Isgid":false,"Hostid":100000,"Nsid":0,"Maprange":65536},{"Isuid":false,"Isgid":true,"Hostid":100000,"Nsid":0,"Maprange":65536}]'
volatile.last_state.idmap: '[{"Isuid":true,"Isgid":false,"Hostid":100000,"Nsid":0,"Maprange":65536},{"Isuid":false,"Isgid":true,"Hostid":100000,"Nsid":0,"Maprange":65536}]'
volatile.last_state.power: RUNNING
devices: {}
ephemeral: false
profiles:

default
stateful: false
created_at: 2017-04-20T21:31:12Z
expanded_config:
boot.autostart: "yes"
raw.lxc: lxc.cgroup.devices.allow = c 10:200 rwm
volatile.base_image: a221591e855f271769b3d780789c25d504b4062475c125f790b97d4afa0539f5
volatile.eth0.hwaddr: 00:16:3e:51:72:a8
volatile.idmap.base: "0"
volatile.idmap.next: '[{"Isuid":true,"Isgid":false,"Hostid":100000,"Nsid":0,"Maprange":65536},{"Isuid":false,"Isgid":true,"Hostid":100000,"Nsid":0,"Maprange":65536}]'
volatile.last_state.idmap: '[{"Isuid":true,"Isgid":false,"Hostid":100000,"Nsid":0,"Maprange":65536},{"Isuid":false,"Isgid":true,"Hostid":100000,"Nsid":0,"Maprange":65536}]'
volatile.last_state.power: RUNNING
expanded_devices:
eth0:
name: eth0
nictype: bridged
parent: vmbr99
type: nic
root:
path: /
pool: mirr1tb
size: 20GB
type: disk
tun:
path: /dev/net/tun
type: unix-char
name: strongswan
status: Running
status_code: 103
last_used_at: 2017-04-30T11:42:52.919320571Z
snapshots: []
pool:
config:
source: mirr1tb
zfs.pool_name: mirr1tb
name: mirr1tb
driver: zfs
used_by: []
volume:
config: {}
name: strongswan
type: container
used_by: []`

Ok, can you do
lxc storage create mirr1tb zfs source=mirr1tb

and then try
lxd import strongswan --force

I get the following:
root@opti-bram-srv01:/home/jon#
lxc storage create mirr1tb zfs source=mirr1tb
error: Provided ZFS pool (or dataset) isn't empty
On Mon, 1 May 2017 at 20:00 Christian Brauner<EMAIL_ADDRESS>wrote:

Ok, can you do
lxc storage create mirr1tb zfs source=mirr1tb
and then try
lxd import strongswan --force
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/lxc/lxd/issues/3257#issuecomment-298403140, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AAly53HfRdpD9QEjPle7NY2FUC7zNgL6ks5r1iuygaJpZM4NMp_U
.

Can you please download this custom LXD binary I built for you from https://goo.gl/cg0uVt and try
lxd import strongswan --force

sha256: 460278ee7df6fe89a7fea4cf9bb0021cee196bda3135b26a9253d5c3db0720e1

Hi
Thanks for your help but earlier today I did something trigger happy stupid
and accidently deleted all the zfs mounts :'-(
Running your binary showed there was nothing left.
Sorry for wasting time!
Cheers and thanks again,
Jon.
On Tue, 2 May 2017 at 11:13 Christian Brauner<EMAIL_ADDRESS>wrote:

Can you please download this custom LXD binary I built for you from
https://goo.gl/cg0uVt and try
lxd import strongswan --force
sha256: 460278ee7df6fe89a7fea4cf9bb0021cee196bda3135b26a9253d5c3db0720e1
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/lxc/lxd/issues/3257#issuecomment-298592153, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AAly57wAgC5cRS4mZe0sQynIn0gVzE56ks5r1wGsgaJpZM4NMp_U
.

Hi,
Any chance of re-opening this one?  I've got the same problem.  I've fitted a new system disk, now I'm stuck trying to import the containers on the ZFS pool back into a new install of LXD.
I'm running the version in the stable PPA.
I get same issue with  .... "error: Provided ZFS pool (or dataset) isn't empty"
Cheers!
Jon.

@bodleytunes can you show "zfs list -t all" on your system?

The error you're getting is expected if you're attempting to run "lxc storage create" against an existing pool. This isn't the way to get your containers back into LXD, "lxd import" is the way to do that. The command above should let me see if things are roughly where they need to be for lxd import to do its job.

Hi Stephan
Thanks for the fast reply.
Here is the output:
NAME                                                                                USED  AVAIL  REFER  MOUNTPOINT large1-5                                                                                700G   649G   699G  /large1-5 mirr1tb                                                                                290G   609G   154G  /mirr1tb mirr1tb/containers                                                                                133G   609G    96K  none mirr1tb/containers/authbram                                                                       1018M   609G  1.40G  /var/lib/lxd/storage-pools/default/containers/authbram mirr1tb/containers/backup-alpinespoke                                                             41.0M   609G  40.6M  /var/lib/lxd/storage-pools/default/containers/backup-alpinespoke mirr1tb/containers/backup-alpinespoke@snapshot-copy                                                472K      -  40.6M  - mirr1tb/containers/containers                                                                       96K   609G    96K  none mirr1tb/containers/custom                                                                           96K   609G    96K  none mirr1tb/containers/deleted                                                                          96K   609G    96K  none mirr1tb/containers/images                                                                           96K   609G    96K  none mirr1tb/containers/local                                                                          55.9G   609G  55.0G  /var/lib/lxd/storage-pools/default/containers/local mirr1tb/containers/local@snapshot-virldone                                                         826M      -  20.4G  - mirr1tb/containers/local@snapshot-copy                                                             656K      -  55.1G  - mirr1tb/containers/local@migration-send-a22b0b23-c986-496e-bfea-0b236306fabe                       176K      -  55.1G  - mirr1tb/containers/plex                                                                           12.2G   609G  12.5G  /var/lib/lxd/storage-pools/default/containers/plex mirr1tb/containers/plex@snapshot-backup                                                            808K      -  12.5G  - mirr1tb/containers/plex@snapshot-backup2                                                           812K      -  12.5G  - mirr1tb/containers/plex-dbox                                                                      2.44G   609G  1.61G  /var/lib/lxd/storage-pools/default/containers/plex-dbox mirr1tb/containers/plex-dbox@snapshot-fres                                                        48.5M      -   650M  - mirr1tb/containers/plex-dbox@snapshot-plexinstalledppa                                             298M      -  1.08G  - mirr1tb/containers/plex-dbox@snapshot-first                                                        207M      -  1.65G  - mirr1tb/containers/plex-dbox@snapshot-backup                                                       145M      -  1.63G  - mirr1tb/containers/python                                                                         2.82G   609G  3.29G  /var/lib/lxd/storage-pools/default/containers/python mirr1tb/containers/vmhost                                                                         56.0G   609G  54.8G  /var/lib/lxd/storage-pools/default/containers/vmhost mirr1tb/containers/vmhost@snapshot-virldone                                                        826M      -  20.4G  - mirr1tb/containers/vmhost@snapshot-copy                                                            844K      -  55.1G  - mirr1tb/containers/vmhost@migration-send-d20be613-4c26-46ee-b4cd-784185f1528e                      844K      -  55.1G  - mirr1tb/containers/vpn-concentrator2                                                              2.37G   609G  2.85G  /var/lib/lxd/storage-pools/default/containers/vpn-concentrator2 mirr1tb/containers/vpn-concentrator2@snapshot-backup                                              81.6M      -  2.84G  - mirr1tb/custom                                                                                96K   609G    96K  none mirr1tb/deleted                                                                                649M   609G    96K  none mirr1tb/deleted/images                                                                             649M   609G    96K  none mirr1tb/deleted/images/7a7ff654cbd8f5f09bec03aa19d8d7d92649127d18659036a963b1ea63f90d25            649M   609G   649M  none mirr1tb/deleted/images/7a7ff654cbd8f5f09bec03aa19d8d7d92649127d18659036a963b1ea63f90d25@readonly      0      -   649M  - mirr1tb/images                                                                                2.43G   609G    96K  none mirr1tb/images/3e50ba589426c21f26370e2f949f30210f2d0419fbb9d4d4a0f860a035373353                    754M   609G   754M  none mirr1tb/images/3e50ba589426c21f26370e2f949f30210f2d0419fbb9d4d4a0f860a035373353@readonly              0      -   754M  - mirr1tb/images/58f90cbf68927c3fc43e6ee1386446a04f3d8068c1a75a291339cb2be01dec08                    651M   609G   651M  none mirr1tb/images/58f90cbf68927c3fc43e6ee1386446a04f3d8068c1a75a291339cb2be01dec08@readonly              0      -   651M  - mirr1tb/images/a221591e855f271769b3d780789c25d504b4062475c125f790b97d4afa0539f5                    653M   609G   653M  none mirr1tb/images/a221591e855f271769b3d780789c25d504b4062475c125f790b97d4afa0539f5@readonly              0      -   653M  - mirr1tb/images/eb34d444b13fdafe390f4022152c259395130ccc9d78b24f9cd1a550829fef7a                    431M   609G   431M  none mirr1tb/images/eb34d444b13fdafe390f4022152c259395130ccc9d78b24f9cd1a550829fef7a@readonly              0      -   431M  - mirr1tb/snapshots                                                                                392K   609G   104K  /mirr1tb/snapshots mirr1tb/snapshots/plex                                                                              96K   609G    96K  /mirr1tb/snapshots/plex mirr1tb/snapshots/plex-dbox                                                                         96K   609G    96K  /mirr1tb/snapshots/plex-dbox mirr1tb/snapshots/vpn-concentrator2                                                                 96K   609G    96K  /mirr1tb/snapshots/vpn-concentrator2
And then when I try to import with lxd:
root@bramdc-src-01:/home/jon# lxd import plex error: The container "plex" does not seem to exist on any storage pool.
Cheers,
Jon.

@bodleytunes Ok, so you'll want to do "zfs mount mirr1tb/containers/plex" and then make sure that you have some stuff in /var/lib/lxd/storage-pools/default/containers/plex.
Once that's the case, "lxd import plex" should then work better.

OK I will try now!
Cheers,
Jon.
On Tue, 19 Sep 2017 at 19:35 Stéphane Graber<EMAIL_ADDRESS>wrote:

@bodleytunes https://github.com/bodleytunes Ok, so you'll want to do
"zfs mount mirr1tb/containers/plex" and then make sure that you have some
stuff in /var/lib/lxd/storage-pools/default/containers/plex.
Once that's the case, "lxd import plex" should then work better.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/lxc/lxd/issues/3257#issuecomment-330631241, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AAly57wckdM1oxA-Cxpjd9eEDloeA7wSks5skAlxgaJpZM4NMp_U
.

OK got further this time but seen this message before, I think its looking in the wrong place and might need a symlink?
root@bramdc-src-01:/home/jon# lxd import plex error: open /var/lib/lxd/containers/plex/backup.yaml: no such file or directory root@bramdc-src-01:/home/jon#

Gah, I thought we had that one fixed...
So yeah, try creating a symlink from /var/lib/lxd/containers/plex to /var/lib/lxd/storage-pools/default/containers/plex and then try the import again.

no joy :(
root@bramdc-src-01:/home/jon# ln -s  /var/lib/lxd/storage-pools/default/containers/plex /var/lib/lxd/containers/plex root@bramdc-src-01:/home/jon# lxd import plex error: not found

Re-opening this. @brauner can you look into this and add it to your ever growing list of things to fix in "lxd import"?
Hopefully the design we agreed on in #3682 will help making things reliable in the future...

`root@bramdc-src-01:/var/lib/lxd/containers/plex# lxd import plex
error: No root device could be found.

Got a bit further I think
Ran this:
lxc profile device add default root disk path=/ pool=default
Which then let me import plex
root@bramdc-src-01:/var/lib/lxd/containers/plex# lxd import plex  root@bramdc-src-01:/var/lib/lxd/containers/plex# lxc list +------+---------+------+------+------------+-----------+ | NAME |  STATE  | IPV4 | IPV6 |    TYPE    | SNAPSHOTS | +------+---------+------+------+------------+-----------+ | plex | STOPPED |      |      | PERSISTENT | 0         | +------+---------+------+------+------------+-----------+
Then tried to start it, and it seems to take an age then finally comes back with an error :(
root@bramdc-src-01:/var/lib/lxd/containers/plex# lxc start plex error: Failed to run: /usr/bin/lxd forkstart plex /var/lib/lxd/containers /var/log/lxd/plex/lxc.conf:  Try lxc info --show-log plex` for more info
root@bramdc-src-01:/var/lib/lxd/containers/plex# lxc info --show-log plex
Name: plex
Remote: unix://
Architecture: x86_64
Created: 2017/09/19 21:09 UTC
Status: Stopped
Type: persistent
Profiles: default
Log:
        lxc<PHONE_NUMBER>1011.338 ERROR    lxc_conf - conf.c:run_buffer:416 - Script exited with status 1.
        lxc<PHONE_NUMBER>1011.338 ERROR    lxc_start - start.c:lxc_init:450 - Failed to run lxc.hook.pre-start for container "plex".
        lxc<PHONE_NUMBER>1011.338 ERROR    lxc_start - start.c:__lxc_start:1314 - Failed to initialize container "plex".
        lxc<PHONE_NUMBER>1011.338 WARN     lxc_commands - commands.c:lxc_cmd_rsp_recv:177 - Command get_cgroup failed to receive response: Connection reset by peer.

`

Ok, can you tell me:

lxc config show --expanded plex
What does /var/lib/lxd/containers/plex point to?
Does that target exist?
What's in /var/lib/lxd/storage-pools/
What does "lxc storage list" show you?

root@bramdc-src-01:/var/lib/lxd/containers/plex# lxc config show --expanded plex
architecture: x86_64
config:
boot.autostart: "true"
image.architecture: amd64
image.description: ubuntu 17.04 amd64 (release) (20170412.1)
image.label: release
image.os: ubuntu
image.release: zesty
image.serial: "20170412.1"
image.version: "17.04"
limits.network.priority: "8"
volatile.base_image: a221591e855f271769b3d780789c25d504b4062475c125f790b97d4afa0539f5
volatile.idmap.base: "0"
volatile.idmap.next: '[{"Isuid":true,"Isgid":false,"Hostid":100000,"Nsid":0,"Maprange":65536},{"Isuid":false,"Isgid":true,"Hostid":100000,"Nsid":0,"Maprange":65536}]'
volatile.last_state.idmap: '[{"Isuid":true,"Isgid":false,"Hostid":100000,"Nsid":0,"Maprange":65536},{"Isuid":false,"Isgid":true,"Hostid":100000,"Nsid":0,"Maprange":65536}]'
volatile.last_state.power: RUNNING
devices:
1500gbdisk:
path: /media/1500gb
source: /large1-5/1500gb_media
type: disk
bramnas:
path: /bramnas
source: /media/nas
type: disk
dreambox:
path: /media/dreamboxhdd
source: /media/dreambox-hdd
type: disk
root:
path: /
pool: default
type: disk
ephemeral: false
profiles:

default
stateful: false
description: ""

Just checking, looks empty ....  :(

Exists but empty is what we're expecting.

OK yes its empty:
root@bramdc-src-01:/home/jon# ls /var/lib/lxd/containers/plex
root@bramdc-src-01:/home/jon#  ls /var/lib/lxd/storage-pools/default/containers/plex
backup.yaml  metadata.yaml  plex  rootfs  templates

root@bramdc-src-01:/home/jon# ls /var/lib/lxd/storage-pools/
default

oh, hmm, that's confusing, so /var/lib/lxd/containers/plex is a directory and not a symlink?

Sorted it, it must have been some remnants of a fudged symlink, I did it all again ad its running 🥇

Thanks for your help!

sweet

Did it work properly for your other containers without manual messing with symlinks and such?

If so, then I guess we can close this issue again as 2.17 seems to behave for you after you upgraded to it.

This seems to be LXD 2.13 and if this is the symlink issue than this has been fixed and removed from my "ever-growing list" of import issues.

Hi Sorry for the delay in response.
I tried the import, and it succeeds but I still have to do the symlink . Even though I'm now using 2.17
Unless its something strange with my specific setup?
Cheers,
Jon.

 The commit is definitely in lxd-2.16 and lxd-2.17.

Possibly not unless it restarts the daemon when using apt dist-upgrade
I'll try again and see what happens.
On Wed, 20 Sep 2017 at 14:28 Christian Brauner<EMAIL_ADDRESS>wrote:

@bodleytunes https://github.com/bodleytunes, did you restart your
daemon after you upgrade to 2.17? The commit is definitely in lxd-2.16 and
lxd-2.17.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/lxc/lxd/issues/3257#issuecomment-330851283, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AAly52brh0_-phnzqwUUaU9TyxHcryJDks5skRMZgaJpZM4NMp_U
.

imported okay but looks to have not created the symlink properly

deleted the attempted symlink (vmhost) and created the manual way, rebooted and it works.

Ok, I'm about to rewrite the whole lxd import stuff so I'll keep this open for now.

OK :)
On Wed, 20 Sep 2017 at 16:34 Christian Brauner<EMAIL_ADDRESS>wrote:

Ok, I'm about to rewrite the whole lxd import stuff so I'll keep this open
for now.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/lxc/lxd/issues/3257#issuecomment-330890054, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AAly58COPqzJ2EMS9aYo1GhguqcnD_P4ks5skTBlgaJpZM4NMp_U
.

I think this can be closed due to https://github.com/lxc/lxd/pull/3828 being merged. If there are more issues or oversights, please open a new issue.

Hi,
I'm using lxd 2.18 in Ubuntu 16.04 server trying to recover a container after reinstalling:
I have a container in another hard disk (zfs), now I re-installed the system in the main hard disk (ubuntu 16.04), I follow this thread to recover:
zfs output:
mypool                                                                              1.43G  34.4G    19K  /mypool
mypool/dat                                                                          1.43G  34.4G    19K  none
mypool/dat/containers                                                                466M  34.4G    19K  none
mypool/dat/containers/c1                                                            13.4M  34.4G   305M  /var/lib/lxd/storage-pools/default/containers/c1
....

sudo lxc profile copy default dualnic
sudo lxc profile device add dualnic root disk path=/ pool=default
sudo lxd import c1
sudo lxc start c1

The container is not started, sudo lxc info --show-log c1 shows following:
Name: c1
Remote: unix://
Architecture: x86_64
Created: 2017/10/10 04:17 UTC
Status: Stopped
Type: persistent
Profiles: dualnic

Log:

            lxc<PHONE_NUMBER>1804.762 WARN     lxc_monitor - monitor.c:lxc_monitor_fifo_send:111 - Failed to open fifo to send message: No such file or directory.
            lxc<PHONE_NUMBER>1804.762 WARN     lxc_monitor - monitor.c:lxc_monitor_fifo_send:111 - Failed to open fifo to send message: No such file or directory.
            lxc<PHONE_NUMBER>1805.964 ERROR    dir - storage/dir.c:dir_mount:179 - No such file or directory - Failed to mount "/var/lib/lxd/containers/c1/rootfs" on "/usr/lib/x86_64-linux-gnu/lxc"
            lxc<PHONE_NUMBER>1805.964 ERROR    lxc_conf - conf.c:lxc_setup_rootfs:1313 - Failed to mount rootfs "dir:/var/lib/lxd/containers/c1/rootfs" onto "/usr/lib/x86_64-linux-gnu/lxc" with options "(null)".
            lxc<PHONE_NUMBER>1805.965 ERROR    lxc_conf - conf.c:do_rootfs_setup:3103 - failed to setup rootfs for 'c1'
            lxc<PHONE_NUMBER>1805.965 ERROR    lxc_conf - conf.c:lxc_setup:3144 - Error setting up rootfs mount after spawn
            lxc<PHONE_NUMBER>1805.965 ERROR    lxc_start - start.c:do_start:921 - Failed to setup container "c1".
            lxc<PHONE_NUMBER>1805.965 ERROR    lxc_sync - sync.c:__sync_wait:57 - An error occurred in another process (expected sequence number 5)
            lxc<PHONE_NUMBER>1805.965 WARN     lxc_monitor - monitor.c:lxc_monitor_fifo_send:111 - Failed to open fifo to send message: No such file or directory.
            lxc<PHONE_NUMBER>1805.965 WARN     lxc_monitor - monitor.c:lxc_monitor_fifo_send:111 - Failed to open fifo to send message: No such file or directory.
            lxc<PHONE_NUMBER>1805.966 ERROR    lxc_container - lxccontainer.c:wait_on_daemonized_start:760 - Received container state "ABORTING" instead of "RUNNING"
            lxc<PHONE_NUMBER>1805.968 ERROR    lxc_start - start.c:__lxc_start:1451 - Failed to spawn container "c1".
            lxc<PHONE_NUMBER>1805.968 WARN     lxc_monitor - monitor.c:lxc_monitor_fifo_send:111 - Failed to open fifo to send message: No such file or directory.
            lxc<PHONE_NUMBER>1805.968 WARN     lxc_monitor - monitor.c:lxc_monitor_fifo_send:111 - Failed to open fifo to send message: No such file or directory.
            lxc<PHONE_NUMBER>1805.189 WARN     lxc_monitor - monitor.c:lxc_monitor_fifo_send:111 - Failed to open fifo to send message: No such file or directory.
            lxc<PHONE_NUMBER>1805.189 WARN     lxc_monitor - monitor.c:lxc_monitor_fifo_send:111 - Failed to open fifo to send message: No such file or directory.
            lxc<PHONE_NUMBER>1805.189 WARN     lxc_commands - commands.c:lxc_cmd_rsp_recv:125 - Command get_cgroup failed to receive response: Connection reset by peer.

Can you please show:
ls -al /var/lib/lxd/containers
?

I re-installed the ubuntu 16.04 with virtual host option, and repeat the following steps:
sudo zfs mount mypool/dat/containers/c1
sudo lxd import c1
sudo lxc profile assign c1 default
sudo lxc start c1
error: no such file or directory
Try `lxc info --show-log c1` for more info

sudo lxc info --show-log c1
Name: c1
Remote: unix://
Architecture: x86_64
Created: 2017/10/11 07:47 UTC
Status: Stopped
Type: persistent
Profiles: default

Log:

ls -al /var/lib/lxd/containers shows following:
drwx--x--x  2 root root    4096 Oct 11 15:47 .
drwxr-xr-x 12 lxd  nogroup 4096 Oct 11 15:54 ..
lrwxrwxrwx  1 root root      44 Oct 11 15:47 c1 -> /var/lib/lxd/storage-pools/lxd/containers/c1
lrwxrwxrwx  1 root root      48 Oct 11 12:22 docker -> /var/lib/lxd/storage-pools/lxd/containers/docker
lrwxrwxrwx  1 root root      49 Oct 11 12:22 docker2 -> /var/lib/lxd/storage-pools/lxd/containers/docker2
lrwxrwxrwx  1 root root      49 Oct 11 13:58 docker3 -> /var/lib/lxd/storage-pools/lxd/containers/docker3
-rw-r--r--  1 root root    3052 Oct 11 12:10 lxc-monitord.log

not sure if following is what needed:
 mount |grep containers
lxd/containers/docker on /var/lib/lxd/storage-pools/lxd/containers/docker type zfs (rw,relatime,xattr,noacl)
lxd/containers/docker2 on /var/lib/lxd/storage-pools/lxd/containers/docker2 type zfs (rw,relatime,xattr,noacl)
mypool/dat/containers/c1 on /var/lib/lxd/storage-pools/default/containers/c1 type zfs (rw,relatime,xattr,noacl)

Oh I see what's going on here the container's symlink points to a wrong path...

Hm, we should force the mountpoint and symlink recreation. Sending a patch.

Oh wait, I totally missed that my import fixes didn't make it into LXD 2.18... So yeah, starting with the next LXD feature release 2.19 this should be fixed since we re-create any missing symlinks.

ok, actually I'm just testing the recovery option before putting lxd into production, for now I'll just keep this intact and wait for the next version to try out, thanks for the help.

We are using lxd in debian via snapd. Due to this issue we are not able to import containers after strorage issues which lead to OS reinstall.

Hmm, the fact that you're using the snap shouldn't interfere too much with the recovery process.
 Once that's done, make sure the containers are all mounted under /var/snap/lxd/common/lxd/storage-pools/POOL-NAME/containers/CONTAINER-NAME. Once that's all looking good, I'd recommend you restart the LXD snap (systemctl restart snap.lxd.daemon) to make sure there's no weird mount table entry. After that, I'd expect "lxd import" to behave properly.
Most of those steps are identical to a non-snap install. The main differences are the path at which things much be mounted and the fact that you'll need to restart the LXD daemon to have it refresh its mount table from the host.

I installed zfs on new system but for some reason zfs mount -a not working, i am only able to load  volumes manually. Also after importing container it fails to start with error similar to sqllyw’s one.

The fact that "zfs mount -a" doesn't work is expected as LXD volumes are marked with a flag which requires direct mounting.

So if I import container once does it means that LXD will continue to mount it’s volume after system reboot?

Once the container is known to LXD, LXD will dynamically mount/unmount the container's dataset as needed.

Well, for some reason it fails to do so and after reboot there is no files in contaners’s folder. Container shows up in lxc list.

@TechnicLab, what does fail? If you start the container lxc will mount the volume. Otherwise it will usually be unmounted.

In logs I see lots of not found errors.

Can you please show the logs?
Does the container actually start?

 This should change with 2.19.

root@host:/etc/ssh# lxc start firewall
error: Failed to run: /snap/lxd/4572/bin/lxd forkstart firewall /var/snap/lxd/common/lxd/containers /var/snap/lxd/common/lxd/logs/firewall/lxc.conf:
Try lxc info --show-log firewall for more info
root@host:/etc/ssh# lxc info --show-log firewall
Name: firewall
Remote: unix://
Architecture: x86_64
Created: 2017/10/15 14:15 UTC
Status: Stopped
Type: persistent
Profiles: public
Log:
        lxc<PHONE_NUMBER>1210.407 WARN     lxc_monitor - monitor.c:lxc_monitor_fifo_send:111 - Failed to open fifo to send message: No such file or directory.
        lxc<PHONE_NUMBER>1210.407 WARN     lxc_monitor - monitor.c:lxc_monitor_fifo_send:111 - Failed to open fifo to send message: No such file or directory.
        lxc<PHONE_NUMBER>1220.446 ERROR    lxc_conf - conf.c:run_buffer:438 - Script exited with status 1.
        lxc<PHONE_NUMBER>1220.446 ERROR    lxc_start - start.c:lxc_init:639 - Failed to run lxc.hook.pre-start for container "firewall".
        lxc<PHONE_NUMBER>1220.446 WARN     lxc_monitor - monitor.c:lxc_monitor_fifo_send:111 - Failed to open fifo to send message: No such file or directory.
        lxc<PHONE_NUMBER>1220.446 WARN     lxc_monitor - monitor.c:lxc_monitor_fifo_send:111 - Failed to open fifo to send message: No such file or directory.
        lxc<PHONE_NUMBER>1220.446 ERROR    lxc_start - start.c:__lxc_start:1418 - Failed to initialize container "firewall".
        lxc<PHONE_NUMBER>1220.447 ERROR    lxc_container - lxccontainer.c:wait_on_daemonized_start:751 - No such file or directory - Failed to receive the container state

Container is not running.

On Oct 16, 2017, at 17:34, Christian Brauner<EMAIL_ADDRESS>wrote:
Can you please show the logs?
Does the container actually start?
 This should change with 2.19.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub https://github.com/lxc/lxd/issues/3257#issuecomment-336906163, or mute the thread https://github.com/notifications/unsubscribe-auth/AJJ4HSnGIAWJvT5YiYNyLQjCYNSofmBCks5ss2mBgaJpZM4NMp_U.


Issue on page /api.html

I tried to establish a connection to my sqlite3 database which is located on my laptop's hard drive. I used the follwing example code from https://sfu-db.github.io/connector-x/databases/sqlite.html:
import connectorx as cx
db_path = '/home/user/path/test.db'                         # path to your SQLite database
conn = 'sqlite://' + db_path                                # connection token
query = 'SELECT * FROM `database.dataset.table`'            # query string
cx.read_sql(conn, query)                                    # read data from SQLite

Since I'm using Windows the path to the database contains a colon:
db_path = 'E:/my_db.db'
conn = 'sqlite://E:/my_db.db'

When I try to execute cx.read_sql(conn, 'select * from tablename') I get the following error message: [2023-01-21T19:01:47Z ERROR r2d2] unable to open database file: E/my_db.db
What's interesing about the error message is that the path to the database which it displays is missing the colon. It is E/my_db.db instead of E:/my_db.db. It it a bug? Or how can I establish the connection to my database on Windows?
I already posted the question on stackoverflow: :https://stackoverflow.com/questions/75195915/read-sql-from-sqlite3-database-in-windows-using-connectorx

Hi @johannesthird , for windows, can you try to construct and encode your url like this:
import urllib

path = urllib.parse.quote("E:\\your_path\\your_db.db")
df = cx.read_sql(f"sqlite://{path}", query)

Thx for helping me out @wangxiaoying. Although I don't get the same error I get a new one :(


OCM-11556 | fix: refactor multiple ca tests from getClusterRegistryConfig

https://issues.redhat.com/browse/OCM-11556

/retest


PyPI build doesn't seem to have latest version

I installed your extension using pip install --user sphinx-sitemap. version.py is updated but not __init__.py. See this diff:
diff ~/.local/lib/python2.7/site-packages/sphinx_sitemap/__init__.py __init__.py

19c19
<     """Setup conntects events to the sitemap builder"""
---
>     """Setup connects events to the sitemap builder"""
22c22
<         default='https://my-site.com/docs/',
---
>         default=None,

, etc.

I'm ramping up for the next version. Those changes in master are mostly refactoring right now, but I am hoping to merge #15 soon as I have a multi-lingual project I am working on, so I'll be able to test it out first hand. I plan to cut a new release when I feel that is stable enough.


Jasmine done() on setTimeout

If you run
describe("Testing", function () {

    it("1", function () {
        expect(false).toBeTruthy();
    });

    it("2", function (done) {
        setTimeout(function () {
            expect(false).toBeTruthy();
            done();
        }, 2000);
    });

});

with<EMAIL_ADDRESS>then only first test fails.
If you run the same code with<EMAIL_ADDRESS>or with jasmine+nodejs (http://jasmine.github.io/edge/node.html) then both test fails.

So the issue is related to protractor/node_modules/selenium-webdriver
With<EMAIL_ADDRESS>as a Protractor dependency the above example works, but with<EMAIL_ADDRESS>it doesn't.
There were some changes in Promise/ControlFlow:
https://github.com/SeleniumHQ/selenium/blob/master/javascript/node/selenium-webdriver/CHANGES.md#v2480

I've been hurt by this too. Another place it behaves funny is that one can't make a spec (it()) wait for anything async in the beforeEach, which used to be possible by either declaring beforeEach to take a done callback, or by returning a promise from beforeEach. It is intermingled with so many other oddities that I just assumed my setup was completely broken (an example is buttons that element-finders mislocate and when invoking the click I get the infamous would-hit-another-element exception -- injecting javascript asking the DOM for the location of the element confirms that selenium/protractor aren't doing it right.)

Confirmed - I see this error in jasminewd2 when upgrading from selenium-webdriver 2.47 to 2.48.

After some investigation, I believe this is a correctly working consequence of the control flow changes in selenium-webdriver.  In this case, this means that the task that executes expect will not be a child of the task which executes the it block. See an example here
There are two solutions here - you can use promise.delayed or flow.timeout instead of setTimeout.
We can also change the wrapping around expect so that it does not use the control flow at all if the argument is not a promise. This means that expect(true).toBe(false) will correctly fail within a timeout, but expect(myPromiseThatResolvesToTrue).toBe(false) still won't work. I'll make a PR to do that.

Protractor 3.1.0 now includes this commit from JasmineWD. This is fixed, given the big caveats in my comment above.

I find it hard to understand what changes in selenium that caused this change in behaviour, could you give me a hint? Is this somehow related to the fact that I have to wrap browser.removeMockModule() in a protractor.promise.controlFlow().execute() if I want to add and remove mock modules in the spec? Or is that an unrelated bug? Any spec with addMock();...;operate browser;...;removeMock() will see the removeMock executed prematurely since its not executed in the flow. I'm a bit confused about this -- I find it hard to believe that it's a bug nobody's been hurt by. :/

@PerBoussard I wonder if maybe your issue is not related to this. Are you doing any manual setTimeout? That was the main cause of this issue. If you have another problem that you can reproduce with the latest version, please open up a new issue.
The changes in selenium were how the control flow is managed - see https://github.com/SeleniumHQ/selenium/blob/master/javascript/node/selenium-webdriver/CHANGES.md#v2480


Crash when using compose v 1.8.0-alpha06 on android

Code
ModalBottomSheet(
        state = rememberModalBottomSheetState(initialDetent = SheetDetent.FullyExpanded),
    ) {
        Sheet(
            modifier = Modifier
                .background(Color.Red)
                .fillMaxSize(),
        ) {

        }
    }

Crash:
java.lang.NoSuchMethodError: No direct method <init>(Ljava/lang/Object;Lkotlin/jvm/functions/Function1;Lkotlin/jvm/functions/Function0;Landroidx/compose/animation/core/AnimationSpec;Landroidx/compose/animation/core/DecayAnimationSpec;Lkotlin/jvm/functions/Function1;ILkotlin/jvm/internal/DefaultConstructorMarker;)V in class Landroidx/compose/foundation/gestures/AnchoredDraggableState; or its super classes (declaration of 'androidx.compose.foundation.gestures.AnchoredDraggableState' appears in /data/app/~~oNy348mAOgdSFPflHFliag==/com.x.y.z-LrJmhEfwZDuVcA0oX9CIrw==/base.apk)
    	at com.composables.core.BottomSheetState.<init>(BottomSheet.kt:160)
    	at com.composables.core.BottomSheetKt.rememberBottomSheetState$lambda$17(BottomSheet.kt:85)
    	at com.composables.core.BottomSheetKt.$r8$lambda$HOlp03M64Z9EpLpUe6obdQw4518(Unknown Source:0)
    	at com.composables.core.BottomSheetKt$$ExternalSyntheticLambda12.invoke(D8$$SyntheticClass:0)

I've switched to stable version of compose and eveything works as it should.

Needs more info. Which platform and compose version is the crash from?

Android platform with compose androidx.compose:compose-bom-alpha:2024.11.00 bom version.

Was able to reproduce. Investigating

Fixed. Fix will be available on the next release

This is now available in 1.20.0


Ensure README code examples are all runnable

This will likely include removing and clarifying that when suites are passed for verification, they should not include key pairs (unless key-pinning is desired, which is an advanced case). Similarly, the examples should pass signer APIs (created via keypair.signer(), etc.) instead of passing key pairs for signing directly to encourage this pattern as it supports hiding / not exposing secret key material better.

Because I am new and wanted to explore the options, I started with the first README example:
import vc from '@digitalbazaar/vc';

// Required to set up a suite instance with private key
import {Ed25519VerificationKey2020} from '@digitalbazaar/ed25519-verification-key-2020';
import {Ed25519Signature2020} from '@digitalbazaar/ed25519-signature-2020';

const keyPair = await Ed25519VerificationKey2020.generate();

const suite = new Ed25519Signature2020({key: keyPair});

The first error was, that @digitalbazaar/vc has no default export, so the following import worked for me:
import * as vc from '@digitalbazaar/vc';

// [...]

Then to create my first VC, I used the code below:
// Sample unsigned credential
const credential = {
  "@context": [
    "https://www.w3.org/2018/credentials/v1",
    "https://www.w3.org/2018/credentials/examples/v1"
  ],
  "id": "https://example.com/credentials/1872",
  "type": ["VerifiableCredential", "AlumniCredential"],
  "issuer": "https://example.edu/issuers/565049",
  "issuanceDate": "2010-01-01T19:23:24Z",
  "credentialSubject": {
    "id": "did:example:ebfeb1f712ebc6f1c276e12ec21",
    "alumniOf": "Example University"
  }
};

const signedVC = await vc.issue({credential, suite, documentLoader});
console.log(JSON.stringify(signedVC, null, 2));

The problem with that was the documentLoader, which was not declared anywhere except in the custom documentLoader section. I re-engineered the code from jsonld-signatures and created the following simple documentLoader (which should not be used from a security perspective but works for the moment) that would preceed the above code:
const contexts = Object.create(null);

async function documentLoader(url) {
  if (!contexts[url]) {
    try {
      const response = await fetch(url)
      const document = await response.json()
      if (!document['@context']) throw new Error('invalid ContextDocument')
      contexts[url] = document
    } catch (err) {
      console.error(err)
      return defaultDocumentLoader(url)
    }
  }
  return { documentUrl: url, document: contexts[url] }
}

After all this, I still got the following error:
TypeError: "suite.verificationMethod" property is required.
    at Module.issue (file:///./node_modules/@digitalbazaar/vc/lib/index.js:123:11)
    at <anonymous> (./temp-sample.ts:44:27)

To just see a first result, I added the following before issuing the VC:
suite.verificationMethod = () => true;

This is obviously not the way it is meant to be, but I could also not find any documentation of the verificationMethod, how it is used and if I have to add it somewhere or this was an internal error.

Related to this are recent updates to an example script to issue and verify a VC and VP: https://github.com/digitalbazaar/vc/pull/162.
The readme examples should be fixed as is, and it might be good to additionally add examples using the newer data integrity support.


Move scene-node-details-header out of index.css

We are working on moving stuff out of index.css in favor of style object. I have started that transition here https://github.com/MiguelCastillo/scenic/pull/16
This ticket is to figure out how we want to move shared styles out of CSS.

Create a SceneNodeDetailsHeader component which wraps all the styles as a component.
Create a styles.js file in which we share styles.

Im definitely not a huge fan of option 2 because I have seen that pattern become easy to abuse where such file just has a whole bunch non semantic 1 off css styles.
Sample component
import * as React from "react";
import {PanelHeader} from "../components/panel.jsx";
export const SceneNodePanelHeader = (props) => {
  return (
    <PanelHeader style={styles.sceneNodePanelHeader}>
      {props.children}
    </PanelHeader>
  );
};
const styles = {
  sceneNodePanelHeader: {
    textTransform: "capitalize",
    padding: "1em",
    backgroundColor: "#000000",
  },
};

Ok we ended up with css imports in javascript and that was a nice way to share CSS styles.  And that was done in #16


Fix resize problems when charts are initially hidden

This commit aims to fix the resize problems for charts documented in #592 #762 #961 #1020 #1311 and #1395
It also possibly also fixes #1006 but this has not been tested.
New Dependency
Cloned javascript-detect-element-resize into the chart.js organization. Use this to detect when an individual canvas element resizes. This removes the need for the core.responsive file and so it is removed.
Aspect Ratios
Charts can now force an aspect ratio if the user does not specify the original canvas size. This will make the doughnut canvas square for instance if the user does not give it a size.
Canvas Size
Using the gist from #1395, the max-width property of the parent container should now be obeyed. destroy no longer changes the canvas style width and height properties.
Category Scale
Fixed a size issues caused by the category scale that caused the chart to not take up the entire canvas when the labels may have needed to rotate.
Doughnut and Polar Area Charts
Ensure that internal innerRadius and outerRadius properties are always >= 0 even when the canvas has no size (ie is display: none). This prevents crashes.
Samples
Updated the bar sample to hide the chart with a display: none style. Use the 'show' button to show the canvas container which triggers a resize.

@tannerlinsley @derekperkins please give this a good look over

Amazing work! Merging.


[SA-55649] Fix crash on SFSafariVC fallback

Problem:
ASWebAuthenticationSession.start() can return false meaning that it failed to start, but that automatically calls the completionHandler even before returning, which will invalidate the session automatically. In this case, the code falls back to SFSafariViewController which even on a successful login will fail and crash the application because the SDK will try to process an authorization response when the session has already been invalidated.
Resolution:
Make sure to only process completionHandler from ASWebAuthenticationSession when the auth presentation was successful.

@floschliep I have applied your suggestions, please take another look


Need access to test-packet-armv8-ubuntu-16-04

I need an access to test-packet-armv8-ubuntu-16-04 for investigating failures that don't occur on other machines.

One of the failures to investigate: https://github.com/eclipse/openj9/issues/9048

Created account<EMAIL_ADDRESS>and given access to it

@knn-k I assume this request was related to https://github.com/eclipse/openj9/issues/9042. Since that issue has been closed, do you still need access to test-packet-armv8-ubuntu-16-04?

You can disable my account at test-packet-armv8-ubuntu-16-04 for now.
Thanks.

@sxa in case he missed it

Your account has been removed from the machine


Dependencies for Struct support on Ubuntu 18.04

Here's what I needed to install before ctypes.sh would compile and pass all test in /tests folder:
# mandatory to built ctypes.sh without Structs:
sudo apt install autoconf libffi-dev libltdl-dev automake libtool

above are mandatory for ./autogen.sh to build ./configure
# mandatory to build ctypes.sh with Structs:
sudo apt install libdw-dev libelf-dev

The build script states that the failure is a lack of elfutils when actually it's a lack of libdwfl.h
The error would be much more helpful if it reported what the actual failure was instead of reporting the name of a package which it mistakenly assumes will bring in what's missing.

What would be the alternative for macos?

You should be able to build it for MacOS as well using homebrew.  Sorry but it's been a long time since I built anything on MacOS, but you should be able to follow the missing library errors and use that to search which brews to install, until it will eventually build.


Broken Organizations links

On the live website: https://fastify.github.io/website-next/
The homepage organization section is broken:

Images:

Links:

We must use the <Link component and solve the image issue as well (not sure how)

@Eomm let me look into


devspace does not create namespace for dependency deployment

What happened?
I declared a dependency in my devspace.yaml file with the namespace config option set. The namespace does not exist when starting the cluster. The deployment fails because the namespace isn't created.
What did you expect to happen instead?
Devspace should create this namespace automatically (see #605).
How can we reproduce the bug? (as minimally and precisely as possible)
My devspace.yaml:
version: v2beta1
name: xxx-api

pipelines:
   dev:
    run: |-
      run_dependencies --all
      create_deployments --all
      start_dev app

deployments:
  xxx-api:
    helm:
      chart:
        name: xxx-api
        repo: https://xxx.xxx.net/
        username: ${HELM_USERNAME}
        password: ${HELM_PASSWORD}
      valuesFiles: ["dev/values.yaml"]

dev:
  app:
    devImage: ghcr.io/lusu007/devspace-containers/typescript:18-alpine
    imageSelector: xxx.xxx.xxx:5005/xxx-api:nightly
    sync:
      - path: ./
        uploadExcludeFile: .dockerignore
    terminal:
      command: NPM_TOKEN=${NPM_TOKEN} ./devspace_start.sh
    ssh:
      enabled: true
    proxyCommands:
      - command: devspace
      - command: kubectl
      - command: helm
      - command: git
    ports:
      - port: "9229"
      - port: "3000"
    open:
      - url: http://localhost:3000
vars:
  HELM_PASSWORD:
    password: true
  NPM_TOKEN:
    question: "Please enter your NPM token:"
    password: true

dependencies:
  xxx-api:
    git: https://xxx.xxx/xx/xx/xxxx
    branch: dev
    pipeline: dev
    namespace: xxx-api

Local Environment:

DevSpace Version: 6.1.1
Operating System: Linux Ubuntu (WSL)
ARCH of the OS: AMD64
Kubernetes Cluster:
Cloud Provider: kind
Kubernetes Version:  v1.25.3

Anything else we need to know?

I'm experiencing this issue as well.

There was a pullrequest for this issue but it was closed without any reason.
You can create a function that creates the needed namespaces and call that function in your pipeline for a temporary workaround.
...
functions:
  create_namespaces: |
    kubectl create ns namespace1 --dry-run=client -o yaml | kubectl apply -f -
    kubectl create ns namespace2 --dry-run=client -o yaml | kubectl apply -f -

pipelines:
  deploy:
    run: |-
      run_dependencies --all
      ensure_pull_secrets --all
      build_images --all -t $(git describe --always)
      create_deployments --all
  dev:
    run: |-
      create_namespaces
      run_dependencies --all
      ensure_pull_secrets --all
      create_deployments --all
      start_dev app
...

Thanks @lusu007, I'm already using a similar workaround.
Additional calls to kubectl are causing me troubles when I deploy a project with many dependencies as it is hitting kubectl rate limits. Due to that I had to resolve to using --sequential flag, which slowed down everything noticeably.

Do we have any news on this?


Simple code won't work on 3.2.0 & 4.0.0

Hello, I am running on an AWS Lambda using winston papertrail and for some reason, the lambda won't respond on 4.0.0.
You'll find the code here (to test, replace with own papertrail host/port)
https://gist.github.com/quentinfasquel/78630bb57a7ab9a440f2a88f9acd5272

What's in the logs?

The app works super fine under express locally and I believe the issue is specific to AWS Lambda along a usage of winston-papertrail logger and alexa-app 4.0.0.
If the winston logger is closed (papertrail connection is closed) and the alexa-app 4.0.0 will respond, but the logs aren't sent. Without closing, the logs are sent but it will take too long and say "the requested skill...", but alexa-app 3.2.0 works fine with that.

@quentinfasquel it's difficult to tell, but I think the issue may be due to the fact that the lambda callback is waiting for an empty event loop but if you keep the papertrail connection open, this will not occur. I'm not sure why manually closing it prevents the logs from being sent, though.
Prior to 4.0.0, we were using .context to end the lambda function rather than .callback. You can set callbackWaitsForEmptyEventLoop = false:
exports.handler = (event, ctx, callback) => {
  ctx.waitsForEmptyEventLoop = false;
  alexa.request(event)
      .then(response => callback(null, response))
      .catch(callback));
}

Was this ever resolved?


[Bug]: navigateTo hidden pages is not working properly and breaking apps in deployed mode

Is there an existing issue for this?

[X] I have searched the existing issues

Description
NavigateTo function to go to hidden page is breaking. Users see blank page, if they refresh they can see the actual page but, this results in loss of the query params, which is not ideal. This is breaking the deployed apps in user's prod.
Steps To Reproduce
NavigateTo (1).json

Create 2 pages
Hide one
Try to navigate to from page 1 to hidden page.

I've uploaded a sample app.
Public Sample App
No response
Environment
Production
Severity
Critical (Broken Production apps)
Issue video log
No response
Version
Latest

We are also experiencing a similar issue
Expected Behavior: Navigation between custom tabs should work seamlessly in launch mode.
Actual Behavior: Navigation between custom tabs fails in launch mode but works correctly in edit mode.
Please let me know if you need any further information or if there are specific steps we should follow to address this issue.

@jeet-playleap Can you more details about this issue or loom recording maybe, if would be easier for us to triage this issue ? Thanks

Experiencing the same issue, temporarily unhid pages. Application was working fine for months, until two days ago it just stopped working due to this bug.

@luigifan9 this should now be fixed

@Nikhil-Nandagopal Yes it is fixed now, thanks


Default layout content slides under topbar

Checklist

[x] I have read the tutorials and know the correct effect of the functional design.
[x] There are no similar reports on existing issues (including closed ones).
[x] I found the bug on the latest code of the master branch.

Describe the bug

If I choose the default theme as my home page (to make the right panel disappear), the content slides below the top menu.
To Reproduce
Steps to reproduce the behavior:

Change index.html or another page layout to default
Add a content to the site.
Examine it in Developer Tools

Expected behavior

The content of the page must start in the same place as the other pages.
These 3 divs before the {{ content }} in the default.html solves the problem:

Screenshots

Environment

Command
Version

ruby -v
ruby 3.1.2p20 (2022-04-12 revision 4491bb740a) [x64-mingw-ucrt]

gem -v
3.3.7

bundle -v
2.3.15

bundle exec jekyll -v
jekyll 4.2.2

bundle info jekyll-theme-chirpy
jekyll-theme-chirpy (5.2.0)

Desktop

OS: Windows 10
Browser: Microsoft Edge 102.0.1245.33

Smartphone

Additional context

Please don't call exceptions caused by your code changes as bugs. Take the time to learn the basics of Jekyll and understand the code for this project.


FancyZones: Add "for this desktop" to the zone editor top label

Summary of the new feature/enhancement
If you breezed through the documentation it's easy to miss that you set the zones on a per-desktop basis depending on the location of the editor window when it's opened. Adding "for this desktop" to the existing "Choose your layout" label at the top of the zone editor window would provide an immediate implication that different layouts for different desktops can be specified.

like this?

That is exactly what I was thinking of.
On Fri, May 1, 2020, 5:04 PM Clint Rutkas<EMAIL_ADDRESS>wrote:

like this?
[image: image]
https://user-images.githubusercontent.com/1462282/80845082-1247da00-8bbd-11ea-8666-894136a10910.png
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/microsoft/PowerToys/issues/2564#issuecomment-622586293,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAFUXFACU2RTPJFY4IR5JDLRPNBQJANCNFSM4MWVAUEQ
.

The fix is now available in 0.18 https://github.com/microsoft/PowerToys/releases


chore: additional vue-router API preset

They are not included on purpose. As they are not commonly used enough, and createXX will only be called one per App. They probably don't need to be auto-imported.


Uncaught Error: Element ref was specified as a string (editor) but no owner was set.

I am using this package and before I didn't have any problem. but after updating react with npm install, this issue happen. When The page is rendering this component produce three errors and all the page goes blank. I do research but I found nothing useful. I don't know how to fix this. Here is my errors in chrome's console :
invariant.js:42 Uncaught Error: Element ref was specified as a string (editor) but no owner was set. You may have multiple copies of React loaded. (details: https://fb.me/react-refs-must-have-owner).     at invariant (invariant.js:42)     at coerceRef (react-dom.development.js:8579)     at reconcileSingleElement (react-dom.development.js:9379)     at reconcileChildFibers (react-dom.development.js:9477)     at reconcileChildrenAtPriority (react-dom.development.js:10127)     at reconcileChildren (react-dom.development.js:10118)     at finishClassComponent (react-dom.development.js:10254)     at updateClassComponent (react-dom.development.js:10226)     at beginWork (react-dom.development.js:10605)     at performUnitOfWork (react-dom.development.js:12573)
react-dom.development.js:8305 The above error occurred in the <MarkdownEditorContent> component:     in MarkdownEditorContent     in div     in MarkdownEditor (created by TopicEditComponent)     in div (created by TopicEditComponent)     in div (created by TopicEditComponent)     in div (created by TopicEditComponent)     in div (created by TopicEditComponent)     in form (created by TopicEditComponent)     in div (created by TopicEditComponent)     in TopicEditComponent (created by TopicComponent)     in div (created by TopicComponent)     in TopicComponent (created by CountryContainer)     in div (created by CountryContainer)     in CountryContainer (created by Connect(CountryContainer))     in Connect(CountryContainer) (created by RouterContext)     in div (created by CoreLayout)     in div (created by CoreLayout)     in CoreLayout (created by RouterContext)     in RouterContext (created by Router)     in Router (created by Routes)     in Routes     in Provider Consider adding an error boundary to your tree to customize error handling behavior. You can learn more about error boundaries at https://fb.me/react-error-boundaries.
react-dom.development.js:1345 Uncaught Error: A cross-origin error was thrown. React doesn't have access to the actual error object in development. See https://fb.me/react-crossorigin-error for more information.     at Object.invokeGuardedCallbackDev (react-dom.development.js:1345)     at invokeGuardedCallback (react-dom.development.js:1195)     at performWork (react-dom.development.js:12800)     at batchedUpdates (react-dom.development.js:13244)     at performFiberBatchedUpdates (react-dom.development.js:1646)     at stackBatchedUpdates (react-dom.development.js:1637)     at batchedUpdates (react-dom.development.js:1651)     at Object.batchedUpdatesWithControlledComponents [as batchedUpdates] (react-dom.development.js:1664)     at dispatchEvent (react-dom.development.js:1874)

The error is caused by this： https://reactjs.org/docs/refs-and-the-dom.html#legacy-api-string-refs

Hi,
Sorry for not answering before. I didn't receive any notifications in my emails.
I apologize.
@MehrnooshHajkhalil @gerryl1991 What version of react are you using?

Thanks. Will check.

I'm getting this too, any resolution? I am using:
react: 16.2.0
react-dom: 16.2.0
I was seeing it on 16, then upgraded, still seeing it.

Yes I didn't get to it yet. Let me see if I can fix the issue this weekend.

The issue right now is that Reflux is not compatible with React 16 as far as I can tell https://github.com/reflux/refluxjs/issues/537

@dsacramone @gerryl1991 @jaywcjlove @MehrnooshHajkhalil Can you try to install the package using: npm install --save react-markdown-editor@beta. That one should work with React 16.


model predictions were all grey

Thank you for your nice work. I had some problems with the code, my model predictions were all grey with a little bit of texture. What might be the cause of the error?

Hello, I guess it may be caused by not loading the trained model correctly.

您好，我想这可能是由于未正确加载训练的模型引起的。

Thank you

Hello, I guess it may be caused by not loading the trained model correctly.

Thank you

Hello, I guess it may be caused by not loading the trained model correctly.

Thank you

i meet the same problem, but i don't know how to solve it

@Qiublack @xiechenxi99 @cenchaojun How to load the trained model correctly ? I meet the same problem, I use test.py and i haven't change anything.


update ada_idna to support unicode 15.1

Thanks to @lemire, we can add unicode 15.1 support.

cc @annevk


Stale lock file prevents Prometheus start

tsdb puts a lock file into its directory to ensure exclusive access. This lock file is pid-based (e.g. not flock() based) and this leads to the following problem:

lock file is created
node is crashed
prometheus boots, finds stale lock, checks PID and if such PID is already occupied (by some other program) decides that the database is locked and exits.

I believe there are two possible solutions:

provide an option to configure lock file location, so it can be placed on tmpfs
switch to flock() based approach.

There's an option to disable the lock file, which should often be OK if your scheduling system ensures the safety via other means. Prometheus exposes this option through a flag as well.
OS file locks were initially used, however, there's a variety of rants on how badly everything around those is broken. Plain PID lock files remain the sanest option according to my research.
Two blog posts describing the madness quite well:

http://0pointer.de/blog/projects/locking.html
http://apenwarr.ca/log/?m=201012#13

Ok, I see. Thanks!

In absence of a better option than no locking or a conventional lock file, I'm closing here.

OS file locks were initially used, however, there's a variety of rants on how badly everything around those is broken. Plain PID lock files remain the sanest option according to my research.
Two blog posts describing the madness quite well:

http://0pointer.de/blog/projects/locking.html
http://apenwarr.ca/log/?m=201012#13

Those are interesting reads, and the conclusion I can draw from it is that POSIX locks should work just fine if you use it on sentinel files, i.e. not on files with real data. Modulo NFS, of course, but that's a special case.
Were there any problems in practice with the Prometheus 1.x file locks?

One problem I see is that people will run Prometheus on NFS. Regardless of whether we officially support it, we shouldn't block it unnecessarily.
The other is that we are working with a bunch of files here. Some coming, some going as Prometheus runs. Getting additional management of locks over those right is complexity. What we get for that complexity, though?  Which means applications would have to use the same kind of locking we do (and get it right!). If not, they can still do whatever they want with the files. There's no use case for multiple processes writing our files really, e.g. by locking byte ranges and concurrently writing to disjoint ranges.
The only thing we can and want to achieve is locking is two Prometheus processes running against the same data directory. A simple PID lock file seems to do this job perfectly with virtually no complexity overhead.
There are other things of course, out-of-process modifications to our immutable blocks can be used to implement things like complex retention policies. However, there's a safe and simple workflow for that: "disable compactions", "do stuff with files" (through atomic mv), "trigger TSDB to reload files", "re-enable compactions".
I have no full understanding of the degree of file locking Prometheus 1 does. I suppose the question is more whether it brings as many benefits as one would like to imagine, as the linked blog posts elaborate.

Prometheus 1.x was only ever locking the sentinel DIRTY file.
By using a POSIX lock for it, we avoided exactly the problem @pborzenkov has encountered before filing this issue.
The only case where the approach didn't work is on (arguably old-ish/broken) NFS setups or other non-POSIX compliant file systems. I would have thought that the problem @pborzenkov is way more common than the problem of non-POSIX compliant file systems. The option of disabling locks could also be used as an argument for NFS user (which could disable locks, or we could have an option of PID based locking just for them).
It would be (or have been, I guess) good to get some stats first what problem is actually more common.

Just edited my first response as I realized what you actually meant afterwards. That might actually be a good solution. That's not a breaking change I'd say so we can certainly improve in that direction at any point.

I think you are rather hinting at having a lock file over which a POSIX advisory lock is acquired, which won't suffer from the false non-return issue via PIDs? I have not considered that actually but sounds feasible.

Precisely. That's what Prometheus 1.x did. (At least in our own code. I think LevelDB did some locking on its own.)


ResourceRequest: prevent race condition

Description
This PR fixes a race condition in the resource request controller, which could cause the failure to retrieve a foreign cluster just created (during an incoming peering), missing at the same time the configuration of the appropriate controller reference. Additionally, it makes the controller reference configuration idempotent.
How Has This Been Tested?
Please describe the tests that you ran to verify your changes. Please also note any relevant details for your test configuration.

[x] Unit testing (existing + new)
[x] E2E testing (existing)

/test

/rebase test=true

/rebase

/merge


HOTT-3953: Fix synchronizer coupling between CDS and TARIC

Jira link
HOTT-
What?
I have added/removed/altered:

[ ] Refactored Tariff synchronizer to separate CDS and TARIC APIs

Why?
I am doing this because:

Have you? (optional)

[ ] Added documentation for new apis
[ ] Added new environment variables with correct values to all apps in all spaces

Deployment risks (optional)

Includes destructive/migratory actions which may effect critical data
Changes an api that is used in production

It would be good if we could add a rationale in the pull request template for future developers to know why we've done this.
I'm wondering what manually testing you've done?
I'd run sidekiq and see if the schedules for the workers look right:
bundle exec sidekiq
For xi/uk services, I'd manually run:

a rollback (both in the admin UI and in a ruby console)
a download
an apply

For the download step I'd make sure that we're actually physically downloading a file (we can delete one of the files in the s3 bucket)


New Office Deployment

Please Fire who ever came up with
Volume licensed versions of Visio 2019 are available directly from the Office CDN instead of from the Volume Licensing Service Center.
You had something that worked and people could deal with.

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: e3fc30fd-858c-d1cd-0729-6eb72ef7975a
Version Independent ID: aa690d1d-8e25-6de1-9a83-7acd851fed7a
Content: Deployment guide for Visio
Content Source: DeployOffice/deployment-guide-for-visio.md
Service: o365-proplus-itpro
GitHub Login: @DHB-MSFT
Microsoft Alias: danbrown

Hello @sknouse, sorry to hear you are dissatisfied with the way Office Click-to-Run products are acquired.  Can you explain a bit more what you are having difficulty with?  Perhaps we can clarify the steps or improve the process here.


concat all files produces error

when i concat all those files :
<!-- Javascript -->
<script src="./js/video.js" type="text/javascript" ></script>
<script src="//imasdk.googleapis.com/js/sdkloader/ima3.js"></script>
<script src="./js/videojs.ads.js" type="text/javascript" ></script>
<script src="./js/videojs.ima.js" type="text/javascript" ></script>

it make me an error :
local.js:804 Uncaught TypeError: Cannot read property 'Events' of undefined
at local.js:804
at local.js:804
it happens when i add videojs in top of all files it is mandatory for me to concat all files because only one file will be integrated on websites...
any idea?

Do you have a copy of the concatenated file I can take a look at? Also we strongly recommend against hosting your own copy of ima3.js - that file gets regular updates, and if you store it and use your own copy you'll miss out on those updates, which could break things in the future.

just contact with first video.js, then ima3.js sdk then ads.js then ima.js...mine is specifiq to me... that files is regular updated but for example brightcove recompile for his need and incorpore it into his js file.... i need to do the same thing and have a light SDK file how can i do ?

test.txt

Unfortunately the use case you describe for ima3.js is not supported - the SDK should error out if it sees that it's loaded from any domain other than the one on which we host it. Does this work if you concatenate all of the files except for ima3.js?

it is working with ima3.js after delete the exception in minimified JS... i will try it and say to you... but it is mandatory we have only one JS file -(

Unfortunately as noted above this is not supported - you'll need to load ima3.js from our servers, and not store a local copy of your own.

you say if i manage to get it locally and have for example the problem i have now it is not supported ? so no one could fix this issue ? thanks for great help!

I'm sorry I can't be of more help, but the SDK is reliant on you using the latest version at all times, so we enforce the policy that you cannot store the SDK file locally to ensure that you're always on the latest version.


LuckyPerms and Worldedit

Hi, I am trying to prevent the default permission from using world edit, but I have been unsuccessful thus far. I did try this "/lp group default permissions set worldedit.* false" but this didn't seem to work. I also noted that the autofill for the command groups, where it says minecraft and bukkit, does not mention worldedit. I would like to prevent people from crashing the server time and time again by removing the permissions for it from everyone. Please help me, this has begun to frustrate me.
Thank you,
Claire (psuedonym)

Make sure that you’re not using another perms plugin besides LuckPerms and that all users are either in the default group directly or that the group they are in inherits default.

The verbose command may also help you to diagnose the problem. :)
https://github.com/lucko/LuckPerms/wiki/Verbose


Actions for build automation

[x] ~Package and deploy TeamCloud.Providers.Core~
[x] Build and test Azure Providers
[x] Create publish zips for releases
[x] Split ci builds and release build

"Package and deploy TeamCloud.Providers.Core" has been set up in the workflow yml files, however it is currently commented out pending solution for issue #11.  Closing this issue and we'll track this step on #11 moving forward.


Inactive plugins are still listed

Inactive plugins should be marked as inactive or removed form the list... otherwise it's unclear why certain shortcuts don't work

Is the inactive means disable it in the Plugins panel of Sketch?

yes


Forgot to take out quotes.

Already did it in master :)

ok. :) Sorry, should have realised.

All good! Took like 2 seconds :)


[WIP] release: v3.6.0

TODO

[ ] Feat: support package.json exports field with webpack4
[ ] Refactor: rework configurable  TabBar for SPA and MPA
[ ] Fix: tschecker error with default template

Codecov Report

Merging #720 (7d10c1e) into master (c996d69) will increase coverage by 46.36%.
The diff coverage is n/a.

@@             Coverage Diff             @@
##           master     #720       +/-   ##
===========================================
+ Coverage        0   46.36%   +46.36%
===========================================
  Files           0       52       +52
  Lines           0     1320     +1320
  Branches        0      272      +272
===========================================
+ Hits            0      612      +612
- Misses          0      708      +708

Impacted Files
Coverage Δ

packages/plugin-rax-app/src/base.js
100.00% <0.00%> (ø)

packages/plugin-rax-app/src/setBuild.js
93.18% <0.00%> (ø)

packages/rax-babel-config/src/index.js
90.47% <0.00%> (ø)

packages/error-stack-tracey/src/index.js
0.00% <0.00%> (ø)

packages/rax-webpack-config/src/webpack.dev.js
100.00% <0.00%> (ø)

packages/plugin-rax-pha/src/setRegisterMethod.js
0.00% <0.00%> (ø)

packages/plugin-rax-pha/src/index.js
0.00% <0.00%> (ø)

packages/plugin-rax-app/src/setDev.js
82.50% <0.00%> (ø)

packages/plugin-rax-pha/src/phaDevUrls.js
0.00% <0.00%> (ø)

packages/plugin-rax-kraken/src/constants.js
100.00% <0.00%> (ø)

... and 42 more


How can I change the "batch_size"

I directly change the "batch_size" in file "execute_cora.py" from 1 to 10, and the following error occurred.
ValueError: Cannot feed value of shape (1, 2708, 1433) for Tensor 'input/Placeholder:0', which has shape '(10, 2708, 1433)'
So how can I change the "batch_size" when training or running the model ? Thx

把placehold中的batch_size改成None，不过也没什么用，代码每个epoch都是全量的node训练，蛋疼。

I directly change the "batch_size" in file "execute_cora.py" from 1 to 10, and the following error occurred.
ValueError: Cannot feed value of shape (1, 2708, 1433) for Tensor 'input/Placeholder:0', which has shape '(10, 2708, 1433)'
So how can I change the "batch_size" when training or running the model ? Thx

change placeholder batch_size to None，but this is not useful，every epoch the  model use full data， not node level。when graph is very big， need the change code to support node level train。

hello, do you know how to modify the value of the batch-size?
It seems  can't change it in the layer.py
If you don't mind ,could you please share experience of it?

hello, do you know how to modify the value of the batch-size? It seems can't change it in the layer.py
If you don't mind ,could you please share experience of it? This problem has been bothering me for a week, and I really can’t find a clue

hi， do you know how to modify the batch_size now?  ^_^

GAT is a full batch GNN model. If you require a mini-batch model, you need to graph sampling first.


Storj.io gateway integration

It would be cool if this service could integrate with some IPFS gateways and serve content from distributed sources.  I suggest starting with storj because it is fully S3 compatible.

Hi @jschiarizzi . We do support S3-compatible connectors today, although we haven't tested storj specifically. We'll make a note of that internally though. Does the S3-compatible connector help with your use case?

Yes it probably does. Potentially this is something I could help with too, I'm currently experimenting with making a web gateway for storj.
more info on their s3 compatibility is here: https://github.com/storj/storj/wiki/S3-Gateway

Thanks for letting us know. This appears to be an item the backend Kloudless API would need to support instead, although S3-compatible connectors are supported today. I'm closing this issue. for the File Explorer at the current time.


Remove BakerExtensions

There are not one, but two(!) files in this project named BakerExtensions.cs.  Both contain 1 method which is called one time, and both are highly coupled to one specific baker class.  These are not helpful abstractions, they are annoyances.  Please remove them and migrate the associated code to the calling Bake method.

There are actually 3 BakerExtensions classes. The reason behind that is this project is an example of what can be built on top of NSprites. Devs may often want to reconstruct baker classes I propose here. However in most cases even if you want to write your own baker class animation authoring process still strongly restricted by animation workflow design, so I've prepared baker extensions methods to let devs easily use them here and there in whatever they want baker.


Can I convert a pdf Page with this?

Is your feature request related to a problem? Please describe.
I want to convert a single pdf page into an image
Describe the solution you'd like
with android-pdfview and derivatives you could do something like this https://stackoverflow.com/questions/10698360/how-to-convert-a-pdf-page-to-an-image-in-android
Describe alternatives you've considered
android-pdfview of course but its huge

You can go inside my code and take the code reference where each page is being converted into a bitmap and use that.


Chrome extension: Add option/Default to collapse all items in outline

Link to PDF file (or attach file here):
Configuration:

Web browser and its version: Chrome, 53.0
Operating system and its version: Linux
PDF.js version: 1.5.294
Is an extension: Yes

Steps to reproduce the problem:

Open any PDF with table of contents, and the outline is displayed with everything expanded. For a file with large TOC, it takes a lot of scrolling to find/jump to the right item. This is exacerbated by the fact that outline width isn't adjustable, which means that the content wraps around, resulting in longer scrolls.

What is the expected behavior? (add screenshot)
Please add an option to, or make it the default behaviour that items in the outline start collapsed upon page load. In a stricter sense, only this will give an outline of the document! Users can later expand them as required.
To see how frustrating an expanded TOC is, try the ARM Architecture Manual for ARMv8 (login required) - it's 5000+ pages long, with a rather long and deep TOC.

Another alternative that comes to my mind is to offer a button to recursively expand/collapse a selected item in the TOC. When operated on top-level item thus expands/collapses the entire tree.

It currently is very poorly (or not at all even) surfaced in the UI, but please note that as mentioned in the FAQ, you can double-click on the "Show document outline" button to expand/collapse all outline items.
Furthermore, again please see the FAQ, by pressing the Shift key while clicking on the triangles you can expand/collapse all items under the selected item

Ha! That was basically what I was after. I'd rather have that displayed on the tool tips. Let me see if I can get a patch through.
(My previous comment was left from an account that I use at work)

Fixed by #7717.


Explicitly close the socket in the reconnect loop.

This is needed to make sure these sockets don't connect to the server
when it becomes available thus creating orphaned connections.

Fix for https://github.com/tinode/tindroid/issues/51


parse and displayraw transactions on transaction page

What kind of PR is this?:

/kind feature
What this PR does / why we need it:
Which issue(s) does this PR fixes?:

Fixes #590
Sample Links & Screenshots:

Link:

Desktop Screenshot

Mobile Screenshot

Additional comments?:
Developer Checklist:

[ ] Read your code changes at least once
[ ] Tested on multiple web browsers
[ ] Tested responsiveness (e.g, iPhone, iPad, Desktop)
[ ] No console errors
[ ] Unit tests*
[ ] Added e2e tests*

A few comments:

Follow the previous design of how vout/vins are displayed.
DfTx can be retrieved by:

  function getDfTx (vouts: Vout[]): DfTx<any> | undefined {
    const stack = vouts[0].script.stack
    if (stack.length !== 2 || stack[1].type !== 'OP_DEFI_TX') {
      return undefined
    }
    return (stack[1] as OP_DEFI_TX).tx
  }

Only show Pending TX if the TX has not been confirmed.

Example 1 (Composite Swap)
Example 2 (Composite Swap)
Example 3 (Auction Bid)
Example 4 (Take Loan)

Changes Needed:

Only show Raw Tx if the Tx is still pending
Add a check to ensure that Raw Tx provided is valid (No errors when processing)
Follow the design exactly
- Missing arrow between Input and Output
- Increase padding between "Pending Tx" and Input/Output section


Using paraformer-en model returns an error: [WinError 2] The system cannot find the file specified

Steps to reproduce

Deploy a model Hugging Face/funasr/paraformer-en
Open in playground and generate the text.

Result

Returned an error.

Failed to transcribe audio, [WinError 2] The system cannot find the file specified

Environment

GPUStack version: main 28e5269
OS: Windows 11
GPU: NVIDIA 4080

Additional context
Add any other context about the problem here.

Verified on main 81ac226


Remove unnecessary entries in build.gradle

Current coverage is 89.13% (diff: 100%)

Merging #3 into master will not change coverage

@@             master         #3   diff @@
==========================================
  Files             4          4
  Lines            92         92
  Methods           0          0
  Messages          0          0
  Branches         14         14
==========================================
  Hits             82         82
  Misses            5          5
  Partials          5          5

Powered by Codecov. Last update b83047f...a3c9f26


Unable to access the program

After installation, I can't find the installation to launch it

Hi @folychael
Can you explain a little bit?
Do you install in what OS? How did you install it? What steps did you use?
Is the Python you used for TEx the system one? Or did you use VENV?


Fix parse for "relationships"

add "type" condition to parsing relationships data
please check test code 😉

@kozo002 Good fix and thanks for the added tests!


SDDS not working with Vue3/Vite

Describe the bug
When using Vite (https://vitejs.dev) as bundler for a Vue3 project will SDDS generate errors which stops rendering of the page.
ReferenceError: require is not defined
at @scania_components.js:1726
at async initializeComponent (@scania_components.js:1421) undefined
consoleError @ index-5cfef938.js:1713
index-5cfef938.js:1366 Uncaught (in promise) TypeError: Cannot read property 'isProxied' of undefined
at initializeComponent (@scania_components.js:1424)
The same code works fine in a Vue3 project using Vue CLI.
To Reproduce

Generate a shell project in Vue3 using Vite (Instructions at https://vitejs.dev)
Follow basic instructions for adding SDDS.
Add a  component and some HTML.
Run and check the console

Demo project can be found here: https://gitlab.scania.com/sssmzb/sdds-vue3-vite (internal)
Expected behavior
SDDS in combination with Vue3 should be possible to bundle with Vite.
Screenshots
If applicable, add screenshots to help explain your problem.
Version of SDDS
"@scania/components": "^1.4.2",
"@scania/theme-light": "^2.1.0",
Framework and version
"vue": "^3.0.5"
"vite": "^2.1.5"
Repo link
https://gitlab.scania.com/sssmzb/sdds-vue3-vite
Desktop information:
Chrome 89
AB#744

Will be solved with the release of @scania/tegel.