DNS lookup fails for all containers launched with rancher

Containers are not able to resolve hosts for linked services and all DNS lookups are failing with Rancher 0.32 and rancher agent instance v0.3.1 (rancher/agent-instance:v0.3.1) and rancher agent v0.7.11 (rancher/agent:v0.7.11).
Steps to reproduce:
Launch any container with Rancher server 0.32. Execute shell and try pinging an external host (e.g., google.com) or a linked service. The rancher-agent on each host is not affected by this issue and is able to resolve hosts.
Other Info:
Docker version: 1.6.2
Host provider: AWS EC2
Error logs from rancher agent:
09/08/2015 03:17:27rancher-dns: no process found
09/08/2015 03:17:27[[scripts.sh:198] docker_env
09/08/2015 03:17:27[[scripts.sh:26] '[' -e /.dockerenv ']'
09/08/2015 03:17:27[[[scripts.sh:27] docker_env_vars
09/08/2015 03:17:27[[[scripts.sh:19] '[' -e /.dockerenv ']'
09/08/2015 03:17:27[[[scripts.sh:20] grep CATTLE_
09/08/2015 03:17:27[[[scripts.sh:20] xargs -0 '-I{}' echo export '"{}"'
09/08/2015 03:17:27[[[scripts.sh:20] cat /proc/1/environ
09/08/2015 03:17:27[[scripts.sh:27] eval export '"CATTLE_CONFIG_URL=http://HOST:PORT/v1"' export '"CATTLE_AGENT_INSTANCE_AUTH=Basic' 'BASIC-AUTH"' export '"CATTLE_HOME=/var/lib/cattle"'
09/08/2015 03:17:27[[[scripts.sh:27] export CATTLE_CONFIG_URL=http://HOST:PORT/v1 export 'CATTLE_AGENT_INSTANCE_AUTH=Basic AUTH' export CATTLE_HOME=/var/lib/cattle
09/08/2015 03:17:27[[[scripts.sh:27] CATTLE_CONFIG_URL=http://HOST:PORT/v1
09/08/2015 03:17:27[[[scripts.sh:27] CATTLE_AGENT_INSTANCE_AUTH='Basic AUTH'
09/08/2015 03:17:27[[[scripts.sh:27] CATTLE_HOME=/var/lib/cattle
09/08/2015 03:17:27[[scripts.sh:199] script_env
09/08/2015 03:17:27[[scripts.sh:123] '[' -n http://HOST:PORT/v1 ']'
09/08/2015 03:17:27[[scripts.sh:124] return
09/08/2015 03:17:27[[scripts.sh:201] export CATTLE_HOME=/var/lib/cattle
09/08/2015 03:17:27[[scripts.sh:201] CATTLE_HOME=/var/lib/cattle
09/08/2015 03:17:27[[scripts.sh:202] export CATTLE_CONFIG_URL=http://HOST:PORT/v1
09/08/2015 03:17:27[[scripts.sh:202] CATTLE_CONFIG_URL=http://HOST:PORT/v1
09/08/2015 03:17:27[[scripts.sh:203] export CATTLE_STORAGE_URL=
09/08/2015 03:17:27[[scripts.sh:203] CATTLE_STORAGE_URL=
09/08/2015 03:17:27[apply.sh:21] DNS=
09/08/2015 03:17:27[[apply.sh:23] awk '{print $2}'
09/08/2015 03:17:27[[apply.sh:23] grep '^nameserver'
09/08/2015 03:17:27[[apply.sh:23] sed 's/^# nameserver/nameserver/'
09/08/2015 03:17:27[[apply.sh:23] cat /etc/resolv.conf
09/08/2015 03:17:27[apply.sh:23] for address in '$(cat /etc/resolv.conf  | sed '''s/^# nameserver/nameserver/''' | grep ^nameserver | awk '''{print $2}''')'
09/08/2015 03:17:27[apply.sh:24] '[' <IP_ADDRESS> = <IP_ADDRESS> ']'
09/08/2015 03:17:27[apply.sh:28] '[' -z '' ']'
09/08/2015 03:17:27[apply.sh:29] DNS='"<IP_ADDRESS>"'
09/08/2015 03:17:27[apply.sh:35] sed -i 's/PARENT_DNS/"<IP_ADDRESS>"/' content-home/etc/cattle/dns/answers.json
09/08/2015 03:17:27[apply.sh:37] stage_files
09/08/2015 03:17:27[scripts.sh:91] local monit=false
09/08/2015 03:17:27[scripts.sh:93] '[' -d content-home ']'
09/08/2015 03:17:27[scripts.sh:94] find content-home -name '*.sh' -exec chmod +x '{}' ';'
09/08/2015 03:17:27[scripts.sh:95] sed 's/^/INFO: HOME -> /'
09/08/2015 03:17:27[scripts.sh:95] tar xvf - --no-overwrite-dir -C /var/lib/cattle
09/08/2015 03:17:27[scripts.sh:95] tar cf - -C content-home .
09/08/2015 03:17:27[scripts.sh:98] '[' -d content ']'
09/08/2015 03:17:27[scripts.sh:116] '[' false = true ']'
09/08/2015 03:17:27[apply.sh:39] ip addr add <IP_ADDRESS>/32 dev eth0
09/08/2015 03:17:27[apply.sh:39] true
09/08/2015 03:17:27[apply.sh:40] grep -q <IP_ADDRESS>
09/08/2015 03:17:27[apply.sh:40] ip route show
09/08/2015 03:17:27[apply.sh:44] reload_dns
09/08/2015 03:17:27[apply.sh:7] '[' '!' -e /etc/init.d/rancher-dns ']'
09/08/2015 03:17:27[[apply.sh:12] pidof rancher-dns
09/08/2015 03:17:27[apply.sh:12] PID=870
09/08/2015 03:17:27[apply.sh:14] '[' -z 870 ']'
09/08/2015 03:17:27[apply.sh:18] killall -HUP rancher-dns

After further investigation it seems like the issue is tied to the version of docker on the client hosts and not to the rancher version. I run can reproduce the problem with docker version 1.6.2 but I'm unable to reproduce it with docker version 1.7.1.

@bilal Thanks for pointing this out.  We do all our testing on 1.7.x at the moment so I don't doubt that we could have introduced a regression in 1.6.

This problem is replicated Docker version 1.7.0, all new containers that I have linked are not working in DNS lookup.
Old containers that are running are not affected.

@silviupanaite could you please share:

The details of your stack - exported docker-compose.yml would be helpful.
The output of answers.json file from the network agent container running on the host having problems. The path to the file is: /var/lib/cattle/etc/cattle/dns/answers.json
If you see any errors in agent log (/var/log/rancher/agent.log), could you also include it to the bug

connector-fullcontact:
restart: always
environment:
NODE_ENV: beta
REDISCLOUD_URL: redis://none:none@redis-outboxpro:6379
tty: true
cpu_shares: 512
image: docker.unifiedinbox.com:4433/outboxpro/nodejs
links:

redis-outboxpro:redis-outboxpro
volumes:
/connector-fullcontact/data/ue-connector-fullcontact:/usr/share/node/app
/connector-fullcontact/logs:/var/log/node
stdin_open: true
redis-outboxpro:
tty: true
image: redis
stdin_open: true
test-balancer2:
restart: always
ports:
8884:5000
8885:5000
8886:5000
8887:5000
8888:5000
labels:
io.rancher.loadbalancer.target.connector-twitter: 8885=5000
io.rancher.loadbalancer.target.connector-linkedin: 8886=5000
io.rancher.loadbalancer.target.connector-fullcontact: 8887=5000
io.rancher.loadbalancer.target.connector-weibo: 8883=5000
io.rancher.loadbalancer.target.connector-facebook: 8888=5000
io.rancher.loadbalancer.target.connector-xing: 8884=5000
tty: true
image: rancher/load-balancer-service
links:
connector-fullcontact:connector-fullcontact
connector-linkedin:connector-linkedin
connector-facebook:connector-facebook
connector-twitter:connector-twitter
connector-xing:connector-xing
connector-weibo:connector-weibo
stdin_open: true
connector-twitter:
restart: always
environment:
NODE_ENV: beta
REDISCLOUD_URL: redis://none:none@redis-outboxpro:6379
tty: true
cpu_shares: 512
image: nodejs
links:
redis-outboxpro:redis-outboxpro
volumes:
/connector-twitter/data/ue-connector-twitter:/usr/share/node/app
/connector-twitter/logs:/var/log/node
stdin_open: true
connector-xing:
restart: always
environment:
NODE_ENV: beta
REDISCLOUD_URL: redis://none:none@redis-outboxpro:6379
tty: true
cpu_shares: 512
image: docker.unifiedinbox.com:4433/outboxpro/nodejs
links:
redis-outboxpro:redis-outboxpro
volumes:
/connector-xing/data/ue-connector-xing:/usr/share/node/app
/connector-xing/logs:/var/log/node
stdin_open: true
connector-facebook:
restart: always
environment:
NEW_RELIC_APDEX: '0.01'
NEW_RELIC_APP_NAME: connector-fb
NEW_RELIC_LICENSE_KEY: db4aadc9771c9195fb7abcef180ae9b63b5a905c
NODE_ENV: beta
REDISCLOUD_URL: redis://none:none@redis-outboxpro:6379
tty: true
cpu_shares: 512
image: nodejs
links:
redis-outboxpro:redis-outboxpro
volumes:
/connector-facebook/data/ue-connector-fb:/usr/share/node/app
/connector-facebook/logs:/var/log/node
stdin_open: true
connector-linkedin:
restart: always
environment:
NEW_RELIC_APDEX: '0.01'
NEW_RELIC_APP_NAME: connector-in
NEW_RELIC_LICENSE_KEY: db4aadc9771c9195fb7abcef180ae9b63b5a905c
NODE_ENV: beta
REDISCLOUD_URL: redis://none:none@redis-outboxpro:6379
tty: true
cpu_shares: 512
image: nodejs
links:
redis-outboxpro:redis-outboxpro
volumes:
/connector-linkedin/data/ue-connector-in:/usr/share/node/app
/connector-linkedin/logs:/var/log/node
stdin_open: true
connector-weibo:
restart: always
environment:
NODE_ENV: beta
REDISCLOUD_URL: redis://none:none@redis-outboxpro:6379
tty: true
cpu_shares: 512
image: nodejs
links:
redis-outboxpro:redis-outboxpro
volumes:
/connector-weibo/data/ue-connector-weibo:/usr/share/node/app
/connector-weibo/logs:/var/log/node
stdin_open: true

no dns file

08:27:06,927 ERROR cattle [140568136493648] [utils.py:278] Failed to call (['/var/lib/cattle/config.sh', u'host-iptables'],)
2015-08-10 05:22:06,674 ERROR agent [140568136536944] [publisher.py:26] Error [], Request [{"name": "reply.3581326572721852989", "resourceType": "agent", "resourceId": "1a21", "previousNames": ["ping"], "time":<PHONE_NUMBER>000, "

@silviupanaite Absence of answers.json file is very suspicious, especially knowing that the containers from the previous version continue to run w/o any problem. Are these "successful" containers running on the same host with the services container that fail to resolve DNS? If yes, could you double check that you've tried to pull the "answers.json" file from the container created from "rancher/agent-instance:v0.3.1" image?
If all the containers that failed to resolve DNS, are running on a different host from the containers that can resolve DNS successfully, then there might be a problem with that particular host/agent on it. If thats the case, could you upload the entire agent.log file from the day when upgrade was performed, and give us a reference to it.
Need this info to narrow down the failure either to DNS answers.json being misconfigured, or network agent having problems

Yes I hadn't pulled the right container, also these are container running on the same host, tried a different host, got the same problem.
{
"default": {
"recurse": [
"<IP_ADDRESS>"
]
},
"<IP_ADDRESS>": {
"a": {
"redis.": {"answer": ["<IP_ADDRESS>"]},
"redis.rancher.internal.": {"answer": ["<IP_ADDRESS>"]}
}
},

"<IP_ADDRESS>": {
    "a": {
	"redis-outboxpro.": {"answer": ["<IP_ADDRESS>"]},
	"redis-outboxpro.rancher.internal.": {"answer": ["<IP_ADDRESS>"]},
	"connector-twitter.": {"answer": ["<IP_ADDRESS>"]},
	"connector-twitter.rancher.internal.": {"answer": ["<IP_ADDRESS>"]}
	}

},

"<IP_ADDRESS>": {
    "a": {
	"database.": {"answer": ["<IP_ADDRESS>"]},
	"database.rancher.internal.": {"answer": ["<IP_ADDRESS>"]},
	"ruby-daemon.": {"answer": ["<IP_ADDRESS>"]},
	"ruby-daemon.rancher.internal.": {"answer": ["<IP_ADDRESS>"]}
	}

},

"<IP_ADDRESS>": {
    "a": {
	"redis-outboxpro.": {"answer": ["<IP_ADDRESS>"]},
	"redis-outboxpro.rancher.internal.": {"answer": ["<IP_ADDRESS>"]}
	}

},

"<IP_ADDRESS>": {
    "a": {
	"mongodb.": {"answer": ["<IP_ADDRESS>"]},
	"mongodb.rancher.internal.": {"answer": ["<IP_ADDRESS>"]},
	"daemon.": {"answer": ["<IP_ADDRESS>"]},
	"daemon.rancher.internal.": {"answer": ["<IP_ADDRESS>"]},
	"apache-php.": {"answer": ["<IP_ADDRESS>"]},
	"apache-php.rancher.internal.": {"answer": ["<IP_ADDRESS>"]},
	"redis.": {"answer": ["<IP_ADDRESS>"]},
	"redis.rancher.internal.": {"answer": ["<IP_ADDRESS>"]},
	"database.": {"answer": ["<IP_ADDRESS>"]},
	"database.rancher.internal.": {"answer": ["<IP_ADDRESS>"]}
	}

},

"<IP_ADDRESS>": {
    "a": {
	"database.": {"answer": ["<IP_ADDRESS>"]},
	"database.rancher.internal.": {"answer": ["<IP_ADDRESS>"]},
	"mongodb.": {"answer": ["<IP_ADDRESS>"]},
	"mongodb.rancher.internal.": {"answer": ["<IP_ADDRESS>"]}
	}

},

"<IP_ADDRESS>": {
    "a": {
	"mysql.": {"answer": ["<IP_ADDRESS>"]},
	"mysql.rancher.internal.": {"answer": ["<IP_ADDRESS>"]}
	}

},

"<IP_ADDRESS>": {
    "a": {
	"unifiedinbox.": {"answer": ["<IP_ADDRESS>"]},
	"unifiedinbox.rancher.internal.": {"answer": ["<IP_ADDRESS>"]}
	}

},

"": {}

}

this is the network agent errors:
7/18/2015 1:09:03 PM[config.sh:122] rm /var/lib/cattle/download.Je0ZL6v/download
7/18/2015 1:09:03 PM[[[config.sh:124] ls -1 /var/lib/cattle/download.Je0ZL6v
7/18/2015 1:09:03 PM[[config.sh:124] basename iptables-2-57d6c642b0fe838d32afc550f929c743365f9bfa3f31850fe73e4149e76c1f77
7/18/2015 1:09:03 PM[config.sh:124] local dir=iptables-2-57d6c642b0fe838d32afc550f929c743365f9bfa3f31850fe73e4149e76c1f77
7/18/2015 1:09:03 PM[config.sh:125] '[' '!' -e /var/lib/cattle/download.Je0ZL6v/iptables-2-57d6c642b0fe838d32afc550f929c743365f9bfa3f31850fe73e4149e76c1f77 ']'
7/18/2015 1:09:03 PM[config.sh:132] cd /var/lib/cattle/download.Je0ZL6v
7/18/2015 1:09:03 PM[config.sh:134] '[' '!' -e iptables-2-57d6c642b0fe838d32afc550f929c743365f9bfa3f31850fe73e4149e76c1f77/SHA1SUMSSUM ']'
7/18/2015 1:09:03 PM[config.sh:134] '[' '!' -e iptables-2-57d6c642b0fe838d32afc550f929c743365f9bfa3f31850fe73e4149e76c1f77/SHA1SUMS ']'
7/18/2015 1:09:03 PM[config.sh:139] sha1sum -c iptables-2-57d6c642b0fe838d32afc550f929c743365f9bfa3f31850fe73e4149e76c1f77/SHA1SUMSSUM
7/18/2015 1:09:03 PM[config.sh:140] sha1sum -c iptables-2-57d6c642b0fe838d32afc550f929c743365f9bfa3f31850fe73e4149e76c1f77/SHA1SUMS
7/18/2015 1:09:03 PM[config.sh:143] '[' -n '' ']'
7/18/2015 1:09:03 PM[config.sh:150] content_root=/var/lib/cattle/download/iptables/iptables-2-57d6c642b0fe838d32afc550f929c743365f9bfa3f31850fe73e4149e76c1f77
7/18/2015 1:09:03 PM[config.sh:152] '[' -e /var/lib/cattle/download.Je0ZL6v/iptables-2-57d6c642b0fe838d32afc550f929c743365f9bfa3f31850fe73e4149e76c1f77/uptodate ']'
7/18/2015 1:09:03 PM[config.sh:160] '[' -e /var/lib/cattle/download/iptables/iptables-2-57d6c642b0fe838d32afc550f929c743365f9bfa3f31850fe73e4149e76c1f77 ']'
7/18/2015 1:09:03 PM[config.sh:161] rm -rf /var/lib/cattle/download/iptables/iptables-2-57d6c642b0fe838d32afc550f929c743365f9bfa3f31850fe73e4149e76c1f77
7/18/2015 1:09:03 PM[[config.sh:164] dirname /var/lib/cattle/download/iptables/iptables-2-57d6c642b0fe838d32afc550f929c743365f9bfa3f31850fe73e4149e76c1f77
7/18/2015 1:09:03 PM[config.sh:164] mkdir -p /var/lib/cattle/download/iptables
7/18/2015 1:09:03 PM[config.sh:165] mv /var/lib/cattle/download.Je0ZL6v/iptables-2-57d6c642b0fe838d32afc550f929c743365f9bfa3f31850fe73e4149e76c1f77 /var/lib/cattle/download/iptables/iptables-2-57d6c642b0fe838d32afc550f929c743365f9bfa3f31850fe73e4149e76c1f77
7/18/2015 1:09:03 PM[config.sh:252] '[' false '!=' true ']'
7/18/2015 1:09:03 PM[config.sh:253] apply
7/18/2015 1:09:03 PM[config.sh:180] check_applied
7/18/2015 1:09:03 PM[config.sh:170] local current=/var/lib/cattle/download/iptables/iptables-2-57d6c642b0fe838d32afc550f929c743365f9bfa3f31850fe73e4149e76c1f77/../current
7/18/2015 1:09:03 PM[config.sh:171] '[' -e /var/lib/cattle/download/iptables/iptables-2-57d6c642b0fe838d32afc550f929c743365f9bfa3f31850fe73e4149e76c1f77/../current ']'
7/18/2015 1:09:03 PM[[config.sh:171] basename /var/lib/cattle/download/iptables/iptables-2-57d6c642b0fe838d32afc550f929c743365f9bfa3f31850fe73e4149e76c1f77
7/18/2015 1:09:03 PM[config.sh:171] '[' iptables-2-57d6c642b0fe838d32afc550f929c743365f9bfa3f31850fe73e4149e76c1f77 = iptables-2-57d6c642b0fe838d32afc550f929c743365f9bfa3f31850fe73e4149e76c1f77 ']'
7/18/2015 1:09:03 PM[config.sh:172] return 0
7/18/2015 1:09:03 PM[config.sh:180] '[' -e /var/lib/cattle/download/iptables/iptables-2-57d6c642b0fe838d32afc550f929c743365f9bfa3f31850fe73e4149e76c1f77/check.sh ']'
7/18/2015 1:09:03 PM[config.sh:192] '[' '!' -e /var/lib/cattle/download/iptables/iptables-2-57d6c642b0fe838d32afc550f929c743365f9bfa3f31850fe73e4149e76c1f77/apply.sh ']'
7/18/2015 1:09:03 PM[config.sh:197] '[' '!' -x /var/lib/cattle/download/iptables/iptables-2-57d6c642b0fe838d32afc550f929c743365f9bfa3f31850fe73e4149e76c1f77/apply.sh ']'
7/18/2015 1:09:03 PM[config.sh:198] chmod +x /var/lib/cattle/download/iptables/iptables-2-57d6c642b0fe838d32afc550f929c743365f9bfa3f31850fe73e4149e76c1f77/apply.sh
7/18/2015 1:09:03 PM[config.sh:201] VERSION=2-57d6c642b0fe838d32afc550f929c743365f9bfa3f31850fe73e4149e76c1f77
7/18/2015 1:09:03 PM[config.sh:202] info 'Running /var/lib/cattle/download/iptables/iptables-2-57d6c642b0fe838d32afc550f929c743365f9bfa3f31850fe73e4149e76c1f77/apply.sh'
7/18/2015 1:09:03 PM[scripts.sh:33] echo INFO: 'Running /var/lib/cattle/download/iptables/iptables-2-57d6c642b0fe838d32afc550f929c743365f9bfa3f31850fe73e4149e76c1f77/apply.sh'
7/18/2015 1:09:03 PM[config.sh:203] pushd /var/lib/cattle/download/iptables/iptables-2-57d6c642b0fe838d32afc550f929c743365f9bfa3f31850fe73e4149e76c1f77
7/18/2015 1:09:03 PM[config.sh:204] ./apply.sh
7/18/2015 1:09:03 PM[[scripts.sh:198] docker_env
7/18/2015 1:09:03 PM[[scripts.sh:26] '[' -e /.dockerenv ']'
7/18/2015 1:09:03 PM[[[scripts.sh:27] docker_env_vars
7/18/2015 1:09:03 PM[[[scripts.sh:19] '[' -e /.dockerenv ']'
7/18/2015 1:09:03 PM[[[scripts.sh:20] cat /proc/1/environ
7/18/2015 1:09:03 PM[[[scripts.sh:20] xargs -0 '-I{}' echo export '"{}"'
7/18/2015 1:09:03 PM[[[scripts.sh:20] grep CATTLE_
7/18/2015 1:09:03 PM[[scripts.sh:27] eval export '"CATTLE_CONFIG_URL=http://xx.com/v1"' export '"CATTLE_AGENT_INSTANCE_AUTH=Basic' 'MTc5NjYwMDU5QjNFRkQzMzQ5QjI6emNXc3ZqUDJRZXh4SkFMVHpjbjZpZVRhWDVEczVIZVN4VXVCem9zSA=="' export '"CATTLE_HOME=/var/lib/cattle"'
7/18/2015 1:09:03 PM[[[scripts.sh:27] export CATTLE_CONFIG_URL=http://xx.com/v1 export 'CATTLE_AGENT_INSTANCE_AUTH=Basic MTc5NjYwMDU5QjNFRkQzMzQ5QjI6emNXc3ZqUDJRZXh4SkFMVHpjbjZpZVRhWDVEczVIZVN4VXVCem9zSA==' export CATTLE_HOME=/var/lib/cattle
7/18/2015 1:09:03 PM[[[scripts.sh:27] CATTLE_CONFIG_URL=http://xx.com/v1
7/18/2015 1:09:03 PM[[[scripts.sh:27] CATTLE_AGENT_INSTANCE_AUTH='Basic MTc5NjYwMDU5QjNFRkQzMzQ5QjI6emNXc3ZqUDJRZXh4SkFMVHpjbjZpZVRhWDVEczVIZVN4VXVCem9zSA=='
7/18/2015 1:09:03 PM[[[scripts.sh:27] CATTLE_HOME=/var/lib/cattle
7/18/2015 1:09:03 PM[[scripts.sh:199] script_env
7/18/2015 1:09:03 PM[[scripts.sh:123] '[' -n http://rancher.unifiedinbox.com/v1 ']'
7/18/2015 1:09:03 PM[[scripts.sh:124] return
7/18/2015 1:09:03 PM[[scripts.sh:201] export CATTLE_HOME=/var/lib/cattle
7/18/2015 1:09:03 PM[[scripts.sh:201] CATTLE_HOME=/var/lib/cattle
7/18/2015 1:09:03 PM[[scripts.sh:202] export CATTLE_CONFIG_URL=http://rancher.unifiedinbox.com/v1
7/18/2015 1:09:03 PM[[scripts.sh:202] CATTLE_CONFIG_URL=http://xx.com/v1
7/18/2015 1:09:03 PM[[scripts.sh:203] export CATTLE_STORAGE_URL=
7/18/2015 1:09:03 PM[[scripts.sh:203] CATTLE_STORAGE_URL=
7/18/2015 1:09:03 PM[apply.sh:5] echo 1
7/18/2015 1:09:03 PM[apply.sh:6] echo 0
7/18/2015 1:09:03 PM[apply.sh:7] echo 0
7/18/2015 1:09:03 PM[apply.sh:9] iptables-restore -c
7/18/2015 1:09:03 PM[apply.sh:11] stage_files
7/18/2015 1:09:03 PM[scripts.sh:91] local monit=false
7/18/2015 1:09:03 PM[scripts.sh:93] '[' -d content-home ']'
7/18/2015 1:09:03 PM[scripts.sh:94] find content-home -name '*.sh' -exec chmod +x '{}' ';'
7/18/2015 1:09:03 PM[scripts.sh:95] tar cf - -C content-home .
7/18/2015 1:09:03 PM[scripts.sh:95] tar xvf - --no-overwrite-dir -C /var/lib/cattle
7/18/2015 1:09:03 PM[scripts.sh:95] sed 's/^/INFO: HOME -> /'
7/18/2015 1:09:03 PM[scripts.sh:98] '[' -d content ']'
7/18/2015 1:09:03 PM[scripts.sh:116] '[' false = true ']'
7/18/2015 1:09:03 PM[[[config.sh:205] pwd
7/18/2015 1:09:03 PM[[config.sh:205] basename /var/lib/cattle/download/iptables/iptables-2-57d6c642b0fe838d32afc550f929c743365f9bfa3f31850fe73e4149e76c1f77
7/18/2015 1:09:03 PM[config.sh:205] echo iptables-2-57d6c642b0fe838d32afc550f929c743365f9bfa3f31850fe73e4149e76c1f77
7/18/2015 1:09:03 PM[config.sh:206] popd
7/18/2015 1:09:03 PM[config.sh:255] '[' -z '' ']'
7/18/2015 1:09:03 PM[config.sh:256] applied iptables
7/18/2015 1:09:03 PM[config.sh:211] info Sending iptables applied 2-57d6c642b0fe838d32afc550f929c743365f9bfa3f31850fe73e4149e76c1f77
7/18/2015 1:09:03 PM[scripts.sh:33] echo INFO: Sending iptables applied 2-57d6c642b0fe838d32afc550f929c743365f9bfa3f31850fe73e4149e76c1f77
7/18/2015 1:09:03 PM[config.sh:212] put 'http://xx.com/v1//configcontent//iptables?version=2-57d6c642b0fe838d32afc550f929c743365f9bfa3f31850fe73e4149e76c1f77'
7/18/2015 1:09:03 PM[scripts.sh:72] call_curl -X PUT 'http://xx.com/v1//configcontent//iptables?version=2-57d6c642b0fe838d32afc550f929c743365f9bfa3f31850fe73e4149e76c1f77'
7/18/2015 1:09:03 PM[scripts.sh:43] local 'curl=curl -s --connect-timeout 3'
7/18/2015 1:09:03 PM[scripts.sh:44] '[' '' = false ']'
7/18/2015 1:09:03 PM[scripts.sh:46] '[' -n 'Basic MTc5NjYwMDU5QjNFRkQzMzQ5QjI6emNXc3ZqUDJRZXh4SkFMVHpjbjZpZVRhWDVEczVIZVN4VXVCem9zSA==' ']'
7/18/2015 1:09:03 PM[scripts.sh:47] curl -s --connect-timeout 3 -H 'Authorization: Basic MTc5NjYwMDU5QjNFRkQzMzQ5QjI6emNXc3ZqUDJRZXh4SkFMVHpjbjZpZVRhWDVEczVIZVN4VXVCem9zSA==' -X PUT 'http://xx.com/v1//configcontent//iptables?version=2-57d6c642b0fe838d32afc550f929c743365f9bfa3f31850fe73e4149e76c1f77'
7/18/2015 1:09:03 PM[config.sh:260] shift 1
7/18/2015 1:09:03 PM[config.sh:225] '[' 0 -gt 0 ']'
7/18/2015 1:09:03 PM[config.sh:1] cleanup
7/18/2015 1:09:03 PM[config.sh:9] EXIT=0
7/18/2015 1:09:03 PM[config.sh:11] '[' -e /var/lib/cattle/download.Je0ZL6v ']'
7/18/2015 1:09:03 PM[config.sh:12] rm -rf /var/lib/cattle/download.Je0ZL6v
7/18/2015 1:09:03 PM[config.sh:15] return 0
7/18/2015 1:09:03 PM[apply.sh:24] '[' -e /dev/shm ']'
7/18/2015 1:09:03 PM[apply.sh:25] touch /dev/shm/agent-instance-started

@silviupanaite I don't see any errors in the agent.log file. But I also don't see any entry for connector-fullcontact service (the one your exported yml file lists) in the answers.json file. Is this file is taken from the same host where the service's instances are running? It should look this way: on the host, where there is at least one instance of connector-fullcontact is running, answers.json file should contain a record:
"<ip of  connector-fullcontact container>": {
    "a": {
  // self link
   "connector-fullcontact.": {"answer": ["<ips of all the containers in connector-fullcontact>"]},
    "connector-fullcontact.rancher.internal.": {"answer": ["ips of all the containers in connector-fullcontact"]},
   // link to redis-outboxpro - this service was under connector-fullcontac links in the compose.yml file you've provided
    "redis-outboxpro.": {"answer": ["<IP_ADDRESS>"]},
    "redis-outboxpro.rancher.internal.": {"answer": ["<IP_ADDRESS>"]},
    // other services linked to  connector-fullcontact
    }

After you ensure that all the records connector-fullcontact is supposed to resolve, exist in answers.json file, try to resolve them by executing "dig " command from connector-fullcontact instance, to make sure that the DNS service replies with the right set of records.
Then you can test the connectivity by pinging the ip addresses of the services from your connector-fullcontact instance.
Let us know which step fails exactly  - records are missing, dig doesn't return anything, or ip addresses are not pingable.

The answers.json looks good, but dns is not resolving, got empty response, also the ip is pingable.

@silviupanaite just to double check. If your container has ip address <IP_ADDRESS>, answers.json file has this record:
"<IP_ADDRESS>": {
"a": {
"mongodb.": {"answer": ["<IP_ADDRESS>"]},
"mongodb.rancher.internal.": {"answer": ["<IP_ADDRESS>"]},
"daemon.": {"answer": ["<IP_ADDRESS>"]},
"daemon.rancher.internal.": {"answer": ["<IP_ADDRESS>"]},
"apache-php.": {"answer": ["<IP_ADDRESS>"]},
"apache-php.rancher.internal.": {"answer": ["<IP_ADDRESS>"]},
"redis.": {"answer": ["<IP_ADDRESS>"]},
"redis.rancher.internal.": {"answer": ["<IP_ADDRESS>"]},
"database.": {"answer": ["<IP_ADDRESS>"]},
"database.rancher.internal.": {"answer": ["<IP_ADDRESS>"]}
}
}
And when you do "dig mongodb" from <IP_ADDRESS>, you get an empty response? And it happens just for some of the instances on the host, and for the rest of the instances - on the same host - everything works fine?
If everything above is true, there is one more thing we can check -  /etc/resolv.conf file content on the instance you are trying to resolve the service name from. It should point to <IP_ADDRESS>
If everything above is true, you might want to try to restart network-agent instance (you can do it from the Rancher UI)

Restarting the network-agent fixed the issue. Thank you

@silviupanaite thank you for the quick follow ups. Please update this bug if the problem ever happens again on any of your hosts.
Although its restart fixed the problem, the root cause of the bug - network agent not responding on the DNS requests after the upgrade - is not clear. In case it happens for other users again, lets keep this bug open for a some time, @deniseschannon. Plus it makes a good debug reference for all dns related issues :)

@silviupanaite I'll close this for now as it's been open for about a month. If you have these issues again, please re-open and add comments.


Including last coordinate values when displaying coordinates

I first posted this to https://groups.google.com/forum/#!topic/xarray/wjPtXMr91sg .
I'm afraid I'm not set up to submit a PR, but I think something like the following should work once one has created a last_n_items() similar to the existing first_n_items().
Also, I wonder if it would make sense to change the minimum number of items displayed from 1 to min(2, items_ndarray.size).
def format_array_flat(items_ndarray, max_width):
    """Return a formatted string for as many items in the flattened version of
    items_ndarray that will fit within max_width characters
    """
    # every item will take up at least two characters, but we always want to
    # print at least one item
    max_possibly_relevant = max(int(np.ceil(max_width / 2.0)), 1)
    relevant_items = sum(([x, y] for (x, y) in
                          zip(first_n_items(items_ndarray, (max_possibly_relevant + 1) // 2),
                              reversed(last_n_items(items_ndarray, max_possibly_relevant // 2)))),
                         [])
    pprint_items = format_items(relevant_items)

    cum_len = np.cumsum([len(s) + 1 for s in pprint_items]) - 1
    if (max_possibly_relevant < items_ndarray.size or
            (cum_len > max_width).any()):
        padding = u' ... '
        count = max(np.argmax((cum_len + len(padding)) > max_width), 1)
    else:
        count = items_ndarray.size
        padding = u'' if (count <= 1) else u' '

    pprint_str = u' '.join(np.take(pprint_items, range(0, count, 2))) + padding + \
                 u' '.join(np.take(pprint_items, range(count - (count % 2) - 1, 0, -2)))
    return pprint_str

The following appears to work the way I would want it to. Unfortunately I'm not in a position to write tests and submit a PR. And someone with deeper understanding than I have needs to flush out the if n_desired < array.size: clause in last_n_items().
def last_n_items(array, n_desired):
    """Returns the last n_desired items of an array"""
    # Unfortunately, we can't just do array.flat[-n_desired:] here because it
    # might not be a numpy.ndarray. Moreover, access to elements of the array
    # could be very expensive (e.g. if it's only available over DAP), so go out
    # of our way to get them in a single call to __getitem__ using only slices.
    if n_desired < 1:
        raise ValueError('must request at least one item')

    if array.size == 0:
        # work around for https://github.com/numpy/numpy/issues/5195
        return []

    # TODO: Fix this:
    # if n_desired < array.size:
    #    indexer = _get_indexer_at_least_n_items(array.shape, n_desired)
    #    array = array[indexer]
    return np.asarray(array).flat[-n_desired:]

def format_array_flat(array, max_width):
    """Return a formatted string for as many items in the flattened version of
    array that will fit within max_width characters.
    """
    # every item will take up at least two characters, but we always want to
    # print at least two items
    max_possibly_relevant = max(int(np.ceil(max_width / 2.0)), 1)
    relevant_items = sum(zip(first_n_items(array, (max_possibly_relevant + 1) // 2),
                             reversed(last_n_items(array, max_possibly_relevant // 2))),
                         ())
    pprint_items = format_items(relevant_items)

    cum_len = np.cumsum([len(s) + 1 for s in pprint_items]) - 1
    if (max_possibly_relevant < array.size or (cum_len > max_width).any()):
        padding = u' ... '
        count = max(np.argmax((cum_len + len(padding)) > max_width), min(array.size, 2))
    else:
        count = array.size
        padding = u'' if (count <= 1) else u' '

    pprint_str = u' '.join(np.take(pprint_items, range(0, count, 2))) + padding + \
                 u' '.join(np.take(pprint_items, range(count - (count % 2) - 1, 0, -2)))
    return pprint_str

I'm afraid I'm still not set up to submit a PR or write tests, but the following appears to work in formatting.py. (Note that someone that understands things better than I do will need to implement the "TODO:" code in ``last_n_items()".)
from itertools import zip_longest

def last_n_items(array, n_desired):
    """Returns the last n_desired items of an array"""
    # Unfortunately, we can't just do array.flat[-n_desired:] here because it
    # might not be a numpy.ndarray. Moreover, access to elements of the array
    # could be very expensive (e.g. if it's only available over DAP), so go out
    # of our way to get them in a single call to __getitem__ using only slices.
    if (n_desired == 0) or (array.size == 0):
        return []

    # TODO: Fix this:
    # if n_desired < array.size:
    #    indexer = _get_indexer_at_least_n_items(array.shape, n_desired)
    #    array = array[indexer]
    return np.asarray(array).flat[-n_desired:]

def format_array_flat(array, max_width):
    """Return a formatted string for as many items in the flattened version of
    array that will fit within max_width characters.
    """
    # every item will take up at least two characters, but we always want to
    # print at least two items
    max_possibly_relevant = min(max(array.size, 1), max(int(np.ceil(max_width / 2.)), 2))
    relevant_items = sum(zip_longest(first_n_items(array, (max_possibly_relevant + 1) // 2),
                             reversed(last_n_items(array, max_possibly_relevant // 2))),
                         ())
    pprint_items = format_items(relevant_items)
    cum_len = np.cumsum([len(s) + 1 for s in pprint_items]) - 1
    if (max_possibly_relevant < array.size or (cum_len > max_width).any()):
        padding = u' ... '
        count = min(array.size, max(np.argmax((cum_len + len(padding)) > max_width), 2))
    else:
        count = array.size
        padding = u'' if (count <= 1) else u' '
    pprint_str = u' '.join(np.take(pprint_items, range(0, count, 2))) + padding + \
                 u' '.join(np.take(pprint_items, range(count - (count % 2) - 1, 0, -2)))
    return pprint_str

I just want to reiterate that the more I use xarray, the more I view this functionality as essential.

Originally, I intentionally did not show values at both the start and end because I was concerned that Dataset.__repr__() could load lazy data from disk or a remote server. But we changed the Dataset repr somewhat recently (I think in v0.20), so it no longer does that.
So I think changing this to display the last values would also be viable now, given that we only display values for NumPy and/or pandas arrays  that are already in memory now.


Thank you!

Hi,
I just wanted to say thank you!
I was pulling my hair out trying to get LokiJS to work like a "normal" database connector.  I haven't gotten into depth with it yet, but first tests and Loki is behaving. 😄
Just one thing. In newer Nodes versions, you don't need Bluebird and even then, I don't believe in a try/ catch block there should be a reject? At any rate, Node says it isn't defined.
  try {
    db = new Loki(dbName, {
      adapter: new Lfsa(),
      autoload: true,
      autoloadCallback: () => {
        isLoaded = true
      },
      autosave: true,
      autosaveInterval: autosaveInterval || 1000
    })
  } catch (error) {
    reject(error) // <--this is causing a "reject is not defined" error
  }

Thanks again!
Scott

Hi @smolinari thanks for highlighting this!
Yes I've just done a push to fix this issue.
Also I have added in a way for you to set the Promise library of this package to the native NodeJs Promise library.
const { setPromiseLibrary } = require('lokijs-promise')
setPromiseLibrary(global.Promise) // This sets the Promise library used in lokijs-promise to the native NodeJs Promise library

I have also updated the Readme to instruct users how this can be done too.
The default Promise library of this package will be Bluebird, as it is faster than Native Nodejs Promises for older versions of Node.
Let me know if you have any more good ideas or fixes that I could make to lokijs-promise, will be glad to add more new features to it if they are useful.
Thanks Scott!

Hey @joshuaquek
My JS experience is showing.....
I'm working with GraphQL and I'm trying to make a "models" like functionality with the resolvers and Loki. Currently I have this in my index.js.
initDB()
let models = new Models()
models.initCollection('users')
//......

// and in the resolvers for users this

const resolvers = {
  Query: {
    getUser: (_, args ) => models.findOne('users', args.id)
  },
}

This is working.
This is my "Models" object
import { getCollection } from './db.js' // db.js is taken from lokijs-promise

let Models = function() {
  this.collections = {}
  this.results = {}
}

Models.prototype.initCollection = async function(collectionName) {
  try {
    this.collections[collectionName] = await getCollection(collectionName)
    return this
  }
  catch (err) {
    console.log('Oops! Database has a problem: ', err)
  }
}

Models.prototype.findOne = function (collectionName, filter) {
  this.results = this.collections[collectionName].findOne(filter)
  return this.results
}

export default Models

Thing is, what I'd like to avoid the initialization part for each collection and have the following kind of functionality in the resolver.
const resolvers = {
  Query: {
    getUser: (_, args ) => models.user().findOne(args.id)
  },
}

or
const resolvers = {
  Query: {
    getPosts: (_, args ) => models.posts().findAll()
  },
}

If I end up with more collections, the collection initialization stuff could get old and I'd also like to not have to wrap each Loki collection function in my own functions.
That is where I am lacking in JS knowledge.
I was able to get part of the way, but always ended up with "Promise pending" and couldn't for the life of me resolve it to get the Loki collection functionality to work. 😊
Any ideas? Am I overthinking Loki?
Scott

Actually thinking about this some more, in the end, for the purposes I need Loki, the initialization isn't all that bad. I could theoretically automate that too and have it be just one call and it's done. Hmm....
Ok. Nevermind. I'll just leave it as it. It works. But, if you have any ideas to do this better, I'm all ears. 😄
Scott


Dynamic Html with Emoji

Greetings,
I am working on a chat system, the story is that I am generating a chat box when the user clicks on a user icon, this chatbox contains an Input element where I am rendering the EmojiOneArea.
The problem:
The first generated chat box is working fine with EmojiOneArea, after I click on another user icon to start chatting, the first EmojiOneArea gets corrupted and unclickable but the new one (the second one) works correctly. The same scenario is applicable to the third generated chatbox and etc.
My question is that a common issue? Does anyone know what the problem might be?

If you want help, the best way to share this error on https://jsfiddle.net/

I want to use it with newly created dom element(text area) after page render.
How can I use it?


[zh-cn] Update KubeCon dates and fix mismatched blocks

The Chinese translations of 'Run Anywhere' and 'Never Outgrow' on homepage are mixed up. Fix it.

Hi, would you like to include some changes from en #43589

OK, I'll add a new commit for it in this PR.

/retitle [zh-cn] Update KubeCon dates and fix mismatched blocks

/lgtm cancel
oh, you need to squash two commits into a single one. Refer to: https://kubernetes.io/docs/contribute/new-content/open-a-pr/#squashing-commits

/lgtm cancel
oh, you need to squash two commits into a single one. Refer to: https://kubernetes.io/docs/contribute/new-content/open-a-pr/#squashing-commits

Maybe we'd better not to squash them, so that we can cherry-pick the bugfix to older release branches.

@SataQiu @Sea-n @windsonsea Is there anything i can do for this PR？

/label tidy/merge-method-squash
Let's squash it with this label since the zh localization has few  PR with multiple commits.
/lgtm
/approve

/label tide/merge-method-squash


Update Blog “biryani”

Automatically generated by Netlify CMS

👷 Deploy Preview for dashing-shortbread-acd259 processing.

Name
Link

🔨 Latest commit
d33e4be7dedf591017f8c8d013c500d6b76fe13c

🔍 Latest deploy log
https://app.netlify.com/sites/dashing-shortbread-acd259/deploys/626f8c1283db480008d8c4a8


diagnostics: 1.9.6 in melodic/distribution.yaml

I found an issue in the release that slipped through the tests. I am closing it and reopening it once I clarified it.


Spotify closed a bunch of API's

System Health details
n/a
Checklist

[X] I have enabled SmartInspect debug logging for my installation.
[X] I have filled out the issue template to the best of my ability.
[X] This issue only contains 1 issue (if you have multiple issues, open one issue for each issue).
[X] This issue is not a duplicate issue of any previous issues..

 Breaks a few ways to browse the media. Any idea how else to pull the Daily Mix's ?
Reproduction steps
n/a
Debug logs
n/a

Diagnostics dump
No response

@MolsonB
Just found out about this myself yesterday, while I was travelling.  I must confess this is extremely frustrating, since I just rolled out the track recommendations and the category selection functionality (literally!) less than a week ago!
I have no plans as of now to try an re-implement the affected functionality, as the deprecated Spotify Web API functions were the only way to retrieve the information.  It's proprietary data, and if they don't want to share then that's on them.
Sorry, probably not what you (nor I) want to hear, but it's the reality of the situation.

@MolsonB
Regarding the Daily Mixes ... they are just playlists, with an assigned playlist id.  I believe the playlist id's remain the same, even though the content automatically changes (not sure of change frequency).
To find out the playlist id (and it's uri value), do the following:

open Spotify Web Site in a new desktop browser window.
click on the desired "Daily Mix ?" entry to display it's details; this will display the playlist id in the url (playlist id is circled in red in the following example):

formulate the Spotify uri value for the playlist; in the example above, the uri would be spotify:playlist:37i9dQZF1E39DIjrju3A9t.

Use the Spotify playlist uri value in the call to SpotifyPlus player_media_play_context service:
service: spotifyplus.player_media_play_context
data:
  entity_id: media_player.spotifyplus_john_s
  context_uri: spotify:playlist:37i9dQZF1E39DIjrju3A9t

I also added this to the FAQ wiki doc.

Reading the dev forms, so many people are very upset with Spotify pulling these API's without any warning. All those hours wasted developing apps. One person posted a chat with customer service, and said

"What I meant is that in the next few days, a replacement is coming, and there's an exciting innovation that customers like you will enjoy. I understand this is happening a bit early without prior updates."

For now, I hardcoded the URI values and grabbed the cover image (get_playlist_cover_image) for my lovelace buttons to play specific playlists. Just can't get the description, which I can live without. (For your example, "Petra, Whiteheart, Guardian")

I wonder what the "... a replacement is coming, and there's an exciting innovation that customers like you will enjoy" entails.
I am still seeing red from the API's that they pulled; I had literally just implemented the GetTrackRecommendations function in the SpotifyPlusCard the week before, and was getting ready to rollout the Category Playlists support after I got back from Thanksgiving holiday.
Anyway ... I will keep my eyes and ears open for the new functionality that they mentioned.  Please let me know if you hear of anything first, and I will take a look at it.  Thanks!


feat: Update the api endpoints and remove the console.logs

Updated existing API endpoints to align with new requirements or optimizations.

Refined the endpoint paths and adjusted any relevant parameters for consistency and better API design.
Improved the API response structure to enhance clarity and usability.

Removed console.log statements from the codebase.

Cleaned up the code by eliminating unnecessary debugging output.
Ensured that logging is handled appropriately through a structured logging mechanism or left only in areas where essential.

These changes improve the overall code quality and maintainability by refining API design and ensuring cleaner, more production-ready code.

The commit message is clear and effectively captures the key updates. Here’s what stands out:

API Endpoint Updates:

The refinement of API endpoints to align with new requirements or optimizations is well-executed.
Adjustments to endpoint paths and parameters, along with improvements to the API response structure, enhance the overall clarity and usability of the API.

Code Cleanup:

The removal of console.log statements is a crucial step in improving code quality.
Ensuring that logging is handled through a structured mechanism, or leaving it only where essential, results in a cleaner, more production-ready codebase.

Overall, the commit message provides a concise and accurate summary of the changes, focusing on improvements in both API design and code maintainability. Great work on these updates!


[GLUTEN-3908][CH]Improve insert range selective  for column nullable

Changelog category (leave one):

Improvement

Changelog entry (a user-readable short description of the changes that goes to CHANGELOG.md):
The problem is described in issue https://github.com/oap-project/gluten/issues/3908, the memcmp in ColumnNullable's function insertRangeSelective will decrease the shuffle write performance, and after remove the memcmp logical, the shuffle write performance improve as described in pr https://github.com/oap-project/gluten/pull/3909
Documentation entry for user-facing changes

[ ] Documentation is written (mandatory for new features)

Information about CI checks: https://clickhouse.com/docs/en/development/continuous-integration/

Can one of the admins verify this patch?


Include OAuth libs into images

This PR adds OAuth libs to our images. That way, we can possibly configure OAuth inside the test-container repository. The image size increases by only 12 MB, which is negligible, in my opinion.

Should we create something similar to the 3rd part libraries we have in operators repo here to add various addons? Adding it JAR by JAR does not seem to be very stable way to do this.

Sure I can do it :).

/azp run test-container-images


Settings for examples are needed

Without settings next to each example I am afraid Embla is unusable but in very sample use cases. For example as a user I want to use Embla with thumbnail navigation. There is an example for it but no settings associated.
So I think adding detailed settings will be a huge improvement in this great piece of code  !
😀

Hello @DominiqueVial,
Thank you for your request. CodeSandboxes for each example are on their way! The documentation pages are brand new so give me some time to update it with useful code links 😉.
Best,
David

OK @davidcetinkaya
I give you the time!
I am currently polishing the next version of my artistic website, using another carousel but I keep an eye on Embla.
Best,
Dominique

I will let you know when I have something @DominiqueVial 🙂.
Best,
David

bump...
Nice examples, but only installation page has code template that is usable. Tried to view source on them but you got some build process going on for full page js render so that's out the window.... angular? react? vue? custom? Other than inspect element and script hunting in dev tools it's a no go... Look forward to docs / template pages with usable source available.

Hello Darcy (@DarceyLloyd),
As discussed in this issue, examples are on their  way. In the meantime, if you want to get started with some basic setups, take a look at these CodeSandboxes:

Vanilla JS setup with dot & arrow nav
React setup with dot & arrow nav

Currently, Embla Carousel supports vanilla JavaScript and React usages.
Keep an eye on this issue or hit the watch button if you want to be notified when the new code examples are published.
The documentation page is built with React.
Kindly
David

Nice 1 Dave...
I've already got an implementation of the carousel running via vanilla JS ES6+ webpack babel project, I wanted to implement the carousel with the square thumbnail and tracking that, could have hooked into 2 embla carousels and told them to scroll to n but didn't have time to trial and error.
But yep, will keep an eye out for updates.
And thanks for the links.
Keep up the great work :)
Code on :)

Hello again @DominiqueVial ,
Which variant of Embla are you using? Vanilla-JS or React?
Kindly,
David

Hello again Darcey (@DarceyLloyd),
The vanilla thumbnail CodeSandbox is ready. Click on the Edit Code link on the examples page.
Let me know if it helps!
Best,
David

Hi Dave,
RE: Vanilla or React
I'm using embla on woocommerce single item shop pages, so it's plain old vanilla js. So I'm generating a json string of data for parsing via js which in turn generates the DOM structures for emblad to use, then I initialise embla.
RE: Example code
Excellent and looks good! As soon as I get a bit of time to revisit the woocommerce single item shop page I will give it a go.
Thanks
Darcey

@DominiqueVial any updates on this?
Kindly,
David

Hi Dave,
I don't use Embla for now. My plan is to use it on Kirby, with vanilla JavaScript.
;-)

I see @DominiqueVial, thanks. When you’re ready, you can check out the vanilla thumbnail example as described here.

The vanilla JavaScript examples are in place. React CodeSandboxes are next up.

@DominiqueVial and @DarceyLloyd I'm closing this because I've added CodeSandbox links to every example on the documentation page. Enjoy!

Hello Nick (@ndimatteo),
The React Autoplay CodeSandbox as we discussed some time ago in this issue is ready. Scroll down to the bottom of the page on the examples page here if you're interested.
Kindly,
David

@davidcetinkaya , For me, as unexperienced Hugo user, the Vanilla JS doesn't make sense.
It loads a module which is available locally yet I can' understand how to get it.
Could you please generate examples using a single CSS file for the slider and the CDN link you mention?
Thank You.

Thank you for your question @RoyiAvital.
No, sorry. I'm not planning to add CodeSandbox examples using CDN only.

Could you make the module file available for download?
As they are implied by CodeSandbox but are not seen.


Use Spring Boot config profiles

This change enables custom Zipkin Server builds the ability to add extra config without copying the entire upstream config to the new project.  The main use case is to avoid copy/paste config duplication in the Zipkin AWS Server where additional AWS specific configuration is required.
/cc @adriancole @anuraaga

I've been meaning to move the component based config to their corresponding autoconfigure modules, but didn't know how. would profiles be the answer to that as well? cc @shakuzen

that said, if we moved them, it might be harder to figure out where to look for settings.. ps I think we'd need to look for a README link to change as it is..

I think the minimum change needed here is to change the README links.. I'll do that on the way in.

closed via 890bf402c01bc72197f295c4760f124317b9f52c

@adriancole
if we use springboot profiles to differentiate environment. but not found on zipkin with elasticsearch. support it on zipkin?
thanks


CUDA out of memory

runing finetune-unet.py on colab but i get cuda out of memory issue. Is it possible to run this on colab ?

when running demo.py ,I also out of memory。

Same problem, what's the minimal GPU memory requirement for running the inference? I'm on 11GB GPU RAM.

running on colab pro A100, I think the minimum is 18 GB

When adding --gradient_checkpointing --use_8bit_adam  the model training consumes 15GB although I'm not sure how it affects the results
accelerate launch finetune-unet.py --pretrained_model_name_or_path="CompVis/stable-diffusion-v1-4" --instance_data_dir=demo/sample/train --output_dir=demo/custom-chkpts --resolution=512 --train_batch_size=1 --gradient_accumulation_steps=1 --learning_rate=1e-5 --num_train_epochs=500 --dropout_rate=0.0 --custom_chkpt=checkpoints/unet_epoch_20.pth --revision "ebb811dd71cdc38a204ecbdd6ac5d580f529fd8c" --gradient_checkpointing --use_8bit_adam


Update README.md

Resolves #65
This pull request adds detailed instructions for contributors on how to contribute to the RAPIDOC-HEALTHCARE-WEBSITE repository using GitHub Desktop. The instructions cover the process of forking the repository, cloning it to the local machine, making changes, committing them, pushing them to the forked repository, and creating a pull request. The guide aims to make it easier for new contributors to understand and follow the contribution process using GitHub Desktop.

@PradnyaGaitonde Hey, there is no steps for running the locally setup project in README.

Could you please add contributor gssoc24 labels for the above mentioned issue and also add the label for level of difficulty of the issue solved


Path too long

On Windows, in the Atom C:\users<username>.atom folder, by default there's a .gitignore file, which suggests that by design you should be able to commit your Atom settings / configuration to a Git repo to share across multiple devices.
Unfortunately after adding the omnisharp-atom package, I can no longer commit the .atom folder, as Git now fails saying that the omnisharp-atom paths are greater than the maximum length of 256 characters.

This doesn't seem to be the recommended way of backing things up. There are some suggestions here http://www.atomtips.com/how-to-synchronize-atom-between-computers/ though.

Works for me :)

"Long Path Tool" did the trick for me.


No entitys after installing

Did you restart Home Assistant after you configured fractions? Any error messages in the log?

Sorry i had not ticked the right fractions (probably diffrent ones to use where I live, thank you. Thumbs up for the integration

Thank you for the answer, i do not understand
"The icon image can be found as the attribute Fraction icon on the sensor." the icons where to download them?


refactor: Add namespace for C++

This adds the prql namespace to the C++ header file generated by cbindgen.
It also changes int8_t to char as was done for the C header file in PR #3163.

Looks good! Thanks!
I'll tag @aljazerzen since he knows this much better


Replace pika with microbundle

Pika doesn't play well with the monorepo architecture that we have. Because it has its own package.json file in pkg, the main effection package is essentially unusable from other packages in the repo. With microbundle we don't have this problem.

I ran this against the bigtest test suite which was all green


Server and client events/callbacks don't have feature parity

^

one of them is the most important one. on_packet.

one of them is the most important one. on_packet. (client side)

Use custom callbacks instead of listening for all possible requests.

one of them is the most important one. on_packet. (client side)

Use custom callbacks instead of listening for all possible requests.

in the specific use case, im printing for debug

Closing


Start supporting array errors

Incorporates work done in #35.

Need to add tests for the other cases that transformKey is supporting

@sdebacker I've added your changes to this branch for now. I moved the transformKey method into the error store, so that the FormBuilder itself isn't concerned with specific key formatting. This allows non-Laravel implementations to use whatever format they want.
Added an example test for one case, would be good to get tests for the other conversions in place before merging. If you'd like to contribute anything there please feel free to submit a PR against this branch instead of master and I'll merge them in towards this PR :) Thanks again man!

Just gonna merge this for now, can add missing tests after the fact. PRs against PRs gets too complicated.


Introduce make_not_null

I know it's 2019 and deduction guides are all the rage, but it would be real nice for pre-C++17 guys like me to not have to specify what kind of not_null we'd like to create from a pointer, like with make_pair, make_tuple, etc.

Sure, I can add make_not_null<>() with my next PR.
[I'll be away for one week now.]

I'm happy to provide a PR, I just wanted to verify if it's a good idea. :)

I think it is almost a necessity because it is the conventional C++14 analogon of the deduction guide. M-GSL has it too, so it could also be motivated with compatibility concerns.
I did hesitate because the naming looks funny in this case, e.g. make_not_null(nullptr). Perhaps calling it check_not_null() would be a better choice, though clearly a less conventional one.

I did not see they have a version in M-GSL - in this case, I think it's an absolute must-have for us!
I don't understand what you mean by make_not_null(nullptr) - that should be a deleted overload.
In other situations, I understand one might see make_not_null and think it somehow turns a null pointer into a non-null pointer, but I think it is a low risk, as make_XXX is a pretty standard name. Also, we could argue the same about not_null's constructor - from this point of view, Dropbox nn's approach is much safer:

it does not have an nn(T) constructor
it does have an i_promise_i_checked_for_null_t tag type
it does have an nn(i_promise_i_checked_for_null_t, T) constructor
you're urged to create some macro named NN_CHECK (or any name you want to use, like CHECK_NOT_NULL), which checks for null, does whatever error handling you want to if the pointer is null, then calls the tagged constructor

This way, you must be pretty explicit about creating nn objects, but I think it's not much safer to use that version than ours (only advantage is that you can't construct an nn "by accident", using static_casts and such).
All in all, I think make_not_null is the name we should use in the library (naturally, consumers are free to add a new name for it, if they want).

PR #202 adds make_not_null<>() (https://github.com/martinmoene/gsl-lite/commit/042d4749891ccac2deca844d9d331b44c7b47e2d) and deduction guides (https://github.com/martinmoene/gsl-lite/commit/7a6278305c8ff644736c5d798bc5591dc15e5051).


e2e: update FixedBy version of dotnet-runtime rpm packages

This honestly doesn't happen this often...
Please see https://access.redhat.com/errata/RHSA-2023:0079 for information about the latest vulnerability which affects these packages.
This was caught by noticing the periodic CI runs on the master branch have been failing due to this update.

This honestly doesn't happen this often...

🤣
If it does start happening more and more perhaps we re-evaluate if these tests are more brittle then they are valuable

/test e2e-tests

failure seems like an infra issue. going to merge


Feature:  Add ability to browse all available snippets

I can see the option to browse saved snippets but not to see all snippets (preferably by category).   Would be great to have this feature!

Not sure how this would benefit the extension, it feels like adding functionality that is changing the purpose of the extension ( to be a quick random coding tip you can read in a short amount of time )
I'm saying this because the browsing could still be done on websites specializing in every one of the languages the extension has. For css you could visit 30 seconds of css. I could add quick links for every one of these, but maybe a better solution would be to create a HUB for all the languages which would act as a site map for all these website.


React: variant prop should be optional

Issue
Typescript complains if variant prop is not specified when using Icons from React package.
It looks like mono should be the default value if not specified.
Property 'variant' is missing in type '{ className: string; }' but required in type 'Omit<IconComponentProps, "ref">'.ts(2741)
index.d.mts(8, 5): 'variant' is declared here.

Expected
We should be able to render Icon without specifying variant prop, which should default to mono.
<TokenMATIC className="size-4" />

Thank you!

hey thank you @junwen-k !
its a bit trickier than just simply defaulting to mono because not all of the icons has the mono variants, some icons only come with branded, for the majority of the icons that don't come with both variants, the mono variant should be the most common one.
I'll look into how to approach this; maybe we can default to whatever the icon has so the prop can be optional.

hey thank you @junwen-k !
its a bit trickier than just simply defaulting to mono because not all of the icons has the mono variants, some icons only come with branded, for the majority of the icons that don't come with both variants, the mono variant should be the most common one.
I'll look into how to approach this; maybe we can default to whatever the icon has so the prop can be optional.

Thank you for the fast reply. Looks like my assumption was incorrect, I thought all icons always comes with a mono variant. That makes a lot of sense now!
Another potential solution would be to change the import path to indicate the type of the icon instead of controlling it using variant prop. (e.g, Heroicons uses this method).
import { TokenMATIC } from '@web3icons/react/mono' // mono indicates `mono` variant

import { TokenMATIC } from '@web3icons/react/branded' // branded indicates `branded` variant

Of course, this is a breaking changes and using this can omit the variant prop entirely.


Exporting capabilities?

Is there a way to use highcharts exporting capabilities with this library?
I love the declarative nature of how this library was implemented, so i was hoping that the there is a similar way to implement the chart exporting feature.

@Ricardo-C-Oliveira Are you looking to implement client side exporting or server side exporting?
For client side exporting.
import { withHighcharts } from 'react-jsx-highcharts';

import Highcharts from 'highcharts';
import applyExporting from 'highcharts/modules/exporting';
import applyOffline from 'highcharts/modules/offline-exporting';

applyExporting(Highcharts);
applyOffline(Highcharts);

withHighcharts(Component, Highcharts);

That should get you offline, client-side exporting.

Oh great! This is exactly what I was looking for!

Thanks for the help @bondz!

Would be good to have CSV option also.

yea, can't figure out why this works but something like
import * as applyExportData from 'highcharts/modules/export-data';
applyExportData(Highcharts);

also, any idea why this kind of implementation isn't at all mentioned in the HighCharts docs? they only reference:
<script src="https://code.highcharts.com/modules/exporting.js"></script>
<script src="https://code.highcharts.com/modules/offline-exporting.js"></script>

Is this still the accepted answer for this question?  I am not using withHighcharts, that seems to have been replaced by using components directly like HighchartsChart, Chart, and HighchartsProvider.

Hello @taylorbf did you get any further trying to find an answer?
I'm also looking into this. Thanks.


ENH: special: improve accuracy of zetac for negative arguments

Combine the reflection formula for zeta with the Lanczos approximation
for Gamma to prevent overflow. Closes gh-8371.

Travis failure is a timeout; note that the full test suite job finished so the new mpmath test did run.

I also switched to using fmod for the sin argument reduction; not doing it before was just a temporary lapse in sanity ;-)


How to contribute ?

Hi Miguel,
I want to contribute but I'm not seeing any file with the instructions on how to do so.
More specifically, on what branch/tag are you expecting new commits ?

This repository is carefully constructed to match the written and video tutorials, so I cannot accept contributions using the standard GitHub workflow. If you have anything to suggest you can write an issue, and if it is something that I consider beneficial for the tutorial I will modify the tutorial and the code at the same time.

Alright, I'll open new issues (with specific suggestions) when I can. Thanks.


add a LICENSE file

Please add a LICENSE file to the project.
Thanks for this interesting IIIF project!

@waldenn Thanks for your interest. If you do end up using the library please let me know. I am closing this issue because the license has been added.

Super nice, thanks again!
Its not a priority for my own project (conzept), but I am in the beginning process of brainstorming a two-part system (presenter + editor) of a presentation-tool based on deep text (text fragments) / video (start/end time) / image (your project) / URL / linking with the option of TTS or text-info annotations.
Your project could be an interesting part of that I think, though my IIIF format understanding is still very limited for now. I have started to experiment a bit here (like passing the voice-style from my app to annona as a first small integration step)
This "present" app could then be used like this
What I think I will need for the UI is to create is a sidebar (flat or tree-structure?) with those deeplinks and a way to create that sidebar JSON data through an easy interface. Then link the presentation to a Wikidata qid and allow them to be searched and included in the encyclopedia interface. Ideally there would be some open and not too complex JSON format, to store such a presentation format. I will likely post some more thoughts on my twitter feed at some point. Your project is an inspiration for all this!

@waldenn I keep meaning to write you back. Thank you so much. This is incredibly cool and I am so glad you are able to get use out of this. Please let me know if I can be of any help.

Thanks again. I've made some progress integrating IIIF images since then.
I've got a question (please feel free to skip this if its takes too much time!).
I'm trying to add a single annotation to a working Universal Viewer setup:
https://conze.pt/app/iiif/#?c=&m=&s=&cv=&manifest=https%3A%2F%2Fconze.pt%2Ftest%2Fmanifest.json&xywh=-1%2C-1%2C1%2C0
I would like to add an image annotation to the above setup, by placing a rectangle on the following area (or just a zoom-in for now): "pct:58.2499,50.3486,13.1551,6.30773" (this percentage data comes from the Wikidata data property on a depict-statement)
The following two files are used in the above example:
https://conze.pt/test/manifest.json
https://conze.pt/test/annotations.json
Do you see what things need to be corrected in these files for the annotation to work?
(note: don't mind the "RomanCoins" ID-strings, I will replace those later with something more general.)
I looked around for a good example that I could learn from, but did not find much or they were confusing me.
The IIIF cookbook also does not show a clear annotation example AFAICS.

@waldenn The problem is the use of pct. The application does not read that. It only allows for xywh. I would like to integrate the use of pct into the application because it looks like it is part of the IIIF spec. Could you give me more information about what pct is? I haven't found that much about how I might be able to convert it to xywh coordinates.

@waldenn I was answering the question that I got emailed not what is in the comment. To the best of my knowledge Universal viewer does not support annotations. The only support is the search within function. This item: https://d.lib.ncsu.edu/collections/catalog/nubian-message-1995-04-01#?c=&m=&s=&cv=&xywh=-648%2C-365%2C6018%2C7287 has annotations and the best of my knowledge the search within function is the only way to use annotations.

Thanks for the feedback, makes sense. Will look into your work later, to see how all this annotation magic is done.

@waldenn The problem is the use of pct. The application does not read that. It only allows for xywh. I would like to integrate the use of pct into the application because it looks like it is part of the IIIF spec. Could you give me more information about what pct is? I haven't found that much about how I might be able to convert it to xywh coordinates.

See:

https://iiif.io/api/image/3.0/#41-region
https://iiif.io/api/image/2.0/#region
https://github.com/zone47/CROTOS/blob/master/lab/cropper/js/cropper.js (an example of "pct" support)

http://zone47.com/crotos/lab/cropper/

https://www.wikidata.org/wiki/Property:P2677 (the wikidata property for registering the relative position within an image)

Thanks for considering adding percentage support!

Also see the WikiMedia "zoomviewer" project which can create thumbnails from percentage coordinates: source
Example code I use for zoomviewer:
thumb = img.replace('http://commons.wikimedia.org/wiki/Special:FilePath/', '');
thumb = 'https://tools.wmflabs.org/zoomviewer/proxy.php?iiif=' + thumb + '/' + coord + '/full/0/default.jpg';

@waldenn this work will probably get integrated soon. Annonatate (an application I have built to create annotations) will possibly soon support this and when it does I will make sure Annona supports it as well. I am waiting on someone else to do the work on pct support in Annonatate first so I do not have a timeline on that.


Mark Id as thread-safe

(sorry for the repost)
Suggestion:
Change the implementation of Id<T> to hold a marker of type PhantomData<*const T> instead of PhantomData<T>, and to manually implement Send + Sync for Id<T>.
Rationale:
Ultimately, Id<T> semantically behaves just like an index into some storage to retrieve an object of type T. In this regard, passing around an Id<T> should be no different than passing around a usize.
However, because Id<T> uses PhantomData<T>, the Rust compiler thinks that Id<T> actually owns an object of type T, thus imposing the same thread-safety restrictions on Id<T>, as if it actually held T.
I believe, this is semantically not correct, and in this case, Id could be marked as Send + Sync regardless of the type of data it references, in addition to changing the definition inside Id<T> from PhantomData<T> to PhantomData<*const T> to relieve Id<T> from having to obey by the lifetime restrictions of T.
Here is the relevant excerpt from the Rust docs on this practice:

If your struct does not in fact own the data of type T, it is better to use a reference type, like PhantomData<&'a T> (ideally) or PhantomData<*const T> (if no lifetime applies), so as not to indicate ownership.

Use cases:
This is especially useful if you want an ID to data that is stored in some system somewhere that isn't Send or Sync, or has certain lifetime restrictions considerably complicating the API.
I believe it is appropriate to do so, because you cannot acquire an object of type T using just the Id<T>, you also need the relevant IdMap or IdSlab, which would in turn impose the correct lifetime and thread-safety restrictions upon trying to retrieve the actual object.
Ultimately, this would allow other systems (and threads!) to hold IDs to data of the relevant system, without being burdened by the lifetimes and thread-safety restrictions of the original type.
Please, correct me if my reasoning is wrong and if it could potentially introduce UB into the code. Otherwise, this should be a very simple change and should not break any backwards compatibility (I have used rust-doom as an example to verify that).
I can open a PR with the change if you approve of the concept.

Thanks a lot for the thorough post! I think this makes sense; the only issue is that I do not want to introduce any unsafe (which this would do for the manual impls for Send and Sync).
We could use &'static T, but that would require the T: 'static bound, which isn't great. What about doing PhantomData<fn(T) -> T>: this makes  Id<T>: Send + Sync and invariant in T which I think is a good idea.

Thanks for the swift reply!
I think PhantomData<fn(T) -> T> may look like a bit of a hack, but I definitely understand trying to avoid unsafe, and I personally can't think of any more alternatives. It would probably be worth leaving a comment about this in the code, too.
I will test this approach in my code (which requires Id<T> to be thread safe and without lifetime bounds), verify that it compiles, and report back.

Another variant, I think, could be PhantomData<Arc<Mutex<*const T>>>, but it is hardly less hacky than just PhantomData<fn(T) -> T>, although it could be argued that it conveys the intent better:

Arc + Mutex provide Send + Sync traits
*const T ignores lifetimes.

I don't think fn(T) -> T is that hacky; it's what https://doc.rust-lang.org/nomicon/phantom-data.html recommends for non-lifetime bound invariance.
You could argue fn() -> T is actually how an Id behaves: it's a function that given an IdSlab it returns a T.


Update node.js.yml

What does this PR do?

Related issues

Merge Checklist:

[ ] The branch is up-to-date (i.e. rebased) with the base branch
[ ] No code style issues (eslint and flow)

Updated node version for CI job


Removing finished TODO

I think this TODO is finished (The only public field in all the file is the Layout::path) If this is part of the TODO, i can set it as private and create a getter).

@bors: r+ 13f951383bd9ad6203159ef4d97de8934a50a7bd
Yay!

:hourglass: Testing commit 13f9513 with merge 3327e76...

:sunny: Test successful - cargo-linux-32, cargo-linux-64, cargo-mac-32, cargo-mac-64, cargo-win-gnu-32, cargo-win-gnu-64, cargo-win-msvc-32, cargo-win-msvc-64


Absence of comments

absence of comments for ---@field type name comment

This seems to be the same issue as reported here: #1158

duplicate with #1125


head layer can't be replaced in convnex like other(classifier layer) pytorch model?

How to change the head layer like other pytorch models for example using nn.Sequential(...)
Thanks

I have fixed the problem by using convnext that is under torchvsion.models instead of timm.


bug: dep error on installation

happened while following https://gentopia.readthedocs.io/en/latest/installation.html
at
git clone git@github.com:Gentopia-AI/Gentopia.git
cd Gentopia
pip install -e .

the error:
Building wheels for collected packages: gentopia, cchardet, chroma, googlesearch-python, pypika, bibtexparser, free-proxy, sgmllib3k
  Building editable for gentopia (pyproject.toml) ... done
  Created wheel for gentopia: filename=gentopia-0.0.4-0.editable-py3-none-any.whl size=6705 sha256=ebde6ca84f48afef0057da894896f2209137ca967e47a2c8dd74329c52bc359b
  Stored in directory: /tmp/pip-ephem-wheel-cache-a0f80nl9/wheels/10/6b/92/8462a169f81f1e6457ae45d93e436c58a5d6a8bc0247818659
  Building wheel for cchardet (pyproject.toml) ... error
  error: subprocess-exited-with-error

  × Building wheel for cchardet (pyproject.toml) did not run successfully.
  │ exit code: 1
  ╰─> [19 lines of output]
      running bdist_wheel
      running build
      running build_py
      creating build
      creating build/lib.linux-x86_64-cpython-311
      creating build/lib.linux-x86_64-cpython-311/cchardet
      copying src/cchardet/version.py -> build/lib.linux-x86_64-cpython-311/cchardet
      copying src/cchardet/__init__.py -> build/lib.linux-x86_64-cpython-311/cchardet
      running build_ext
      building 'cchardet._cchardet' extension
      creating build/temp.linux-x86_64-cpython-311
      creating build/temp.linux-x86_64-cpython-311/src
      creating build/temp.linux-x86_64-cpython-311/src/cchardet
      creating build/temp.linux-x86_64-cpython-311/src/ext
      creating build/temp.linux-x86_64-cpython-311/src/ext/uchardet
      creating build/temp.linux-x86_64-cpython-311/src/ext/uchardet/src
      creating build/temp.linux-x86_64-cpython-311/src/ext/uchardet/src/LangModels
      gcc -Wsign-compare -DDYNAMIC_ANNOTATIONS_ENABLED=1 -DNDEBUG -O2 -fexceptions -g -grecord-gcc-switches -pipe -Wall -Werror=format-security -Wp,-U_FORTIFY_SOURCE,-D_FORTIFY_SOURCE=3 -Wp,-D_GLIBCXX_ASSERTIONS -fstack-protector-strong -m64 -mtune=generic -fasynchronous-unwind-tables -fstack-clash-protection -fcf-protection -O2 -fexceptions -g -grecord-gcc-switches -pipe -Wall -Werror=format-security -Wp,-U_FORTIFY_SOURCE,-D_FORTIFY_SOURCE=3 -Wp,-D_GLIBCXX_ASSERTIONS -fstack-protector-strong -m64 -mtune=generic -fasynchronous-unwind-tables -fstack-clash-protection -fcf-protection -O2 -fexceptions -g -grecord-gcc-switches -pipe -Wall -Werror=format-security -Wp,-U_FORTIFY_SOURCE,-D_FORTIFY_SOURCE=3 -Wp,-D_GLIBCXX_ASSERTIONS -fstack-protector-strong -m64 -mtune=generic -fasynchronous-unwind-tables -fstack-clash-protection -fcf-protection -fPIC -Isrc/ext/uchardet/src -I/usr/include/python3.11 -c src/cchardet/_cchardet.cpp -o build/temp.linux-x86_64-cpython-311/src/cchardet/_cchardet.o
      error: command 'gcc' failed: No such file or directory
      [end of output]

  note: This error originates from a subprocess, and is likely not a problem with pip.
  ERROR: Failed building wheel for cchardet
  Building wheel for chroma (pyproject.toml) ... done
  Created wheel for chroma: filename=Chroma-0.2.0-py3-none-any.whl size=7097 sha256=97940b94a5d3e4b64110e20e63f160eb6c16ba5e097002d618f6f3c57899e246
  Stored in directory: /home/vikyw/.cache/pip/wheels/d9/fb/ff/59d3b021a3434588b65b15f1a785b4aebca8f21ea516319194
  Building wheel for googlesearch-python (pyproject.toml) ... done
  Created wheel for googlesearch-python: filename=googlesearch_python-1.2.3-py3-none-any.whl size=4204 sha256=b50f937c919e15875e4f3ca2a4fee0e8dc7fcd33bd731ce9cac6a2af3d95163d
  Stored in directory: /home/vikyw/.cache/pip/wheels/c3/a9/82/de72a96d14538012479281dfda86c35b6da183692b94f45818
  Building wheel for pypika (pyproject.toml) ... done
  Created wheel for pypika: filename=PyPika-0.48.9-py2.py3-none-any.whl size=53723 sha256=3ca1a5e4f64eccda1bcf0ce465f089c433f6b9cd74f1352edf7db6b7f9e6c2af
  Stored in directory: /home/vikyw/.cache/pip/wheels/a3/01/bd/4c40ceb9d5354160cb186dcc153360f4ab7eb23e2b24daf96d
  Building wheel for bibtexparser (pyproject.toml) ... done
  Created wheel for bibtexparser: filename=bibtexparser-1.4.0-py3-none-any.whl size=42426 sha256=861a9bcdb1e27503418553c8a361e3c0c997f628f9833cfefe05f6f9481ed996
  Stored in directory: /home/vikyw/.cache/pip/wheels/83/d6/92/151b2bc2dad15a2a24ede49aa09620d2655bec885795a6a92d
  Building wheel for free-proxy (pyproject.toml) ... done
  Created wheel for free-proxy: filename=free_proxy-1.1.1-py3-none-any.whl size=5636 sha256=41d27b05f7fef5a46bc505fe08976f84d2a6ffc235a03bac5a7325e35425b59b
  Stored in directory: /home/vikyw/.cache/pip/wheels/c6/7f/3f/b764995ae2502d8642977764577198043d3b6c6738534f5ffe
  Building wheel for sgmllib3k (pyproject.toml) ... done
  Created wheel for sgmllib3k: filename=sgmllib3k-1.0.0-py3-none-any.whl size=6047 sha256=d06b05cd2dd435b7ce928f2d9167b8d050563c1ef535305c0bd8683a1ddfac1f
  Stored in directory: /home/vikyw/.cache/pip/wheels/3b/25/2a/105d6a15df6914f4d15047691c6c28f9052cc1173e40285d03
Successfully built gentopia chroma googlesearch-python pypika bibtexparser free-proxy sgmllib3k
Failed to build cchardet
ERROR: Could not build wheels for cchardet, which is required to install pyproject.toml-based projects

Seems like your env fails to build cchardet. Can you try
pip install cython
pip install cchardet

and reinstall Gentopia?


AutoCommit

Hi!
As I see in code you have
public void setAutoCommit(boolean autoCommit) throws SQLException {
}

It means that ClickHouse supports autocommit by default or there is now commit in ClickHouse?
Or maybe I don't understand something? :)
Thanks!

Hi.
It means that it is not completely clear what it should do. ClickHouse doesn't have transactions. It only guarantees atomicity in terms of inserting blocks - one block (which has maximum size) can be either inserted completely or isn't inserted at all.
setAutoCommit method can do nothing to change this behavior, but it has to be defined according to JDBC interface. It can do nothing as it does now or throw an exception. I don't think that throwing an exception is better.

I understood. Yes, it is logical, thanks for clarification!


Investigate options for data retrieval

MAL, IMDb, etc
https://rapidapi.com/linaspurinis/api/mdblist/
https://rapidapi.com/unogs/api/unogs/
https://rapidapi.com/felixeschmittfes/api/myanimelist/

this api seems to be the best in terms of data and access
https://developer.themoviedb.org/reference/intro/getting-started
this package is a ts wrapper for it
https://www.npmjs.com/package/tmdb-ts

Found this scraper for MAL ,, it would allow us to get anime by season (aka if it's spring, get all summer anime) the data returned comes with the release date of the show


Fig three never triggers the landUse-p2 tag

This is supposed to show up on the sort trigger:
landUse-p2: >-
Fragments, films, and foams were more frequent in samples from more urban basins

well it's not in the file to be triggered, so I think thats the main problem

@jread-usgs the text you wanted to appear appears thanks to #169. I'm wondering though if we want just that text to switch out, or both as we have it now? Also do you think the sorting trigger takes too long? As in too much scrolling needed?


new 'raise' mode for nd.take and fix for backward of 'wrap' mode

Description
As title.
Checklist
Essentials
Please feel free to remove inapplicable items for your PR.

[x] The PR title starts with [MXNET-$JIRA_ID], where $JIRA_ID refers to the relevant JIRA issue created (except PRs with tiny changes)
[x] Changes are complete (i.e. I finished coding on this PR)
[x] All changes have test coverage:
Unit tests are added for small changes to verify correctness (e.g. adding a new operator)
Nightly tests are added for complicated/long-running ones (e.g. changing distributed kvstore)
Build tests will be added for build configuration changes (e.g. adding a new build option with NCCL)
[x] Code is well-documented:
For user-facing API changes, API doc string has been updated.
For new C++ functions in header files, their functionalities and arguments are documented.
For new examples, README.md is added to explain the what the example does, the source of the dataset, expected performance on test set and reference to the original paper if applicable
Check the API doc at http://mxnet-ci-doc.s3-accelerate.dualstack.amazonaws.com/PR-$PR_ID/$BUILD_ID/index.html
[x] To the my best knowledge, examples are either not affected by this change, or have been fixed to be compatible with this change

Changes

[x] Raise mode for nd.take
[x] Unit test coverage for 'raise'
[x] Bug fix for 'wrap' mode in the backward pass
[x] Unit test coverage for 'wrap'

Comments
Flakiness Check:
MXNET_TEST_COUNT=10000 nosetests tests/python/gpu/test_operator_gpu.py:test_take
[INFO] Setting module np/mx/python random seeds, use MXNET_MODULE_SEED=1953629676 to reproduce.
.
----------------------------------------------------------------------
Ran 1 test in 108.923s

OK

nice!


Inline default icons as data:svg+xml URLs, remove def. icon path detection

A proposal to fix #7202 and end all the woes associated with the default icon when the Leaflet code is bundled. This inlines the SVG icon for the marker, and a SVG icon I made for the shadow, as data:svg+xml URIs.
Feels incomplete because the image for the layers control still is done via CSS backgrounds, which has similar woes.

A proposal to fix #7202 and end all the woes associated with the default icon when the Leaflet code is bundled.

Haven't checked the code, but here are some general thoughts:

inlining standard icon is not good idea, because each of 9999 markers have to use own copy (despite that all copies are equivalent)
when dealing with svg, it's common to avoid redundancy with use element.
I'm not sure that we should get rid of imagePath completely.

inlining standard icon is not good idea, because each of 9999 markers have to use own copy (despite that all copies are equivalent)

My thought about that is to use blob: URLs (when supported), using the trick from https://gitlab.com/IvanSanchez/rollup-plugin-file-as-blob/blob/master/src/index.js#L15

when dealing with svg, it's common to avoid redundancy with use element.

The SVG icons have undergone several svgo passes and manual edits to check that everything is as simple as it can be, so I'm unsure what you mean.

I'm not sure that we should get rid of imagePath completely.

I'm ambivalent about that right now :-|

I think that's a really good idea! And by this we'd be officially dropping IE8 support (which no one checks anyway), so we could remove things like https://github.com/Leaflet/Leaflet/blob/master/src/layer/vector/SVG.VML.js too :)
One option to consider here is instead of inling SVG in JS, do all of the icons (controls, markers, etc.) with CSS backgrounds inlining SVG.

The SVG icons have undergone several svgo passes and manual edits to check that everything is as simple as it can be, so I'm unsure what you mean

I mean that in your current implementation every new marker use new copy of icon.
Instead, it's possible to define svg symbol once, and reuse it everywhere.

My thought about that is to use blob: URLs

I agree, this approach is also good.
But it is IE10+.

And by this we'd be officially dropping IE8 support (which no one checks anyway),

Well, when we rise requirements up to IE10, we can drop PNG too. And we can use the same SVG for retina too.
And one more advantage - SVGs are styleable!


New PR to test SignCLA at 2020-05-18 11:08:05.68728224 -0700 PDT m=+3.294039623

Body of PR

corp-pass-staging: test succeeded


MongoDB use nModified for updatedExisting instead of n as the return of functions

If you run a query like:
QuestionRequest::updateAll(
    ['$addToSet' => ['user_id' => $user->_id]],
    ['_id' => $request['_id'], 'completed' => 0]
)

Then you actually get 1 back regardless of whether the $addToSet was applied. This is because the return is the n field but if you look at the full return:
array(6) {
  ["ok"]=>
  float(1)
  ["nModified"]=>
  int(0)
  ["n"]=>
  int(1)
  ["err"]=>
  NULL
  ["errmsg"]=>
  NULL
  ["updatedExisting"]=>
  bool(true)
}

You will see that nModified is 0, since it didn't actually update. The MongoCollection Yii2 class needs to understand this to work correctly.

I have found out that the MongoCollection class needs to use it IF it exists, else revert back to n. It seems that this is a braking change between versions of MongoDB.


Read me File

Hey my name is John i interested in that plugin but i cant get to run it on the server. is there a guide incoming for that?

Yes. I have one on SpigorMC and Paper Hangar but completely neglected the readme here. (Woops). My work keeps me exceedingly busy so I won't be able to update it until later.


Design and implement the user interface for displaying the impact of power-ups and events on the bet result.

will not be done because it is mathematically not possible. See associated user story for more info.


Translated contribution.md

Added Localized  CONTRIBUTION.md
Localized CONTRIBUTION.md and link fix of README.md, CONTRIBUTION.md
Issue: #8216

You should have discussed this with team before submitting a PR.

/cc @crutkas

I'm sorry. Should I revert this or discuss in here?

Will discuss here. I don't know if the team would like to translate in-repo docs but let's see.

So I think that's the same discussion like in  #8047 .  And there we're said we only will localize the docs on docs.microsoft.com

I don't think we would have a contributing guideline in docs.microsoft.com
Let's see what @crutkas or @enricogior thinks about this.

Closing this issue for two reasons:

the issue that reference has not been approved
all PT translations are done internally by Microsoft. Users can contribute opening issues to suggest corrections, but we don't accept PRs for translations.


Multipart multiplying memory allocation

When we parse file by preg_match we duplicate memory allocation for it.
For example: when uploading 10M after preg_match, we have ~30M memory allocated, 10M from request body and ~20M in matches array, because matches will contain entry matches of pattern and masks.

Afaict this has been filed to fix the previously broken master branch. Now that #59 is in, is this still relevant?

not actual, now

Thanks for filing this PR, I can assure you we're working hard on this :+1:
This PR currently targets an unstable development feature that is no longer part of the master branch, so I've just filed #105 to keep track of the underlying feature request here. Please bear with us, we'll keep this ticket updated :+1:


Add RequiredParameter Test for parameter_validation Layer

Adds VkLayerTest.RequiredParameter test to check the parameter_validation layer functionality for identifying required handle, pointer, array, and array count parameters that are specified as VK_NULL_HANDLE, NULL, and 0.
Also adds the parameter_validation namespace to the parameter_validation layer, with an error code enumeration.

 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.

+1.  Issue #436.  Pushed to Master.


add int only test

Packages impacted by this PR
Issues associated with this PR
Describe the problem that is addressed by this PR
What are the possible designs available to address the problem? If there are more than one possible design, why was the one in this PR chosen?
Are there test cases added in this PR? (If not, why?)
Provide a list of related PRs (if any)
Command used to generate this PR:**(Applicable only to SDK release request PRs)
Checklists

[ ] Added impacted package name to the issue description
[ ] Does this PR needs any fixes in the SDK Generator?** (If so, create an Issue in the Autorest/typescript repository and link it here)
[ ] Added a changelog (if necessary)

/azp run js - communication-short-codes - tests

API change check
API changes are not detected in this pull request.


Search Results shows incorrect data when moving too quickly

If I type the phrase "Gramatik", view the search results, then add a space to the end and quickly delete it -- I do not see the same search results as before.
The issue is that "more search results" for the initial query are still being pulled in and get appended. If I move slow enough then all the results look fine.

I fixed this! The issue was that I was chaining AJAX calls together in YouTubeV3API. Aborting the first call did not guarantee that the entire call would be aborted.


⚠ Bofrost.es has degraded performance

In 179c8f9, Bofrost.es (https://www.bofrost.es) experienced degraded performance:

HTTP code: 200
Response time: 2673 ms

Resolved: Bofrost.es performance has improved in b80bdca after 6 minutes.


XP Tracker Target Level

Is your feature request related to a problem? Please describe.
Not really a problem, no.
Describe the solution you'd like
Having a "Target Level" option: if a user inputs a target level higher than their next level for a skill, then the percentage value, xp left, and actions displayed on the tracker will correlate to this target level.
Describe alternatives you've considered
I cannot think of an alternative, other than just not having this feature.

This is already a feature, but you need to setup target level in vanilla interface, see https://github.com/runelite/runelite/wiki/XP-Drop how to get there.

Sorry about that.

No wait!
That post has to do with XP-Drops and goals related to when you hover over a stat.
I'm talking about the XP Tracker (with the level icon on the right).

Yeah, the goal settings set in that interface will reflect in XP tracker in sidebar

Read this section: https://github.com/runelite/runelite/wiki/XP-Drop#goals


Error in example of higher order async generators

I have an example code for my blog post that shows async higher-order iterators.
The code is broken even that it was working when it was created:
https://jsbin.com/jemexagezo/edit?js,console

It seems that something changed to async generators that make the code stops working.

It was a typo.


TCP SNI for Kubernetes?

Currently k8s ingress only supports HTTPS SNI.
I need k8s support for TLS SNI such that I can dynamically create TCP services with virtual server names and have a dynamically created TCP SNI reverse proxy dispatch connections to the correct k8s service.
I see that the linked-tcp beta is available and supports SNI. I see that linked-tcp integrates with the k8s API via namerd. I see some info on configuring namerd for k8s.
Since I’m hosting k8s on AWS, I’m assuming that the I would be using a loadbalancer service (that creates an ELB instance) as the internet entry point for TCP connections. This would load balance connections across instances of linked-tcp (that have been plumbed-into k8s via namerd).
What I don’t see is the full set of k8s resources that are required to get this to work.
Has anyone done this? What is the best way to get this configured?

Hi @hapnermw!
Currently, linkerd-tcp supports SNI insofar as a server may support multiple named certs.  However, currently (or at least the last I looked), rustls does not expose the server name that was negotiated to the application, so linkerd can't yet route on this name dynamically.
I'd really like to support this type of configuration, but we need to get some changes into the libraries we depend on.  The good news is that we're currently sponsoring some work on these projects that should make this a closer reality in the coming weeks.

Oliver, thanks for the explanation.
Assuming that Tokio is updated to expose the TLS SNI value to linked-tcp, I
think you are saying that linkerd-tcp SNI routing would likely be
implemented soon after. Is this correct?
In this thread I had asked a few general linkerd-tcp/namerd k8s config
questions. Can you give me some pointers on how to resolve these?
On Tue, Aug 15, 2017 at 12:56 PM, Oliver Gould<EMAIL_ADDRESS>wrote:

Hi @hapnermw https://github.com/hapnermw!
Currently, linkerd-tcp supports SNI insofar as a server may support
multiple named certs. However, currently (or at least the last I looked),
rustls does not expose the server name that was negotiated to the
application, so linkerd can't yet route on this name dynamically.
I'd really like to support this type of configuration, but we need to get
some changes into the libraries we depend on. The good news is that we're
currently sponsoring some work on these projects that should make this a
closer reality in the coming weeks.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/linkerd/linkerd-tcp/issues/71#issuecomment-322571408,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAySh4Hs2MPVUkbWKXOxkYiBCHWnkGu-ks5sYff0gaJpZM4Ov8_t
.

PR #76 shows that the SNI information is exposed to the application by the underlying library (Rustls).


Update READEME

"Each team will update their Readme.md file (or OPE book) on their github project repo with detailed instructions for installing and deploying their project along with a well documented explanation of their project. We will be reading this before your presentation date, and this is an important part of your project."

"Much of the project final grade will be based on the final project demos and README, so make sure to put good effort into them. Please discuss with your mentors. "

"We will send you the final recording, and expect you to make them available in your README.md file. "

Done


Deck Folders

Hi!
So it would be cool if you could put your decks into folders.
Like current decks and old decks you want to keep and tavern brawl.
Let me know what you think!

I like this idea... I have to check the best way to do that.
I think I have to change a lot of things on deck manager to simplify it, but also add some features like this one (and deck versions, as well as "deck archive")

A tag system could (maybe) be simpler…


Docs consider 1.x stable, 2.x prerelease

What did you do?

Visit https://prometheus.io/docs/prometheus/latest/getting_started/
Look at the version selector on the left nav

What did you expect to see?
(Tweaking the DOM, something like the following)

What did you see instead? Under which circumstances?

And when selecting 2.55:

I read in https://prometheus.io/blog/2024/09/11/prometheus-3-beta/ that 2.0 was released in 2017, so I take it 2.x is latest, 1.x is legacy, 3.x is prerelease.
System information
n/a
Prometheus version
n/a

Prometheus configuration file
n/a

Alertmanager version
n/a

Alertmanager configuration file
n/a

Logs
n/a

Thanks for reporting! This was also reported in https://github.com/prometheus/docs/issues/2514 and I fixed it on the weekend in https://github.com/prometheus/docs/pull/2516. Basically the website build process ran into a weird edge case where there were already both release-3.0 and release-2.55 branches, both without a tagged stable release on them (one is still a beta tag, the other still an RC), and it didn't deal with that correctly.


feat: (3) Yard Docs for models

Describe the changes you have made in this PR -

Added yard docs for all the AcitveModel available in this repository

Note: Please check Allow edits from maintainers. if you would like us to assist in the PR.

If possible, can you review and merge this PR because it will be t easier for  me to verify solargraph setup while working on the docker environment environment and as well as prepairing the documentation.
@tachyons @vedant-jain03 @smritigarg


[bug]: Error while finding module specification for 'invokeai.frontend.install.invokeai_update' (ModuleNotFoundError: No module named 'invokeai')

Is there an existing issue for this?

[X] I have searched the existing issues

OS
Linux
GPU
cuda
VRAM
8Gb
What version did you experience this issue on?
3.0.2post1
What happened?
Just tried to update InvokeAI by invoke.sh script. Choose 9 (Update InvokeAI), and then see next error:
Update InvokeAI
/home/frimn/stable_diffusion/InvokeAI/.venv/bin/python: Error while finding module specification for 'invokeai.frontend.install.invokeai_update' (ModuleNotFoundError: No module named 'invokeai')

Screenshots
No response
Additional context
No response
Contact Details
No response

Looks like it's not finding the previously installed version of InvokeAI. The easiest solve is to reinstall InvokeAI in the same location as the old one. This will retain all old images & models.

I did a reinstall into the same folder, but lost all metadata on the old images in the process (i can't use any of the "use seed", "use prompt", "upscale" options on images generated on the old install). Is there any way to restore those?

Thanks, it seems to be working, I reinstalled the new version. But I also ran 7 (fix installation) after reinstall.

@grunblatt-git what version did you reinstall from?

I installed version 3.1.0 over the existing 3.0.1 install.
By now i "fixed" the issue by doing a clean new install (to a new folder) of version 3.1.1 and copied the database and all output images and latents to the new location. That restored the metadata as well for some reason.

this worked for me
pip install invokeai

be sure you have activated your env through venv or anaconda

FWIW I had this issue by updating to 4.0.0 rc6 or something and just replaced invokeai_update.py by doing this:
cd /invokeai/.venv/lib/python3.10/site-packages/invokeai/frontend/install
Then:
wget https://raw.githubusercontent.com/invoke-ai/InvokeAI/v4.0.0rc5/invokeai/frontend/install/invokeai_update.py
That puts the file back.  No clue why it disappeared to begin with but at that point I was able to do an update to 4.0.3 and it's up and running.


Drag tab out of window to open in new window

It would be nice to be able to drag a tab out of the window and have it open in a new window rather then having to open a new window then drag the tab into the new window.
I'm on Windows 8.1, not sure if this behavior is different on other OS.

Yeah, that would be useful -- thanks for the feedback! I think this is a duplicate of https://github.com/atom/tabs/issues/39, so I'm closing this in favor of that issue.