New agents unable to register with Rancher Server

What kind of request is this (question/bug/enhancement/feature request):
Bug/Question
Steps to reproduce (least amount of steps as possible):
Unknown reproduction.
Result:
Current situation is that existing hosts already registered can reconnect, but new hosts time out during registration.
Other details that may be helpful:
16 days ago is our last successful registration - 8 days ago it no longer was working.
Environment information
Rancher Server 1.6.23
Rancher Agent 1.2.11
Non-HA Server
Cluster information
AWS EC2 instances running in VPC

Docker (use docker info):

 # docker info
Containers: 0
 Running: 0
 Paused: 0
 Stopped: 0
Images: 2
Server Version: 18.06.1-ce
Storage Driver: overlay2
 Backing Filesystem: extfs
 Supports d_type: true
 Native Overlay Diff: true
Logging Driver: json-file
Cgroup Driver: cgroupfs
Plugins:
 Volume: local
 Network: bridge host macvlan null overlay
 Log: awslogs fluentd gcplogs gelf journald json-file logentries splunk syslog
Swarm: inactive
Runtimes: runc
Default Runtime: runc
Init Binary: docker-init
containerd version: 468a545b9edcd5932818eb9de8e72413e616e86e
runc version: 69663f0bd4b60df09991c08812a60108003fa340
init version: v0.13.2 (expected: fec3683b971d9c3ef73f284f176672c44b448662)
Security Options:
 seccomp
  Profile: default
 selinux
Kernel Version: 4.14.67-coreos
Operating System: Container Linux by CoreOS 1855.4.0 (Rhyolite)
OSType: linux
Architecture: x86_64
CPUs: 2
Total Memory: 14.93GiB
Name: ip-172-22-222-118
ID: FJC3:IJ6R:QCM3:YNLJ:ZYOC:X7AI:2VDY:YREO:A26N:RP4G:3TPM:2X35
Docker Root Dir: /var/lib/docker
Debug Mode (client): false
Debug Mode (server): false
Registry: https://index.docker.io/v1/
Labels:
Experimental: false
Insecure Registries:
 <IP_ADDRESS>/8
Live Restore Enabled: false

We are seeing the following in the Rancher Agent startup:
sudo docker run -e CATTLE_AGENT_IP="<IP_ADDRESS>"  --rm --privileged -v /var/run/docker.sock:/var/run/docker.sock -v /var/lib/rancher:/var/lib/rancher rancher/agent:v1.2.11 https://rancher_server/v1/scripts/6ED9DB0F2FA4D07DDCAF:1514678400000:UzvsHFAk3SN7w29awlPZU29Ioig

INFO: Running Agent Registration Process, CATTLE_URL=https://rancher_server/v1
INFO: Attempting to connect to: https://rancher_server/v1
INFO: https://rancher_server/v1 is accessible
INFO: Configured Host Registration URL info: CATTLE_URL=https://rancher_server/v1 ENV_URL=https://rancher_server/v1
INFO: Inspecting host capabilities
INFO: Boot2Docker: false
INFO: Host writable: true
INFO: Token: xxxxxxxx
INFO: Running registration
Traceback (most recent call last):
  File "./register.py", line 28, in <module>
    r = client.list_register(key=key)[0]
IndexError: list index out of range

And also:
# sudo docker run -e "LOGLEVEL=DEBUG" -e CATTLE_AGENT_IP="<IP_ADDRESS>"  --rm --privileged -v /var/run/docker.sock:/var/run/docker.sock -v /var/lib/rancher:/var/lib/rancher rancher/agent:v1.2.11 https://rancher_server/v1/scripts/<SNIP>

INFO: Running Agent Registration Process, CATTLE_URL=https://rancher_server/v1
INFO: Attempting to connect to: https://rancher_server/v1
INFO: https://rancher_server/v1 is accessible
INFO: Configured Host Registration URL info: CATTLE_URL=https://rancher_server/v1 ENV_URL=https://rancher_server/v1
INFO: Inspecting host capabilities
INFO: Boot2Docker: false
INFO: Host writable: true
INFO: Token: xxxxxxxx
INFO: Running registration
Traceback (most recent call last):
  File "./register.py", line 31, in <module>
    r = client.wait_success(r, timeout=300)
  File "/usr/local/lib/python2.7/dist-packages/cattle.py", line 15, in wait_success
    obj = self.wait_transitioning(obj, timeout)
  File "/usr/local/lib/python2.7/dist-packages/cattle.py", line 33, in wait_transitioning
    raise Exception(msg)
Exception: Timeout waiting for [register:1r105] to be done after<PHONE_NUMBER>59 seconds

Rancher Server shows the api.register.create event in the audit logs, with the following API entries:
{
"id": "1go106",
"type": "register",
"links": {
"self": "…/v2-beta/register/1go106",
"account": "…/v2-beta/register/1go106/account"
},
"actions": {
"stop": "…/v2-beta/register/1go106/?action=stop"
},
"baseType": "genericObject",
"name": null,
"state": "removed",
"accountId": "1a92",
"created": "2018-10-24T21:17:57Z",
"createdTS":<PHONE_NUMBER>000,
"data": {
"agentId": 135367
},
"description": null,
"kind": "register",
"removeTime": "2018-10-24T21:29:50Z",
"removeTimeTS":<PHONE_NUMBER>000,
"removed": "2018-10-24T21:23:49Z",
"removedTS":<PHONE_NUMBER>000,
"resourceData": null,
"transitioning": "no",
"transitioningMessage": null,
"transitioningProgress": null,
"uuid": "c8d8d43f-6717-43e6-84c7-708a3d9355cd"
}

The entry never goes "active" and stays in "transitioning" until it is "removed".
On the Rancher Server in the cattle-debug.log the only relevant line I can find is:
2018-10-24 21:30:03,657 INFO  [:] [] [] [] [ecutorService-3] [.e.s.i.ProcessInstanceDispatcherImpl] Timeout on process [genericobject.create:14445292] on [107] : Waiting: credentials assigned [registeredAgent:1ra135381]

But I can provide full logs if needed.

We're also seeing a ton of services stuck in the "Waiting: Allocated container" state.
I've confirmed the Rancher Server can reach the internal IPs set by the CATTLE_AGENT_IP env var:
root@556c897bb7f7:/var/lib/cattle/logs# ping <IP_ADDRESS>
PING <IP_ADDRESS> (<IP_ADDRESS>) 56(84) bytes of data.
64 bytes from <IP_ADDRESS>: icmp_seq=1 ttl=63 time=0.619 ms
64 bytes from <IP_ADDRESS>: icmp_seq=2 ttl=63 time=0.587 ms
^C
--- <IP_ADDRESS> ping statistics ---
2 packets transmitted, 2 received, 0% packet loss, time 1024ms
rtt min/avg/max/mdev = 0.587/0.603/0.619/0.016 ms
root@556c897bb7f7:/var/lib/cattle/logs#

We're also seeing "Timeout getting IP Address" for a lot of containers on a single host in our cluster. It seems the DB for Rancher Server may be deadlocked?

Also seeing new container instances unable to start, and errors in the Rancher Server logs:
2018-10-24 21:47:48,850 ERROR [0efc5ca6-f095-4cff-bdea-d97e49ac9696:14446090] [instance:156555] [instance.start->(InstanceStart)] [] [cutorService-10] [i.c.p.process.instance.InstanceStart] Failed [Dependencies readiness error instance is not running] for instance [156555]
2018-10-24 21:47:48,868 INFO  [:] [] [] [] [cutorService-15] [.e.s.i.ProcessInstanceDispatcherImpl] Timeout on process [instance.create:14446152] on [156557] : Waiting: active credentials [agent:1a135383]
2018-10-24 21:47:48,881 ERROR [0efc5ca6-f095-4cff-bdea-d97e49ac9696:14446090] [instance:156555] [instance.start] [] [cutorService-10] [c.p.e.p.i.DefaultProcessInstanceImpl] Unknown exception io.cattle.platform.util.exception.ExecutionException: Dependencies readiness error
	at io.cattle.platform.process.instance.InstanceStart.waitForDependenciesStart(InstanceStart.java:294)
	at io.cattle.platform.process.instance.InstanceStart.handle(InstanceStart.java:118)
	at io.cattle.platform.engine.process.impl.DefaultProcessInstanceImpl.runHandler(DefaultProcessInstanceImpl.java:470)
	at io.cattle.platform.engine.process.impl.DefaultProcessInstanceImpl$4.execute(DefaultProcessInstanceImpl.java:421)
	at io.cattle.platform.engine.process.impl.DefaultProcessInstanceImpl$4.execute(DefaultProcessInstanceImpl.java:415)
	at io.cattle.platform.engine.idempotent.Idempotent.execute(Idempotent.java:42)
	at io.cattle.platform.engine.process.impl.DefaultProcessInstanceImpl.runHandlers(DefaultProcessInstanceImpl.java:415)
	at io.cattle.platform.engine.process.impl.DefaultProcessInstanceImpl.runLogic(DefaultProcessInstanceImpl.java:517)
	at io.cattle.platform.engine.process.impl.DefaultProcessInstanceImpl.runWithProcessLock(DefaultProcessInstanceImpl.java:345)
	at io.cattle.platform.engine.process.impl.DefaultProcessInstanceImpl$2.doWithLockNoResult(DefaultProcessInstanceImpl.java:245)
	at io.cattle.platform.lock.LockCallbackNoReturn.doWithLock(LockCallbackNoReturn.java:7)
	at io.cattle.platform.lock.LockCallbackNoReturn.doWithLock(LockCallbackNoReturn.java:3)
	at io.cattle.platform.lock.impl.AbstractLockManagerImpl$3.doWithLock(AbstractLockManagerImpl.java:40)
	at io.cattle.platform.lock.impl.LockManagerImpl.doLock(LockManagerImpl.java:33)
	at io.cattle.platform.lock.impl.AbstractLockManagerImpl.lock(AbstractLockManagerImpl.java:13)
	at io.cattle.platform.lock.impl.AbstractLockManagerImpl.lock(AbstractLockManagerImpl.java:37)
	at io.cattle.platform.engine.process.impl.DefaultProcessInstanceImpl.acquireLockAndRun(DefaultProcessInstanceImpl.java:242)
	at io.cattle.platform.engine.process.impl.DefaultProcessInstanceImpl.runDelegateLoop(DefaultProcessInstanceImpl.java:184)
	at io.cattle.platform.engine.process.impl.DefaultProcessInstanceImpl.executeWithProcessInstanceLock(DefaultProcessInstanceImpl.java:157)
	at io.cattle.platform.engine.process.impl.DefaultProcessInstanceImpl$1.doWithLock(DefaultProcessInstanceImpl.java:116)
	at io.cattle.platform.engine.process.impl.DefaultProcessInstanceImpl$1.doWithLock(DefaultProcessInstanceImpl.java:113)
	at io.cattle.platform.lock.impl.AbstractLockManagerImpl$3.doWithLock(AbstractLockManagerImpl.java:40)
	at io.cattle.platform.lock.impl.LockManagerImpl.doLock(LockManagerImpl.java:33)
	at io.cattle.platform.lock.impl.AbstractLockManagerImpl.lock(AbstractLockManagerImpl.java:13)
	at io.cattle.platform.lock.impl.AbstractLockManagerImpl.lock(AbstractLockManagerImpl.java:37)
	at io.cattle.platform.engine.process.impl.DefaultProcessInstanceImpl.execute(DefaultProcessInstanceImpl.java:113)
	at io.cattle.platform.engine.server.impl.ProcessInstanceDispatcherImpl.processExecuteWithLock(ProcessInstanceDispatcherImpl.java:136)
	at io.cattle.platform.engine.server.impl.ProcessInstanceDispatcherImpl$1.doWithLock(ProcessInstanceDispatcherImpl.java:123)
	at io.cattle.platform.engine.server.impl.ProcessInstanceDispatcherImpl$1.doWithLock(ProcessInstanceDispatcherImpl.java:120)
	at io.cattle.platform.lock.impl.AbstractLockManagerImpl$4.doWithLock(AbstractLockManagerImpl.java:50)
	at io.cattle.platform.lock.impl.LockManagerImpl.doLock(LockManagerImpl.java:33)
	at io.cattle.platform.lock.impl.AbstractLockManagerImpl.tryLock(AbstractLockManagerImpl.java:25)
	at io.cattle.platform.lock.impl.AbstractLockManagerImpl.tryLock(AbstractLockManagerImpl.java:47)
	at io.cattle.platform.engine.server.impl.ProcessInstanceDispatcherImpl.execute(ProcessInstanceDispatcherImpl.java:120)
	at io.cattle.platform.engine.server.ProcessInstanceReference.doRun(ProcessInstanceReference.java:59)
	at org.apache.cloudstack.managed.context.NoExceptionRunnable.runInContext(NoExceptionRunnable.java:15)
	at org.apache.cloudstack.managed.context.ManagedContextRunnable$1.run(ManagedContextRunnable.java:49)
	at org.apache.cloudstack.managed.context.impl.DefaultManagedContext$1.call(DefaultManagedContext.java:55)
	at org.apache.cloudstack.managed.context.impl.DefaultManagedContext.callWithContext(DefaultManagedContext.java:108)
	at org.apache.cloudstack.managed.context.impl.DefaultManagedContext.runWithContext(DefaultManagedContext.java:52)
	at org.apache.cloudstack.managed.context.ManagedContextRunnable.run(ManagedContextRunnable.java:46)
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
	at java.lang.Thread.run(Thread.java:745)

