text:
kubectl panic on pod delete

Is this a request for help? (If yes, you should use our troubleshooting guide and community support channels, see http://kubernetes.io/docs/troubleshooting/.): No
What keywords did you search in Kubernetes issues before filing this one? (If you have found any duplicates, you should instead reply there.): panic, SIGSEGV

Is this a BUG REPORT or FEATURE REQUEST? (choose one): BUG REPORT ?

Kubernetes version (use kubectl version):

Client Version: version.Info{Major:"1", Minor:"9", GitVersion:"v1.9.2", GitCommit:"5fa2db2bd46ac79e5e00a4e6ed24191080aa463b", GitTreeState:"clean", BuildDate:"2018-01-18T21:12:46Z", GoVersion:"go1.9.2", Compiler:"gc", Platform:"darwin/amd64"}
Server Version: version.Info{Major:"1", Minor:"9", GitVersion:"v1.9.0", GitCommit:"925c127ec6b946659ad0fd596fa959be43f0cc05", GitTreeState:"clean", BuildDate:"2017-12-15T20:55:30Z", GoVersion:"go1.9.2", Compiler:"gc", Platform:"linux/amd64"}

Environment:

Cloud provider or hardware configuration: Minikube (minikube version: v0.24.1 (also seems to be same at v0.25.0)) ( --kubernetes-version v1.9.0 --bootstrapper kubeadm --vm-driver virtualbox  )
OS (e.g. from /etc/os-release): macOS High Sierra (Version 10.13.2)
Kernel (e.g. uname -a): Darwin A966.local 17.3.0 Darwin Kernel Version 17.3.0: Thu Nov  9 18:09:22 PST 2017; root:xnu-4570.31.3~1/RELEASE_X86_64 x86_64
Install tools: brew?
Others: Docker for mac running?

What happened:
panic: runtime error: invalid memory address or nil pointer dereference
[signal SIGSEGV: segmentation violation code=0x1 addr=0x58 pc=0x21b8f83]

What you expected to happen:
No panic.
How to reproduce it (as minimally and precisely as possible):
Get ngnix-deployment.yaml from https://raw.githubusercontent.com/kubernetes/website/master/docs/concepts/workloads/controllers/nginx-deployment.yaml .
Create the deployment:
λ kubectl create -f nginx-deployment.yaml
deployment "nginx-deployment" created

Delete a pod from the deployment (either one or all gives the same result):
λ kubectl delete pod nginx-deployment-6c54bd5869-2lshn
panic: runtime error: invalid memory address or nil pointer dereference
[signal SIGSEGV: segmentation violation code=0x1 addr=0x58 pc=0x21b8f83]

goroutine 1 [running]:
k8s.io/kubernetes/pkg/kubectl.ReaperFor(0x0, 0x0, 0x2370237, 0x3, 0x0, 0x0, 0x0, 0xc420a094a0, 0x13fdaa2, 0xbe9284d8ac70ccf0)
        /private/tmp/kubernetes-cli-20180118-36889-kx51hi/src/k8s.io/kubernetes/_output/local/go/src/k8s.io/kubernetes/pkg/kubectl/delete.go:82 +0x1373
k8s.io/kubernetes/pkg/kubectl/cmd/util.(*ring1Factory).Reaper(0xc420751200, 0xc4204f79d0, 0x3666b40, 0x1a0003825900, 0xb8, 0xb8)
        /private/tmp/kubernetes-cli-20180118-36889-kx51hi/src/k8s.io/kubernetes/_output/local/go/src/k8s.io/kubernetes/pkg/kubectl/cmd/util/factory_object_mapping.go:295 +0x151
k8s.io/kubernetes/pkg/kubectl/cmd/util.(*factory).Reaper(0xc420751230, 0xc4204f79d0, 0x3825900, 0x3e2b6c8, 0x0, 0x2678340)
        <autogenerated>:1 +0x47
k8s.io/kubernetes/pkg/kubectl/cmd.ReapResult.func1(0xc4204f7b20, 0x0, 0x0, 0x3815c00, 0x2853435)
        /private/tmp/kubernetes-cli-20180118-36889-kx51hi/src/k8s.io/kubernetes/_output/local/go/src/k8s.io/kubernetes/pkg/kubectl/cmd/delete.go:250 +0xe9
k8s.io/kubernetes/pkg/kubectl/resource.ContinueOnErrorVisitor.Visit.func1(0xc4204f7b20, 0x0, 0x0, 0x0, 0x0)
        /private/tmp/kubernetes-cli-20180118-36889-kx51hi/src/k8s.io/kubernetes/_output/local/go/src/k8s.io/kubernetes/pkg/kubectl/resource/visitor.go:396 +0x164
k8s.io/kubernetes/pkg/kubectl/resource.DecoratedVisitor.Visit.func1(0xc4204f7b20, 0x0, 0x0, 0x7, 0xa)
        /private/tmp/kubernetes-cli-20180118-36889-kx51hi/src/k8s.io/kubernetes/_output/local/go/src/k8s.io/kubernetes/pkg/kubectl/resource/visitor.go:372 +0xe7
k8s.io/kubernetes/pkg/kubectl/resource.FlattenListVisitor.Visit.func1(0xc4204f7b20, 0x0, 0x0, 0xc42096d140, 0x414e798)
        /private/tmp/kubernetes-cli-20180118-36889-kx51hi/src/k8s.io/kubernetes/_output/local/go/src/k8s.io/kubernetes/pkg/kubectl/resource/visitor.go:433 +0x4fe
k8s.io/kubernetes/pkg/kubectl/resource.(*Info).Visit(0xc4204f7b20, 0xc42096d140, 0x0, 0x10103e7)
        /private/tmp/kubernetes-cli-20180118-36889-kx51hi/src/k8s.io/kubernetes/_output/local/go/src/k8s.io/kubernetes/pkg/kubectl/resource/visitor.go:105 +0x42
k8s.io/kubernetes/pkg/kubectl/resource.VisitorList.Visit(0xc4201f2350, 0x1, 0x1, 0xc42096d140, 0x1, 0xc42096d140)
        /private/tmp/kubernetes-cli-20180118-36889-kx51hi/src/k8s.io/kubernetes/_output/local/go/src/k8s.io/kubernetes/pkg/kubectl/resource/visitor.go:234 +0x63
k8s.io/kubernetes/pkg/kubectl/resource.(*VisitorList).Visit(0xc420450900, 0xc42096d140, 0x3e2b6c8, 0x0)
        <autogenerated>:1 +0x58
k8s.io/kubernetes/pkg/kubectl/resource.FlattenListVisitor.Visit(0x365a640, 0xc420450900, 0xc4203516c0, 0xc4207864c0, 0x60000000001, 0xc4207864c0)
        /private/tmp/kubernetes-cli-20180118-36889-kx51hi/src/k8s.io/kubernetes/_output/local/go/src/k8s.io/kubernetes/pkg/kubectl/resource/visitor.go:428 +0x9e
k8s.io/kubernetes/pkg/kubectl/resource.(*FlattenListVisitor).Visit(0xc420450920, 0xc4207864c0, 0x28, 0x3825900)
        <autogenerated>:1 +0x58
k8s.io/kubernetes/pkg/kubectl/resource.DecoratedVisitor.Visit(0x365a5c0, 0xc420450920, 0xc4201f2360, 0x2, 0x2, 0xc420450980, 0x1, 0xc420450980)
        /private/tmp/kubernetes-cli-20180118-36889-kx51hi/src/k8s.io/kubernetes/_output/local/go/src/k8s.io/kubernetes/pkg/kubectl/resource/visitor.go:363 +0x9b
k8s.io/kubernetes/pkg/kubectl/resource.(*DecoratedVisitor).Visit(0xc42096d110, 0xc420450980, 0xc4201f2370, 0xc420a09b60)
        <autogenerated>:1 +0x62
k8s.io/kubernetes/pkg/kubectl/resource.ContinueOnErrorVisitor.Visit(0x365a4c0, 0xc42096d110, 0xc4204f7b90, 0x0, 0x2)
        /private/tmp/kubernetes-cli-20180118-36889-kx51hi/src/k8s.io/kubernetes/_output/local/go/src/k8s.io/kubernetes/pkg/kubectl/resource/visitor.go:391 +0xe4
k8s.io/kubernetes/pkg/kubectl/resource.(*ContinueOnErrorVisitor).Visit(0xc4201f2370, 0xc4204f7b90, 0x1010b48, 0x70)
        <autogenerated>:1 +0x4f
k8s.io/kubernetes/pkg/kubectl/resource.(*Result).Visit(0xc4202ae600, 0xc4204f7b90, 0xc42095bd10, 0x3679b80)```
        /private/tmp/kubernetes-cli-20180118-36889-kx51hi/src/k8s.io/kubernetes/_output/local/go/src/k8s.io/kubernetes/pkg/kubectl/resource/result.go:98 +0x62
k8s.io/kubernetes/pkg/kubectl/cmd.ReapResult(0xc4202ae600, 0x3686980, 0xc420751230, 0x3659480, 0xc42000c018, 0xc420130001, 0x0, 0xffffffffffffffff, 0xc4209a0000, 0x3679b80, ...)
        /private/tmp/kubernetes-cli-20180118-36889-kx51hi/src/k8s.io/kubernetes/_output/local/go/src/k8s.io/kubernetes/pkg/kubectl/cmd/delete.go:245 +0x16c
k8s.io/kubernetes/pkg/kubectl/cmd.(*DeleteOptions).RunDelete(0xc4207104d0, 0xc420290480, 0x0)
        /private/tmp/kubernetes-cli-20180118-36889-kx51hi/src/k8s.io/kubernetes/_output/local/go/src/k8s.io/kubernetes/pkg/kubectl/cmd/delete.go:235 +0xd2
k8s.io/kubernetes/pkg/kubectl/cmd.NewCmdDelete.func1(0xc420290480, 0xc42013d4c0, 0x2, 0x2)
        /private/tmp/kubernetes-cli-20180118-36889-kx51hi/src/k8s.io/kubernetes/_output/local/go/src/k8s.io/kubernetes/pkg/kubectl/cmd/delete.go:142 +0x178
k8s.io/kubernetes/vendor/github.com/spf13/cobra.(*Command).execute(0xc420290480, 0xc42013d300, 0x2, 0x2, 0xc420290480, 0xc42013d300)
        /private/tmp/kubernetes-cli-20180118-36889-kx51hi/src/k8s.io/kubernetes/_output/local/go/src/k8s.io/kubernetes/vendor/github.com/spf13/cobra/command.go:603 +0x234
k8s.io/kubernetes/vendor/github.com/spf13/cobra.(*Command).ExecuteC(0xc420396900, 0x8000104, 0x0, 0xffffffffffffffff)
        /private/tmp/kubernetes-cli-20180118-36889-kx51hi/src/k8s.io/kubernetes/_output/local/go/src/k8s.io/kubernetes/vendor/github.com/spf13/cobra/command.go:689 +0x2fe
k8s.io/kubernetes/vendor/github.com/spf13/cobra.(*Command).Execute(0xc420396900, 0xc420751230, 0x3659440)
        /private/tmp/kubernetes-cli-20180118-36889-kx51hi/src/k8s.io/kubernetes/_output/local/go/src/k8s.io/kubernetes/vendor/github.com/spf13/cobra/command.go:648 +0x2b
k8s.io/kubernetes/cmd/kubectl/app.Run(0x0, 0x0)
        /private/tmp/kubernetes-cli-20180118-36889-kx51hi/src/k8s.io/kubernetes/_output/local/go/src/k8s.io/kubernetes/cmd/kubectl/app/kubectl.go:41 +0xd5
main.main()
        /private/tmp/kubernetes-cli-20180118-36889-kx51hi/src/k8s.io/kubernetes/_output/local/go/src/k8s.io/kubernetes/cmd/kubectl/kubectl.go:27 +0x26

Anything else we need to know:
kubectl describe pod nginx-deployment-6c54bd5869-2lshn
Gives correct result.
Any deployment gives the same result.

I'm having the same issue, but I'm using minikube version 25 and Linux Mint, otherwise I have the same client and server kube versions.

Running against another, non-minikube, server seems to work for me.
Client Version: version.Info{Major:"1", Minor:"9", GitVersion:"v1.9.2", GitCommit:"5fa2db2bd46ac79e5e00a4e6ed24191080aa463b", GitTreeState:"clean", BuildDate:"2018-01-18T21:12:46Z", GoVersion:"go1.9.2", Compiler:"gc", Platform:"darwin/amd64"}
Server Version: version.Info{Major:"1", Minor:"9", GitVersion:"v1.9.2", GitCommit:"5fa2db2bd46ac79e5e00a4e6ed24191080aa463b", GitTreeState:"clean", BuildDate:"2018-01-18T09:42:01Z", GoVersion:"go1.9.2", Compiler:"gc", Platform:"linux/amd64"}
Against a cluster running on a Ubuntu16 server with kubeadm (kubeadm version: &version.Info{Major:"1", Minor:"9", GitVersion:"v1.9.1", GitCommit:"3a1c9449a956b6026f075fa3134ff92f7d55f812", GitTreeState:"clean", BuildDate:"2018-01-04T11:40:06Z", GoVersion:"go1.9.2", Compiler:"gc", Platform:"linux/amd64"}
) and kubelet (Kubernetes v1.9.1) and weave.
So this might be an issue with minikube only?

Possibly related information:
Creating a service, and then trying to fetch it gives different results when using svc vs service, against the broken cluster, but seems to work against other cluster?
kubectl create service nodeport nginx --tcp=8080
service "nginx" created

kubectl get svc nginx
the server doesn't have a resource type "svc"

kubectl get service nginx
NAME      TYPE       CLUSTER-IP     EXTERNAL-IP   PORT(S)          AGE
nginx     NodePort   10.98.56.135   <none>        8080:31786/TCP   18s

svc should be just an alias of service, it should get the same result as kubectl get service ***, but what you mean against a broken cluster? @rednatto

@adohe What I mean is that svc was not recognized, but service was, when running commands against the minikube cluster where pod delete panicked; and that it worked when running against another, non-minikube, cluster - where the delete did not panic.
Sorry to be unclear, I had written the same things in the minikube-issue and did not keep track of what I had written.
This missing alias thing seems to cooccur with the panicking?

I get a similar stack trace:
[signal SIGSEGV: segmentation violation code=0x1 addr=0x70 pc=0x15b6af7]

goroutine 1 [running]:
k8s.io/kubernetes/pkg/kubectl.ReaperFor(0x1c51e7a, 0xa, 0x17a3423, 0x9, 0x0, 0x0, 0xc4201c45f0, 0xa, 0xc4201c45f0, 0xa)
        /go/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/pkg/kubectl/delete.go:79 +0x1507
k8s.io/kubernetes/pkg/kubectl/cmd/util.(*ring1Factory).Reaper(0xc42031dd10, 0xc4202c62a0, 0x0, 0xc4207a75a0, 0x4d0d6a, 0xc420a063c0)
        /go/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/pkg/kubectl/cmd/util/factory_object_mapping.go:295 +0x151
k8s.io/kubernetes/pkg/kubectl/cmd/util.(*factory).Reaper(0xc42031dd40, 0xc4202c62a0, 0xc4207a7580, 0xc4207a74e0, 0x44606a, 0x20)
        <autogenerated>:1 +0x47
k8s.io/kubernetes/pkg/kubectl/cmd.ReapResult.func1(0xc4202c63f0, 0x0, 0x0, 0x2bfe940, 0x1c50a1e)
        /go/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/pkg/kubectl/cmd/delete.go:250 +0xe9
k8s.io/kubernetes/pkg/kubectl/resource.ContinueOnErrorVisitor.Visit.func1(0xc4202c63f0, 0x0, 0x0, 0x0, 0x0)
        /go/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/pkg/kubectl/resource/visitor.go:396 +0x164
k8s.io/kubernetes/pkg/kubectl/resource.DecoratedVisitor.Visit.func1(0xc4202c63f0, 0x0, 0x0, 0x1d, 0x1)
        /go/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/pkg/kubectl/resource/visitor.go:372 +0xe7
k8s.io/kubernetes/pkg/kubectl/resource.FlattenListVisitor.Visit.func1(0xc4202c63f0, 0x0, 0x0, 0xc420a19800, 0x7f600f0c1218)
        /go/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/pkg/kubectl/resource/visitor.go:433 +0x4fe
k8s.io/kubernetes/pkg/kubectl/resource.EagerVisitorList.Visit.func1(0xc4202c63f0, 0x0, 0x0, 0x1, 0xc420a19800)
        /go/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/pkg/kubectl/resource/visitor.go:255 +0x164
k8s.io/kubernetes/pkg/kubectl/resource.(*Info).Visit(0xc4202c63f0, 0xc420a19800, 0x28, 0x1a96480)
        /go/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/pkg/kubectl/resource/visitor.go:105 +0x42
k8s.io/kubernetes/pkg/kubectl/resource.EagerVisitorList.Visit(0xc4203361a0, 0x1, 0x1, 0xc4209f9140, 0x1, 0xc4209f9140)
        /go/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/pkg/kubectl/resource/visitor.go:250 +0xea
k8s.io/kubernetes/pkg/kubectl/resource.(*EagerVisitorList).Visit(0xc420a19740, 0xc4209f9140, 0x7f600f0f96c8, 0x0)
        <autogenerated>:1 +0x58
k8s.io/kubernetes/pkg/kubectl/resource.FlattenListVisitor.Visit(0x2a43300, 0xc420a19740, 0xc420054500, 0xc42034a8c0, 0x60000000001, 0xc42034a8c0)
        /go/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/pkg/kubectl/resource/visitor.go:428 +0x9e
k8s.io/kubernetes/pkg/kubectl/resource.(*FlattenListVisitor).Visit(0xc420a19760, 0xc42034a8c0, 0x28, 0xc4202eb180)
        <autogenerated>:1 +0x58
k8s.io/kubernetes/pkg/kubectl/resource.DecoratedVisitor.Visit(0x2a43380, 0xc420a19760, 0xc4203361b0, 0x2, 0x2, 0xc420a197c0, 0xc420336101, 0xc420a197c0)
        /go/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/pkg/kubectl/resource/visitor.go:363 +0x9b
k8s.io/kubernetes/pkg/kubectl/resource.(*DecoratedVisitor).Visit(0xc4209f9110, 0xc420a197c0, 0xc4203361c0, 0xc4207a7b60)
        <autogenerated>:1 +0x62
k8s.io/kubernetes/pkg/kubectl/resource.ContinueOnErrorVisitor.Visit(0x2a43280, 0xc4209f9110, 0xc4202c6540, 0x0, 0x2)
        /go/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/pkg/kubectl/resource/visitor.go:391 +0xe4
k8s.io/kubernetes/pkg/kubectl/resource.(*ContinueOnErrorVisitor).Visit(0xc4203361c0, 0xc4202c6540, 0x410d48, 0x70)
        <autogenerated>:1 +0x4f
k8s.io/kubernetes/pkg/kubectl/resource.(*Result).Visit(0xc4202e8000, 0xc4202c6540, 0xc42091b900, 0x2a62840)
        /go/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/pkg/kubectl/resource/result.go:98 +0x62
k8s.io/kubernetes/pkg/kubectl/cmd.ReapResult(0xc4202e8000, 0x2a6f640, 0xc42031dd40, 0x2a42480, 0xc42000c018, 0xc420480001, 0x0, 0xffffffffffffffff, 0xc420980000, 0x2a62840, ...)
        /go/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/pkg/kubectl/cmd/delete.go:245 +0x16c
k8s.io/kubernetes/pkg/kubectl/cmd.(*DeleteOptions).RunDelete(0xc42069de40, 0xc42038e000, 0x0)
        /go/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/pkg/kubectl/cmd/delete.go:235 +0xd2
k8s.io/kubernetes/pkg/kubectl/cmd.NewCmdDelete.func1(0xc42038e000, 0xc42048ebd0, 0x1, 0x1)
        /go/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/pkg/kubectl/cmd/delete.go:142 +0x178
k8s.io/kubernetes/vendor/github.com/spf13/cobra.(*Command).execute(0xc42038e000, 0xc42048eb70, 0x1, 0x1, 0xc42038e000, 0xc42048eb70)
        /go/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/vendor/github.com/spf13/cobra/command.go:603 +0x234
k8s.io/kubernetes/vendor/github.com/spf13/cobra.(*Command).ExecuteC(0xc4203a5440, 0x5000107, 0x0, 0xffffffffffffffff)
        /go/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/vendor/github.com/spf13/cobra/command.go:689 +0x2fe
k8s.io/kubernetes/vendor/github.com/spf13/cobra.(*Command).Execute(0xc4203a5440, 0xc42031dd40, 0x2a42440)
        /go/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/vendor/github.com/spf13/cobra/command.go:648 +0x2b
k8s.io/kubernetes/cmd/kubectl/app.Run(0x0, 0x0)
        /go/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/cmd/kubectl/app/kubectl.go:41 +0xd5
main.main()
        /go/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/cmd/kubectl/kubectl.go:27 +0x26

When running the following:
kubectl delete daemonsets/fluentd-elasticsearch
After a long delay kubectl version will return:
Client Version: version.Info{Major:"1", Minor:"9", GitVersion:"v1.9.2", GitCommit:"5fa2db2bd46ac79e5e00a4e6ed24191080aa463b", GitTreeState:"clean", BuildDate:"2018-01-18T10:09:24Z", GoVersion:"go1.9.2", Compiler:"gc", Platform:"linux/amd64"}
Unable to connect to the server: dial tcp x.x.x.x:443: i/o timeout

I recently updated my cluster using kops (it is running on AWS) to version 1.8.6 .

I have experienced this panic when accidentally running kubectl delete on worker node.

$ kubectl delete pod foo
panic: runtime error: invalid memory address or nil pointer dereference
[signal SIGSEGV: segmentation violation code=0x1 addr=0x58 pc=0x15b6963]

Environment:

Kubernetes version (use kubectl version):
Client Version: version.Info{Major:"1", Minor:"9", GitVersion:"v1.9.2", GitCommit:"5fa2db2bd46ac79e5e00a4e6ed24191080aa463b", GitTreeState:"clean", BuildDate:"2018-01-18T10:09:24Z", GoVersion:"go1.9.2", Compiler:"gc", Platform:"linux/amd64"}
Server Version: version.Info{Major:"1", Minor:"9", GitVersion:"v1.9.3", GitCommit:"d2835416544f298c919e2ead3be3d0864b52323b", GitTreeState:"clean", BuildDate:"2018-02-07T11:55:20Z", GoVersion:"go1.9.2", Compiler:"gc", Platform:"linux/amd64"}

OS (e.g. from /etc/os-release):
NAME="Ubuntu"
VERSION="16.04.3 LTS (Xenial Xerus)"
ID=ubuntu
ID_LIKE=debian
PRETTY_NAME="Ubuntu 16.04.3 LTS"
VERSION_ID="16.04"
HOME_URL="http://www.ubuntu.com/"
SUPPORT_URL="http://help.ubuntu.com/"
BUG_REPORT_URL="http://bugs.launchpad.net/ubuntu/"
VERSION_CODENAME=xenial
UBUNTU_CODENAME=xenial

Kernel (e.g. uname -a):
Linux stg-docker-004 4.4.0-96-generic #119-Ubuntu SMP Tue Sep 12 14:59:54 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux

Install tools:
KTHW (custom)

I'd like to investigate on this issue. @rsalmond  Can you share how you created my-nginx-nginx-ingress-controller in the above example?

@Liujingfang1 for sure, that was created using the stable nginx ingress controller helm chart.
helm install stable/nginx-ingress --name my-nginx --set rbac.create=true --set controller.hostNetwork=true

It's probably not the reason, but it could be a result of running out of disk space.

@rsalmond Thank you for your help. I used the same environment and running the same chart as you listed, but couldn't reproduce the error.  The reason might be out of disk space as @decoursin mentioned. I checked my nodes and none of them are out of disk.

Based on the stacktrace, the error is from this part of code in k8s.io/kubernetes/pkg/kubectl/cmd/util/factory_object_mapping.go
	reaper, reaperErr := kubectl.ReaperFor(mapping.GroupVersionKind.GroupKind(), clientset)

If clientset is nil, then we will see this segmentation error.  The fix would be to add a check on clientsetErr:
	clientset, clientsetErr := f.clientAccessFactory.ClientSet()
	if clientsetErr != nil {
		return nil, clientsetErr
	}
	reaper, reaperErr := kubectl.ReaperFor(mapping.GroupVersionKind.GroupKind(), clientset)

/assign @mengqiy

I got the same stacktrace as reproduced before while deleting pods, probably due to networking issues.

$ kubectl version
Client Version: version.Info{Major:"1", Minor:"9", GitVersion:"v1.9.1", GitCommit:"3a1c9449a956b6026f075fa3134ff92f7d55f812", GitTreeState:"archive", BuildDate:"1970-01-01T00:00:01Z", GoVersion:"go1.10", Compiler:"gc", Platform:"linux/amd64"}
The connection to the server 10.37.144.42:6443 was refused - did you specify the right host or port?

Same error here
Server Version is 1.9.6
Client Version is 1.9.6

Hi, i am working on a project to create a declarative application in
printers...I dont have any idea how to approach this...my job depends on
this...i searched on the internet and found your project...guys can you
please help me out for my project or any documents that i can study dor
declarative application...
Regards
Rishab Patnaik
On Sun, Apr 1, 2018, 6:32 PM Martin Dünkelmann notifications@github.com
wrote:

Same error here
Server Version is 1.9.6
Client Version is 1.9.6
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/kubernetes/kubectl/issues/226#issuecomment-377785401,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AbcxyYS_1mcKh1lvkhip_bUMFe6Vs5TRks5tkNAAgaJpZM4RsiGi
.

@rishabp please do not hijack bug tickets in an issue tracker. https://paste.kde.org/pmh0qaunn

authors: Liujingfang1 MartinX3 adohe aheart decoursin gardarh jdanekrh rednatto rishabp rsalmond

repo: kubernetes/kubectl


text:
Typo fix, trailing whitespace and updated email address

\cc @vishh

LGTM

source: gharchive/pull-request

authors: afein vishh

repo: kubernetes/kubedash

license_type: permissive

license_source: github-api


text:
ClusterLoader2 Module API

If you want to see it in action please take a look at this PoC PR  - https://github.com/kubernetes/perf-tests/pull/1632

/assign @jkaniuk
/assign @marseel
/assign @mborsz
/assign @tosi3k

/test pull-perf-tests-clusterloader2

/hold cancel
I'm fine with the direction - I will let others review details.

/lgtm
/hold
LGTM for me

/lgtm

LGTM for me

/lgtm

/hold cancel

authors: jkaniuk marseel mborsz mm4tt tosi3k wojtek-t

repo: kubernetes/perf-tests

license_source: bigquery


text:
Issue with 'kubectl completion powershell'

kubectl completion powershell
error: Unsupported shell type "powershell".
See 'kubectl completion -h' for help and examples

EN page: https://kubernetes.io/docs/tasks/tools/install-kubectl-windows/
It seems that you can use kubectl completion powershell with kubectl v1.23~.
If you are using kubectl ~v1.22, then you cannot use kubectl completion powershell.
Please run kubectl version, and copy & paste the result to here!
For example:
❯ kubectl version
Client Version: version.Info{Major:"1", Minor:"21", GitVersion:"v1.21.9", GitCommit:"b631974d68ac5045e076c86a5c66fba6f128dc72", GitTreeState:"clean", BuildDate:"2022-01-21T02:19:59Z", GoVersion:"go1.16.13", Compiler:"gc", Platform:"linux/amd64"}

/kind support
/retitle Issue with 'kubectl completion powershell'

EN page: https://kubernetes.io/docs/tasks/tools/install-kubectl-windows/
It seems that you can use kubectl completion powershell with kubectl v1.23~.
If you are using kubectl ~v1.22, then you cannot use kubectl completion powershell.
What is the version of kubectl you are using? Please run kubectl version, and copy & paste the result to here!
For example:
❯ kubectl version
Client Version: version.Info{Major:"1", Minor:"21", GitVersion:"v1.21.9", GitCommit:"b631974d68ac5045e076c86a5c66fba6f128dc72", GitTreeState:"clean", BuildDate:"2022-01-21T02:19:59Z", GoVersion:"go1.16.13", Compiler:"gc", Platform:"linux/amd64"}

/kind support /retitle Issue with 'kubectl completion powershell'

Thank you!
My version is 1.22, I will update to 1.23

It seems that this issue has been resolved and okay to close. 😊
/close

source: gharchive/issue

repo: kubernetes/website


text:
Documentation link for 'Weave Net' broken in 'Installing Addons' page

Broken link to the Weave Net plugin.
Weave Net it's broken
USE IT LINK https://github.com/weaveworks/weave

Page related to issue: https://kubernetes.io/docs/concepts/cluster-administration/addons/
/language en
/kind bug

/retitle Documentation link for 'Weave Net' broken in 'Installing Addons' page

This looks similar to issue we already have https://github.com/kubernetes/website/issues/45201
I think it is a duplicate.
/triage duplicate

Closing in favor of https://github.com/kubernetes/website/issues/45201
/close

authors: dipesh-rawat reylejano slavnyj


text:
Add clarity around ReadWriteMany and CSI volume fsgroup ownership changes

This is a Feature Request

What would you like to be added

Enhance the documentation around volume permissions and ownership change policy for Pods. In the documentation the fsgroup setting is not explicitly defined as only supporting ReadWriteOnce volumes. In the CSI mounter code, fsgroup is ignored if the AccessMode for a PVC is not ReadWriteOnce. This request is to enhance the documentation by adding a note stating this setting is ignored in RWX mode.
Why is this needed
This would clarify the use of the fsgroup setting fpr RWX volumes
Comments

If that ftn returns false, then I think we fall back to the kubelet fsgroup policy which will apply it for RWX volumes: https://github.com/kubernetes/kubernetes/blob/9e2075b3c87061d25759b0ad112266f03601afd8/pkg/volume/csi/csi_mounter.go#L335
?

I think it's driver dependent. Fsgroup will only be honoured for RWX volumes if the driver supports VOLUME_MOUNT_GROUP. By default the Kubelet fsgroup will only be applied if that function (supportsFSGroup) returns true (and the function returns false if the PVC isn't RWO).

Hmm. I thought I'd seen problems for fsgroup on nfs volumes, though.

Oh, but if a driver advertises, eg, a File access mode then fsgroup will apply: https://kubernetes-csi.github.io/docs/support-fsgroup.html.

Oh, but if a driver advertises, eg, a File access mode then fsgroup will apply: https://kubernetes-csi.github.io/docs/support-fsgroup.html.

Yes, I think that's the only way that non-RWO volumes can support fsgroup, by delegating to a (supported) CSI driver

authors: mattcary pwschuurman


text:
Add content/es/docs/content/overview/working-with-objects

Spanish Translation

Muchas gracias @emedina!

Buenas @emedina, le estoy echando un ojo al mecanismo que se utiliza para el glosario de términos, ya que está provocando que el build no se complete.
/hold

Ok @raelga, avisa si necesitas que haga cualquier cosa para moverlo... Búscame por Slack si me necesitas...

Buenas @emedina,
El build falla por la ausencia de las templates de feature-state, he creado la PR https://github.com/kubernetes/website/pull/14135 para añadirlas.

All green ✔
I added the glossary terms for name and uid, and added the rest to the #13948 to work on them during the hackaton.

/hold-cancel

/hold cancel

@alexbrand Can you review the content?
Thanks!

@raelga Ya he incorporado tus cambios con algunas correcciones al PR.

Tracked in https://github.com/kubernetes/website/issues/13948

Thanks for this @emedina!
/lgtm

Thanks @alexbrand for the review and @emedina for the localization!
/lgtm
/approve

authors: alexbrand emedina raelga


text:
Translate concept and related glossaries to Japanese

concept / components と、そこからリンクされている glossaries を日本語訳しました。
gloassary はディレクトリ一式追加してしまいましたが、日本語訳しているのは以下12ファイルです。

container-runtime.md
controller.md
daemonset.md
deployment.md
etcd.md
kube-apiserver.md
kube-controller-manager.md
kube-proxy.md
kube-scheduler.md
kubelet.md
pod.md
service.md

ところで、これらのファイルは必須(無いとビルドが通らない)でしょうか？

むしろ

glossary配下の全ファイルが必須ではないですが、components.md 内に埋め込まれている kubelet.md, etcd.md などは存在しないとHugo でビルドエラーになります。 @nasa9084
ちなみに未翻訳のファイルも含めて一式入れたのは、今後翻訳した際、コミット差分で英語と日本語が出た方が分かりやすいのでは･･･という観点です。

今後翻訳した際、コミット差分で英語と日本語が出た方が分かりやすいのでは･･･という観点です。

そういう考え方もあるんですが、英語（つまりMasterブランチ）の方でいつどのタイミングで変更がかかるかわからず、日本語のディレクトリに入れてしまうとその変更がトラックできないんですよね。
そのため、基本的には必須でない限りはその時点で不要なものは入れない、という形でやらせていただいてます。

そのため、基本的には必須でない限りはその時点で不要なものは入れない、という形でやらせていただいてます。
そうでしたか。。失礼しました。 @inductor

ご指摘に従い、翻訳していないファイルを削除しました。
また、消し忘れていた英文があったので、消しました。

あ、いえ、全く咎めるなどの意図はなく、そういう感じでやってますよという情報共有でした:relieved:
ご理解、ご対応ありがとうございます！

可能であればbaseを dev-1.15-ja.1 へ変更してrebaseとcherry-pickをしていただきたく:bow:

すみません。遅くなりましたが、dev-1.15-ja.1 への rebase と cherry-pick をしてみました。
@cstoku
あまり Git に慣れていないので、間違いがあれば指摘して下さい。

/approve

/lgtm

authors: craftone cstoku inductor nasa9084


text:
add docs for csi expansion going beta

Add docs for csi expansion going beta.
Xref https://github.com/kubernetes/enhancements/issues/556

/approve

authors: gnufied simplytunde


text:
Fix title format error

https://deploy-preview-21810--kubernetes-io-master-staging.netlify.app/zh/docs/tasks/configure-pod-container/assign-cpu-resource/

Thanks for the quick fix. Preview looks nice.
/lgtm
/approve

authors: tengqm xieyanker


text:
Use overviews in reference section

The Docsy theme makes much more of section overview compared to the somewhat custom-for-Kubernetes documentation theme this site previously used.
Now we've switched to Docsy, some pages and sections have spartan overviews. This PR aims to help out there.

Move https://kubernetes.io/docs/reference/using-api/api-overview/ to https://kubernetes.io/docs/reference/using-api/
Move Controlling Access to the Kubernetes API out of the reference section and into https://kubernetes.io/docs/concepts/security/controlling-access/ [preview]
Update the overview for https://kubernetes.io/docs/reference/access-authn-authz/ [preview]

also fixing links and redirects.

/hold

/approve cancel

Hi @irvifa
What needs to happen to move this PR forward?

/hold cancel
Previously it needs rebase now it’s good
/approve

authors: irvifa sftim


text:
Update Calico description on 'Cluster Networking' page

This PR updates the description of Calico on the 'Cluster Networking' page: https://kubernetes.io/docs/concepts/cluster-administration/networking/
The current description is a bit dated and doesn't capture the current state of Calico's dataplane options and general platform support. For example, Calico's got an eBPF dataplane and its Windows dataplane has been opensourced.

Page preview:
https://deploy-preview-24730--kubernetes-io-master-staging.netlify.app/docs/concepts/cluster-administration/networking/#how-to-implement-the-kubernetes-networking-model

Nice!
/lgtm

Thanks @lmm .
/approve

Great, thanks @sftim @kbhawkey !

authors: kbhawkey lmm sftim


text:
Add reference for audit API group

This is a reference for "audit.k8s.io/v1" API group generated from kubernetes-sigs/reference-docs/genref tool.
More specifically, it is generated using the following command:
./genref -format markdown -include apiserver-audit

Preview: https://deploy-preview-26606--kubernetes-io-master-staging.netlify.app/docs/reference/command-line-tools-reference/apiserver-audit.v1/

Hi @tengqm . Here is initial feedback on the rendered output.

Some fields have an asterisk? The field type is listed below the field name. Would it make sense to list
the type next to the field name?
The name of the resource type is level H3? Could remove the top TOC (Resource types) and use level H2 for each type?
If fields are missing a description, should you substitute some common text into the blank table fields?
The file is named, docs/reference/command-line-tools-reference/apiserver-audit.v1/ and the title of the page is:
audit.k8s.io/v1? Should the title include "apiserver"?
You may want to create a new directory in the left navigation tree to house the configuration references? Also, one of the link locations is: /docs/reference/command-line-tools-reference/apiserver-audit.v1/#audit-k8s-io-v1-Stage? Do you want to replace the "dot" in the filename to apiserver-audit-v1`?
Do you like the table rows with "shading/stripes"?

Some fields have an asterisk?

A blue star indicates that field is NOT marked as optional.

The field type is listed below the field name. Would it make sense to list the type next to the field name?

My overall observation is that in most if not all configuration structs, the field names and field type names tend to be long. The descriptions for field member are markdown paragraphs. Which are long too. To make sure the whole table is always readable on all devices, wrapping the type of the field to a second line is a good choice.

The name of the resource type is level H3? Could remove the top TOC (Resource types) and use level H2 for each type?

Yes. That is doable. Will revise.

If fields are missing a description, should you substitute some common text into the blank table fields?

That makes sense.

The file is named, docs/reference/command-line-tools-reference/apiserver-audit.v1/ and the title of the page is:  audit.k8s.io/v1? Should the title include "apiserver"?

The apiserver-audit name comes from the config.yaml file. It is just a unique identifier for the API package. The apiserver part comes from the package path. audit.k8s.io/v1 comes from the source code parsing. Maybe I can go through the config file and rename the identifier accordingly.

You may want to create a new directory in the left navigation tree to house the configuration references? Also, one of the link locations is: /docs/reference/command-line-tools-reference/apiserver-audit.v1/#audit-k8s-io-v1-Stage? Do you want to replace the "dot" in the filename to apiserver-audit-v1`?

I don't see that renaming an improvement. It will make version parsing difficult given that group names for these config APIs vary in length. Keeping a dot in the name helps extract/identify version string from the file name.

Do you like the table rows with "shading/stripes"?

I can remove the table-striped class. Let's see if such a change helps improve the look & feel.
Thanks for the detailed review.

/assign @kbhawkey

Preview link: https://deploy-preview-26606--kubernetes-io-master-staging.netlify.app/docs/reference/config-api/apiserver-audit.v1/

/hold
Depends on: https://github.com/kubernetes-sigs/reference-docs/pull/214

/hold cancel
kubernetes-sigs/reference-docs#214 is in.

Page preview:
https://deploy-preview-26606--kubernetes-io-master-staging.netlify.app/docs/reference/#config-apis

The Audit configuration page publishes under reference/config-api but will not
display under this directory until the section _index file merges (related PR).
/lgtm

Taking https://github.com/kubernetes/website/pull/26606#issuecomment-808750450 as LGTM by another party
/approve

authors: kbhawkey sftim tengqm


text:
Fix typo a extension

Fixed typo a extension to an extension, to better the documents.

@astra99 DON'T DO THIS.
We are not supposed to submit a PR to multiple languages, unless the fix is very simple and you are sure you are not breaking the workflow of any localization teams. For this PR, this is not a blocker.
Another problem of this PR is that it is fixing a zh localization file, while we are not sure whether that file is still well in sync with the upstream English file. Please run the script ./scripts/lsync.sh to verify.
/hold

@astra99 DON'T DO THIS.
We are not supposed to submit a PR to multiple languages, unless the fix is very simple and you are sure you are not breaking the workflow of any localization teams. For this PR, this is not a blocker.
Another problem of this PR is that it is fixing a zh localization file, while we are not sure whether that file is still well in sync with the upstream English file. Please run the script ./scripts/lsync.sh to verify.
/hold

Got it, updated with only one doc(en/zh), and checked still in sync.
scripts/lsync.sh content/en/docs/reference/scheduling/config.md
content/en/docs/reference/scheduling/config.md is still in sync

The other file fixed with a new PR: https://github.com/kubernetes/website/pull/29486
@tengqm PTAL thanks.

@astraw99 You were running a different command. The correct command to run under main branch is:
scripts/lsync.sh content/zh/docs/reference/scheduling/config.md

@astraw99 You were running a different command. The correct command to run under main branch is:
scripts/lsync.sh content/zh/docs/reference/scheduling/config.md

Got it, fix this typo with a new PR: https://github.com/kubernetes/website/pull/29500

/hold
谢谢贡献。根据指南约定，我们会拒绝对页面的部分修改。部分修改针对的是对应页面的英文上游还有其他改动需要同步的情况。
一旦我们合并了此 PR，将来就无法根据文件的最后更改时间来判断是否有其他上游变更尚未同步。请理解。
请在 main 分支上执行以下命令查看上游尚未同步的更改：
./scripts/lsync.sh content/zh/docs/reference/scheduling/config.md

/hold
谢谢贡献。根据指南约定，我们会拒绝对页面的部分修改。部分修改针对的是对应页面的英文上游还有其他改动需要同步的情况。
一旦我们合并了此 PR，将来就无法根据文件的最后更改时间来判断是否有其他上游变更尚未同步。请理解。
请在 main 分支上执行以下命令查看上游尚未同步的更改：
./scripts/lsync.sh content/zh/docs/reference/scheduling/config.md

Got it. Checked the diff in main branch: scripts/lsync.sh
Found there are lots of inconsistency, it is hard to resync the whole page, so just close this PR.


text:
[zh] sync auth for 1.22

related: #29327
Sync Chinese for following:
42	23	content/zh/docs/reference/access-authn-authz/certificate-signing-requests.md
6	6	content/zh/docs/reference/access-authn-authz/extensible-admission-controllers.md
1	1	content/zh/docs/reference/access-authn-authz/_index.md

/lgtm
/approve

authors: chenxuc tengqm


text:
No need for special handling for zsh aliases

Zsh completion is native since v1.22. Native zsh completion automatically deals with aliases without needing any extra configuration from the user.
Ref: https://github.com/kubernetes/kubernetes/pull/96087
/cc @eddiezane @brianpursley

/assign @kbhawkey

Page preview:
https://deploy-preview-32050--kubernetes-io-main-staging.netlify.app/docs/tasks/tools/install-kubectl-linux/#enable-shell-autocompletion

/approve

authors: eddiezane kbhawkey marckhouzam


text:
Update taint-and-toleration.md. Correct explanation of tolerationSeconds: 3600

Correct explanation of tolerationSeconds: 3600
Current documentation says
means that if this pod is running and a matching taint is added to the node, then
I think this is wrong? Its not making sense to me. Pardon me if I am missing something.
I think. It should be
means that if this pod is running without required toleration and taint is added to the node, then

Agreed with @divya-mohan0209 regarding this contribution.
Given that, I'll be closing this PR – @meSunnySrivastava please reopen this if you believe otherwise.
/close

authors: meSunnySrivastava natalisucks


text:
Fix broken link on Enforcing Pod Security Standards page

Fixes #36929
Updated page Enforcing Pod Security Standards

Thanks for the fix!
/lgtm

The page updated by this PR states Pod Security Admission has the Feature State for Pod Security Admission as beta as of 1.23. Can you also update the feature state to be FEATURE STATE: Kubernetes v1.25 [stable]

Page preview:
https://deploy-preview-36930--kubernetes-io-main-staging.netlify.app/docs/setup/best-practices/enforcing-pod-security-standards/#configure-all-cluster-namespaces
/king cleanup

/approve

authors: kadtendulkar kbhawkey mtardy reylejano


text:
[ko] Update outdated files in dev-1.25-ko.1 (M53-M60)

Related Issue : #36863

8 files to be modified

[ ]  M53.  content/en/docs/contribute/participate/_index.md  | 1(+XS) 1(-)
[ ]  M54.  content/en/docs/contribute/style/write-new-topic.md  | 2(+XS) 2(-)
[ ]  M55.  content/en/docs/reference/access-authn-authz/authorization.md  | 2(+XS) 0(-)
[ ]  M56.  content/en/docs/reference/access-authn-authz/service-accounts-admin.md  | 16(+S) 7(-)
[ ]  M57.  content/en/docs/reference/command-line-tools-reference/feature-gates.md  | 86(+M) 38(-)
[ ]  M58.  content/en/docs/reference/command-line-tools-reference/kube-proxy.md  | 3(+XS) 3(-)
[ ]  M59.  content/en/docs/reference/glossary/cni.md  | 4(+XS) 4(-)
[ ]  M60.  content/en/docs/reference/glossary/eviction.md  | 18(+S) 18(-)

@bconfiden2 좋으네요! 리뷰 의견 반영까지 잘 해 주셔서 감사합니다!
/lgtm

감사합니다!!
/approve

authors: bconfiden2 jihoon-seo seokho-son


text:
update glossary entry for MVP

This PR adds a hyperlink to feature gates in the glossary entry for MVP

Do we want to try and merge this PR before the code freeze which starts on Monday?

authors: Richabanker Rishit-dagli


text:
Merged main into dev 1.29 branch

This PR syncs the dev-1.29 branch with main to keep the dev-1.29 branch up to date.
cc: @katcosgrove @drewhagen  @harshitasao @Princesso

/lgtm

/lgtm

Thanks
/approve

authors: Princesso katcosgrove sftim taniaduggal


text:
[ja] Follow the upstream for content/ja/community/static/cncf-code-of-conduct.md

close #45002
Change List

update commit hash in content/ja/community/code-of-conduct.md
update content/ja/community/static/cncf-code-of-conduct.md from v1.0 to v1.3

ref. https://github.com/cncf/foundation/pull/631

Comment
If need to modify the content, it is necessary to first make corrections to cncf/foundation

/assign @nasa9084

/label tide/merge-method-squash

The target pages on the deploy preview site:

https://deploy-preview-45004--kubernetes-io-main-staging.netlify.app/ja/community/code-of-conduct/

@nasa9084
ありがとうございます :)
一応コメントに書いた通りで、https://github.com/cncf/foundation/blob/main/code-of-conduct-languages/jp.md を真としたいので、更新したものを先に https://github.com/cncf/foundation に反映させて頂いても良いですか？？

