Container loses static IPv6 default route (interference from SLAAC)

Required information

Distribution: ubuntu
Distribution version: 16.04.2 (server, amd64)
The output of "lxc info"

config:
  core.https_address: '[::]:8443'
  core.trust_password: true
api_extensions:
- id_map
api_status: stable
api_version: "1.0"
auth: trusted
public: false
environment:
  addresses:
  - <IP_ADDRESS>:8443
  - '[XXXX:XXX:XXXX:XXXX::21]:8443'
  - <IP_ADDRESS>:8443
  - '[YYYY:YYY:YYYY:21::1]:8443'
  architectures:
  - x86_64
  - i686
  certificate: <SNIP>
  certificate_fingerprint: <SNIP>
  driver: lxc
  driver_version: 2.0.8
  kernel: Linux
  kernel_architecture: x86_64
  kernel_version: 4.4.0-83-generic
  server: lxd
  server_pid: 1402
  server_version: 2.0.10
  storage: btrfs
  storage_version: "4.4"

Issue description
A container is configured with a static IPv6 address and gateway:
iface eth0 inet6 static
address XXXX:XXX:XXXX:XXXX::32/64
gateway XXXX:XXX:XXXX:XXXX::1
privext 0
accept_ra 0
autoconf 0
dad-attempts 0

However after a period of time, the container drops its IPv6 gateway.
The container is bridged to the outside network where RAs and SLAAC are enabled; and as you can see, I have tried to disable its use in the container by setting accept_ra 0 and autoconf 0.  However it seems that RAs are the source of the problem, because:

If the upstream router is making RA's with a lifetime of 30 minutes, then default gateway is lost 30 minutes after the container starts
If I change the router to send RA's with a lifetime of 10 minutes, then default gateway is lost 10 minutes after the container starts

With RA lifetime of 30 minutes - when the container starts I see:
# ip -f inet6 route
XXXX:XXX:XXXX:XXXX::/64 dev eth0  proto kernel  metric 256  expires 2591998sec pref medium
fe80::/64 dev eth0  proto kernel  metric 256  pref medium
default via fe80::66d1:54ff:fe5b:e2dd dev eth0  proto ra  metric 1024  expires 1798sec pref medium

(Note that the manually-configured gateway XXXX:XXX:XXXX:XXXX::1 is not present; the only gateway is the link-local address from proto ra)
After a short time, the "expires ...." part of the LAN route disappears, but not for the gateway:
# ip -f inet6 route
XXXX:XXX:XXXX:XXXX::/64 dev eth0  proto kernel  metric 256  pref medium
fe80::/64 dev eth0  proto kernel  metric 256  pref medium
default via fe80::66d1:54ff:fe5b:e2dd dev eth0  proto ra  metric 1024  expires 1732sec pref medium

Then after 30 minutes I see:
# ip -f inet6 route
XXXX:XXX:XXXX:XXXX::/64 dev eth0  proto kernel  metric 256  pref medium
fe80::/64 dev eth0  proto kernel  metric 256  pref medium

... and the container loses its IPv6 connectivity to the outside world.
If I change the router to send RAs with 10 minute lifetime, then restart the container, I see:
# ip -6 route list
XXXX:XXX:XXXX:XXXX::/64 dev eth0  proto kernel  metric 256  pref medium
fe80::/64 dev eth0  proto kernel  metric 256  pref medium
default via fe80::66d1:54ff:fe5b:e2dd dev eth0  proto ra  metric 1024  expires 597sec pref medium

As a related problem, I find that the container picks up a SLAAC IPv6 address in addition to its manually-assigned one, despite having set autoconf 0.
root@lxd1:~# lxc list ns-auth
+---------+---------+---------------------+----------------------------------------------+------------+-----------+
|  NAME   |  STATE  |        IPV4         |                     IPV6                     |    TYPE    | SNAPSHOTS |
+---------+---------+---------------------+----------------------------------------------+------------+-----------+
| ns-auth | RUNNING | <IP_ADDRESS> (eth0) | XXXX:XXX:XXXX:XXXX::32 (eth0)                | PERSISTENT | 0         |
|         |         |                     | XXXX:XXX:XXXX:XXXX:216:3eff:fe27:fea9 (eth0) |            |           |
+---------+---------+---------------------+----------------------------------------------+------------+-----------+

My guess as to what's happening is:

The container interface is created with SLAAC/RAs enabled
The container static address and gateway are added
RA replaces the static gateway with a dynamic one
Acceptance of RAs is then disabled
The dynamic gateway expires

Note that this problem doesn't occur on the host, which is apparently configured in the same way (details below).  But actually, the host sees both its static default route and the one from RAs:
root@lxd1:~# ip -6 route | tail -2
default via XXXX:XXX:XXXX:XXXX::1 dev br255  metric 1024  pref medium
default via fe80::66d1:54ff:fe5b:e2dd dev br255  proto ra  metric 1024  expires 540sec pref medium

Steps to reproduce
The host needs to be connected to a network with IPv6 and SLAAC.
On the host (ubuntu 16.04) I have:
auto eth0
iface eth0 inet manual

auto br255
iface br255 inet static
bridge_ports eth0
bridge_stp off
bridge_fd 0
bridge_maxwait 0
address <IP_ADDRESS>/24
gateway <IP_ADDRESS>
dns-nameservers <IP_ADDRESS>
dns-search home.example.net

auto br255
iface br255 inet6 static
address XXXX:XXX:XXXX:XXXX::21/64
gateway XXXX:XXX:XXXX:XXXX::1
privext 0
accept_ra 0
autoconf 0
dad-attempts 0

The container was launched with -p br255 where this profile is:
config: {}
description: ""
devices:
  eth0:
    name: eth0
    nictype: bridged
    parent: br255
    type: nic
name: br255

In the container (ubuntu:16.04) I have:
auto eth0
iface eth0 inet static
address <IP_ADDRESS>/24
gateway <IP_ADDRESS>
dns-nameservers <IP_ADDRESS>
dns-search home.example.net

iface eth0 inet6 static
address XXXX:XXX:XXXX:XXXX::32/64
gateway XXXX:XXX:XXXX:XXXX::1
privext 0
accept_ra 0
autoconf 0
dad-attempts 0

There is no firewalling on the host, apart from the ACCEPT rules added by lxd itself:
# ufw status
Status: inactive

# ip6tables -L -n -v
Chain INPUT (policy ACCEPT 130K packets, 211M bytes)
 pkts bytes target     prot opt in     out     source               destination
    0     0 ACCEPT     tcp      lxdbr0 *       ::/0                 ::/0                 tcp dpt:53 /* managed by lxd-bridge */
    0     0 ACCEPT     udp      lxdbr0 *       ::/0                 ::/0                 udp dpt:53 /* managed by lxd-bridge */
    0     0 ACCEPT     udp      lxdbr0 *       ::/0                 ::/0                 udp dpt:67 /* managed by lxd-bridge */

Chain FORWARD (policy ACCEPT 0 packets, 0 bytes)
 pkts bytes target     prot opt in     out     source               destination
    0     0 ACCEPT     all      *      lxdbr0  ::/0                 ::/0                 /* managed by lxd-bridge */
    0     0 ACCEPT     all      lxdbr0 *       ::/0                 ::/0                 /* managed by lxd-bridge */

Chain OUTPUT (policy ACCEPT 70001 packets, 5275K bytes)
 pkts bytes target     prot opt in     out     source               destination

The host does have IPv6 forwarding enabled, and in /etc/default/lxd-bridge I have a separate routed subnet for the lxdbr0 bridge:
# IPv6
## IPv6 address (e.g. 2001:470:b368:4242::1)
LXD_IPV6_ADDR="YYYY:YYY:YYYY:21::1"

## IPv6 CIDR mask (e.g. 64)
LXD_IPV6_MASK="64"

## IPv6 network (e.g. 2001:470:b368:4242::/64)
LXD_IPV6_NETWORK="YYYY:YYY:YYYY:21::/64"

## NAT IPv6 traffic
LXD_IPV6_NAT="false"

# Run a minimal HTTP PROXY server
LXD_IPV6_PROXY="false"

Although the affected container is not using lxdbr0, I think this may be related, because on the host I see accept_ra=2 on the bridge interface.  Since I have not set this in sysctl.conf I suspect it was set by lxd.
root@lxd1:~# sysctl net.ipv6.conf.br255
net.ipv6.conf.br255.accept_dad = 1
net.ipv6.conf.br255.accept_ra = 2
net.ipv6.conf.br255.accept_ra_defrtr = 1
net.ipv6.conf.br255.accept_ra_from_local = 0
net.ipv6.conf.br255.accept_ra_min_hop_limit = 1
net.ipv6.conf.br255.accept_ra_mtu = 1
net.ipv6.conf.br255.accept_ra_pinfo = 1
net.ipv6.conf.br255.accept_ra_rt_info_max_plen = 0
net.ipv6.conf.br255.accept_ra_rtr_pref = 1
net.ipv6.conf.br255.accept_redirects = 1
net.ipv6.conf.br255.accept_source_route = 0
net.ipv6.conf.br255.autoconf = 0
net.ipv6.conf.br255.dad_transmits = 1
net.ipv6.conf.br255.disable_ipv6 = 0
net.ipv6.conf.br255.force_mld_version = 0
net.ipv6.conf.br255.force_tllao = 0
net.ipv6.conf.br255.forwarding = 1
net.ipv6.conf.br255.hop_limit = 64
net.ipv6.conf.br255.ignore_routes_with_linkdown = 0
net.ipv6.conf.br255.max_addresses = 16
net.ipv6.conf.br255.max_desync_factor = 600
net.ipv6.conf.br255.mc_forwarding = 0
net.ipv6.conf.br255.mldv1_unsolicited_report_interval = 10000
net.ipv6.conf.br255.mldv2_unsolicited_report_interval = 1000
net.ipv6.conf.br255.mtu = 1500
net.ipv6.conf.br255.ndisc_notify = 0
net.ipv6.conf.br255.proxy_ndp = 0
net.ipv6.conf.br255.regen_max_retry = 3
net.ipv6.conf.br255.router_probe_interval = 60
net.ipv6.conf.br255.router_solicitation_delay = 1
net.ipv6.conf.br255.router_solicitation_interval = 4
net.ipv6.conf.br255.router_solicitations = 3
sysctl: reading key "net.ipv6.conf.br255.stable_secret"
net.ipv6.conf.br255.suppress_frag_ndisc = 1
net.ipv6.conf.br255.temp_prefered_lft = 86400
net.ipv6.conf.br255.temp_valid_lft = 604800
net.ipv6.conf.br255.use_oif_addrs_only = 0
net.ipv6.conf.br255.use_tempaddr = 0

Other things tried
I tried setting on the host:
root@lxd1:~# sysctl net.ipv6.conf.default.autoconf=0
root@lxd1:~# sysctl net.ipv6.conf.default.accept_ra=0

and then stopping and starting the container.  This makes no difference: the container still gets a SLAAC address in addition to its static one, and the default gateway is still ticking away to expiry.
I tried commenting out all the extra settings inside the container:
#privext 0
#accept_ra 0
#autoconf 0
#dad-attempts 0

