Fail to setup BOSH with vsphere with BOSH version 2830

Hello,
I'm a newbie on BOSH so sorry if this question is stupid....I've been playing with BOSH for few days now and got a old release (912) running on vsphere but when I tried with a newer version (2830) and I'm getting an error (see below).
I'm getting the stemcells & release from here: http://bosh_artifacts.cfapps.io.
the vms are created
root@ubuntu1404:~/my-bosh-deployment# bosh vms
Deployment `bosh2'
Director task 27
Task 27 done
+-------------+---------+---------------+----------------+
| Job/index   | State   | Resource Pool | IPs            |
+-------------+---------+---------------+----------------+
| bosh_api/0  | running | default       | <IP_ADDRESS> |
| bosh_data/0 | running | default       | <IP_ADDRESS> |
+-------------+---------+---------------+----------------+
VMs total: 2
& strangely, "bosh cloudcheck bosh2" returns "No problems found"  (bosh2 is the name of my instance)
Any idea about the cause of this pb ? (See below traces observed & manifest used)
Thx beforehand.

HERE IS THE OUTPUT OF THE DEPLOY
==================================
root@ubuntu1404:~/my-bosh-deployment# bosh deployment bosh.yml
Deployment set to `/root/my-bosh-deployment/bosh.yml'
root@ubuntu1404:~/my-bosh-deployment# bosh deploy

