add-ons don't get installed properly

Must say up front - I am trying the install on redhat. Having said that after correcting the paths little bit I am able to get the cluster up and running. But for some reason the add-ons don't get installed even though I see the activities  related to grafana, heapster, and influxdb in the log file.
This is what I get after the install:
[rakeshk@cd3labvdapp002 ~]$ kubectl cluster-info
Kubernetes master is running at http://localhost:8080

From the log:

2016-05-02 16:22:51,989 p=18914 u=rakeshk |  task path: /home/rakeshk/contrib/ansible/roles/kubernetes-addons/tasks/cluster-monitoring.yml:11
2016-05-02 16:22:53,512 p=18914 u=rakeshk |  ok: [cd3labvdapp002 -> localhost] => (item=grafana-service.yaml) => {"changed": false, "checksum_dest": "487a140bd7f826b16eec34c6cd293c5e9a04f774", "checksum_src": "487a140bd7f826b16eec34c6cd293c5e9a04f774", "dest": "/tmp/kubernetes/addons/cluster-monitoring/grafana-service.yaml.j2", "gid": 1012, "group": "rakeshk", "item": "grafana-service.yaml", "md5sum": "8b492d5ee6bf197684d9c3cedd86201d", "mode": "0664", "msg": "OK (431 bytes)", "owner": "rakeshk", "size": 431, "src": "/tmp/tmpsHRowM", "state": "file", "uid": 1012, "url": "https://raw.githubusercontent.com/GoogleCloudPlatform/kubernetes/master/cluster/addons/cluster-monitoring/influxdb/grafana-service.yaml"}
2016-05-02 16:22:53,548 p=18914 u=rakeshk |  ok: [cd3labvdapp002 -> localhost] => (item=heapster-controller.yaml) => {"changed": false, "checksum_dest": "d65ae026a787914518a8b9227b5e16c024d11fb8", "checksum_src": "680ed4f1282025987cad1ff8bebef9bf1c62ae8e", "dest": "/tmp/kubernetes/addons/cluster-monitoring/heapster-controller.yaml.j2", "gid": 1012, "group": "rakeshk", "item": "heapster-controller.yaml", "md5sum": "e0b52e80a2bb0e8ec74b925412305629", "mode": "0664", "msg": "OK (3688 bytes)", "owner": "rakeshk", "size": 3688, "src": "/tmp/tmpQpRU3R", "state": "file", "uid": 1012, "url": "https://raw.githubusercontent.com/GoogleCloudPlatform/kubernetes/master/cluster/addons/cluster-monitoring/influxdb/heapster-controller.yaml"}
2016-05-02 16:22:53,583 p=18914 u=rakeshk |  ok: [cd3labvdapp002 -> localhost] => (item=heapster-service.yaml) => {"changed": false, "checksum_dest": "fa6a6611afc134933df625660e5044f5a485d077", "checksum_src": "fa6a6611afc134933df625660e5044f5a485d077", "dest": "/tmp/kubernetes/addons/cluster-monitoring/heapster-service.yaml.j2", "gid": 1012, "group": "rakeshk", "item": "heapster-service.yaml", "md5sum": "f455a4c445fb61865170494cbc0d872e", "mode": "0664", "msg": "OK (258 bytes)", "owner": "rakeshk", "size": 258, "src": "/tmp/tmpjYya6a", "state": "file", "uid": 1012, "url": "https://raw.githubusercontent.com/GoogleCloudPlatform/kubernetes/master/cluster/addons/cluster-monitoring/influxdb/heapster-service.yaml"}
2016-05-02 16:22:53,616 p=18914 u=rakeshk |  ok: [cd3labvdapp002 -> localhost] => (item=influxdb-grafana-controller.yaml) => {"changed": false, "checksum_dest": "2c8d5bbd5117cbaab7926d9bb04976c2c8c781b1", "checksum_src": "2c8d5bbd5117cbaab7926d9bb04976c2c8c781b1", "dest": "/tmp/kubernetes/addons/cluster-monitoring/influxdb-grafana-controller.yaml.j2", "gid": 1012, "group": "rakeshk", "item": "influxdb-grafana-controller.yaml", "md5sum": "24e5ba5b0d0bc75ec64728f8aed3e7d7", "mode": "0664", "msg": "OK (2423 bytes)", "owner": "rakeshk", "size": 2423, "src": "/tmp/tmp7_aGKc", "state": "file", "uid": 1012, "url": "https://raw.githubusercontent.com/GoogleCloudPlatform/kubernetes/master/cluster/addons/cluster-monitoring/influxdb/influxdb-grafana-controller.yaml"}
2016-05-02 16:22:53,650 p=18914 u=rakeshk |  ok: [cd3labvdapp002 -> localhost] => (item=influxdb-service.yaml) => {"changed": false, "checksum_dest": "bc359e21f8779fe54a15c4ca4616f4d90f2d6bca", "checksum_src": "bc359e21f8779fe54a15c4ca4616f4d90f2d6bca", "dest": "/tmp/kubernetes/addons/cluster-monitoring/influxdb-service.yaml.j2", "gid": 1012, "group": "rakeshk", "item": "influxdb-service.yaml", "md5sum": "1d195f93019f20ffece7a0d5c177f06a", "mode": "0664", "msg": "OK (351 bytes)", "owner": "rakeshk", "size": 351, "src": "/tmp/tmpFcdZ2E", "state": "file", "uid": 1012, "url": "https://raw.githubusercontent.com/GoogleCloudPlatform/kubernetes/master/cluster/addons/cluster-monitoring/influxdb/influxdb-service.yaml"}

...

2016-05-02 16:22:56,194 p=18914 u=rakeshk |  TASK [kubernetes-addons : MONITORING | Install template from converted saltfile] ***
2016-05-02 16:22:56,195 p=18914 u=rakeshk |  task path: /home/rakeshk/contrib/ansible/roles/kubernetes-addons/tasks/cluster-monitoring.yml:55
2016-05-02 16:22:59,649 p=18914 u=rakeshk |  ok: [cd3labvdapp002] => (item=grafana-service.yaml) => {"changed": false, "gid": 0, "group": "root", "item": "grafana-service.yaml", "mode": "0755", "owner": "root", "path": "/etc/kubernetes/addons/cluster-monitoring/grafana-service.yaml", "size": 431, "state": "file", "uid": 0}
2016-05-02 16:22:59,685 p=18914 u=rakeshk |  ok: [cd3labvdapp002] => (item=heapster-controller.yaml) => {"changed": false, "gid": 0, "group": "root", "item": "heapster-controller.yaml", "mode": "0755", "owner": "root", "path": "/etc/kubernetes/addons/cluster-monitoring/heapster-controller.yaml", "size": 3119, "state": "file", "uid": 0}
2016-05-02 16:22:59,723 p=18914 u=rakeshk |  ok: [cd3labvdapp002] => (item=heapster-service.yaml) => {"changed": false, "gid": 0, "group": "root", "item": "heapster-service.yaml", "mode": "0755", "owner": "root", "path": "/etc/kubernetes/addons/cluster-monitoring/heapster-service.yaml", "size": 258, "state": "file", "uid": 0}
2016-05-02 16:22:59,764 p=18914 u=rakeshk |  ok: [cd3labvdapp002] => (item=influxdb-grafana-controller.yaml) => {"changed": false, "gid": 0, "group": "root", "item": "influxdb-grafana-controller.yaml", "mode": "0755", "owner": "root", "path": "/etc/kubernetes/addons/cluster-monitoring/influxdb-grafana-controller.yaml", "size": 2423, "state": "file", "uid": 0}
2016-05-02 16:22:59,799 p=18914 u=rakeshk |  ok: [cd3labvdapp002] => (item=influxdb-service.yaml) => {"changed": false, "gid": 0, "group": "root", "item": "influxdb-service.yaml", "mode": "0755", "owner": "root", "path": "/etc/kubernetes/addons/cluster-monitoring/influxdb-service.yaml", "size": 351, "state": "file", "uid": 0}

[rakeshk@cd3labvdapp002 system]$ sudo systemctl status kube-addons
● kube-addons.service - Kubernetes Addon Object Manager
   Loaded: loaded (/etc/systemd/system/kube-addons.service; enabled; vendor preset: disabled)
   Active: active (running) since Sat 2016-04-30 15:58:29 EDT; 2 days ago
     Docs: https://github.com/GoogleCloudPlatform/kubernetes
 Main PID: 13835 (kube-addons.sh)
   Memory: 2.6M
   CGroup: /system.slice/kube-addons.service
           ├─13835 /bin/bash /usr/libexec/kubernetes/kube-addons.sh
           ├─30211 /bin/bash /usr/libexec/kubernetes/kube-addons.sh
           └─30212 /usr/bin/kubectl get --namespace=kube-system serviceaccount default -o go-template={{with index .secrets 0}}{{.name}}{{end}}

May 03 10:53:30 cd3labvdapp002 kube-addons.sh[13835]: error: output format "go-template={{with index .secrets 0}}{{.name}}{{end}}" not recognized
May 03 10:53:31 cd3labvdapp002 kube-addons.sh[13835]: error: output format "go-template={{with index .secrets 0}}{{.name}}{{end}}" not recognized

Does the kube system namespace exist?
 Failed creating a mirror pod "fluentd-elasticsearch-cd3labvdapp002_kube-system": Pod "fluentd-elasticsearch-cd3labvdapp002" is forbidden: Namespace kube-system does not exist

As per the log it does not and I checked it too. The addons should create
it before installing themselves, I suppose. I am using the contrib repo's
ansible script.
On May 3, 2016 9:51 PM, "Prashanth B"<EMAIL_ADDRESS>wrote:

Does the kube system namespace exist?
Failed creating a mirror pod "fluentd-elasticsearch-cd3labvdapp002_kube-system": Pod "fluentd-elasticsearch-cd3labvdapp002" is forbidden: Namespace kube-system does not exist
—
You are receiving this because you authored the thread.
Reply to this email directly or view it on GitHub
https://github.com/kubernetes/contrib/issues/886#issuecomment-216718978

is the kubelet service up?

[rakeshk@cd3labvdapp002 group_vars]$ kubectl describe node cd3labvdapp002
Name:                   cd3labvdapp002
Labels:                 kubernetes.io/hostname=cd3labvdapp002
CreationTimestamp:      Sun, 01 May 2016 22:30:59 -0400
Conditions:
Type          Status  LastHeartbeatTime
LastTransitionTime
Reason                                  Message
Ready         True    Tue, 03 May 2016 23:09:05 -0400         Mon, 02 May
2016 16:24:28 -0400         kubelet is posting ready status
Addresses:      <IP_ADDRESS>
Capacity:
memory:        8008352Ki
pods:          40
cpu:           2
Version:
Kernel Version:                3.10.0-229.el7.x86_64
OS Image:                      Red Hat Enterprise Linux
Container Runtime Version:     docker://1.8.2-el7
Kubelet Version:               v<IP_ADDRESS>+b9a88a7d0e357b
Kube-Proxy Version:            v<IP_ADDRESS>+b9a88a7d0e357b
ExternalID:                     cd3labvdapp002
Pods:                           (2 in total)
Namespace                     Name
default                       nginx-qi9zm
default                       nginx-scy94
No events.
On Tue, May 3, 2016 at 11:01 PM, Guohua Ouyang<EMAIL_ADDRESS>wrote:

is the kubelet service up?
—
You are receiving this because you authored the thread.
Reply to this email directly or view it on GitHub
https://github.com/kubernetes/contrib/issues/886#issuecomment-216730753

[rakeshk@cd3labvdapp002 group_vars]$ kubectl describe node cd3labvdapp002
Name:                   cd3labvdapp002
Labels:                 kubernetes.io/hostname=cd3labvdapp002
CreationTimestamp:      Sun, 01 May 2016 22:30:59 -0400
Conditions:
  Type          Status  LastHeartbeatTime                       LastTransitionTime                      Reason                                  Message
  Ready         True    Tue, 03 May 2016 23:09:05 -0400         Mon, 02 May 2016 16:24:28 -0400         kubelet is posting ready status
Addresses:      <IP_ADDRESS>
Capacity:
 memory:        8008352Ki
 pods:          40
 cpu:           2
Version:
 Kernel Version:                3.10.0-229.el7.x86_64
 OS Image:                      Red Hat Enterprise Linux
 Container Runtime Version:     docker://1.8.2-el7
 Kubelet Version:               v<IP_ADDRESS>+b9a88a7d0e357b
 Kube-Proxy Version:            v<IP_ADDRESS>+b9a88a7d0e357b
