text:
NO ip address for jessie in container

Hi,
I'm sorry but actually I have the same problem with a jessie in guest !?
uname -a
Linux fx8320e 4.2.0-35-generic #40~14.04.1-Ubuntu SMP Fri Mar 18 16:37:35 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux
lxd --version
2.0.0
ifconfig lxdbr0
lxdbr0    Link encap:Ethernet  HWaddr fe:15:87:8f:e9:ab
          inet addr:10.0.4.1  Bcast:0.0.0.0  Mask:255.255.255.0
          inet6 addr: fe80::88:95ff:fe78:1991/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:84 errors:0 dropped:0 overruns:0 frame:0
          TX packets:102 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:9356 (9.3 KB)  TX bytes:15643 (15.6 KB)

lxc profile show default
name: default
config: {}
description: Default LXD profile
devices:
  eth0:
    name: eth0
    nictype: bridged
    parent: lxdbr0
    type: nic

lxc config show
config:
  images.auto_update_cached: "true"
  images.auto_update_interval: "24"
  images.remote_cache_expiry: "10"
  storage.lvm_thinpool_name: LXDPool
  storage.lvm_vg_name: ssd
  storage.lvm_volume_size: 2G

I'm running a few ditros & version, in a fresh installation with this step:

lxc image copy ...
lxc init ...
lxc start ...

for

c1 - centos6
j1 - jessie
s1 - stretch
t1 - trusty
w1 - wheezy

lxc list
+------+---------+-------------------+------+------------+-----------+
| NAME |  STATE  |       IPV4        | IPV6 |    TYPE    | SNAPSHOTS |
+------+---------+-------------------+------+------------+-----------+
| c1   | RUNNING | 10.0.4.138 (eth0) |      | PERSISTENT | 0         |
+------+---------+-------------------+------+------------+-----------+
| j1   | RUNNING |                   |      | PERSISTENT | 0         |
+------+---------+-------------------+------+------------+-----------+
| s1   | RUNNING | 10.0.4.240 (eth0) |      | PERSISTENT | 0         |
+------+---------+-------------------+------+------------+-----------+
| t1   | RUNNING | 10.0.4.106 (eth0) |      | PERSISTENT | 0         |
+------+---------+-------------------+------+------------+-----------+
| w1   | RUNNING | 10.0.4.56 (eth0)  |      | PERSISTENT | 0         |
+------+---------+-------------------+------+------------+-----------+

lxc info j1 --show-log
Name: j1
Architecture: x86_64
Created: 2016/04/19 00:18 UTC
Status: Running
Type: persistent
Profiles: default
Pid: 13600
Ips:
  eth0:	inet6	fe80::216:3eff:fe11:b410	veth44EYE8
  lo:	inet	127.0.0.1
  lo:	inet6	::1
Resources:
  Processes: 1
  Network usage:
    lo:
      Bytes received: 0 bytes
      Bytes sent: 0 bytes
      Packets received: 0
      Packets sent: 0
    eth0:
      Bytes received: 3.56kB
      Bytes sent: 578 bytes
      Packets received: 21
      Packets sent: 7