Again no difference, and indeed eth0.accept_ra was zero, although all.accept_ra and default.accept_are were both set to one.
root@ns-auth:~# sysctl -a | grep accept_ra
sysctl: permission denied on key 'fs.protected_hardlinks'
sysctl: permission denied on key 'fs.protected_symlinks'
sysctl: permission denied on key 'kernel.cad_pid'
sysctl: permission denied on key 'kernel.unprivileged_userns_apparmor_policy'
sysctl: permission denied on key 'kernel.usermodehelper.bset'
sysctl: permission denied on key 'kernel.usermodehelper.inheritable'
sysctl: reading key "net.ipv6.conf.all.stable_secret"
net.ipv6.conf.all.accept_ra = 1
net.ipv6.conf.all.accept_ra_defrtr = 1
net.ipv6.conf.all.accept_ra_from_local = 0
net.ipv6.conf.all.accept_ra_min_hop_limit = 1
net.ipv6.conf.all.accept_ra_mtu = 1
net.ipv6.conf.all.accept_ra_pinfo = 1
net.ipv6.conf.all.accept_ra_rt_info_max_plen = 0
net.ipv6.conf.all.accept_ra_rtr_pref = 1
sysctl: reading key "net.ipv6.conf.default.stable_secret"
net.ipv6.conf.default.accept_ra = 1
net.ipv6.conf.default.accept_ra_defrtr = 1
net.ipv6.conf.default.accept_ra_from_local = 0
net.ipv6.conf.default.accept_ra_min_hop_limit = 1
net.ipv6.conf.default.accept_ra_mtu = 1
net.ipv6.conf.default.accept_ra_pinfo = 1
net.ipv6.conf.default.accept_ra_rt_info_max_plen = 0
net.ipv6.conf.default.accept_ra_rtr_pref = 1
sysctl: reading key "net.ipv6.conf.eth0.stable_secret"
net.ipv6.conf.eth0.accept_ra = 0
net.ipv6.conf.eth0.accept_ra_defrtr = 1
net.ipv6.conf.eth0.accept_ra_from_local = 0
net.ipv6.conf.eth0.accept_ra_min_hop_limit = 1
net.ipv6.conf.eth0.accept_ra_mtu = 1
net.ipv6.conf.eth0.accept_ra_pinfo = 1
net.ipv6.conf.eth0.accept_ra_rt_info_max_plen = 0
net.ipv6.conf.eth0.accept_ra_rtr_pref = 1
sysctl: reading key "net.ipv6.conf.lo.stable_secret"
net.ipv6.conf.lo.accept_ra = 1
net.ipv6.conf.lo.accept_ra_defrtr = 1
net.ipv6.conf.lo.accept_ra_from_local = 0
net.ipv6.conf.lo.accept_ra_min_hop_limit = 1
net.ipv6.conf.lo.accept_ra_mtu = 1
net.ipv6.conf.lo.accept_ra_pinfo = 1
net.ipv6.conf.lo.accept_ra_rt_info_max_plen = 0
net.ipv6.conf.lo.accept_ra_rtr_pref = 1

So finally, I tried explicitly enabling acceptance of RAs:
privext 0
accept_ra 1
autoconf 0
dad-attempts 0

This did change the sysctl setting inside the container (net.ipv6.conf.eth0.accept_ra = 1), and now the default gateway is refreshed via RAs:
root@ns-auth:~# ip -6 route
XXXX:XXX:XXXX:XXXX::/64 dev eth0  proto kernel  metric 256  expires 2591891sec pref medium
fe80::/64 dev eth0  proto kernel  metric 256  pref medium
default via fe80::66d1:54ff:fe5b:e2dd dev eth0  proto ra  metric 1024  expires 491sec pref medium
root@ns-auth:~# ip -6 route
XXXX:XXX:XXXX:XXXX::/64 dev eth0  proto kernel  metric 256  expires 2591998sec pref medium
fe80::/64 dev eth0  proto kernel  metric 256  pref medium
default via fe80::66d1:54ff:fe5b:e2dd dev eth0  proto ra  metric 1024  expires 598sec pref medium

So this is a usable workaround, because the container doesn't lose connectivity. However I wanted to set a static gateway and not be reliant on RAs.

This is pretty odd. It's very unlikely to be a LXD issue in itself but I'll try to reproduce it and poke around to see what's going on exactly. You certainly shouldn't be getting an RA provided route when you have a static entry and disabled RAs in your container.

So I appear unable to reproduce this here with a basic Ubuntu 16.04 container.
/etc/network/interfaces:
root@test:~# cat /etc/network/interfaces
# This file describes the network interfaces available on your system
# and how to activate them. For more information, see interfaces(5).

# The loopback network interface
auto lo
iface lo inet loopback

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

iface eth0 inet6 static
    address 2001:470:b368:4242::32/64
    gateway 2001:470:b368:4242::1

Routes:
root@test:~# ip -6 route show
2001:470:b368:4242::/64 dev eth0  proto kernel  metric 256  pref medium
fe80::/64 dev eth0  proto kernel  metric 256  pref medium
default via 2001:470:b368:4242::1 dev eth0  metric 1024  pref medium

Looks like the above config did cause the usual sysctls to be set to sane values:
root@test:~# sysctl net.ipv6.conf.eth0.accept_ra
net.ipv6.conf.eth0.accept_ra = 0
root@test:~# sysctl net.ipv6.conf.eth0.autoconf
net.ipv6.conf.eth0.autoconf = 0

For comparison, a container without the /etc/network/interfaces modification on the same host gets this:
root@test1:~# ip -6 route show
2001:470:b368:4242::/64 dev eth0  proto kernel  metric 256  expires 3592sec pref medium
fe80::/64 dev eth0  proto kernel  metric 256  pref medium
default via fe80::ccfd:30ff:fe75:1546 dev eth0  proto ra  metric 1024  expires 1792sec hoplimit 64 pref medium
root@test1:~# sysctl net.ipv6.conf.eth0.accept_ra
net.ipv6.conf.eth0.accept_ra = 1
root@test1:~# sysctl net.ipv6.conf.eth0.autoconf
net.ipv6.conf.eth0.autoconf = 1

Marking the issue as Incomplete as I'm unable to reproduce the issue. I'll keep the container running for a few hours and see if maybe further RA cause it to reconfigure its default gateway.

OK, I'll try to make a standalone test case with a local bridge and radvd.  I suspect there is some sort of race involved.

I can replicate locally as follows.  This is on a low power machine (actually an ubuntu 16.04 VM, running inside a NUC DN2820 which is also ubuntu 16.04)
If the following steps don't work for you, I'll try to replicate in a t2.nano in EC2.
# On the host
brctl addbr brtest
ifconfig brtest up
ip -6 addr add 2001:db8:0:1::1/64 dev brtest
lxc profile create brtest
lxc profile edit brtest

---
config: {}
description: ""
devices:
  eth0:
    name: eth0
    nictype: bridged
    parent: brtest
    type: nic
name: brtest
---

apt-get install radvd
vi /etc/radvd.conf

---
interface brtest
{
        AdvSendAdvert on;
        MaxRtrAdvInterval 30;
        prefix 2001:db8:0:1::/64
        {
                AdvOnLink on;
                AdvAutonomous on;
        };
};
---

systemctl start radvd
lxc launch ubuntu:16.04 -p brtest test1
lxc exec test1 bash

# Now we're inside the container; use "ifconfig" to check
# a SLAAC address is obtained, e.g. 2001:db8:0:1:216:3eff:fe15:f2ca/64
# check that SLAAC address is obtained

vi /etc/network/interfaces.d/50-cloud-init.cfg

---
auto eth0
iface eth0 inet manual

iface eth0 inet6 static
address 2001:db8:0:1::1000/64
gateway 2001:db8:0:1::1
accept_ra 0
autoconf 0
privext 0
dad-attempts 0
---

exit

# Now we are back on the host
lxc stop test1
lxc start test1
lxc exec test1 bash

# Back inside the container:
# ip -6 route
2001:db8:0:1::/64 dev eth0  proto kernel  metric 256  pref medium
fe80::/64 dev eth0  proto kernel  metric 256  pref medium
default via fe80::fc22:cff:fe72:7b93 dev eth0  proto ra  metric 1024  expires 53sec hoplimit 64 pref medium

# ip -6 addr show dev eth0
17: eth0@if18: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 state UP qlen 1000
    inet6 2001:db8:0:1::1000/64 scope global
       valid_lft forever preferred_lft forever
    inet6 2001:db8:0:1:216:3eff:fe15:f2ca/64 scope global mngtmpaddr dynamic
       valid_lft 86094sec preferred_lft 14094sec
    inet6 fe80::216:3eff:fe15:f2ca/64 scope link
       valid_lft forever preferred_lft forever

The static default gw is missing
The RA default gw is counting down to zero and then negative. After it has got to expires -29sec the default gw vanishes entirely.
The container has a SLAAC address in addition to its manually-assigned address

This very much appears to be a race condition.  I can reproduce in EC2 on a t2.nano instance using the following script, but inside the container I need either to uncomment the post-up sleep 2 line, or change inet static to inet dhcp.  My underpowered home server doesn't need this.
#!/bin/sh -ex
# Reproducer for lxc/lxd #3582
# Run this script as root on a clean 16.04 VM

#### networking setup
apt-get -y install bridge-utils
cat <<EOS >/etc/network/interfaces.d/brtest.cfg
auto brtest
iface brtest inet static
  address        <IP_ADDRESS>/24
  bridge_ports   none
  bridge_stp     off
  bridge_fd      0
  bridge_maxwait 0

iface brtest inet6 static
  address        2001:db8:0:1::1/64
  autoconf       0
  privext        0
  accept_ra      0
  dad-attempts   0
EOS
ifup brtest

cat >/etc/sysctl.d/99-sysctl.conf <<EOS
# radvd won't start unless this is set
net.ipv6.conf.all.forwarding=1
EOS
sysctl -p /etc/sysctl.d/99-sysctl.conf

apt-get -y install radvd
cat <<EOS >/etc/radvd.conf
interface brtest
{
        AdvSendAdvert on;
        MaxRtrAdvInterval 30;
        prefix 2001:db8:0:1::/64
        {
                AdvOnLink on;
                AdvAutonomous on;
        };
};
EOS
systemctl stop radvd
systemctl start radvd

#### lxd setup
lxd init --auto --storage-backend=dir
lxc profile create brtest
lxc profile device add brtest eth0 nic name=eth0 nictype=bridged parent=brtest

### container setup
lxc launch ubuntu:16.04 -p brtest testv6
lxc file push - testv6/etc/cloud/cloud.cfg.d/99-disable-network-config.cfg <<EOS
network: {config: disabled}
EOS
lxc file push - testv6/etc/network/interfaces.d/50-cloud-init.cfg <<EOS
auto lo
iface lo inet loopback

auto eth0
iface eth0 inet static
  address       <IP_ADDRESS>/24
  gateway       <IP_ADDRESS>
  #post-up sleep 2

#iface eth0 inet dhcp

iface eth0 inet6 static
  address       2001:db8:0:1::100/64
  gateway       2001:db8:0:1::1
  accept_ra     0
  autoconf      0
  privext       0
  dad-attempts  0
EOS
lxc restart testv6

### Show the problems inside the container
sleep 5
echo "--- Container IPv6 routes ---"
lxc exec testv6 -- /sbin/ip -6 route
echo "--- Container IPv6 addresses ---"
lxc exec testv6 -- ip -6 addr show dev eth0

# 1. The static default gateway to 2001:db8:0:1::1 is missing
# 2. There is a "proto ra" default gateway to fe80::..., despite "accept_ra 0"
# 3. This RA default gateway expires after a few minutes, and since there
#    is no static gateway, the container loses its IPv6 connectivity
#    (this is the main issue)
# 4. eth0 has picked up a SLAAC address in addition to its static address,
#    despite "autoconf 0"