もう一点お手数なんですが、 https://github.com/cncf/foundation に日本語ローカライズのreviewerがいないので、作成したPRのレビューお願いしてもいいですか（マージは nate-double-u sanにお願いします）

すみません、ちゃんと理解してなかったです。コピーしてきただけのファイルなんですね。では一旦そのまま行きましょう
必要ならcncf/foundation側でのレビュー対応も了解です

/approve

/hold
ref. https://kubernetes.slack.com/archives/C016LL2HF61/p1707925168714439

/label tide/merge-method-squash

/hold cancel

@nasa9084
cncf側のPRがマージされたので、こちらも取り込めそうです（このprに関してはnasaさんがLGTM打ってよさそうに見えますがどうでしょう。。？？）

/hold

/unhold

it seems that other reviewers have been busy recently... 😢
as it's just copied from the CNCF's one basically, let me lgtm as well
/lgtm


text:
Added glossary definition for init container.

^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
For 1.10 Features: set Milestone to 1.10 and Base Branch to release-1.10
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
NOTE: After opening the PR, please un-check and re-check the "Allow edits from maintainers" box so that maintainers can work on your patch and speed up the review process. This is a temporary workaround to address a known issue with GitHub.>
Please delete this note before submitting the pull request.

This change is

@brahmaroutu 👋 :shipit:
/lgtm

