Master fails to come back online after termination

Tectonic Version
1.6.2-tectonic.1
Environment
AWS
Expected Behavior
Tectonic to come back online after the master was terminated
Actual Behavior
The ELB reports the new master to be OutOfService. The master seems to fail to come back online
Reproduction Steps

Launch tectonic cluster with 1 of each instance type
Wait until all is well
Terminate the master
Wait for new master to come up and check if it works

Other Information
Logging on to the master first showed that tectonic.service didn't start. I assumed this was a temporary issue, so I terminated the instance and let the ASG bring up a new one. The new instance didn't complain about the service, however it doesn't seem to function either:
ip-10-0-45-163 ~ # fleetctl status tectonic.service
Error retrieving unit: Get http://domain-sock/fleet/v1/units?alt=json: dial unix /var/run/fleet.sock: connect: no such file or directory

I'll assume that by "instance type" you mean master/worker instead of m3.medium.
Can you grab the logs from tectonic.service with journalctl -u tectonic.service from the machine?
A note: fleet doesn't have anything to do with Tectonic (and is marked for deprecation). I think the command you were looking for was systemctl status tectonic.service.

@mitom The controller node ASG can spin up new controllers if there is already a functioning kube-api-server. If you desire controller resilience from failure you'll need to deploy multiple controllers at cluster initialization.
If you are deployed with a single controller and this node becomes unavailable you'll need to create a temporary api-server and perform some additional recovery steps:
https://gist.github.com/soggiest/fead136ce1be6927c338d84e18105b3b
https://github.com/coreos/tectonic-installer/blob/fe9f6c70a4e2d26dacaa1a45e0975d135f9d2206/Documentation/troubleshooting/controller-recovery.md