# IF THIS DOES NOT WORK:
# 1. Check that radvd is running.  Often it seems not to start for some reason.
# 2. Inside the container, run "tcpdump -i eth0 -nn icmp6" and check that RAs
#    are being received. (May not be shown until you hit ^C)
# 3. Try uncommenting "post-up sleep 2", or changing inet static to dhcp
#    (both of these slow down the container startup)

@stgraber: If you want access to the EC2 instance, please post or E-mail me your SSH public key.

Ok, so sounds like it's a race between the kernel and ifupdown. If the kernel gets the RA before ifupdown is run, then you end up with the default gateway configured by the RA rather than the static configuration you entered...
I wonder if putting:
pre-up ip -6 route flush dev eth0

In the inet6 section would fix the race.

I wonder if putting:
pre-up ip -6 route flush dev eth0

In the inet6 section would fix the race.

Interesting idea. I have tested it on my slow box, and what I find is that:

The container loses the /64 LAN route as well, so now it has only the RA default route and nothing else
root@apt-cacher:~# ip -6 route
default via fe80::66d1:54ff:fe5b:e2dd dev eth0  proto ra  metric 1024  expires 594sec pref medium

The container gets only a SLAAC address, and loses its static IP address
root@apt-cacher:~# ip -6 addr show dev eth0
25: eth0@if26: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 state UP qlen 1000
    inet6 XXXX:XXX:XXXX:XXXX:216:3eff:feaa:752d/64 scope global mngtmpaddr dynamic
       valid_lft 2591986sec preferred_lft 604786sec
    inet6 fe80::216:3eff:feaa:752d/64 scope link
       valid_lft forever preferred_lft forever

What I should probably do is test this with a "full fat" VM with sleep 2.  If it replicates that way, then it would suggest the race is inherent to debian/ubuntu startup scripts, and not related to running in lxd.

Well, LXD doesn't configure any of that kernel stuff, so we're really debating whether it's a kernel bug or an ifupdown bug at this point :)

I have added post-up sleep 2 under the inet section to a full-fat VM (actually the VM in which the lxd containers are running) and rebooted it.  I find the same problem:

the static default route is missing, there is only a temporary RA route
the VM has picked up a SLAAC address in addition to its static address

Arguably several things at play here.

In ifupdown, perhaps all the interface sysctl settings should be made before the interface is brought up. It seems that the interface is brought up during IPv4 initialization, and the IPv6 sysctls are not made until IPv6 initialization starts.  By that stage it's too late if we have things like default.accept_ra=1 and default.autoconf=1
I can't see why the static default route is getting dropped: either the "gateway" setting is being ignored if there's already an RA default route, or the gateway is being added but the RA default route is ripping out the static one.

I'm not sure where best to raise this though.  Ubuntu launchpad? Debian?

https://launchpad.net/ubuntu/+source/ifupdown/+filebug for Ubuntu. Though the problem is likely to be the same in Debian so maybe going upstream makes sense here.
As a workaround, you could put a pre-up in the ipv4 section which sets the sysctl keys directly. This should have them all set properly prior to the device coming up.

As a workaround, you could put a pre-up in the ipv4 section which sets the sysctl keys directly

Great idea... but I just tried it and it doesn't work.
A thought.  Is it possible that with lxd at least, the eth0 interface is already 'up' before ifupdown gets a look-in?
If I put in the inet section
pre-up /var/tmp/fixit.sh

and this script contains
#!/bin/sh -xe
exec >/tmp/fixit.log 2>&1
ifconfig eth0
sysctl net.ipv6.conf.eth0.accept_ra

then the result is:
+ ifconfig eth0
eth0      Link encap:Ethernet  HWaddr 00:16:3e:aa:75:2d
          inet6 addr: XXXX:XXX:XXXX:XXXX:216:3eff:feaa:752d/64 Scope:Global
          inet6 addr: fe80::216:3eff:feaa:752d/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:12 errors:0 dropped:0 overruns:0 frame:0
          TX packets:7 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:1098 (1.0 KB)  TX bytes:586 (586.0 B)

+ sysctl net.ipv6.conf.eth0.accept_ra
net.ipv6.conf.eth0.accept_ra = 1

Notice how the interface is already UP by the time pre-up is called. (And even has its SLAAC address already).

Ah, yeah, that'd make sense. I believe those veth pair are already up by the time the container starts up.
So maybe you need to bring it down and back up too to avoid the race? :)

OK, that works: if I run as a pre-up script
ifconfig eth0 down
sysctl net.ipv6.conf.eth0.accept_ra=0
sysctl net.ipv6.conf.eth0.autoconf=0

then everything is fine.  What a palaver.  (Aside: whose idea was it to put IPv6 address autoconfiguration into the kernel anyway?? :-)
BTW, I did also try setting net.ipv6.conf.default.autoconf=0 and net.ipv6.conf.default.accept_ra=0 on the host, hoping that when the veth/eth pair was created, they would inherit these settings. But they don't. In fact, if I look inside the container, I see:
root@apt-cacher:~# sysctl net.ipv6.conf.default.accept_ra
net.ipv6.conf.default.accept_ra = 1
root@apt-cacher:~# sysctl net.ipv6.conf.default.autoconf
net.ipv6.conf.default.autoconf = 1

But outside, on the host:
root@apt-cacher:~# exit
root@lxd1:~# sysctl net.ipv6.conf.default.accept_ra
net.ipv6.conf.default.accept_ra = 0
root@lxd1:~# sysctl net.ipv6.conf.default.autoconf
net.ipv6.conf.default.autoconf = 0

So even the concept of default settings, to be inherited by newly created interfaces, is virtualised inside the container - and defaults to the autoconf nonsense turned on.  We need a tunable default for the default! :-)
Back to lxd. I see this:
func (c *containerLXC) createNetworkDevice...
...
        // Handle bridged and p2p
        if shared.StringInSlice(m["nictype"], []string{"bridged", "p2p"}) {
                n2 := deviceNextVeth()

                _, err := shared.RunCommand("ip", "link", "add", n1, "type", "veth", "peer", "name", n2)
...
                _, err = shared.RunCommand("ip", "link", "set", n1, "up")
...
                dev = n2
...
        // Bring the interface up
        _, err := shared.RunCommand("ip", "link", "set", "dev", dev, "up")

So it appears that lxd is indeed bringing up the container-side eth, as well as the veth side which attaches to the host bridge.  I guess there must be a reason why it doesn't leave it for the OS inside the container to bring up the interface?

Yeah, that code is for device hotplug which is a bit different than what you get on a fresh container start where liblxc does effectively the same for you.
The reason why liblxc does it is because it also allows pre-configuring a number of device settings which cannot be set if the device isn't up. Some device types like macvlan also need to be brought up to have their MAC address properly registered in the NIC, leaving it to the container's init system to bring it up would hide a number of critical errors.
There also are a number of distributions that were expecting devices to be brought up because their initrd was usually doing that. I think most of those no longer do this, but it certainly used to be a thing...

FYI, I caught a container "in the act".  After adding this workaround to the inet section in the container config:
pre-up ip link set dev eth0 down
pre-up sysctl net.ipv6.conf.eth0.autoconf=0
pre-up sysctl net.ipv6.conf.eth0.accept_ra=0

Then restarting the container, and doing "lxc list" repeatedly:
root@lxd1:~# lxc list
+------------+---------+---------------------+-------------------------------+------------+-----------+
|    NAME    |  STATE  |        IPV4         |             IPV6              |    TYPE    | SNAPSHOTS |
+------------+---------+---------------------+-------------------------------+------------+-----------+
| apt-cacher | RUNNING |                     |                               | PERSISTENT | 0         |
+------------+---------+---------------------+-------------------------------+------------+-----------+
root@lxd1:~# lxc list
+------------+---------+---------------------+----------------------------------------------+------------+-----------+
|    NAME    |  STATE  |        IPV4         |                     IPV6                     |    TYPE    | SNAPSHOTS |
+------------+---------+---------------------+----------------------------------------------+------------+-----------+
| apt-cacher | RUNNING |                     | XXXX:XXX:XXXX:XXXX:216:3eff:feaa:752d (eth0) | PERSISTENT | 0         |
+------------+---------+---------------------+----------------------------------------------+------------+-----------+
root@lxd1:~# lxc list
+------------+---------+---------------------+-------------------------------+------------+-----------+
|    NAME    |  STATE  |        IPV4         |             IPV6              |    TYPE    | SNAPSHOTS |
+------------+---------+---------------------+-------------------------------+------------+-----------+
| apt-cacher | RUNNING | <IP_ADDRESS> (eth0) |                               | PERSISTENT | 0         |
+------------+---------+---------------------+-------------------------------+------------+-----------+
root@lxd1:~# lxc list
+------------+---------+---------------------+-------------------------------+------------+-----------+
|    NAME    |  STATE  |        IPV4         |             IPV6              |    TYPE    | SNAPSHOTS |
+------------+---------+---------------------+-------------------------------+------------+-----------+
| apt-cacher | RUNNING | <IP_ADDRESS> (eth0) | XXXX:XXX:XXXX:XXXX::31 (eth0) | PERSISTENT | 0         |
+------------+---------+---------------------+-------------------------------+------------+-----------+

Just went through this again and I'm really not seeing anything that LXD itself is doing wrong.
I'd recommend filing a bug against ifupdown. It may then be further moved to the kernel, but it feels to me as if ifupdown should really be able to do what you ask it to do in this case.
I'm closing the LXD issue as there doesn't appear anything for us to do here. Please let us know of any bug report you file here, so that we can subscribe to it.

FYI workarounded this using:
pre-up ip -6 route del default dev $IFACE || true
As the default gateway is already there adding the correct (static) one fails - which also prevents post-up commands (and similar) from triggering.


Some risc asm improvements

What happens if it is a write to register 0 though? Is the instruction just ignored?

Yes, the riscv standard says that the write is ignored.

Ah, this is actually missing the implementation for the memory load instructions.

Updated.

Rebased it.


Extract auth challenge and expose it

This p-r implements #226

Current coverage is 80.35%

Merging #254 into master will increase coverage by +3.45% as of ff81f9d

@@            master    #254   diff @@
======================================
  Files           11      10     -1
  Stmts         1260    1069   -191
  Branches         0       0
  Methods          0
======================================
- Hit            969     859   -110
  Partial          0       0
+ Missed         291     210    -81

Review entire Coverage Diff as of ff81f9d

Powered by Codecov. Updated on successful CI builds.


loadhooks.js issue

any idea for this issue that loadhook.js is loaded first before any config files in version 0.11.3.
the order of loading may cause the following config doesn't work.
module.exports = {
hookTimeout: 40000
}

loadHook is loaded before the config files because the config files are themselves loaded via a hook.  This means that if you set hookTimeout in a config file, it will not be in effect when the first two core hooks (moduleLoader and userConfig) are loaded, but will be in effect for all of the other hooks.  If for some reason you need the timeout to be configured for those first two hooks, you can set it in the .sailsrc file or using a sails_hookTimeout environment variable on the command line.

Thanks. But can you give me a configuration sample for .sailsrc and sails_hookTimeout?

In the .sailsrc file:
"hookTimeout": 40000

On the command line:
sails_hookTimeout=40000 sails lift

thanks.


Improve command help text

What would you like to have changed?

I would like to get a more descriptive help text when using archiver as command (as arc in a terminal).
The current (just updated with get get -u) help text starts like this:
Usage: arc {archive|unarchive|extract|ls|compress|decompress|help} [arguments...]
  archive
    Create a new archive file. List the files/folders
    to include in the archive; at least one required.

From this info you still don't know how to archive a file or folder. From the text you might think that you can use arc archive file-to-archive, because that's arc and the subcommand and as [arguments...] you enter what the archive info tells you: "list the files [...]; at least one required", which is fulfilled. But it doesn't work that way. You get:

format unrecognized by filename: file-to-archive

So the help should somehow make clear that the first argument must be the target archive file.
But that's not the only thing. There's the global flag level:
   -level int
    	Compression level (default -1)

But what compression levels are supported?  Only when entering an unsupported level (e.g. 10), you get this:
2019/04/26 13:36:55 [ERROR] Walking file-to-archive: file-to-archive: writing: file-to-archive: making header: flate: invalid compression level 10: want value in range [-2, 9]

When using arc as command, this error should probably be a message to the user, instead of a log entry. Like: "You passed an invalid compression level (10). Supported levels: [-2, 9]" or something like that. But maybe that's a different issue and we should focus on the help text in this one. So at least the valid levels should already be shown in the help text.
If you don't want to make the help text too long, make help support the subcommands. So arc help prints an overview and mentions you can use help on subcommands, then arc help archive gives you more info on how to use that, including the mandatory output file as parameter, as well as the compression level. This is intuitive and people will know this pattern from commands like docker help run, git help push etc.
Why is this feature a useful, necessary, and/or important addition to this project?

I think a great advantage of arc is its usability and ease of use, which is great compared to remembering all the flags of tar for example, but without a proper help text this hurts exactly this advantage.
What alternatives are there, or what are you doing in the meantime to work around the lack of this feature?

You can figure out how arc works by some common sense and some trial and error until the help text is improved.
Please link to any relevant issues, pull requests, or other discussions.

/

I'd like to heavily support that. Besides that it is not clear which options apply to which commands, it is not clear to me how one could switch an option off (many of them say default true). Also there are some strange behaviours of the commands which aren't mentioned in the help, and I don't know whether I'm doing something wrong or there is much functionality missing:

if I unpack an archive it creates a directory named like the archive in the current directory - even if I explicitly give a . as directory to unpack
I couldn't find any way to create an archive containing files with arbitrary paths, e.g. a/b/c.txt, a/b/d.txt etc.  - the directory a/ seems thrown away.

I agree, the CLI could use some attention.
Unfortunately I've been swamped with my day job (especially busy since all the craziness this year, for some reason). Would be happy to have help maintaining this repo in the meantime.

Actually, I am here, because of the confusion caused by vague help message.
Where should I put -level in the following sequence to squeeze extra bytes and what levels are possible for zip?
$ arc.exe archive test.zip "my folder"

As I don't have plans/time to make a command for v4 (unless sponsorships motivate it specifically), I'll close this issue; but I've labeled it with "command" so we can remember this if someone does end up contributing a command later. Thanks!


Crash in AssetsViewController.photoLibraryDidChange

Hi! Thanks for such a great library.
When I switched the app to the background, and launched the camera app to take a picture, when I came back to the foreground, it crashed in AssetsViewController.photoLibraryDidChange(_:) every time.
The log is shown below.
*** Terminating app due to uncaught exception 'NSInternalInconsistencyException', reason: 'Invalid update: invalid number of items in section 0.  The number of items contained in an existing section after the update (67) must be equal to the number of items contained in that section before the update (67), plus or minus the number of items inserted or deleted from that section (1 inserted, 0 deleted) and plus or minus the number of items moved into or out of that section (0 moved in, 0 moved out).

why use performBatchUpdates ?
Is there a problem if I only handle it with reloadData?
    func photoLibraryDidChange(_ changeInstance: PHChange) {
        guard let changes = changeInstance.changeDetails(for: fetchResult) else { return }
        // Since we are gonna update UI, make sure we are on main
        DispatchQueue.main.async {
            self.fetchResult = changes.fetchResultAfterChanges
            self.collectionView.reloadData()

            // No matter if we have incremental changes or not, sync the selections
            self.syncSelections(self.store.assets)
        }
    }

It won't crash if you use reload data, sure.
However it won't look good. The UI will blink/glitch every time photoLibraryDidChange is called as it reload all cells instead of just updating those that have changed.
Put a breakpoint in the performBatchUpdates block and figure out what is going on. Does it have incremental changes? Does it have deleted, inserted or moved items? And are we updating the collection view with those changes.
I'll look into too whenever I have time.

If the UI blinking is the only problem, is it okay to take temporary action by using reloaddata first? Crash is a serious problem.
I'm still analyzing it with performanceBatchUpdates, but it's too difficult. ;(

If you are fine with that.

Fork this repo
Make the fix
Update your Podfile to use your fork until I've made a proper fix.

pod 'BSImagePicker', :git => 'https://github.com/Haccoon/BSImagePicker.git'

So I just tried reproducing the crash, but it works for me.
Could you give me any more details?

Device
iOS version
Any special settings made to the image picker
Etc

iPhone SE
OS 12

I attach a reenactment video.
Photos taken with cameras should be added, but the app is crash.

Yeapp, reproducible on iOS 12. Thanks :)

Oh, this is not a crash that occurs only with iOS 12. It also happens in 13.

Alright, worked for me on iOS 13 but crashes on iOS 12 :)