authors: brahmaroutu zacharysarah


text:
feat: add caching for testkube binary

This PR...
Changes

Fixes

https://github.com/kubeshop/testkube/issues/4939

Checklist

[ ] tested locally
[ ] added new dependencies
[ ] updated the docs
[ ] added a test

Hi @devcatalin , @rangoo94 Thank you for the concise support regarding this feature. I've recently had the opportunity to review your implementation, and I'd like to share some comments from my perspective. This approach is only viable once Testkube is successfully installed within the GitHub Actions (GA) workflow. This means the cache is effective only when Testkube has been installed. There's a scenario where GitHub.io might impose rate limits, rejecting installation from anonymous access, rendering this caching implementation ineffective.
I propose we implement an additional feature: allowing users to define the GitHub.io Personal Access Token (PAT) within the action.yaml. This PAT could then be used to authorize with GitHub.io, overcoming potential rate-limiting issues. For more details about the token property I mentioned, you can refer to https://github.com/actions/setup-python.
The combination of a GitHub.io token and caching would be highly beneficial. 👍

repo: kubeshop/setup-testkube

license: MIT


text:
✨ Change E2E setup to let core chart install kubeflex in hosting cluster

Summary
This PR changes the script that does setup for E2E testing to align it with what the Getting Started instructions tell users, which is to use scripts/create-kind-cluster-with-SSL-passthrough.sh to create the hosting cluster and let the core Helm chart install KubeFlex in the hosting cluster; formerly the E2E test setup used kflex init and had the core Helm chart not install KubeFlex in the hosting cluster. This change is good because we want to regularly test the recipe that we tell users to do.
Related issue(s)
This is also good because it moots #2491 . I am not saying this fully resolves #2491 , because we do not forbid users to use kflex init and we also have a dependency-checking script that does not check versions.