Log:

            lxc 1461027126.583 INFO     lxc_confile - confile.c:config_idmap:1437 - read uid map: type u nsid 0 hostid 165536 range 65536
            lxc 1461027126.583 INFO     lxc_confile - confile.c:config_idmap:1437 - read uid map: type g nsid 0 hostid 165536 range 65536
            lxc 1461027126.588 WARN     lxc_cgmanager - cgmanager.c:cgm_get:994 - do_cgm_get exited with error
            lxc 1461027126.592 INFO     lxc_confile - confile.c:config_idmap:1437 - read uid map: type u nsid 0 hostid 165536 range 65536
            lxc 1461027126.592 INFO     lxc_confile - confile.c:config_idmap:1437 - read uid map: type g nsid 0 hostid 165536 range 65536
            lxc 1461027126.597 WARN     lxc_cgmanager - cgmanager.c:cgm_get:994 - do_cgm_get exited with error
            lxc 1461027126.602 WARN     lxc_cgmanager - cgmanager.c:cgm_get:994 - do_cgm_get exited with error
            lxc 1461027126.616 WARN     lxc_cgmanager - cgmanager.c:cgm_get:994 - do_cgm_get exited with error
            lxc 1461027126.616 INFO     lxc_start - start.c:lxc_check_inherited:240 - closed inherited fd 3
            lxc 1461027126.616 INFO     lxc_start - start.c:lxc_check_inherited:240 - closed inherited fd 8
            lxc 1461027126.620 INFO     lxc_container - lxccontainer.c:do_lxcapi_start:712 - Attempting to set proc title to [lxc monitor] /var/lib/lxd/containers j1
            lxc 1461027126.621 INFO     lxc_start - start.c:lxc_check_inherited:240 - closed inherited fd 8
            lxc 1461027126.621 INFO     lxc_lsm - lsm/lsm.c:lsm_init:48 - LSM security driver AppArmor
            lxc 1461027126.621 INFO     lxc_seccomp - seccomp.c:parse_config_v2:324 - processing: .reject_force_umount  # comment this to allow umount -f;  not recommended.
            lxc 1461027126.621 INFO     lxc_seccomp - seccomp.c:parse_config_v2:426 - Adding native rule for reject_force_umount action 0
            lxc 1461027126.621 INFO     lxc_seccomp - seccomp.c:do_resolve_add_rule:216 - Setting seccomp rule to reject force umounts

            lxc 1461027126.621 INFO     lxc_seccomp - seccomp.c:parse_config_v2:429 - Adding compat rule for reject_force_umount action 0
            lxc 1461027126.621 INFO     lxc_seccomp - seccomp.c:do_resolve_add_rule:216 - Setting seccomp rule to reject force umounts

            lxc 1461027126.621 INFO     lxc_seccomp - seccomp.c:parse_config_v2:324 - processing: .[all].
            lxc 1461027126.621 INFO     lxc_seccomp - seccomp.c:parse_config_v2:324 - processing: .kexec_load errno 1.
            lxc 1461027126.621 INFO     lxc_seccomp - seccomp.c:parse_config_v2:426 - Adding native rule for kexec_load action 327681
            lxc 1461027126.621 INFO     lxc_seccomp - seccomp.c:parse_config_v2:429 - Adding compat rule for kexec_load action 327681
            lxc 1461027126.621 INFO     lxc_seccomp - seccomp.c:parse_config_v2:324 - processing: .open_by_handle_at errno 1.
            lxc 1461027126.621 INFO     lxc_seccomp - seccomp.c:parse_config_v2:426 - Adding native rule for open_by_handle_at action 327681
            lxc 1461027126.621 INFO     lxc_seccomp - seccomp.c:parse_config_v2:429 - Adding compat rule for open_by_handle_at action 327681
            lxc 1461027126.621 INFO     lxc_seccomp - seccomp.c:parse_config_v2:324 - processing: .init_module errno 1.
            lxc 1461027126.621 INFO     lxc_seccomp - seccomp.c:parse_config_v2:426 - Adding native rule for init_module action 327681
            lxc 1461027126.621 INFO     lxc_seccomp - seccomp.c:parse_config_v2:429 - Adding compat rule for init_module action 327681
            lxc 1461027126.621 INFO     lxc_seccomp - seccomp.c:parse_config_v2:324 - processing: .finit_module errno 1.
            lxc 1461027126.621 INFO     lxc_seccomp - seccomp.c:parse_config_v2:426 - Adding native rule for finit_module action 327681
            lxc 1461027126.621 INFO     lxc_seccomp - seccomp.c:parse_config_v2:429 - Adding compat rule for finit_module action 327681
            lxc 1461027126.621 INFO     lxc_seccomp - seccomp.c:parse_config_v2:324 - processing: .delete_module errno 1.
            lxc 1461027126.621 INFO     lxc_seccomp - seccomp.c:parse_config_v2:426 - Adding native rule for delete_module action 327681
            lxc 1461027126.621 INFO     lxc_seccomp - seccomp.c:parse_config_v2:429 - Adding compat rule for delete_module action 327681
            lxc 1461027126.621 INFO     lxc_seccomp - seccomp.c:parse_config_v2:436 - Merging in the compat seccomp ctx into the main one
            lxc 1461027126.621 INFO     lxc_conf - conf.c:run_script_argv:362 - Executing script '/usr/bin/lxd callhook /var/lib/lxd 1 start' for container 'j1', config section 'lxc'
            lxc 1461027126.622 INFO     lxc_start - start.c:lxc_check_inherited:240 - closed inherited fd 3
            lxc 1461027126.622 INFO     lxc_start - start.c:lxc_check_inherited:240 - closed inherited fd 8
            lxc 1461027126.626 INFO     lxc_monitor - monitor.c:lxc_monitor_sock_name:178 - using monitor sock name lxc/d78a9d7e97b4b375//var/lib/lxd/containers
            lxc 1461027126.639 DEBUG    lxc_start - start.c:setup_signal_fd:278 - sigchild handler set
            lxc 1461027126.640 DEBUG    lxc_console - console.c:lxc_console_peer_default:536 - no console peer
            lxc 1461027126.640 INFO     lxc_start - start.c:lxc_init:474 - 'j1' is initialized
            lxc 1461027126.640 DEBUG    lxc_start - start.c:__lxc_start:1186 - Not dropping cap_sys_boot or watching utmp
            lxc 1461027126.642 INFO     lxc_start - start.c:resolve_clone_flags:883 - Cloning a new user namespace
            lxc 1461027126.643 DEBUG    lxc_conf - conf.c:instantiate_veth:2821 - instantiated veth 'veth44EYE8/vethUYB2PG', index is '14'
            lxc 1461027126.643 INFO     lxc_cgroup - cgroup.c:cgroup_init:65 - cgroup driver cgmanager initing for j1
            lxc 1461027126.678 DEBUG    lxc_conf - conf.c:lxc_assign_network:3238 - move 'eth0' to '13600'
            lxc 1461027126.682 NOTICE   lxc_start - start.c:do_start:699 - switching to gid/uid 0 in new user namespace
            lxc 1461027126.683 DEBUG    lxc_conf - conf.c:setup_rootfs:1295 - mounted '/var/lib/lxd/containers/j1/rootfs' on '/usr/lib/x86_64-linux-gnu/lxc'
            lxc 1461027126.683 INFO     lxc_conf - conf.c:setup_utsname:928 - 'j1' hostname has been setup
            lxc 1461027126.697 DEBUG    lxc_conf - conf.c:setup_hw_addr:2368 - mac address '00:16:3e:11:b4:10' on 'eth0' has been setup
            lxc 1461027126.698 DEBUG    lxc_conf - conf.c:setup_netdev:2595 - 'eth0' has been setup
            lxc 1461027126.698 INFO     lxc_conf - conf.c:setup_network:2616 - network has been setup
            lxc 1461027126.698 INFO     lxc_conf - conf.c:mount_autodev:1157 - Mounting container /dev
            lxc 1461027126.701 INFO     lxc_conf - conf.c:mount_autodev:1179 - Mounted tmpfs onto /usr/lib/x86_64-linux-gnu/lxc/dev
            lxc 1461027126.701 INFO     lxc_conf - conf.c:mount_autodev:1197 - Mounted container /dev
            lxc 1461027126.702 DEBUG    lxc_conf - conf.c:mount_entry:1738 - 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 1461027126.702 DEBUG    lxc_conf - conf.c:mount_entry:1753 - (at remount) flags for /proc/sys/fs/binfmt_misc was 4110, required extra flags are 14
            lxc 1461027126.702 DEBUG    lxc_conf - conf.c:mount_entry:1788 - mounted '/proc/sys/fs/binfmt_misc' on '/usr/lib/x86_64-linux-gnu/lxc/proc/sys/fs/binfmt_misc', type 'none'
            lxc 1461027126.702 DEBUG    lxc_conf - conf.c:mount_entry:1738 - remounting /sys/firmware/efi/efivars on /usr/lib/x86_64-linux-gnu/lxc/sys/firmware/efi/efivars to respect bind or remount options
            lxc 1461027126.702 DEBUG    lxc_conf - conf.c:mount_entry:1753 - (at remount) flags for /sys/firmware/efi/efivars was 4096, required extra flags are 0
            lxc 1461027126.702 DEBUG    lxc_conf - conf.c:mount_entry:1762 - mountflags already was 20480, skipping remount
            lxc 1461027126.702 DEBUG    lxc_conf - conf.c:mount_entry:1788 - mounted '/sys/firmware/efi/efivars' on '/usr/lib/x86_64-linux-gnu/lxc/sys/firmware/efi/efivars', type 'none'
            lxc 1461027126.702 DEBUG    lxc_conf - conf.c:mount_entry:1738 - remounting /sys/fs/fuse/connections on /usr/lib/x86_64-linux-gnu/lxc/sys/fs/fuse/connections to respect bind or remount options
            lxc 1461027126.702 DEBUG    lxc_conf - conf.c:mount_entry:1753 - (at remount) flags for /sys/fs/fuse/connections was 4096, required extra flags are 0
            lxc 1461027126.702 DEBUG    lxc_conf - conf.c:mount_entry:1762 - mountflags already was 20480, skipping remount
            lxc 1461027126.702 DEBUG    lxc_conf - conf.c:mount_entry:1788 - mounted '/sys/fs/fuse/connections' on '/usr/lib/x86_64-linux-gnu/lxc/sys/fs/fuse/connections', type 'none'
            lxc 1461027126.702 DEBUG    lxc_conf - conf.c:mount_entry:1738 - remounting /sys/fs/pstore on /usr/lib/x86_64-linux-gnu/lxc/sys/fs/pstore to respect bind or remount options
            lxc 1461027126.702 DEBUG    lxc_conf - conf.c:mount_entry:1753 - (at remount) flags for /sys/fs/pstore was 4096, required extra flags are 0
            lxc 1461027126.702 DEBUG    lxc_conf - conf.c:mount_entry:1762 - mountflags already was 20480, skipping remount
            lxc 1461027126.702 DEBUG    lxc_conf - conf.c:mount_entry:1788 - mounted '/sys/fs/pstore' on '/usr/lib/x86_64-linux-gnu/lxc/sys/fs/pstore', type 'none'
            lxc 1461027126.702 DEBUG    lxc_conf - conf.c:mount_entry:1738 - remounting /sys/kernel/debug on /usr/lib/x86_64-linux-gnu/lxc/sys/kernel/debug to respect bind or remount options
            lxc 1461027126.702 DEBUG    lxc_conf - conf.c:mount_entry:1753 - (at remount) flags for /sys/kernel/debug was 4096, required extra flags are 0
            lxc 1461027126.702 DEBUG    lxc_conf - conf.c:mount_entry:1762 - mountflags already was 20480, skipping remount
            lxc 1461027126.702 DEBUG    lxc_conf - conf.c:mount_entry:1788 - mounted '/sys/kernel/debug' on '/usr/lib/x86_64-linux-gnu/lxc/sys/kernel/debug', type 'none'
            lxc 1461027126.702 DEBUG    lxc_conf - conf.c:mount_entry:1738 - remounting /sys/kernel/security on /usr/lib/x86_64-linux-gnu/lxc/sys/kernel/security to respect bind or remount options
            lxc 1461027126.702 DEBUG    lxc_conf - conf.c:mount_entry:1753 - (at remount) flags for /sys/kernel/security was 4096, required extra flags are 0
            lxc 1461027126.702 DEBUG    lxc_conf - conf.c:mount_entry:1762 - mountflags already was 20480, skipping remount
            lxc 1461027126.702 DEBUG    lxc_conf - conf.c:mount_entry:1788 - mounted '/sys/kernel/security' on '/usr/lib/x86_64-linux-gnu/lxc/sys/kernel/security', type 'none'
            lxc 1461027126.702 ERROR    lxc_utils - utils.c:safe_mount:1686 - No such file or directory - Failed to mount /dev/mqueue onto /usr/lib/x86_64-linux-gnu/lxc/dev/mqueue
            lxc 1461027126.702 INFO     lxc_conf - conf.c:mount_entry:1727 - failed to mount '/dev/mqueue' on '/usr/lib/x86_64-linux-gnu/lxc/dev/mqueue' (optional): No such file or directory
            lxc 1461027126.702 DEBUG    lxc_conf - conf.c:mount_entry:1738 - remounting /var/lib/lxd/devlxd on /usr/lib/x86_64-linux-gnu/lxc/dev/lxd to respect bind or remount options
            lxc 1461027126.702 DEBUG    lxc_conf - conf.c:mount_entry:1753 - (at remount) flags for /var/lib/lxd/devlxd was 4096, required extra flags are 0
            lxc 1461027126.702 DEBUG    lxc_conf - conf.c:mount_entry:1762 - mountflags already was 4096, skipping remount
            lxc 1461027126.702 DEBUG    lxc_conf - conf.c:mount_entry:1788 - mounted '/var/lib/lxd/devlxd' on '/usr/lib/x86_64-linux-gnu/lxc/dev/lxd', type 'none'
            lxc 1461027126.702 DEBUG    lxc_conf - conf.c:mount_entry:1738 - remounting /var/lib/lxd/shmounts/j1 on /usr/lib/x86_64-linux-gnu/lxc/dev/.lxd-mounts to respect bind or remount options
            lxc 1461027126.702 DEBUG    lxc_conf - conf.c:mount_entry:1753 - (at remount) flags for /var/lib/lxd/shmounts/j1 was 4096, required extra flags are 0
            lxc 1461027126.702 DEBUG    lxc_conf - conf.c:mount_entry:1762 - mountflags already was 4096, skipping remount
            lxc 1461027126.702 DEBUG    lxc_conf - conf.c:mount_entry:1788 - mounted '/var/lib/lxd/shmounts/j1' on '/usr/lib/x86_64-linux-gnu/lxc/dev/.lxd-mounts', type 'none'
            lxc 1461027126.702 INFO     lxc_conf - conf.c:mount_file_entries:2150 - mount points have been setup
            lxc 1461027126.702 INFO     lxc_conf - conf.c:run_script_argv:362 - Executing script '/usr/share/lxcfs/lxc.mount.hook' for container 'j1', config section 'lxc'
            lxc 1461027126.761 INFO     lxc_conf - conf.c:fill_autodev:1225 - Creating initial consoles under container /dev
            lxc 1461027126.761 INFO     lxc_conf - conf.c:fill_autodev:1236 - Populating container /dev
            lxc 1461027126.761 INFO     lxc_conf - conf.c:fill_autodev:1269 - Populated container /dev
            lxc 1461027126.761 INFO     lxc_conf - conf.c:setup_dev_console:1518 - console has been setup
            lxc 1461027126.761 INFO     lxc_utils - utils.c:mount_proc_if_needed:1718 - I am 1, /proc/self points to '1'
            lxc 1461027126.777 DEBUG    lxc_conf - conf.c:setup_rootfs_pivot_root:1135 - pivot_root syscall to '/usr/lib/x86_64-linux-gnu/lxc' successful
            lxc 1461027126.777 INFO     lxc_conf - conf.c:setup_tty:1080 - 0 tty(s) has been setup
            lxc 1461027126.777 INFO     lxc_conf - conf.c:setup_personality:1473 - set personality to '0x0'
            lxc 1461027126.777 DEBUG    lxc_conf - conf.c:setup_caps:2279 - drop capability 'mac_admin' (33)
            lxc 1461027126.777 DEBUG    lxc_conf - conf.c:setup_caps:2279 - drop capability 'mac_override' (32)
            lxc 1461027126.777 DEBUG    lxc_conf - conf.c:setup_caps:2279 - drop capability 'sys_time' (25)
            lxc 1461027126.777 DEBUG    lxc_conf - conf.c:setup_caps:2279 - drop capability 'sys_module' (16)
            lxc 1461027126.777 DEBUG    lxc_conf - conf.c:setup_caps:2279 - drop capability 'sys_rawio' (17)
            lxc 1461027126.777 DEBUG    lxc_conf - conf.c:setup_caps:2288 - capabilities have been setup
            lxc 1461027126.777 NOTICE   lxc_conf - conf.c:lxc_setup:4026 - 'j1' is setup.
            lxc 1461027126.778 INFO     lxc_apparmor - lsm/apparmor.c:apparmor_process_label_set:187 - changed apparmor profile to lxd-j1_</var/lib/lxd>
            lxc 1461027126.778 NOTICE   lxc_start - start.c:start:1295 - exec'ing '/sbin/init'
            lxc 1461027126.781 NOTICE   lxc_start - start.c:post_start:1306 - '/sbin/init' started with pid '13600'
            lxc 1461027126.781 WARN     lxc_start - start.c:signal_handler:326 - invalid pid for SIGCHLD
            lxc 1461027126.781 DEBUG    lxc_commands - commands.c:lxc_cmd_handler:893 - peer has disconnected
            lxc 1461027126.782 DEBUG    lxc_commands - commands.c:lxc_cmd_get_state:579 - 'j1' is in 'RUNNING' state
            lxc 1461027126.782 DEBUG    lxc_commands - commands.c:lxc_cmd_handler:893 - peer has disconnected
            lxc 1461027135.159 INFO     lxc_confile - confile.c:config_idmap:1437 - read uid map: type u nsid 0 hostid 165536 range 65536
            lxc 1461027135.159 INFO     lxc_confile - confile.c:config_idmap:1437 - read uid map: type g nsid 0 hostid 165536 range 65536
            lxc 1461027135.163 DEBUG    lxc_commands - commands.c:lxc_cmd_handler:893 - peer has disconnected
            lxc 1461027135.164 DEBUG    lxc_commands - commands.c:lxc_cmd_handler:893 - peer has disconnected
            lxc 1461027135.164 DEBUG    lxc_commands - commands.c:lxc_cmd_get_state:579 - 'j1' is in 'RUNNING' state
            lxc 1461027135.167 INFO     lxc_confile - confile.c:config_idmap:1437 - read uid map: type u nsid 0 hostid 165536 range 65536
            lxc 1461027135.167 INFO     lxc_confile - confile.c:config_idmap:1437 - read uid map: type g nsid 0 hostid 165536 range 65536
            lxc 1461027135.171 DEBUG    lxc_commands - commands.c:lxc_cmd_handler:893 - peer has disconnected
            lxc 1461027135.172 DEBUG    lxc_commands - commands.c:lxc_cmd_handler:893 - peer has disconnected
            lxc 1461027135.172 DEBUG    lxc_commands - commands.c:lxc_cmd_get_state:579 - 'j1' is in 'RUNNING' state
            lxc 1461027135.175 DEBUG    lxc_commands - commands.c:lxc_cmd_handler:893 - peer has disconnected
            lxc 1461027135.176 DEBUG    lxc_commands - commands.c:lxc_cmd_handler:893 - peer has disconnected
            lxc 1461027135.176 DEBUG    lxc_commands - commands.c:lxc_cmd_get_state:579 - 'j1' is in 'RUNNING' state
            lxc 1461027135.176 DEBUG    lxc_commands - commands.c:lxc_cmd_handler:893 - peer has disconnected
            lxc 1461027135.176 DEBUG    lxc_commands - commands.c:lxc_cmd_handler:893 - peer has disconnected
            lxc 1461027135.188 DEBUG    lxc_commands - commands.c:lxc_cmd_handler:893 - peer has disconnected
            lxc 1461027135.189 DEBUG    lxc_commands - commands.c:lxc_cmd_handler:893 - peer has disconnected
            lxc 1461027135.189 DEBUG    lxc_commands - commands.c:lxc_cmd_get_state:579 - 'j1' is in 'RUNNING' state
            lxc 1461027135.189 DEBUG    lxc_commands - commands.c:lxc_cmd_handler:893 - peer has disconnected
            lxc 1461027135.189 DEBUG    lxc_commands - commands.c:lxc_cmd_handler:893 - peer has disconnected
            lxc 1461027135.192 DEBUG    lxc_commands - commands.c:lxc_cmd_handler:893 - peer has disconnected
            lxc 1461027135.194 DEBUG    lxc_commands - commands.c:lxc_cmd_handler:893 - peer has disconnected
            lxc 1461027135.194 DEBUG    lxc_commands - commands.c:lxc_cmd_get_state:579 - 'j1' is in 'RUNNING' state
            lxc 1461027135.194 DEBUG    lxc_commands - commands.c:lxc_cmd_handler:893 - peer has disconnected
            lxc 1461027135.194 DEBUG    lxc_commands - commands.c:lxc_cmd_handler:893 - peer has disconnected

And the only one container which have not ip address is jessie !?
Thank's for any helps ;o)

two other information about this problem :
on host
root@fx8320e:~$find / -name j1
/dev/ssd/j1
/var/log/lxd/j1
/var/lib/lxd/shmounts/j1
/var/lib/lxd/devices/j1
/var/lib/lxd/security/seccomp/j1
/var/lib/lxd/containers/j1
/sys/fs/cgroup/systemd/lxc/j1
root@fx8320e:~$find / -name t1
/dev/ssd/t1
/usr/src/linux-headers-4.2.0-35-generic/include/config/chelsio/t1
/var/log/lxd/t1
/var/lib/lxd/shmounts/t1
/var/lib/lxd/devices/t1
/var/lib/lxd/security/seccomp/t1
/var/lib/lxd/containers/t1
/var/lib/lxd/containers/t1/rootfs/var/lib/cloud/instances/t1
/sys/fs/cgroup/systemd/lxc/t1
/run/lxcfs/controllers/blkio/lxc/t1
/run/lxcfs/controllers/cpu/lxc/t1
/run/lxcfs/controllers/cpuacct/lxc/t1
/run/lxcfs/controllers/cpuset/lxc/t1
/run/lxcfs/controllers/devices/lxc/t1
/run/lxcfs/controllers/freezer/lxc/t1
/run/lxcfs/controllers/hugetlb/lxc/t1
/run/lxcfs/controllers/memory/lxc/t1
/run/lxcfs/controllers/net_cls/lxc/t1
/run/lxcfs/controllers/net_prio/lxc/t1
/run/lxcfs/controllers/perf_event/lxc/t1
/run/lxcfs/controllers/name=systemd/lxc/t1

unable to reload networking in jessie container:
root@fx8320e:~$lxc exec j1 bash
root@j1:~# service networking restart
Failed to get D-Bus connection: No such file or directory

pending a good template of debian jessie, resolving with https://github.com/lxc/lxc/issues/979


