Most containers do not get an ip address after update from lxc 0.19 to lxd 2.0.0-rc1

Required information

Distribution: Ubuntu
Distribution version: Ubuntu 15.04
The output of "lxc info":

apicompat: 0
auth: trusted
environment:
  addresses: []
  architectures:
  - x86_64
  - i686
  certificate:
  --- removed ---
  driver: lxc
  driverversion: 2.0.0.rc5
  kernel: Linux
  kernelarchitecture: x86_64
  kernelversion: 3.19.0-51-generic
  server: lxd
  serverpid: 23382
  serverversion: 2.0.0.beta4
  storage: lvm
  storageversion: 2.02.111(2) (2014-09-01) / 1.02.90 (2014-09-01) / 4.29.0
config:
  images.remote_cache_expiry: "1"

Issue description
After upgrading from  lxd 0.19 to 2.0.0-rc1 most containers no not get an IP address anymore.
lxc list output:
+-------------------+---------+--------------------------------+------+------------+-----------+
|       NAME        |  STATE  |              IPV4              | IPV6 |    TYPE    | SNAPSHOTS |
+-------------------+---------+--------------------------------+------+------------+-----------+
| container1        | STOPPED |                                |      | PERSISTENT | 0         |
+-------------------+---------+--------------------------------+------+------------+-----------+
| container2        | RUNNING | <IP_ADDRESS> (eth1)                |      | PERSISTENT | 0         |
|                   |         | <IP_ADDRESS> (eth0)              |      |            |           |
+-------------------+---------+--------------------------------+------+------------+-----------+
| container3        | RUNNING | <IP_ADDRESS> (eth0)             |      | PERSISTENT | 0         |
|                   |         | <IP_ADDRESS> (eth1)               |      |            |           |
+-------------------+---------+--------------------------------+------+------------+-----------+
| container4        | RUNNING |                                |      | PERSISTENT | 0         |
+-------------------+---------+--------------------------------+------+------------+-----------+
| container5        | RUNNING |                                |      | PERSISTENT | 0         |
+-------------------+---------+--------------------------------+------+------------+-----------+
| container6        | RUNNING |                                |      | PERSISTENT | 0         |
+-------------------+---------+--------------------------------+------+------------+-----------+
| container7        | RUNNING |                                |      | PERSISTENT | 0         |
+-------------------+---------+--------------------------------+------+------------+-----------+
| container8        | RUNNING |                                |      | PERSISTENT | 0         |
+-------------------+---------+--------------------------------+------+------------+-----------+
| container9        | RUNNING |                                |      | PERSISTENT | 0         |
+-------------------+---------+--------------------------------+------+------------+-----------+
| container10       | RUNNING |                                |      | PERSISTENT | 0         |
+-------------------+---------+--------------------------------+------+------------+-----------+
| container11       | RUNNING |                                |      | PERSISTENT | 0         |
+-------------------+---------+--------------------------------+------+------------+-----------+
| container12       | RUNNING |                                |      | PERSISTENT | 0         |
+-------------------+---------+--------------------------------+------+------------+-----------+
| container12       | STOPPED |                                |      | PERSISTENT | 0         |
+-------------------+---------+--------------------------------+------+------------+-----------+

container1 won't start anymore, but I'm opening a separate issue for this problem.
I've investigated container 6:
container6's profile:
name: container6
config:
  boot.autostart: "true"
  limits.cpu: "3"
  limits.memory: 3072MB
  raw.lxc: lxc.aa_profile=unconfined
  security.privileged: "true"
description: ""
devices:
  eth0:
    nictype: bridged
    parent: lxcbr0
    type: nic
  eth1:
    nictype: bridged
    parent: br0.114
    type: nic
  eth2:
    nictype: bridged
    parent: br0
    type: nic

ifconfig in container6:
Notice the interface names, I would have expected these to be eth0, eht1 and eth2. After restarting this container the interface names changed from eth0, eht1 and eth2 to eth3, eht4 and eth5. After restarting this container again the interface names stayed the same (still eth3, eht4 and eth5).
eth3      Link encap:Ethernet  HWaddr 00:16:3e:8a:67:be
          inet6 addr: fe80::216:3eff:fe8a:67be/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:8 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:0 (0.0 B)  TX bytes:648 (648.0 B)

eth4      Link encap:Ethernet  HWaddr 00:16:3e:28:54:12
          inet6 addr: fe80::216:3eff:fe28:5412/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:214 errors:0 dropped:0 overruns:0 frame:0
          TX packets:8 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:12216 (12.2 KB)  TX bytes:648 (648.0 B)

eth5      Link encap:Ethernet  HWaddr 00:16:3e:1f:33:05
          inet6 addr: fe80::216:3eff:fe1f:3305/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:228 errors:0 dropped:0 overruns:0 frame:0
          TX packets:8 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:13064 (13.0 KB)  TX bytes:648 (648.0 B)

lo        Link encap:Local Loopback
          inet addr:<IP_ADDRESS>  Mask:<IP_ADDRESS>
          inet6 addr: ::1/128 Scope:Host
          UP LOOPBACK RUNNING  MTU:65536  Metric:1
          RX packets:144 errors:0 dropped:0 overruns:0 frame:0
          TX packets:144 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:12384 (12.3 KB)  TX bytes:12384 (12.3 KB)

/etc/network/interfaces (container6):
auto lo
iface lo inet loopback

# lxcbr0
auto eth0
iface eth0 inet static
        address <IP_ADDRESS>
        netmask <IP_ADDRESS>
        gateway <IP_ADDRESS>
        dns-nameservers <IP_ADDRESS> <IP_ADDRESS>

# vlan br0.106
auto eth1
iface eth1 inet static
        address <IP_ADDRESS>
        netmask <IP_ADDRESS>

# keepalived failover ip interface
auto eth2
iface eth2 inet static
        address <IP_ADDRESS>
        dns-nameservers <IP_ADDRESS> <IP_ADDRESS>

lxc info container6:
Name: container6
Architecture: x86_64
Status: Running
Type: persistent
Profiles: container6
Pid: 2898114
Processes: 37
Ips:
  eth5:	inet6	fe80::216:3eff:fe1f:3305	veth75MSAD
  lo:	inet	<IP_ADDRESS>
  lo:	inet6	::1
  eth3:	inet6	fe80::216:3eff:fe8a:67be	vethC4AF26
  eth4:	inet6	fe80::216:3eff:fe28:5412	vethCLKMBQ

"ifconfig lxcbr0" on host

lxcbr0    Link encap:Ethernet  HWaddr fe:32:db:96:96:b7
          inet addr:<IP_ADDRESS>  Bcast:<IP_ADDRESS>  Mask:<IP_ADDRESS>
          inet6 addr: fe80::fc32:dbff:fe96:96b7/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:7569 errors:0 dropped:0 overruns:0 frame:0
          TX packets:6662 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:744901 (744.9 KB)  TX bytes:20589048 (20.5 MB)

cat /etc/default/lxc-net (host)
USE_LXC_BRIDGE="true"
LXC_BRIDGE="lxcbr0"
LXC_ADDR="<IP_ADDRESS>"
LXC_NETMASK="<IP_ADDRESS>"
LXC_NETWORK="<IP_ADDRESS>/24"
LXC_DHCP_RANGE="<IP_ADDRESS>,<IP_ADDRESS>"
LXC_DHCP_MAX="253"

Information to attach

[x] any relevant kernel output (dmesg)

[17174.306916] br0: port 6(veth5YWJYR) entered disabled state
[17174.307539] br0.114: port 2(vethFGNEUQ) entered disabled state
[17174.308153] lxcbr0: port 4(vethMW4LGP) entered disabled state
[17174.308612] device veth5YWJYR left promiscuous mode
[17174.308614] br0: port 6(veth5YWJYR) entered disabled state
[17174.308776] device vethFGNEUQ left promiscuous mode
[17174.308778] br0.114: port 2(vethFGNEUQ) entered disabled state
[17174.308943] device vethMW4LGP left promiscuous mode
[17174.308944] lxcbr0: port 4(vethMW4LGP) entered disabled state
[17174.500218] net_ratelimit: 218 callbacks suppressed
[17174.990381] audit: type=1400 audit(1457104948.509:74): apparmor="STATUS" operation="profile_remove" profile="unconfined" name="lxd-container6_</var/lib/lxd>" pid=2897460 comm="apparmor_parser"
[17179.348058] EXT4-fs (dm-17): mounted filesystem with ordered data mode. Opts: discard
[17179.350135] audit: type=1400 audit(1457104952.865:75): apparmor="STATUS" operation="profile_load" profile="unconfined" name="lxd-container6_</var/lib/lxd>" pid=2897995 comm="apparmor_parser"
[17179.355970] device vethC4AF26 entered promiscuous mode
[17179.356006] IPv6: ADDRCONF(NETDEV_UP): vethC4AF26: link is not ready
[17179.356016] lxcbr0: port 4(vethC4AF26) entered forwarding state
[17179.356018] lxcbr0: port 4(vethC4AF26) entered forwarding state
[17179.357760] lxcbr0: port 4(vethC4AF26) entered disabled state
[17179.359134] device vethCLKMBQ entered promiscuous mode
[17179.359182] IPv6: ADDRCONF(NETDEV_UP): vethCLKMBQ: link is not ready
[17179.359197] br0.114: port 2(vethCLKMBQ) entered listening state
[17179.359200] br0.114: port 2(vethCLKMBQ) entered listening state
[17179.362330] device veth75MSAD entered promiscuous mode
[17179.362374] IPv6: ADDRCONF(NETDEV_UP): veth75MSAD: link is not ready
[17179.362389] br0: port 6(veth75MSAD) entered listening state
[17179.362393] br0: port 6(veth75MSAD) entered listening state
[17179.364594] IPVS: Creating netns size=2056 id=24
[17179.459417] eth3: renamed from vethSAJ21Q
[17179.478237] eth4: renamed from vethSOJXQF
[17179.498040] eth5: renamed from vethC0AY30
[17179.518111] IPv6: ADDRCONF(NETDEV_CHANGE): vethCLKMBQ: link becomes ready
[17179.518154] IPv6: ADDRCONF(NETDEV_CHANGE): veth75MSAD: link becomes ready
[17179.518180] IPv6: ADDRCONF(NETDEV_CHANGE): vethC4AF26: link becomes ready
[17179.518200] lxcbr0: port 4(vethC4AF26) entered forwarding state
[17179.518203] lxcbr0: port 4(vethC4AF26) entered forwarding state