@robszumski you are right, sorry for the ambiguity, I did master/worker/etcd by instance type.
Here is the log from journalctl -u tectonic.service:
-- Logs begin at Wed 2017-05-24 10:37:55 UTC, end at Wed 2017-05-24 12:08:54 UTC. --
May 24 10:41:17 ip-10-0-12-107 systemd[1]: Starting Bootstrap a Tectonic cluster...
May 24 10:41:21 ip-10-0-12-107 bash[2161]: [  206.296186] hyperkube[5]: Waiting for Kubernetes API...
May 24 10:41:21 ip-10-0-12-107 bash[2161]: [  206.464467] hyperkube[5]: Kubernetes master is running at https://tamas-test-api.tamas.colab.**********.com:443
May 24 10:41:21 ip-10-0-12-107 bash[2161]: [  206.502518] hyperkube[5]: Heapster is running at https://tamas-test-api.tamas.colab.**********.com:443/api/v1/proxy/namespaces/kube-system/services/heapster
May 24 10:41:21 ip-10-0-12-107 bash[2161]: [  206.502795] hyperkube[5]: KubeDNS is running at https://tamas-test-api.tamas.colab.**********.com:443/api/v1/proxy/namespaces/kube-system/services/kube-dns
May 24 10:41:21 ip-10-0-12-107 bash[2161]: [  206.503041] hyperkube[5]: To further debug and diagnose cluster problems, use 'kubectl cluster-info dump'.
May 24 10:41:21 ip-10-0-12-107 bash[2161]: [  206.504772] hyperkube[5]: Waiting for pods in namespace kube-system
May 24 10:41:21 ip-10-0-12-107 bash[2161]: [  206.698557] hyperkube[5]: Creating Tectonic Namespace
May 24 10:41:21 ip-10-0-12-107 bash[2161]: [  206.699427] hyperkube[5]: Executing kubectl create -f namespace.yaml
May 24 10:41:21 ip-10-0-12-107 bash[2161]: [  206.954931] hyperkube[5]: Error from server (AlreadyExists): error when creating "namespace.yaml": namespaces "tectonic-system" already exists, skipping
May 24 10:41:21 ip-10-0-12-107 bash[2161]: [  206.955578] hyperkube[5]: Creating Initial Roles
May 24 10:41:21 ip-10-0-12-107 bash[2161]: [  206.955847] hyperkube[5]: Executing kubectl delete -f rbac/role-admin.yaml
May 24 10:41:21 ip-10-0-12-107 bash[2161]: [  207.149044] hyperkube[5]: clusterrole "admin" deleted
May 24 10:41:21 ip-10-0-12-107 bash[2161]: [  207.149789] hyperkube[5]: Executing kubectl create -f rbac/role-admin.yaml
May 24 10:41:22 ip-10-0-12-107 bash[2161]: [  207.348462] hyperkube[5]: clusterrole "admin" created
May 24 10:41:22 ip-10-0-12-107 bash[2161]: [  207.349226] hyperkube[5]: Executing kubectl create -f rbac/role-user.yaml
May 24 10:41:22 ip-10-0-12-107 bash[2161]: [  207.533122] hyperkube[5]: Error from server (AlreadyExists): error when creating "rbac/role-user.yaml": clusterroles.rbac.authorization.k8s.io "user" already exists, skipping
May 24 10:41:22 ip-10-0-12-107 bash[2161]: [  207.533913] hyperkube[5]: Executing kubectl create -f rbac/binding-admin.yaml
May 24 10:41:22 ip-10-0-12-107 bash[2161]: [  207.707933] hyperkube[5]: Error from server (AlreadyExists): error when creating "rbac/binding-admin.yaml": clusterrolebindings.rbac.authorization.k8s.io "admin-user" already exists, skipping
May 24 10:41:22 ip-10-0-12-107 bash[2161]: [  207.708608] hyperkube[5]: Executing kubectl create -f rbac/binding-discovery.yaml
May 24 10:41:22 ip-10-0-12-107 bash[2161]: [  207.885674] hyperkube[5]: Error from server (AlreadyExists): error when creating "rbac/binding-discovery.yaml": clusterrolebindings.rbac.authorization.k8s.io "discovery" already exists, skipping
May 24 10:41:22 ip-10-0-12-107 bash[2161]: [  207.886875] hyperkube[5]: Creating Tectonic ConfigMaps
May 24 10:41:22 ip-10-0-12-107 bash[2161]: [  207.887513] hyperkube[5]: Executing kubectl create -f config.yaml
May 24 10:41:22 ip-10-0-12-107 bash[2161]: [  208.103461] hyperkube[5]: Error from server (AlreadyExists): error when creating "config.yaml": configmaps "tectonic-config" already exists, skipping
May 24 10:41:22 ip-10-0-12-107 bash[2161]: [  208.103981] hyperkube[5]: Creating Tectonic Secrets
May 24 10:41:22 ip-10-0-12-107 bash[2161]: [  208.104282] hyperkube[5]: Executing kubectl create -f secrets/pull.json
May 24 10:41:23 ip-10-0-12-107 bash[2161]: [  208.315351] hyperkube[5]: Error from server (AlreadyExists): error when creating "secrets/pull.json": secrets "coreos-pull-secret" already exists, skipping
May 24 10:41:23 ip-10-0-12-107 bash[2161]: [  208.315806] hyperkube[5]: Executing kubectl create -f secrets/license.json
May 24 10:41:23 ip-10-0-12-107 bash[2161]: [  208.532978] hyperkube[5]: Error from server (AlreadyExists): error when creating "secrets/license.json": secrets "tectonic-license-secret" already exists, skipping
May 24 10:41:23 ip-10-0-12-107 bash[2161]: [  208.533862] hyperkube[5]: Executing kubectl create -f secrets/ingress-tls.yaml
May 24 10:41:23 ip-10-0-12-107 bash[2161]: [  208.755816] hyperkube[5]: Error from server (AlreadyExists): error when creating "secrets/ingress-tls.yaml": secrets "tectonic-ingress-tls-secret" already exists, skipping
May 24 10:41:23 ip-10-0-12-107 bash[2161]: [  208.756399] hyperkube[5]: Executing kubectl create -f secrets/ca-cert.yaml
May 24 10:41:23 ip-10-0-12-107 bash[2161]: [  208.971247] hyperkube[5]: Error from server (AlreadyExists): error when creating "secrets/ca-cert.yaml": secrets "tectonic-ca-cert-secret" already exists, skipping
May 24 10:41:23 ip-10-0-12-107 bash[2161]: [  208.971846] hyperkube[5]: Executing kubectl create -f secrets/identity-grpc-client.yaml
May 24 10:41:23 ip-10-0-12-107 bash[2161]: [  209.185038] hyperkube[5]: Error from server (AlreadyExists): error when creating "secrets/identity-grpc-client.yaml": secrets "tectonic-identity-grpc-client-secret" already exists, skipping
May 24 10:41:23 ip-10-0-12-107 bash[2161]: [  209.185521] hyperkube[5]: Executing kubectl create -f secrets/identity-grpc-server.yaml
May 24 10:41:24 ip-10-0-12-107 bash[2161]: [  209.402391] hyperkube[5]: Error from server (AlreadyExists): error when creating "secrets/identity-grpc-server.yaml": secrets "tectonic-identity-grpc-server-secret" already exists, skipping
May 24 10:41:24 ip-10-0-12-107 bash[2161]: [  209.402920] hyperkube[5]: Creating Tectonic Identity
May 24 10:41:24 ip-10-0-12-107 bash[2161]: [  209.403251] hyperkube[5]: Executing kubectl create -f identity/configmap.yaml
May 24 10:41:24 ip-10-0-12-107 bash[2161]: [  209.626363] hyperkube[5]: Error from server (AlreadyExists): error when creating "identity/configmap.yaml": configmaps "tectonic-identity" already exists, skipping
May 24 10:41:24 ip-10-0-12-107 bash[2161]: [  209.626838] hyperkube[5]: Executing kubectl create -f identity/services.yaml
May 24 10:41:24 ip-10-0-12-107 bash[2161]: [  209.915754] hyperkube[5]: Error from server (AlreadyExists): error when creating "identity/services.yaml": services "tectonic-identity" already exists
May 24 10:41:24 ip-10-0-12-107 bash[2161]: [  209.916300] hyperkube[5]: Error from server (AlreadyExists): error when creating "identity/services.yaml": services "tectonic-identity-api" already exists, skipping
May 24 10:41:24 ip-10-0-12-107 bash[2161]: [  209.916682] hyperkube[5]: Executing kubectl create -f identity/deployment.yaml
May 24 10:41:24 ip-10-0-12-107 bash[2161]: [  210.159162] hyperkube[5]: Error from server (AlreadyExists): error when creating "identity/deployment.yaml": deployments.extensions "tectonic-identity" already exists, skipping
May 24 10:41:24 ip-10-0-12-107 bash[2161]: [  210.159653] hyperkube[5]: Creating Tectonic Console
May 24 10:41:24 ip-10-0-12-107 bash[2161]: [  210.159942] hyperkube[5]: Executing kubectl create -f console/service.yaml
May 24 10:41:25 ip-10-0-12-107 bash[2161]: [  210.375816] hyperkube[5]: Error from server (AlreadyExists): error when creating "console/service.yaml": services "tectonic-console" already exists, skipping
May 24 10:41:25 ip-10-0-12-107 bash[2161]: [  210.376199] hyperkube[5]: Executing kubectl create -f console/deployment.yaml
May 24 10:41:25 ip-10-0-12-107 bash[2161]: [  210.580928] hyperkube[5]: Error from server (AlreadyExists): error when creating "console/deployment.yaml": deployments.extensions "tectonic-console" already exists, skipping
May 24 10:41:25 ip-10-0-12-107 bash[2161]: [  210.581418] hyperkube[5]: Creating Tectonic Monitoring
May 24 10:41:25 ip-10-0-12-107 bash[2161]: [  210.581643] hyperkube[5]: Executing kubectl create -f monitoring/prometheus-operator-service-account.yaml
May 24 10:41:25 ip-10-0-12-107 bash[2161]: [  210.803719] hyperkube[5]: Error from server (AlreadyExists): error when creating "monitoring/prometheus-operator-service-account.yaml": serviceaccounts "prometheus-operator" already exists, skipping
May 24 10:41:25 ip-10-0-12-107 bash[2161]: [  210.804187] hyperkube[5]: Executing kubectl create -f monitoring/prometheus-operator-cluster-role.yaml
May 24 10:41:25 ip-10-0-12-107 bash[2161]: [  211.003916] hyperkube[5]: Error from server (AlreadyExists): error when creating "monitoring/prometheus-operator-cluster-role.yaml": clusterroles.rbac.authorization.k8s.io "prometheus-operator" already exists, skipping
May 24 10:41:25 ip-10-0-12-107 bash[2161]: [  211.004628] hyperkube[5]: Executing kubectl create -f monitoring/prometheus-operator-cluster-role-binding.yaml
May 24 10:41:25 ip-10-0-12-107 bash[2161]: [  211.194916] hyperkube[5]: Error from server (AlreadyExists): error when creating "monitoring/prometheus-operator-cluster-role-binding.yaml": clusterrolebindings.rbac.authorization.k8s.io "prometheus-operator" already exists, skipping
May 24 10:41:25 ip-10-0-12-107 bash[2161]: [  211.195639] hyperkube[5]: Executing kubectl create -f monitoring/prometheus-k8s-service-account.yaml
May 24 10:41:26 ip-10-0-12-107 bash[2161]: [  211.413309] hyperkube[5]: Error from server (AlreadyExists): error when creating "monitoring/prometheus-k8s-service-account.yaml": serviceaccounts "prometheus-k8s" already exists, skipping
May 24 10:41:26 ip-10-0-12-107 bash[2161]: [  211.413877] hyperkube[5]: Executing kubectl create -f monitoring/prometheus-k8s-cluster-role.yaml
May 24 10:41:26 ip-10-0-12-107 bash[2161]: [  211.589460] hyperkube[5]: Error from server (AlreadyExists): error when creating "monitoring/prometheus-k8s-cluster-role.yaml": clusterroles.rbac.authorization.k8s.io "prometheus-k8s" already exists, skipping
May 24 10:41:26 ip-10-0-12-107 bash[2161]: [  211.590291] hyperkube[5]: Executing kubectl create -f monitoring/prometheus-k8s-cluster-role-binding.yaml
May 24 10:41:26 ip-10-0-12-107 bash[2161]: [  211.769921] hyperkube[5]: Error from server (AlreadyExists): error when creating "monitoring/prometheus-k8s-cluster-role-binding.yaml": clusterrolebindings.rbac.authorization.k8s.io "prometheus-k8s" already exists, skipping
May 24 10:41:26 ip-10-0-12-107 bash[2161]: [  211.770587] hyperkube[5]: Executing kubectl create -f monitoring/prometheus-k8s-config.yaml
May 24 10:41:26 ip-10-0-12-107 bash[2161]: [  211.983652] hyperkube[5]: Error from server (AlreadyExists): error when creating "monitoring/prometheus-k8s-config.yaml": configmaps "prometheus-k8s" already exists, skipping
May 24 10:41:26 ip-10-0-12-107 bash[2161]: [  211.984043] hyperkube[5]: Executing kubectl create -f monitoring/prometheus-k8s-rules.yaml
May 24 10:41:26 ip-10-0-12-107 bash[2161]: [  212.201885] hyperkube[5]: Error from server (AlreadyExists): error when creating "monitoring/prometheus-k8s-rules.yaml": configmaps "prometheus-k8s-rules" already exists, skipping
May 24 10:41:26 ip-10-0-12-107 bash[2161]: [  212.202668] hyperkube[5]: Executing kubectl create -f monitoring/prometheus-svc.yaml
May 24 10:41:27 ip-10-0-12-107 bash[2161]: [  212.419737] hyperkube[5]: Error from server (AlreadyExists): error when creating "monitoring/prometheus-svc.yaml": services "prometheus" already exists, skipping
May 24 10:41:27 ip-10-0-12-107 bash[2161]: [  212.420247] hyperkube[5]: Executing kubectl create -f monitoring/node-exporter-svc.yaml
May 24 10:41:27 ip-10-0-12-107 bash[2161]: [  212.635337] hyperkube[5]: Error from server (AlreadyExists): error when creating "monitoring/node-exporter-svc.yaml": services "node-exporter" already exists, skipping
May 24 10:41:27 ip-10-0-12-107 bash[2161]: [  212.635755] hyperkube[5]: Executing kubectl create -f monitoring/node-exporter-ds.yaml
May 24 10:41:27 ip-10-0-12-107 bash[2161]: [  212.841360] hyperkube[5]: Error from server (AlreadyExists): error when creating "monitoring/node-exporter-ds.yaml": daemonsets.extensions "node-exporter" already exists, skipping
May 24 10:41:27 ip-10-0-12-107 bash[2161]: [  212.841804] hyperkube[5]: Executing kubectl create -f monitoring/prometheus-operator.yaml
May 24 10:41:27 ip-10-0-12-107 bash[2161]: [  213.055746] hyperkube[5]: Error from server (AlreadyExists): error when creating "monitoring/prometheus-operator.yaml": deployments.extensions "prometheus-operator" already exists, skipping
May 24 10:41:27 ip-10-0-12-107 bash[2161]: [  213.056293] hyperkube[5]: Waiting for TPR prometheus.monitoring.coreos.com
May 24 10:41:27 ip-10-0-12-107 bash[2161]: [  213.243507] hyperkube[5]: NAME                               DESCRIPTION                 VERSION(S)
May 24 10:41:27 ip-10-0-12-107 bash[2161]: [  213.243888] hyperkube[5]: prometheus.monitoring.coreos.com   Managed Prometheus server   v1alpha1
May 24 10:41:27 ip-10-0-12-107 bash[2161]: [  213.245861] hyperkube[5]: Waiting for TPR service-monitor.monitoring.coreos.com
May 24 10:41:28 ip-10-0-12-107 bash[2161]: [  213.428912] hyperkube[5]: NAME                                    DESCRIPTION                           VERSION(S)
May 24 10:41:28 ip-10-0-12-107 bash[2161]: [  213.429347] hyperkube[5]: service-monitor.monitoring.coreos.com   Prometheus monitoring for a service   v1alpha1
May 24 10:41:28 ip-10-0-12-107 bash[2161]: [  213.431444] hyperkube[5]: Executing kubectl create -f monitoring/prometheus-k8s.yaml
May 24 10:41:28 ip-10-0-12-107 bash[2161]: [  213.612431] hyperkube[5]: Error from server (AlreadyExists): error when creating "monitoring/prometheus-k8s.yaml": thirdpartyresourcedatas.extensions "k8s" already exists, skipping
May 24 10:41:28 ip-10-0-12-107 bash[2161]: [  213.613207] hyperkube[5]: Executing kubectl create -f monitoring/prometheus-k8s-service-monitor-k8s-apps-http.yaml
May 24 10:41:28 ip-10-0-12-107 bash[2161]: [  213.804165] hyperkube[5]: Error from server (AlreadyExists): error when creating "monitoring/prometheus-k8s-service-monitor-k8s-apps-http.yaml": thirdpartyresourcedatas.extensions "k8s-apps-http" already exists, skipping
May 24 10:41:28 ip-10-0-12-107 bash[2161]: [  213.804810] hyperkube[5]: Executing kubectl create -f monitoring/prometheus-k8s-service-monitor-kubelet.yaml
May 24 10:41:28 ip-10-0-12-107 bash[2161]: [  213.987708] hyperkube[5]: Error from server (AlreadyExists): error when creating "monitoring/prometheus-k8s-service-monitor-kubelet.yaml": thirdpartyresourcedatas.extensions "kubelet" already exists, skipping
May 24 10:41:28 ip-10-0-12-107 bash[2161]: [  213.988335] hyperkube[5]: Creating Ingress
May 24 10:41:28 ip-10-0-12-107 bash[2161]: [  213.988875] hyperkube[5]: Executing kubectl create -f ingress/default-backend/configmap.yaml
May 24 10:41:28 ip-10-0-12-107 bash[2161]: [  214.209113] hyperkube[5]: Error from server (AlreadyExists): error when creating "ingress/default-backend/configmap.yaml": configmaps "tectonic-custom-error" already exists, skipping
May 24 10:41:28 ip-10-0-12-107 bash[2161]: [  214.209620] hyperkube[5]: Executing kubectl create -f ingress/default-backend/service.yaml
May 24 10:41:29 ip-10-0-12-107 bash[2161]: [  214.445855] hyperkube[5]: Error from server (AlreadyExists): error when creating "ingress/default-backend/service.yaml": services "default-http-backend" already exists, skipping
May 24 10:41:29 ip-10-0-12-107 bash[2161]: [  214.446593] hyperkube[5]: Executing kubectl create -f ingress/default-backend/deployment.yaml
May 24 10:41:29 ip-10-0-12-107 bash[2161]: [  214.654675] hyperkube[5]: Error from server (AlreadyExists): error when creating "ingress/default-backend/deployment.yaml": deployments.extensions "default-http-backend" already exists, skipping
May 24 10:41:29 ip-10-0-12-107 bash[2161]: [  214.655297] hyperkube[5]: Executing kubectl create -f ingress/ingress.yaml
May 24 10:41:29 ip-10-0-12-107 bash[2161]: [  214.866099] hyperkube[5]: Error from server (AlreadyExists): error when creating "ingress/ingress.yaml": ingresses.extensions "tectonic-ingress" already exists, skipping
May 24 10:41:29 ip-10-0-12-107 bash[2161]: [  214.866834] hyperkube[5]: Executing kubectl create -f ingress/nodeport/service.yaml
May 24 10:41:29 ip-10-0-12-107 bash[2161]: [  215.094780] hyperkube[5]: The Service "tectonic-lb" is invalid: spec.ports[0].nodePort: Invalid value: 32000: provided port is already allocated
May 24 10:41:29 ip-10-0-12-107 bash[2161]: [  215.095373] hyperkube[5]: kubectl failed, retrying in 5 seconds
May 24 10:41:35 ip-10-0-12-107 bash[2161]: [  220.314627] hyperkube[5]: The Service "tectonic-lb" is invalid: spec.ports[0].nodePort: Invalid value: 32000: provided port is already allocated
May 24 10:41:35 ip-10-0-12-107 bash[2161]: [  220.315289] hyperkube[5]: kubectl failed, retrying in 5 seconds
May 24 10:41:40 ip-10-0-12-107 bash[2161]: [  225.538089] hyperkube[5]: The Service "tectonic-lb" is invalid: spec.ports[0].nodePort: Invalid value: 32000: provided port is already allocated
May 24 10:41:40 ip-10-0-12-107 bash[2161]: [  225.538418] hyperkube[5]: kubectl failed, retrying in 5 seconds
May 24 10:41:45 ip-10-0-12-107 bash[2161]: [  230.767954] hyperkube[5]: The Service "tectonic-lb" is invalid: spec.ports[0].nodePort: Invalid value: 32000: provided port is already allocated
May 24 10:41:45 ip-10-0-12-107 bash[2161]: [  230.768689] hyperkube[5]: kubectl failed, retrying in 5 seconds
May 24 10:41:58 ip-10-0-12-107 bash[2161]: [  243.632186] hyperkube[5]: error: error validating "ingress/nodeport/service.yaml": error validating data: Get https://tamas-test-api.tamas.colab.**********.com:443/swaggerapi/api/v1: EOF; if you choose to ignore these errors, turn validation off with --validate=false
May 24 10:41:58 ip-10-0-12-107 bash[2161]: [  243.632942] hyperkube[5]: kubectl failed, retrying in 5 seconds
May 24 10:42:03 ip-10-0-12-107 bash[2161]: [  248.775973] hyperkube[5]: error: error validating "ingress/nodeport/service.yaml": error validating data: Get https://tamas-test-api.tamas.colab.**********.com:443/swaggerapi/api/v1: EOF; if you choose to ignore these errors, turn validation off with --validate=false
May 24 10:42:03 ip-10-0-12-107 bash[2161]: [  248.776358] hyperkube[5]: kubectl failed, retrying in 5 seconds
May 24 10:42:08 ip-10-0-12-107 bash[2161]: [  253.924518] hyperkube[5]: error: error validating "ingress/nodeport/service.yaml": error validating data: Get https://tamas-test-api.tamas.colab.**********.com:443/swaggerapi/api/v1: EOF; if you choose to ignore these errors, turn validation off with --validate=false

******* truncated ***********

