[2.6.4] RKE provisioned cluster become unreachable via UI and kubectl after some times

Rancher Server Setup

Rancher version: 2.6.4
Installation option (Docker install/Helm Chart): Helm, RKE1, K8S 1.21.10

Information about the Cluster

Kubernetes version: K8S 1.20.9
Cluster Type (Local/Downstream): Downsteam, the remote cluster was provisioned using docker command. We are able to reproduce this on two different cluster.

User Information

What is the role of the user logged in? Admin

Describe the bug
We noticed since the upgrade from 2.5.8 to 2.6.4 that our cluster would become unresponsive via the UI and via Kubectl. However, weirdly enough, if we log via the old ui (removing the /dashboard in the url and add login), we still can't see everything without issue...
To Reproduce
The fastest way we found to reproduce is to spam a few times (10-15, not in parallel) the following command toward the cluster, the cluster is quite busy so we get a bunch of logs doing this:
 kubectl logs -n ingress-nginx -f <nignx-ingress-pod> or  kubectl logs -n ingress-nginx <nignx-ingress-pod>
Result
After a few attempts, it will hang, and any command via kubectl will hang (either all the time or once every 2 attempts at the start). The cluster is still displayed as connected and healthy in the UI.
Expected Result
The command shouldn't hang making the interaction with the cluster impossible.
The situation never recover we are forced to kill all the rancher pod to restore the UI + kubectl.
Additional context
We are unsure if the kubectl logs is the reason or if it's just a quantity of data that is enough to block something in rancher.. We are wondering if we aren't in a similar case of this one where the routing that handle the forward to the cluster is blocked by a full buffer or something similar. But as the ticket is close, we aren't sure if it could be the same. https://github.com/rancher/rancher/issues/34819#issuecomment-1007600901
We also see alot of message mentioned in this one: https://github.com/rancher/rancher/issues/36584 but we aren't sure if they are the cause of our outages.
Also note that restarting the agent on the downstream or forcing a full connection interrupt between the agents and the cluster to make them reconnect doesn't fix the issue either, only a full kill of the rancher pod fixes our issue at the moment
SURE-4484

Exact same issue here....

the same issue.. =/
one of the three provisioned cluster become partly unavailable. not working Cluster Summary Page, external link to Longhorn UI , to Prometheus UI with proxy uRL

I just found the issue you all created, and believe the issue I commented on/joined (https://github.com/rancher/rancher/issues/37174) is related. Do any of you notice that kubectl shell is no longer working once you've upgraded from Rancher v2.6.2 to v2.6.4? Can't use the kubectl tool from the menu bar, nor can you do "execute shell" to connect to any pods.

Having the same issues as well with regards to going from 2.6.3 -> 2.6.4. But, can at least one of the downstream clusters use the kubectl from to UI.

Faced with the exactly same problem few days ago, right after upgrading to 2.4.0. Non of my monitoring stack or rancher downstream cluster ui is resplonsible, as downstream cluster via kubectl. But if i do direct access to downstream cluster, or grafana ingress endpoin, everything works fine. seems like the problem related to proxy part

Is anyone able to produce this from scratch starting with a new setup and a new downstream cluster? If not a new setup then at least a new cluster?

We are also affected. Baremetal, Onprem on Ubuntu 20.04.
As mentioned above, a restart of the cluster agent does not help.

We are also experimenting this.. but currently only on one of our down-stream clusters.
@AndreasDeCrinis what do you mean with "affected rancher pod"? The rancher/rancher:v2.6.4 pod on the mgmt cluster?

@beatsandpics exactly:
kubectl rollout restart -n=cattle-system deployment rancher
BTW it happened to us today. So ~4 days since the last restart. We set up monitoring and alerting using kube-prometheus probes to get alerted as soon as it pops up again.
this is the URL we continuously check: https://rancher.mycompany.com/k8s/clusters//api?timeout=32s

we are facing the same problem, the described restart is also for us the only way how we could fix this temporarily.
We played a little bit around with some timeout values in the cluster where the rancher application is deployed and since we did that, we did not have this issue (around 8 days). Maybe you could also try this values and it helps you.
Here is, what we changed:
kubectl get cm -n ingress-nginx ingress-nginx-controller -o json
{
    "data": {
        "client-body-timeout": "120",
        "client-header-timeout": "120",
        "keep-alive": "360",
        "proxy-send-timeout": "120",
    }
}

If this helps in your case, please let me know

@abaua unfortunately, increasing the timeouts did not solve it on our side. it occured again today

We are seeing this issue as well, @AndreasDeCrinis did you set those annotations as well as the configmap @abaua pasted?

@justdan96 @AndreasDeCrinis as i metnined above, try to do a new  backup of rancher state via rancher-backup operator, and then restore it right after that, its look dumb but it works, and  permanently fix that problem )

@T-helper I'll see if we can give it a go and test that it resolves the issue.

@rmweir why would we test this on new clusters? This problem is on many existing clusters.
Unable to connect to the server: net/http: request canceled (Client.Timeout exceeded while awaiting headers)
There are no log errors in rancher or downstream agents
Log nginx: upstream_status="-" upstream_response_time="32.000" request_uri="/k8s/clusters/[cluster]/apis?timeout=32s"
Rancher 2.6.5 and downstream clusters RKE 1.21.10 and 1.22.9
After restart rancher it's working for some time, till someone as mentioned above do:
To Reproduce
The fastest way we found to reproduce is to spam a few times (10-15, not in parallel) the following command toward the cluster, the cluster is quite busy so we get a bunch of logs doing this:
kubectl logs -n ingress-nginx -f  or kubectl logs -n ingress-nginx

why would we test this on new clusters? This problem is on many existing clusters with load.

@nickvth asking because we have not been able to reproduce this on the Rancher side, and it's very hard to debug without doing that. We've tried creating new downstream clusters and adding loads to them, then doing the kubectl logs steps, but still haven't seen this behavior. So there is some specific piece we are still missing.

@cbron We can reproduce this by obtaining logs from any pod with a large amount of logs.

this is the URL we continuously check: https://rancher.mycompany.com/k8s/clusters/c-clusterid/api?timeout=32s

We just had this issue reoccur and this URL returned with "200 OK" so I'm not sure it can be consistently relied upon to test the error occurred.

@fplantinga-guida Would you be able to say approximately how many log entries there are? I'm attempting to reproduce the issue on a pod with 20,000 logs but I am not able to so far.

I think we have the same issue here. We have 3 rancher pods, one of the pods stuck at somewhere.
I have tested with commands bellow. (pod-ip-1 is from working pods, pod-ip-2 is from stuck pod)
# this is working
curl -k -v -H 'Authorization: Bearer <TOKEN>' https://<pod-ip-1>/k8s/clusters/c-psxs4/apis

# this is not working
curl -k -v -H 'Authorization: Bearer <TOKEN>' https://<pod-ip-2>/k8s/clusters/c-psxs4/apis

# this is working
curl -k -v -H 'Authorization: Bearer <TOKEN>' https://<pod-ip-2>/k8s/clusters

closed #37747 in favor of tracking via this issue.

@justdan96
We reproduce this by enabling debug log for our promtail pods. In the example below you see the api requests on the ingress controller. Steps:

kubectl get pod promtail-8zghf (works fine)
kubectl logs promtail-8zghf -f (works fine)
kubectl get pod promtail-8zghf (not responding, have to cancel the command)

2022-05-27 10:50:23 | (no unique labels) | upstream_status="-" request_uri="/k8s/clusters/<redacted>/api/v1/namespaces/<redacted>/pods/promtail-8zghf" request_time="95.180"
2022-05-27 10:48:39 | (no unique labels) | upstream_status="200" request_uri="/k8s/clusters/<redacted>/api/v1/namespaces/<redacted>/pods/promtail-8zghf/log" request_time="10.328"
2022-05-27 10:48:28 | (no unique labels) | upstream_status="200" request_uri="/k8s/clusters/<redacted>/api/v1/namespaces/<redacted>/pods/promtail-8zghf" request_time="0.093"

After this Rancher is only available via the authorized endpoint and Rancher UI. It can only be fixed by restarting the rancher deployment.

I can reproduce on rancher 2.6.4, can't connect to imported clusters... (specially one of them which is in datacenter and much bigger than others)
Some facts (for this cluster, which is on kube 1.21 and built with kubeadm)

Cluster works fine (and admin credentials work good)
Rancher cluster main page doesn't load (c/c-rcjg6/explorer)
But if you click anywhere else (nodes/namespaces/..., c/c-rcjg6/explorer/projectsnamespaces) it works
And I can also click on "Kubectl shell" and it works perfectly from the rancher web console
However, accessing the cluster with kube config credentials from the internet doesn't work
It also doesn't work connecting with Curl (makes sense as i'm recreating the same queries that kubectl would do - i saw them with --v=9)
Querying svc/rancher through kubectl port-forwarding also doesn't work.

I am seeing this on an RKE cluster running in Azure, with the 2.6.4 Rancher node/ K3S also running in Azure.  This demo config in Azure had been working fine, I fired it up today to check it out and found my downstream RKE cluster stuck in this state, "Cluster Agent is not connected"

It looks this is reproducible on 2.6.5 as well, correct?

Correct, we upgraded from 2.6.2 to 2.6.5

Hello all, thanks for the information so far. We are trying to piece together the problem here. So far we have been unable to reproduce this on the Rancher side. Some questions to tie threads together:

For those that see this on only some of your clusters, are there any common traits between those affected clusters ? This could be things like k8s distro, k8s version, imported vs provisioned, or cluster usage.
Is anyone seeing this issue below k8s 1.21 ?
Has anyone seen this issue before Rancher 2.6.4 ?
Are people seeing high CPU usage on the downstream agent when this happens ?
Does Rancher have high CPU or memory usage ?
Does this only happen during high Rancher usage hours ? Meaning people updating things via Rancher or getting logs.
Downstream workload activity shouldn't matter here.
What do affected downstream clusters have in them. What amount of namespaces, workloads, rolebindings etc... This info we are looking for specifically to try and reproduce the bug.

Last time I restarted the rancher server pods (2 days ago), it kept working fine and has not broke ever since. If it happens again I'll happily try to answer all those questions. As OP said, maybe, who knows, is triggered by a huge burst/spam of api calls on that cluster, so I'll try that next week.

Hello all, thanks for the information so far. We are trying to piece together the problem here. So far we have been unable to reproduce this on the Rancher side. Some questions to tie threads together:

For those that see this on only some of your clusters, are there any common traits between those affected clusters ? This could be things like k8s distro, k8s version, imported vs provisioned, or cluster usage.
Is anyone seeing this issue below k8s 1.21 ?

yes.  1.20.11

Has anyone seen this issue before Rancher 2.6.4 ?

No.  The issue surfaced after the upgrade to 2.6.4

Are people seeing high CPU usage on the downstream agent when this happens ?

No.

Does Rancher have high CPU or memory usage ?

No.

Does this only happen during high Rancher usage hours ? Meaning people updating things via Rancher or getting logs.

I think yes.  Usually find out because someone is using kubectl and starts having issues

Downstream workload activity shouldn't matter here.

What do affected downstream clusters have in them. What amount of namespaces, workloads, rolebindings etc... This info we are looking for specifically to try and reproduce the bug.

It doesn't seem to be associated with any particular cluster (we have about 40 clusters)

I am running Rancher 2.6.5 on Kubernetes v1.22.9-eks-a64ea69, using nginx-ingress.
I have found a way to reliably reproduce the issue on my server. First I created a pod on one of my clusters that generates a large amount of logs:
apiVersion: apps/v1
kind: StatefulSet
metadata:
  labels:
    app: snowcrash
  name: snowcrash
