Warning - Instances information unavailable

Hi, I am using Diego v0.1460.0 witch CF v233, stemcell v3215 on AWS.
After pushing docker image (cloudfoundry/lattice-app), when executing:
cf restart lattice-app

I have following warning (several times):
Could not fetch instance count: Server error, status code: 503, error code: 220002, message: Instances information unavailable: getaddrinfo: No address associated with hostname

App is working, but from time to time it turns down and starts again.
Have you any idea what can be wrong?

Hmm... It looks rather like CF CLI issue...
Using veritas to monitor this app for over 20 minutes and it's working non stop.
When execute 'cf apps' there are above errors.
If no one has different ideas, issue can be closed...

Hi, @pako-grape,
If you're getting errors from Cloud Controller with getaddrinfo in the error message, it likely means that Cloud Controller is unable to resolve the CC-Bridge components via consul DNS. If this issue is ongoing, do you have any failing jobs in the deployment? The output from bosh instances --ps would be particularly useful. Could you also provide logs from the consul-agent jobs on the VMs that host CC and the CC-Bridge components? Those logs are located at /var/vcap/sys/log/consul_agent/consul_agent.stdout.log.
Thanks,
Eric, CF Runtime Diego PM

@ematpl Thanks for reply.
'bosh instances --ps' on cf deployment:
+----------------------------------------------------------------------------+---------+-----+-----------+-------------+
| Instance                                                                   | State   | AZ  | VM Type   | IPs         |
+----------------------------------------------------------------------------+---------+-----+-----------+-------------+
| api_z1/0 (6c1572dd-2ebf-486c-af55-e29347fe9e15)*                           | running | n/a | small_z1  | <IP_ADDRESS>   |
|   cloud_controller_ng                                                      | running |     |           |             |
|   cloud_controller_worker_local_1                                          | running |     |           |             |
|   cloud_controller_worker_local_2                                          | running |     |           |             |
|   nginx_cc                                                                 | running |     |           |             |
|   cloud_controller_migration                                               | running |     |           |             |
|   cloud_controller_worker_1                                                | running |     |           |             |
|   cloud_controller_clock                                                   | running |     |           |             |
|   metron_agent                                                             | running |     |           |             |
|   route_registrar                                                          | running |     |           |             |
|   consul_agent                                                             | running |     |           |             |
+----------------------------------------------------------------------------+---------+-----+-----------+-------------+
| blobstore_z1/0 (6ed731ef-4d92-45e8-8c89-76667ee33deb)*                     | running | n/a | small_z1  | <IP_ADDRESS>   |
|   blobstore_nginx                                                          | running |     |           |             |
|   blobstore_url_signer                                                     | running |     |           |             |
|   metron_agent                                                             | running |     |           |             |
|   route_registrar                                                          | running |     |           |             |
|   consul_agent                                                             | running |     |           |             |
+----------------------------------------------------------------------------+---------+-----+-----------+-------------+
| consul_z1/0 (7a23ea0c-5a29-45ee-9c86-c77dd2397e0c)*                        | running | n/a | small_z1  | <IP_ADDRESS> |
|   metron_agent                                                             | running |     |           |             |
|   consul_agent                                                             | running |     |           |             |
+----------------------------------------------------------------------------+---------+-----+-----------+-------------+
| doppler_z1/0 (186488de-808d-4375-abce-04609bd68a0a)*                       | running | n/a | small_z1  | <IP_ADDRESS>   |
|   doppler                                                                  | running |     |           |             |
+----------------------------------------------------------------------------+---------+-----+-----------+-------------+
| etcd_z1/0 (d1f8fd9f-aa33-4035-a8a6-4b062e96b168)*                          | running | n/a | small_z1  | <IP_ADDRESS> |
|   etcd                                                                     | running |     |           |             |
|   etcd_metrics_server                                                      | running |     |           |             |
|   metron_agent                                                             | running |     |           |             |
+----------------------------------------------------------------------------+---------+-----+-----------+-------------+
| ha_proxy_z1/0 (b35645c9-160e-43c7-a851-625f97f34129)*                      | running | n/a | small_z1  | ########### |
|                                                                            |         |     |           | <IP_ADDRESS>  |
|   haproxy                                                                  | running |     |           |             |
|   metron_agent                                                             | running |     |           |             |
+----------------------------------------------------------------------------+---------+-----+-----------+-------------+
| hm9000_z1/0 (946ad92a-6a18-486d-99c1-95125bf87ee6)*                        | running | n/a | small_z1  | <IP_ADDRESS>   |
|   consul_agent                                                             | running |     |           |             |
|   hm9000_listener                                                          | running |     |           |             |
|   hm9000_fetcher                                                           | running |     |           |             |
|   hm9000_analyzer                                                          | running |     |           |             |
|   hm9000_sender                                                            | running |     |           |             |
|   hm9000_api_server                                                        | running |     |           |             |
|   hm9000_evacuator                                                         | running |     |           |             |
|   hm9000_shredder                                                          | running |     |           |             |
|   metron_agent                                                             | running |     |           |             |
|   route_registrar                                                          | running |     |           |             |
+----------------------------------------------------------------------------+---------+-----+-----------+-------------+
| loggregator_trafficcontroller_z1/0 (348c5956-41ea-41fc-b5c8-9638aed9bb91)* | running | n/a | small_z1  | <IP_ADDRESS>   |
|   loggregator_trafficcontroller                                            | running |     |           |             |
|   metron_agent                                                             | running |     |           |             |
|   route_registrar                                                          | running |     |           |             |
+----------------------------------------------------------------------------+---------+-----+-----------+-------------+
| nats_z1/0 (db2895e7-96ec-44b6-8bfb-17f4852d9549)*                          | running | n/a | small_z1  | <IP_ADDRESS> |
|   nats                                                                     | running |     |           |             |
|   nats_stream_forwarder                                                    | running |     |           |             |
|   metron_agent                                                             | running |     |           |             |
+----------------------------------------------------------------------------+---------+-----+-----------+-------------+
| postgres_z1/0 (3c1f7f70-51d1-4d0d-865f-bcc3f86caeb0)*                      | running | n/a | small_z1  | <IP_ADDRESS> |
|   postgres                                                                 | running |     |           |             |
|   metron_agent                                                             | running |     |           |             |
+----------------------------------------------------------------------------+---------+-----+-----------+-------------+
| router_z1/0 (31c06994-10de-4021-9ffb-ee52fbce28f4)*                        | running | n/a | small_z1  | <IP_ADDRESS> |
|   gorouter                                                                 | running |     |           |             |
|   metron_agent                                                             | running |     |           |             |
|   consul_agent                                                             | running |     |           |             |
+----------------------------------------------------------------------------+---------+-----+-----------+-------------+
| runner_z1/0 (910ca2ef-203c-409e-b43e-ff714383fd08)*                        | running | n/a | runner_z1 | <IP_ADDRESS>  |
|   consul_agent                                                             | running |     |           |             |
|   warden                                                                   | running |     |           |             |
|   dea_next                                                                 | running |     |           |             |
|   dir_server                                                               | running |     |           |             |
|   dea_logging_agent                                                        | running |     |           |             |
|   metron_agent                                                             | running |     |           |             |
+----------------------------------------------------------------------------+---------+-----+-----------+-------------+
| uaa_z1/0 (0179dd90-3b9d-4452-b24e-5f29e3e8bb01)*                           | running | n/a | small_z1  | <IP_ADDRESS>   |
|   uaa                                                                      | running |     |           |             |
|   metron_agent                                                             | running |     |           |             |
|   route_registrar                                                          | running |     |           |             |
+----------------------------------------------------------------------------+---------+-----+-----------+-------------+