Try 3.1.4 - it should be fixed now. Thanks for helping out :)


generate-series-transact-sql - Fix example description

Example shows 10 but description 100. Fixed to 10.

@ClaudioESSilva : Thanks for your contribution! The author(s) have been notified to review your proposed change.

@kendalvandyke
Can you review the proposed changes? IMPORTANT: When the changes are ready for publication, add a #sign-off comment to signal that the PR is ready for the review team to merge.
#label:"aq-pr-triaged"

Thank you for your contribution. I'm closing this as it is a duplicate of #7643.
#please-close

Docs Build status updates of commit b9f7640:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docs/t-sql/functions/generate-series-transact-sql.md
:white_check_mark:Succeeded

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel


fix: hz_kitex_demo queryStudent API not work (#55)

What type of PR is this?
fix: Bugfix for issue #55: hz_kitex_demo queryStudent API not work.
What this PR does / why we need it (English/Chinese):
English: fix the bug that queryStudent API not work in hz_kitex_demo.
中文: 修复在hz_kitex_demo案例中queryStudent API无法正常工作的bug。
Which issue(s) this PR fixes:
Fixes #55

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.

@li-jin-gou Please help to review the PR. Thanks!


Menu hides when hovering over menu item after hovering over submenu

Steps to reproduce:

Set triggers to ['hover']
Hover over submenu
Hover over menu item

On the video menu hides automatically, I don't click anywhere.
https://user-images.githubusercontent.com/47790197/205085809-9fc460f5-9f94-4a42-8db0-2dd7ce7d7ffe.mp4

Same here, it also occurs when using nested DropDown components in beta.20 version

what is the solution?

Same for me, Is there any way to fix it? or disable auto hide on hovering items

how to use submenu?

please, sample how use submenu ?

Same here, unable to use the submenus when the trigger is ['hover'], since it will directly close it on the last nested item. Haven't found any way around it, besides setting the trigger to click, which is obviously not that great...

If anyone else has the issue, I was able to solve it by overwriting the showTriggers and hideTriggers props on the submenu.
Eg.
  <VMenu placement="bottom-start">
      <button class="border border-gray-300 rounded px-4 py-2">
        Hover me
      </button>

      <template #popper>

          Sub menus:

        <VMenu
          v-for="n in 5"
          :key="n"
          placement="right-start"
          instant-move
          :showTriggers="['hover', 'click']"
          :hideTriggers="['click']"
        >
          <button class="rounded hover:bg-green-100 px-4 py-2">
            Sub menu >
          </button>

          <template #popper>
            <VMenu
              v-for="n in 5"
              :key="n"
              placement="right-start"
              instant-move
              :showTriggers="['hover', 'click']"
              :hideTriggers="['click']"
            >
              <button class="rounded hover:bg-green-100 px-4 py-2">
                Option {{ n }} >
              </button>

              <template #popper>

                  Hello

              </template>
            </VMenu>
          </template>
        </VMenu>
      </template>
    </VMenu>

I have this same issue when using vmenu - Happening on the first dropdown menu - not even a submenu.

anyone resolved this? @jamiecorky I am sorry, but can you explain a bit better how you fixed it?

anyone resolved this? @jamiecorky I am sorry, but can you explain a bit better how you fixed it?

So basically I had a tooltip wrapped around the same button that I was trying to attach the menu to, The issue fixed for me when I wrapped the menu around the tooltip rather than the other way around. I am having more issues with this around accessibility though so might just make my own menu to get rid of these issues.

I think the root cause is this line:
https://github.com/Akryum/floating-vue/commit/01ef6f86aadc43488ade03cffd2158f2825cb416#r131886309

This is a mayor issue, makes using the sub menu's unusable right now.

Same for me, Is there any way to fix it? or disable auto hide on hovering items

I think the root cause is this line:
01ef6f8#r131886309

by @towry
works for me.

I think the root cause is this line:
01ef6f8#r131886309

by @towry
works for me.

Works for me as well. I forked the repository and fixed the issue locally while we wait for a new release

Added a setting to change the auto-close behavior.
Will increase the 1-second timeout to 2 seconds:
<VDropdown :autoCloseTimeout="2000">
...
</VDropdown>

Will disable the auto-close behavior completely:
<VDropdown :autoCloseTimeout="0">
...
</VDropdown>


dealerWallet have a floating sat balance

'BTC:Liabilities:Customer:5f8a1e6c2f410ed166a1b9ab': -378669.81700220774,

broker is no longer part of the main repo


Uncaught TypeError: Cannot read property 'statusCode' of undefined

[Enter steps to reproduce below:]

open favicon.ico
upload to imgur

Atom Version: 0.187.0
System: Mac OS X 10.10.2
Thrown From: kinetic package, v0.2.5
Stack Trace
Uncaught TypeError: Cannot read property 'statusCode' of undefined
At /Users/JacobWunder/.atom/packages/kinetic/lib/kinetic-module.coffee:123

TypeError: Cannot read property 'statusCode' of undefined
  at Request._callback (/Users/JacobWunder/.atom/packages/kinetic/lib/kinetic-module.coffee:123:53)
  at self.callback (/Users/JacobWunder/.atom/packages/kinetic/node_modules/request/request.js:121:22)
  at Request.emit (events.js:116:17)
  at ClientRequest.self.clientErrorHandler (/Users/JacobWunder/.atom/packages/kinetic/node_modules/request/request.js:230:10)
  at ClientRequest.emit (events.js:116:17)
  at TLSSocket.socketErrorListener (_http_client.js:273:9)
  at TLSSocket.emit (events.js:138:20)
  at net.js:452:14
  at process._tickCallback (node.js:366:11)

Commands
     -6:51.5 editor:newline (atom-text-editor.editor)
     -6:51.1 core:save (atom-text-editor.editor)
  2x -6:49.9 core:backspace (atom-text-editor.editor)
  3x -6:48.0 core:move-down (atom-text-editor.editor)
     -6:44.5 core:undo (atom-text-editor.editor)
     -6:12.0 settings-view:check-for-package-updates (atom-workspace.workspace.scrollbars-visible-when-scrolling.theme-solarized-light-syntax.theme-solarized-light-ui)
     -1:09.9 settings-view:open (atom-text-editor.editor)
     -1:05.3 core:confirm (atom-text-editor.editor.mini)
     -0:27.6 command-palette:toggle (atom-text-editor.editor)
     -0:19.3 core:move-down (atom-text-editor.editor.mini)
     -0:18.4 core:confirm (atom-text-editor.editor.mini)
     -0:18.4 kinetic:upload-to-Imgur (atom-text-editor.editor)
     -0:02.5 command-palette:toggle (ol.tree-view.full-menu.list-tree.has-collapsable-children.focusable-panel)
     -0:00.9 core:move-down (atom-text-editor.editor.mini)
     -0:00.6 core:confirm (atom-text-editor.editor.mini)
     -0:00.6 kinetic:upload-to-Imgur (ol.tree-view.full-menu.list-tree.has-collapsable-children.focusable-panel)

Config
{
  "core": {
    "disabledPackages": [
      "atom-html-preview"
    ],
    "themes": [
      "solarized-light-ui",
      "solarized-light-syntax"
    ],
    "projectHome": "/Users/JacobWunder/Documents/",
    "audioBeep": false
  }
}

Installed Packages
# User
achievements, v0.7.0
autocomplete-css, v0.4.0
autocomplete-html, v0.3.0
autocomplete-plus, v2.4.2
autocomplete-plus-jedi, v0.0.8
autocomplete-snippets, v1.0.1
kinetic, v0.2.5
minimap, v4.6.0
project-manager, v1.15.5
solarized-light-ui, v0.1.0
terminal-status, v1.3.5

# Dev
No dev packages

Thanks for reporting this.  I'll look into it as soon as i can!

no prob :+1:


Viral 'movement' terms problems

Hello,
@sylvainpoux reported that the following terms now cause taxon violations when annotated to viruses:

GO:0039675 exit of virus from host cell nucleus through nuclear pore
GO:0046802 exit of virus from host cell nucleus by nuclear egress
GO:0046765 viral budding from nuclear membrane
GO:0075732 viral penetration into host nucleus

This is probably due to the ongoing work in this area; I'll look at all the terms and edit as needed.
Thanks, Pascale

GO:0039675 exit of virus from host cell nucleus through nuclear pore
has logical definition:
'exit of virus from host cell nucleus'
and ('process has causal agent' some 'nuclear pore')
I dont think it's is right that the causal agent is the nuclear pore. I will remove the LD.

GO:0046802 exit of virus from host cell nucleus by nuclear egress (similar to its sibling GO:0039675 exit of virus from host cell nucleus through nuclear pore mentioned in the previous comment) probably inherit a taxon constraint from their subclass 'nuclear export'. I'll remove that, which leaves the subclass 'intracellular transport of virus'

GO:0046765 viral budding from nuclear membrane
has logical definition:
'viral budding'
and ('has input' some 'host cell nuclear membrane')
I dont think this is the correct usage of 'has input'. The definition of has input is:
p has input c iff: p is a process, c is a material entity, c is a participant in p, c is present at the    start of p, and the state of c is modified during p.
The host cell nuclear membrane is modified during budding, but not in the sense intended in this definition. I'll remove the LD.

Same for the children:

GO:0046771 viral budding from inner nuclear membrane
GO:0046772 viral budding from outer nuclear membrane

or maybe I should replace by 'has participant'?
@cmungall @ukemi What do you think ?

GO:0075732 viral penetration into host nucleus
also has subclass subclass 'intracellular transport of virus' (no taxon constraint, as far as I can tell)
AND GO:1902594 multiorganism nuclear import (removed; the parent 'import in the nucleus' is causing problems)

Thanks, Pascale


rop_exit binary still has canaries

Apparently the rop_exit binary is still compiled with stack canaries.
It was changed in f2aa1145ab0573f42382b563c4c8519bbbc6f0e2, but apparently it was not rebuilt before the 1.1 release.

Can you confirm if this is the binary in the v1.1 VM or the one in the standalone binaries zip? I believe the standalone binaries zip might not be in sync with the binaries in the v1.1 VM, so that should probably be fixed.

The VM has canaries
fa6bf6f0b133d6127a2f796a3f6873cb  rop_exit
lecture@warzone:/levels/lecture/rop$ gdb rop_exit
Reading symbols from rop_exit...(no debugging symbols found)...done.
gdb-peda$ disass main
Dump of assembler code for function main:
   0x080486dc <+95>:    call   0x8048550 <__stack_chk_fail@plt>
   0x080486e1 <+100>:   lea    esp,[ebp-0xc]
   0x080486e4 <+103>:   pop    ebx
   0x080486e5 <+104>:   pop    esi
   0x080486e6 <+105>:   pop    edi
   0x080486e7 <+106>:   pop    ebp
   0x080486e8 <+107>:   ret
End of assembler dump.
gdb-peda$ checksec
CANARY    : ENABLED
FORTIFY   : disabled
NX        : ENABLED
PIE       : disabled
RELRO     : Partial

$ md5 MBE_VM.vmdk
MD5 (MBE_VM.vmdk) = 9655bbe68e22d466885ebc17320d3a0e
$ ls -lh MBE_VM.vmdk.gz
-rw-r--r--  1 grazfather  staff<PHONE_NUMBER> Sep 28 00:02 MBE_VM.vmdk.gz

also, shouldn't it be compiled statically? it's probably their first rop chain

God...I have spent my afternoon trying to bypass the canaries...


Is there a straightforward way to send a message that isn't a reply?

I'm looking to set up a reminder such that the bot will post a message to a specific channel on a specific server on a schedule.
I see that say needs to be called within the context of build-handler-fn and can't specify a channel directly.  I also see that say* looks like it can specify a channel but is private.  I tried debugging to check out a message's channel and saw that it only had an id.  Could I potentially use that id or just save that entire channel object if I tried to make a say function that worked outside of build-handler-fn?
Is there already a way to do what I'm looking for or maybe there's a better way to go about it?
Thanks!

There is a send-message function
in the http name space that you should be able to leverage to send
unprompted messages.
On Fri, May 10, 2019, 22:08 Jason<EMAIL_ADDRESS>wrote:

I'm looking to set up a reminder such that the bot will post a message to
a specific channel on a specific server on a schedule.
I see that say needs to be called within the context of build-handler-fn
and can't specify a channel directly. I also see that say* looks like it
can specify a channel but is private. I tried debugging to check out a
message's channel and saw that it only had an id. Could I potentially use
that id or just save that entire channel object if I tried to make a say
function that worked outside of build-handler-fn?
Is there already a way to do what I'm looking for or maybe there's a
better way to go about it?
Thanks!
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/gizmo385/discord.clj/issues/11, or mute the thread
https://github.com/notifications/unsubscribe-auth/AAQHM2PCYEWOHEYRIN5QZW3PUZBCJANCNFSM4HMHISKQ
.

Thanks again!  It was super easy.  I was able to store the channel from a message to the bot and then call discord.http/send-message using (:auth (:client my-bot)) where my-bot was the returned value from discord.bot/create-bot.


Add leaderboard FAQ link (Friday from Christine)

Closing this issue as it is stale for a long time.


added alchemy news api

adds endpoint and widget for accessing the Alchemy news api.
The endpoint creates a query for news items having a company entity and
displays them with color/size attributes indicating sentiment.

This is covered by a red-shirts repo that's going to be updated for endpoints.


Fixed compute type for ReLU on non-x86 in conv (when jitted as a unary TPP)

Without fix, will produce an error when jitting relu_kernel_bf16 with libxsmm after commit https://github.com/libxsmm/libxsmm/commit/8eec24c267faf1831a82a2d1fadec15d09ba3733
Test case:
PREC=2 ITERS=1 FUSE=2 LIBXSMM_TARGET=neov1 ${NUMACTL} "${HERE}/layer_example" ${ITERS} 64 64 ${MB} 64 64 1 1 0 0 1 ${TYPE} L ${PAD} ${FUSE} ${BC} ${BK} ${PREC}

@egeor why closing and not merging this?


Include jump URL in mod log embed for infraction edits

Closes #2495
Screenshot:

It's looking good, I just have one comment before I submit a formal review:
When I edit an infraction twice, first in a moderators, then in a ModMail channel, I lose context to the first edit.
Which raises 2 questions:

Is that something that has happened before ? (Even if it didn't, it can still )
Do we want to cover that ?

By context you mean the jump URL, right?
Through this PR, jump URL to the edit context is displayed in the edit log embed- but it is not stored in the database. When you use the !infraction search, only the original context is displayed. The assumption is that the context is more likely to be present where the infraction was originally invoked  (although if any offending messages are deleted then :shrug: ).
As of now, there is no indication in the !infraction search embed that the infraction reason, expiry, etc. has been edited.  We could/should add message link to  edit contexts to infraction details when/if work on https://github.com/python-discord/site/issues/752 starts.
So,

I lose context to the first edit.
both the edit log embeds will still be in #mod-log channel, and the edit context information will not be stored in the database. It will only be included in the log embed that is sent to the #mod-log channel, and then discarded.


add support for securityContext in postgres containers

Hello,
I've noticed that the postgres container of the pods created by the operator have a very basic securityContext:
    securityContext:
      runAsUser: 1001

I saw there's a way to set the seccompProfile but I was hoping one can also set the full securityContext of the container, which doesn't seem to be the case. This is a problem when the restricted PSS is enforced.
This could become part of the ClusterSpec object - e.g. keeping the current value as defaults, but adding the option to override if required.
I don't know how much work this would represent, and I would be happy to help if I can - I would just need some guidance to get started.
Fred

@fad3t hi!
Are you talking about restricted-scc ? which it's something from openshift right ?
Regards,

Hi @sxd, no I'm referring to the pod security standards (cf. https://kubernetes.io/docs/concepts/security/pod-security-standards/#restricted).
We're enforcing it with Kyverno in our case, although I suppose this can be done otherwise.

Hi @sxd, I see you have assigned yourself to this issue. Does this mean you're working on it?
Otherwise I would be happy to contribute!

Hi, any update? Thanks

One more reason to have this feature is that large databases might take up to 30 minutes to mount due to this issue: https://github.com/kubernetes/kubernetes/issues/69699
using
securityContext:
  fsGroupChangePolicy: "OnRootMismatch"

would fix this.

last I ran across this setting the namespace to restricted prevent the init pods from starting entirely


Multi select?

Is the a select with multiple option?

This is not currently supported. It hasn't been requested yet (surprisingly).
Sounds easy enough, and useful. I'll add it to the next release.

Just wanted to let you know that this feature has been released with version 1.7.0.

Cool, thanks.
Chen Kinnrot
<EMAIL_ADDRESS>On Mon, Jan 12, 2015 at 7:34 AM, Brian Vaughn<EMAIL_ADDRESS>wrote:

Just wanted to let you know that this feature has been released with version
1.7.0 https://github.com/bvaughn/angular-form-for/releases/tag/1.7.0.
—
Reply to this email directly or view it on GitHub
https://github.com/bvaughn/angular-form-for/issues/89#issuecomment-69531314
.

Hi @kinnrot,
I hope you don't mind my reaching out to you in this way, but I have a small request I'd like to make of you. (And there will be no hard feelings if you don't have the time!)
I've recently started created a new JavaScript library named Task Runner (github.com/bvaughn/task-runner). If you're willing and able to take a few moments to look over the library, I'd love to hear your feedback. It's in the early stages (only 1 release) so there's still a lot of room for changes.
I think the library has a lot of potential, but before I push it out via Reddit and other forums, I'd love to get some unbiased feedback.
Cheers,
Brian


Validate Blazor InputNumber supports System.Int64

https://github.com/aspnet/AspNetCore/issues/13215

Confirmed, this is fixed as of at least 3.1.0-preview2.19517.21.


Adding vizanti and line_planner to documentation index for noetic

Please Add These Packages to be indexed in the rosdistro.
Noetic
The source is here:
https://github.com/MoffKalast/vizanti
https://github.com/MoffKalast/line_planner
Checks

[x] All packages have a declared license in the package.xml
[x] These repositories have a LICENSE file
[x] These packages are expected to build on the submitted rosdistro

Hey @cottsay if I can bother you with a slight follow-up, I see you've also added the packages to be built (not just the docs) which is cool, but while line_planner seems to build fine, I'm seeing some weird logs that I can't really explain for vizanti:
https://build.ros.org/job/Ndev__vizanti__ubuntu_focal_amd64/lastBuild/console
11:17:36 Resolved the dependencies to the following binary packages:
11:17:36   - ros-noetic-actionlib-msgs
11:17:36   - ros-noetic-catkin
11:17:36   - ros-noetic-dynamic-reconfigure
11:17:36   - ros-noetic-geometry-msgs
11:17:36   - ros-noetic-message-generation
11:17:36   - ros-noetic-move-base-msgs
11:17:36   - ros-noetic-rospy
11:17:36   - ros-noetic-std-msgs
11:17:36 Traceback (most recent call last):
11:17:36   File "/usr/lib/python3/dist-packages/apt/cache.py", line 299, in __getitem__
11:17:36     rawpkg = self._cache[key]
11:17:36 KeyError: 'ros-noetic-catkin'
11:17:36
11:17:36 During handling of the above exception, another exception occurred:
11:17:36
11:17:36 Traceback (most recent call last):
11:17:36   File "/tmp/ros_buildfarm/scripts/devel/create_devel_task_generator.py", line 21, in <module>
11:17:36     run_module('ros_buildfarm.scripts.devel.create_devel_task_generator', run_name='__main__')
11:17:36   File "/usr/lib/python3.8/runpy.py", line 210, in run_module
11:17:36     return _run_code(code, {}, init_globals, run_name, mod_spec)
11:17:36   File "/usr/lib/python3.8/runpy.py", line 87, in _run_code
11:17:36     exec(code, run_globals)
11:17:36   File "/tmp/ros_buildfarm/ros_buildfarm/scripts/devel/create_devel_task_generator.py", line 304, in <module>
11:17:36     sys.exit(main())
11:17:36   File "/tmp/ros_buildfarm/ros_buildfarm/scripts/devel/create_devel_task_generator.py", line 140, in main
11:17:36     get_binary_package_versions(apt_cache, debian_pkg_names))
11:17:36   File "/tmp/ros_buildfarm/ros_buildfarm/common.py", line 175, in get_binary_package_versions
11:17:36     pkg = apt_cache[debian_pkg_name]
11:17:36   File "/usr/lib/python3/dist-packages/apt/cache.py", line 301, in __getitem__
11:17:36     raise KeyError('The cache has no package named %r' % key)
11:17:36 KeyError: "The cache has no package named 'ros-noetic-catkin'"
11:17:36 Build step 'Execute shell' marked build as failure

Meanwhile line_planner has that same catkin dep which works fine:
https://build.ros.org/job/Ndev__line_planner__ubuntu_focal_amd64/lastBuild/console
02:58:39 Resolved the dependencies to the following binary packages:
02:58:39   - ros-noetic-actionlib-msgs
02:58:39   - ros-noetic-catkin
02:58:39   - ros-noetic-dynamic-reconfigure
02:58:39   - ros-noetic-geometry-msgs
02:58:39   - ros-noetic-move-base-msgs
02:58:39   - ros-noetic-rospy
02:58:39   - ros-noetic-std-msgs
02:58:39 Identified the following run and test dependencies (ignoring packages available from source):
02:58:39   - actionlib_msgs
02:58:39   - dynamic_reconfigure
02:58:39   - geometry_msgs
02:58:39   - move_base_msgs
02:58:39   - rospy
02:58:39   - std_msgs
02:58:39 Resolved the dependencies to the following binary packages:
02:58:39   - ros-noetic-actionlib-msgs
02:58:39   - ros-noetic-dynamic-reconfigure
02:58:39   - ros-noetic-geometry-msgs
02:58:39   - ros-noetic-move-base-msgs
02:58:39   - ros-noetic-rospy
02:58:39   - ros-noetic-std-msgs
02:58:39 Using the following distribution repositories:
02:58:39   http://repositories.ros.org/ubuntu/testing (/tmp/keys/0.key)
02:58:39 Generating Dockerfile '/tmp/docker_build_and_install/Dockerfile':
02:58:39   # generated from devel/devel_task.Dockerfile.em

Plus the pacakge.xmls are virtually identical, aside from message gen and the two extras:

I've retested the build process on a clean-ish install of Noetic and they both seem to resolve deps and build fine, I've tried a few random things that could've been tipping it off but so far it's always failed for what seems to be no reason at all, so I'm really at a loss as to what's happening. I imagine you might've seen such issues before?

Hello @MoffKalast -
The ros-noetic-catkin issue was a problem on the buildfarm unrelated to your package. It was resolved last week. I retried your job and it appears to have passed the issue previously blocking it.

Ah, it's always nice to hear that it's not an issue on my side.

If you don't want the builds, add the test_commits: False configuration to your source stanza.

Good to know, though these are fairly general packages that would be handy to have apt-installable eventually, I was just rather surprised that you guys are doing all of this building for free 😄


ComfyUI support?

Do you have any plans to launch comfyui with official native support? Integrate into the ComfyUI ecosystem like IPAdapter or InstantID?

Do you have any plans to launch comfyui with official native support? Integrate into the ComfyUI ecosystem like IPAdapter or InstantID?

Yes, we will also release the ComfyUI version, which has a lower priority than other tasks. We will release it in time, please stay tuned. If you have any further ideas, please feel free to ask~


Schedule page redesign to use expandable blocks

resolves #764
fixes broken display of track legend (at the bottom of the page) introduced by 99622d0

Current coverage is 42.60% (diff: 100%)

Merging #765 into development will not change coverage

@@           development       #765   diff @@
=============================================
  Files                6          6
  Lines              730        730
  Methods             73         73
  Messages             0          0
  Branches           118        118
=============================================
  Hits               311        311
  Misses             419        419
  Partials             0          0

Powered by Codecov. Last update e867b0f...34ebaa4


Home Assistant Support

Hello.
I am trying to configure my Nuki device. I have done the following steps: I have connected it to the WiFi and I have paired it. I just have to connect it to Home Assistant. But I have never used mqtt and I don't know how to connect it.
The console at https://technyon.github.io/nuki_hub/ shows me the following messages:
Attempting MQTT connection
MQTT: Connecting without credentials
MQTT connect failed, rc=-2
Free Heap: 116552
Nuki start pairing
Nuki paired
Attempting MQTT connection
MQTT: Connecting without credentials
MQTT connect failed, rc=-2
Free Heap: 114892
Attempting MQTT connection
MQTT: Connecting without credentials
MQTT connect failed, rc=-2
Free Heap: 113956
...
I also have MQTT enabled in Home Assistant.

What else should I do?
Thanks in advance.

It seems you didn't configure MQTT correctly. Did you configure the correct address / port for the MQTT broker, and entered the credentials (if needed)?

Worth mentioning that the username/password should be the ones that you added to homeassistant via Settings -> People -> Users.
Also, note that there is an autodiscovery section in the NUKI bridge MQTT configuration - set that to homeassistant (as technyon recommended).
@technyon , it took me a while to figure this out as I am a complete noob at this so may be worth adding to the README :)

I have configured mqtt with username and password in Home Assistant
The nuki_hub configuration process did not ask me for a username and password, so I do not know where to enter these credentials.

You need to set up under "MQTT and Network Configuration" (/mqttconfig).

Does it work now?

Closing due to inactivity. Let me know if issue persists, so I can reopen.


Is there any reason why we are keeping this feature on the classical interface as it is not active?

This feature is not active, when are we planning to remove it from the classical interface & remove it from our documentation?

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

ID: c6668926-c332-1348-2559-ee4e6dbf68a9
Version Independent ID: 214e5b3a-ba59-2dd3-5e97-7d642072afaf
Content: Enable or disable preview features in SharePoint - SharePoint in Microsoft 365
Content Source: SharePoint/SharePointOnline/enable-or-disable-preview-features.md
Service: sharepoint-online
GitHub Login: @kaarins
Microsoft Alias: kaarins

@jamilhaddadin Thank you for submitting feedback.
I think the best way forward is if you open a service ticket in your tenant so this can get resolved ASAP. Based on the outcome let me know if it is something that can be called out in the docs.
Please follow this link to contact support for business products:https://docs.microsoft.com/office365/admin/contact-support-for-business-products
Please keep us posted here on the resolution so we can feed whatever information you discover into the content.


Updates domains list and prints if quic is supported

Updates the list of domains and fixes #16
Also added in the print statement a column that prints 'yes' or 'no'
if QUIC is supported which allows for easier grepping for the output.
So if you wanted to see all the domains that support quic
quicreach '*' -s | grep yes (havent discussed about this change so if
you dont want it let me know I will revert it)
Signed-off-by: Sotiris Nanopoulos<EMAIL_ADDRESS>

@nibanks PTAL

Also added in the print statement a column that prints 'yes' or 'no' if QUIC is supported which allows for easier grepping for the output.
So if you wanted to see all the domains that support quic
quicreach '*' -s | grep yes (havent discussed about this change so if you dont want it let me know I will revert it)

I think quicreach '*' -s | grep ms would work just fine without the additional code change, right? I'd prefer not to make the additional change right now if you don't mind.


Unable to capture the Client disconnect exception

@spencergibb We are trying to implement the proxy using the Spring Cloud Gateway. Sometimes the client is disconnected due to timeout. We need to do capture the client disconnect events and do some process. But we are not able to find away to handle the client disconnect events/error handler.
We tried adding WebExceptionHandler and added the corresponding @Bean  but the ErrorHandler never picked up the client disconnect exception.  Please let us know whether it supported or not. If it supported can you provide some sample.

Use Hystrix Fallback. hystrix.command.default.execution.isolation.thread.timeoutInMilliseconds: 3000

We don't have anything right now that can handle that.  The first thing that comes to mind is a circuit breaker but I don't think it would handle a disconnect exception.  It might be a nice enhancement though.

If you would like us to look at this issue, please provide the requested information. If the information is not provided within the next 7 days this issue will be closed.

Closing due to lack of requested feedback. If you would like us to look at this issue, please provide the requested information and we will re-open the issue.


Why two build tools?

The grunt tasks should be converted to leiningen ones, there's no need for two build tools.

I think it won't be possible to merge the grunt tasks to leiningen ones. I think boot maybe a better fit but I am not too familiar with it.
PR welcome!

I think boot will be a better option. +1


Added minutes

minutes
list of attendees
actuion items

Please review ASAP @ryjones @thb-sb @Naomi-Wash and merge
Will share in my email to mailing list to announce next meeting and agenda
Thanks

now that I see what you want to do, I'll wait for a vote to approve from a TAC member

@planetf1 please merge if you agree

An additional observation.
We have a bulleted list of attendees - I presume these are the TAC members
How about having this in two parts ie
TAC members

[ ] A tac member

Additional attendees

[ ] A non member

(For the record I attended, but am not a tac member)


404, static files.

I can't seem to load the static files.
Vue File:
           <img src="/static/img/placeholder.png"/>
File Structure
- src
- static
    -- img
    --- placeholder.png

Got it working by renaming the static folder to public.
Seems the static folder gets copied directly to the .ream/dist folder without the static folder enclosing, while the public folder, does not get copied and served directly

Yep, that's the expected behavior.

Hmm, this seems a bit confusing, maybe we can remove ./public folder support, since using ./static/public has the same effect.

The behavior in ream@next:

./static/foo will be served at /_ream/static/foo but also available at /foo


JSON content topic corrupting db

I find that topics receiving certain types of JSON cause the app the crash, and corrupt the database as well.  This is using MQTT version 5.0

Hi, sorry about that and thanks for your feedback. Could you please describe its details? You can follow the issue-template, which will be better. :)
bug-report-template
---
name: Bug report
about: Create a report to help us improve
title: "[Bug] the title of bug report"
labels: bug
assignees: ''

