Include ansible playbook test to induce periodic network failures on OpenEBS replica volume

What this PR does / why we need it:

Includes an ansible playbook test suite to induce periodic (<timeout value of 60s) network failures on OpenEBS replica volume.
The network failures are injected by Pumba network emulation tool at periodic intervals specified by the user in the vars file.
The volume resiliency is tracked via liveness probe on the application deployment, with the probe performing continuous writes on the volume (In this case, DB writes are performed on percona). This probe is implemented via a shell script which is mounted into percona deployment as a configmap.

Which issue this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close that issue when PR gets merged): fixes #277
Special notes for your reviewer:
Provided the sample run playbook output in the comment section below.
@ksatchit @yudaykiran Can you please review this PR?

Test Playbook output:
devops@devops-virtual-machine:~/build/openebs/e2e/ansible$ ansible-playbook playbooks/resiliency/test-network-failure-rep/test-nw-failure-rep.yml -vv
ansible-playbook <IP_ADDRESS>
  config file = /home/devops/build/openebs/e2e/ansible/ansible.cfg
  configured module search path = [u'/home/devops/.ansible/plugins/modules', u'/usr/share/ansible/plugins/modules']
  ansible python module location = /usr/lib/python2.7/dist-packages/ansible
  executable location = /usr/bin/ansible-playbook
  python version = 2.7.12 (default, Dec  4 2017, 14:50:18) [GCC 5.4.0 20160609]
Using /home/devops/build/openebs/e2e/ansible/ansible.cfg as config file
[DEPRECATION WARNING]: The use of 'include' for tasks has been deprecated. Use 'import_tasks' for static inclusions or 'include_tasks' for dynamic inclusions. This feature will be removed in a
future release. Deprecation warnings can be disabled by setting deprecation_warnings=False in ansible.cfg.a
[DEPRECATION WARNING]: include is kept for backwards compatibility but usage is discouraged. The module documentation details page may explain more about this rationale.. This feature will be
removed in a future release. Deprecation warnings can be disabled by setting deprecation_warnings=False in ansible.cfg.
statically imported: /home/devops/build/openebs/e2e/ansible/playbooks/resiliency/test-network-failure-rep/test-nw-failure-rep-cleanup.yml
 [WARNING]: Ignoring invalid attribute: retried

PLAYBOOK: test-nw-failure-rep.yml *******************************************************************************************************************************************************************
1 plays in playbooks/resiliency/test-network-failure-rep/test-nw-failure-rep.yml

PLAY [localhost] ************************************************************************************************************************************************************************************

TASK [Gathering Facts] ******************************************************************************************************************************************************************************
ok: [localhost]
META: ran handlers

TASK [Get $HOME of K8s master for kubernetes user] **************************************************************************************************************************************************
task path: /home/devops/build/openebs/e2e/ansible/playbooks/resiliency/test-network-failure-rep/test-nw-failure-rep.yml:18
changed: [localhost -> None] => {"changed": true, "cmd": "source ~/.profile; echo $HOME", "delta": "0:00:00.003009", "end": "2018-04-19 00:01:51.482015", "rc": 0, "start": "2018-04-19 00:01:51.479006", "stderr": "", "stderr_lines": [], "stdout": "/home/ubuntu", "stdout_lines": ["/home/ubuntu"]}