on diego deployment:
+------------------------------------------------------------+---------+-----+------------------+-----------+
| Instance                                                   | State   | AZ  | VM Type          | IPs       |
+------------------------------------------------------------+---------+-----+------------------+-----------+
| access_z1/0 (3395cbf4-884c-4c11-ac22-9752a36c8c33)*        | running | n/a | access_z1        | <IP_ADDRESS> |
|   consul_agent                                             | running |     |                  |           |
|   ssh_proxy                                                | running |     |                  |           |
|   metron_agent                                             | running |     |                  |           |
|   file_server                                              | running |     |                  |           |
+------------------------------------------------------------+---------+-----+------------------+-----------+
| brain_z1/0 (d771578c-f881-4742-9ef5-a0d734d306ae)*         | running | n/a | brain_z1         | <IP_ADDRESS> |
|   consul_agent                                             | running |     |                  |           |
|   auctioneer                                               | running |     |                  |           |
|   converger                                                | running |     |                  |           |
|   metron_agent                                             | running |     |                  |           |
+------------------------------------------------------------+---------+-----+------------------+-----------+
| cc_bridge_z1/0 (7fdfbbfe-d7d0-481f-85e7-0559bc2d6a02)*     | running | n/a | cc_bridge_z1     | <IP_ADDRESS> |
|   consul_agent                                             | running |     |                  |           |
|   stager                                                   | running |     |                  |           |
|   nsync_listener                                           | running |     |                  |           |
|   nsync_bulker                                             | running |     |                  |           |
|   tps_listener                                             | running |     |                  |           |
|   tps_watcher                                              | running |     |                  |           |
|   cc_uploader                                              | running |     |                  |           |
|   metron_agent                                             | running |     |                  |           |
+------------------------------------------------------------+---------+-----+------------------+-----------+
| cell_z1/0 (201df1fc-3ba6-444f-872c-c712c127027c)*          | running | n/a | cell_z1          | <IP_ADDRESS> |
|   consul_agent                                             | running |     |                  |           |
|   rep                                                      | running |     |                  |           |
|   garden                                                   | running |     |                  |           |
|   metron_agent                                             | running |     |                  |           |
+------------------------------------------------------------+---------+-----+------------------+-----------+
| database_z1/0 (67c516b3-3543-4d0a-9907-43cc46604d2d)*      | running | n/a | database_z1      | <IP_ADDRESS> |
|   consul_agent                                             | running |     |                  |           |
|   etcd                                                     | running |     |                  |           |
|   bbs                                                      | running |     |                  |           |
|   metron_agent                                             | running |     |                  |           |
+------------------------------------------------------------+---------+-----+------------------+-----------+
| route_emitter_z1/0 (651c18d2-c18e-4339-a153-14599f80f611)* | running | n/a | route_emitter_z1 | <IP_ADDRESS> |
|   consul_agent                                             | running |     |                  |           |
|   route_emitter                                            | running |     |                  |           |
|   metron_agent                                             | running |     |                  |           |
+------------------------------------------------------------+---------+-----+------------------+-----------+

logs from CC:
==> Starting Consul agent...
==> Starting Consul agent RPC...
==> Consul agent running!
          Synced with 1 initial agents
    2016/04/08 05:17:33 [INFO] agent: Synced service 'cloud-controller-ng'
{"timestamp":"1460092654.212332964","source":"confab","message":"confab.agent-client.verify-joined.members.request","log_level":1,"data":{"wan":false}}
{"timestamp":"1460092654.214618683","source":"confab","message":"confab.agent-client.verify-joined.members.response","log_level":1,"data":{"members":["<IP_ADDRESS>","<IP_ADDRESS>","<IP_ADDRESS>","<IP_ADDRESS>","<IP_ADDRESS>","<IP_ADDRESS>","<IP_ADDRESS>","<IP_ADDRESS>","<IP_ADDRESS>","<IP_ADDRESS>","<IP_ADDRESS>","<IP_ADDRESS>"],"wan":false}}
{"timestamp":"1460092654.214711666","source":"confab","message":"confab.agent-client.verify-joined.members.joined","log_level":1,"data":{}}
{"timestamp":"1460092654.214767694","source":"confab","message":"confab.controller.boot-agent.success","log_level":1,"data":{}}
{"timestamp":"1460092654.214818478","source":"confab","message":"confab.agent-runner.run.write-pidfile","log_level":1,"data":{"path":"/var/vcap/sys/run/consul_agent/consul_agent.pid","pid":4994}}
    2016/04/08 05:17:34 [INFO] agent: Synced check 'service:cloud-controller-ng'
    2016/04/08 05:17:37 [WARN] agent: Check 'service:cloud-controller-ng' is now critical
    2016/04/08 05:17:37 [INFO] agent: Synced check 'service:cloud-controller-ng'
    2016/04/08 05:17:40 [WARN] agent: Check 'service:cloud-controller-ng' is now critical
    2016/04/08 05:17:43 [WARN] agent: Check 'service:cloud-controller-ng' is now critical
    2016/04/08 05:17:46 [WARN] agent: Check 'service:cloud-controller-ng' is now critical
    2016/04/08 05:17:49 [INFO] agent: Synced check 'service:cloud-controller-ng'
    2016/04/08 05:18:32 [INFO] serf: EventMemberLeave: runner-z1-0 <IP_ADDRESS>
    2016/04/08 05:18:39 [INFO] serf: EventMemberJoin: runner-z1-0 <IP_ADDRESS>
    2016/04/08 05:19:46 [INFO] serf: EventMemberLeave: database-z1-0 <IP_ADDRESS>
    2016/04/08 05:20:03 [INFO] serf: EventMemberLeave: brain-z1-0 <IP_ADDRESS>
    2016/04/08 05:20:11 [INFO] serf: EventMemberJoin: brain-z1-0 <IP_ADDRESS>
    2016/04/08 05:20:14 [INFO] serf: EventMemberJoin: database-z1-0 <IP_ADDRESS>
    2016/04/08 05:20:22 [INFO] serf: EventMemberLeave: cc-bridge-z1-0 <IP_ADDRESS>
    2016/04/08 05:20:22 [INFO] serf: EventMemberLeave: access-z1-0 <IP_ADDRESS>
    2016/04/08 05:20:23 [INFO] serf: EventMemberLeave: route-emitter-z1-0 <IP_ADDRESS>
    2016/04/08 05:20:28 [INFO] serf: EventMemberJoin: route-emitter-z1-0 <IP_ADDRESS>
    2016/04/08 05:20:28 [INFO] serf: EventMemberLeave: cell-z1-0 <IP_ADDRESS>
    2016/04/08 05:20:29 [INFO] serf: EventMemberJoin: access-z1-0 <IP_ADDRESS>
    2016/04/08 05:20:34 [INFO] serf: EventMemberJoin: cc-bridge-z1-0 <IP_ADDRESS>
    2016/04/08 05:20:41 [INFO] serf: EventMemberJoin: cell-z1-0 <IP_ADDRESS>
    2016/04/08 05:36:11 [WARN] dns: node 'cc-bridge-z1-0' failing health check 'service:nsync: Service 'nsync' check', dropping from service 'nsync'
    2016/04/08 05:36:11 [WARN] dns: node 'cc-bridge-z1-0' failing health check 'service:nsync: Service 'nsync' check', dropping from service 'nsync'
    2016/04/08 05:36:11 [WARN] dns: node 'cc-bridge-z1-0' failing health check 'service:nsync: Service 'nsync' check', dropping from service 'nsync'
    2016/04/08 05:36:11 [WARN] dns: node 'cc-bridge-z1-0' failing health check 'service:nsync: Service 'nsync' check', dropping from service 'nsync'
    2016/04/08 05:36:11 [WARN] dns: node 'cc-bridge-z1-0' failing health check 'service:nsync: Service 'nsync' check', dropping from service 'nsync'
    2016/04/08 05:36:11 [WARN] dns: node 'cc-bridge-z1-0' failing health check 'service:nsync: Service 'nsync' check', dropping from service 'nsync'
    2016/04/08 05:36:49 [WARN] dns: node 'cc-bridge-z1-0' failing health check 'service:stager: Service 'stager' check', dropping from service 'stager'
    2016/04/08 05:36:49 [WARN] dns: node 'cc-bridge-z1-0' failing health check 'service:stager: Service 'stager' check', dropping from service 'stager'
    2016/04/08 05:36:53 [WARN] dns: node 'cc-bridge-z1-0' failing health check 'service:nsync: Service 'nsync' check', dropping from service 'nsync'
    2016/04/08 05:36:53 [WARN] dns: node 'cc-bridge-z1-0' failing health check 'service:nsync: Service 'nsync' check', dropping from service 'nsync'
    2016/04/08 05:36:54 [WARN] dns: node 'cc-bridge-z1-0' failing health check 'service:nsync: Service 'nsync' check', dropping from service 'nsync'
    2016/04/08 05:36:54 [WARN] dns: node 'cc-bridge-z1-0' failing health check 'service:nsync: Service 'nsync' check', dropping from service 'nsync'
    2016/04/08 05:36:54 [WARN] dns: node 'cc-bridge-z1-0' failing health check 'service:nsync: Service 'nsync' check', dropping from service 'nsync'
    2016/04/08 05:36:54 [WARN] dns: node 'cc-bridge-z1-0' failing health check 'service:nsync: Service 'nsync' check', dropping from service 'nsync'