/cc @francostellari
/cc @pdettori
/cc @dumb0002
/cc @KPRoche

/lgtm

a) I tested this PR in a env with an old Kubeflex version installed: v0.6.1
b) the e2e test in this PR deployed the correct version for Kubeflex:
k -n kubeflex-system logs kubeflex-controller-manager-749f8c7c6b-twshk
2024-10-10T14:51:54Z	INFO	controller-runtime.metrics	Metrics server is starting to listen	{"addr": "127.0.0.1:8080"}
2024-10-10T14:51:54Z	INFO	setup	starting manager	{"version": "v0.6.3.672cc8a"}
2024-10-10T14:51:54Z	INFO	Starting server	{"kind": "health probe", "addr": "[::]:8081"}
2024-10-10T14:51:54Z	INFO	starting server	{"path": "/metrics", "kind": "metrics", "addr": "127.0.0.1:8080"}
I1010 14:51:54.339982       1 leaderelection.go:250] attempting to acquire leader lease kubeflex-system/c6f71c85.kflex.kubestellar.org...
I1010 14:51:54.349438       1 leaderelection.go:260] successfully acquired lease kubeflex-system/c6f71c85.kflex.kubestellar.org

@MikeSpreitzer, everything works as expected. Thanks!
/lgtm

authors: MikeSpreitzer dumb0002 francostellari

repo: kubestellar/kubestellar


text:
[Feature] Upgrade golangci-lint to a higher version

Is your feature request related to a problem? Please describe.

The golangci-lint in KubeVela repo is v1.38.0 which is kinda outdated, it's nice to upgrade it to a higher version.
At the same time, some codes in the repo don't meet the lint requirement in the higher version, so please fix them in the upgrading.
You can use the command make lint to check all the results.
Describe the solution you'd like

Describe alternatives you've considered

Additional context

Along with the upgrade, we should fix the potential lints detected in the new version.

@FogDong make lint has errors now, am i right? I forked your repository, and when i make lint, i got some errors

If your golangci-lint is higher than v.1.38.0, the code won't pass all the lints.
So yes if you want to get started with this issue, you can fix all the lints problem when you use a higher version of golangci-lint.

/assign

@FogDong One of the checks from golangci-lint  states that strings.Title  has been deprecated. It suggests using [cases]( golang.org/x/text/cases instead).
However, cases.Title requires a language tag to specify which language it should parse. I used English at first, but since KubeVela is used in Chinese, I may have to check for that too. This could mean modifying function parameters, which I am skeptical about.  What do you suggest? Should I just use English for now?
Please find attached a working sample code I wrote on the Go playground

Should I just use English for now?

@MimicTester1307 You can use English directly, some of the core contributors of KubeVela are from China but they're all good with both English and Chinese, the project itself is a worldwide project so we can just use English in the code.

This issue is not concrete and actually it can be never closed if it's really an issue, because we can always upgrade to higher version as time passed. 😸  Closing

authors: FogDong MimicTester1307 wonderflow

repo: kubevela/kubevela


text:
[Feature] Add more data field to application view and managed resource view in vela top

Is your feature request related to a problem? Please describe.

At present, the data in the app view and managed resource view are relatively thin. We should add some fields to these fields.
Describe the solution you'd like

About application, we can add:

workflow step mode
finished workflow / total workflow
running service / total service

About managed resource, we can add:

of which component

Describe alternatives you've considered

Additional context

/assign


text:
Bug 2176708: Adding disk name to pending changes alert

📝 Description
Adding the disk name to pending changes alert at VM details to change of make persistent disk.
🎥 Demo
After:

Before:

/lgtm

authors: metalice pcbailey