May 24 10:49:58 ip-10-0-12-107 bash[2161]: [  723.273198] hyperkube[5]: kubectl failed, retrying in 5 seconds
May 24 10:50:03 ip-10-0-12-107 bash[2161]: [  728.428745] hyperkube[5]: error: error validating "ingress/nodeport/service.yaml": error validating data: Get https://tamas-test-api.tamas.colab.**********.com:443/swaggerapi/api/v1: EOF; if you choose to ignore these errors, turn validation off with --validate=false
May 24 10:50:03 ip-10-0-12-107 bash[2161]: [  728.429124] hyperkube[5]: kubectl failed, retrying in 5 seconds
May 24 10:50:08 ip-10-0-12-107 bash[2161]: [  733.430113] hyperkube[5]: kubectl failed, giving up
May 24 10:50:08 ip-10-0-12-107 systemd[1]: tectonic.service: Main process exited, code=exited, status=1/FAILURE
May 24 10:50:08 ip-10-0-12-107 systemd[1]: Failed to start Bootstrap a Tectonic cluster.
May 24 10:50:08 ip-10-0-12-107 systemd[1]: tectonic.service: Unit entered failed state.
May 24 10:50:08 ip-10-0-12-107 systemd[1]: tectonic.service: Failed with result 'exit-code'.

The truncated part is the same lines repeating until it gave up, plus I have replaced the domain name with **********.
@kbrwn The first link states it only works if etcd was not deployed as part of the cluster - I went with the stable version which deploys a separate etcd server(s). To be honest, both processes look fairly complex considering that a plain k8s deployment by kops can recover from this kind of failure without any actions required.


ERROR os "ubuntu" version "24.04" not found

Bug Description
I couldn't deploy Canonical K8s charm on an series other than 24.04 - even when explicitly specifying the Ubuntu series.
If I run:
juju deploy k8s my-k8s-test-application --channel=latest/edge --revision=59 --series=jammy
Juju says:
WARNING series flag is deprecated, use --base instead ERROR os "ubuntu" version "24.04" not found
If I run:
juju deploy k8s my-k8s-test-application --channel=latest/edge --revision=59<EMAIL_ADDRESS>Juju says:
ERROR os "ubuntu" version "24.04" not found
The current workaround is: using revision 47 - later revisions fail.
To Reproduce

juju deploy k8s my-k8s-test-application --channel=latest/edge --revision=59<EMAIL_ADDRESS>Fails.

Environment
stg-is-new-canonical-k8s-testing@is-bastion-ps6
Channel: latest/edge
Failing revisions: 48 and above
Working revisions: 47 and below
Juju Controller/Model: 3.1.8
Juju client: 3.1.8-ubuntu-amd64
Relevant log output
`juju debug-log` is empty because nothing is even deployed.

Additional context
We have Ubuntu 24.04 available on the cloud.
For instance, juju add-machine<EMAIL_ADDRESS>works and creates a Noble VM.

https://discourse.charmhub.io/t/juju-support-for-the-latest-lts-release-noble-numbat-24-04/14051
i'm not sure how to deploy to noble.  I think this is a issue of juju
⚡ juju deploy k8s focal-k8s --channel=1.30/edge<EMAIL_ADDRESS>Deployed "focal-k8s" from charm-hub charm "k8s", revision 58 in channel 1.30/beta on<EMAIL_ADDRESS>
addyess@addyess-dell /home/addyess
⚡ juju deploy k8s jammy-k8s --channel=1.30/edge<EMAIL_ADDRESS>Deployed "jammy-k8s" from charm-hub charm "k8s", revision 58 in channel 1.30/beta on<EMAIL_ADDRESS>
addyess@addyess-dell /home/addyess
⚡ juju deploy k8s noble-k8s --channel=1.30/edge<EMAIL_ADDRESS>ERROR os "ubuntu" version "24.04" not found

Strangely running juju deploy k8s focal-k8s --channel=1.30/edge<EMAIL_ADDRESS>on my environment (juju v3.1.8) shows this error:
ERROR storing charm "k8s": retrieving essential metadata for charm "ch:amd64/focal/k8s-58": resolving origin for "ch:amd64/focal/k8s-58": os "ubuntu" version "24.04" not found (not found)
Even though I am explicitly asking for focal (20.04), it tries to deploy to 24.04 it looks like?

@hmlanigan Can you comment on whether or not juju is acting appropriately here
the k8s charm is
  - build-on:
    - name: ubuntu
      channel: "20.04"
      architectures: [amd64]
    run-on:
    - name: ubuntu
      channel: "20.04"
      architectures: [amd64]
    - name: ubuntu
      channel: "22.04"
      architectures: [amd64]
    - name: ubuntu
      channel: "24.04"
      architectures: [amd64]

@addyess ubuntu 24.04 is supported with juju 3.4 and higher.

Success with juju 3.5
⚡ juju status
Model  Controller       Cloud/Region    Version  SLA          Timestamp
k8s    addyess-vsphere  vsphere/Boston  3.5.0    unsupported  13:14:06-05:00

App        Version  Status  Scale  Charm  Channel      Rev  Exposed  Message
noble-k8s  1.30.0   active      1  k8s    latest/edge   59  no       Ready

Unit          Workload  Agent  Machine  Public address  Ports     Message
noble-k8s/2*  active    idle   2        <IP_ADDRESS>   6443/tcp  Ready

Machine  State    Address        Inst id        Base          AZ  Message
2        started  <IP_ADDRESS>  juju-358c1f-2<EMAIL_ADDRESS>    poweredOn

@mcarvalhor I don't get it.
addyess@addyess-dell /home/addyess
⚡ juju deploy k8s jammy-k8s  --constraints='cores=2 mem=16G root-disk=40G' --channel=edge<EMAIL_ADDRESS>Deployed "jammy-k8s" from charm-hub charm "k8s", revision 59 in channel latest/edge on<EMAIL_ADDRESS>

Does it work on 3.1.8 (the current prodstack version)?

yeah, confirmed it doesn't work right in juju 3.1.8.  @hmlanigan
ubuntu@juju-dae67f-0:~$ juju deploy k8s jammy-k8s  --constraints='cores=2 mem=16G root-disk=40G' --channel=edge --series=jammy --debug
13:42:49 INFO  juju.cmd supercommand.go:56 running juju [3.1.8 810900f47952a1f3835576f57dce2f9d1aef23d0 gc go1.21.9]
13:42:49 DEBUG juju.cmd supercommand.go:57   args: []string{"/snap/juju/26977/bin/juju", "deploy", "k8s", "jammy-k8s", "--constraints=cores=2 mem=16G root-disk=40G", "--channel=edge", "--series=jammy", "--debug"}
13:42:49 WARN  cmd deploy.go:765 series flag is deprecated, use --base instead
13:42:49 INFO  juju.juju api.go:86 connecting to API addresses: [<IP_ADDRESS>:17070]
13:42:49 DEBUG juju.api apiclient.go:1172 successfully dialed "wss://<IP_ADDRESS>:17070/model/8a27aee0-2145-4129-84a6-f515d5e320c9/api"
13:42:49 INFO  juju.api apiclient.go:707 connection established to "wss://<IP_ADDRESS>:17070/model/8a27aee0-2145-4129-84a6-f515d5e320c9/api"
13:42:49 INFO  juju.juju api.go:86 connecting to API addresses: [<IP_ADDRESS>:17070]
13:42:49 DEBUG juju.api apiclient.go:1172 successfully dialed "wss://<IP_ADDRESS>:17070/api"
13:42:49 INFO  juju.api apiclient.go:707 connection established to "wss://<IP_ADDRESS>:17070/api"
13:42:49 DEBUG juju.cmd.juju.application.deployer deployer.go:400 cannot interpret as local charm: file does not exist
13:42:49 DEBUG juju.cmd.juju.application.deployer deployer.go:207 cannot interpret as a redeployment of a local charm from the controller
13:42:50 DEBUG juju.cmd.juju.application.store charmadapter.go:95 cannot interpret as charmstore bundle: jammy (series) != "bundle"
13:42:50 INFO  cmd charm.go:377 Preparing to deploy "k8s" from the charmhub
13:42:50 INFO  juju.cmd.juju.application.deployer series_selector.go:163 with the user specified series "jammy"
13:42:51 DEBUG juju.api monitor.go:35 RPC connection died
13:42:51 DEBUG juju.api monitor.go:35 RPC connection died
ERROR storing charm "k8s": retrieving essential metadata for charm "ch:amd64/jammy/k8s-59": resolving origin for "ch:amd64/jammy/k8s-59": os "ubuntu" version "24.04" not found (not found)
13:42:51 DEBUG cmd supercommand.go:528 error stack:
retrieving essential metadata for charm "ch:amd64/jammy/k8s-59": resolving origin for "ch:amd64/jammy/k8s-59": os "ubuntu" version "24.04" not found (not found)
github.com/juju/juju/rpc.(*Conn).Call:178:
github.com/juju/juju/api/client/charms.(*Client).AddCharm:161:
github.com/juju/juju/cmd/juju/application/deployer.(*repositoryCharm).PrepareAndDeploy:505: storing charm "k8s"

@hmlanigan i have GREAT news that this works fine on juju 3.3 as well
juju deploy k8s jammy-k8s  --constraints='cores=2 mem=16G root-disk=40G' --channel=edge --series=jammy --debug
@mcarvalhor it's come to my understanding that juju 3.1 is no longer supported, this is a known bug in juju that seems to have been fixed going forward in supported juju.  You are recommended to model migrate to juju 3.3 in order to deploy canonical k8s.
This issue should now remain with k8s in that we should update the metadata of the charm to indicate a required juju 3.3 or beyond


Incorrect KamajiControlPlaneReady condition

Related to : #66
For the first time, I missed the important fact.

cluster controller also watches external object : https://github.com/kubernetes-sigs/cluster-api/blob/14efefeb46dbe8d0cd0f5b7d1718e00ec58fc079/internal/controllers/cluster/cluster_controller_phases.go#L96

I could check that cluster and kamaji control plane are inheriting the readiness from Kamaji.
But I think the kamajiControlPlane condition is not correct. It is always true during my test.
Steps to reproduce

deploy cluster by CAPI kamaji
delete deployment(control plane)

ubuntu@kamaji:~$ k delete deploy kamajicontrolplane-27
deployment.apps "kamajicontrolplane-27" deleted

check tenant control plane's status : Ready -> NotReady

kubectl get tcp -o=jsonpath={.items[0].status.kubernetesResources.version.status}

check kamaji control plane's status : true -> false

kubectl get kamajicontrolplane -o=jsonpath={.items[0].status.ready}

check kamaji control plane condition's KamajiControlPlaneReady : true -> true (not correct)

kubectl get kamajicontrolplane -o=jsonpath='{.items[0].status.conditions[4].type} {.items[0].status.conditions[4].status}'

check cluster's status : true -> false

kubectl get cluster -o=jsonpath={.items[0].status.controlPlaneReady}

about 50 seconds later

deployment(control plane) : Running
check tenant control plane's status : NotReady -> Ready

kubectl get tcp -o=jsonpath={.items[0].status.kubernetesResources.version.status}

check kamaji control plane's status : false -> true

kubectl get kamajicontrolplane -o=jsonpath={.items[0].status.ready}

check kamaji control plane condition's KamajiControlPlaneReady : true -> true (not correct)

kubectl get kamajicontrolplane -o=jsonpath='{.items[0].status.conditions[4].type} {.items[0].status.conditions[4].status}'

check cluster's status : false -> true

kubectl get cluster -o=jsonpath={.items[0].status.controlPlaneReady}

Additionally,
What still makes me confused is as below(@prometherion shared this).
# REDACTED
status:
  conditions:
  ...
  - lastTransitionTime: "2023-12-11T16:59:16Z"
    message: TenantControlPlane in Provisioning status, enqueue back
    observedGeneration: 1
    reason: Failed
    status: "False" #  KamajiControlPlaneIsReady condition is not ready
    type: KamajiControlPlaneIsReady
  externalManagedControlPlane: true
  initialized: true
  ready: true # KamajiControlPlane's status is ready
  readyReplicas: 2
  replicas: 2
  selector: cluster.x-k8s.io/cluster-name=capi-quickstart
  unavailableReplicas: 0
  updatedReplicas: 2
  version: v1.23.10

When KamajiControlPlane's status is ready, KamajiControlPlaneIsReady condition is not ready.
When can this situation happen?
Please, describe this situation :) @prometherion

I tried to replicate your issue @jds9090 but with no luck.
By deleting the Deployment, the KamajiControlPlane is marked as non ready:
$: kubectl delete deployment capi-quickstart-kubevirt
deployment.apps "capi-quickstart-kubevirt" deleted

$: kubectl get kamajicontrolplane capi-quickstart-kubevirt -o='jsonpath={.status.ready}'
false

Also the condition seems reporting the correct status along with the error.
  - lastTransitionTime: "2023-12-28T16:13:30Z"
    message: TenantControlPlane in NotReady status, enqueue back
    observedGeneration: 1
    reason: Failed
    status: "False"
    type: KamajiControlPlaneIsReady