Possibly related, the rancher/scheduler server had crashed completely and now refuses to start. I'm assuming that means any containers with scheduling rules won't start either.
It is showing the "Waiting: allocated container" message in the UI, and I'm seeing the same logs:
2018-10-24 22:10:14,127 INFO  [:] [] [] [] [cutorService-16] [.e.s.i.ProcessInstanceDispatcherImpl] Timeout on process [instance.create:14447755] on [156580] : Waiting: active credentials [agent:1a135389]
2018-10-24 22:10:14,172 INFO  [:] [] [] [] [cutorService-14] [.e.s.i.ProcessInstanceDispatcherImpl] Timeout on process [service.upgrade:14447754] on [140] : Waiting: allocated [container:1i156580]
2018-10-24 22:10:44,132 INFO  [:] [] [] [] [ecutorService-3] [.e.s.i.ProcessInstanceDispatcherImpl] Timeout on process [instance.create:13363144] on [155503] : Waiting: active credentials [agent:1a135334]
2018-10-24 22:11:14,139 INFO  [:] [] [] [] [ecutorService-4] [.e.s.i.ProcessInstanceDispatcherImpl] Timeout on process [instance.create:14447755] on [156580] : Waiting: active credentials [agent:1a135389]
2018-10-24 22:11:14,232 INFO  [:] [] [] [] [ecutorService-2] [.e.s.i.ProcessInstanceDispatcherImpl] Timeout on process [service.upgrade:14447754] on [140] : Waiting: allocated [container:1i156580]

Also saw similar error on rancher/external-dns:
10/24/2018 4:03:10 PMtime="2018-10-24T23:03:10Z" level=info msg="Starting Rancher External DNS service v0.7.9"
10/24/2018 4:03:10 PMtime="2018-10-24T23:03:10Z" level=fatal msg="Environment variable 'CATTLE_URL' is not set"

I've confirmed that all the services which are failing with the missing environment variables do have io.rancher.container.create_agent set to 'true' in their configurations.

Also seeing the same in our Healthcheck container:

10/24/2018 5:32:18 PMtime="2018-10-25T00:32:18Z" level=info msg="CATTLE_URL is not set"
10/24/2018 5:32:18 PMtime="2018-10-25T00:32:18Z" level=fatal msg="Can not create RancherClient, No credentials found"
10/24/2018 5:32:25 PMtime="2018-10-25T00:32:25Z" level=info msg="CATTLE_URL is not set"
10/24/2018 5:32:25 PMtime="2018-10-25T00:32:25Z" level=fatal msg="Can not create RancherClient, No credentials found"
10/24/2018 5:32:27 PMtime="2018-10-25T00:32:27Z" level=info msg="CATTLE_URL is not set"
10/24/2018 5:32:27 PMtime="2018-10-25T00:32:27Z" level=fatal msg="Can not create RancherClient, No credentials found"

Pinging @deniseschannon in case someone is willing to help out. Our infrastructure is gently crumbling since no system services can start.

I am having a similar issue.  New hosts are not registering with the server.  v1.6.16/agent 1.2.10

For those who find this - we were unable to find a solution to the issue - something in the database had broken irreparably. We ended up doing a rebuild from scratch after removing our cattle database from RDS and using Terraform to recreate our service instances.
We used the rancher CLI to export all our service stacks before doing the rebuild, so the whole process only took a couple hour maintenance window to complete.

Hi,
I know this issue is closed but I just want to inform that we had the same issue. Loadbalancer did'nt work and no new agents could register.
We had to restart metaservices, clone scheduler (and delete the old one) and then reinstall our load balancers. Then our clusters were alright again. (phew...)


docs(README): add a link and description of wink-nlp

What do you think about the language and look? Should we make it subtle, or even bolder?

Coverage remained the same at 100.0% when pulling aef347c929c05b75c06e6cddb49af102dd86afe4 on prtksxna:patch-3 into 8d41973b66d6162a70fdf634fe80ffe0cebe2005 on winkjs:master.


fix nil pointer parameter

Issues associated with this PR
Your PR should present related issues you want to solve.
Solutions
You should show your solutions about the issues in your PR, including the overall solutions, details and the changes. At this time, Chinese is allowed to describe these.
UT result
Unit Test is needed if the code is changed, your unit test should cover boundary cases, corner cases, and some exceptional cases. And you need to show the UT result.
Benchmark
If your code involves the processing of every request, you should give the Benchmark Result.
Code Style

Make sure Goimports has run
Show Golint result

Codecov Report

Merging #1160 into master will increase coverage by 0.00%.
The diff coverage is 54.54%.

@@           Coverage Diff           @@
##           master    #1160   +/-   ##
=======================================
  Coverage   56.15%   56.15%
=======================================
  Files         268      268
  Lines       25415    25420    +5
=======================================
+ Hits        14271    14274    +3
  Misses       9780     9780
- Partials     1364     1366    +2

Impacted Files
Coverage Δ

pkg/configmanager/configmanager.go
95.92% <0.00%> (-1.77%)
:arrow_down:

pkg/upstream/healthcheck/factory.go
71.42% <66.66%> (-1.91%)
:arrow_down:

pkg/upstream/healthcheck/healthchecker.go
87.00% <100.00%> (+0.26%)
:arrow_up:

pkg/upstream/cluster/loadbalancer.go
71.95% <0.00%> (-1.22%)
:arrow_down:

pkg/module/http2/transport.go
78.62% <0.00%> (+0.14%)
:arrow_up:

pkg/module/http2/frame.go
84.47% <0.00%> (+0.30%)
:arrow_up:

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update b4c61ca...944b21e. Read the comment docs.


no upload on the NAS

Hi,
I've used the simple configuration, all is fine. Music is Sync from the NAS to the PI Music folder, I can see the Dashcam icon running on the screen. I can save clips (which are present on the USB CAM drive when mounted on a PC)...
BUT...
when I park the car, the PI comes on the Wifi, but do not sync the files on the NAS.
I've checked mounting is possible with my config - ok
I can ssh - ok
here is my  /boot/teslausb-headless-setup.log
I've launched a setup since, it installed some more files, checked the system but still I have this issue...This is why the following file is long...