text:
Mount snap "core" (1689) ([start snap-core-1689.mount] failed with exit status 1

How to test snaps with LXD?
$ lxc launch ubuntu:16.04/amd64 snapsnap
$ lxc exec snapsnap -- snap install micro --beta
...
error: cannot perform the following tasks:
- Mount snap "core" (1689) ([start snap-core-1689.mount] failed with exit status 1: Job for snap-core-1689.mount failed. See "systemctl status snap-core-1689.mount" and "journalctl -xe" for details.
)

$ lxc exec snapsnap -- systemctl status snap-core-1689.mount
● snap-core-1689.mount - Mount unit for core
   Loaded: loaded (/etc/systemd/system/snap-core-1689.mount; enabled; vendor preset: enabled)
   Active: failed (Result: exit-code) since Fri 2017-06-16 12:02:20 UTC; 6min ago
    Where: /snap/core/1689
     What: /var/lib/snapd/snaps/core_1689.snap
  Process: 521 ExecMount=/bin/mount /var/lib/snapd/snaps/core_1689.snap /snap/core/1689 -t squashfs -o nodev,ro (code=exited, status=32)

Jun 16 12:02:20 snapsnap systemd[1]: Mounting Mount unit for core...
Jun 16 12:02:20 snapsnap mount[521]: mount: /snap/core/1689: mount failed: Unknown error -1
Jun 16 12:02:20 snapsnap systemd[1]: snap-core-1689.mount: Mount process exited, code=exited status=32
Jun 16 12:02:20 snapsnap systemd[1]: Failed to mount Mount unit for core.
Jun 16 12:02:20 snapsnap systemd[1]: snap-core-1689.mount: Unit entered failed state.

$ lxc exec snapsnap -- journalctl -xe
...
Jun 16 12:01:03 snapsnap snapd[337]: 2017/06/16 12:01:03.790126 api.go:912: Installing snap "micro" revision unset
Jun 16 12:01:04 snapsnap /usr/lib/snapd/snapd[337]: daemon.go:176: DEBUG: uid=0;@ POST /v2/snaps/micro 568.833648ms 202
Jun 16 12:01:04 snapsnap /usr/lib/snapd/snapd[337]: snapmgr.go:496: DEBUG: Next refresh scheduled for 2017-06-16 20:57:17.719060486 +0000 UTC.
Jun 16 12:01:04 snapsnap /usr/lib/snapd/snapd[337]: taskrunner.go:367: DEBUG: Running task 2 on Do: Download snap "core" (1689) from channel "stable"
Jun 16 12:02:18 snapsnap /usr/lib/snapd/snapd[337]: taskrunner.go:367: DEBUG: Running task 3 on Do: Fetch and check assertions for snap "core" (1689)
Jun 16 12:02:20 snapsnap /usr/lib/snapd/snapd[337]: taskrunner.go:367: DEBUG: Running task 4 on Do: Mount snap "core" (1689)
Jun 16 12:02:20 snapsnap systemd[1]: Reloading.
Jun 16 12:02:20 snapsnap systemd[1]: apt-daily.timer: Adding 2h 4min 14.263669s random time.
Jun 16 12:02:20 snapsnap systemd[1]: Reloading.
Jun 16 12:02:20 snapsnap systemd[1]: apt-daily.timer: Adding 11h 26min 34.666378s random time.
Jun 16 12:02:20 snapsnap systemd[1]: Failed to reset devices.list on /system.slice: Operation not permitted
Jun 16 12:02:20 snapsnap systemd[1]: Failed to reset devices.list on /system.slice/snap-core-1689.mount: Operation not permitted
Jun 16 12:02:20 snapsnap systemd[1]: Mounting Mount unit for core...
-- Subject: Unit snap-core-1689.mount has begun start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit snap-core-1689.mount has begun starting up.
Jun 16 12:02:20 snapsnap systemd[1]: Failed to reset devices.list on /user.slice: Operation not permitted
Jun 16 12:02:20 snapsnap systemd[1]: Failed to reset devices.list on /init.scope: Operation not permitted
Jun 16 12:02:20 snapsnap systemd[1]: Failed to reset devices.list on /system.slice/proc-meminfo.mount: Operation not permitted
Jun 16 12:02:20 snapsnap systemd[1]: Failed to reset devices.list on /system.slice/-.mount: Operation not permitted
Jun 16 12:02:20 snapsnap systemd[1]: Failed to reset devices.list on /system.slice/proc-diskstats.mount: Operation not permitted
Jun 16 12:02:20 snapsnap systemd[1]: Failed to reset devices.list on /system.slice/rc-local.service: Operation not permitted
Jun 16 12:02:20 snapsnap systemd[1]: Failed to reset devices.list on /system.slice/sys-kernel-debug.mount: Operation not permitted
Jun 16 12:02:20 snapsnap systemd[1]: Failed to reset devices.list on /system.slice/lvm2-monitor.service: Operation not permitted
Jun 16 12:02:20 snapsnap mount[521]: mount: /snap/core/1689: mount failed: Unknown error -1
Jun 16 12:02:20 snapsnap systemd[1]: Failed to reset devices.list on /system.slice/dev-tty.mount: Operation not permitted
Jun 16 12:02:20 snapsnap systemd[1]: Failed to reset devices.list on /system.slice/dev-lxd.mount: Operation not permitted
Jun 16 12:02:20 snapsnap systemd[1]: Failed to reset devices.list on /system.slice/dev-fuse.mount: Operation not permitted
Jun 16 12:02:20 snapsnap systemd[1]: Failed to reset devices.list on /system.slice/networking.service: Operation not permitted
Jun 16 12:02:20 snapsnap systemd[1]: Failed to reset devices.list on /system.slice/dev-net-tun.mount: Operation not permitted
Jun 16 12:02:20 snapsnap systemd[1]: Failed to reset devices.list on /system.slice/systemd-logind.service: Operation not permitted
Jun 16 12:02:20 snapsnap systemd[1]: Failed to reset devices.list on /system.slice/sys-kernel-debug-tracing.mount: Operation not permitted
Jun 16 12:02:20 snapsnap systemd[1]: Failed to reset devices.list on /system.slice/dev-.lxd\x2dmounts.mount: Operation not permitted
Jun 16 12:02:20 snapsnap systemd[1]: Failed to reset devices.list on /system.slice/snapd.service: Operation not permitted
Jun 16 12:02:20 snapsnap systemd[1]: Failed to reset devices.list on /system.slice/proc-stat.mount: Operation not permitted
Jun 16 12:02:20 snapsnap systemd[1]: Failed to reset devices.list on /system.slice/proc-sys-fs-binfmt_misc.mount: Operation not permitted
Jun 16 12:02:20 snapsnap systemd[1]: Failed to reset devices.list on /system.slice/var-lib-lxcfs.mount: Operation not permitted
Jun 16 12:02:20 snapsnap systemd[1]: Failed to reset devices.list on /system.slice/dev-ptmx.mount: Operation not permitted
Jun 16 12:02:20 snapsnap systemd[1]: Failed to reset devices.list on /system.slice/systemd-journald.service: Operation not permitted
Jun 16 12:02:20 snapsnap systemd[1]: Failed to reset devices.list on /system.slice/cloud-config.service: Operation not permitted
Jun 16 12:02:20 snapsnap systemd[1]: Failed to reset devices.list on /system.slice/system-getty.slice: Operation not permitted
Jun 16 12:02:20 snapsnap systemd[1]: Failed to reset devices.list on /system.slice/ssh.service: Operation not permitted
Jun 16 12:02:20 snapsnap systemd[1]: Failed to reset devices.list on /system.slice/systemd-random-seed.service: Operation not permitted
Jun 16 12:02:20 snapsnap systemd[1]: Failed to reset devices.list on /system.slice/systemd-journal-flush.service: Operation not permitted
Jun 16 12:02:20 snapsnap systemd[1]: Failed to reset devices.list on /system.slice/systemd-tmpfiles-setup.service: Operation not permitted
Jun 16 12:02:20 snapsnap systemd[1]: Failed to reset devices.list on /system.slice/polkitd.service: Operation not permitted
Jun 16 12:02:20 snapsnap systemd[1]: Failed to reset devices.list on /system.slice/dev-null.mount: Operation not permitted
Jun 16 12:02:20 snapsnap systemd[1]: Failed to reset devices.list on /system.slice/ufw.service: Operation not permitted
Jun 16 12:02:20 snapsnap systemd[1]: Failed to reset devices.list on /system.slice/apparmor.service: Operation not permitted
Jun 16 12:02:20 snapsnap systemd[1]: Failed to reset devices.list on /system.slice/proc-swaps.mount: Operation not permitted
Jun 16 12:02:20 snapsnap systemd[1]: Failed to reset devices.list on /system.slice/mdadm.service: Operation not permitted
Jun 16 12:02:20 snapsnap systemd[1]: Failed to reset devices.list on /system.slice/dev-zero.mount: Operation not permitted
Jun 16 12:02:20 snapsnap systemd[1]: Failed to reset devices.list on /system.slice/cron.service: Operation not permitted
Jun 16 12:02:20 snapsnap systemd[1]: Failed to reset devices.list on /system.slice/sys-fs-fuse-connections.mount: Operation not permitted
Jun 16 12:02:20 snapsnap systemd[1]: Failed to reset devices.list on /system.slice/resolvconf.service: Operation not permitted
Jun 16 12:02:20 snapsnap systemd[1]: Failed to reset devices.list on /system.slice/atd.service: Operation not permitted
Jun 16 12:02:20 snapsnap systemd[1]: Failed to reset devices.list on /system.slice/console-getty.service: Operation not permitted
Jun 16 12:02:20 snapsnap systemd[1]: Failed to reset devices.list on /system.slice/proc-cpuinfo.mount: Operation not permitted
Jun 16 12:02:20 snapsnap systemd[1]: Failed to reset devices.list on /system.slice/systemd-udev-trigger.service: Operation not permitted
Jun 16 12:02:20 snapsnap systemd[1]: Failed to reset devices.list on /system.slice/ondemand.service: Operation not permitted
Jun 16 12:02:20 snapsnap systemd[1]: Failed to reset devices.list on /system.slice/dbus.service: Operation not permitted
Jun 16 12:02:20 snapsnap systemd[1]: Failed to reset devices.list on /system.slice/cloud-init.service: Operation not permitted
Jun 16 12:02:20 snapsnap systemd[1]: Failed to reset devices.list on /system.slice/cloud-final.service: Operation not permitted
Jun 16 12:02:20 snapsnap systemd[1]: Failed to reset devices.list on /system.slice/cloud-init-local.service: Operation not permitted
Jun 16 12:02:20 snapsnap systemd[1]: Failed to reset devices.list on /system.slice/proc-uptime.mount: Operation not permitted
Jun 16 12:02:20 snapsnap systemd[1]: Failed to reset devices.list on /system.slice/dev-urandom.mount: Operation not permitted
Jun 16 12:02:20 snapsnap systemd[1]: Failed to reset devices.list on /system.slice/rsyslog.service: Operation not permitted
Jun 16 12:02:20 snapsnap systemd[1]: Failed to reset devices.list on /system.slice/systemd-user-sessions.service: Operation not permitted
Jun 16 12:02:20 snapsnap systemd[1]: Failed to reset devices.list on /system.slice/systemd-udevd.service: Operation not permitted
Jun 16 12:02:20 snapsnap systemd[1]: Failed to reset devices.list on /system.slice/systemd-update-utmp.service: Operation not permitted
Jun 16 12:02:20 snapsnap systemd[1]: Failed to reset devices.list on /system.slice/irqbalance.service: Operation not permitted
Jun 16 12:02:20 snapsnap systemd[1]: Failed to reset devices.list on /system.slice/unattended-upgrades.service: Operation not permitted
Jun 16 12:02:20 snapsnap systemd[1]: Failed to reset devices.list on /system.slice/dev-random.mount: Operation not permitted
Jun 16 12:02:20 snapsnap systemd[1]: Failed to reset devices.list on /system.slice/apport.service: Operation not permitted
Jun 16 12:02:20 snapsnap systemd[1]: Failed to reset devices.list on /system.slice/lxd-containers.service: Operation not permitted
Jun 16 12:02:20 snapsnap systemd[1]: Failed to reset devices.list on /system.slice/dev-mqueue.mount: Operation not permitted
Jun 16 12:02:20 snapsnap systemd[1]: Failed to reset devices.list on /system.slice/dev-full.mount: Operation not permitted
Jun 16 12:02:20 snapsnap systemd[1]: Failed to reset devices.list on /system.slice/accounts-daemon.service: Operation not permitted
Jun 16 12:02:20 snapsnap systemd[1]: snap-core-1689.mount: Mount process exited, code=exited status=32
Jun 16 12:02:20 snapsnap systemd[1]: Failed to mount Mount unit for core.
-- Subject: Unit snap-core-1689.mount has failed
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit snap-core-1689.mount has failed.
--
-- The result is failed.
Jun 16 12:02:20 snapsnap systemd[1]: snap-core-1689.mount: Unit entered failed state.
Jun 16 12:02:20 snapsnap /usr/lib/snapd/snapd[337]: task.go:303: DEBUG: 2017-06-16T12:02:20Z ERROR [start snap-core-1689.mount] failed with exit status 1: Job for snap-core-1689.mount failed. See "systemctl status snap-core-1689.mount" and "journalctl -xe" for details.
Jun 16 12:02:20 snapsnap /usr/lib/snapd/snapd[337]: taskrunner.go:367: DEBUG: Running task 2 on Undo: Download snap "core" (1689) from channel "stable"
Jun 16 12:02:21 snapsnap /usr/lib/snapd/snapd[337]: handlers.go:204: Reported install problem for "core" as a6e1f2fe-528b-11e7-a696-fa163ebeb28a OOPSID
Jun 16 12:02:21 snapsnap snapd[337]: 2017/06/16 12:02:21.626068 handlers.go:204: Reported install problem for "core" as a6e1f2fe-528b-11e7-a696-fa163ebeb28a OOPSID

Required information

Distribution: Ubuntu 17.04
The output of "lxc info" or if that fails:
driver: lxc
driver_version: 2.0.8
kernel: Linux
kernel_architecture: x86_64
kernel_version: 4.10.0-23-generic
server: lxd
server_pid: 2214
server_version: "2.12"
storage: dir
storage_version: "1"

Information to attach

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

Did you install "squashfuse" prior to installing your snap package?

It's a known issue with snapd inside containers and one which is tracked by the snapd people upstream.

https://bugs.launchpad.net/snappy/+bug/1628289

There is no such package in Ubuntu 16.04
root@snapsnap:~# apt install squashfuse
...
E: Unable to locate package squashfuse

You may need to run "apt update" to update the package list.

Yes. After apt update squashfuse installe successfully. snap install micro --beta was ok too. Why ubuntu:16.04/amd64 comes not updated? I thought that these images are updated frequently.

The image is indeed updated every few weeks and the packages in the image are therefore up to date.
"apt update" doesn't update any actual package (that's what "apt upgrade" would do), instead it just updates the package index files which are used to look up packages.
Anyway, looks like things are working as is expected. Hopefully snapd will finally bundle squashfuse soon and then things will be even easier.

