"error: No storage pool specified." after upgrade lxd to 2.9.1

Required Information

Distribution: lubuntu
Distribution version: 16.04.2 LTS
The output of "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
api_status: stable
api_version: "1.0"
auth: trusted
public: false
environment:
  addresses: []
  architectures:
  - x86_64
  - i686
  certificate: |
    -----BEGIN CERTIFICATE-----
    MIIFRjCCAy6gAwIBAgIQUMwlqmF+TOJrioPa/pyE0DANBgkqhkiG9w0BAQsFADA2
    MRwwGgYDVQQKExNsaW51eGNvbnRhaW5lcnMub3JnMRYwFAYDVQQDDA1yb290QHBj
    bWFudWVsMB4XDTE2MTIyNzEyMTEzOFoXDTI2MTIyNTEyMTEzOFowNjEcMBoGA1UE
    ChMTbGludXhjb250YWluZXJzLm9yZzEWMBQGA1UEAwwNcm9vdEBwY21hbnVlbDCC
    AiIwDQYJKoZIhvcNAQEBBQADggIPADCCAgoCggIBALBspNcymKEEw/xADobg9MFI
    06rp0FBy7zPJ6lOOr6duKcRv83q/xC9UaMmqje4XNNJLKNIhvjTVjeRuNP4DxuAz
    wU3aYID5R3k/8llOFencIuSxq4aaBemcSZr8LQK0DucbJ0rEua6dKgQbXENxTtIY
    oLwTGjW/EfHbahpFSvK0E3XkFVojXTMhaInCcSXFihhVOzvPBKW+swB5hDIBi35m
    oUuYi1c2K/KNenSBcID0+qY1kIv/H3FwH3W2mUvebsdc/EgaT49E9H0GY77P6wj7
    ovk3qF+LyKF7b/CCReyxpgYroC19Ih6pi7jE5eDXTGl7ALoEtoIuIoPoF9vl600J
    b1KAZCZhxKgf6eO0rRGSDl+RVc6dklDupxa4d764/Fu6FoDGBUqQ+2+LTC4FN/i4
    xgQfQew4eMGM7PUCMwwg0o8ezEsA7nt6IWtJv7oel1DPdmOJqtOi2hLHHVJ2u47K
    bIbER3y7e8KRC68M6gQdatyH+VV+Hhcngso5lBAcH3oBQCB5FtbYAWAgBxhktd9+
    PmtlvQgV4gPwtipnh5dlRBIp5I4x1nSuu64ALONjzacKkkssjR/xbIYjp4dsw2E7
    rFY9oIBEDTn7SBMegTBY0Tk8vM3XKkVOpaZV+IjQTU673N0yVcCN8aVaKIMCDRH5
    czRtHrUK6nVr1kuDdpyFAgMBAAGjUDBOMA4GA1UdDwEB/wQEAwIFoDATBgNVHSUE
    DDAKBggrBgEFBQcDATAMBgNVHRMBAf8EAjAAMBkGA1UdEQQSMBCCCHBjbWFudWVs
    hwTAqAEsMA0GCSqGSIb3DQEBCwUAA4ICAQAUkyyt9i27e+Uy8Ee4htVfoIMHiN9D
    C0tJ5MJun6ye7JwP0SR4t4m/fq36h8/iGn+g8IVifzObeW5w+aoIEFLNsPzg7Ivs
    +NVhdylEJGquU1ZtXAk2+JNrnZ5qZWVFrlKN5SXhNrF8A3TTQjnZrXNLC/+/NImW
    cXsxNczEkXUswnx7J99uK12LoRz+EEFhyi1TKF1zF5QHybjYxgKdcFSt3ILviXp7
    DwQ/dEZzEC28I0Ztrn9JuQOW3k0v2NqQdpTEZU2U27cMlP+UCQlc2b4wi89S4BE3
    gsa5ZnJfCUYcTQ4q+8H228TEs7mgVMZ6RDXaBdUl2cg974XFvgFSw/VW2clJrTh7
    ForEl2kP7Fzkdmph3n4rdp2vOhkqt+f1iuyi2ngFCR8psExbH5mhJMKZcBeWDNNm
    Xngm/Q7MS0jSwUYvvCmMEwBgvqDuoG8L1QBbe5j+WL0RYz+aCdWg18nHG2sV1J3H
    VH+AygVi9UUQe22yyBKsa0xOr+SrbFg3TGQXhdI8RTynRcSL5TgwsKNxVfEJNUpL
    je1mxPbV1JUlASKzA9RRNCoQnbklBjgZ8Xf7rEsuUqwrajhjRDFNeZ+0PfKPYx7X
    SWbgc02DBR/HDv2y24qvmXHHoawJc8/tQX6L32PdIP3h/xCz2DgfomeIJHicVCbq
    z0+3osJShnp2Yg==
    -----END CERTIFICATE-----
  certificate_fingerprint: d6052c34cef7200ea3c4d90b7f358da514deb515a3858e00e2b4a9fe0effa595
  driver: lxc
  driver_version: 2.0.7
  kernel: Linux
  kernel_architecture: x86_64
  kernel_version: 4.4.0-62-generic
  server: lxd
  server_pid: 2358
  server_version: 2.9.1
  storage: zfs
  storage_version: <IP_ADDRESS>-0ubuntu15

Issue description
After upgrade lxd to 2.9.1 version, all containers are working except one. When I try to start this container appears that mesage: error: No storage pool specified. ZFS pool is ok and the files associated with the container seem to be ok.
Information to attach
lxc ls: the container proxy is in status ERROR
manuel@pcmanuel:~$ lxc ls -c n,s,4,6,P,S,l,t
+------------+---------+----------------------+------+----------+-----------+----------------------+------------+
|   NOMBRE   | ESTADO  |         IPV4         | IPV6 | PERFILES | SNAPSHOTS |     LAST USED AT     |    TIPO    |
+------------+---------+----------------------+------+----------+-----------+----------------------+------------+
| apt-cacher | RUNNING | <IP_ADDRESS> (eth0) |      | default  | 0         | 2017/02/18 20:47 UTC | PERSISTENT |
+------------+---------+----------------------+------+----------+-----------+----------------------+------------+
| proxy      | ERROR   |                      |      |          |           |                      | PERSISTENT |
+------------+---------+----------------------+------+----------+-----------+----------------------+------------+
| server01   | STOPPED |                      |      | default  | 0         | 2017/02/18 20:49 UTC | PERSISTENT |
+------------+---------+----------------------+------+----------+-----------+----------------------+------------+
| vsftpd     | STOPPED |                      |      | default  | 0         | 2017/02/18 20:01 UTC | PERSISTENT |
+------------+---------+----------------------+------+----------+-----------+----------------------+------------+

Start proxy container:
manuel@pcmanuel:~$ lxc start proxy
error: No storage pool specified.
manuel@pcmanuel:~$ lxc start --debug proxy
DBUG[02-19|00:35:25] Raw response: {"type":"sync","status":"Success","status_code":200,"operation":"","error_code":0,"error":"","metadata":{"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"],"api_status":"stable","api_version":"1.0","auth":"trusted","public":false,"environment":{"addresses":[],"architectures":["x86_64","i686"],"certificate":"-----BEGIN CERTIFICATE-----\nMIIFRjCCAy6gAwIBAgIQUMwlqmF+TOJrioPa/pyE0DANBgkqhkiG9w0BAQsFADA2\nMRwwGgYDVQQKExNsaW51eGNvbnRhaW5lcnMub3JnMRYwFAYDVQQDDA1yb290QHBj\nbWFudWVsMB4XDTE2MTIyNzEyMTEzOFoXDTI2MTIyNTEyMTEzOFowNjEcMBoGA1UE\nChMTbGludXhjb250YWluZXJzLm9yZzEWMBQGA1UEAwwNcm9vdEBwY21hbnVlbDCC\nAiIwDQYJKoZIhvcNAQEBBQADggIPADCCAgoCggIBALBspNcymKEEw/xADobg9MFI\n06rp0FBy7zPJ6lOOr6duKcRv83q/xC9UaMmqje4XNNJLKNIhvjTVjeRuNP4DxuAz\nwU3aYID5R3k/8llOFencIuSxq4aaBemcSZr8LQK0DucbJ0rEua6dKgQbXENxTtIY\noLwTGjW/EfHbahpFSvK0E3XkFVojXTMhaInCcSXFihhVOzvPBKW+swB5hDIBi35m\noUuYi1c2K/KNenSBcID0+qY1kIv/H3FwH3W2mUvebsdc/EgaT49E9H0GY77P6wj7\novk3qF+LyKF7b/CCReyxpgYroC19Ih6pi7jE5eDXTGl7ALoEtoIuIoPoF9vl600J\nb1KAZCZhxKgf6eO0rRGSDl+RVc6dklDupxa4d764/Fu6FoDGBUqQ+2+LTC4FN/i4\nxgQfQew4eMGM7PUCMwwg0o8ezEsA7nt6IWtJv7oel1DPdmOJqtOi2hLHHVJ2u47K\nbIbER3y7e8KRC68M6gQdatyH+VV+Hhcngso5lBAcH3oBQCB5FtbYAWAgBxhktd9+\nPmtlvQgV4gPwtipnh5dlRBIp5I4x1nSuu64ALONjzacKkkssjR/xbIYjp4dsw2E7\nrFY9oIBEDTn7SBMegTBY0Tk8vM3XKkVOpaZV+IjQTU673N0yVcCN8aVaKIMCDRH5\nczRtHrUK6nVr1kuDdpyFAgMBAAGjUDBOMA4GA1UdDwEB/wQEAwIFoDATBgNVHSUE\nDDAKBggrBgEFBQcDATAMBgNVHRMBAf8EAjAAMBkGA1UdEQQSMBCCCHBjbWFudWVs\nhwTAqAEsMA0GCSqGSIb3DQEBCwUAA4ICAQAUkyyt9i27e+Uy8Ee4htVfoIMHiN9D\nC0tJ5MJun6ye7JwP0SR4t4m/fq36h8/iGn+g8IVifzObeW5w+aoIEFLNsPzg7Ivs\n+NVhdylEJGquU1ZtXAk2+JNrnZ5qZWVFrlKN5SXhNrF8A3TTQjnZrXNLC/+/NImW\ncXsxNczEkXUswnx7J99uK12LoRz+EEFhyi1TKF1zF5QHybjYxgKdcFSt3ILviXp7\nDwQ/dEZzEC28I0Ztrn9JuQOW3k0v2NqQdpTEZU2U27cMlP+UCQlc2b4wi89S4BE3\ngsa5ZnJfCUYcTQ4q+8H228TEs7mgVMZ6RDXaBdUl2cg974XFvgFSw/VW2clJrTh7\nForEl2kP7Fzkdmph3n4rdp2vOhkqt+f1iuyi2ngFCR8psExbH5mhJMKZcBeWDNNm\nXngm/Q7MS0jSwUYvvCmMEwBgvqDuoG8L1QBbe5j+WL0RYz+aCdWg18nHG2sV1J3H\nVH+AygVi9UUQe22yyBKsa0xOr+SrbFg3TGQXhdI8RTynRcSL5TgwsKNxVfEJNUpL\nje1mxPbV1JUlASKzA9RRNCoQnbklBjgZ8Xf7rEsuUqwrajhjRDFNeZ+0PfKPYx7X\nSWbgc02DBR/HDv2y24qvmXHHoawJc8/tQX6L32PdIP3h/xCz2DgfomeIJHicVCbq\nz0+3osJShnp2Yg==\n-----END CERTIFICATE-----\n","certificate_fingerprint":"","driver":"lxc","driver_version":"2.0.7","kernel":"Linux","kernel_architecture":"x86_64","kernel_version":"4.4.0-62-generic","server":"lxd","server_pid":2358,"server_version":"2.9.1","storage":"zfs","storage_version":"<IP_ADDRESS>-0ubuntu15"}}}

DBUG[02-19|00:35:25] Raw response: {"error":"No storage pool specified.","error_code":500,"type":"error"}

error: No storage pool specified.

Status of zfs pool:
manuel@pcmanuel:~$ sudo zpool status
  pool: lxd
 state: ONLINE
  scan: scrub repaired 0 in 0h0m with 0 errors on Sun Jan  8 00:24:33 2017
config:

	NAME        STATE     READ WRITE CKSUM
	lxd         ONLINE       0     0     0
	  sdc       ONLINE       0     0     0