spec:
  replicas: 1
  selector:
    matchLabels:
      app: snowcrash
  serviceName: snowcrash
  template:
    metadata:
      labels:
        app: snowcrash
    spec:
      containers:
        - command:
            - sh
            - -c
            - while true ; do sleep 1 ; dd if=/dev/zero bs=8M count=32 | xxd -c 1048576 ; done
          image: alpine
          name: snowcrash
          resources:
            requests:
              memory: "256Mi"
              cpu: "100m"
            limits:
              memory: "256Mi"
              cpu: "100m"

Next, using a kubeconfig that utilizes Rancher's auth proxy, I leave the following command running:
kubectl logs -f snowcrash-0

One instance of kubectl logs would eventually (5m?) make that cluster unreachable through the auth proxy. Running three of those in parallel would kill it in about 1-3 minutes. Restarting Rancher fixes everything. If I connect directly to the cluster instead of going through Rancher server's proxy everything works fine.
I tried kubectl attach through the proxy, and could run several instances of that in parallel experiencing any issues. There must be something different about kubectl logs that breaks things.

I could replicate. It took a few minutes but then I broke the clusterk with 3 tabs using kubectl logs.
Once the cluster is broken, I tried to set rancher pods to loglevel --set trace. But I could not find any specific "error" or exception. There are of course messages I don't understand, but nothing explicit related to errors when I send a request.

It's much more than that when you include all the vendored repo's. Not an efficient angle to attack it from. However, we have started to be able to reproduce this in-house thanks to @EC-Sean 's comment. Still some sporadic behavior, but leaving multiple console's following a logs feed is reproducing it at least some of the time. Hope to have a better update soon. We have started to look into specific commits between 2.6.3 and 2.6.4 which we think may be causing it.

We are also affected by this since the upgrade to Rancher 2.6.5.  We were running 2.6.2.  We can reproduce the issue in the same way with getting logs from multiple consoles on a downstream cluster.
Restarting the rancher pods on the Rancher cluster and then the cattle-cluster-agent pods on the downstream cluster fixes it.  For how long, no idea.
Case has been logged with SUSE support.

I've done quite a bit of work replicating the issue across our clusters - can I ask what people have for their Docker logging driver maximum file size? For example we aren't able to replicate in environments with these logging options in daemon.json:
{
  "log-opts": {
    "max-size": "10m",
    "max-file": "10"
  }
}

Larger values for the max-size seem to equate with being able to replicate the issue.

@justdan96 We have the same logging options for Docker in the daemon.json file.
  "log-opts": {
     "max-size": "10m",
     "max-file": "10"

Yet we are affected.  I just checked in one of the clusters that had the issue and it has those values. ( in fact, all of our clusters use those values. )

@justdan96 I do not have a daemon.json file. I'm running this version of docker:
 docker-ce | 5:20.10.8~3-0~ubuntu-bionic | https://download.docker.com/linux/ubuntu bionic/stable amd64 Packages

I believe the defaults are 10m and 3.

The defaults depend on the logging driver. We use json and the default size is unlimited and file count is 1.
Unsure if this is the cause but we're configured for 100m for size and leave the rest for default.
https://docs.docker.com/config/containers/logging/json-file/

Changing the logging driver settings is maybe a workaround but not a solution. Why is the max-size an issue after 2.6.4? This issue is only when you do kubectl logs over rancher api in combination with rancher cluster agent, when direct on k8s api (authorized endpoint) it’s always working and we have no issues.

I just changed our logging options in an affected cluster to 10m and 10 and are still seeing the same issue - so clearly something else is going on.

The cluster were I see most of the issues is on datacenter, whereas Rancher is on AWS. Just another hint, in case latency/slowness could be a factor.

In our environment I recognized a Crashloop of the cattle-cluster-agent. You can verify it with kubectl -n cattle-system get pods. If you have a high number of restarts, check the logs of the pods: kubectl -n cattle-system logs cattle-cluster-agent-7768b574c6-74jlw (<- adjust the pod name from the previous output).
It helped to redeploy the cluster agent, but only for a few seconds: kubectl rollout restart -n=cattle-system deployment cattle-cluster-agent.
This was our error trace you can retrieve with kubectl -n cattle-system logs  cattle-cluster-agent-7768b574c6-74jlw (<- adjust the pod name from the previous output):
E0614 04:55:52.712879      39 runtime.go:78] Observed a panic: runtime.boundsError{x:3, y:0, signed:true, code:0x2} (runtime error: slice bounds out of range [:3] with capacity 0)
goroutine 3461 [running]:
k8s.io/apimachinery/pkg/util/runtime.logPanic({0x3cee580, 0xc033910228})
	/go/pkg/mod/k8s.io/apimachinery@v0.23.3/pkg/util/runtime/runtime.go:74 +0x7d
k8s.io/apimachinery/pkg/util/runtime.HandleCrash({0x0, 0x0, 0xc01c5f2450})
	/go/pkg/mod/k8s.io/apimachinery@v0.23.3/pkg/util/runtime/runtime.go:48 +0x75
panic({0x3cee580, 0xc033910228})
	/usr/lib64/go/1.17/src/runtime/panic.go:1038 +0x215
github.com/rancher/rancher/pkg/catalogv2/helm.decodeHelm3({0x0, 0xc9d18d})
	/go/src/github.com/rancher/rancher/pkg/catalogv2/helm/helm3.go:124 +0x1b1
github.com/rancher/rancher/pkg/catalogv2/helm.fromHelm3Data({0x0, 0xc007d2be80}, 0x3fc4a54)
	/go/src/github.com/rancher/rancher/pkg/catalogv2/helm/helm3.go:23 +0x25
github.com/rancher/rancher/pkg/catalogv2/helm.ToRelease({0x47b3720, 0xc007d2be80}, 0x23)
	/go/src/github.com/rancher/rancher/pkg/catalogv2/helm/release.go:74 +0x3eb
github.com/rancher/rancher/pkg/controllers/dashboard/helm.(*appHandler).OnSecretChange(0xc00da90f50, {0xc00c33f810, 0x4f}, 0xc007d2be80)
	/go/src/github.com/rancher/rancher/pkg/controllers/dashboard/helm/apps.go:170 +0xa5
github.com/rancher/wrangler/pkg/generated/controllers/core/v1.FromSecretHandlerToHandler.func1({0xc00c33f810, 0x59f31e7551bea}, {0x47b3720, 0xc007d2be80})
	/go/pkg/mod/github.com/rancher/wrangler@v0.8.11-0.20220411195911-c2b951ab3480/pkg/generated/controllers/core/v1/secret.go:102 +0x44
github.com/rancher/lasso/pkg/controller.SharedControllerHandlerFunc.OnChange(0xc007d2be80, {0xc00c33f810, 0x400dc68}, {0x47b3720, 0xc007d2be80})
	/go/pkg/mod/github.com/rancher/lasso@v0.0.0-20220412224715-5f3517291ad4/pkg/controller/sharedcontroller.go:29 +0x38
github.com/rancher/lasso/pkg/controller.(*SharedHandler).OnChange(0xc001115860, {0xc00c33f810, 0x4f}, {0x47b3720, 0xc007d2be80})
	/go/pkg/mod/github.com/rancher/lasso@v0.0.0-20220412224715-5f3517291ad4/pkg/controller/sharedhandler.go:75 +0x23f
github.com/rancher/lasso/pkg/controller.(*controller).syncHandler(0xc001200f20, {0xc00c33f810, 0x4f})
	/go/pkg/mod/github.com/rancher/lasso@v0.0.0-20220412224715-5f3517291ad4/pkg/controller/controller.go:220 +0x93
github.com/rancher/lasso/pkg/controller.(*controller).processSingleItem(0xc001200f20, {0x35b2e60, 0xc01c5f2450})
	/go/pkg/mod/github.com/rancher/lasso@v0.0.0-20220412224715-5f3517291ad4/pkg/controller/controller.go:201 +0x10e
github.com/rancher/lasso/pkg/controller.(*controller).processNextWorkItem(0xc001200f20)
	/go/pkg/mod/github.com/rancher/lasso@v0.0.0-20220412224715-5f3517291ad4/pkg/controller/controller.go:178 +0x46
github.com/rancher/lasso/pkg/controller.(*controller).runWorker(...)
	/go/pkg/mod/github.com/rancher/lasso@v0.0.0-20220412224715-5f3517291ad4/pkg/controller/controller.go:167
k8s.io/apimachinery/pkg/util/wait.BackoffUntil.func1(0x7f1cabfda990)
	/go/pkg/mod/k8s.io/apimachinery@v0.23.3/pkg/util/wait/wait.go:155 +0x67
k8s.io/apimachinery/pkg/util/wait.BackoffUntil(0x634c6e77772f4b64, {0x4781a40, 0xc00c46a7e0}, 0x1, 0xc0005fc3c0)
	/go/pkg/mod/k8s.io/apimachinery@v0.23.3/pkg/util/wait/wait.go:156 +0xb6
k8s.io/apimachinery/pkg/util/wait.JitterUntil(0x394b5a6f75694f54, 0x3b9aca00, 0x0, 0x56, 0x3538473137534676)
	/go/pkg/mod/k8s.io/apimachinery@v0.23.3/pkg/util/wait/wait.go:133 +0x89
k8s.io/apimachinery/pkg/util/wait.Until(0x4450625a784f315a, 0x4c6a576f6a61336b, 0x436d506f2f4d5475)
	/go/pkg/mod/k8s.io/apimachinery@v0.23.3/pkg/util/wait/wait.go:90 +0x25
created by github.com/rancher/lasso/pkg/controller.(*controller).run
	/go/pkg/mod/github.com/rancher/lasso@v0.0.0-20220412224715-5f3517291ad4/pkg/controller/controller.go:135 +0x2c6
panic: runtime error: slice bounds out of range [:3] with capacity 0 [recovered]
	panic: runtime error: slice bounds out of range [:3] with capacity 0

The cluster agent seemed to crash while reading a Helm secret. We worked on a Helm deployment before the UI was unaccessible. The Helm secret of this deployment seemed to be corrupt, so helm list returned an error. So we deleted the Helm secrets and the cluster agent stopped restarting (kubectl -n cattle-system get pods) which brought back the Rancher UI for us.
Although your situation might be very different, I hope the debug steps described helps to better understand what's going on and maybe brings back your UI as well. If you also have corrupt resources, restoring a recent etcd snapshot might help if it's okay for you to loose latest changes and to have a downtime while the restore is in progress.

@jaimehrubiks We are in the same scenario, RKE in our data centres is seeing the issue but GKE and EKS are not.

We're facing the same problem.

It's good to see the issue will be resolved soon, is anyone in this thread able to test if the following PRs resolve their issue? https://github.com/rancher/rancher/pull/38096 https://github.com/rancher/remotedialer/pull/46

I've built 2.6.5 with bumped version of remotedialer.
If I'll be able to replicate issue on dev environment, I'll test this change.

Hi,
we have fixed this Issue in a way, that so far no one has mentioned. We had a problem with our rancher setup. We determined that this command:
kubectl get pods -A | awk '{ system ("kubectl logs --all-containers " $2 " -n " $1) }'
pretty reliably crashed rancher with the error about remotedial mentioned above.
After some research, where we for example activated log rotate as mentioned, we found a flag in the api, that seems to have caused this.
We used the API extraArg --service-account-api-audience before upgrading to Rancher version 2.6.5. The key-value is deprecated and is now called --api-audiences.
We missed that, and after some research realized, that rancher ignored --service-account-api-audience and set --api-audiences, but to unknown. So we removed the Flag --service-account-api-audience and added --api-audiences=api (which rancher itself set to --api-audiences=unknown) and after that, everything works fine.
Maybe this causes the error and this is the fix? Could someone verify that?

We used the API extraArg --service-account-api-audience before upgrading to Rancher version 2.6.5. The key-value is deprecated and is now called --api-audiences.
Maybe this causes the error and this is the fix? Could someone verify that?