pi@teslausb:~ $ cat /boot/teslausb-headless-setup.log
Sat 15 Jun 22:27:12 BST 2019 : Detecting whether to update wpa_supplicant.conf
Sat 15 Jun 22:27:12 BST 2019 : Wifi variables specified, and no /boot/WIFI_ENABLED. Building wpa_supplicant.conf.
Sat 15 Jun 22:27:12 BST 2019 : Rebooting...
Sat 15 Jun 22:27:40 BST 2019 : Detecting whether to update wpa_supplicant.conf
Sat 15 Jun 22:27:40 BST 2019 : Grabbing main setup file.
Sat 15 Jun 22:27:42 BST 2019 : Starting setup.
Sat 15 Jun 22:27:42 BST 2019 : reading config from /root/teslausb_setup_variables.conf
Sat 15 Jun 22:27:42 BST 2019 : curl -s https://api.github.com/repos/marcone/teslausb/git/refs/heads/main-dev
Sat 15 Jun 22:27:43 BST 2019 : 'curl -s https://api.github.com/repos/marcone/teslausb/git/refs/heads/main-dev' failed, retrying
Sat 15 Jun 22:27:47 BST 2019 : 'curl -s https://api.github.com/repos/marcone/teslausb/git/refs/heads/main-dev' failed, retrying
Sat 15 Jun 22:27:51 BST 2019 : 'curl -s https://api.github.com/repos/marcone/teslausb/git/refs/heads/main-dev' failed, retrying
Sat 15 Jun 22:27:55 BST 2019 : 'curl -s https://api.github.com/repos/marcone/teslausb/git/refs/heads/main-dev' failed, retrying
Thu 22 Aug 13:04:39 BST 2019 : curl -o /tmp/setup-teslausb https://raw.githubusercontent.com/marcone/teslausb/996e4bba750d3dbf2598c1c1bad93349fe0089a7/setup/pi/setup-teslausb
Thu 22 Aug 13:04:40 BST 2019 : Downloaded /tmp/setup-teslausb ...
Thu 22 Aug 13:04:41 BST 2019 : /root/bin/setup-teslausb is up to date
Thu 22 Aug 13:04:41 BST 2019 : Updating package index files...
Thu 22 Aug 13:05:20 BST 2019 : Detecting whether to update wpa_supplicant.conf
Thu 22 Aug 13:05:20 BST 2019 : Starting setup.
Thu 22 Aug 13:05:21 BST 2019 : reading config from /root/teslausb_setup_variables.conf
Thu 22 Aug 13:05:21 BST 2019 : curl -s https://api.github.com/repos/marcone/teslausb/git/refs/heads/main-dev
Thu 22 Aug 13:05:29 BST 2019 : curl -o /tmp/setup-teslausb https://raw.githubusercontent.com/marcone/teslausb/996e4bba750d3dbf2598c1c1bad93349fe0089a7/setup/pi/setup-teslausb
Thu 22 Aug 13:05:37 BST 2019 : Downloaded /tmp/setup-teslausb ...
Thu 22 Aug 13:05:37 BST 2019 : /root/bin/setup-teslausb is up to date
Thu 22 Aug 13:05:37 BST 2019 : Updating package index files...
Thu 22 Aug 13:09:13 BST 2019 : Verifying that the requested configuration is valid...
Thu 22 Aug 13:09:13 BST 2019 : curl -o /tmp/verify-configuration.sh https://raw.githubusercontent.com/marcone/teslausb/996e4bba750d3dbf2598c1c1bad93349fe0089a7/setup/pi/verify-configuration.sh
Thu 22 Aug 13:09:14 BST 2019 : Downloaded /tmp/verify-configuration.sh ...
Thu 22 Aug 13:09:14 BST 2019 : Verifying that there is sufficient space available on the MicroSD card...
Thu 22 Aug 13:09:14 BST 2019 : There is sufficient space available.
Thu 22 Aug 13:09:23 BST 2019 : Downloading additional setup scripts.
Thu 22 Aug 13:09:23 BST 2019 : curl -o /root/bin/remountfs_rw https://raw.githubusercontent.com/marcone/teslausb/996e4bba750d3dbf2598c1c1bad93349fe0089a7/run/remountfs_rw
Thu 22 Aug 13:09:23 BST 2019 : Downloaded /root/bin/remountfs_rw ...
Thu 22 Aug 13:09:23 BST 2019 : curl -o /root/bin/mount_snapshot.sh https://raw.githubusercontent.com/marcone/teslausb/996e4bba750d3dbf2598c1c1bad93349fe0089a7/run/mount_snapshot.sh
Thu 22 Aug 13:09:24 BST 2019 : Downloaded /root/bin/mount_snapshot.sh ...
Thu 22 Aug 13:09:24 BST 2019 : curl -o /root/bin/release_snapshot.sh https://raw.githubusercontent.com/marcone/teslausb/996e4bba750d3dbf2598c1c1bad93349fe0089a7/run/release_snapshot.sh
Thu 22 Aug 13:09:25 BST 2019 : Downloaded /root/bin/release_snapshot.sh ...
Thu 22 Aug 13:09:25 BST 2019 : curl -o /tmp/create-backingfiles-partition.sh https://raw.githubusercontent.com/marcone/teslausb/996e4bba750d3dbf2598c1c1bad93349fe0089a7/setup/pi/create-backingfiles-partition.sh
Thu 22 Aug 13:09:26 BST 2019 : Downloaded /tmp/create-backingfiles-partition.sh ...
Thu 22 Aug 13:09:26 BST 2019 : curl -o /tmp/create-backingfiles.sh https://raw.githubusercontent.com/marcone/teslausb/996e4bba750d3dbf2598c1c1bad93349fe0089a7/setup/pi/create-backingfiles.sh
Thu 22 Aug 13:09:27 BST 2019 : Downloaded /tmp/create-backingfiles.sh ...
Thu 22 Aug 13:09:27 BST 2019 : curl -o /tmp/make-root-fs-readonly.sh https://raw.githubusercontent.com/marcone/teslausb/996e4bba750d3dbf2598c1c1bad93349fe0089a7/setup/pi/make-root-fs-readonly.sh
Thu 22 Aug 13:09:28 BST 2019 : Downloaded /tmp/make-root-fs-readonly.sh ...
Thu 22 Aug 13:09:28 BST 2019 : curl -o /tmp/configure.sh https://raw.githubusercontent.com/marcone/teslausb/996e4bba750d3dbf2598c1c1bad93349fe0089a7/setup/pi/configure.sh
Thu 22 Aug 13:09:29 BST 2019 : Downloaded /tmp/configure.sh ...
Thu 22 Aug 13:09:29 BST 2019 : Fixing the modules-load parameter in /boot/cmdline.txt...
Thu 22 Aug 13:09:29 BST 2019 : Fixed cmdline.txt.
Thu 22 Aug 13:09:38 BST 2019 : Checking existing partitions...
Thu 22 Aug 13:09:39 BST 2019 : Modifying partition table for backing files partition...
Thu 22 Aug 13:09:39 BST 2019 : Modifying partition table for mutable (writable) partition for script usage...
Thu 22 Aug 13:09:40 BST 2019 : Writing updated partitions to fstab and /boot/cmdline.txt
Thu 22 Aug 13:09:40 BST 2019 : Formatting new partitions...
Thu 22 Aug 13:10:33 BST 2019 : Mounting the partition for the backing files...
Thu 22 Aug 13:10:33 BST 2019 : Mounted the partition for the backing files.
Thu 22 Aug 13:10:33 BST 2019 : Creating backing disk files.
Thu 22 Aug 13:10:33 BST 2019 : create-backingfiles: starting
Thu 22 Aug 13:10:33 BST 2019 : create-backingfiles: cam: 90%, music: 100%, mountpoint: /backingfiles
Thu 22 Aug 13:10:34 BST 2019 : create-backingfiles: Allocating 53009020K for /backingfiles/cam_disk.bin...
Thu 22 Aug 13:10:34 BST 2019 : create-backingfiles: Creating filesystem with label 'CAM'
Thu 22 Aug 13:10:35 BST 2019 : create-backingfiles: updated /etc/fstab for /mnt/cam
Thu 22 Aug 13:10:35 BST 2019 : create-backingfiles: created camera backing file
Thu 22 Aug 13:10:35 BST 2019 : create-backingfiles: Allocating 5889892K for /backingfiles/music_disk.bin...
Thu 22 Aug 13:10:37 BST 2019 : create-backingfiles: Creating filesystem with label 'MUSIC'
Thu 22 Aug 13:10:38 BST 2019 : create-backingfiles: updated /etc/fstab for /mnt/music
Thu 22 Aug 13:10:38 BST 2019 : create-backingfiles: created music backing file
Thu 22 Aug 13:10:40 BST 2019 : create-backingfiles: done
Thu 22 Aug 13:10:49 BST 2019 : Main setup completed.
Thu 22 Aug 13:10:49 BST 2019 : calling configure.sh
Thu 22 Aug 13:10:50 BST 2019 : configure: /tmp/configure.sh starting with REPO=marcone, BRANCH=main-dev, ARCHIVE_SYSTEM=cifs
Thu 22 Aug 13:10:50 BST 2019 : configure: Getting files from marcone:main-dev
Thu 22 Aug 13:10:50 BST 2019 : configure: Pushover not configured.
Thu 22 Aug 13:10:50 BST 2019 : configure: Gotify not configured.
Thu 22 Aug 13:10:50 BST 2019 : configure: Gotify not configured.
Thu 22 Aug 13:10:50 BST 2019 : configure: Starting download for /root/bin/send-push-message
Thu 22 Aug 13:10:51 BST 2019 : configure: Done
Thu 22 Aug 13:10:51 BST 2019 : configure: Starting download for /root/bin/send_sns.py
Thu 22 Aug 13:10:52 BST 2019 : configure: Done
Thu 22 Aug 13:10:52 BST 2019 : configure: Checking archive configs:
Thu 22 Aug 13:10:52 BST 2019 : configure: done
Thu 22 Aug 13:10:52 BST 2019 : configure: Using archive module: run/cifs_archive
Thu 22 Aug 13:10:52 BST 2019 : configure: Installing base archive scripts into /root/bin
Thu 22 Aug 13:10:52 BST 2019 : configure: Starting download for /root/bin/archiveloop
Thu 22 Aug 13:10:53 BST 2019 : configure: Done
Thu 22 Aug 13:10:53 BST 2019 : configure: Starting download for /root/bin/remountfs_rw
Thu 22 Aug 13:10:54 BST 2019 : configure: Done
Thu 22 Aug 13:10:54 BST 2019 : configure: Starting download for /root/bin/tesla_api.py
Thu 22 Aug 13:10:55 BST 2019 : configure: Done
Thu 22 Aug 13:10:55 BST 2019 : configure: Installing archive module scripts
Thu 22 Aug 13:10:55 BST 2019 : configure: Starting download for /tmp/verify-and-configure-archive.sh
Thu 22 Aug 13:10:56 BST 2019 : configure: Done
Thu 22 Aug 13:10:56 BST 2019 : configure: Starting download for /root/bin/archive-clips.sh
Thu 22 Aug 13:10:57 BST 2019 : configure: Done
Thu 22 Aug 13:10:57 BST 2019 : configure: Starting download for /root/bin/connect-archive.sh
Thu 22 Aug 13:10:58 BST 2019 : configure: Done
Thu 22 Aug 13:10:58 BST 2019 : configure: Starting download for /root/bin/disconnect-archive.sh
Thu 22 Aug 13:10:59 BST 2019 : configure: Done
Thu 22 Aug 13:10:59 BST 2019 : configure: Starting download for /root/bin/write-archive-configs-to.sh
Thu 22 Aug 13:11:00 BST 2019 : configure: Done
Thu 22 Aug 13:11:00 BST 2019 : configure: Starting download for /root/bin/archive-is-reachable.sh
Thu 22 Aug 13:11:01 BST 2019 : configure: Done
Thu 22 Aug 13:11:01 BST 2019 : configure: Starting download for /root/bin/copy-music.sh
Thu 22 Aug 13:11:02 BST 2019 : configure: Done
Thu 22 Aug 13:11:02 BST 2019 : verify-and-configure-archive: Installing/updating required packages if needed
Thu 22 Aug 13:11:07 BST 2019 : verify-and-configure-archive: Done
Thu 22 Aug 13:11:07 BST 2019 : verify-and-configure-archive: Verifying that the archive server <IP_ADDRESS> is reachable...
Thu 22 Aug 13:11:07 BST 2019 : verify-and-configure-archive: The archive server is reachable.
Thu 22 Aug 13:11:07 BST 2019 : verify-and-configure-archive: Verifying that the archive share is mountable...
Thu 22 Aug 13:11:07 BST 2019 : verify-and-configure-archive: Trying mount command-line:
Thu 22 Aug 13:11:07 BST 2019 : verify-and-configure-archive: mount -t cifs '//<IP_ADDRESS>/Public/TESLA/TeslaCam' '/tmp/archivetestmount' -o 'credentials=/tmp/teslaCamArchiveCredentials,iocharset=utf8,file_mode=0777,dir_mode=0777,,'
Thu 22 Aug 13:11:08 BST 2019 : verify-and-configure-archive: The archive share is mountable using: mount -t cifs '//<IP_ADDRESS>/Public/TESLA/TeslaCam' '/tmp/archivetestmount' -o 'credentials=/tmp/teslaCamArchiveCredentials,iocharset=utf8,file_mode=0777,dir_mode=0777,,'
Thu 22 Aug 13:11:08 BST 2019 : verify-and-configure-archive: Verifying that the archive share is mountable...
Thu 22 Aug 13:11:08 BST 2019 : verify-and-configure-archive: Trying mount command-line:
Thu 22 Aug 13:11:08 BST 2019 : verify-and-configure-archive: mount -t cifs '//<IP_ADDRESS>/Public/TESLA/TeslaMusic' '/tmp/archivetestmount' -o 'credentials=/tmp/teslaCamArchiveCredentials,iocharset=utf8,file_mode=0777,dir_mode=0777,,'
Thu 22 Aug 13:11:08 BST 2019 : verify-and-configure-archive: The archive share is mountable using: mount -t cifs '//<IP_ADDRESS>/Public/TESLA/TeslaMusic' '/tmp/archivetestmount' -o 'credentials=/tmp/teslaCamArchiveCredentials,iocharset=utf8,file_mode=0777,dir_mode=0777,,'
Thu 22 Aug 13:11:08 BST 2019 : verify-and-configure-archive: Configuring the archive...
Thu 22 Aug 13:11:09 BST 2019 : verify-and-configure-archive: Configured the archive.
Thu 22 Aug 13:11:09 BST 2019 : configure: Skipping rc.local installation
Thu 22 Aug 13:11:09 BST 2019 : make-root-fs-readonly: start
Thu 22 Aug 13:11:09 BST 2019 : make-root-fs-readonly: Removing unwanted packages...
Thu 22 Aug 13:12:08 BST 2019 : make-root-fs-readonly: Installing ntp and busybox-syslogd...
Thu 22 Aug 13:13:10 BST 2019 : make-root-fs-readonly: Configuring system...
Thu 22 Aug 13:13:10 BST 2019 : make-root-fs-readonly: Mounting the mutable partition...
Thu 22 Aug 13:13:10 BST 2019 : make-root-fs-readonly: Mounted.
Thu 22 Aug 13:13:11 BST 2019 : make-root-fs-readonly: Moving fake-hwclock data
Thu 22 Aug 13:13:11 BST 2019 : make-root-fs-readonly: done
Thu 22 Aug 13:13:11 BST 2019 : Upgrading installed packages...
Thu 22 Aug 13:20:19 BST 2019 : All done.
Fri 23 Aug 17:27:15 BST 2019 : Detecting whether to update wpa_supplicant.conf
Fri 23 Aug 17:27:55 BST 2019 : reading config from /root/teslausb_setup_variables.conf
Fri 23 Aug 17:27:55 BST 2019 : curl -s https://api.github.com/repos/marcone/teslausb/git/refs/heads/main-dev
Fri 23 Aug 17:27:56 BST 2019 : curl -o /tmp/setup-teslausb https://raw.githubusercontent.com/marcone/teslausb/996e4bba750d3dbf2598c1c1bad93349fe0089a7/setup/pi/setup-teslausb
Fri 23 Aug 17:27:57 BST 2019 : Downloaded /tmp/setup-teslausb ...
Fri 23 Aug 17:27:57 BST 2019 : /root/bin/setup-teslausb is up to date
Fri 23 Aug 17:27:57 BST 2019 : Updating package index files...
Fri 23 Aug 17:29:09 BST 2019 : Verifying that the requested configuration is valid...
Fri 23 Aug 17:29:09 BST 2019 : curl -o /tmp/verify-configuration.sh https://raw.githubusercontent.com/marcone/teslausb/996e4bba750d3dbf2598c1c1bad93349fe0089a7/setup/pi/verify-configuration.sh
Fri 23 Aug 17:29:10 BST 2019 : Downloaded /tmp/verify-configuration.sh ...
Fri 23 Aug 17:29:10 BST 2019 : Verifying that there is sufficient space available on the MicroSD card...
Fri 23 Aug 17:29:10 BST 2019 : There is sufficient space available.
Fri 23 Aug 17:29:18 BST 2019 : Downloading additional setup scripts.
Fri 23 Aug 17:29:18 BST 2019 : curl -o /root/bin/remountfs_rw https://raw.githubusercontent.com/marcone/teslausb/996e4bba750d3dbf2598c1c1bad93349fe0089a7/run/remountfs_rw
Fri 23 Aug 17:29:19 BST 2019 : Downloaded /root/bin/remountfs_rw ...
Fri 23 Aug 17:29:19 BST 2019 : curl -o /root/bin/mount_snapshot.sh https://raw.githubusercontent.com/marcone/teslausb/996e4bba750d3dbf2598c1c1bad93349fe0089a7/run/mount_snapshot.sh
Fri 23 Aug 17:29:20 BST 2019 : Downloaded /root/bin/mount_snapshot.sh ...
Fri 23 Aug 17:29:20 BST 2019 : curl -o /root/bin/release_snapshot.sh https://raw.githubusercontent.com/marcone/teslausb/996e4bba750d3dbf2598c1c1bad93349fe0089a7/run/release_snapshot.sh
Fri 23 Aug 17:29:21 BST 2019 : Downloaded /root/bin/release_snapshot.sh ...
Fri 23 Aug 17:29:21 BST 2019 : curl -o /tmp/create-backingfiles-partition.sh https://raw.githubusercontent.com/marcone/teslausb/996e4bba750d3dbf2598c1c1bad93349fe0089a7/setup/pi/create-backingfiles-partition.sh
Fri 23 Aug 17:29:22 BST 2019 : Downloaded /tmp/create-backingfiles-partition.sh ...
Fri 23 Aug 17:29:22 BST 2019 : curl -o /tmp/create-backingfiles.sh https://raw.githubusercontent.com/marcone/teslausb/996e4bba750d3dbf2598c1c1bad93349fe0089a7/setup/pi/create-backingfiles.sh
Fri 23 Aug 17:29:23 BST 2019 : Downloaded /tmp/create-backingfiles.sh ...
Fri 23 Aug 17:29:23 BST 2019 : curl -o /tmp/make-root-fs-readonly.sh https://raw.githubusercontent.com/marcone/teslausb/996e4bba750d3dbf2598c1c1bad93349fe0089a7/setup/pi/make-root-fs-readonly.sh
Fri 23 Aug 17:29:24 BST 2019 : Downloaded /tmp/make-root-fs-readonly.sh ...
Fri 23 Aug 17:29:24 BST 2019 : curl -o /tmp/configure.sh https://raw.githubusercontent.com/marcone/teslausb/996e4bba750d3dbf2598c1c1bad93349fe0089a7/setup/pi/configure.sh
Fri 23 Aug 17:29:25 BST 2019 : Downloaded /tmp/configure.sh ...
Fri 23 Aug 17:29:25 BST 2019 : Fixing the modules-load parameter in /boot/cmdline.txt...
Fri 23 Aug 17:29:25 BST 2019 : Fixed cmdline.txt.
Fri 23 Aug 17:29:34 BST 2019 : using existing backingfiles and mutable partitions
Fri 23 Aug 17:29:43 BST 2019 : Main setup completed.
Fri 23 Aug 17:29:43 BST 2019 : calling configure.sh
Fri 23 Aug 17:29:43 BST 2019 : configure: /tmp/configure.sh starting with REPO=marcone, BRANCH=main-dev, ARCHIVE_SYSTEM=cifs
Fri 23 Aug 17:29:43 BST 2019 : configure: Getting files from marcone:main-dev
Fri 23 Aug 17:29:43 BST 2019 : configure: Pushover not configured.
Fri 23 Aug 17:29:43 BST 2019 : configure: Gotify not configured.
Fri 23 Aug 17:29:43 BST 2019 : configure: Gotify not configured.
Fri 23 Aug 17:29:43 BST 2019 : configure: Starting download for /root/bin/send-push-message
Fri 23 Aug 17:29:44 BST 2019 : configure: Done
Fri 23 Aug 17:29:44 BST 2019 : configure: Starting download for /root/bin/send_sns.py
Fri 23 Aug 17:29:45 BST 2019 : configure: Done
Fri 23 Aug 17:29:45 BST 2019 : configure: Checking archive configs:
Fri 23 Aug 17:29:45 BST 2019 : configure: done
Fri 23 Aug 17:29:45 BST 2019 : configure: Using archive module: run/cifs_archive
Fri 23 Aug 17:29:45 BST 2019 : configure: Installing base archive scripts into /root/bin
Fri 23 Aug 17:29:45 BST 2019 : configure: Starting download for /root/bin/archiveloop
Fri 23 Aug 17:29:46 BST 2019 : configure: Done
Fri 23 Aug 17:29:46 BST 2019 : configure: Starting download for /root/bin/remountfs_rw
Fri 23 Aug 17:29:47 BST 2019 : configure: Done
Fri 23 Aug 17:29:47 BST 2019 : configure: Starting download for /root/bin/tesla_api.py
Fri 23 Aug 17:29:48 BST 2019 : configure: Done
Fri 23 Aug 17:29:48 BST 2019 : configure: Installing archive module scripts
Fri 23 Aug 17:29:48 BST 2019 : configure: Starting download for /tmp/verify-and-configure-archive.sh
Fri 23 Aug 17:29:49 BST 2019 : configure: Done
Fri 23 Aug 17:29:49 BST 2019 : configure: Starting download for /root/bin/archive-clips.sh
Fri 23 Aug 17:29:50 BST 2019 : configure: Done
Fri 23 Aug 17:29:50 BST 2019 : configure: Starting download for /root/bin/connect-archive.sh
Fri 23 Aug 17:29:51 BST 2019 : configure: Done
Fri 23 Aug 17:29:51 BST 2019 : configure: Starting download for /root/bin/disconnect-archive.sh
Fri 23 Aug 17:29:52 BST 2019 : configure: Done
Fri 23 Aug 17:29:52 BST 2019 : configure: Starting download for /root/bin/write-archive-configs-to.sh
Fri 23 Aug 17:29:53 BST 2019 : configure: Done
Fri 23 Aug 17:29:53 BST 2019 : configure: Starting download for /root/bin/archive-is-reachable.sh
Fri 23 Aug 17:29:53 BST 2019 : configure: Done
Fri 23 Aug 17:29:53 BST 2019 : configure: Starting download for /root/bin/copy-music.sh
Fri 23 Aug 17:29:54 BST 2019 : configure: Done
Fri 23 Aug 17:29:54 BST 2019 : verify-and-configure-archive: Installing/updating required packages if needed
Fri 23 Aug 17:29:59 BST 2019 : verify-and-configure-archive: Done
Fri 23 Aug 17:29:59 BST 2019 : verify-and-configure-archive: Verifying that the archive server NASTORMWIND2.local is reachable...
Fri 23 Aug 17:29:59 BST 2019 : verify-and-configure-archive: The archive server is reachable.
Fri 23 Aug 17:29:59 BST 2019 : verify-and-configure-archive: Verifying that the archive share is mountable...
Fri 23 Aug 17:29:59 BST 2019 : verify-and-configure-archive: Trying mount command-line:
Fri 23 Aug 17:29:59 BST 2019 : verify-and-configure-archive: mount -t cifs '//NASTORMWIND2.local/TeslaCam' '/tmp/archivetestmount' -o 'credentials=/tmp/teslaCamArchiveCredentials,iocharset=utf8,file_mode=0777,dir_mode=0777,,'
Fri 23 Aug 17:30:00 BST 2019 : verify-and-configure-archive: The archive share is mountable using: mount -t cifs '//NASTORMWIND2.local/TeslaCam' '/tmp/archivetestmount' -o 'credentials=/tmp/teslaCamArchiveCredentials,iocharset=utf8,file_mode=0777,dir_mode=0777,,'
Fri 23 Aug 17:30:00 BST 2019 : verify-and-configure-archive: Verifying that the archive share is mountable...
Fri 23 Aug 17:30:00 BST 2019 : verify-and-configure-archive: Trying mount command-line:
Fri 23 Aug 17:30:00 BST 2019 : verify-and-configure-archive: mount -t cifs '//NASTORMWIND2.local/Public/TESLA/TeslaMusic' '/tmp/archivetestmount' -o 'credentials=/tmp/teslaCamArchiveCredentials,iocharset=utf8,file_mode=0777,dir_mode=0777,,'
Fri 23 Aug 17:30:00 BST 2019 : verify-and-configure-archive: The archive share is mountable using: mount -t cifs '//NASTORMWIND2.local/Public/TESLA/TeslaMusic' '/tmp/archivetestmount' -o 'credentials=/tmp/teslaCamArchiveCredentials,iocharset=utf8,file_mode=0777,dir_mode=0777,,'
Fri 23 Aug 17:30:00 BST 2019 : verify-and-configure-archive: Configuring the archive...
Fri 23 Aug 17:30:00 BST 2019 : verify-and-configure-archive: Configured the archive.
Fri 23 Aug 17:30:00 BST 2019 : configure: Skipping rc.local installation
Fri 23 Aug 17:30:00 BST 2019 : make-root-fs-readonly: start
Fri 23 Aug 17:30:00 BST 2019 : make-root-fs-readonly: Removing unwanted packages...
Fri 23 Aug 17:30:10 BST 2019 : make-root-fs-readonly: Installing ntp and busybox-syslogd...
Fri 23 Aug 17:30:15 BST 2019 : make-root-fs-readonly: Configuring system...
Fri 23 Aug 17:30:15 BST 2019 : make-root-fs-readonly: done
Fri 23 Aug 17:30:15 BST 2019 : Upgrading installed packages...
Fri 23 Aug 17:30:22 BST 2019 : All done.
pi@teslausb:~ $