---

## what did I do

something you have done.

## what happened

get an error

## environment

- ubuntu

## log/Screenshot/context

xxxx

Hi, sorry about that and thanks for your feedback. Could you please describe its details? You can follow the issue-template, which will be better. :)
bug-report-template
---
name: Bug report
about: Create a report to help us improve
title: "[Bug] the title of bug report"
labels: bug
assignees: ''

---

## what did I do

something you have done.

## what happened

get an error

## environment

- ubuntu

## log/Screenshot/context

xxxx


M14 - Models.py

Setup Models.py
Create model to populate db in a similar manner to socrata

Modified issue. Turns out, we made the wrong kind of pyramid app.

Made Entry model


Add rescan in settings

Just a small note that #84 contains important fixes to the logic so this needs to be updated in order to be tested properly.

#84 was merged. This can be finalized.


Only init status reporter when PILOT_ENABLE_STATUS=true

otherwise, we will init StatusReporter and it will RegisterEventand also process the events

@hzxuzhonghu: The following test failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

release-notes_istio
2515df3b1668a44851b673745e3e77e12d731952
link
/test release-notes_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@hzxuzhonghu: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

release-notes_istio
2515df3b1668a44851b673745e3e77e12d731952
link
/test release-notes_istio

unit-tests_istio
2515df3b1668a44851b673745e3e77e12d731952
link
/test unit-tests_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@hzxuzhonghu: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