https://github.com/rancher/rancher/issues/37250
We tried setting the kube-apiserver flag for our RKE clusters. This resulted in the token authentication not working anymore.

@konih the value of --api-audiences needs to match the one from --service-account-issuer in our case (I am in the same team as @GentianRrafshi ).
This only makes sense if you have --service-account-api-audience set and are running a Kubernetes version affected by the deprecation I guess.
It is the only change we did since we can't reproduce the rancher agent issues anymore so we are not sure if this is the real cause. Our Kubernetes clusters are running 1.22.9
I hope this helps :)

Was not able to reproduce this issue using verified repro steps on the latest 2.5.15-rc1 or 2.6.6-rc2. This issue is resolved.
Note that previous behavior has also been observed: if attempting to stream logs using multiple concurrent connections (running kubectl logs -f with multiple shell instances) then the following error might be encountered error: stream error: stream ID 3; PROTOCOL_ERROR; received from peer.

I've also confirmed on 2.6.5 + just remotedialer patch.

The issue is still there even after upgrading to v2.6.6
Getting below error:
helm upgrade --install dev-calico-ipam . '--kubeconfig=****' '--namespace=dev-ipam'
Error: Kubernetes cluster unreachable: Get "https://rancher.xyz.net/k8s/clusters/c-123/version?timeout=32s": net/http: TLS handshake timeout
My environment details:
RKE2 Version: v1.23.6+rke2r1
Rancher Version: v2.6.6
Downstream K8s version: v1.21.7

the same issue.. =/ one of the 3 provisioned cluster become partly unavailable. not working Cluster Summary Page, external link to Longhorn UI , to Prometheus UI with proxy uRL

Exactly facing the same issue Rancher v2.6.4! :-(

@beatsandpics exactly: kubectl rollout restart -n=cattle-system deployment rancher
BTW it happened to us today. So ~4 days since the last restart. We set up monitoring and alerting using kube-prometheus probes to get alerted as soon as it pops up again. this is the URL we continuously check: https://rancher.mycompany.com/k8s/clusters/c-clusterid/api?timeout=32s

Unable to open Downstream Cluster Summary Page, Pods summary page, external link to Longhorn UI , to Grafana monitoring page with proxy URL. We had setup another Downstream cluster which is was working fine while the other Downstream cluster breaking our heads!
This is fix worked perfectly for now in Rancher v2.6.4 - kubectl rollout restart -n=cattle-system deployment rancher

same here 2.6.6

runs stable since 25d in 2.6.6

Still seeing this issue w/ 2.6.6 and 2.6.7 a couple of times per day:
  |   | 2022/08/22 12:08:03 [INFO] error in remotedialer server [400]: websocket: close 1006 (abnormal closure): unexpected EOF
  |   | 2022/08/22 12:08:03 [INFO] error in remotedialer server [400]: websocket: close 1006 (abnormal closure): unexpected EOF
  |   | 2022/08/22 12:08:03 [INFO] error in remotedialer server [400]: websocket: close 1006 (abnormal closure): unexpected EOF
  |   | 2022/08/22 12:08:03 [INFO] error in remotedialer server [400]: websocket: close 1006 (abnormal closure): unexpected EOF
  |   | 2022/08/22 12:08:03 [INFO] error in remotedialer server [400]: websocket: close 1006 (abnormal closure): unexpected EOF
  |   | 2022/08/22 12:08:03 [INFO] error in remotedialer server [400]: websocket: close 1006 (abnormal closure): unexpected EOF
  |   | 2022/08/22 12:08:03 [INFO] error in remotedialer server [400]: websocket: close 1006 (abnormal closure): unexpected EOF
  |   | 2022/08/22 12:08:03 [INFO] error in remotedialer server [400]: websocket: close 1006 (abnormal closure): unexpected EOF
  |   | 2022/08/22 11:32:23 [INFO] error in remotedialer server [400]: read tcp <IP_ADDRESS>:80-><IP_ADDRESS>:54940: i/o timeout
  |   | 2022/08/22 05:39:43 [INFO] error in remotedialer server [400]: read tcp <IP_ADDRESS>:443-><IP_ADDRESS>:50982: read: connection reset by peer
  |   | 2022/08/22 03:17:22 [INFO] error in remotedialer server [400]: read tcp <IP_ADDRESS>:80-><IP_ADDRESS>:36940: i/o timeout
  |   | 2022/08/22 03:17:22 [INFO] error in remotedialer server [400]: websocket: close 1006 (abnormal closure): unexpected EOF
  |   | 2022/08/21 21:41:52 [INFO] error in remotedialer server [400]: read tcp <IP_ADDRESS>:443-><IP_ADDRESS>:58050: read: connection reset by peer
  |   | 2022/08/21 13:14:00 [INFO] error in remotedialer server [400]: read tcp <IP_ADDRESS>:443-><IP_ADDRESS>:33576: read: connection reset by peer
  |   | 2022/08/20 13:02:37 [INFO] error in remotedialer server [400]: read tcp <IP_ADDRESS>:443-><IP_ADDRESS>:55962: read: connection reset by peer
  |   | 2022/08/20 13:01:51 [INFO] error in remotedialer server [400]: read tcp <IP_ADDRESS>:443-><IP_ADDRESS>:55118: read: connection reset by peer

As a workaround, we continuously check https://rancher<...>/k8s/clusters//api?timeout=10s and restart Rancher if needed. Obviously, this is not a long-term solution.

@medicol69 We were affected on this remote dialer thing for a very long time with sporadic outages on downstream clusters (mostly with high load on Kube API). This is done in 2.6.6. If you facing this again, you should verify if all agents are really updated to 2.6.6. Or it's another incident.


take into account 'minItems' when generating arrays in the grammar

See https://swagger.io/docs/specification/data-models/data-types.
RESTler should generate the minimum number of required elements to successfully execute the payload.  (Then, the payload body checker will fuzz element lengths outside this range).  The values generated should be unique.
type: array
items:
type: integer
minItems: 1
maxItems: 10

We hit this issue while trying to fuzz MLFlow Serve REST APIs: the ML inference endpoint requires arrays of 10 numbers to accept the request. In our case the numbers do not need to be unique. Is there a workaround until min/max items is supported?
Swagger:
swagger: "2.0"
info:
  version: "1.0.0"
  title: "MLFlow Model Serving"
host: "<IP_ADDRESS>:5000"
schemes:
- "http"
paths:
  /invocations:
    post:
      consumes:
      - "application/json; format=pandas-split"
      produces:
      - "application/json"
      parameters:
      - in: "body"
        name: "body"
        required: true
        schema:
          type: "object"
          required:
          - "data"
          properties:
            data:
              type: "array"
              minItems: 1
              items:
                type: "array"
                minItems: 10
                maxItems: 10
                items:
                  type: "number"
      responses:
        "200":
          description: "OK"
        "500":
          description: "Internal Server Error"

Adding examples in the Swagger helped a bit. The array appears to get truncated though: instead of containing 10 items, requests only contain 5.
swagger: "2.0"
info:
  version: 1.0.0
  title: MLFlow Model Serving
host: <IP_ADDRESS>:5000
schemes:
- http
paths:
  /invocations:
    post:
      consumes:
      - application/json; format=pandas-split
      produces:
      - application/json
      parameters:
      - in: body
        name: body
        required: true
        schema:
          type: object
          required:
          - data
          properties:
            data:
              type: array
              minItems: 1
              items:
                type: array
                minItems: 10
                maxItems: 10
                items:
                  type: number
                example: [0.0199132142,0.0506801187,0.1048086895,0.0700725447,-0.0359677813,-0.0266789028,-0.0249926566,-0.002592262,0.0037117382,0.0403433716]
      responses:
        "200":
          description: Inference result
          schema:
            type: array
            minItems: 1
            items:
              type: number
            example: [235.11371081266924]
        "500":
          description: Internal server error


Yarn creates incompatible @ngtools/webpack/node_modules (AppModule is not an NgModule)

- [X] bug report -> please search issues before submitting
- [ ] feature request

There have been a number of reports about Angular 4 working with npm. But failing with the following error message on "ng build" when yarn has been used:
ERROR in AppModule is not an NgModule
Among the many differences in node_modules between npm and yarn, I traced the issue down to the folder node_modules/@ngtools/webpack/node_modules. It does not exist on npm install, but yarn creates it with loader-utils (version 1.1.0) and typescript (version 2.2.2).
Deleting this folder fixes the "AppModule is not an NgModule" error and the project can be compiled successfully.
Please note: The typescript version in that folder is 2.2.2. The instructions at Updating to 4.0.0 suggest to use typescript@latest, which results in ^2.3.3 in package.json
Versions.

@angular/cli: 1.0.4
node: 6.9.5 os: linux x64
@angular/animations, @angular/common, @angular/compiler, @angular/core, @angular/forms, @angular/http, @angular/platform-browser, @angular/platform-browser-dynamic, @angular/router and
@angular/compiler-cli: 4.1.3
typescript: 2.3.3
npm: 3.10.10
yarn: 0.19.1

The log given by the failure.

ng build --prod --aot
Hash: f51dd13e0d7162822443
Time: 20451ms
chunk    {0} styles.96c0a658294179b6d7fc.bundle.css (styles) 281 bytes {3} [initial] [rendered]
chunk    {1} main.117d403616e3c6b9015d.bundle.js (main) 1.39 kB {2} [initial] [rendered]
chunk    {2} vendor.c85a90b3d399a6fd167d.bundle.js (vendor) 1.04 MB [initial] [rendered]
chunk    {3} inline.d05467de75134d5563b5.bundle.js (inline) 0 bytes [entry] [rendered]

ERROR in AppModule is not an NgModule

ERROR in ./src/main.ts
Module not found: Error: Can't resolve './$$_gendir/app/app.module.ngfactory' in '/tmp/hisngyarn/src'
 @ ./src/main.ts 5:0-74
 @ multi ./src/main.ts

Mention any other details that might be useful.
package.json.txt

Changing package.json to the exact same typescript version 2.2.2 prevents the error as well.

My guess is your yarn lock file is working against you.  It probably linked TS 2.2.2 to @ngtools/webpack before the upgrade attempt and is trying to give it the same version; which is technically acceptable from a package management perspective.

@clydin the issue is reproducible after deleting yarn.lock and node_modules folders.

Can you provide your package.json?

I have attached it as downloadable file to the initial comment (please note the .txt extensions which needs to be removed).

Sorry.  Didn't see it there.
1.0 doesn't support TS 2.3.  You'll need to either wait for 1.1 (should be soon) or use the release candidate (1.1.0-rc.0).

Any news on this in 2018? I'm running into this issue when deploying with Jenkins, which does a yarn install and then ng build. Works locally, and can build with NPM, but that takes about 10 times as long to build as Yarn does, so I'd rather use yarn.

Are you still able to reproduce this issue with the latest CLI?

The issue does not occur with a recent version of Angular (CLI).
It was caused by the update instructions to Angular 4 suggesting to use typescript@latest, which at some point in time pointed to a version new than the one supported by Angular 4.

Thanks for the response!


Upgrade Kotlin to 1.9.20 and Ktlint to 1.0.1

This PR upgrades Kotlin to 1.9.20, and Ktlint to 1.0.1.
I had to abandon the pretty-format-kotlin pre-commit hook since it was ignoring our .editorconfig, which made it impossible to suppress some of the newer lints that would be difficult and undesirable to fix. Now all Ktlint runs go through gradle, so there isn't any way for inconsistencies to creep in.
 When reviewing the Ktlint formatting changes, be sure to hide whitespace changes to reduce how much needs to be examined.

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

This is a repost of https://github.com/smithy-lang/smithy-rs/pull/3301 merging into the correct branch.


PIM-897 adding jwt functionality

The process that I am implementing here is to create a class that fetches the session id for you by passing in a connected app id and username. Then you can pass the session id onto the connection class and continue your normal process.

Does this mean we have to add connect app for every org? Or we ship the private key with pkg?

Great questions I am in the middle of documenting all the steps, and the short answer is yes we will deploy a connected app to every org. and no we are not shipping with the private key.
Salesforce is really giving bad advice to ship with the private key in a metadata config object, for two reasons.

your private key would be checked into source code
you have to send your private key over the internet to the heroku code that is calling back to salesforce.

We are implementing a key management system, but for now we are going to use Env Variables on Heroku. I will have a full implementation and documentation in a few days.


PagerTree not mapped loaders.py

Setting up pagertree alerts today, I was getting an error:
Nov 18 20:57:04 dashboards elastalert[8878]: elastalert.util.EAException: Error initiating alert ['pagertree']: Could not import module pagertree: not enough values to unpack (expected 2, got 1) Nov 18 20:57:04 dashboards elastalert[8878]: During handling of the above exception, another exception occurred: Nov 18 20:57:04 dashboards elastalert[8878]: Traceback (most recent call last): Nov 18 20:57:04 dashboards elastalert[8878]:   File "/usr/local/bin/elastalert", line 11, in <module> Nov 18 20:57:04 dashboards elastalert[8878]:     load_entry_point('elastalert==0.2.1', 'console_scripts', 'elastalert')() Nov 18 20:57:04 dashboards elastalert[8878]:   File "/usr/local/lib/python3.6/dist-packages/elastalert-0.2.1-py3.6.egg/elastalert/elastalert.py", line 2050, in main Nov 18 20:57:04 dashboards elastalert[8878]:     client = ElastAlerter(args) Nov 18 20:57:04 dashboards elastalert[8878]:   File "/usr/local/lib/python3.6/dist-packages/elastalert-0.2.1-py3.6.egg/elastalert/elastalert.py", line 140, in __init__ Nov 18 20:57:04 dashboards elastalert[8878]:     self.rules = self.rules_loader.load(self.conf, self.args) Nov 18 20:57:04 dashboards elastalert[8878]:   File "/usr/local/lib/python3.6/dist-packages/elastalert-0.2.1-py3.6.egg/elastalert/loaders.py", line 125, in load Nov 18 20:57:04 dashboards elastalert[8878]:     raise EAException('Error loading file %s: %s' % (rule_file, e)) Nov 18 20:57:04 dashboards elastalert[8878]: elastalert.util.EAException: Error loading file /opt/elastalert/rules/heartbeat-monitor-down.yaml: Error initiating alert ['pagertree']: Could not import module pagertree: not enough values to unpack (expected 2, got 1)
I had to modify the loaders.py file adding the pagertree loader:
        'pagertree': alerts.PagerTreeAlerter,
Once re-running setup.py and restarting elastalert all was then well.

elastalert2 solved this problem
https://github.com/jertel/elastalert2


an export problem ,store('xls') and download('xls') have different output

when i export a excel file , i use store('xls') and download('xls') , but the file downloaded was like this
"䄀Laravel ExcelUnknown CreatorUnknown Creator@娺Bс@娺Bс	"  ,

the file stored on the server is just the right export like this "10002	BBBBB	92" , here is my code
        $cellData = [
            ['number','name','score'],
            ['10001','AAAAA','99'],
            ['10002','BBBBB','92'],
            ['10003','CCCCC','95'],
            ['10004','DDDDD','89'],
            ['10005','EEEEE','96'],
        ];
        $excel->create('Laravel Excel', function($excel)use($cellData) {

            $excel->sheet('Excel sheet', function($sheet)use ($cellData) {
                $sheet->rows($cellData);
            });

        })->store('xls')->download('xls');

someone help？thank you...

+1 I'm having the same issue

I can store the file and open it directly but it I download or export anything other than CSV excel cannot open the file

I have already solved the problem, in the output before you flush the output buffer, use
ob_clead () or ob_end_clean ()

hope this can help you

It sure did, thanks dude


Rails 3.1 compatible branch doesn't work w/o Asset Pipeline

Please fix the Rails 3.1 compatible branch and release a version 3.1.6.
Thanks!

It's also possible to fake the asset pipeline for the benefit of sass-rails: http://bettong.net/2012/03/07/using-sass-rails-3-dot-1-5-without-the-asset-pipeline-on-rails-3-dot-1-4/


Hydrated?

What exactly is a "fully hydrated repo"?  There is no such thing in Git terminology.
Please use proper terminology in the Readme and elsewhere.

There is no such thing in Git terminology because Git itself doesn't have the concept of getting a partial repository that still functions as a full copy. Hydration implies that the file's contents are available locally, while most files are simulated as being there, and only files where the contents are needed to perform the actions become "hydrated".

To hydrate generally means to fill something with contents. In GVFS, what we mean is that when you first enumerate a directory, what you see in the listing looks like normal files, but they don't have any contents in them. When you open a file for the first time, we go and download its contents and hydrate the file on disk so that from then on, it's a normal file with full contents.

If you want to say "git and tools see a fully functioning repo" in the Readme's second sentence, then just do so.


Completion - receiver not completing correctly

Not sure if this should be a reopen of #200
type Foo struct {
a float
b int
}
func (f *Foo) Init() {
f.<correct completions missing and some that shouldn't be there are appearing>
}

yes that would be -- can you provide specific example -- and also double-check that you fully updated (pi too!) as that should be fixed.. :)