and
/mutable/archiveloop.log

Thu  3 Nov 17:17:06 GMT 2016: Starting archiveloop...
Thu  3 Nov 17:17:07 GMT 2016: Waiting for time to be set by ntpd...
Fri 23 Aug 18:02:25 BST 2019: Time still not set, attempting to force it
Fri 23 Aug 18:02:25 BST 2019: Failed to set time
Fri 23 Aug 18:02:25 BST 2019: Ensuring music backing file is mounted...
Fri 23 Aug 18:02:25 BST 2019: Mounting /mnt/music...
Fri 23 Aug 18:02:25 BST 2019: Mounted /mnt/music.
Fri 23 Aug 18:02:26 BST 2019: Ensured music drive is mounted.
Fri 23 Aug 18:02:26 BST 2019: Running fsck on /mnt/music...
Fri 23 Aug 18:02:26 BST 2019: | fsck from util-linux 2.29.2
Fri 23 Aug 18:02:27 BST 2019: | fsck.fat 4.1 (2017-01-24)
Fri 23 Aug 18:02:27 BST 2019: | 0x41: Dirty bit is set. Fs was not properly unmounted and some data may be corrupt.
Fri 23 Aug 18:02:27 BST 2019: |  Automatically removing dirty bit.
Fri 23 Aug 18:02:27 BST 2019: | Performing changes.
Fri 23 Aug 18:02:27 BST 2019: | /dev/loop0: 164 files, 55578/1469343 clusters
Fri 23 Aug 18:02:27 BST 2019: Finished fsck on /mnt/music.
Fri 23 Aug 18:02:27 BST 2019: Unmounting /mnt/music...
Fri 23 Aug 18:02:27 BST 2019: Unmounted /mnt/music.
Fri 23 Aug 18:02:27 BST 2019: Archiving...
Fri 23 Aug 18:02:27 BST 2019: Disconnecting usb from host...
Fri 23 Aug 18:02:28 BST 2019: Disconnected usb from host.
Fri 23 Aug 18:02:28 BST 2019: Ensuring cam archive is mounted...
Fri 23 Aug 18:02:28 BST 2019: /mnt/archive is already mounted.
Fri 23 Aug 18:02:28 BST 2019: Ensured cam archive is mounted.
Fri 23 Aug 18:02:28 BST 2019: Ensuring music archive is mounted...
Fri 23 Aug 18:02:28 BST 2019: /mnt/musicarchive is already mounted.
Fri 23 Aug 18:02:28 BST 2019: Ensured music archive is mounted.
Fri 23 Aug 18:02:28 BST 2019: Starting recording archiving...
Fri 23 Aug 18:02:28 BST 2019: Ensuring cam file is mounted...
Fri 23 Aug 18:02:28 BST 2019: Mounting /mnt/cam...
Fri 23 Aug 18:02:28 BST 2019: Mounted /mnt/cam.
Fri 23 Aug 18:02:28 BST 2019: Ensured cam file is mounted.
Fri 23 Aug 18:02:28 BST 2019: Running fsck on /mnt/cam...
Fri 23 Aug 18:02:28 BST 2019: | fsck from util-linux 2.29.2
Fri 23 Aug 18:02:30 BST 2019: | fsck.fat 4.1 (2017-01-24)
Fri 23 Aug 18:02:30 BST 2019: | 0x41: Dirty bit is set. Fs was not properly unmounted and some data may be corrupt.
Fri 23 Aug 18:02:30 BST 2019: |  Automatically removing dirty bit.
Fri 23 Aug 18:02:30 BST 2019: | Performing changes.
Fri 23 Aug 18:02:30 BST 2019: | /dev/loop0: 414 files, 176467/1656092 clusters
Fri 23 Aug 18:02:30 BST 2019: Finished fsck on /mnt/cam.
Fri 23 Aug 18:02:30 BST 2019: wake up car process is 1443
Fri 23 Aug 18:02:30 BST 2019: Moving clips to archive...
Fri 23 Aug 18:02:30 BST 2019: Creating output directory ''
Fri 23 Aug 18:02:30 BST 2019: Creating output directory '2019-08-22_19-13-17'
Fri 23 Aug 18:02:30 BST 2019: Failed to create '2019-08-22_19-13-17', check that archive server is writable and has free space
Fri 23 Aug 18:02:30 BST 2019: Moved 0 file(s), failed to copy 0, deleted 0.
Fri 23 Aug 18:02:30 BST 2019: Finished moving clips to archive.