errors: No known data errors
manuel@pcmanuel:~$ sudo sudo zpool list
NAME   SIZE  ALLOC   FREE  EXPANDSZ   FRAG    CAP  DEDUP  HEALTH  ALTROOT
lxd    464G  1,90G   462G         -     0%     0%  1.00x  ONLINE  -
manuel@pcmanuel:~$ sudo zfs list
NAME                                                                                USED  AVAIL  REFER  MOUNTPOINT
lxd                                                                                1,90G   448G    96K  none
lxd/containers                                                                        503M   448G    96K  none
lxd/containers/apt-cacher                                                             139M   448G   428M  /var/lib/lxd/storage-pools/lxd/containers/apt-cacher
lxd/containers/proxy                                                                  109M   448G   412M  /var/lib/lxd/storage-pools/lxd/containers/proxy
lxd/containers/server01                                                              43,2M   448G   360M  /var/lib/lxd/storage-pools/lxd/containers/server01
lxd/containers/vsftpd                                                                 212M   448G   481M  /var/lib/lxd/storage-pools/lxd/containers/vsftpd
lxd/deleted                                                                          1,05G   448G    96K  none
lxd/deleted/images                                                                   1,05G   448G    96K  none
lxd/deleted/images/5f19596a09c19d4beed653de08ea438c32e2fee35a10c6963a8285cae95c0a43   360M   448G   360M  none
lxd/deleted/images/8573fa6fed57ecadbb6f76f6b424533e4a8c5a562e29cee28ba47b6923aa4f88   360M   448G   360M  none
lxd/deleted/images/d57cf522816f735c132b9eac444e86557c9b43e30dde7ba0dc61a7dbde3933a6   360M   448G   360M  none
lxd/images                                                                            361M   448G    96K  none
lxd/images/3b825a6a063aacc6b19df84f7ddc4fe872a0e382ec0bb92f475a9493b0857e01           360M   448G   360M  none

Files:
manuel@pcmanuel:~$ ls -lahF /var/lib/lxd/storage-pools/lxd/containers/proxy
total 39K
drwxr-xr-x  4<PHONE_NUMBER>36    6 ene 24 12:19 ./
drwx--x--x  6 root   root   4,0K feb 18 21:53 ../
-r--------  1 root   root   2,4K feb 18 01:34 backup.yaml
-rw-r--r--  1 root   root   1,5K ene 10 21:52 metadata.yaml
drwxr-xr-x 22<PHONE_NUMBER>36   23 ene 24 16:59 rootfs/
drwxr-xr-x  2 root   root      8 ene 10 21:52 templates/

Container log:
manuel@pcmanuel:~$ lxc info proxy --show-log
error: No storage pool specified.

Hi, can you please show the output of:

sqlite3 /var/lib/lxd/lxd.db "SELECT name FROM storage_pools"
sqlite3 /var/lib/lxd/lxd.db "SELECT name FROM storage_volumes"

@brauner the reason for the failure here is that the "proxy" container doesn't use any profiles and LXD didn't fill the "pool" property on upgrade. It's the same problem that's hitting people who migrate containers from pre-2.9 to 2.9 as the container will have a "root" disk entry but no pool property, leading to the container failing to start.
@mgregal You can try:
lxc config device set proxy root pool default

I'm not sure it's going to work though as that pool config check seems to be triggering even when reading the container's config...

@stgraber, actually the upgrade fills in the storage pool device. Only when the default profile isn't find it won't. We could try on upgrade to give each container that is not on the default profile it's local root disk device.

@brauner I think we need something like this.
On upgrade:

Update the default profile
Iterate through all existing containers

Find where the container's root is stored (mentioned later as CTPOOL)
Check ExpandedDevices for a valid root entry (type=disk path=/ pool=CTPOOL), if found, skip to next container
Set the local root disk in Devices to have a pool property pointing to CTPOOL

On copy:

Find where the container's root is stored (mentioned later as CTPOOL)
Check ExpandedDevices for a valid root entry (type=disk path=/ pool=CTPOOL), if found, skip to next container
Set the local root disk in Devices to have a pool property pointing to CTPOOL

That should take care of the upgrade problem when people have a container which doesn't use the default profile and will also take care of the copying from an older LXD problem as it'll fill the pool property as needed on copy.
Does that seem reasonable?

@stgraber
lxc config device set proxy root pool default don't work for me:
manuel@pcmanuel:~$ lxc config device set proxy root pool default
error: No storage pool specified.

But your answer and the conversation with brauner makes me to see that the "proxy" container has a specific profile (2NICs). I compared the default and the proxy profile and saw the differences. The proxy profile 2NICs haven't got defined a root disk device. I proceed to add the root disk device and the zfs pool and it works!. Now the profile is:
manuel@pcmanuel:~$ lxc profile show 2NICs
config: {}
description: ""
devices:
  eth0:
    nictype: bridged
    parent: br0
    type: nic
  eth1:
    name: eth1
    nictype: bridged
    parent: int172-16
    type: nic
  root:
    path: /
    pool: lxd
    type: disk
name: 2NICs
used_by:
- /1.0/containers/proxy

Now the container is working
manuel@pcmanuel:~$ lxc ls -c n,s,4,6,P,S,l,t
+------------+---------+--------------------------------+------+----------+-----------+----------------------+------------+
|   NOMBRE   | ESTADO  |              IPV4              | IPV6 | PERFILES | SNAPSHOTS |     LAST USED AT     |    TIPO    |
+------------+---------+--------------------------------+------+----------+-----------+----------------------+------------+
| apt-cacher | STOPPED |                                |      | default  | 0         | 2017/02/18 20:47 UTC | PERSISTENT |
+------------+---------+--------------------------------+------+----------+-----------+----------------------+------------+
| proxy      | RUNNING | <IP_ADDRESS> (eth0)           |      | 2NICs    | 0         | 2017/02/19 16:09 UTC | PERSISTENT |
|            |         | <IP_ADDRESS> (eth1)          |      |          |           |                      |            |
+------------+---------+--------------------------------+------+----------+-----------+----------------------+------------+
| proxy2     | STOPPED |                                |      | 2NICs    | 0         |                      | PERSISTENT |
+------------+---------+--------------------------------+------+----------+-----------+----------------------+------------+
| server01   | STOPPED |                                |      | default  | 0         | 2017/02/18 20:49 UTC | PERSISTENT |
+------------+---------+--------------------------------+------+----------+-----------+----------------------+------------+
| vsftpd     | STOPPED |                                |      | default  | 0         | 2017/02/18 20:01 UTC | PERSISTENT |
+------------+---------+--------------------------------+------+----------+-----------+----------------------+------------+

Without the root disk device into the profile the container proxy can't start and even I can't create a new container using that profile.
Thanks for the answer and your fantastic work

@brauner
Hi, the problem is solved but the outputs:
manuel@pcmanuel:~$ sqlite3 /var/lib/lxd/lxd.db "SELECT name FROM storage_pools"
lxd
manuel@pcmanuel:~$ sqlite3 /var/lib/lxd/lxd.db "SELECT name FROM storage_volumes"
apt-cacher
proxy
server01
vsftpd
3b825a6a063aacc6b19df84f7ddc4fe872a0e382ec0bb92f475a9493b0857e01

apt-cacher, server01, vsftpd are containers using the default profile
proxy is the problematic container using a special profile
3b825a6a.. is an image ubuntu 14.04 64 bits
Thanks and salutes from Spain

@mgregal, cool. Glad that problem was solved. There will be a couple of improvements to profile handling in the next release that should avoid these issues.
@stgraber, sounds good so far. I will implement tomorrow and see whether it all works out or if I need adaptions.

@stgraber, also the issue with setting the storage pools with lxc config device set ... should be addressed in PR https://github.com/lxc/lxd/pull/2903, specifically:

https://github.com/lxc/lxd/pull/2903/commits/0e9fb70c3f24857c2adc92c79ec00a1c053eaa79
and
https://github.com/lxc/lxd/pull/2903/commits/cbd2b0feac32a0eb484a8e35fc60622d2b5773f1

Same issue here. All my containers were created with a custom profile and I got the storage pool error when trying to start them:
error: No storage pool specified.
After editing the custom profile and inserting the root device entry everything is working again:
~$ lxc profile edit bridged

devices:
  root:
    path: /
    pool: default
    type: disk

I also had this issue (or similar) and definitely was not expecting a minor version bump to cause such a large issue. Definitely would recommend pulling 2.9 from the stable PPA until it is further tested.
Here's my upgrade log:
$ sudo apt dist-upgrade
Reading package lists... Done
Building dependency tree
Reading state information... Done
Calculating upgrade... Done
The following packages will be upgraded:
  lxd lxd-client snap-confine snapd ubuntu-core-launcher
5 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
Need to get 13.6 MB of archives.
After this operation, 534 kB of additional disk space will be used.
Do you want to continue? [Y/n] y
Get:1 http://us.archive.ubuntu.com/ubuntu xenial-updates/main amd64 snapd amd64 2.22.3 [8,741 kB]
Get:2 http://ppa.launchpad.net/ubuntu-lxc/lxd-stable/ubuntu xenial/main amd64 lxd amd64 2.9.1-0ubuntu3~ubuntu16.04.1~ppa1 [2,818 kB]
Get:3 http://us.archive.ubuntu.com/ubuntu xenial-updates/main amd64 ubuntu-core-launcher amd64 2.22.3 [1,578 B]
Get:4 http://us.archive.ubuntu.com/ubuntu xenial-updates/main amd64 snap-confine amd64 2.22.3 [41.5 kB]
Get:5 http://ppa.launchpad.net/ubuntu-lxc/lxd-stable/ubuntu xenial/main amd64 lxd-client amd64 2.9.1-0ubuntu3~ubuntu16.04.1~ppa1 [1,950 kB]
Fetched 13.6 MB in 3s (3,392 kB/s)
(Reading database ... 114402 files and directories currently installed.)
Preparing to unpack .../snapd_2.22.3_amd64.deb ...
Warning: Stopping snapd.service, but it can still be activated by:
  snapd.socket
Unpacking snapd (2.22.3) over (2.22.2) ...
Preparing to unpack .../ubuntu-core-launcher_2.22.3_amd64.deb ...
Unpacking ubuntu-core-launcher (2.22.3) over (2.22.2) ...
Preparing to unpack .../snap-confine_2.22.3_amd64.deb ...
Unpacking snap-confine (2.22.3) over (2.22.2) ...
Preparing to unpack .../lxd_2.9.1-0ubuntu3~ubuntu16.04.1~ppa1_amd64.deb ...
Warning: Stopping lxd.service, but it can still be activated by:
  lxd.socket
Unpacking lxd (2.9.1-0ubuntu3~ubuntu16.04.1~ppa1) over (2.8-0ubuntu1~ubuntu16.04.1~ppa1) ...
Preparing to unpack .../lxd-client_2.9.1-0ubuntu3~ubuntu16.04.1~ppa1_amd64.deb ...
Unpacking lxd-client (2.9.1-0ubuntu3~ubuntu16.04.1~ppa1) over (2.8-0ubuntu1~ubuntu16.04.1~ppa1) ...
Processing triggers for man-db (2.7.5-1) ...
Processing triggers for ureadahead (0.100.0-19) ...
ureadahead will be reprofiled on next reboot
Processing triggers for systemd (229-4ubuntu16) ...
Setting up snap-confine (2.22.3) ...
Setting up snapd (2.22.3) ...
Setting up ubuntu-core-launcher (2.22.3) ...
Setting up lxd-client (2.9.1-0ubuntu3~ubuntu16.04.1~ppa1) ...
Setting up lxd (2.9.1-0ubuntu3~ubuntu16.04.1~ppa1) ...
Job for lxd-containers.service failed because the control process exited with error code. See "systemctl status lxd-containers.service" and "journalctl -xe" for details.
lxd-containers.service couldn't restart.

Looking at the details...
$ systemctl status lxd-containers.service
● lxd-containers.service - LXD - container startup/shutdown
   Loaded: loaded (/lib/systemd/system/lxd-containers.service; enabled; vendor preset: enabled)
   Active: failed (Result: exit-code) since Sun 2017-02-19 22:29:37 CST; 3min 8s ago
     Docs: man:lxd(1)
  Process: 24126 ExecStop=/usr/lib/lxd/shutdown (code=exited, status=0/SUCCESS)
  Process: 24132 ExecStart=/usr/bin/lxd activateifneeded (code=exited, status=1/FAILURE)
 Main PID: 24132 (code=exited, status=1/FAILURE)

Feb 19 22:29:37 hyper systemd[1]: Starting LXD - container startup/shutdown...
Feb 19 22:29:37 hyper lxd[24132]: error: No storage pool specified.
Feb 19 22:29:37 hyper systemd[1]: lxd-containers.service: Main process exited, code=exited, status=1/FAILURE
Feb 19 22:29:37 hyper systemd[1]: Failed to start LXD - container startup/shutdown.
Feb 19 22:29:37 hyper systemd[1]: lxd-containers.service: Unit entered failed state.
Feb 19 22:29:37 hyper systemd[1]: lxd-containers.service: Failed with result 'exit-code'.