hmmm, one particular file is giving me the problem. I'll see if I can figure why. pi was updated.

I changed the name of the struct and that resolved the issue. Must be defined somewhere else as well. Sorry for the false alarm.


Extract canvas logic in top level layout

The components folder is starting to become unwieldy, so far we've treated the "application editor" as just another component. It's not meant for reuse. I'm proposing to extract this into its own top level folder, which can be more seen as entry-points into the application
Aiming towards a better top-level project layout. I propose:

./server: all server only code (OK)
./runtime: toolpad application runtime (OK)
./canvas: application runtime with overrides, used inside the editor (this PR)
./toolpad: Editor application (currently interleaved with ./components)
./components: shared components (currently contains Toolpad editor as well)
./utils: shared generic utility functions, do not put toolpad specific functionality in here (OK)
./toolpadDatasources: available datasources
./: toolpad specific libraries, we will let this folder grow until it becomes unwieldy and needs organization

sounds good, maybe the toolpad folder could be editor

My only objection would be that it is more than just the application editor, it also houses the application overview, application management, (future) user management, the release process

and toolpadDatasources could be just datasources?

👍


[ECS] Breakage after updating from 8.2.1 to 8.2.2

Hi Tomáš,
We're seeing breakage show up on our project after updating to 8.2.2.. If I have "symplify/easy-coding-standard": "8.2.1" fixed in composer.json, i get this:
$ ./vendor/bin/ecs check

 [OK] No errors found. Great job - your code is shiny in style!

Then, updating to 8.2.2, we get this:
$ composer require --dev symplify/easy-coding-standard ^8.2
./composer.json has been updated
Loading composer repositories with package information
Updating dependencies (including require-dev)
Restricting packages listed in "symfony/symfony" to "^4.4 | ^5.1"
Package operations: 0 installs, 1 update, 0 removals
  - Updating symplify/easy-coding-standard (v8.2.1 => v8.2.2): Loading from cache
…
Executing script cache:clear --no-warmup [OK]
Executing script assets:install --symlink --relative public [OK]

> php bin/console bolt:info

 Bolt version: 4.0.0 RC 34

 * Install type: Git clone
 * Database: mysql 5.7.26 - <IP_ADDRESS> via TCP/IP (with JSON)
 * PHP version: 7.2.26
 * Symfony version: v5.1.3
 * Operating System: Darwin - 19.5.0

Nothing to unpack

$ ./vendor/bin/ecs check

PHP Fatal error:  Uncaught Symfony\Component\OptionsResolver\Exception\UndefinedOptionsException: The option "functions" does not exist. Defined options are: "exclude", "include", "scope", "strict". in /xxx/vendor/symfony/options-resolver/OptionsResolver.php:871
Stack trace:
#0 /xxx/vendor/friendsofphp/php-cs-fixer/src/FixerConfiguration/FixerConfigurationResolver.php(107): Symfony\Component\OptionsResolver\OptionsResolver->resolve(Array)
#1 /xxx/vendor/friendsofphp/php-cs-fixer/src/AbstractFixer.php(156): PhpCsFixer\FixerConfiguration\FixerConfigurationResolver->resolve(Array)
#2 /xxx/vendor/friendsofphp/php-cs-fixer/src/Fixer/FunctionNotation/NativeFunctionInvocationFixer.php(63): PhpCsFixer\AbstractFixer->configure(Array)
#3 /private/var/folders/8m/bhw0z8ds0_3390t47stvdg680000gn/T/easy_coding_standard/ContainerYZwjIJk/getFixerFileProcessorService.php(103): PhpCsFixer\Fixer\FunctionNotation\NativeFunctionInvocationFixe in /xxx/vendor/friendsofphp/php-cs-fixer/src/AbstractFixer.php on line 170

Is this a mistake on our end, or did a bug sneak in?
Thanks!

Hi,
upgrade ecs.yml to ecs.php. Let me know if there are some troubles afterwards.
Here is how: https://tomasvotruba.com/blog/2020/07/27/how-to-switch-from-yaml-xml-configs-to-php-today-with-migrify/

Ah, posibly related: https://github.com/symplify/symplify/pull/2057

Actually, you helped converting it to .php a few weeks ago. ;-)
https://github.com/bolt/core/blob/master/ecs.php
I'll try the suggestion in #2057 in the morning!

I can confirm #2057 does indeed fix this problem. Thank you, closing this issue! :-)


vagrant provision fails on Windows servers using winrm communicator when using --provider=managed

I'm piloting vagrant-managed-servers for some of our deployment use cases. It works fantastically for linux servers (thanks!), but I've found at least one issue when running vagrant provision against a Windows 2008 R2 server using the winrm communicator. To be clear, this "guest" machine was not provisioned using Vagrant and was created by our IT team and is running on a VMWare ESX host using VMWare tools. I'm running vagrant from terminal on Mac OSX 10.9.5.
This may not be the primary use case that vagrant-managed-servers was built for, but I think I'm close and have an interest in getting this to work, so I'd be happy to help if you can give me some direction.
Vagrantfile
# -*- mode: ruby -*-
# vi: set ft=ruby :

Vagrant.configure("2") do |config|

  config.vm.provision "shell", inline: "get-childitem C:\\"
  config.vm.box = "tknerr/managed-server-dummy"

  instances = ['myserver.mydomain.com']

  instances.each do |instance|
    config.vm.define "#{instance}" do |box|
      box.vm.communicator = :winrm
      box.winrm.username = "vagrant"
      box.winrm.password = "vagrant"
      box.vm.provider :managed do |managed, override|
        managed.server = instance
      end
    end
  end

end

The up, status and destroy commands appear to work well, and when I run them with the --debug command line option, I am able to verify that they are connecting and communicating over winrm (not ssh).
When I run the vagrant provision command, I am prompted for the ssh user's password (I had installed cygwin/openssh on the machine as an alternate approach, but I'd ideally like to get to a winrm only solution.
Output
> vagrant provision

==> mymachine.mydomain.com: high-level network configurations (`config.vm.network`). They
==> mymachine.mydomain.com: will be silently ignored.
==> mymachine.mydomain.com: Warning! The ManagedServers provider doesn't support any of the Vagrant
==> mymachine.mydomain.com: high-level network configurations (`config.vm.network`). They
==> mymachine.mydomain.com: will be silently ignored.
 INFO warden: Calling IN action: #<Vagrant::Action::Builtin::Call:0x00000102504f08>
 INFO runner: Preparing hooks for middleware sequence...
 INFO runner: 1 hooks defined.
 INFO runner: Running action: #<Vagrant::Action::Builder:0x000001009795e0>
 INFO warden: Calling IN action: #<VagrantPlugins::ManagedServers::Action::IsReachable:0x000001009804f8>
 INFO winrm: Checking whether WinRM is ready...