repo: kubevirt-ui/kubevirt-plugin


text:
Allow infra components to be scheduled to master nodes

In many environments the master key is still being used (e.g. [1]).
[1] https://docs.openshift.com/container-platform/4.15/nodes/scheduling/nodes-scheduler-taints-tolerations.html
Therefore, allow infra pods to be scheduled to such nodes as well.
Special notes for your reviewer
Follow-up to: https://github.com/kubevirt/kubevirt/pull/11659
See this comment especially: https://github.com/kubevirt/kubevirt/pull/11659#discussion_r1555270580
Release note

NONE

Special thanks to @brianmcarey who proactively raised my attention to this.
In https://github.com/kubevirt/kubevirt/pull/11659#discussion_r1555270580 I've intended to include the master label, but since it was deprecated it was eventually removed from the PR. We should bring it back to support old clusters that were upgraded and lack the CP label.
/cc @acardace @fossedihelm

Thank you @iholder101! As already said I agree with this change #11659 (comment) Sorry for the initial wrong suggestion

No need to apologize!
You were pointing out true facts :) I also wasn't aware that the master label is still used in some environments.
Thank you!

/approve

repo: kubevirt/kubevirt


text:
Add ready condition flag to VM (#2864)

Signed-off-by: Mason Prey masonprey7@gmail.com

What this PR does / why we need it:
Provides ready condition flag to the VM which enables
$ kubectl wait --for=condition=Ready vm <vm>
Which issue(s) this PR fixes
Fixes #2864
Special notes for your reviewer:
N/A
Release note:

There are some unit test errors: https://travis-ci.org/kubevirt/kubevirt/builds/621749349#L1535

/ok-to-test

authors: mprey rmohr


text:
Fix node-labeller flaky test

What this PR does / why we need it:
Virsh reports some cpu models as supported, but libvirt refuses to run vm with that cpu model.
This commit adds new functionality, which checks requested cpu model against supported models reported by virsh.
added check for usable cpu models
added attribute check=none to vmi cpu converter
Which issue(s) this PR fixes:
Fixes #3390
Release note:

//cc @rmohr
Signed-off-by: Karel Simon ksimon@redhat.com

At least some tests fail due to the change: https://prow.apps.ovirt.org/view/gcs/kubevirt-prow/pr-logs/pull/kubevirt_kubevirt/3403/pull-kubevirt-e2e-k8s-1.15-ceph/1260172878217744384

/test pull-kubevirt-e2e-k8s-cnao-1.17

/retest


text:
Fix bug in restore-controller when creating a restore PVC with both dataSource and dataSourceRef

What this PR does / why we need it:
With the dataSourceRef API inclusion in k8s v1.22, a new validation mechanism was added for PVCs ensuring that, if present, both the dataSource and dataSourceRef fields must be equal.
This behavior conflicts with the restore-controller, which creates the restore PVC using the source spec as a reference, but overwriting the dataSource field. If the source PVC has a populated dataSourceRef field, just overwriting the dataSource triggers the validation error.
This Pull Request aims to modify this behavior, so both dataSource and dataSourceRef are overwritten.
Which issue(s) this PR fixes:
https://bugzilla.redhat.com/show_bug.cgi?id=2128872
Special notes for your reviewer:
In order to replicate the bug in older k8s versions (v1.18-v1.23), the AnyVolumeDataSource feature gate needs to be enabled in kube-apiserver. This feature gate is enabled by default in newer versions.
Release note:

NONE

Awesome!
I think you could have even reduced the tests to VMRestore of already "restored" (i.e. PVC that was created from a dataSource) PVC but definitely a wider cover with the included cloning mechanism. More info on the validation logic is described here btw: https://kubernetes.io/docs/concepts/storage/persistent-volumes/#data-source-references
Note that this is likely a problem on release-0.53 as well, as that is what we ship with OpenShift 4.11 (=> k8s 1.24 where the FG is enabled by default)
/lgtm

Thank you for the input! I'll wait for this PR to be merged before opening the backport PR.

/approve

The bumped non-root lanes are stuck in expected state - triggering them now.
/test pull-kubevirt-e2e-k8s-1.24-operator-nonroot
/test pull-kubevirt-e2e-k8s-1.24-sig-compute-nonroot
/test pull-kubevirt-e2e-k8s-1.24-sig-network-nonroot
/test pull-kubevirt-e2e-k8s-1.24-sig-storage-nonroot

/retest-required

/cherry-pick release-0.58
/cherry-pick release-0.53

/cherry-pick release-0.53<

/cherry-pick release-0.53

authors: alromeros brianmcarey maya-r mhenriks


text:
Update cni-plugin.md

Minor updates to the details.

Hello contributor, thanks for submitting a PR for this project!
I am the bot who triggers "standard-CI" builds for this project.
As a security measure, I will not run automated tests on PRs that are not from white-listed contributors.
In order to allow automated tests to run, please ask one of the project maintainers to review the code and then do one of the following:

Type ci test please on this PR to trigger automated tests for it.
Type ci add to whitelist on this PR to trigger automated tests for it and also add you to the contributor white-list so that your future PRs will be tested automatically.
If you are planning to contribute to more than one project, maybe it's better to ask them to add you to the project organization, so you'll be able to run tests for all the organization's projects.

ci test please

ci add to whitelist

@ashish-billore thanks!

authors: ashish-billore ovirt-infra phoracek

repo: kubevirt/ovs-cni


text:
export v2v request functions + few fixes

add secret owner references
move selectors for clearer approach
support unit when creating PVCs
let startV2VVMWareController behave like a promise

required by https://github.com/openshift/console/pull/2964

Pull Request Test Coverage Report for Build 2373

4 of 16 (25.0%)  changed or added relevant lines in 4 files are covered.
1 unchanged line in 1 file lost coverage.
Overall coverage decreased (-0.2%) to 82.61%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

src/k8s/requests/v2v/correctVCenterSecretLabels.js
0
1
0.0%

src/k8s/requests/v2v/startV2VvmwareController.js
0
1
0.0%

src/k8s/requests/v2v/importVmware.js
3
7
42.86%

src/k8s/requests/v2v/createV2VvmwareObject.js
1
7
14.29%

Files with Coverage Reduction
New Missed Lines
%

src/k8s/requests/v2v/startV2VvmwareController.js
1
11.86%

Totals

Change from base Build 1957:
-0.2%

Covered Lines:
4205

Relevant Lines:
4870

💛  - Coveralls

authors: coveralls suomiy

repo: kubevirt/web-ui-components


text:
网络图片出不来解决.

遇到网络图片出不来的问题，这个要么图片链接有问题，有么就是代码有问题，然后我遇到的是图片链接有问题，首先图片链接要https才行，然后图片服务器的域名要添加到微信的小程序后台的downloadfile合法域名中，这样才能正常的加载出来。

补充图片不能用base64 因为微信的文件下载不支持base64

是的 真机测试之前一定要验证下图片的链接是不是支持 https 有没有在小程序后台的downloadfile合法域名中, 可以这样验证问题: 加载本地图片测试一次, 然后再加载网络图片测试一次 就清楚了

authors: jocongmin zmGitHub


text:
Blog post and add myself as author.

Signed-off-by: Marcin Owsiany mowsiany@D2iQ.com

What this PR does / why we need it:
Which issue(s) this PR fixes:

Fixes #
Special notes for your reviewer:

Nice read 👏
just one tiny typo, otherwise lgtm!

authors: meichstedt porridge


text:
Allow custom output directory for diagnostics collection

Signed-off-by: Andreas Neumann aneumann@mesosphere.com
What this PR does / why we need it:
Allow kudo diagnostics collect --outputDir instance1 so we can collect multiple diagnostics in the same directory

How does this differ from #1599?

How does this differ from #1599?

It doesn't. Alena and I implemented this independently. She was trying out the diagnostic feature, I was trying to integrate it with KUDO Cassandra and we both noticed that it needs to be done

Can you and @alenkacz reconcile which one should be closed?

I've closed Alenas PR (after reconciling with her), I'm going to add her as Co-Author on this one when it's merged.

repo: kudobuilder/kudo


text:
#230 - Fix CI merge formatting test.

What type of PR is this?
/kind bug
What this PR does / why we need it:
Instead of merging master into the PR, we merge the PR into master to check the merge formatting.
Which issue(s) this PR fixes:

Fixes #230

Oh, duh, git is mad that it hasn't been configured with a username and email.


text:
Reflect sections for the week, month, quarter and year

I really like the dedicated daily reflect page, and was wondering if it would be possible to add in a weekly, monthly, quarterly and yearly reflect sections?
It can be something very similar (weekly/monthly summary, gratefulness, milestones/challenges, weekly/monthly log).

Yep, that is something that I was also thinking about
I'll try to get this done this year 😬

authors: AbstractGeek kudrykv

repo: kudrykv/latex-yearly-planner


text:
Version relaxation & minor build improvements

We encountered a resolution problem trying to use the component with angular versions > 1.2.x. I modified the build to accept versions of angular after 1.2.x and tested against 1.3.14.
The remaining changes were fixes to get the build working (package.json), eliminate warnings (karma.conf.js), environmental (.gitignore), or cosmetic (README.md).

Thanks @edthorne I'm not getting much time to maintain this right now so I've made you a contributor.

Is this going to get merged soon? I really want to use this with angular 1.3.

Will this get merged soon? Wanting to use this with Angular 1.3 as well...thank you! :)

authors: Choc13 daniellecs edthorne kuhnza

license: mit


text:
[feature request] Connect by ip address

Hi,
I've installed this module, but only support connecting through USB device. Can have this integration supporting LAN ip address?
Best Regards,

No.

authors: fapgomes kukulich


text:
fix: replaced the use of getTarget() with getTargetName()

Fixes #44

I have tested that this works. The user block notification was sent correctly.

Thank you! Merged in :)

authors: harshkhandeparkar kulttuuri

repo: kulttuuri/SlackNotifications


text:
Allow adding badge name depending on badge type

For artists/exhibitors/press, the ability to add a badge name with manager override (for at-con registration).
Note that for regular attendees, you should not be able to add a badge name when registering At-Con, but that would be desirable for specialty badges (industry, exhibitors, etc).
Need to figure out an elegant way to handle that.

It's very likely that we'll allow setting badge names for at-con registrations next year, which makes the security side of this moot - just need to add badge name to the at-con screen.

Closed in e4f47be55fc0f9e95a513fee50c901b2d332e50e

repo: kumoregdev/kumoreg


text:
Unknown Error in IDR Step