@stgraber the question is why ubuntu:16.04/amd64 comes with updated software but outdated indexes/

I'm not sure, my best guess is that since those index files expire pretty quickly and can be somewhat big, they may not be included in the image itself, instead relying on the user (or cloud-init) running the update.

How to find out the size of container? df seems to report params of the host system,
root@snapsnap:~# df
Filesystem     1K-blocks     Used Available Use% Mounted on
/dev/sda5       79458176 53099752  22299136  71% /
none                 492        0       492   0% /dev
udev             3801356        0   3801356   0% /dev/tty
tmpfs                100        0       100   0% /dev/lxd
tmpfs                100        0       100   0% /dev/.lxd-mounts
tmpfs            3828332        0   3828332   0% /dev/shm
tmpfs            3828332     8348   3819984   1% /run
tmpfs               5120        0      5120   0% /run/lock
tmpfs            3828332        0   3828332   0% /sys/fs/cgroup

After apt update:
root@snapsnap:~# df
Filesystem     1K-blocks     Used Available Use% Mounted on
/dev/sda5       79458176 53260384  22138504  71% /
none                 492        0       492   0% /dev
udev             3801356        0   3801356   0% /dev/tty
tmpfs                100        0       100   0% /dev/lxd
tmpfs                100        0       100   0% /dev/.lxd-mounts
tmpfs            3828332        0   3828332   0% /dev/shm
tmpfs            3828332     8348   3819984   1% /run
tmpfs               5120        0      5120   0% /run/lock
tmpfs            3828332        0   3828332   0% /sys/fs/cgroup

(22299136-22138504)/1024=156.87 Mb which seems to much, because image list:
+---------------------------------------------+---------+----------+-------------------------------+
|                 DESCRIPTION                 |  ARCH   |   SIZE   |          UPLOAD DATE          |
+---------------------------------------------+---------+----------+-------------------------------+
| ubuntu 16.04 LTS amd64 (release) (20170610) | x86_64  | 153.78MB | Jun 14, 2017 at 8:36pm (UTC)  |
+---------------------------------------------+---------+----------+-------------------------------+

Only ZFS and LVM will report the container size properly in "df -h". For everything else, your best bet is likely "du -sch /var/lib/lxd/containers/NAME/rootfs" on the host...

Well, I'd expect "du -schx /" inside the container to give you the right number too.

# du -schx /
606M    /
606M    total
# apt update
...
# du -schx /
763M    /
763M    total

(763-606)/606=0.26 - 26% increase is not that much, and I guess that people who need extra small images are using https://developer.ubuntu.com/core anyway.

Yeah, anyway, we don't have any control on that. Those images are the same Ubuntu images used for all cloud instances, not special LXD ones.

I am having this same issue.
system info
host: ubuntu 16.04.4
lxd: 3.0.0 snap
steps to reproduce
lxc launch images:ubuntu/16.04 nextcloud
lxc exec nextcloud -- apt install snapd -y
lxc exec nextcloud -- apt install squashfuse -y
lxc exec nextcloud -- snap install nextcloud

i have also tried to set the following configs for my lxc container:
lxc config set nextcloud security.privileged true
lxc config set nextcloud security.nesting true
lxc config set nextcloud raw.apparmor "fstype=squashfs,"

but I am still getting the error Mount snap "core" (4407) ([start snap-core-4407.mount] failed with exit status 1: Job for snap-core-4407.mount failed. See "systemctl status snap-core-4407.mount" and "journalctl -xe" for details.

i just ran lxc exec nextcloud -- apt install fuse -y and my problems appear to be solved for the most part: I ran into this error as well but running snap install nextcloud twice seems to have worked.

i just ran lxc exec nextcloud -- apt install fuse -y and my problems appear to be solved for the most part: I ran into this error as well but running snap install nextcloud twice seems to have worked.

source: gharchive/issue

authors: rhetr stgraber techtonik

repo: lxc/lxd

license_type: permissive

license_source: bigquery


text:
send a proper 404 for missing profiles

Signed-off-by: Tycho Andersen tycho.andersen@canonical.com

go fmt :)

source: gharchive/pull-request


text:
Backup: Fix regression of VM backup imports