DEBUG provider: Searching for cap: winrm_info
DEBUG provider: Checking in: managed
DEBUG winrmshell: initializing WinRMShell
DEBUG winrmshell: powershell executing:
hostname
if ($?) { exit 0 } else { if($LASTEXITCODE) { exit $LASTEXITCODE } else { exit 1 } }
 INFO winrmshell: Attempting to connect to WinRM...
 INFO winrmshell:   - Host: mymachine.mydomain.com
 INFO winrmshell:   - Port: 5985
 INFO winrmshell:   - Username: vagrant
DEBUG winrmshell: Output: {:data=>[{:stdout=>"mymachine\r\n"}], :exitcode=>0}
 INFO winrm: WinRM is ready!
 INFO warden: Calling OUT action: #<VagrantPlugins::ManagedServers::Action::IsReachable:0x000001009804f8>
 INFO runner: Preparing hooks for middleware sequence...
 INFO runner: 1 hooks defined.
 INFO runner: Running action: #<Vagrant::Action::Warden:0x00000105333618>
 INFO warden: Calling IN action: #<Proc:0x000001053fafb0@/Applications/Vagrant/embedded/gems/gems/vagrant-1.6.4/lib/vagrant/action/warden.rb:94 (lambda)>
 INFO warden: Calling IN action: #<Vagrant::Action::Builtin::Provision:0x000001053335a0>
 INFO provision: Ignoring sentinel check, forcing provision
 INFO provision: Checking provisioner sentinel file...
 INFO provision: Sentinel found! Not provisioning.
 INFO warden: Calling IN action: #<VagrantPlugins::ManagedServers::Action::SyncFolders:0x0000010536a0a0>
 INFO warden: Calling IN action: #<Proc:0x000001053bb518@/Applications/Vagrant/embedded/gems/gems/vagrant-1.6.4/lib/vagrant/action/warden.rb:94 (lambda)>
 INFO warden: Calling OUT action: #<Proc:0x000001053bb518@/Applications/Vagrant/embedded/gems/gems/vagrant-1.6.4/lib/vagrant/action/warden.rb:94 (lambda)>
 INFO interface: info: Rsyncing folder: /Users/cbaldauf/dev/cbaldauf/vagrant-managed-servers/ => /vagrant
 INFO interface: info: ==> mymachine.mydomain.com: Rsyncing folder: /Users/cbaldauf/dev/cbaldauf/vagrant-managed-servers/ => /vagrant
==> mymachine.mydomain.com: Rsyncing folder: /Users/cbaldauf/dev/cbaldauf/vagrant-managed-servers/ => /vagrant
DEBUG winrmshell: powershell executing:
mkdir '/vagrant' -force
if ($?) { exit 0 } else { if($LASTEXITCODE) { exit $LASTEXITCODE } else { exit 1 } }
DEBUG winrmshell: Output: {:data=>[{:stdout=>"\r\n"}, {:stdout=>"\r\n"}, {:stdout=>"    Directory: C:\\\r\n\r\n\r\nMode                LastWriteTime     Length Name                              \r\n----                -------------     ------ ----                              \r\nd----         11/4/2014   1:00 PM            vagrant                           \r\n"}], :exitcode=>0}
 INFO subprocess: Starting process: ["/usr/bin/rsync", "--verbose", "--archive", "-z", "--exclude", ".vagrant/", "--exclude", "Vagrantfile", "-e", "ssh -p 22 -o StrictHostKeyChecking=no -i '/Users/cbaldauf/.vagrant.d/insecure_private_key'  ", "/Users/cbaldauf/dev/cbaldauf/vagrant-managed-servers/", "vagrant@mymachine.mydomain.com:/vagrant"]
DEBUG subprocess: Command not in installer, not touching env vars.
DEBUG subprocess: Selecting on IO
DEBUG subprocess: stderr:
                            ****USAGE WARNING****

This is a private computer system. This computer system, including all
related equipment, networks, and network devices (specifically including
Internet access) are provided only for authorized use. This computer system
may be monitored for all lawful purposes, including to ensure that its use
is authorized, for management of the system, to facilitate protection against
unauthorized access, and to verify security procedures, survivability, and
operational security. Monitoring includes active attacks by authorized entities
to test or verify the security of this system. During monitoring, information
may be examined, recorded, copied and used for authorized purposes. All
information, including personal information, placed or sent over this system
may be monitored.

Use of this computer system, authorized or unauthorized, constitutes consent
to monitoring of this system. Unauthorized use may subject you to criminal
prosecution. Evidence of unauthorized use collected during monitoring may be
used for administrative, criminal, or other adverse action. Use of this system
constitutes consent to monitoring for these purposes.

<EMAIL_ADDRESS>password:

At this point, it feels like a dead end to me, since I'd strongly prefer to communicate over a single protocol (ssh or winrm and I'm favoring winrm given the additional support that it has been getting lately).
Within my local copy of the vagrant-managed-servers gem, I was able to add a patch and get it to run the actual provisioning step successfully.
/action/sync_folder.rb
module VagrantPlugins
  module ManagedServers
    module Action
      # This middleware uses `rsync` to sync the folders over to the
      # AWS instance.
      class SyncFolders
        include Vagrant::Util::ScopedHashOverride

        def initialize(app, env)
          @app    = app
          @logger = Log4r::Logger.new("vagrant_managed_servers::action::sync_folders")
        end

        def call(env)
+          return
          @app.call(env)

          ssh_info = env[:machine].ssh_info

Output (no debug)
> vagrant provision
==> mymachine.mydomain.com: Warning! The ManagedServers provider doesn't support any of the Vagrant
==> mymachine.mydomain.com: high-level network configurations (`config.vm.network`). They
==> mymachine.mydomain.com: will be silently ignored.
==> mymachine.mydomain.com: Running provisioner: shell...
    mymachine.mydomain.com: Running: inline PowerShell script
==> mymachine.mydomain.com:     Directory: C:\
==> mymachine.mydomain.com:
==> mymachine.mydomain.com:
==> mymachine.mydomain.com: Mode                LastWriteTime     Length Name
==> mymachine.mydomain.com: ----                -------------     ------ ----
==> mymachine.mydomain.com: d----         7/13/2009  11:20 PM            PerfLogs
==> mymachine.mydomain.com: d-r--         11/4/2014   4:47 PM            Program Files
==> mymachine.mydomain.com: d-r--         3/29/2011   4:50 PM            Program Files (x86)
==> mymachine.mydomain.com: d----         11/5/2014  12:24 PM            temp
==> mymachine.mydomain.com: d----         11/5/2014  12:24 PM            tmp
==> mymachine.mydomain.com: d-r--         11/4/2014   4:41 PM            Users
==> mymachine.mydomain.com: d----         11/4/2014   1:00 PM            vagrant
==> mymachine.mydomain.com: d----        10/29/2014  12:03 PM            Windows

This obviously isn't a proper solution, but it allowed me to prove to myself that I was able to use winrm for end-to-end provisioning, although my prototype only uses an inline powershell script - I may want/need the files to be synced to the remote machine to do any sort of real provisioning. I saw that there was an open ticket related to using the built in vagrant rsync functionality (https://github.com/tknerr/vagrant-managed-servers/issues/17).
I'd like to get your thoughts on this and perhaps some guidance on how you recommend I proceed. Again, I'm willing to put some time and effort into a solution that I can submit back, but appreciate your recommendation on the best approach.

Do you guys have a README for how to get both the Windows guest and the non-Windows host (here Mac) properly configured so that "vagrant provision" can work with a Windows guest. In my case, I use chocolately on the guest to bring in Bitvise SSHd and vagrant-winrm-config. "vagrant ssh" works fine now. I tried throwing in cwRsync but the Mac rsync and the cwRsync don't agree to talk. Of course, I'd just like the known good configuration of Windows apps and vagrant settings that would allow this setup issue to go away.

@lonniev, can you post the contents of your Vagrantfile? Maybe in a gist? I've been regularly spinning up and connecting to Windows machines from my Mac, so I'd be happy to take a look.

Turns out it is a known issue in vagrant pre-1.7.3 about rsync and its inability (or decision) not to pre-create a nested directory structure. Rsynch is complaining that the destination directory for /tmp/vagrant-chef-#/ does not exist.
I borrowed some veewee and packer box-configuration scripts to come up with https://gist.github.com/lonniev/350a444c626119c31208 to get the Softlayer instance into a vagrant-talkative mood.
This all works except that the rsync/vagrant issue of pre-1.7.3 remains.

I think I could probably swap out the cygwin ssh and rsync for the BitVise/cwRsync that I started with in the gist script and get right back to the same rsync issue. So, I will wait for 1.7.3.

Is there a reason that you're not using the winrm communicator for Windows?
http://docs.vagrantup.com/v2/vagrantfile/winrm_settings.html
http://www.vagrantup.com/blog/feature-preview-vagrant-1-6-windows.html

The communicator for vagrant is set to winrm and the post install provisioning script does enable winrm and vagrant --debug does show that winrm is there and open.
The need is, apparently, for rsync and ssh to share local host directories with the guest OS to support the chef-solo provisioner. I would set the sync folder type to nfs or smb if the host/guest pair supported either. They don't.

Ah, now I better understand. Yes, SMB host support on mac has been on my todo list for a while now - I just haven't gotten to it yet. What I've been doing as a workaround with winrm is to abandon the puppet provisioner (we use puppet, not chef), and just craft the appropriate puppet apply --modulepath c:\vagrant\puppet\modules c:\vagrant\puppet\manifests\default.pp <extra_args> command in a shell provisioner.
Again, not ideal, but it has been working for us for the time being.

Likewise, I comment out the chef-solo provisioner and manually choco-up the instance. Hopefully, one day, we'll all have a configuration that truly/fully supports Unixy hosts and Windows guests.

just FYI as I expect vagrant 1.7.3 to fix this (and offer World Peace):
Host path: /Users/lonniev/Vagrants/softlayer-windows-integrity/cookbooks/
Guest path: /tmp/vagrant-chef/3c82aaf2d4fcab5d6e99f607c734158c/cookbooks
Command: rsync --verbose --archive --delete -z --copy-links --no-owner --no-group -e ssh -p 22 -o StrictHostKeyChecking=no -o UserKnownHostsFile=/dev/null -i '/Users/lonniev/.vagrant.d/insecure_private_key' --exclude .vagrant/ /Users/lonniev/Vagrants/softlayer-windows-integrity/cookbooks/ vagrant@<IP_ADDRESS>:/tmp/vagrant-chef/3c82aaf2d4fcab5d6e99f607c734158c/cookbooks
Error: Warning: Permanently added '<IP_ADDRESS>' (RSA) to the list of known hosts.
rsync: mkdir "/tmp/vagrant-chef/3c82aaf2d4fcab5d6e99f607c734158c/cookbooks" failed: No such file or directory (2)
rsync error: error in file IO (code 11) at main.c(674) [Receiver=3.1.0]

It is the no such file or directory on the guest that is the problem.

Thanks @chrisbaldauf for jumping in, I couldn't have helped with this!
@lonniev just curious as you mentioned softlayer (and that will probably not solve your problem), but did you try out https://github.com/audiolize/vagrant-softlayer? I did not, but would be interested in whether it's usable or not...

@tknerr For SoftLayer images, I have crafted a custom post_install script to make a base SL Windows image communicative with vagrant.
The post installer installer is here:
https://gist.github.com/lonniev/7d967b09add6ca1f3a8a

Thanks @lonniev, that is super useful!