$ systemctl status lxd-containers.service
● lxd-containers.service - LXD - container startup/shutdown
   Loaded: loaded (/lib/systemd/system/lxd-containers.service; enabled; vendor preset: enabled)
   Active: failed (Result: exit-code) since Sun 2017-02-19 22:29:37 CST; 3min 8s ago
     Docs: man:lxd(1)
  Process: 24126 ExecStop=/usr/lib/lxd/shutdown (code=exited, status=0/SUCCESS)
  Process: 24132 ExecStart=/usr/bin/lxd activateifneeded (code=exited, status=1/FAILURE)
 Main PID: 24132 (code=exited, status=1/FAILURE)

Feb 19 22:29:37 hyper systemd[1]: Starting LXD - container startup/shutdown...
Feb 19 22:29:37 hyper lxd[24132]: error: No storage pool specified.
Feb 19 22:29:37 hyper systemd[1]: lxd-containers.service: Main process exited, code=exited, status=1/FAILURE
Feb 19 22:29:37 hyper systemd[1]: Failed to start LXD - container startup/shutdown.
Feb 19 22:29:37 hyper systemd[1]: lxd-containers.service: Unit entered failed state.
Feb 19 22:29:37 hyper systemd[1]: lxd-containers.service: Failed with result 'exit-code'.

The following command was just blocked w/o any return value:
$ lxc storage list
^C

lxd-containers was in a failed status:
$ systemctl status lxd-containers
● lxd-containers.service - LXD - container startup/shutdown
   Loaded: loaded (/lib/systemd/system/lxd-containers.service; enabled; vendor preset: enabled)
   Active: failed (Result: exit-code) since Sun 2017-02-19 22:29:37 CST; 7min ago
     Docs: man:lxd(1)
  Process: 24126 ExecStop=/usr/lib/lxd/shutdown (code=exited, status=0/SUCCESS)
  Process: 24132 ExecStart=/usr/bin/lxd activateifneeded (code=exited, status=1/FAILURE)
 Main PID: 24132 (code=exited, status=1/FAILURE)

Feb 19 22:29:37 hyper systemd[1]: Starting LXD - container startup/shutdown...
Feb 19 22:29:37 hyper lxd[24132]: error: No storage pool specified.
Feb 19 22:29:37 hyper systemd[1]: lxd-containers.service: Main process exited, code=exited, status=1/FAILURE
Feb 19 22:29:37 hyper systemd[1]: Failed to start LXD - container startup/shutdown.
Feb 19 22:29:37 hyper systemd[1]: lxd-containers.service: Unit entered failed state.
Feb 19 22:29:37 hyper systemd[1]: lxd-containers.service: Failed with result 'exit-code'.

I poked at the database and saw:
$ sqlite3 /var/lib/lxd/lxd.db 'SELECT name FROM storage_volumes'
bitnode

Odd note, bitnode is just a name of one of my containers, not sure that I was expecting to see that?
At this point I decided it was best to downgrade and worry about this another day, for those wondering, this is how it worked for me:
$ sudo apt install lxd=2.8-0ubuntu1~ubuntu16.04.1 lxd-client=2.8-0ubuntu1~ubuntu16.04.1

I also copied over the backup db and restarted everything after that, thankfully that was done during the upgrade process for us.

It's somewhat surprising that the downgrade worked, I'd have expected the upgrade to 2.9 to move enough of the containers to the new paths that LXD 2.8 wouldn't be able to make sense of them.
I'd strongly recommend you don't stop or restart any of your existing containers as chances are that will fail due to them having been relocated.

Also, LXD 2.8 and LXD 2.9 are full feature releases of LXD which come with newly added features. We only bump the major version (LXD 2.x vs 3.x) every couple of years when we do API breaking changes.
The LTS branch that only gets bugfixes and security updates is LXD 2.0.x, that one will not see any feature addition at all between releases.

@cerealcable Can you paste "journalctl --unit=lxd"? With a bit of luck, it'll contain the original upgrade failure.
The output of "lxc info" and "lxc config show" would also be useful

If it helps I am running on zfs, not sure if that matters.
# journalctl --unit=lxd
-- Logs begin at Fri 2017-02-17 16:31:04 CST, end at Sun 2017-02-19 23:17:01 CST. --
Feb 17 16:31:29 hyper systemd[1]: Starting LXD - main daemon...
Feb 17 16:31:29 hyper lxd[5010]: lvl=warn msg="CGroup memory swap accounting is disabled, swap limits will be ignored." t=2017-02-17T16:31:29-0600
Feb 17 16:31:39 hyper lxd[5010]: lvl=warn msg="Unable to refresh cache, using stale entry" server=https://cloud-images.ubuntu.com/releases t=2017-02-17T16:31:39-0600
Feb 17 16:31:56 hyper systemd[1]: Started LXD - main daemon.
Feb 19 22:29:31 hyper systemd[1]: Stopping LXD - main daemon...
Feb 19 22:29:31 hyper systemd[1]: Stopped LXD - main daemon.
Feb 19 22:33:55 hyper systemd[1]: Starting LXD - main daemon...
Feb 19 22:33:55 hyper lxd[24799]: lvl=warn msg="CGroup memory swap accounting is disabled, swap limits will be ignored." t=2017-02-19T22:33:55-0600
Feb 19 22:34:06 hyper lxd[24799]: error: Failed to unmount ZFS filesystem: umount: /var/lib/lxd/containers/bitnode.zfs: target is busy
Feb 19 22:34:06 hyper lxd[24799]:         (In some cases useful info about processes that
Feb 19 22:34:06 hyper lxd[24799]:          use the device is found by lsof(8) or fuser(1).)
Feb 19 22:34:06 hyper lxd[24799]: cannot unmount '/var/lib/lxd/containers/bitnode.zfs': umount failed
Feb 19 22:34:06 hyper systemd[1]: lxd.service: Main process exited, code=exited, status=1/FAILURE
Feb 19 22:43:27 hyper systemd[1]: Stopped LXD - main daemon.
Feb 19 22:43:27 hyper systemd[1]: lxd.service: Unit entered failed state.
Feb 19 22:43:27 hyper systemd[1]: lxd.service: Failed with result 'exit-code'.
Feb 19 22:43:27 hyper systemd[1]: Starting LXD - main daemon...
Feb 19 22:43:27 hyper lxd[27078]: lvl=warn msg="CGroup memory swap accounting is disabled, swap limits will be ignored." t=2017-02-19T22:43:27-0600
Feb 19 22:43:27 hyper lxd[27078]: error: UNIQUE constraint failed: storage_pools.name
Feb 19 22:43:27 hyper systemd[1]: lxd.service: Main process exited, code=exited, status=1/FAILURE
Feb 19 22:45:46 hyper systemd[1]: Stopped LXD - main daemon.
Feb 19 22:45:46 hyper systemd[1]: lxd.service: Unit entered failed state.
Feb 19 22:45:46 hyper systemd[1]: lxd.service: Failed with result 'exit-code'.
Feb 19 22:45:46 hyper systemd[1]: Starting LXD - main daemon...
Feb 19 22:45:46 hyper lxd[27430]: lvl=warn msg="CGroup memory swap accounting is disabled, swap limits will be ignored." t=2017-02-19T22:45:46-0600
Feb 19 22:45:46 hyper lxd[27430]: error: UNIQUE constraint failed: storage_pools.name
Feb 19 22:45:46 hyper systemd[1]: lxd.service: Main process exited, code=exited, status=1/FAILURE
Feb 19 22:45:56 hyper systemd[1]: Stopped LXD - main daemon.
Feb 19 22:45:56 hyper systemd[1]: lxd.service: Unit entered failed state.
Feb 19 22:45:56 hyper systemd[1]: lxd.service: Failed with result 'exit-code'.
Feb 19 22:45:56 hyper systemd[1]: Starting LXD - main daemon...
Feb 19 22:45:56 hyper lxd[27482]: lvl=warn msg="CGroup memory swap accounting is disabled, swap limits will be ignored." t=2017-02-19T22:45:56-0600
Feb 19 22:45:56 hyper lxd[27482]: error: UNIQUE constraint failed: storage_pools.name
Feb 19 22:45:56 hyper systemd[1]: lxd.service: Main process exited, code=exited, status=1/FAILURE
Feb 19 22:45:59 hyper systemd[1]: Stopped LXD - main daemon.
Feb 19 22:45:59 hyper systemd[1]: lxd.service: Unit entered failed state.
Feb 19 22:45:59 hyper systemd[1]: lxd.service: Failed with result 'exit-code'.
Feb 19 22:46:12 hyper systemd[1]: Starting LXD - main daemon...
Feb 19 22:46:12 hyper lxd[27548]: lvl=warn msg="CGroup memory swap accounting is disabled, swap limits will be ignored." t=2017-02-19T22:46:12-0600
Feb 19 22:46:12 hyper lxd[27548]: error: UNIQUE constraint failed: storage_pools.name
Feb 19 22:46:12 hyper systemd[1]: lxd.service: Main process exited, code=exited, status=1/FAILURE
Feb 19 22:52:05 hyper systemd[1]: Stopped LXD - main daemon.
Feb 19 22:52:05 hyper systemd[1]: lxd.service: Unit entered failed state.
Feb 19 22:52:05 hyper systemd[1]: lxd.service: Failed with result 'exit-code'.
Feb 19 22:52:05 hyper systemd[1]: Starting LXD - main daemon...
Feb 19 22:52:05 hyper lxd[28767]: lvl=warn msg="CGroup memory swap accounting is disabled, swap limits will be ignored." t=2017-02-19T22:52:05-0600
Feb 19 22:52:05 hyper lxd[28767]: error: UNIQUE constraint failed: storage_pools.name
Feb 19 22:52:05 hyper systemd[1]: lxd.service: Main process exited, code=exited, status=1/FAILURE
Feb 19 23:02:05 hyper lxd[28768]: error: LXD still not running after 600s timeout.
Feb 19 23:02:05 hyper systemd[1]: lxd.service: Control process exited, code=exited status=1
Feb 19 23:02:05 hyper systemd[1]: Failed to start LXD - main daemon.
Feb 19 23:02:05 hyper systemd[1]: lxd.service: Unit entered failed state.
Feb 19 23:02:05 hyper systemd[1]: lxd.service: Failed with result 'exit-code'.
Feb 19 23:02:05 hyper systemd[1]: lxd.service: Service hold-off time over, scheduling restart.
Feb 19 23:02:05 hyper systemd[1]: Stopped LXD - main daemon.
Feb 19 23:02:05 hyper systemd[1]: Starting LXD - main daemon...
Feb 19 23:02:05 hyper lxd[30727]: lvl=warn msg="CGroup memory swap accounting is disabled, swap limits will be ignored." t=2017-02-19T23:02:05-0600
Feb 19 23:02:06 hyper systemd[1]: Started LXD - main daemon.
Feb 19 23:02:06 hyper systemd[1]: Stopping LXD - main daemon...
Feb 19 23:02:06 hyper systemd[1]: Stopped LXD - main daemon.
Feb 19 23:02:06 hyper systemd[1]: Starting LXD - main daemon...
Feb 19 23:02:06 hyper lxd[30798]: lvl=warn msg="CGroup memory swap accounting is disabled, swap limits will be ignored." t=2017-02-19T23:02:06-0600
Feb 19 23:02:06 hyper systemd[1]: Started LXD - main daemon.
Feb 19 23:04:20 hyper systemd[1]: Stopping LXD - main daemon...
Feb 19 23:04:20 hyper systemd[1]: Stopped LXD - main daemon.
Feb 19 23:04:25 hyper systemd[1]: Stopped LXD - main daemon.
Feb 19 23:06:05 hyper systemd[1]: Starting LXD - main daemon...
Feb 19 23:06:05 hyper lxd[31617]: lvl=warn msg="CGroup memory swap accounting is disabled, swap limits will be ignored." t=2017-02-19T23:06:05-0600
Feb 19 23:06:06 hyper systemd[1]: Started LXD - main daemon.

# lxc info
config:
  storage.zfs_pool_name: tank/lxd