When support was added for exporting/importing custom block volumes in https://github.com/lxc/lxd/pull/9300 this broke support for importing VM backups.
The good news is that the daily automated tests picked up the issue (https://jenkins.linuxcontainers.org/job/lxd-test-storage-vm/), the bad news is that we didn't see it in time.

Testsuite passed

authors: lxc-jenkins tomponline


text:
core & ios: implement typed configurations & template

Introduces a Configuration type which consumers will use to start instances of Envoy. This change allows us to:

Provide an ergonomic interface for using Envoy Mobile without having to learn Envoy's configuration YAML structure
Utilize a solid set of default settings for this library
Prevent consumers from accessing features that are unsupported
Validate configuration at compile time rather than runtime

This PR:

Adds a templated configuration in a .cc file, exposed through the common layer all the way through to the platform layers
Adds a Configuration type for accessing this configuration
Updates the iOS example apps to use the new typed configuration instead of their own yaml files
Maintains an existing initializer for exposing a string configuration for consumers who may still want this functionality

Tests will be added in a separate PR that updates this interface further with a builder for Envoy instances.
Resolves https://github.com/lyft/envoy-mobile/issues/169.
Signed-off-by: Michael Rebello me@michaelrebello.com

If we structure the configuration in swift we are opening up the gates for having to do the same in every language we want to support.

I outlined some of the concerns with a purely string-based approach in the linked issue, but to add some more color:

Envoy Mobile supports a small subset of the configurations that are available in upstream Envoy. This will likely always be the case, and going outside those configurations can cause undefined behavior at runtime. Using types can help alleviate this
Having consumers manually load configuration file resources and pass them to Envoy Mobile at runtime is additional overhead and can lead to bugs discovered at runtime instead of build time (invalid config files, mis-loading resources, etc.)
Envoy's current configurations are non-trivial and require a learning curve to be able to use them at all. The status quo of networking libraries on mobile generally requires little up-front configuration cost, and we should try to match that here to encourage wider adoption
Supporting this in each language (currently Swift/Kotlin) does amount to some overhead, but that can be said about every other aspect of the library as well (i.e., Envoy Mobile isn't all C++ 😄)

What are your thoughts about maintenance of this typed configuration approach?

Configs will be forwards compatible. Using a builder pattern on both platforms will allow us to add new defaults without making consumers update their code unless they want to take advantage of the new features
On the other hand, we can always deprecate/remove options from the configuration if necessary (especially pre-1.0), and consumers will find out at build time rather than when loading a config file at runtime

In summary: I think the reduced barrier to entry, ease of use, and simplicity of typed configurations far out-weighs the minimal maintenance cost this will incur.

Thanks for that explanation. It goes to show my bias from the far more complex land of service mesh configurations. I think all the reasons listed above really assuage any immediate concerns I have with this approach :)

Envoy's current configurations are non-trivial and require a learning curve to be able to use them at all. The status quo of networking libraries on mobile generally requires little up-front configuration cost, and we should try to match that here to encourage wider adoption.

This specially makes me agree with the approach taken here. And reminds me that a very similar pattern is being used in cronet; with, as you say here, a very small configuration surface.

I talked with @junr03 a bit about this offline. In general, while I think @junr03's concerns merit consideration, I tend to agree with @rebello95's points above. To summarize a couple of the things we discussed:
I think the challenges the Network Team has faced are a bit beyond the scope of what we'll encounter here. The configuration of Lyft's mesh is far more complex than our default template configuration will ever have to be.
The proto generation, serialization and deserialization that would be required to support the proto based approach is a fair amount of overhead, whereas string interpolation is cheap, and at least for a smaller set of configurable touch points, easy.
Finally, I think we can avoid the risks of implementing across languages by having the templating be well-documented. If this ends up being a pain point, we can also consider migrating templating logic down into the common layer at some point down the road.

Finally, I think we can avoid the risks of implementing across languages by having the templating be well-documented. If this ends up being a pain point, we can also consider migrating templating logic down into the common layer at some point down the road.

Yep I think documenting this is very valuable, and we can also use upstream Envoy's comprehensive docs as a point of reference here too. I also think it's useful to allow consumers to instantiate Envoy Mobile instances using raw string files (which is maintained in this PR), for those who are interested in doing something ultra-customized.

Implementation looks great; just a couple minor suggestions.

repo: lyft/envoy-mobile

license_source: github-api


text:
Pass command-line arguments

TL;DR
Pass command-line arguments
Type

[x] Bug Fix
[ ] Feature
[ ] Plugin

Are all requirements met?

[ ] Code completed
[ ] Smoke tested
[ ] Unit tests added
[ ] Code documentation added
[ ] Any pending items have an associated Issue

Complete description
Tracking Issue
https://github.com/lyft/flyte/issues/167
Follow-up issue

@kumare3 can you review the PR?

@kumare3 can you review the PR?

Hey @evalsocket, can you rebase and make sure tests are green?

Hey @evalsocket, can you rebase and make sure tests are green?

@EngHabu pr is ready

@EngHabu pr is ready

authors: EngHabu evalsocket

repo: lyft/flytepropeller


text:
Opus support by default

Currently Opus support can be only enabled trough changing Sdpinfo.cpp. Are there any reasons why Opus support is not enabled by default? It seems that this has been a topic before, no problems were mentioned, but Opus is still disabled.
this issue is a follow up to PR https://github.com/ging/licode/pull/67#issuecomment-52152607
If this can't be considered, some kind of parameterized compilation with a list of enabled codecs would be a nice feature.

I think that this can be closed, it seems that https://github.com/lynckia/licode/blob/master/scripts/rtp_media_config_default.js solves this task (though I could not find a documentation on this)

repo: lynckia/licode

license: mit


text:
Performance: lazyloading of units/equipments image

When showing the units page:

When showing the inventory page:

This is a crazy amount of request!
To greatly reduce the number of request made, and to improve performance in browser, this PR implements lazy loading of units and equipments image.
With lazy loading, units page:

With lazy loading, inventory page:

Of course, if the user scroll all the way down, all image will be loaded. But at least the first display will not overload the browser. This is especially true for mobile users.
The great library lazyload is used to implement this.

Thanks a lot, it's a great improvement !
My server will thank you at the next big banner XD

repo: lyrgard/ffbeEquip

license: ISC


text:
添加功能建议

搜索框每次退出，上次搜索的记录都没了，建议添加搜索记录

重复：https://github.com/lyswhut/lx-music-desktop/issues/135

authors: liugongding lyswhut

repo: lyswhut/lx-music-desktop


text:
🛑 影视4 is down

In 54656b9, 影视4 (https://fei.lzhpri.tk) was down:

HTTP code: 0
Response time: 0 ms

Resolved: 影视4 is back up in 10711e0 after 11 minutes.

repo: lzh-zone/lin-uptime

license: MIT


text:
🛑 影视4 is down

In d7d8bef, 影视4 (https://fei.lzhpri.tk) was down:

HTTP code: 0
Response time: 0 ms

Resolved: 影视4 is back up in 40ce3de after 7 minutes.


text:
Setting a shortcut for exit

I'm trying to set ^D to the exit function.
Set-PSReadlineKeyHandler -Key Ctrl+d `
                         -BriefDescription "Exit" `
                         -LongDescription "Exit" `
                         -ScriptBlock {
    param($key, $arg)

    exit
}

But when I set this up, it end up with exception:
Exception:
System.Management.Automation.ExitException: System error.
   at System.Management.Automation.Interpreter.ThrowInstruction.Run(InterpretedFrame frame)
   at System.Management.Automation.Interpreter.EnterTryCatchFinallyInstruction.Run(InterpretedFrame frame)
   at System.Management.Automation.Interpreter.EnterTryCatchFinallyInstruction.Run(InterpretedFrame frame)
   at System.Management.Automation.Interpreter.Interpreter.Run(InterpretedFrame frame)
   at System.Management.Automation.Interpreter.LightLambda.RunVoid1[T0](T0 arg0)
   at System.Management.Automation.ScriptBlock.InvokeWithPipeImpl(ScriptBlockClauseToInvoke clauseToInvoke, Boolean createLocalScope, Dictionary`2 functionsToDefine, List`1 variablesToDefine, ErrorHandlingBehavior errorHandlingBehavior, Object dollarUnder, Object input, Object scriptThis, Pipe outputPipe, InvocationInfo invocationInfo, Object[] args)
   at System.Management.Automation.ScriptBlock.<>c__DisplayClassa.<InvokeWithPipe>b__8()
   at System.Management.Automation.Runspaces.RunspaceBase.RunActionIfNoRunningPipelinesWithThreadCheck(Action action)
   at System.Management.Automation.ScriptBlock.InvokeWithPipe(Boolean useLocalScope, Dictionary`2 functionsToDefine, List`1 variablesToDefine, ErrorHandlingBehavior errorHandlingBehavior, Object dollarUnder, Object input, Object scriptThis, Pipe outputPipe, InvocationInfo invocationInfo, Object[] args)
   at System.Management.Automation.ScriptBlock.DoInvoke(Object dollarUnder, Object input, Object[] args)
   at PSConsoleUtilities.PSConsoleReadLine.<>c__DisplayClass66.<ProcessOneKey>b__64()
   at PSConsoleUtilities.PSConsoleReadLine.<>c__DisplayClass62.<CalloutUsingDefaultConsoleMode>b__61()
   at PSConsoleUtilities.PSConsoleReadLine.CalloutUsingDefaultConsoleMode[T](Func`1 func)
   at PSConsoleUtilities.PSConsoleReadLine.ProcessOneKey(ConsoleKeyInfo key, Dictionary`2 dispatchTable, Boolean ignoreIfNoAction, Object arg)
   at PSConsoleUtilities.PSConsoleReadLine.InputLoop()
   at PSConsoleUtilities.PSConsoleReadLine.ReadLine(Runspace remoteRunspace, EngineIntrinsics engineIntrinsics)
-----------------------------------------------------------------------

Is there a way to do it other way? I, so far, resulted to calling [Environment]::Exit(0), but that's dead slow.

Try
Set-PSReadlineKeyHandler -Chord 'Ctrl+d' -Function DeleteCharOrExit

It works great for me...

I know about this one. I just don't like the deleting char part. :)

Yeah, it's a little weird - but some people expect it.
Try this:
Set-PSReadlineKeyHandler -Key Ctrl+d `
                         -BriefDescription "Exit" `
                         -LongDescription "Exit" `
                         -ScriptBlock {
    param($key, $arg)

    [PSConsoleUtilities.PSConsoleReadLine]::RevertLine()
    [PSConsoleUtilities.PSConsoleReadLine]::Insert('exit')
    [PSConsoleUtilities.PSConsoleReadLine]::AcceptLine()
}

authors: cincuranet gwojan lzybkr

repo: lzybkr/PSReadLine


text:
Addition of Sub-navigation & Breadcrumbs

Please NOTE - This pull request builds upon https://github.com/m-lab/m-lab.github.io/pull/14 and should be merged in after that PR.
It includes the addition of the sub-navigation & breadcrumbs to the site's conversion.  A preview of this functionality can be seen on my [staging site] (http://andrew-m-lab.github.io/)  Below are additional notes for the items completed with this pull request:

[x] Addition of sub-navigation for the about and visualizations sub-pages.  In order to edit or add new sub-navigations, one can simply edit hierarchy in the _data/header-footer-content.yml file.  If adding a new sub-navigation for an existing landing page the sub-navigation's title will need to equate to the key on an individual landing page's breadcrumb front-matter value.
[x] Addition of breadcrumbs for all landing and sub-pages.

This does NOT include the breadcrumbs for the observatory page.  This will be added once https://github.com/m-lab/m-lab.github.io/pull/15 is merged as there is a dependency there.
This does NOT include the breadcrumbs for the blog pages.  This will be added once the blog layout and pages are completed.

[x] Also, minor fix for several page <title> tags so that they match what is on the current site.

LGTM @shredtechular

authors: critzo shredtechular


text:
Add 10 year wrap up blog post

@georgiamoon This PR adds the 10 year wrapup post and associated files. Also has one change to the notebook from a previous post where the github folder structure has since been modified.
Note that the github pages preview shows some formatting inconsistencies. Not sure why this is happening but I suspect it's because we're now using Jekyll modules that don't build correctly on github pages. Previewing the changes locally confirms the final site output is formatted fine.

This change is

One quick comment, and then I also wanted to add a lede photo, but we can do that as a follow up post.

authors: critzo georgiamoon


text:
MakeTicker -> NewTicker

Just a name change

This change is

Pull Request Test Coverage Report for Build 1079

1 of 2 (50.0%)  changed or added relevant lines in 1 file are covered.
10 unchanged lines in 3 files lost coverage.
Overall coverage decreased (-0.5%) to 79.295%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

ndt7/measurer/measurer.go
1
2
50.0%

Files with Coverage Reduction
New Missed Lines
%

ndt5/protocol/protocol.go
2
83.78%

ndt5/web100/web100_linux.go
2
94.52%

ndt5/c2s/c2s.go
6
73.21%

Totals

Change from base Build 1073:
-0.5%

Covered Lines:
1574

Relevant Lines:
1985

💛  - Coveralls

authors: coveralls pboothe

repo: m-lab/ndt-server


text:
Disconnect doesn't disconnect a microphone

Context
OS: Windows 11 10.0.22631.3007
The version of the ToothTray: ToothTray v0.2
Bluetooth headsets that were tested: Jabra Evolve 75e, Sony WH-1000XM5
Problem description
After disconnecting an audio device using the ToothTray, the device doesn't disconnect completely - the microphone is still left connected:
Streps to reproduce

Connect to the headset device via the ToothTray or via Bluetooth & devices Windows dialog
Audio and Microphone get connected.

Disconnect the device via ToothTray
Only the audio part of the device is disconnected. The microphone is still left connected.

As pointed out by a comment in the linked issue, this app was designed to only enumerates audio capture devices (shown as stereo devices).
Can you confirm if this is a Win 11 specific issue? When I was testing on Win 10, connecting a headset won't automatically connect its mic. The mic is connected only when the device is selected as a hands-free device in Windows

@m2jean,

this app was designed to only enumerates audio capture devices (shown as stereo devices).

Thank you for the explanation. However, on Windows 11, at least, if I connect the headset using the ToothTray the microphone gets connected as well. Then, when I disconnect, only the audio part of the device is disconnected. I have updated the Streps to reproduce section to make this clearer.

Can you confirm if this is a Win 11 specific issue?

Unfortunately, I don't have Windows 10 to test if ToothTray works there.

this app was designed to only enumerates audio capture devices

Could you please consider adding a feature to ToothTray to connect/disconnect a microphone for headset devices?

@m2jean,
Your advice to use eAll in the BluetoothAudioDeviceEnumerator::EnumerateAudioDevices() function worked.
Thank you very much for the solution.
I have adopted your implementation in my BluetoothDevicePairing utility: AudioDeviceEnumerator.cs

@PolarGoose I haven't gotten a chance to try it out myself with a Win 11 machine but glad it works


text:
Pairing characters and strings

This is the only extension I know which pairs $ correctly in LaTeX.
However, in LaTeX we pair \[ with \] and \left( with \right), etc. How can this be accomplished here, and without interfering with the pairs ( and )?

This feature can't be accomplished here because autoclose.nvim only supports single character pairs. However, it could be done with treesitter. I'll study this in the future.

I decide to not add this feature because the implementation of it is complicated and may cause more new issues. The philosophy of autoclose.nvim is being stable and minimal. If you want this feature you can use nvim-autopairs instead.


text:
Getting crash in android 10

in.mayanknagwanshi.imagepicker.ImageSelectActivity}: java.lang.IllegalArgumentException: Couldn't find meta-data for provider with authority com.indiatalent.provider
at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:3520)
at android.app.ActivityThread.handleLaunchActivity(ActivityThread.java:3659)
at android.app.servertransaction.LaunchActivityItem.execute(LaunchActivityItem.java:83)
at android.app.servertransaction.TransactionExecutor.executeCallbacks(TransactionExecutor.java:140)
at android.app.servertransaction.TransactionExecutor.execute(TransactionExecutor.java:100)
at android.app.ActivityThread$H.handleMessage(ActivityThread.java:2245)
at android.os.Handler.dispatchMessage(Handler.java:107)
at android.os.Looper.loop(Looper.java:227)
at android.app.ActivityThread.main(ActivityThread.java:7835)
at java.lang.reflect.Method.invoke(Native Method)
at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:492)
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:980)
Caused by: java.lang.IllegalArgumentException: Couldn't find meta-data for provider with authority com.indiatalent.provider
at androidx.core.content.FileProvider.parsePathStrategy(FileProvider.java:606)
at androidx.core.content.FileProvider.getPathStrategy(FileProvider.java:579)
at androidx.core.content.FileProvider.getUriForFile(FileProvider.java:417)
at in.mayanknagwanshi.imagepicker.imagePicker.ImagePicker.getCaptureImageOutputUri(ImagePicker.java:150)
at in.mayanknagwanshi.imagepicker.imagePicker.ImagePicker.getPickImageChooserIntent(ImagePicker.java:93)
at in.mayanknagwanshi.imagepicker.imagePicker.ImagePicker.start(ImagePicker.java:76)
at in.mayanknagwanshi.imagepicker.ImageSelectActivity.onCreate(ImageSelectActivity.java:46)
at android.app.Activity.performCreate(Activity.java:7974)
at android.app.Activity.performCreate(Activity.java:7963)
at android.app.Instrumentation.callActivityOnCreate(Instrumentation.java:1307)
at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:3495)
at android.app.ActivityThread.handleLaunchActivity(ActivityThread.java:3659)
at android.app.servertransaction.LaunchActivityItem.execute(LaunchActivityItem.java:83)
at android.app.servertransaction.TransactionExecutor.executeCallbacks(TransactionExecutor.java:140)
at android.app.servertransaction.TransactionExecutor.execute(TransactionExecutor.java:100)
at android.app.ActivityThread$H.handleMessage(ActivityThread.java:2245)
at android.os.Handler.dispatchMessage(Handler.java:107)
at android.os.Looper.loop(Looper.java:227)
at android.app.ActivityThread.main(ActivityThread.java:7835)
at java.lang.reflect.Method.invoke(Native Method)
at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:492)
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:980)

Hi @pankajjangid ,
this seems like a manifest merge issue.
does your app override the file provider in manifest?

What if I need my file provider separate for other functionality?
Is there a solution available thay I can use separate file provider in my manifest?

yes @pankajjangid ,
I have pushed an update for that. you should be able to do that with 1.0.6
Let me know if the issue still persists

authors: maayyaannkk pankajjangid

repo: maayyaannkk/ImagePicker


text:
Failed to launch App on Xcode 11 "Invalid top-level type in JSON write"

Hello,
I have a problem with this line in R.generated when i launch my app since Xcode 11 :
fileprivate static let applicationLocale = hostingBundle.preferredLocalizations.first.flatMap(Locale.init) ?? Locale.current
I have this error :
*** Terminating app due to uncaught exception 'NSInvalidArgumentException', reason: '*** +[NSJSONSerialization dataWithJSONObject:options:error:]: Invalid top-level type in JSON write'
*** First throw call stack:
In my app i have only one language "fr".
Somebody can help me ?
Thanks

This specific line hasn't changed in R.swift since Xcode 11. Also, R.swift doesn't doe anything with JSON serialisation.
Are you sure this error is caused by R.swift?

Yes, when i changed this specific line in
fileprivate static let applicationLocale = Locale.current
it's work

I have more informations :
It's crash when i use strings with params

static func homePageTtl(_ value1: String, preferredLanguages: [String]? = nil) -> String {
guard let preferredLanguages = preferredLanguages else {
let format = NSLocalizedString("homePageTtl", bundle: hostingBundle, comment: "")
return String(format: format, locale: applicationLocale, value1)
}
    guard let (locale, bundle) = localeBundle(tableName: "Localizable", preferredLanguages: preferredLanguages) else {
      return "homePageTtl"
    }

    let format = NSLocalizedString("homePageTtl", bundle: bundle, comment: "")
    return String(format: format, locale: locale, value1)
  }

The crash occurs at this line:

return String(format: format, locale: applicationLocale, value1)

The problem is that the code does not take the good initializer of Locale in Locale.init
It seems to take Locale.init(from: Any) who expects to have a dictionary while you pass him a String. We must slightly modify the line to specify the initializer that we want:
Locale.init(identifier: $0)
Which give :
fileprivate static let applicationLocale = hostingBundle.preferredLocalizations.first.flatMap({Locale.init(identifier: $0)}) ?? Locale.current
Can you check on your side and make a fix accordingly?

Does it actually work if you change the generated code to that?
What error are you getting? A compile time error, or a runtime crash?
Because I don't see how Locale.init(from: Decoder) could compile, if we give it a String.

Yes it's work.
It's a runtime crash.
It's not Locale.init(from: Decoder) but Locale.init(from: Any). I think it's the new default initializer in Swift 5.1 : https://github.com/apple/swift-evolution/blob/master/proposals/0242-default-values-memberwise.md

I don't think its related to the memberwise initializer. That doesn't take an Any, or generates an optional initializer.
Is your Any initializer perhaps an extension from some library in your code? I'm not seeing it in documentation (or in my own autocomplete).

Oh yes you're right.
it comes from the SweeterSwift library which has an extension of Decodable with init?(from: Any)
Is it possible for you to add an explicit initializer to avoid this problem?

Yes we can change that.
As well as look through other code where we don't have explicit method signatures. To prevent other such issues for people who have libraries that include Any overloads.

Thank you very much !
Do you have any idea of deadlines to have a new version available with this hotfix?

Thank you very much for your responsiveness. We look forward to the release because it is blocking each of my builds that I disable the automatic generation.

authors: damienb tomlokhorst


text:
Geometry manager layout

[ ] Fix resize quirks/Tao [1]