Once the Deployment is created back, everything's ok.
$: kubectl get capi-quickstart-kubevirt
NAME                       READY   UP-TO-DATE   AVAILABLE   AGE
capi-quickstart-kubevirt   2/2     2            2           113s

$: kubectl get kamajicontrolplane capi-quickstart-kubevirt -o='jsonpath={.status.ready}'
true

  - lastTransitionTime: "2023-12-28T16:14:56Z"
    message: ""
    observedGeneration: 1
    reason: Succeeded
    status: "True"
    type: KamajiControlPlaneIsReady

I tried to replicate your issue @jds9090 but with no luck.
By deleting the Deployment, the KamajiControlPlane is marked as non ready:
$: kubectl delete deployment capi-quickstart-kubevirt
deployment.apps "capi-quickstart-kubevirt" deleted

$: kubectl get kamajicontrolplane capi-quickstart-kubevirt -o='jsonpath={.status.ready}'
false

Also the condition seems reporting the correct status along with the error.
  - lastTransitionTime: "2023-12-28T16:13:30Z"
    message: TenantControlPlane in NotReady status, enqueue back
    observedGeneration: 1
    reason: Failed
    status: "False"
    type: KamajiControlPlaneIsReady

Once the Deployment is created back, everything's ok.
$: kubectl get capi-quickstart-kubevirt
NAME                       READY   UP-TO-DATE   AVAILABLE   AGE
capi-quickstart-kubevirt   2/2     2            2           113s

$: kubectl get kamajicontrolplane capi-quickstart-kubevirt -o='jsonpath={.status.ready}'
true

  - lastTransitionTime: "2023-12-28T16:14:56Z"
    message: ""
    observedGeneration: 1
    reason: Succeeded
    status: "True"
    type: KamajiControlPlaneIsReady

Which version of KamajiControlPlane were you using?

I was running from master branch. Now that you let me think about it, I think aed438a is doing the trick.
If you agree, I would cut out a new version with the improvements and hotfixes collected, if the problem persists we could open the issue back.
Deal?

Which version of KamajiControlPlane were you using?

I was running from master branch. Now that you let me think about it, I think aed438a is doing the trick. If you agree, I would cut out a new version with the improvements and hotfixes collected, if the problem persists we could open the issue back.
Deal?

I think that would be a good idea.

v0.4.2 has been released, please, give it a try and feel free to open this issue back if the problem persists.


Replace index in Room DB with arklib

It is necessary to rework PlainResourcesIndex.kt in such a way that arklib would be used inside. Performance and functionality must not suffer from this refactoring. This change would allow us to build another apps with exactly the same indexing functionality as in Navigator and also to improve it for all apps at the same time.
Room DB must be used only for keeping list of folders after solving this task. Index will be kept in memory of arklib process. We should guarantee that arklib is not killed as long as app instance lives. Even better if we can keep it live longer than the app, so if we restarted the app we would not recalculate the index. If this is not possible, we will need to create persistence of index (cache), see https://github.com/ARK-Builders/ARK-Navigator/issues/142 and https://github.com/ARK-Builders/arklib/issues/15 for more details.

#325


Google.Apis 1.9.3 nuget package not visible from VS2015 package manager

And there is an assembly mismatch when we try to use another 1.9.3 package (Auth or other).
As an example Google.Apis.Auth.PlatformServices 1.9.3 requires Google.Apis.PlatformServices 1.9.3 but we have only  Google.Apis.PlatformServices 1.9.2 in package Google.Apis 1.9.3.
Any way to get this 1.9.3 ?

Ok I just seen it is a duplicate of issue #582 but with a better title

I'm seeing the same issue with Google.Apis.BigQuery.
To reproduce:
Download this repo:
https://github.com/GoogleCloudPlatform/csharp-docs-samples
Then open the solution with Visual Studio 2015:
bigquery/GettingStarted/BigQuery.sln.
Then, try to build and resolve the dependency errors.  It doesn't work.
If  I open the same solution with Visual Studio 2012, there is no problem.

Trying to Install Google.Apis always picks up 1.9.2:
PM> Install-Package Google.Apis
Attempting to gather dependencies information for package 'Google.Apis.1.9.2' with respect to project 'CleanBigQuery2', targeting '.NETFramework,Version=v4.5.2'

I was able to reproduce this issue with Visual Studio 2015.
The problem seems to be that the Google.Apis nuget package is for some reason not visible through the nuget v3 api.
A workaround in my case was to add the nuget v2 API as one of the package sources
Tools->Package Manager Settings-> PackageSources -> Add
Name: nuget.org v2
Source: https://www.nuget.org/api/v2
Related:
http://blog.nuget.org/20150226/nuget-3.0-beta2.html

Thanks for the work-around.  That unblocked me.
Are you continuing to investigate why Google.Apis is not visible to v3?

Note, this issue does not resolve by upgrading to Nuget 3.2.0.

FYI confirmed that the NuGet v3 API does not list 1.9.3:
https://api-v3search-0.nuget.org/query?q=Id:Google.Apis
But the v2 API does:
https://www.nuget.org/api/v2/Packages?$filter=Id eq 'Google.Apis'

Also note that other 1.9.3 Google.Apis.* packages released on 8/12 do show up in the new API, eg. Google.Apis.Core and Google.Apis.Auth.

This has been resolved:
https://github.com/NuGet/Home/issues/1544

Thanks @SurferJeffAtGoogle for looking into this. It looks like the issue has been resolved, so closing now. Feel free to reopen if needed.


NoSuchElementException - nable to locate element: {"method":"css selector","selector":"p"}

I have this error and don't know how to fix it.
python main.py --headless --url "https://www.glassdoor.com/Overview/Working-at-Wells-Fargo-EI_IE8876.11,22.htm" --limit 5 -f wells_fargo_reviews.csv
2019-11-21 16:21:07,264 INFO 377    :main.py(19772) - Configuring browser
DevTools listening on ws://<IP_ADDRESS>:54285/devtools/browser/45fc8723-9a20-498a-864e-5b4544f795ab
2019-11-21 16:21:09,710 INFO 419    :main.py(19772) - Scraping up to 5 reviews.
2019-11-21 16:21:09,718 INFO 358    :main.py(19772) - Signing in to<EMAIL_ADDRESS>2019-11-21 16:21:15,642 INFO 339    :main.py(19772) - Navigating to company reviews
2019-11-21 16:21:37,112 INFO 286    :main.py(19772) - Extracting reviews from page 1
2019-11-21 16:21:37,150 INFO 291    :main.py(19772) - Found 10 reviews on page 1
Traceback (most recent call last):
File "main.py", line 461, in
main()
File "main.py", line 441, in main
reviews_df = extract_from_page()
File "main.py", line 295, in extract_from_page
data = extract_review(review)
File "main.py", line 281, in extract_review
res[field] = scrape(field, review, author)
File "main.py", line 264, in scrape
return fdictfield
File "main.py", line 156, in scrape_years
'reviewBodyCell').find_element_by_tag_name('p')
File "C:\Users\E20008699\AppData\Local\Continuum\anaconda3\lib\site-packages\selenium\webdriver\remote\webelement.py", line 305, in find_element_by_tag_name
return self.find_element(by=By.TAG_NAME, value=name)
File "C:\Users\E20008699\AppData\Local\Continuum\anaconda3\lib\site-packages\selenium\webdriver\remote\webelement.py", line 659, in find_element
{"using": by, "value": value})['value']
File "C:\Users\E20008699\AppData\Local\Continuum\anaconda3\lib\site-packages\selenium\webdriver\remote\webelement.py", line 633, in _execute
return self._parent.execute(command, params)
File "C:\Users\E20008699\AppData\Local\Continuum\anaconda3\lib\site-packages\selenium\webdriver\remote\webdriver.py", line 321, in execute
self.error_handler.check_response(response)
File "C:\Users\E20008699\AppData\Local\Continuum\anaconda3\lib\site-packages\selenium\webdriver\remote\errorhandler.py", line 242, in check_response
raise exception_class(message, screen, stacktrace)
selenium.common.exceptions.NoSuchElementException: Message: no such element: Unable to locate element: {"method":"css selector","selector":"p"}
(Session info: headless chrome=78.0.3904.97)

I was able to found similar solution in previous issue.


Suggestion: make this project more visible

As a user,
I want this project to be visible and easily comparable to other similar projects,
in order to find this project again next time, and to make it easier to get inflow of new ideas and users
Context
I've been wanting something like homu for a while, which became bors-ng, but the whole solution seemed a bit too involved to be applicable to my current client. If, at that time, I would have imagined there are a lot of options, I would have ended up on the repo-automation-tools above and the toolkit for making your own. And we actually did make our own, but it's a deployed and heavy-handed kind of bot, which keeps being slow and throwing errors and making us retry. Doing deploys as a comment inside the relevant PR seems it would be a huge improvement. And now I'm trying to figure out if Derek is, or can soon enough be, a solution for our various needs.

Hi @sesam thank you for your feedback. I'll close the issue since we use the tracker for bugs and features.
It's nice of you to want the project to be more visible. Feel free to make suggestions on how you see that happening. I'm listening.
Blog posts and tweets from users can be helpful.
Regarding your other request for deployments, that sounds like a separate request and feature.
Why don't you join the Slack community to have a conversation about your ideas with the other users?
Alex

From your recent activity on the repo and the various issues that you've raised, it seems like you may be evaluating Derek for use at work or for participation in a feature.
If that's the case then I think more synchronous conversation on Slack with the other users would be the most efficient way to achieve that.

slack.openfaas.io


Feat/metric collection and submission to proxy

Before submitting this PR, please make sure:

[x] Your code builds clean without any errors or warnings
[x] You are using approved title ("feat/", "fix/", "docs/", "refactor/")

A description of the changes proposed in the pull request:
Tests performed by the developer:
Tips for QA testing:

Notion page for ongoing discussion with Michael Chuang - https://www.notion.so/hummingbot/Requirements-for-Gateway-Datadog-usage-404c7391c9a446539688ff5a645c97f5

Closing in favor of https://github.com/CoinAlpha/hummingbot/pull/10


Remember previous query variable selection

Fixes #167

Two issues remain

Previous selection of variables will always be restored if a previous selection was stored to the browser storage, not only when pressing the "CHANGE VARIABLES" button as requested

Currently, variable selection is stored correctly to browser storage upon change and is loaded correctly from the browser storage upon first render, but is not set as current value upon first render. This might be because react does not recognize the option passed to the value property of the AutocompleteSelection or some timing issue upon first render.


⚠ Bofrost.at has degraded performance

In 4ec4567, Bofrost.at (https://www.bofrost.at) experienced degraded performance:

HTTP code: 200
Response time: 1490 ms

Resolved: Bofrost.at performance has improved in 194a71c.


bug: $ionicHistory.clearCache(); with collection-repeat

Type: bug
Platform: all
When using $ionicHistory.clearCache(); with collection-repeat
when clicking on an item and going to detail view then hitting the back button i get a black screen im using $ionicHistory.clearCache();
like this
  $scope.$on('$ionicView.afterLeave', function(){
    $ionicHistory.clearCache();
  });
  $scope.$on('$ionicView.beforeEnter', function(){
    $ionicHistory.clearCache();
  });
  $scope.$on('$ionicView.beforeLeave', function(){
    $ionicHistory.clearCache();
  });
  $scope.$on('$ionicView.afterEnter', function(){
    $ionicHistory.clearCache();
  });

in my mainCtrl
if i need to provide a codepen i can do that

Greetings @cyprusglobe!
My sensors indicate that I require more information in order to assist you.

Can you provide a detailed description of this issue?
How would a robot go about replicating this issue?
On which platform does this happen occur? (iOS, Android, all, etc.)
On which platform versions does this occur? (Android 4.2, iOS 8, all, etc.)
Is this an issue with the Ionic Framework or Ionic CLI?

Additionally, providing a codepen that replicates the issue is extremely helpful.
If you wish to get help using the framework itself, I recommended visiting the forum, where many humans will be able to offer wisdom and advice.
Thank you for allowing me to assist you.

I wouldn't recommend clearing the before you enter, but rather after you leave.

@adamdbradley Thanks, for the suggestion :)


[New Project] Can you make it so that if any response comes in the web platform then there should be an alert or a notification?

Is this project already existing in the app?

[X] I have searched the existing projects