apiextensions:
- 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
apistatus: stable
apiversion: "1.0"
auth: trusted
public: false
environment:
  addresses: []
  architectures:
  - x86_64
  - i686
  certificate: |
    -----BEGIN CERTIFICATE-----
    MIIFSTCCAzGgAwIBAgIQEQN0VPYedVPWE6T6MVILjzANBgkqhkiG9w0BAQsFADAz
    MRwwGgYDVQQKExNsaW51eGNvbnRhaW5lcnMub3JnMRMwEQYDVQQDDApyb290QGh5
    cGVyMB4XDTE3MDEyOTAyNDAwNVoXDTI3MDEyNzAyNDAwNVowMzEcMBoGA1UEChMT
    bGludXhjb250YWluZXJzLm9yZzETMBEGA1UEAwwKcm9vdEBoeXBlcjCCAiIwDQYJ
    KoZIhvcNAQEBBQADggIPADCCAgoCggIBAOuQwFoYXcahiocVO5YOHvCd8LvJq9bD
    V2UjBr97MQoicpjKrwvlM4CAtFJKquZcDevtXIqDWDBWHkYCynf8qodeUCN+BFs6
    pA8yqBkhbE1nnYB41VNnEaS90+nMRF1iy4Iv3xu2H1tCjBdEsebgDgPI0EvCXhHl
    VwhLWZVLklx0HVfB/AXyQXoT9wWOdBSMozD6cpOLHuNrQ/gkbXwuKtjU+pjf+rp8
    ngdJ1BErN3waVjwCn/+ESaWgz+z/gVnnryLQTgfVRH314AoBqnK2A6j6FrdBwsAt
    /pY32nC3Fw07mNz6s4p3QSGnYrM2+f935+4vPqrV8Pd2775dXUzCcSRA/Vz4z8Nh
    kOR+b9thSvtmc1uNfYpqhq/RWd5JCcAIL76q4g4/JSlY8m0Vg4RZvbex55otduvl
    DZ24eT8IcaDfJTg7Bzb1bUQ75c9YarayQa0yepO4hdO7LZYahwVFYVYgfWDEd6dP
    dOL1epRSGQpLTd51bOlVaygr7SUGA0YKlE17sk+c22C7O0R9iNrd9kiT8mlb49aD
    ypPag+sqCmWdU2xo2SUk3suty7LJOOZ1AnpRJnVIlEMkiD6JQTq+PdVgu6Eg3g5X
    KD4/hgUSM1zrKfpr+76w5B+lylKHte14f/hBgB8wD95/+cwBX9t++236LFA8/nsL
    1lYCseRb5GybAgMBAAGjWTBXMA4GA1UdDwEB/wQEAwIFoDATBgNVHSUEDDAKBggr
    BgEFBQcDATAMBgNVHRMBAf8EAjAAMCIGA1UdEQQbMBmCBWh5cGVyhwQKHwEFhwQK
    AAMBhwTAqHoBMA0GCSqGSIb3DQEBCwUAA4ICAQCdpZzPS+G01p2//P/Ha/jrcHoG
    1t8ncbYeBQudqRzXJCGX4/A1xoIpnFxKBSo5S+te1iW2ahYLSObusOXOEsoUAN+3
    wAhVlOjRDG+G8AoXwqkbrr4xMJOTlofFAPDzUJ2y5l08kQgA+5Y69STLkT7FuIJj
    ttiMWuK1yQBSW7f9YyQ2xKm6ALGjxtw2w1HyZdyApSjD7LoyDb12mYTPuakcweLP
    RCngjGQSzS1Tz1VUp9IoWk8KXzVjb9DFWOGkDeV6XbJFjOSziMlK0fVthWNXez5e
    1w/F/xFc1GEFLvn4YXk5LMM8qd1IDZbgkhxSZrEqu4ywzmNSmX3dgDBEuY9wEGoI
    6dgA40J+4NCwmCp6lAf3K9beUq1SquwbO+jxpG8rEwPCzAgVmAubq3xizi/GZHlq
    qLSlRUzi2/MbK3DEzxvN3O4o9GzDsBbIhN7HJw+FuGKjIujwPlPmYBavG3qEWhgO
    1SlUKJKFuJ2XO+jSXGek8lrPsU75zGMV66zebq37AxdZnccgzhH4/bEkFySkbioB
    DMUiFkYzWnC16cOaKV6iyCVLkan+FiMQsj1xMNYxhiKz6mefHGQ96kJ7ArTHoaCb
    I/W/tpLMEIzirmx5McqJ7o1pl5dX6MFdrLDQIedwRMONc+DTS0+4vQ5VWuBOVHB3
    A733RtnwVv2OWHYb2w==
    -----END CERTIFICATE-----
  certificatefingerprint: 502d01293ba62609d8585b9e2e5e372034f497002475f1cce61ab32ef764706c
  driver: lxc
  driverversion: 2.0.7
  kernel: Linux
  kernelarchitecture: x86_64
  kernelversion: 4.4.0-62-generic
  server: lxd
  serverpid: 31617
  serverversion: "2.8"
  storage: zfs
  storageversion: "5"

# lxc config show
config:
  storage.zfs_pool_name: tank/lxd

Also of interesting note, I was able to stop/start a container that I didn't care too much about, everything worked. Noting the upgrade log where the name "bitnode" is referenced, that is the first container alphabetically so maybe it only got to doing anything with that?
I also made note that I restored the backup database after downgrading if that means much of anything and I would assume zfs wouldn't be changing the data paths?

@cerealcable yeah, if your problem is the same as what I hit on one of my machines and what some other hit, that container failed to get unmounted and crashed the upgrade code. So that container may be at risk if you stop/start it, same goes for the next one alphabetically. The others shouldn't have been touched at all and so should be fine.
Yeah, the DB downgrade could only really work if done after reverting the code, otherwise LXD would have re-upgraded the database during the package downgrade. What's not covered by the DB downgrade is the disk changes that the upgrade would have done. Things like changing the symlinks in /var/lib/lxd/containers, removing the .zfs entries in /var/lib/lxd/containers and /var/lib/lxd/images, creating a whole bunch of stuff under /var/lib/lxd/storage-pools/, ...

Right so I did replace the database after downgrading so who knows. This is just my home lab at least so this is just something to figure out and get past. Not sure what the next steps are, wouldn't be opposed to hearing any thoughts.

@cerealcable we're working on a LXD 2.9.2 release which will fix all the major issues we're aware of, including being able to recover from a partial upgrade as best we can.
I've helped a few users who ran into the same failure you did recover from it and get a working LXD 2.9.1, but since you downgrade to LXD 2.8 and have things working, I'd recommend staying on LXD 2.8 until we have LXD 2.9.2 out.

We'll also be waiting until we're done dealing with any report of broken upgrades before we push LXD 2.9.x to xenial-backports and yakkety-backports where most of the users for those feature releases are.
That should limit the user base to those who use the LXD snap, Ubuntu development release or LXD PPA. Which is a tiny fraction of our user base and who's typically more tech savvy which helps us with tracking down those issues.

Not sure if this is going to be important but at one point while messing around with lxd I did delete the default profile because I felt like it, not sure if that's of concern with the upgrade or not.
Should I not use the stable ppa as a stable release channel? I don't really have a reason to not be using a bit more bleeding edge for my home lab but if the ppa stable isn't the right place for more serious usage than my home lab I would like to know and probably would be beneficial for some sort of information somewhere? I know that's not very helpful at all.

Glad to see the problem has already been identified. Updated my custom profile, and we're a go again.

I got the same after the upgrade to 2.9- i was able to resolve the issue by updating containers_profiles with records for the container's snapshots as well as the snapshot itself. The upgrade had updated just the container's "containers_profiles" aka. echo "insert into containers_profiles(container_id,profile_id,apply_order) values(XX,Y,Z);" | sqlite3 /var/lib/lxd/lxd.db

@cerealcable The LXD feature releases get new releases at least once a month. We do support those releases so it's not like a development build or anything. However for people who need absolute stability and several years of support with nothing being added or change, we have the LTS branch (2.0.x) for that.
So typically developers and home labs will play with the latest features and so the feature releases work fine for them. Production environments do tend to stick to the LTS branch as they don't care so much about new features and just want all the bugfixes, stability and support.

This issue should now have been resolved in git and in LXD 2.9.2, closing.
If anyone who has installed LXD 2.9.2 runs into something like this, please file another issue.

Hey Stéphane,
Not sure if you have this all worked out in 2.9.2, but my upgrade from 2.8 failed as well. Two different boxes with one thing in common, they both had non-standard zfs pool names.  While I've re-inited lxd, and can now launch machines I still can't get the zpool name (kept at default) from lxc info/config, which breaks other things I do to ensure the zpool is large enough.  ;),
~$ journalctl --unit=lxd
-- Logs begin at Die 2017-02-21 20:15:32 PST, end at Mit 2017-02-22 09:47:10 PST. --
Feb 21 20:15:40 OrangeBox20 systemd[1]: Starting LXD - main daemon...
Feb 21 20:15:40 OrangeBox20 lxd[4103]: lvl=warn msg="CGroup memory swap accounting is disabled, swap limits will be ignored." t=2017-02-21T20:15:40-0800
Feb 21 20:15:40 OrangeBox20 lxd[4103]: lvl=eror msg="Error checking storage pool \"lxd_zfs\": Unable to import the ZFS pool: cannot import '/var/lib/lxd/disks/lxd_zfs.img