Hello,
I am attempting to run your ATAC-Seq pipeline, just on some sample ENCODE data at the moment (thank you for sharing it!). I'm consistently running into an error at the IDR step that I'm not sure how to interpret and would appreciate any insight you have into what is going wrong.
Thank you!
Full log:
https://gist.github.com/smuchnik/f496b3a880fed9a06cbf51e6904f4af2
Error message:
Task failed:
Program & line     : '/home/sm2576/project/ATAC/atac_dnase_pipelines/modules/callpeak_idr.bds', line 74
Task Name          : 'idr2 rep1-pr'
Task ID            : 'atac.bds.20170605_132057_849/task.callpeak_idr.idr2_rep1_pr.line_74.id_43'
Task PID           : '8589'
Task hint          : 'idr --samples /ycga-gpfs/project/fas/sestan/sm2576/ATAC/screen_test5/out/peak/macs2/pseudo_reps/rep1/pr1/Test_Read1.trim.PE2SE.nodup.pr1.tn5.pf.pval0.1.500K.narrowPeak.gz /ycga-gpfs/project/fas/sestan/sm2576/ATAC/screen_test5/out/peak/macs2/pseudo_reps/rep1/pr2/Test_Read1.trim.PE2SE.nodup.pr2.tn5.pf'
Task resources     : 'cpus: -1	mem: -1.0 B	wall-timeout: 8640000'
State              : 'ERROR'
Dependency state   : 'ERROR'
Retries available  : '1'
Input files        : '[/ycga-gpfs/project/fas/sestan/sm2576/ATAC/screen_test5/out/peak/macs2/pseudo_reps/rep1/pr1/Test_Read1.trim.PE2SE.nodup.pr1.tn5.pf.pval0.1.500K.narrowPeak.gz, /ycga-gpfs/project/fas/sestan/sm2576/ATAC/screen_test5/out/peak/macs2/pseudo_reps/rep1/pr2/Test_Read1.trim.PE2SE.nodup.pr2.tn5.pf.pval0.1.500K.narrowPeak.gz, /ycga-gpfs/project/fas/sestan/sm2576/ATAC/screen_test5/out/peak/macs2/rep1/Test_Read1.trim.PE2SE.nodup.tn5.pf.pval0.1.500K.narrowPeak.gz]'
Output files       : '[/ycga-gpfs/project/fas/sestan/sm2576/ATAC/screen_test5/out/peak/macs2/idr/pseudo_reps/rep1/screen_test5_rep1-pr.IDR0.1.filt.narrowPeak.gz, /ycga-gpfs/project/fas/sestan/sm2576/ATAC/screen_test5/out/peak/macs2/idr/pseudo_reps/rep1/screen_test5_rep1-pr.unthresholded-peaks.txt.png, /ycga-gpfs/project/fas/sestan/sm2576/ATAC/screen_test5/out/peak/macs2/idr/pseudo_reps/rep1/screen_test5_rep1-pr.IDR0.1.log.txt, /ycga-gpfs/project/fas/sestan/sm2576/ATAC/screen_test5/out/peak/macs2/idr/pseudo_reps/rep1/screen_test5_rep1-pr.unthresholded-peaks.txt.gz, /ycga-gpfs/project/fas/sestan/sm2576/ATAC/screen_test5/out/peak/macs2/idr/pseudo_reps/rep1/screen_test5_rep1-pr.IDR0.1.filt.12-col.bed.gz]'
Script file        : '/ycga-gpfs/project/fas/sestan/sm2576/ATAC/screen_test5/atac.bds.20170605_132057_849/task.callpeak_idr.idr2_rep1_pr.line_74.id_43.sh'
Exit status        : '1'
Program            :
	# SYS command. line 76

	 if [[ -f $(which conda) && $(conda env list | grep bds_atac_py3 | wc -l) != "0" ]]; then source activate bds_atac_py3; sleep 5; fi;  export PATH=/home/sm2576/project/ATAC/atac_dnase_pipelines/.:/home/sm2576/project/ATAC/atac_dnase_pipelines/modules:/home/sm2576/project/ATAC/atac_dnase_pipelines/utils:${PATH}:/bin:/usr/bin:/usr/local/bin:${HOME}/.bds; set -o pipefail; STARTTIME=$(date +%s)

	# SYS command. line 78

	 idr --samples /ycga-gpfs/project/fas/sestan/sm2576/ATAC/screen_test5/out/peak/macs2/pseudo_reps/rep1/pr1/Test_Read1.trim.PE2SE.nodup.pr1.tn5.pf.pval0.1.500K.narrowPeak.gz /ycga-gpfs/project/fas/sestan/sm2576/ATAC/screen_test5/out/peak/macs2/pseudo_reps/rep1/pr2/Test_Read1.trim.PE2SE.nodup.pr2.tn5.pf.pval0.1.500K.narrowPeak.gz --peak-list /ycga-gpfs/project/fas/sestan/sm2576/ATAC/screen_test5/out/peak/macs2/rep1/Test_Read1.trim.PE2SE.nodup.tn5.pf.pval0.1.500K.narrowPeak.gz --input-file-type narrowPeak \
				--output-file /ycga-gpfs/project/fas/sestan/sm2576/ATAC/screen_test5/out/peak/macs2/idr/pseudo_reps/rep1/screen_test5_rep1-pr.unthresholded-peaks.txt --rank p.value --soft-idr-threshold 0.1 \
				--plot --use-best-multisummit-IDR --log-output-file /ycga-gpfs/project/fas/sestan/sm2576/ATAC/screen_test5/out/peak/macs2/idr/pseudo_reps/rep1/screen_test5_rep1-pr.IDR0.1.log.txt

	# SYS command. line 82

	 idr_thresh_transformed=$(awk -v p=0.1 'BEGIN{print -log(p)/log(10)}')

	# SYS command. line 85

	 awk 'BEGIN{OFS="\t"} $12>='"${idr_thresh_transformed}"' {if ($2<0) $2=0; print $1,$2,$3,$4,$5,$6,$7,$8,$9,$10,$11,$12,"0"}' /ycga-gpfs/project/fas/sestan/sm2576/ATAC/screen_test5/out/peak/macs2/idr/pseudo_reps/rep1/screen_test5_rep1-pr.unthresholded-peaks.txt \
				| sort | uniq | sort -k7n,7n | gzip -nc > /ycga-gpfs/project/fas/sestan/sm2576/ATAC/screen_test5/out/peak/macs2/idr/pseudo_reps/rep1/screen_test5_rep1-pr.IDR0.1.13-col.bed.gz

	# SYS command. line 88

	 zcat /ycga-gpfs/project/fas/sestan/sm2576/ATAC/screen_test5/out/peak/macs2/idr/pseudo_reps/rep1/screen_test5_rep1-pr.IDR0.1.13-col.bed.gz | awk 'BEGIN{OFS="\t"} {print $1,$2,$3,$4,$5,$6,$7,$8,$9,$10}' | gzip -nc > /ycga-gpfs/project/fas/sestan/sm2576/ATAC/screen_test5/out/peak/macs2/idr/pseudo_reps/rep1/screen_test5_rep1-pr.IDR0.1.narrowPeak.gz

	# SYS command. line 89

	 zcat /ycga-gpfs/project/fas/sestan/sm2576/ATAC/screen_test5/out/peak/macs2/idr/pseudo_reps/rep1/screen_test5_rep1-pr.IDR0.1.13-col.bed.gz | awk 'BEGIN{OFS="\t"} {print $1,$2,$3,$4,$5,$6,$7,$8,$9,$10,$11,$12}' | gzip -nc > /ycga-gpfs/project/fas/sestan/sm2576/ATAC/screen_test5/out/peak/macs2/idr/pseudo_reps/rep1/screen_test5_rep1-pr.IDR0.1.12-col.bed.gz

	# SYS command. line 91

	 bedtools intersect -v -a <(zcat -f /ycga-gpfs/project/fas/sestan/sm2576/ATAC/screen_test5/out/peak/macs2/idr/pseudo_reps/rep1/screen_test5_rep1-pr.IDR0.1.13-col.bed.gz) -b <(zcat -f /ycga-gpfs/project/fas/sestan/sm2576/ATAC/genome_data/hg38/hg38.blacklist.bed.gz) | grep -P 'chr[\dXY]+[ \t]' | awk 'BEGIN{OFS="\t"} {if ($5>1000) $5=1000; print $0}' | gzip -nc > /ycga-gpfs/project/fas/sestan/sm2576/ATAC/screen_test5/out/peak/macs2/idr/pseudo_reps/rep1/screen_test5_rep1-pr.IDR0.1.filt.13-col.bed.gz

	# SYS command. line 92

	 zcat /ycga-gpfs/project/fas/sestan/sm2576/ATAC/screen_test5/out/peak/macs2/idr/pseudo_reps/rep1/screen_test5_rep1-pr.IDR0.1.filt.13-col.bed.gz | awk 'BEGIN{OFS="\t"} {print $1,$2,$3,$4,$5,$6,$7,$8,$9,$10}' | gzip -nc > /ycga-gpfs/project/fas/sestan/sm2576/ATAC/screen_test5/out/peak/macs2/idr/pseudo_reps/rep1/screen_test5_rep1-pr.IDR0.1.filt.narrowPeak.gz

	# SYS command. line 93

	 zcat /ycga-gpfs/project/fas/sestan/sm2576/ATAC/screen_test5/out/peak/macs2/idr/pseudo_reps/rep1/screen_test5_rep1-pr.IDR0.1.filt.13-col.bed.gz | awk 'BEGIN{OFS="\t"} {print $1,$2,$3,$4,$5,$6,$7,$8,$9,$10,$11,$12}' | gzip -nc > /ycga-gpfs/project/fas/sestan/sm2576/ATAC/screen_test5/out/peak/macs2/idr/pseudo_reps/rep1/screen_test5_rep1-pr.IDR0.1.filt.12-col.bed.gz

	# SYS command. line 95

	 gzip -f /ycga-gpfs/project/fas/sestan/sm2576/ATAC/screen_test5/out/peak/macs2/idr/pseudo_reps/rep1/screen_test5_rep1-pr.unthresholded-peaks.txt

	# SYS command. line 96

	 rm -f /ycga-gpfs/project/fas/sestan/sm2576/ATAC/screen_test5/out/peak/macs2/idr/pseudo_reps/rep1/screen_test5_rep1-pr.IDR0.1.13-col.bed.gz /ycga-gpfs/project/fas/sestan/sm2576/ATAC/screen_test5/out/peak/macs2/idr/pseudo_reps/rep1/screen_test5_rep1-pr.IDR0.1.filt.13-col.bed.gz

	# SYS command. line 98

	 TASKTIME=$[$(date +%s)-${STARTTIME}]; echo "Task has finished (${TASKTIME} seconds)."

Fatal error: /home/sm2576/project/ATAC/atac_dnase_pipelines/atac.bds, line 1277, pos 2. Task/s failed.
Creating checkpoint file: Config or command line option disabled checkpoint file creation, nothing done.

Can I see files in /ycga-gpfs/project/fas/sestan/sm2576/ATAC/screen_test5/out/peak/macs2/idr/pseudo_reps/rep1?
$ ls -l /ycga-gpfs/project/fas/sestan/sm2576/ATAC/screen_test5/out/peak/macs2/idr/pseudo_reps/rep1

Sure, that folder contains the following:
total 256
-rw-r--r-- 1 sm2576 sestan    20 Jun  5 13:55 screen_test5_rep1-pr.IDR0.1.12-col.bed.gz
-rw-r--r-- 1 sm2576 sestan    20 Jun  5 13:55 screen_test5_rep1-pr.IDR0.1.13-col.bed.gz
-rw-r--r-- 1 sm2576 sestan    20 Jun  5 13:55 screen_test5_rep1-pr.IDR0.1.filt.13-col.bed.gz
-rw-r--r-- 1 sm2576 sestan    20 Jun  5 13:55 screen_test5_rep1-pr.IDR0.1.narrowPeak.gz
-rw-r--r-- 1 sm2576 sestan 12642 Jun  5 13:55 screen_test5_rep1-pr.unthresholded-peaks.txt
-rw-r--r-- 1 sm2576 sestan 88898 Jun  5 13:55 screen_test5_rep1-pr.unthresholded-peaks.txt.noalternatesummitpeaks.png

It looks like none of the peaks passed IDR threshold of 0.1. Can you check the following? Can you also post or email me /ycga-gpfs/project/fas/sestan/sm2576/ATAC/screen_test5/out/peak/macs2/idr/pseudo_reps/rep1/screen_test5_rep1-pr.unthresholded-peaks.txt?
$ idr_thresh_transformed=$(awk -v p=0.1 'BEGIN{print -log(p)/log(10)}')

$ awk 'BEGIN{OFS="\t"} $12>='"${idr_thresh_transformed}"' {if ($2<0) $2=0; print $1,$2,$3,$4,$5,$6,$7,$8,$9,$10,$11,$12,"0"}' \
	/ycga-gpfs/project/fas/sestan/sm2576/ATAC/screen_test5/out/peak/macs2/idr/pseudo_reps/rep1/screen_test5_rep1-pr.unthresholded-peaks.txt \
	| sort | uniq | sort -k7n,7n | wc -l

Ah I see, that makes sense. Thank you!


text:
[Documentation Bug]: Games section of the README.md file looks so unorganized and messy.

Describe the bug ✍
Games section of the README.md file looks so messy due to games being unaligned and unorganized, hence giving bad impression of the project. I will organize the README.md file and its games section to enhance the documentation of project.
@kunjgit please assign this issue to me.
Provide step by step information reproduce the bug 📄
Open README.md file
Select program in which you are contributing
GSSoC24
Code of Conduct

[X] I follow CONTRIBUTING GUIDELINE of this project.

Hey @PRASANNA-THE-PRASANN1 , You can't have another issue before completing the previous one 😀
you already have the following 1 open issues 👀 ! :
#4978

Hey @PRASANNA-THE-PRASANN1 ! Thank you so much for your raising the issue💗
It’s all yours, you can come anytime again and make some contributions! 🚀
Alone, we can do little, but together we can do so much! 😇

Hey @PRASANNA-THE-PRASANN1 !
Thank you for raising an issue 💗
You can self assign the issue by commenting /assign in comment 😀
Make sure you follow CODE OF CONDUCT and CONTRIBUTING GUIDELINES 🚀
Don’t Forget to ⭐ our GameZone🎮
Make sure you join our Discord🕹

repo: kunjgit/GameZone


text:
remove old containers - storage waste

Environment

OS: Ubuntu 22.04
Kubernetes/K3s: v1.30.4+k3s1
AWX Operator: 2.19.1

how to remove old unused pods?
Description
after many updates hdd space become low
I used k3s crictl rmi --prune - it cleaned some space
but old pods are still in a list
root@awx:~# k3s kubectl get pods --all-namespaces
NAMESPACE      NAME                                               READY   STATUS        RESTARTS       AGE
awx            awx-migration-24.0.0-dctpd                         0/1     Completed     0              168d
awx            awx-migration-24.1.0-nwlnf                         0/1     Completed     0              147d
awx            awx-migration-24.2.0-4hcs8                         0/1     Completed     0              133d
awx            awx-migration-24.3.1-8jz95                         0/1     Completed     0              118d
awx            awx-migration-24.4.0-rcg5c                         0/1     Completed     0              93d
awx            awx-migration-24.5.0-b86rb                         0/1     Completed     0              85d
awx            awx-migration-24.6.0-sc654                         0/1     Completed     0              69d
awx            awx-migration-24.6.1-gktt9                         0/1     Completed     0              13h
awx            awx-operator-controller-manager-745b55d94b-8xp9h   2/2     Running       1 (25s ago)    13h
awx            awx-postgres-15-0                                  1/1     Running       7 (21d ago)    133d
awx            awx-task-7fc7b48d56-7wkh2                          4/4     Running       0              13h
awx            awx-web-588b89b466-jhz79                           3/3     Running       0              13h
cert-manager   cert-manager-cainjector-5fd6444f95-dmlxt           1/1     Running       0              13h
cert-manager   cert-manager-d894bbbd4-mvx72                       1/1     Running       0              13h
cert-manager   cert-manager-webhook-869674f96f-488pd              1/1     Running       0              13h
kube-system    coredns-6799fbcd5-57n7s                            1/1     Running       9 (21d ago)    189d
kube-system    helm-install-traefik-crd-p2bhd                     0/1     Completed     0              15s
kube-system    helm-install-traefik-lwjpw                         0/1     Completed     0              15s
kube-system    local-path-provisioner-6795b5f9d8-t59c5            1/1     Running       0              15s
kube-system    local-path-provisioner-6c86858495-tsc2p            1/1     Terminating   10 (21d ago)   168d
kube-system    metrics-server-54fd9b65b-w5gpb                     1/1     Running       8 (21d ago)    133d
kube-system    svclb-traefik-05fee054-dp5vj                       2/2     Running       0              14s
kube-system    traefik-7d5f6474df-bcm7h                           1/1     Running       6 (21d ago)    118d