Tell us about the project
Can you make it so that if any response comes in the web platform then there should be an alert or a notification?
Is the Project a DPG (Digital Public Good)

[X] This Project is a DPG

Does the project list which Sustainable Development Goals it addresses in its labels?

[X] Yes
[ ] No

Code of Conduct

[X] I've read the Code of Conduct and understand my responsibilities as a member of the Ruby for Good community

Anything else?
No, nothing else.

This was already implemented.


[IMP] #9242 Survive broken 'git am' patches

We recently started using a new way of applying MR's to branches. Instead of letting gitaggregator merge, we apply a shell_command_after that applies the MR as a 'git am' patch, which preserves pinning. However when 'git am' fails, the directory is left in a broken state and this should be fixed upon rebuild.

@Hussam-Suleiman Please review


Swap Numbers in C

Hey! @Biplab-313
I would like to add a program to swap the numbers in C language
Kindly assign me this issue

@Ishika0-0 done


Use Java ver 8 as source and target version

Signed-off-by: Ali Ahmed<EMAIL_ADDRESS>

The website docs[1] state:

Java 8 is required by Bazel but Heron does not use Java 8 features; Heron topologies can be written in Java 7 or above and all Heron jars are compatible with Java 7.

Would you please update that to say that Heron requires java 8.
1 - https://twitter.github.io/heron/docs/developers/compiling/compiling/

@billonahill update the docs in the repo

@billonahill updated with you doc comment , awaiting for approval

@aahmed-se have you signed the CLA?

@billonahill not sure , I think I agreed to something when I joined the project.

@billonahill I have signed it now

👍  once CI passes

@billonahill Hey bill can you merge the commit , I don't have merge rights.


Switch logging from glog to logrus

Improve interactive output experience by switching to a logging
library (logrus) that allows customising the output format.
This also removes the glog command line flags.  Replaced with a
simpler --verbose/-v option:

quiet by default (warnings and errors only)
-v for progress info
-vv for debug

Fixes #34

Example output:

Errors look similar, but have a red "FATA" prefix:

The above is probably not what I would have chosen in a perfect world, but not too bad.  The output is written to stderr, which again is probably ok.
Without a tty, the output is not ok (imo):
 % ./kubecfg update -v examples/guestbook.jsonnet 2>&1 | cat
level=fatal msg="Error reading examples/guestbook.jsonnet: RUNTIME ERROR: Couldn't open import "example.libsonnet": No match locally or in the Jsonnet library paths.
        examples/guestbook.jsonnet:16:17-42     thunk <example>
        examples/guestbook.jsonnet:19:24-30     object <anonymous>
        During manifestation
"

So .. assuming I can fix the non-tty case to look basically like the tty version without colours - are we ok with this?
I had dreams of adding a basic progress bar to update (particularly once slow garbage collection is added) so this may change again in the future.  I tried just now, and it seems the 3 "popular" golang progress bar libraries don't properly support mixing line-based output and the progress bar (only one claims to support it, and it fails a quick test).

I don't think you need a progress bar, or if you do it is super low priority.
I am not shocked by the format of the FATAL errors, not sure how you can improve this.
But I would have kept the timestamp in verbose mode.

ok, I'm happy with this version.  Output is similar to screenshots above, but the non-tty version just omits the initial coloured word entirely (a predictable change).  @sebgoa?

ok, that's fine with me


Reconsider precommit.py file format

Instead of defining an init function, maybe it should just define a CHECKS list.

Maybe I should make it runnable, e.g. make precommit equivalent to python precommit.py

If it's not runnable, I don't know if there's much point in having it be a Python file instead of, say, JSON.

Actually I probably do want to keep it as a Python file so that people can write their own, inline checks.

I don't think there's a problem with the current format. It's simple enough, you can disable things by commenting them out, and it allows you to write your own checks if need be in the file.


Help Center: Add 'Embed Web Story' quick tip

Context
Image is being added in #7202.
Designs:

Summary
Adds the new quick tip for 'embedding a web story'.
Relevant Technical Choices
Currently we don't have an animation for this quick tip. Added some temporary props to handle the image rather than a video.
To-do

[ ] Add link once we figure out what the link is

User-facing changes

LTR
RTL

Testing Instructions

make sure FTUE experiment is turned on
go to editor
open help center
click Embed Web Stories

QA

[ ] This is a non-user-facing change and requires no QA

This PR can be tested by following these steps:

make sure FTUE experiment is turned on
go to editor
open help center
click Embed Web Stories

UAT

[x] UAT should use the same steps as above.

Reviews
Does this PR have a security-related impact?
no
Does this PR change what data or activity we track or use?
no
Does this PR have a legal-related impact?
no
Checklist

[x] This PR addresses an existing issue and I have linked this PR to it in ZenHub
[x] I have tested this code to the best of my abilities
[x] I have verified accessibility to the best of my abilities (docs)
[x] I have verified i18n and l10n (translation, right-to-left layout) to the best of my abilities
[ ] This PR contains automated tests (unit, integration, and/or e2e) to verify the code works as intended (docs)
[x] I have added documentation where necessary
[x] I have added a matching Type: XYZ label to the PR

Fixes #5493

looks like the link is: https://wordpress.org/support/article/embeds/
__(
  'https://wordpress.org/support/article/embeds/ ',
  'web-stories'
);

✨ ✨ ✨

Per slack conversation, the link to use is actually: https://wp.stories.google/docs/

Verified in QA


Simplify Product block encoding decomposition

This change refactors the Product block encoding, following suggestion in discussion, to perform fewer partitions of the ancilla and resource registers up front and to rely on AutoPartition to simplify the circuit diagram of each constituent block.

I'm staring at the product_block_encoding_properties.decompose_bloq() diagram and I think this mostly makes sense. Why are the "ancilla" and "resource" registers still being split with different ones being fed into B[U_a] vs B[U_b]?

With ancilla, we are doing just one split at the beginning into the flag_bits and the inner ancilla that is then fed to each of the constituents. The constituents use AutoPartition to ignore the unused bits. I have updated a comment to make it clearer that there are not separate individual ancilla registers.
With resource, there is a question of whether these bits are being returned to zero. If so, the constituents can share the resource bits in the same way as ancilla but without need for the flag bits. I have gone ahead with this assumption for now and changed the code to not split the resource register and rely only on AutoPartition. This cleans up the diagram.
It is possible that some block encodings will leave their resource state dirty and thus require flag bits here. I think properly supporting this behavior without using excessive bits could be done via a flag attribute in the BlockEncoding interface, analogous to the check of whether the signal_state is identity.
I can open an issue tracking the general fix above and add a code comment referencing it. Does that sound like a reasonable plan?

Thanks for the careful thought! Issue sounds like a good thought


generation of text

Hi,
After training my gpt-2 in Portuguese after your README.md, I tried to generate text. I used the following code in my terminal but I got an error. message Could you give me the correct code?
Thank you.
export OUTPUT=output_yt/s
python run_generation.py \
    --model_type=gpt2 \
    --model_name_or_path=$OUTPUT \
    --padding_text="Eu gosto do carro que comprei ontem"

The error message I got:
01/06/2020 15:25:37 - INFO - transformers.tokenization_utils -   Model name 'output_yt/s' not found in model shortcut name list (gpt2, gpt2-medium, gpt2-large, gpt2-xl, distilgpt2). Assuming 'output_yt/s' is a path or url to a directory containing tokenizer files.
01/06/2020 15:25:37 - INFO - transformers.tokenization_utils -   Didn't find file output_yt/s/vocab.json. We won't load it.
01/06/2020 15:25:37 - INFO - transformers.tokenization_utils -   Didn't find file output_yt/s/merges.txt. We won't load it.
01/06/2020 15:25:37 - INFO - transformers.tokenization_utils -   Didn't find file output_yt/s/added_tokens.json. We won't load it.
01/06/2020 15:25:37 - INFO - transformers.tokenization_utils -   Didn't find file output_yt/s/special_tokens_map.json. We won't load it.
01/06/2020 15:25:37 - INFO - transformers.tokenization_utils -   Didn't find file output_yt/s/tokenizer_config.json. We won't load it.
Traceback (most recent call last):
  File "run_generation.py", line 204, in <module>
    main()
  File "run_generation.py", line 166, in main
    tokenizer = tokenizer_class.from_pretrained(args.model_name_or_path)
  File "/opt/anaconda3/envs/gpt/lib/python3.7/site-packages/transformers/tokenization_utils.py", line 302, in from_pretrained
    return cls._from_pretrained(*inputs, **kwargs)
  File "/opt/anaconda3/envs/gpt/lib/python3.7/site-packages/transformers/tokenization_utils.py", line 370, in _from_pretrained
    list(cls.vocab_files_names.values())))
OSError: Model name 'output_yt/s' was not found in tokenizers model name list (gpt2, gpt2-medium, gpt2-large, gpt2-xl, distilgpt2). We assumed 'output_yt/s' was a path or url to a directory containing vocabulary files named ['vocab.json', 'merges.txt'] but couldn't find such vocabulary files at this path or url.

To understand how to generate text you should start by looking at rest.py.

Thanks Mikhail. It helped :-)


About precompile FLOWExaFMM before using FLOWVPM

When I try to precompile FLOWExaFMM, something wrong like this:
[ Info: Precompiling FLOWExaFMM [a07d1f4e-0e34-4d8b-bfef-e5b961477d34]
ERROR: LoadError: could not load library "C:\Users\G.julia\packages\FLOWExaFMM\SwcNX\src\fmm"
The specified module could not be found.
What should I do next?
Thank you so much!

Hi! Please follow the installation instructions of FLOWUnsteady to get FLOWVPM working.


query about file differences

It seems that we are not currently providing gff files for
i) the mating type region contig
ii) the subtelomeric contig
We should export these too .

https://pomrt.gen.private.cam.ac.uk/rt/Ticket/Display.html?id=6421

The GFF files are now generated nightly:
ftp://ftp.pombase.org/nightly_update/gff/
I need to fix things so that the directory you found is updated automatically:
ftp://ftp.pombase.org/pombe/genome_sequence_and_features/gff3/

The current FTP site directory has the gff3 files split by chromosome:
ftp://ftp.pombase.org/pombe/genome_sequence_and_features/gff3
Is that useful?  The current nightly load has a file with everything and forward and reverse strand files
ftp://ftp.pombase.org/nightly_update/gff/

I think people like the individual chromosomes for  Artemis loading etc.
I find it annoying if I want to do something by chromosome and I need to split them up because it isn't possible  using grep because chromosome is just a number.....

OK, no problem.  The current files were made for loading into JBrowse.  I'll add per-chromosome files too.

Yeah, I think bench biologist will appreciate separate files. They are likely want to do manipulations involving spreadsheets etc. They will inevitably want to split them up anyway.

The nightly load now generates GFF3 files per chromosome.  I'll check the FTP site in the morning to make sure it all got through.

I've checked the FTP site and everything is in the right place after the nightly load.


Update webHooks.md

@peeyushchoudharymsft,
Thanks for your contribution.
To ensure that the project team has proper rights to use your work, please complete the Contribution License Agreement at https://cla.microsoft.com.
It will cover your contributions to all Microsoft-managed open source projects.
Thanks,
Microsoft Pull Request Bot

@peeyushchoudharymsft, thanks for signing the contribution license agreement. We will now validate the agreement and then the pull request.
Thanks, Microsoft Pull Request Bot


Make umpire-config.cmake package relocatable

Use configure_package_config_file to make the umpire-config.cmake
package file "relocatable". The file can be moved after install and
still work. See: https://cmake.org/cmake/help/latest/module/CMakePackageConfigHelpers.html

I do think it looks right, but this is kinda new territory.  I’m not sure we actually have the binaries linking in a way that would allow the libraries to be relocated, but this shouldn’t hurt any cases that are currently expected to work, and it makes it easier to maintain and easier to support that later so I’m all for it.


[5.2] Contextual binding does not work for Filesystem

It seems that I can't use contextual binding to override the default provided Illuminate\Contracts\Filesystem\Filesystem (v5.2.10):
<?php namespace App;

use Illuminate\Contracts\Filesystem\Filesystem;

class TestFilesystem implements Filesystem
{
    // ...
}

<?php

namespace App\Providers;

use Illuminate\Support\ServiceProvider;

class AppServiceProvider extends ServiceProvider
{
    /**
     * Bootstrap any application services.
     *
     * @return void
     */
    public function boot()
    {
        //
    }