ExternalID:                     cd3labvdapp002
Pods:                           (2 in total)
  Namespace                     Name
  default                       nginx-qi9zm
  default                       nginx-scy94
No events.

There is a problem that kubelet service is not restarted because "state=started" is missing in  [1].
I could see that namespace=kube-system is not created when kubelet is not running.
https://github.com/kubernetes/contrib/blob/master/ansible/roles/node/tasks/main.yml#L62

@gouyang you are right - here is the service log (for some reason the service shows as enabled):
[rakeshk@cd3labvdapp002 kubernetes]$ sudo systemctl status kubelet
● kubelet.service - Kubernetes Kubelet Server
   Loaded: loaded (/usr/lib/systemd/system/kubelet.service; enabled; vendor preset: disabled)
   Active: active (running) since Mon 2016-05-02 16:24:25 EDT; 1 day 7h ago
     Docs: https://github.com/GoogleCloudPlatform/kubernetes
 Main PID: 21002 (kubelet)
   Memory: 52.1M
   CGroup: /system.slice/kubelet.service
           └─21002 /usr/bin/kubelet --logtostderr=true --v=0 --api-servers=https://cd3labvdapp002:443 --address=<IP_ADDRESS> --hostname-override=cd3labvdapp002 --allow-privileged=true --kubeconfig=/etc/kubernetes/kubelet.kub...

May 04 00:18:41 cd3labvdapp002 kubelet[21002]: E0504 00:18:41.921333   21002 kubelet.go:1260] Failed creating a mirror pod "fluentd-elasticsearch-cd3labvdapp002_kube-system": Pod "fluentd-elasticsearch-cd... does not exist
May 04 00:18:51 cd3labvdapp002 kubelet[21002]: E0504 00:18:51.947640   21002 kubelet.go:1260] Failed creating a mirror pod "fluentd-elasticsearch-cd3labvdapp002_kube-system": Pod "fluentd-elasticsearch-cd... does not exist
May 04 00:19:01 cd3labvdapp002 kubelet[21002]: E0504 00:19:01.938249   21002 kubelet.go:1260] Failed creating a mirror pod "fluentd-elasticsearch-cd3labvdapp002_kube-system": Pod "fluentd-elasticsearch-cd... does not exist
May 04 00:19:11 cd3labvdapp002 kubelet[21002]: E0504 00:19:11.943662   21002 kubelet.go:1260] Failed creating a mirror pod "fluentd-elasticsearch-cd3labvdapp002_kube-system": Pod "fluentd-elasticsearch-cd... does not exist
May 04 00:19:21 cd3labvdapp002 kubelet[21002]: E0504 00:19:21.961166   21002 kubelet.go:1260] Failed creating a mirror pod "fluentd-elasticsearch-cd3labvdapp002_kube-system": Pod "fluentd-elasticsearch-cd... does not exist
May 04 00:19:31 cd3labvdapp002 kubelet[21002]: E0504 00:19:31.964801   21002 kubelet.go:1260] Failed creating a mirror pod "fluentd-elasticsearch-cd3labvdapp002_kube-system": Pod "fluentd-elasticsearch-cd... does not exist
May 04 00:19:41 cd3labvdapp002 kubelet[21002]: E0504 00:19:41.966213   21002 kubelet.go:1260] Failed creating a mirror pod "fluentd-elasticsearch-cd3labvdapp002_kube-system": Pod "fluentd-elasticsearch-cd... does not exist
May 04 00:19:51 cd3labvdapp002 kubelet[21002]: E0504 00:19:51.981382   21002 kubelet.go:1260] Failed creating a mirror pod "fluentd-elasticsearch-cd3labvdapp002_kube-system": Pod "fluentd-elasticsearch-cd... does not exist
May 04 00:20:02 cd3labvdapp002 kubelet[21002]: E0504 00:20:02.004098   21002 kubelet.go:1260] Failed creating a mirror pod "fluentd-elasticsearch-cd3labvdapp002_kube-system": Pod "fluentd-elasticsearch-cd... does not exist
May 04 00:20:11 cd3labvdapp002 kubelet[21002]: E0504 00:20:11.997205   21002 kubelet.go:1260] Failed creating a mirror pod "fluentd-elasticsearch-cd3labvdapp002_kube-system": Pod "fluentd-elasticsearch-cd... does not exist
Hint: Some lines were ellipsized, use -l to show in full.

But the docker containers have fluentd-elasticsearch running:
[rakeshk@cd3labvdapp002 kubernetes]$ docker ps
CONTAINER ID        IMAGE                                                 COMMAND                  CREATED             STATUS              PORTS               NAMES
ec4a6def71b7        nginx                                                 "nginx -g 'daemon off"   31 hours ago        Up 31 hours                             k8s_nginx.9a41f625_nginx-scy94_default_a2af7a52-1084-11e6-967c-0050563c011d_976b8716
f49c3ea9da02        nginx                                                 "nginx -g 'daemon off"   31 hours ago        Up 31 hours                             k8s_nginx.9a41f625_nginx-qi9zm_default_9fc6ec6f-1084-11e6-967c-0050563c011d_6c323271
20857b4cb7a1        gcr.io/google_containers/pause:0.8.0                  "/pause"                 31 hours ago        Up 31 hours                             k8s_POD.e4cc795_nginx-scy94_default_a2af7a52-1084-11e6-967c-0050563c011d_40248c36
fa55a751b87f        gcr.io/google_containers/pause:0.8.0                  "/pause"                 31 hours ago        Up 31 hours                             k8s_POD.e4cc795_nginx-qi9zm_default_9fc6ec6f-1084-11e6-967c-0050563c011d_f7067a63
ecc923ff6a17        gcr.io/google_containers/fluentd-elasticsearch:1.15   "td-agent"               31 hours ago        Up 31 hours                             k8s_fluentd-elasticsearch.cb72b3a7_fluentd-elasticsearch-cd3labvdapp002_kube-system_53df16aa2e7689fc1b6b812b9e9772bf_6d8dbf8e
2323c076f835        gcr.io/google_containers/pause:0.8.0                  "/pause"                 31 hours ago        Up 31 hours                             k8s_POD.e4cc795_fluentd-elasticsearch-cd3labvdapp002_kube-system_53df16aa2e7689fc1b6b812b9e9772bf_e13c647f

There are mainly two problems:

kube-system namespace is not created, which cause addons cannot be not created.
https://github.com/kubernetes/kubernetes/issues/23973  is fixed for Atomic host.

and I opened this
https://github.com/kubernetes/contrib/pull/895

skydns is not created because of error like below

kubectl create -f skydns-rc.yaml
error validating "skydns-rc.yaml": error validating data: [found invalid field failureThreshold for v1.Probe, found invalid field successThreshold for v1.Probe]; if you choose to ignore these errors, turn validation off with --validate=false
you need to run it manually.
$ kubectl create -f /etc/kubernetes/addons/dns/skydns-rc.yaml --validate=false

@gouyang I made the fix locally and reran the playbook but still have the same issue. For some reason the kube-system namespace is not getting created. Kubelet service has the same log as above. Here is logfile snippet:
2016-05-04 08:18:06,420 p=1147 u=rakeshk |  TASK [node : Enable kubelet] ***************************************************
2016-05-04 08:18:06,420 p=1147 u=rakeshk |  task path: /home/rakeshk/contrib/ansible/roles/node/tasks/main.yml:61
2016-05-04 08:18:06,883 p=1147 u=rakeshk |  ok: [cd3labvdapp005] => {"changed": false, "enabled": true, "invocation": {"module_args": {"arguments": "", "enabled": true, "name": "kubelet", "pattern": null, "runlevel": "default", "sleep": null, "state": "started"}, "module_name": "service"}, "name": "kubelet", "state": "started"}
2016-05-04 08:18:06,898 p=1147 u=rakeshk |  ok: [cd3labvdapp004] => {"changed": false, "enabled": true, "invocation": {"module_args": {"arguments": "", "enabled": true, "name": "kubelet", "pattern": null, "runlevel": "default", "sleep": null, "state": "started"}, "module_name": "service"}, "name": "kubelet", "state": "started"}
2016-05-04 08:18:06,942 p=1147 u=rakeshk |  ok: [cd3labvdapp003] => {"changed": false, "enabled": true, "invocation": {"module_args": {"arguments": "", "enabled": true, "name": "kubelet", "pattern": null, "runlevel": "default", "sleep": null, "state": "started"}, "module_name": "service"}, "name": "kubelet", "state": "started"}
2016-05-04 08:18:07,080 p=1147 u=rakeshk |  ok: [cd3labvdapp002] => {"changed": false, "enabled": true, "invocation": {"module_args": {"arguments": "", "enabled": true, "name": "kubelet", "pattern": null, "runlevel": "default", "sleep": null, "state": "started"}, "module_name": "service"}, "name": "kubelet", "state": "started"}

When I try to run the command you asked to run manually I get the following:
[rakeshk@cd3labvdapp002 ansible]$ kubectl create -f /etc/kubernetes/addons/dns/skydns-rc.yaml --validate=false
Error from server: error when creating "/etc/kubernetes/addons/dns/skydns-rc.yaml": ReplicationController "kube-dns-v11" is forbidden: Namespace kube-system does not exist

I manually created the kube-system namespace and then loaded other add-ons. Wonder why the namespace is not loaded by the script automatically? The /var/log/messages has these repeated messages:
kube-addons.sh: error: output format "go-template={{with index .secrets 0}}{{.name}}{{end}}" not recognized
I can not find reference to these in any of the scripts so it must be part of downloaded programs. Is there something wrong with compilation upstream?

kube-addons.sh: error: output format "go-template={{with index .secrets 0}}{{.name}}{{end}}" not recognized
Could not see this error here:
# kubectl get serviceaccount default -o go-template="{{with index .secrets 0}}{{.name}}{{end}}" default-token-fcvuv
What kubernetes version are you using?

This is what I get:
[~]$ kubectl get serviceaccount default -o go-template="{{with index .secrets 0}}{{.name}}{{end}}"
error: output format "go-template={{with index .secrets 0}}{{.name}}{{end}}" not recognized

[ ~]$ kubectl version
Client Version: version.Info{Major:"1", Minor:"0.3", GitVersion:"v<IP_ADDRESS>+b9a88a7d0e357b", GitCommit:"b9a88a7d0e357be2174011dd2b127038c6ea8929", GitTreeState:"clean"}
Server Version: version.Info{Major:"1", Minor:"0.3", GitVersion:"v<IP_ADDRESS>+b9a88a7d0e357b", GitCommit:"b9a88a7d0e357be2174011dd2b127038c6ea8929", GitTreeState:"clean"}

I think you should at least upgrade to kube 1.2 version, it has been release for a while.
And the namespace problem should be gone in next release, the dns addon should still need create manually on that release.

I think it was installed through the ansible script itself. Do I need to tweak the script to upgrade?

Is there a way to tear down the entire install and install a fresh?

I think it was installed through the ansible script itself. Do I need to tweak the script to upgrade?

no, the script is already doing that for you. You need to check whether you have subscribe the Red Hat related pool and enabled that repo.

Is there a way to tear down the entire install and install a fresh?

 How can I get the 1.2 rpm?

@gouyang can you send me the redhat pool so that I can confirm. I can only see the 1.0.3 rpm.

The pool should be different for each subscriber, do you enabled the rhel-7-server-extras-rpms?

I have that repo but I could  only see version 1.0.3 for kubernetes.
I tried localInstall as well - but that did not seem to work for some
reason. The document is vague about the package location etc. I will check
with redhat rep to find out more on the subscription part.
On May 5, 2016 7:14 PM, "Guohua Ouyang"<EMAIL_ADDRESS>wrote:

The pool should be different for each subscriber, do you enabled the
rhel-7-server-extras-rpms?
—
You are receiving this because you authored the thread.
Reply to this email directly or view it on GitHub
https://github.com/kubernetes/contrib/issues/886#issuecomment-217306666

@gouyang I did get the version 1.2 of kubernetes and did a fresh install. This is the error that I get out of journalctl -xe
May 06 15:41:36 cd3labvdapp002 kube-addons.sh[24297]: Error from server: serviceaccounts "default" not found