`~$ lxc info
config:
  core.https_address: '[::]:8443'
  core.trust_password: true
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
api_status: stable
api_version: "1.0"
auth: trusted
public: false
environment:
  addresses:
  - <IP_ADDRESS>:8443
  - <IP_ADDRESS>:8443
  - <IP_ADDRESS>:8443
  - <IP_ADDRESS>:8443
  - <IP_ADDRESS>:8443
  architectures:
  - x86_64
  - i686
  certificate: |
    -----BEGIN CERTIFICATE-----
    MIIFbjCCA1agAwIBAgIRAPeIVbWredhC2wX8fKqtsyMwDQYJKoZIhvcNAQELBQAw
    OTEcMBoGA1UEChMTbGludXhjb250YWluZXJzLm9yZzEZMBcGA1UEAwwQcm9vdEBP
    cmFuZ2VCb3gyMDAeFw0xNzAyMjIwNzQyNTBaFw0yNzAyMjAwNzQyNTBaMDkxHDAa
    BgNVBAoTE2xpbnV4Y29udGFpbmVycy5vcmcxGTAXBgNVBAMMEHJvb3RAT3Jhbmdl
    Qm94MjAwggIiMA0GCSqGSIb3DQEBAQUAA4ICDwAwggIKAoICAQDDgz2XN4j05f2e
    EQVoJDLfGkCeUGoV/DT7fCiM24v4/07EePtTnNkJeuN9sPDwc2jp862ImNRIRoJi
    IPIiyfu/vnIxcb/3Lt7U30wFirz9JOaUYaqhqKGPaJZd5Z375VeLY/GoeWNBxJEv
    z14EtyYwPdgS4Q51ihGhzkRd4kba8cibeCQ3okYqd9y46wa7ldcI2foRtrHpr4qe
    AcP6ZFh5lWeKQzI3KxuAD5HYWHnVHUuwSgsMRZhluXZFgkmQiFn5JO8RfFZKmrZW
    zq5+P5Ly5aV8CNGel/KdPL+3RI5jqqyndfBMCcCubOwnl/54N+QHPrBg2Y8ehrAI
    3sPPsaNPJRE6dR2pLQNPECDmpW+LkD6LFJHaOIQjI4jVnQpNGsxLwqLMk+JjgkKI
    a6irZMaOrpOhcVCEzT0Xc3TW0rh7PYIQaNAuA0ST3zdpbuepx2AwQoxaKAXibOOO
    RTle2/Czmr3blr6rAeNPYwitTKWuhrMeO37Q+SfNC8W/+6EQ2VS8C7RYh07hH0zL
    eOGbvKE10z2ATCxoeJqccuf4GIWijWk77G+zHuLX1G/YPq8MT+Fnm3Fiq/zi09hw
    YdtjFUy26cTiqFXNwbJEd+nz3GaB+e5oPIsj9Qu7+6HM+1jIu1DCWnUzrv0Scc3P
    d/VLxXqqatI9ONoZODA4ZSPe06cqZwIDAQABo3EwbzAOBgNVHQ8BAf8EBAMCBaAw
    EwYDVR0lBAwwCgYIKwYBBQUHAwEwDAYDVR0TAQH/BAIwADA6BgNVHREEMzAxggtP
    cmFuZ2VCb3gyMIcErBsWAYcErBsUAYcEwKhkAYcECmMAAYcECmMAAYcEClKsATAN
    BgkqhkiG9w0BAQsFAAOCAgEActG1+tf6tbTfWjt+k8K9QK1g4WAmV9BDkaAJSzLD
    SMK2PI70s1iTzbGgU6tv4r9U4WjO95whATKcZRg8eAW5pVDd4zKNp5JcfHNXs+91
    vRR9BmGfGl/R5QjgHkQsVsvQnkD+Jy0LVDmjK4SCAb95LPl/1V+JQxjcxxzfqIoG
    agF3Ya9OrXJZqx8kBLUTO5xFOeAT03U+xajN9nKmIXNCwHkaipmKf9Yt1U8RgKTw
    WLU5FDyDdfsuo6L57Gn5AHFzh7jOarDAlT7OpwwLlvFrahBXiba/itULUDlIPZwK
    /I3Wn4W7dyG4ALaXILmuhuoEmyiVj7JdsX+W+bUVSkgQBplBMlSz4fVhwREejxsE
    AO6R6zZBFdjwdpKCnjBfkQLYTM1jfMmvNGC/1czxNy4iwnhyX7Bn2cEEDX0rqk6D
    YuWHX3SgfQJtfu8uFbggx9FIphh/GN/ovB/B7k2HrxqQzvqvXxGOK2ZRWvKaX72/
    9ZrboUdMYhKj+hDEkonWZ79a8UpmNj67hpvMVCYkF2Fw9PA3hbVRoL82jnH89Ufe
    6NOZuqJLkbJCTGkLXYseKI3+GH9eg7EG7jv47ch78oH6/cKxn9QPqCxv8WkEo5XU
    kZo1fI1Ds/93qySV/zo5vujkCeQRf9xApSl2l+2KZOv+yXZTQZscYKCfrr937UI6
    DUg=
    -----END CERTIFICATE-----
  certificate_fingerprint: f83ae3e1b58b0216c189c2a86921324141b80ed4445a524f009046a23f59c398
  driver: lxc
  driver_version: 2.0.7
  kernel: Linux
  kernel_architecture: x86_64
  kernel_version: 4.4.0-64-generic
  server: lxd
  server_pid: 30803
  server_version: 2.9.2
  storage: zfs
  storage_version: <IP_ADDRESS>-0ubuntu15

~$ lxc config show
config:
core.https_address: '[::]:8443'
core.trust_password: true
:~$ sudo zpool status
  pool: default
 state: ONLINE
  scan: none requested
config:

	NAME                              STATE     READ WRITE CKSUM
	default                           ONLINE       0     0     0
	  /var/lib/lxd/disks/default.img  ONLINE       0     0     0

errors: No known data errors

sudo zpool list
NAME      SIZE  ALLOC   FREE  EXPANDSZ   FRAG    CAP  DEDUP  HEALTH  ALTROOT
default  74.5G  10.1G  64.4G

What does "lxc storage list" look like?

Ooh.  Cool!
~$ lxc storage list
+---------+--------+--------------------------------+---------+
|  NAME   | DRIVER |             SOURCE             | USED BY |
+---------+--------+--------------------------------+---------+
| default | zfs    | /var/lib/lxd/disks/default.img | 58      |
+---------+--------+--------------------------------+---------+

Ok, so looks like you got yourself a zpool with a bunch of containers and images on it. Is something actually still broken in your setup?


VS Code characters and icons fading out on Windows 11

Issue Type: Bug
I looked up this issue, and it seems that an update from 2018 had fixed that issue on Windows 10, but I'm having this issue right now on VS Code. Even this bug report window started to fade out as I'm typing this.
The fading does stop when I hover over the files and/or tabs.
Only VSC is doing this, so I don't think it's related to the GPU.
VS Code version: Code 1.67.2 (c3511e6c69bb39013c4a4b7b9566ec1ca73fc4d5, 2022-05-17T18:15:52.058Z)
OS version: Windows_NT x64 10.0.22000
Restricted Mode: No

System Info

Item
Value

CPUs
Intel(R) Core(TM) i3-9100F CPU @ 3.60GHz (4 x 3600)

GPU Status
2d_canvas: enabledcanvas_oop_rasterization: disabled_offdirect_rendering_display_compositor: disabled_off_okgpu_compositing: enabledmultiple_raster_threads: enabled_onoop_rasterization: enabledopengl: enabled_onrasterization: enabledraw_draw: disabled_off_okskia_renderer: enabled_onvideo_decode: enabledvideo_encode: enabledvulkan: disabled_offwebgl: enabledwebgl2: enabled

Load (avg)
undefined

Memory (System)
7.95GB (2.09GB free)

Process Argv
C:\Users\Pichau\OneDrive\Área de Trabalho\Growdev\Aulas\semana 27.1 aula 46 - 16-05-22 - Qualidade de Código --crash-reporter-id bf180521-e84c-4728-a1f1-58558d32387e

Screen Reader
no

VM
0%

Extensions (32)

Extension
Author (truncated)
Version

better-comments
aar
3.0.0

Bookmarks
ale
13.3.0

vscode-sqlite
ale
0.14.0

bracket-pair-colorizer
Coe
1.0.62

vscode-eslint
dba
2.2.2

gitlens
eam
12.0.7

vscode-html-css
ecm
1.12.2

EditorConfig
Edi
0.16.4

vscode-javac
geo
0.2.39

beautify
Hoo
1.5.0

open-in-browser
igo
1.0.2

fontawesome-autocomplete
Jan
1.3.1

vscode-nuget-package-manager
jmr
1.1.6

dotenv
mik
1.0.1

csharp
ms-
1.25.0

vscode-dotnet-runtime
ms-
1.5.0

python
ms-
2022.6.2

vscode-pylance
ms-
2022.5.2

jupyter
ms-
2022.4.1021342353

jupyter-keymap
ms-
1.0.0

jupyter-renderers
ms-
1.0.6

cpptools
ms-
1.9.8

vscode-typescript-next
ms-
4.8.20220524

vsliveshare
ms-
1.0.5595

vsliveshare-audio
ms-
0.1.91

vsliveshare-pack
ms-
0.4.0

material-icon-theme
PKi
4.17.0

LiveServer
rit
5.7.5

tabnine-vscode
Tab
3.5.49

vscode-inline-bookmarks
tin
0.0.26

vscode-icons
vsc
11.12.0

JavaScriptSnippets
xab
1.8.0

(1 theme extensions excluded)

A/B Experiments
vsliv368:30146709
vsreu685:30147344
python383cf:30185419
vspor879:30202332
vspor708:30202333
vspor363:30204092
pythonvspyl392:30443607
pythontb:30283811
pythonvspyt551cf:30345471
pythonptprofiler:30281270
vshan820:30294714
vstes263:30335439
pythondataviewer:30285071
vscod805:30301674
pythonvspyt200:30340761
binariesv615:30325510
bridge0708:30335490
bridge0723:30353136
vsaa593cf:30376535
vsc1dst:30438360
pythonvs932:30410667
wslgetstarted:30449410
pythonvsnew555:30457759
vscscmwlcmt:30465135
cppdebug:30492333
vsclangdc:30486549

First screenshot:

In this one, even the bug report window was fading:

The fading does stop when I hover over the files and/or tabs.

Does the issue happen with latest insiders https://code.visualstudio.com/insiders ? If so, can you try disabling hardware acceleration https://code.visualstudio.com/updates/v1_40#_disable-gpu-acceleration

This issue has been closed automatically because it needs more information and has not had recent activity. See also our issue reporting guidelines.
Happy Coding!

Sorry for the late reply. I guess this got fixed in later updates because it did not happen again.


Pick a newer minimal image and configure it

We'll need a new latest image pulled and configured to suit our needs

Hoping to use Raspbian Buster Lite this year - install everything via CLI (and interact via CLI)


CI - don't allow absolute links to docs.docker.com

Describe the proposed changes
Added a test to prevent absolute links to docs.docker.com.
Also made a few absolute links relative for this test to pass.

Deploy preview ready!
Built with commit e68bbc60163c97964b249bfbb4318cbb39d68fc6
https://deploy-preview-823--docker-docs.netlify.com

@johndmulhausen I'll now add more tests in the same scope to check for dead links or infinite redirection loops... But this one can be merged already.

Will we have the ability to disable this for specific layout features? I'm specifically thinking of links in banners which might be applied at build time, and which since they could be applied anywhere, would need a static url.

@sanscontext sure, it's super flexible. so far it only checks published markdown files. we can add exceptions if needed.

SGTM! Thanks.

@johndmulhausen can you merge it please? I'll submit new tests today, but I would prefer that one to be merged first. Thanks!

I rebased and had to fix a new absolute link in engine/installation/binaries.md...

@aduermael I agree with the goal of this test, however it appears you're parsing links with RegEx here. I don't want to set a precedent of relying on clever/arcane RegEx Markdown processing instead of freely available Go libraries such as Blackfriday.
With Blackfriday you can use Bluemonday to sanitize input:
import (
    "github.com/microcosm-cc/bluemonday"
    "github.com/russross/blackfriday"
)

// ...
unsafe := blackfriday.MarkdownCommon(input)
html := bluemonday.UGCPolicy().SanitizeBytes(unsafe)

Then, if that completes (obviously the CI check should fail if it doesn't), run html through the html Go library and do the link checking there with a data structure that represents the document object model.
Parsing raw Markdown with RegEx is a recipe for unintended consequences.

@johndmulhausen It's way easier to parse markdown than html... I know blackfriday and we may have to use it for other tests, but I don't understand why in this case I would transform our markdown into html before parsing it. Sorry I just don't get it.

Parsing raw Markdown with RegEx is a recipe for unintended consequences.

Please give me a concrete example.

I understand it's easier to implement it this way, but I'm afraid it is also a low-quality approach that is fragile. Just to cite one concrete example: What if we want to document how our Markdown works for contributors? We've talked about such a project.
The probem is, your code has no concept of what a link is, it just hopes that matching []() will always do what you want. When you started validating YAML with CI tests you knew it was important to include a YAML parser so that you would have strongly-typed data and ready-made functions that had a notion of a YAML structure. Now you want to venture into processing page content but with no concept of a document? I don't think we should go there.


Datasets: Rename read() method to load()

This is a much less confusing wording and won't clash with future use cases including reading data, reading measures, etc.

Codecov Report
Base: 65.50% // Head: 65.60% // Increases project coverage by +0.10% :tada:

Coverage data is based on head (da0fa21) compared to base (2b69731).
Patch coverage: 53.65% of modified lines in pull request are covered.

:exclamation: Current head da0fa21 differs from pull request most recent head 615d211. Consider uploading reports for the commit 615d211 to get more accurate results

Additional details and impacted files
@@            Coverage Diff             @@
##             main     #155      +/-   ##
==========================================
+ Coverage   65.50%   65.60%   +0.10%
==========================================
  Files          20       21       +1
  Lines         658      660       +2
  Branches      155      155
==========================================
+ Hits          431      433       +2
  Misses        215      215
  Partials       12       12

Impacted Files
Coverage Δ

src/pymovements/datasets/public_dataset.py
46.87% <46.87%> (ø)

src/pymovements/datasets/dataset.py
30.85% <60.00%> (ø)

src/pymovements/datasets/__init__.py
100.00% <100.00%> (ø)

src/pymovements/datasets/gazebase.py
92.30% <100.00%> (ø)

src/pymovements/datasets/judo1000.py
92.30% <100.00%> (ø)

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

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


DeDuplicationAgent properly handles destruction of memory

Fixes #877

LGTM!  Thanks :)

Is this mergable?

Yes, sorry forgot about it.


Identically named rules get overwritten.

If a user accidentally gives a custom rule a name that already exists then it gets overwritten and never runs. A note in the docs or a warning message would be helpful.

Thank you, @rkrauskopf. That definitely makes sense for me.

@knidarkness I would print an error. I think such situation is not a warning

@RomanHotsiy, I agree that we could throw an error for that. Also, README should be updated.

I'm pretty sure this is solved in #146 (but I'm not 100% sure). Custom rules are namespaced.

This only applies to custom plugins since we have added the namespacing. I think we can adjust the docs there. Also, we should consider can two plugins have the same name as long as they have different rules? And we throw an error on the fully namespaced preprocessor/rule/decorator name collision?


chore: go runtime renaming

Renaming some args in go runtime as suggested in https://github.com/aws/jsii/pull/2257.

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

AWS CodeBuild CI Report

CodeBuild project: AutoBuildProject6AEA49D1-5lHf64IXfvmr
Commit ID: 06f210912c2cf5609324aae58aaecdc54c9d7488
Result: SUCCEEDED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

@mergifyio update

AWS CodeBuild CI Report

CodeBuild project: AutoBuildProject6AEA49D1-5lHf64IXfvmr
Commit ID: a4d8a54800ddfde8b29a916eabe06d100fa78781
Result: SUCCEEDED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

@Mergifyio update

AWS CodeBuild CI Report

CodeBuild project: AutoBuildProject6AEA49D1-5lHf64IXfvmr
Commit ID: b1461cfe5e3dafff6bed4e584871e93444d8cccc
Result: SUCCEEDED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

@Mergifyio update

AWS CodeBuild CI Report

CodeBuild project: AutoBuildProject6AEA49D1-5lHf64IXfvmr
Commit ID: b2cd2148b4d67f8695ba4f3cbe70b32f18b27d97
Result: SUCCEEDED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository


Functions not used

Can I delete the following functions?

cs.scrollStop
cs.scrollStart

You can delete it.


Does not work on latest Rakudo (the code is relying on buggy backtracking)

Currently the tests are failing (on all rakudos after 963a0f0657a).
The issue can be “fixed” by adding :!r here:
https://github.com/jsimonet/dns-zone/blob/master/lib/DNS/Zone/Grammars/Modern.pm6#L252-L260
That being said, I'm not sure why backtracking is needed there. There may be a better way to do it.
See RT #130117 for more info.

Fixed in 186be9599200cc53e864a57344ed026a2893f22a.
Thank you for submitting this PR.
You are saying that I should use || instead of | in the IPV6 regex to match the first one?

No, generally it's not a || vs | question. Maybe see this and this.

I think the backtracking is needed because the first part of an IPV4 can match a IPV6 token (<h16>). So I have to test every forms of <h16> * <ipv4> before trying to test <h16> only one.
Anyway, thank you for the fix 👍


Posibility to define all tools via env

Some tools can be defined with :port or +extra flag. These chars can't
be part of env variable name. Therefore some "magic" has to happen to
allow these options be passed via env. Simple substitutions /+/plus/
and /:/port/ are made when searching for value.

Also shouldn't this feature be documented anywhere?

Just to be clear: these characters can also be part of the key in the testsuite settings, so simple quotes in environment variables won't be enough, right?

I am not sure whether I understand the question.

Just to be clear: these characters can also be part of the key in the testsuite settings, so simple quotes in environment variables won't be enough, right?

I am not sure whether I understand the question.

I wasn't sure if those variables with special characters can also be keys and not only values in the settings (in values these special characters usually can be achieved by quotes around the value e.g. httpbin: "httpbin+svc:8080" (same in the env variables)), as there are no any examples of this feature in the settings template.
But from the implementation, I see that these special characters can also be used as keys names e.g.
httpbin+svc:8080: something.


Segmentation step

Currently we are using part of nsbatwm to do the segmentation step, but the segmentations differ to those from epitools-matlab. We could consider

keep using nsbatwm and rely on manual corrections to the segmentation
port the original epitools-matlab segmentation module to python
use cellpose
use Usiigaci
use startdist
use zelda

which (if any) of these is most appropriate?

we've agreed to stick with nsbatwm and make use of manual corrections to segmentations for now


Dev environment does not work if repo is cloned in a different directory

I guess is the implementation of fetch_macaroon and fetch_pubkey in .envrc
maybe just change the filter from:
local container_id=$(docker ps -q -f status=running -f name="galoy_$1_")

to
# tested on linux but not sure about mac
local container_id=$(docker ps -q -f status=running -f name="${PWD##*/}_$1_")

do you want to make a PR? I can test it out on mac.

do you want to make a PR? I can test it out on mac.

if you can test it would be great... basically is to run echo ${PWD##*/} in the console and verify that returns the current directory name

seems to work:
galoy nicolas$ echo ${PWD##*/}`
galoy