release-notes_istio
2515df3b1668a44851b673745e3e77e12d731952
link
/test release-notes_istio

unit-tests_istio
2515df3b1668a44851b673745e3e77e12d731952
link
/test unit-tests_istio

integ-distroless-k8s-tests_istio
2515df3b1668a44851b673745e3e77e12d731952
link
/test integ-distroless-k8s-tests_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@hzxuzhonghu: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

release-notes_istio
2515df3b1668a44851b673745e3e77e12d731952
link
/test release-notes_istio

unit-tests_istio
2515df3b1668a44851b673745e3e77e12d731952
link
/test unit-tests_istio

integ-distroless-k8s-tests_istio
2515df3b1668a44851b673745e3e77e12d731952
link
/test integ-distroless-k8s-tests_istio

integ-ipv6-k8s-tests_istio
2515df3b1668a44851b673745e3e77e12d731952
link
/test integ-ipv6-k8s-tests_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@hzxuzhonghu: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

release-notes_istio
2515df3b1668a44851b673745e3e77e12d731952
link
/test release-notes_istio

unit-tests_istio
2515df3b1668a44851b673745e3e77e12d731952
link
/test unit-tests_istio

integ-distroless-k8s-tests_istio
2515df3b1668a44851b673745e3e77e12d731952
link
/test integ-distroless-k8s-tests_istio