@rakesh-k Good to know you have kube 1.2 now, but this version still have the namespace problem, it's issue https://github.com/kubernetes/contrib/issues/777. Wait for next update from Red Hat, this problem is fixed, see https://bugzilla.redhat.com/show_bug.cgi?id=1327335.
You can change "apply" to "create" in kube-addons.sh to fix the namespace issue.
The skydns still need to create manually in next release.

@gouyang I changed the kube-addons.sh file to use create. (I had already created the namespace by simply executing the kubectl create command) I see 2 issues now:

the script assumes that it is being run for the first time and thus the 'kube-system' namespace does not exist. But if it does then it does not know how to handle it and keeps on looping for a while.

The script expects /etc/kubernetes/admission-controls but that does not exist. Which ansible role/task is supposed to create that?

rpm -qa | grep kubernetes
kubernetes-client-1.2.0-0.11.git738b760.el7.x86_64
kubernetes-master-1.2.0-0.11.git738b760.el7.x86_64
kubernetes-node-1.2.0-0.11.git738b760.el7.x86_64
kubernetes-debuginfo-1.2.0-0.6.alpha1.git8632732.el7.x86_64

Installing the addons from the kubernetes/contrib master HEAD.
kubectl cluster-info
Kubernetes master is running at http://localhost:8080
Elasticsearch is running at http://localhost:8080/api/v1/proxy/namespaces/kube-system/services/elasticsearch-logging
Heapster is running at http://localhost:8080/api/v1/proxy/namespaces/kube-system/services/heapster
Kibana is running at http://localhost:8080/api/v1/proxy/namespaces/kube-system/services/kibana-logging
KubeDNS is running at http://localhost:8080/api/v1/proxy/namespaces/kube-system/services/kube-dns
Grafana is running at http://localhost:8080/api/v1/proxy/namespaces/kube-system/services/monitoring-grafana
InfluxDB is running at http://localhost:8080/api/v1/proxy/namespaces/kube-system/services/monitoring-influxdb

kubectl get ns
NAME          STATUS    AGE
default       Active    271d
kube-system   Active    71d

@gouyang can you confirm? My steps:

provision one node (or VM)
install the latest rpms from brew
clone contrib repository
use this inventory file[masters]

localhost ansible_connection=local
[nodes]
localhost ansible_connection=local
[etcd]
localhost ansible_connection=local

1. update ``ansible/roles/master/tasks/main.yml`` removing everything up to the first task, i.e. keep

include: coreos.yml
when: is_coreos

The reason is to skip the part where the kube is installed via ansible scripts.

1. run ``ansible-playbook -i inventory.txt --tags addons ./cluster.yml`` under ansible directory

It works even if you skip step 5. I just takes a little longer and you can get:
TASK: [master | Open firewalld port for apiserver] ****************************
failed: [localhost] => {"failed": true, "parsed": false}
BECOME-SUCCESS-htxvrlcmqglyvwmlyicygqxgorjwmcbt
failed=True msg='failed to connect to the firewalld daemon'

Anyway, the ansible roles should be rewritten to be able to just run the minimal subset of roles to install kube-addons on system with kubernetes already installed on.

For better refinement of the roles: https://github.com/kubernetes/contrib/issues/1280

@ingvagabund Your steps are right.

@rakesh-k All problem are fixed, could you please take a look at this again?

@rakesh-k I am closing the issue for now. If you find the add-ons still does not work, please open a new issue.


[libsamplerate] CMake targets are missing

Unlike its sibling libsndfile, libsamplerate doesn't provide CMake targets, so commands like find_package and target_link_libraries can't be used.  It would be great to add such feature to libsamplerate in order to ease the inclusion in a CMake-based project.

Hi @gvnnz
Thanks for posting this issue.
Generally, we prefer to use CMake targets that provided by upstream instead of vcpkg.
I noticed that libsamplerate has implemented this feature in latest changes by upstream.
https://github.com/libsndfile/libsamplerate/blob/master/src/CMakeLists.txt
So we might need to update libsamplerate to support CMake targets.

libsamplerate

I have a commit which uses libsamplerate master branch in https://github.com/mixxxdj/vcpkg/pull/4
I have also opened an upstream PR to make vcpkg support easier.

I have a commit which uses libsamplerate master branch in https://github.com/mixxxdj/vcpkg/pull/4
I have also opened an upstream PR to make vcpkg support easier.

Upstream accepted my PR and I updated the portfile.cmake in https://github.com/mixxxdj/vcpkg/pull/8 . Once upstream finally makes a new release, it will be easy to simply update the commit hash.

Upstream accepted my PR and I updated the portfile.cmake in https://github.com/mixxxdj/vcpkg/pull/8 . Once upstream finally makes a new release, it will be easy to simply update the commit hash.

Fixed by #15797. This issue can be closed now.

Thanks for your help @Be-ing.


Preset Points on Reolink E1 Pro / E1 Zoom

I have two Redolink E1 Pro and one E1 Zoom succesfully working in HA.
But Preset Points in one Cam is working fine with shortcuts, but in the other cams it´s not.
Is it possible that Reolink cams dont´t use  preset: '001' .... preset: '006' for all cams in the network?
But why is it working in one cam, in the others not. The E1 Pro´s are both exactly same Hard- and Firmware Versions.
Or is there something missing with onvif Protocoll not working?
How can I find out how the presets are named in the cams for the onvif_protocol? In Reolink app all is working fine.
Maybe someone has same fault or a way to get it working for all Reolink cams?
Thanx for help.
cheers
Dirk

Your question not related to this integration


Tools 143 improved warnings and errors for na values

Added code to catch and output informative error in case of 'author_cell_type' column containing NaN values.
Changed warning logging so that the columns that contain NaN values are output to the command prompt screen for wrangler convenience.

Looks good to me!


New package: Minio v0.1.0-alpha1

Registering package: Minio
Repository: https://github.com/sjpeterson/Minio.jl
Created by: @sjpeterson
Version: v0.1.0-alpha1
Commit: df86c4224d8905801ce617b8d9df9df00437aa0a
Git reference: v0.1.0-alpha1

This premature pull request is the result of problems finding the documentation. Feel free to discard.


it show window not respoding

We have written the needed data into your clipboard because it was too large to send. Please paste.

/duplicate
Marking as duplicate of https://github.com/microsoft/vscode/issues/178962. Please let us know if McAfee is not installed on your PC, else use the instructions to resolve.


Trying to concat from another folder fails

Right now I'm having babel transpile my code into a separate build folder.
When I run module-concat against that build folder from the parent folder the resulting contact'ed file has 'build' in several places where __dirname are used. I've tried various combinations of the API to no success.
If I go into the build folder and execute module-concat from there it works. What I'm trying to do is it automate the process from a parent folder which doesnt work.

Are you passing the outputPath option to module-concat?  Can you post a little code here?

Hi @bminer
Initially I was running it this way which was failing (and I did try using outputPath without success...
modConcat("build/index.js", "index.concat.js", {excludeNodeModules:true}, function(err, stats) {
						if(err) {
							console.error(err)
						}
						done(err);
					});

But now I am running it like so:
modConcat("build/index.js", "build/index.concat.js", {excludeNodeModules:true}, function(err, stats) {
						if(err) {
							console.error(err)
						}

					});

@tm1000 - Your issue makes more sense now. Your output file path affects how __dirname and __filename are resolved. I can't remember exactly how it works off of the top of my head, but... you can check out the code to learn more if you're ever interested. :)
Glad to hear that you like module-concat! I've been thinking about a gulp / grunt module with sourcemap support, but I haven't had the time to work on this yet.

@bminer I started work on a grunt plugin for your module but it would strangely get stuck in the middle of the stream and just error out. Instead I'm running your module using grunt exec which allows me to run code within a grunt task.

@tm1000 - Cool. Yeah, I've never used grunt myself, so I can't really be of much help. I'm kind of waiting for Gulp v4 (sigh... years in the making) before investing time in building a Gulp plugin.


Oculus Integrations not working correctly with VRTK

VRTK Source:Github
VRTK Version: 3.3.0 (I think or whatever most recent master is called)
Unity3D Version: 2018.1.0f2
Using Oculus
Oculus Utilities 1.27.0
Steps to reproduce
Switch the Oculus SDK in an pointer example scene to Oculus Utilities and play.
Expected behavior
Each hands pointer is dependent on its own hand's touch pad inputs.
Current behavior
Left hand inputs control both hands inputs. So, when you touch the joystick both hand's pointers activate, but on right hand inputs no output.
Other Notes
Local avatar works perfectly fine finger positions respond accurately to actual finger positions. Tracking is fine. Touch and near touch still work correctly, but in order to grab an object with right hand left hand grab needs to be used. All inputs work correctly through UnityXR.

Some Deisim players reported me the exact same issue.
VRTK 3.3.0
Unity 2018.2.1
Oculus Utilities 1.27 (but the first report was with the previous version)

The issue seems to happen when there is another controller plugged in to the computer.

That makes sense because it was working fine then it just wouldn't work anymore. I did buy a new Xbox controller for my PC around the time of this post.

@grizzlypath26 @quintesse Don't hesitate to try my pull request to confirm that it solve the issue on your site so we can merge it to the main branch.
Thank you in advance for your help.


🤑

Feature Request
Motivation Behind Feature

Feature Description

Alternatives or Workarounds

Did you have any issues with the last release?


Convert some non-store Singletons to normal injectables

ClusterManager
KubeconfigSyncManager
LensProxy
WindowManager

Other work:

Convert logger to be an injection token, add createChildLogger to
abstract away the need for logPrefix
Fix tests

Signed-off-by: Sebastian Malton<EMAIL_ADDRESS>

I made this PR as a prerequisite to work that I am doing for https://github.com/lensapp/lens/issues/4652 to help testing easier.
I hope this isn't too hard to review as I tried to only move stuff around and change a few imports.