The problem with rsync is that it elects by design not to create missing parent directories in the path to the destination folder.
I could pre-create the complete path if I knew it a priori but it is constructed in the chef ruby code as it is needed. Therefore, with /tmp/vagrant-chef/3c82aaf2d4fcab5d6e99f607c734158c/cookbooks, I don't have the magic hash value 3c82... beforehand.

Returning to this after several months, still in need of a solution, I looked at the vagrant source code to learn a bit. I see that for Linux guests there is an rsync.rb Cap class that performs the crucial "sudo mkdir -p #{opts[:guest_path]}" operation for rsync. That "guest path" parameter is the pathname that I thought (back on April 21st) was unavailable to me.
There is no similar Cap file for Windows guests.
I will try "monkey patching" my vagrant installation (1.7.2) to see if I can wedge in this missing capability for Windows guests.
If someone knows a better way to accomplish this goal, just reply here.

Evidently, the addition of the rsync_pre is absolutely the way this kind of issue is intended to be addressed: for, in fact, that is exactly what @mitchellh has done for the future vagrant 1.7.3. See his commit 56a6c85e7df482c922910c941c2dda7bfd1250c8 for the addition to latest vagrant.

I found out that the setup for vagrant and chef on the target guest box was not completely correct: it had the TEMP environment variable set to c:\Windows\TEMP and a PATH file therein with that path stated. However, the chef provisioning rsyncs were attempting to copy into c:\tmp folders.
The quickest way to resolve these two paths to temporary folders was to delete c:\tmp and create a symlink of c:\tmp ontp c:\Windows\TEMP. Now, regardless of whether the code uses the environment variable, the PATH file clue, the explicit c:\Windows\TEMP path, the explicit c:\tmp path, or the implicit cygwin /tmp path, all paths lead to the same folder.

@lonniev nice find! Sorry I can't help you much further with that... :-/


Character Portraits with varying expressions for cutscenes/dialogue

To introduce the story and bring up mono/dialogue, could i draw & add character portraits of the MC with different expressions?

I like this idea! Great way to display expositional content and a great way to better show off the characters.
I'd like to put this on the Trello board, but I might need more specific details on what exactly would be need to be made for this feature to work.
How many character portraits/expressions were you thinking about making? Would this include art for the dialogue box?

I was thinking about making 5 expressions (tired(default), determined, weary, surprised, fired up) but I'm open to drawing more if need be.
maq was interested in helping out with this so art for the dialogue boxes would be included

Ok that sounds great! I'll add these expression and the dialogue box to the trello board and mark the tasks as claimed.


Docs: Mention that JSON parsing middleware is needed

I had to find out the hard way...

I second this.  Took me about an hour to come and see this issue.

We're very sorry about that. I'll update the docs. To confirm, you are talking about the JSON-quoted query parser?

I'm not sure exactly what you mean here.  I was having trouble saving objects from backbone to backbone-rest (with backbone-sql).  When an object was posted it would only return the id field (https://gist.github.com/jotham/d85591ed445a4f7910ef)  Once I changed the express program to use a json parser it resolved the issue. i.e:
var bodyParser = require('body-parser');

...

   app.use(bodyParser.json();

@jotham thanks for clarifying what the problem was.
I assumed that needing a json body parser for express would be self-evident, but obviously not! (I think the query parsing middleware might be less so)
I'll add this to the docs here: http://vidigami.github.io/backbone-orm/backbone-rest.html   Is that where you would expect them to be?

I think that would be great

Done: http://vidigami.github.io/backbone-orm/backbone-rest.html


Refactor NetworkController to BaseControllerV2

NetworkController update to extend from BaseControllerV2
swaps out the base controller, implements messenger, fixes all the tests associated
Description

BREAKING:

NetworkController constructor now takes a ControllerMessenger
subscriptions should be made on the messenger, not the controller
listen for providerChange if you want to receive updates once lookupNetwork has completed

CHANGED:

NetworkController uses BaseControllerV2

Checklist

[x] Tests are included if applicable
[x] Any added code is fully documented

Issue
#902

Looked through again and this looks good pending the changes mentioned above.


build(ingest/airflow): Pinning setuptools to fix click-default-group build issue

click-default-group setup fails with the latest setuptools:
error: Failed to download and build `click-default-group==1.2.2`
  Caused by: Failed to build: `click-default-group==1.2.2`
  Caused by: Build backend failed to determine extra requires with `build_wheel()` with exit status: 1

See details here:
https://stackoverflow.com/questions/78806100/no-module-named-setuptools-command-test## Checklist

[ ] The PR conforms to DataHub's Contributing Guideline (particularly Commit Message Format)
[ ] Links to related issues (if applicable)
[ ] Tests for the changes have been added/updated (if applicable)
[ ] Docs related to the changes have been added/updated (if applicable). If a new feature has been added a Usage Guide has been added for the same.
[ ] For any breaking change/potential downtime/deprecation/big changes an entry has been made in Updating DataHub

Summary by CodeRabbit

New Features

Updated package version constraints for setuptools to improve compatibility and avoid potential issues with newer versions.

Bug Fixes

Adjusted requirements to ensure compatibility with the click-default-group package, enhancing stability during installation.

Don't think this is necessary anymore?


Copay is a SCAM

Lost 700 US$ in fees and lost transactions for a balance of 1500 $. I DONT RECOMMEND IT

This the similar issue with me as well

Please check: #7546 (comment)

@iv4n0ff
I can recover your wallet if you want need help send me email<EMAIL_ADDRESS>


Want to add feedback option

Feedback is very important nowadays for Ecommerce. So, I want to add that feature in your website.
Please assign this task to me under gssoc-ext and hacktober.

Go ahead


introduce idris2 node

Thanks!

Please consider adding brief descriptions to you projects' .ipkg files: brief = "My fancy library". These will then be listed in the list of available packages here. Feel free to do this whenever you want to. The descriptions will be picked up when the next nightly is being built.


Make normal output less verbose

During a normal run of svgo it outputs something like
/some/directory:

this.svg:
Done in 22 ms!
6.078 KiB - 23.8% = 4.631 KiB

that.svg:
Done in 7 ms!
6.091 KiB - 26.3% = 4.487 KiB

During a normal build that output really is not needed, only when I want to now more verbose what is going on.
Enhancement idea: Introduce a --verbose option and do the output above only if the option is given. Errors should of course always be output, regardless of the flag.

There was a --quiet option was added in #445.


Using the icons search box while an icon is selected crashes the application

Which version of the app?
WinUI 3 Gallery
Description
In version <IP_ADDRESS>, the DesignGuidance/ItemsPage.xaml contains an ItemsView named "IconsItemsView". Selecting one of the icons in the list and then using the search bar in any way crashes the application.
I have observed this issue when installing from the Microsoft Store on multiple devices, but have been unable to recreate with a debugger attached when compiling from source.
Screenshots
No response
Windows version
Windows 11 23H2 (22631)
Additional context
No response

Resolving as dupe of #1500


Overloading of comparison operator for pauli operator class.

This allows for direct comparison of pauli operators and is much faster than conversion to text as used previously.
Description
in qiskit.tools.qi.pauli I added the two overloading operators to the Pauli class for == and !=
in qiskit.tools.apps.fermion I changed the textual comparison that was used to a direct one
Motivation and Context
Some code in the chemistry examples uses a comparison 'if pauli1.to_label() == pauli2.to_label().'
With the proposed change the comparison is just 'if pauli1 == pauli2'. The direct comparison is 15x faster than the conversion to strings and thus significantly speeds up several codes.
How Has This Been Tested?
pa = Pauli([0,0,1,1,1],[1,0,1,0,0])
pb = Pauli([0,0,1,1,1],[1,0,1,0,0])
pc = Pauli([0,0,1,1,1],[1,0,1,0,1])
if pa == pb:
print('the first two are equal')
if pa != pc:
print('the second two are not equal')
and I tested it on a new version of QChem Notebook which gave a 15x improvement when generating the Paulis for larger molecules.
Types of changes

[x] Bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)

Checklist:

[x] My code follows the code style of this project.
[x] My change requires a change to the documentation.
[ ] I have updated the documentation accordingly.
[x] I have read the CONTRIBUTING document.
[ ] I have added tests to cover my changes.
[ ] All new and existing tests passed.

This change seems to break the function group_paulis in qiskit.tools.apps.optimization.

Thanks, @afu1 !

This change seems to break the function group_paulis in qiskit.tools.apps.optimization.

Could you provide more information about the breaking (ideally, including a code sample in your reply)?

It doesn't break anything in my case adding the comparison. To compare the arrays, on should use the function np.all(). The code would look like this:
def __eq__(self, other):
    """Return True if all Pauli terms are equal."""
    bres = False
    if self.numberofqubits == other.numberofqubits:
        if np.all(self.v == other.v) and np.all(self.w == other.w):
                bres = True
    return bres

I had an incompatible version of qiskit.tools.apps.optimization in my environment. I agree with @nikomoll that the change is compatible with the correct unmodified version.  I removed the overloading for != as suggested since it does not seem to be needed. I also included the suggested change with np.all() and checked that it works.

Thanks for the quick turnaround (and @nikomoll  for the note about np.all()) - it's looking good!
Could you also add some tests:

one or two for the equality comparison (something similar to the excerpt in the "How Has This Been Tested?" section on the PR description)
one that executes group_paulis()

to the existing test.python.test_apps.TestPauli test case? It seems we are having a small surge in Pauli-related activity on the repository, and it would be awesome if we could take the chance to make the tests a bit more formal.

@diego-plan9 the testcase test.python.test_apps.TestPauli does not exist. I can put a test case in test.python.test_qi.TestPauli for the comparison. If you actually mean group_paulis() and not pauli_group() then that would go in test.python.test_apps.TestQuantumOptimization .

Sorry for the confusion, I intended to:

point to the existing test.python.test_qi.TestPauli case for the comparison test.
for the other test, I mentioned group_paulis() based on your earlier comment (even if it was later dismissed as an unrelated issue - just for safety) - and you are right that it would  be more consistent to add it to  test.python.test_apps.TestQuantumOptimization.

Thanks for catching it early!

I agree with @antoniomezzacapo but can we add tests for the comparison and multiplication before we merge.

I have added tests here https://github.com/QISKit/qiskit-sdk-py/pull/166

Thanks everyone for the reviews and the contributions!
For making managing the PRs a bit easier and preserving contributions, I  have included the tests on this PR, and rebased it against the current master - in practice, @afu1 , it has the side effect that your master branch has been force-push and modified. For collaborative pull requests such as this one where several people might be working on the same, it might be handy for the people involved to work on the same branch directly - please let us know if it would make sense or if any help is needed in that regard.
So everything is looking good, has been reviewed and approved, tests have been included, and working, so ... merging!


[ZEPPELIN-4031] Fixed Unable to detect that the interpreter process was killed manually

What is this PR for?
Zeppelin-server can't perceive, When a network exception occurs Or a state where a program exception causes the interpreter process to be unavailable, Cause the user to fail to perform the task all the time. You need to restart the interpreter process to get the user's interpreter back to normal, Cause a bad user experience.
By detecting the state of the remote interpreter process in Zeppelin server, When an interpreter process exception is found, By cleaning up the session of this interpreter, Let the interpreter regain its availability, Improves the user experience, It also reduces the operation and maintenance burden of the system.
What type of PR is it?
[Bug Fix]
What is the Jira issue?

https://issues.apache.org/jira/browse/ZEPPELIN-4031

How should this be tested?
RemoteInterpreterTest::testDetectIntpProcessKilled()

Screenshots (if appropriate)
Before bug fix

After bug fix

Questions:

Does the licenses files need update?
Is there breaking changes for older versions?
Does this needs documentation?

@zjffdu, @felixcheung , @jongyoul , Please help me review the code, Thanks!