awx@awx:~$ kubectl -n awx get awx,all,ingress,secrets,issuer
NAME                      AGE
awx.awx.ansible.com/awx   189d

NAME                                                   READY   STATUS      RESTARTS      AGE
pod/awx-migration-24.0.0-dctpd                         0/1     Completed   0             168d
pod/awx-migration-24.1.0-nwlnf                         0/1     Completed   0             147d
pod/awx-migration-24.2.0-4hcs8                         0/1     Completed   0             133d
pod/awx-migration-24.3.1-8jz95                         0/1     Completed   0             118d
pod/awx-migration-24.4.0-rcg5c                         0/1     Completed   0             93d
pod/awx-migration-24.5.0-b86rb                         0/1     Completed   0             85d
pod/awx-migration-24.6.0-sc654                         0/1     Completed   0             69d
pod/awx-migration-24.6.1-gktt9                         0/1     Completed   0             14h
pod/awx-operator-controller-manager-745b55d94b-8xp9h   2/2     Running     1 (24m ago)   14h
pod/awx-postgres-15-0                                  1/1     Running     7 (22d ago)   133d
pod/awx-task-7fc7b48d56-7wkh2                          4/4     Running     0             14h
pod/awx-web-588b89b466-jhz79                           3/3     Running     0             14h

NAME                                                      TYPE        CLUSTER-IP     EXTERNAL-IP   PORT(S)    AGE
service/awx-operator-controller-manager-metrics-service   ClusterIP   10.43.201.65   <none>        8443/TCP   189d
service/awx-postgres-15                                   ClusterIP   None           <none>        5432/TCP   168d
service/awx-service                                       ClusterIP   10.43.86.221   <none>        80/TCP     189d

NAME                                              READY   UP-TO-DATE   AVAILABLE   AGE
deployment.apps/awx-operator-controller-manager   1/1     1            1           189d
deployment.apps/awx-task                          1/1     1            1           189d
deployment.apps/awx-web                           1/1     1            1           189d

NAME                                                         DESIRED   CURRENT   READY   AGE
replicaset.apps/awx-operator-controller-manager-589cdd869b   0         0         0       180d
replicaset.apps/awx-operator-controller-manager-59b86c6fb    0         0         0       168d
replicaset.apps/awx-operator-controller-manager-6458cd4798   0         0         0       147d
replicaset.apps/awx-operator-controller-manager-66d859dc9f   0         0         0       118d
replicaset.apps/awx-operator-controller-manager-745b55d94b   1         1         1       14h
replicaset.apps/awx-operator-controller-manager-7469875f45   0         0         0       189d
replicaset.apps/awx-operator-controller-manager-7875f768df   0         0         0       69d
replicaset.apps/awx-operator-controller-manager-7bd778dbbc   0         0         0       93d
replicaset.apps/awx-operator-controller-manager-7d497b7874   0         0         0       85d
replicaset.apps/awx-operator-controller-manager-9874d5cfc    0         0         0       133d
replicaset.apps/awx-task-57ddbdf689                          0         0         0       168d
replicaset.apps/awx-task-68889c684d                          0         0         0       93d
replicaset.apps/awx-task-6968cbc89                           0         0         0       118d
replicaset.apps/awx-task-6b998cd649                          0         0         0       189d
replicaset.apps/awx-task-6dbfb7d946                          0         0         0       85d
replicaset.apps/awx-task-6ff56fb6bf                          0         0         0       133d
replicaset.apps/awx-task-7767b6c657                          0         0         0       180d
replicaset.apps/awx-task-7d4c4bdb5                           0         0         0       147d
replicaset.apps/awx-task-7fc7b48d56                          1         1         1       14h
replicaset.apps/awx-task-f9644bbf9                           0         0         0       69d
replicaset.apps/awx-web-549f9f88f5                           0         0         0       189d
replicaset.apps/awx-web-588b89b466                           1         1         1       14h
replicaset.apps/awx-web-5db56bf6b6                           0         0         0       69d
replicaset.apps/awx-web-677486c9                             0         0         0       118d
replicaset.apps/awx-web-695f968f48                           0         0         0       93d
replicaset.apps/awx-web-6bcbd5c8ff                           0         0         0       180d
replicaset.apps/awx-web-74f497f79                            0         0         0       133d
replicaset.apps/awx-web-7c59b86d44                           0         0         0       85d
replicaset.apps/awx-web-c6bdf6549                            0         0         0       147d
replicaset.apps/awx-web-d8848656c                            0         0         0       168d

NAME                               READY   AGE
statefulset.apps/awx-postgres-15   1/1     168d

NAME                             STATUS     COMPLETIONS   DURATION   AGE
job.batch/awx-migration-24.0.0   Complete   1/1           8s         168d
job.batch/awx-migration-24.1.0   Complete   1/1           7s         147d
job.batch/awx-migration-24.2.0   Complete   1/1           7s         133d
job.batch/awx-migration-24.3.1   Complete   1/1           15s        118d
job.batch/awx-migration-24.4.0   Complete   1/1           7s         93d
job.batch/awx-migration-24.5.0   Complete   1/1           8s         85d
job.batch/awx-migration-24.6.0   Complete   1/1           12s        69d
job.batch/awx-migration-24.6.1   Complete   1/1           8s         14h

NAME                                    CLASS     HOSTS                    ADDRESS           PORTS     AGE
ingress.networking.k8s.io/awx-ingress   traefik   awx.webhostingzone.org   162.247.152.240   80, 443   189d

NAME                                  TYPE                DATA   AGE
secret/awx-admin-password             Opaque              1      189d
secret/awx-app-credentials            Opaque              3      189d
secret/awx-broadcast-websocket        Opaque              1      189d
secret/awx-issuer-account-key         Opaque              1      189d
secret/awx-postgres-configuration     Opaque              6      168d
secret/awx-receptor-ca                kubernetes.io/tls   2      189d
secret/awx-receptor-work-signing      Opaque              2      189d
secret/awx-secret-key                 Opaque              1      189d
secret/awx-secret-tls                 kubernetes.io/tls   2      189d
secret/redhat-operators-pull-secret   Opaque              1      189d

NAME                                READY   AGE
issuer.cert-manager.io/awx-issuer   True    189d