Fri 23 Aug 18:02:31 BST 2019: Unmounted /mnt/cam.
Fri 23 Aug 18:02:31 BST 2019: Finished archiving.
Fri 23 Aug 18:02:31 BST 2019: Copying music...
Fri 23 Aug 18:02:31 BST 2019: Starting music sync...
Fri 23 Aug 18:02:31 BST 2019: Ensuring music backing file is mounted...
Fri 23 Aug 18:02:31 BST 2019: Mounting /mnt/music...
Fri 23 Aug 18:02:31 BST 2019: Mounted /mnt/music.
Fri 23 Aug 18:02:31 BST 2019: Ensured music drive is mounted.
Fri 23 Aug 18:02:31 BST 2019: Running fsck on /mnt/music...
Fri 23 Aug 18:02:31 BST 2019: | fsck from util-linux 2.29.2
Fri 23 Aug 18:02:32 BST 2019: | fsck.fat 4.1 (2017-01-24)
Fri 23 Aug 18:02:32 BST 2019: | 0x41: Dirty bit is set. Fs was not properly unmounted and some data may be corrupt.
Fri 23 Aug 18:02:32 BST 2019: |  Automatically removing dirty bit.
Fri 23 Aug 18:02:32 BST 2019: | Performing changes.
Fri 23 Aug 18:02:32 BST 2019: | /dev/loop0: 164 files, 55578/1469343 clusters
Fri 23 Aug 18:02:32 BST 2019: Finished fsck on /mnt/music.
Fri 23 Aug 18:02:32 BST 2019: Copying music from archive...
Fri 23 Aug 18:02:32 BST 2019: Copied 0 music file(s), skipped 42 previously-copied files, encountered 0 errors.
Fri 23 Aug 18:02:32 BST 2019: Unmounting /mnt/music...
Fri 23 Aug 18:02:33 BST 2019: Unmounted /mnt/music.
Fri 23 Aug 18:02:33 BST 2019: Finished copying music.
Fri 23 Aug 18:02:33 BST 2019: unmounting /mnt/archive
Fri 23 Aug 18:02:33 BST 2019: unmounting /mnt/musicarchive
Fri 23 Aug 18:02:33 BST 2019: Connecting usb to host...
Fri 23 Aug 18:02:33 BST 2019: Connected usb to host.
Fri 23 Aug 18:02:33 BST 2019: Waiting for archive to be unreachable...
pi@teslausb:~ $

I'm loosing my mind.
If anyone has a secret or a fix or an idea for checking what's going on when backup is launched...
Thanks for your help.

Btw, I don't get this :

Fri 23 Aug 18:02:30 BST 2019: Creating output directory '2019-08-22_19-13-17'
Fri 23 Aug 18:02:30 BST 2019: Failed to create '2019-08-22_19-13-17', check that archive server is writable and has free space

All permission are set and when I mount the folder manually I'm able to create and delete everything...

Finally I started from scratch again, checked everything again, and now it works....
Case closed for now :)


Build and run local

hi guy, I build and run on my computer. When I login it appear error :
error: {
"status": "error",
"error": "Authorization error.",
"code": 1000
}

please help me.
thanks a lot

@VyVu what authentication method are you using? That error looks normal for the UI trying to access and API while it is not authenticated. Will need more information about the context of the error to provide any assistance.

i'm using basic authentication method.

That error is standard when trying to access the UI before you are authenticated. It's related to trying to fetch the users profile and isn't related to an authentication request itself. Does it continue after authentication?


Run all integration tests on Dask

Run all integration tests on Dask
Description

Category: test
JIRA issue: None

Didn't actually catch any bugs by doing this, but I think it is worth doing. Also removed some unnecessary cruft in the tests.
Testing

[x] all tests pass (pytest --runslow)

I ran some additional large-scale performance testing in https://github.com/ihmeuw/vivarium_research_prl/pull/69.


stop using old versions of node.js

12 is technically not eol

I just noticed tsdx defaults include 10 not 16. Seemed worth keeping versions inline with current version best practice. This is not important.

_ No description provided. _

Thanks


Document the parameters that can be passed to B2C

I think it would be helpful to document the parameters that can be passed to B2C when obtaining tokens.
Example: client_id, response_type, scope, etc.
On OAuth 2.0 authorization code flow -> Use an edit-profile policy is a table that has some of the parameters.

I don't think that list is exhaustive
It is very hard to find.  I'm looking for something global, like under the Reference section.

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

ID: b05da885-25ac-99ff-890d-97e9c670f1d7
Version Independent ID: 0673a2a2-e408-8ed4-83c8-1acc461d2c74
Content
Content Source
Service: active-directory-b2c

@spottedmahn Thanks for the feedback, I assigned the case for further investigation.

@spottedmahn  Thank you for bringing this to our attention. We have opened an item in our documentation backlog to have this investigated and updated. We'll respond back to you on this issue when we've done the work. For now, we'll close this GitHub issue.
#please-close

that's great, thanks @davidmu1!


Show with numeric Slug causes endpoint conflicts

I’ve been alerted to an issue where interactions with the show named “24” are causing those actions to be applied to the show named “Presidio Med” due to the usage of the Trakt Slug instead of the Trakt ID for some endpoints (for reasons I haven’t looked into again just yet, for a lot of them I use the Trakt ID).
For example, grabbing the first episode using
https://api.trakt.tv/shows/24/seasons/1/episodes/1 returns the Presido Med episode, due to its Trakt ID being 24, even though it was intended to be the episode of the show “24” who’s slug is “24”.
I’m wondering whether this is intended or if maybe it’s an unconsidered edge case bug that needs to be addressed?
Either way I will look further into using the Trakt ID instead of the slug but figured it’s still an issue otherwise considering the end points take both slug and ID, and maybe slugs shouldn’t ever be only numeric (eg. “24”’s slug should maybe include the year between a dash such as “24-2001”. Similar to The Flash (2014) which is “the-flash-2014”, even though I assume it’s only like that because there was already The Flash (1990) which had “the-flash”).
Sent with GitHawk

Is there any official method of creating slugs, like adding the first air year at the end of the show name etc, and similarly for movies?

Nah, you shouldn’t need to create them, they’re returned in all the normal objects alongside their other IDs. It’s just once you get an object, you can use either the Trakt ID, Trakt Slug or IMDb ID for a bunch of endpoints (and it matches whatever it finds first etc). Hence the conflict when the slug is numeric only. As “24” will be matched as a Trakt ID.
Sent with GitHawk

The official recommendation is to use Trakt IDs in the URLs for this reason. We also support Trakt slugs and IMDB IDs, but those aren't guaranteed to work like the Trakt ID will.

Awesome, no worries. Just figured I’d check, in case there was some specific way to specify which ID is being sent etc. I’ll go ahead and make sure I’m using the Trakt ID unless absolutely necessary. Thanks!
Sent with GitHawk

Thank you for pointing that out!
I've been wondering for a while why I get derpy results in some cases for my webapp (which I'm in the process of completely rewriting anyway, now knowing what to do better)


Localization doesn't work with Carthage installation

Hi,
I try to use armchair. I use this in my AppDelegate
    Armchair.appID("12345678")

    // Demo mode
    Armchair.showPrompt()

And I added a new language under the project tab. The prompt is always shown in english. Any hints?
Thanks for helping in advance.

Using master head code or tagged one: 0.1.2( Dec 10, 2015) ?
Fix localization by getting the framework bundle ce4d4a42ff62dcffec56fd7980e8d61ad1814f6e committed on Dec 11, 2015


Update readme to refer to this repo

Unlikely someone will hit this, but we probably should make sure people don't accidentally clone a five year old version of this repo instead of the current one.

Wait, did we outsource writing the app market? is that why it's so janky?

Yes.
But to be fair, we outsourced it to a Meteor dev shop and asked them to write it as an SPA, which in retrospect was not a good idea, but that's totally on me.


Release cycle same as in Spring Boot project

It would be nice to have all the dependencies updated to versions as in Spring Boot.
Now SB is 2.0.1.RELEASE and has newer dependencies than this starter which is 2.0.0.RELEASE.

@jzheaux It would be nice also to have a branch that align with 2.1.0.M2.

@DanielFran We will do a 2.1.0.M2 release on August 28th.

Closing since we now have milestones configured and scheduled for each of the boot releases.


refactor(Data/Matrix/Basic): use a defeq for scalar that matches its docstring

This changes the defeq from scalar a = a • 1 to scalar a = diagonal fun _ => a, which has the nice bonus of making algebraMap_eq_diagonal true by rfl.
As a result, we need a new smul_one_eq_diagonal lemma to rewrite diagonal fun _ => a back into a • 1, along with some variants for convenience.
In the long term we could generalize this to non-unital rings, now that it needs no 1.

[x] depends on: #8088
[x] depends on: #8116

bors merge


Immediate-mode clientside 2D/3D rendering functions

Right now, the only way to render basic geometric shapes is to use the Elements, like I do with my racing game:
#[element_component]
fn DebugLines(hooks: &mut Hooks) -> Element {
    let lines = hooks.use_query(components::debug_lines());

    Group::el(lines.into_iter().flat_map(|(_, lines)| {
        lines
            .chunks(2)
            .map(|line| {
                let [start, end]: [Vec3; 2] = line.try_into().unwrap();

                Element::new()
                    .init_default(rect())
                    .with_default(main_scene())
                    .with(line_from(), start)
                    .with(line_to(), end)
                    .with(line_width(), 0.05)
                    .with(color(), vec4(1., 1., 1., 1.))
            })
            .collect::<Vec<_>>()
    }))
}

However, this requires having an Element workflow set up, which can be quite difficult to wire up to the game state / drive correctly. This is especially true if your gameplay logic is quite distant from the top-level. We should improve that experience where possible, but we should also consider adding primitives for basic imperative rendering:

Rendering lines / rects
Rendering text
Rendering points

Where possible, we should encourage people to use Element or the dedicated renderer, so we should avoid offering too much functionality here. This is purely for convenience, so that you can easily debug in-place.

Yes, this kind of facility very useful for debugging. Kinda like https://docs.unity3d.com/ScriptReference/Debug.DrawLine.html where you can call it anywhere in your client code and have a line.

The simplest APIs would be to take one primitive at the time, but do you think the WIT calling overhead makes it unusable? If say I want to draw 1000 lines every frame. We can also make all APIs always take a slice so users can them more efficiently. Or both.

Good question. I'd say we should try a one function=one primitive solution to begin with, and then consider adding solutions for bulk primitives if the overhead becomes untenable.

We already have the gizmos system which have an immediate mode line/sphere/rect/cube rendering.
Could we make use of that and extend it and expose it to the guest api?

We already have the gizmos system which have an immediate mode line/sphere/rect/cube rendering.
Could we make use of that and extend it and expose it to the guest api?

I looked at the Gizmos but felt like the design and implementation are a bit overkill for this very simple use case. Rather than trying to retrofit existing gizmos, I'd like to do a clean implementation.

As an aside: gizmos usually mean something that you use to interact with an object inside an editor. I think that domain is where the gizmos belong.


WNS support on windows phone 8.1

Hi,
this is not really an issue.
I need support of WNS on windows phone 8.1. Do you think you will add it?
Either way, since it's supported on windows 8 version of plugin, is there a simple way to replicate the code on wp8 version to add wns support?
Thanks
F.

Hi Fredericks,
I was wondering the same thing. I ended up creating a fork of the plugin with MPNS support replaced by a WNS implementation. See https://github.com/ttahola/PushPlugin.
best regards, Tero

@ttahola Do you have an example? I'm having some issue.
Where do I put the package SID or Cliente secret and what do I put for Windows configuration

I was using amazon push notifications service (SNS) to test this. If I remember correctly, I put the package SID and client secret into amazon control panel. And when the phone is registered to Windows Notification Service, you will get a channel URI that will serve as an endpoint for push notifications for that specific phone.
But it has been so long time since I tried this, sorry, I may not be able to help :D unfortunately I don't have the phone or the development environment available anymore.
You might be able to proceed by looking the source code of WNS plugin I implemented on my fork of the Cordova Push Notifications Plugin at https://github.com/ttahola/PushPlugin/blob/master/src/wp8/PushPlugin.cs
But be warned that I'm not actively maintaining that code anymore, so it should be considered a reference implementation only.


Add missing docstrings

Codecov Report

Merging #7 (87adc17) into master (e382f6c) will increase coverage by 0.00%.
The diff coverage is 100.00%.

@@           Coverage Diff           @@
##           master       #7   +/-   ##
=======================================
  Coverage   99.29%   99.29%
=======================================
  Files           6        6
  Lines         284      285    +1
  Branches       17       17
=======================================
+ Hits          282      283    +1
  Partials        2        2

Impacted Files
Coverage Δ

app/storage.py
100.00% <ø> (ø)

app/config.py
100.00% <100.00%> (ø)

app/controllers.py
97.40% <100.00%> (ø)

app/helpers/task_list.py
100.00% <100.00%> (ø)

app/main.py
100.00% <100.00%> (ø)

app/models.py
100.00% <100.00%> (ø)

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update e382f6c...87adc17. Read the comment docs.


Auto select node/npm version with asdf / nvm

Signed-off-by: Kevin Cormier<EMAIL_ADDRESS>

/cc @RobDolares

/cherry-pick release-2.6

/cherry-pick release-2.5

/cherry-pick backplane-2.0

/cherry-pick release-2.4


Disable chunked encoding for HTTP server responses

What version of Go are you using (go version)?
go version go1.12.6 darwin/amd64
What did you do?
Because of AWS lambda does not support stream response, so I want to disable chunked encoding. how should I disable it?

Chunked encoding is required when the server doesn't know in advance the length of your response. You can just set the Content-Length response header, and chunked encoding will be automatically disabled.
The golang/go issue tracker is used to develop the Go project, so you'll get more help with questions about using the Go language through the resources listed at https://golang.org/wiki/Questions.

That information might a good candidate for a paragraph in the godoc for http module or one of the calls there