Need Help

Please follow the guide below

Issues submitted without this template format will be ignored.
You will be asked some questions and requested to provide some information, please read them carefully and answer completely.
Put an x into all the boxes [ ] relevant to your issue (like so [x]).
Use the Preview tab to see how your issue will actually look like.

Before submitting an issue, make sure you have:

[x] Updated to the latest version
[x] Read the README and docs
[x] Searched the bugtracker for similar issues including closed ones

Purpose of your issue?

[x] Bug report (encountered problems/errors)
[ ] Feature request (request for a new functionality)
[x] Question
[ ] Other

The following sections requests more details for particular types of issues, you can remove any section (the contents between the triple ---) not applicable to your issue.

For a bug report, you must include the Python version used, code that will reproduce the error, and the error log/traceback.
Paste the output of python -V here:
Code:
# Example code that will produce the error reported
from instabot import Bot

bot = Bot()
bot.login(username="user", password="pass")
followers = bot.get_user_followers(bot.user_id)

Error/Debug Log:
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
ZeroDivisionError: integer division or modulo by zero

Describe your issue
Like_user_following.py no working.Any idea??
2018-12-28 23:55:54,279 - INFO - Logged-in successfully as 'mr.albrech' using the cookie!
2018-12-28 23:55:54,280 - INFO - Like following of: nacho.
2018-12-28 23:55:54,488 - ERROR - Request returns 403 error!
2018-12-28 23:55:55,326 - ERROR - Request returns 404 error!
2018-12-28 23:55:55,326 - INFO - nacho not found / closed / has no following.
2018-12-28 23:55:55,467 - INFO - Bot stopped. Worked: 1:43:43.432013
2018-12-28 23:55:55,468 - INFO - Total requests: 122454

just remove your "cookie.txt" and run again


do not regenerate a signing key secret if we already have one

fixes https://github.com/kiali/kiali/issues/2921

my testing shows this working. and it fixes the problem where it triggers the reconciliation in an infinite loop if I turn on watchDependentResources in the operator.

To test this - install operator, install a basic Kiali CR (do not define signing_key, which you do not typical set anyway).
Look at the kiali-signing-key resource created in istio-system namespace. Look at the key value.
Now touch the Kiali CR (just change, say, deployment.verbose_mode - just change anything basic).
Now look at the secret again - make sure the signing key value does not change.


state diff system

by no means perfect, but a lot closer to what we want, so i'm going to push ahead


consider: Support for sessioned services

Problem to Solve
TBC
Possible Solution
TBC
Notes
No response

Can be implemented by apps themselves. Doesn't require any special support from the framework.


Mutation HoCs give equality-comparison-stable props

As part of upgrading to Vulcan 1.13/Apollo2, I'm going throw places where LW has diverged and upstreaming changes.
React decides which parts of the tree need to be rerendered by comparing component props, assuming that if a component's old and new props don't compare as equal (===), the component needs to be rerendered. If a prop is a callback or an object, and hasn't truly changed but has been reconstructed, it will compare as not-equal and cause a rerender. Vulcan's mutator HoCs add some callbacks to props, which you can call to perform mutations, but they get reconstructed - and, therefore, compare as not-equal - on every render. This caused some performance problems on LW.
This shuffles the construction of objects and callbacks around a bit, to prevent spurious rerenders caused by some Vulcan mutation HoCs. It does not cover every HoC. More importantly, this has (so far) only been  tested on Vulcan 1.12/Apollo1, and it's possible that some subtleties of the graphql function have changed, so it should be retested (both for not-breaking-anything and for not-rerendering) on Vulcan 1.13.

Sounds like a good change, but maybe we could wait until you've tested it with the new version for a while before merging?

@jimrandomh I applied this pull request to my own fork of Vulcan to test it, and I ran into the following problem: The mutation returned by the HoC does not have a name.
Before the change a mutation returned by withUpdate would look like this:

After the change the mutation returned looks like this:

I think this should be easy to remedy.


Problem with yarn -  yarn is not currently included in the bundle