@amg-web
Hi, you can safely remove all jobs which can be found by kubectl -n awx get job, and all replicasets which has DESIRED=0.
However, it is unlikely that these are using a lot of disk space.
If removing them do not increase the free space, you may want to use the du command something like du -sh /* | sort -hr to identify the directory which consumes a lot of disk space.

authors: amg-web kurokobo


text:
Overide Content-Type

For some reason I send logs as json and due to this fact I change with awareness the configuration of headers and I set  Content-Type: application/json, but in the request I see Content-Type: text/plain, application/json. From my point of view this behavior is incorrect, because I want to change configuration and I don not want add new Content-Type.

If the format of message is json the Content-Type is application/json

repo: kutuluk/loglevel-plugin-remote


text:
Notebook: Save results as data set

After running all transformations, the results have to be saved in a dedicated format. In the beginning we should provide CSV, Parquet and JSON.
Depends on #45

@mattigrthr is this request still on the todo list? If so, I'm happy to take a crack at it.

Hi @SamDuan, yes, this one is still on the TODO list! 💯 Great, you'll be tackling this. 💪🏽

@mattigrthr couple questions about this feature:

Shall I just add another section at the end of the notebook, showing how to export result dataframe as CSV, Parquet and Json? Or you are thinking something else?
And create a folder named e.g. result under kuwala?

@SamDuan, yes, that's exactly what I was thinking as well. CSV, Parquet, and JSON are the most common formats. Also, having another result folder under kuwala in the Jupyter environment is a good way. The result folder should be structured with subdirectories according to which notebook the files belong to IMO, and then people can easily download the files from there.
In the future, we can have more connectors to destinations such as data warehouses or S3. But these would be separate issues.

authors: SamDuan mattigrthr

repo: kuwala-io/kuwala


text:
Duplicate collection in treeview storage/realtime

How to reproduce?

go to http://localhost:3000/#!/data/kuzzle-bo-testindex/editable-collection/watch
click on subscribe
open an other window on  http://localhost:3000/#!/data/kuzzle-bo-testindex/

Collection editable-collection is now in storage and in realtime. We have to exclude from realtime collections already in present in storage.

Right, but this information comes from the Kuzzle Server, right? Shouldn't be a Server's concern to exclude the realtime collections if they are also persisted?

I'm not really sure... Because if the collection is duplicate in Storage AND in realtime, the front-end developer can choose to merge or not. But if the merge comes from the server, the front-end developer can't know the list of all realtime collections.

We can add another icon for this kind of collection: there are persisted collections with realtime activity

authors: AnthonySendra stafyniaksacha xbill82

repo: kuzzleio/kuzzle-backoffice


text:
Update README.md

Hente fra main

En kommentar

Hmm

repo: kvapehe/nettsidetest


text:
Design criteria

IMO, an interop layer should have the following qualities:

Lightweight
The library should be small, compile quickly, and be easy to understand.
Zero-cost
Adopting the library should not introduce additional run-time overhead compared to exposing internal types.
Un-opinionated
No system to be interoperated with should feel like a second-class citizen. Reasonable differing conventions should have equal degrees of support.
Safe
The library should prevent nonsensical or unintended operations.

This appears to be a strong case for new types in the library. The existing built-in aliases could then go  into a raw submodule (not sure about it, still investigating). We'll try to derive as much stuff as possible, and also implement the Into/From fixed arrays, but nothing more, keeping it lightweight.
It would be great to get some preliminary opinions from @brendanzab, @sebcrozet, and @nical about providing Into/From these new types from nalgebra/cgmath/euclid respectively:

Sounds reasonable/useful! I'm ok with it.
I don't want extra dependencies! Only behind a feature gate.
I'm only going to use the built-in defines without directly depending on mint.
I have other conditions/requirements for adoption. (please clarify)
One more standard? I don't want it.

I'll elaborate on why the pre-existing approach using type aliases does not fully satisfy the "safe" quality:
Type aliases cannot distinguish between row- and column-major matrices, which are easily confused in the absence of stronger types. Similar story for points vs. vectors, 3-vectors vs. euler angles, 4-vectors vs. quaternions, and so forth. This limits the expressiveness of interfaces defined in terms of mint, and adds substantial risk of a math library unaware of or in disagreement with mint's conventions silently doing the wrong thing when used with a mint-aware interface.
This issue can be (and in the current library, has been) worked around to some extent by switching between tuples and arrays. This is an incomplete solution because it is detrimental to type error clarity, makes conversions to/from types with simpler internal representations awkward to define, and makes the library itself less obvious (why is X a tuple and Y an array?). In principle types can be made arbitrarily distinct with sufficiently elaborate tuple shenanigans, but type aliases are only beneficial in the first place insofar as that they map directly into otherwise-reasonable types.

@Ralith once new types are introduced, it's quite difficult to draw the line between what's provided and what's not. E.g. should we implement Add<Point, Vector>? If we don't, no other library would be able to do it, hence imposing a permanent ergonomic penalty on using the types directly.

As soon as you have structures and methods, you've added yet another math library to the lot.

I think the line is very clear: mint types should have no operations but into and from. They should be immediately converted to or away from at interface boundaries.

@Ralith what about conversion between types within mint itself? E.g. row-major into column-major matrix.

Those feel in-scope to me, as a user might want to compose a library that speaks row-major with one that speaks column-major.

one that speaks quaternions with one that speaks matrices

That would involve quite a bit of computation, which is out of scope.

That seems like a reasonable decision. Thinking about it more, that might have been the start of a slippery slope (lib A has decomposed transforms and lib B wants a mat4!).

authors: Ralith kvark nical

repo: kvark/mint


text:
i cant compile the game

Are you trying to code on Source Code (Haxe) or on the Downloaded Build (Lua)?
Source Code
Show an screenshot/video of your problem.

this is android
download pc version ;p

i want to port my mod on android
thats why i downloaded this

Kviks he meant that android can't compile so he have to use pc to compile because making a android.yml is hard for me and some people

You literally have to use lime test Android for it to work lol

You CAN'T compile the mobile version for pc

You can lol I literally tried that on my laptop it works 💀

You CAN'T compile the mobile version for pc
You can lol I literally tried that on my laptop it works 💀

authors: HafimieForever Noobandguestgang SnakDev bf244 kviks

repo: kviks/Psych-Engine-Android


text:
关于算法

感觉目前开发的算法是基于三方都明牌的情况下开发的，并不能像黑盒一样辅助人或者自己去完成斗地主游戏

目前的算法是暗牌的，在demo中加了上帝视角是为了让玩家方便看，但对AI是隐藏的。

@daochenzha 但是打了几场 比如我是地主，看对方两个农民的出牌策略感觉是知道是知道对方需要什么牌一样，经常出现喂牌的情况。而且感觉也能猜出来我的牌是什么。

@geekli 就像人类玩家一样，AI也可以一定程度上通过别人出过的牌来猜测别人的手牌。尤其是在游戏中后期，这个猜测可以非常准确，因此斗地主高手对局中往往需要进行“藏牌”的操作，以避免暴露自己的手牌。

authors: budaLi daochenzha geekli karoka

repo: kwai/DouZero


text:
IPython.qt: incompatible qt lib issue

/anaconda3/envs/klusta/lib/python2.7/site-packages/IPython/qt.py:13: ShimWarning: The IPython.qt package has been deprecated. You should import from qtconsole instead.
"You should import from qtconsole instead.", ShimWarning)
Cannot mix incompatible Qt library (version 0x40801) with this library (version 0x40805)
Aborted (core dumped):
Can this be b'coz of ubuntu 12.04 version when launching klusta?

As suggested  by @nippoo) it might be a KDE issue. I have not problem with ubuntu-gnome or using xfce.

you mean issue could be coz of launching klusta on 'xterm'?

I have the same problem on Ubuntu 16.04 with MATE desktop (GNOME-based).

There is a fix suggested in the thread indicated by @nippoo (two links further, there: https://github.com/ContinuumIO/anaconda-issues/issues/32). I didn't try to understand but the problem seems to be related to dbus (might be why mate is also affected)

see also https://groups.google.com/forum/#!topic/klustaviewas/oEzZaT9nY-A

authors: ablot michbad patelj65 rossant

repo: kwikteam/klusta


text:
Module not found error for zeta and classifier_free_guidance_pytorch

Module not found error for zeta and classifier_free_guidance_pytorch
To Reproduce
git clone this repo
pip install -r requirements.text
python rtx2_exzample.py
Expected behavior
a tensor like : (tensor([[[-0.1899, -0.2870,  0.4471,  ...,  0.8224,  0.1974,  0.5205],
[-0.0617,  0.2402,  0.7786,  ...,  0.3528,  0.4517,  0.2858],
[-0.1535, -0.4502,  0.4945,  ..., -0.0856,  0.5338,  0.1241],
...,
Screenshots
If applicable, add screenshots to help explain your problem.
Additional context
Add the zeta and classifier_free_guidance_pytorch  to requirements.txt
I

Upvote & Fund

We're using Polar.sh so you can upvote and help fund this issue.
We receive the funding once the issue is completed & confirmed by you.
Thank you in advance for helping prioritize & fund our backlog.

@DeeNihl thanks I made a mistake with the requirements

@DeeNihl try again pls

still missing classifier_free_guidance_pytorch but let me wipe and reclone to be sure

Tested, issue resolved

authors: DeeNihl kyegomez

repo: kyegomez/RT-X


text:
Migrate to ES2015

Use babel instead of ts-loader to compile our javascripts, as well as migrate to es2015 in place of typescript. Also remove relevant typescript options/config files/ignores

WIP currently, Mike broke a bunch of stuff. Fixing now

Nvm, that was me

repo: kyleholzinger/carp


text:
Fix list instances query

Description
Necessary adjustments due to changes introduced by https://github.com/kyma-project/control-plane/pull/1571.
Continuation of https://github.com/kyma-project/control-plane/pull/1655.
Changes proposed in this pull request:

change db queries to fetch shoot names from last operation (instead of extraction from dashboard URL),
adjust tests,
remove unnecessary code.

This PR is a quick fix for issues related to fetching runtimes, kubeconfig from kcp cli.
Improvement to implement in future: Instance and InstanceDTO should contain shootName field.
Related issue(s)
#1571, #1655

/hold

/retest

/cla-recheck

repo: kyma-project/control-plane


text:
Control Plane Agent POC with dapr

Description
Changes proposed in this pull request:

...
...
...

Related issue(s)

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.

authors: CLAassistant crabtree


text:
Implement deploy skr webhook

Proposed changes:
Implement deploy SKR webhook

/test all

/test pre-main-kyma-watcher-kcp-tests

/test pre-main-kyma-watcher-kcp-tests

/test all

/test pre-main-kyma-watcher-kcp-lint

/retest-required

/test all

/test pre-main-kyma-watcher-kcp-tests

The flow looks great! 🔥
Some minor comments though

/test pre-main-kyma-watcher-kcp-tests

repo: kyma-project/kyma-watcher


text:
Self-Monitor monitoring

Description
The new self-monitor integration of https://github.com/kyma-project/telemetry-manager/issues/42 needs to be observable in order to operate it.
Criterias

Assure that manager exposes metrics about communication to the self-monitor
Have operational setup for SAP managed offering

Reasons

Attachments

Release Notes

The new metrics will be rolled out in 1.16

authors: a-thaler skhalash

repo: kyma-project/telemetry-manager


text:
Adds ability to cd into last changed-to directory with ZZ

Adds a new keymap ZQ to exit fx without changing the directory
Adds to README.md a tip to add the function to better integrate with unix shells

Interesting. I gave this a try, and found the following:

Even if ZZ does not work, it does not have to exit: The terminal screen should be cleaned up when exit.  It will go like this:

                                        KeyCode::Char('Z') => {
                                            //To communicate with the calling shell function for
                                            //subsequent use by cd
                                            if let Some(path) = state.lwd_file.to_owned() {
                                                std::fs::write(
                                                    path,
                                                    state.current_dir.to_str().unwrap(),
                                                )?;

                                                break 'main;
                                            } else {
                                                print_warning(
                                                    "env 'SHELL_PID' is not set.",
                                                    state.layout.y,
                                                );
                                            }
                                        }

(I can't push to your PR branch, so forgive me just pasting the code)

As I set the bash function in .bashrc, I got this error message: find: invalid argument +1s' to -mtime'. (I COULD exit to the current directory though) How can we fix this? (And is this necessary?)

Most important thing is, should we change ZZ's role? As felix has used ZZ to exit to the same directory for a long time, users would be confused if ZZ does not work as they intend. Though I admit this is more vim-like way, I think it'd be better to keep ZZ as is, and use e.g. :wq (it must be a new key-mapping to not confuse) instead to realize this function: It must be a new key-mapping to not confuse.

what is the status of this? its a really neat feature

Sorry, this completely slipped my mind. I'll address @kyoheiu 's comments and push my changes.

@kyoheiu Updated the PR with changes in line with your comments.
I have added couple other enhancements:

I've added a toggle to allow users to control whether or not to match the keybinding behavior of VIM. With that behavior switched off by default for backward-compatibility.
I've optimized the shell integration shell script.

I've tested my changes under MacOS, Linux, Zsh and Bash.

@kyoheiu I have also added you the collaborators on my fork of felix. I'm not sure whether this helps with the fact that you can't edit the PR, but you can test and feedback me.

Tested on Void Linux - Bash. Works perfectly.

Cool, it seems great! I'll test this PR in this weekend.

I tried this PR on my Arch Linux and when exiting by ZQ, received error message, similar to before:
bash: bc: command not found
find: invalid argument `+' to `-mmin'

(though I succeeded to exit to the current dir)
I set source <(command fx --init) at the end of .bashrc. Could you tell me if something is wrong?

@kyoheiu Seems I was wrong in assuming that bc comes pre-installed (Apparently it does not on Archlinux, while it does on the systems I'd tested on). I'll replace that arithmetic expression with its result which is static anyways ~ 0.02. I only wrote it that way as a giveaway to my intent at the expense of the repeated cheap calculation.
The whole purpose of it is to remove any leftover LWD files everytime the fx function runs. I believe this might not be necessary as I can move that logic to run every time the fx --init is sourced instead; i.e every time an interactive shell is run.

@kyoheiu Updated the PR

Works like a charm! Thank you. Looks good to me.

authors: ElSamhaa kyoheiu nate-sys

repo: kyoheiu/felix


text:
Add #[track_caller] for better panic error messages

Before:
Error message: panicked at 'already borrowed: BorrowMutError', gc-arena-0.2.0/src/gc_cell.rs:62:29

After: it shows the line that actually tried calling read()/write().
Error message: panicked at 'already borrowed: BorrowMutError', core/src/avm1/activation.rs:1186:48

Should help a bit with pinpointing error sources for library users :)

Yeah this makes sense to have.

repo: kyren/gc-arena


text:
🛑 reservas.mudic.es is down

In 3f23f91, reservas.mudic.es (https://reservas.mudic.es) was down:

HTTP code: 0
Response time: 0 ms

Resolved: reservas.mudic.es is back up in fb8dd69 after 35 minutes.

repo: kyryl-bogach/upptime


text:
Create in Auth module a timeout to resolve response when it is not received from Storehouse

Original issue opened by @gleybersonandrade at https://github.com/kytos/kytos/issues/981.
When the Auth module was created, a while loop was used to wait for the response from the Storehouse, but if it is not received, an infinite loop can occur.
while True:
      time.sleep(0.1)
      if response:
            break

We have to find a method to create a timeout or something like this to resolve the response when it is not received.

This no longer applies. On core Auth is now backed by MongoDB users collection.

authors: ajoaoff viniarck

repo: kytos-ng/kytos


text:
bug when editing the EVC to setup the queue ID

Hi,
When editing the EVC to setup a QueueID, we end up getting the EVC active=False and the following error on the logs:
2023-07-03 13:57:42,274 - INFO [werkzeug] [_internal.py:225:_log] (Thread-119448) 127.0.0.1 - - [03/Jul/2023 13:57:42] "POST /api/kytos/pathfinder/v2/ HTTP/1.1" 200 -
2023-07-03 13:57:42,344 - INFO [kytos.napps.kytos/flow_manager] [main.py:603:_send_flow_mods_from_request] (Thread-119449) Send FlowMod from request dpid: 00:00:00:00:00:40:00:04, command: add, force: False, flows_dict: {'flows': [{'match': {'in_port': 32, 'dl_vlan': 1126}, 'cookie': 12282834762993824579, 'actions': [{'action_type': 'set_vlan', 'vlan_id': 346}, {'action_type': 'output', 'port': 1}, {'action_type': 'set_queue', 'queue_id': '0'}], 'priority': 20000}, {'match': {'in_port': 1, 'dl_vlan': 346}, 'cookie': 12282834762993824579, 'actions': [{'action_type': 'set_vlan', 'vlan_id': 1126}, {'action_type': 'output', 'port': 32}, {'action_type': 'set_queue', 'queue_id': '0'}], 'priority': 20000}], 'force': False}
2023-07-03 13:57:42,371 - ERROR [kytos.napps.kytos/mef_eline] [evc.py:726:deploy_to_path] (Thread-119445) Error deploying EVC EVC(756523c310f343, Vlan_344_MIA-Loop_SCL) when calling flow_manager: {"code":400,"description":"FlowMod.instructions - ListOfInstruction pack error: InstructionApplyAction.actions - ListOfActions pack error: ActionSetQueue.queue_id - Expected UBInt32, found value \"0\" of type str","name":"Bad Request"}
2023-07-03 13:57:42,363 - INFO [werkzeug] [_internal.py:225:_log] (Thread-119449) 127.0.0.1 - - [03/Jul/2023 13:57:42] "POST /api/kytos/flow_manager/v2/flows/00:00:00:00:00:40:00:04 HTTP/1.1" 400 -

Here is the edition was done in the interface:

How to reproduce:

Run Kytos and Mininet (any topology). Then enable everything
Create an EVC inter-switch (EVPL)
Click to list the EVCs and click on the EVC created before to edit it
Change the "Queue"

Expected result: it should change the EVC queue ID
Actual result: the EVC gets innactivated and an error is displayed on the logs

Suggestion: besides fixing the type error on UI, I believe we should also be more robust when handling the data inside EVC model before sending out the FlowMod

@italovalcy thanks for reporting and catching this.
On 2023.1 (unreleased yet as you know) @rmotitsuki has improved and fixed the update payload, for instance trying to set queue_id: 1 works:

Since you managed to get a workaround via the API, do you think we can leave not to be backported? @rmotitsuki's UI fixes have improved many of the other updated fields too, since it would be a small change, and if you're willing to way it might be worth waiting for 2023.1 if you and the Ops team could still live with it in the meantime. Also both mef_eline and flow_manager have stronger validations:
❯ for evc in e616b22e2cd046; do curl -X PATCH http://127.0.0.1:8181/api/kytos/mef_eline/v2/evc/$evc -d '{"queue_id":"1"}' -H 'Content-type: application/json'; done
{"description":"The request body contains invalid API data. '1' is not of type 'integer' for field queue_id.","code":400}

❯ for evc in e616b22e2cd046; do curl -X PATCH http://127.0.0.1:8181/api/kytos/mef_eline/v2/evc/$evc -d '{"queue_id":12}' -H 'Content-type: application/json'; done
{"description":"The request body contains invalid API data. 12 is greater than the maximum of 7 for field queue_id.","code":400}

{
    "description": "FlowMod.instructions - ListOfInstruction pack error: InstructionApplyAction.actions - ListOfActions pack error: ActionSetQueue.queue_id - Expected UBInt32, found value \"1\" of type str",
    "code": 400
}

Although regarding unsetting the queue_id, FYI, I ended up hitting issue #347

authors: italovalcy viniarck