Processing deployment manifest
Getting deployment properties from director...
Unable to get properties list from director, trying without it...
Compiling deployment manifest...
Cannot get current deployment information from director, possibly a new deployment
Please review all changes carefully
Deploying
Deployment name: bosh.yml' Director name: microbosh'
Are you sure you want to deploy? (type 'yes' to continue): yes
Director task 25
Deprecation: Please use templates' when specifying multiple templates for a job. template' for multiple templates will soon be unsupported.
Deprecation: Please use templates' when specifying multiple templates for a job. template' for multiple templates will soon be unsupported.
Started preparing deployment
Started preparing deployment > Binding deployment. Done (00:00:00)
Started preparing deployment > Binding releases. Done (00:00:00)
Started preparing deployment > Binding existing deployment. Done (00:00:00)
Started preparing deployment > Binding resource pools. Done (00:00:00)
Started preparing deployment > Binding stemcells. Done (00:00:00)
Started preparing deployment > Binding templates. Done (00:00:00)
Started preparing deployment > Binding properties. Done (00:00:00)
Started preparing deployment > Binding unallocated VMs. Done (00:00:00)
Started preparing deployment > Binding instance networks. Done (00:00:00)
Done preparing deployment (00:00:00)
Started preparing package compilation > Finding packages to compile. Done (00:00:00)
Started preparing dns > Binding DNS. Done (00:00:00)
Started creating bound missing vms
Started creating bound missing vms > default/0
Started creating bound missing vms > default/1
Done creating bound missing vms > default/0 (00:00:47)
Done creating bound missing vms > default/1 (00:00:47)
Done creating bound missing vms (00:00:47)
Started binding instance vms
Started binding instance vms > bosh_api/0
Started binding instance vms > bosh_data/0
Done binding instance vms > bosh_api/0 (00:00:00)
Done binding instance vms > bosh_data/0 (00:00:00)
Done binding instance vms (00:00:00)
Started preparing configuration > Binding configuration. Failed: Error filling in template director.yml.erb.erb' for bosh_api/0' (line 332: undefined method `each' for nil:NilClass) (00:00:00)
Error 100: Error filling in template director.yml.erb.erb' for bosh_api/0' (line 332: undefined method `each' for nil:NilClass)
Task 25 error
For a more detailed error report, run: bosh task 25 --debug

HERE IS THE BEGINNING OF THE DEBUG FILE (that includes the manifest)
==============================================================
Director task 25
I, [2015-02-07T18:24:54.493001 #1233] [0x3f9ce1dbd324]  INFO -- TaskHelper: Director Version: 1.2830.0
I, [2015-02-07T18:24:54.493073 #1233] [0x3f9ce1dbd324]  INFO -- TaskHelper: Enqueuing task: 25
I, [2015-02-07 18:24:54 #5516] []  INFO -- DirectorJobRunner: Looking for task with task id 25
D, [2015-02-07 18:24:54 #5516] [] DEBUG -- DirectorJobRunner: (0.000591s) SELECT * FROM "tasks" WHERE "id" = 25
I, [2015-02-07 18:24:54 #5516] []  INFO -- DirectorJobRunner: Starting task: 25
I, [2015-02-07 18:24:54 #5516] [task:25]  INFO -- DirectorJobRunner: Creating job
I, [2015-02-07 18:24:54 #5516] [task:25]  INFO -- DirectorJobRunner: Reading deployment manifest
D, [2015-02-07 18:24:54 #5516] [task:25] DEBUG -- DirectorJobRunner: Manifest:

name: bosh2
logging:
-level: DEBUG
director_uuid: 35b5ea35-213b-4494-8fb7-c1c191178824
release:
name: bosh
version: 139
networks:

name: default
type: manual
subnets:

range: <IP_ADDRESS>/28
gateway: <IP_ADDRESS>
static:

<IP_ADDRESS>
<IP_ADDRESS>
reserved:
<IP_ADDRESS> - <IP_ADDRESS>
dns:
<IP_ADDRESS>
<IP_ADDRESS>
cloud_properties:
name: Private Network - vmnic0 vmnic2
resource_pools:

name: default
stemcell:
name: bosh-vsphere-esxi-ubuntu-trusty-go_agent
version: 2830
network: default
size: 5
cloud_properties:
cpu: 2
ram: 512
disk: 2000
compilation:
reuse_compilation_vms: true
workers: 3
network: default
cloud_properties:
ram: 512
disk: 6000
cpu: 2
update:
canaries: 1
canary_watch_time: 30000-90000
update_watch_time: 30000-90000
max_in_flight: 1
jobs:
name: bosh_data
template:

blobstore
postgres
redis
instances: 1
resource_pool: default
persistent_disk: 8000
networks:
name: default
static_ips:

<IP_ADDRESS>

name: bosh_api
template:

nats
director
health_monitor
powerdns
instances: 1
resource_pool: default
networks:
name: default
static_ips:

<IP_ADDRESS>
properties:
ntp:

servertime.service.softlayer.com
nats:
user: nats
password: nats-password
address: <IP_ADDRESS>
port: 4222
blobstore:
address: <IP_ADDRESS>
port: 25251
backend_port: 25552
agent:
user: agent
password: agent
director:
user: director
password: director
postgres: &17533100
user: bosh
password: bosh
host: <IP_ADDRESS>
port: 5432
database: bosh
redis:
password: redis
address: <IP_ADDRESS>
port: 25255
director:
name: bosh2
address: <IP_ADDRESS>
port: 25555
encryption: false
enable_snapshots: false
max_tasks: 100
db: *17533100
hm:
http:
port: 25923
user: admin
password: admin
director_account:
user: admin
password: admin
intervals:
poll_director: 60
poll_grace_period: 30
log_stats: 300
analyze_agents: 60
agent_timeout: 180
rogue_agent_alert: 180
loglevel: info
email_notifications: false
tsdb_enabled: false
cloud_watch_enabled: false
resurrector_enabled: true
dns:
address: <IP_ADDRESS>
recursor: <IP_ADDRESS>
db: *17533100
vcenter:
address: <IP_ADDRESS>
user: Administrator
password: a5pattes
datacenters:

name: bschmcSL1
vm_folder: mycfvm
template_folder: mycftemplate
disk_path: /cfdir
datastore_pattern: datastore1
persistent_datastore_pattern: datastore1
allow_mixed_datastores: true
clusters:

cfcluster:

I, [2015-02-07 18:24:54 #5516] [task:25]  INFO -- DirectorJobRunner: Creating deployment plan
I, [2015-02-07 18:24:54 #5516] [task:25]  INFO -- DirectorJobRunner: Deployment plan options: {}

HERE IS THE END OF THE DEBUG FILE (that includes the error traces)
===========================================================
I, [2015-02-07 18:25:43 #5516] [task:25]  INFO -- DirectorJobRunner: Binding configuration
D, [2015-02-07 18:25:43 #5516] [task:25] DEBUG -- DirectorJobRunner: Downloading template blobstore' (5813adb9-be71-4dd6-a28b-c56d4285b6c3)... D, [2015-02-07 18:25:43 #5516] [task:25] DEBUG -- DirectorJobRunner: Template blobstore' downloaded to /var/vcap/data/tmp/director/template-3d617414-9a8a-403f-bb51-a6aa43b1d2eb (took 0.00196793s)
D, [2015-02-07 18:25:43 #5516] [task:25] DEBUG -- DirectorJobRunner: Downloading template postgres' (7c72ca1a-a125-4e34-947b-561ece179849)... D, [2015-02-07 18:25:43 #5516] [task:25] DEBUG -- DirectorJobRunner: Template postgres' downloaded to /var/vcap/data/tmp/director/template-5b86eed9-44fa-4e60-9590-55eb44e4c094 (took 0.001658084s)
D, [2015-02-07 18:25:43 #5516] [task:25] DEBUG -- DirectorJobRunner: Downloading template redis' (0970103e-beba-4c09-8d45-7bb8d6f68e42)... D, [2015-02-07 18:25:43 #5516] [task:25] DEBUG -- DirectorJobRunner: Template redis' downloaded to /var/vcap/data/tmp/director/template-87ad6318-893e-4c93-8ad1-508d813e48c3 (took 0.001621872s)
D, [2015-02-07 18:25:43 #5516] [task:25] DEBUG -- DirectorJobRunner: (0.000787s) SELECT * FROM "rendered_templates_archives" WHERE ("rendered_templates_archives"."instance_id" = 16) ORDER BY "created_at" DESC LIMIT 1
D, [2015-02-07 18:25:43 #5516] [task:25] DEBUG -- DirectorJobRunner: (0.000130s) BEGIN
D, [2015-02-07 18:25:43 #5516] [task:25] DEBUG -- DirectorJobRunner: (0.000603s) INSERT INTO "rendered_templates_archives" ("blobstore_id", "sha1", "content_sha1", "created_at", "instance_id") VALUES ('ff12cbfa-5a19-412d-9d74-37b7bff4081a', 'c583ac6b01b58bb7254f62b551bf30f393f218ba', '3718c7cee2f33e333b82dd744cc7c152bbc84473', '2015-02-07 18:25:43.754353+0000', 16) RETURNING *
D, [2015-02-07 18:25:43 #5516] [task:25] DEBUG -- DirectorJobRunner: (0.000303s) COMMIT
D, [2015-02-07 18:25:43 #5516] [task:25] DEBUG -- DirectorJobRunner: Downloading template nats' (13bfe8e2-9dcc-44ab-b7d0-d00f97158702)... D, [2015-02-07 18:25:43 #5516] [task:25] DEBUG -- DirectorJobRunner: Template nats' downloaded to /var/vcap/data/tmp/director/template-9ce5dfb8-c01b-4387-9d95-38bcd4c6782c (took 0.001471583s)
D, [2015-02-07 18:25:43 #5516] [task:25] DEBUG -- DirectorJobRunner: Downloading template director' (152ceb9b-df65-4e01-aef2-acd47aee5104)... D, [2015-02-07 18:25:43 #5516] [task:25] DEBUG -- DirectorJobRunner: Template director' downloaded to /var/vcap/data/tmp/director/template-cc5c0bca-6f93-467d-a76c-f70efa82dea7 (took 0.001783735s)
D, [2015-02-07 18:25:43 #5516] [task:25] DEBUG -- DirectorJobRunner: Downloading template health_monitor' (0ffaf10b-bbd3-4df7-9697-e7c319a06494)... D, [2015-02-07 18:25:43 #5516] [task:25] DEBUG -- DirectorJobRunner: Template health_monitor' downloaded to /var/vcap/data/tmp/director/template-1e0013fc-88fa-4d55-8680-1385f7095640 (took 0.001549402s)
D, [2015-02-07 18:25:43 #5516] [task:25] DEBUG -- DirectorJobRunner: Downloading template powerdns' (4207cae4-42e1-4029-ab65-4cf0c95ab54d)... D, [2015-02-07 18:25:43 #5516] [task:25] DEBUG -- DirectorJobRunner: Template powerdns' downloaded to /var/vcap/data/tmp/director/template-30d0e869-0f7e-4ee5-bbcc-402a7d8c65b6 (took 0.001550487s)
D, [2015-02-07 18:25:43 #5516] [task:25] DEBUG -- DirectorJobRunner: #<NoMethodError: undefined method each' for nil:NilClass> D, [2015-02-07 18:25:43 #5516] [task:25] DEBUG -- DirectorJobRunner: Error filling in template director.yml.erb.erb' for bosh_api/0' (line 332: undefined method each' for nil:NilClass)
director/director.yml.erb.erb:332:in block (4 levels) in get_binding' director/director.yml.erb.erb:330:in each'
director/director.yml.erb.erb:330:in block (3 levels) in get_binding' director/director.yml.erb.erb:327:in each'
director/director.yml.erb.erb:327:in block (2 levels) in get_binding' director/director.yml.erb.erb:318:in each'
director/director.yml.erb.erb:318:in block in get_binding' /var/vcap/packages/director/gem_home/ruby/2.1.0/gems/bosh-template-1.2830.0/lib/bosh/template/evaluation_context.rb:101:in if_p'
director/director.yml.erb.erb:308:in get_binding' /var/vcap/packages/ruby/lib/ruby/2.1.0/erb.rb:850:in eval'
/var/vcap/packages/ruby/lib/ruby/2.1.0/erb.rb:850:in result' /var/vcap/packages/director/gem_home/ruby/2.1.0/gems/bosh-director-core-1.2830.0/lib/bosh/director/core/templates/source_erb.rb:17:in render'
/var/vcap/packages/director/gem_home/ruby/2.1.0/gems/bosh-director-core-1.2830.0/lib/bosh/director/core/templates/job_template_renderer.rb:25:in block in render' /var/vcap/packages/director/gem_home/ruby/2.1.0/gems/bosh-director-core-1.2830.0/lib/bosh/director/core/templates/job_template_renderer.rb:24:in map'
/var/vcap/packages/director/gem_home/ruby/2.1.0/gems/bosh-director-core-1.2830.0/lib/bosh/director/core/templates/job_template_renderer.rb:24:in render' /var/vcap/packages/director/gem_home/ruby/2.1.0/gems/bosh-director-core-1.2830.0/lib/bosh/director/core/templates/job_instance_renderer.rb:14:in block in render'
/var/vcap/packages/director/gem_home/ruby/2.1.0/gems/bosh-director-core-1.2830.0/lib/bosh/director/core/templates/job_instance_renderer.rb:12:in map' /var/vcap/packages/director/gem_home/ruby/2.1.0/gems/bosh-director-core-1.2830.0/lib/bosh/director/core/templates/job_instance_renderer.rb:12:in render'
/var/vcap/packages/director/gem_home/ruby/2.1.0/gems/bosh-director-1.2830.0/lib/bosh/director/job_renderer.rb:20:in render_job_instance' /var/vcap/packages/director/gem_home/ruby/2.1.0/gems/bosh-director-1.2830.0/lib/bosh/director/job_renderer.rb:16:in block in render_job_instances'
/var/vcap/packages/director/gem_home/ruby/2.1.0/gems/bosh-director-1.2830.0/lib/bosh/director/job_renderer.rb:16:in each' /var/vcap/packages/director/gem_home/ruby/2.1.0/gems/bosh-director-1.2830.0/lib/bosh/director/job_renderer.rb:16:in render_job_instances'
/var/vcap/packages/director/gem_home/ruby/2.1.0/gems/bosh-director-1.2830.0/lib/bosh/director/deployment_plan/assembler.rb:324:in block in bind_configuration' /var/vcap/packages/director/gem_home/ruby/2.1.0/gems/bosh-director-1.2830.0/lib/bosh/director/deployment_plan/assembler.rb:323:in each'
/var/vcap/packages/director/gem_home/ruby/2.1.0/gems/bosh-director-1.2830.0/lib/bosh/director/deployment_plan/assembler.rb:323:in bind_configuration' /var/vcap/packages/director/gem_home/ruby/2.1.0/gems/bosh-director-1.2830.0/lib/bosh/director/deployment_plan/updater.rb:35:in block in update'
/var/vcap/packages/director/gem_home/ruby/2.1.0/gems/bosh-director-1.2830.0/lib/bosh/director/jobs/base_job.rb:48:in block in track_and_log' /var/vcap/packages/director/gem_home/ruby/2.1.0/gems/bosh-director-1.2830.0/lib/bosh/director/event_log.rb:97:in call'
/var/vcap/packages/director/gem_home/ruby/2.1.0/gems/bosh-director-1.2830.0/lib/bosh/director/event_log.rb:97:in advance_and_track' /var/vcap/packages/director/gem_home/ruby/2.1.0/gems/bosh-director-1.2830.0/lib/bosh/director/event_log.rb:50:in track'
/var/vcap/packages/director/gem_home/ruby/2.1.0/gems/bosh-director-1.2830.0/lib/bosh/director/jobs/base_job.rb:46:in track_and_log' /var/vcap/packages/director/gem_home/ruby/2.1.0/gems/bosh-director-1.2830.0/lib/bosh/director/deployment_plan/updater.rb:34:in update'
/var/vcap/packages/director/gem_home/ruby/2.1.0/gems/bosh-director-1.2830.0/lib/bosh/director/jobs/update_deployment.rb:60:in update' /var/vcap/packages/director/gem_home/ruby/2.1.0/gems/bosh-director-1.2830.0/lib/bosh/director/jobs/update_deployment.rb:87:in block in perform'
/var/vcap/packages/director/gem_home/ruby/2.1.0/gems/bosh-director-1.2830.0/lib/bosh/director/lock_helper.rb:21:in block in with_deployment_lock' /var/vcap/packages/director/gem_home/ruby/2.1.0/gems/bosh-director-1.2830.0/lib/bosh/director/lock.rb:58:in lock'
/var/vcap/packages/director/gem_home/ruby/2.1.0/gems/bosh-director-1.2830.0/lib/bosh/director/lock_helper.rb:21:in with_deployment_lock' /var/vcap/packages/director/gem_home/ruby/2.1.0/gems/bosh-director-1.2830.0/lib/bosh/director/jobs/update_deployment.rb:79:in perform'
/var/vcap/packages/director/gem_home/ruby/2.1.0/gems/bosh-director-1.2830.0/lib/bosh/director/job_runner.rb:108:in perform_job' /var/vcap/packages/director/gem_home/ruby/2.1.0/gems/bosh-director-1.2830.0/lib/bosh/director/job_runner.rb:31:in block in run'
/var/vcap/packages/director/gem_home/ruby/2.1.0/gems/bosh_common-1.2830.0/lib/common/thread_formatter.rb:49:in with_thread_name' /var/vcap/packages/director/gem_home/ruby/2.1.0/gems/bosh-director-1.2830.0/lib/bosh/director/job_runner.rb:31:in run'
/var/vcap/packages/director/gem_home/ruby/2.1.0/gems/bosh-director-1.2830.0/lib/bosh/director/jobs/base_job.rb:10:in perform' /var/vcap/packages/director/gem_home/ruby/2.1.0/gems/resque-1.25.2/lib/resque/job.rb:227:in perform'
/var/vcap/packages/director/gem_home/ruby/2.1.0/gems/resque-1.25.2/lib/resque/worker.rb:250:in perform' /var/vcap/packages/director/gem_home/ruby/2.1.0/gems/resque-1.25.2/lib/resque/worker.rb:189:in block in work'
/var/vcap/packages/director/gem_home/ruby/2.1.0/gems/resque-1.25.2/lib/resque/worker.rb:166:in loop' /var/vcap/packages/director/gem_home/ruby/2.1.0/gems/resque-1.25.2/lib/resque/worker.rb:166:in work'
/var/vcap/packages/director/gem_home/ruby/2.1.0/gems/bosh-director-1.2830.0/bin/bosh-director-worker:83:in <top (required)>' /var/vcap/packages/director/bin/bosh-director-worker:16:in load'
/var/vcap/packages/director/bin/bosh-director-worker:16:in <main>' D, [2015-02-07 18:25:43 #5516] [task:25] DEBUG -- DirectorJobRunner: (0.000884s) SELECT "stemcells".* FROM "stemcells" INNER JOIN "deployments_stemcells" ON (("deployments_stemcells"."stemcell_id" = "stemcells"."id") AND ("deployments_stemcells"."deployment_id" = 6)) D, [2015-02-07 18:25:43 #5516] [] DEBUG -- DirectorJobRunner: Lock renewal thread exiting D, [2015-02-07 18:25:43 #5516] [task:25] DEBUG -- DirectorJobRunner: Deleting lock: lock:deployment:bosh2 D, [2015-02-07 18:25:43 #5516] [task:25] DEBUG -- DirectorJobRunner: Deleted lock: lock:deployment:bosh2 I, [2015-02-07 18:25:43 #5516] [task:25]  INFO -- DirectorJobRunner: sending update deployment error event D, [2015-02-07 18:25:43 #5516] [task:25] DEBUG -- DirectorJobRunner: SENT: hm.director.alert {"id":"7d4e345b-c4e2-45d3-9b92-5ad58f5c98ff","severity":3,"title":"director - error during update deployment","summary":"Error during update deployment for bosh2 against Director 35b5ea35-213b-4494-8fb7-c1c191178824: #<RuntimeError: Error filling in template director.yml.erb.erb' for bosh_api/0' (line 332: undefined method each' for nil:NilClass)>","created_at":1423333543}
E, [2015-02-07 18:25:43 #5516] [task:25] ERROR -- DirectorJobRunner: Error filling in template director.yml.erb.erb' for bosh_api/0' (line 332: undefined method each' for nil:NilClass) /var/vcap/packages/director/gem_home/ruby/2.1.0/gems/bosh-director-core-1.2830.0/lib/bosh/director/core/templates/source_erb.rb:32:in rescue in render'
/var/vcap/packages/director/gem_home/ruby/2.1.0/gems/bosh-director-core-1.2830.0/lib/bosh/director/core/templates/source_erb.rb:17:in render' /var/vcap/packages/director/gem_home/ruby/2.1.0/gems/bosh-director-core-1.2830.0/lib/bosh/director/core/templates/job_template_renderer.rb:25:in block in render'
/var/vcap/packages/director/gem_home/ruby/2.1.0/gems/bosh-director-core-1.2830.0/lib/bosh/director/core/templates/job_template_renderer.rb:24:in map' /var/vcap/packages/director/gem_home/ruby/2.1.0/gems/bosh-director-core-1.2830.0/lib/bosh/director/core/templates/job_template_renderer.rb:24:in render'
/var/vcap/packages/director/gem_home/ruby/2.1.0/gems/bosh-director-core-1.2830.0/lib/bosh/director/core/templates/job_instance_renderer.rb:14:in block in render' /var/vcap/packages/director/gem_home/ruby/2.1.0/gems/bosh-director-core-1.2830.0/lib/bosh/director/core/templates/job_instance_renderer.rb:12:in map'
/var/vcap/packages/director/gem_home/ruby/2.1.0/gems/bosh-director-core-1.2830.0/lib/bosh/director/core/templates/job_instance_renderer.rb:12:in render' /var/vcap/packages/director/gem_home/ruby/2.1.0/gems/bosh-director-1.2830.0/lib/bosh/director/job_renderer.rb:20:in render_job_instance'
/var/vcap/packages/director/gem_home/ruby/2.1.0/gems/bosh-director-1.2830.0/lib/bosh/director/job_renderer.rb:16:in block in render_job_instances' /var/vcap/packages/director/gem_home/ruby/2.1.0/gems/bosh-director-1.2830.0/lib/bosh/director/job_renderer.rb:16:in each'
/var/vcap/packages/director/gem_home/ruby/2.1.0/gems/bosh-director-1.2830.0/lib/bosh/director/job_renderer.rb:16:in render_job_instances' /var/vcap/packages/director/gem_home/ruby/2.1.0/gems/bosh-director-1.2830.0/lib/bosh/director/deployment_plan/assembler.rb:324:in block in bind_configuration'
/var/vcap/packages/director/gem_home/ruby/2.1.0/gems/bosh-director-1.2830.0/lib/bosh/director/deployment_plan/assembler.rb:323:in each' /var/vcap/packages/director/gem_home/ruby/2.1.0/gems/bosh-director-1.2830.0/lib/bosh/director/deployment_plan/assembler.rb:323:in bind_configuration'
/var/vcap/packages/director/gem_home/ruby/2.1.0/gems/bosh-director-1.2830.0/lib/bosh/director/deployment_plan/updater.rb:35:in block in update' /var/vcap/packages/director/gem_home/ruby/2.1.0/gems/bosh-director-1.2830.0/lib/bosh/director/jobs/base_job.rb:48:in block in track_and_log'
/var/vcap/packages/director/gem_home/ruby/2.1.0/gems/bosh-director-1.2830.0/lib/bosh/director/event_log.rb:97:in call' /var/vcap/packages/director/gem_home/ruby/2.1.0/gems/bosh-director-1.2830.0/lib/bosh/director/event_log.rb:97:in advance_and_track'
/var/vcap/packages/director/gem_home/ruby/2.1.0/gems/bosh-director-1.2830.0/lib/bosh/director/event_log.rb:50:in track' /var/vcap/packages/director/gem_home/ruby/2.1.0/gems/bosh-director-1.2830.0/lib/bosh/director/jobs/base_job.rb:46:in track_and_log'
/var/vcap/packages/director/gem_home/ruby/2.1.0/gems/bosh-director-1.2830.0/lib/bosh/director/deployment_plan/updater.rb:34:in update' /var/vcap/packages/director/gem_home/ruby/2.1.0/gems/bosh-director-1.2830.0/lib/bosh/director/jobs/update_deployment.rb:60:in update'
/var/vcap/packages/director/gem_home/ruby/2.1.0/gems/bosh-director-1.2830.0/lib/bosh/director/jobs/update_deployment.rb:87:in block in perform' /var/vcap/packages/director/gem_home/ruby/2.1.0/gems/bosh-director-1.2830.0/lib/bosh/director/lock_helper.rb:21:in block in with_deployment_lock'
/var/vcap/packages/director/gem_home/ruby/2.1.0/gems/bosh-director-1.2830.0/lib/bosh/director/lock.rb:58:in lock' /var/vcap/packages/director/gem_home/ruby/2.1.0/gems/bosh-director-1.2830.0/lib/bosh/director/lock_helper.rb:21:in with_deployment_lock'
/var/vcap/packages/director/gem_home/ruby/2.1.0/gems/bosh-director-1.2830.0/lib/bosh/director/jobs/update_deployment.rb:79:in perform' /var/vcap/packages/director/gem_home/ruby/2.1.0/gems/bosh-director-1.2830.0/lib/bosh/director/job_runner.rb:108:in perform_job'
/var/vcap/packages/director/gem_home/ruby/2.1.0/gems/bosh-director-1.2830.0/lib/bosh/director/job_runner.rb:31:in block in run' /var/vcap/packages/director/gem_home/ruby/2.1.0/gems/bosh_common-1.2830.0/lib/common/thread_formatter.rb:49:in with_thread_name'
/var/vcap/packages/director/gem_home/ruby/2.1.0/gems/bosh-director-1.2830.0/lib/bosh/director/job_runner.rb:31:in run' /var/vcap/packages/director/gem_home/ruby/2.1.0/gems/bosh-director-1.2830.0/lib/bosh/director/jobs/base_job.rb:10:in perform'
/var/vcap/packages/director/gem_home/ruby/2.1.0/gems/resque-1.25.2/lib/resque/job.rb:227:in perform' /var/vcap/packages/director/gem_home/ruby/2.1.0/gems/resque-1.25.2/lib/resque/worker.rb:250:in perform'
/var/vcap/packages/director/gem_home/ruby/2.1.0/gems/resque-1.25.2/lib/resque/worker.rb:189:in block in work' /var/vcap/packages/director/gem_home/ruby/2.1.0/gems/resque-1.25.2/lib/resque/worker.rb:166:in loop'
/var/vcap/packages/director/gem_home/ruby/2.1.0/gems/resque-1.25.2/lib/resque/worker.rb:166:in work' /var/vcap/packages/director/gem_home/ruby/2.1.0/gems/bosh-director-1.2830.0/bin/bosh-director-worker:83:in <top (required)>'
/var/vcap/packages/director/bin/bosh-director-worker:16:in load' /var/vcap/packages/director/bin/bosh-director-worker:16:in '
D, [2015-02-07 18:25:43 #5516] [task:25] DEBUG -- DirectorJobRunner: (0.000089s) BEGIN
D, [2015-02-07 18:25:43 #5516] [task:25] DEBUG -- DirectorJobRunner: (0.000371s) UPDATE "tasks" SET "state" = 'error', "timestamp" = '2015-02-07 18:25:43.890471+0000', "description" = 'create deployment', "result" = 'Error filling in template director.yml.erb.erb'' for bosh_api/0'' (line 332: undefined method `each'' for nil:NilClass)', "output" = '/var/vcap/store/director/tasks/25', "checkpoint_time" = '2015-02-07 18:25:26.456490+0000', "type" = 'update_deployment', "username" = 'admin' WHERE ("id" = 25)
D, [2015-02-07 18:25:43 #5516] [task:25] DEBUG -- DirectorJobRunner: (0.000351s) COMMIT
I, [2015-02-07 18:25:43 #5516] []  INFO -- DirectorJobRunner: Task took 49.178562133 seconds to process.

Hi me again,
I did change my manifest file to remove the warning about the "template" statement being deprecated when having several components deployed within the same vm by replacing with a "templateS" statement (in the job section of the manifest) thinking that it might fixed the problem but unfortunately it did not & I still have the same error as before when Binding configuration takes place:
Started preparing configuration > Binding configuration. Failed: Error filling in template director.yml.erb.erb' for bosh_api/0' (line 332: undefined method `each' for nil:NilClass) (00:00:00)
Error 100: Error filling in template director.yml.erb.erb' for bosh_api/0' (line 332: undefined method `each' for nil:NilClass)
Any idea ?
SEE BELOW THE NEW MANIFEST FILE I'M USING
name: bosh2
logging:
-level: DEBUG
director_uuid: 35b5ea35-213b-4494-8fb7-c1c191178824
release: {name: bosh, version: 139}
networks:

name: default
type: manual
subnets:

range: <IP_ADDRESS>/28
gateway: <IP_ADDRESS>
static:

<IP_ADDRESS>
<IP_ADDRESS>
reserved:

.224 is special, not sure if I need to put it in the reserved range

<IP_ADDRESS> - <IP_ADDRESS>

.239 is special, not sure if I need to put it in the reserved range
dns:

<IP_ADDRESS>
<IP_ADDRESS>
cloud_properties:
name: Private Network - vmnic0 vmnic2

resource_pools:

name: default
stemcell:
name: bosh-vsphere-esxi-ubuntu-trusty-go_agent
version: 2830
network: default
size: 5
cloud_properties:
cpu: 2
ram: 512
disk: 2000

compilation:
reuse_compilation_vms: true
workers: 3
network: default
cloud_properties:
ram: 512
disk: 6000
cpu: 2
update:
canaries: 1
canary_watch_time: 30000-90000
update_watch_time: 30000-90000
max_in_flight: 1
jobs:

name: bosh_data
templates:

name: blobstore
name: postgres
name: redis
instances: 1
resource_pool: default
persistent_disk: 8_000
networks:
name: default
static_ips: [<IP_ADDRESS>]

name: bosh_api
templates:

name: nats
name: director
name: health_monitor
name: powerdns
instances: 1
resource_pool: default
networks:
name: default
static_ips: [<IP_ADDRESS>]

properties:
env:
ntp:
- servertime.service.softlayer.com
nats:
user: nats
password: nats-password
address: <IP_ADDRESS>
port: 4222
blobstore:
address: <IP_ADDRESS>
port: 25251
backend_port: 25552
agent:
user: agent
password: agent
director:
user: director
password: director
postgres: &bosh_db
user: bosh
password: bosh
host: <IP_ADDRESS>
port: 5432
database: bosh
redis:
password: redis
address: <IP_ADDRESS>
port: 25255
director:
name: bosh2
address: <IP_ADDRESS>
port: 25555
encryption: false
# Check if the CPI for your IaaS supports snapshots, otherwise disable it.
# As an example vCloud CPI 0.5.2 does not support snapshots
enable_snapshots: false
max_tasks: 100
db: *bosh_db
# If needed, limit the number of threads used to concurrently instantiate new vms (32 by default)
# max_threads: 1
hm:
http:
port: 25923
user: admin
password: admin
director_account:
user: admin
password: admin
intervals:
poll_director: 60
poll_grace_period: 30
log_stats: 300
analyze_agents: 60
agent_timeout: 180
rogue_agent_alert: 180
loglevel: info
email_notifications: false
tsdb_enabled: false
cloud_watch_enabled: false
resurrector_enabled: true
dns:
address: <IP_ADDRESS>
recursor: <IP_ADDRESS>
db: *bosh_db
vcenter:
address: <IP_ADDRESS>
user: Administrator
password: a5pattes
datacenters:
- name: bschmcSL1
vm_folder: mycfvm
template_folder: mycftemplate
disk_path: /cfdir
datastore_pattern: datastore1
persistent_datastore_pattern: datastore1
allow_mixed_datastores: true
clusters:
- cfcluster:

The failure reported is in rendering a director job template:
https://github.com/cloudfoundry/bosh/blob/master/release/jobs/director/templates/director.yml.erb.erb
It looks like you need to provide additional properties, namely
vcenter.datacenters[0].clusters. Your yaml indentation might be wrong. I
can't tell.
-Karl
On Sunday, February 8, 2015, fckbo<EMAIL_ADDRESS><javascript:_e(%7B%7D,'cvml','notifications@github.com');>> wrote:

Hi me again,
I did change my manifest file to remove the warning about the "template"
statement being deprecated when having several components deployed within
the same vm by replacing with a "templateS" statement (in the job section
of the manifest) thinking that it might fixed the problem but unfortunately
it did not & I still have the same error as before when Binding
configuration takes place:
Started preparing configuration > Binding configuration. Failed: Error
filling in template director.yml.erb.erb' forbosh_api/0' (line 332:
undefined method `each' for nil:NilClass) (00:00:00)
Error 100: Error filling in template director.yml.erb.erb' forbosh_api/0'
(line 332: undefined method `each' for nil:NilClass)
Any idea ?
SEE BELOW THE NEW MANIFEST FILE I'M USING
name: bosh2
logging:
-level: DEBUG
director_uuid: 35b5ea35-213b-4494-8fb7-c1c191178824
release: {name: bosh, version: 139}
networks:

name: default type: manual subnets:

range: <IP_ADDRESS>/28 gateway: <IP_ADDRESS> static:

<IP_ADDRESS>
<IP_ADDRESS> reserved: # .224 is special, not sure if I need
to put it in the reserved range
<IP_ADDRESS> - <IP_ADDRESS> # .239 is special, not sure if
I need to put it in the reserved range dns:

<IP_ADDRESS>
<IP_ADDRESS> cloud_properties: name: Private Network - vmnic0
vmnic2

resource_pools:

name: default stemcell: name:
bosh-vsphere-esxi-ubuntu-trusty-go_agent version: 2830 network: default
size: 5 cloud_properties: cpu: 2 ram: 512 disk: 2000

compilation:
reuse_compilation_vms: true
workers: 3
network: default
cloud_properties:
ram: 512
disk: 6000
cpu: 2
update:
canaries: 1
canary_watch_time: 30000-90000
update_watch_time: 30000-90000
max_in_flight: 1
jobs:

name: bosh_data
templates:
- name: blobstore
- name: postgres
- name: redis instances: 1 resource_pool: default persistent_disk:
8_000 networks:
- name: default static_ips: [<IP_ADDRESS>]
-
name: bosh_api
templates:
- name: nats
- name: director
- name: health_monitor
- name: powerdns instances: 1 resource_pool: default networks:
- name: default static_ips: [<IP_ADDRESS>]
properties:
env:
ntp:

servertime.service.softlayer.com

nats:
user: nats
password: nats-password
address: <IP_ADDRESS>
port: 4222
blobstore:
address: <IP_ADDRESS>
port: 25251
backend_port: 25552
agent:
user: agent
password: agent
director:
user: director
password: director
postgres: &bosh_db
user: bosh
password: bosh
host: <IP_ADDRESS>
port: 5432
database: bosh
redis:
password: redis
address: <IP_ADDRESS>
port: 25255
director:
name: bosh2
address: <IP_ADDRESS>
port: 25555
encryption: false
Check if the CPI for your IaaS supports snapshots, otherwise disable it.
As an example vCloud CPI 0.5.2 does not support snapshots
enable_snapshots: false
max_tasks: 100
db: *bosh_db
If needed, limit the number of threads used to concurrently instantiate
new vms (32 by default)
max_threads: 1
hm:
http:
port: 25923
user: admin
password: admin
director_account:
user: admin
password: admin
intervals:
poll_director: 60
poll_grace_period: 30
log_stats: 300
analyze_agents: 60
agent_timeout: 180
rogue_agent_alert: 180
loglevel: info
email_notifications: false
tsdb_enabled: false
cloud_watch_enabled: false
resurrector_enabled: true
dns:
address: <IP_ADDRESS>
recursor: <IP_ADDRESS>
db: *bosh_db
vcenter:
address: <IP_ADDRESS>
user: Administrator
password: a5pattes
datacenters:

name: bschmcSL1
vm_folder: mycfvm
template_folder: mycftemplate
disk_path: /cfdir
datastore_pattern: datastore1
persistent_datastore_pattern: datastore1
allow_mixed_datastores: true
clusters:
cfcluster:

—
Reply to this email directly or view it on GitHub
https://github.com/cloudfoundry/bosh/issues/750#issuecomment-73433277.

may also want to post on<EMAIL_ADDRESS>which has many eyeballs

Karl,
thx a lot that was it!!  Apparently I need to specify a resource pool under the cluster name.
What bugs me a bit is that:

As I said this manifest is working properly with release 912 (but ok things change ...)
but reading the documentation here http://docs.cloudfoundry.org/bosh/vsphere-cpi.html#resource-pools,  it says resource pool is optional:

" clusters [Array, required]: Array of clusters to use for VM placement.
 [String, required]: Cluster name.
resource_pool [String, optional]: Specific vSphere resource pool to use within the cluster."
I actually put the following
clusters:
- cfcluster:
resource_pool: mycf
without creating the resource_pool "mycf" on  vcenter and it worked: Install succeeded, still need to check now that I can deploy new stuff (in fact a CF) on it.
I've got the following questions:

any insights on how bosh uses resource_pool parameter ?

before posting this issue I had done a couple of tries to patch the bosh ruby code with additional logs/traces on the vm running the MicroBosh that is used to deploy my BOSH instance but it did take into account my changes. For example I made some changes in the following file
/var/vcap/packages/director/gem_home/ruby/2.1.0/gems/bosh-director-core-1.2830.0/lib/bosh/director/core/templates/source_erb.rb but none of my new traces were taken in account. I guess it's because some  compilation is taking place to generate the director on the microbosh server when its installation took place so is there anyway to re-generate on the microbosh server itself a module ?

Thank again for your help.

It looks like the vsphere cpi is more demanding than the configuration processing in the director job templates. See the full validation here: https://github.com/cloudfoundry/bosh/blob/master/bosh_vsphere_cpi/lib/cloud/vsphere/config.rb
At some point in the near future the cpi config will go directly to the cpi, rather than going through the director. Hopefully this will make debugging CPI config simpler.
I can't validate your issue arm, but it possible that your yaml was invalid. Did you try one of these?
clusters:

cfcluster

clusters: [cfcluster]
clusters:

cfcluster: {}

As for release changes: microbosh is deployed using a bosh release precompiled into the stemcell, which is non-trivial to modify. We're working on a new bosh-micro cli that handles release compilation itself, but it's not quite ready for public consumption.
The new docs might have more info on resource pools: http://bosh.io/docs/vsphere-cpi.html

@fckbo vsphere cpi options did not change. i think problem with origin manifest is ':' after your cluster name. even though it's valid yaml i think it would trip up one of the validations that vsphere cpi was doing.  i definitely run few of my own env without resource pools and did not have to change that. let us know if that does not work.

karlfi, cppforlife,
thx  a lot for your answers, removing the ':' after cluster make it work without resource pool.
I didn't know anything about bosh few days ago and now go it up & running on two environments with 2 different versions so I kind of like this tool
I'm now trying to make use of it to first deploy jenkins on one environment and then cf on another environment, let see how that goes...
Thx again.


fix: fire selection CHANGE event to correct listener

Summary
This is PR for https://github.com/maxGraph/maxGraph/issues/112
There is breaking change during migration (i think), which resulted to CHANGE event being fired at Graph instead of GraphSelectionModel when cell selection occured. I cheked mxgraph sources and found two places with breaking changes and reverted them.
Description for the changelog
Now CHANGE event is fired to GraphSelectionModel instead of Graph
fixes #112

Hang on @tbouffard - while this may work around the problem, I don't think it necessarily solves the root cause.
As I said in my comment I think I may have (potentially accidentally) changed the first argument provided to SelectionChange may changed to graph: Graph from selectionModel in the original mxGraph.
If that is the case, then I think the argument to the constructor should be changed back to be selectionModel, rather than having graph provided to the constructor and calling this.graph.getSelectionModel() later on.


make error

bonesi make error.

amandeep@amandeep-HP-G42-Notebook-PC:~/Desktop/Test/bonesi/trunk$ make
cd . && /bin/bash ./config.status config.h
config.status: error: invalid argument: `config.h'
make: *** [stamp-h1] Error 1

Please help

Original issue reported on code.google.com by<EMAIL_ADDRESS>on 14 Oct 2011 at 1:56

> checking for libnet.h... no
> configure: error: header missing

Please make sure to install all necessary header files, in this case
libnet1-dev.

Original comment by Markus-Go on 17 Oct 2011 at 8:25

Changed state: WontFix


Add NATS_REQUEST_TIMEOUT

Codecov Report

Merging #14 (9ae8946) into main (e8c4f6b) will decrease coverage by 0.47%.
The diff coverage is 33.33%.

:exclamation: Current head 9ae8946 differs from pull request most recent head fc86685. Consider uploading reports for the commit fc86685 to get more accurate results

:mega: This organization is not using Codecov’s GitHub App Integration. We recommend you install it so Codecov can continue to function properly for your repositories. Learn more
@@            Coverage Diff             @@
##             main      #14      +/-   ##
==========================================
- Coverage   65.07%   64.61%   -0.47%
==========================================
  Files           4        4
  Lines          63       65       +2
  Branches        4        4
==========================================
+ Hits           41       42       +1
- Misses         22       23       +1

Impacted Files
Coverage Δ

nats_client/clients.py
39.28% <33.33%> (+0.82%)
:arrow_up:

:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more


next-sass: Flash of unstyled content only when building for production

Hi!
I've been struggling with a flash of unstyled content "FOUC" issue my entire day, testing various solutions I found online, but none seemed to work for me. The issue is especially visible when using CSS transitions, as the components will be visible without any styles and then transition to their CSS style.
This is only visible when building for production using next build and then next start. In development mode, using next, there is no FOUC issue.
Minimal example:
// next.config.js
const withSass = require('@zeit/next-sass');
module.exports = withSass();

// scss/style.scss
body {
    background-color: red;
    transition: 2s all ease;
}

// pages/index.js
import React from "react";
import "../scss/style.scss";

const Home = () => (

Test

);

export default Home;

GitHub repo: https://github.com/jesperlindstrom/next-sass-fouc/
Video of problem: https://drive.google.com/file/d/12yukgmgsuPKRs0TD2yYZK9F7fBC7oSkF/view?usp=sharing
What am I doing wrong? Thanks!

So... the issue turns out to be a browser bug, not related to Next or Webpack at all. Managed to replicate with ordinary CSS and HTML, where transitions are fired on load.  I'm guesing it makes both the resources "blocking" and therefore waits for first render...
If anyone has the same issue in Next.js, I added this to my _document.js:

...


Refactor hardcoded servlet dependencies

Resteasy has a few places that are dependent on Servlet.  This PR removes those dependencies

I look forward to reading this. As soon as 3.9.0.Final is out the door next week. ;-)


Source startup file command caption not localized

Tested with French language.
"Source startup file" is the caption for F5 on the toolbar.
For reference, I've circled the "Set As Startup R Script" which has been localized already.

Still needs fixing? Looks like a loc bug rather than code bug


New package: InputFiles v1.1.3

Registering package: InputFiles
Repository: https://github.com/OmegaLambda1998/InputFiles.jl
Created by: @OmegaLambda1998
Version: v1.1.3
Commit: 4ca8002eaafa5b01de20835931f55e7d7fc4bb96
Git reference: HEAD
Description: Consistent and powerful input files for julia projects

This can be closed


Refactor: Move seven module into apisix-ingress-controller

I suggest to move seven module into pkg path in apisix-ingress-controller. We can do unified management and testing.

Agree.
It's still convenient if users want to import this package.

Let me do it.


Please, return the feature of prioritization of equipped characters

We don't accept requests of "change it back". Please provide actual feedback or a way to improve on the idea.
Read the following conversation from our Discord where frzyc talks about why it won't change back:
https://discord.com/channels/785153694478893126/785176548428087306/1078155958892638300


GitLab: media loading and uploading broken

- Do you want to request a feature or report a bug?
bug
- What is the current behavior?
Quoting @DavidRayner from https://github.com/netlify/netlify-cms/issues/1565#issuecomment-412331348:

I still have this issue with my site which was based off the hugo starter
I will try to reproduce with the hugo starter upgraded to v2.x

- If the current behavior is a bug, please provide the steps to reproduce.
Quoting @DavidRayner from https://github.com/netlify/netlify-cms/issues/1565#issuecomment-412333598:

I believe this issue still exists on netlify-cms 2.0.9
I made a Netlify site using GitHub and https://github.com/DavidRayner/one-click-hugo-cms. I was able to upload media without any problem.
I made another Netlify site using GitLab and https://gitlab.com/davidrayner/one-click-hugo-cms (an import of the working GH repo) - and I was not able to upload media.

- What is the expected behavior?
Media loads and can be uploaded successfully.

- Please mention your versions where applicable.

Netlify CMS version: 2.0.9
Browser version:

Node.JS version:
Operating System:
- Please link or paste your config.yml below if applicable.

For some reason, Redux is getting a MEDIA_LOAD_FAILURE. This line is then undefined:
https://github.com/netlify/netlify-cms/blob/f801b192211b1e1953ced969a3093eab9e04e14d/packages/netlify-cms-core/src/actions/mediaLibrary.js#L84

Media loading is currently failing at this line:
https://github.com/netlify/netlify-cms/blob/412d1e629f22d98c7806280780687fec016350ff/packages/netlify-cms-backend-gitlab/src/implementation.js#L137
new URL() only works on absolute URLs, so it is failing whenever fileDownloadURL returns a non-absolute URL.

This will be fixed by #1433.


Any plan to support Bitflyer and Coincheck?

no plans yet.

Bitflyer streaming support https://github.com/bitrich-info/xchange-stream/pull/27

@winwish Would you be willing to donate a bounty?

After I receive the postcard from them to pass verification, I think I can donate some or share with someone with the same needs.

bitmex too

If you are only interested in public (market data) API, the xchange-stream (websocket) supports Bitflyer and Bitmex now

hey, does anyone has any updates on Bitflyer implementation? I intended to start the implementation, but I have difficulties enabling the API keys.


coreos-ssh-import-github causes network failure on DigitalOcean

When you use the coreos-ssh-import-github to create SSH key's on DigitalOcean, SSH'ing into a droplet times out. Reproducible consistently.

@bobbytables can you look at the machines console and see if it has a publicly accessible ip?

bug spotted. coreos-cloudinit tries to pull the keys from github while setting up users before configuring the interfaces, and when the requests to github fail, cloudinit aborts, leaving you with the network unconfigured.
see https://github.com/coreos/coreos-cloudinit/blob/master/initialize/config.go#L45
cc @crawford

Same root cause as https://github.com/coreos/coreos-cloudinit/issues/215. This class of bugs is due to a deep design flaw. In some scenarios, coreos-cloudinit is responsible for configuring the network; in others, it depends on the network.
My suggestion would be to include your key directly in the config via ssh-authorized-keys. The coreos-ssh-import-github feature really should have never been introduced, but it has been kept for backward compatibility. :(

Cool thanks :)

I ran into the same issue where on bare-meta, the CoreOS user directive ran before our *.network units where processed, resulting in a timeout when using coreos-ssh-import-github.
We'll be solving it by using ssh-authorized-keys. Too bad network units can't be loaded before the users configurations are set.


[WIP] 0.11.1

Various small fixes which should go into the next release

[ ] Fix screenshots on cocoadocs.org

This looks good! Any thought on directing users to SQLiteMigrationManager in the docs for more advanced migration needs?

Yes, only concern is that it hasn't been updated in a while. I know the developer, maybe I'll give him a nudge.

@stephencelis OK, there will be an update of the migration manager soon. once that's done I'll add it to the docs.

Ah nice! Otherwise I am totally cool with removing it if/when it's unmaintained.

To fix images on CocoaDocs: https://github.com/CocoaPods/cocoadocs.org/issues/482


Make it so that an instance of xnd has the type of an instance of ndt

This means that the following code works:
t = ndt('int32')
arr = xnd(5, type=t)

assert arr.type == type(arr)

Blocked by #1


test: pull testbench docker image, kokoro presubmit conformance test …

…hooks
Thank you for opening a Pull Request! Before submitting your PR, there are a few things you can do to make sure it goes smoothly:

[ ] Make sure to open an issue as a bug/issue before writing your code!  That way we can discuss the change, evaluate designs, and agree on the general idea
[ ] Ensure the tests and linter pass
[ ] Code coverage does not decrease (if any source code was changed)
[ ] Appropriate docs were updated (if necessary)

Fixes #<issue_number_goes_here> 🦕

There is currently a conformance-test.yaml that appears to run the tests on every pull request. However, it seems like most other tests / workflows use the .cfg / .sh approach. Not sure which is better and if we should just remove the older yaml file?

This looks good to me, but you should also request review from someone who actually knows how this is supposed to work.


Create a promote command

Instead of removing a player and and having to readd them create a promote command.

https://github.com/jjj5311/NameLayer/commit/17436aac232e1f410d663c2916a9c4f0581c7613

This is not quite the same as the other duplicate closed suggestion, unless you also add a DEmote command.  So if this is the way you are addressing it, please put in both. Just making sure.

@GavJenks  this would provide both


fix failing 503 test

I think I know why this was passing for everyone and Travis before. While the mock is clearly wrong, since there's no API running on Travis, the real data_api_client was returning the expected 503 after failing to connect to the API. ./scripts/run_tests.sh doesn't set the Data API URL variable, so the test would fail to connect to the API even if it's running locally on the standard port.
But, if you launch the API and export the API URL variable for the supplier-frontend tests (which is what Andrew did following our README) the client connects to the API and returns 404 instead of 503.
:+1:, happy we caught this, but we should think about what we can change in the apiclient so that it never makes actual requests during test runs.


User can set their preferred shifts

See class UserShiftDefaultRequest in model.py

This is no longer relevant given change in the model


Get access token using Microsoft.Azure.Services.AppAuthentication in a container

I've got a docker container using the AzureServiceTokenProvider to get an access token to access key vault but it's not working. I'm getting the following exception message:
Parameters: Connection String: [No connection string specified], Resource: https://vault.azure.net, Authority: https://login.windows.net/{GUID}. Exception Message: Tried the following 3 methods to get an access token, but none of them worked.
Parameters: Connection String: [No connection string specified], Resource: https://vault.azure.net, Authority: https://login.windows.net/{GUID}. Exception Message: Tried to get token using Managed Service Identity. Unable to connect to the Managed Service Identity (MSI) endpoint. Please check that you are running on an Azure resource that has MSI setup.
Parameters: Connection String: [No connection string specified], Resource: https://vault.azure.net, Authority: https://login.windows.net/{GUID}. Exception Message: Tried to get token using Visual Studio. Access token could not be acquired. Environment variable LOCALAPPDATA not set.
Parameters: Connection String: [No connection string specified], Resource: https://vault.azure.net, Authority: https://login.windows.net/{GUID}. Exception Message: Tried to get token using Azure CLI. Access token could not be acquired.

I'm not sure if the nuget package should be working inside a docker container I start up using Visual Studio (docker-compose).

Anyone have an idea if this should be working or if this is not supported currently?

@Zenuka please give a test drive for this cli tool https://www.nuget.org/packages/appauthnetication/#

To use the app auth library in a container on local machine, you will need to set env variables to use an explicit service principal credential. https://docs.microsoft.com/en-us/azure/key-vault/service-to-service-authentication#running-the-application-using-a-service-principal


cotyledon development

13.cotyledon development ISA embryonic development
(sensu Magnoliophyta) GO:0009793
Def: The process whose specific outcome is the
progression of the cotyledons over time, from their
formation to the mature structure.
Ref: TAIR:tb
Also add ‘cotyledon morphogenesis’ as a child of this
term.
Reported by: jenclark
Original Ticket: "geneontology/ontology-requests/3222":https://sourceforge.net/p/geneontology/ontology-requests/3222

thanks www.movied.org


SILGen: Remove unnecessary assertion when emitting conformances

Asserting that a conformance is "complete" before emitting its witness table during SILGen is unnecessary since the typechecking request architecture already handles checking a conformance lazily as needed.
Resolves rdar://117439077

@swift-ci please smoke test


Table of Contents is too long maybe make it a collapsible section

Table of Contents is too long maybe make it a collapsible section  .
Just like shown below.
https://github.com/sudheerj/reactjs-interview-questions/assets/68190549/ecb2f42a-aee7-4c4d-b058-8d655ef7a351
Above video from this gist :  https://gist.github.com/pierrejoubert73/902cc94d79424356a8d20be2b382e1ab#how-to-add-a-collapsible-section-in-markdown

The table of contents is helpful to see all the questions at the same time. If we close it by default, reader may not get idea to expand them.

Can we open it by default ? readers can choose to close if they want.

In Markdown, you can create collapsible sections like the one you've shown
using HTML  and  elements, just as you've demonstrated in
your example. Here's how to do it:

Use  and : These HTML elements are used to define the
collapsible section. The  element is the clickable header that
users will click on to expand or collapse the content.
2.
Place your content inside the  element: You can include any
Markdown content, such as headings, lists, code blocks, or paragraphs,
within the  element. This content will be hidden by default
when the section is collapsed.
3.
Keep the  element concise: The  element should provide
a brief and meaningful label for the collapsible section. Users will click
on this label to toggle the visibility of the content.
4.
Use indentation: While it's not required, indenting the content within
the  element helps improve readability and maintainability,
especially for larger sections of content.
5.
Use backticks for code blocks: If you want to include code blocks, as
you did in your example, use triple backticks (```) to define the code
block and specify the language (e.g., js for JavaScript).
Remember that the support for HTML in Markdown may vary depending on the
platform or renderer you're using. Most Markdown renderers should support
 and , but it's a good idea to test your Markdown
documents in the specific environment where you intend to use them to
ensure proper rendering and interactivity.
On Tue, Oct 3, 2023 at 8:24 PM Sahil bakoru  @.***>
wrote:

Closed #273
https://github.com/sudheerj/reactjs-interview-questions/issues/273 as
completed.
—
Reply to this email directly, view it on GitHub
https://github.com/sudheerj/reactjs-interview-questions/issues/273#event-10539612218,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/A7GHGHU5MC4S3ZU4BXJXGALX5QRKRAVCNFSM6AAAAAA5KZPOAGVHI2DSMVQWIX3LMV45UABCJFZXG5LFIV3GK3TUJZXXI2LGNFRWC5DJN5XDWMJQGUZTSNRRGIZDCOA
.
You are receiving this because you are subscribed to this thread.Message
ID:
<sudheerj/reactjs-interview-questions/issue/273/issue_event/10539612218@
github.com>

chat GPT is that you ?

Ok i will send you tomorrow
On Tue, 3 Oct, 2023, 10:43 pm Sahil bakoru , @.***>
wrote:

Reopened #273
https://github.com/sudheerj/reactjs-interview-questions/issues/273.
—
Reply to this email directly, view it on GitHub
https://github.com/sudheerj/reactjs-interview-questions/issues/273#event-10541213730,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/A7GHGHXBP5UPOC4X27VT6S3X5RBU7AVCNFSM6AAAAAA5KZPOAGVHI2DSMVQWIX3LMV45UABCJFZXG5LFIV3GK3TUJZXXI2LGNFRWC5DJN5XDWMJQGU2DCMRRGM3TGMA
.
You are receiving this because you commented.Message ID:
<sudheerj/reactjs-interview-questions/issue/273/issue_event/10541213730@
github.com>

I have made a pull request  for that, video and code is also there.
check the pull request : https://github.com/sudheerj/reactjs-interview-questions/pull/274

@sahilbakoru Thanks added


Fix superset cli for python3

While at it avoid cleanup the code a bit.

Ooops. Thanks for fixing this.


Do not require moment.js

Expected Behavior
Chart.js requires moment.js but only uses some of its functions. The moment.js size is too large for production. I want to reduce the bundle size by using a date-time library supporting tree-shaking
Current Behavior

I have a problem with the bundle size of moment.js in production. Moment.js does not support tree-shaking so its size is kinda overwhelming.
Possible Solution
Using date-fns instead of moment.js. Date-fns offers similar APIs and support tree-shaking. There are some comparisons between date-fns and moment.js

https://github.com/date-fns/date-fns/issues/275#issuecomment-264934189
https://github.com/date-fns/date-fns/issues/275#issuecomment-264941412
https://github.com/moment/moment/issues/2373#issuecomment-230478550

Context
Chart.js is the only library requiring moment.js in my application. I did some searches and date-fns seems to be a decent choice.
Environment

Chart.js version: 2.5.0
Browser name and version: Chrome v59.0.3071.29

I think lack of time zone support would be the main obstacle
But this brings up another good point. It seems like it'd be helpful for chartjs to support tree shaking. If I'm only using one chart type then why should I have to include the code for all chart types? I believe moving to ES6 modules would fix that. Perhaps we should have a separate issue to track that

@benmccann not sure we need a new ticket, I'm already on reorganizing the - weird - require() strategy in order to migrate to ES6 modules and finally switch to Rollup instead of Browserify. Tree shaking would be great for external dependencies, but we don't want to get rid of our own methods that are not referenced in the main repo (e.g. deprecations or methods used by external modules).
I remember a few tickets that suggested other date/time libraries: an idea would be to have our own time/date wrapper and provide a few adapters to popular libs such as moment or date-fns. The adapter could be automatically selected based on some global detection or enforced by the user.
And maybe we should deprecate the Chart.bundle.js?

Oh, that's awesome that you're already working on a migration to ES6 modules.
Btw, I wasn't suggesting been would tree shake our own modules. Rather that if we use ES6 modules then end users can tree shake out chartjs modules that they don't need.

Agree, that would be convenient, though I think it's for "advanced" users that want to build the lib by their own. For others, it would be great if Chart(.min)?.js could detect if a compatible date/time lib is already loaded by the user and use it. But also allow users to write custom adapter for their preferred date/time lib.

Funny that #4461 got filed about this very topic today

Does chart.js use moment timezone? How does a chart library require timezone support? Date/time library adapters are expensive, IMO. Anyway, tree-shaking is kinda inconsistent across bundlers. E.g. Webpack cannot prune unused pure imports, rollup can.

Chart.js doesn't use time zone itself, but It looks like some people use the client-side time zone support that moment provides to format/parse chart.js labels. E.g.: https://stackoverflow.com/questions/40891462/chart-js-display-control-timescale-time-zone/41715066#41715066
It would be cheaper from a library size perspective to do any timezone handling on the server side, so I'd be fine advising people to do that instead.

By expensive I mean, the burden of building adapters which supports a variety of date/time libraries should not be on the Chart.js end.
If users want to manipulate the labels, they should use their own library.

I wasn't thinking writing tons of adapters, but at least one (moment.js?) and accept contributions from users who want to interface with another lib. The idea behind this would be to keep the Chart.js code independent of any third party date/time lib and allow users to make their project depends on whatever lib they want.
Because right now, switching to another lib may be a breaking change for external charts/plugins and I would prefer not to have to change again for a better library if someone else think that finally Chart.js shouldn't use date-fns :)

For example: #3533

I understand the benefit of adapters here. There is a small difference between injecting a date/time library and my proposed approach.
If we offer adapters, at some point in the future, chart.js will end up with a dozen of adapters and the problem of bundle size may not be resolved as people will keep injecting the whole date/time library into chart.js.
So instead of a library, we use standalone functions, e.g. format(), parse (which are provided by date-fns or any library). We don't have to care about those libraries anymore.

So why do I keep insisting on date-fns? Because of tree-shaking / function separation.
import {format, parse} from 'date-fns/esm' // This works

import Format from 'date-fns/format' // This
import Parse from 'date-fns/parse' // And this also work

date-fns looks great indeed, let's have a look at it after we switch to ES6 module. We will also need to make sure it doesn't break external code.

Hope it arrives soon. I will have my own fork of chart.js-no-moment.js for now.

Sounds good, can you share your repo/branch once ready, I'm curious to see what really means switching to another date/time lib :)

Yep. Looking forward to your feedbacks when it's done.

@hiendv can you publish your fork with no moment? Or comment on how to do that?

To help with the switch, I've created a gist of every instance of moment within Chart.js
https://gist.github.com/merlinpatt/9925bbac94b0c91f1430c2de1569bb26

Just wondering whether this is still needed as momentjs is now moving to ES6

Can you share an issue or pull request that describes moment's move to es6? I wasn't aware of it and am not familiar with the details

Whether it's needed depends on if the switch to ES2015+ will include tree shaking.

Refer to https://github.com/moment/moment/#port-to-ecmascript-6-version-2100 and also the package.json in the jsnext:main property.
You should be using import from 'moment/src/moment.js' rather than just 'moment'

@beeing It doesn't support tree-shaking. So for example, if you only want to use function now() you have to import like this
import { now } from 'moment/src/lib/moment/now'
console.log(now())

It's a pain in the ass because they have a number of entry points
https://github.com/moment/moment/blob/2.19.2/src/moment.js

Thanks for the info. The import path is fine as we are used to it.

@beeing I don't think you fully understood the problem here. You have to trace for a particular function by traversing a number of imports. And moment is not even pure-function. E.g. Could you exclusively pick the function format alone?

Ok, got you. Well, I think this issue should be raised to moment itself.
However, good to point out for others to understand the limitations.
Thanks.

Yes, there is an issue raised with moment: https://github.com/moment/moment/issues/2373

@benmccann Well, it has clearly taken time and will eventually be a breaking change. I see no reason why we haven't switch to date-fns already.

@hiendv I don't have preference for the date/time lib we integrate as long as it doesn't introduce breaking changes (including external code such as plugins, custom charts, etc.) - else it would need to wait until 3.x. It should also makes sense to switch (e.g. be a lighter and/or faster lib) but I guess that's the case with date-fns (unless it's not because we don't support tree shaking right now?!).
I can't find repo/branch where that switch to date-fns has been implemented, is there anywhere we can check to figure out these changes?
BTW, there is an open PR to add support for timezone (#4843), is that possible with date-fns as well?

There's a new Moment project Luxon, which is much smaller, immutable, etc. and might be a pretty good alternative to Moment for us to consider: http://moment.github.io/luxon/. It has timezone support , so could be better than date-fns as well

@benmccann definitely worth investigating luxon as part of this discussion

@simonbrunel It will take a while but I will try my best in the next couple of days. Timezone support may be a challenge.
@benmccann I don't think luxon is a good competitor because of its nature. It's too object-oriented, not pure-functional.
Same as described in this comment

All the options seem sub-optimal to me

Luxon is still a bit large - https://github.com/moment/luxon/issues/94
date-fns doesn't have timezone support yet - https://github.com/date-fns/date-fns/issues/479#issuecomment-346479071

I think the best thing to do in the short term is remove moment from our APIs to make it easier to switch between implementations.
I'd also love to see someone copy Luxon's timezone support into date-fns as that seems like the solution would best meet our needs.

Wouldn't it be possible to design some kind of adapter interface, containing the date-related methods actually needed by chart.js, and provide various implementations of this interface (based on luxon, moment, date-fns, etc.). That way, people who don't need date support in charts don't even need to configure any adapter, and people who need it can use the adapter implementation they want, based on the library they're (probably) already using in their own code.

I've sent a PR to date-fns to add timezone support there, which would be required before we could consider supporting it here

Here's another project that abandoned moment for datefns and luxon: https://github.com/dmtrKovalenko/material-ui-pickers/pull/218. It's looks like they made a pluggable interface so users can switch between the three. That might be a path forward to consider here

I've sent a PR to add support for Luxon: https://github.com/chartjs/Chart.js/pull/5522. This is a big improvement over Moment and a much easier switch to make than date-fns because the API is so similar
Luxon is much smaller than Moment and adds timezone support, which will allow us to fix existing timezone bugs and add new functionality. I've also been working to help make Luxon even smaller than it currently is. There's a 2.0 branch of Luxon where some work has started to help allow additional tree shaking (though it will never be as shakable as date-fns)
date-fns is not well maintained and does not support timezones, so I'm not sure I want to add a dependency on it. I sent a PR to add timezone support to it months ago and there's been basically no movement. It seems there's a positive reaction to the approach I was taking, but just a lack of maintainer time to review any PRs

@dmtrKovalenko (creator of material-ui-pickers) has recently split out his date abstraction library: https://github.com/dmtrKovalenko/date-io.
Maybe this is something to consider?

@geirsagberg that looks fantastic! We will absolutely consider it. I have a few questions about it that I left in the project's issue tracker to understand how / if we can use it

Sorry but It is not clear to me, do exist a way to use chart without moment?

@ciaoben Not at the moment (heh). Using a similar approach to the repo I linked earlier should make it possible, but I imagine it will require quite a bit of effort.

I moved to babel-plugin-transform-vue-jsx.

Is there any quick workaround ? I do not use  graphs  with date, so I really don't need moments and I would like to reduce size of module. How can we found  quick workaround ?

@ciaoben, @lsn793:
While we wait for the much anticipated 2.8 release, one quick hack you can do is exclude the moment locales if you use webpack:
plugins: [
  new webpack.IgnorePlugin(/^\.\/locale$/, /moment$/)
]

At least for me (as someone who doesn't use time charts), it cut the moment bundle size by about 73%, saving me roughly 180KB.
My apologies if this isn't 100% germane to the discussion, just something I haven't seen on the various moment.js threads, and I thought folks might benefit.

Hi Team,
I had started using react-chartjs-2 for charting needs in my react app. Although i used the suggested npm command to install react-chartjs-2 and chart.js; I am facing a build error of like right after adding import statement from react-chartjs-2.
Error is something like : requirejs compile (requirejs task) : Error ENONENT: No such file or directory open '...........temp\moment.js.
Then I have done npm install moment --save as well but still error persisted. Any suggestion please.

HI All,
Getting above error while importing from react-chartjs-2. Any suggestion please on how to solve it.

@ciaoben, @lsn793:
While we wait for the much anticipated 2.8 (or 3.0?) release, one quick hack you can do is exclude the moment locales if you use webpack:
plugins: [
  new webpack.IgnorePlugin(/^\.\/locale$/, /moment$/)
]

At least for me (as someone who doesn't use time charts), it cut the moment bundle size by about 73%, saving me roughly 180KB.
My apologies if this isn't 100% germane to the discussion, just something I haven't seen on the various moment.js threads, and I thought folks might benefit.

I can confirm that this works. I think it's quite an elegant solution too!

For WebPack 5, I had to use this:
plugins: [
  new webpack.IgnorePlugin({
    resourceRegExp: /^\.\/locale$/,
    contextRegExp: /moment$/
  })
]

From webpack docs.

For WebPack 5, I had to use this:
plugins: [
  new webpack.IgnorePlugin({
    resourceRegExp: /^\.\/locale$/,
    contextRegExp: /moment$/
  })
]

From webpack docs.

I'm using just donut chart, no need of moment at all, so removed it completely:
new webpack.IgnorePlugin({
   resourceRegExp: /moment$/,
}),

1mb less of dependencies :+1:

I'm using just donut chart, no need of moment at all, so removed it completely:
new webpack.IgnorePlugin({
   resourceRegExp: /moment$/,
}),

1mb less of dependencies :+1:


Handle multiple peers for the same account address

Contacts -> Peers, Cards -> Contacts
I think this makes a lot more sense now. Peers map to IPFS peers. A Contact can contain multiple peers.
Fixes #565
Fixes #531

TODO:

[ ] Build contacts from search results
[ ] Finish #531

Feeling good about this one. Sadly, the multi-contact thing required some actual refactoring. I tried two quick hacks (which ended up wasting time) before biting the bullet and addressing it head on. Now there is a clear distinction between Contacts and Peers. However, the API only exposes Contacts.

Objections to merge? Hard to properly review this guy cause of all the small changes, but the deets are covered in the targeted issues: #565, #531


torch  extra requires for safetensors dep

This change is needed, otherwise numpy won't be installed. See https://github.com/huggingface/safetensors/blob/079781fd0dc455ba0fe851e2b4507c33d0c0d407/bindings/python/pyproject.toml#L35

The docs for this PR live here. All of your documentation changes will be reflected on that endpoint. The docs are available until 30 days after the last update.


Run command 'helm lint my-chart-v1.0.0.tgz', the check passes, is 'v1.0.0' a valid semantic version number?

The Chart.yaml:
apiVersion: v1
appVersion: "1.0"
description: A Helm chart for Kubernetes
name my-chart
version: v1.0.0
helm lint my-chart-v1.0.0.tgz, output:
==> Linting my-chart-v1.0.0.tgz
[INFO] Chart.yaml: icon is recommended
1 chart(s) linted, no failures
my helm version is v2.16.9, is 'v1.0.0' a valid semantic version number?

Helm 2's support lifecycle ended on November 2020. See the blog post for more details.


When renaming MD file, option to NOT automatically add the path prefix to all linked attachments

Using Obsidian 1.7.1 + Plugin version 4.9.3
At some point the behavior was introduced that inserts the path prefix in front of all existing linked images upon renaming the .md file. This adds a lot of unneeded characters to the notes and clutters them. I would prefer if this did not happen, or at least was an option that could be toggled off.
Example (filename: Foo Test Abc123.md)
Content Before
foo
bar
![[IMG-20240829073246779.png]]
![[IMG-20240829073246780.png]]
![[IMG-20240829073246781.png]]
quux

Then, file is renamed to Foo Test Xyz456.md...
Content After
foo
bar
![[attach/Foo Test Xyz456/IMG-20240829073246779.png]]
![[attach/Foo Test Xyz456/IMG-20240829073246780.png]]
![[attach/Foo Test Xyz456/IMG-20240829073246781.png]]
quux

Fixed in https://github.com/RainCat1998/obsidian-custom-attachment-location/releases/tag/4.9.4

@mnaoumov There seems to be a problem: I just tried it on a note with about 12 images. When I renamed the note filename, only about 1/2 of the linked images stayed as relative filenames, the others all got the full ![[attach/path/to/file/... prefix prepended to them.
Maybe be a race condition?

@mnaoumov I just made a screen recording of this... seemingly random so looks like a missing await somewhere maybe? I didn't check
https://github.com/user-attachments/assets/0f0e5e10-6330-4702-ac29-62039da71760

Fixed in https://github.com/RainCat1998/obsidian-custom-attachment-location/releases/tag/4.10.0


Added span for external file errors

This adds spans for all errors that occur in files outside of Typst's source files (i.e SVG images, external JSON, etc.)
This required quite a laundry list of changes, including to the test framework most notably:

allow external path with syntax // Error: "/path/to/external/file" 3-5 ...
allow using raw byte addressing // Error: "/path/to/external/file" #3-#5 -> this is needed for handling of edge cases where errors occur on line breaks, a bit annoying, if you find a workaround, let me know

And then changes in all of the image decoding (for SVG), and all of the loaders (csv, json, xml).
There are likely stuff left to do and discussions to be had, but now I am going to bed.

Ok, I fixed all of the current code review items ;)

@laurmaedje I didn't have time to finish it last week in the end, thanks for the review, I come back from a work trip on Thursday evening so I'll try and get to it maybe on Friday :)

Sounds good, no rush


no sound from usb sound card

Dear all thank you for your exceptional work in this project.
I just installed version 2.0 via the one line install script and everything seems to work except the sound from the usb sound card.
I already tried:
I installed version 2.0 and everything seems to run except my usb sound card
I tried all hints from https://learn.adafruit.com/usb-audio-cards-with-a-raspberry-pi/testing-audio but the sound card does not appear when trying the commands dsmeg ...
then I change sound usb from 2 to 0 as explained in the install section but it still does not work
Does anyone have an idea where to fix?
Thanks in advance!
IZooRz

Please check #973 as Raspberry Pi changed the audio behavior recently.

Please check #973 as Raspberry Pi changed the audio behavior recently.

Thanks s-martin. Honestly i am a litte lost in the #973. Do you have a hint what to try exactly?
Thank you!

I just tried https://github.com/MiczFlor/RPi-Jukebox-RFID/wiki/Troubleshooting-FAQ#audio-is-not-working and have now a starting up sound ;-)
The problem was, that in in the example one would have to change the output to 1 but my usb card has the 0 and now I have change that and it works!!!
Thank you very very much for the impressive project.
IZooRz

The Box is running


add a cookie consent

with link to http://cookiesandyou.com

Hi, sorry for the delay in looking at this.  I'll have a look and be back in touch shortly.

I've just checked and my site which uses pretty much the default Hugo Smorg theme does not create any cookies. I'll double check but this may not be a necessary change to the base theme.


[FYI] I made a fork you might be interested in

Hi.
I wanted to inform you I forked your watchface, but since my repo contains multiple watchface, I don't know how to link your repo to mine.
I made a lot of changes. The most prominent is that it compiles with a standard Watchy lib (it uses a secondary settings file).
The rest of the "changelog" :

Translatable (committed in French, FYI)
Added local weather support (with Wifi)
Added different modes (light/dark themes, showing values or not, 12h/24h (to look like an analog watch)). You can change between them with up/down buttons
Battery is the central circle
Moon and weather are fonts (so, vector-ish images)
Added daylight thin circle on minutes too, when you are in the right hour

Anyway, you can take everything you want from my fork, it's MIT after all :)
Just beware, if you pick and choose, I adjusted the radiuses of the circles to fit everything, so might not be copy-pastable out of the box.
But I have a question : since my version can compile with the standard lib, I thought of submitting it for it to be displayed at https://watchy.sqfmi.com/watchfaces/. But since there is still a lot of your code in there, I felt it wrong doing it without talking to you first.
So, how do you want to proceed ? You can integrate my change in yours and do it yourself. Or just the "hack" of the second setting file, and do it too. Or I could do it with my version. Or you need your name to be more prominently displayed. Or I just don't submit it.
The choice is yours, truly and fully :)
Oh and, obviously, the URL : https://github.com/Cqoicebordel/Watchfaces/tree/main/Orbital
Cheers !

Feel free to submit - I'm just throwing out concepts. Though, as the issue says, you might want to give yourself a bit to figure out the detail number alignment issue.


Does not list necessary DNS records

The following article specifies various DNS records and where they need to point:
https://support.microsoft.com/en-us/help/2566790/troubleshooting-skype-for-business-online-dns-configuration-issues-in
.this article (that I'm commenting on now) mentions alternate DNS records and mentions IPs.  It does not however say for example. what _sip._tls.<domain> should be pointing to.
Net result - DoD customer do not know what to setup DNS to point to and it's generating Critsit cases to support (me).

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

ID: 58bf69f3-b268-a5e6-2db8-63c496137226
Version Independent ID: d8449616-ae9c-1b7b-224b-9f3f12d8a669
Content: Office 365 U.S. Government DoD endpoints
Content Source: Enterprise/office-365-u-s-government-dod-endpoints.md
Service: o365-administration
GitHub Login: @JoeDavies-MSFT
Microsoft Alias: josephd

@JoshJ-MSFT - thank for the feedback, I'll get this over to the Enterprise content team for investigation.

@JoshJ-MSFT Moving this as a discussion inside Microsoft. Thanks for letting us know.


Vagrant ubuntu 14.04 admin panel not working

installation worked, but admin panel not  working ( whoops something went wrong)
I am trying to run pagekit using vagrant ( host: virtualbox 5 & ubuntu 14.04, guest : 14.04) .
problem 1)
initially installation was not successful error message in browser was "Whoops something went wrong" .
Solution : i checked in apache logs ( /var/log/apache2/error.log ) ,  permission denied to tmp folder , I run " sudo chmod 777 -R /var/www/pagekit/tmo "  .. it worked.
installation created database successfully.
Problem 2: when i tried to open admin panel after installation,   now the same problem again "Whoops something went wrong " , i couldn't see anything now in error log (/var/log/apache2/error.log).
Any help please?
Technical Details

Pagekit version: 1.0.1
Webserver: apache 2.4.7
Database: mysql
PHP Version: 5.5.9

Troubleshooting

[x] I have enabled debug mode: /etc/php/apache/php.ini
[x] I have verified the server requirements: https://pagekit.com/docs/getting-started/requirements
[x] I have tried disabling all installed extensions
[x] I have checked the browser developer console for http errors ( 500 )

Please enable Pagekits debug manually in the /config.phpfile like described here.

thank you @MalteScharenberg
i could see file_put_contentns failing while writing cache data

Fixed
If you're running apache, then you can update the user to 'vagrant' by editing the following file (/etc/apache2/envvars) like below:
Find this section
export APACHE_RUN_USER=www-data
export APACHE_RUN_GROUP=www-data
And change it to
export APACHE_RUN_USER=vagrant
export APACHE_RUN_GROUP=vagrant
the following helped me to sort out this.
http://stackoverflow.com/questions/30854013/vagrant-file-put-contents-permission-denied


Added Domain

Rapid7 indentifies googlecm.hit.gemius.pl as a crypto web miner domain

I added this site to recent update.
Thank you!


BUG - Bot Profile Images are not loading

Summary
When automatic reminder messages, reports get posted profile images of the bot is not getting loaded.
Expected behavior
Profile images should load.
Observed Behavior
Profile images not loading.
Screenshots

Environment

Mattermost version: 5.10.0
OS:  Windows 10 Pro
Platform: browser, desktop app
Browser (if applicable): chrome

@Nisarg10 this is a but with Mattermost v5.10 as discussed in #12.
You'll need to disable image proxy under System Console > Files > Storage > Enable Image Proxy.

Let me know if you still face the issue.

@harshilsharma63 Thank you. Disabling image proxy worked.


An minor compile error occurred after building the generated solution via VS2017.

Please answer these questions before submitting your issue.
What version of gRPC and what language are you using?
https://github.com/grpc/grpc master
C++ VS2017
What operating system (Linux, Windows, …) and version?
Windows10 Home
What runtime / compiler are you using (e.g. python version or version of gcc)
VS2017
What did you do?
I did the operations according to the document  https://github.com/grpc/grpc/blob/v1.11.x/INSTALL.md
(except that I using VS2017 instead for the step: cmake .. -G "Visual Studio 14 2015" -DCMAKE_BUILD_TYPE=Release)
And then built the generated grpc.sln in VS2017, an compile error occurred
Error	C2001	newline in constant	crypto_test_data	c:\cppworkspace\grpc.build\third_party\boringssl\crypto_test_data.cc	2612
After I fixed the compile error by inserting the " before , at the line, I built the solution again without any compile error.
What did you expect to see?
No compile error should occur.

By default, Visual Studio detects a byte-order mark to determine if the source file is in an encoded Unicode format, for example, UTF-16 or UTF-8. If no byte-order mark is found, it assumes the source file is encoded using the current user code page, unless you have specified a code page by using /utf-8 or the /source-charset option. Visual Studio allows you to save your C++ source code by using any of several character encodings. For information about source and execution character sets, see Character Sets in the language documentation.
but, how to add  "/source-charset:utf-8" option?

fix：

Download zip version of boringssl-chromium-stable branch from https://github.com/google/boringssl/tree/chromium-stable

Unzip the tarball: boringssl-chromium-stable.zip and rename the folder from "boringssl-chromium-stable" to "boringssl"

Delete "boringssl" folder from  "gRPC\grpc\third_party", use the new unzipped "boringssl" instead.

build

I tried this way, it works. so I guess the "boringssl" submodule should be updated to latest commit.

We've updated the submodules now. Please re-open a new issue if it's still an issue.


Updated to SCP format version 1.6.

And added correct checksum calculation.

I reworked the patch series and committed to master.


Add possibility to invalidate form in onvalidate hook

We have an adyen form that contains a confirmation checkbox (Terms) at the end and I want to be able to enable submit button only when this checkbox is checked.
If I could invalidate form in onvalidate hook that would be great.
I suggest that in the callback it could be done by simply returning false if one wants the form to be invalidated.

Then of the part of disabling submit button should be moved after onvalidate hook is fired.

One workaround to this problem is to check condition in onvalidate and reenable submit button.

Hi @mieszko4,
In my work, we have the same problem.
We need to enter with the anti-fraud fields in the adyen form.
Have you solved this problem yet? What do you did?

@espudaro I did it with ref. In my case I wanted to make sure that checkbox for terms and conditions is checked.
onvalidate: (e) => { // make sure submit is enabled only when agreedStatus is checked
  if (e.valid && !this.state.agreedStatus) {
    this.refs.submit.disabled = true;
  }
}

let btn = (<input
  type="submit"
  value="Send"
  disabled={!this.state.agreedStatus}
  ref="submit"
/>);


@slidy/svelte - Improve template accessibility

Current implementation of the svelte template uses valid semantic markup, aria attributes and all controls are focusable etc. Used information from WAI ARIA and this post.


Strip trailing slash from base url in SpecialCoverageLoader

Coverage remained the same at 86.41% when pulling fded41958bd26d2a717a04b8e3000f126f3ebc8f on fix-special-coverage-loader into 970e3070a2241bf5851d076a259caf6a53993c0c on master.

Coverage remained the same at 86.41% when pulling fded41958bd26d2a717a04b8e3000f126f3ebc8f on fix-special-coverage-loader into 970e3070a2241bf5851d076a259caf6a53993c0c on master.

Coverage remained the same at 86.41% when pulling fded41958bd26d2a717a04b8e3000f126f3ebc8f on fix-special-coverage-loader into 970e3070a2241bf5851d076a259caf6a53993c0c on master.


support for nomad

I try to use cvmfs through CSI Plugin in nomad, but I encounter problems when creating volume it seems that the access_mode parameter configured in nomad is not supported
here is my volume config file:
type = "csi"
id   = "cvmfs-volume"
name = "cvmfs-volume"

plugin_id = "cvmfs0"

capability {
  access_mode     = "multi-node-reader-only"
  attachment_mode = "file-system"
}

mount_options {
  fs_type = "cvmfs2"
}

secrets {}

the error info:
root@ubuntu:~/nomad-jobs# nomad volume create cvmfs.volume.hcl
Error creating volume: Unexpected response code: 500 (1 error occurred:
        * controller create volume: CSI.ControllerCreateVolume: volume "cvmfs-volume" snapshot source &{"" ""} is not compatible with these parameters: rpc error: code = InvalidArgument desc = volume accessibility requirements are not supported)

Can you provide an example of using cvmfs csi in nomad？
Ref: https://github.com/cvmfs-contrib/cvmfs-csi/issues/51

Hi @shumin1027. It seems this error originates from having non-nil AccessibilityRequirements (i.e. topology) in CreateVolumeRequest rather than AccessMode.
https://github.com/cvmfs-contrib/cvmfs-csi/blob/18097c80de75c7325c910d53086cd76ef9aa797f/internal/cvmfs/controller/csiserver.go#L205-L207
I don't have Nomad environment at hand so I cannot test this. Can you pass logs from the controller plugin (running with -v=5 verbosity level) to see what Nomad's CSI client is passing the driver? Is there a way to pass nil topology requirements when creating a volume?

Another way to do this is to create the volume manually (similar to how you would manually create a PersistentVolume and its PersistentVolumeClaim in Kubernetes). Is this possible in Nomand? That way you would circumvent the provisioning stage.
You can see a Kubernetes example for this here: https://github.com/cvmfs-contrib/cvmfs-csi/blob/master/example/volume-pv-pvc.yaml

@gman0
The example given above is to manually create volume
nomad volume create cvmfs.volume.hcl

This is the log output by the controller plugin when creating a volume manually：
I1205 13:47:16.773803       1 grpcserver.go:136] Call-ID 3443: Call: /csi.v1.Controller/CreateVolume
I1205 13:47:16.774096       1 grpcserver.go:137] Call-ID 3443: Request: {"accessibility_requirements":{},"name":"cvmfs-volume","volume_capabilities":[{"AccessType":{"Mount":{"fs_type":"cvmfs2"}},"access_mode":{"mode":3}}]}
E1205 13:47:16.774136       1 grpcserver.go:141] Call-ID 3443: Error: rpc error: code = InvalidArgument desc = volume accessibility requirements are not supported

What I meant is to just register an existing volume without actually triggering CreateVolume call on the driver. I'm not familiar with Nomad so I'm not sure if it's possible.
The volume itself is "virtual", it's just a reference for cvmfs-csi.

Relaxing validation and letting it pass on "accessibility_requirements":{} doesn't seem too unreasonable -- we may include this change in the next point release.

What I meant is to just register an existing volume without actually triggering CreateVolume call on the driver. I'm not familiar with Nomad so I'm not sure if it's possible.
The volume itself is "virtual", it's just a reference for cvmfs-csi.

Execute the register command can be completed correctly：
nomad volume register cvmfs.volume.hcl

But I still can't mount the cvmfs volume correctly in the application container
JuiceFS gives a good support use case，we can use it as a reference：
https://github.com/juicedata/juicefs-csi-driver/blob/master/docs/en/cookbook/csi-in-nomad.md

@gman0 Thank you for your help，your guess might be right，nomad  seems to be temporarily unsupported mount-propagation

Thanks for following this up, @shumin1027. We can continue once this is resolved in Nomad.

@gman0
I fixed this issue: https://github.com/hashicorp/nomad/issues/15524， the mount-propagation option can be successfully set when mounting the  volume


[image_picker] Android: Save state of the image picker to handle data lost if the MainActivity is killed by system.

Description
On Android, the MainActivity can be killed and restarted after launching the image picker for various of reasons. this can be tested by selecting `don't keep activities alive' option in the developer options in phone's setting app.
This PR first prevents the crash by not trying to access the already nulled pendingResult, then also save the information of the image/video that was picked in the SharedPreference.
This PR also added a retrieveLostData method to retrieve the data saved in the SharedPreference.
There were also some refactoring being done in the example app in order to demonstrate the retrieveLostData method.
Also updated dart doc on pickImage and pickVideo methods to explain this situation.
Related Issues
Directly fixing https://github.com/flutter/flutter/issues/17950
Possibly: https://github.com/flutter/flutter/issues/23788, https://github.com/flutter/flutter/issues/21102,
https://github.com/flutter/flutter/issues/18700
Checklist
Before you create this PR confirm that it meets all requirements listed below by checking the relevant checkboxes ([x]). This will ensure a smooth and quick review process.

[x] I read the Contributor Guide and followed the process outlined there for submitting PRs.
[x] My PR includes unit or integration tests for all changed/updated/fixed behaviors (See Contributor Guide).
[x] All existing and new tests are passing.
[x] I updated/added relevant documentation (doc comments with ///).
[x] The analyzer (flutter analyze) does not report any problems on my PR.
[x] I read and followed the Flutter Style Guide.
[x] The title of the PR starts with the name of the plugin surrounded by square brackets, e.g. [shared_preferences]
[x] I updated pubspec.yaml with an appropriate new version according to the pub versioning philosophy.
[x] I updated CHANGELOG.md to add a description of the change.
[x] I signed the CLA.
[x] I am willing to follow-up on review comments in a timely manner.

Breaking Change
Does your PR require plugin users to manually update their apps to accommodate your change?

[ ] Yes, this is a breaking change (please indicate a breaking change in CHANGELOG.md and increment major revision).
[x] No, this is not a breaking change.

After offline discussion with @mklim, we decided to have smaller patches to fix different problems. I will soon create another PR just to fix the crash. And have a follow up on a new solution to retrieving the lost data.


Set up subdomain for Andromeda at andromeda.imageomics.org

From Hunt Wagner, OSU OTDI Web Systems Administrator:

The general idea is that you setup an elastic IP in the AWS account for your EC2 to use, and go to your domain registrar and setup the subdomain. Based on a whois lookup, your registrar is namecheap. A more complete answer can be found by googling something like "How to setup subdomain AWS namecheap". There should be a good step by step guide out there.

Here's namecheap's article on creating a subdomain:
https://www.namecheap.com/support/knowledgebase/article.aspx/9776/2237/how-to-create-a-subdomain-for-my-domain/
And according to AWS docs:

You can have one Elastic IP (EIP) address associated with a running instance at no charge.

But

You will be charged "$0.005 per Elastic IP address not associated with a running instance per hour on a pro rata basis

http://andromedia.imageomics.org is good to go, https://imageomics.org/andromeda has been taken down.


[FRONTED] Add Dark Mode Support in Dashboard

Task
Added dark mode support in Dashboard section as in homepage

I am interested. Please assign this task to me.

Will be assigning from tomorrow onwards


⚠ Bofrost.es has degraded performance

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

HTTP code: 200
Response time: 1695 ms

Resolved: Bofrost.es performance has improved in 4029236 after 11 minutes.


See  only black window in a browser when launch serve

But some errors there:
HTTP  2/25/2024 4:42:34 PM <IP_ADDRESS> GET /
HTTP  2/25/2024 4:42:34 PM <IP_ADDRESS> Returned 304 in 17 ms
HTTP  2/25/2024 4:42:34 PM <IP_ADDRESS> GET /jsUtils/materialize.min.css
HTTP  2/25/2024 4:42:34 PM <IP_ADDRESS> GET /jsUtils/jquery-3.6.4.min.js
HTTP  2/25/2024 4:42:34 PM <IP_ADDRESS> GET /jsUtils/materialize.min.js
HTTP  2/25/2024 4:42:34 PM <IP_ADDRESS> GET /jsUtils/webgl-lessons-ui.js
HTTP  2/25/2024 4:42:34 PM <IP_ADDRESS> GET /jsUtils/webgl-utils.js
HTTP  2/25/2024 4:42:34 PM <IP_ADDRESS> GET /dist/main.js
HTTP  2/25/2024 4:42:34 PM <IP_ADDRESS> Returned 304 in 10 ms
HTTP  2/25/2024 4:42:34 PM <IP_ADDRESS> Returned 304 in 7 ms
HTTP  2/25/2024 4:42:34 PM <IP_ADDRESS> Returned 304 in 6 ms
HTTP  2/25/2024 4:42:34 PM <IP_ADDRESS> Returned 304 in 10 ms
HTTP  2/25/2024 4:42:34 PM <IP_ADDRESS> Returned 304 in 10 ms
HTTP  2/25/2024 4:42:34 PM <IP_ADDRESS> Returned 304 in 8 ms
HTTP  2/25/2024 4:42:34 PM <IP_ADDRESS> GET /fonts/roboto/Roboto-Regular.woff2
HTTP  2/25/2024 4:42:34 PM <IP_ADDRESS> Returned 404 in 3 ms
HTTP  2/25/2024 4:42:34 PM <IP_ADDRESS> GET /fonts/roboto/Roboto-Regular.woff
HTTP  2/25/2024 4:42:34 PM <IP_ADDRESS> Returned 404 in 2 ms
HTTP  2/25/2024 4:42:34 PM <IP_ADDRESS> GET /fonts/roboto/Roboto-Regular.ttf
HTTP  2/25/2024 4:42:34 PM <IP_ADDRESS> Returned 404 in 2 ms
HTTP  2/25/2024 4:42:34 PM <IP_ADDRESS> GET /mesh_data/metadata.json
HTTP  2/25/2024 4:42:34 PM <IP_ADDRESS> Returned 404 in 1 ms

Problem solved when I moved finetune and output folder to web_demo.

Hi @crankyz
Could you please explain which folders and files should be located in web_demo directory?
I moved finetune_mesh_output  and sequence_data there, but still getting the black window (although with "common loaded MLP loaded" logs in the bottom)

@dhbloo could you please describe what should be the structure inside web_demo folder so that web demo works?
 Thanks!


[Bug] [Bug] [TC-BRBINFO-4.1] Testcase needs to be moved to Python Testing Suite

Describe the bug

TC-BRBINFO-4.1 tescase is listed under the Python Testing Suite - No commissioning in the TH UI. But this tescase needs to be commissioned before the test execution hence this testcase needs to be moved to the Python Testing Suite

Steps to reproduce the behavior

From the Test-Harness user interface loaded the PICS file to select the test cases.
Selected the python test case in Python Testing Suite - No commissioning section to executed.
Click the Start button on Test-Harness user interface.

Expected behavior
The testcase needs to be commissioned before the start python test
Log files
TC-BRBINFO-4.1.log
PICS file
Bridged Device Basic Information Cluster Test Plan.zip
Screenshots

Environment
Version: v2.11-beta2+fall2024
Sha: bbeda31
Additional Information
No response

Issue fixed


The chains containing residues with non-descendent order are not displayed correctly in the sequence panel.

The residue with max residue number is determined by the last element of the chain array (in seqpanel.js), which is not correct in such the case. I changed MolResidue.getChainJSON() to return the sorted array of the residue info to avoid this situation.


The required version of Golang is wrong

https://github.com/Microsoft/frameworkcontroller/blame/07c2a6c058b1c369cb9d3d339a042fc351e28d71/example/run/README.md#L100

There is a typo in the description above, I think the golang version should be 1.10, and the description should be "Golang 1.10 or above and the ${GOPATH} is valid." :smiley:

Hi William, thank you to be the first one to report issue.
And it is indeed a typo.
I will fix it later. :)

PTAL: https://github.com/Microsoft/frameworkcontroller/pull/5


APT whitelist request for libqt5webkit5-dev

This replaces travis-ci/travis-ci#4519.
The original text by @mcmire follows

This is necessary in order to run capybara-webkit tests against a project that requires Qt 5 (using features that weren't available in Qt 4, such as ES5 getters/setters). (Source)
Thanks!

Ran tests and found setuid bits by purely textual search. Further analysis is required.
If these are found to be benign, add:
libqt5webkit5-dev libqt5webkit5 qml-module-qtwebkit libqt5webkit5-dbg qtwebkit5-doc-html
See https://travis-ci.org/travis-ci/apt-whitelist-checker/builds/72545685.

Any news on this? We're waiting quite long now.

+1 for for this requirement