[x] container log (lxc info NAME --show-log)

            lxc<PHONE_NUMBER>2227.651 DEBUG    lxc_commands - commands.c:lxc_cmd_handler:893 - peer has disconnected
            lxc<PHONE_NUMBER>2227.651 DEBUG    lxc_commands - commands.c:lxc_cmd_handler:893 - peer has disconnected
            lxc<PHONE_NUMBER>2227.651 DEBUG    lxc_commands - commands.c:lxc_cmd_handler:893 - peer has disconnected
            lxc<PHONE_NUMBER>2227.651 DEBUG    lxc_commands - commands.c:lxc_cmd_handler:893 - peer has disconnected
            lxc<PHONE_NUMBER>2227.651 DEBUG    lxc_commands - commands.c:lxc_cmd_handler:893 - peer has disconnected
            lxc<PHONE_NUMBER>2227.651 DEBUG    lxc_commands - commands.c:lxc_cmd_handler:893 - peer has disconnected
            lxc<PHONE_NUMBER>2227.651 DEBUG    lxc_commands - commands.c:lxc_cmd_handler:893 - peer has disconnected
            lxc<PHONE_NUMBER>2227.651 DEBUG    lxc_commands - commands.c:lxc_cmd_handler:893 - peer has disconnected
            lxc<PHONE_NUMBER>2227.651 DEBUG    lxc_commands - commands.c:lxc_cmd_handler:893 - peer has disconnected
            lxc<PHONE_NUMBER>2227.651 DEBUG    lxc_commands - commands.c:lxc_cmd_handler:893 - peer has disconnected
            lxc<PHONE_NUMBER>2227.651 DEBUG    lxc_commands - commands.c:lxc_cmd_handler:893 - peer has disconnected
            lxc<PHONE_NUMBER>2227.651 DEBUG    lxc_commands - commands.c:lxc_cmd_handler:893 - peer has disconnected
            lxc<PHONE_NUMBER>2227.707 DEBUG    lxc_start - start.c:signal_handler:341 - container init process exited
            lxc<PHONE_NUMBER>2227.707 DEBUG    lxc_start - start.c:__lxc_start:1324 - unknown exit status for init: 9
            lxc<PHONE_NUMBER>2227.707 DEBUG    lxc_start - start.c:__lxc_start:1329 - Pushing physical nics back to host namespace
            lxc<PHONE_NUMBER>2227.707 DEBUG    lxc_start - start.c:__lxc_start:1332 - Tearing down virtual network devices used by container
            lxc<PHONE_NUMBER>2227.707 WARN     lxc_conf - conf.c:lxc_delete_network:2904 - failed to remove interface 134 'eth3'
            lxc<PHONE_NUMBER>2227.707 WARN     lxc_conf - conf.c:lxc_delete_network:2904 - failed to remove interface 136 'eth4'
            lxc<PHONE_NUMBER>2227.707 WARN     lxc_conf - conf.c:lxc_delete_network:2904 - failed to remove interface 138 'eth5'
            lxc<PHONE_NUMBER>2227.707 INFO     lxc_error - error.c:lxc_error_set_and_log:55 - child <1913240> ended on signal (9)
            lxc<PHONE_NUMBER>2227.707 WARN     lxc_conf - conf.c:lxc_delete_network:2904 - failed to remove interface 134 'eth3'
            lxc<PHONE_NUMBER>2227.707 WARN     lxc_conf - conf.c:lxc_delete_network:2904 - failed to remove interface 136 'eth4'
            lxc<PHONE_NUMBER>2227.707 WARN     lxc_conf - conf.c:lxc_delete_network:2904 - failed to remove interface 138 'eth5'
            lxc<PHONE_NUMBER>2227.817 INFO     lxc_conf - conf.c:run_script_argv:367 - Executing script '/usr/share/lxcfs/lxc.reboot.hook' for container 'container6', config section 'lxc'
            lxc<PHONE_NUMBER>2228.318 INFO     lxc_conf - conf.c:run_script_argv:367 - Executing script '/usr/bin/lxd callhook /var/lib/lxd 22 stop' for container 'container6', config section 'lxc'
            lxc<PHONE_NUMBER>2228.521 INFO     lxc_commands - commands.c:lxc_cmd_stop:624 - 'container6' has stopped
            lxc<PHONE_NUMBER>2232.859 INFO     lxc_start - start.c:lxc_check_inherited:251 - closed inherited fd 3
            lxc<PHONE_NUMBER>2232.859 INFO     lxc_start - start.c:lxc_check_inherited:251 - closed inherited fd 8
            lxc<PHONE_NUMBER>2232.860 INFO     lxc_container - lxccontainer.c:do_lxcapi_start:797 - Attempting to set proc title to [lxc monitor] /var/lib/lxd/containers container6
            lxc<PHONE_NUMBER>2232.861 INFO     lxc_start - start.c:lxc_check_inherited:251 - closed inherited fd 8
            lxc<PHONE_NUMBER>2232.861 INFO     lxc_lsm - lsm/lsm.c:lsm_init:48 - LSM security driver AppArmor
            lxc<PHONE_NUMBER>2232.861 INFO     lxc_seccomp - seccomp.c:parse_config_v2:342 - processing: .reject_force_umount  # comment this to allow umount -f;  not recommended.
            lxc<PHONE_NUMBER>2232.861 INFO     lxc_seccomp - seccomp.c:parse_config_v2:446 - Adding native rule for reject_force_umount action 0
            lxc<PHONE_NUMBER>2232.861 INFO     lxc_seccomp - seccomp.c:do_resolve_add_rule:216 - Setting seccomp rule to reject force umounts

            lxc<PHONE_NUMBER>2232.861 INFO     lxc_seccomp - seccomp.c:parse_config_v2:449 - Adding compat rule for reject_force_umount action 0
            lxc<PHONE_NUMBER>2232.861 INFO     lxc_seccomp - seccomp.c:do_resolve_add_rule:216 - Setting seccomp rule to reject force umounts

            lxc<PHONE_NUMBER>2232.861 INFO     lxc_seccomp - seccomp.c:parse_config_v2:342 - processing: .[all].
            lxc<PHONE_NUMBER>2232.861 INFO     lxc_seccomp - seccomp.c:parse_config_v2:342 - processing: .kexec_load errno 1.
            lxc<PHONE_NUMBER>2232.861 INFO     lxc_seccomp - seccomp.c:parse_config_v2:446 - Adding native rule for kexec_load action 327681
            lxc<PHONE_NUMBER>2232.861 INFO     lxc_seccomp - seccomp.c:parse_config_v2:449 - Adding compat rule for kexec_load action 327681
            lxc<PHONE_NUMBER>2232.861 INFO     lxc_seccomp - seccomp.c:parse_config_v2:342 - processing: .open_by_handle_at errno 1.
            lxc<PHONE_NUMBER>2232.861 INFO     lxc_seccomp - seccomp.c:parse_config_v2:446 - Adding native rule for open_by_handle_at action 327681
            lxc<PHONE_NUMBER>2232.861 INFO     lxc_seccomp - seccomp.c:parse_config_v2:449 - Adding compat rule for open_by_handle_at action 327681
            lxc<PHONE_NUMBER>2232.861 INFO     lxc_seccomp - seccomp.c:parse_config_v2:342 - processing: .init_module errno 1.
            lxc<PHONE_NUMBER>2232.861 INFO     lxc_seccomp - seccomp.c:parse_config_v2:446 - Adding native rule for init_module action 327681
            lxc<PHONE_NUMBER>2232.861 INFO     lxc_seccomp - seccomp.c:parse_config_v2:449 - Adding compat rule for init_module action 327681
            lxc<PHONE_NUMBER>2232.861 INFO     lxc_seccomp - seccomp.c:parse_config_v2:342 - processing: .finit_module errno 1.
            lxc<PHONE_NUMBER>2232.861 INFO     lxc_seccomp - seccomp.c:parse_config_v2:446 - Adding native rule for finit_module action 327681
            lxc<PHONE_NUMBER>2232.861 INFO     lxc_seccomp - seccomp.c:parse_config_v2:449 - Adding compat rule for finit_module action 327681
            lxc<PHONE_NUMBER>2232.861 INFO     lxc_seccomp - seccomp.c:parse_config_v2:342 - processing: .delete_module errno 1.
            lxc<PHONE_NUMBER>2232.861 INFO     lxc_seccomp - seccomp.c:parse_config_v2:446 - Adding native rule for delete_module action 327681
            lxc<PHONE_NUMBER>2232.861 INFO     lxc_seccomp - seccomp.c:parse_config_v2:449 - Adding compat rule for delete_module action 327681
            lxc<PHONE_NUMBER>2232.861 INFO     lxc_seccomp - seccomp.c:parse_config_v2:456 - Merging in the compat seccomp ctx into the main one
            lxc<PHONE_NUMBER>2232.861 INFO     lxc_conf - conf.c:run_script_argv:367 - Executing script '/usr/bin/lxd callhook /var/lib/lxd 22 start' for container 'container6', config section 'lxc'
            lxc<PHONE_NUMBER>2232.861 INFO     lxc_start - start.c:lxc_check_inherited:251 - closed inherited fd 3
            lxc<PHONE_NUMBER>2232.861 INFO     lxc_start - start.c:lxc_check_inherited:251 - closed inherited fd 8
            lxc<PHONE_NUMBER>2232.862 INFO     lxc_monitor - monitor.c:lxc_monitor_sock_name:178 - using monitor sock name lxc/d78a9d7e97b4b375//var/lib/lxd/containers
            lxc<PHONE_NUMBER>2232.871 DEBUG    lxc_start - start.c:setup_signal_fd:289 - sigchild handler set
            lxc<PHONE_NUMBER>2232.872 DEBUG    lxc_console - console.c:lxc_console_peer_default:473 - no console peer
            lxc<PHONE_NUMBER>2232.872 INFO     lxc_start - start.c:lxc_init:488 - 'container6' is initialized
            lxc<PHONE_NUMBER>2232.872 DEBUG    lxc_start - start.c:__lxc_start:1259 - Not dropping cap_sys_boot or watching utmp
            lxc<PHONE_NUMBER>2232.875 DEBUG    lxc_conf - conf.c:instantiate_veth:2609 - instantiated veth 'vethC4AF26/vethSAJ21Q', index is '156'
            lxc<PHONE_NUMBER>2232.878 DEBUG    lxc_conf - conf.c:instantiate_veth:2609 - instantiated veth 'vethCLKMBQ/vethSOJXQF', index is '158'
            lxc<PHONE_NUMBER>2232.882 DEBUG    lxc_conf - conf.c:instantiate_veth:2609 - instantiated veth 'veth75MSAD/vethC0AY30', index is '160'
            lxc<PHONE_NUMBER>2232.882 INFO     lxc_cgroup - cgroup.c:cgroup_init:65 - cgroup driver cgroupfs initing for container6
            lxc<PHONE_NUMBER>2232.884 DEBUG    lxc_cgfs - cgfs.c:do_setup_cgroup_limits:1999 - cgroup 'devices.deny' set to 'a'
            lxc<PHONE_NUMBER>2232.884 DEBUG    lxc_cgfs - cgfs.c:do_setup_cgroup_limits:1999 - cgroup 'devices.allow' set to 'c *:* m'
            lxc<PHONE_NUMBER>2232.884 DEBUG    lxc_cgfs - cgfs.c:do_setup_cgroup_limits:1999 - cgroup 'devices.allow' set to 'b *:* m'
            lxc<PHONE_NUMBER>2232.884 DEBUG    lxc_cgfs - cgfs.c:do_setup_cgroup_limits:1999 - cgroup 'devices.allow' set to 'c 5:0 rwm'
            lxc<PHONE_NUMBER>2232.884 DEBUG    lxc_cgfs - cgfs.c:do_setup_cgroup_limits:1999 - cgroup 'devices.allow' set to 'c 5:1 rwm'
            lxc<PHONE_NUMBER>2232.884 DEBUG    lxc_cgfs - cgfs.c:do_setup_cgroup_limits:1999 - cgroup 'devices.allow' set to 'c 1:5 rwm'
            lxc<PHONE_NUMBER>2232.884 DEBUG    lxc_cgfs - cgfs.c:do_setup_cgroup_limits:1999 - cgroup 'devices.allow' set to 'c 1:7 rwm'
            lxc<PHONE_NUMBER>2232.884 DEBUG    lxc_cgfs - cgfs.c:do_setup_cgroup_limits:1999 - cgroup 'devices.allow' set to 'c 1:3 rwm'
            lxc<PHONE_NUMBER>2232.884 DEBUG    lxc_cgfs - cgfs.c:do_setup_cgroup_limits:1999 - cgroup 'devices.allow' set to 'c 1:8 rwm'
            lxc<PHONE_NUMBER>2232.884 DEBUG    lxc_cgfs - cgfs.c:do_setup_cgroup_limits:1999 - cgroup 'devices.allow' set to 'c 1:9 rwm'
            lxc<PHONE_NUMBER>2232.884 DEBUG    lxc_cgfs - cgfs.c:do_setup_cgroup_limits:1999 - cgroup 'devices.allow' set to 'c 5:2 rwm'
            lxc<PHONE_NUMBER>2232.884 DEBUG    lxc_cgfs - cgfs.c:do_setup_cgroup_limits:1999 - cgroup 'devices.allow' set to 'c 136:* rwm'
            lxc<PHONE_NUMBER>2232.884 DEBUG    lxc_cgfs - cgfs.c:do_setup_cgroup_limits:1999 - cgroup 'memory.limit_in_bytes' set to '3221225472'
            lxc<PHONE_NUMBER>2232.884 INFO     lxc_cgfs - cgfs.c:do_setup_cgroup_limits:2003 - cgroup has been setup
            lxc<PHONE_NUMBER>2232.913 DEBUG    lxc_conf - conf.c:lxc_assign_network:3043 - move 'eth3' to '2898114'
            lxc<PHONE_NUMBER>2232.945 DEBUG    lxc_conf - conf.c:lxc_assign_network:3043 - move 'eth4' to '2898114'
            lxc<PHONE_NUMBER>2232.977 DEBUG    lxc_conf - conf.c:lxc_assign_network:3043 - move 'eth5' to '2898114'
            lxc<PHONE_NUMBER>2232.978 DEBUG    lxc_conf - conf.c:setup_rootfs:1210 - mounted '/var/lib/lxd/containers/container6/rootfs' on '/usr/lib/x86_64-linux-gnu/lxc'
            lxc<PHONE_NUMBER>2232.978 INFO     lxc_conf - conf.c:setup_utsname:842 - 'container6' hostname has been setup
            lxc<PHONE_NUMBER>2232.997 DEBUG    lxc_conf - conf.c:setup_hw_addr:2140 - mac address '00:16:3e:8a:67:be' on 'eth3' has been setup
            lxc<PHONE_NUMBER>2232.997 DEBUG    lxc_conf - conf.c:setup_netdev:2367 - 'eth3' has been setup
            lxc<PHONE_NUMBER>2233.017 DEBUG    lxc_conf - conf.c:setup_hw_addr:2140 - mac address '00:16:3e:28:54:12' on 'eth4' has been setup
            lxc<PHONE_NUMBER>2233.017 DEBUG    lxc_conf - conf.c:setup_netdev:2367 - 'eth4' has been setup
            lxc<PHONE_NUMBER>2233.037 DEBUG    lxc_conf - conf.c:setup_hw_addr:2140 - mac address '00:16:3e:1f:33:05' on 'eth5' has been setup
            lxc<PHONE_NUMBER>2233.037 DEBUG    lxc_conf - conf.c:setup_netdev:2367 - 'eth5' has been setup
            lxc<PHONE_NUMBER>2233.037 INFO     lxc_conf - conf.c:setup_network:2388 - network has been setup
            lxc<PHONE_NUMBER>2233.037 INFO     lxc_conf - conf.c:mount_autodev:1071 - Mounting container /dev
            lxc<PHONE_NUMBER>2233.041 INFO     lxc_conf - conf.c:mount_autodev:1094 - Mounted tmpfs onto /usr/lib/x86_64-linux-gnu/lxc/dev
            lxc<PHONE_NUMBER>2233.041 INFO     lxc_conf - conf.c:mount_autodev:1112 - Mounted container /dev
            lxc<PHONE_NUMBER>2233.042 DEBUG    lxc_conf - conf.c:mount_entry:1703 - mounted 'mqueue' on '/usr/lib/x86_64-linux-gnu/lxc/dev/mqueue', type 'mqueue'
            lxc<PHONE_NUMBER>2233.042 DEBUG    lxc_conf - conf.c:mount_entry:1653 - remounting /proc/sys/fs/binfmt_misc on /usr/lib/x86_64-linux-gnu/lxc/proc/sys/fs/binfmt_misc to respect bind or remount options
            lxc<PHONE_NUMBER>2233.042 DEBUG    lxc_conf - conf.c:mount_entry:1668 - (at remount) flags for /proc/sys/fs/binfmt_misc was 4096, required extra flags are 0
            lxc<PHONE_NUMBER>2233.042 DEBUG    lxc_conf - conf.c:mount_entry:1677 - mountflags already was 4096, skipping remount
            lxc<PHONE_NUMBER>2233.042 DEBUG    lxc_conf - conf.c:mount_entry:1703 - mounted '/proc/sys/fs/binfmt_misc' on '/usr/lib/x86_64-linux-gnu/lxc/proc/sys/fs/binfmt_misc', type 'none'
            lxc<PHONE_NUMBER>2233.042 DEBUG    lxc_conf - conf.c:mount_entry:1653 - remounting /sys/firmware/efi/efivars on /usr/lib/x86_64-linux-gnu/lxc/sys/firmware/efi/efivars to respect bind or remount options
            lxc<PHONE_NUMBER>2233.042 DEBUG    lxc_conf - conf.c:mount_entry:1668 - (at remount) flags for /sys/firmware/efi/efivars was 4110, required extra flags are 14
            lxc<PHONE_NUMBER>2233.042 DEBUG    lxc_conf - conf.c:mount_entry:1703 - mounted '/sys/firmware/efi/efivars' on '/usr/lib/x86_64-linux-gnu/lxc/sys/firmware/efi/efivars', type 'none'
            lxc<PHONE_NUMBER>2233.042 DEBUG    lxc_conf - conf.c:mount_entry:1653 - remounting /sys/fs/fuse/connections on /usr/lib/x86_64-linux-gnu/lxc/sys/fs/fuse/connections to respect bind or remount options
            lxc<PHONE_NUMBER>2233.042 DEBUG    lxc_conf - conf.c:mount_entry:1668 - (at remount) flags for /sys/fs/fuse/connections was 4096, required extra flags are 0
            lxc<PHONE_NUMBER>2233.042 DEBUG    lxc_conf - conf.c:mount_entry:1677 - mountflags already was 4096, skipping remount
            lxc<PHONE_NUMBER>2233.042 DEBUG    lxc_conf - conf.c:mount_entry:1703 - mounted '/sys/fs/fuse/connections' on '/usr/lib/x86_64-linux-gnu/lxc/sys/fs/fuse/connections', type 'none'
            lxc<PHONE_NUMBER>2233.042 DEBUG    lxc_conf - conf.c:mount_entry:1653 - remounting /sys/fs/pstore on /usr/lib/x86_64-linux-gnu/lxc/sys/fs/pstore to respect bind or remount options
            lxc<PHONE_NUMBER>2233.042 DEBUG    lxc_conf - conf.c:mount_entry:1668 - (at remount) flags for /sys/fs/pstore was 4110, required extra flags are 14
            lxc<PHONE_NUMBER>2233.042 DEBUG    lxc_conf - conf.c:mount_entry:1703 - mounted '/sys/fs/pstore' on '/usr/lib/x86_64-linux-gnu/lxc/sys/fs/pstore', type 'none'
            lxc<PHONE_NUMBER>2233.042 DEBUG    lxc_conf - conf.c:mount_entry:1653 - remounting /sys/kernel/debug on /usr/lib/x86_64-linux-gnu/lxc/sys/kernel/debug to respect bind or remount options
            lxc<PHONE_NUMBER>2233.042 DEBUG    lxc_conf - conf.c:mount_entry:1668 - (at remount) flags for /sys/kernel/debug was 4096, required extra flags are 0
            lxc<PHONE_NUMBER>2233.042 DEBUG    lxc_conf - conf.c:mount_entry:1677 - mountflags already was 4096, skipping remount
            lxc<PHONE_NUMBER>2233.042 DEBUG    lxc_conf - conf.c:mount_entry:1703 - mounted '/sys/kernel/debug' on '/usr/lib/x86_64-linux-gnu/lxc/sys/kernel/debug', type 'none'
            lxc<PHONE_NUMBER>2233.042 DEBUG    lxc_conf - conf.c:mount_entry:1653 - remounting /sys/kernel/security on /usr/lib/x86_64-linux-gnu/lxc/sys/kernel/security to respect bind or remount options
            lxc<PHONE_NUMBER>2233.042 DEBUG    lxc_conf - conf.c:mount_entry:1668 - (at remount) flags for /sys/kernel/security was 4110, required extra flags are 14
            lxc<PHONE_NUMBER>2233.042 DEBUG    lxc_conf - conf.c:mount_entry:1703 - mounted '/sys/kernel/security' on '/usr/lib/x86_64-linux-gnu/lxc/sys/kernel/security', type 'none'
            lxc<PHONE_NUMBER>2233.042 DEBUG    lxc_conf - conf.c:mount_entry:1653 - remounting /var/lib/lxd/devlxd on /usr/lib/x86_64-linux-gnu/lxc/dev/lxd to respect bind or remount options
            lxc<PHONE_NUMBER>2233.042 DEBUG    lxc_conf - conf.c:mount_entry:1668 - (at remount) flags for /var/lib/lxd/devlxd was 3072, required extra flags are 0
            lxc<PHONE_NUMBER>2233.042 DEBUG    lxc_conf - conf.c:mount_entry:1677 - mountflags already was 4096, skipping remount
            lxc<PHONE_NUMBER>2233.042 DEBUG    lxc_conf - conf.c:mount_entry:1703 - mounted '/var/lib/lxd/devlxd' on '/usr/lib/x86_64-linux-gnu/lxc/dev/lxd', type 'none'
            lxc<PHONE_NUMBER>2233.042 DEBUG    lxc_conf - conf.c:mount_entry:1653 - remounting /var/lib/lxd/shmounts/container6 on /usr/lib/x86_64-linux-gnu/lxc/dev/.lxd-mounts to respect bind or remount options
            lxc<PHONE_NUMBER>2233.043 DEBUG    lxc_conf - conf.c:mount_entry:1668 - (at remount) flags for /var/lib/lxd/shmounts/container6 was 3072, required extra flags are 0
            lxc<PHONE_NUMBER>2233.043 DEBUG    lxc_conf - conf.c:mount_entry:1677 - mountflags already was 4096, skipping remount
            lxc<PHONE_NUMBER>2233.043 DEBUG    lxc_conf - conf.c:mount_entry:1703 - mounted '/var/lib/lxd/shmounts/container6' on '/usr/lib/x86_64-linux-gnu/lxc/dev/.lxd-mounts', type 'none'
            lxc<PHONE_NUMBER>2233.043 INFO     lxc_conf - conf.c:mount_file_entries:1922 - mount points have been setup
            lxc<PHONE_NUMBER>2233.043 INFO     lxc_conf - conf.c:run_script_argv:367 - Executing script '/usr/share/lxcfs/lxc.mount.hook' for container 'container6', config section 'lxc'
            lxc<PHONE_NUMBER>2233.072 INFO     lxc_conf - conf.c:fill_autodev:1140 - Creating initial consoles under container /dev
            lxc<PHONE_NUMBER>2233.072 INFO     lxc_conf - conf.c:fill_autodev:1151 - Populating container /dev
            lxc<PHONE_NUMBER>2233.072 INFO     lxc_conf - conf.c:fill_autodev:1184 - Populated container /dev
            lxc<PHONE_NUMBER>2233.072 INFO     lxc_conf - conf.c:setup_dev_console:1433 - console has been setup
            lxc<PHONE_NUMBER>2233.072 INFO     lxc_utils - utils.c:mount_proc_if_needed:1725 - I am 1, /proc/self points to '1'
            lxc<PHONE_NUMBER>2233.085 DEBUG    lxc_conf - conf.c:setup_rootfs_pivot_root:1049 - pivot_root syscall to '/usr/lib/x86_64-linux-gnu/lxc' successful
            lxc<PHONE_NUMBER>2233.086 INFO     lxc_conf - conf.c:setup_tty:994 - 0 tty(s) has been setup
            lxc<PHONE_NUMBER>2233.086 INFO     lxc_conf - conf.c:setup_personality:1388 - set personality to '0x0'
            lxc<PHONE_NUMBER>2233.086 DEBUG    lxc_conf - conf.c:setup_caps:2051 - drop capability 'mac_admin' (33)
            lxc<PHONE_NUMBER>2233.086 DEBUG    lxc_conf - conf.c:setup_caps:2051 - drop capability 'mac_override' (32)
            lxc<PHONE_NUMBER>2233.086 DEBUG    lxc_conf - conf.c:setup_caps:2051 - drop capability 'sys_time' (25)
            lxc<PHONE_NUMBER>2233.086 DEBUG    lxc_conf - conf.c:setup_caps:2051 - drop capability 'sys_module' (16)
            lxc<PHONE_NUMBER>2233.086 DEBUG    lxc_conf - conf.c:setup_caps:2060 - capabilities have been setup
            lxc<PHONE_NUMBER>2233.086 NOTICE   lxc_conf - conf.c:lxc_setup:3832 - 'container6' is setup.
            lxc<PHONE_NUMBER>2233.086 DEBUG    lxc_cgfs - cgfs.c:do_setup_cgroup_limits:1999 - cgroup 'devices.deny' set to 'a'
            lxc<PHONE_NUMBER>2233.086 DEBUG    lxc_cgfs - cgfs.c:do_setup_cgroup_limits:1999 - cgroup 'devices.allow' set to 'c *:* m'
            lxc<PHONE_NUMBER>2233.086 DEBUG    lxc_cgfs - cgfs.c:do_setup_cgroup_limits:1999 - cgroup 'devices.allow' set to 'b *:* m'
            lxc<PHONE_NUMBER>2233.086 DEBUG    lxc_cgfs - cgfs.c:do_setup_cgroup_limits:1999 - cgroup 'devices.allow' set to 'c 5:0 rwm'
            lxc<PHONE_NUMBER>2233.086 DEBUG    lxc_cgfs - cgfs.c:do_setup_cgroup_limits:1999 - cgroup 'devices.allow' set to 'c 5:1 rwm'
            lxc<PHONE_NUMBER>2233.086 DEBUG    lxc_cgfs - cgfs.c:do_setup_cgroup_limits:1999 - cgroup 'devices.allow' set to 'c 1:5 rwm'
            lxc<PHONE_NUMBER>2233.086 DEBUG    lxc_cgfs - cgfs.c:do_setup_cgroup_limits:1999 - cgroup 'devices.allow' set to 'c 1:7 rwm'
            lxc<PHONE_NUMBER>2233.086 DEBUG    lxc_cgfs - cgfs.c:do_setup_cgroup_limits:1999 - cgroup 'devices.allow' set to 'c 1:3 rwm'
            lxc<PHONE_NUMBER>2233.086 DEBUG    lxc_cgfs - cgfs.c:do_setup_cgroup_limits:1999 - cgroup 'devices.allow' set to 'c 1:8 rwm'
            lxc<PHONE_NUMBER>2233.086 DEBUG    lxc_cgfs - cgfs.c:do_setup_cgroup_limits:1999 - cgroup 'devices.allow' set to 'c 1:9 rwm'
            lxc<PHONE_NUMBER>2233.086 DEBUG    lxc_cgfs - cgfs.c:do_setup_cgroup_limits:1999 - cgroup 'devices.allow' set to 'c 5:2 rwm'
            lxc<PHONE_NUMBER>2233.086 DEBUG    lxc_cgfs - cgfs.c:do_setup_cgroup_limits:1999 - cgroup 'devices.allow' set to 'c 136:* rwm'
            lxc<PHONE_NUMBER>2233.086 DEBUG    lxc_cgfs - cgfs.c:do_setup_cgroup_limits:1999 - cgroup 'memory.limit_in_bytes' set to '3221225472'
            lxc<PHONE_NUMBER>2233.086 INFO     lxc_cgfs - cgfs.c:do_setup_cgroup_limits:2003 - cgroup has been setup
            lxc<PHONE_NUMBER>2233.086 INFO     lxc_apparmor - lsm/apparmor.c:apparmor_process_label_set:229 - apparmor profile unchanged
            lxc<PHONE_NUMBER>2233.086 NOTICE   lxc_start - start.c:start:1368 - exec'ing '/sbin/init'
            lxc<PHONE_NUMBER>2233.089 NOTICE   lxc_start - start.c:post_start:1379 - '/sbin/init' started with pid '2898114'
            lxc<PHONE_NUMBER>2233.089 WARN     lxc_start - start.c:signal_handler:337 - invalid pid for SIGCHLD
            lxc<PHONE_NUMBER>2233.089 DEBUG    lxc_commands - commands.c:lxc_cmd_handler:893 - peer has disconnected
            lxc<PHONE_NUMBER>2233.089 DEBUG    lxc_commands - commands.c:lxc_cmd_handler:893 - peer has disconnected
            lxc<PHONE_NUMBER>2233.089 DEBUG    lxc_commands - commands.c:lxc_cmd_handler:893 - peer has disconnected
            lxc<PHONE_NUMBER>2233.089 DEBUG    lxc_commands - commands.c:lxc_cmd_handler:893 - peer has disconnected
            lxc<PHONE_NUMBER>2233.089 DEBUG    lxc_commands - commands.c:lxc_cmd_handler:893 - peer has disconnected