integ-ipv6-k8s-tests_istio
2515df3b1668a44851b673745e3e77e12d731952
link
/test integ-ipv6-k8s-tests_istio

integ-helm-tests_istio
2515df3b1668a44851b673745e3e77e12d731952
link
/test integ-helm-tests_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@hzxuzhonghu: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

release-notes_istio
2515df3b1668a44851b673745e3e77e12d731952
link
/test release-notes_istio

unit-tests_istio
2515df3b1668a44851b673745e3e77e12d731952
link
/test unit-tests_istio

integ-distroless-k8s-tests_istio
2515df3b1668a44851b673745e3e77e12d731952
link
/test integ-distroless-k8s-tests_istio

integ-ipv6-k8s-tests_istio
2515df3b1668a44851b673745e3e77e12d731952
link
/test integ-ipv6-k8s-tests_istio

integ-helm-tests_istio
2515df3b1668a44851b673745e3e77e12d731952
link
/test integ-helm-tests_istio

integ-multicluster-k8s-tests_istio
2515df3b1668a44851b673745e3e77e12d731952
link
/test integ-multicluster-k8s-tests_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@hzxuzhonghu: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

release-notes_istio
2515df3b1668a44851b673745e3e77e12d731952
link
/test release-notes_istio

unit-tests_istio
2515df3b1668a44851b673745e3e77e12d731952
link
/test unit-tests_istio

integ-distroless-k8s-tests_istio
2515df3b1668a44851b673745e3e77e12d731952
link
/test integ-distroless-k8s-tests_istio

integ-ipv6-k8s-tests_istio
2515df3b1668a44851b673745e3e77e12d731952
link
/test integ-ipv6-k8s-tests_istio

integ-helm-tests_istio
2515df3b1668a44851b673745e3e77e12d731952
link
/test integ-helm-tests_istio

integ-multicluster-k8s-tests_istio
2515df3b1668a44851b673745e3e77e12d731952
link
/test integ-multicluster-k8s-tests_istio

integ-pilot-multicluster-tests_istio
2515df3b1668a44851b673745e3e77e12d731952
link
/test integ-pilot-multicluster-tests_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@hzxuzhonghu: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

release-notes_istio
2515df3b1668a44851b673745e3e77e12d731952
link
/test release-notes_istio

unit-tests_istio
2515df3b1668a44851b673745e3e77e12d731952
link
/test unit-tests_istio

integ-distroless-k8s-tests_istio
2515df3b1668a44851b673745e3e77e12d731952
link
/test integ-distroless-k8s-tests_istio

integ-ipv6-k8s-tests_istio
2515df3b1668a44851b673745e3e77e12d731952
link
/test integ-ipv6-k8s-tests_istio

integ-helm-tests_istio
2515df3b1668a44851b673745e3e77e12d731952
link
/test integ-helm-tests_istio

integ-multicluster-k8s-tests_istio
2515df3b1668a44851b673745e3e77e12d731952
link
/test integ-multicluster-k8s-tests_istio

integ-pilot-multicluster-tests_istio
2515df3b1668a44851b673745e3e77e12d731952
link
/test integ-pilot-multicluster-tests_istio

integ-operator-controller-tests_istio
2515df3b1668a44851b673745e3e77e12d731952
link
/test integ-operator-controller-tests_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@hzxuzhonghu: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

release-notes_istio
2515df3b1668a44851b673745e3e77e12d731952
link
/test release-notes_istio

unit-tests_istio
2515df3b1668a44851b673745e3e77e12d731952
link
/test unit-tests_istio

integ-distroless-k8s-tests_istio
2515df3b1668a44851b673745e3e77e12d731952
link
/test integ-distroless-k8s-tests_istio

integ-ipv6-k8s-tests_istio
2515df3b1668a44851b673745e3e77e12d731952
link
/test integ-ipv6-k8s-tests_istio

integ-helm-tests_istio
2515df3b1668a44851b673745e3e77e12d731952
link
/test integ-helm-tests_istio

integ-multicluster-k8s-tests_istio
2515df3b1668a44851b673745e3e77e12d731952
link
/test integ-multicluster-k8s-tests_istio

integ-pilot-multicluster-tests_istio
2515df3b1668a44851b673745e3e77e12d731952
link
/test integ-pilot-multicluster-tests_istio

integ-operator-controller-tests_istio
2515df3b1668a44851b673745e3e77e12d731952
link
/test integ-operator-controller-tests_istio

integ-pilot-k8s-tests_istio
2515df3b1668a44851b673745e3e77e12d731952
link
/test integ-pilot-k8s-tests_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@hzxuzhonghu: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

release-notes_istio
2515df3b1668a44851b673745e3e77e12d731952
link
/test release-notes_istio

unit-tests_istio
2515df3b1668a44851b673745e3e77e12d731952
link
/test unit-tests_istio

integ-distroless-k8s-tests_istio
2515df3b1668a44851b673745e3e77e12d731952
link
/test integ-distroless-k8s-tests_istio

integ-ipv6-k8s-tests_istio
2515df3b1668a44851b673745e3e77e12d731952
link
/test integ-ipv6-k8s-tests_istio

integ-helm-tests_istio
2515df3b1668a44851b673745e3e77e12d731952
link
/test integ-helm-tests_istio

integ-multicluster-k8s-tests_istio
2515df3b1668a44851b673745e3e77e12d731952
link
/test integ-multicluster-k8s-tests_istio

integ-pilot-multicluster-tests_istio
2515df3b1668a44851b673745e3e77e12d731952
link
/test integ-pilot-multicluster-tests_istio

integ-operator-controller-tests_istio
2515df3b1668a44851b673745e3e77e12d731952
link
/test integ-operator-controller-tests_istio

integ-pilot-k8s-tests_istio
2515df3b1668a44851b673745e3e77e12d731952
link
/test integ-pilot-k8s-tests_istio

integ-security-multicluster-tests_istio
2515df3b1668a44851b673745e3e77e12d731952
link
/test integ-security-multicluster-tests_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@hzxuzhonghu: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

release-notes_istio
2515df3b1668a44851b673745e3e77e12d731952
link
/test release-notes_istio

unit-tests_istio
2515df3b1668a44851b673745e3e77e12d731952
link
/test unit-tests_istio

integ-distroless-k8s-tests_istio
2515df3b1668a44851b673745e3e77e12d731952
link
/test integ-distroless-k8s-tests_istio

integ-ipv6-k8s-tests_istio
2515df3b1668a44851b673745e3e77e12d731952
link
/test integ-ipv6-k8s-tests_istio

integ-helm-tests_istio
2515df3b1668a44851b673745e3e77e12d731952
link
/test integ-helm-tests_istio

integ-multicluster-k8s-tests_istio
2515df3b1668a44851b673745e3e77e12d731952
link
/test integ-multicluster-k8s-tests_istio

integ-pilot-multicluster-tests_istio
2515df3b1668a44851b673745e3e77e12d731952
link
/test integ-pilot-multicluster-tests_istio

integ-operator-controller-tests_istio
2515df3b1668a44851b673745e3e77e12d731952
link
/test integ-operator-controller-tests_istio

integ-pilot-k8s-tests_istio
2515df3b1668a44851b673745e3e77e12d731952
link
/test integ-pilot-k8s-tests_istio

integ-security-multicluster-tests_istio
2515df3b1668a44851b673745e3e77e12d731952
link
/test integ-security-multicluster-tests_istio

integ-telemetry-mc-k8s-tests_istio
2515df3b1668a44851b673745e3e77e12d731952
link
/test integ-telemetry-mc-k8s-tests_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@hzxuzhonghu: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

release-notes_istio
2515df3b1668a44851b673745e3e77e12d731952
link
/test release-notes_istio

unit-tests_istio
2515df3b1668a44851b673745e3e77e12d731952
link
/test unit-tests_istio