[Bug] Possible to use 'Request => url' function as Query value

Insomnia Version: 6.02
Operating System: Windows 10

Details
[Bug] Possible to use 'Request => url' function as Query value:

After doing this Insomnia hangs sometimes. I think it goes to infinite loop with adding parameter to url and recalculating the url

Hmm, this may be a tricky one to fix. It's definitely infinite recursion. Any ideas?


Security Scorecards integration

See https://github.com/ossf/scorecard for more info.
Reviewer checklist

[ ] Ensure relevant issues are linked (description should include text like "Fixes #")
[ ] Ensure correct labels applied
[ ] Ensure any appropriate documentation has been added or amended

Coverage: 96.075%. Remained the same when pulling 9d9000ff7932439319599361cd9382c8b8b1648e on scorecards into 3d7f7451357ca878b6ecad54caadf75963d34052 on main.


Make keystone_server_url config optional in openstack_controller

What does this PR do?
Make keystone_server_url config optional in openstack_controller since it comes on the openstack config file

I think there is a condition remaining in the check method which will fail if the URL isn't present. Which makes me think it's not tested, which is a bit sad.

Seems it just logs a warning


fix(deno): incorrect handling of deno config for emit

fixes #309
adds sourcemap option

@barbados-clemens could this one please be code reviewed as well?


'Ghost' NPC with type 0

I'm sorry for not using the issue template, because it's just a strange behaviour, not an ordinary 'bug', and seems to be a problem from vanilla Terraria.
In a projectile AI, I wanted to fetch a list of NPCs that had one of my buffs on. When I call Main.npc.Where with NPC.HasBuff in the condition, it threw an IndexOutOfBoundsException in FindBuffIndex. I was frustrated, and checked your code. I found that it seem to be buffimmune. I outputed the length in the Where lambda (I created a function that outputs and returns true, and && in the condition) and got 206, which is the length in vanilla terraria. With my mod it should be 306.
But strangely, this npc is active but not calling GlobalNPC.AI. It does not have a name,and has a type of 0. It seems that it is not initialized by tModLoader.
An appearant solution is to check npc.type==0, but I'm curious about it.
Could you explain to me why is this NPC active, and why we need an NPC here?
If this NPC is not important, would you mind removing it from Main.npc in the next version?

Can you provide a minimum complete reproducible example for us? Everything in Main.npc should have the correct buffImmune array, it would be good to fix this.

You just need to create any mod buffs and call Main.npc.Where((n) => n.active &&n.HasBuff(mod.BuffType<...>())) in ModProjectile.AI. The reproduction rate here seem to be 100%.

I'm really sad and I feel sorry for not being able to present an entire reproducible example :sob:. The repairing shop says my computer has got some more problems and I should wait for another 2 days... Could you use ExampleMod to reproduce the problem? Just need to add
Main.npc.Where(n => n.active && n.HasBuff(mod.BuffType("Nullified")));  // Or some other buffs

to any of ModProjectile.AI().

I tried this but didn't experience any exceptions. When you get around to this, can you verify that this happens with a fresh launch of tmodloader where only examplemod is enabled?

I'm really sorry.. We tried for a long time but we cannot reproduce it... There seems to be somewhere unknown here in my mod producing this strange behavior...

K, feel free to reopen this if you find a reproducible situation.


[MINOR][PYTHON] Remove unnecessary quotes in pyspark

What changes were proposed in this pull request?
Remove unnecessary quotes in pyspark
Why are the changes needed?
 To make the code clean
Does this PR introduce any user-facing change?
No
How was this patch tested?
Existing tests

cc @HyukjinKwon

cc @zero323 FYI

cc @zero323 FYI

Thanks. Should be OK, as long as the tests pass, though I won't be able to review it properly at the moment.

Merged to master.


refactor: remove code related to embedded text extraction

This PR removes all code related to filling inferred elements text from embedded text (pdfminer). This PR is the first part of moving embedded text related code from unstructured-inference to unstructured and works together with https://github.com/Unstructured-IO/unstructured/pull/3061.

LGTM. This is the logic that moved over in Unstructured-IO/unstructured#3061 right?

Yes, that's right.


Prevent overwriting source file when cmorizing

At the moment the function esmvaltool.preprocessor.fix_file overwrites the source file. This does not work if the input data is stored in a read only location and is an unexpected result of running the esmvaltool. Instead, the input file should be copied to the preprocessor output directory and the copy should be fixed.

This a serious bug, it should definitely not overwrite the source file in any case.

Let's clarify:
This function in _reformat.py is wrong
def fix_file(filename, short_name, project, model):
    """Fix errors that prevent loading or can not be fixed in the cube."""
    for fix in Fix.get_fixes(
            project=project, model=model, variable=short_name):
          fix.fix_file(filename)
    return filename

fix_file is returning a filename that must be captured. By default is the same one that it receives, but fixes MUST change it if they need to do something. The function should be:
def fix_file(filename, short_name, project, model):
    """Fix errors that prevent loading or can not be fixed in the cube."""
    for fix in Fix.get_fixes(
            project=project, model=model, variable=short_name):
          filename = fix.fix_file(filename)
    return filename

Nevertheless, there is a bug in the CESM1-BGC nbp fixer that is working with the original file instead of a copy. The bad news is that this bug has prevented us to detect the other. I will fix both

This means that no fixes were applied before, but also that no input files were overwritten.
Is that correct?

No. This means that, thanks to the overwriting bug in the only fix applied at file level, we did not detect the bug in the fix_file function.


added support for getting envelopeInfo based on an envelopeId

great, thanks so much @loredanalehadus this is more new functionality, right?
does it work for you? just making sure before I merge. thanks!

Hello,
Yes, it's working. I'm already using this in my application.
Sent from my iPhone

On Nov 16, 2015, at 18:24, Inbar Gazit<EMAIL_ADDRESS>wrote:
great, thanks so much @loredanalehadus this is more new functionality, right?
does it work for you? just making sure before I merge. thanks!
—
Reply to this email directly or view it on GitHub.

Hey,
It seems that including the dll in the project works but only on my machine. When I deploy it the nuget packages restore overrides the library i included. How much time do you think you'll need in order to get a new nuget? I will apreciate it if it will be asap.
Thanks,
Loredana
Sent from my iPhone

On Nov 16, 2015, at 18:24, Inbar Gazit<EMAIL_ADDRESS>wrote:
great, thanks so much @loredanalehadus this is more new functionality, right?
does it work for you? just making sure before I merge. thanks!
—
Reply to this email directly or view it on GitHub.

sure thing, will try to get this out today!

this one has conflicts, I'll need to resolve them later, not sure why this happened.

Let me know if you need help with it. Maybe i can merge on my branch and make a new pull request?
Sent from my iPhone

On Nov 17, 2015, at 15:42, Inbar Gazit<EMAIL_ADDRESS>wrote:
this one has conflicts, I'll need to resolve them later, not sure why this happened.
—
Reply to this email directly or view it on GitHub.

I think we're good. I had a conflict in envelope.cs that seems to be stylistic and only like spaces and such. please check latest master branch and let me know

@loredanalehadus I just pushed a new nuget (version 1.7.0) with your changes. Can you confirm it's working for you when you deploy? thanks!


Paper 57005, gene extraction problem

@valearna this is for you to check:
The authors have added trx-1 ( WBGene00015062 ) and Removed: Bm1_46700A ( WBGene00222771 ): trx-1 is asynonym of Bm1_46700A: TAG2510, Bm1_46705, Bm1_46700A, trx-1.
It seems that instead of trx-1, the pipeline extracted Bm1_46700A. This might be fixed already as we changed the order of priorities, e.g. locus, sequence, synonym
Can you please check?

Thanks @draciti for bringing up this example. I ran the pipeline in debug mode on paper 57005 with the new priorities and I see trx-1 extracted instead of Bm1_46700A. This means that this issue is solved and won't affect future extractions.

Wonderful! closing


MVP Additions ahead on demo Monday 4/17

Here are the priorities coming out of tonight's work session for improvements to the MVP ahead of @NealHumphrey 's demo on Monday. It's all very related to the larger issue #143 .

Add ability to display two fields on top of the main map view: building permit count and crime count. These will be provided by API call, which should be ready for use by Wednesday evening. The API should return JSON (one array of objects) per zone aggregation type. Subtasks could be divided this way:

[ ] build menu, top-left of map, similar to zone selector that offers the two options of Crime and Building permit
[ ] selecting an option calls relevant API endpoint and returns appropriate data (or we fetch data on load in anticipation)
[ ] the harder part: have mapBox fill the zones based on the data