[x] main daemon log (/var/log/lxd.log)

t=2016-03-04T16:25:31+0100 lvl=info msg=handling url=/1.0/operations/ef663f9b-4c51-4484-9220-9e6c089f0a76/wait ip=@ method=GET
t=2016-03-04T16:25:35+0100 lvl=info msg=handling method=GET url=/1.0 ip=@
t=2016-03-04T16:25:35+0100 lvl=info msg=handling url=/1.0/profiles/container6 ip=@ method=GET
t=2016-03-04T16:27:33+0100 lvl=info msg=handling method=GET url=/1.0 ip=@
t=2016-03-04T16:27:33+0100 lvl=info msg=handling method=POST url=/1.0/containers/container6/exec ip=@
t=2016-03-04T16:27:33+0100 lvl=info msg=handling method=GET url="/1.0/operations/cb7775ae-fa28-4783-b8a7-fc9524671be5/websocket?secret=7ac92da4ae478b9513370703ecb49d1b98582f82a6238bd9bbf8ac8f01eff9ce" ip=@
t=2016-03-04T16:27:33+0100 lvl=info msg=handling ip=@ method=GET url="/1.0/operations/cb7775ae-fa28-4783-b8a7-fc9524671be5/websocket?secret=9fa1960675d059d9a3e9f14f01c364daf1baa957784bed3bc986269883616bda"
t=2016-03-04T16:30:13+0100 lvl=info msg=handling url=/1.0/operations/cb7775ae-fa28-4783-b8a7-fc9524671be5/wait ip=@ method=GET
t=2016-03-04T16:30:15+0100 lvl=info msg=handling method=GET url=/1.0 ip=@
t=2016-03-04T16:30:15+0100 lvl=info msg=handling method=GET url=/1.0/profiles/container6 ip=@