When trying rails new example --webpack=react -T
I would get
https://github.com/bundler/bundler/blob/3df56d9a374b7239d196e02adffa6bcb734af49d/lib/bundler/rubygems_integration.rb#L371
to prompt
 `block in replace_bin_path': can't find executable yarn for gem yarn. yarn is not currently included in the bundle, perhaps you meant to add it to your Gemfile? (Gem::Exception)
Yarn not installed. Please download and install Yarn from https://yarnpkg.com/lang/en/docs/install/

Even though I have already yarn installed and I have tried multiple things. Uninstalling the yarn gem, removing all the binaries appearing after which yarn , uninstalling and reinstalling with npm & brew, etc.

solvec with:
for ver in $(rbenv whence yarn); do
  RBENV_VERSION="$ver" gem uninstall -ax yarn
  rm -f "$(rbenv prefix "$ver")/bin/yarn"
done
rbenv rehash


Fix two issues which prevents incremental llvm compilation

debug-info: Don't write temporary file names in the debug info.

This would prevent incremental llvm compilation because we would generate different IR on every compiler invocation.

SILCombiner: fix a non-determinism in a peephole optimization for load instructions.

Something went wrong when updating the original PR (https://github.com/apple/swift/pull/14337). So I created a new one.

@swift-ci smoke test and merge

@swift-ci smoke test linux

@swift-ci smoke test linux


fix update bzip download info

Signed-off-by: Wu, Kaiqiang<EMAIL_ADDRESS>Proposed changes
Issue Number: close #15938
Problem summary
Check historical changes, no need for two source for same bzip(as some other remove two source like boost etc.)
Checklist(Required)

Does it affect the original behavior:

[ ] Yes
[ ] No
[ ] I don't know

Has unit tests been added:

[ ] Yes
[ ] No
[ ] No Need

Has document been added or modified:

[ ] Yes
[ ] No
[ ] No Need

Does it need to update dependencies:

[ ] Yes
[ ] No

Are there any changes that cannot be rolled back:

[ ] Yes (If Yes, please explain WHY)
[ ] No

Further comments
If this is a relatively large or complex change, kick off the discussion at<EMAIL_ADDRESS>by explaining why you chose the solution you did and what alternatives you considered, etc...

TeamCity pipeline, clickbench performance test result:
the sum of best hot time: 35.01 seconds
load time: 497 seconds
storage size:<PHONE_NUMBER>7 Bytes
https://doris-community-test-1308700295.cos.ap-hongkong.myqcloud.com/tmp/20230117123329_clickbench_pr_82151.html


Configure Bnd plugin to create correct OSGi headers in the manifests

The current build does not run the bnd plugin, leaving the build artifacts with no OSGi headers in the manifest.

@hekonsek The configuration for the maven-jar-plugin seems to conflict with the Bnd plugin. I think it would be a good idea to keep the camel components build config as much like the "real" camel components as possible. That means moving the config to make the components self executable out, and the config for OSGi compatibility in.
WDYT?

@geertschuring yeah I think over the years from Apache Camel we have learned that the bnd tools and felix bundle plugin need a bit help from time to time, so having flexibility to tweak the plugin as we can do in the pom.xml at Apache Camel is likely needed.
Also we need for osgi to declare the export service and so on.
I would suggest to adopt the Camel way of making the components OSGi bundles.
Usually that is not so invasive as for most components its a few lines of properties in the top.

@gautric Can we remove these maven-jar-plugin entries from the components? I propose to create a dedicated "main runner" fat jars if you need them.

I have a commit on my laptop that removes the maven-jar-plugin config and adds the correct maven-bundle-plugin config. As soon as @gautric aggrees with this change, I will push it.

@hekonsek  @geertschuring  ok to remove


Cannot call a class as a function

Describe the bug
Component doesn't render. Gives the error:
Error in render: "TypeError: Cannot call a class as a function"

Code to replicate:
import VueSlider from 'vue-slider-component'
import 'vue-slider-component/theme/default.css'

Vue.component('vue-slider', VueSlider)

And then display the component.
<vue-slider v-model="value"></vue-slider>

Environment (If you feel unrelated, please delete the block)

OS & Version: macOS
Vue version: v2.6
Component Version: Tested on: v3.0.46, v3.2

Is it the same issue?
https://github.com/NightCatSama/vue-slider-component/issues/495

The same problem occurs to me.


Backport oracle database support to 3.0.2

Backport oracle database support to 3.0.2.

I have tested this pull request with MySQL, Postgres, Oracle 12c and 11g R2.


Compiler error without feature turned on

win32\platform.nim(1348, 12) Error: startHttpRequest requires --threads:on option

Not sure if this can be configured per nimble library that it needs this feature to be used?

Hm, I guess that approach isn't going to work. Instead I'll just not include the code without --threads:on until I can ideally remove the requirement (have idea but not guaranteed).
Added to this PR:
https://github.com/treeform/windy/pull/71

This should be fixed now.


LanguageClient doesn't show any error if initialization fails

I created a LanguageClient passing the path to a dll for Language Server. If the dll doesn't exist, the initialization fails but I don't see any error in the extension. I tracked the problem and realized in main.js/Initialize method when it's handling the error, the error.data is undefined so that's why the onReadyCallbacks.reject() is never get called. I added check null for error.data and error.data.retry and it fixed the problem. Not sure if there's something I'm missing or there's actually a bug in the main.ts

There is actually a real bug. The code can't assume that the error is of type response error since the error could be a normal program exception as well.


chore: Adding Spark35 support

Acrolinx Scorecards
A minimum Acrolinx score of 80 is required.
Click the scorecard links for each article to review the Acrolinx feedback on grammar, spelling, punctuation, writing style, and terminology.

Article
Acrolinxscore
Word andPhrases Score
CorrectnessScore
Scorecard
Processed

docs/Get Started/Install SynapseML.md
67
100
55
link
:white_check_mark:

More information about Acrolinx

Install Acrolinx locally for VSCode
False positives or issues
Troubleshooting issues with Acrolinx

Acrolinx Scorecards
A minimum Acrolinx score of 80 is required.
Click the scorecard links for each article to review the Acrolinx feedback on grammar, spelling, punctuation, writing style, and terminology.

Article
Acrolinxscore
Word andPhrases Score
CorrectnessScore
Scorecard
Processed

docs/Get Started/Install SynapseML.md
67
100
55
link
:white_check_mark:

More information about Acrolinx

Install Acrolinx locally for VSCode
False positives or issues
Troubleshooting issues with Acrolinx

Acrolinx Scorecards
A minimum Acrolinx score of 80 is required.
Click the scorecard links for each article to review the Acrolinx feedback on grammar, spelling, punctuation, writing style, and terminology.

Article
Acrolinxscore
Word andPhrases Score
CorrectnessScore
Scorecard
Processed

docs/Get Started/Install SynapseML.md
67
100
55
link
:white_check_mark:

More information about Acrolinx

Install Acrolinx locally for VSCode
False positives or issues
Troubleshooting issues with Acrolinx

Acrolinx Scorecards
A minimum Acrolinx score of 80 is required.
Click the scorecard links for each article to review the Acrolinx feedback on grammar, spelling, punctuation, writing style, and terminology.

Article
Acrolinxscore
Word andPhrases Score
CorrectnessScore
Scorecard
Processed

docs/Get Started/Install SynapseML.md
67
100
55
link
:white_check_mark:

More information about Acrolinx

Install Acrolinx locally for VSCode
False positives or issues
Troubleshooting issues with Acrolinx

Acrolinx Scorecards
A minimum Acrolinx score of 80 is required.
Click the scorecard links for each article to review the Acrolinx feedback on grammar, spelling, punctuation, writing style, and terminology.

Article
Acrolinxscore
Word andPhrases Score
CorrectnessScore
Scorecard
Processed

docs/Get Started/Install SynapseML.md
67
100
55
link
:white_check_mark:

More information about Acrolinx

Install Acrolinx locally for VSCode
False positives or issues
Troubleshooting issues with Acrolinx

Acrolinx Scorecards
A minimum Acrolinx score of 80 is required.
Click the scorecard links for each article to review the Acrolinx feedback on grammar, spelling, punctuation, writing style, and terminology.

Article
Acrolinxscore
Word andPhrases Score
CorrectnessScore
Scorecard
Processed

docs/Get Started/Install SynapseML.md
67
100
55
link
:white_check_mark:

More information about Acrolinx

Install Acrolinx locally for VSCode
False positives or issues
Troubleshooting issues with Acrolinx

Acrolinx Scorecards
A minimum Acrolinx score of 80 is required.
Click the scorecard links for each article to review the Acrolinx feedback on grammar, spelling, punctuation, writing style, and terminology.

Article
Acrolinxscore
Word andPhrases Score
CorrectnessScore
Scorecard
Processed

docs/Get Started/Install SynapseML.md
67
100
55
link
:white_check_mark:

More information about Acrolinx

Install Acrolinx locally for VSCode
False positives or issues
Troubleshooting issues with Acrolinx

Acrolinx Scorecards
A minimum Acrolinx score of 80 is required.
Click the scorecard links for each article to review the Acrolinx feedback on grammar, spelling, punctuation, writing style, and terminology.

Article
Acrolinxscore
Word andPhrases Score
CorrectnessScore
Scorecard
Processed

docs/Get Started/Install SynapseML.md
67
100
55
link
:white_check_mark:

More information about Acrolinx

Install Acrolinx locally for VSCode
False positives or issues
Troubleshooting issues with Acrolinx

Acrolinx Scorecards
A minimum Acrolinx score of 80 is required.
Click the scorecard links for each article to review the Acrolinx feedback on grammar, spelling, punctuation, writing style, and terminology.

Article
Acrolinxscore
Word andPhrases Score
CorrectnessScore
Scorecard
Processed

docs/Get Started/Install SynapseML.md
67
100
55
link
:white_check_mark:

More information about Acrolinx

Install Acrolinx locally for VSCode
False positives or issues
Troubleshooting issues with Acrolinx

Acrolinx Scorecards
A minimum Acrolinx score of 80 is required.
Click the scorecard links for each article to review the Acrolinx feedback on grammar, spelling, punctuation, writing style, and terminology.

Article
Acrolinxscore
Word andPhrases Score
CorrectnessScore
Scorecard
Processed

docs/Get Started/Install SynapseML.md
67
100
55
link
:white_check_mark:

More information about Acrolinx

Install Acrolinx locally for VSCode
False positives or issues
Troubleshooting issues with Acrolinx

Codecov Report
Attention: Patch coverage is 0% with 32 lines in your changes are missing coverage. Please review.

Project coverage is 12.10%. Comparing base (964ebfc) to head (a78f8ba).

Files
Patch %
Lines

...rk/sql/types/injections/OptimizedCKNNFitting.scala
0.00%
7 Missing :warning:

...crosoft/azure/synapse/ml/io/image/ImageUtils.scala
0.00%
3 Missing :warning:

...azure/synapse/ml/stages/MiniBatchTransformer.scala
0.00%
2 Missing :warning:

...ql/execution/streaming/DistributedHTTPSource.scala
0.00%
2 Missing :warning:

...ure/synapse/ml/services/bing/BingImageSearch.scala
0.00%
1 Missing :warning:

...e/ml/services/speech/SpeakerEmotionInference.scala
0.00%
1 Missing :warning:

...e/synapse/ml/services/speech/SpeechToTextSDK.scala
0.00%
1 Missing :warning:

...zure/synapse/ml/services/speech/TextToSpeech.scala
0.00%
1 Missing :warning:

...osoft/azure/synapse/ml/core/env/PackageUtils.scala
0.00%
1 Missing :warning:

...crosoft/azure/synapse/ml/explainers/LIMEBase.scala
0.00%
1 Missing :warning:

... and 12 more

Additional details and impacted files
@@             Coverage Diff             @@
##           master    #2182       +/-   ##
===========================================
- Coverage   76.37%   12.10%   -64.27%
===========================================
  Files         329      329
  Lines       17086    17086
  Branches     1515     1515
===========================================
- Hits        13049     2069    -10980
- Misses       4037    15017    +10980

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.

Acrolinx Scorecards
A minimum total score of 80 is required.
Select the total score link to review all feedback on clarity, consistency, tone, brand, terms, spelling, grammar, readability, and inclusive language. You should fix all spelling errors regardless of your total score. Fixing spelling errors helps maintain customer trust in overall content quality.

Article
Total score(Required: 80)
Words + phrases(Brand, terms)
Correctness(Spelling, grammar)
Clarity(Readability)

:white_check_mark: docs/Get Started/Install SynapseML.md
67
100
55
37

More information about Acrolinx

Install Acrolinx locally for VSCode
False positives or issues
Troubleshooting issues with Acrolinx

Acrolinx Scorecards
A minimum total score of 80 is required.
Select the total score link to review all feedback on clarity, consistency, tone, brand, terms, spelling, grammar, readability, and inclusive language. You should fix all spelling errors regardless of your total score. Fixing spelling errors helps maintain customer trust in overall content quality.

Article
Total score(Required: 80)
Words + phrases(Brand, terms)
Correctness(Spelling, grammar)
Clarity(Readability)

:white_check_mark: docs/Get Started/Install SynapseML.md
78
100
100
35

More information about Acrolinx

Install Acrolinx locally for VSCode
False positives or issues
Troubleshooting issues with Acrolinx

Acrolinx Scorecards
A minimum total score of 80 is required.
Select the total score link to review all feedback on clarity, consistency, tone, brand, terms, spelling, grammar, readability, and inclusive language. You should fix all spelling errors regardless of your total score. Fixing spelling errors helps maintain customer trust in overall content quality.

Article
Total score(Required: 80)
Words + phrases(Brand, terms)
Correctness(Spelling, grammar)
Clarity(Readability)

:white_check_mark: docs/Get Started/Install SynapseML.md
78
100
100
33

More information about Acrolinx

Install Acrolinx locally for VSCode
False positives or issues
Troubleshooting issues with Acrolinx

Acrolinx Scorecards
A minimum total score of 80 is required.
Select the total score link to review all feedback on clarity, consistency, tone, brand, terms, spelling, grammar, readability, and inclusive language. You should fix all spelling errors regardless of your total score. Fixing spelling errors helps maintain customer trust in overall content quality.

Article
Total score(Required: 80)
Words + phrases(Brand, terms)
Correctness(Spelling, grammar)
Clarity(Readability)

:white_check_mark: docs/Get Started/Install SynapseML.md
78
100
100
33

More information about Acrolinx

Install Acrolinx locally for VSCode
False positives or issues
Troubleshooting issues with Acrolinx

Acrolinx Scorecards
A minimum total score of 80 is required.
Select the total score link to review all feedback on clarity, consistency, tone, brand, terms, spelling, grammar, readability, and inclusive language. You should fix all spelling errors regardless of your total score. Fixing spelling errors helps maintain customer trust in overall content quality.

Article
Total score(Required: 80)
Words + phrases(Brand, terms)
Correctness(Spelling, grammar)
Clarity(Readability)

:white_check_mark: docs/Get Started/Install SynapseML.md
78
100
100
33

More information about Acrolinx

Install Acrolinx locally for VSCode
False positives or issues
Troubleshooting issues with Acrolinx

Acrolinx Scorecards
A minimum total score of 80 is required.
Select the total score link to review all feedback on clarity, consistency, tone, brand, terms, spelling, grammar, readability, and inclusive language. You should fix all spelling errors regardless of your total score. Fixing spelling errors helps maintain customer trust in overall content quality.

Article
Total score(Required: 80)
Words + phrases(Brand, terms)
Correctness(Spelling, grammar)
Clarity(Readability)

:white_check_mark: docs/Get Started/Install SynapseML.md
78
100
100
33

More information about Acrolinx

Install Acrolinx locally for VSCode
False positives or issues
Troubleshooting issues with Acrolinx


Changes to course statistics

For new courses stats on the course statistic page:

[x] Create a link on the title, which links to the detail page.
[x] Change amount from 15 to 25 courses
[x] Add amount of new courses per month, for the last 1.5 year

(discussed during the meeting today, except point 2)
In the test instance, this page can be found here: https://test-dhcr.clarin-dariah.eu/dashboard/statistics
Note: Don't use this data since data in the test instance is always outdated!

@IvdL22 @PixlTracer
The 3 features you've requested (see first comment) are ready.
You can find them in the test instance, at Dashboard / Statistics / Course Statistics
Can you change the label to Done if satisfied?

this is great, thank you Patrick!

Implemented in 2023-12


Unicode font fallback not working

When generating a PDF, I have some characters that render fine using "Helvetica" (characters like ǹ, Ț, ȑ) but also others that don't. These others (e.g. Chinese characters) seem to work fine when I use "Arial Unicode", but Arial Unicode does not support either of ǹ or Ț. So I figured I could specify several font families, just like in a browser, where it would go through the list to find a font family that has the missing glyphs:
body {
    font-family: "Arial Unicode", "Helvetica", "sans-serif";
}

But that is the same as if I only specified "Arial Unicode". If I reverse the order, it's the same as if I only specified "Helvetica". So it seems to me that xhtml2pdf only ever looks at the first font in the list, even though, according to the debug log, it loads all specified font files.

I think this is a matter of the lower layers, reportlab and also ultimately the responsibility of the PDF viewer. xhtml2pdf won't be able to parse font files (that may not even be present on the server) to analyze which glyphs are there and which are in the displayed elements etc.


chore(main): release pixels 0.3.0

:robot: I have created a release beep boop
0.3.0 (2024-04-16)
Features

uniform: add initial package (c189b28)

Bug Fixes

pixels,uniform: improve build logic (adc013d)
pixels: fixed jumping copy icon in Json component (135dd00)

This PR was generated with Release Please. See documentation.

:robot: Release is at https://github.com/fuf-stack/uniform/releases/tag/pixels-v0.3.0 :sunflower:


Safe to use personal facebook account?

I discovered the fbchat library recently and was using it to create a bot that prevents nicknames from being changed in one of my messenger groups. However, I am using this bot with the login credentials of my personal account (the one I've used for Facebook for 10+ years now). The account is very active and I'm always liking, commenting, following pages, and messaging using it. It also has a verified mobile phone number associated with it.
Despite it not being a pure bot account, I am still worried that my account might get disabled and I might be required to send facebook government ID to recover it. I already got a notice after 4-5 logins saying that there was unusual activity on my account and had to reset my password.
The bot doesn't spam messages and acts as human as it can be. The only sort of spammy thing it does is change back the nicknames of all the people in the group (6-7 people) to their original nickname, without delays in between, when it first logs in. It then listens for nickname changes and if a change is detected it changes the nickname back to the original nickname. When I decide to exit the program it logs out.
I am starting to use session cookies to login and trying to minimize the logging in and out using fbchat. I think that has stopped the unusual activity problem but I'll see in a few days.
Are there any things I can do on top of this to make sure that my personal account doesn't get blocked and is it safe for me to use my personal facebook account with this library?

Using session cookies is a very good idea. I was using fbchat on my personal account for almost a year, and it was never blocked permanently. Now I'm using it on a second account and they have blocked me only once (fbchat + not using session cookies + IP from mobile data). But I needed just to type the birthday date (I didn't remeber it) and luckily after a few days, they just... unblocked it. So finally, you CAN use it on your personal account but it's not a big deal to create a new account just for safety.

Related: #343 and #427

I used my personal account to develop #434, and Im using it also for my chat logger.
No problems so far.


Issue 3440 not resolved on version 5.4.40

Description
Receiving the error below when trying to auto fill any user when using a luck perms command
Reproduction Steps
Typing any luckperms command and trying to auto fill.
Expected Behaviour
The command should work.
Server Details
git-Pufferfish-24 (MC: 1.19)
LuckPerms Version
5.4.40
Logs and Configs
https://pastes.dev/lb5zWUpN0r
Extra Details
No response

#3440 is not the same issue as this. also please attach a full log, not just the error from the console

#3440 is not the same issue as this. also please attach a full log, not just the error from the console

My bad, I've attached the entire log.

can you paste the latest.log file instead of uploading a compressed older log

can you paste the latest.log file instead of uploading a compressed older log

The latest.log is running an older version that I tried today, is that fine?

update everything, restart the server, reproduce the issue, then do it

update everything, restart the server, reproduce the issue, then do it

Ok, I'll do that now


Fix issue with cursor in pycharm console (#29)

This PR provides a fix for the behavior described in #29.
In comparing the plugin's theme definitions with those of a handful of other plugins (e.g. Nord, Material, and Solarized), I noticed that ours don't specify a concrete value for CONSOLE_USER_INPUT, as shown here:
<option name="CONSOLE_USER_INPUT">
  <value />
</option>

When the value is specified, as below, the Pycharm's console cursor appears in the correct place. So it seems like Pycharm takes issue with the definition above. Shame it doesn't issue a warning or anything.
<option name="CONSOLE_USER_INPUT">
  <value>
    <option name="FOREGROUND" value="ebdbb2" />
  </value>
</option>

This isn't the only instance of <value /> in the theme definitions. I've also provided a concrete specification for CONSOLE_NORMAL_OUTPUT. The rest I've left as is, since there are no indications that they are causing problems.

Thanks!
I actually took a look at this this morning and found out these <value /> as well in the color scheme.
I will review this and the other missing values tomorrow :)

Sorry for the delay!

No worries! Thanks for merging. :)


Play an empty track at all time to ensure autoplay on safari

depends on https://github.com/livekit/client-sdk-js/pull/733
The current implementation requires an update to getEmptyAudioTrack that sets its volume to 0, otherwise users would constantly hear the sine wave playing.

instead of handling this on the react level we could also do this

in the core package with document.append(emptyAudioPlayer) and call play on startAudio
move the logic for it into client-sdk-js so that all implementations get it. we could also make it Safari only for now

closing in favor of https://github.com/livekit/client-sdk-js/pull/733


Extension Bundles v2.8.5 and v3.5.0 have been abandoned

We have abandoned two versions of Extension Bundles: 2.8.5 and 3.5.0. The next versions released will be 2.9.0 and 3.6.0.
Please keep any questions and discussions under this issue. Thank you.

Any timeframe on these releases?  I am waiting on the durable task storage fixes in https://github.com/Azure/durabletask/releases/tag/durabletask.azurestorage-v1.9.3.

Closing this one as an updated version of bundle v2 and v3 have been released.


Deprecate FileCollection.add()

The method was never really working as expected, as in most cases it would throw UOE.
This also fixes a bug with PmdExtension.ruleSetFiles() always throwing the aforementioned UOE exception.

Build: https://builds.gradle.org/viewQueued.html?itemId=11933649


How to adjust Dropdown width?

Hi !
I noticed that Dropdown component has hardcoded width: 224px and if DropdownItem has long long word in title inside (unfortunately happens in hardware naming)  than horizontal scrollbar appears inside open dropdown.
Would it be possible to adjust width: 224px maybe to be min-width: 224px ?
Thank you in advance.

Hi,
Thank you for pointing out this issue to us.
We will look into it.


Why is my car looks weird ?

Here is the screen and the obj zip (I changed the .jpg to .png before rendering).

uploads_files_1017599_Jeep_Renegade_2016_obj (2).zip
The link of the model : https://www.cgtrader.com/free-3d-models/car/suv/jeep-renegade-a-5-doors-compact-suv-from-2016

https://www.cgtrader.com/items/3132934/download-page
Same for this car, this time it has his own .png texture so Idk why it doesn't work.

try triangulating the model first


Deleting incoming messages

While looping over incoming messages, calling the deleteMessage() function doesn't appear to work - the message is still there the next time.  Also there's no way to get the ID of a message from the IncomingMessage object.
$messages = $imap->getMessages();
foreach ($messages as $message)
{
    $imap->deleteMessage($message->id); // had to make the id property public to do this
}

OK I figured it out - you have to use the "uid" not the "id" to delete a message - but the "uid" property on the IncomingMessage object was null, so you have to do the following which is weird really:
$uid = $imap->getUid($message->id);
$imap->deleteMessage($uid);

Shouldn't there just be a deleteMessage() function on the IncomingMessage class itself?

So this deleteMessage would 1) Delete the message from the inbox 2) Null the object correct?

Message id is obtained this way
$inMessages = $imap->getMessages();
foreach ($inMessages as $inMessage)
{
# id
    $inMessage->header->msgno;
# uid
    $inMessage->header->uid;
}

See http://php.net/manual/ru/function.imap-fetch-overview.php
Id in IncomingMessage must be private, therefore.
You can also use method
$imap->getUid($id);

But we'll think about this.
$imap->deleteMessage($uid);

This should be added to the documentation.
# id
    $inMessage->header->msgno;

Hello @hhdivil, Is this still an issue. Please close this issue if so.

@hhdivil I assume this issue is fixed. Closing...


Command name: Should it be "BlameEnable"?

I noticed that the patterns of command name is different from other plugins.
Specifically, "FooToggle" is more common than "ToggleFoo". This seems a typical convention.
Example:
https://github.com/folke/trouble.nvim?tab=readme-ov-file#commands
So my proposal is to rename "Enable" to "BlameEnable". What do you think?

Oh I see.
I agree that this should have been the other way,
but I don't think its such a big deal to warrant breaking peoples configs.
Ill leave it open as its a valid observation and should be visible somewhere

I'd like to suggest creating aliases for EnableBlame, and then deprecating EnableBlame, and finally removing it.

There is only BlameToggle command now in the latest version


test.py

Is there not the file test.py in this code?

I guess author just wanted to get embedding from train.py instead of considering TransE as a baseline model.


Changeable upload field destination path

After adding an Upload Field to a section, when editing the field if I change destination path, I think old destination folder should be renamed to new destination folder and all affected entries should be updated accordingly (file pointing to new destination + filename).
What do you think?

Renaming the physical destination folder is dangerous as soon as two different upload fields make use of the same folder. It would be a good idea, if Symphony wasn't storing the path in the database for each entry though: this way you could change the path in the settings and move the files via FTP and everything would still be working.

It would be a good idea, if Symphony wasn't storing the path in the database for each entry though: this way you could change the path in the settings and move the files via FTP and everything would still be working.

It'd just flip the scenario. Users who don't move files to the new directory would then have broken links. By having the full path stored in the database, regardless of how many times the folder name is changed, there won't be broken links.

This is be most unrealistic scenario for me when I'm thinking of our projects. Normally, we only change folders during development so the initial content we added for the client would be placed inside wrong folders. We would be very lazy not to move the files to the corrected place but with the given Symphony setup you have to edit each entry in the data base manually or you have to detach and reattach all files in the backend. It's far easier if you have to take care of the physically files manually than of the rest.

Users who don't move files to the new directory would then have broken links.

Then perhaps Symphony could move files from old location to new location? And update all affected entries on change.

This is not something that will be addressed by Symphony in the near future.


python312Packages.zipstream-ng: 1.7.1 -> 1.8.0

Diff: https://github.com/pR0Ps/zipstream-ng/compare/refs/tags/v1.7.1...v1.8.0
Changelog: https://github.com/pR0Ps/zipstream-ng/blob/v1.8.0/CHANGELOG.md

Things done

Built on platform(s)

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

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[x] sandbox = relaxed
[ ] sandbox = true

[x] Tested, as applicable:

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

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

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[x] Fits CONTRIBUTING.md.

Add a :+1: reaction to pull requests you find important.

Result of nixpkgs-review pr 353125 at e7bf5fb7 run on aarch64-darwin 1

:fast_forward: 1 package marked as broken and skipped:

octoprint

:white_check_mark: 4 packages built:

magic-wormhole (python312Packages.magic-wormhole)
python311Packages.magic-wormhole
python311Packages.zipstream-ng
python312Packages.zipstream-ng

Result of nixpkgs-review pr 353125 at e7bf5fb7 run on x86_64-linux 1

:x: 3 packages failed to build:

tahoe-lafs
tahoe-lafs.doc
tahoe-lafs.info

:white_check_mark: 6 packages built:

gnome-keysign
magic-wormhole (python312Packages.magic-wormhole)
octoprint
python311Packages.magic-wormhole
python311Packages.zipstream-ng
python312Packages.zipstream-ng

tahoe-lafs is already broken on master.


How to do kubectl cp with the lib?

I need to copy files to/from containers in pods. What's the best way to do that with the pykube lib?

Sadly, kubectl cp is just a kubectl exec 'tar ....', thus it only works with containers that have the tar command installed.
But I agree that having this command is sometimes useful. We've implemented kubectl cp in python but having it natively in pykube could be great


📝docs: sync with examples files, small updates

Add some prints on example files with key information about possible error and a description in some examples about a correct way to have en environment variables for the correct use of the example
Also update the example docs and improve docs navigation.

Tutorial and Examples Review Completion
Overview
Completed comprehensive review and validation of all tutorial sections and example code. All components have been tested and verified for functionality.
Completed Tasks
Tutorial Sections

✓ Project Setup and Installation
✓ Core Functionality Implementation
✓ Error Handling and Data Persistence
✓ Advanced Features and Visualization

Example Code Verification

✓ Basic Usage Examples
✓ Async Operations
✓ File Operations
✓ Docker Integration
✓ Error Handling Patterns

Key Improvements
Documentation Structure

Organized tutorial sections with clear progression
Added cross-references between related concepts
Improved code comments and explanations

Code Quality

Verified all code snippets execute successfully
Added error handling for edge cases
Improved type hints and documentation

Example Coverage

Added missing examples for key features
Updated outdated code patterns
Expanded Docker usage examples

Testing Results
Core Tutorial Code
Successfully tested main components:
markdown:(docs/tutorial/core_functionality.md)

startLine: 70
endLine: 114

References

Quick Start Guide
API Reference
Implementation Guide

All tutorial sections and examples are now ready for production use. Documentation provides a clear path from basic to advanced usage.


Get rid of ImageView onClick in GameDetailViewModel

Find a way to change the image without having to pass the view in the ViewModel. This is not good practice

Done! Moved to viewactions package


Add IRC bot to integrations list.

Signed-off-by: Ben Kochie<EMAIL_ADDRESS>Closes: https://github.com/prometheus/docs/issues/1013

As far as I can see this is not an IRC bot, it is a telegram bot of which we already have one listed.

Oh, my mistake, how about https://github.com/multimfi/bot


"This target might include its own product" error when archiving

I get this error whenever I archive (using Xcode 8). If I just build, I get #5:

I tried disabling "Find Implicit Dependencies" in the scheme, and removing the explicit target dependency in the app target, but nothing helped :/

Go to Build Phases for the target "SwiftInitializerGenerator" and remove the Copy Files phase.

I had the same issue. Deleting the Copy Files stage got it to build and archive. However, following the remaining steps in the README still goes get me a functioning extension. It does not appear in the Editor menu.

I've reverted the Copy Files phase, thanks. @rcritz can you try once again? And maybe try and check if there's something logged in the Console app? If it still doesn't work, please open a new issue, as it is not related to the one discussed here.

I had the same issue. Deleting the Copy Files stage got it to build and archive. However, following the remaining steps in the README still goes get me a functioning extension. It does not appear in the Editor menu.

Same here: I managed to build, archive, and install the extension as described in the README. However, it's still not showing up on the Editor menu in Xcode, despite multiple attempts, restarting Xcode, etc.

@NachoSoto @rcritz I had to go to System Preferences -> Extensions -> Xcode Source Editor and enable the extension before it showed up


Update Pr Girolami link

Old page is gone

404 http://www.brc.dcs.gla.ac.uk/~girolami/Machine_Learning_Module_2006/index.htm
404 http://www.brc.dcs.gla.ac.uk/~girolami

Seems like the old page is available sometimes but yeah why not simplify and use the GitHub mirror.


Change color from pink to white for UTXO and Change amount on send confirmation screen

Please make amounts of "Total UTXO value" and "Change" in white color. Pink color only for send amount. On previous screen (send) available in white color, so UTXO and Change also should be in white

Design: https://zpl.io/2jzPBkm

checked

checked


Can not run on winXP 64bit

Environment

Tesseract Version: tesseract-ocr-w64-setup-v5.0.0-alpha.20191030.exe
Commit Number:
Platform: Windows XP Profesional Service Pack 1 - 64bit

Current Behavior:
Can not run tesseract.exe

Expected Behavior:
Running well on Windows Xp 64 bit

Windows XP is end of life, so no longer supported by its vendor.
I suggest to use Tesseract on Linux which works well and is faster.

Building Tesseract for Windows XP is possible in principle, but needs some work. I estimate several days. So this is a question of priorities and costs.