    /**
     * Register any application services.
     *
     * @return void
     */
    public function register()
    {
        $this->app->when('App\Http\Controllers\TestController')
            ->needs('Illuminate\Contracts\Filesystem\Filesystem')
            ->give('App\TestFilesystem');
    }
}

<?php

namespace App\Http\Controllers;

use Illuminate\Contracts\Filesystem\Filesystem;

class TestController extends Controller
{
	public function __construct(Filesystem $filesystem)
	{
		dd($filesystem);
	}
}

Output:
FilesystemAdapter {#120 ▼
  #driver: Filesystem {#119 ▼
    #adapter: Local {#118 ▼
      #pathSeparator: "/"
      #permissionMap: array:2 [▼
        "file" => array:2 [▼
          "public" => 484
          "private" => 448
        ]
        "dir" => array:2 [▼
          "public" => 493
          "private" => 448
        ]
      ]
      #writeFlags: 2
      -linkHandling: 2
      #pathPrefix: "/Users/hasyimibahrudin/Projects/fstest/storage/app/"
    }
    #plugins: []
    #config: null
  }
}

Is this the expected behavior?

What happens if you out that in boot out of interest?

The same thing happens. I still got FilesystemAdapter instead of TestFilesystem.

This is due to the Illuminate\Contracts\Filesystem\Filesystem interface being aliased to filesystem.disk by Laravel. By the time the contextual lookup is done, it is checking to see if filesystem.disk has a contextual setting, rather than the interface itself.
The quickest solution is to use filesystem.disk as the needs() parameter:
/**
 * Register any application services.
 *
 * @return void
 */
public function register()
{
    $this->app->when('App\Http\Controllers\TestController')
        ->needs('filesystem.disk')
        ->give('App\TestFilesystem');
}

I wouldn't consider this a bug, just a conflict with the aliasing system (a definite frustration for the end user still, though). I don't know enough about the intention behind aliases to determine how this can be potentially resolved for a future version of Laravel. Personally, I don't like using anything other than fully qualified class names in the container.

Thanks @cryode.

I believe this should be fixed in upcoming Laravel 5.4 release.


Question about CUDA failed with error out of memory error

Hi, I have recently changed the server and with this I have the possibility of an intel i5-10th iGPU and a nvidia GTX 1650
I am installing openai-whisper with the faster_whisper module, this is the docker-compose
services:
  whisperasr:
    image: onerahmet/openai-whisper-asr-webservice:latest-gpu
    container_name: Openai-Whisper
    environment:
      - ASR_MODEL=large
      - ASR_ENGINE=faster_whisper
    deploy:
      resources:
        reservations:
          devices:
            - driver: nvidia
              count: 1
              capabilities: [gpu]
    ports:
      - 9000:9000
    restart: unless-stopped

I was hoping to be able to use the large model but I think it is too big, in fact I get the error CUDA failed with error out of memory, it seems like it wants to dump it all into the video card ram, maybe what I am asking is impossible, but I don't know how the whole system works and I don't see mounted volumes, so I ask hoping the question is not too stupid, can't you download the model locally and use it without the need for it all to be loaded into memory? Or is there a way to share the system ram with the video card ram when needed?
J

Use smaller model or use device=cpu.

can't you download the model locally and use it without the need for it all to be loaded into memory?

You can't.

Thank you @Purfview for your reply.
For cpu ok, but what is the difference if I run this docker-compose?
services:
  whisperasr:
    image: onerahmet/openai-whisper-asr-webservice:latest
    environment:
      - ASR_MODEL=small
      - ASR_ENGINE=faster_whisper
    ports:
      - 9000:9000
    restart: unless-stopped

Is the same or is better to remain with this and specify the cpu mode?


Eady turbulence example

This PR adds an example that models baroclinic equilibration in the Eady problem. It uses biharmonic viscosity, a tuple of closures, and implements a background flow.

This PR also includes code for the two-dimensional Leith parameterization, but it is not compiled or added to the code. Depending on when this PR is merged, that work could be added to this PR. Otherwise, it will come later.
cc @navidcy @basileg


sendgrid - npm run dev - Error: Element type is invalid - You likely forgot to export your component

Dear reader,
In an attempt to make a typescript web app that will send an email I have tried following steps:

% npx create-remix@latest
cd into the directory of your newly created app folder
% npm install @react-email/html @react-email/button @react-email/render @sendgrid/mail
I copied the contents of the index.tsx to the root.tsx
and I created the email.tsx
I put the SENDGRID_API_KEY in the .env file
% npm run dev