[x] output of the client with --debug

DBUG[03-04|16:33:48] Raw response: {"type":"sync","status":"Success","status_code":200,"metadata":{"api_extensions":[],"api_status":"development","api_version":"1.0","auth":"trusted","config":{"images.remote_cache_expiry":"1","storage.lvm_thinpool_name":"LXDPool","storage.lvm_vg_name":"vg-system"},"environment":{"addresses":[],"architectures":["x86_64","i686"],"certificate":"-----BEGIN CERTIFICATE-----\nMIIFYDCCA0qgAwIBAgIQeTuUeUIurPafSmoJzmKVdDALBgkqhkiG9w0BAQswHjEc\nMBoGA1UEChMTbGludXhjb250YWluZXJzLm9yZzAeFw0xNTA3MTkxNjQzMjZaFw0y\nNTA3MTYxNjQzMjZaMB4xHDAaBgNVBAoTE2xpbnV4Y29udGFpbmVycy5vcmcwggIi\nMA0GCSqGSIb3DQEBAQUAA4ICDwAwggIKAoICAQCorRjEM6cmOakwCqUuU728GYoI\nBE2qFpXfNe/k0smZa/JxoJ4in+tKgUeJ7p6ER8Ofv66i/UvW+pg6MGOgY6yKPsiw\n1Vtht/mqmF12EF0p1XPRr09kOIxwz9bP8Xp07ZsZ0MkwChyqFOR5KZ5IUlPVAi78\nH5yt6Nb3RAp09MV1hoA1QO8mLvzrUsMa5veIAkesQ/BrkDQARnYQHvdKGiTeWRS3\nef3kBJuMOPuyBaxfe/SJT9rqlOkHFLpmsc73PO3IzdTrLQaiMUDygXFTnvFmMxlR\ngKjtJIGYKXMlh7OqnfI8gDJpPqAt7zYSr8y2bmGeOU63mMv6HKurYEvV2WPipM2z\nUDTG3AulB1JMVIpAYEFgr/A0NyQskmtrKP6dRuRJDpnE25clAJ3/kthD5ic8m3FR\nkodeIxgITGhiJZlGtUK3V6ZqGPZ6GO325JrQmj+K1jXXx3JMRykbHpotc3/tcG35\nb76rQSo0aCKXLpR2rNOdzB2D92MryQmGWhZUnmwgUN7eBgyMYd/RJ8Qi4KNEbMDX\nm14tuoGL1WcyECaUnQJ1EPUQYXxggmDpZEZF/D2+iRSJfQva3alwIBFpCp/Bh8Yi\n69UeONO0h8d7JI5nPLJQgGhgM4LDChNPwuYMN+z7IMbCqGhJohLa29dxObUlvDYF\nNScs4R2YKlhm0SGeJQIDAQABo4GdMIGaMA4GA1UdDwEB/wQEAwIAoDATBgNVHSUE\nDDAKBggrBgEFBQcDATAMBgNVHRMBAf8EAjAAMGUGA1UdEQReMFyCBGhzMDKCDjUu\nMjAwLjI1Ljk5LzI4ghpmZTgwOjplYzQ6N2FmZjpmZTY5OjFmOC82NIILMTAuMC4z\nLjEvMjSCG2ZlODA6OmIwNGE6NzhmZjpmZTk2OmJlYS82NDALBgkqhkiG9w0BAQsD\nggIBAA3iqt356XG0V5SggO8OrFb4ZsNmu/C+PNdEB0OShI5mMnM9/ptF+nD7e8zA\nxZniaR/hFekXSqq0Yb0P0Y2WGby14KPXhmsD5M8UHxqr3kv8pV0ADZWSUMrly25S\noOr/cCnVJPGS7m5OdztknWrEXE2lGbEtqjuTJErNQH2gilD0lamrFhQ1v1ynchc2\nLgDtstcujtkh77kAtLq+tARbzMXRaPNNCOpnvXhyz0y+cJdwxgsgWW5PmA179ZY2\nwWdb8Cbqox9Nf7957Xy151qAnRFqb9rVqaEsQPPMZ1FS33bEElSkwbFyt0htFnRp\nRsFR9MyRdE/kdVhOMy542c80ChX32H6LhhjS4RXOw4XrpA2a5Z2m49Vie3GqRtdx\nmk8VprlTTpc+TKi34cA1NI5HC5if6GlSiE7AeABf+/kNeywsAlXcKkbBUwvM/yDW\n1xhcQlRpb2c4iuPB3ZmMzgAei2460RPeNIuW+6J6XSni8VprXfZyK7jUmYoA+VJo\ncXKMe2W24zQtYa2JAhNZ+Hb6hJ6Wu+Y9piFyLWL5Anf+pTebwmj4N+KEMrHmfV/3\n2MSJ5EIHH4XBgpHSGtbiGFXF8Tsul1OLoa5dPtc9lv9WqIYsFu0v8RF0TG7V/aN6\nu0UcOITXdBh4n5tdO3QamtNq3FDVIAA178IkDt0P5s3BC3pc\n-----END CERTIFICATE-----\n","driver":"lxc","driver_version":"2.0.0.rc5","kernel":"Linux","kernel_architecture":"x86_64","kernel_version":"3.19.0-51-generic","server":"lxd","server_pid":23382,"server_version":"2.0.0.beta4","storage":"lvm","storage_version":"2.02.111(2) (2014-09-01) / 1.02.90 (2014-09-01) / 4.29.0"},"public":false}}