[1] At least the way I have it packaged, even if I modify the group, all resizing takes the group in the same direction (i.e. making larger and smaller does the same thing

repo: macMikey/scanhammer


text:
problems

[ ] LICENSE
[ ] electron -> electron-prebuilt

suggest： https://github.com/mikaelbr/node-notifier

done

authors: leungwensen xudafeng

repo: macacajs/torch


text:
Only 1 blind showing

I downloaded the app and have 8 blinds and added them all to homekit fine, and then now only 1 blind appears and I don't see the remaining 7. I get this log error:
11/8/2023, 9:38:49 AMSunsa BridgeLoaded plugin 'homebridge-sunsa'
11/8/2023, 9:38:49 AMSunsa BridgeLoading 1 platforms...
11/8/2023, 9:38:50 AMSunsa BridgeBridge is running on port 51846.
11/8/2023, 9:38:50 AMSunsa BridgeSunsaFound Device: Bedroom
11/8/2023, 9:38:50 AMSunsa BridgeSunsaAdding new accessory: Bedroom
11/8/2023, 9:38:50 AMSunsa BridgeWARNINGunhandled rejection: Error: UNKNOWN: unknown error, open '/var/lib/hoobs/sunsabridge.accessories/cachedAccessories'
I have Sunsa version 1.1.1
Hoobs version 4.3.0
Node: 16.20.2
Homebridge: 1.6.0
Using the MacOS App

Unfortunately I am not familiar with HOOBS. But according to the error message it looks like it is having a hoobs specific problem retrieving the cached accessories. I would personally remove the sunsa devices that are not showing up from the cache and see if that resolves the issue. You can check here to see how to remove individual cached accessories https://support.hoobs.org/docs/60e0c685646faaa152f10dd8.


text:
bug: message from previous execution is showing

There seems to be a bug where when you move between executions, there's sometimes a row from the previous execution hanging as the first row in the output.

I guess what we should do is to put a clear after the first message after of the freshly subscribed Observable.

Hey @cburgdorf I know this one has been hanging here for quite a while...
You don't have a reproducible by any chance? I'm trying to reproduce it without luck.

authors: PascalPrecht cburgdorf

repo: machinelabs/machinelabs


text:
JsonValue::Number(f64::INFINITY) prints invalid JSON

It gets printed as inf. Similar for f64::NEG_INFINITY.

@dtolnay let me use this issue to thank you a lot for all the effort reporting this stuff! It's pretty great help :).

authors: dtolnay maciejhirsz

repo: maciejhirsz/json-rust


text:
Fixed some typos

Just some typos fixed.

Thanks!

authors: FlorianWilhelm maciejkula

repo: maciejkula/spotlight


text:
Improvement:  FromPropertyList overloads which accept CF::Data

Again, nice to parse blobs!

FromPropertyList takes a path. You can use FromPropertyListString, which takes a std::string, when you have the property list data.
Note that CF::Data declares a cast operator for std::string, so you can simply:
CF::Dictionary::FromPropertyListString( CF::Data( cfDataObject ) );

Declaring a specific overload would cause some ambiguity between CF::Data and std::string.
That being said, FromPropertyListData could be OK.

Thanks for the tip regarding the cast operator, nice!
Looking at the implementation, wouldn't this imply a lot of to and froing ? '''CF::Data''' to '''std::string''' when casting, then in the implementation of '''FromPropertyList( std::string )''', from the string back to '''CF::Data'''?

Yup, sure...
I think I'll go with FromPropertyListData, as this will be straightforward and will remove the ambiguity.

Added in b485abcc6bbf40f11f04f80a6192cfa47a423ffe.

authors: gregzo macmade

repo: macmade/CFPP


text:
some updates and fixes

ERROR! 'become' is not a valid attribute for a TaskInclude
should be fixed
added a variable scala_version so that it is easier to switch and also added a variable confluent_distribution because oss is now community ;)

Thank you for your contribution :D


text:
[Aborted (core dumped)] commit 3b553d3548f44708e4fa9ddd80b45bae2ba756e3

New build - Ubuntu 20.04.2 Server. Fresh compile.
[P1] Table 2 took 1060.64 sec, found 4294961225 matches
[P1] Table 3 took 1639.5 sec, found 4294933574 matches
[P1] Table 4 took 2379.71 sec, found 4294894330 matches
terminate called after throwing an instance of 'std::runtime_error'
  what():  thread failed with: input not sorted
Aborted (core dumped)```

#46

hm that fix from #46 is already in commit 3b553d3548f44708e4fa9ddd80b45bae2ba756e3
could be unstable RAM

could be unstable RAM

The RAM is not overclocked or underclocked. I will run a memtest later today.

I went in front of the server this morning, as I could not ssh after the reboot last night. Anyway, bunch of I/O errors on /dev/sdb. I will check the drives for bad sectors.

that could be the cause indeed, if you don't use ramdisk

Closing this issue.

authors: Dartellum grayfallstown madMAx43v3r


text:
Cheapo SSL cert not trusted.

Looks like my 5 buck a year certificate from SSLS.COM is throwing some sort of error when hitting Home-Assistant.

[2016-11-23T20:54:36.146Z] Brooklyn DASH pressed.
[2016-11-23T20:54:36.559Z] there was an error
{ [Error: unable to verify the first certificate] code: 'UNABLE_TO_VERIFY_LEAF_SIGNATURE' }
/home/pi/dasher/lib/dasher.js:46
    if (response && response.statusCode < 200 || response.statusCode > 299) {
                                                         ^

TypeError: Cannot read property 'statusCode' of undefined
    at Request.onResponse [as _callback] (/home/pi/dasher/lib/dasher.js:46:58)
    at self.callback (/home/pi/dasher/node_modules/request/request.js:186:22)
    at emitOne (events.js:77:13)
    at Request.emit (events.js:169:7)
    at Request.onRequestError (/home/pi/dasher/node_modules/request/request.js:845:8)
    at emitOne (events.js:77:13)
    at ClientRequest.emit (events.js:169:7)
    at TLSSocket.socketErrorListener (_http_client.js:259:9)
    at emitOne (events.js:77:13)
    at TLSSocket.emit (events.js:169:7)

it looks like this require module might fix the issue for people with broken chains (as in my case).
https://github.com/Daplie/node-ssl-root-cas
Any Shot of incorporating this fix?
Thanks

I actually just combined all my certs..  All is good now..

I'm having a similar issue. My cert is good, but doesn't work at home as my OnHub router doesn't do NAT loopback, so I have to use the IP address to access the server. Any other ways of fixing this with an option through dasher to just accept the bad cert?

repo: maddox/dasher


text:
default language selection on config.php page not working properly

If default language = german is chosen, the app still starts using the english version.

Default_Language works only if you have the Use_Multi_Language_Selector = off.
Else the cookie will say what Language is the selected one.
In case it is a fresh start and you do not have any cookie yet then the Browser string will give as the Language.
Uncomment line 81 in class.language.php to check your Browser string.

authors: ChristianStrotkoetter madnetdev

repo: madnetdev/regmon-os


text:
Read project fail

Game name: Zombieville2_v1.6.1
Engine version: 5.4.0b21
Platform: Android
File name: globalgamemanagers
Error message: Read 232 but expected 220 for asset type GraphicsSettings
Stack trace:    在 uTinyRipper.SerializedFile.ReadAsset(AssetReader reader, AssetInfo assetInfo, Int64 offset, Int32 size)
在 uTinyRipper.SerializedFile.ReadAsset(AssetReader reader, ObjectInfo& info)
在 uTinyRipper.SerializedFile.ReadData(Stream stream)
在 uTinyRipper.GameProcessorContext.ReadFile(SerializedFile file)
在 uTinyRipper.GameProcessorContext.ReadSerializedFiles()
在 uTinyRipper.GameStructureProcessor.ProcessSchemes(GameCollection fileCollection)
在 uTinyRipper.GameStructure.Load(List1 pathes, LayoutInfo layinfo)    在 uTinyRipper.GameStructure.Load(IEnumerable1 pathes, LayoutInfo layinfo)
在 uTinyRipperGUI.MainWindow.LoadFiles(Object data)

uTinyRipper has been discontinued. Better use AssetRipper.

repo: mafaca/UtinyRipper


text:
Use Object.assign to ensure opts isn't mutated

Some users may re-use the opts object passed as a parameter,
which results in surprising behaviour protocol errors after multiple
calls to .replicate() eg. random errors such as:
Only 128 feeds currently supported.
Remote sent invalid feed message
Remote message is larger than 8MB (max allowed)
There was also an instance of the opts object in the constructor
being mutated as well, so added an Object.assign for that as well.

Here was the original gist from the #dat irc channel that exhibited the issue:
https://gist.github.com/fsteff/62afca979806bfbca1ced9bd3b0d7563

@reconbot Object.freeze() is a great idea. I just tried it, but it seems it only throws if I add 'use strict'; into the code. The funny thing is that without 'use strict'; - the freeze actually makes the test pass!

3.4.0 !

authors: jimpick mafintosh

repo: mafintosh/hyperdb


text:
[spike] WireGuard VPN protocol research

Please analyze the documentation for WireGuard protocol and see what are the different ways a wireguard connection could be established.
We were introduced to peer to peer config, but that requires that each peer knows each-other public IPs. This will be difficult to overcome in Gateway usecase, as Gateways are behind NAT.
Please experiment with a local setup.

It is hard to estimate this task. We are setting 8 for a start, but it could take less/more.

Summary of the findings so far:

Only one of the peers need to know the others endpoint establish connection
PeersistentKeepalive option can be used to negate address change effects

authors: jkmar xbend

repo: magma/domain-proxy


text:
print self.performance_interval instead of hardcoded 10

It's just minor change to don't confuse the ones who are looking into the example.

Thanks for the pull request, and welcome! The MaidSafe team is excited to review your changes, and you should hear from @chandraprakash (or someone else) soon.
If any changes to this PR are deemed necessary, please add them as extra commits. This ensures that the reviewer can see what has changed since they last reviewed the code. The way GitHub handles out-of-date commits, this should also make it reasonably obvious what issues have or haven't been addressed. Large or tricky changes may require several passes of review and changes.
Please see CONTRIBUTOR.md for more information.

Nice, one thanks for this

Review status: 0 of 1 files reviewed at latest revision, all discussions resolved, all commit checks successful.

Comments from the review on Reviewable.io

authors: Nonius dirvine maidsafe-highfive

repo: maidsafe/crust


text:
How to use "Pipeline" - Build  Pipelines / Releases

Describe the issue
Have had several errors when trying to use the same technique as "Pipeline" for CI.  CD is not working.
**Extension **
Power BI Action: Publish
Publisher - Maik van der Gaag
Installed version - 5.4.31 (Latest)
Last updated - Mar 28, 2022 at 3:05 AM EDT
To Reproduce
Building a new pipeline (Release) section.
Create Release
Deploy - and the "TEST/PROD" versions are not loading into the workspace(s).
Pipelines works!
Releases does not.
Expected behavior
Expected this to push to TEST/PROD as the stages are layed out.
Situation (please complete the following information):

Agent type:   Release
Authentication:  "Service Connection"
Extension Version:

Log info
Attached.
2022-04-27_Log.txt
Additional information
Add any other context about the problem here.

Hi @DerekLedbetter,
As the Source file isn't correct the extension is not finding any files. This property should point to the powerbi file / files you can use wild card inclusing for example *.pbix

Hi @maikvandergaag ,
thanks for replying.  I tried changing it and it worked.  However, nothing updated.
THE CI is working great.  We built 3 pipelines.  However, according to Microsoft, one is supposed to be build for "DEV", the CD (Release) is built for TEST/ PROD.
Attached are the logs as I saw no change in the RELEASE version.
in TEST - Source - $(System.DefaultWorkingDirectory)/*.pbix - However, nothing moved.
ReleaseLogs_14 (1).zip

The stage is still not finding reports. Please make sure that you set it up correctly. The output should show the reports it is working on. If you share a log file please also make sure you send one when the system.debug variable is set to true

Any update on your issue

I can’t figure out how to get the “extension” to work with the “Release pipeline”.  It is working GREAT with the Pipelines!
Please send a sample if possible so I can resolve this quickly.
@.***
@.***
Should the source be the “source artifact”?
From: Maik van der Gaag @.>
Sent: Monday, May 9, 2022 7:45 AM
To: maikvandergaag/msft-extensions @.>
Cc: Ledbetter, Derek @.>; Mention @.>
Subject: [External Email]Re: [maikvandergaag/msft-extensions] How to use "Pipeline" - Build Pipelines / Releases (Issue #398)
Any update on your issue
—
Reply to this email directly, view it on GitHubhttps://secure-web.cisco.com/1-voSvMHYHhR0bdTzzZNK4xlpWeEPucuCz49D-ji1upQ8oyzuNpC7BCD7hUHzkOSlxBoFoovgoQxJKrruRO8NOW2d4wdECJW_0mfbpbm8oOeQu-xBS68nnTnFlC32GIGtYoantzsRyJOWqFt3cZP9dQbJ1iUj86mA7fHYSSWmxMnsTsB6t-VIzei_lS4pU7PGClYJh638Fbzj9zYYV5sHOwrr7K9-30zoSMDvscTvHkC1x63PmSBFih2y57G7yLOuPvBJ1jVYGO0Lxyr_EG3pPL74AQC6gu8tGz2lF5D3tf06j3wFz7LJSxi6OgwrMdn342laGzz-Om9iAJ8Lf2OxZQu3qEr6mWwHcnxDXHUAOlNjLD5pIkWSuqi_YMd_Q2cTt7c_mY_nfncAEzXrn2QbcA/https%3A%2F%2Fgithub.com%2Fmaikvandergaag%2Fmsft-extensions%2Fissues%2F398%23issuecomment-1120993523, or unsubscribehttps://secure-web.cisco.com/1VFRfhiiZbKMNuqVuMF_arWUoZ9j-e3p4dFUbk2gEQd_OW0akODZXkvNWGV1Eja0J4FCOa0Dfq8z_FT24DxTEtYSIibdZU2lW3e_FnMMV-r2YuvWVZjnHOAsX_u3JxwE0xCvJOIqDsUfmi8_LnbamIuaDw7k7MYOQKJmDhOFEs9gFOAPQbtgYxAaXVrDSgA68Fg_OPAo6YXor13rKDanovxZhNpzSbwx8wpkJxe8tTVRsIVfOi00V5jyTj-jPR4cyh4rH8aHiRuKMRWmDLfEb86fv8FelHL7hQ_wbZi_2PdCLCfp-qD2LnLrTdlxJiFYpHNZYsccsTRJofDn0gV6wU0vwMvUo_oia5W5W18xmSeImKm8ioymVs3oiU1lDMqzdlwpZnzsv_y98GA_klyw5yA/https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAJSRQC6S4CIUC6TCW77NEGTVJD3D5ANCNFSM5UO22L2A.
You are receiving this because you were mentioned.Message ID: @.***>
NOTICE: This message may contain confidential information intended only for the recipient.  If you have received this communication in error, please notify the sender immediately by replying to the message and deleting it from your computer.

doesn’t matter what I put, same error.
@.***
From: Maik van der Gaag @.>
Sent: Monday, May 9, 2022 7:45 AM
To: maikvandergaag/msft-extensions @.>
Cc: Ledbetter, Derek @.>; Mention @.>
Subject: [External Email]Re: [maikvandergaag/msft-extensions] How to use "Pipeline" - Build Pipelines / Releases (Issue #398)
Any update on your issue
—
Reply to this email directly, view it on GitHubhttps://secure-web.cisco.com/1-voSvMHYHhR0bdTzzZNK4xlpWeEPucuCz49D-ji1upQ8oyzuNpC7BCD7hUHzkOSlxBoFoovgoQxJKrruRO8NOW2d4wdECJW_0mfbpbm8oOeQu-xBS68nnTnFlC32GIGtYoantzsRyJOWqFt3cZP9dQbJ1iUj86mA7fHYSSWmxMnsTsB6t-VIzei_lS4pU7PGClYJh638Fbzj9zYYV5sHOwrr7K9-30zoSMDvscTvHkC1x63PmSBFih2y57G7yLOuPvBJ1jVYGO0Lxyr_EG3pPL74AQC6gu8tGz2lF5D3tf06j3wFz7LJSxi6OgwrMdn342laGzz-Om9iAJ8Lf2OxZQu3qEr6mWwHcnxDXHUAOlNjLD5pIkWSuqi_YMd_Q2cTt7c_mY_nfncAEzXrn2QbcA/https%3A%2F%2Fgithub.com%2Fmaikvandergaag%2Fmsft-extensions%2Fissues%2F398%23issuecomment-1120993523, or unsubscribehttps://secure-web.cisco.com/1VFRfhiiZbKMNuqVuMF_arWUoZ9j-e3p4dFUbk2gEQd_OW0akODZXkvNWGV1Eja0J4FCOa0Dfq8z_FT24DxTEtYSIibdZU2lW3e_FnMMV-r2YuvWVZjnHOAsX_u3JxwE0xCvJOIqDsUfmi8_LnbamIuaDw7k7MYOQKJmDhOFEs9gFOAPQbtgYxAaXVrDSgA68Fg_OPAo6YXor13rKDanovxZhNpzSbwx8wpkJxe8tTVRsIVfOi00V5jyTj-jPR4cyh4rH8aHiRuKMRWmDLfEb86fv8FelHL7hQ_wbZi_2PdCLCfp-qD2LnLrTdlxJiFYpHNZYsccsTRJofDn0gV6wU0vwMvUo_oia5W5W18xmSeImKm8ioymVs3oiU1lDMqzdlwpZnzsv_y98GA_klyw5yA/https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAJSRQC6S4CIUC6TCW77NEGTVJD3D5ANCNFSM5UO22L2A.
You are receiving this because you were mentioned.Message ID: @.***>
NOTICE: This message may contain confidential information intended only for the recipient.  If you have received this communication in error, please notify the sender immediately by replying to the message and deleting it from your computer.

Source path should be linked to a file. I'm not aware what your file structure is within your pipeline

$(System.DefaultWorkingDirectory) refers to the file system of your repo. The source file it self should point to one or more pbix files.

I've tried this many times and getting the same error.
Please assist.
From: Maik van der Gaag @.>
Sent: Monday, May 16, 2022 4:22 AM
To: maikvandergaag/msft-extensions @.>
Cc: Ledbetter, Derek @.>; Mention @.>
Subject: [External Email]Re: [maikvandergaag/msft-extensions] How to use "Pipeline" - Build Pipelines / Releases (Issue #398)
$(System.DefaultWorkingDirectory) refers to the file system of your repo. The source file it self should point to one or more pbix files.
—
Reply to this email directly, view it on GitHubhttps://secure-web.cisco.com/1T4AoJkuXa_ey9qhyyQt4_e1hkQ8R1Ehx4B4K8nMmNuOHZS_Cr2hhVh408poy17ZXNFHeAl-ZWbqK9nUOH0bJInAK32EkYV8TR60Pxu7bFYoxDQLzqqrs6b0GYwpoeM_k6L7A5ygt9EpAFE62AhTJhsm_HAjazQDCbK1RRwHI2h6V4TG9Cwfy8xCfoYdFq013laNTmUdAZVtJHrFooQALKZon_3Lfx3kitAIbZTvBTGyPJzYrVrjRFTnM9V-v9nlQd9tLhP30bMjv9ocSgWOzlzL12wIQ9VxfHBiqm8RGXPGtb1_kPVekAW135yfy9ngRPk74vJBdtD5u8_jnqu7AX92uWozj3ClkdPdH5HitIOVBiyZPirRwZAg75LoktrvB5x4o8Qo3_A5YpeyayuMZbA/https%3A%2F%2Fgithub.com%2Fmaikvandergaag%2Fmsft-extensions%2Fissues%2F398%23issuecomment-1127375104, or unsubscribehttps://secure-web.cisco.com/1H1xd4xu_Vu98CArblo_CxvLaXkp3TVUvS7hKA00p6PZuHHcWlJ-J2IeeWMTh1b1dqeb4FMUYJi-mFe8fbZ8kh5SRJ0pfTtxhBnVvVxdDNyZ-z1BA3gKnEp94TXDyuCG1A-eOtJsK8RyPZrDb6YqPVJeR4MAWzZwNFZ9JWv9rIuMIF_4D0mbsmd9_Vmq_KUFXmCc4i4wKeY_7AnreiUZsIfU9PCQf7aRgzRIuppw4Ijlrl9fd1p3veleHBLK6R5ZZGLpeF-H09s4Up1zmG9UVjAjQnaKMY2UDg25efUGW968uN5i1YMVGXFdXkDG-8NeOJDMl2GiwUrvP7Bs_srFkzMH_P9YEjMzPjdIcDTvB9r13T_NXNnBZGh9Hmq2uCkLmxoBuC0pBsHgzf6FOBTRM2Q/https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAJSRQCZNMUUPESYXKCYNXUTVKIAULANCNFSM5UO22L2A.
You are receiving this because you were mentioned.Message ID: @.@.>>
NOTICE: This message may contain confidential information intended only for the recipient.  If you have received this communication in error, please notify the sender immediately by replying to the message and deleting it from your computer.

@DerekLedbetter Technically there is not much different from a CI / CD pipeline. The main difference are the tasks and the references to the filepaths. If it works for CI it should also work for your CD. What are the differences between those two?

Please don’t close.
Let’s setup a meeting so I can get the CD portion working.
I am still requesting assistance.
From: Maik van der Gaag @.>
Sent: Thursday, June 16, 2022 3:13 PM
To: maikvandergaag/msft-extensions @.>
Cc: Ledbetter, Derek @.>; Mention @.>
Subject: [External Email]Re: [maikvandergaag/msft-extensions] How to use "Pipeline" - Build Pipelines / Releases (Issue #398)
Closed #398https://secure-web.cisco.com/1FppiaMeB_yf7TEmx6U5fYFXmjTOqRgjmjho86HHIEHGIwKFwpnqbxrnRVy57bN4Bzg67fIuZHyZUQRDdkKHINljejEzjSbRgM1NqFsgl6FGFeL1KLyR9BRXz-X0C6OEn4KXFmfpmVwStfa_CU9YTT1ajS5rneHnL1PipcGJJpzMbWChrm7LcB8XfaeFpBGyXMonbNzxpbL6SG4Cd_9Kuw3fS5q_JtmYuzVRHM_8Qfdgs2WBzoN2lTlEW9i4eapnNlAiA0zF88T2JRwXL0FALoFxhI_f4tkgvpcB7JejBQBPQmwNj_dQZUBWDbXnSPjavsooUde4fx-pNtSXaZH9SStwySFlL9cce7xEzkBIrnG_NZqFj7oTjCwxAe8FsBau2rWrcqnJfN1eSJYYdnCbvFA/https%3A%2F%2Fgithub.com%2Fmaikvandergaag%2Fmsft-extensions%2Fissues%2F398 as completed.
—
Reply to this email directly, view it on GitHubhttps://secure-web.cisco.com/1hG3E8IGb1bl_rLGQoFc9-Ndv3aSeaKh9nR9jAc1PjXR3g810y5BX114zv2g2FEluoO5AS_h2pTJSR3VHRdI-JUHEMKJRiSI7c3wbJuE3sQ7369TFJ3NoeD-XFA5iNl8mUT3hG3lcN7dOPUpUeq9cc3vqaD9Agh9OUlYX3r-6JyX2bwnSqMeNCNH7SJ8zcUjRXJYWvUBslUD1ZfEZ8zzFcdcWI1zXVeRBlZj8IBZcOJQQHse_sHu1d4NV9qH1hm3pgH43nooH_xhElTqEG9IcmB3TeS-sqW1ECM_tM3o36WW3DSrib0ZVJibJH-aTmcIYsK1nnqfhdldoN0T_K0Br4VLXEG1B8RRJBsycw-zovwtktRBSRDXSksxoZ8OYUAtV8CA389y6myKF0Lnb2rfNhg/https%3A%2F%2Fgithub.com%2Fmaikvandergaag%2Fmsft-extensions%2Fissues%2F398%23event-6823447862, or unsubscribehttps://secure-web.cisco.com/1wijIj1_VGgtjJRQfqbBb4TaVHfCglSJdA1cq6KLrnkubDmtGbruw_PdtJyN01GWED_KY_Tz6cN_yLiWPeDetCSGW1nZfHVD4bcnz9T7GwbwgaeynuKXvTENDCQ-ypfs8t9OAmTAuZEYmEIdTzCtxknAtXZzhjixbUhKCObr9SIRObv7TO11PG7JnnrpTZv4fMMyi69CI0F5DyJdmzDWoh6cP0UwVuhDeKKJZAOLBbTyM1vRqM3qsTrLKI8cdck4qlEnAZWJlZTl1q5GCmzwIJgeXConAltuB0DkjDWVv8NTgZD9Rb7e1AjPya2GP7YbaR6dOppRJFD04DCzhUZdS-rj1wk7Q6t2MDQ1lBoE417fY0PBpPr-oz8KdRb4tu7ztmRPMT38e4RlFZ04B9jaqvQ/https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAJSRQC7E6KIGSY7VSHPYDO3VPN4CLANCNFSM5UO22L2A.
You are receiving this because you were mentioned.Message ID: @.@.>>
NOTICE: This message may contain confidential information intended only for the recipient.  If you have received this communication in error, please notify the sender immediately by replying to the message and deleting it from your computer.

Ok, @DerekLedbetter will reopen as there was no response for 20 days. I closed it. it should work on both portions. so we need to look at your setup.

Please give me some dates times for a meeting (I'm on the East Coast USA).  Currently the time is 16:00.

sorry very busy, just send a invite I will see if it works

Info @ msftplayground . com
Groet,
Maik van der Gaag
From: DerekLedbetter @.>
Sent: Tuesday, 28 June 2022 16:27
To: maikvandergaag/msft-extensions @.>
Cc: Maik van der Gaag @.>; State change @.>
Subject: Re: [maikvandergaag/msft-extensions] How to use "Pipeline" - Build Pipelines / Releases (Issue #398)
Please let me know the email I should send the invite.
From: Maik van der Gaag @.mailto:***@***.***>
Sent: Monday, June 27, 2022 5:34 PM
To: maikvandergaag/msft-extensions @.mailto:***@***.***>
Cc: Ledbetter, Derek @.mailto:***@***.***>; Mention @.mailto:***@***.***>
Subject: [External Email]Re: [maikvandergaag/msft-extensions] How to use "Pipeline" - Build Pipelines / Releases (Issue #398)
sorry very busy, just send a invite I will see if it works
—
Reply to this email directly, view it on GitHubhttps://secure-web.cisco.com/1O22NeeNAN7rO4yubXfe1lWd3ltz9mXQ5iO588nDQo3dnxNBtmkznx3AZ8PVek4IGGXeHaZBxNFsAOCIjPwX88TWG7HUg888C632TM6mdZeLY2YMuvITQTsZpvzGBq-DL1-ujaWCEwxdj0HJsgZDrYj-EqH1uhsUerMG8YjnqBCBpfSZ4FJogzQ4qLxII5az5J7CxmYlV5ValekZXF1IYfawgK2xxudH6GPa_1tSdidR_SaS1_GNMiUvHnYzJf92N6XfXT-L8kw9ibBzqtphF9ijvxxaNsKBhxF12aZ0wzD39kOI9Ntgr4OgrGqW6kemTlqWOd4MHVyy4MIkbELbxumxmAc1Q_hPF9Hrj0g_HpagLN_m_r_IlCEtAvf4bqZopMGF8_OPHChs8YKawoMPydQ/https%3A%2F%2Fgithub.com%2Fmaikvandergaag%2Fmsft-extensions%2Fissues%2F398%23issuecomment-1167929039, or unsubscribehttps://secure-web.cisco.com/12fsThlQjP5uraYEgvS2tophJp8ByDW-zWfBu11OuNs6GWuDvyGOOuMeFvCveliUnD1E4PvgJn5UmA1YRdNSStU-oMpOlV6wSlDHflUuGxRX8_3OPxmNluNzaCMxfad1vhjH2R1jAeIzV_20T-sndfdC7yGI_q2bmPlwqBQPTnKTcGRKwpy6OPjgBgP019TVlgOR45wBRXu9KJVDUDQdnMl7RMgtB_SC-ikX3horpae9ex4LM5q9rvqEsd9SJe1yrnO5THSLEX6JNiEbHeRDTZF3GHwhzqal5aKKveD47sMGKC3bWtm3YzQmKfyyzOXDdVmtVKSOadEEj3V98umztm_EoRGhI4HSbdqG20GWKpm-T0j3Wj36f1rx0abdMN2H_XZ5E4lRQAejkZkIKqFLDGg/https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAJSRQCZ3TGHSUT35XX4ISCLVRIM3ZANCNFSM5UO22L2A.
You are receiving this because you were mentioned.Message ID: @.@.mailto:***@***.******@***.***>>
NOTICE: This message may contain confidential information intended only for the recipient. If you have received this communication in error, please notify the sender immediately by replying to the message and deleting it from your computer.
—
Reply to this email directly, view it on GitHubhttps://github.com/maikvandergaag/msft-extensions/issues/398#issuecomment-1168798068, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ACIXAE6FPJSTR2UKDCFUV6DVRMDUBANCNFSM5UO22L2A.
You are receiving this because you modified the open/close state.Message ID: @.@.>>

Closing this issue as everything was discussed

I’d like to setup a meeting for us to get together and work through the “Release” pipeline with the extension.
From: Maik van der Gaag @.>
Sent: Thursday, June 16, 2022 3:55 PM
To: maikvandergaag/msft-extensions @.>
Cc: Ledbetter, Derek @.>; Mention @.>
Subject: [External Email]Re: [maikvandergaag/msft-extensions] How to use "Pipeline" - Build Pipelines / Releases (Issue #398)
Reopened #398https://secure-web.cisco.com/1teNroWovC7VWtaaU5DQyqI2sf1yzp87KL6r-LTMvhYgMsC6WoMTkJOgaueQKXIGsQ-K9CUD2mD1Wmub1mjDk7-ETkgv982Bq1IeLq6g1nRuotb-xPM2A7wfOzm4L8ArFVcphlhWKaX6yq4Vov9e0c1K-9Y3BV5TYpKlAZQUVNZaIukDCNi247EgHqCZaN5AEsi5O7STo3YhP1naSHunM9yTeQPAW9NBglxYint9MacApbh2YFnx1h8S7wyXCb4cdi5-ATuc9v_cipXoV5Qf-cw0KBZM25wo83CUc-4-ThbrOanRr8N9YOETtad3UU7714skcZIz3sqKnzpZ1r6rY8EowtvMSx14-jqLAC3edSmhvAy5P_hHYfL3Y8Aj2-lzA8l8Hwsjs9CG6Kr3dcNdSNg/https%3A%2F%2Fgithub.com%2Fmaikvandergaag%2Fmsft-extensions%2Fissues%2F398.
—
Reply to this email directly, view it on GitHubhttps://secure-web.cisco.com/1OH3l9coyl3p_4OZBte-caeNI8j0-hOMsrGDBWFDNJAsMiT1LrZjQ0uOMPOGKzOfXSX8ac1HPyCg1K2ahXTcNFyWjjMUfubHa6y9uQs84w3gaEhBmMNW_LeMKyyKJCfo43N_PFqn-xtcd7rKzQfeKtJlFTi9qbiJOYeJ6EDnKiJ7ZQCZNGe-DIgCSyLgHtcGY4iYpeJc_pm-FxC6Frv7-1slg532cnW1ncu0sheWj3SJNP78eZvqvD1ZvS7Cxwm4jKtC3bfYDbmfOj7gY20Pb8YAEsUtGoJNotWLPLz4CQwcXTLJKyc2BtuYh4H-Pv4a_75hrLH4VWS-dFOn7rDzOV9BX92eSalVuQVFbCULWFqTC4ECLxsTryi1qSe-guPzOLZhk9V2ec0pKYjOb0FMNZg/https%3A%2F%2Fgithub.com%2Fmaikvandergaag%2Fmsft-extensions%2Fissues%2F398%23event-6823665847, or unsubscribehttps://secure-web.cisco.com/1-AYREcUmToDr6xKwNCDORSoMrbxd8E5EjgLERDtCv8GMLD_VSS0vQqiYmT9Ed1Bfv6WKoKmrQhL2DFgPQzDgxjpbJXwLLJSa51jPmp2x4izpQtuCoEYM65hzVfzs8K74uTFACGZDfYlNlK61Lb8To7uAwFyTVayqaPa7hFCUHhIauLp0SW455uGLvS7ptxGnAgFC7aGFc-VdORYSqkobySfOE7Hn6n8f-6Mz1k4jPxwFXqeJFwgCSAOYwM5FqKzJDGcLij_Lat-ddtVJSaIA5BmXk7-WmcSGNVyXcrkGkRXvR2KiR_wKcB6NGX3z7j6Tmz0a8NxyUtgvxOYxBrd631EMxkeVgHznCuYRg92TYnk-poYho-jBHMX4hOZQWEDM6PwV09LD4DGYs3STdSjsFw/https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAJSRQC3PKUTBJFRKSRTIYEDVPOBCHANCNFSM5UO22L2A.
You are receiving this because you were mentioned.Message ID: @.@.>>
NOTICE: This message may contain confidential information intended only for the recipient.  If you have received this communication in error, please notify the sender immediately by replying to the message and deleting it from your computer.

authors: DerekLedbetter maikvandergaag

repo: maikvandergaag/msft-extensions


text:
PHP Configuration hints

I had loads of trouble trying to get MailHog (with or without mhsendmail) to work with php-fpm (MacOS, homebrew, php5.6, mailhog 0.2)
I finally got it going with this in php.ini:
sendmail_path = "/usr/local/bin/mailhog sendmail test@example.org"
I can do a PR to add that simple recipe to the docs if you'll direct me where to put it.
(I do see that hint in https://github.com/mailhog/mhsendmail/issues/3#issuecomment-127992203, which is where I got it, but that was closed.)

mailhog/mhsendmail#3 should have fixed it, assuming you have a To: header in the message
It could be worth adding some documentation to mention it - PHP config is mentioned in the (mhsendmail)[https://github.com/mailhog/mhsendmail]) readme, but currently without the e-mail address in the path

Hmm, maybe a new release for mhsendmail is the key fix?
Note that I couldn't get mailhog 0.2.0 to work without the gratuitous test@example.com, but it works fine with it.

It might be that (really need to fix #71!), but if you've tried the MailHog sendmail one then it should use the latest mhsendmail for whichever version of MailHog you have installed
I'll do a new release after I've got through some open issues, hopefully that'll fix it!

OK, thanks for your work on this. MailHog is awesome. A real step forward in my dev workflow. Love the "delete all".

Thanks @rfay, and no problem, glad its useful :smile:

A tip to anyone wondering how to use Mailhog if it's running on a separate instance (not the php server) - for example on a separate docker container.
All you need to do is modify the sendmail_path on php server to include -S option:
sendmail_path = /usr/sbin/sendmail -S mail:1025 -t

Where "mail" is the alias of my container running Mailhog.

:+1: thanks for the info, I've added the info to the MailHog README including a php.ini example

I would like to add that using sendmail in debian docker containers seem to have issues. A good replacement is ssmtp.
Install using apt install ssmtp
ssmtp can be configured to use mailhog by editing /etc/ssmtp/ssmtp.conf like so:
root=yourmail@mail.com
# replace mailhog with the name of the mailhog service
mailhub=mailhog:1025
hostname=yourserver.example.com
FromLineOverride=YES

PHP can then be configured in php.ini like so:
sendmail_path = /usr/sbin/ssmtp -t
Some more details on ssmtp can be found here
This worked for me. I hope someone finds it useful

authors: Feyisayo SlayerBirden ian-kent rfay

repo: mailhog/MailHog


text:
OSSM-5596:Skip Web Assembly IBM P/Z

https://master-jenkins-csb-servicemesh.apps.ocp-c1.prod.psi.redhat.com/job/maistra/job/maistra-test-tool/1143/,
Web Assembly IBM P/Z is not supported for the IBM P/Z platform.
     Error from server (NotFound): namespaces "3scale" not found

reformatted the code to skip the test case properly.

Test case run successfully: https://master-jenkins-csb-servicemesh.apps.ocp-c1.prod.psi.redhat.com/job/maistra/job/maistra-test-tool/1146/console.

repo: maistra/maistra-test-tool


text:
Instructions to run the code

Hi! It looks like we're trying to solve a similar problem. I'm new to poetry, is it possible to add a few instructions to the README to get it up and running?

Sure! I'll see what I can do. I need to get back in here when I get time to clean things up. 😉

authors: joshuamarkovic major

repo: major/yotagrabber


text:
cant solve integration

Describe the bug

A clear and concise description of what the bug is.

Possible solution

Describe the solution you thought of.

Screenshots

I am requesting You to permit me to work on this issue.

repo: makesmatheasy/makesmatheasy


text:
Window headers aren't changed in latest EAP

Also, since I'm writing about this kind of windows, is that possible to remove that light line on top (or make it optional)? I believe that line is there because it's in Material guidelines, but it really doesn't look good in IDEA:

Environment
PyCharm 2017.3 EAP (Professional Edition)
Build #PY-173.2941.3, built on October 3, 2017
PyCharm EAP User
Expiration date: November 2, 2017
JRE: 1.8.0_152-release-1012-b1 x86_64
JVM: OpenJDK 64-Bit Server VM by JetBrains s.r.o
Mac OS X 10.12.6

Fixed

Thanks!
But what about that line on top?

I don't know but either way I'm not adding features at the moment.

authors: mallowigi roboslone

repo: mallowigi/material-theme-jetbrains-eap


text:
Using with Fragments (Icon dialog must have a callback.)

I try to use this library with fragment and apply as in example
override val iconDialogIconPack: IconPack?         get() = (requireActivity().application as App).iconPack

And in onViewCreat
`
val iconDialog = requireActivity().supportFragmentManager.findFragmentByTag(ICON_DIALOG_TAG) as IconDialog?
?: IconDialog.newInstance(IconDialogSettings())
    button_icons.setOnClickListener {
        iconDialog.show(requireActivity().supportFragmentManager, ICON_DIALOG_TAG)
    }

`
when I try click button I have this exception
E/AndroidRuntime: FATAL EXCEPTION: main
Process: com.example.mjet, PID: 8467
java.lang.IllegalStateException: Icon dialog must have a callback.

Did you implement the callback in your activity or fragment? If you check the example, you'll see that the activity implements the IconDialog.Callback interface and the onIconDialogIconsSelected method, which is needed to allow the dialog to send results.

I implements in fragment also I implements IconDialog.Callback interface and the onIconDialogIconsSelected method

It is work now I change supportFragmentManager to childFragmentManager
Thank you

authors: ahmed-ms maltaisn

repo: maltaisn/icondialoglib


text:
Incompatibility with Lunar Client when new Sodium 0.6.+ versions are present (MC 1.21-1.21.4)

When I try to use this mod with Lunar Client and the new Sodium 0.6.+ versions my game spawns the Mojang Loading Screen and for some reason my game gets stuck loading forever.
When I don't have the newest Sodium 0.6.+ versions it works fine but still spawns the Mojang Logo (Loading Screen) which Lunar disabled for a smoother transition.
It would be great to have something that detects if a player is playing with Lunar Client and have the Mojang Loading screen disabled!
I believe this is a bug created by this fix: #68
Steps to reproduce:

Install Lunar Client
Go to Versions tab
Select Version 1.21.3
Select Lunar + Fabric
Go to Version Settings
Click the Folder Icon named Open Mods Folder
Download FerriteCore version ferritecore-7.1.0-hotfix-fabric
Download Sodium version mc1.21.3-0.6.5-fabric and add it to the mod folder you have opened
Start the game
Observe (The Mojang Screen is loading forever)

Screenshots:

Affected Lunar Client Minecraft Versions: 1.21 to 1.21.4 - This issue happens with any MC version that has any Sodium 0.6.+ version installed. For testing I recommend the mc1.21.3-0.6.5-fabric Sodium version on MC 1.21.3 with ferritecore-7.1.0-hotfix-fabric FerriteCore version.
Logs (no crash report since it doesn't crash just gets stuck at the Mojang Loading screen when starting so only game logs that contain me force closing at the end): https://mclo.gs/Rr7lrPl
Note: You can investigate with Lunar's built-in Mission Control (debug) feature:

#68

Will be fixed by Lunar!


text:
Nil checks -> guard

All nil checks on the superviews are now using guards. This makes sure you never have to force unwrap the variable.

Awesome! Two things:

Just read up on guard and I'm a fan, so thats awesome. I'm curious though to know if  guard let superview = superview is what we would want to test there? I know there's a distinction between guard and a normal if-statement, but if superview was nil, wouldn't nil == nil? You probably know more on this than I, so enlighten me if I'm mistaken.

It seems in the copy-paste process the function-specific error messages were lost. Any chance you could update the error log messages with what they were previously?

after a guard statement, the 'let' declaration is unwrapped for the scope it's contained in. I don't really understand what you mean with the nil==nil part, but it should be fine as it is now.

whoops! Will do.

Sorry, my question wasn't very clear, and as I was writing out a clarification I think I discovered what that actually does, so thanks for that!

Thanks!

authors: BasThomas mamaral

repo: mamaral/Neon