This bug, It's not easy to get through the code review to understand the situation.
Better way, It is verified by testing.

ok thanks for explaining. im ok with this. IMO might be worthwhile to refactor the code to make it more straightforward perhaps?

No need to click the second time to execute successfully.  Restore the interpreter process immediately

CI Pass https://travis-ci.org/liuxunorg/zeppelin
@zjffdu , @felixcheung , Please help me review code.
In the second commit, I adjusted the way to recreate the invalid remote interpreter process. It is now very elegant to fix remote invalid interpreters, It can be used immediately without any manual intervention.
See the GIF effect: https://github.com/apache/zeppelin/pull/3342#issuecomment-477046336


[cryptopp] fix build by disabling assembly on osx

This port fails to build on osx (see #5953). The cmake files seem designed to test for the needed compiler support but it isn't working for some reason. This patch just disables all assembly on mac to get the port to build. Not tested on windows because I don't have access, but linux is still ok.

Thanks for the PR!


SAK-30863 change zh to zh-cn

change sakai11.x\reference\library\src\webapp\editor\ckextraplugins\autosave\lang\zh-cn.js

Hi @yushanyuan. Thanks for the contribution but it looks like this was already fixed in the upstream library here https://github.com/w8tcha/CKEditor-AutoSave-Plugin/commit/32af5d698df143da1e1bdea2b43e0efde096ebad  So I think I'm just going to pull in the updates from there to sync it up.

Also PR's should be made against the master rather than 11.x branch

On second thought, this is probably the easier fix right now for 11. I'd like to remove this code entirely and change this to a webjar but I don't want this holding up 11.


handle None-indexes

Summary:
In some pptx files (possible due to them being created on google slides and then exported to pptx) images do not have the idx set (as they're part of a layout?)
PR - Merge Checklist:
-- Verify:

[ ] ALL tests have passed
[ ] Code Review is done
[ ] Documentation updated or N/A
[ ] Dependencies satisfied

I see this is a duplicate of https://github.com/scanny/python-pptx/issues/190

@pterk I'm going to leave this one open if that's okay. This shows exactly how to fix it and I like the approach; I think it's the most sensible "compensation" for the invalid XML, it definitely won't make the XML any worse :) I'm going to try to get this into the next release, should have one going in sometime in the next couple weeks.

Definitely okay ;-) Thanks again for the nice software!

This is fixed in release v0.6.6.


Add support for normalized entry "full text content" ?

Typically rss feed provide "full text content" directly in their feed file, content:encoded or description in rss format, content or summary in atom format, etc.
So can feed-extractor try to add a normalized content property to entry item?
I know you have another package called article-extractor, but I don't want to do a manually html-parse if it already provides it's full "content". also some websites are not server-rendered thus can not be parsed correctly

@isunjn the reason that content is not included in the default result is because websites handle it inconsistently. Some websites provide this content, while others don't. The 4 default fields chosen are link, title, description and pubdate which have the highest stability, almost all feeds return them.
If you know exactly a website includes content in its feed data, you can use getExtraEntryFields() to get them into your extraction result.


Version 2.9.2 not working

Description
Trying to upgrade to<EMAIL_ADDRESS>Issue
My packager is complaining that ./NativeSerializer could not be found from Bugsnag.js.
Error: Unable to resolve module `./NativeSerializer` from `/<project-path>/node_modules/bugsnag-react-native/lib/Bugsnag.js`: The module `./NativeSerializer` could not be found from `/<project-path>/node_modules/bugsnag-react-native/lib/Bugsnag.js`. Indeed, none of these files exist:

Environment
Library versions:
──<EMAIL_ADDRESS>

I just found the issue - I believe.
In bugsnag-react-native/package.json:
"prepublish": "mkdir -p lib && babel src/Bugsnag.js -s -o lib/Bugsnag.js"
Should be
"prepublish": "mkdir -p lib && babel --source-maps --out-dir='lib' --ignore='__tests__' src",

The problem is already fixed on master: https://github.com/bugsnag/bugsnag-react-native/pull/227

Addressed in v2.9.3


hub_tools updates

Updates for hubtools
/assign @fzliu

Codecov Report

Merging #177 (33a1271) into main (b3d39dd) will decrease coverage by 0.34%.
The diff coverage is 0.00%.

:exclamation: Current head 33a1271 differs from pull request most recent head 6f1144b. Consider uploading reports for the commit 6f1144b to get more accurate results

@@            Coverage Diff             @@
##             main     #177      +/-   ##
==========================================
- Coverage   73.98%   73.64%   -0.35%
==========================================
  Files          92       92
  Lines        3460     3476      +16
  Branches      359      361       +2
==========================================
  Hits         2560     2560
- Misses        771      787      +16
  Partials      129      129

Impacted Files
Coverage Δ

towhee/utils/hub_tools.py
0.00% <0.00%> (ø)

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update b3d39dd...6f1144b. Read the comment docs.


[Bug]: MP4 files don't seem to save

What happened?
An MP4 file isn't created despite movie.start_capture() being in the movie.
What should have happened?
The MP4 file should be created.
UniTAS version
Latest master
UniTAS setup tool
None
BepInEx version
v5.3
Game name
Do It For Me
Game build
Windows x64 - Mono
How to reproduce
Replay this movie file and it shouldn't generate an MP4 file.
Log output
LogOutput.log
Additional context
Movie:
movie.zip
My game path is C:\Users\sawar\OneDrive\Documents\Do It For Me V1.0.1 - 64bit

Wait, FFMPEG doesn't seem to be found...

Yeah I guess I should state in the movie logger that ffmpeg is missing to avoid confusion
Also the output mp4 file size is 1KB?

Yep, output size is 1KB. Not sure why.

Still happens on the latest commit (https://github.com/Eddio0141/UniTAS/commit/4eb63aed4b52a6990f0c0a015152f7cb5cd732ca).

lmao see how it goes

Works fine now :D

nice! glad its fixed


Patching NPM vulnerabilities

Describe the bug
3 moderate severity vulnerabilities on npm packages, can verify through npm i. Checked via npm audit
Additional context
fixed via npm audit fix to update packages for semver, tough-cookie, word-wrap.

reviewed in discord. ran npm audit and npm audit fix to resolve package vulnerabilities to semver, tough-cookie, and word-wrap.


Please replace AFO:/process#AFP_0000112 mapping for DissolvingProcess in berkeley schema

AFO is a problematic ontology, both in terms of it's URI syntax and it's upper hierarchy
You will notice that it's not defined in nmdc.yaml's prefixes block
Is there any reason we can't use CHMO:0002773 ?

@turbomam  to double check and then close

this related issue has been closed https://github.com/microbiomedata/nmdc-schema/issues/1626 to resolve this open issue. can close.


Add unit tests for IdentityProcessor getCallbackPath method

We need to handle a few cases here
tenant qualified mode with absolute callback path

tenant qualified mode with relative callback path without /t/

tenant qualified mode with relative callback path with /t/ (already tenant qualified)

non-tenant qualified mode with absolute callback path

non-tenant qualified mode with relative callback path without /t/

non-tenant qualified mode with relative callback path with /t/ (already tenant qualified)

This issue is being closed due to extended inactivity. Please feel free to reopen it if further attention is needed. Thank you for helping us keep the issue list relevant and focused!


Added a new file python Program to get Fizz, Buzz and FizzBuzz

Python program which iterates the integers from 1 to 50. For multiples of three print "Fizz" instead of the number and for the multiples of five print "Buzz". For numbers which are multiples of both three and five print "FizzBuzz"

Thank you for your PR!
Unfortunately a solution similar to yours has already been submitted :/
The goal is to find creative/abstract new solutions to FizzBuzz.
Please consult the readme for more information and see The top 5 samples here.
Thanks anyway! :)


SW-2508 Clean up checkbox border radius styles

we were unable to use a border radius before using default mui checkbox
using additional enhancements to enable this
see Chudo's findings in the jira https://terraformation.atlassian.net/browse/SW-2508
the focus outline is still a question on how to do
feels like maybe the checkbox looks too big now
test in vercel

@hannah-cai let me know if you have any feedback.

thank you for the updates! the checkboxes look a lot more consistent with everything else now.
a small detail I noticed: the border cuts off the checkmark on the sides.

I would also prefer the checkbox to be smaller, but I know that Chudo was pushing for larger checkboxes for bigger click targets. that's something we can still explore though.
I'll leave @chudo76 to be the decider on what we do for focus states, since I'm not as familiar with them.
@karthikbtf a separate issue I noticed is that table rows have a hover state when they're selected and you hover over them. also, clicking on the row selects/de-selects the checkbox; the intended behavior was that you'd need to click on the checkbox itself. these may already be covered in Rachel's table updates, but I wanted to bring them up in case they weren't

thank you for the updates! the checkboxes look a lot more consistent with everything else now. a small detail I noticed: the border cuts off the checkmark on the sides.  I would also prefer the checkbox to be smaller, but I know that Chudo was pushing for larger checkboxes for bigger click targets. that's something we can still explore though. I'll leave @chudo76 to be the decider on what we do for focus states, since I'm not as familiar with them.
@karthikbtf a separate issue I noticed is that table rows have a hover state when they're selected and you hover over them. also, clicking on the row selects/de-selects the checkbox; the intended behavior was that you'd need to click on the checkbox itself. these may already be covered in Rachel's table updates, but I wanted to bring them up in case they weren't

Thanks @hannah-cai ! I will take a look.

thank you for the updates! the checkboxes look a lot more consistent with everything else now. a small detail I noticed: the border cuts off the checkmark on the sides.  I would also prefer the checkbox to be smaller, but I know that Chudo was pushing for larger checkboxes for bigger click targets. that's something we can still explore though. I'll leave @chudo76 to be the decider on what we do for focus states, since I'm not as familiar with them.
@karthikbtf a separate issue I noticed is that table rows have a hover state when they're selected and you hover over them. also, clicking on the row selects/de-selects the checkbox; the intended behavior was that you'd need to click on the checkbox itself. these may already be covered in Rachel's table updates, but I wanted to bring them up in case they weren't

Thanks @hannah-cai ! I will take a look.

Looks like adding overflow: visible; to the svg's CSS fixes the clipping issue.

Closing this since we're using other checkboxes now.


No way to build & deploy 'ui.apps' module separately

Expected Behaviour
According to docs:

Or to deploy only a single content package, run in the sub-module directory (i.e ui.apps)
mvn clean install -PautoInstallPackage