DBUG[03-04|16:33:48] Raw response: {"type":"sync","status":"Success","status_code":200,"metadata":{"architecture":"x86_64","config":{"volatile.base_image":"22eb31d72f62e9e37c7ea12d0259e2f8f80ae56a8e3756dc484b0bf2d3896a36","volatile.eth0.hwaddr":"00:16:3e:8a:67:be","volatile.eth0.name":"eth3","volatile.eth1.hwaddr":"00:16:3e:28:54:12","volatile.eth1.name":"eth4","volatile.eth2.hwaddr":"00:16:3e:1f:33:05","volatile.eth2.name":"eth5","volatile.last_state.idmap":"[]","volatile.lo.hwaddr":"00:16:3e:29:d3:b5","volatile.lo.name":"eth0"},"created_at":"1970-01-01T00:00:00Z","devices":{"root":{"path":"/","type":"disk"}},"ephemeral":false,"expanded_config":{"boot.autostart":"true","limits.cpu":"3","limits.memory":"3072MB","raw.lxc":"lxc.aa_profile=unconfined","security.privileged":"true","volatile.base_image":"22eb31d72f62e9e37c7ea12d0259e2f8f80ae56a8e3756dc484b0bf2d3896a36","volatile.eth0.hwaddr":"00:16:3e:8a:67:be","volatile.eth0.name":"eth3","volatile.eth1.hwaddr":"00:16:3e:28:54:12","volatile.eth1.name":"eth4","volatile.eth2.hwaddr":"00:16:3e:1f:33:05","volatile.eth2.name":"eth5","volatile.last_state.idmap":"[]","volatile.lo.hwaddr":"00:16:3e:29:d3:b5","volatile.lo.name":"eth0"},"expanded_devices":{"eth0":{"nictype":"bridged","parent":"lxcbr0","type":"nic"},"eth1":{"nictype":"bridged","parent":"br0.114","type":"nic"},"eth2":{"nictype":"bridged","parent":"br0","type":"nic"},"root":{"path":"/","type":"disk"}},"name":"container6","profiles":["container6"],"stateful":false,"status":"Stopped","status_code":102}}

DBUG[03-04|16:33:48] Putting {"action":"start","force":false,"stateful":false,"timeout":-1}
 to http://unix.socket/1.0/containers/container6/state
DBUG[03-04|16:33:48] Raw response: {"type":"async","status":"Operation created","status_code":100,"metadata":{"id":"cd61186f-58ee-45b0-a73f-d87b084988c1","class":"task","created_at":"2016-03-04T16:33:48.587205242+01:00","updated_at":"2016-03-04T16:33:48.587205242+01:00","status":"Running","status_code":103,"resources":{"containers":["/1.0/containers/container6"]},"metadata":null,"may_cancel":false,"err":""},"operation":"/1.0/operations/cd61186f-58ee-45b0-a73f-d87b084988c1"}

DBUG[03-04|16:33:48] 1.0/operations/cd61186f-58ee-45b0-a73f-d87b084988c1/wait
DBUG[03-04|16:33:48] Raw response: {"type":"sync","status":"Success","status_code":200,"metadata":{"id":"cd61186f-58ee-45b0-a73f-d87b084988c1","class":"task","created_at":"2016-03-04T16:33:48.587205242+01:00","updated_at":"2016-03-04T16:33:48.587205242+01:00","status":"Success","status_code":200,"resources":{"containers":["/1.0/containers/container6"]},"metadata":null,"may_cancel":false,"err":""}}

[ ] output of the daemon with --debug

I believe this is an unfortunate side effect of a change meant to make such things more reliable in the future.
Back in LXD 0.19, the actual order of the interfaces was determining their name, which on occasion would mean two would get swapped and users would get very confused.
To fix that, I introduced interface name tracking, working in much the same way the hwaddr record works. I believe it is this code that's getting confused when it first runs after upgrade and sees running containers without a recorded interface name, it then figures out a name to use for the interface but since the container is running, it skips all the existing ones and picks the next one, causing this issue.
There is unfortunately no way for us to fix this retro-actively as once a new name is recorded we can't know if it's set to its current value by mistake or not...
To fix your setup, you have two solutions:

Stop the container, run "lxc config edit NAME" and remove all the volatile.INT.name keys (but not the hwaddr one), then start the container again, it should get back to the right device names and record those so that they don't change again
If you expect the interface name to be consistent across all containers using the same profile, then you can set the "name" property for the nic entry in your profile, LXD will then use that over whatever it thinks should be the right name.