logs from CC-Bridge (content is repeated many times):
    2016/04/08 05:38:29 [WARN] agent: Check 'service:nsync' is now critical
    2016/04/08 05:38:29 [INFO] agent: Synced check 'service:nsync'
    2016/04/08 05:38:30 [WARN] agent: Check 'service:stager' is now critical
    2016/04/08 05:38:30 [INFO] agent: Synced check 'service:stager'
    2016/04/08 05:38:31 [INFO] agent: Synced check 'service:nsync'
    2016/04/08 05:38:31 [WARN] agent: Check 'service:cc-uploader' is now critical
    2016/04/08 05:38:31 [INFO] agent: Synced check 'service:cc-uploader'
    2016/04/08 05:38:32 [INFO] agent: Synced check 'service:stager'
    2016/04/08 05:38:32 [INFO] agent: Synced check 'service:cc-uploader'
    2016/04/08 05:38:32 [WARN] agent: Check 'service:tps' is now critical
    2016/04/08 05:38:32 [INFO] agent: Synced check 'service:tps'
    2016/04/08 05:38:32 [INFO] agent: Synced check 'service:tps'

Hi @pako-grape,
It looks like bosh thinks all of your bridge jobs are operating, but consul doesn't agree. Is it possible that your bridge processes are flapping? If you could bosh ssh into that bridge VM, and watch -n0.5 monit summary for a bit, I'd be curious to see if all the processes are always up.
Additionally, do the TPS or nsync jobs have obvious error log lines?

Also, diego-release v0.1490.0 is not a release as of yet. Our last release (yesterday) was v0.1464.0

I suspect that's supposed to be 0.1460.0, based on https://github.com/cloudfoundry/cf-release/releases/tag/v233#recommended-diego-release-version.

In fact diego release is v0.1460.0. Sorry for this typo.
After over 3 minutes with 'watch -n0.5 monit summary' it seems that all jobs are running non stop.
Logs from TPS listener:
{"timestamp":"1460178373.272938728","source":"tps-listener","message":"tps-listener.exited-with-failure","log_level":2,"data":{"error":"Exit trace for group:\nregistration-runner exited with error: Put http://<IP_ADDRESS>:8500/v1/agent/service/deregister/: dial tcp <IP_ADDRESS>:8500: getsockopt: connection refused\napi exited with nil\ndebug-server exited with nil\n"}}
{"timestamp":"1460178385.528144360","source":"tps-listener","message":"tps-listener.registration-runner.starting","log_level":1,"data":{"registration":{"Name":"tps","Port":1518,"Check":{"TTL":"3s"},"Checks":null},"service":"tps","session":"1"}}
{"timestamp":"1460178385.528466463","source":"tps-listener","message":"tps-listener.registration-runner.attempting-registering-service","log_level":1,"data":{"service":"tps","session":"1"}}
{"timestamp":"1460178385.539237261","source":"tps-listener","message":"tps-listener.registration-runner.succeeded-registering-service","log_level":1,"data":{"service":"tps","session":"1"}}
{"timestamp":"1460178385.547142506","source":"tps-listener","message":"tps-listener.registration-runner.poll-until-signaled.started","log_level":1,"data":{"service":"tps","session":"1.1","update-interval":"1.5s"}}
{"timestamp":"1460178385.547278881","source":"tps-listener","message":"tps-listener.started","log_level":1,"data":{}}
{"timestamp":"1460179059.668472052","source":"tps-listener","message":"tps-listener.registration-runner.poll-until-signaled.deregistering-service","log_level":1,"data":{"service":"tps","session":"1.1","update-interval":"1.5s"}}
{"timestamp":"1460179059.668750763","source":"tps-listener","message":"tps-listener.registration-runner.poll-until-signaled.finished","log_level":1,"data":{"service":"tps","session":"1.1","update-interval":"1.5s"}}
{"timestamp":"1460179059.668825150","source":"tps-listener","message":"tps-listener.registration-runner.finished","log_level":1,"data":{"service":"tps","session":"1"}}
{"timestamp":"1460179059.668975353","source":"tps-listener","message":"tps-listener.exited-with-failure","log_level":2,"data":{"error":"Exit trace for group:\nregistration-runner exited with error: Put http://<IP_ADDRESS>:8500/v1/agent/service/deregister/: dial tcp <IP_ADDRESS>:8500: connection refused\napi exited with nil\ndebug-server exited with nil\n"}}
{"timestamp":"1460179072.479903460","source":"tps-listener","message":"tps-listener.registration-runner.starting","log_level":1,"data":{"registration":{"Name":"tps","Port":1518,"Check":{"TTL":"3s"},"Checks":null},"service":"tps","session":"1"}}
{"timestamp":"1460179072.480226755","source":"tps-listener","message":"tps-listener.registration-runner.attempting-registering-service","log_level":1,"data":{"service":"tps","session":"1"}}
{"timestamp":"1460179072.487333298","source":"tps-listener","message":"tps-listener.registration-runner.succeeded-registering-service","log_level":1,"data":{"service":"tps","session":"1"}}
{"timestamp":"1460179072.500604868","source":"tps-listener","message":"tps-listener.registration-runner.poll-until-signaled.started","log_level":1,"data":{"service":"tps","session":"1.1","update-interval":"1.5s"}}
{"timestamp":"1460179072.500660181","source":"tps-listener","message":"tps-listener.started","log_level":1,"data":{}}