integ-distroless-k8s-tests_istio
2515df3b1668a44851b673745e3e77e12d731952
link
/test integ-distroless-k8s-tests_istio

integ-ipv6-k8s-tests_istio
2515df3b1668a44851b673745e3e77e12d731952
link
/test integ-ipv6-k8s-tests_istio

integ-helm-tests_istio
2515df3b1668a44851b673745e3e77e12d731952
link
/test integ-helm-tests_istio

integ-multicluster-k8s-tests_istio
2515df3b1668a44851b673745e3e77e12d731952
link
/test integ-multicluster-k8s-tests_istio

integ-pilot-multicluster-tests_istio
2515df3b1668a44851b673745e3e77e12d731952
link
/test integ-pilot-multicluster-tests_istio

integ-operator-controller-tests_istio
2515df3b1668a44851b673745e3e77e12d731952
link
/test integ-operator-controller-tests_istio

integ-pilot-k8s-tests_istio
2515df3b1668a44851b673745e3e77e12d731952
link
/test integ-pilot-k8s-tests_istio

integ-security-multicluster-tests_istio
2515df3b1668a44851b673745e3e77e12d731952
link
/test integ-security-multicluster-tests_istio

integ-telemetry-mc-k8s-tests_istio
2515df3b1668a44851b673745e3e77e12d731952
link
/test integ-telemetry-mc-k8s-tests_istio

integ-telemetry-k8s-tests_istio
2515df3b1668a44851b673745e3e77e12d731952
link
/test integ-telemetry-k8s-tests_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@hzxuzhonghu: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

release-notes_istio
2515df3b1668a44851b673745e3e77e12d731952
link
/test release-notes_istio

unit-tests_istio
2515df3b1668a44851b673745e3e77e12d731952
link
/test unit-tests_istio

integ-distroless-k8s-tests_istio
2515df3b1668a44851b673745e3e77e12d731952
link
/test integ-distroless-k8s-tests_istio

integ-ipv6-k8s-tests_istio
2515df3b1668a44851b673745e3e77e12d731952
link
/test integ-ipv6-k8s-tests_istio

integ-helm-tests_istio
2515df3b1668a44851b673745e3e77e12d731952
link
/test integ-helm-tests_istio

integ-multicluster-k8s-tests_istio
2515df3b1668a44851b673745e3e77e12d731952
link
/test integ-multicluster-k8s-tests_istio

integ-pilot-multicluster-tests_istio
2515df3b1668a44851b673745e3e77e12d731952
link
/test integ-pilot-multicluster-tests_istio

integ-operator-controller-tests_istio
2515df3b1668a44851b673745e3e77e12d731952
link
/test integ-operator-controller-tests_istio

integ-pilot-k8s-tests_istio
2515df3b1668a44851b673745e3e77e12d731952
link
/test integ-pilot-k8s-tests_istio

integ-security-multicluster-tests_istio
2515df3b1668a44851b673745e3e77e12d731952
link
/test integ-security-multicluster-tests_istio

integ-telemetry-mc-k8s-tests_istio
2515df3b1668a44851b673745e3e77e12d731952
link
/test integ-telemetry-mc-k8s-tests_istio

integ-telemetry-k8s-tests_istio
2515df3b1668a44851b673745e3e77e12d731952
link
/test integ-telemetry-k8s-tests_istio

integ-security-k8s-tests_istio
2515df3b1668a44851b673745e3e77e12d731952
link
/test integ-security-k8s-tests_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

Not right, the reporter also record the distribution versions which can be queried


Investigate small vertical shift after entering message list

As reported by @gnprice :

When I navigate to a message list, the messages appear… and then around 100-200ms later, some of the elements in the message pane shift downward by a couple of pixels.
I suspect this is a regression in today's deployment, just because it feels pretty conspicuous to me and I don't recall seeing it before.
Greg Price: I don't think I see this when navigating from one message list to another. But I do see it when going from "Recent conversations" to a message list.
It reproduces each time if I just hit the back and then forward buttons, over and over — so that should be convenient for debugging, at least.
Specifically, the things that move include:

Status emoji after sender names.
Emoji reactions — the whole chips/pills, not just the emoji.
Some other pieces — for example here, I see the bottom half or so of the message move down, while the top half stays in place. Perhaps the line-height increased by a fraction of a pixel? (And then the browser is effectively rounding the y-positions to integer pixels, for text clarity.)

We should investigate and try to track down this issue. See CZO thread for discussion.

@zulipbot claim

@zulipbot  claim


3.3.1 load config from config.yaml

Everything look good!
I am using the new option --config passing a file to code-server.
looks like user-data-dir and extensions-dir  is not read from file.
my config.yaml:
user-data-dir: /home/junyan/mnt/e/Config/code-server/Data/
extensions-dir: /home/junyan/mnt/e/Config/code-server/Extensions/
using command line parameter everything works.

Looking into it!

Ah got it, thanks for reporting will push fix soon.

Hate to bring this back but I still face this issue on v3.4.0

Yup, see release notes in #1766


skipDuplicates doesn't work with CockroachDB

Bug description
This is it, it doesn't. CockroachDB does support ON CONFLICT DO NOTHING.
How to reproduce

Expected behavior
No response
Prisma information

// Add your schema.prisma

// Add your code using Prisma Client

Environment & setup
generator client {
provider        = "prisma-client-js"
previewFeatures = ["interactiveTransactions", "filterJson"]
engineType      = "binary"
}
Prisma Version
prisma                  : 4.3.1
@prisma/client          : 4.3.1
Current platform        : darwin-arm64
Query Engine (Node-API) : libquery-engine c875e43600dfe042452e0b868f7a48b817b9640b (at<EMAIL_ADDRESS>Migration Engine        : migration-engine-cli c875e43600dfe042452e0b868f7a48b817b9640b (at node_modules/@prisma/engines/migration-engine-darwin-arm64)
Introspection Engine    : introspection-core c875e43600dfe042452e0b868f7a48b817b9640b (at node_modules/@prisma/engines/introspection-engine-darwin-arm64)
Format Binary           : prisma-fmt c875e43600dfe042452e0b868f7a48b817b9640b (at node_modules/@prisma/engines/prisma-fmt-darwin-arm64)
Format Wasm             : @prisma/prisma-fmt-wasm 4.3.0-32.c875e43600dfe042452e0b868f7a48b817b9640b
Default Engines Hash    : c875e43600dfe042452e0b868f7a48b817b9640b
Studio                  : 0.473.0
Preview Features        : filterJson, interactiveTransactions

So does it after all?

I Have the same issue with Mongodb, how to work around it


Change tgi tag because gaudi driver is upgraded to 1.16.1

Description
Change tgi tag because gaudi driver is upgraded to 1.16.1
Issues
n/a
Type of change
List the type of change like below. Please delete options that are not relevant.

[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds new functionality)
[ ] Breaking change (fix or feature that would break existing design and interface)

Dependencies
n/a
Tests
CI tests

The CI test is verified here: https://github.com/opea-project/GenAIInfra/actions/runs/10037728498


Network settings in tests

I found some problems with running tests in docker with port 2000 and local ipv6.
So I changed the test ports to 808* and the listening address to ipv4 to make the test work also on ipv4-only systems.
I also added a "test" script to the composer file.

Thanks


librespot integration

Just discovered this plug-in today; great work!  I wondered, with the likely demise of libspotify at some point, along with its limited functionality, if you'd considered integrating librespot instead?  It would open up several avenues including zeroconf-based authentication, Spotify Connect, radio/"smart" playlists, etc.

The likelihood of this is (currently) close to zero:

librespot does not work properly on Windows.
There is no way to build librespot as a dll with C/C++ interface, so it can't be consumed easily. And I have zero interest in learning Rust =)

Thanks for taking the time to provide your reasoning.  Makes total sense and I appreciate the response.

Thanks for taking the time to provide your reasoning.  Makes total sense and I appreciate the response.


Update inscriptions.json - stars added, names updated

just added stars, and fixed some wrong  names

yo everyone were waiting 2 weeks now... please dudes ;)


ionic input type number accept the  character "e"

Short description of the problem:
What behavior are you expecting?
Steps to reproduce:
1.
2.
3.
insert any relevant code between the above and below backticks

Ionic Version: 1.x / 2.x
Browser & Operating System: iOS / Android / Chrome
Run ionic info from terminal/cmd prompt:
paste output from `ionic info` here

Sorry but this comes from HTML5 and not Ionic: http://stackoverflow.com/questions/31706611/why-does-the-html-input-with-type-number-allow-the-letter-e-to-be-entered-in


Move our work so far to bare react native

Its not needed anymore.
Regarding the triggered build job. I cannot find any work around to take advantages on both Expo's accessibility for development and Bare RN's flexibility for deployment, so we will go for Expo since its more relevant to us at the moment.
However I kept the triggered build job here to run npm audit for us which at least could make sure we don't have regression on fixed vulnerabilities. Please check when you have time.


nil slice to zero-length blob

Changes to fix https://github.com/mattn/go-sqlite3/issues/424 also make nil slice be converted to zero-length blob. Instead, nil slice should be converted to value NULL.
Current code:
	[]byte -> zero length blob
	nil    -> zero length blob
Proposal:
	[]byte -> zero length blob
	nil    -> NULL blob

I can submit a PR if the proposal makes sense to you.

@lucasmrod makes sense, can you submit a PR of evaluation and testing, please also include tests in your PR.


skaffold dev fails to copy file

After running skaffold dev, the first run succeeds.
When I copy my binary into the workspace that skaffold is watching, then a new build is triggered as expected, but the docker build errors with:
Starting build...
ERRO[0127] Can't add file path/to/my/workspace/binary to tar: archive/tar: write too long
Sending build context to Docker daemon  6.581MB
Step 1/5 : FROM alpine
 ---> 3fd9065eaf02

# ...
# continues to deploy the broken image such that Pod fails

This is unexpected. My binary is 61M for reference.

Hi @clanstyles, thanks for the report!

Can you tell us which version of skaffold you are using?
Does skaffold docker deps works?
Does skaffold docker context works?

Oops wrong @ tag :)
Version below + both commands work:
$ skaffold version
v0.2.0

$ skaffold docker deps -v info
INFO[0000] Skaffold &{Version:v0.2.0 GitVersion: GitCommit:eb0fd0223bb9ec640f1031bb8c9858ef22338e01 GitTreeState:clean BuildDate:2018-03-09T22:47:32Z GoVersion:go1.10 Compiler:gc Platform:darwin/amd64}
INFO[0002] Found dependencies for dockerfile [my-files]
# ... paths to files ...

$ skaffold docker context -v info
INFO[0000] Skaffold &{Version:v0.2.0 GitVersion: GitCommit:eb0fd0223bb9ec640f1031bb8c9858ef22338e01 GitTreeState:clean BuildDate:2018-03-09T22:47:32Z GoVersion:go1.10 Compiler:gc Platform:darwin/amd64}
INFO[0000] Dockerfile
INFO[0000] /path/to/Dockerfile
INFO[0002] Found dependencies for dockerfile [my-files]

My replacement workflow has been cp my/binary to/skaffold/artifact/directory/ && skaffold run -f skaffold.yaml which works for now.

@julianvmodesto Can you please try again with version 0.3.0? That would be awesome

My use case is fixed, thanks!
Note that one potential bug I noticed is new files aren't watched by skaffold dev.
e.g. touch foobar into one of the watched directories doesn't do anything.