Hi Stéphane,
Awesome. Thanks for the quick reply (I didn't expect one before the weekend)!.
I can conform that setting the name property fixes my setup.
Have a good weekend.


GH-45039: [CI][Packaging][Python] Fix Docker push step for free-threaded wheel builds

GitHub Issue: #45039

@github-actions crossbow submit wheel-manylinux-2-28-cp313-cp313-amd64 wheel-manylinux-2-28-cp313-cp313t-amd64

@kou @raulcd Does this seem ok?

@github-actions crossbow submit wheelmanylinux


Roll Flutter Engine from 5b3bf9a950b2 to 8fbcb51531a2 (1 revision)

https://github.com/flutter/engine/compare/5b3bf9a950b2...8fbcb51531a2
2024-05-17<EMAIL_ADDRESS>Roll Skia from 6f7cb3d360b7 to 3f4c5038da37 (1 revision) (flutter/engine#52907)
If this roll has caused a breakage, revert this CL and stop the roller
using the controls here:
https://autoroll.skia.org/r/flutter-engine-flutter-autoroll
Please CC bdero@google.com,rmistry<EMAIL_ADDRESS>on the revert to ensure that a human
is aware of the problem.
To file a bug in Flutter: https://github.com/flutter/flutter/issues/new/choose
To report a problem with the AutoRoller itself, please file a bug:
https://issues.skia.org/issues/new?component=1389291&template=1850622
Documentation for the AutoRoller is here:
https://skia.googlesource.com/buildbot/+doc/main/autoroll/README.md

Commit queue failed; closing this roll.


ZAMN Image Command

zamn

seems good, i might make a couple of changes to make it fit better with the rest of the bot however


Feat/add absolute imports

This PR implements the following feature:

Add path alias base url.
Improve components imports structure from relative paths to absolute paths.

:tada: This PR is included in version 1.10.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


[ADP-3212] Add voting certificates to primitive lib

[x] Add Conway certificates support to primitive lib

ADP-3212
All credits to Pawel

I think the name changes are important in order to reduce cognitive load when comparing the specification to our code.
Other than these changes, I'm happy to approve the pull request. 👍


Hartree fock odd qubits

a. Restricted-Hartree-Fock OPDM analysis and measurement now work for an odd number of qubits (odd number of molecular orbitals).
b. Example attached H3^{+} (sto-3g basis)
Contributors

Sahil Gulania
<EMAIL_ADDRESS>University of Southern California

James Daniel Whitfield
<EMAIL_ADDRESS>Dartmouth College

@googlebot I signed it!

Binary files for H_{3}^{+} (STO-3g) are added in
OpenFermion-Cirq/openfermioncirq/experiments/hfvqe/molecular_data/hydrogen_chains/h_3_p_sto-3g/bond_distance_2.5/
Other than these binary files were not touched.


Sign In Flow

Hello @jumaallan , when a person tries to sign in to the app using their google account the app does not move to the next screen. The facebook option works however. This happens in Android 4.4.2.
Another issue is that the Introductory pages keep showing up even after a person has logged in. Some code updates would be highly appreciated.

@CodeZilla7
Now, the Google Sign In Fails because I deleted the project on Firebase. I reached the free limit, haha. You can however set up using your Firebase Credentials. It should work just fine. The issue with the splash screen showing every time is a shared preference issue. I'll fix that and update the code. But you can also do that if you get time and create a pull request 👍 Cheers

Okay, I will create a new Firebase project and see if I can solve the issues.


Forever formatting loop

Hi! thx for the addon, it's been really useful to me.
However when running on file with hundreds of lines, it stopped working and the showed forever formatting loop.
I've set format on save in atom-ide-ui, so whenever I safe the file, typically it should format on the fly, but after it stopped working, it get all piled up in the task queue and not doing anything.
I'm wondering if this is normal with the python ide server or possible can be handled by the addon. Thx.

I have the same issue on windows, but from what I see not only formating stop working but linter and suggestion too stoped working at some point.
Usually I just restart my editor but it's not great to do it every 5 or 10 saves.
Do you need any help ? Which log can I give you that will help ?

It can be reproduced by constantly saving in a short period(I have formatting on save to True in atom ide ui settings.)
This is lead me to believe it's something to do with task queue issue.

Same here. Happens every couple of saves and requires restart to fix...

I think I found a potential cause.
It's related to hyper link function.
When it's enabled, and you drag across multiple variables, it will stuffed the ide server to death.
Not sure if this is the only cause, but I can trigger the forever loop by clicking this on and off.
I end up using python-tools goto, its not that intuitive, but at least the linter won't crash.

This sounds like pyls is crashing underneath. Which version of pyls are you using?
Could you enable debug messages by executing atom.config.set('core.debugLSP', true) in the Developer Tools Console and post a screenshot of the console output when this issue occurs? You might need to restart Atom in order to see the debug messages.

@lgeiger  Hi! I'm using plys 0.12.1.

And here's the log, it seems to indicate something with ide-css and ide-vue, which I uninstalled. But still popped up.

Thanks for the screenshots! I wonder if the problem is coming from the unicode characters.
Could you provide some example code where formating fails?

Hi! This one is successfully formatted. (which contains non-latin characters.)

But this one failed to format the code, I've been using save to format so I've been hitting ctrl-s several times but nothing happened. But the linting is working though which is weird. I thought LSP should handled all the interfaces at once so if linting is working why won't formatting work?

I thought LSP should handled all the interfaces at once so if linting is working why won't formatting work?

It looks like the formating request was completed but yapf didn't know how to format it. Therefor linting still works.
You can see the requests if you enable debug messages by executing atom.config.set('core.debugLSP', true) in the Developer Tools Console and restarting Atom?

Ah, forgot to turn this on.
So it's throwing error for "rangeFormatting".

Unfortunately the internal error from pyls doesn't show up in the log. Can you post the content of paq-flask/project/common/data.py so I can try and reproduce this error.

@lgeiger  Since it imported some external files and modules, do I have to share those with you too? If so I'm afraid I won't be able to so  since it needs to be approved by peers.
Is that ok I e-mail you just this script?

Is that ok I e-mail you just this script?

I guess for formatting the script should be enough<EMAIL_ADDRESS>

@extraymond You're running into https://github.com/google/yapf/issues/403 since some of your variable names are unicode characters. Unfortunately we cannot do anything about this on the ide-python side.
I also noticed that yapf can take a long time for formating code. That's why there may be multiple formatting requests queued up. For long files I wouldn't recommend format on save.
I don't know if there's a better/faster python code formatter to use but you can open a issue on the python-language-server and suggest optimisations. The problem with this is that long running formatting requests will block linting and other ls features until they resolve due to the implementation in pyls.
That said I think the python-language-server should properly handle the errors instead of throwing a exception. I'm going to open a issue on the pyls repo.

@lgeiger  Thx for sharing this. I'll try replacing vars to be more formal. I'm really thankful for you being both helpful and educational in the end of a year! Wish you a happy holiday.

The latest release supports the autopep8 formatter. This might help with this issue.


ci: bsim-tests: Use zephyr-runner v2

This commit updates the bsim-tests workflow to use the new zephyr-runner v2 CI runner deployment.
It also updates the workflow to use the ci-repo-cache Docker image, which includes the Zephyr repository cache, because the node level repository cache is no longer available in the zephyr-runner v2.

Some BabbleSim tests seem to be unstable and fail intermittently (see https://github.com/zephyrproject-rtos/zephyr/actions/runs/8226719915) on the self-hosted runners with older/slower CPUs. This should be investigated and fixed in a follow-up PR.

Thanks @stephanosio . Overall I don't mind running in one set of machines or another. But two thoughts:

It does not seem too nice that the runtime for that set of tests is increasing quite a lot (from 30min-50m in the current version runners to 55min-1h:15m in this PR runs). The previous runners were already very slow. These new ones would seem to be adding a very long delay to get CI results.
About tests timing out, I'd much rather fix it before changing CI (I just created #70087)

It does not seem too nice that the runtime for that set of tests is increasing quite a lot (from 30min-50m in the current version runners to 55min-1h:15m in this PR runs). The previous runners were already very slow. These new ones would seem to be adding a very long delay to get CI results.

Given that it takes much longer than 1 hour to get PRs reviewed and merged, 1 hour CI run time should be more than reasonable.
When this grows up to be more than just a few hours, the BabbleSim tests should be split into multiple subsets so that they can be simultaneously scheduled onto multiple runners.

Given that it takes much longer than 1 hour to get PRs reviewed and merged, 1 hour CI run time should be more than reasonable.

@stephanosio I'm not going to reject the change due to this. But it makes me uncomfy. Users do sometimes make mistakes, need to push updates, and get CI rerun. That cycle will now be longer.


Enlarge comment text-area on enter

Is there an existing issue for this?

[ ] I have searched the existing issues

Describe the bug
When attempting to submit a new comment in the comments section, pressing the enter key causes a new line to be created instead of posting the comment. If this is the intended user experience, it may be helpful to enlarge the textarea box of that comment so that the user can easily distinguish between creating a new line and submitting a comment.
Steps To Reproduce

Go to any simulator page. For example go here
Write a comment.
Hit Enter key

Expected Behavior
On hitting Enter key, size of textarea should increase. so that user can see all the new lines with previous lines.
Screenshots
You can play the following video to understand the issue.
Video can be found here
Device Information [optional]
No response
Additional context
No response
Are you working on this issue?
No

Can I work on this issue if no one is working on this?

Hey @Sheikh-JamirAlam. Welcome to the CircuitVerse community. you can start working on this issue. If you need any help ping me.

@Waishnav I belive this issue is already taken care on #3521

@Waishnav I belive this issue is already taken care on #3521

thanks for letting me know. I was not aware about this PR.

@Arnabdaz We were thinking about custom size of comment box on adding new line by hitting enter. (basically adding event listner to the textarea and increasing the row number)

@Arnabdaz We were thinking about custom size of comment box on adding new line by hitting enter. (basically adding event listner to the textarea and increasing the row number)

@tachyons WDYT?

@Waishnav well for that I already added that feature while trying to fix the issue i mentioned earlier but as it was assigned to someone I didn't make a pr .. I asked about the feature and the updates  I made in #ux channel on slack but no one replied ... so yah if you would like I can discuss about it.

Can I work on this issue if no one is working on this?


Could you evaluate your best result on the test set with multi reference ground truth?

Currently a small version (d=512) of the model obtains the following scores with multi-reference gt:
BLEU4: 0.392
METEOR: 0.269
ROUGE-L: 0.559
CIDEr: 1.066

Thanks for your reply.
We used the small version (d=512) and got the following scores with single-reference gt which is similar to your paper.
BLEU4: 0.124
METEOR: 0.162
ROUGE-L: 0.352
CIDEr: 1.194
However, we got the following scores with multi-reference gt:
BLEU4: 0.331
METEOR: 0.271
ROUGE-L: 0.551
CIDEr: 1.019
We use the default settings described in your paper. And we use stop words ",", ".". We don't know what leads to this big gap in BLEU-4. Could you help me bring the gap?

I wonder if our evaluation is correct. Could you send us your prediction results OR could you help us evaluate our prediction results?
Email<EMAIL_ADDRESS>Thanks very much.

I dropped you an email @lizekang. I also used stop words "," and "."

Thank you very much!

Hi @lizekang, I have similar problems. Have you found out why?

@ranpox I haven't found out...

Do you know the scores of 6 reference on paper? I did not find it.

The 6-reference ground truth was not available before the paper so the paper result was based on single-reference ground truth.


history stats sensor recording 0 value in history when hass restarts

Home Assistant release (hass --version):
0.63.3
Python release (python3 --version):
Python 3.6.3
Component/platform:
history_stats, history
Description of problem:
Killing and restarting hass results in my history_stats sensor showing a 0 in its history. It quickly recovers after restart, though.
Expected:
The history_stats sensor value should be restored from the database before the history component has a chance to record its value again.
Problem-relevant configuration.yaml entries and steps to reproduce:
sensor:
  - platform: history_stats
    name: treadmill runtime today
    entity_id: binary_sensor.treadmill_desk_active
    state: 'on'
    type: time
    start: '{{ now().replace(hour=0).replace(minute=0).replace(second=0) }}'
    end: '{{ now() }}'

history_graph:
  office_temps:
    hours_to_show: 72
    entities:
      - sensor.treadmill_runtime_today

pkill hass
re-run hass
observe that history graph shows dips to 0 value with each restart

Visual of the issue:

I may take a look if I have some freetime soon.

@bokub Thanks! If there's any additional testing I could do, please let me know.

This is awesome. Thank you @bokub and @pvizeli !


do you plan to support version 1.0 ?

current gem is not compatible with json_api_client version 1.0+

At some point I will work on this, but currently I don't have the time.


adding my animated Button for GSSOC'23

Please review and merge and give tags. Thank you so much

@Spyware007 can you merge my PR please


Refactor Model to MLModel

@pmbrull going to rename existing Model to MLModel as we are planning to add DBT integration where Model is use to create the tables.

Makes sense, thanks for the ping!
also, good news to have DBT as well 🚀


Uncaught TypeError: Cannot read property 'hours' of undefined

Uncaught TypeError: Cannot read property 'hours' of undefined
    at Object.updateSelectedDate (http://localhost:3000/static/js/bundle.js:86604:8)
    at Object.updateSelectedDate (http://localhost:3000/static/js/bundle.js:86925:15)
    at Object.ReactErrorUtils.invokeGuardedCallback (http://localhost:3000/static/js/bundle.js:16912:17)
    at executeDispatch (http://localhost:3000/static/js/bundle.js:16694:22)
    at Object.executeDispatchesInOrder (http://localhost:3000/static/js/bundle.js:16717:6)
    at executeDispatchesAndRelease (http://localhost:3000/static/js/bundle.js:16105:23)
    at executeDispatchesAndReleaseTopLevel (http://localhost:3000/static/js/bundle.js:16116:11)
    at Array.forEach (native)
    at forEachAccumulated (http://localhost:3000/static/js/bundle.js:17015:10)
    at Object.processEventQueue (http://localhost:3000/static/js/bundle.js:16319:8)
updateSelectedDate @ DateTime.js:319
updateSelectedDate @ DaysView.js:115
ReactErrorUtils.invokeGuardedCallback @ ReactErrorUtils.js:70
executeDispatch @ EventPluginUtils.js:85
executeDispatchesInOrder @ EventPluginUtils.js:108
executeDispatchesAndRelease @ EventPluginHub.js:43
executeDispatchesAndReleaseTopLevel @ EventPluginHub.js:54
forEachAccumulated @ forEachAccumulated.js:24
processEventQueue @ EventPluginHub.js:257
runEventQueueInBatch @ ReactEventEmitterMixin.js:17
handleTopLevel @ ReactEventEmitterMixin.js:28
handleTopLevelImpl @ ReactEventListener.js:72
perform @ Transaction.js:140
batchedUpdates @ ReactDefaultBatchingStrategy.js:62
batchedUpdates @ ReactUpdates.js:97
dispatchEvent @ ReactEventListener.js:147

I found this error that happens once in a while while changing the day. It even happens when clicking in the same day.
I am using version 2.8.8

Hi @ferpintado. Can you provide a demo (you can fork this) or a step-by-step guide to recreating this bug? Otherwise it's very hard to find it.

Happens to me when I use render day prop. renderDay={(props, currentDate, selectedDate) => ({currentDate.date()}	)}

Having the same issue with renderDay anytime I wrap the contents of the  rather than just calling the date function:
WORKS:
return (

        {currentDate.date()}

    )

DOESN'T WORK:
return (

        {currentDate.date()}

    )

I have the same behaviour that @larrydahooster. Could we reopen this issue @simeg ?

 Can we reopen this issue?

Hey new version 2.16 is out and it should tackle this kind of errors. Thanks @ferpintado @milasevicius  and @larrydahooster for your date, it made possible the fix.

static formatDuration(durationObj) {
const duration = ${durationObj.hours ? (${durationObj.hours}:) : ''}${       durationObj.minutes ? durationObj.minutes : '00'     }:${       (durationObj.seconds < 10)         ? ('0' + durationObj.seconds)         : (durationObj.seconds         ? durationObj.seconds         : '00')     };
return duration;
}
};
TypeError: Cannot read property 'hours' of undefined
what can I do?


Truble with vuetify v2

Hello
With vuetify v2 theme and font not working. For exemple all color is black. Could fix it?
thank you
PS: sorry for my english

i have the same problem, this is not working with v2 of vuetify

i have the same problem, this is not working with v2 of vuetify


jupyter extensions

Description of changes
Add the following python packages:

jupyter-contrib-core
jupyter-nbextensions-configurator
jupyter-highlight-selected-word
jupyter-contrib-nbextensions

Things done

Built on platform(s)

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

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

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

[x] 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/)
23.11 Release Notes (or backporting 23.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.

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

16 packages built:

python310Packages.jupyter-contrib-core
python310Packages.jupyter-contrib-core.dist
python310Packages.jupyter-contrib-nbextensions
python310Packages.jupyter-contrib-nbextensions.dist
python310Packages.jupyter-highlight-selected-word
python310Packages.jupyter-highlight-selected-word.dist
python310Packages.jupyter-nbextensions-configurator
python310Packages.jupyter-nbextensions-configurator.dist
python311Packages.jupyter-contrib-core
python311Packages.jupyter-contrib-core.dist
python311Packages.jupyter-contrib-nbextensions
python311Packages.jupyter-contrib-nbextensions.dist
python311Packages.jupyter-highlight-selected-word
python311Packages.jupyter-highlight-selected-word.dist
python311Packages.jupyter-nbextensions-configurator
python311Packages.jupyter-nbextensions-configurator.dist

@ofborg build python3Packages.jupyter-contrib-core python3Packages.jupyter-nbextensions-configurator python3Packages.jupyter-highlight-selected-word
python3Packages.jupyter-contrib-nbextensions

btw ofborg will build the packages if you change the commit messages from python3Packages to python310Packages

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

16 packages built:

python310Packages.jupyter-contrib-core
python310Packages.jupyter-contrib-core.dist
python310Packages.jupyter-contrib-nbextensions
python310Packages.jupyter-contrib-nbextensions.dist
python310Packages.jupyter-highlight-selected-word
python310Packages.jupyter-highlight-selected-word.dist
python310Packages.jupyter-nbextensions-configurator
python310Packages.jupyter-nbextensions-configurator.dist
python311Packages.jupyter-contrib-core
python311Packages.jupyter-contrib-core.dist
python311Packages.jupyter-contrib-nbextensions
python311Packages.jupyter-contrib-nbextensions.dist
python311Packages.jupyter-highlight-selected-word
python311Packages.jupyter-highlight-selected-word.dist
python311Packages.jupyter-nbextensions-configurator
python311Packages.jupyter-nbextensions-configurator.dist

@SuperSandro2000 what you want to say is that tests are currently not detected and thus not ran, right ?
Do you want me to create a PR to explicitly set doCheck = false for all of them ?

Then the tests are probably not included in the pypi download. Just fetch from github. If packages have no tests we likely won't notice when they break in a more subtle way because of dependency updates. All the packages that have tests upstream should run them if possible.

Then the tests are probably not included in the pypi download. Just fetch from github. If packages have no tests we likely won't notice when they break in a more subtle way because of dependency updates. All the packages that have tests upstream should run them if possible.

I see, thanks for the clarification.
However in this case, we are using fetchFromGitHub and not fetchPypi.
Do you want have a change in mind for those specific packages ?

If the package has tests and we add pytestCheckHook to nativeBuildInputs, those tests should be run. Otherwise we might need to add the location of the tests to pytestCheckFlags.


Store etag So Downloads Use Cache

Storing Etag received from fetch API parallel to mtime file and passing this header to If-None-Match.
Fixing https://github.com/teaxyz/cli/issues/85

Needs a test

In the end, this was good work, thanks @kunalgoyal9


malformed URL request on ElevationRequest

I set up the ElevationRequest like this
ElevationRequest request = new ElevationRequest()
{
BingMapsKey = Properties.Settings.Default.API_Key,
Points = points,
Height = ElevationType.Ellipsoid
};
upon executing the response is: StatusDescription "Unauthorized"
The GetRequestUrl generated is: https://dev.virtualearth.net/REST/v1/Elevation/List?height=ellipsoid?key=API_Key&points=49,-103
The expected URL should be: https://dev.virtualearth.net/REST/v1/Elevation/List?points=49,-103&height=Ellipsoid&key=API_Key (or similar)

Ditto. The relevant line is at
https://github.com/Microsoft/BingMapsRESTToolkit/blob/05f29a7fcd47f86006b590a70f0782025a09b05e/Source/Requests/ElevationRequest.cs#L242
I tried just changing "height=ellipsoid" to "heights=ellipsoid" and it works as expected


Exporting: In game characters heads show in cutscenes

Game
Resident Evil 5
When importing/exporting any character that appears in a cut-scene, two heads appear: the in-game head and the more detailed/high poly head for cut-scenes. Only the latter should should.
It was observed that this is a setting apparently controlled by' Mod156.group_data_array; every mesh has an index to a member then, in Mesh156.group_index, which could be renamed to 'RenderOptions', probably.

Fixed in Albam Reloaded and backported to Albam.


Fix FileTreeView to handle duplicate paths

Ref https://github.com/sbt/sbt/issues/4650

To validate this pull request against other sbt modules, please visit this link.

Locally verified that shapeless build works.

I copied these commits into #238


Ability to set a custom name without templates restriction

OS: Ubuntu 20.04
Launch command used:
./destreamer.sh --format mp4 -o out -i "my_url" -t "Lesson 5"
Hi there,
I'm not able to set a custom template name like the one above. I must set at least one of the "magic sequences" to make it work.
For example:
"Lesson 5" -> This is not a valid title template. Thus, destreamer refuses to use my custom file name and simply fallbacks to the default one.
"Lesson 5 {author}" -> This one is a valid template. Destreamer accepts my custom title template.
I don't understand this behaviour. Why I can't set a custom name?

This line is the problem. You are looking for at least one match. Otherwise you set manually the default template here

If you send a PR to amend the regex we'd be happy to merge it.

You don't have to modify current regex. We only need to verify that there is a match in order to ensure that all the "magic sequences" are correctly spelled. Code from line #197 to line #201 no longer exists. The key part of the formatting process is here. Already fixed and tested. I'm going to make a pull request.


Enable ssm to send command output to cloudwatch logs

Hi, aws just enabled that ssm to send the output to cloudwatch logs, this diff is to enabled ssm-sh to use this feature, please review.

Thanks for the PR; the feature and code looks great :tada: Bit busy this weekend unfortunately, but will try to make time to review it! One thing - could you vendor the cloudwatch module so we can see if travis turns green?

Hey! Sorry for the radio silence on my end; what is the status of this PR? I'd really like to see this merged, do you think you'll have time finish it?

I'l try to finish this weekend ya.

Ref this commit: https://github.com/itsdalmo/ssm-sh/commit/2a2860692d7ce2680d6ae458a87fd5c37703a9ed
I have updated the terraform example to generate a CloudWatch logs group and grant the instance permissions to write to the log group, but on building the latest commit in your branch and testing the ssm-sh binary I get the following error:
$ ./ssm-sh run command -t <instance-id> -l  ssm-sh-example-output-<account-id> -x -- ls -la

<instance-id> - Success:
can't find log stream with prefix b6be0895-2dbd-430d-9a4f-2147a332bedc/i-00e303a0eba0de85d in ssm-sh-example-output-<account-id> log group

<rest of output>

Perhaps I got the permissions wrong for CloudWatch output? You can see them here:
https://github.com/itsdalmo/ssm-sh/blob/master/terraform/modules/ssm-example/main.tf#L110-L123

Hi
Regarding the diff, this is actually my first time doing PR, thanks for be nice, already fixed it.
Regarding CW Logs stream, my bad, i don't read the error message carefully.
I'm pretty sure, policy you created and attached to ec2 already sufficient.
I found different behaviour when i try this with different AMI, but same policy. I try to apply the terraform and run ssm-sh run command, i found issue like yours. I try to look to error message on instance, and cannot find ssm error logs file on /var/log/amazon/ssm, but when i try to change the AMI on terraform config using AMI (ubuntu), the logstream is created, and  the error log is created. Will continue investigation later.

Great stuff @SiahaanBernard - I'll try to help with figuring out the correct IAM permissions when I have time 👍

Sorry I dropped the ball on this one. I'll close the PR now since it's stale, and also the AWS CLI has session manager baked in.


Crash on load

Description
Crashes on load
Screenshots or Errors
https://pastebin.com/cqgA74y7 (it says it's an older version of Skungee but the same happened on the latest version, I was just checking if it would work with an older version)
Actual Behavior
Expected Behavior
Steps to Reproduce the Problem

Install the jar on the Spigot server
Crashes on load

Specifications
Skungee Version: 16.2
Proxy Platform and Version: Waterfall (1.8.9)
System/Panel (if applicable): -

Skungee 2.0.0 only supports Skript 2.3+ currently.

Fixed in ALPHA-17 https://github.com/Skungee/Skungee-2.0.0/releases/tag/2.0.0-ALPHA-17


Circular type imports for classes throws: TestClass:  This type is incompatible with 'TestClass'

I have an issue with circular type imports.
Given the following two files:
// context.js
/* flow */
import {
  myExecutionHandler
} from './handler';

// The following line throws error: TestContext:  This type is incompatible with 'TestContext'
// This can also not be silenced with $FlowFixMe: It says unused suppression in that case
export class TestContext {
  execute(): void {
    return myExecutionHandler(this); // If this line is removed / changed, the error disappears
  }
}

// handler.js
/* flow */
import type {
  TestContext
} from './context';

export function myExecutionHandler(test: TestContext): void {
  // Do something with TestContext
  console.log(test);
}

If I put all the code in one file, flow does not complain. Am I missing something or are circular imports problematic? The fact that I cannot suppress that error with $FlowFixMe makes me think there is more to the problem. Any suggestions?
I love this library btw! 👍

I am having the same problem.
`// @flow
import Bar from "./Bar";
class Foo {
constructor(){
const bar = new Bar(this);
}
}
export default Foo;`
`//@flow
import Foo from "./Foo";
class Bar {
constructor(foo: Foo){
}
}
export default Bar;
`


Ionic template SPA server not working properly

I'm submitting a...

[x ] Bug report
[ ] Feature request
[ ] Documentation issue or request
Current behavior
If I create a test component (doesn't matter what it does) and add a routing example like below:
const routes: Routes = [
  { path: 'login', component: LoginComponent, data: { title: extract('Login') } },
  { path: 'test/:testId', component: TestComponent, data: { title: extract('Test') } }
];

Going to http://localhost:4200/test/randomId doesn't work. All of the script tags are getting 404 error because its trying to load them from "test" folder - http://prntscr.com/ifskud
However if I load the login component view first and the navigate to test component view, it works fine.
Environment
The issue only appears when working with Ionic generated templates.
{
  "generator-ngx-rocket": {
    "version": "3.2.1",
    "props": {
      "appName": "test5",
      "target": [
        "web",
        "cordova"
      ],
      "pwa": false,
      "mobile": [
        "ios",
        "android"
      ],
      "ui": "ionic",
      "auth": true,
      "projectName": "test-5",
      "packageManager": "npm"
    }
  }
}

Possible solution
I noticed that only Ionic generated templates have this in index.html:
<base href="./"/>

Changing it to this seems to fix the issue
<base href="/"/>

I was just wondering if this change might break something else as if there might be a specific reason Ionic templates use a different base href?

Thanks for reporting the issue.
The <base href="./"/> is not specifically for Ionic, but whenever Cordova target is enabled as it is needed for apps to works with Cordova on iOS 😕
It was a quick workaround but since it causes issues with routing, I have to find something else...

I posted an issue on the related ionic plugin: https://github.com/ionic-team/cordova-plugin-ionic-webview/issues/77

@sinedied , I think this post might be somehow related as they talk about the issues of base href: https://github.com/angular/angular/issues/13948

The only workable fix for this until (if) https://github.com/ionic-team/cordova-plugin-ionic-webview/issues/77 is fixed, is to remove <base href="/"/> completely and switch Angular to legacy hashbang routing instead of HTML5 routing 😞
I'll create a PR to implement this only for cordova-based target, even though I tried to avoid it in first place.

@ALander26 I just tried with the <script>document.write('<script>document.write('<base href="' + document.location + '" />');</script> solution suggested in your linked issue, and the behavior is the same as with <base href="./"/>: it works for Cordova, but not for subroutes unless legacy hashbang routing is enabled.
But on the same idea, I tried:
<script>document.write('<base href="' + (/^localhost:8080/.test(location.host) ? './' : '/') + '" />');</script>

which works as it now uses ./ only for ios (which runs on a local server), but this still feel hack-ish 😕
Cordova apps should not suffer from having a ./ base href as you cannot "F5" them, they will always load from root.

After a bit of research, I just found that angular-cli builds supports the --base-href option to change the <base> tag on build, so I will always set it to / and just use the --base-href="./" option when building for cordova through @ngx-rocket/scripts.
Seems the best way to fix this I think 😄

@sinedied Indeed seems like the best solution. I was already thinking of doing it manually before building.
Thanks for your quick responses!


scalajs support?

any interest in adding scala.js support?

@kailuowang Sorry, this slipped past me.  I'm not against the idea. I currently don't use scala.js, but if you are interested I'm definitely open to PRs.

awesome, just submitted #5

Merged!


Add Indonesian translation for Names

This PR addresses #13929
/language id

@iputra please sign the CLA first

/assign

/retest

@iputra please sign the CLA first

done

Also since the test is still failing, could you please run make docker-serve on your local first? Thanks 🙂

Also since the test is still failing, could you please run make docker-serve on your local first? Thanks

on my local machine it run properly

@iputra seems like it's because of the CLA, will see after the patch is built

@iputra seems like it's because of the glossary https://app.netlify.com/sites/kubernetes-io-master-staging/deploys/5cdb11b2b0619f00099b259d

@iputra seems like it's because of the glossary https://app.netlify.com/sites/kubernetes-io-master-staging/deploys/5cdb11b2b0619f00099b259d

I found the problem, it is because I insert wrong date format in glossary files :sweat_smile:

@iputra after you squash your commits I'll give LGTM

/lgtm
/approve


ARK v0.3.0 Release Plan (Released)

Timeline
Released Date: Oct. 4th, 2023
Work Items
Scheduler

[x] Graph Optimization: enable this feature (#136)

[ ] SimpleScheduler: fix broken features plan changed -- deprecate SimpleScheduler

Communication Stack

[x] Interface: make send/recv interface simpler (#138)

Operators Support

[x] Operator: add more operators (#107)

Examples

[x] Example: add Llama2 example (#121)

Bug Fix

[x] Fix install bugs (#116)
[x] Fix a batched matmul bug (#117)
[x] #112

Released: https://github.com/microsoft/ark/releases/tag/v0.3.0


v1.0.0-rc.4 contains CVE-2023-2650 sev HIGH

Name: libcrypto3, Version: 3.1.0-r4
    CVE-2023-2650, Severity: HIGH, Source: https://security.alpinelinux.org/vuln/CVE-2023-2650
        Fixed version: 3.1.1-r0
Name: libssl3, Version: 3.1.0-r4
    CVE-2023-2650, Severity: HIGH, Source: https://security.alpinelinux.org/vuln/CVE-2023-2650
        Fixed version: 3.1.1-r0

Please familiarize yourself with https://fluxcd.io/flux/security/#scanning-for-cves


refactor(*): add iso8601duration validate tag

Signed-off-by: lsytj0413<EMAIL_ADDRESS>Many thanks for submitting your Pull Request :heart:!
What this PR does / why we need it:

simplify iso 8601 duration string validate

Special notes for reviewers:
Additional information (if needed):

The https://github.com/serverlessworkflow/sdk-go/pull/76 should be merge before, it will fix WhiteSource Security Check

@ricardozanini
done, PTAL


Incorrect draggable height of AppWindow's title bar

Describe the bug
The draggable area of AppWindow's title bar exceeds the expected height
It have wrong extra height
AvaloniaApplication1.zip
Screenshots

Desktop/Platform (please complete the following information):

OS: Windows 10
FluentAvalonia Version 2.1.0
Avalonia Version 11.1.3

I found this bug is related to DPI, if I set to 200%, draggable area size will be double size of real title bar area size

https://github.com/amwx/FluentAvalonia/blob/2264dfe44bce8b0f532f58909a47cd5edf9acdf7/src/FluentAvalonia/UI/Windowing/AppWindow/AppWindow.cs#L240
I delete  * RenderScaling, this issue solved.
But I don't konw why this happend. Somebody know reason?


Selector based port rules dont include standalone containers.

Rancher server version - Build from wagyu
Steps to reproduce the problem:
Create a standalone container with labels "test1=value1"
Create a LB service with following  selector based port rules:
"portRules": [
{
"type": "portRule",
"priority": 1,
"protocol": "http",
"selector": "test1=value1",
"sourcePort": 8000,
"targetPort": 80,
},
],

ha proxy configuration does not include standalone containers as targets for the backend relating to this portRule.

Would require an ability to specify port rules on the target container side; that would be like a special feature. Moving to unscheduled for now.


Welcome tab theme link incorrect

Environment (please complete the following information):

OS: All
Extension version 1.3.0

Describe the bug:

Welcome tab theme link is incorrect
Repro steps:

open welcome tab,
click theme link,
notice that it resolves to incorrect page

This might have become irrelevant, I don't see the Welcome tab in the extension anymore. @codepo8 can you confirm that the tab isn't there and close the issue if so?


Adding support for cab files to Chef package provider on windows

[In progress]

@mwrock you talked with @lamont-granquist about this pattern when you wrote the chocolately provider, yeah? any opinions on continuing with this pattern or writing a completely separate resource and provider for new functionality?

+1 on completely separate cab_package resource + provider.

@Vasu1105 I thought I linked to these somewhere for you to reference, but not sure where. Maybe slack. Anyway, this is the most recent package provider on Windows. It's got newer patterns that you should use.
https://github.com/chef/chef/blob/master/lib/chef/resource/chocolatey_package.rb
https://github.com/chef/chef/blob/master/lib/chef/provider/package/chocolatey.rb
I'd only use my old old cab branch as a guide on the systems integration portion of the provider.

Please rebase and signoff after incorporating feedback.

@btm Fixed review comments, rebase branch and signed off


Make the template responsive on mobile

Maybe ask jonginn for help

(mostly) resolved in https://github.com/PHPDorset/phpdorset.github.io/pull/51


Added Heroku deployment instructions

Two more things to add:

Once you separate the repository into one with client and one with the server, update the .github\workflows\main.yml in each as the following:
server
name: FakeStackOverflow CI
on: # Controls when the action will run.
  # Triggers the workflow on push or pull request events but only for the master branch. If you want to trigger the action on other branches, add here
  push:
    branches: [main]
  pull_request:
    branches: [main]

  # Allows you to run this workflow manually from the Actions tab
  workflow_dispatch:

# A workflow run is made up of one or more jobs that can run sequentially or in parallel
jobs:
  build-and-test: #
    # The type of runner that the job will run on
    runs-on: ubuntu-20.04

    # Steps represent a sequence of tasks that will be executed as part of the job
    steps:
      - name: Git Checkout
        uses: actions/checkout@v4

      - name: Set up Node.js 20.x
        uses: actions/setup-node@v4
        with:
          node-version: "20.x"

      - name: Launch MongoDB Server
        uses<EMAIL_ADDRESS>        with:
          mongodb-version: "7.0"

      - name: Build and lint frontend
        if: ${{ always() }}
        env:
          REACT_APP_SERVER_URL: http://localhost:8000
        run: cd client; npm ci && npm run build && npm run lint

client
name: FakeStackOverflow CI
on: # Controls when the action will run.
  # Triggers the workflow on push or pull request events but only for the master branch. If you want to trigger the action on other branches, add here
  push:
    branches: [main]
  pull_request:
    branches: [main]

  # Allows you to run this workflow manually from the Actions tab
  workflow_dispatch:

# A workflow run is made up of one or more jobs that can run sequentially or in parallel
jobs:
  build-and-test: #
    # The type of runner that the job will run on
    runs-on: ubuntu-20.04

    # Steps represent a sequence of tasks that will be executed as part of the job
    steps:
      - name: Git Checkout
        uses: actions/checkout@v4

      - name: Set up Node.js 20.x
        uses: actions/setup-node@v4
        with:
          node-version: "20.x"

      - name: Launch MongoDB Server
        uses<EMAIL_ADDRESS>        with:
          mongodb-version: "7.0"

      - name: Build backend service
        if: ${{ always() }}
        run: cd server; npm ci

      - name: Test backend server
        if: ${{ always() }}
        env:
          # Pass the environmental variables for the backend tests to use
          MONGODB_URI: mongodb://localhost:27017
        run: |
          cd server

          npm run start & sleep 10

          echo "Checking if the server is running..."
          curl --fail 'http://localhost:8000/question/getQuestion?order=newest&search=' || (echo "Server failed to start" && killall node && exit 1)

          echo "Server started successfully. Now stopping..."
          killall node

          npm run test

      - name: Lint backend
        if: ${{ always() }}
        run: cd server; npm run lint

In case you are still running into memory issues in the Heroku deployment, you can update the "Dynos" type.
Add the steps from here: https://help.heroku.com/XX3MKY2E/how-do-i-change-the-dyno-types-for-my-application

I have resolved the comments made by Anikesh. If everything works fine I will close this PR and raise a new PR for Module13 Activity.md file


Use Case: Views

Read single from a view
Read filtered from a view
Read all from a view
4. Write to view (or underlying table if writing to a view isn't supported)

Use the Employee table joined to the EmployeeClassification table. Writes would only affect the Employee table.

[x] Database changes
[x] Test cases
[x] ADO
[x] Chain
[x] Dapper
[x] EF Core
[x] NHibernate
[ ] RepoDB
[x] ServiceStack
[x] Documentation
[ ] LLBL Gen Pro

Removing the "Write to view" use case. This is pretty obscure and really falls into the "stupid pet tricks" category.

Tickets opened for remaining ORMs.


Update staging webapps to use tailscale subnet router

Add vpc, subnet, security groups, and listener arn to AwsTool._deploy_service
Update CLI to include those options
Update deploy to staging workflows to use newly created subnet router.
Add docs on how to deploy websites to staging environment with whitelist access through tailscale.

I renamed staging from webapp-homepage-staging to just homepage-staging, once this is merged I'll probably go in and manually delete the old staging resources


nvm use 16.14.2 displays "exit status 1: The device does not support symbolic links."

Issue:
After nvm install lts, nvm use 16.14.2 causes "exit status 1: The device does not support symbolic links."
How To Reproduce:

Download the installer from https://github.com/coreybutler/nvm-windows
Run the installer, set nvm home to D:\tools\nvm and node home to D:\tools\nodejs
run nvm install lts, wait for complete
run nvm use 16.14.2

Expected Behavior:
Node 16.14.2 is installed
Screenshots:

Fixed by using C:\ drive instead. Externals do not support symbolic links it seems.