Link the selection of 'Neighborhood' to the options in the dropdown for the pie charts. (I can do this—didn't realize it was actually Neighborhood cluster, which has a one-to-one mapping to the project.csv data.

Add legend to map to explain the color-coding of the dots.

Leave the pie charts (NH edit: aggregating client side) connected to static projects.csv file (NH edit: now pulling from API) for now, but add (probably not programmatically—just force them in) the human readable field names as labels

Animate the pie charts when subzones are selected from the dropdown. I think this would be easier if the donuts were really showing just one arc ("yes") on top of a 360* background, rather than two arcs.

Some cleaning up of the building view page. Like can the be styled more like the map on the map view page? Get rid of unused accordion sections? (NH edit: should keep them we can fill in w/ some placeholders)

Let me know if anything's unclear, and let's let others know if you're jumping on anything.

Hey @ostermanj and @ptgott, moving conversation to this ticket for now until we get the version for Monday deployed - we can do a sweep of issue #143 after Monday to pick up any lingering issues we haven't dealt with yet.

The API endpoints I described in #143 are live on the Flask API.

Use the format http://hiapidemo.us-east-1.elasticbeanstalk.com/api/raw/<tablename> to get the raw data for any table from these currently available options: ['census_mapping', 'project', 'subsidy', 'acs_rent_lower', 'acs_rent_median', 'crime', 'acs_rent_upper', 'manifest', 'building_permits']
Use the format http://hiapidemo.us-east-1.elasticbeanstalk.com/api/<tablename>/all/<zonetype> for the tables building_permits, crime and zones of anc, ward, neighborhood_cluster. zipcode is available for building_permits only since zipcode wasn't in the source data for crime and we'll need to add a geocoding function - won't be there for Monday.

@ptgott 's code is merged in to dev, which provides the API version of the projects table. I upped the raw limit to 1,000 so that we'd get all project records from this endpoint (but so we wouldn't crash anything with 50,000 crime records in one endpoint).

I can focus on 6) if you all can focus on the map view items. I will try to add relevant API endpoints so that those views can be live updated (for example an endpoint that servers up building_permits within X miles). I may need your help with the Javascript side of stuff - and may hack some things in that will need better treatment using the getAPIData() approach.

I'll have a stab today at the third part of (1), 'have mapBox fill the zones based on the data'. I'll set the 'visibility' layout property to 'none' to anticipate making the menu.

In PR #201, I've implemented a version of the third task under item one. I've changed 'getAPIData()' in housing-insights.js into a slightly different function, 'getInitialData()', to reflect two things about it: first, it fetches data from the project server in general, rather than just the API; and second, in its current form, the code is meant to grab all data sources we might need for a given view before that view loads (there's currently an issue with this; see below).
I've also added an 'addDataToPolygons' function in rich-map.js, which adds values from the aggregate datasets to the appropriate geojson polygon FeatureCollection. Currently the third argument is a callback that converts the naming conventions of the geojson file to those of the API data, but we might be able to do away with this if the zone names within all of the API data differ from the zone names within all of the geojson polygon files in a consistent way.
Another thing to note: currently I've produced filled polygon layers for crime and building permits with zoning layers for ward and neighborhood-cluster. I've assigned the aggregates for both crime and building_permits within a single Mapbox source for each of ward and neighborhood_cluster. We can split these into separate sources if you'd like.
Some other outstanding things

We could add a 'loading' animation as the data load.

We could give app.dataCollection a more hierarchical structure. Currently I represent hierarchy using underscores ('crime_ward', 'crime_neighborhood'...).

There doesn't seem to be a geoJSON polygon source for ANC in the javascript/tool/data folder.

I define the color range for the filled polygon layers arbitrarily. It's probably a good idea to use D3's ability to define ranges dynamically.

There's an outstanding issue in which in some browsers (e.g. Chrome), the map loads before the data do and prevents the proper map styling from taking place. We could put the map declaration within the 'prepareMaps()' callback in rich-map.js and fix whatever repercussions emerge from that (h/t to Neal Williams).

@ptgott, a couple responses:

for your addDataToPolygons method, we should (after this weekend) work to get all data sources to behave consistently in how they use zone names. We can make sure the geoJSON and the API have the exact same label for each zone so that no callback is necessary.
I'm guessing a heirarchical structure for the data will be useful, e.g. nesting 'neighborhood' and 'ward' under 'crime' so that when we have many more data sources we can refactor the 'add layer' code to act dynamically on toggle instead of adding a layer for all of them. We should flag this for a post-MVP refactor discussion.

Thanks for this! I've made some good progress on 6) and will be doing my own PR later today.

When using Firefox on my internet connection (it isn't great), the app doesn't always successfully finish all its API calls within the 10 x 500 millisecond time limit specified in housing-insights.js.  We probably want to bump this limit up before the demo, otherwise a slow internet connection could make the app totally nonfunctional.  See issue #209


NodePort for ingressgateway loadbalancer service change every time there is a change to the service through the operator breaking upstream cloud LoadBalancers

Bug description
Link to my post in the forum
When deploying an ingressgateway using the operator a Service of type LoadBalancer is created and some nodeports are allocated. This ports are supposed to be immutable and in particular when used with AWS load balancer they must be since the option can't be updated in the targetgroup once the TG is created.
Whenever a change to the service is applied by the istio-operator though the nodeport change causing the Upstream cloud load balancer to break either temporarily , if the cloud resource can be updated, or indefinitely in aws where the tg cannot be updated with the new port.
My Current Workaround is to set the nodeport in the service spec , but that is fragile and potentially could create conflict
On a unmanaged Service Loadbalancer any change can be performed without causing the nodeport to change.
Affected product area (please put an X in all that apply)
[ ] Docs
[ ] Installation
[X] Networking
[ ] Performance and Scalability
[ ] Extensions and Telemetry
[ ] Security
[ ] Test and Release
[ ] User Experience
[ ] Developer Infrastructure
[ ] Upgrade
Affected features (please put an X in all that apply)
[ ] Multi Cluster
[ ] Virtual Machine
[ ] Multi Control Plane
Expected behavior
Service managed by the istio operator should behave like a normal un-managed kubernetes service loadbalancer, nodeports should not change once allocated.
Steps to reproduce the bug

Install istio operator
apply a resource like

---
apiVersion: install.istio.io/v1alpha1
kind: IstioOperator
metadata:
  name: standard
  namespace: istio-system
spec:
  components:
    ingressGateways:
    - enabled: true
      k8s:
        service:
          ports:
          - name: http
            port: 80
            targetPort: 8080
          - name: https
            port: 443
            targetPort: 8443
      name: public-ingress
      namespace: istio-system
  profile: default

wait for the service to show up nodeport is 80:31497

public-ingress     LoadBalancer   <IP_ADDRESS>    <pending>     80:31497/TCP,443:32045/TCP              3m30s

change port name from http to http2 and apply istiooperator  - watch the nodeports change - > 80:31748

public-ingress     LoadBalancer   <IP_ADDRESS>    <pending>     80:31748/TCP,443:30293/TCP              4m42s

add a new port - apply the istiooperator - watch the nodeports change -> 80:30834

public-ingress     LoadBalancer   <IP_ADDRESS>    <pending>     80:30834/TCP,443:30052/TCP,15443:30516/TCP   5m5s

For comparison when the same is done to an un-managed service everything works as expected

create service

zipkin-np    LoadBalancer   <IP_ADDRESS>   <pending>     9411:32027/TCP   0s

change port name from http to http2

zipkin-np    LoadBalancer   <IP_ADDRESS>   <pending>     9411:32027/TCP   13s

Change target port

zipkin-np    LoadBalancer   <IP_ADDRESS>   <pending>     9411:32027/TCP   21s

Version (include the output of istioctl version --remote and kubectl version --short and helm version --short if you used Helm)
1.5.10+ -> 1.9.1
How was Istio installed?

istio-operator

Environment where the bug was observed (cloud vendor, OS, etc) both on Kind locally and AWS. k8s version 1.16.15 in both cases
Additionally, please consider running istioctl bug-report and attach the generated cluster-state tarball to this issue.
Refer cluster state archive for more details.

@richardwxn I thought this was fixed by using SSA?

Oh that only works on new Kubernetes - maybe that is why

Interesting , according to https://kubernetes.io/docs/reference/using-api/server-side-apply/ this is beta in 1.16 though and so , as far as I know , enabled.
Maybe i need to do something to get it ?
All my experiences with the issue are on 1.16.15 but i can try on newer version with kind.

Looks like we enable in 1.18+:
https://github.com/istio/istio/blob/cb803698c79c9b1afd8cd20db3f7e058faa86f83/operator/pkg/helmreconciler/reconciler.go#L244
On Fri, Mar 12, 2021 at 11:20 AM Francesco Ciocchetti <
@.***> wrote:

Interesting , according to
https://kubernetes.io/docs/reference/using-api/server-side-apply/ this is
beta in 1.16 though and so , as far as I know , enabled.
Maybe i need to do something to get it ?
All my experiences with the issue are on 1.16.15 but i can try on newer
version with kind.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/istio/istio/issues/31418#issuecomment-797699840, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AAEYGXN6MLTFV7JB6YM7F5TTDJSQ7ANCNFSM4ZB3E4CA
.

And i see the comment about gke
Well if we can't have it before 1.18 i Guess we can close this and for now I will hardcore a nodeport in my service definition


External requests fail, and "Problem with the SSL CA cert" when sending an HTTPS request from the istio-proxy

I installed istio and injected the sidecar into one of my services. My issue is that with the sidecar container being in place, I cannot send any requests to external services from my actual container, and I'm trying to investigate what the problem can be.
If I enter the istio-proxy container with bash, and execute curl http://example.com, then it works, but if I do curl https://example.com, then I receive
curl: (77) Problem with the SSL CA cert (path? access rights?)

Is this expected? If not, what can cause this?
The actual issue that I'm investigating is that if I'm trying to do the same curl command (curl http://example.com) in my actual application container, I get
root@myservice-6f548df4d5-v4kmj:/# curl http://example.com
curl: (7) Failed to connect to example.com port 80: Connection refused

I have already followed the guide about setting up the rule for egress traffic, and I applied the following rul:
apiVersion: config.istio.io/v1alpha2
kind: EgressRule
metadata:
  name: examplecom-egress-allow-rule
spec:
  destination:
    service: example.com
  ports:
    - port: 80
      protocol: http
    - port: 443
      protocol: https

Should external requests work properly?
It'd be great if you could give me some pointers about where to start troubleshooting this issue.

As a workaround, I think you'd want to flip it around and use
  CIDR=$(gcloud container clusters describe ${K8S_CLUSTER} ${GCP_OPTS:-} --format "value(servicesIpv4Cidr)")

and set that as IP_RANGES_INCLUDE env to only intercept cluster ips instead of all traffic

Closing this in favor of https://github.com/istio/istio/issues/4378

Hi Guys, I am facing similar issues with

error reading ca cert file /etc/ssl/certs/ca-certificates.crt (Error while reading file.)

istio-proxy@consul1-v1-688df668c9-8cs25:/$ curl --verbose https://config.somedomain.com

Rebuilt URL to: https://config.somedomain.com/
Trying <IP_ADDRESS>...
Connected to config.somedomain.com (<IP_ADDRESS>) port 443 (#0)
error reading ca cert file /etc/ssl/certs/ca-certificates.crt (Error while reading file.)
Closing connection 0
curl: (77) Problem with the SSL CA cert (path? access rights?)
istio-proxy@consul1-v1-688df668c9-8cs25:/$

config.somedomain.com is one of our internal URL.
Really appreciate If you have any inputs on this.
Kube version: v1.10.5
Istio version: 1.0


feat: support building pika_exporter docker image

feat: support building pika_exporter docker image

Can we add the build and push processes to the CI?
You can refer to

.github/workflows/publish_nightly_docker_image.yml
.github/workflows/publish_release_docker_image.yml

Can you add the build and push processes to the CI? You can refer to

.github/workflows/publish_nightly_docker_image.yml
.github/workflows/publish_release_docker_image.yml

added

please fix comment

don’t use private email the reason is ? @baerwang


Custom placeholder when loading scene asynchronously

We recently updated the iOS SDK sample app to load scene files asynchronously. When making that change we noticed that the map background is black before any of the tiles load. This doesn't occur when loading the scene file synchronously (the background is gray).
Could we update tangram to provide a gray background in all cases by default and also to allow users to designate a custom background color (or view) to display before tiles load?
Here is an updated example which highlights the issue by creating two TGMapViewController subclasses within a tab bar and sets the background to be red before the tiles finish loading.

I vote for white by default.

On Apr 10, 2017, at 15:17, Sarah Lensing<EMAIL_ADDRESS>wrote:
We recently updated the iOS SDK sample app to load scene files asynchronously. When making that change we noticed that the map background is black before any of the tiles load. This doesn't occur when loading the scene file synchronously (the background is gray).
Could we update tangram to provide a gray background in all cases by default and also to allow users to designate a custom background color (or view) to display before tiles load?
Here is an updated example which highlights the issue by creating two TGMapViewController subclasses within a tab bar and sets the background to be red before the tiles finish loading.
―
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.

That is an odd difference, I agree that it would be preferable to make the behavior more consistent.
To clarify, we're talking about the application background while the scene is loading, yes? There is already an option in the scene file to specify a background color where tiles are loading, but of course we can't apply that option before the scene is parsed and loaded.

@sarahlensing have you tried changing the background color in the interface builder?

In tangram, setting the clear color in the first GL call that happens in like so:
diff --git a/core/src/tangram.cpp b/core/src/tangram.cpp
index a9e19f0..4ed3a50 100644
--- a/core/src/tangram.cpp
+++ b/core/src/tangram.cpp
@@ -864,6 +864,8 @@ void Map::setupGL() {

     LOG("setup GL");

+    impl->renderState.clearColor(1.0, 0.0, 0.0, 1.0);
+
     impl->renderState.invalidate();

     impl->tileManager.clearTileSets();
(END)

Doesn't seem to resolve the issue, even though it would still be good to add that diff to provide a default color before the scene is loaded.

"To clarify, we're talking about the application background while the scene is loading, yes?"
@matteblair we're talking about the GLKView background while the scene is loading
@karimnaaji I tried that but it didnt have any effect. I was able to change the color with this code:
override func glkView(_ view: GLKView, drawIn rect: CGRect) {
    super.glkView(view, drawIn: rect)
    if(!loaded) {
      glClearColor(1.0, 0.0, 0.1, 1.0);
      glClear(GLbitfield(GL_COLOR_BUFFER_BIT | GL_DEPTH_BUFFER_BIT));
    }
  }

Clients could achieve this desired outcome by subclassing TGMapViewController and adding this but it seems like we might want to provide a more consistent default at the core level

Yeahhhh ok so I think I understand what's making this color. When we load a scene asynchronously, the render loop in tangram-es is running - but with an empty scene. The default background color for a scene is 0x000000 and so that's all we render.
We could try simply returning early in our drawInRect implementation if the map doesn't have a scene loaded. Ideally, that would allow any external methods of setting a background (e.g. Interface Builder) work as expected.

Another idea: if we add an interface to the tangram-es core that lets you specify a "default clear color" then our iOS platform wrapper might be able to query the background color set to the view in interface builder and pass that into the core.


cli/common: introduce a common config file

This introduces a torcx-config-v0 JSON input to specify common
torcx configuration. This is mostly useful for torcx-generator, as
it can't be passed custom command-line or environmental flags.
The config file is located by default under /etc/torcx/config.json
but can be moved somewhere else by specifying torcx_config= as a
kernel boot option.

For reference, this is coming from https://github.com/coreos/torcx/pull/37#issuecomment-298952154.

LGTM, sweet.

Single line change to resolve a simple move conflict, I'm keeping previous LGTM.


click.echo() and click.secho() failed under ipython notebook

I am using ipython notebook to run some of the terminal based code I wrote and found click.echo() and click.secho() will failed...
Any suggestion for a quick fix?
import click
click.echo('hello')

---------------------------------------------------------------------------
UnsupportedOperation                      Traceback (most recent call last)
<ipython-input-3-f575ef2d5c44> in <module>()
----> 1 click.echo('hello')

~/.virtualenvs/bernardyue.com/lib/python3.6/site-packages/click/utils.py in echo(message, file, nl, err, color)
    257
    258     if message:
--> 259         file.write(message)
    260     file.flush()
    261

UnsupportedOperation: not writable

Did you find a fix?

Any suggestions? I'm hitting the same issue.

This is a bug that was fixed in ipython. A workaround is on click master.

I'm having the same problem... I'm using Jupyter-notebook, python 3.5.
 258     if message:
 259         file.write(message)
 260     file.flush()

UnsupportedOperation: not writable

I believe this is causing issues ielsewhere:
https://github.com/enigmampc/catalyst/pull/181
https://github.com/enigmampc/catalyst/issues/261

Last "click" release according to https://github.com/pallets/click/releases was before fixing this issue
When do you plan next release with this fix so that installing with python pip will download release with this problem resolved?

In the meantime, the workaround is: pip install git+https://github.com/pallets/click. Be sure to do this in a virtualenv.


I18n key test

This should fail still requires keys to be fixed.

Also please note as mentioned earlier this is failing intentionally right now to let us know what keys need to be fixed.
I'll continue to rebase this until it's been fixed.

:+1: Not merging until you give me the :heavy_check_mark:

for #96.
Well it'll be waiting on all the french text to be added before I can merge it,

What French terms are missing?

Sorry just saw this now they get spit out during the test:
extra keys in en.json
proceduralFairnessImplementation1
proceduralFairnessImplementation2
proceduralFairnessImplementation3
proceduralFairnessImplementation4
proceduralFairnessImplementation5
proceduralFairnessImplementation6
proceduralFairnessImplementation7
proceduralFairnessImplementation8
proceduralFairnessImplementation9
proceduralFairnessImplementation10
proceduralFairnessImplementation11
proceduralFairnessImplementation12
proceduralFairnessImplementation13
proceduralFairnessImplementation14
proceduralFairnessImplementation15
proceduralFairnessImplementation16
proceduralFairnessImplementation17 extra keys in fr.json
Will probably have to rebase and run again.

OK, Will shortly look at it. Working on Thursday's workshop
Le mar. 18 juin 2019 09 h 04, Calvin Rodo<EMAIL_ADDRESS>a
écrit :

Sorry just saw this now they get spit out during the test:
extra keys in en.json
proceduralFairnessImplementation1
proceduralFairnessImplementation2
proceduralFairnessImplementation3
proceduralFairnessImplementation4
proceduralFairnessImplementation5
proceduralFairnessImplementation6
proceduralFairnessImplementation7
proceduralFairnessImplementation8
proceduralFairnessImplementation9
proceduralFairnessImplementation10
proceduralFairnessImplementation11
proceduralFairnessImplementation12
proceduralFairnessImplementation13
proceduralFairnessImplementation14
proceduralFairnessImplementation15
proceduralFairnessImplementation16
proceduralFairnessImplementation17 extra keys in fr.json
Will probably have to rebase and run again.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/canada-ca/aia-eia-js/pull/101?email_source=notifications&email_token=AAM4TZK5AFUEAE62ZRNYIJTP3DMORA5CNFSM4HPV2VP2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODX6RRLA#issuecomment-503126188,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAM4TZPCYZNEUNM43XUI3L3P3DMORANCNFSM4HPV2VPQ
.

@gcharest  Any update on this do we need to add these questions in French or can we remove them from the English?

Yes, I'll review shortly. Was scheduled this morning but got sidetracked.

Just a reminder to @gcharest or @MrDeshaies to validate the missing keys this test will be really useful for anyone adding new languages to the project since they'll be able to validate that the keys are matching.

Found the reason for the failure it was because of a bug in the coding of the fairnessImplentation strings
This PR fixes Bug #130

My view was because it's just a dev dependency it wasn't worth tracking
down how i used it. but I can do that if you want.
On Thu, Oct 10, 2019 at 12:47 PM Nick Schonning<EMAIL_ADDRESS>wrote:

@nschonni commented on this pull request.
In package.json
https://github.com/canada-ca/aia-eia-js/pull/101#discussion_r333625988:

@@ -55,6 +55,7 @@
"eslint-plugin-vue": "^5.0.0",
"jest-transform-stub": "^2.0.0",
"push-dir": "^0.4.1",

"lodash": "^4.17.11",

I forget how this package changed its deployment, but I think it might be
better to install the individual components of lodash you're using instead
of the full library. EX: lodash.isempty above in the dependencies
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/canada-ca/aia-eia-js/pull/101?email_source=notifications&email_token=AAAVNOSRLV3TYWMZNMBTD5DQN5MDPA5CNFSM4HPV2VP2YY3PNVWWK3TUL52HS4DFWFIHK3DMKJSXC5LFON2FEZLWNFSXPKTDN5WW2ZLOORPWSZGOCHSNCCI#pullrequestreview-300208393,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAAVNOW47A43XBZTOPNLCWLQN5MDPANCNFSM4HPV2VPQ
.

--
-Calvin Rodo

Looks like https://www.npmjs.com/package/lodash.intersection and https://www.npmjs.com/package/lodash.difference
I think the separate ones are a good idea since lodash has had a view security issues recently that trigger the Security Alerts on GitHub. With the standalone packages, they're less likely to be affected unless it's actually related to that component


Allow fire blocks to give updrafts

I think this would allow you to use the updraft a lot more often during casual gameplay without having to carry tons of campfires around. Being able to climb a tall ledge by using a flint and steel sounds really fun
If it seems too overpowered it could maybe be its own option in config

Yeah, makes sense.
I haven't really had the energy to work on mods in quite a bit, but when it comes back I'll probably add this

Will be in the next update, which will hopefully release in the next few days (sorry it's taken so long, my motivation drought was immediately followed by exams!)


Fix expected OpenAPI components in test_merged_components_correct

Fix expected OpenAPI components for this PR. Removed the explode element, because now explode is None by default.
PR Checklist

[x] Have you followed the guidelines in CONTRIBUTING.md?
[ ] Have you got 100% test coverage on new code?
[ ] Have you updated the prose documentation?
[ ] Have you updated the reference documentation?

can you update poetry update

I can but there is no updated
pydantic-openapi-schema. I guess this is because CI job has failed.

As I can see we have to make a new release for pydantic-openapi-schema in order to publish library to PyPi

@all-contributors add @Gamazic code


E2E setup teaching tooltip

Dev Home version
No response
Windows build number
No response
Other software
No response
Steps to reproduce the bug
Description
Open E2e Setup flow there should be a teaching tip inform the user all the changes will apply in the end of the set up flow
Expected result
No response
Actual result
No response
Included System Information
No response
Included Extensions Information
No response

Tooltip exists that says "Your changes won't be applied until the end."


Use package:vm_service instead of json_rpc_2

And generally simplify the deps of fuchsia_remote_debug_protocol. This also allows dropping web_socket_channel.
Additionally:

Drop the flutter_driver dep since it was only used for an example. If we really want to keep examples here, we should make a proper example package so that these dependencies don't leak to consumers.
Drop the flutter_test package, which not only was incorrectly listed as a direct dep, it just wasn't necessary - the test(s) were fine as package:test tests.

AFAICT, the real use of this is covered by our Fuchsia driver tests. @gw280, @blasten, or @iskakaushik can hopefully confirm that.

I'm really not quite sure why this is even separate from flutter_driver itself. I can't find any usage of it in the Fuchsia tree or internally.

I'm really not quite sure why this is even separate from flutter_driver itself. I can't find any usage of it in the Fuchsia tree or internally.

I'm working with some Fuchsia folks to verify this change doesn't break attach on Fuchsia.

I'm working with some Fuchsia folks to verify this change doesn't break attach on Fuchsia.

@chaselatta has confirmed that this still works for Fuchsia attach/tunnel use cases. Going to land this.

@chaselatta has confirmed that this still works for Fuchsia attach/tunnel use cases. Going to land this.


update setup.py

Create package file
This PR only changes the version reference to 0.1.3 and updates the documentation for the install process.
It's now been rebased on the current main branch because it was out of date.
The package has been uploaded to PyPi: https://pypi.org/project/wagtail-wordpress-import/
Ticket URL: https://projects.torchbox.com/projects/wordpress-to-wagtail-importer-package/tickets/61

Testing

[x] CI passes
[x] If necessary, tests are added for new or fixed behaviour
[x] These changes do not reduce test coverage

Documentation.

[x] This PR adds or updates documentation

Import.

[x] Tested against: https://raw.githubusercontent.com/WPTT/theme-unit-test/master/themeunittestdata.wordpress.xml with one caveat: In the xml is one page item for url https://wpthemetestdata.wordpress.com/2009/09/05/edge-case-no-title/ which has no title. Removing this fixture is required. We always expect a page title.

In future, you can use https://test.pypi.org/ for testing package installation and the use of package managers, and then you don't need to bump the version number for the public facing package on the live PyPI.


[stable/prometheus-operator]Moving out PrometheusSpec.portName from range loop to Global Scope.

Update Prometheus-operator for accepting prometheusSpec.portName to Global Scope and Chart Version
Signed-off-by: Sergio Borges<EMAIL_ADDRESS>
Is this a new chart

NOTE: We're experiencing a high volume of PRs to this repo and reviews will be delayed. Please host your own chart repository and submit your repository to the Helm Hub instead of this repo to make them discoverable to the community. Here is how to submit new chart repositories to the Helm Hub.

What this PR does / why we need it:
*Running within the range loop the variable value can't be accessed.
*Putting the portName as Global scope makes easier to have access on it.
Which issue this PR fixes
(optional, in fixes #(, fixes #<issue_number>, ...) format, will close that issue when PR gets merged)
fixes #18948
Special notes for your reviewer:
Checklist
[Place an '[x]' (no spaces) in all applicable fields. Please remove unrelated fields.]

[x] DCO signed
[x] Chart Version bumped
[x] Variables are documented in the README.md
[x] Title of the PR starts with chart name (e.g. [stable/mychartname])

/ok-to-test

/retest

This looks like the cluster can't schedule the pods, I don't see any errors related to the chart.
the same issue occurs with #20545

/retest

/retest

/retest

/lgtm
/retest

I0220 23:19:51.600]  ✖ prometheus-operator => (version: "8.9.0", path: "stable/prometheus-operator") > Chart version not ok. Needs a version bump!

/cc vsliouniaev

https://prow.k8s.io/view/gcs/kubernetes-jenkins/pr-logs/pull/helm_charts/20495/pull-charts-e2e/1230809879636086784/#1:build-log.txt%3A193

/retest

Fixed the Chart version
/cc vsliouniaev

/cc vsliouniaev

/lgtm


Deprecate the constructor that receives a ListDataProvider and caption

The constructor is TwinColGrid(ListDataProvider<T>, String caption)  is redundant and can be replaced with a call to TwinColGrid(String caption) followed by setDataProvider(ListDataProvider<T>).
In addition, my proposal for #96 requires  two new constructors
TwinColGrid(Grid<T> availableGrid, Grid<T> selectionGrid)
TwinColGrid(Supplier<Grid<T>>)

And two redundant overloads with caption (because of #97)
TwinColGrid(String caption, Grid<T> availableGrid, Grid<T> selectionGrid)
TwinColGrid(String caption, Supplier<Grid<T>>)

If instantiating TwinColGrid with a data provider is a feature we want to mantain, then #96 would require eight constructors instead of "only" four.
TwinColGrid(ListDataProvider<T>, Grid<T> availableGrid, Grid<T> selectionGrid)
TwinColGrid(ListDataProvider<T>, Supplier<Grid<T>>)
TwinColGrid(ListDataProvider<T>, String caption, Grid<T> availableGrid, Grid<T> selectionGrid)
TwinColGrid(ListDataProvider<T>, String caption, Supplier<Grid<T>>)

Therefore: deprecate TwinColGrid(ListDataProvider<T>, String caption)

Released in v2.7.0


The batch request could not be fulfilled

I randomly get the error "The batch request could not be fulfilled" with the Google Tasks API.
Any clue of what it's caused by?

The Tasks API should be working properly, if not please send product feedback to the Tasks API.


Update usage

Hi,
Is it possible to update usage in every action like copy, upload, delete etc instead only when open directory? I already tried to do so but sometimes the usage value is not correct and won't change except when open directory

Hi @benny-adiwijaya, the backend updates the storage usage on each of those commands' execution. Can you provide an example of how you are working to retrieve the storage usage?

Hi @trannamtrung1st, this is example code

Application response for upload and delete
`public class ApplicationUploadResponse : UploadResponse
{
public ApplicationUploadResponse(UploadResponse uploadResponse)
{
added = uploadResponse.added;
}
  public long usage { get; set; }
  public long quota { get; set; }

}
public class ApplicationRmResponse
{
public ApplicationRmResponse()
{
removed = new List();
}
  public List<string> removed { get; set; }
  public long usage { get; set; }
  public long quota { get; set; }

}`

Added this code in CuztomizeResponse in FilesController
else if (connectorResult.Response is UploadResponse uploadResponse)           {               connectorResult.Response = new ApplicationUploadResponse(uploadResponse)               {                   quota = quota,                   usage = storageCache.Storage               };           }           else if (connectorResult.Response is RmResponse rmResponse)           {               connectorResult.Response = new ApplicationRmResponse()               {                   removed = rmResponse.removed,                   quota = quota,                   usage = storageCache.Storage               };           }

-And for javascript I added this
`elf.bind('upload', function (e, fm) {
fm.getUI().data('_quota', e.data.quota);
fm.getUI().data('_usage', e.data.usage);
elfinderSetVolumeSize();
});
        elf.bind('rm', function (e, fm) {
            fm.getUI().data('_quota', e.data.quota);
            fm.getUI().data('_usage', e.data.usage);
            elfinderSetVolumeSize();
        });`

When delete files, sometimes usage not updated

It's on purpose since I think 'delete' is not too important to be necessary to update storage instantly. So I decided to let a background worker do the calculation after the deletion, and it may run after you retrieving the usage. The instant update can affect the performance.
However, I think I will enable an option to decide whether to use it or not.

Hi @benny-adiwijaya, I just updated the plugin to 1.2.5. Nothing changes, but it works as your expectation now.

yes, it works now.. thank you 👍