Should work to build & deploy only ui.apps module.
Actual Behaviour
Build fails.
Reproduce Scenario (including but not limited to)
Steps to Reproduce
Generate project from archetype 24, then run command:
cd ui.apps && mvn clean install -PautoInstallPackage
Logs taken while reproducing problem
[ERROR] ValidationViolation: "jackrabbit-filter: Filter root's ancestor '/apps/mysite' is not covered by any of the specified dependencies nor a valid root.", filePath=META-INF/vault/filter.xml
[INFO] ValidationViolation: "jackrabbit-filter: Ancestor node '/apps' is not covered by any of the filter rules but that node is a given root (either by a dependency or by the known roots). Remove that node!", filePath=jcr_root/apps/.content.xml
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time:  6.640 s
[INFO] Finished at: 2020-09-16T21:35:24+02:00
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal org.apache.jackrabbit:filevault-package-maven-plugin:1.1.4:validate-package (default-validate-package) on project mysite.ui.apps: Found 1 violation(s) (with severity=ERROR). Check above errors for details -> [Help 1]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions, please read the following articles:
[ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException
➜  ui.apps mvn clean install -PautoInstallPackage

I build and deploy ui.apps regularly without issue. Did you check the ui.apps.structure POM to make sure /apps and /apps/mysite are there?

I will recheck that. Please consider a case right after generating project from archetype.

ui.apps.structure must be build before


Async CustomCollector

So I need to obtain some metrics from a database and I'm planning to create a custom collector as described here: http://prometheus.github.io/client_python/collector/custom/
I use asyncpg to connect to PostgreSQL. My problem though is that asyncpg query needs to be called from an async function and collect() is synchronous.
Is there an async equivalent? It looks like the client supports being used from ASGI.

Not today, but adding async support for custom collectors would be a reasonable feature to add. I doubt I will have time to add it soon but would be happy to take a contribution.


Problems switching on 16-bit field header reductions

Following the instructions here:
https://github.com/svaarala/duktape/blob/master/doc/low-memory.rst
I changed my duk_config to the following:
#define DUK_USE_REFCOUNT16
#define DUK_USE_STRHASH16
#define DUK_USE_STRLEN16
#define DUK_USE_BUFLEN16
#define DUK_USE_OBJSIZES16
#undef DUK_USE_HSTRING_CLEN

Now when I try and compile, I get lots of and lots of compilation errors ... here are some examples:
CC src/duktape.o
duk_unicode_support.c: In function 'duk_unicode_case_convert_string':
duk_hstring.h:94:62: error: 'duk_heaphdr_string' has no member named 'h_strextra16'
duk_util.h:147:41: note: in definition of macro 'DUK_BW_INIT_PUSHBUF'
duk_unicode_support.c:1024:31: note: in expansion of macro 'DUK_HSTRING_GET_BYTELEN'
duk_hstring.h:94:62: error: 'duk_heaphdr_string' has no member named 'h_strextra16'
duk_unicode_support.c:1029:20: note: in expansion of macro 'DUK_HSTRING_GET_BYTELEN'
duk_api_bytecode.c: In function 'duk__dump_hstring_raw':
duk_hstring.h:94:62: error: 'duk_heaphdr_string' has no member named 'h_strextra16'
duk_api_bytecode.c:54:8: note: in expansion of macro 'DUK_HSTRING_GET_BYTELEN'
duk_api_bytecode.c: In function 'duk__dump_string_prop':
duk_hstring.h:94:62: error: 'duk_heaphdr_string' has no member named 'h_strextra16'
duk_util.h:221:49: note: in definition of macro 'DUK_BW_ENSURE_RAW'
duk_api_bytecode.c:97:41: note: in expansion of macro 'DUK_HSTRING_GET_BYTELEN'
duk_hstring.h:94:62: error: 'duk_heaphdr_string' has no member named 'h_strextra16'
duk_util.h:223:55: note: in definition of macro 'DUK_BW_ENSURE_RAW'
duk_api_bytecode.c:97:41: note: in expansion of macro 'DUK_HSTRING_GET_BYTELEN'
duk_api_bytecode.c: In function 'duk__dump_varmap':
duk_hstring.h:94:62: error: 'duk_heaphdr_string' has no member named 'h_strextra16'
duk_util.h:221:49: note: in definition of macro 'DUK_BW_ENSURE_RAW'
duk_api_bytecode.c:171:43: note: in expansion of macro 'DUK_HSTRING_GET_BYTELEN'
duk_hstring.h:94:62: error: 'duk_heaphdr_string' has no member named 'h_strextra16'
duk_util.h:223:55: note: in definition of macro 'DUK_BW_ENSURE_RAW'
duk_api_bytecode.c:171:43: note: in expansion of macro 'DUK_HSTRING_GET_BYTELEN'
duk_api_bytecode.c: In function 'duk__dump_formals':

Some of the lowmemory options depend on one another but that set seems correct at a glance.
Could you double check that there isn't e.g. a #define and an #undef for any of the options? The cleanest way to enable/disable options would be via tools/configure.py but editing duk_config.h manually is also workable.

I double checked my configuration and believe that the settings are as stated ... just in case, I have attached the duk_config.h that I am using assuming (if you were like me), you'd want to see for yourself.   Screen sharing available on request.
duk_config_h.txt

It seems there's a bug in master with the 16-bit fields when reference counting is disabled. That h_strextra16 is assumed by duk_hstring but is incorrectly not present without reference counting.
For now, could you enable reference counting - I'll fix the incorrect assumption tomorrow.

There's currently no commit regression coverage for 16-bit fields + no refcounting: ajduk covers 16-bit fields but has refcounting enabled, while stripsize has no refcounting but 32-bit fields. I'll add that commit test  coverage at the same time.

Howdy ... thanks for the response.  Could you elaborate on "For now, could you enable reference counting" ... I don't know what that means.

Enable DUK_USE_REFERENCE_COUNTING and DUK_USE_DOUBLE_LINKED_HEAP.


Unify KeyCodec and ValueCodec traits into a single Codec

Originally posted by @bkolad in https://github.com/Sovereign-Labs/sov-db/pull/4#discussion_r1113469349

Actually, this change would make it impossible to blanket implement the storage traits for SDK types: https://github.com/Sovereign-Labs/sovereign/blob/research/sdk/src/node/db/slot_by_hash.rs#L24-L50
If we only have one trait, Rustc complains that it has duplicate implementations.


iPad not correctly detected on iOS 13 and 14

Version

Phaser Version: all versions including latest 3.50 - beta X

Operating system: iOS

Browser: Safari on iPad

Description
Since iOS 13 Apple changed user agent string on iPad devices to something like this:
Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_6) AppleWebKit/605.1.15 (KHTML, like Gecko) Version/13.1.2 Safari/605.1.15

So, device is recognized as macOS in https://github.com/photonstorm/phaser/blob/master/src/device/OS.js#L70 It means that app behaves like desktop (=true) app on iPad.
Workaround I found on internet is to check support for maxTouchPoints to make decision between macOS and iPad. Adjusting code like this worked for me:
    else if ((/Mac OS/).test(ua) && !((/like Mac OS/).test(ua)))
    {
        if (navigator.maxTouchPoints && navigator.maxTouchPoints > 2) {
            OS.iOS = true;
            OS.iPad = true;

            (navigator.appVersion).match(/Version\/(\d+)/);
            OS.iOSVersion = parseInt(RegExp.$1, 10);

        } else {
            OS.macOS = true;
        }
    }

Thank you for submitting this issue. We have fixed this and the fix has been pushed to the master branch. It will be part of the next release. If you get time to build and test it for yourself we would appreciate that.


Wallet settings as per new Design

design screenshot

dev app

Design Link
https://xd.adobe.com/view/f1543c84-c25a-4ad6-81ca-1e0c540e956e-a407/screen/d917dc94-f798-4e85-8ef3-111009cc6c35/

The transfer policy UI will be revamped in sprint 29. I have created an issue for this.
https://github.com/bithyve/bitcoin-keeper/issues/3965

CC: @antuz123

Verified this issue on keeper app v 1.2.0(319)


Thread pool

satisfy llvm thread pool dependency
add thread pool tests

Coverage increased (+0.5%) to 95.489% when pulling f00449e9feacf8ca709dfd5ef30ad98d2284eb2e on yangjuns:thread_pool into 10818ffb90891fe1a10f2a6959b4649f68d5327d on cmu-db:master.

The last run on Travis looks like it might have deadlocked (it timed out).

Yes. The bug is not fixed by this commit. I haven't pushed the corrected version because I need to fix some other stuff (API, design, documentation).

I'll also add that while I think this suffices for our use cases right now, we might want to look at Arrow's thread pool to see if there's anything we should incorporate.
https://github.com/apache/arrow/blob/master/cpp/src/arrow/util/thread-pool.h
https://github.com/apache/arrow/blob/master/cpp/src/arrow/util/thread-pool.cc
https://github.com/apache/arrow/blob/master/cpp/src/arrow/util/thread-pool-test.cc
The use of std::packaged_task and std::future is new to me, but might be worth looking into its intended uses.

After looking at the std::future and std::packaged_task stuff a bit more, I think those are the foundations for a more modern C++ thread pool. If the time comes to bolster the functionality of our thread pool implementation, we should look at Arrow's (linked previously).
In the meantime, if @lmwnshn can review this then this can go in.

Just started looking at this, sorry. I may try to add some tests and remove dead code if that's alright.


Fixing some grammatcal issues

Fixing some doc issues
@eyurtsev , @baskaryan

@baskaryan, I have resolved the conversation, Please have a look.
Thanks

@baskaryan , @eyurtsev Awaiting for your feedback :)

@baskaryan , @eyurtsev Awaiting for your feedback :)


Obsolete docs and asserts in DraggableScrollableSheet

DraggableScrollableSheet.dart contains quite a few lines of documentation and asserts that are no longer relevant since the file migrated to sound null safety. They should be removed to improve readability.

This is true of the whole codebase, but it's intentional. We still support non-null safe apps.


"APIs are independent" failed once on Travis

06 12 2018 14:43:15.267:ERROR [Chromium 62.0.3202 (Ubuntu 0.0.0) | Simple HiGlassComponent, Options tests | APIs are independent]: Expected false to equal true.
    at eval (webpack://%5Bname%5D/../test/APITests.js?:320:34)

Recording it here just to have a record in case we see it again.
Commit: a2c26d0

I believe there are some internal race conditions either with initializing HG or the test framework. I've seen it fail on CI a few times but never locally. Unfortunately I couldn't find out what the issue was as I wasn't able to reproduce it locally.


Story | App Walkthrough

This will not be a component exported from foundry, but rather a story within storybook to serve as an example of what can be done with it and provide sourcecode to achieve it.
This will require the completion of the Callout and StepProgress components. I would suggest using react-archer to add the arrows to the correct places.

This will be included in the #301 Spotlight component


bump: bump up dependencies for release-1.3 branch

This PR targets on release-1.3 branch.

Should this PR be a cherry-pick of #488

Should this PR be a cherry-pick of #488

It doesn't have to be a cherry pick. In the previous cherry pick, I got a conflict for the bump up.


rx.audio playing prop expects str instead of bool

Describe the bug
A clear and concise description of what the bug is.
rx.audio requires the playing prop to be bool as per documentation.
https://reflex.dev/docs/library/media/audio/
but yields an error expecting it to be str if you actually set a bool
 rx.audio(url=Button_State.url, playing=True, muted = True),
  File "/usr/local/lib/python3.10/dist-packages/reflex/components/component.py", line 447, in create
    return cls(children=children, **props)
  File "/usr/local/lib/python3.10/dist-packages/reflex/components/component.py", line 165, in __init__
    raise TypeError(
TypeError: Invalid var passed for prop playing, expected type <class 'str'>, got value True of type <class 'bool'>.

setting a str negates this issue but the playing prop does nothing

Good catch - this should be fixed by #1986 in the next release


Fixed url to Shopware 5.2.21 release notes

previous url led to a GitHub 404 page

Hey @vintagesucks, good catch, thank you :)


Windows default apps settings open when navigation to an email  website

This pops up when i use the browser and navigate to outlook or gmail

Can you please attach a code example?
I tested both gmail and outlook - for me everything works correctly both in headless and visible mode.

Can you please attach a code example?
I tested both gmail and outlook - for me everything works correctly both in headless and visible mode.

happens you get set as default permission popup for emails, you need to be logged in

@CheshireCaat

Usually happens when i move to fowarding section in outlook

like maybe when there is a popup that requests the website to set as the default mailing shortcut, same behvaviour with new gmail accounts

@CheshireCaat


Country (Turkey)

"Turkey country is missing. Can you add it?"

When you log into the app, it should open a website where you enter email / password. Can you copy that URL and post it here? Please remove any tokens, emails, etc. - I'm just interested in the part that looks like realms/vaillant-germany-b2c

Nevermind, figured it out. Will be in the next release.

Hi
realms/vaillant-turkiye-b2c
Thank you.

Can you test the latest pre-release please and let me know if it works? You need to enable beta versions in HACS to see it.

Yes ! Its work. Thank You 🥰

No problem, glad it works!