Logs from TPS watcher:
{"timestamp":"1460178386.370812654","source":"tps-watcher","message":"tps-watcher.watcher.starting","log_level":1,"data":{"session":"2"}}
{"timestamp":"1460178386.371064425","source":"tps-watcher","message":"tps-watcher.watcher.started","log_level":1,"data":{"session":"2"}}
{"timestamp":"1460178386.371150255","source":"tps-watcher","message":"tps-watcher.watcher.subscribing-to-events","log_level":1,"data":{"session":"2"}}
{"timestamp":"1460178386.371956587","source":"tps-watcher","message":"tps-watcher.started","log_level":1,"data":{}}
{"timestamp":"1460178386.405641079","source":"tps-watcher","message":"tps-watcher.watcher.subscribed-to-events","log_level":1,"data":{"session":"2"}}
{"timestamp":"1460179005.702743053","source":"tps-watcher","message":"tps-watcher.watcher.failed-getting-next-event","log_level":2,"data":{"error":"EOF","session":"2"}}
{"timestamp":"1460179006.703215837","source":"tps-watcher","message":"tps-watcher.watcher.failed-getting-next-event","log_level":2,"data":{"error":"EOF","session":"2"}}
{"timestamp":"1460179007.703614712","source":"tps-watcher","message":"tps-watcher.watcher.failed-getting-next-event","log_level":2,"data":{"error":"EOF","session":"2"}}
{"timestamp":"1460179008.703970909","source":"tps-watcher","message":"tps-watcher.watcher.subscribing-to-events","log_level":1,"data":{"session":"2"}}
{"timestamp":"1460179020.357481718","source":"tps-watcher","message":"tps-watcher.watcher.subscribed-to-events","log_level":1,"data":{"session":"2"}}
{"timestamp":"1460179057.240381718","source":"tps-watcher","message":"tps-watcher.lock.lost-lock","log_level":1,"data":{"err":"Lost lock 'v1/locks/tps_watcher_lock'","key":"v1/locks/tps_watcher_lock","session":"1","value":"7e21aa50-f1aa-4ce9-61b9-e99e0a22d04c"}}
{"timestamp":"1460179057.240549326","source":"tps-watcher","message":"tps-watcher.lock.done","log_level":1,"data":{"key":"v1/locks/tps_watcher_lock","session":"1","value":"7e21aa50-f1aa-4ce9-61b9-e99e0a22d04c"}}
{"timestamp":"1460179057.240639210","source":"tps-watcher","message":"tps-watcher.watcher.stopping","log_level":1,"data":{"session":"2"}}
{"timestamp":"1460179057.240725040","source":"tps-watcher","message":"tps-watcher.watcher.finished","log_level":1,"data":{"session":"2"}}
{"timestamp":"1460179057.240951061","source":"tps-watcher","message":"tps-watcher.exited-with-failure","log_level":2,"data":{"error":"Exit trace for group:\nlock-maintainer exited with error: lock lost\nwatcher exited with nil\ndebug-server exited with nil\n"}}
{"timestamp":"1460179073.473150969","source":"tps-watcher","message":"tps-watcher.lock.starting","log_level":1,"data":{"key":"v1/locks/tps_watcher_lock","session":"1","value":"0e60f21a-2d16-48fd-678b-0dd53a9d00e4"}}
{"timestamp":"1460179073.473260880","source":"tps-watcher","message":"tps-watcher.lock.acquiring-lock","log_level":1,"data":{"key":"v1/locks/tps_watcher_lock","session":"1","value":"0e60f21a-2d16-48fd-678b-0dd53a9d00e4"}}
{"timestamp":"1460179073.496469975","source":"tps-watcher","message":"tps-watcher.lock.acquire-lock-succeeded","log_level":1,"data":{"key":"v1/locks/tps_watcher_lock","session":"1","value":"0e60f21a-2d16-48fd-678b-0dd53a9d00e4"}}
{"timestamp":"1460179073.496716738","source":"tps-watcher","message":"tps-watcher.lock.started","log_level":1,"data":{"key":"v1/locks/tps_watcher_lock","session":"1","value":"0e60f21a-2d16-48fd-678b-0dd53a9d00e4"}}

Hi @pako-grape,
Is there any way you could give us the contents of the monit log file in /var/vcap/monit/monit.log? This should give us a better idea of the lifecycle of processes on the cc_bridge VM.
Also from the above logs, we see that both the TPS listener and the TPS watcher exited. Was this a recurring failure? Or did this only happen once during the deploy? Also we notice that there were no logs after the started log line, was the CF installation under almost no load during the above investigation?
Thanks,
@jfmyers9 && @andrew-edgar, CF Diego Team

Hi @pako-grape, we were looking at https://github.com/cloudfoundry/cf-release/issues/926 over the weekend and your issue seems vaguely similar.
Did you generate your manifest with the scripts/generate-deployment-manifest script provided with v0.1460.0? Some older versions of diego-release manifest generation use manifest-based configuration for consul registration and that can cause service registration to fail.
You can also check to see if something like the following block exists in your manifest. If so, removing it may get you past the problem:
-    consul:
 -      agent:
 -        services:
 -          bbs: {}
 -          etcd: {}
 -          auctioneer: {}
 -          cc_uploader: {}
 -          nsync: {}
 -          stager: {}
 -          tps: {}
 -          file_server: {}
 -          ssh_proxy: {}

If this doesn't address your problem, please paste the content of your manifest here (with credentials REDACTED), and we can have a closer look.

Thank you very much!
@cwlbraa - that's it. I'am almost 100% sure.
I will check this out next week but issue can be closed.
I still cannot believe that this was such a breeze...
Thanks a lot for your help and time.

Thanks, @pako-grape! Glad to hear that's probably the issue. If it turns out to be something else, please let us know, and we'll be happy to assist again.
Best,
Eric