TASK [Get percona spec and liveness scripts] ********************************************************************************************************************************************************
task path: /home/devops/build/openebs/e2e/ansible/playbooks/resiliency/test-network-failure-rep/test-nw-failure-rep.yml:25
changed: [localhost -> None] => (item=https://raw.githubusercontent.com/openebs/elves/master/e2e/percona-liveness/percona.yaml) => {"changed": true, "checksum_dest": null, "checksum_src": "66bda981b5e740c1715ec7aefc89000f0797c403", "dest": "/home/ubuntu/percona.yaml", "gid": 1000, "group": "ubuntu", "item": "https://raw.githubusercontent.com/openebs/elves/master/e2e/percona-liveness/percona.yaml", "md5sum": "d7b60974e8970cc7ceb7025ac028290f", "mode": "0664", "msg": "OK (1593 bytes)", "owner": "ubuntu", "size": 1593, "src": "/tmp/tmp8U7GMq", "state": "file", "status_code": 200, "uid": 1000, "url": "https://raw.githubusercontent.com/openebs/elves/master/e2e/percona-liveness/percona.yaml"}
changed: [localhost -> None] => (item=https://raw.githubusercontent.com/openebs/elves/master/e2e/percona-liveness/sql-test.sh) => {"changed": true, "checksum_dest": null, "checksum_src": "1808253d88759a699ea9738916d1febe04547ca6", "dest": "/home/ubuntu/sql-test.sh", "gid": 1000, "group": "ubuntu", "item": "https://raw.githubusercontent.com/openebs/elves/master/e2e/percona-liveness/sql-test.sh", "md5sum": "d235f8179f540ebae853378070247fd5", "mode": "0664", "msg": "OK (399 bytes)", "owner": "ubuntu", "size": 399, "src": "/tmp/tmpqTQ31V", "state": "file", "status_code": 200, "uid": 1000, "url": "https://raw.githubusercontent.com/openebs/elves/master/e2e/percona-liveness/sql-test.sh"}

TASK [Replace volume-claim name with test parameters] ***********************************************************************************************************************************************
task path: /home/devops/build/openebs/e2e/ansible/playbooks/resiliency/test-network-failure-rep/test-nw-failure-rep.yml:32
changed: [localhost -> None] => (item=[u'demo-vol1-claim', u'test-nw-failure']) => {"changed": true, "item": ["demo-vol1-claim", "test-nw-failure"], "msg": "2 replacements made"}
changed: [localhost -> None] => (item=[u'demo-vol1', u'test-nw']) => {"changed": true, "item": ["demo-vol1", "test-nw"], "msg": "2 replacements made"}

TASK [Start the log aggregator to capture test pod logs] ********************************************************************************************************************************************
task path: /home/devops/build/openebs/e2e/ansible/playbooks/resiliency/test-network-failure-rep/test-nw-failure-rep.yml:42
changed: [localhost -> None] => {"changed": true, "cmd": "source ~/.profile; nohup stern \"maya*|openebs*|pvc*|percona*|pumba*\" --since 1m > \"/home/ubuntu/setup/logs/network_failure_test.log\" &", "delta": "0:00:00.004637", "end": "2018-04-19 00:02:05.113151", "rc": 0, "start": "2018-04-19 00:02:05.108514", "stderr": "/bin/bash: /home/ubuntu/setup/logs/network_failure_test.log: No such file or directory", "stderr_lines": ["/bin/bash: /home/ubuntu/setup/logs/network_failure_test.log: No such file or directory"], "stdout": "", "stdout_lines": []}

TASK [Check whether maya-apiserver pod is deployed] *************************************************************************************************************************************************
task path: /home/devops/build/openebs/e2e/ansible/playbooks/resiliency/test-network-failure-rep/test-nw-failure-rep.yml:50
changed: [localhost -> None] => {"attempts": 1, "changed": true, "cmd": "source ~/.profile; kubectl get pods | grep maya-apiserver", "delta": "0:00:00.279961", "end": "2018-04-19 00:02:05.710892", "rc": 0, "start": "2018-04-19 00:02:05.430931", "stderr": "", "stderr_lines": [], "stdout": "maya-apiserver-69f9db69-7vpxd          1/1       Running   0          28m", "stdout_lines": ["maya-apiserver-69f9db69-7vpxd          1/1       Running   0          28m"]}

TASK [Setup the pumba infrastructure] ***************************************************************************************************************************************************************
task path: /home/devops/build/openebs/e2e/ansible/playbooks/resiliency/test-network-failure-rep/test-nw-failure-rep.yml:66
changed: [localhost -> None] => {"changed": true, "cmd": "source ~/.profile; kubectl apply -f https://raw.githubusercontent.com/openebs/elves/master/chaos/pumba/pumba_kube.yml", "delta": "0:00:01.653185", "end": "2018-04-19 00:02:07.698347", "rc": 0, "start": "2018-04-19 00:02:06.045162", "stderr": "", "stderr_lines": [], "stdout": "daemonset \"pumba\" created", "stdout_lines": ["daemonset \"pumba\" created"]}

TASK [Confirm that the pumba deployment is running] *************************************************************************************************************************************************
task path: /home/devops/build/openebs/e2e/ansible/playbooks/resiliency/test-network-failure-rep/test-nw-failure-rep.yml:72
FAILED - RETRYING: Confirm that the pumba deployment is running (15 retries left).
changed: [localhost -> None] => {"attempts": 2, "changed": true, "cmd": "source ~/.profile; kubectl get pods --no-headers -l app=pumba", "delta": "0:00:00.269332", "end": "2018-04-19 00:02:38.890090", "rc": 0, "start": "2018-04-19 00:02:38.620758", "stderr": "", "stderr_lines": [], "stdout": "pumba-rvs7k   1/1       Running   0         31s\npumba-t6kkh   1/1       Running   0         31s\npumba-tm8hl   1/1       Running   0         31s", "stdout_lines": ["pumba-rvs7k   1/1       Running   0         31s", "pumba-t6kkh   1/1       Running   0         31s", "pumba-tm8hl   1/1       Running   0         31s"]}

TASK [Create a configmap with the liveness sql script] **********************************************************************************************************************************************
task path: /home/devops/build/openebs/e2e/ansible/playbooks/resiliency/test-network-failure-rep/test-nw-failure-rep.yml:82
changed: [localhost -> None] => {"changed": true, "cmd": "source ~/.profile; kubectl create configmap sqltest --from-file=sql-test.sh", "delta": "0:00:00.198231", "end": "2018-04-19 00:02:39.613700", "failed_when_result": false, "rc": 0, "start": "2018-04-19 00:02:39.415469", "stderr": "", "stderr_lines": [], "stdout": "configmap \"sqltest\" created", "stdout_lines": ["configmap \"sqltest\" created"]}

TASK [Create percona deployment with OpenEBS storage] ***********************************************************************************************************************************************
task path: /home/devops/build/openebs/e2e/ansible/playbooks/resiliency/test-network-failure-rep/test-nw-failure-rep.yml:90
changed: [localhost -> None] => {"changed": true, "cmd": "source ~/.profile; kubectl apply -f percona.yaml", "delta": "0:00:01.807237", "end": "2018-04-19 00:02:41.746718", "rc": 0, "start": "2018-04-19 00:02:39.939481", "stderr": "", "stderr_lines": [], "stdout": "deployment \"percona\" created\npersistentvolumeclaim \"test-nw-failure\" created\nservice \"percona-mysql\" created", "stdout_lines": ["deployment \"percona\" created", "persistentvolumeclaim \"test-nw-failure\" created", "service \"percona-mysql\" created"]}

TASK [Wait for 120s to ensure liveness check starts] ************************************************************************************************************************************************
task path: /home/devops/build/openebs/e2e/ansible/playbooks/resiliency/test-network-failure-rep/test-nw-failure-rep.yml:96
ok: [localhost] => {"changed": false, "elapsed": 120, "path": null, "port": null, "search_regex": null, "state": "started"}

TASK [Confirm percona pod is running] ***************************************************************************************************************************************************************
task path: /home/devops/build/openebs/e2e/ansible/playbooks/resiliency/test-network-failure-rep/test-nw-failure-rep.yml:100
changed: [localhost -> None] => {"attempts": 1, "changed": true, "cmd": "source ~/.profile; kubectl get pods --no-headers -l name=percona", "delta": "0:00:00.277039", "end": "2018-04-19 00:04:44.063897", "rc": 0, "start": "2018-04-19 00:04:43.786858", "stderr": "", "stderr_lines": [], "stdout": "percona-bf58c966c-48pml   1/1       Running   0         2m", "stdout_lines": ["percona-bf58c966c-48pml   1/1       Running   0         2m"]}

TASK [Get the node details on which pvc-rep is scheduled] *******************************************************************************************************************************************
task path: /home/devops/build/openebs/e2e/ansible/playbooks/resiliency/test-network-failure-rep/test-nw-failure-rep.yml:110
changed: [localhost -> None] => {"changed": true, "cmd": "kubectl get pods -o wide | grep rep | awk 'FNR == 1 {print}' | awk {'print $7'}", "delta": "0:00:00.298548", "end": "2018-04-19 00:04:44.706736", "rc": 0, "start": "2018-04-19 00:04:44.408188", "stderr": "", "stderr_lines": [], "stdout": "kubeminion-02", "stdout_lines": ["kubeminion-02"]}

TASK [Get the pvc-rep name] *************************************************************************************************************************************************************************
task path: /home/devops/build/openebs/e2e/ansible/playbooks/resiliency/test-network-failure-rep/test-nw-failure-rep.yml:117
changed: [localhost -> None] => {"changed": true, "cmd": "kubectl get pods | grep rep | awk 'FNR == 1 {print}' | awk {'print $1'}", "delta": "0:00:00.341741", "end": "2018-04-19 00:04:45.413756", "rc": 0, "start": "2018-04-19 00:04:45.072015", "stderr": "", "stderr_lines": [], "stdout": "pvc-fab0bf0c-4364-11e8-9a76-02b983f0a4db-rep-5b9f47757f-6qc8c", "stdout_lines": ["pvc-fab0bf0c-4364-11e8-9a76-02b983f0a4db-rep-5b9f47757f-6qc8c"]}

TASK [Get the rep container name] *******************************************************************************************************************************************************************
task path: /home/devops/build/openebs/e2e/ansible/playbooks/resiliency/test-network-failure-rep/test-nw-failure-rep.yml:124
changed: [localhost -> None] => {"changed": true, "cmd": "kubectl describe pod pvc-fab0bf0c-4364-11e8-9a76-02b983f0a4db-rep-5b9f47757f-6qc8c | grep rep-con | awk {'print $1'}", "delta": "0:00:00.430457", "end": "2018-04-19 00:04:46.140856", "rc": 0, "start": "2018-04-19 00:04:45.710399", "stderr": "", "stderr_lines": [], "stdout": "pvc-fab0bf0c-4364-11e8-9a76-02b983f0a4db-rep-con:", "stdout_lines": ["pvc-fab0bf0c-4364-11e8-9a76-02b983f0a4db-rep-con:"]}

TASK [Set container name to variable] ***************************************************************************************************************************************************************
task path: /home/devops/build/openebs/e2e/ansible/playbooks/resiliency/test-network-failure-rep/test-nw-failure-rep.yml:131
ok: [localhost] => {"ansible_facts": {"container": "pvc-fab0bf0c-4364-11e8-9a76-02b983f0a4db-rep-con:"}, "changed": false}

TASK [Get pumba container name] *********************************************************************************************************************************************************************
task path: /home/devops/build/openebs/e2e/ansible/playbooks/resiliency/test-network-failure-rep/test-nw-failure-rep.yml:141
changed: [localhost -> None] => {"changed": true, "cmd": "kubectl get pods -o wide | grep kubeminion-02 | grep pumba | awk {'print $1'}", "delta": "0:00:00.357415", "end": "2018-04-19 00:04:46.832763", "rc": 0, "start": "2018-04-19 00:04:46.475348", "stderr": "", "stderr_lines": [], "stdout": "pumba-rvs7k", "stdout_lines": ["pumba-rvs7k"]}

TASK [Initiate periodic network failures from pumba] ************************************************************************************************************************************************
task path: /home/devops/build/openebs/e2e/ansible/playbooks/resiliency/test-network-failure-rep/test-nw-failure-rep.yml:148
changed: [localhost -> None] => (item=3000) => {"changed": true, "cmd": "kubectl exec pumba-rvs7k -- pumba netem --interface eth0 --duration 1m delay --time 3000 re2:k8s_pvc-fab0bf0c-4364-11e8-9a76-02b983f0a4db-rep-con; sleep 10", "delta": "0:01:10.986842", "end": "2018-04-19 00:05:58.148315", "item": 3000, "rc": 0, "start": "2018-04-19 00:04:47.161473", "stderr": "time=\"2018-04-19T00:04:49Z\" level=info msg=\"netem: delay for containers\" \ntime=\"2018-04-19T00:04:50Z\" level=info msg=\"Running netem command '[delay 3000ms 10ms 20.00]' on container bf772abb1208a755eae32cf451c726313d9892d487f6d946d889b2ee3fee2769 for 1m0s\" \ntime=\"2018-04-19T00:04:50Z\" level=info msg=\"Start netem for container bf772abb1208a755eae32cf451c726313d9892d487f6d946d889b2ee3fee2769 on 'eth0' with command '[delay 3000ms 10ms 20.00]'\" \ntime=\"2018-04-19T00:05:50Z\" level=info msg=\"Stopping netem on container bf772abb1208a755eae32cf451c726313d9892d487f6d946d889b2ee3fee2769\" \ntime=\"2018-04-19T00:05:50Z\" level=info msg=\"Stop netem for container bf772abb1208a755eae32cf451c726313d9892d487f6d946d889b2ee3fee2769 on 'eth0'\" ", "stderr_lines": ["time=\"2018-04-19T00:04:49Z\" level=info msg=\"netem: delay for containers\" ", "time=\"2018-04-19T00:04:50Z\" level=info msg=\"Running netem command '[delay 3000ms 10ms 20.00]' on container bf772abb1208a755eae32cf451c726313d9892d487f6d946d889b2ee3fee2769 for 1m0s\" ", "time=\"2018-04-19T00:04:50Z\" level=info msg=\"Start netem for container bf772abb1208a755eae32cf451c726313d9892d487f6d946d889b2ee3fee2769 on 'eth0' with command '[delay 3000ms 10ms 20.00]'\" ", "time=\"2018-04-19T00:05:50Z\" level=info msg=\"Stopping netem on container bf772abb1208a755eae32cf451c726313d9892d487f6d946d889b2ee3fee2769\" ", "time=\"2018-04-19T00:05:50Z\" level=info msg=\"Stop netem for container bf772abb1208a755eae32cf451c726313d9892d487f6d946d889b2ee3fee2769 on 'eth0'\" "], "stdout": "", "stdout_lines": []}
changed: [localhost -> None] => (item=6000) => {"changed": true, "cmd": "kubectl exec pumba-rvs7k -- pumba netem --interface eth0 --duration 1m delay --time 6000 re2:k8s_pvc-fab0bf0c-4364-11e8-9a76-02b983f0a4db-rep-con; sleep 10", "delta": "0:01:11.282333", "end": "2018-04-19 00:07:09.757581", "item": 6000, "rc": 0, "start": "2018-04-19 00:05:58.475248", "stderr": "time=\"2018-04-19T00:06:01Z\" level=info msg=\"netem: delay for containers\" \ntime=\"2018-04-19T00:06:01Z\" level=info msg=\"Running netem command '[delay 6000ms 10ms 20.00]' on container bf772abb1208a755eae32cf451c726313d9892d487f6d946d889b2ee3fee2769 for 1m0s\" \ntime=\"2018-04-19T00:06:01Z\" level=info msg=\"Start netem for container bf772abb1208a755eae32cf451c726313d9892d487f6d946d889b2ee3fee2769 on 'eth0' with command '[delay 6000ms 10ms 20.00]'\" \ntime=\"2018-04-19T00:07:01Z\" level=info msg=\"Stopping netem on container bf772abb1208a755eae32cf451c726313d9892d487f6d946d889b2ee3fee2769\" \ntime=\"2018-04-19T00:07:01Z\" level=info msg=\"Stop netem for container bf772abb1208a755eae32cf451c726313d9892d487f6d946d889b2ee3fee2769 on 'eth0'\" ", "stderr_lines": ["time=\"2018-04-19T00:06:01Z\" level=info msg=\"netem: delay for containers\" ", "time=\"2018-04-19T00:06:01Z\" level=info msg=\"Running netem command '[delay 6000ms 10ms 20.00]' on container bf772abb1208a755eae32cf451c726313d9892d487f6d946d889b2ee3fee2769 for 1m0s\" ", "time=\"2018-04-19T00:06:01Z\" level=info msg=\"Start netem for container bf772abb1208a755eae32cf451c726313d9892d487f6d946d889b2ee3fee2769 on 'eth0' with command '[delay 6000ms 10ms 20.00]'\" ", "time=\"2018-04-19T00:07:01Z\" level=info msg=\"Stopping netem on container bf772abb1208a755eae32cf451c726313d9892d487f6d946d889b2ee3fee2769\" ", "time=\"2018-04-19T00:07:01Z\" level=info msg=\"Stop netem for container bf772abb1208a755eae32cf451c726313d9892d487f6d946d889b2ee3fee2769 on 'eth0'\" "], "stdout": "", "stdout_lines": []}
changed: [localhost -> None] => (item=10000) => {"changed": true, "cmd": "kubectl exec pumba-rvs7k -- pumba netem --interface eth0 --duration 1m delay --time 10000 re2:k8s_pvc-fab0bf0c-4364-11e8-9a76-02b983f0a4db-rep-con; sleep 10", "delta": "0:01:11.392145", "end": "2018-04-19 00:08:21.424738", "item": 10000, "rc": 0, "start": "2018-04-19 00:07:10.032593", "stderr": "time=\"2018-04-19T00:07:12Z\" level=info msg=\"netem: delay for containers\" \ntime=\"2018-04-19T00:07:13Z\" level=info msg=\"Running netem command '[delay 10000ms 10ms 20.00]' on container bf772abb1208a755eae32cf451c726313d9892d487f6d946d889b2ee3fee2769 for 1m0s\" \ntime=\"2018-04-19T00:07:13Z\" level=info msg=\"Start netem for container bf772abb1208a755eae32cf451c726313d9892d487f6d946d889b2ee3fee2769 on 'eth0' with command '[delay 10000ms 10ms 20.00]'\" \ntime=\"2018-04-19T00:08:13Z\" level=info msg=\"Stopping netem on container bf772abb1208a755eae32cf451c726313d9892d487f6d946d889b2ee3fee2769\" \ntime=\"2018-04-19T00:08:13Z\" level=info msg=\"Stop netem for container bf772abb1208a755eae32cf451c726313d9892d487f6d946d889b2ee3fee2769 on 'eth0'\" ", "stderr_lines": ["time=\"2018-04-19T00:07:12Z\" level=info msg=\"netem: delay for containers\" ", "time=\"2018-04-19T00:07:13Z\" level=info msg=\"Running netem command '[delay 10000ms 10ms 20.00]' on container bf772abb1208a755eae32cf451c726313d9892d487f6d946d889b2ee3fee2769 for 1m0s\" ", "time=\"2018-04-19T00:07:13Z\" level=info msg=\"Start netem for container bf772abb1208a755eae32cf451c726313d9892d487f6d946d889b2ee3fee2769 on 'eth0' with command '[delay 10000ms 10ms 20.00]'\" ", "time=\"2018-04-19T00:08:13Z\" level=info msg=\"Stopping netem on container bf772abb1208a755eae32cf451c726313d9892d487f6d946d889b2ee3fee2769\" ", "time=\"2018-04-19T00:08:13Z\" level=info msg=\"Stop netem for container bf772abb1208a755eae32cf451c726313d9892d487f6d946d889b2ee3fee2769 on 'eth0'\" "], "stdout": "", "stdout_lines": []}

TASK [Confirm percona application is still running] *************************************************************************************************************************************************
task path: /home/devops/build/openebs/e2e/ansible/playbooks/resiliency/test-network-failure-rep/test-nw-failure-rep.yml:163
changed: [localhost -> None] => {"attempts": 1, "changed": true, "cmd": "source ~/.profile; kubectl get pods --no-headers -l name=percona", "delta": "0:00:00.331859", "end": "2018-04-19 00:08:22.084802", "rc": 0, "start": "2018-04-19 00:08:21.752943", "stderr": "", "stderr_lines": [], "stdout": "percona-bf58c966c-48pml   1/1       Running   0         5m", "stdout_lines": ["percona-bf58c966c-48pml   1/1       Running   0         5m"]}

TASK [Terminate the log aggregator] *****************************************************************************************************************************************************************
task path: /home/devops/build/openebs/e2e/ansible/playbooks/resiliency/test-network-failure-rep/test-nw-failure-rep.yml:179
fatal: [localhost -> None]: FAILED! => {"changed": true, "cmd": "source ~/.profile; killall stern", "delta": "0:00:00.009331", "end": "2018-04-19 00:08:22.457557", "msg": "non-zero return code", "rc": 1, "start": "2018-04-19 00:08:22.448226", "stderr": "stern: no process found", "stderr_lines": ["stern: no process found"], "stdout": "", "stdout_lines": []}

TASK [set_fact] *************************************************************************************************************************************************************************************
task path: /home/devops/build/openebs/e2e/ansible/playbooks/resiliency/test-network-failure-rep/test-nw-failure-rep.yml:189
ok: [localhost] => {"ansible_facts": {"flag": "Fail"}, "changed": false}

TASK [Get pvc name to verify successful pvc deletion] ***********************************************************************************************************************************************
task path: /home/devops/build/openebs/e2e/ansible/playbooks/resiliency/test-network-failure-rep/test-nw-failure-rep-cleanup.yml:2
changed: [localhost -> None] => {"changed": true, "cmd": "source ~/.profile; kubectl get pvc | grep test-nw-failure | awk {'print $3'}", "delta": "0:00:00.204552", "end": "2018-04-19 00:08:23.018972", "rc": 0, "start": "2018-04-19 00:08:22.814420", "stderr": "", "stderr_lines": [], "stdout": "pvc-fab0bf0c-4364-11e8-9a76-02b983f0a4db", "stdout_lines": ["pvc-fab0bf0c-4364-11e8-9a76-02b983f0a4db"]}

TASK [Delete pumba infrastructure] ******************************************************************************************************************************************************************
task path: /home/devops/build/openebs/e2e/ansible/playbooks/resiliency/test-network-failure-rep/test-nw-failure-rep-cleanup.yml:9
changed: [localhost -> None] => {"changed": true, "cmd": "source ~/.profile; kubectl delete daemonset pumba", "delta": "0:00:08.347650", "end": "2018-04-19 00:08:31.704073", "rc": 0, "start": "2018-04-19 00:08:23.356423", "stderr": "", "stderr_lines": [], "stdout": "daemonset \"pumba\" deleted", "stdout_lines": ["daemonset \"pumba\" deleted"]}

TASK [Confirm pumba pod has been deleted] ***********************************************************************************************************************************************************
task path: /home/devops/build/openebs/e2e/ansible/playbooks/resiliency/test-network-failure-rep/test-nw-failure-rep-cleanup.yml:15
changed: [localhost -> None] => {"attempts": 1, "changed": true, "cmd": "source ~/.profile; kubectl get pods --no-headers -l app=pumba", "delta": "0:00:00.212663", "end": "2018-04-19 00:08:32.243263", "rc": 0, "start": "2018-04-19 00:08:32.030600", "stderr": "No resources found.", "stderr_lines": ["No resources found."], "stdout": "", "stdout_lines": []}

TASK [Delete percona mysql pod] *********************************************************************************************************************************************************************
task path: /home/devops/build/openebs/e2e/ansible/playbooks/resiliency/test-network-failure-rep/test-nw-failure-rep-cleanup.yml:25
changed: [localhost -> None] => {"changed": true, "cmd": "source ~/.profile; kubectl delete -f percona.yaml", "delta": "0:00:03.581959", "end": "2018-04-19 00:08:36.184556", "rc": 0, "start": "2018-04-19 00:08:32.602597", "stderr": "", "stderr_lines": [], "stdout": "deployment \"percona\" deleted\npersistentvolumeclaim \"test-nw-failure\" deleted\nservice \"percona-mysql\" deleted", "stdout_lines": ["deployment \"percona\" deleted", "persistentvolumeclaim \"test-nw-failure\" deleted", "service \"percona-mysql\" deleted"]}

TASK [Confirm percona pod has been deleted] *********************************************************************************************************************************************************
task path: /home/devops/build/openebs/e2e/ansible/playbooks/resiliency/test-network-failure-rep/test-nw-failure-rep-cleanup.yml:31
FAILED - RETRYING: Confirm percona pod has been deleted (10 retries left).
changed: [localhost -> None] => {"attempts": 2, "changed": true, "cmd": "source ~/.profile; kubectl get pods -l name=percona", "delta": "0:00:00.199126", "end": "2018-04-19 00:09:07.372150", "rc": 0, "start": "2018-04-19 00:09:07.173024", "stderr": "No resources found.", "stderr_lines": ["No resources found."], "stdout": "", "stdout_lines": []}

TASK [Confirm pvc pod has been deleted] *************************************************************************************************************************************************************
task path: /home/devops/build/openebs/e2e/ansible/playbooks/resiliency/test-network-failure-rep/test-nw-failure-rep-cleanup.yml:41
changed: [localhost -> None] => {"changed": true, "cmd": "source ~/.profile; kubectl get pods | grep pvc-fab0bf0c-4364-11e8-9a76-02b983f0a4db", "delta": "0:00:00.296102", "end": "2018-04-19 00:09:07.988885", "failed_when_result": false, "rc": 0, "start": "2018-04-19 00:09:07.692783", "stderr": "", "stderr_lines": [], "stdout": "pvc-fab0bf0c-4364-11e8-9a76-02b983f0a4db-ctrl-56f99fdb98-mn88w   0/2       Terminating   0          6m", "stdout_lines": ["pvc-fab0bf0c-4364-11e8-9a76-02b983f0a4db-ctrl-56f99fdb98-mn88w   0/2       Terminating   0          6m"]}

TASK [Remove the percona liveness check config map] *************************************************************************************************************************************************
task path: /home/devops/build/openebs/e2e/ansible/playbooks/resiliency/test-network-failure-rep/test-nw-failure-rep-cleanup.yml:51
changed: [localhost -> None] => {"changed": true, "cmd": "source ~/.profile; kubectl delete cm sqltest", "delta": "0:00:00.192098", "end": "2018-04-19 00:09:08.550836", "failed_when_result": false, "rc": 0, "start": "2018-04-19 00:09:08.358738", "stderr": "", "stderr_lines": [], "stdout": "configmap \"sqltest\" deleted", "stdout_lines": ["configmap \"sqltest\" deleted"]}

TASK [Remove test artifacts] ************************************************************************************************************************************************************************
task path: /home/devops/build/openebs/e2e/ansible/playbooks/resiliency/test-network-failure-rep/test-nw-failure-rep-cleanup.yml:59
changed: [localhost -> None] => (item=percona.yaml) => {"changed": true, "item": "percona.yaml", "path": "/home/ubuntu/percona.yaml", "state": "absent"}
changed: [localhost -> None] => (item=sql-test.sh) => {"changed": true, "item": "sql-test.sh", "path": "/home/ubuntu/sql-test.sh", "state": "absent"}

TASK [Send slack notification] **********************************************************************************************************************************************************************
task path: /home/devops/build/openebs/e2e/ansible/playbooks/resiliency/test-network-failure-rep/test-nw-failure-rep.yml:196
skipping: [localhost] => {"changed": false, "skip_reason": "Conditional result was False"}
META: ran handlers
META: ran handlers

PLAY RECAP ******************************************************************************************************************************************************************************************
localhost                  : ok=28   changed=24   unreachable=0    failed=1

@ksatchit Linted the playbooks using ansible lint. I was able to resolve Trailing White spaces errors. I am seeing few more errors, for which need to debug and fix them.
ansible-lint output:
devops@devops-virtual-machine:~$ ansible-lint PR3/openebs/e2e/ansible/playbooks/resiliency/test-network-failure-rep/test-nw-failure-rep.yml
[ANSIBLE0012] Commands should not change things if nothing needs doing
/home/devops/PR3/openebs/e2e/ansible/playbooks/resiliency/test-network-failure-rep/test-nw-failure-rep-cleanup.yml:2
Task/Handler: Get pvc name to verify successful pvc deletion

[ANSIBLE0012] Commands should not change things if nothing needs doing
/home/devops/PR3/openebs/e2e/ansible/playbooks/resiliency/test-network-failure-rep/test-nw-failure-rep-cleanup.yml:9
Task/Handler: Delete pumba infrastructure

[ANSIBLE0012] Commands should not change things if nothing needs doing
/home/devops/PR3/openebs/e2e/ansible/playbooks/resiliency/test-network-failure-rep/test-nw-failure-rep-cleanup.yml:15
Task/Handler: Confirm pumba pod has been deleted

[ANSIBLE0012] Commands should not change things if nothing needs doing
/home/devops/PR3/openebs/e2e/ansible/playbooks/resiliency/test-network-failure-rep/test-nw-failure-rep-cleanup.yml:25
Task/Handler: Delete percona mysql pod

[ANSIBLE0012] Commands should not change things if nothing needs doing
/home/devops/PR3/openebs/e2e/ansible/playbooks/resiliency/test-network-failure-rep/test-nw-failure-rep-cleanup.yml:31
Task/Handler: Confirm percona pod has been deleted

[ANSIBLE0012] Commands should not change things if nothing needs doing
/home/devops/PR3/openebs/e2e/ansible/playbooks/resiliency/test-network-failure-rep/test-nw-failure-rep-cleanup.yml:41
Task/Handler: Confirm pvc pod has been deleted

[ANSIBLE0012] Commands should not change things if nothing needs doing
/home/devops/PR3/openebs/e2e/ansible/playbooks/resiliency/test-network-failure-rep/test-nw-failure-rep-cleanup.yml:51
Task/Handler: Remove the percona liveness check config map

[ANSIBLE0011] All tasks should be named
PR3/openebs/e2e/ansible/playbooks/resiliency/test-network-failure-rep/test-nw-failure-rep.yml:196
Task/Handler: set_fact flag=Pass __file__=PR3/openebs/e2e/ansible/playbooks/resiliency/test-network-failure-rep/test-nw-failure-rep.yml __line__=196

[ANSIBLE0011] All tasks should be named
PR3/openebs/e2e/ansible/playbooks/resiliency/test-network-failure-rep/test-nw-failure-rep.yml:200
Task/Handler: set_fact flag=Fail __file__=PR3/openebs/e2e/ansible/playbooks/resiliency/test-network-failure-rep/test-nw-failure-rep.yml __line__=200

@ksatchit @yudaykiran
Ansible lint report with latest changes:
devops@devops-virtual-machine:~/PR3/openebs/e2e/ansible/playbooks/resiliency/test-network-failure-rep$ ansible-lint test-nw-failure-rep.yml
[ANSIBLE0011] All tasks should be named
test-nw-failure-rep.yml:196
Task/Handler: set_fact flag=Pass __file__=test-nw-failure-rep.yml __line__=196

[ANSIBLE0011] All tasks should be named
test-nw-failure-rep.yml:200
Task/Handler: set_fact flag=Fail __file__=test-nw-failure-rep.yml __line__=200

Does the above lint error can be ignored as ansible set_fact cannot be given with task name?

@dargasudarshan , can you skip the lint checking for set_fact using tags.
# Append to the tasks that need linting to be skipped. Built in tag for ansible-lint tool
  tags:
  - skip_ansible_lint

@ksatchit @yudaykiran I am able to lint my ansible playbooks without any errors.
devops@devops-virtual-machine:~/PR3/openebs/e2e/ansible/playbooks/resiliency/test-network-failure-rep$ ansible-lint test-nw-failure-rep.yml
I was seeing 3 Errors reported by lint:

[ANSIBLE0002] Trailing whitespace.

To resolve this error we have to run :%s/\s\+$//e on the test playbook yml files.

[ANSIBLE0012]  Commands should not change things if nothing needs doing

To resolve this error we have to add changed_when: true to all tasks where we are using shell/command modules.

[ANSIBLE0011] all tasks should be named

To resolve this error we have to give task name while using set flag module.


Unexpected behavior on [data-failed-once]

Brian, here is a little issue I discovered. It has more to do with user experience.
You know how when you are filling in a form for common fields (name, email, address), most browsers provide little drop down with history of what you filled in before? Well if you tried to fill a line, and it failed validation after you tabbed away from it and then came back to it, that dropdown will try to help you again. But [data-failed-once] keyup event keeps refreshing the field trying to validate it, as you type. As a result it keeps flickering which is very annoying, plus it's not letting user to use the browser dropdown.
Also trying to force the dropdown on keydown, also doesn't work. Although - that seems to be an issue in firefox, not chrome.
I see why would you want to validate as you type, but then it creates unpleasant experience, especially for people who are used to reusing value from that dropdown. I think the expected behavior would be to validate on blur, maybe? What do you think? Or is there a way to disable the dropdown altogether, so at least it's not confusing?
I'm not sure if it qualifies as bug, rather than a unexpected feature :-)

I have the same problem with the auto-completion in Safari. It seems that does not trigger the change event.


add a lock property to the callback schema

This took more than expected, because i hit a bug on Z-Schema

Fine, I suggest a name like copy for that function accepting an object as parameter, so we have
var schemas = copy(originalSchemas)
and is more explicit what is going on.
Up to your, for the rest LGTM , merge :+1:

well, deepCopy is even more explicit than copy, right?

Absolutely, then do we need the getSchemas one at all, since the originalSchemas variable is bound on the outer scope?

okay i renamed as you suggested :+1:

:rocket:


Expand documentation on Bastion's behavior when connecting to VM

I haven't seen any detailed documentation on which IP Bastion uses to connect to a VM, and what happens when there are NIC/IP config changes on a VM.  I believe it would be useful to include this documentation.
I have done my own testing and observed the following:
Bastion will only ever connect via the primary IP address of the primary NIC.  Even if an NSG blocks the primary IP of the primary NIC from RDP/SSH, Bastion will never try to use alternative NICs/IPs on the VM to connect.
If the primary NIC is changed, the VM must be deallocated and reallocated before Bastion will connect via the new primary NIC's primary IP.  This does NOT count the VM deallocation needed to change which NIC is primary (so the steps are: deallocate VM, change which NIC is primary, reallocate VM, then deallocate and reallocate VM one more time.  You cannot use the "restart" feature for the last steps).
If the primary IP address of the primary NIC is changed (requires stopping the VM), Bastion will connect via the new primary IP as soon as the VM is reallocated (this includes the case where the primary NIC is switched to a different subnet, as this is effectively just an IP change).  So the steps are: deallocate VM, change primary IP of the primary NIC, reallocate VM.

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

ID: 3a1d3f69-74ba-0ba9-17ba-c7c1086d2662
Version Independent ID: 7f2680d3-7d10-b253-bdc3-ca661b5da5af
Content: Azure Bastion
Content Source: articles/bastion/bastion-overview.md
Service: bastion
GitHub Login: @cherylmc
Microsoft Alias: cherylmc

@mhollismcgill Thanks for the info! I have assigned the issue to the content author to evaluate and update as appropriate.


Incorrect Package reference

Below "Before you can use dependency injection, you must install the following NuGet packages" there is a list of packages that must be referenced.
Microsoft.Extensions.DependencyInjection does NOT need to be referenced, in fact if you do it may clash with the version of Microsoft.Extensions.DependencyInjection that is included in Microsoft.Azure.Functions.Extensions. For Microsoft.Azure.Functions.Extensions V1.1.0 this is Microsoft.Extensions.DependencyInjection V2.1.0

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

ID: 5786402e-9d88-5de0-607a-1c2a143af006
Version Independent ID: 15368d1c-b22e-7eb2-413f-cc0d41d2b909
Content: Use dependency injection in .NET Azure Functions
Content Source: articles/azure-functions/functions-dotnet-dependency-injection.md
Service: azure-functions
GitHub Login: @ggailey777
Microsoft Alias: glenga

Hello @endintiers - Thank you for your feedback! We will review and update as appropriate.

@endintiers the Microsoft.Azure.Functions.Extensions packages requires the Microsoft.Extensions.DependencyInjection package of a version >=2.1 and the doc does mention that only 3.x or earlier versions are supported.
The case where someone was to install a version lower than 2.1, a warning would be shown to the user to alert the same.
Nonetheless, I suppose the doc could mention any pitfalls. We are assigning this issue to the content author for further review.

My point was that you don't NEED a reference to Microsoft.Extensions.DependencyInjection, because there is already one (in Microsoft.Azure.Functions.Extensions). Startup works fine if you don't include a reference to DependencyInjection.
By adding one you are overriding the version referenced in Microsoft.Azure.Functions.Extensions, which is OK (I guess) because that has no upper limit on the version of Microsoft.Extensions.DependencyInjection it can use.
Anyway, it doesn't cause an issue as written as far as I can see, I just saw that it wasn't actually required (as stated).


✨(theme) Add themes

Add Themes
The component CunninghamProvider will be responsible to handle the current state via the optional prop theme.
<CunninghamProvider theme="light">
This will set a custom class to a root div in the provider:
<div class="cunningham-provider--light"/>
EDIT: The class will be set on :root element in order to make variables like --my-component-border: var(--theme-color-500) overridable. ( As those component variables are defined on :root element their chained variable should be overriden at at the same or on a parent node, but as :root as no parent, we set the class of :root )
Then the CSS generated file will contain the following addition in order to support the themes:
.cunningham-provider--light {
	--c--theme--colors--primary-100: #EBF2FC;
	...
}

.cunningham-provider--light {
	--c--theme--colors--primary-100: #000000;
	...
}

Regarding cunningham.ts we will add a nested property to handle themes:
const config: DefaultTokens = {
  themes: {
    default: {
      theme: {
        colors: {
          "primary-500": "purple",
          "success-700": "lime",
          "greyscale-300": "#ff18e5",
        },
      },
      components: {
        button: {
          "border-radius": "30px",
        },
      },
    },
    light: {
      colors: {
        "primary-500": "white",
      }
    },
    ...
  },
};

export default config;

The default is the default one, and all other defined themes are totally arbitrary and will be deep merged with default.
Test

[ ] Theme switching in Provider
[ ] CssGenerator

After re-reading this PR, I think we might add a new doc called Migrating to 2.0.0 in order to showcase the changes needed, WDYT @jbpenrath?


[DoNotMerge] [Tests-Only] Skip skipOnOcis tag for the tests with getting shares that pass on ocis

Passed


⚠ ClamAV has degraded performance

In c56e020, ClamAV (https://spamassassin.apache.org/) experienced degraded performance:

HTTP code: 200
Response time: 74 ms

Resolved: ClamAV performance has improved in 5fc05a9.


Should rtl handle side coordinates too ?

I see that alignment has first class support for RTL: https://github.com/floating-ui/floating-ui/blob/a8de472098fdae2e7b45353402f56ae249a9d906/packages/core/src/computeCoordsFromPlacement.ts#L38-L45
Should this also be done for the side ? i.e. left becomes right and vice versa. I can't speak for all users of the library but we are currently switching the side placement for rtl handling always. Is this a valid scenario for floating ui ?

Decided to leave side physical for these reasons here: https://github.com/floating-ui/floating-ui/discussions/1549
You'd can something like:
computePosition(a, b, {
  // right for LTR, left for RTL
  placement: logical('inline-end', isRTL(b)),
});

We could technically export this

Yeah that function is very similar to something we wrote for Popper (we also mapped a our own placement terms, but the rtl handling is similar to what you're proposing)
https://github.com/microsoft/fluentui/blob/63447028978db5e34dc46d56fb63fd02290a44b5/packages/react-positioning/src/utils/positioningHelper.ts#L32
Previously  when we used popper we would pass the the RTL down from React context (since we used React), so definitely more used to explicitly configuring this.
However, after testing the computed position, it seems that dir also cascades down the DOM tree so I'm not against this.

Later on we can export a logical -> physical side/placement converter but for now it's not crucial. An issue can be opened to track that feature if it's requested frequently.

Reopening because this is kinda bothering me leading up to v1 given it's a breaking change. 😅 I feel like it should be supported by default with space-separated syntax (like CSS). I hope it's not too costly to support by default though. I'll investigate, but at minimum I think it should be supported via an export as mentioned, though built-in would be better.
e.g.
placement: 'inline-start end

After experimenting with how this would work I think it's sort of impractical to do built-in:

writing-mode is obscure but necessary for this feature to make any real sense. But it adds a lot to the bundle size.
If we don't add writing-mode, then block-* logical sides are useless, because only inline-* sides have effect in RTL mode.
Logical alignments made much more sense than logical sides in terms of ergonomics because they are always the same unlike physical alignments which are different depending on the side, e.g. top alignment only makes sense for left/right sides.
A lot of edge cases to consider
A physical function can still do this work.

I don't think it should block v1.


Deprecating Fastlane

Description:

Removing Fastlane from code

@LetoFranco what's the motivation for this change?
The last think I know is that we want the ios-base to be an example of how to configure our CI/CD workflows with Fastlane.

@LetoFranco what's the motivation for this change? The last think I know is that we want the ios-base to be an example of how to configure our CI/CD workflows with Fastlane.

Hey @glm4, i added more details to the description in order to give more visibility about the motivations of the change.

@LetoFranco what's the motivation for this change? The last think I know is that we want the ios-base to be an example of how to configure our CI/CD workflows with Fastlane.

Hey @glm4, i added more details to the description in order to give more visibility about the motivations of the change.

I think we should discuss this on the next iOS Roundtable as a team, and take a better look at the possible advantages and disadvantages.


move Stats to Deedle.Stats project.

There is an attempt to move stats module to the separated project. It is the first steps for implement https://github.com/fslaborg/Deedle/issues/423
Some things are left:

Fix documentation.
For now I left tests as it is. Should think: do we need to move tests fo statas into separated Test project. For now I don't see there some problems to keep tests as it is now.

@alexpantyukhin Sorry for the long wait on Deedle.Math extension. I have some extra time these days to work on this project.
I've started a WIP pull on expanding Deedle using Math.Net. After some thoughts, I think it's best to leave the current Stats module intact. Those native implementations are good enough for basic descriptive stats. It does not need external dependency on Math.Net. No code base will be impacted on this math extension.
Please take a look on my pull to provide any feedback. I plan to merge it when basic functionality and testing are in shape. Then will release a separate Deedle.Math nuget package.


fix: clarify instances in steps and config

Following breaking changes where introduced:

Rename S3DefaultInstance setup step to FirstInstance
Remove CustomDomain from FirstInstance-step. The domain used for the instance is the same as config.ExternalDomain

installation docs and helm chart need to be updated


Failid to run config for laeravel.nvim

Hai,
Neovim Version = 0.10.1
Terminal  = Wezterm
OS    = Windows 11
I have error like this

My Config
	{
		"adalessa/laravel.nvim",
		enabled = is_laravel_project(), -- pastikan membuka laravel project
		dependencies = {
			"tpope/vim-dotenv",
			"nvim-telescope/telescope.nvim",
			"MunifTanjim/nui.nvim",
			"kevinhwang91/promise-async",
		},
		cmd = { "Laravel" },
		keys = {
			{ "<leader>L", "", desc = " 󰫐 Laravel" },
			{ "<leader>La", ":Laravel artisan<cr>" },
			{ "<leader>Lr", ":Laravel routes<cr>" },
			{ "<leader>Lm", ":Laravel related<cr>" },
		},
		event = { "VeryLazy" },
		opts = {},
		config = true,
	},

Strange, there only runs for the query set native function, could be from your configuration treesitter has not loaded php treesitter properly.  could you add the dependencies to treesitter so it ensure is loaded before laravel plugin ?

Thaks,
now it's ok
after adding
“nvim-lua/plenary.nvim”,
“nvim-treesitter/nvim-treesitter”,
to the dependencies


add feature: query top n process instance order by running duration

add feature: query top n process instance order by running duration

add feature: query top n process instance order by running duration

Hi,
Very good job and thx a lot for your contribution.
Please create an issue and link this pr to the issue to help us to track the feature.
Thx a lot.


not working

I'm trying to use this amazing extension but nothin happens.
I just put the file into the playnite, and configure monitor on fullscreen monitor settings,
Need to make some additional configurations?

Are you using Playnite in a full-screen mode? It only works this way. Does anything happens on start? Any kind of display blinking? It should always attempt to switch as long as display was set and it's not primary already.

Are you using Playnite in a full-screen mode?
Yes
Does anything happens on start? Any kind of display blinking?
No
It should always attempt to switch as long as the display was set and it's not primary already.
yes, It's exactly that the point.
Are you using Nvidia drivers? windows 10?
how can I debug this extension?

Are you using Nvidia drivers? windows 10?
Windows 10 with Radeon, but it shouldn't matter since it uses standard windows api

Does your log at %appdata%\Playnite\playnite.log has a string "Error setting primary display: Your display DeviceName"?

Hello good news, I formatted my computer and updated my graphics card drivers for the version 451,67 using Nvidia gtx1050ti, after reinstalling the application and the extension everything is working perfectly
Thanks for your attention and for this amazing extension


Add a way to override all client options

This can be very useful if the user has already created a ClientOptions that they want to reuse across many different clients.

I've added a warning to the docs to make it clear to users that this overrides all client options previously set.
As a side note: I think we'll eventually want to abstract over these builders as there is a lot of overlap between the cosmos and blob storage client builders.


x/build/cmd/rundockerbuildlet: unable to start rundockerbuildlet on ppc64

What version of Go are you using (go version)?

$ go version
go version go1.18.5 linux/amd64

Does this issue reproduce with the latest release?
I have not tested.
What operating system and processor architecture are you using (go env)?
go env Output
debian@go-be-debian-1:~$ go env
GO111MODULE=""
GOARCH="ppc64"
GOBIN=""
GOCACHE="/home/debian/.cache/go-build"
GOENV="/home/debian/.config/go/env"
GOEXE=""
GOEXPERIMENT=""
GOFLAGS=""
GOHOSTARCH="ppc64"
GOHOSTOS="linux"
GOINSECURE=""
GOMODCACHE="/home/debian/go/pkg/mod"
GONOPROXY=""
GONOSUMDB=""
GOOS="linux"
GOPATH="/home/debian/go"
GOPRIVATE=""
GOPROXY="https://proxy.golang.org,direct"
GOROOT="/usr/lib/go-1.19"
GOSUMDB="sum.golang.org"
GOTMPDIR=""
GOTOOLDIR="/usr/lib/go-1.19/pkg/tool/linux_ppc64"
GOVCS=""
GOVERSION="go1.19"
GCCGO="gccgo"
GOPPC64="power8"
AR="ar"
CC="gcc"
CXX="g++"
CGO_ENABLED="0"
GOMOD="/dev/null"
GOWORK=""
CGO_CFLAGS="-g -O2"
CGO_CPPFLAGS=""
CGO_CXXFLAGS="-g -O2"
CGO_FFLAGS="-g -O2"
CGO_LDFLAGS="-g -O2"
PKG_CONFIG="pkg-config"
GOGCCFLAGS="-fPIC -Wl,--no-gc-sections -fmessage-length=0 -fdebug-prefix-map=/tmp/go-build2889172257=/tmp/go-build -gno-record-gcc-switches"

What did you do?
I built the latest version of rundockerbuildlet on my amd64 dev machine.

GOARCH=ppc64 GOOS=linux /usr/bin/go build -o rundockerbuildlet.ppc64 golang.org/x/build/cmd/rundockerbuildlet

I created a systemd unit file to run rundockerbuildlet similar to other PPC64 builders, and the utility fails to start with the following error:

Aug 30 20:30:39 go-be-debian-1 systemd[1]: Started Run Buildlets in Docker.
░░ Subject: A start job for unit rundockerbuildlet.service has finished successfully
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░
░░ A start job for unit rundockerbuildlet.service has finished successfully.
░░
░░ The job identifier is 4777.
Aug 30 20:30:40 go-be-debian-1 rundockerbuildlet[330779]: 2022/08/30 20:30:40 unable to retrieve EC2 user data: EC2MetadataError: failed to make EC2Metadata request
Aug 30 20:30:40 go-be-debian-1 rundockerbuildlet[330779]:         status code: 404, request id:
Aug 30 20:30:40 go-be-debian-1 rundockerbuildlet[330779]: caused by: 404 Not Found
Aug 30 20:30:40 go-be-debian-1 rundockerbuildlet[330779]: The resource could not be found.
Aug 30 20:30:40 go-be-debian-1 rundockerbuildlet[330779]:

What did you expect to see?
This builder is not running on AWS. I wouldn't expect to see AWS related chatter causing a failure to start.
What did you see instead?
The usual startup and status information for this utility.

Also, the relevant systemd line for starting.

ExecStart=/usr/local/bin/rundockerbuildlet -basename=power_ -image=golang/buildlet-stage0 -n=5 -cpu=4 -memory=6g --env=host-linux-ppc64-sid

That error suggests that the program has successfully connected to an EC2 metadata server for the purposes of onEC2 but then failed to actually read the EC2 metadata. I assume these machines are not AWS machines so I don't know why that would be. Sorry.
cc @golang/release


Accessibility (WCAG level A) HTML 5 validation error on Packages page because of the use of an hgroup element

Go to http://validator.w3.org/ and validate the page https://nuget.org/packages.

Result:  In addition to other validation errors which I've logged elsewhere, there is a validation error message triggered by our use of an hgroup element:
Error Line 49, Column 23: The hgroup element is obsolete. To mark up subheadings, consider either just putting the subheading into a p element after the h1-h6 element containing the main heading, or else putting the subheading directly within the h1-h6 element containing the main heading, but separated from the main heading by punctuation and/or within, for example, a span class="subheading" element with differentiated styling. To group headings and subheadings, alternative titles, or taglines, consider using the header or div elements.
Expected:  I don't see a good reason why we can't take the last of these suggestions and have a span styled to be a block element within the header to achieve the desired visual and semantic effect.

We have a new gallery design.


Need Styleguide

A source code style guide is needed.
Among other things, it should require formatting to be using 4-spaces instead of tabs. I've put editor configure files into the source code trees now to help with this.

This relates to issue #20 .

I've migrated development of this fork as well as this issue to my PlayRho repository. Please go there from now on for information about its evolution.


[FEATURE REQUEST] Get all the comment for specific reference id

U### Is your feature request related to a problem? Please describe.
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
Users should be able to get all comments for a particular referenceId (i.e user).
Describe the solution you'd like
A clear and concise description of what you want to happen.
A controller to get all comment for a specific reference Id
Endpoints: /comment/refs/:{refId}
Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.
No alternative
Additional context
Add any other context or screenshots about the feature request here.
No
Time Duration to finish
50mins

Please ensure you use the updated docs at https://comments-microservice.herokuapp.com/


Icon pack proposal: Cryptocurrency Icons

Name: Cryptocurrency Icons
License: CC0-1.0
NPM package: https://www.npmjs.com/package/cryptocurrency-icons
Website (if any): http://cryptoicons.co/

Thanks for the proposal, this has been released in v6.2.0! 🎉

Awesome thanks!


Web download: same permission asked twice

Testing #109284
Edge/Linux
Open the web playground, select a folder and download. When asked for a destination, create a new folder.
Two permission dialogs appear, select 'View files' and 'Save files'

Now download another folder. Select the same folder as destination. Again I'm asked for the same permissions.
Isn't the playground supposed to have the permissions already?

I can reproduce and I am surprised too, but I am not sure if my code has any impact on this behaviour...

Filed https://bugs.chromium.org/p/chromium/issues/detail?id=1143184. Possibly this is expected behaviour though.

:+1:
It would also be great to have a single permission dialog for reading and writing.

Since this issue has a linked upstream issue referenced, I am going ahead to close this issue as part of our issue grooming effort: https://github.com/microsoft/vscode/wiki/Issue-Grooming


Picker View Styling

Picker view is shown from the position last selected.
For example, if the last item is selected, the picker view would be bottom to up, next time.
How can I adjust this view fixed as top to bottom all time?

Thanks for question and sorry for delayed reply. Please take look at #14 and dropdownPosition prop.


Incompatible with puppetlabs/puppet_agent

It appears these lines of code are a duplicate declaration from puppetlabs/puppet_agent.
Can this be wrapped in a manage_service boolean?

hmm, that module is like a one-off upgrade module isnt it? I would imagine it probably should not be used at the same time as many other modules and once used you should stop using it?
I might be wrong but its a module for doing upgrades only?

I think it was designed to be one-off for upgrading from 3.x to 4.x; however, if you do keep it in, you can manage the puppet versions quite well and it does become quite useful.
The puppetlabs/puppet_agent module also manages the puppetlabs repo which is quite nice since some Linux Distribution packages place the config paths in nasty locations (such as Fedora who places puppet config in /etc/puppet/).

Ok - perhaps then just tell that module to not manage the service using its service_names property.
I am not too keen on sending a message that there is any expectation that multiple modules can manage mco when this module is in use - it's not something I am in a position to support - and such a property would do that
But as that module does seem to have the ability to not manage mco that's probably best?

You are correct, I will manage the service functionality from the puppet_agent module. I did not even to think to see if it had that option.

thanks @andrewwippler I hope that works, if not get in touch again by reopening this one and we can see what we can do


Signups endpoint

What's this PR do?
Catches errors and returns null for campaigns and reportbacks in order to reach all /signup endpoints.
For some reason, users can sign up for some nodes that are not campaigns or sms_games which was breaking when we tried to build the campaign in Signup.php's get function.
We were hitting the No reportback found. error, again breaking the endpoint, in the situation where there was a reportback in the database but couldn't be returned if has not yet been reviewed.
How should this be manually tested?
Make sure all /signup endpoints work and don't log and errors in the Drupal log messages.
http://dev.dosomething.org:8888/api/v1/signups
http://dev.dosomething.org:8888/api/v1/signups/42
http://dev.dosomething.org:8888/api/v1/signups?user=98&campaigns=1227,1173
What are the relevant tickets?
Fixes #6193

Ah yikes! @angaither do you know why it pulled other people's commits here?

Yeah, there's something crazy going on @_@

Try rebasing w/ dev....

eek just did that and same thing! Maybe I should just close this and start over?


[CP] beta 138434 flutter tools pathnotfoundexception

Fixes:

https://github.com/flutter/flutter/issues/138434

Cherry pick into Beta issue:

https://github.com/flutter/flutter/issues/140006

@godofredoc do we need to branch recipes for beta?

Uncaught Exception: AssertionError('analyze is not listed in available_validations.')

https://github.com/flutter/flutter/pull/140005/checks?check_run_id=19576191609

@godofredoc do we need to branch recipes for beta?

This should have been fixed in https://github.com/flutter/cocoon/pull/3305. Let me try rerunning, maybe there was a Cocoon issue where it was rolled back to an older version.
I've gone ahead and manually rerun the two failing targets to see if that gets them passing.

@CaseyHillers those two checks seem to be stuck, I'm going to push an empty commit to see if that restarts them

@eliasyishak I think there's an issue with your checkout. I'm going to land on red to bypass the presubmit check, but your branch should've included https://github.com/flutter/flutter/pull/139161 which I'm not seeing.


ui review fixes

*Issue:*https://github.com/bcgov/entity/issues/
Description of changes:
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of the namex license (Apache 2.0).

/gcbrun

Temporary Url for review: https://strr-ui-dev--pr-8-96f9qjij.web.app

/gcbrun

Temporary Url for review: https://strr-ui-dev--pr-8-96f9qjij.web.app


FixBug: update user.go, solve login bug interface conversion:

Environment:
DB: mysql
orm: unuse

Description:

When I have installed go-admin, and I login on <IP_ADDRESS>/admin/login use default admin/123456.  I found this error

. This is because interface converse in line353 plugins/admin/models/user.go. And in my db, there is some menu that don't have parent

Solve

I remove the rows that without parent_id.

mysql 驱动版本问题


100% cpu usage and stuck

npm-check -u works fine on most projects of mine, but I have one where, as soon as I start it, it goes to 100% cpu usage and stays there for minutes (until I kill it).
It seems to open many files and not closing it anymore:

Nevermind, I had a thousand js files lying around that it was analyzing.


[FEATURE] Make the pic-text generator output downloadable

Description
Use an npm package to make the output generated downloadable either in image,svg or copy code form.
Using the Download Image amd Download Svg buttons
Screenshots

Can I work on this?

Can I work on this?

Sure go ahead

:tada: This issue has been resolved in version 1.0.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:

Thank you for creating this issue. Wait until you are allowed to work on this before you start, and do not forget to include this issue in your pull request[Automated].


Slower Fetch Times for S3 Objects in INTELLIGENT_TIERING compared to STANDARD Tier

Describe the bug
Currently, we are attempting to download S3 objects in part size of 24MB, the fetch time for each 24MB chunk is noticeably slower in the INTELLIGENT_TIERING storage class compared to the STANDARD tier.
Regression Issue

[ ] Select this option if this issue appears to be a regression.

Expected Behavior
As we know initial fetching time for intelligent tiering will be slow but once the first download is complete, the rest of the download will be invariant.
Current Behavior
As we know initial fetching time for intelligent tiering will be slow but once the first download is complete, the rest of the download will be invariant. But this is not happening using AWS CPP SDK.
Reproduction Steps
To reproduce the issue, start downloading S3 objects from the INTELLIGENT_TIERING storage class in small chunks and compare with downloading from STANDARD tiering. You'll easily observe that fetch times for each part are significantly slower in INTELLIGENT_TIERING.
Possible Solution
No response
Additional Information/Context
No response
AWS CPP SDK version used
1.11.408
Compiler and Version used
gcc (GCC) 4.8.5
Operating System and version
CentOS Linux and version 7

Can you include some trace level logs of the GetObjectRequests that you are making? There should be a header included in the response that says some info about the current tier that your objects currently have

@jmklix please find the trace level logs for both intelligent tiering and standard tiering below.
Intelligent-tiering logs , Standard-tiering logs

Sorry, but I was mistaken. The logs only state the the storage class is INTELLIGENT_TIERING rather then tell us what tier each object is currently at:
[TRACE] 2024-11-18 11:01:37.792 http-stream [140011056908032] id=0x7f56d001e680: Incoming header: x-amz-storage-class: INTELLIGENT_TIERING

This looks like the s3 might not have you object in the tier that you are expecting. This might be because something is wrong on the s3 side, s3 is taking longer than expected to change the tier, or s3 documentation might not be clear with it's documentation for how intelligent tiering is supposed to work. Can you try analyzing what storage tier some objects are before and after you try accessing them? You can to this with s3 Inventory and look for this field S3 Intelligent-Tiering access tier

@jmklix but aws s3 cp cli command is taking the same time to download the file irrespective of STANDARD or INTELLIGENT_TIERING

Is cli and cpp perf similar for standard tier?
Im wondering of cli is equally slow for both tiers, but for cpp something is making standard tier faster, but not intelligent tier.
In general there should be no tier specific code in sdks. To sdk is just all endpoint and it does not care what data it is pulling. My initial guess is that it might have something to do with dns resolution or connection pooling. S3 supported mva dns for over a year now, but maybe something in how cpp sdk chooses ip or how it reuses connection causes intelligent to be slower

@DmitriyMusatkin relatively CLI performance for both STANDARD and INTELLIGENT-TIERING is the same, so why its not the same in the case of CPP performance?

Hard to tell off hand without a deeper dive. What we know is on sdk side there is no difference between the tiers, sdk ends up calling the same endpoints regardless of tier. This will require some bandwidth from someone sdk team to investigate.
Some potential theories:

cli is just slow for both tiers, while on cpp sdk side some optimization makes standard tier go faster, but not intelligent tier. im not an expert on how intelligent tier is implemented, but i think its reasonable to assume that s3 cannot make the object hot in all hosts after initial download in intelligent tier. So its possible that CPP SDK is more eager to connect to new host on which the object is not hot
maybe cli and cpp send slightly different requests and that has impact on perf. thing like transfer-encoding or some defaults might be different

Note: cli does not save anything on client side between runs. So whatever results in improved perf on subsequent runs must be server side

What timings are you seeing for STANDARD vs INTELLIGENT-TIERING are you seeing when using the cpp sdk?

@jmklix To fetch 24MB from intelligent-tiering using CPP SDK it is taking around 1200ms, while fetching from STANDARD tiering it is taking around 400ms for the same. There is around 800ms diff between the two.
Yes we are see this using CPP SDK


ClickOutside not working on iOS devices

I haven't done extensive testing on this, but in using the latest version of this package straight from GitHub, rather than npm, the events failed to fire on iOS for some reason. The only device I tried this on was an iPhone 7, though I'm unsure of the Safari version (I don't own an iOS device).
I found a workaround through a similar package for React—kentor/react-click-outside, where their README mentions needing cursor: pointer on the document.body for iOS to see the event here:
https://github.com/kentor/react-click-outside#not-working-on-ios
After I did this, vue-click-outside started working like a charm on a buddy's iPhone.
I'm not sure if this is something worth implementing in the package itself, or if it should be mentioned in the README since there are a number of ways to handle feature detection and adding this workaround.
Thanks!

My first thought is https://github.com/vue-bulma/click-outside/blob/45629f43911abfe9bcba3172e2a3f723a0fa7ce5/index.js#L56
It specifies click, but I'd typically have a touch event recognized as well.
const clickHandler = 'ontouchstart' in document.documentElement ? 'touchstart' : 'click';

@paquette The above fix worked for me. Thank you.

Glad to help @brennenf totally forgot about this, I haven't made a PR yet!

@Paquette Actually, if you have the time would you mind making a PR? It would be helpful for project install automation to have the patched version on npm. No worries if not!

@brennenf made the PR :)

So, is that issue closed?

😞

This package looks abandoned. For anyone trying to fix this, try : https://github.com/ndelvalle/v-click-outside, it supports touch events out of the box and was good for my case.

Yeah it seems like it, I've had an open PR that's received no feedback or sign of merge whatsoever.
https://github.com/vue-bulma/click-outside/pull/17
I have left the PR open and branch for so long because when I closed it and cleaned up some people emailed me asking where it had disappeared to, was hoping to get this merged sometime before the year 2045 but not looking hopeful at this point 😅

Sweet, glad this is finally merged.

Thanks.

https://github.com/vue-bulma/click-outside/compare/45629f43911abfe9bcba3172e2a3f723a0fa7ce5...v1.1.0


On Windows, build bundle fails when building APK if a flavor is defined.

This is the log: https://api.cirrus-ci.com/v1/task/6380156054142976/logs/test.log
Do you know what could be going on @jonahwilliams? I have confirmed that this only happen when the flavor is defined.
FileSystemException: Cannot copy file to 'C:\Users\ContainerAdministrator\AppData\Local\Temp\flutter_devicelab_gradle_plugin_test.3994aaac-f150-11e9-aad5-c8150419f7aa\hello\build\app\intermediates\flutter\productionRelease\android-arm64/flutter_assets\packages/cupertino_icons/assets/CupertinoIcons.ttf', path = 'C:\Users\ContainerAdministrator\AppData\Roaming\Pub\Cache\hosted\pub.dartlang.org\cupertino_icons-0.1.2\assets\CupertinoIcons.ttf' (OS Error: The system cannot find the path specified.
[gradle_plugin_bundle_test] [STDOUT]
[gradle_plugin_bundle_test] [STDOUT] , errno = 3)
[gradle_plugin_bundle_test] [STDOUT] #0      _File.copy.<anonymous closure> (dart:io/file_impl.dart:336:9)
[gradle_plugin_bundle_test] [STDOUT] #1      _rootRunUnary (dart:async/zone.dart:1132:38)
[gradle_plugin_bundle_test] [STDOUT] #2      _CustomZone.runUnary (dart:async/zone.dart:1029:19)
[gradle_plugin_bundle_test] [STDOUT] #3      _FutureListener.handleValue (dart:async/future_impl.dart:137:18)
[gradle_plugin_bundle_test] [STDOUT] #4      Future._propagateToListeners.handleValueCallback (dart:async/future_impl.dart:678:45)
[gradle_plugin_bundle_test] [STDOUT] #5      Future._propagateToListeners (dart:async/future_impl.dart:707:32)
[gradle_plugin_bundle_test] [STDOUT] #6      Future._completeWithValue (dart:async/future_impl.dart:522:5)
[gradle_plugin_bundle_test] [STDOUT] #7      Future._asyncComplete.<anonymous closure> (dart:async/future_impl.dart:552:7)
[gradle_plugin_bundle_test] [STDOUT] #8      _rootRun (dart:async/zone.dart:1124:13)
[gradle_plugin_bundle_test] [STDOUT] #9      _CustomZone.run (dart:async/zone.dart:1021:19)
[gradle_plugin_bundle_test] [STDOUT] #10     _CustomZone.runGuarded (dart:async/zone.dart:923:7)
[gradle_plugin_bundle_test] [STDOUT] #11     _CustomZone.bindCallbackGuarded.<anonymous closure> (dart:async/zone.dart:963:23)
[gradle_plugin_bundle_test] [STDOUT] #12     _microtaskLoop (dart:async/schedule_microtask.dart:41:21)
[gradle_plugin_bundle_test] [STDOUT] #13     _startMicrotaskLoop (dart:async/schedule_microtask.dart:50:5)
[gradle_plugin_bundle_test] [STDOUT] #14     _runPendingImmediateCallback (dart:isolate-patch/isolate_patch.dart:116:13)
[gradle_plugin_bundle_test] [STDOUT] #15     _RawReceivePortImpl._handleMessage (dart:isolate-patch/isolate_patch.dart:173:5)
[gradle_plugin_bundle_test] [STDOUT]
[gradle_plugin_bundle_test] [STDOUT] Failed to build bundle.

What test is this? I can run it locally to double check. My guess is that the subdirectory productionRelease\android-arm64 is missing for some reason

@blasten Do you remember the test this was for?  That log is long gone.

I don't have the log unfortunately. Let's just close this bug.


sudo: unable to stat /etc/sudoers: Permission denied

I tried making swap file follow this add.
https://github.com/chainpoint/chainpoint-node/wiki/Frequently-Asked-Questions#i-am-seeing-range-error-array-buffer-allocation-failed-messages-in-the-logs-what-gives
but, at first step, it show this error.
I can not continue more.
---------# sudo swapon --show
sudo: unable to stat /etc/sudoers: Permission denied
sudo: no valid sudoers sources found, quitting
sudo: unable to initialize policy plugin
How can I fix it?
I need to delete all data on server and re-install all from beginning?
Can I keep my node registration at that time??

Sorry, this is outside the scope of your project. I suggest checking the documentation for the version of Linux you are running.


Rename traffic_monitor_golang/traffic_monitor to traffic_monitor

Per<EMAIL_ADDRESS>

Refer to this link for build results (access rights to CI server needed):
https://builds.apache.org/job/incubator-trafficcontrol-PR/530/
Test PASSed.

Refer to this link for build results (access rights to CI server needed):
https://builds.apache.org/job/incubator-trafficcontrol-PR-trafficops-test/484/


General cleanup

thanks a lot @kevmoo !!!
I wanted to clean it myself, but I have no access to my computer for few days.


bug: Conflicts with vimgrep

Did you check docs and existing issues?

[X] I have read all the flash.nvim docs
[X] I have searched the existing issues of flash.nvim
[X] I have searched the existing issues of plugins related to this issue

Neovim version (nvim -v)
NVIM v0.9.1
Operating system/version
Pop!_OS 22.04
Describe the bug
When vimgrepping, the h key is sometimes handled by flash and causes the command to exit.
Steps To Reproduce

type /
type 'sh' or 'fh'

Command exits after pressing h.
Expected Behavior
'h' is not intercepted by flash.
Repro
-- DO NOT change the paths and don't remove the colorscheme
local root = vim.fn.fnamemodify("./.repro", ":p")

-- set stdpaths to use .repro
for _, name in ipairs({ "config", "data", "state", "cache" }) do
  vim.env[("XDG_%s_HOME"):format(name:upper())] = root .. "/" .. name
end

-- bootstrap lazy
local lazypath = root .. "/plugins/lazy.nvim"
if not vim.loop.fs_stat(lazypath) then
  vim.fn.system({ "git", "clone", "--filter=blob:none", "https://github.com/folke/lazy.nvim.git", lazypath, })
end
vim.opt.runtimepath:prepend(lazypath)

-- install plugins
local plugins = {
  "folke/tokyonight.nvim",
  { "folke/flash.nvim", opts = {} },
  -- add any other plugins here
}
require("lazy").setup(plugins, {
  root = root .. "/plugins",
})

vim.cmd.colorscheme("tokyonight")
-- add anything else here

flash uses labels in search. you can disable search if you dont want that


Call HLS.Helper.merge_uri/2 to save uri host on remote m3u8 files

Issue Link
If a master playlist with HTTP urls contains relative paths, it cannot find the media playlists because the host is lost.
22:35:45.768 [error] GenServer #PID<0.1329.0> terminating
** (MatchError) no match of right hand side value: {:error, {:no_scheme}}
    (kim_hls 0.1.0) lib/hls/playlist/media/tracker.ex:56: HLS.Playlist.Media.Tracker.read_media_playlist/2
    (kim_hls 0.1.0) lib/hls/playlist/media/tracker.ex:62: HLS.Playlist.Media.Tracker.handle_refresh/2

Solution: call URI.merge/2 to keep the host of the target.
I would like to confirm with you if this is the correct solution before I focus on writing a test.
Example of failing m3u8 file.

Closing the issue, this is not relevant anymore. I didn't understand the lib, I just need to call HLS.Playlist.Master.build_media_uri(master.uri, stream.uri) to solve my problem.


Clock prevents me from energy-saving mode

The current time in the Cairo Desktop prevents me from going into energy-saving mode; if the time is removed, the mode works without any problems.

Could you please clarify what you mean by energy-saving mode and how you are measuring this, so that we can better understand?

Sorry I tested once more and now my PC shutdown to hibernate after my
time..
Please close the ticket.
Regards
Juergen
------ Originalnachricht ------
Von: "Sam Johnson" @.>
An: "cairoshell/cairoshell" @.>
Cc: "juwo1811" @.>; "Author"
@.>
Gesendet: 19.04.2021 22:42:20
Betreff: Re: [cairoshell/cairoshell] Clock prevents me from
energy-saving mode (#550)

Could you please clarify what you mean by energy-saving mode and how
you are measuring this, so that we can better understand?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/cairoshell/cairoshell/issues/550#issuecomment-822771205,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ATUGBSGD7ECYW4AA7LLJWFLTJSISZANCNFSM42X75GKA.


Realm doesn't reconnect, after device goes to sleep automatically, and 5-10 minutes pass

Goals
Make sure device is always in sync when there is network connection and app is opened.
Expected Results
When device sleeps, and 5-10 minutes pass, reopen app: changes made should be pushed, changes on other devices should be received.
Actual Results
In the steps described below, the device gets out of sync.
Steps to Reproduce

Open synced realm using asyncOpen
Let the device go to sleep (note: device should not be connected via lightning cable)
Wait 5-10 minutes
Reopen app
Make changes either on this device or on other connected devices
Changes from this device are not pushed, changes on other synced devices are not received

Version of Realm and Tooling
Realm framework version: RealmSwift 3.1.1
Realm Object Server version: ROS 2.0
Xcode version: 9.2 (9C40B)
iOS/OSX version: iOS 11.2.6
Dependency manager + version: Cocoapods v 1.3.1

Do you have a small app where this can be demonstrated? It works fine on an app I tested.

Closing this issue due to no response. Feel free to reopen if additional information can be provided.


Fix ninja not showing compiler error output in some cases

Ninja sometimes does not correctly print the compiler error messages when they are too long. In this case the (discarded) return value of fwrite() was zero while GetLastError() reported "8: ERROR_NOT_ENOUGH_MEMORY".
This was observed and reproducible on Windows 7 when running ninja in cmd with my codebase.
The best reasoning about the underlying problem that I found was at https://bugs.python.org/issue11395
The threshold introduced in this patch was chosen arbitrarily and might still be too large in same cases. However, I was not able to reproduce the problem anymore after this patch.

I don't think the failed test by AppVeyor is related to any change I made as #1430 shows the same test issue without any code changes made there.

Thanks for the PR! Can you move the code into a #ifdef _WIN32? Also please squash your commits into one, capitalize the first letter of the commit message and don't add a dot at the end of the first line.

Done.

Thanks!
Do you have an idea how we could add some kind auf automated for this?

If you wanted to test this change we would need to have a way to specify the file descriptor to be used inside LinePrinter::PrintOrBuffer() as well as control error conditions when writing to that descriptor with fwrite().
We'd probably have to wrap the fwrite() calls in an abstraction. During unit you can instantiate the LinePrinter with an implementation that simulates various error conditions (return values 0<n<len and setting errno). This way the unit test can show that eventually the complete message is written.
I'm not sure if its feasible to prove that there was an issue in the first place (if you were looking for something like that) since the stdout bahvior is OS dependant since I'm not familiar with AppVeyor. If you can get a Win7 instance to run the tests and then write north of 65k bytes in one go, it should trigger the original bug that I witnessed.

Yeah an automated test for AppVeyor would be pretty hard to come up with. I'm more looking for a simple example which I can run on a Windows 7 machine manually.

I originally ran into this problem on a 64bit Win7 machine when Clang produced a message with a length of ~70k bytes which ninja then tried to write to stdout with one call to fwrite() in PrintOrBuffer().
This should let you reproduce it (cannot test myself right now because I'm working on Win10 at the moment):
LinePrinter printer;

const std::string message{ 70*1024, 'A' };
printer.PrintOrBuffer( message.c_str(), message.size() );

If you'd like I can put this into a test case and include it in the pull request.


Sum If cannot be applied to Int Columns

Describe the bug
applying Sum If expression in Metabase to Int columns will generate invalid SQL
Steps to reproduce
Given Schema
create table public.sum_if_test
(
    id            Int64,
    int_value     Int64,
    discriminator String
) ENGINE = MergeTree()
      primary key (id, discriminator);

Given Test Data
insert into public.sum_if_test values (1, 1, 'foo');
insert into public.sum_if_test values (2, 1, 'foo');
insert into public.sum_if_test values (3, 3, 'bar');
insert into public.sum_if_test values (4, 5, 'bar');

Given Metbase Report Configuration
custom expression configured in Metabase when summarizing this table:

Will generate SQL:
SELECT sum(CASE WHEN `public`.`sum_if_test`.`discriminator` = 'bar' THEN `public`.`sum_if_test`.`int_value` ELSE 0.0 END) AS `sum_if_with_int`
FROM `public`.`sum_if_test`

using a float 0.0 default value instead of 0 in ELSE 0.0
Expected behaviour
Sum If expression can be applied to Int typed columns
Error log
ode: 386. DB::Exception: There is no supertype for types Float64, Int64 because some of them are integers and some are floating point, but there is no floating point type, that can exactly represent all required integers: While processing if(discriminator = 'bar', int_value, 0.). (NO_COMMON_TYPE) (version <IP_ADDRESS>) , server ClickHouseNode [uri=https://(...)/public, options={use_server_time_zone_for_dates=true,use_no_proxy=false,product_name=metabase/1.1.2}]@92216918

Configuration
Environment

metabase-clickhouse-driver version: 1.1.2
Metabase version: v0.46.2
OS: Linux

ClickHouse server

ClickHouse Server version: 22.8.15

@pulsar256, could you try 1.1.4? It should work there now.

@slvrtrn thank you for the fix! I have just deployed the new version and it seems to be working now.

Glad that it worked!


Different dimension for attention

Description
I added channels_per_head parameter to attention. I know that it is breaking change, but I think there is not a good way of doing it - look at the discussion in https://github.com/NVIDIA/TransformerEngine/pull/731
Fixes # (issue)
Type of change

[ ] Documentation change (change only to the documentation, either a fix or a new content)
[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[x] Breaking change (fix or feature that would cause existing functionality to not work as expected)

Changes
Please list the changes introduced in this PR:

Added channels_per_head parameter to attention,
Added simple unit test, I don't know if its necessary

Checklist:

[x] I have read and followed the contributing guidelines
[x] The functionality is complete
[x] I have commented my code, particularly in hard-to-understand areas
[x] I have made corresponding changes to the documentation
[x] My changes generate no new warnings
[x] I have added tests that prove my fix is effective or that my feature works
[x] New and existing unit tests pass locally with my changes

But this tutorial mode change is good. Should I remove it and add to the new PR?

/te-ci pytorch

/te-ci pytorch

Why change the file permission for the tutorial?

It seems like we mistakenly changed the permission last time so I think we're reverting it back. Is that okay or do we need to create a separate fix for it?

/te-ci pytorch


Grinding Hamlet Destroys items

Description

Grinding Hamlet and other animals destroys the items they had equip, meaning you can destroy caps jetpack by putting it on hamlet then grinding him. Destroy items no good, should drop items grrrr.
Reproduction

Put captains jetpack on hamlet
Put hamlet in reagent grinder
Grind

Screenshots

https://github.com/user-attachments/assets/b8ba5605-16ce-4e92-8dc0-7399e8694bbd

why can hamlet wear a jetpack

why can hamlet wear a jetpack

Because it has a backslot, for oxygen tanks ostensibly.
However #22444 is the answer to your question, captain jetpack can be worn on the backslot like mini-jetpacks.


What determines if .appx or .msix packages are created?

Please clarify what options or manifest-properties that determines if an .appx or .msix package is created by MakeAppx.exe
We're creating UWP-apps for a Windows 10 IoT Core environment and they are installed by Azure IoT DM Client  (Device Management). The DM Client can only install .appx files but when we build with the latest Visual Studio we get .msix packages.

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

ID: 36fa5c17-6f3f-d941-6148-65703136a94f
Version Independent ID: c64136ad-cc7e-8cff-bf46-fb4d2c908149
Content: Create an app package with the MakeAppx.exe tool - MSIX
Content Source: msix-src/package/create-app-package-with-makeappx-tool.md
Product: windows
Technology: msix
GitHub Login: @dianmsft
Microsoft Alias: diahar

@devgaia - All .appx/.msix get packaged using Packaging APIs. There is no means to distinguish if a package is packaged via MakeAppx or the packaging APIs just by looking at the manifest or the package, given that MakeAppx also uses the packaging APIs. Visual Studio and MSIX SDK also uses the same packaging APIs


[Bug] Fix Complement data Tenant abnormality

fix https://github.com/apache/dolphinscheduler/issues/15366
fix https://github.com/apache/dolphinscheduler/issues/16010
Purpose of the pull request
Fix Complement data Tenant abnormality
Brief change log
Add setTenantCode for Command to WorkflowExecuteRunnable.java file
Verify this pull request
This pull request is already covered by existing tests, such as org.apache.dolphinscheduler.server.master.runner.WorkflowExecuteRunnableTest.

Codecov Report
Attention: Patch coverage is 0% with 1 lines in your changes are missing coverage. Please review.

Project coverage is 40.66%.

Files
Patch %
Lines

.../server/master/runner/WorkflowExecuteRunnable.java
0.00%
1 Missing :warning:

Additional details and impacted files
@@             Coverage Diff              @@
##                dev   #16092      +/-   ##
============================================
- Coverage     40.67%   40.66%   -0.01%
  Complexity     5238     5238
============================================
  Files          1382     1382
  Lines         46023    45991      -32
  Branches       4922     4898      -24
============================================
- Hits          18719    18702      -17
+ Misses        25379    25364      -15
  Partials       1925     1925

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


Gedcom

Changes the file type to gedcomx-json

Only one file needed
More features
Open standard

Full support with images will come later, I will merge this for now


Fix outdated fields

This should allow you to merge back into master.

This change is

Thanks @domgreen!


Confirm file loadd

I know how to do a group but how can i show the percent loaded when adding files to the group to confirm the file is loaded then I can play the group
var drums = new Pz.Sound('./audio/drums.mp3');
var guitar = new Pz.Sound('./audio/guitar.mp3');
var bass = new Pz.Sound('./audio/bass.mp3');

var group = new Pizzicato.Group([drums, guitar]);

group.addSound(bass);
group.addEffect(reverb);
group.play();

I tried something like this
 var testSound = new Pizzicato.Sound('test.mp3', function() { });
            var group = new Pizzicato.Group();

            group.addSound(testSound);
            group.play();

But I get  a error
this.getRawSourceNode is not a function

So I got it working but loop doesn't seem to work
var group = new Pizzicato.Group();

            var track1 = new Pizzicato.Sound({
                source: 'file',
                loop: 1,
                options: { path: '/api/user/track/audio/9?token='+this.$auth.token() }
            }, function() {
                group.addSound(track1);
            });

            var track2 = new Pizzicato.Sound({
                source: 'file',
                options: { path: '/api/user/track/audio/1?token='+this.$auth.token() }
            }, function() {
                group.addSound(track2);
                group.play();
            });

I got the loop working now
 options: { path: '/api/user/track/audio/9?token='+this.$auth.token(), loop: true }


googleFonts families in nuxt.config

"The object literal can only specify known properties, and googleFonts does not exist in the InputConfig<NuxtConfig, ConfigLayerMeta> type."
I don't know what is the reason for this unexpected issue.
Kind regards,
Daniel

I just use this now: https://nuxt.com/modules/fonts
It is a very nice module to quickly add webfonts like google fonts!
Thanks.


Remove docstring for removed function IsBefore.

Overview
Remove docstring for removed function IsBefore.
IsBefore was removed in #1304:

IsBefore inlined, so we don't need to include this method in interface (it's a oneliner used once)

Checklist

[ ] New and updated code has appropriate documentation
[ ] New and updated code has new and/or updated testing
[ ] Required CI checks are passing
[ ] Visual proof for any user facing features like CLI or documentation updates
[ ] Linked issues closed with keywords

Codecov Report

Merging #2195 (870e1c4) into main (9ecf08f) will decrease coverage by 0.13%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##             main    #2195      +/-   ##
==========================================
- Coverage   55.89%   55.76%   -0.13%
==========================================
  Files         216      216
  Lines       14091    14091
==========================================
- Hits         7876     7858      -18
- Misses       5425     5445      +20
+ Partials      790      788       -2

Impacted Files
Coverage Δ

header/header.go
61.40% <ø> (ø)

... and 4 files with indirect coverage changes


Converse command line arguments produce false warnings

Original issue: https://charm.cs.illinois.edu/redmine/issues/1081

Converse command line arguments are not properly registered during initialization, so using them generates a warning that they are not being parsed by the runtime.
The command line options in convcore.c are +csdLocalMax, +useAbsoluteTime, +nice, +CmiSpinOnIdle, +CmiSleepOnIdle, and +CmiNoProcForComThread.

Original date: 2016-10-11 21:49:57

There are two separate issues here from what I can tell.
For +nice and +csdLocalMax, they are correctly registered and function fine. The warning prints out when you pass them without an integer argument since they are registered as integer command line options. So here, I think either the general warning needs to be clarified to say that the option may not have been used as intended, or if we try to consume a command line argument that does is not used properly we should spit out an error right then and there. I would lean towards the latter.
For the others, they never seem to be read from the command line (at least for the build im currently using which is netlrts-linux-x86_64). I need to dig a bit further to figure out when and where they are used and therefore where they should be registered to the CLA database.

Original date: 2016-10-12 19:07:01

+useAbsoluteTime, +CmiSpinOnIdle, +CmiSleepOnIdle, and +CmiNoProcForComThread are all SMP options, and when running with the SMP build the warning does not show up as expected.
In summary, all of the above options seem to be registered correctly, and the warning functions as expected. The only thing that should change is that if an option that expects an int isn't given an int, there should be an error. I'm pretty sure that the Charm++ options do something like that, so the same functionality should be added for Converse options. I'll look to add that some time this week probably.

Original date: 2016-10-12 19:12:07

There already exists code in convcore.c that is supposed to make sure that arguments expecting an int actually are given that int, but it no longer seems to work. Fixing this code should fix this bug.

Original date: 2017-10-02 20:02:13

I'm going to take a quick look at this, and if I can't just nail it down, we should defer it. If we've lived with it for the past year, it's not a reason to hold the bug-fix release.

Original date: 2017-10-02 20:23:32

~~https://charm.cs.illinois.edu/gerrit/3091~~ https://github.com/UIUC-PPL/charm/commit/329e0989f2133be4600e9b005e6ea37a7ea9d540


Linux install, "Error in python bot" after login

Issue without proper information won't be answered
Expected Behavior
Login, begin botting
Actual Behavior

Steps to Reproduce
log in using google, wait 5 seconds
Information

OS: Ubuntu 16
Git commit: 5f9617406ff94ec58e53975d98575612c6ccd953
App's logs

Starting Python process...
Bot path: /home/tnn/desktop-bot/PokemonGo-Bot-Desktop/gofbot
python ./pokecli.py
Python: 2016-08-10 22:33:35,660 [       cli] [INFO] PokemonGO Bot v1.0
Python: 2016-08-10 22:33:35,661 [       cli] [INFO] No config argument specified, checking for /configs/config.json
Python: 2016-08-10 22:33:35,662 [       cli] [INFO] Configuration initialized
Python: 2016-08-10 22:33:35,662 [pokemongo_bot.health_record.bot_event] [INFO] Health check is enabled. For more information:
2016-08-10 22:33:35,662 [pokemongo_bot.health_record.bot_event] [INFO] https://github.com/PokemonGoF/PokemonGo-Bot/tree/dev#analytics
Python: 2016-08-10 22:33:35,664 [requests.packages.urllib3.connectionpool] [INFO] Starting new HTTP connection (1): www.google-analytics.com
Python: 2016-08-10 22:33:35,717 [PokemonGoBot] [INFO] [set_start_location] Setting start location.
Python: 2016-08-10 22:33:35,718 [PokemonGoBot] [INFO] [x] Coordinates found in passed in location, not geocoding.
Python: 2016-08-10 22:33:35,718 [PokemonGoBot] [INFO] [location_found] Location found: 37.791492, -122.390006 (37.791492, -122.390006, 0.0)
Python: 2016-08-10 22:33:35,718 [PokemonGoBot] [INFO] [position_update] Now at (37.791492, -122.390006, 0)
Python: 2016-08-10 22:33:35,718 [PokemonGoBot] [INFO] [login_started] Login procedure started.
Python: 2016-08-10 22:33:36,576 [PokemonGoBot] [INFO] [login_successful] Login successful.
Python: 2016-08-10 22:33:37,896 [PokemonGoBot] [INFO]
Python: 2016-08-10 22:33:37,897 [PokemonGoBot] [INFO] --- username ---
2016-08-10 22:33:37,897 [PokemonGoBot] [INFO] Pokemon Bag: 0/250
Python: 2016-08-10 22:33:37,897 [PokemonGoBot] [INFO] Items: 54/350
Python: 2016-08-10 22:33:37,897 [PokemonGoBot] [INFO] Stardust: 0 | Pokecoins: 0
Python: 2016-08-10 22:33:37,897 [PokemonGoBot] [INFO] PokeBalls: 50 | GreatBalls: 0 | UltraBalls: 0
Python: 2016-08-10 22:33:37,898 [PokemonGoBot] [INFO] RazzBerries: 0 | BlukBerries: 0 | NanabBerries: 0
Python: 2016-08-10 22:33:37,898 [PokemonGoBot] [INFO] LuckyEgg: 0 | Incubator: 0 | TroyDisk: 0
Python: 2016-08-10 22:33:37,898 [PokemonGoBot] [INFO] Potion: 0 | SuperPotion: 0 | HyperPotion: 0 | MaxPotion: 0
Python: 2016-08-10 22:33:37,898 [PokemonGoBot] [INFO] Incense: 2 | IncenseSpicy: 0 | IncenseCool: 0
Python: 2016-08-10 22:33:37,898 [PokemonGoBot] [INFO] Revive: 0 | MaxRevive: 0
Python: 2016-08-10 22:33:37,898 [PokemonGoBot] [INFO]
Python: 2016-08-10 22:33:37,899 [PokemonGoBot] [INFO] Found encrypt.so! Platform: linux2 Encrypt.so directory: /home/tnn/desktop-bot/PokemonGo-Bot-Desktop/gofbot
Python: 2016-08-10 22:33:37,899 [PokemonGoBot] [INFO]
Python: 2016-08-10 22:33:39,622 [PokemonGoBot] [INFO] [bot_start] Starting bot...
Python: 2016-08-10 22:33:41,315 [       cli] [INFO]
2016-08-10 22:33:41,316 [       cli] [INFO] Ran for 0:00:06
Python: Traceback (most recent call last):
File "./pokecli.py", line 522, in
Python:     main()
File "./pokecli.py", line 138, in main
report_summary(bot)
File "./pokecli.py", line 150, in report_summary
logger.info('Total XP Earned: {}  Average: {:.2f}/h'.format(metrics.xp_earned(), metrics.xp_per_hour()))
File "/home/tnn/desktop-bot/PokemonGo-Bot-Desktop/gofbot/pokemongo_bot/metrics.py", line 28, in xp_earned
return self.xp['latest'] - self.xp['start']
TypeError:
Python: unsupported operand type(s) for -: 'NoneType' and 'NoneType'
Python: 2016-08-10 22:33:41,323 [sentry.errors] [ERROR] Sentry responded with an error: 'ascii' codec can't decode byte 0x9c in position 1: ordinal not in range(128) (url: https://app.getsentry.com/api/90254/store/)
Traceback (most recent call last):
File "/usr/local/lib/python2.7/dist-packages/raven/transport/threaded.py", line 174, in send_sync
super(ThreadedHTTPTransport, self).send(data, headers)
File "/usr/local/lib/python2.7/dist-packages/raven/transport/http.py", line 47, in send
ca_certs=self.ca_certs,
File "/usr/local/lib/python2.7/dist-packages/raven/utils/http.py", line 66, in urlopen
return opener.open(url, data, timeout)
File "/home/tnn/.local/lib/python2.7/site-packages/future/backports/urllib/request.py", line 494, in open
response = self._open(req, data)
File "/home/tnn/.local/lib/python2.7/site-packages/future/backports/urllib/request.py", line 512, in _open
'_open', req)
File "/home/tnn/.local/lib/python2.7/site-packages/future/backports/urllib/request.py", line 466, in _call_chain
result = func(*args)
File "/usr/local/lib/python2.7/dist-packages/raven/utils/http.py", line 46, in https_open
return self.do_open(ValidHTTPSConnection, req)
File "/home/tnn/.local/lib/python2.7/site-packages/future/backports/urllib/request.py", line 1284, in do_open
h.request(req.get_method(), req.selector, req.data, headers)
File "/usr/lib/python2.7/httplib.py", line 1057, in request
self._send_request(method, url, body, headers)
File "/usr/lib/python2.7/httplib.py", line 1097, in _send_request
self.endheaders(body)
File "/usr/lib/python2.7/httplib.py", line 1053, in endheaders
self._send_output(message_body)
File "/usr/lib/python2.7/httplib.py", line 895, in _send_output
msg += message_body
UnicodeDecodeError: 'ascii' codec can't decode byte 0x9c in position 1: ordinal not in range(128)
Python: 2016-08-10 22:33:41,324 [sentry.errors.uncaught] [ERROR] [u"TypeError: unsupported operand type(s) for -: 'NoneType' and 'NoneType'", u'  File "pokecli.py", line 522, in ', u'  File "pokecli.py", line 138, in main', u'  File "pokecli.py", line 150, in report_summary', u'  File "pokemongo_bot/metrics.py", line 28, in xp_earned']
Bot exited

It seems you need support for utf-8.
Have you checked your system setting about encoding? It should be in the "languages" in system settings.
I don't know if this is the reason, just a guess.

Check out https://github.com/PokemonGoF/PokemonGo-Bot-Desktop/issues/138

It seems the issue was related to the configuration file being changed by the app. If I launch with a fresh config file it works, however after quitting  and relaunching the error occurs again.
If I run gofbot and SimpleHTTPServer separately, it works just fine