Then I go to the web browser address: localhost:3000
And I get the error below.
Do you know how to resolve this?
Error: Element type is invalid: expected a string (for built-in components) or a class/function (for composite components) but got: undefined. You likely forgot to export your component from the file it's defined in, or you might have mixed up default and named imports.
at renderElement (/Users//Documents/webapps/typescript/typescript-test-0002/node_modules/react-dom/cjs/react-dom-server-legacy.node.development.js:6047:9)
at renderNodeDestructiveImpl (/Users//Documents/webapps/typescript/typescript-test-0002/node_modules/react-dom/cjs/react-dom-server-legacy.node.development.js:6108:11)
at renderNodeDestructive (/Users//Documents/webapps/typescript/typescript-test-0002/node_modules/react-dom/cjs/react-dom-server-legacy.node.development.js:6080:14)
at retryTask (/Users//Documents/webapps/typescript/typescript-test-0002/node_modules/react-dom/cjs/react-dom-server-legacy.node.development.js:6532:5)
at performWork (/Users//Documents/webapps/typescript/typescript-test-0002/node_modules/react-dom/cjs/react-dom-server-legacy.node.development.js:6580:7)
at /Users//Documents/webapps/typescript/typescript-test-0002/node_modules/react-dom/cjs/react-dom-server-legacy.node.development.js:6904:12
at scheduleWork (/Users//Documents/webapps/typescript/typescript-test-0002/node_modules/react-dom/cjs/react-dom-server-legacy.node.development.js:78:3)
at startWork (/Users//Documents/webapps/typescript/typescript-test-0002/node_modules/react-dom/cjs/react-dom-server-legacy.node.development.js:6903:3)
at renderToStringImpl (/Users//Documents/webapps/typescript/typescript-test-0002/node_modules/react-dom/cjs/react-dom-server-legacy.node.development.js:6977:3)
at Object.renderToStaticMarkup (/Users//Documents/webapps/typescript/typescript-test-0002/node_modules/react-dom/cjs/react-dom-server-legacy.node.development.js:7069:10)
Sincerely

Can you share the email.tsx code?

Hello Bu,
See the attachment.
Sincerely,
Martijn

On 1 Feb 2023, at 04:20, Bu Kinoshita @.***> wrote:
Can you share the email.tsx code?
—
Reply to this email directly, view it on GitHub https://github.com/resendlabs/react-email/issues/426#issuecomment-1411406796, or unsubscribe https://github.com/notifications/unsubscribe-auth/APLCWP5FQ4TCE7D3U4ODEJ3WVHJAHANCNFSM6AAAAAAUM6D2DY.
You are receiving this because you authored the thread.


[BUG] Copy button glides along when scrolling, it should remain fixed

https://github.com/code100x/daily-code/assets/72187548/0788faa8-712b-4769-9f62-61fb41376c7f

I think they are using predefined component form notion. Can't do much. I could be wrong but code component is being imported from notion.

I am able to reach the code block. But the next task is to add a custom code snippet block.

The code blocks are replaced by plain text.

I think I have arrived at a solution.

Seems to work now.

I will be working on this and I will raise a PR for this.


[Feature] Discord Rich Presence/Integeration

Rich Presence - it would be nice for the song, metadata, thumbnail and the time to be displayed like the official Spotify client.
e.g.

Integration - This would allow listen together sessions on discord (like on the official client). I'm pretty certain this is a massive stretch though and most likely impossible to implement.
But one can dream :)

Yeah, sorry no clue how that would be implemented and really not a priority given spot is still missing quite a few basic features sorry ;)

@Essasetic is you want discord RPC while you using spot there are a few MPRIS rpc clients you can get. such as this one I found: https://github.com/RayzrDev/discord-rpc-mpris . Doesn't do thumbnails (Can't really do thumbnails from normal discord applications) but shows song and artist name.

Don't quote me on that, but I think fixing #55 should also make Discord RPC work.


Markdown different from GitHub? Problem with Image size

Hi guys,
I've created a readme.md with an <img> tag inside and noticed that Gogs filters out the height and width information in the file preview.
My readme.md looks like this:
# Dev Repo

<img src="https://git-scm.com/images/logos/downloads/Git-Logo-2Color.png" height="100px">

I expected that the image is resized to 100px height (like on GitHub), instead this happend and you see the image in original size:

Also happens with width attribute, both attributes gets removed in preview.
Thanks.
Gogs Version: <IP_ADDRESS>8

It works perfect without the px, damn css and html mixture. My Mistake. Closed! :-)

:trollface:


Working with shared subnet aws-alb-ingress-controller can't create ingress

Steps to recreate

Share public and private subnet using a different account.

Create eks cluster using terraform-aws-eks (https://github.com/terraform-aws-modules/terraform-aws-eks/). Select all 4 nodes for control pane.

Create a worker asg in private subnet.

Deploy aws-alb-ingress-controller (1.1.0) using the helm

create ingress with annotations

 alb.ingress.kubernetes.io/scheme: internet-facing
 alb.ingress.kubernetes.io/security-groups: 'cluster_sg,worker_sg,https_sg'
 kubernetes.io/ingress.class: alb
 alb.ingress.kubernetes.io/listen-ports: '[{"HTTP":80,"HTTPS": 443}]'
 alb.ingress.kubernetes.io/subnets: 'public_subnet1,public_subnet2'

Observe exception as
E0221 10:28:14.476654       1 loadbalancer.go:195] echoserver/echoserver: 	status code: 400, request id: 64d66e20-35c3-11e9-93fe-d10ee5c193ac
E0221 10:28:14.477021       1 :0] kubebuilder/controller "msg"="Reconciler error" "error"="failed to create LoadBalancer due to ValidationError: A security group must be specified for creating a loadbalancer in a VPC not owned by the AWS account\n\tstatus code: 400, request id: 64d66e20-35c3-11e9-93fe-d10ee5c193ac"  "controller"="alb-ingress-controller" "request"={"Namespace":"echoserver","Name":"echoserver"}

@M00nF1sh were you able to address this in your last release? As mentioned I was able to create the load balancer by adding the unofficial variable but there is no target group launched.

/assign @M00nF1sh


Fixed interface

Fixed a number of interface issues. Only not implemented errors left in the validation log.

can not merge... sigh.


chore: updated/added deprecation message

Change list:

updated/added deprecation message.
Also removed usage of deprecated types in algorithms.go file

@shizhMSFT @Two-Hearts @rgnote  Can you please review this PR?


API struct tagged to produce proper output when marshalled #217

Signed-off-by: Kunal Kushwaha<EMAIL_ADDRESS>

You also need to change the code in client. Look at types.go there. Otherwise ci will fail.

Thanks for review. Issue fixed.

Please have only one commit given the second fixes a breakage from the first one.
I want to hear from @dave-tucker if this addresses his request in issue #217.
Specifically, if we go with the json tagging route, then shouldn't we tag the backend data structures and get rid of the response body structures in api/types.go, which were added for lack of tagging ?

Actually reading again issue #217, it looks like the issue is only about avoiding camelCase and capitalized fields in the json string... Then this is good. Only one more comment on the diffs and please have only one commit. Thanks.

Closing this. Created a new PR,


Allow for Multiple Potential Env Var Names

I am deploying an application to a few different cloud environments, where equivalent environment variables are not named the same.
To get around this, I wrote a small but super-useful multi_config that works the same way as config, but it takes in a variadic number of environment variable names to check. It iterates through these in order and returns the first matching & valid environment variable.
AWS_ACCESS_KEY_ID = multi_config('BUCKETEER_AWS_ACCESS_KEY_ID', 'S3_ACCESS_KEY_ID', cast=str, default=None)

I would like to upstream this to the package. I am creating a PR with the feature shortly and will use this issue as a reference.

Hi. I too deploy to different cloud environments, but I'm always able to specify the env vars names. This seems to me that a design challenge on a lower level is being corrected with decouple. Since this is too specific and against the design decisions of the project, this should not be on upstream. If you find ppl interested, maybe you should publish a complimentary library.

@dstarner I think the solution for this is:
AWS_ACCESS_KEY_ID = config('BUCKETEER_AWS_ACCESS_KEY_ID', default=config('S3_ACCESS_KEY_ID',default=None), cast=str)

you can wrap this in a function


Need to run Trim on Page Object Includes

Create a page object yaml file with two included files.
Put a space after the comma before the second page object

RESULT: The second page object file cannot be found because there is a space before the name.
EXPECTED: The page object would be found because the name is trimmed before the search happens.
This should probably be fixed in the FileManager

Hi, could I take a look at this issue?

Hi, I created a PR for this issue here: https://github.com/dougnoel/sentinel/pull/405
I think this addresses the issue, but not sure if there needs to be a better suited integration test? I couldn't figure out the right way to create a page object and have the included pages also be loaded

I'll take a look thanks. The page objects are YAML files.
On Mon, Aug 1, 2022, 8:53 AM AMehtaSL @.***> wrote:

Hi, I created a PR for this issue here: #405
https://github.com/dougnoel/sentinel/pull/405
I think this addresses the issue, but not sure if there needs to be a
better suited integration test? I couldn't figure out the right way to
create a page object and have the included pages also be loaded
—
Reply to this email directly, view it on GitHub
https://github.com/dougnoel/sentinel/issues/392#issuecomment-1201162533,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AFSR66LRHICFFO73PCSRNPTVW7CDJANCNFSM54TLXDYA
.
You are receiving this because you authored the thread.Message ID:
@.***>


Use smaller traits

I can certainly understand the desire to have four smaller traits instead of one larger one. That could give a bit more flexibility for implementors of custom parts of the codec, at the cost of having to potentially define four traits instead of one.
The other thing I'm not sure about is our error handling. We define some neat error types in error.rs, but then default right back to ServerFnError. I'd still love to be able to expand that a bit so people can return their own errors
Other than that it's basically the same thing, and I'm still excited about the approach.


Accept the same arguments as dict constructor for template rendering functions

The template rendering functions currently only accept named arguments to build the context dictionary passed to jinja2.Template.render(). While unpacking is easy enough, it would be nice to be able to use the same arguments as the dict constructor (like how Jinja's render function works).
Examples:
flask.render_template("index.html", {"greeting": "Hello", "name": "World"})
flask.render_template("index.html", {"greeting": "Hello"}, name="World")

I'll link a PR in case this is something people would like.

Thanks, but I prefer keeping this API simple, as you say dict unpacking already handles this.


LDAP support?

I was curious if there has been an LDAP plugin that has been contributed to the community or is that in the roadmap for Azkaban in the future.
Thanks!

https://github.com/researchgate/azkaban-ldap-usermanager is certainly available.


Avoid using hardcoded colors

The default mode_colors setting uses colors that don't work well with certain color schemes. I think that it would be better if staline-nvim would (by default) use colors based on the current color scheme instead of being hardcoded (kind of relates to #26).
I've gotten something like this to work with the following:
local function ExtractHl(name)
	return vim.api.nvim_exec('highlight ' .. name, true):match('guifg=(#[0-9A-Fa-f]+)')
end

require('staline').setup {
	mode_colors = {
		n  = ExtractHl("Normal"),
		i  = ExtractHl("Blue"),
		ic = ExtractHl("Green"),
		c  = ExtractHl("Purple"),
		v  = ExtractHl("Yellow"),
		['']  = ExtractHl("Yellow"),
		V  = ExtractHl("Orange"),
		t  = ExtractHl("Red"),
	}
}

This isn't perfect as ExtractHl will break if a highlight group does not exist or is linked to another group but it can definitely can be improved upon :D

vim.api.nvim_get_hl_by_name(hl_name, true) works great! This fixes the config from returning an error when a highlight group is linked but not when it does not exist. At that point however, I think it would make sense to fallback on the current default colors right?

Ah yes, setting fallback colors instead of hardcoding makes sense.
Will change when i get some free time 😅

Heyyo @is0n ,
I have pushed the fallback feature to main, let me know if it works when you have time.

It works perfectly and looks so nice!
Thanks again for your amazing work! 👍🏽


lib: src: simulations: Implement simple pendulum simulation

id: NA
Category: Physics

I'd like to work on this. Can you please assign it to me?

Hi @Sameerkash, We actually planned to do this but never got a around an accurate implementation. We would love to hear about how you would like to implement it! Let's discuss this first on gitter or slack.

Hello @sudhansukinng please go ahead. You can discuss your ideas on discord or gitter.


sometime map not loading

hai! do you know why this happens? 1.18.2 version.

map with chest load very fast btw. only sometime the map is like in the picture.

after flying around lootboxes to check on maps, so far only 1 map not loading which is the one near spawn.. i guess it needs more time to generate.

So long as you leave it in the chest, it should finish locating.
There are edge cases, like https://github.com/thebrightspark/AsyncLocator/issues/8 where it won't work if you break the chest, but I will fix that. But bear in mind I don't intend to down-port features so older versions like 1.18.2.

roger that. thank you!


add aliyun DNS plugin

add aliyun DNS plugin

Docker Image for build 1 is available on DockerHub as jc21/nginx-proxy-manager:github-pr-738

Thanks for the contribution :)


fix: attribute reference causing owner to not be identified

We were trying to run this Script as the administrator/owner of the Azure tenant/subscription and we encountered errors. We had to switch the reference to be .id instead of .objectId as the objectId key did not exist and the value null was getting assigned when performing the Owner permissions User check. When we changed it to .id, the script began to function as we expected.

@mardinyadegar - Thank you so much for your contribution! I just replicated this issue in my dev account:

Ran it with your fix and it all works as expected:

I do wonder what happened? 🤔 Maybe Azure changed their APIs or the CLI 😕 - Very confusing...

Thank you for the merge. We are happy to use Lacework and happy to contribute. Not sure what happened with Azure, but we are glad it seemed simple to fix.


coral-schema: merge schema if avro schema is outdated

If table avro schema is outdated compared to Hive schema, we merge them as the new table schema.

Could you merge the latest commits to your branch coral-schema-merging so that it is easier to run integration test?

Rebased latest master and triggered integration testing.

Could you please add tests?

Added unit tests in MergeHiveSchemaWithAvroTests. Link: https://github.com/linkedin/coral/pull/92/files#diff-0db0e1ab014dff3e66ebc8109a0a2c0ac0b15facc586e3b0890f02d1d6f9521f

There seems to be some regressions in the integration test, could you fix them?


Bug report: Wrong model aspect ratio in the diagnostic if setting it after specifying the basis

What
If during the initialization of the model the aspect ratio n is changed after the setting of the basis of functions, like in :
# Model parameters instantiation with some non-default specs
model_parameters = QgParams({'phi0_npi': np.deg2rad(50.)/np.pi, 'hd':0.3})
# Mode truncation at the wavenumber 2 in both x and y spatial coordinate
model_parameters.set_atmospheric_channel_fourier_modes(2, 2)

model_parameters.set_params({'n': 0.3})

then the model core compute the trajectories with the right aspect ratio, but the diagnostic classes are not. You can thus trust the model output but not the diagnostic ones (see temporary solution below).
Consequences
Due to the fact that the aspect ratio n is incorrect in the diagnostics, it can lead to aberrant spatial field renditions (again, in the spectral domain the model results are correct). For instance, for the example above, the Fourier basis function 2 * sin (y) * cos(n * y) is rendered as

where many maxima and minima can be seen over the domain, instead of only one maxima and one minima (see below). Aliasing due to an incorrect sampling can also be seen.
Again, this impact only your results when you use diagnostic classes to obtain spatial fields.
Temporary solution
Presently, the simplest way to avoid this bug is to instantiate the QgParams object for the model configuration directly with the desired aspect ratio:
# Model parameters instantiation with some non-default specs
model_parameters = QgParams({'phi0_npi': np.deg2rad(50.)/np.pi, 'hd':0.3, 'n':1.3})
# Mode truncation at the wavenumber 2 in both x and y spatial coordinate
model_parameters.set_atmospheric_channel_fourier_modes(2, 2)

This ensures that the aspect ratio is properly communicated to the diagnostics. In this case, the Fourier basis function above is rendered as:

Final solution
This bug will be resolved soon, but we are in the middle of a very thorough modification of the model's core and thus we need to wait that other issues are resolved before moving to this one. The final bugfix should come at the end of 2022.

Solved by https://github.com/Climdyn/qgs/pull/15

Solved by merging develop to master.


Exclude test files from indexing.

May put this into command line argument, but now just use a default one.

but it still needs to be fixed here https://github.com/padawan-php/padawan.php/pull/54

yes, I'm working on it. And also some code to make sure that cached index is used while the editing file has semantic errors.
Scenario:
Given file:
<?php
function test_function_one() {
    return new Class();
}

function test_function() {
    if (test_function_one()->{complete here}
}

And indexed file:
<?php
function test_function_one() {
    return new Class();
}

function test_function() {
}


WIP: User-friendly message if you are running without root permissions

There's a lot missing here (such as all kinds tests and perhaps some extra functionality). Just uploaded to get some early feedback on style.
Will update this body later.
Resolves: #246

Codecov Report
Attention: Patch coverage is 42.50000% with 23 lines in your changes missing coverage. Please review.

Project coverage is 36.93%. Comparing base (1f8435d) to head (6bef825).
Report is 1 commits behind head on main.

Files
Patch %
Lines

pkg/beyla/os.go
45.94%
18 Missing and 2 partials :warning:

cmd/beyla/main.go
0.00%
2 Missing and 1 partial :warning:

:exclamation:  There is a different number of reports uploaded between BASE (1f8435d) and HEAD (6bef825). Click for more details.
HEAD has 2 uploads less than BASE

Flag
BASE (1f8435d)
HEAD (6bef825)

unittests
1
0

k8s-integration-test
1
0

Additional details and impacted files
@@             Coverage Diff             @@
##             main    #1067       +/-   ##
===========================================
- Coverage   79.20%   36.93%   -42.27%
===========================================
  Files         139      138        -1
  Lines       11328    11364       +36
===========================================
- Hits         8972     4197     -4775
- Misses       1812     6744     +4932
+ Partials      544      423      -121

Flag
Coverage Δ

k8s-integration-test
?

oats-test
36.93% <42.50%> (+0.01%)
:arrow_up:

unittests
?

Flags with carried forward coverage won't be shown. Click here to find out more.

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


Why cpp

Any way to use it without cpp
I want use java only

@michoael we are working on adding vad support, realtime transcription and noise processing. Supporting these feature in Java will add significant delay. So using native code to add these feature to avoid processing delay.
Still you can use java only code by initialising whisper engine instance with Java engine instead of Native engine in Whisper.java

Okay, thanks.
Now i can use it to transcription in realTime when i speaking withOut end recorder?
Now i can use it with long wav file?

Yes. We will support realtime transcription and long wav file transcription. It is under implementation.

I hope do this very soon, thanks


FIX: Broken Link to Source Repo

I noticed that the link to this repo is actually incorrect. I have fixed that

Looks good, thanks!


grammar.h is missing in Python 3.10

Describe the bug
I just want to note here that with python 3.10 the project cannot be built anymore, because the grammar.h including the parser module has been removed.
See https://docs.python.org/3/whatsnew/3.10.html#removed

Removed the parser module, which was deprecated in 3.9 due to the switch to the new PEG parser, as well as all the C source and header files that were only being used by the old parser, including node.h, parser.h, graminit.h and grammar.h.

To Reproduce

mkdir build && cd build
cmake ..  -DHAL_STUDY=0 -DBUILD_ALL_PLUGINS=1 -DCMAKE_INSTALL_PREFIX=/usr -GNinja
ninja

The error message looks something like this:
[433/720] Building CXX object plugins/gui/CMakeFiles/gui.dir/src/python/python_context.cpp.o
FAILED: plugins/gui/CMakeFiles/gui.dir/src/python/python_context.cpp.o
/usr/bin/ccache /usr/bin/c++ -DFMT_LOCALE -DFMT_SHARED -DQT_CONCURRENT_LIB -DQT_CORE_LIB -DQT_GUI_LIB -DQT_NO_DEBUG -DQT_NO_KEYWORDS -DQT_SVG_LIB -DQT_WIDGETS_LIB -DSPDLOG_COMPILED_LIB -DSPDLOG_FMT_EXTERNAL -DSPDLOG_SHARED_LIB -Dgui_EXPORTS -I/home/daniel/Desktop/other_repos/hal/include -I/home/daniel/Desktop/other_repos/hal/hal_plugins -I/home/daniel/Desktop/other_repos/hal/plugins -I/home/daniel/Desktop/other_repos/hal/build -isystem /home/daniel/Desktop/other_repos/hal/plugins/gui/include -isystem /usr/include/python3.10 -isystem /usr/include/qt -isystem /usr/include/qt/QtWidgets -isystem /usr/include/qt/QtGui -isystem /usr/include/qt/QtCore -isystem /usr/lib/qt/mkspecs/linux-g++ -isystem /usr/include/qt/QtConcurrent -isystem /usr/include/qt/QtSvg -fopenmp -pthread -O3 -DNDEBUG -fPIC -O3 -DNDEBUG -Wall -Wextra -pedantic -Wshadow -Wno-undef -Werror=return-type -fdiagnostics-color=always -fsized-deallocation -fPIC -std=gnu++17 -MD -MT plugins/gui/CMakeFiles/gui.dir/src/python/python_context.cpp.o -MF plugins/gui/CMakeFiles/gui.dir/src/python/python_context.cpp.o.d -o plugins/gui/CMakeFiles/gui.dir/src/python/python_context.cpp.o -c /home/daniel/Desktop/other_repos/hal/plugins/gui/src/python/python_context.cpp
/home/daniel/Desktop/other_repos/hal/plugins/gui/src/python/python_context.cpp:19:10: schwerwiegender Fehler: grammar.h: Datei oder Verzeichnis nicht gefunden
   19 | #include <grammar.h>
      |          ^~~~~~~~~~~
Kompilierung beendet.

Expected behavior
I suppose we would have to switch to the PEG parser.
Desktop (please complete the following information):

OS: Arch Linux 5.16.1-arch1-1

Additional context
Since only Ubuntu 20.04 is officially supported at the moment, this is not very urgent.

Should be fixed by #463


Managed Indices Policy needs to start with a state named "hot"

Describe the bug
I could not save my index policy if the first state name is other than "hot". The error messages that is returned says:
Failed to create policy: [illegal_argument_exception] Policy must have a valid default state
To Reproduce
Steps to reproduce the behavior:

Click Index Management->IndexPolicies->Create policy
Click on Visual editor and press Continue
Choose a name for policy
Scroll down to States(2) and edit state hot and change it to hot2 or something different than hot, press Update state
Error message occurs: Failed to create policy: [illegal_argument_exception] Policy must have a valid default state

Expected behavior
It should be saved and it should be valid to choose own state names.
OpenSearch Version
Please list the version of OpenSearch being used.
Dashboards Version
1.2 latest version
Plugins
all default plugins

There was a bug where changing the value of the current default state wouldn't also update the value of the default_state field in the policy.
Current workaround is you have to toggle the default state dropdown to a different state and then back to the one you originally wanted.
Fix has been created here and will go out in the next release
https://github.com/opensearch-project/index-management-dashboards-plugin/pull/145


iOS/MacOS/iPad OS - Fetching Manifest error even on Sample App

Have you read the FAQ and checked for duplicate open issues?
Yes
If the problem is related to FairPlay, have you read the tutorial?
/
What version of Shaka Player are you using?
4.9.0
Can you reproduce the issue with our latest release version?
Yes
Can you reproduce the issue with the latest code from main?
Yes
Are you using the demo app or your own custom app?
Both
If custom app, can you reproduce the issue using our demo app?
/
What browser and OS are you using?
Safari macOS / ipad OS / iphone iOS
For embedded devices (smart TVs, etc.), what model and firmware version are you using?
/
What are the manifest and license server URIs?
any m3u8 manifest even those you have online
-- https://shaka-player-demo.appspot.com/demo/#audiolang=fr-FR;textlang=fr-FR;uilang=fr-FR;asset=https://storage.googleapis.com/shaka-demo-assets/bbb-dark-truths-hls/hls.m3u8;panel=ALL_CONTENT;panelData=HLS;build=uncompiled --
What configuration are you using?  What is the output of player.getConfiguration()?
/
What did you do?
Start content on the player
What did you expect to happen?
Fetching all my tracks from my manifest
What actually happened?
Are you planning send a PR to fix it?
No


afterEach hook doesn't runs after a test failure

For more context:

https://github.com/wellwelwel/poku/issues/580#issuecomment-2248316882

By using beforeEach and afterEach, if a failure occurs in its scope, the error will be emitted, the process is exited as 0 instead of 1.


python311Packages.pyswitchbot: 0.47.2 -> 0.48.0

Diff: https://github.com/Danielhiversen/pySwitchbot/compare/refs/tags/0.47.2...0.48.0
Changelog: https://github.com/Danielhiversen/pySwitchbot/releases/tag/0.48.0
Description of changes

Things done

Built on platform(s)

[ ] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
24.11 Release Notes (or backporting 23.11 and 24.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[ ] Fits CONTRIBUTING.md.

Add a :+1: reaction to pull requests you find important.

Result of nixpkgs-review pr 321213 run on x86_64-linux 1

8 packages built:

home-assistant-component-tests.bluetooth
home-assistant-component-tests.mopeka
home-assistant-component-tests.shelly
home-assistant-component-tests.switchbot
python311Packages.pyswitchbot
python311Packages.pyswitchbot.dist
python312Packages.pyswitchbot
python312Packages.pyswitchbot.dist


[raudio] Switching audio output on windows crashes

[x] I tested it on latest raylib version from master branch
[x] I checked there is no similar issue already reported
[x] I checked the documentation on the wiki
[x] My code has no errors or misuse of raylib

Issue description
Briefly describe the issue you are experiencing (or the feature you want to see added to raylib). Tell us what you were trying to do and what happened instead. Remember, this is not the best place to ask questions. For questions, go to raylib Discord server.
Environment
Windows 10
Issue Screenshot
https://github.com/raysan5/raylib/assets/34615798/ded1538f-8285-431b-9a45-7db6db528d59
I am using rust bindings of raylib on 5.0 master but someone else confirmed the same for C++ as well. https://discord.com/channels/426912293134270465/427518168995725317/1168659928651669625

It dies in the miniaudio worker thread, not raylib. Raylib can't fix this, it would have to be fixed on the miniaudio side. I recommend you report it there.

As Jeff mentions, this is related to miniaudio, afaik, not much can be done on raylib side.


License Demo and installer still exist in the code base

Are these used anywhere now ?
Krypton-NET-5.470/Source/Krypton Components/ComponentFactory.Krypton.Navigator/

and what about these?

No, they can be removed

I was running it from a remote drive, therefore when the UAC was supposed to pop-up, it just bombed out as above.
The installer should either copy local, or state up front that UAC is needed (i.e. use a manifest to make user copy to local machine) via an icon overlay in Explorer (Automatic via manifest)

Might need to look for an alternative installer, would WIX work? Or I could try NSIS?

Maybe with this theme?

I use WIX all the time,
As I understand it: Nullsoft would be easier for something like this, because its a "Take directory" and install it with a shortcut to 1 app


[5.1] CapturePromotion: Fix promotion of resilient but locally non-re…

…silient types
Pass the resilience expansion to the cloner so that it can correctly (in
agreement with the caller) decide whether something is address only.
rdar://52263202

@swift-ci Please test

@swift-ci Please test

Build failed
Swift Test Linux Platform
Git Sha - e0fbc122a38ea10685893171a10a7e0ca8122cb6

Build failed
Swift Test OS X Platform
Git Sha - e0fbc122a38ea10685893171a10a7e0ca8122cb6

This patch is not necessary on swift-5.1-branch because this branch does not have the commit:
SIL: Use the best resilience expansion when lowering types
In swift-5.1-branch both relevant places (computeNewArgInterfaceTypes, isPartialApplyNonEscapingUser) query with a minimal resilience expansion.


Better error message for incomplete def

At least since e728e319c6373c63480817920ecffc9b8a42fd7b, the program
app "hello-world"
    packages { base: "platform" }
    imports []
    provides [ main ] to base

main =

panics during compilation/checking with
thread 'main' panicked at 'There were still outstanding Arc references to module_ids', /Users/hafi
z/Code/Roc/roc/compiler/load/src/file.rs:1573:33
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace

In the repl the true error is exposed:
» main =
thread 'main' panicked at 'not yet implemented: unhandled parse error: IndentEnd(3, 10)', reportin
g/src/error/parse.rs:546:14

It seems this issue is solved. The current message for the above code is:
── MISSING EXPRESSION ────────────────────────────────────────────── test4.roc ─

I am partway through parsing a definition, but I got stuck here:

 6│      provides [main] to pf
 7│
 8│  # main : Task.Task {} []
 9│
10│  main =
            ^

I was expecting to see an expression like 42 or "hello".

Also in the repl, there is now a decent error message:
INDENT ENDS AFTER EXPRESSION ────────────────────────────────────────────────

I am partway through parsing an expression, but I got stuck here:

1│  app "app" provides [replOutput] to "./platform"
2│
3│  replOutput =
4│      main =
              ^

Looks like the indentation ends prematurely here. Did you mean to have
another expression after this line?


Update Pages “WhenAreTermitesMostActivePage”

Automatically generated by Netlify CMS

👷 Deploy Preview for chic-shortbread-66a66b processing.

Name
Link

🔨 Latest commit
8d610cb75e2119c3718d1fdb13cc2c4f5aea8e3a

🔍 Latest deploy log
https://app.netlify.com/sites/chic-shortbread-66a66b/deploys/655fe2bcfc0b2d0008488bdf


Send XY color for non-osram hue bulbs

Description:
It seems that Philips bulbs don't display the correct colors when given a hue/sat command. This PR restores the previous behavior of sending an XY color command for non-osram bulbs.
Original behavior for reference:
https://github.com/home-assistant/home-assistant/pull/11288/files#diff-09fd3b3fbdd20cedcad9fcf474b4aeb7L275
Related issue (if applicable): fixes #13632 fixes #13614
Checklist:

[x] The code change is tested and works locally.
[x] Local tests pass with tox. Your PR cannot be merged unless tests pass

Hue/sat does support all possible bulb colors but they are shifted from xy and we don't know by how much because it differes for each light model. Maybe a reasonable comment would be:

We use our own conversion function for consistent xy->HS->xy translations.

However, I checked our xy conversion functions against Hue docs and I found a difference:
diff --git a/homeassistant/util/color.py b/homeassistant/util/color.py
--- a/homeassistant/util/color.py
+++ b/homeassistant/util/color.py
@@ -203,7 +203,7 @@ def color_RGB_to_xy_brightness(

     # Wide RGB D65 conversion formula
     X = R * 0.664511 + G * 0.154324 + B * 0.162028
-    Y = R * 0.313881 + G * 0.668433 + B * 0.047685
+    Y = R * 0.283881 + G * 0.668433 + B * 0.047685
     Z = R * 0.000088 + G * 0.072310 + B * 0.986039

     # Convert XYZ to xy

>>> color_xy_brightness_to_RGB(*color_RGB_to_xy_brightness(250, 250, 250))
(248, 255, 248)
>>> color_RGB_to_xy_brightness(*color_xy_brightness_to_RGB(0.5, 0.5, 128))
(0.486, 0.481, 128)

I think we should apply that diff to ensure that xy -> HS -> xy (as we end up with after this PR) actually does pass the original xy value to the bulb. That should then fix #13686 as well.

Is this staying in dev for the next release cycle or will there be another MR for a hotfix? Not saying it's urgent as I'm just sitting back on a 0.65 version - just curious how these things fit into the updated release cycle.

Updated to the beta which should include this but the color in the UI is now worse. Changing the colors on the picker now change the bulb colors but they don't change the icon in the UI. The color is now "stuck" on the green color even when the bulbs are changing.

@NaffanDroo Another hotfix is unlikely. The idea of the updated release cycle is that people like you try out the beta (it's out now) and report issues so the .0 release will have less bugs.
@omriasta you should report new bugs in new issues, though that one sounds like #13589


Emacs package updates

It's nice to keep these packages relatively up to date, and an update was specifically requested in #17298.
I've actually been running with a subset of the packages from these changes for several weeks now, though I generally restrict myself to the melpa-stable versions.
This was generated with a version of emacs2nix that has stable versioning for melpa packages, so from here on out, we shouldn't see wholesale updates when those are regenerated.
In addition, a couple of overrides that no longer apply to stable packages (because the things they needed unstable versions for have been themselves upgrade) are removed.  These are both packages that I specifically use.

@ttuegel, @DamienCassou if one of you wants to look at committing that, it would be great.

Thank you very much.