What's the meaning of valsegm_map_0?

Hello,
What does valsegm_map_0 mean because it doesn't seem like it's a map50:95? Is there a mistake in my understanding?
Because I looked at the log, the values output by it and the COCOAPI were not the same.

map50:95


moco: work around "too many open files" by slurping the data (#2149)

We're just replacing use of mmap'able .nii files by .nii.gz files, which need to be read entirely, which reduces the number of open files. Obviously now the bottleneck becomes RAM.

A proper solution still uses mmap()'ed data, so the data is accessed on-demand and the computer RAM is not a limitation.
The moco functions are splitting an input 4D file in 3D files, but it's not necessary to do so, the 3D files could still be looked up from the original data.


BI-ZMA timetable

I am not able to view timetable for BI-ZMA course (https://timetable.fit.cvut.cz/courses/BI-ZMA). The widget just keeps loading forever...

This is probably the same mysterious problem as in #94.


Cannot access Grid as a ref

Grid is declared as a functional component, so c is null in the below example.
<Grid ref={c => this.myRef = c} />

More info:
https://facebook.github.io/react/docs/refs-and-the-dom.html#refs-and-functional-components

would you be able to use gridHoc instead for that? that would give you access to the underlying ref

This can be accomplished with a one-liner:
const GridWithRef = GridHoc(props => <div {...props} ref={props.innerRef} />)
then accessed with:
<GridWithRef innerRef={ref => console.log(ref) /> // ref to div

Cool that works, thanks!


No Option for Profile Pic Change

There should be an option to change the profile pic
Screenshots:

I'll be working on it. @therajanmaurya


Definition context suggestions don't work in reviews

Consider someone opening a pull request that changes this code:
(define (foo x)
  (displayln "foo")
  (* x 2))

Into this code:
(define (foo x)
  (displayln "foo")
  (let ([y (* x 2)])
    (* y 3)))

The current analysis logic and github pull request review integration will see that only the last two lines are changed, and limit the syntax objects Resyntax analyzes to only the fully enclosed syntax objects within those lines. But since #294 was implemented, definition context rules are capable of analyzing the surrounding syntax object while narrowing their suggested replacement to just the changed parts of the context. Concretely, the let-to-define rule is perfectly capable of making a suggestion whose string replacement only touches the last two lines above. That should be turned into a review comment on the pull request, but currently it's not. The resyntax analyze CLI handles this correctly so this should be easy to fix. The only changes needed are to:

Make sure the github pull request review comments generated by Resyntax use the line range defined by the string replacement, not the line range of the original syntax object.
Adjust the code in resyntax/private/source.rkt that filters which syntax objects are analyzed. It should analyze any syntax object that overlaps the requested file ranges, not just those that are enclosed by the file ranges.
Tweak the logic in Resyntax for applying refactoring suggestions to filter out suggestions whose string replacement (and not their syntax replacement) is not fully enclosed by the requested file ranges.

This should make the Resyntax pull request reviewer a lot more useful. Today, it discards so many suggestions that it's not useful.

Nope still busted, jackfirth/racket-disposable#134 isn't producing the expected review comment and I've verified it used the most recent version of Resyntax.

Okay I fixed it! The cause was source-analyze not adding scopes from syntax objects outside the analyzed line range.


Setting enforce_access_policies to false doesn't work inside functions

Functions are precompiled, so setting enforce_access_policies to false doesn't affect their behavior at all.
Fixing this is not too hard: functions already take an extra json argument that encodes global variables, and we can just put the value of enforce_access_policies in it, and check that when evaluating access policies inside the function

I was wondering if this flag to ignore access policies for a particular function will be exposed for schema use too.  I've been wanting to extract portions of my access policies into functions but this is complicated or made impossible by the functions themselves respecting access policies.
A contrived example:
function complex_check(obj: A) -> bool {
    using (...);
}

type A {
    link parent -> A;
    link sibling -> A;

    access policy complicated_policy
        allow all using (
            complex_check(.parent) and complex_check(.sibling);
        );
}

Is there some way to achieve the above or am I missing an easier option?

@zerosym that's a good point. I'll think about it.
One simple option might be for us to expose the "current function" as a built-in global, and then you can use that in policies to "bless" certain functions. We'd probably want to do a bit of special casing to optimize, maybe?
I don't know.
I now realize though that using functions in insert/update constraints is perilous: newly inserted/updated data is not visible to functions.


Add support for full text search (FTS 3,4,5)

It would be nice to detect FTS tables and do special things with them. I.e. also omit FTS backing tables from Lighter schemas (they need to be included in schemas if DB recreation is on, but no regular Swift funcs etc should be emitted for them?).
Table Detection
The tables can be detected by looking at the SQL in the metadata:
CREATE VIRTUAL TABLE papers USING fts3(...)

i.e. "VIRTUAL TABLE" and "USING fts*".
FTS tables, even contentful, have no associated column types (though they should be all TEXT?).
FTS creates a set of supporting, regular, tables that should be omitted, FTS 3:
papers_content
papers_segments
papers_segdir

FTS 4:
papers4_content
papers4_segments
papers4_segdir
papers4_docsize
papers4_stat

FTS 5:
email_data
email_idx
email_content
email_docsize
email_config

So first the FTS table needs to be detected, then the associated tables need to be tagged/excluded.
External content FTS tables can refer to a backing table ("documents" in this case):
USING fts5(title, value, content='documents')

So that can be detected too (i.e. whether a regular table has one (or more! e.g. for multiple languages) FTS backing tables).
Operations
It is unclear what kind of operations would need to be supported? Everything in FTS centers around MATCH queries, like:
SELECT * FROM mail WHERE body MATCH 'sqlite';

Note that FTS table columns are completely untyped (but except for rowid always TEXT?)
The rowid is also more important to match up w/ the content table and needs to be exposed? (e.g. it can be aliased to an integer primary key and is also stable between VACUUMs).
Then FTS also has a set of special functions, like highlight and snippet:
SELECT highlight(email, 2, '<b>', '</b>') FROM email WHERE email MATCH 'fts5';

2 is the 0 based column index here ("email" is the FTS table). Also note that the table can be used on the left side of the match.
If an FTS table has a backing table (content='mytable'), maybe the ops should be directly attached to the content table, like sqlite_mytable_fts(...).
FTS 5 query language:
<phrase>    := string [*]
<phrase>    := <phrase> + <phrase>
<neargroup> := NEAR ( <phrase> <phrase> ... [, N] )
<query>     := [ [-] <colspec> :] [^] <phrase>
<query>     := [ [-] <colspec> :] <neargroup>
<query>     := [ [-] <colspec> :] ( <query> )
<query>     := <query> AND <query>
<query>     := <query> OR <query>
<query>     := <query> NOT <query>
<colspec>   := colname
<colspec>   := { colname1 colname2 ... }

Ordering has a special rank column (ORDER BY rank), that would need to be made available.

https://www.sqlite.org/fts3.html
https://www.sqlite.org/fts5.html

does FTS5 work with Lighter and your suggestions are improvements on top of basic functionality?

Specific FTS support is not implemented yet, otherwise the issue would not be open :-) But a plan is outlined above.

Thanks it read as if these were enhancements but that FTS could still be used via raw SQL

Oh yes, you should still be able to use FTS using raw SQLite. But you get no extra support beyond that.
Lighter should at least filter out the FTS tables from the generation, as they are really different to regular SQL tables and the generated code isn't helpful.
It's not a huge amount of work to get this in, but I didn't get to it yet.


Update Grant-CsTeamsUpgradePolicy.md

Fixes syntax block.

:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

skype/skype-ps/skype/Grant-CsTeamsUpgradePolicy.md
:white_check_mark:Succeeded
View (skype-ps)

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


cmake: libc: minimal: Move sources from 'app' to a new CMake library

The minimal libc source files have been added to 'app'. The Zephyr
build system should not be adding source files to the 'app' library
unless necessary.
This patch creates a new Zephyr CMake Library in lib/libc/minimal and
adds the sources to it.
This resolves #8206
Signed-off-by: Sebastian Bøe<EMAIL_ADDRESS>

NB: Should not be merged during the release cycle as this is a refactoring, not a bugfix.

Codecov Report

Merging #8241 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master    #8241   +/-   ##
=======================================
  Coverage   64.53%   64.53%
=======================================
  Files         420      420
  Lines       40109    40109
  Branches     6762     6762
=======================================
  Hits        25884    25884
  Misses      11108    11108
  Partials     3117     3117

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 fd561dd...c4decc4. Read the comment docs.


Join verifications in batch async/await verification

@marcio-diaz reported that it might be slow for his use cases

@marcio-diaz Would you be able to run your thing and collect some logs (-ltxpool=trace), maybe we can add some more to make sure it is running in parallel.


Remove enforcement of django.sessions in middleware

Hey there,
I just updated to the latest version of the package since I noticed that the storage didn't get properly saved in the CredentialsField, which resulted in always needing to refresh before doing any requests. But I can't test if new version fixes it for me.
We use django-user-sessions instead of the default django sessions. This is a drop-in replacement so everything should work, however there is an if check here which breaks everything.
My proposal is to remove the if check and assume people have their project configured properly, if not the resulting error should be obvious anyway.
I know this package is deprecated, but moving to google-auth is not an option for us at this time, and this change should not break backwards compatibility.

Thank you for creating this issue, however, this project is deprecatedand we will only be addressing critical security issues. You can read moreabout this deprecation here.
If you need support or help using this library, we recommend that you ask yourquestion on StackOverflow.
If you still think this issue is relevant and should be addressed, pleasecomment and let us know!


"needs triage" is not being reliably removed once other tags are added

Didn't we have a bot for that?

We have the rule:
    - if:
      - payloadType: Issues
      - isAction:
          action: Labeled
      - hasLabel:
          label: needs-triage
      - not:
          labelAdded:
            label: needs-triage
      then:
      - removeLabel:
          label: needs-triage

It should take care of removing the needs-triage as soon as any other tag is added.  I will create an issue to test it

Tested here: https://github.com/Azure/azure-dev/issues/2936
Working as expected


Issue 1: Virtual dev environment

This should cover the basics for this feature
Closes #1

hosts folder might be better off inside examples?

@woloski I agree that hosts at the root is a little confusing.  However, they aren't really examples.  When you run the dev.sh script it uses files in the hosts directory to spin up a dev/testing environment in Docker.  This makes it easy for everyone to run Nginx (and whatever other hosts we want it to reverse proxy to) in an execution environment that will behave the same on everyone's machine.
I usually don't do something like this for a simple web app (like Node), but for something that requires multiple hosts that run in collaboration, it made more sense.


Implement unit tests

Will have to research how this is best handled in Python.

It seems some new feature need wait for unit test implemented, so that cheat could keep stable and reliable.
I would like to help on this if you hadn't start on this!
Actually, I had a WIP branch that implement unit test for cheats.py at 636e9f5f39b6699a597731833c5a2a49b25bec72.
That my idea is cheat will use lot of user environment, like path or variables, that would different between server and server.
So we need to do is mock them.
If there is no big problem, I will try finish them soon!

Closing as resolved - nearly 7 years later - with the release of cheat v3.


Test restructure

This is the first part of a restructuring/refactoring of the existing test and a little expansion of the test suite.
Test file structure
The existing test suite consisted largely of functional tests on an ECMeasurement and these functional tests on this object itself was combined with round trip tests through directory backend save/load and through as_dict/from_dict to test that everything in the ECMeasurement survived the trip. While this first iteration of tests was very successful in aiding during development, the structure made is difficult to figure out exactly what was tested where and if some things were being tested more than once. Tests, also functional tests, should ideally test just one thing, so the first step of the refactoring was to brake these tests up into two modules. This was combined with a new test folder structure, which lends itself towards lots of tests of different kinds. The results structure is:
tests/
├── functional
│   ├── conftest.py
│   ├── __init__.py
│   ├── test_backends.py
│   └── test_measurements.py
└── README.md

where conftest.py contains some shared test fixtures (more about those below). The structure can then be expanded e.g. with unit tests in a folder called "unit" at the same level as "functional"
Equality
As mentioned, a central part of the rewrite was to separate the two purposes mentioned above; ECMeasurement functionality (of which testing very little was changed) and round trip survival. The latter leads into a discussion about how exactly to test for whether an object survives the trip. In the ideal, I think, what we should check for is whether an object is equal to whatever arrives in the other end, i.e:
id_ = measurement.save()
reloaded_measurement = Measurement.get(id_)
assert measurement == reloaded_measurement

Then we need to figure out, how exactly do we define equality for our objects. A couple of interesting questions came up:

Is the backend, and thereby all the ids, required to be equal?
What about the data, is it required to be equal down to the last bit, in order to be equal?

The decisions I landed on, and which obviously are open to discussion, were:

No. For all of the types we have, that can be saved and loaded, I consider this saving and loading something orthogonal to the object itself, and I therefore do not consider ids of objects or the backend when comparing equality. This has as a consequence that we do have to test equality on the data itself
I personally think it is too strict a requirement on a backend, and other serialization, that the data has to arrive back unaltered down to the last bit. I therefore opted to test for data equality with numpy.allclose which tests rtol=1e-05, atol=1e-08. Obviously the thresholds could be modified by making a local partial in tools or utils.

With these two decisions in mind, the __eq__ method was implemented for all the necessary objects and the tests merely written as above. A side note to implementing __eq__ for a custom object is that doing so, sets the implementation of __hash__ to None (see here https://docs.python.org/3/reference/datamodel.html#object.hash). This is problem, because the trick of passing a sequence of objects through set to remove duplicates is used several places, but this requires the object to be hashable. This is quickly fixed by borrowing the hash function from object (which I think essentially just returns the memory address). This has the implication that only the same object will have the same hash. As mentioned in the docs above, this may be a problem, because the implementation or __eq__ are "expected to be" related to the implementation of __hash__. Ours are not and with the decision on 2 probably never will. This has the amusing and somewhat exotic effect that trying to combine series which are the same, but with different backends, will not remove the "duplicates" from the series list, even though the object is equal. This may not be the intention, but that is also the way it already was.
One unresolved problem that I ran into, is that Calibration has an optional back reference to the measurement it should work on by default. Since I would normally include all objects in the equality check, this would result in a circular reference and infinite recursion. For now this is "solved" by simply not including this measurement in the Calibration equality check.
The decision on 2, in that I meant it to also apply to metadata, meant that some helper functions was written in tools.py to compare equality on dicts and lists, but where floats in the data structure are only required to be close (using np.isclose).
Tests improvements
A few but important improvements was done to make use of some of the testing framework:

Setup of dependencies that is used in multiple tests, was factored out of the test code by means of fixtures
Testing load/save to the directory backend was altered so that every test happens on a completely fresh directory backend in a tmp dir. This also happens by the magic of fixtures. I also fixed a bug found during this testing.
Several tests on float values was changed to use pytest approx to make sure they will keep working even if more manipulation is done on them, which might have float rounding problems.

Future work and proof reading focus
I think a natural next step is to remove the last duplication of tests that still exists, and say that if we really trusts the round trip tests, then it should not be necessary to do functionality tests across round trips. This of course means that it is super important that we all trust and completely agree on the round trip tests that depends on __eq__ so those should get at much attention as possible.
I hope you like it :)

Hi Kenneth,
Awesome philosophical stuff. Agree with the test restructure and the need for an __eq__, and all your considerations about what __eq__ should mean.
I think __eq__  should make use of the as_dict() representation and the class attribute child_attrs. If two Saveable objects have the same keys in their dictionary representations (self_as_dict and other_as_dict) AND for every key either (i) each object pointed to in  the lists self_as_dict[key] and  other_as_dict[key] are equal if key referes to a "child attr" and (ii) the two values are equal (or np.allclose for numerical data) otherwise.
I think that then __eq__ (and __hash__ need only be implemented once and away from the eyes of users or most developers, in db.Saveable.
I want to write test this, however, I am stuck with how to work on this and need a bit of help:

You're making this PR on a fork rather than a branch, so don't see how to add commits to the PR it in a straightforward way. Should I (i) approve this and make my own PR with what I figure out

I can't run the tests :( ... this is a me problem, but indicates that the barrier to entry is still quite high to all the stuff in tools.rst. I've tried the following (attempts i and ii give the same result in git bash):

(i) tox in the Anaconda Powershell Prompt. I get
ModuleNotFoundError: No module named 'distlib'
and
ERROR:   py37: InvocationError for command 'c:\users\scott\anaconda3\python.exe' -m virtualenv --no-download --python 'c:\users\scott\anaconda3\python.exe' py37 (exited with code 1)
(ii) pytest in Anaconda Powershell Prompt. I get
ERROR  - ModuleNotFoundError: No module named 'ixdat'
(iii) Doing it manually. Running a module rests/functional/run_test.py with the content
from .test_measurements import TestBiologicEC
from .conftest import ec_measurement as get_ec_measurement

ec_measurement = get_ec_measurement()

tester = TestBiologicEC()

tester.test_calibrate_and_append(ec_measurement)

gives the error
ModuleNotFoundError: No module named 'main.test_measurements'; 'main' is not a package
I only had a hour to try and figure out how to run tests today. DIdn't find a clear answer in tools.rst which I think means  that documentation is incomplete. Didn't start googling for answers. Suggestions welcome!

Here is the Saveable.__eq__ mentioned above: https://github.com/ixdat/ixdat/blob/c050207a494df12a404dfbd75d1cddc7f7a09de9/src/ixdat/db.py#L308


Split identifiers from keywords or identifiers

Separate identifiers, and keywords including identifiers in the grammar.

💟 Thanks!


the "set services to manual" option never ends

after clicking run tweaks it started to set services to manual but when it got to the XboxGipSvc it just didn't end ( it's been 20 minutes )
it tested on w10 and w11, same results

Try now

It works now and it's faster thanks


Only showing at mouse-over, not before

All icons look like this in the Tile Browser:

The images appear after you mouse over them, and while its loading you see a loading icon:

Can I change behavior so they're all automatically loaded?

That was the original behaviour. The problem is, that this can slow down very quickly, especially if the files are multiple MB in size and you have many of them in a directory. I'll think about maybe adding an option to change the behaviour at your own risk 😉

An option would be great. For local hosting it would definitely be preferred.
On 31 Dec 2021, 19:05 +0100, Steven Weingärtner @.***>, wrote:

That was the original behaviour. The problem is, that this can slow down very quickly, especially if the files are multiple MB in size and you have many of them in a directory. I'll think about maybe adding an option to change the behaviour at your own risk 😉
—
Reply to this email directly, view it on GitHub, or unsubscribe.
Triage notifications on the go with GitHub Mobile for iOS or Android.
You are receiving this because you authored the thread.Message ID: @.***>

With HTML5 and canvas you can also generate static images as placeholder, before you mouseover.
https://stackoverflow.com/questions/1158759/get-video-first-frame-in-javascript
On Friday, December 31, 2021, 07:26:37 PM GMT+1, @.***> wrote:
An option would be great. For local hosting it would definitely be preferred. On 31 Dec 2021, 19:05 +0100, Steven Weingärtner @.***>, wrote:
That was the original behaviour. The problem is, that this can slow down very quickly, especially if the files are multiple MB in size and you have many of them in a directory. I'll think about maybe adding an option to change the behaviour at your own risk 😉
—
Reply to this email directly, view it on GitHub, or unsubscribe.
Triage notifications on the go with GitHub Mobile for iOS or Android.
You are receiving this because you authored the thread.Message ID: @.***>

Hi and thanks for your module, I'm seft host my foundry and I'm interest about this option.


How to create only left side menu ?

I am developing a mobile app with meteoric, which have left hand side menu only but meteor-ionic is adding menu on both sides. Although I haven't added any right hand side menu but it is show some blank space on right hand side and its drag able event is also active on right hand side, here is a sample video
http://screencast.com/t/b9EeNizro

Have a look at #74.

its has done something different now my left hand side menu is shown on full screen

How you are creating side menu ?
this how I am doing going it
https://gist.github.com/MFQ/dadc8f2baf744dc62de0

@MFQ that looks correct. Have you tried running meteor update to make sure you have the latest versions of all the meteoric packages?

@MFQ any update. are you able to get it fix?

@nickw I have tired "meteor update" and I have removed "meteoric:ionic-sass" and then added it again but still no success.

Try this code on your rendered function:
IonSideMenu.snapper.settings({disable: 'right'});

@dancering I have tried your approach but I am getting this error
Exception from Tracker afterFlush function: Can't find variable: IonSideMenu
I guess IonSideMenu is not access in my rendered function, this how I am implementing my rendered function.
Template.mobileLayout.rendered = function () {
IonSideMenu.snapper.settings({disable: 'right'});
};

I have attached screen to show you how it works. IonSideMenu has to be available on the console. Can you list the packages that are you using?

Thanks dancering
Template.layout.rendered = function () {
IonSideMenu.snapper.settings({disable: 'right'});
};
Solved the issue with a blank menu on the RHS
Cheers

Good to know it's working.
@MFQ Please close the issue. Thx.

@dancering i can't access IonSideMenu at my browser console


deploy a zip

hello I'm trying to deploy a zip using this command
az webapp deployment source config-zip
But i have this issue
Expecting value: line 1 column 1 (char 0)
Traceback (most recent call last):
lib\site-packages\knack\cli.py, ln 206, in invoke
    cmd_result = self.invocation.execute(args)
cli\core\commands\__init__.py, ln 603, in execute
    raise ex
cli\core\commands\__init__.py, ln 661, in _run_jobs_serially
    results.append(self._run_job(expanded_arg, cmd_copy))
cli\core\commands\__init__.py, ln 654, in _run_job
    six.reraise(*sys.exc_info())
Python37-32\lib\site-packages\six.py, ln 693, in reraise
    raise value
...
Python37-32\lib\json\__init__.py, ln 348, in loads
    return _default_decoder.decode(s)
Python37-32\lib\json\decoder.py, ln 337, in decode
    obj, end = self.raw_decode(s, idx=_w(s, 0).end())
Python37-32\lib\json\decoder.py, ln 355, in raw_decode
    raise JSONDecodeError("Expecting value", s, err.value) from None
json.decoder.JSONDecodeError: Expecting value: line 1 column 1 (char 0)

To Reproduce:
Steps to reproduce the behavior. Note that argument values have been redacted, as they may contain sensitive information.

Put any pre-requisite steps here...
az webapp deployment source config-zip --resource-group {} --name {} --src {}

Expected Behavior
Environment Summary
Windows-10-10.0.17134-SP0
Python 3.7.4
Shell: cmd.exe

azure-cli 2.0.74 *

can you please tell me what is going on thank you

Similar problems are fixing.

Can you please re-try with the latest version & let us know if this still repros. Thanks!


Add composable API for Array generation on VectorFuzzer

Summary:
Add API fuzzArray(vector, size) to allow a more composable API for
clients generating a specific encoding configuration. Next PR will add support
for Maps and refactor the current fuzz() method to use them.
Reviewed By: mbasmanova
Differential Revision: D39681322

This has been merged already.


[5.1] Add the ability to set a directory prefix/root to a S3 disk

Add missing ability to set a directory prefix to a S3 disk.

You broke the build.

Also, I don't think root is a good name. prefix would be better.

Using the same markup as local disks in config/filesystems.php, not a good idea ?
For example:
'local' => [
'driver' => 'local',
'root' => storage_path() . '/app',
],

Maybe it's fine. Taylor can always change it if he prefers prefix.

Can you fix the cs issues please.

Fixed cs issue, all checks passed.

Done!


Dck redux 4

updated redux to v.4.0.4
refactored items reducers
implemented selection reducers
fixed issues #61 #62 #63
added more tests

@volodymyrrudyi please, review it


Don't set ip_forward when no subnet is set in bridge config

The lxd-bridge code enables net.ipv4.ip_forward by default. In the Ubuntu images that the Certified Public Cloud team produce for Google Compute Engine, we explicitly disable net.ipv4.ip_forward, which is overriden when lxd-bridge starts up. As such, automatically enabling it has a (minor) security surface, as it breaks our user's expectations.
We would like it if you would move away from automatically enabling it in the future.

N.B. stgraber has already told me that this is the plan (when moving to lxdbr0 instead of lxcbr0), but I wanted an open bug so that (a) it doesn't get lost in the shuffle, and (b) I have something that I can point GCE folks at.

Updating the issue for the part that's actually relevant to LXD upstream.
The rest of the bridge stuff is a distro specific thing which isn't done by LXD upstream.


Rfc: fix up match arm pattern

This PR implements part of RFC style for match arm.

Put { on a newline if we break before if
Do not add visual offset (if ) when the condition goes multi line (like we do in normal if expression)

Added force_format_strings option to one of the tests because otherwise the string did not get formatted.

Thank you!


Could not find com.github.yalantis:ucrop:2.2.7.

Could not find com.github.yalantis:ucrop:2.2.7.
update yalantis dependency in your library

It is 2.2.7: https://github.com/Drjacky/ImagePicker/blob/6e5b9abf7675c927eae306e31ba92a9d8de4844e/imagepicker/build.gradle#L52
Please take a look at this: https://github.com/Drjacky/ImagePicker/issues/47


Moveend Event on a layer

Hi!
I would like to know how to listen to a zoom in-out and mouse move (center change) event on a layer, just to make a WMS request each time that happends. I tried the following code but it doesn't work:
$scope.$on('openlayers.layers.ccaa.moveend', function(event, feature){
....	 });
Thanks

Hey, something like this may work.
<!-- map.html -->
<openlayers ol-center="vm.center" ...>
</openlayers>

and in the controller
var component = {
   templateUrl: 'map.html',
   controller: MapController,
   controllerAs: 'vm'
};

function MapController($scope) {
   var vm = this;

   ...
   $scope.$watch('vm.center', function(newVal, oldVal) {
      var zoomLevel = newVal.zoom;
      var lat = newVal.lat;
      var lng = newVal.lon
   });

}

Is there any solution with out using $watch?.


Unable to submit a file attachment through a file form input

I'm not 100% sure if this is a GhostDriver issue but I figured this would be a good place to start. I've narrowed it down to either PhantomJS or GhostDriver I think
I'm currently working on acceptance tests using Codeception, PhantomJS and PHP's built-in web server. I came across an issue today where trying to submit a file to a file input was failing. After a lot of digging I didn't really get anywhere solid other than Facebook's webdriver returning null at some point.
Turning off PhantomJS and instead using Selenium's standalone server allows the file to attach properly
Current setup

Codeception
PhantomJS w/GhostDriver

phantomjs --webdriver=4444

PHP's Built In Server

Error Output
Below is a part of the stack trace that doesn't involve my individual test files
[ErrorException] Invalid argument supplied for foreach()

#1  vendor/facebook/webdriver/lib/WebDriverKeys.php:103
#2  vendor/facebook/webdriver/lib/remote/RemoteWebElement.php:266

I know these errors are showing up in Facebook's Webdriver but I think that's more just a symptom of the issue since not using PhantomJS allows for it to all work properly.
After digging through what Facebook's Webdriver is doing, when it goes through the act of attaching a file, it makes a curl request and which ends up returning an Invalid Command Method when it's executed

I'm sorry if this issue is somewhat vague. I've been trying to sort out something more concrete for a while but haven't made much progress. All I've been able to determine for sure is that using Selenium standalone allows it to work properly.
Please let me know if there's any other information I can provide that would help debug this a bit more.
Does any of this sound familiar to you who are more familiar with internals of how all this works? Would there be a better place to post this issue?
Thanks!

@Olofguard Do u know if anyone has fixed this issue yet? Or r u still experiencing it?
I'm having the same problem using nightwatchjs. Appreciate any help

I have the same issue. Appreciate any help

Sorry guys, this is still a problem for me as well. :(