Closing this as most of this work is covered (by accident in #5324 )


Editor's view should follow cursor in these cases

VSCode Version: 1.10.2
OS Version: Ubuntu 16.04

Jump to Bracket:

Choose a completion:

This does not happen in Atom and Sublime.

In the first case this appears to be fixed, but I can still reproduce for the accepting completion case:


"Linking with cc failed" -- issue compiling?

Hey folks! I'm having what appears to be some issue compiling. Do you have any thoughts or suggestions about what might be going on here?
The closest I can find seems to point to a cargo or mac error:
https://github.com/rust-lang/rust/issues/25289#issuecomment-101352844
https://github.com/rust-lang/rust/issues/60149#issuecomment-485253621
I'm really quite a newbie at rust, so any debugging advice is appreciated!
Code :
use faiss::{index_factory, MetricType};

pub fn run_query() -> Option<f32>{
    let mut index = index_factory(3, "Flat", MetricType::L2).unwrap();
    Some(0.0)
}

Dependency:
[dependencies]
"faiss" = {version = "0.6.0"}

Error:
error: linking with `cc` failed: exit status: 1
  |
  = note: "cc" "-m64" "-arch" "x86_64" "-L" "/Users/bradwindsor/.rustup/toolchains/nightly-x86_64-apple-darwin/lib/rustlib/x86_64-apple-darwin/lib" "/Users/bradwindsor/ms_projects/thistle/thistle/target/debug/deps/thistle.1npak595a7css8z4.rcgu.o" "/Users/bradwindsor/ms_projects/thistle/thistle/target/debug/deps/thistle.20hce9hmqhl203kn.rcgu.o" "/Users/bradwindsor/ms_projects/thistle/thistle/target/debug/deps/thistle.2m6hiy95l4iyrwu5.rcgu.o" "/Users/bradwindsor/ms_projects/thistle/thistle/target/debug/deps/thistle.2wd4t96zh75gv0va.rcgu.o" "/Users/bradwindsor/ms_projects/thistle/thistle/target/debug/deps/thistle.3aclf5rjqxhrola4.rcgu.o" "/Users/bradwindsor/ms_projects/thistle/thistle/target/debug/deps/thistle.chnosn5cykoslmi.rcgu.o" "/Users/bradwindsor/ms_projects/thistle/thistle/target/debug/deps/thistle.sf29mzngf3nyfuf.rcgu.o" "-o" "/Users/bradwindsor/ms_projects/thistle/thistle/target/debug/deps/thistle" "/Users/bradwindsor/ms_projects/thistle/thistle/target/debug/deps/thistle.1vtd5t81sh40jhul.rcgu.o" "-Wl,-dead_strip" "-nodefaultlibs" "-L" "/Users/bradwindsor/ms_projects/thistle/thistle/target/debug/deps" "-L" "/Users/bradwindsor/ms_projects/thistle/thistle/target/debug/build/torch-sys-ff3e9973ea28b04e/out/libtorch/libtorch/lib" "-L" "/Users/bradwindsor/ms_projects/thistle/thistle/target/debug/build/torch-sys-ff3e9973ea28b04e/out" "-L" "/Users/bradwindsor/ms_projects/thistle/thistle/target/debug/build/bzip2-sys-7fb991f7dbc50a4c/out/lib" "-L" "/Users/bradwindsor/.rustup/toolchains/nightly-x86_64-apple-darwin/lib/rustlib/x86_64-apple-darwin/lib" "/Users/bradwindsor/ms_projects/thistle/thistle/target/debug/deps/libthistle-d4a6c2bff82dd787.rlib" "/Users/bradwindsor/ms_projects/thistle/thistle/target/debug/deps/librust_bert-31fa07c451540f80.rlib" "/Users/bradwindsor/ms_projects/thistle/thistle/target/debug/deps/libitertools-1dfefb650b8cd53d.rlib" "/Users/bradwindsor/ms_projects/thistle/thistle/target/debug/deps/librust_tokenizers-c31d0d587cde9540.rlib" "/Users/bradwindsor/ms_projects/thistle/thistle/target/debug/deps/libcsv-ed679ac6734a6098.rlib" "/Users/bradwindsor/ms_projects/thistle/thistle/target/debug/deps/libcsv_core-d75bfe6d0b9a8acb.rlib" "/Users/bradwindsor/ms_projects/thistle/thistle/target/debug/deps/libbstr-c0070e4a1cc2d79c.rlib" "/Users/bradwindsor/ms_projects/thistle/thistle/target/debug/deps/libregex_automata-87878d88ec463ae2.rlib" "/Users/bradwindsor/ms_projects/thistle/thistle/target/debug/deps/libserde_json-21d54dcd579fec67.rlib" "/Users/bradwindsor/ms_projects/thistle/thistle/target/debug/deps/libryu-90cf68ddeda11aee.rlib" "/Users/bradwindsor/ms_projects/thistle/thistle/target/debug/deps/libitoa-abc241418b49187a.rlib" "/Users/bradwindsor/ms_projects/thistle/thistle/target/debug/deps/libunicode_normalization-b2ce0f79e7c9edf9.rlib" "/Users/bradwindsor/ms_projects/thistle/thistle/target/debug/deps/libtinyvec-1c50f201c52e47ed.rlib" "/Users/bradwindsor/ms_projects/thistle/thistle/target/debug/deps/libtinyvec_macros-58d800761f45510a.rlib" "/Users/bradwindsor/ms_projects/thistle/thistle/target/debug/deps/libregex-7a5e938964f73b44.rlib" "/Users/bradwindsor/ms_projects/thistle/thistle/target/debug/deps/libregex_syntax-5efabd26812b2a98.rlib" "/Users/bradwindsor/ms_projects/thistle/thistle/target/debug/deps/libaho_corasick-35270916c15955fe.rlib" "/Users/bradwindsor/ms_projects/thistle/thistle/target/debug/deps/libmemchr-3f7b52af37b6f9bd.rlib" "/Users/bradwindsor/ms_projects/thistle/thistle/target/debug/deps/libitertools-ae0eacccf85a2ec4.rlib" "/Users/bradwindsor/ms_projects/thistle/thistle/target/debug/deps/librayon-bc7a015cc78390f5.rlib" "/Users/bradwindsor/ms_projects/thistle/thistle/target/debug/deps/librayon_core-99e1dad4e52206ec.rlib" "/Users/bradwindsor/ms_projects/thistle/thistle/target/debug/deps/libnum_cpus-0cc61c5a851016e3.rlib" "/Users/bradwindsor/ms_projects/thistle/thistle/target/debug/deps/libcrossbeam_deque-8134651f99d6d55c.rlib" "/Users/bradwindsor/ms_projects/thistle/thistle/target/debug/deps/libcrossbeam_epoch-5f4b888d78829961.rlib" "/Users/bradwindsor/ms_projects/thistle/thistle/target/debug/deps/libmemoffset-6a6eb427edffc44b.rlib" "/Users/bradwindsor/ms_projects/thistle/thistle/target/debug/deps/libscopeguard-31f20504eb2703cc.rlib" "/Users/bradwindsor/ms_projects/thistle/thistle/target/debug/deps/libcrossbeam_channel-6756a1e59e54d8c6.rlib" "/Users/bradwindsor/ms_projects/thistle/thistle/target/debug/deps/libcrossbeam_utils-a78a168a13cd1267.rlib" "/Users/bradwindsor/ms_projects/thistle/thistle/target/debug/deps/libeither-562e7f0a923e8f49.rlib" "/Users/bradwindsor/ms_projects/thistle/thistle/target/debug/deps/libordered_float-51fc742f3bcfcf51.rlib" "/Users/bradwindsor/ms_projects/thistle/thistle/target/debug/deps/libtch-574ba415f0a7b978.rlib" "/Users/bradwindsor/ms_projects/thistle/thistle/target/debug/deps/libndarray-20eeeae1632d9fd8.rlib" "/Users/bradwindsor/ms_projects/thistle/thistle/target/debug/deps/libmatrixmultiply-f4c1da960d45074e.rlib" "/Users/bradwindsor/ms_projects/thistle/thistle/target/debug/deps/libnum_complex-d55c58eb6e91e88f.rlib" "/Users/bradwindsor/ms_projects/thistle/thistle/target/debug/deps/libnum_integer-e553cc3e4c6712d2.rlib" "/Users/bradwindsor/ms_projects/thistle/thistle/target/debug/deps/libnum_traits-a75e93e9dc909b7f.rlib" "/Users/bradwindsor/ms_projects/thistle/thistle/target/debug/deps/librawpointer-af04cc4bb8e47631.rlib" "/Users/bradwindsor/ms_projects/thistle/thistle/target/debug/deps/libtorch_sys-2d9d21974de55caa.rlib" "/Users/bradwindsor/ms_projects/thistle/thistle/target/debug/deps/libzip-c44b3f38577791de.rlib" "/Users/bradwindsor/ms_projects/thistle/thistle/target/debug/deps/libtime-b0c05a3d813ace7b.rlib" "/Users/bradwindsor/ms_projects/thistle/thistle/target/debug/deps/libthiserror-68a9b42d4132521f.rlib" "/Users/bradwindsor/ms_projects/thistle/thistle/target/debug/deps/libbzip2-896046b3e15dd93a.rlib" "/Users/bradwindsor/ms_projects/thistle/thistle/target/debug/deps/libbzip2_sys-e17a3ea19e42b8cc.rlib" "/Users/bradwindsor/ms_projects/thistle/thistle/target/debug/deps/libflate2-6e853baf9c8b9e50.rlib" "/Users/bradwindsor/ms_projects/thistle/thistle/target/debug/deps/libminiz_oxide-8509711269a1300e.rlib" "/Users/bradwindsor/ms_projects/thistle/thistle/target/debug/deps/libadler32-51f964c75e3afbf2.rlib" "/Users/bradwindsor/ms_projects/thistle/thistle/target/debug/deps/libcfg_if-892e7cee77ae3329.rlib" "/Users/bradwindsor/ms_projects/thistle/thistle/target/debug/deps/libbyteorder-be28ddbc530eab12.rlib" "/Users/bradwindsor/ms_projects/thistle/thistle/target/debug/deps/libcrc32fast-6110fcd70cf2e9da.rlib" "/Users/bradwindsor/ms_projects/thistle/thistle/target/debug/deps/libfailure-ae0aa4a153df8b9f.rlib" "/Users/bradwindsor/ms_projects/thistle/thistle/target/debug/deps/libbacktrace-093e0afaa529e2b3.rlib" "/Users/bradwindsor/ms_projects/thistle/thistle/target/debug/deps/libobject-c15f758dd1367b9c.rlib" "/Users/bradwindsor/ms_projects/thistle/thistle/target/debug/deps/libaddr2line-1fc0fb83f501e321.rlib" "/Users/bradwindsor/ms_projects/thistle/thistle/target/debug/deps/libgimli-6174ef008c83096e.rlib" "/Users/bradwindsor/ms_projects/thistle/thistle/target/debug/deps/libcfg_if-a42ba01468c6d92e.rlib" "/Users/bradwindsor/ms_projects/thistle/thistle/target/debug/deps/librustc_demangle-9cc4760bb3afbdef.rlib" "/Users/bradwindsor/ms_projects/thistle/thistle/target/debug/deps/liblazy_static-98ea06d08472431a.rlib" "/Users/bradwindsor/ms_projects/thistle/thistle/target/debug/deps/libfaiss-c6a410c6f8ab2423.rlib" "/Users/bradwindsor/ms_projects/thistle/thistle/target/debug/deps/libfaiss_sys-74aeabac60e0cbd0.rlib" "/Users/bradwindsor/ms_projects/thistle/thistle/target/debug/deps/libuuid-7e702774b0c69b2c.rlib" "/Users/bradwindsor/ms_projects/thistle/thistle/target/debug/deps/libserde-7d7b34b7398292db.rlib" "/Users/bradwindsor/ms_projects/thistle/thistle/target/debug/deps/librand-90af94b665a55644.rlib" "/Users/bradwindsor/ms_projects/thistle/thistle/target/debug/deps/librand_xorshift-71f5c0bf8db7f494.rlib" "/Users/bradwindsor/ms_projects/thistle/thistle/target/debug/deps/librand_pcg-c9f195549219f059.rlib" "/Users/bradwindsor/ms_projects/thistle/thistle/target/debug/deps/librand_hc-7600fcdf91228ccb.rlib" "/Users/bradwindsor/ms_projects/thistle/thistle/target/debug/deps/librand_chacha-f72b2299b81d26aa.rlib" "/Users/bradwindsor/ms_projects/thistle/thistle/target/debug/deps/librand_isaac-8e1f8597c5ec4d3f.rlib" "/Users/bradwindsor/ms_projects/thistle/thistle/target/debug/deps/librand_core-4170c848b672f583.rlib" "/Users/bradwindsor/ms_projects/thistle/thistle/target/debug/deps/librand_os-5e84c8953b0ba2d6.rlib" "/Users/bradwindsor/ms_projects/thistle/thistle/target/debug/deps/librand_jitter-3cd042c23570d8ca.rlib" "/Users/bradwindsor/ms_projects/thistle/thistle/target/debug/deps/liblibc-c2fdc019e3d38deb.rlib" "/Users/bradwindsor/ms_projects/thistle/thistle/target/debug/deps/librand_core-92e42927a2b53f93.rlib" "/Users/bradwindsor/.rustup/toolchains/nightly-x86_64-apple-darwin/lib/rustlib/x86_64-apple-darwin/lib/libstd-46a061b08cc06738.rlib" "/Users/bradwindsor/.rustup/toolchains/nightly-x86_64-apple-darwin/lib/rustlib/x86_64-apple-darwin/lib/libpanic_unwind-7bebd2f04d2b9056.rlib" "/Users/bradwindsor/.rustup/toolchains/nightly-x86_64-apple-darwin/lib/rustlib/x86_64-apple-darwin/lib/libobject-8022bf77ecaec932.rlib" "/Users/bradwindsor/.rustup/toolchains/nightly-x86_64-apple-darwin/lib/rustlib/x86_64-apple-darwin/lib/libaddr2line-40998048b1ba428e.rlib" "/Users/bradwindsor/.rustup/toolchains/nightly-x86_64-apple-darwin/lib/rustlib/x86_64-apple-darwin/lib/libgimli-bd2a545ac887ab20.rlib" "/Users/bradwindsor/.rustup/toolchains/nightly-x86_64-apple-darwin/lib/rustlib/x86_64-apple-darwin/lib/libstd_detect-c0832a78f281aa17.rlib" "/Users/bradwindsor/.rustup/toolchains/nightly-x86_64-apple-darwin/lib/rustlib/x86_64-apple-darwin/lib/librustc_demangle-e84927fb7a338bcb.rlib" "/Users/bradwindsor/.rustup/toolchains/nightly-x86_64-apple-darwin/lib/rustlib/x86_64-apple-darwin/lib/libhashbrown-80e6dd310746668f.rlib" "/Users/bradwindsor/.rustup/toolchains/nightly-x86_64-apple-darwin/lib/rustlib/x86_64-apple-darwin/lib/librustc_std_workspace_alloc-70160232b7f5a1eb.rlib" "/Users/bradwindsor/.rustup/toolchains/nightly-x86_64-apple-darwin/lib/rustlib/x86_64-apple-darwin/lib/libunwind-dc1f6511b0655580.rlib" "/Users/bradwindsor/.rustup/toolchains/nightly-x86_64-apple-darwin/lib/rustlib/x86_64-apple-darwin/lib/libcfg_if-7606550a486f0fa7.rlib" "/Users/bradwindsor/.rustup/toolchains/nightly-x86_64-apple-darwin/lib/rustlib/x86_64-apple-darwin/lib/liblibc-d71be2efb2f94c3f.rlib" "/Users/bradwindsor/.rustup/toolchains/nightly-x86_64-apple-darwin/lib/rustlib/x86_64-apple-darwin/lib/liballoc-6bbd477ed289203f.rlib" "/Users/bradwindsor/.rustup/toolchains/nightly-x86_64-apple-darwin/lib/rustlib/x86_64-apple-darwin/lib/librustc_std_workspace_core-c7c7638eea6d267e.rlib" "/Users/bradwindsor/.rustup/toolchains/nightly-x86_64-apple-darwin/lib/rustlib/x86_64-apple-darwin/lib/libcore-ac475f5c856023a5.rlib" "/Users/bradwindsor/.rustup/toolchains/nightly-x86_64-apple-darwin/lib/rustlib/x86_64-apple-darwin/lib/libcompiler_builtins-35393beafda280dd.rlib" "-lc++" "-ltorch" "-ltorch_cpu" "-lc10" "-lfaiss_c" "-framework" "Security" "-liconv" "-lSystem" "-lresolv" "-lc" "-lm" "-liconv"
  = note: ld: library not found for -lfaiss_c

I suspect that the native library has not been built and installed beforehand. Have you built the C API of the Faiss library? Instructions are in the readme.
For version 0.9.0, you will need to build this revision of faiss_c. The upstream branches have substantial modifications which are yet to be released.

Yes, that was it, thank you for the fast response. Still working through; a bash install would be helpful in future versions.


Port to Clarity V3 and fix tests

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.OxMarco seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.You have signed the CLA already but the status is still pending? Let us recheck it.


ARR Showcase App - Failed to load model

Hi,

In Remote Rendering Showcase app, models from our blob container are getting listed under the menu but aren't loading when user press the load buttons. It shows error:  Failed to load model. Reason: Load model failed with status 'FileDownloadFailed'

Model names are listed correctly, and session is connecting without issues.
The issue started happening since 2-3 weeks. Before we were able to load models from blob container without issues.
Models are converted using ARRT, there in ARRT it is loading and rendering fine.
As I was using the release of Showcase app from some months ago, I thought maybe building it again might help, I pulled the latest release and took build, but no luck and still the same error.

The sessionId:Arr62aa7224c6db19a77341a90b69b05440

I also have given storage account access to remote rendering account, following this documentation https://docs.microsoft.com/en-us/azure/remote-rendering/how-tos/create-an-account#link-storage-accounts:

Thanks in advance.

Hi @selinkampa,
thank you for the report. The reason ARRT works and Showcase not is most likely because ARRT uses LoadModelFromSasAsync and Showcase uses LoadModelAsync. So there is probably a problem with the storage account linkage.
We are looking into the issue right now and will get back to you as soon as we can.
Cheers,
Christopher

It looks like the ARR account was moved to another subscription. In that case, the problem can probably be fixed by turning the system assigned managed identity off and on again:

You might need to re-link your storage account with your arr account after doing this.

Just wanted to add some info in addition to what @ChristopherManthei already covered:

From discussions in a separate thread, my understanding is your Azure resources were moved to a different org / tenant ? This would explain why the service is now unable to access storage. Unfortunately, attached identities cannot move with the resource as mentioned here: List role assignments for managed identities

Managed identities do not get updated when a subscription is transferred to another directory. As a result, any existing system-assigned or user-assigned managed identities will be broken. After the transfer, you can re-enable any system-assigned managed identities.

The same note applies even if only resources were moved to a subscription in a different tenant instead of the whole subscription.

Also, managed identities cannot be used to access resources in a different tenant as mentioned here: Can I use a managed identity to access a resource in a different directory/tenant?

Managed identities do not currently support cross-directory scenarios.

To summarize:

Both your ARR account/ resource and your storage account needs to be in the same tenant
Do toggle "System assigned" which will create and attach a new identity (with the same name but different ID in the new tenant) then you'll need to re-assign permissions to your storage account as per: re-link your storage account.

Apologies for the inconvenience.

Dear @ChristopherManthei and @jeofyoung,
thank you so much for the support.
It was indeed about the migration of the tenant, there must be something going wrong during that.
First I tried toggling "System assigned", which did remove the "undefined identity" and the name of the remote rendering account was shown in the assigned roles list again. But that didn't fix the issue, and I still couldn't load models.
In the separate thread, I received one more comment additional to what you said, which is to open a new remote rendering account if toggling wouldn't help. Once I opened a second remote rendering account in the new tenant and linked it with the existent blob storage, and took another Unity build with the new keys, it worked! We can render remotely again :)
Great work and support! Thanks once more.

Hi @selinkampa,
Thank you very much for reporting your results after re-creating the identity. It seems that something we enabled recently is causing an issue that prevented the newly created identity for your old account from getting registered which we will resolve. Thanks for helping us uncover this!


merge the service registry delta sql to v200-v210 as 2.1.0 is not released

What's the purpose of this PR
merge the service registry delta sql to v200-v210 as 2.1.0 is not released
Follow this checklist to help us incorporate your contribution quickly and easily:

[x] Read the Contributing Guide before making this pull request.
[x] Write a pull request description that is detailed enough to understand what the pull request does, how, and why.
[ ] Write necessary unit tests to verify the code.
[x] Run mvn clean test to make sure this pull request doesn't break anything.
[ ] Update the CHANGES log.

mark https://github.com/apolloconfig/apollo/pull/4595


HintAttribute.g.cs is missing using System;

Error: CS0246.
Not everyone has used global using.

Thanks bud.  On it.

Here's the requested fix if you need something straight away.
Just getting a csc crash with my tests when I turn off explicit usings :/
GodotSharp.SourceGenerators.2.2.1-231021-1714.Release.zip


SDL2: disable parallel make

Example failure: https://hydra.nixos.org/build/64494600
It could be fixed more properly, but for me it builds under 80 secs anyway.
Things done

[x] Tested using sandboxing (nix.useSandbox on NixOS, or option build-use-sandbox in nix.conf on non-NixOS)
Built on platform(s)

[x] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nox --run "nox-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
[x] Fits CONTRIBUTING.md.

You have committed this already to staging in 020a6663d319c7b4af5c0219bc451abdac12f62a.

Ah, you've committed this to gcc-7 in 80e8e555b4c2cd90701bbff664b1c8db6e81fd2f and I picked it to staging :)

:-D  I completely forgot.  Whoever merges, feel free to resolve the conflict in any sane way.


To cache top 100 articles

為了因應群組聊天的功能，bot sevrer 必須要把前 100 則常詢問且有回應的文章存起來，如此一來可以快速地查詢。

Since we plan to use word count as filter & do queries when word counts matches criteria, we no longer need caching now.


Condition/Fulfillment Enum Types and the actual Golang types are deeply coupled

The enum types ConditionType/FulfillmentType are highly coupled with the Golang types that actually implement the logic behind those types. This on its own is not really wrong, but it does stand in stark contrast with the promise that any chain that uses Rivine could overwrite the Conditions/Fulfillments. Something that isn't really true:

The wallet code relies on type assertions in order to know which output belongs it. It does so in order to be able to know how to find the UnlockHashes, within that condition, it owns;
Our CLI code has an entire section devoted to AtomicSwaps, yet how is that series of commands functional, or even useful, if a Rivine-based chain either doesn't implement that type or uses that enum value for an entirely different kind of condition/fulfillment;

There might be some other examples, but this is from the top of my hat.
That makes the choice of allowing any Condition/Fulfillment type to be registered questionable. Because for example what use is it to be able to overwrite or delete the AtomicSwapCondition for let's say a stack-based SCRIPT condition, if there is an entire series of commands hardcoded in your CLI that relies on this type to be exactly what it was, an AtomicSwapCondition.
On the other hand allowing to overwrite for example a condition did make it easy for TFChain to define extra checks, as to allow it to disallow that type of condition until a certain block height. Surely enough that was possible as well if we would have provided some kind of (configurable) block height constant.
Allowing custom conditions/fulfillment types for a chain implemented using Rivine does remain useful, as it allows to define specific type of conditions that are unique to a a chain. But it is becoming questionable if it is useful to being able to overwrite condition/fulfillment types that we provide together with Rivine. And if that is not the thing that is questionable, than surely the way we currently allow it is.

The enum types ConditionType/FulfillmentType are highly coupled with the Golang types that actually implement the logic behind those types.

This is why tfchain is having troubles with their multisig outputs, as reported at threefoldfoundation/tfchain#142. It is due to the fact that the Rivine code relies on the fact that there is  a *types.MultiSignatureCondition used for MultiSigs. This raw type assertion doesn't really work for Tfhcain as they wrap our type as type MultiSIgnatureCondition struct { types.MultiSignatureCondition}. This way, our type assertion doesn't work, and thus our wallet cannot handle our type.
In order to have tfchain being not blocking on this issue, it could manually patch the Rivine code by having the wallet code try it based on an interface type instead, which makes it possible to implement the MultSignatureCondition in any kind of way. This would be an easy fix to the problem at hand, allowing tfchain to be unblocked, while keeping their custom block-height limit for multisigs.
That quick (see: dirty) fix does however not fix the design mistake discussed earlier in this issue.

Clearly the Git hook does not understand the keyword not in front of resolve, as in:

`This commit [34ab7ab] does not resolve #404, but it may serve as a starting point.


Bsb error lines swallowed

Finally found a repro for this:
git clone https://github.com/tiensonqin/reason-error.git
cd reason-error
npm install
npm start

Doesn't happen when you run ./node_modules/.bin/bsb

This should be fixed in the most recent beta<EMAIL_ADDRESS>

Woah!


Remove CreateChannel() method from LB helper API.

This removes more surface area from the LB policy API, as requested by Sanjay.  It also eliminates a method from the ClientChannelFactory API, which is provided by most transports.  (The latter will require internal changes in order to import this PR, so I will probably do the import as a cherry-pick.)
Instead of creating channels through the helper, LB policies now go directly to the C-core API.  Eventually, they will be able to use the C generic bidi streaming callback API that we will build after we move to the callback API in C++.
Note that this change does slightly change the semantics of how grpclb or xds interact with alternative transports.  Prior to this PR, using the helper to create the balancer channel ensured that the balancer channel would always use the same transport as the parent channel; with this PR, grpclb and xds will always use the HTTP/2 transport.  This should be fine for now, since we don't actually have any use-cases where we need to use grpclb or xds with any other transport (inproc and cronet use direct channels and therefore don't support load balancing at all, and our internal quic transport is not currently used in production).  And if we do encounter such use-cases in the future, I suspect that we will want to address them in a different way anyway, since we will probably want to allow selecting the transport for the backend and balancer channels independently of each other.

This change is

@nicolasnoble, when you get a chance (not until after you're done with the upb work!), can you help me understand what's causing the linker errors under bazel?  It's not happening with make, so I assume I've got something wrong in the BUILD files somewhere.

The bazel build failures are resolved, so this should now be ready for re-review.


Grafana not displaying data

Hi, Grafana is not showing data after I did a docker-compose up, as shown below

Do I need to specify the query to in relations to the data.json i used?

Hi,
Can I see the data.json file that you used ?


Enable Prow for Auth

Jenkins job auth/presubmit passed

Jenkins job auth/presubmit passed

Prow presubmit available at https://k8s-gubernator.appspot.com/build/istio-prow/pull/istio_auth/190/auth-presubmit/9/

Jenkins job auth/presubmit passed

I don't see prow/auth-presubmit.sh shows in the list of checks. Is it expected or we need to enable it somewhere?

@lookuptable we will enable it by removing this line after this PR is merged and the prow/auth-presubmit file is in the master branch (otherwise we would have failing presubmits on all other PRs for this repo during the course of introducing this job).


fix: resolve tx dialog feedbacks and bugs

Changes

Swap tx status emojis with icons [SPE-312]
Update tx history chain symbol resolver [SPE-316]

SPE-312 SPE-316


tests/snapd: Add quick check for snap preseed handling

This PR adds a quick check to ensure that preseeds set via snap are handled.

Oh looks like the snapd test doesnt run, is that on purpose @simondeziel ?

@boltmark please can you enable this test in this section of the workflow and we'll see if it passes:
https://github.com/canonical/lxd-ci/blob/main/.github/workflows/tests.yml#L84-L177

@boltmark please can you enable this test in this section of the workflow and we'll see if it passes:
https://github.com/canonical/lxd-ci/blob/main/.github/workflows/tests.yml#L84-L177

Looks like su jenkins -c '/usr/sbin/lxc info' is failing with error message
su: user jenkins does not exist or the user entry does not contain all the required fields

@boltmark please can you enable this test in this section of the workflow and we'll see if it passes:
https://github.com/canonical/lxd-ci/blob/main/.github/workflows/tests.yml#L84-L177

Looks like su jenkins -c '/usr/sbin/lxc info' is failing with error message su: user jenkins does not exist or the user entry does not contain all the required fields

Please can you update to remove Jenkins references

You may need to update to use helpers and vars the other tests use

You may need to update to use helpers and vars the other tests use

If I am understanding correctly, we have the below check just to ensure we can use lxd as a user in the lxd group. Is there a particular reason we are using the jenkins user? If not, I've updated this check to just create and use a new user, but please let me know if I'm missing something here.
if [ "${ID}" != "ubuntu-core" ]; then
    (
        set -e
        usermod -G lxd -a jenkins || true
        LXC=$(which lxc)
        su jenkins -c "${LXC} info"
    )
    )
fi

I think we can remove references to ubuntu core and jenkins.

Oh looks like the snapd test doesnt run, is that on purpose @simondeziel ?

Indeed, it was never "ported" to GitHub CI.

@simondeziel I appreciate the review! I've made updates and left a few comments.
In the pipeline this test seems to fail to connect to images.lxd.canonical.com. This does not happen for me locally. Any idea why this is failing here?
$ lxc launch images:ubuntu-minimal-daily:24.04 unprivileged
Launching unprivileged
Error: Failed instance creation: Failed getting remote image info: Failed getting image: Failed parsing stream: Get "https://images.lxd.canonical.com/streams/v1/index.json": Unable to connect to: images.lxd.canonical.com:443 ([dial tcp <IP_ADDRESS>:443: connect: connection refused])

@simondeziel I appreciate the review! I've made updates and left a few comments.
In the pipeline this test seems to fail to connect to images.lxd.canonical.com. This does not happen for me locally. Any idea why this is failing here?
$ lxc launch images:ubuntu-minimal-daily:24.04 unprivileged
Launching unprivileged
Error: Failed instance creation: Failed getting remote image info: Failed getting image: Failed parsing stream: Get "https://images.lxd.canonical.com/streams/v1/index.json": Unable to connect to: images.lxd.canonical.com:443 ([dial tcp <IP_ADDRESS>:443: connect: connection refuse

No need for " images:" prefix

@simondeziel I appreciate the review! I've made updates and left a few comments.
In the pipeline this test seems to fail to connect to images.lxd.canonical.com. This does not happen for me locally. Any idea why this is failing here?
$ lxc launch images:ubuntu-minimal-daily:24.04 unprivileged
Launching unprivileged
Error: Failed instance creation: Failed getting remote image info: Failed getting image: Failed parsing stream: Get "https://images.lxd.canonical.com/streams/v1/index.json": Unable to connect to: images.lxd.canonical.com:443 ([dial tcp <IP_ADDRESS>:443: connect: connection refuse

No need for " images:" prefix

Oops. Thanks for catching that @tomponline.

Looks like the tests are failing for snapd test

@boltmark we are interested in latest/edge tests passing for this, as ive not backported your fix to 5.21/edge yet.
The error you're seeing is:

Error: Failed instance creation: Failed creating instance from image: Unpack failed: Failed to run: unsquashfs -f -d /var/snap/lxd/common/lxd/storage-pools/test-lvm/images/cf50a6b79620d2cfe6337c389a6a70f78dd1a6d092583786380a0bcd86cf51e2/rootfs -n /var/snap/lxd/common/lxd/images/cf50a6b79620d2cfe6337c389a6a70f78dd1a6d092583786380a0bcd86cf51e2.rootfs: exit status 1 (Write on output file failed because No space left on device
Retrieving image: Unpacking image: 100% (761.55MB/s)
FATAL ERROR: writer: failed to write file /var/snap/lxd/common/lxd/storage-pools/test-lvm/images/cf50a6b79620d2cfe6337c389a6a70f78dd1a6d092583786380a0bcd86cf51e2/rootfs/usr/bin/dpkg-divert)

https://github.com/canonical/lxd-ci/actions/runs/10205740488/job/28237210776?pr=248

@tomponline I've removed the ceph check, and the snapd test now only fails on 5.21 (expected as preseed fix not yet backported), and 4.0/edge (only on 22.04) due to Error: Required tool 'zpool' is missing when creating a zfs storage pool.
Is this related to https://discuss.linuxcontainers.org/t/ubuntu-22-04-lxd-5-0-2-required-tool-zpool-is-missing-after-apt-upgrade/18791/14? If it is, is there a similar fix for 4.0 or should we skip this check for 4.0 on 22.04 in the testing?

Let's get rid of the zfs check too for now, this is tested elsewhere

Sounds good. Should we just get rid of all storage tests (only btrfs and lvm remaining) in the snapd test? I see these are tested more thoroughly in storage-vm.

Yeah good idea


Added install from Windows support

Added permissions setting and line ending conversion from DOS to unix to ensure if the directory was cloned by a Windows machine, everything still works.

I changed installing dos2unix such that it works properly with Amazon Linux and Ubuntu

Oh, wow, OK, thanks for the explanation on both the line ending thing and the execute permissions with Windows. This seems like a general purpose problem that every Packer template would have when being run from Windows, right? If so, is there no solution built-in to Packer to handle this? It feels messy and non-DRY to call dos2unix and chmod +x on every single script...

Hmm, I agree that the edits proposed are pretty non-DRY, and should be refactored into a single location. I'm not sure if a Packer option exists, since I think what we want would be in the File provisioner, we'd want some options to convert from Windows files to Unix. According to their documentation it doesn't seem like such an option exists. The other issue, is that you don't want ALL files converted into executable, you pick and choose per upload, so there's not an easy way to "convert all" I think. Maybe a custom provisioner could make everything possible? Each script would still have to specify which files they wanted to be executable, but at least the line endings could be converted automatically, and the chmod ... repetitive stuff could be made much simpler.

We are looking into this. Perhaps using a file provisioner is a bad idea in general if Windows is in the mix. We may want to switch to a git clone approach...
That said, do you have core.autocrlf true in your Git config? If so, I believe the line ending issue can at least be fixed by switching to core.autocrlf input.

Hm, for the permissions issues, I found various StackOverflow threads (example) that mention:

git update-index --chmod=+x <file> for each file that needs execute permissions.
On Windows, set the Git config to use core.fileMode false so it doesn't try to change those permissions.

Perhaps worth a shot? I suspect that may only ensure you don't get spurrious diffs locally though; if Windows itself doesn't respect the file permissions on the file itself, then when we use the file provisioner, the file that gets uploaded still won't have those permissions.
So I suspect the real solution will be to switch from the file provisioner to git clone everywhere :-\

Hmm, the issue I see with the cloning idea is that people who use windows can't change any files and have the results sent to AWS. Realistically, isn't everything inside the "modules" directory executable? Would it be bad to just do a blanket file permissions change if it came from there?

Hmm, the issue I see with the cloning idea is that people who use windows can't change any files and have the results sent to AWS.

Why not? You would have to commit and push your changes to a Git repo, but that should work the same from Windows as anywhere else, right?

Realistically, isn't everything inside the "modules" directory executable?

No, just a handful of scripts.

Would it be bad to just do a blanket file permissions change if it came from there?

Principle of least privilege means that would not be a good idea. It also doesn't matter if Windows doesn't maintain permissions after clone...

Why not? You would have to commit and push your changes to a Git repo, but that should work the same from Windows as anywhere else, right?

So imagine you clone with Windows, edit a file, and push to git. As soon as you edited the file from Windows, the line endings changed, and pushing to Git doesn't change them back. Also, as soon as you clone to Windows permissions are lost, so if you push back to git, they're still gone.

Principle of least privilege means that would not be a good idea. It also doesn't matter if Windows doesn't maintain permissions after clone...

I do agree with this, was just throwing things out there.
One other option is to just not support Windows? As long as a warning is there in the documentation, there is now WSL which is pretty good, and if someone does their work from there everything should be fine.

So imagine you clone with Windows, edit a file, and push to git. As soon as you edited the file from Windows, the line endings changed, and pushing to Git doesn't change them back.

I believe configuring core.autocrlf in Git will prevent that issue. It looks like we may be able to enforce it repo-wide via
.gitattributes file: https://stackoverflow.com/a/40821931/483528

Also, as soon as you clone to Windows permissions are lost, so if you push back to git, they're still gone.

I think if we use git update-index to manage execute permissions, that will also be preserved regardless of OS: https://stackoverflow.com/a/13593391/483528.

Ok, I think I initially misunderstood. That sounds like it should work then!


Incorrect VISIB data element when compared to raw METAR in same object

See below RAW METAR and compare it to VISIB.
I noticed this when I checked the avaiation weather map android app and it was saying all clear w/ respect to VIS - But our internal server app was still saying VIS was poor. :(
I compared the raw metar for both apps - Mobile app works fine (not sure what backend modules they are using) to this aviation weather model - And obviously there were diffs.
I checked module source code and did not easily see where the raw METAR data was being parsed... Not sure why VISIB is off.
Any ideas?
Example of live data dump:
"airportCode": "KILN",
"airportName": "Wilmington Arpt, OH, US",
"icaoId": "KILN",
"visib": "2",
"wspd": "4",
"clouds": 2300,
"rawMetar": "KILN 030954Z AUTO 10004KT 4SM BR OVC023 07/07 A3013 RMK AO2 SLP214 T00720067",
"reportTime": "2024-03-03 10:00:00",
"receiptTime": "2024-03-03 09:58:13"
I also noticed it on this one:
    "airportCode": "KLUK",
    "airportName": "Cincinnati/Lunken Fld, OH, US",
    "icaoId": "KLUK",
    "visib": "2",
    "wspd": "0",
    "clouds": 0,
    "rawMetar": "KLUK 031042Z AUTO 00000KT M1/4SM R21L/1000V1200FT FG VV002 06/05 A3014 RMK AO2 T00560050",

    "reportTime": "2024-03-03 10:42:00",
    "receiptTime": "2024-03-03 10:46:05"

DISREGARD!
It was a VERY late night coming off of a head cold... I just noticed I had a hard coded value set from some previous testing.
Please excuse my lack of redbull!
FIX - Don't code while falling asleep.
CLOSED


[Breaking Change] Deprecate All from OAL source.

[ ] If this pull request closes/resolves/fixes an existing issue, replace the issue number. Closes #.
[x] Update the CHANGES log.

Deprecate All from OAL source, according to latest layer concept, All as source has lost its meaning. We never would find a way to have scope=all metrics, as each layer is different from others.
@kezhenxu94 Event source is belong to All(a.k.a. default) scope, because we don't set its ScopeDeclaration#catalog`. Which scope or catalog should it belong?

@kezhenxu94 Event source is belong to All(a.k.a. default) scope, because we don't set its ScopeDeclaration#catalog`. Which scope or catalog should it belong?

I think it should belong to service scope.

@kezhenxu94 Done.


[speech_recognition] Dockerfile.gpu fails to find CUDA_HOME build in warp-ctc step

I am trying to run  the speech recognition workload and have encountered the following error in the warp-ctc step of the docker build:

Traceback (most recent call last):
  File "setup.py", line 50, in <module>
    extra_compile_args=extra_compile_args
  File "/usr/local/lib/python2.7/dist-packages/torch/utils/cpp_extension.py", line 328, in CUDAExten                         sion
    library_dirs += library_paths(cuda=True)
  File "/usr/local/lib/python2.7/dist-packages/torch/utils/cpp_extension.py", line 393, in library_p                         aths
    paths.append(_join_cuda_home(lib_dir))
  File "/usr/local/lib/python2.7/dist-packages/torch/utils/cpp_extension.py", line 724, in _join_cud                         a_home
    raise EnvironmentError('CUDA_HOME environment variable is not set. '
EnvironmentError: CUDA_HOME environment variable is not set. Please set it to your CUDA install root                         .
The command '/bin/sh -c git clone https://github.com/SeanNaren/warp-ctc.git &&     cd warp-ctc &&                              mkdir -p build && cd build && cmake .. && make &&     cd ../pytorch_binding && /bin/bash -c "sed -                         i '92s/THFloatTensor_size(probs, 2)/THCudaTensor_size(state, probs, 2)/' ./src/binding.cpp"     && /                         bin/bash -c "sed -i $'s/void\* gpu_workspace = THCudaMalloc(state, gpu_size_bytes);/void\* gpu_works                         pace\;\\\n    THCudaMalloc(state, \&gpu_workspace, gpu_size_bytes);/' ./src/binding.cpp"     && pyth                         on setup.py install' returned a non-zero code: 1

I have changed the dockerfile to the following as per the solution given in a comment in issue #113 :
FROM nvidia/cuda:9.0-cudnn7-devel-ubuntu16.04

WORKDIR /tmp

# Generic python installations
# PyTorch Audio for DeepSpeech: https://github.com/SeanNaren/deepspeech.pytorch/releases
# Development environment installations
RUN apt-get update && apt-get install -y \
  python \
  python-pip \
  sox \
  libsox-dev \
  libsox-fmt-all \
  git \
  cmake \
  tree \
  htop \
  bmon \
  iotop \
  tmux \
  vim \
  apt-utils

# Make pip happy about itself.
RUN pip install --upgrade pip

# Unlike apt-get, upgrading pip does not change which package gets installed,
# (since it checks pypi everytime regardless) so it's okay to cache pip.
# Install pytorch
# http://pytorch.org/
RUN pip install                h5py
RUN pip install                pytest
RUN pip install                hickle
#Was split to see why hickle install failed, and installing pytest fixed it
RUN pip install                matplotlib
RUN pip install                tqdm
RUN pip install                http://download.pytorch.org/whl/cu90/torch-0.4.0-cp27-cp27mu-linux_x86_64.whl
RUN pip install                torchvision
RUN pip install                cffi
RUN pip install                python-Levenshtein
RUN pip install                librosa
RUN pip install                wget
RUN pip install                tensorboardX

RUN apt-get update && apt-get install --yes --no-install-recommends cmake \
                                                                    sudo

ENV CUDA_HOME "/usr/local/cuda"

# install warp-ctc
RUN git clone https://github.com/SeanNaren/warp-ctc.git && \
    cd warp-ctc && \
    mkdir -p build && cd build && cmake .. && make && \
    cd ../pytorch_binding && /bin/bash -c "sed -i '92s/THFloatTensor_size(probs, 2)/THCudaTensor_size(state, probs, 2)/' ./src/binding.cpp" \
    && /bin/bash -c "sed -i $'s/void\* gpu_workspace = THCudaMalloc(state, gpu_size_bytes);/void\* gpu_workspace\;\\\n    THCudaMalloc(state, \&gpu_workspace, gpu_size_bytes);/' ./src/binding.cpp" \
    && python setup.py install

# install pytorch audio
RUN apt-get install -y sox libsox-dev libsox-fmt-all
RUN git clone https://github.com/pytorch/audio.git
RUN cd audio; python setup.py install

# install ctcdecode
RUN git clone --recursive https://github.com/parlance/ctcdecode.git
RUN cd ctcdecode; pip install .

ENV SHELL /bin/bash

The environment variables on my machine:
user@ubuntu:~/SeniorDesignI21/automated_script/training/speech_recognition/pytorch/docker$ echo $CUDA_HOME
/usr/local/cuda-9.0
user@ubuntu:~/SeniorDesignI21/automated_script/training/speech_recognition/pytorch/docker$ echo $LD_LIBRARY_PATH
/usr/local/cuda-9.0/lib64:
user@ubuntu:~/SeniorDesignI21/automated_script/training/speech_recognition/pytorch/docker$ /usr/local/cuda-9.0
 -bash: /usr/local/cuda-9.0: Is a directory
user@ubuntu:~/SeniorDesignI21/automated_script/training/speech_recognition/pytorch/docker$ ls /usr/local/cuda-9.0
bin  extras   jre    libnsight  nsightee_plugins              nvml  samples  src    version.txt
doc  include  lib64  libnvvp    NVIDIA_SLA_cuDNN_Support.txt  nvvm  share    tools
user@ubuntu:~/SeniorDesignI21/automated_script/training/speech_recognition/pytorch/docker$ ls /usr/local/cuda
bin  extras   jre    libnsight  nsightee_plugins              nvml  samples  src    version.txt
doc  include  lib64  libnvvp    NVIDIA_SLA_cuDNN_Support.txt  nvvm  share    tools
user@ubuntu:~/SeniorDesignI21/automated_script/training/speech_recognition/pytorch/docker$

I am at a loss since the instruction for setting the environmental variable compiles, has anyone encountered this CUDA_HOME issue after fixing the dockerfile per issue #113 .

I was able to bypass the error and build the dockerfile by changing it to the following:
FROM nvidia/cuda:9.0-cudnn7-devel-ubuntu16.04

WORKDIR /tmp

# Generic python installations
# PyTorch Audio for DeepSpeech: https://github.com/SeanNaren/deepspeech.pytorch/releases
# Development environment installations
RUN apt-get update && apt-get install -y \
  python \
  python-pip \
  sox \
  libsox-dev \
  libsox-fmt-all \
  git \
  cmake \
  tree \
  htop \
  bmon \
  iotop \
  tmux \
  vim \
  apt-utils

# Make pip happy about itself.
RUN pip install --upgrade pip

# Unlike apt-get, upgrading pip does not change which package gets installed,
# (since it checks pypi everytime regardless) so it's okay to cache pip.
# Install pytorch
# http://pytorch.org/
RUN pip install                h5py
RUN pip install                pytest
RUN pip install                hickle
#Was split to see why hickle install failed, and installing pytest fixed it
RUN pip install                matplotlib
RUN pip install                tqdm
RUN pip install                http://download.pytorch.org/whl/cu90/torch-0.4.0-cp27-cp27mu-linux_x86_64.whl
RUN pip install                torchvision
RUN pip install                cffi
RUN pip install                python-Levenshtein
RUN pip install                librosa
RUN pip install                wget
RUN pip install                tensorboardX

RUN apt-get update && apt-get install --yes --no-install-recommends cmake \
                                                                    sudo

ENV CUDA_HOME "/usr/local/cuda"

# install warp-ctc
RUN git clone -n https://github.com/SeanNaren/warp-ctc.git
RUN cd warp-ctc && git checkout -b oldBranch 7fcbf65ea08c0f3df8c802ae65dc5f60c3d07d67 \
    && mkdir -p build && cd build && cmake .. && make && \
    cd ../pytorch_binding && /bin/bash -c "sed -i '92s/THFloatTensor_size(probs, 2)/THCudaTensor_size(state, probs, 2)/' ./src/binding.cpp" \
    && /bin/bash -c "sed -i $'s/void\* gpu_workspace = THCudaMalloc(state, gpu_size_bytes);/void\* gpu_workspace\;\\\n    THCudaMalloc(state, \&gpu_workspace, gpu_size_bytes);/' ./src/binding.cpp" \
    && python setup.py install

# install pytorch audio
RUN apt-get install -y sox libsox-dev libsox-fmt-all
RUN git clone https://github.com/pytorch/audio.git
RUN cd audio; git reset --hard 67564173db19035329f21caa7d2be986c4c23797; python setup.py install

# install ctcdecode
RUN git clone --recursive https://github.com/parlance/ctcdecode.git
RUN cd ctcdecode && git checkout -b oldBranch2<PHONE_NUMBER>ca493491bf1bdd3fed52700d88689f; \
	pip install .

ENV SHELL /bin/bash


Add test file for presubmit tests

[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: iamsubratp
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

OWNERS [iamsubratp]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment


Benchmarks

Sorry, didn't mean to open this PR upstream.

No problem, though I don't mind merging this in.  Actually, can you reach out to me on Telegram @saley?  I have a question.


About issues

https://camo.githubusercontent.com/f364ec6565b14e266e33005c9cb80e5c7f7b367d/687474703a2f2f692e696d6775722e636f6d2f396e756b7a74412e706e67
can you provide this layout code? thanks

It's just iTerm panes with the following commands:
$ voltron v d
$ voltron v r -i # the -i should be default now so it may be just `voltron v r`
$ lldb inferior
$ voltron v s

iTerm panes set up manually or saved to a window arrangement (I normally just set them up kinda like that when I need to use it).

@snare  I mean to layout these panes with tmuxinator

https://github.com/snare/voltron/wiki/Layout-automation


Update to Swift 5.2 release.

cc @dylansturg

Can I build a project right now without merging the branch?

Can I build a project right now without merging the branch?

If you check this PR out locally, yes, it should build successfully with Xcode 11.4.

I tried to build from https://github.com/allevato/swift-format.git and still getting
SwiftSyntax parser library isn't compatible


[FLINK-36705] Add initial ProcessTableFunction class and annotations

What is the purpose of the change
Adds the initial interfaces of ProcessTableFunction and StateHint mentioned in FLIP-440 to the code base. This is a requirement to continue with the TypeInferenceExtractor extractor work.
Brief change log

Introduce ProcessTableFunction and StateHint
Add FunctionHint.state()
Add TableSementics for powering the context of PTFs

Verifying this change
This change is a trivial rework / code cleanup without any test coverage.
Does this pull request potentially affect one of the following parts:

Dependencies (does it add or upgrade a dependency): no
The public API, i.e., is any changed class annotated with @Public(Evolving): yes
The serializers: no
The runtime per-record code paths (performance sensitive): no
Anything that affects deployment or recovery: JobManager (and its components), Checkpointing, Kubernetes/Yarn, ZooKeeper: no
The S3 file system connector: no

Documentation

Does this pull request introduce a new feature? yes
If yes, how is the feature documented? JavaDocs

ideally testing the behavior documented in the comments.

This is a feature under development. The behavior in comments is not fully implemented yet. As can be seen in the umbrella ticket FLINK-36703, this is just the very beginning of the implementation. The interfaces are necessary as a first step to power the next tasks which is TypeInferenceExtractor update.

@flinkbot run azure


master

add helper method to identify all declared methods on a class.
This will fix loading problems with Spring 4.2.1

Would this fix https://issues.jboss.org/browse/RESTEASY-1221??

Hi,
actually I do not know.
This is a fix for  in the SpringBeanProcessor to avoid the following exception:
Exception in thread "main" java.lang.IllegalStateException: RESTEASY013015: could not find the type for bean named org.springframework.transaction.config.internalTransactionalEventListenerFactory
	at org.jboss.resteasy.plugins.spring.SpringBeanProcessor.getBeanClass(SpringBeanProcessor.java:457)
	at org.jboss.resteasy.plugins.spring.SpringBeanProcessor.processBean(SpringBeanProcessor.java:282)
	at org.jboss.resteasy.plugins.spring.SpringBeanProcessor.postProcessBeanFactory(SpringBeanProcessor.java:260)
	at org.springframework.context.support.PostProcessorRegistrationDelegate.invokeBeanFactoryPostProcessors(PostProcessorRegistrationDelegate.java:284)
	at org.springframework.context.support.PostProcessorRegistrationDelegate.invokeBeanFactoryPostProcessors(PostProcessorRegistrationDelegate.java:174)
	at org.springframework.context.support.AbstractApplicationContext.invokeBeanFactoryPostProcessors(AbstractApplicationContext.java:673)
	at org.springframework.context.support.AbstractApplicationContext.refresh(AbstractApplicationContext.java:519)
	at org.springframework.boot.context.embedded.EmbeddedWebApplicationContext.refresh(EmbeddedWebApplicationContext.java:118)
	at org.springframework.boot.SpringApplication.refresh(SpringApplication.java:686)
	at org.springframework.boot.SpringApplication.run(SpringApplication.java:320)

After commiting the pull request I saw that there already was a fix (see https://github.com/resteasy/Resteasy/pull/659)

cwiejack: your fix for issue in SpringBeanProcessor is much appreciated! I introduced your snapshot into my project and problem was resolved.
To the resteasy team, when can I expect the changes be merged into resteasy:master? Hopefully it will be available with 3.0.14.Final?
Thanks,
Pete

guys, please merge this ASAP, our project suffers from this issue

Thanks for all hands :-) As PR695 is merged I'll close this one.


the form button when hovered resizes all input's

This bug just happens in the Desktop view. when the cursor is hover the form button it resizes all form inputs.

bug already fixed


#213 TMP dir is also created and logged at start.

 vs. asterisk :)
Made a small test script for paths:
(venv) PS C:\Users\dphdp> cat .\tmp2\path.py
import sys
import os

def print_call_info():
        # Location of the program being executed
    program_location = os.path.abspath(sys.argv[0])

    # Location from which the program was called
    call_location = os.getcwd()

    print(f"Call location: {call_location}")
    print(f"Program location: {program_location}")

print_call_info()

(venv) PS C:\Users\dphdp> .\tmp2\path.exe
Call location: C:\Users\dphdp
Program location: C:\Users\dphdp\tmp2\path.exe
(venv) PS C:\Users\dphdp>

Changed to:
ROOT_DIR = os.path.dirname(os.path.abspath(sys.argv[0]))


compose: Offer a "Quote and reply" option

Fixes: #1975

(Rebased, resolving some conflicts.)

Thanks for the review! Revision pushed.

Thanks for the review! Revision pushed.

Thanks for the revision! Looks good -- merging.


[FEATURE] Add dark mode.

Is this a unique feature?

[X] I have checked "open" AND "closed" issues and this is not a duplicate

Is your feature request related to a problem/unavailable functionality? Please describe.
no
Proposed Solution
no
Screenshots
No response
Do you want to work on this issue?
Yes
If "yes" to above, please explain how you would technically implement this (issue will not be assigned if this is skipped)
No response

@vishalverma9572 Please assign me this issue under hacktoberfest.

@taneeshaa15 , Since we are currently focusing on just one theme and not supporting a dark theme, you can shift your efforts toward resolving other issues or contributing in different areas. Thanks for your understanding and cooperation!


Stucked on Processing upscaled video

Hi, I'm stuck on "Processing upscaled video" for about an hour. It would be nice to see some progress on processing.
Or is this a bug?

AMD 7950x3D
Nvidia 4090

Hi my friend,
i think there is an error with ffmpeg. The default ffmpeg is the version 4.2 that is not compatible with cpus with >= 16 threads.
To solve this issue you can 2 things:

Select in "CPU number" widget any value lower than 16

OR

Download the new version of ffmpeg (https://www.gyan.dev/ffmpeg/builds/)
Rename "ffmpeg.exe" as "ffmpeg_7.exe"
Put this file in "Assets" directory

I have this same problem with version 3.7 and the following settings:

So not sure it's related to >=16 threads.

Hi my friend,
did you build QualityScaler from code? or did you download the version from itch or steam?
If you downloaded the version from code, you should also add the updated version of ffmpeg to the “Assets” folder:

download it from here https://www.gyan.dev/ffmpeg/builds/

Extract the ffmpeg.exe file from the folder and put it in the “Assets” folder

Because the default version of ffmpeg is very old and may have problems with many modern cpu's. And I can't put the updated version because it is too heavy for github :(

Hi my friend,
did you build QualityScaler from code? or did you download the version from itch or steam?
If you downloaded the version from code, you should also add the updated version of ffmpeg to the “Assets” folder:
1. download it from here https://www.gyan.dev/ffmpeg/builds/

2. Extract the ffmpeg.exe file from the folder and put it in the “Assets” folder

Because the default version of ffmpeg is very old and may have problems with many modern cpu's. And I can't put the updated version because it is too heavy for github :(

Hi,
I downloaded the zip file from the latest release (https://github.com/Djdefrag/QualityScaler/releases/tag/3.7) however I realised that this does not include ffmpeg.exe in the Assets folder.
It would be very helpful if this was mentioned somewhere in the instructions (https://github.com/Djdefrag/QualityScaler?tab=readme-ov-file#make-it-work-by-yourself-) as I had no idea this was missing until I checked after reading this issue.
However, even after putting the latest version of ffmpeg.exe in the directory it still got stuck on the Processing upscaled video step.

Hi my friend,
actually QualityScaler comes with ffmpeg 4.2 installed when you download all dependecies, you just updated the ffmpeg version.
it doesn't tell you anything in the terminal? no errors? if you open task manager do you see the ffmpeg.exe process working?

Hi,
The zip file under Releases does not come with ffmpeg installed. Here is the zip folder:

As you can see, ffmpeg.exe does not exist there.
However, I realised this and I have now put the latest version of ffmpeg in the Assets folder:

It still gets hung up on Processing upscaled video:

Yes, app requires reboot to resume the position of ffmpeg.


Retry a polling function if the previous execution has exceeded a time out.

Include an optional timeout when setting up a poll function that will retry the function if the previous call has not returned.

Fixed with 7733b6725aefc5c344b124bee1ca652e326acde0


[Bug]: Buttons wider on v8.4.1 - unnecessary scrolling, mobile phone only

Current Behavior
The vacuum card and media player card buttons have become very wide in 8.4.1, rather than being nice and compact like they were in 8.4.0.
Expected Behavior
I preferred the old size buttons and behaviour of 8.4.0
Steps To Reproduce

Open dashboard on Safari on iPhone.
Observe that the buttons have changed size and introduced scrolling.

Environment
- OS: iOS 15.4.1
- Browser: Safari
- Version:
- Hassio: 2022.5.2

Anything else?

Hi 🙂 I didn't see it when I tested on Safari desktop. I unpublished the 1.8.1 and will push 1.8.2 to fix this 🙂

Thanks for that, sorry I totally messed up the versioning in the bug report

With mush-control-button-ratio: 2  you can see the whole control button again (at least on light and media card).

I have this issue with the light cards as well. The buttons are wider than the card, causing a scroll bar to appear even though there is plenty of room.

Update is coming 😅 https://github.com/piitaya/lovelace-mushroom/commit/691ca86c909e95c0d6a623354bc4cb14b7257f2f

Fixed with https://github.com/piitaya/lovelace-mushroom/releases/tag/v1.8.3


Update?

Hello
Do you plan any version update? I cannot run some plugin because the grafana version is too old. I did not check if influxdb needs also update
thanks

would be great to get this updated...

Agreed. If folks have moved to another docker image, please share.

Happy to provide an update for this. Sorry a bit busy and haven't used this container myself since moving house.
This original container was made before the services here had their own standalone images. If you can't wait for me to upgrade this, you can move to the dedicated images from Grafana and Influx.
Here is an example of how to do this with Docker compose:
https://github.com/jkehres/docker-compose-influxdb-grafana/blob/master/docker-compose.yml

@philhawthorne
Hi Phil
I'm really happy that I found your project. I use it for a long time and updated the versions frequently myself. Because I like to have all in one container. But I'm not able to upgrade InfluxDB to version 2 because it looks like that there is no pid file in /var/run/influxdb anymore. Do you have an idea how to do it?
or will be the use of 3 container (influx, telegraf, grafana) the only way I can go if I want InfluxDB v2.4?
BR
Ronald


Netbox migration/exporting files

Hi,
I am trying to migrate netbox but I am failing at the restoring part.
I ran the command "sudo -u postgres psql netbox < netbox.sql" for restoring and I am getting the following error. I think it has to do with some permissions but not sure. I am not much familiar with postgres db, docker etc. but somehow I was able to get netbox running. Can anyone please help?
Thanks.
After I run the command I am getting the following error
sudo -u postgres psql netbox < db_dump_2018-12-03.sql
could not change directory to "/root/netbox-docker"
SET
SET
ERROR: unrecognized configuration parameter "idle_in_transaction_session_timeout"
SET
SET
SET
SET
ERROR: unrecognized configuration parameter "row_security"
S

Thank you for your interest in NetBox. GitHub issues are intended for reporting reproducible bugs and requesting features, and must be submitted using the template provided here. For general discussion, questions, or assistance with installation issues, please post to our mailing list.


Enable dm.use_deferred_deletion only if it is supported by the underlying kernel.

Signed-off-by: Shishir Mahajan<EMAIL_ADDRESS>

ping @rhvgoyal

Put your fifos on /run not on /tmp and make sure they are only writable by root.

@rhvgoyal PTAL.

@shishir-a412ed We aready have a test for /usr/bin/growpart in the dss script. I think lets do a similar test.
[  ! -x /usr/bin/dss-child-read-write.sh ]  && return 1

@shishir-a412ed Also bash read seems to support the timeout option. -t. Let us use a timeout of say 10 seconds. If we don't hear back from child in 10 seconds, return error (instead of blocking infinitely).

@rhvgoyal PTAL.

@rhvgoyal PTAL.

@shishir-a412ed can we also update docker-storage-setup.spec file to accomodate new binary dss-child-read-write.sh

@rhvgoyal PTAL.

LGTM. Thanks Shishir.

@rh-atomic-bot r+


fix(loader): syntax errors in dev mode

The dev server would silently hang when a syntax error was encountered in the @mdx-deck/loader module. You would only see the error after pressing ctrl+c to exit the process manually.
Before: https://streamable.com/7dpju
After: https://streamable.com/0jdz8

Thanks!


No such file or directory: 'thirdpart/face3d/BFM/similarity Lm3D_all.mat'

when --exp_img is put an image, the error occurs

It is the same problem for me too. Any solution for this issue

Just copy the BFM folder from the checkpoints folder and paste it to " third_part\face3d" path

when --exp_img is put an image, the error occurs


Tiles not triggering in 0.8.9

(Hey, Wait! version 0.6.1)
Following an upgrade to Foundry 0.8.9, the Hey, Wait! tiles no longer trigger.
I'm no JavaScript programmer, but attempted to dig around and was wondering it this was related to the following issue: https://gitlab.com/foundrynet/foundryvtt/-/issues/5651.
Looking at the TokenUpdateCoordinator.coordinateUpdate method, this.tokenInitPos.get(tokenDoc.id) is always returning null (or whatever - as I said, I'm no JS dev!), so the method calls _cleanQueuedTokenInitPos and then exits.
The only place I saw TokenUpdateCoordinator.tokenInitPos being set was in registerTokenInitPos, and the only reference I found to that was during the module setup:
Hooks.on('preUpdateToken', async document => {
  tokenUpdateCoordinator.registerTokenInitPos(document.toObject());
});

Given that the issue referenced above talks about pre-updates on tokens, I thought this might be a cause?
Additionally, from within Foundry's debugging tools I searched for 'preUpdateToken' and found _preUpdateTokenActor in the Foundry files, so maybe the name had been changed?

Hey! Thank you so much for the in-depth analysis here. I just got back from vacation so I can take a look today. I'll post an update later...

So I took a peek, and I'm unable to reproduce on v0.8.9 of FoundryVTT. Just want to check before digging further, are you sure that you don't have "Token Disposition Types Allowed" set to something restricting the token you're testing with, or "Restrict GM From Triggering Tiles" set to checked (and testing with a GM user?)

Just want to check before digging further, are you sure that you don't have "Token Disposition Types Allowed" set to something restricting the token you're testing with, or "Restrict GM From Triggering Tiles" set to checked (and testing with a GM user?)

No, I'm pretty-sure they're both set correctly. It's more than likely some bizarre interaction with other modules. Let me do some testing and get back to you.

OK, I've got what the problem is now. Nothing to do with other modules or tiles not triggering...
It turns out that I'd placed the Hey, Wait! tiles in the foreground tile layer, and not the background one.
However, I did this because the system wouldn't allow me to place them in the background layer... I'm playing D&D and have used kakaroto's R20Converter, which seems to place the background map graphic as a tile with a z-order of 0 (as opposed to have a background image for the scene), so maybe that explains why I can't place background tiles over the top?

OK, I've got what the problem is now. Nothing to do with other modules or tiles not triggering...
It turns out that I'd placed the Hey, Wait! tiles in the foreground tile layer, and not the background one.
However, I did this because the system wouldn't allow me to place them in the background layer... I'm playing D&D and have used kakaroto's R20Converter, which seems to place the background map graphic as a tile with a z-order of 0 (as opposed to have a background image for the scene), so maybe that explains why I can't place background tiles over the top?

OK - found a workaround to the R20Converter 'thing' of using tiles for the background map. It's trivially easy to just point the background image to that tile and then delete the tile. Hey, Wait! then works perfectly!!!