getting-started-issues: creating pod takes a long time / rpc error: code = DeadlineExceeded / PLEG is not healthy

Background info: I already have some prior experience with Docker and Kubernetes, now trying out k3s for the first time and having issues even with basic operations.
I created two new VMs with a clean &  minimal install of Centos 7 on x86_64 and updated it to the latest version 7.6.1810.
The only package that I installed was policycoreutils-python because it provides semanage command that the installation procedure uses in case SELinux is enabled.
Both VMs offer 2 CPU cores, 2 GB RAM and 20 GB disk space.
I installed k3s 0.5.0 using the curl-pipe-shell one-liner.
[root@k3s-node01 ~]# curl -sfL https://get.k3s.io | sh -
[INFO]  Finding latest release
[INFO]  Using v0.5.0 as release
[INFO]  Downloading hash https://github.com/rancher/k3s/releases/download/v0.5.0/sha256sum-amd64.txt
[INFO]  Skipping binary downloaded, installed k3s matches hash
[INFO]  Creating /usr/local/bin/kubectl symlink to k3s
[INFO]  Creating /usr/local/bin/crictl symlink to k3s
[INFO]  Creating killall script /usr/local/bin/k3s-killall.sh
[INFO]  Creating uninstall script /usr/local/bin/k3s-uninstall.sh
[INFO]  env: Creating environment file /etc/systemd/system/k3s.service.env
[INFO]  systemd: Creating service file /etc/systemd/system/k3s.service
[INFO]  systemd: Enabling k3s unit
Created symlink from /etc/systemd/system/multi-user.target.wants/k3s.service to /etc/systemd/system/k3s.service.
[INFO]  systemd: Starting k3s

I have disabled firewalld as it seemed to cause problems and I wanted to look into these issues later.
SELinux is still enabled and in enforcing mode but this does not seem to cause any issues.
I have created a two-node-cluster and set up /etc/hosts on both nodes for name resolution
<IP_ADDRESS> k3s-node01.lab k3s-node01
<IP_ADDRESS> k3s-node02.lab k3s-node02

Out if laziness, I simply edited the k3s systemd service on the second node:
First node (Server):
ExecStart=/usr/local/bin/k3s server
Second node (Agent):
ExecStart=/usr/local/bin/k3s agent --server https://k3s-node01.lab:6443 --token .....
But I can't get the system to work properly.
Newly spawned pods are stuck nearly forever in state ContainerCreating:
kubectl get pods --all-namespaces
NAMESPACE     NAME                                READY   STATUS              RESTARTS   AGE
default       whoami-deployment-9f9c86c4f-br2rj   0/1     ContainerCreating   0          19m
default       whoami-deployment-9f9c86c4f-ftj6x   1/1     Running             0          75m
kube-system   coredns-695688789-tt6rw             1/1     Running             15         170m
kube-system   svclb-traefik-6mpzx                 2/2     Running             6          161m
kube-system   svclb-traefik-phpd2                 0/2     Unknown             0          111m
kube-system   traefik-55bd9646fc-6jdp5            1/1     Running             3          161m

I had created a simple "whoami" deployment object with replica count of 1 but it look a long time until the pod was in state "Running". I also rebooted both nodes. At some point, the pod was finally running. I am not sure if the reboots solved the problem or if it would have gone away after some time anyway.
I have now scaled replica count from 1 to 2 but now the second pod also cannot be created - just as the first one before.
Now, even the node became unavailable:
kubectl get nodes
NAME             STATUS     ROLES    AGE    VERSION
k3s-node01.lab   Ready      <none>   174m   v1.14.1-k3s.4
k3s-node02.lab   NotReady   <none>   115m   v1.14.1-k3s.4

kubectl describe node k3s-node02.lab
Name:               k3s-node02.lab
Roles:              <none>
Labels:             beta.kubernetes.io/arch=amd64
                    beta.kubernetes.io/os=linux
                    kubernetes.io/arch=amd64
                    kubernetes.io/hostname=k3s-node02.lab
                    kubernetes.io/os=linux
Annotations:        flannel.alpha.coreos.com/backend-data: {"VtepMAC":"b6:58:36:34:f0:25"}
                    flannel.alpha.coreos.com/backend-type: vxlan
                    flannel.alpha.coreos.com/kube-subnet-manager: true
                    flannel.alpha.coreos.com/public-ip: <IP_ADDRESS>
                    node.alpha.kubernetes.io/ttl: 0
                    volumes.kubernetes.io/controller-managed-attach-detach: true
CreationTimestamp:  Mon, 27 May 2019 14:47:29 +0200
Taints:             node.kubernetes.io/not-ready:NoExecute
                    node.kubernetes.io/not-ready:NoSchedule
Unschedulable:      false
Conditions:
  Type             Status  LastHeartbeatTime                 LastTransitionTime                Reason                       Message
  ----             ------  -----------------                 ------------------                ------                       -------
  MemoryPressure   False   Mon, 27 May 2019 16:43:12 +0200   Mon, 27 May 2019 14:56:54 +0200   KubeletHasSufficientMemory   kubelet has sufficient memory available
  DiskPressure     False   Mon, 27 May 2019 16:43:12 +0200   Mon, 27 May 2019 14:56:54 +0200   KubeletHasNoDiskPressure     kubelet has no disk pressure
  PIDPressure      False   Mon, 27 May 2019 16:43:12 +0200   Mon, 27 May 2019 14:56:54 +0200   KubeletHasSufficientPID      kubelet has sufficient PID available
  Ready            False   Mon, 27 May 2019 16:43:12 +0200   Mon, 27 May 2019 16:40:42 +0200   KubeletNotReady              PLEG is not healthy: pleg was last seen active 5m38.674727787s ago; threshold is 3m0s.
Addresses:
  InternalIP:  <IP_ADDRESS>
  Hostname:    k3s-node02.lab
Capacity:
 cpu:                2
 ephemeral-storage:  17394Mi
 hugepages-1Gi:      0
 hugepages-2Mi:      0
 memory:             1863248Ki
 pods:               110
Allocatable:
 cpu:                2
 ephemeral-storage:<PHONE_NUMBER>4
 hugepages-1Gi:      0
 hugepages-2Mi:      0
 memory:             1863248Ki
 pods:               110
System Info:
 Machine ID:                 ba7665b65d1c4ada9534cec1acd8472e
 System UUID:                7B224D56-59BD-25ED-AE6A-305E6E497962
 Boot ID:                    fd46f542-b0ee-4479-b249-3b1ac4123cb0
 Kernel Version:             3.10.0-957.12.2.el7.x86_64
 OS Image:                   CentOS Linux 7 (Core)
 Operating System:           linux
 Architecture:               amd64
 Container Runtime Version:  containerd://1.2.5+unknown
 Kubelet Version:            v1.14.1-k3s.4
 Kube-Proxy Version:         v1.14.1-k3s.4
PodCIDR:                     <IP_ADDRESS>/24
Non-terminated Pods:         (2 in total)
  Namespace                  Name                                 CPU Requests  CPU Limits  Memory Requests  Memory Limits  AGE
  ---------                  ----                                 ------------  ----------  ---------------  -------------  ---
  default                    whoami-deployment-9f9c86c4f-br2rj    0 (0%)        0 (0%)      0 (0%)           0 (0%)         23m
  kube-system                svclb-traefik-phpd2                  0 (0%)        0 (0%)      0 (0%)           0 (0%)         115m
Allocated resources:
  (Total limits may be over 100 percent, i.e., overcommitted.)
  Resource           Requests  Limits
  --------           --------  ------
  cpu                0 (0%)    0 (0%)
  memory             0 (0%)    0 (0%)
  ephemeral-storage  0 (0%)    0 (0%)
Events:
  Type     Reason             Age                   From                     Message
  ----     ------             ----                  ----                     -------
  Warning  ContainerGCFailed  8m46s (x19 over 81m)  kubelet, k3s-node02.lab  rpc error: code = DeadlineExceeded desc = context deadline exceeded
  Normal   NodeReady          3m41s (x20 over 84m)  kubelet, k3s-node02.lab  Node k3s-node02.lab status is now: NodeReady

There are lot of errors logged on the second node, like:
Image garbage collection failed once. Stats initialization may not have completed yet: invalid capacity 0 on image filesystem
node "k3s-node02.lab" not found
/run/flannel/subnet.env: no such file or directory
and several others
Despite the error message, /run/flannel/subnet.env exists on both nodes.
journalctl -u k3s | egrep -e " E[0-9]+"
May 27 16:59:50 k3s-node02.lab k3s[6528]: E0527 16:59:50.925765    6528 cri_stats_provider.go:373] Failed to get the info of the filesystem with mountpoint "/var/lib/rancher/k3s/agent/containerd/io.containerd.snapshotter.v1.overlayfs": unable to find data in memory cache.
May 27 16:59:50 k3s-node02.lab k3s[6528]: E0527 16:59:50.925781    6528 kubelet.go:1250] Image garbage collection failed once. Stats initialization may not have completed yet: invalid capacity 0 on image filesystem
May 27 16:59:51 k3s-node02.lab k3s[6528]: E0527 16:59:51.058091    6528 kubelet.go:2207] node "k3s-node02.lab" not found
May 27 16:59:51 k3s-node02.lab k3s[6528]: E0527 16:59:51.406351    6528 cadvisor_stats_provider.go:397] Partial failure issuing cadvisor.ContainerInfoV2: partial failures: ["/kubepods/besteffort/pod964d3950-807d-11e9-9350-000c29eea077": RecentStats: unable to find data in memory cache], ["/systemd": RecentStats: unable to find data in memory cache]
May 27 16:59:51 k3s-node02.lab k3s[6528]: E0527 16:59:51.715754    6528 remote_runtime.go:132] StopPodSandbox "2b7faf766adf0ef5a2037e623354f5c0cca1980aa7cf357bc5bfdd878d939b9b" from runtime service failed: rpc error: code = Unknown desc = an error occurred when try to find sandbox "2b7faf766adf0ef5a2037e623354f5c0cca1980aa7cf357bc5bfdd878d939b9b": does not exist
May 27 16:59:51 k3s-node02.lab k3s[6528]: E0527 16:59:51.715801    6528 kuberuntime_manager.go:846] Failed to stop sandbox {"containerd" "2b7faf766adf0ef5a2037e623354f5c0cca1980aa7cf357bc5bfdd878d939b9b"}
May 27 16:59:51 k3s-node02.lab k3s[6528]: E0527 16:59:51.719724    6528 remote_runtime.go:109] RunPodSandbox from runtime service failed: rpc error: code = Unknown desc = failed to setup network for sandbox "ffce3e0a3ceea863767c53702e59a9993d21719e285b3e9a2e03adbc346ad214": open /run/flannel/subnet.env: no such file or directory
May 27 16:59:51 k3s-node02.lab k3s[6528]: E0527 16:59:51.719801    6528 kuberuntime_sandbox.go:68] CreatePodSandbox for pod "whoami-deployment-9f9c86c4f-br2rj_default(69483298-808a-11e9-b0e8-000c29eea077)" failed: rpc error: code = Unknown desc = failed to setup network for sandbox "ffce3e0a3ceea863767c53702e59a9993d21719e285b3e9a2e03adbc346ad214": open /run/flannel/subnet.env: no such file or directory
May 27 16:59:51 k3s-node02.lab k3s[6528]: E0527 16:59:51.719823    6528 kuberuntime_manager.go:693] createPodSandbox for pod "whoami-deployment-9f9c86c4f-br2rj_default(69483298-808a-11e9-b0e8-000c29eea077)" failed: rpc error: code = Unknown desc = failed to setup network for sandbox "ffce3e0a3ceea863767c53702e59a9993d21719e285b3e9a2e03adbc346ad214": open /run/flannel/subnet.env: no such file or directory
May 27 16:59:51 k3s-node02.lab k3s[6528]: E0527 16:59:51.719882    6528 pod_workers.go:190] Error syncing pod 69483298-808a-11e9-b0e8-000c29eea077 ("whoami-deployment-9f9c86c4f-br2rj_default(69483298-808a-11e9-b0e8-000c29eea077)"), skipping: failed to "CreatePodSandbox" for "whoami-deployment-9f9c86c4f-br2rj_default(69483298-808a-11e9-b0e8-000c29eea077)" with CreatePodSandboxError: "CreatePodSandbox for pod \"whoami-deployment-9f9c86c4f-br2rj_default(69483298-808a-11e9-b0e8-000c29eea077)\" failed: rpc error: code = Unknown desc = failed to setup network for sandbox \"ffce3e0a3ceea863767c53702e59a9993d21719e285b3e9a2e03adbc346ad214\": open /run/flannel/subnet.env: no such file or directory"
May 27 16:59:51 k3s-node02.lab k3s[6528]: E0527 16:59:51.759033    6528 kuberuntime_manager.go:641] killPodWithSyncResult failed: failed to "KillPodSandbox" for "964d3950-807d-11e9-9350-000c29eea077" with KillPodSandboxError: "rpc error: code = Unknown desc = an error occurred when try to find sandbox \"2b7faf766adf0ef5a2037e623354f5c0cca1980aa7cf357bc5bfdd878d939b9b\": does not exist"
May 27 16:59:51 k3s-node02.lab k3s[6528]: E0527 16:59:51.759058    6528 pod_workers.go:190] Error syncing pod 964d3950-807d-11e9-9350-000c29eea077 ("svclb-traefik-phpd2_kube-system(964d3950-807d-11e9-9350-000c29eea077)"), skipping: failed to "KillPodSandbox" for "964d3950-807d-11e9-9350-000c29eea077" with KillPodSandboxError: "rpc error: code = Unknown desc = an error occurred when try to find sandbox \"2b7faf766adf0ef5a2037e623354f5c0cca1980aa7cf357bc5bfdd878d939b9b\": does not exist"
May 27 17:01:52 k3s-node02.lab k3s[6528]: E0527 17:01:52.922502    6528 remote_runtime.go:186] ListPodSandbox with filter &PodSandboxFilter{Id:,State:&PodSandboxStateValue{State:SANDBOX_READY,},LabelSelector:map[string]string{},} from runtime service failed: rpc error: code = DeadlineExceeded desc = context deadline exceeded
May 27 17:01:52 k3s-node02.lab k3s[6528]: E0527 17:01:52.922579    6528 kuberuntime_sandbox.go:210] ListPodSandbox failed: rpc error: code = DeadlineExceeded desc = context deadline exceeded
May 27 17:01:52 k3s-node02.lab k3s[6528]: E0527 17:01:52.922595    6528 kubelet_pods.go:1019] Error listing containers: &status.statusError{Code:4, Message:"context deadline exceeded", Details:[]*any.Any(nil)}
May 27 17:01:52 k3s-node02.lab k3s[6528]: E0527 17:01:52.922617    6528 kubelet.go:1942] Failed cleaning pods: rpc error: code = DeadlineExceeded desc = context deadline exceeded
May 27 17:01:53 k3s-node02.lab k3s[6528]: E0527 17:01:53.150165    6528 remote_runtime.go:186] ListPodSandbox with filter nil from runtime service failed: rpc error: code = DeadlineExceeded desc = context deadline exceeded
May 27 17:01:53 k3s-node02.lab k3s[6528]: E0527 17:01:53.150219    6528 kuberuntime_sandbox.go:210] ListPodSandbox failed: rpc error: code = DeadlineExceeded desc = context deadline exceeded
May 27 17:01:53 k3s-node02.lab k3s[6528]: E0527 17:01:53.150310    6528 generic.go:205] GenericPLEG: Unable to retrieve pods: rpc error: code = DeadlineExceeded desc = context deadline exceeded
May 27 17:02:01 k3s-node02.lab k3s[6528]: E0527 17:02:01.436395    6528 remote_runtime.go:186] ListPodSandbox with filter &PodSandboxFilter{Id:,State:nil,LabelSelector:map[string]string{},} from runtime service failed: rpc error: code = DeadlineExceeded desc = context deadline exceeded
May 27 17:02:01 k3s-node02.lab k3s[6528]: E0527 17:02:01.436459    6528 eviction_manager.go:247] eviction manager: failed to get summary stats: failed to list pod stats: failed to list all pod sandboxes: rpc error: code = DeadlineExceeded desc = context deadline exceeded
May 27 17:02:51 k3s-node02.lab k3s[6528]: E0527 17:02:51.361094    6528 remote_runtime.go:186] ListPodSandbox with filter nil from runtime service failed: rpc error: code = DeadlineExceeded desc = context deadline exceeded
May 27 17:02:51 k3s-node02.lab k3s[6528]: E0527 17:02:51.361168    6528 kuberuntime_sandbox.go:210] ListPodSandbox failed: rpc error: code = DeadlineExceeded desc = context deadline exceeded
May 27 17:02:51 k3s-node02.lab k3s[6528]: E0527 17:02:51.361371    6528 kubelet.go:1222] Container garbage collection failed: rpc error: code = DeadlineExceeded desc = context deadline exceeded
May 27 17:03:52 k3s-node02.lab k3s[6528]: E0527 17:03:52.178685    6528 remote_runtime.go:109] RunPodSandbox from runtime service failed: rpc error: code = DeadlineExceeded desc = context deadline exceeded
May 27 17:03:52 k3s-node02.lab k3s[6528]: E0527 17:03:52.178763    6528 kuberuntime_sandbox.go:68] CreatePodSandbox for pod "svclb-traefik-phpd2_kube-system(964d3950-807d-11e9-9350-000c29eea077)" failed: rpc error: code = DeadlineExceeded desc = context deadline exceeded
May 27 17:03:52 k3s-node02.lab k3s[6528]: E0527 17:03:52.178794    6528 kuberuntime_manager.go:693] createPodSandbox for pod "svclb-traefik-phpd2_kube-system(964d3950-807d-11e9-9350-000c29eea077)" failed: rpc error: code = DeadlineExceeded desc = context deadline exceeded
May 27 17:03:52 k3s-node02.lab k3s[6528]: E0527 17:03:52.178886    6528 pod_workers.go:190] Error syncing pod 964d3950-807d-11e9-9350-000c29eea077 ("svclb-traefik-phpd2_kube-system(964d3950-807d-11e9-9350-000c29eea077)"), skipping: failed to "CreatePodSandbox" for "svclb-traefik-phpd2_kube-system(964d3950-807d-11e9-9350-000c29eea077)" with CreatePodSandboxError: "CreatePodSandbox for pod \"svclb-traefik-phpd2_kube-system(964d3950-807d-11e9-9350-000c29eea077)\" failed: rpc error: code = DeadlineExceeded desc = context deadline exceeded"
May 27 17:03:54 k3s-node02.lab k3s[6528]: E0527 17:03:54.152691    6528 remote_runtime.go:186] ListPodSandbox with filter nil from runtime service failed: rpc error: code = DeadlineExceeded desc = context deadline exceeded
May 27 17:03:54 k3s-node02.lab k3s[6528]: E0527 17:03:54.152765    6528 kuberuntime_sandbox.go:210] ListPodSandbox failed: rpc error: code = DeadlineExceeded desc = context deadline exceeded
May 27 17:03:54 k3s-node02.lab k3s[6528]: E0527 17:03:54.152793    6528 generic.go:205] GenericPLEG: Unable to retrieve pods: rpc error: code = DeadlineExceeded desc = context deadline exceeded
May 27 17:05:52 k3s-node02.lab k3s[6528]: E0527 17:05:52.187016    6528 remote_runtime.go:287] ListContainers with filter &ContainerFilter{Id:,State:&ContainerStateValue{State:CONTAINER_RUNNING,},PodSandboxId:,LabelSelector:map[string]string{},} from runtime service failed: rpc error: code = DeadlineExceeded desc = context deadline exceeded
May 27 17:05:52 k3s-node02.lab k3s[6528]: E0527 17:05:52.187440    6528 kuberuntime_container.go:335] getKubeletContainers failed: rpc error: code = DeadlineExceeded desc = context deadline exceeded
May 27 17:05:52 k3s-node02.lab k3s[6528]: E0527 17:05:52.187477    6528 kubelet_pods.go:1019] Error listing containers: &status.statusError{Code:4, Message:"context deadline exceeded", Details:[]*any.Any(nil)}
May 27 17:05:52 k3s-node02.lab k3s[6528]: E0527 17:05:52.187518    6528 kubelet.go:1942] Failed cleaning pods: rpc error: code = DeadlineExceeded desc = context deadline exceeded
May 27 17:05:52 k3s-node02.lab k3s[6528]: E0527 17:05:52.187599    6528 remote_runtime.go:186] ListPodSandbox with filter &PodSandboxFilter{Id:,State:nil,LabelSelector:map[string]string{},} from runtime service failed: rpc error: code = DeadlineExceeded desc = context deadline exceeded
May 27 17:05:52 k3s-node02.lab k3s[6528]: E0527 17:05:52.187646    6528 eviction_manager.go:247] eviction manager: failed to get summary stats: failed to list pod stats: failed to list all pod sandboxes: rpc error: code = DeadlineExceeded desc = context deadline exceeded
May 27 17:05:52 k3s-node02.lab k3s[6528]: E0527 17:05:52.187737    6528 remote_runtime.go:287] ListContainers with filter &ContainerFilter{Id:,State:nil,PodSandboxId:,LabelSelector:map[string]string{},} from runtime service failed: rpc error: code = DeadlineExceeded desc = context deadline exceeded
May 27 17:05:52 k3s-node02.lab k3s[6528]: E0527 17:05:52.187764    6528 kuberuntime_container.go:335] getKubeletContainers failed: rpc error: code = DeadlineExceeded desc = context deadline exceeded
May 27 17:05:52 k3s-node02.lab k3s[6528]: E0527 17:05:52.187775    6528 kubelet.go:1222] Container garbage collection failed: rpc error: code = DeadlineExceeded desc = context deadline exceeded
May 27 17:05:52 k3s-node02.lab k3s[6528]: E0527 17:05:52.927958    6528 remote_runtime.go:109] RunPodSandbox from runtime service failed: rpc error: code = DeadlineExceeded desc = context deadline exceeded
May 27 17:05:52 k3s-node02.lab k3s[6528]: E0527 17:05:52.928020    6528 kuberuntime_sandbox.go:68] CreatePodSandbox for pod "whoami-deployment-9f9c86c4f-br2rj_default(69483298-808a-11e9-b0e8-000c29eea077)" failed: rpc error: code = DeadlineExceeded desc = context deadline exceeded
May 27 17:05:52 k3s-node02.lab k3s[6528]: E0527 17:05:52.928049    6528 kuberuntime_manager.go:693] createPodSandbox for pod "whoami-deployment-9f9c86c4f-br2rj_default(69483298-808a-11e9-b0e8-000c29eea077)" failed: rpc error: code = DeadlineExceeded desc = context deadline exceeded
May 27 17:05:52 k3s-node02.lab k3s[6528]: E0527 17:05:52.928103    6528 pod_workers.go:190] Error syncing pod 69483298-808a-11e9-b0e8-000c29eea077 ("whoami-deployment-9f9c86c4f-br2rj_default(69483298-808a-11e9-b0e8-000c29eea077)"), skipping: failed to "CreatePodSandbox" for "whoami-deployment-9f9c86c4f-br2rj_default(69483298-808a-11e9-b0e8-000c29eea077)" with CreatePodSandboxError: "CreatePodSandbox for pod \"whoami-deployment-9f9c86c4f-br2rj_default(69483298-808a-11e9-b0e8-000c29eea077)\" failed: rpc error: code = DeadlineExceeded desc = context deadline exceeded"
May 27 17:05:52 k3s-node02.lab k3s[6528]: E0527 17:05:52.997924    6528 remote_runtime.go:109] RunPodSandbox from runtime service failed: rpc error: code = Unknown desc = failed to reserve sandbox name "svclb-traefik-phpd2_kube-system_964d3950-807d-11e9-9350-000c29eea077_1": name "svclb-traefik-phpd2_kube-system_964d3950-807d-11e9-9350-000c29eea077_1" is reserved for "081b44846a5be544621fad10e504f6f51e3d128753dc83825b78460863a7748a"
May 27 17:05:52 k3s-node02.lab k3s[6528]: E0527 17:05:52.997953    6528 kuberuntime_sandbox.go:68] CreatePodSandbox for pod "svclb-traefik-phpd2_kube-system(964d3950-807d-11e9-9350-000c29eea077)" failed: rpc error: code = Unknown desc = failed to reserve sandbox name "svclb-traefik-phpd2_kube-system_964d3950-807d-11e9-9350-000c29eea077_1": name "svclb-traefik-phpd2_kube-system_964d3950-807d-11e9-9350-000c29eea077_1" is reserved for "081b44846a5be544621fad10e504f6f51e3d128753dc83825b78460863a7748a"
May 27 17:05:52 k3s-node02.lab k3s[6528]: E0527 17:05:52.997969    6528 kuberuntime_manager.go:693] createPodSandbox for pod "svclb-traefik-phpd2_kube-system(964d3950-807d-11e9-9350-000c29eea077)" failed: rpc error: code = Unknown desc = failed to reserve sandbox name "svclb-traefik-phpd2_kube-system_964d3950-807d-11e9-9350-000c29eea077_1": name "svclb-traefik-phpd2_kube-system_964d3950-807d-11e9-9350-000c29eea077_1" is reserved for "081b44846a5be544621fad10e504f6f51e3d128753dc83825b78460863a7748a"
May 27 17:05:52 k3s-node02.lab k3s[6528]: E0527 17:05:52.998005    6528 pod_workers.go:190] Error syncing pod 964d3950-807d-11e9-9350-000c29eea077 ("svclb-traefik-phpd2_kube-system(964d3950-807d-11e9-9350-000c29eea077)"), skipping: failed to "CreatePodSandbox" for "svclb-traefik-phpd2_kube-system(964d3950-807d-11e9-9350-000c29eea077)" with CreatePodSandboxError: "CreatePodSandbox for pod \"svclb-traefik-phpd2_kube-system(964d3950-807d-11e9-9350-000c29eea077)\" failed: rpc error: code = Unknown desc = failed to reserve sandbox name \"svclb-traefik-phpd2_kube-system_964d3950-807d-11e9-9350-000c29eea077_1\": name \"svclb-traefik-phpd2_kube-system_964d3950-807d-11e9-9350-000c29eea077_1\" is reserved for \"081b44846a5be544621fad10e504f6f51e3d128753dc83825b78460863a7748a\""
May 27 17:08:07 k3s-node02.lab k3s[6528]: E0527 17:08:07.964732    6528 remote_runtime.go:186] ListPodSandbox with filter nil from runtime service failed: rpc error: code = DeadlineExceeded desc = context deadline exceeded
May 27 17:08:07 k3s-node02.lab k3s[6528]: E0527 17:08:07.964815    6528 kuberuntime_sandbox.go:210] ListPodSandbox failed: rpc error: code = DeadlineExceeded desc = context deadline exceeded
May 27 17:08:07 k3s-node02.lab k3s[6528]: E0527 17:08:07.964845    6528 generic.go:205] GenericPLEG: Unable to retrieve pods: rpc error: code = DeadlineExceeded desc = context deadline exceeded
May 27 17:08:08 k3s-node02.lab k3s[6528]: E0527 17:08:08.923180    6528 remote_runtime.go:186] ListPodSandbox with filter &PodSandboxFilter{Id:,State:&PodSandboxStateValue{State:SANDBOX_READY,},LabelSelector:map[string]string{},} from runtime service failed: rpc error: code = DeadlineExceeded desc = context deadline exceeded
May 27 17:08:08 k3s-node02.lab k3s[6528]: E0527 17:08:08.923275    6528 kuberuntime_sandbox.go:210] ListPodSandbox failed: rpc error: code = DeadlineExceeded desc = context deadline exceeded
May 27 17:08:08 k3s-node02.lab k3s[6528]: E0527 17:08:08.923330    6528 kubelet_pods.go:1035] Error listing containers: &status.statusError{Code:4, Message:"context deadline exceeded", Details:[]*any.Any(nil)}
May 27 17:08:08 k3s-node02.lab k3s[6528]: E0527 17:08:08.923411    6528 kubelet.go:1942] Failed cleaning pods: rpc error: code = DeadlineExceeded desc = context deadline exceeded
May 27 17:08:12 k3s-node02.lab k3s[6528]: E0527 17:08:12.207717    6528 remote_runtime.go:186] ListPodSandbox with filter &PodSandboxFilter{Id:,State:nil,LabelSelector:map[string]string{},} from runtime service failed: rpc error: code = DeadlineExceeded desc = context deadline exceeded
May 27 17:08:12 k3s-node02.lab k3s[6528]: E0527 17:08:12.207795    6528 eviction_manager.go:247] eviction manager: failed to get summary stats: failed to list pod stats: failed to list all pod sandboxes: rpc error: code = DeadlineExceeded desc = context deadline exceeded
May 27 17:08:52 k3s-node02.lab k3s[6528]: E0527 17:08:52.189809    6528 remote_runtime.go:186] ListPodSandbox with filter nil from runtime service failed: rpc error: code = DeadlineExceeded desc = context deadline exceeded
May 27 17:08:52 k3s-node02.lab k3s[6528]: E0527 17:08:52.189882    6528 kuberuntime_sandbox.go:210] ListPodSandbox failed: rpc error: code = DeadlineExceeded desc = context deadline exceeded
May 27 17:08:52 k3s-node02.lab k3s[6528]: E0527 17:08:52.189900    6528 kubelet.go:1222] Container garbage collection failed: rpc error: code = DeadlineExceeded desc = context deadline exceeded
May 27 17:10:06 k3s-node02.lab k3s[6528]: E0527 17:10:06.918561    6528 remote_runtime.go:109] RunPodSandbox from runtime service failed: rpc error: code = DeadlineExceeded desc = context deadline exceeded
May 27 17:10:06 k3s-node02.lab k3s[6528]: E0527 17:10:06.918633    6528 kuberuntime_sandbox.go:68] CreatePodSandbox for pod "whoami-deployment-9f9c86c4f-br2rj_default(69483298-808a-11e9-b0e8-000c29eea077)" failed: rpc error: code = DeadlineExceeded desc = context deadline exceeded
May 27 17:10:06 k3s-node02.lab k3s[6528]: E0527 17:10:06.918662    6528 kuberuntime_manager.go:693] createPodSandbox for pod "whoami-deployment-9f9c86c4f-br2rj_default(69483298-808a-11e9-b0e8-000c29eea077)" failed: rpc error: code = DeadlineExceeded desc = context deadline exceeded
May 27 17:10:06 k3s-node02.lab k3s[6528]: E0527 17:10:06.918721    6528 pod_workers.go:190] Error syncing pod 69483298-808a-11e9-b0e8-000c29eea077 ("whoami-deployment-9f9c86c4f-br2rj_default(69483298-808a-11e9-b0e8-000c29eea077)"), skipping: failed to "CreatePodSandbox" for "whoami-deployment-9f9c86c4f-br2rj_default(69483298-808a-11e9-b0e8-000c29eea077)" with CreatePodSandboxError: "CreatePodSandbox for pod \"whoami-deployment-9f9c86c4f-br2rj_default(69483298-808a-11e9-b0e8-000c29eea077)\" failed: rpc error: code = DeadlineExceeded desc = context deadline exceeded"
May 27 17:10:06 k3s-node02.lab k3s[6528]: E0527 17:10:06.976974    6528 remote_runtime.go:109] RunPodSandbox from runtime service failed: rpc error: code = DeadlineExceeded desc = context deadline exceeded
May 27 17:10:06 k3s-node02.lab k3s[6528]: E0527 17:10:06.977097    6528 kuberuntime_sandbox.go:68] CreatePodSandbox for pod "svclb-traefik-phpd2_kube-system(964d3950-807d-11e9-9350-000c29eea077)" failed: rpc error: code = DeadlineExceeded desc = context deadline exceeded
May 27 17:10:06 k3s-node02.lab k3s[6528]: E0527 17:10:06.977128    6528 kuberuntime_manager.go:693] createPodSandbox for pod "svclb-traefik-phpd2_kube-system(964d3950-807d-11e9-9350-000c29eea077)" failed: rpc error: code = DeadlineExceeded desc = context deadline exceeded
May 27 17:10:06 k3s-node02.lab k3s[6528]: E0527 17:10:06.977187    6528 pod_workers.go:190] Error syncing pod 964d3950-807d-11e9-9350-000c29eea077 ("svclb-traefik-phpd2_kube-system(964d3950-807d-11e9-9350-000c29eea077)"), skipping: failed to "CreatePodSandbox" for "svclb-traefik-phpd2_kube-system(964d3950-807d-11e9-9350-000c29eea077)" with CreatePodSandboxError: "CreatePodSandbox for pod \"svclb-traefik-phpd2_kube-system(964d3950-807d-11e9-9350-000c29eea077)\" failed: rpc error: code = DeadlineExceeded desc = context deadline exceeded"
May 27 17:12:18 k3s-node02.lab k3s[6528]: E0527 17:12:18.007921    6528 remote_runtime.go:186] ListPodSandbox with filter nil from runtime service failed: rpc error: code = DeadlineExceeded desc = context deadline exceeded
May 27 17:12:18 k3s-node02.lab k3s[6528]: E0527 17:12:18.008053    6528 kuberuntime_sandbox.go:210] ListPodSandbox failed: rpc error: code = DeadlineExceeded desc = context deadline exceeded
May 27 17:12:18 k3s-node02.lab k3s[6528]: E0527 17:12:18.008076    6528 generic.go:205] GenericPLEG: Unable to retrieve pods: rpc error: code = DeadlineExceeded desc = context deadline exceeded
May 27 17:12:18 k3s-node02.lab k3s[6528]: E0527 17:12:18.921567    6528 remote_runtime.go:186] ListPodSandbox with filter &PodSandboxFilter{Id:,State:&PodSandboxStateValue{State:SANDBOX_READY,},LabelSelector:map[string]string{},} from runtime service failed: rpc error: code = DeadlineExceeded desc = context deadline exceeded
May 27 17:12:18 k3s-node02.lab k3s[6528]: E0527 17:12:18.921645    6528 kuberuntime_sandbox.go:210] ListPodSandbox failed: rpc error: code = DeadlineExceeded desc = context deadline exceeded
May 27 17:12:18 k3s-node02.lab k3s[6528]: E0527 17:12:18.921662    6528 kubelet_pods.go:1019] Error listing containers: &status.statusError{Code:4, Message:"context deadline exceeded", Details:[]*any.Any(nil)}
May 27 17:12:18 k3s-node02.lab k3s[6528]: E0527 17:12:18.921688    6528 kubelet.go:1942] Failed cleaning pods: rpc error: code = DeadlineExceeded desc = context deadline exceeded
May 27 17:12:27 k3s-node02.lab k3s[6528]: E0527 17:12:27.029444    6528 remote_runtime.go:186] ListPodSandbox with filter &PodSandboxFilter{Id:,State:nil,LabelSelector:map[string]string{},} from runtime service failed: rpc error: code = DeadlineExceeded desc = context deadline exceeded
May 27 17:12:27 k3s-node02.lab k3s[6528]: E0527 17:12:27.029523    6528 eviction_manager.go:247] eviction manager: failed to get summary stats: failed to list pod stats: failed to list all pod sandboxes: rpc error: code = DeadlineExceeded desc = context deadline exceeded
May 27 17:12:52 k3s-node02.lab k3s[6528]: E0527 17:12:52.937711    6528 remote_runtime.go:186] ListPodSandbox with filter nil from runtime service failed: rpc error: code = DeadlineExceeded desc = context deadline exceeded
May 27 17:12:52 k3s-node02.lab k3s[6528]: E0527 17:12:52.937755    6528 kuberuntime_sandbox.go:210] ListPodSandbox failed: rpc error: code = DeadlineExceeded desc = context deadline exceeded
May 27 17:13:06 k3s-node02.lab k3s[6528]: E0527 17:13:06.983890    6528 remote_runtime.go:186] ListPodSandbox with filter nil from runtime service failed: rpc error: code = DeadlineExceeded desc = context deadline exceeded
May 27 17:13:06 k3s-node02.lab k3s[6528]: E0527 17:13:06.983990    6528 kuberuntime_sandbox.go:210] ListPodSandbox failed: rpc error: code = DeadlineExceeded desc = context deadline exceeded
May 27 17:13:06 k3s-node02.lab k3s[6528]: E0527 17:13:06.984009    6528 kubelet.go:1222] Container garbage collection failed: rpc error: code = DeadlineExceeded desc = context deadline exceeded
May 27 17:14:17 k3s-node02.lab k3s[6528]: E0527 17:14:17.916729    6528 remote_runtime.go:109] RunPodSandbox from runtime service failed: rpc error: code = DeadlineExceeded desc = context deadline exceeded
May 27 17:14:17 k3s-node02.lab k3s[6528]: E0527 17:14:17.916792    6528 kuberuntime_sandbox.go:68] CreatePodSandbox for pod "whoami-deployment-9f9c86c4f-br2rj_default(69483298-808a-11e9-b0e8-000c29eea077)" failed: rpc error: code = DeadlineExceeded desc = context deadline exceeded
May 27 17:14:17 k3s-node02.lab k3s[6528]: E0527 17:14:17.916812    6528 kuberuntime_manager.go:693] createPodSandbox for pod "whoami-deployment-9f9c86c4f-br2rj_default(69483298-808a-11e9-b0e8-000c29eea077)" failed: rpc error: code = DeadlineExceeded desc = context deadline exceeded
May 27 17:14:17 k3s-node02.lab k3s[6528]: E0527 17:14:17.916856    6528 pod_workers.go:190] Error syncing pod 69483298-808a-11e9-b0e8-000c29eea077 ("whoami-deployment-9f9c86c4f-br2rj_default(69483298-808a-11e9-b0e8-000c29eea077)"), skipping: failed to "CreatePodSandbox" for "whoami-deployment-9f9c86c4f-br2rj_default(69483298-808a-11e9-b0e8-000c29eea077)" with CreatePodSandboxError: "CreatePodSandbox for pod \"whoami-deployment-9f9c86c4f-br2rj_default(69483298-808a-11e9-b0e8-000c29eea077)\" failed: rpc error: code = DeadlineExceeded desc = context deadline exceeded"
May 27 17:16:18 k3s-node02.lab k3s[6528]: E0527 17:16:18.921967    6528 remote_runtime.go:186] ListPodSandbox with filter nil from runtime service failed: rpc error: code = DeadlineExceeded desc = context deadline exceeded
May 27 17:16:18 k3s-node02.lab k3s[6528]: E0527 17:16:18.922031    6528 kuberuntime_sandbox.go:210] ListPodSandbox failed: rpc error: code = DeadlineExceeded desc = context deadline exceeded
May 27 17:16:18 k3s-node02.lab k3s[6528]: E0527 17:16:18.922049    6528 generic.go:205] GenericPLEG: Unable to retrieve pods: rpc error: code = DeadlineExceeded desc = context deadline exceeded
May 27 17:16:18 k3s-node02.lab k3s[6528]: E0527 17:16:18.922095    6528 remote_runtime.go:186] ListPodSandbox with filter &PodSandboxFilter{Id:,State:&PodSandboxStateValue{State:SANDBOX_READY,},LabelSelector:map[string]string{},} from runtime service failed: rpc error: code = DeadlineExceeded desc = context deadline exceeded
May 27 17:16:18 k3s-node02.lab k3s[6528]: E0527 17:16:18.922123    6528 kuberuntime_sandbox.go:210] ListPodSandbox failed: rpc error: code = DeadlineExceeded desc = context deadline exceeded
May 27 17:16:18 k3s-node02.lab k3s[6528]: E0527 17:16:18.922134    6528 kubelet_pods.go:1035] Error listing containers: &status.statusError{Code:4, Message:"context deadline exceeded", Details:[]*any.Any(nil)}
May 27 17:16:18 k3s-node02.lab k3s[6528]: E0527 17:16:18.922159    6528 kubelet.go:1942] Failed cleaning pods: rpc error: code = DeadlineExceeded desc = context deadline exceeded
May 27 17:16:27 k3s-node02.lab k3s[6528]: E0527 17:16:27.948495    6528 remote_runtime.go:186] ListPodSandbox with filter &PodSandboxFilter{Id:,State:nil,LabelSelector:map[string]string{},} from runtime service failed: rpc error: code = DeadlineExceeded desc = context deadline exceeded
May 27 17:16:27 k3s-node02.lab k3s[6528]: E0527 17:16:27.948601    6528 eviction_manager.go:247] eviction manager: failed to get summary stats: failed to list pod stats: failed to list all pod sandboxes: rpc error: code = DeadlineExceeded desc = context deadline exceeded
May 27 17:17:17 k3s-node02.lab k3s[6528]: E0527 17:17:17.922641    6528 remote_runtime.go:186] ListPodSandbox with filter nil from runtime service failed: rpc error: code = DeadlineExceeded desc = context deadline exceeded
May 27 17:17:17 k3s-node02.lab k3s[6528]: E0527 17:17:17.922693    6528 kuberuntime_sandbox.go:210] ListPodSandbox failed: rpc error: code = DeadlineExceeded desc = context deadline exceeded
May 27 17:17:17 k3s-node02.lab k3s[6528]: E0527 17:17:17.922705    6528 kubelet.go:1222] Container garbage collection failed: rpc error: code = DeadlineExceeded desc = context deadline exceeded

Can somebody maybe point me in the right direction?
Thanks in advance :)

I figured out that the systemd service of the k3s agent was somehow causing these problems, although I can't tell what was the exact reason for it.
I have now adjusted and simplified the services:
/etc/systemd/system/k3s-server.service:

[Unit]
Description=Lightweight Kubernetes
Documentation=https://k3s.io
After=network-online.target

[Service]
EnvironmentFile=/etc/systemd/system/k3s-server.service.env
ExecStartPre=/usr/sbin/modprobe ip_vs
ExecStartPre=/usr/sbin/modprobe ip_vs_rr
ExecStartPre=/usr/sbin/modprobe ip_vs_wrr
ExecStartPre=/usr/sbin/modprobe ip_vs_sh
ExecStart=/usr/local/bin/k3s server
LimitNOFILE=infinity
LimitNPROC=infinity
LimitCORE=infinity
TasksMax=infinity
TimeoutStartSec=0
Restart=always

[Install]
WantedBy=multi-user.target

/etc/systemd/system/k3s-agent.service:

[Unit]
Description=Lightweight Kubernetes
Documentation=https://k3s.io
After=network-online.target

[Service]
EnvironmentFile=/etc/systemd/system/k3s-agent.service.env
ExecStartPre=/usr/sbin/modprobe ip_vs
ExecStartPre=/usr/sbin/modprobe ip_vs_rr
ExecStartPre=/usr/sbin/modprobe ip_vs_wrr
ExecStartPre=/usr/sbin/modprobe ip_vs_sh
ExecStart=/usr/local/bin/k3s agent --server https://k3s-node01.lab:6443 --token .....
LimitNOFILE=infinity
LimitNPROC=infinity
LimitCORE=infinity
TasksMax=infinity
TimeoutStartSec=0
Restart=always

[Install]
WantedBy=multi-user.target

Which these service files, the cluster seems to run fine.

I have this very same issue. I've installed three agents and they're constantly up and down.
Type     Reason                   Age                  From                  Message

Normal   Starting                 13m                  kubelet, worker01     Starting kubelet.
Normal   Starting                 13m                  kube-proxy, worker01  Starting kube-proxy.
Warning  InvalidDiskCapacity      13m                  kubelet, worker01     invalid capacity 0 on image filesystem
Normal   NodeHasSufficientMemory  13m (x2 over 13m)    kubelet, worker01     Node worker01 status is now: NodeHasSufficientMemory
Normal   NodeHasNoDiskPressure    13m (x2 over 13m)    kubelet, worker01     Node worker01 status is now: NodeHasNoDiskPressure
Normal   NodeHasSufficientPID     13m (x2 over 13m)    kubelet, worker01     Node worker01 status is now: NodeHasSufficientPID
Normal   NodeAllocatableEnforced  13m                  kubelet, worker01     Updated Node Allocatable limit across pods
Warning  ContainerGCFailed        2m55s                kubelet, worker01     rpc error: code = DeadlineExceeded desc = context deadline exceeded
Normal   NodeReady                2m46s (x3 over 13m)  kubelet, worker01     Node worker01 status is now: NodeReady
Normal   NodeNotReady             106s (x3 over 10m)   kubelet, worker01     Node worker01 status is now: NodeNotReady

Same issue, unable to run pods on nodes. Pods on nodes just keep crashing while pods on server work fine.

Same issue here.
Failed create pod sandbox: rpc error: code = DeadlineExceeded desc = context deadline exceeded.


Libraries

What are the libraries that are required to run this code?
I'm missing a 'util' library and a 'pl.pretty' library.

After viewing over the code, it seems there are no references to the libraries. Are they needed for something, or do the libraries declare global variables?
Also, on that note, try to make your libraries return a table (5.2's require() prefers this) or set a global table as to not clutter up _G with random functions.

@AlissaSquared I'm not maintaining this library anymore. This was some minimal effort I put in back in college. I would feel honored if you fork and make it the way you see better. Cheers!


Improve/add atomics

Remove use of non-builtin overloaded InterlockedExhangeSubtract() for Windows. Moreover, it was wrongly being used as if it hadn't a 64-bit version instead of being overloaded. (*)
Implement exchange-if-greater (as a CAS loop).

*: @vnen, you were right regarding InterlockedExhangeSubtract64() not being present in UWP, but the thing is that it doesn't even exist in "normal" Windows at all. I imagined it. :)

Ah, never realized it was only going into that condition in UWP. Godot defines _WIN32_WINNT = 0x0600 for Windows platform.


check usages of isolation level of pgx.Serializable

TL;DR
audit usages of pgx.Serializable
lower to ReadCommitted if appropriate

Done.


Update githubIssues.js task to pull issues from a Google Spreadsheet instead?

The CSV in the repo is great, but, depending on the complexity of what we want to put into the default text, editing it is kind of a pain. An alternate idea could be to point to a Google Sheet, automatically d/l a CSV from there, and then continue on with the task?
This is a pretty minor nice-to-have.

Might be worth pulling from an ArchieML doc instead--you'd want to set up the relevant tasks to export their internal mechanisms in a way that could be could be imported elsewhere (maybe by adding them onto the function that they're already exporting as properties, or by moving that code into tasks/lib the way the Chalkbeat rig does with S3 now), but once that's done it'd be pretty easy to pull that down and convert it into the same structure that the GH task currently expects.


Add "Insert Resource" to the Bicep.exe file, not just VS code extension

Is your feature request related to a problem? Please describe.
The "Insert Resource" command is excellent but only works in VS code as a function of the VS Code extension.  Please add this to the bicep executable as
bicep.exe import "/subscription/.../object/ID"

Describe the solution you'd like
By adding this feature to the Bicep.exe file, scripting the output of many objects can be simplified.
bicep import "id1" >> outfile.bicep
bicep import "id2" >> outfile.bicep
bicep import "id3" >> outfile.bicep
bicep import "id4" >> outfile.bicep

IMPORT might be the wrong action word for the EXE.  We have build and Decompile, maybe something more like GET or READ.

My suggestion is to name this command bicep export.
bicep export "/<subscription-id>/<rg>/<resource-id>" --outfile "c:\temp\myResource.bicep"

Any news regarding this?

Interesting suggestion! Would there be any objection to building this into AzCLI & AzPwsh instead of the Bicep CLI?
e.g. something like:
az bicep insert-resource --ids '<id>' --out-file 'res.bicep'

Conceptually this is also quite similar to the export + decompile sinppet here - apart from simplicity, are there any benefits to having "Insert Resource" in the CLI instead of using this snippet?

@anthony-c-martin
Not any objection, as long the binary does the job, altrough I would be a big fan of seeing this in the Bicep CLI binary.
Reason for not using the already existing export + decompile is that quite frankly often you don't have the JSON or you don't want to download download the JSON it manually and decompile it.
Having this bicep export functionality in place will leverage a "new world" where you can just call to Azure, traverse thru everything and download the complete environment in bicep in source control.
It will enable teams that do not have their Azure stack in neither bicep or IaC at all to get it and will be a MAJOR improvement.

Interesting suggestion! Would there be any objection to building this into AzCLI & AzPwsh instead of the Bicep CLI?
e.g. something like:
az bicep insert-resource --ids '<id>' --out-file 'res.bicep'

Conceptually this is also quite similar to the export + decompile sinppet here - apart from simplicity, are there any benefits to having "Insert Resource" in the CLI instead of using this snippet?

The two commands are not functionally the same.  The VSCode bicep insert resource is scoped to a single resource, whereas az group export has to act on a group.  There is no az resource export command.
For example, pointing bicep insert resource at a Resource Group produces:
@description('Generated from /subscriptions/xxxx-xxxx-xxxx/resourceGroups/myRG')
resource myRG 'Microsoft.Resources/resourceGroups@2021-04-01' = {
  name: 'myRG'
  location: 'eastus'
  tags: {}
  properties: {}
}

Note this is a bicep file for the Resource Group, not any objects in it.
The Az command your proposing does this:
az group export --resource-group 'MyRG
{
  "$schema": "https://schema.management.azure.com/schemas/2019-04-01/deploymentTemplate.json#",
  "contentVersion": "<IP_ADDRESS>",
  "parameters": {
    "storageAccounts_mystorageacct_name": {
      "type": "String"
    }
  },
  "resources": [
    {
      "apiVersion": "2021-09-01",
      "kind": "StorageV2",
      "location": "eastus",
      "name": "[parameters('storageAccounts_mystorageacct_name')]",
      "properties": {
        "accessTier": "Cool",
        "allowBlobPublicAccess": true,
        "allowCrossTenantReplication": true,
        "allowSharedKeyAccess": true,
        "defaultToOAuthAuthentication": false,
        "minimumTlsVersion": "TLS1_2",
        "publicNetworkAccess": "Enabled",
        "supportsHttpsTrafficOnly": true
      },
      "sku": {
        "name": "Standard_LRS",
        "tier": "Standard"
      },
      "type": "Microsoft.Storage/storageAccounts"
    }
  ],
  "variables": {}
}

Which is a complete ARM template for the objects inside the RG, not the RG itself.

Thanks @ChristopherGLewis, that's one of the things I was hoping to get at with my questioning. You're right - ARM's export more limited in that it can only be used to fetch resources inside a resource group, and has no support for subscription, tenant, extension resources etc.
I do still feel like conceptually this would fit better as an az command, but agree that providing a one-liner equivalent of the 'export-and-decompile' isn't going to provide the same set of functionality.

Interesting suggestion! Would there be any objection to building this into AzCLI & AzPwsh instead of the Bicep CLI?
e.g. something like:
az bicep insert-resource --ids '<id>' --out-file 'res.bicep'

Conceptually this is also quite similar to the export + decompile sinppet here - apart from simplicity, are there any benefits to having "Insert Resource" in the CLI instead of using this snippet?

The two commands are not functionally the same. The VSCode bicep insert resource is scoped to a single resource, whereas az group export has to act on a group. There is no az resource export command.
For example, pointing bicep insert resource at a Resource Group produces:
@description('Generated from /subscriptions/xxxx-xxxx-xxxx/resourceGroups/myRG')
resource myRG 'Microsoft.Resources/resourceGroups@2021-04-01' = {
  name: 'myRG'
  location: 'eastus'
  tags: {}
  properties: {}
}

Note this is a bicep file for the Resource Group, not any objects in it.
The Az command your proposing does this:
az group export --resource-group 'MyRG
{
  "$schema": "https://schema.management.azure.com/schemas/2019-04-01/deploymentTemplate.json#",
  "contentVersion": "<IP_ADDRESS>",
  "parameters": {
    "storageAccounts_mystorageacct_name": {
      "type": "String"
    }
  },
  "resources": [
    {
      "apiVersion": "2021-09-01",
      "kind": "StorageV2",
      "location": "eastus",
      "name": "[parameters('storageAccounts_mystorageacct_name')]",
      "properties": {
        "accessTier": "Cool",
        "allowBlobPublicAccess": true,
        "allowCrossTenantReplication": true,
        "allowSharedKeyAccess": true,
        "defaultToOAuthAuthentication": false,
        "minimumTlsVersion": "TLS1_2",
        "publicNetworkAccess": "Enabled",
        "supportsHttpsTrafficOnly": true
      },
      "sku": {
        "name": "Standard_LRS",
        "tier": "Standard"
      },
      "type": "Microsoft.Storage/storageAccounts"
    }
  ],
  "variables": {}
}

Which is a complete ARM template for the objects inside the RG, not the RG itself.

Please know, it is actually possible to extract a single resource from a given resource group like this:
#export the resource to a ARM template
az group export -g MyResourceGroupName --resource-ids "resourceId" >myresource.json


[SPARK-48577][SQL] Invalid UTF-8 byte sequence replacement

What changes were proposed in this pull request?
Added UTF8String methods for replacing invalid UTF-8 byte sequences within UTF8Strings.
Why are the changes needed?
By adding this method, we allow for predictable invalid UTF-8 byte sequence replacement using the Unicode replacement character (U+FFFD), as per the rules defined in the Unicode standard 15, Section 3.9, Paragraph D86, Table 3-7.
Does this PR introduce any user-facing change?
No.
How was this patch tested?
Unit tests in UTF8StringSuite.
Was this patch authored or co-authored using generative AI tooling?
No.

thanks, merging to master!


Unable to display calendar for the whole day

Hi everyone,
could anyone help please?
How do I show calendar from the beginning till the end of the day? When I set min = 0 am and max = 0 am of the next day - it does not show any slots http://take.ms/b6Huj

I got it, the calendar displays the whole day of pass min / max as undefined. Closing the issue.


[Feature]: Package proxying for deno.land, esm.sh etc.

Describe the feature you would like
When we are running multiple pipelines at the same time we have noticed that we can sometimes get 403 HTTP errors. We believe these to be because of too many requests to package repositories and CDNs blocking this traffic. One way around this could be to setup a local mirror or proxy requests to these package repositories. @mweichert mentioned setting up a Varnish instance, or similar tool, in front of deno.land, esm.sh, skypack, and any others we might want.
Is this feature solving a problem?
Prevents our CI requests to package managers from potentially being blocked by CDNs because of too many requests.
Code of Conduct

[X] I agree to follow this project's Code of Conduct

@mweichert if you have anymore information on this could you please add it here. Also could you please add any acceptance criteria you might have for setting this up.

First time I've heard of Verdaccio but it looks like a good fit!

After some discussions with SRE and Michael I am looking at using CICD caching and deno.lock files


links broken on flutter webpage https://github.com/flutter/flutter/wiki/Creating-Responsive-Apps

There are quite a few broken links:
https://github.com/flutter/flutter/wiki/Creating-Responsive-Apps

Thanks for the report!

cc @mjohnsullivan

Links have been updated and should now resolve correctly.


Basic app with NextJS using netlify-cms-backend-fs throws React hooks error

Describe the bug

When using netlify-cms-backend-fs as the backend, an invalid React hook error is thrown in the browser. From what I can tell, there is only one version of React and React-DOM being used. The issue appears to be with netlify-cms-backend-fs (should I create an issue at https://github.com/ADARTA/netlify-cms-components instead?).
To Reproduce

Loading Netlify CMS in the browser results in this error:
Error
There's been an error - please report it.

Details
Invariant Violation: Invalid hook call. Hooks can only be called inside of the body of a function component. This could happen for one of the following reasons: 1. You might have mismatching versions of React and the renderer (such as React DOM) 2. You might be breaking the Rules of Hooks 3. You might have more than one copy of React in the same app See https://fb.me/react-invalid-hook-call for tips about how to debug and fix this problem.

Expected behavior

Screenshots

All code + dependencies:

Applicable Versions:

Netlify CMS version: 2.9.1
OS: macOS
Browser version: Chrome Version 73.0.3683.86

Node.JS version: v10.13.0

CMS configuration

{
        backend: {
          name: "file-system",
          api_root: "/api"
        },
        media_folder: "static/uploads",
        public_folder: "/static/uploads",
        collections: [
          {
            name: "my-collection",
            label: "My Collection",
            folder: "content/my-collection",
            fields: [
              {
                name: "my-field",
                label: "My Field"
              }
            ]
          }
        ]
 }

Additional context

@tadhgcreedon You can create the issue on my component if you want.
The issue is that netlify-cms is not using React as a peer dependency. You need to be using netlify-cms-app instead. https://github.com/ADARTA/netlify-cms-components/tree/master/packages/netlify-cms-backend-fs

@talves Ah, I see - the README explains this, but I missed the distinction between netlify-cms and netlify-cms-app.
Thank you very much!

Just for clarity.  netlify-cms-app as the package with React as a peer dependency, so any implementation of registered components should use this version to be using a single instance of React. 😀


Expose ports in the docker executor when creating a container

Creating a service with:
service create --name redis --image redis:3.0.5 --ports redis:6379:6379

does not currently expose the requested port(s) on the nodes of the swarm cluster.  This PR adds the ExposedPorts to the ContainerConfig object and adds the PortBindings member to the HostConfig object.

Please sign your commits following these rules:
https://github.com/docker/docker/blob/master/CONTRIBUTING.md#sign-your-work
The easiest way to do this is to amend the last commit:
$ git clone -b "expose-ports" git@github.com:marccampbell/swarmkit.git somewhere
$ cd somewhere
$ git commit --amend -s --no-edit
$ git push -f

Ammending updates the existing PR. You DO NOT need to open a new one.

[Current coverage][cc-pull] is 52.63%

Merging [#911][cc-pull] into [master][cc-base-branch] will decrease coverage by 1.78%

5 files (not in diff) in agent were deleted. more
3 files (not in diff) in manager were modified. more

Misses +8
Partials +4
Hits +4

4 files (not in diff) in agent/exec were modified. more

Misses +6
Partials +4
Hits +13

4 files (not in diff) in agent were modified. more

Misses +223
Partials -3
Hits +3

File ...ntainer/container.go was modified. more

Misses -2
Partials 0
Hits +2

File .../test/deepcopy.pb.go (not in diff) was modified. more

Misses +11
Partials +9
Hits -20

@@             master       #911   diff @@
==========================================
  Files            75         70     -5
  Lines         11289      11176   -113
  Methods           0          0
  Messages          0          0
  Branches          0          0
==========================================
- Hits           6144       5883   -261
- Misses         4288       4459   +171
+ Partials        857        834    -23

[][cc-pull]

Powered by Codecov. Last updated by [e5a001d...40cb45b][cc-compare]
[cc-base-branch]: https://codecov.io/gh/docker/swarmkit/branch/master?src=pr
[cc-compare]: https://codecov.io/gh/docker/swarmkit/compare/e5a001d37e8cb9aa844e98e820a41e8e8cc01c0a...40cb45b0ec68d3317154b2c8ec18903f8427b258
[cc-pull]: https://codecov.io/gh/docker/swarmkit/pull/911?src=pr

@marccampbell This PR attempts to expose SwarmPort as a HostPort of every container which belongs to the service. But that wouldn't work if a single node gets assigned for more than one container of the service because of HostPort conflict.

If I need to expose a port to external (non-swarm) services, is there another method get the port to be exposed on the host using SwarmKit?

@marccampbell There is another method to access these services from outside the cluster. But that needs a version of docker which includes SwarmKit(there is a PR open in docker for this). With that version of docker once a service exposes a port, that port becomes accessible in all the nodes of the cluster using the corresponding SwarmPort.

Understood. I'll close this. Thanks for explaining.
On Jun 10, 2016 17:37, "Jana Radhakrishnan"<EMAIL_ADDRESS>wrote:

@marccampbell https://github.com/marccampbell There is another method
to access these services from outside the cluster. But that needs a version
of docker which includes SwarmKit(there is a PR open in docker for this).
With that version of docker once a service exposes a port, that port
becomes accessible in all the nodes of the cluster using the corresponding
SwarmPort.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/docker/swarmkit/pull/911#issuecomment-225325846, or mute
the thread
https://github.com/notifications/unsubscribe/AAKliyrvN00bvE8CxKkLziRqXIegBFybks5qKgNNgaJpZM4IzQO-
.


Applied fixes from StyleCI

This pull request applies code style fixes from an analysis carried out by StyleCI.

For more information, click here.

Changes Unknown when pulling dbaac940954cf6fd7322fcda7e8604fc54671eb2 on analysis-qvL44y into ** on master**.


Google Drive (?)

Source name
Google Drive
Source link
https://drive.google.com
Source language
All
Other details
I open this from the perspective that if there are images that can be downloaded and viewed online then an extension can be made from that
Also there is already a Google Drive but under Aniyomi, so I don't think it's impossible that an individual extension can be made for images
I have no idea about how extensions are generally made, so that's all I can say
I would like to believe that it would be similar for MEGA or Dropbox
Acknowledgements

[X] I have checked that the extension does not already exist by searching the extension listing and verified it does not appear there.
[X] I have searched the existing issues and this is a new ticket, NOT a duplicate or related to another open or closed issue.
[X] I have written a meaningful title with the source name.
[X] I will fill out all of the requested information in this form.

Not a keiyoushi contributor but i think this can hardly be done for a fundamental reason. Structure.
I mean you'll have to use your own drive because it will have to be carefully prepared.
Manga scrapers works with a structure : you can identify a Manga, where you find Chapters and within chapters you have pictures. I think the drive you are exploring would have to fulfill such conditions, by the simple mean of folders.
Manga Folder > Chapter folder > Pictures.  Finding a google drive that is fulfilling those conditions is hard unless you do it yourself :D
It seems to me that you just want an image viewer and downloader perhaps like this https://chromewebstore.google.com/detail/google-drive-image-viewer/kkphaaonihdkgkhlbalckaejbdjpiebf or this https://github.com/morozig/drive-photos.
I am just a random dev, in no way affiliated with Keiyoushi or Mihon so take my words with a grain of salt, i may be wrong.


change follow-redirect to 10 for fix eof error

Since 2015-11-14 12am(GMT), receive EOFError on event_source.
Firebase support team says,

We indeed introduced an extra redirect in the initial setup of the connection from the client to the correct Firebase server.
So I change follow-redirect to 10.

The issue is fixed.

Thanks! I feel 10 times is a bit too many though. What do you think about 5 times?

I'll be changing it from 10 to 5, if there's no further feedback and release a new version soon. As a side note, you could workaround this by setting max_redirects for the client. i.e.
client = RestFirebase.new(:max_redirects => 10)

or
client = RestFirebase.new
client.max_redirects = 10


Session search is not working on redaction app

Describe the bug in current situation
Session search is not working on redaction app
Link bug to the User Story
Impact of this bug
Describe the impact, i.e. what the impact is, and number of users impacted.
Chance of Occurring (high/medium/low/very low)
Pre Conditions: which Env, any pre-requesites or assumptions to execute steps?
Test-marshal
Steps to Reproduce
Steps to reproduce the behavior:

Go to Redaction app
Search for any sections on comment section
It is not showing up

Actual/ observed behaviour/ results
Expected behaviour
A clear and concise description of what you expected to happen. Use the gherking language.
Screenshots/ Visual Reference/ Source
If applicable, add screenshots to help explain your problem. You an use screengrab.

need to attempt to replicate via the comments search


-X isn't under help

The -X option which fixes https://github.com/thoughtbot/pick/issues/32 isn't documented under pick --help

This should also be added to an example for how to use this with vim.


proposal: image/png: Add HuffmanOnly compression levels.

Problem:
The HuffmanOnly option, which only performs Huffman encoding, is supported by the zlib library, but not by png using zlib.
Solution
Add a HuffmanOnly const to image/png.
Golang developer can pass the HuffmanOnly option with the code below and get a PNG with only huffman encoding.
png.Encoder{
    CompressionLevel: png.HuffmanOnly,
}

Are you proposing adding a new API to the image/png package? (Adding an exported constant is a new API.) If so, you'll need to follow the proposal process, see https://golang.org/s/proposal . Thanks.

Is it better to edit this issue (#59023) now as a template for a proposal?
Or should I follow the link below to create a new issue as a template for a proposal?
https://github.com/golang/proposal/blob/master/go2-language-changes.md
Thanks for your help.

@HyeockJinKim Either way is fine.  Thanks.

It would also be nice to work on supporting all zlib compression levels from 1-9, would you mind if I put that in the proposal as well?

I've rewritten it, please review it again. :cry:

CC @nigeltao

Adding const HuffmanOnly CompressionLevel = -4 to package png LGTM.
Optionally, if you also want to implement this (below) in image/png/writer.go, then that LGTM too.
    // Positive CompressionLevel values are reserved to mean a numeric zlib
    // compression level, although that is not implemented yet.

In hindsight, it would have been nice if the numeric values were consistent (and, perhaps, that 0 meant "default"). But it's too late to change existing constants.

Shall I add to CL to receive compression levels of 1-9?

I'm OK with that, but I'd also wait until there's a formal response to the proposal.


Add CMD to Dockerfile

At the moment the Dockerfile has no default CMD specified:
https://github.com/piccolo-orm/piccolo-admin-docker/blob/376f0ac0fd230036acd5e931703a275c1e774a71/Dockerfile
You have it in the Docker Compose file:
https://github.com/piccolo-orm/piccolo-admin-docker/blob/376f0ac0fd230036acd5e931703a275c1e774a71/docker-compose.yml#L4
But it should be in the Dockerfile instead, because someone might run the container without Docker Compose (e.g. via Kubernetes).
So it looks something like:
CMD ["python", "main.py"]

@dantownsend There was a CMD command in the Dockerfile, but I guess I accidentally deleted it at some point. Sorry. I can add that or would you?

@sinisaos Yes, we should add it. But I think it should be this:
CMD ["python", "main.py"]

Because you specify WORKDIR, you can use main.py instead of specifying the full path.
I'll just create some issues for things we can add, and if you want to pick any of them up just assign yourself to it. I can do some too, just want to make sure we don't duplicate work.

@dantownsend I just managed to try CMD ["python", "main.py"], but I get error from logs python: cannot open file '/code/main.py': [Errno 2] No such file or directory. If I run CMD ["python", "app/main.py"] everything works. I'm sorry if I'm doing something wrong, but I'm build a container with the command
docker build -t piccolo_admin .

and running the container with this command.
docker run --env-file .env -d --network=host --name admin_container piccolo_admin


PUT or POST interval action not work

Fix #1497
Added code to enable parameters to be included as body for POST and PUT
httpMethods.
Updated Scheduler.RST documentation to reflect the changes in types from Schedule, ScheduleEvent to Interval, IntervalAction.
Signed-off-by: xmlviking<EMAIL_ADDRESS>

Codecov Report

Merging #1538 into master will decrease coverage by 0.02%.
The diff coverage is 0%.

@@            Coverage Diff             @@
##           master    #1538      +/-   ##
==========================================
- Coverage   22.77%   22.74%   -0.03%
==========================================
  Files         102      102
  Lines        9586     9596      +10
==========================================
  Hits         2183     2183
- Misses       7224     7234      +10
  Partials      179      179

Impacted Files
Coverage Δ

internal/support/scheduler/schedule.go
0% <0%> (ø)
:arrow_up:

Continue to review full report at Codecov.

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

recheck

@xmlviking Be advised that docs are being deleted with this PR https://github.com/edgexfoundry/edgex-go/pull/1562
The content in this PR should be moved to the new egdex-docs repo

recheck

The docs have been moved into the edges-docs as well
On Thu, Jul 18, 2019 at 5:40 PM Trevor Conn<EMAIL_ADDRESS>wrote:

recheck
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/edgexfoundry/edgex-go/pull/1538?email_source=notifications&email_token=AAXO7B45JYB7HYSKX6X6NWLQADWM7A5CNFSM4ID3DG5KYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD2KAGPI#issuecomment-513016637,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAXO7BYFZIS5BLKYDCLVPMDQADWM7ANCNFSM4ID3DG5A
.

@xmlviking You'll need to address the conflict

Will do ty
On Thu, Jul 18, 2019 at 8:35 PM Trevor Conn<EMAIL_ADDRESS>wrote:

@xmlviking https://github.com/xmlviking You'll need to address the
conflict
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/edgexfoundry/edgex-go/pull/1538?email_source=notifications&email_token=AAXO7B7D2KSSYFUGJ76CDBLQAEK6FA5CNFSM4ID3DG5KYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD2KJTSI#issuecomment-513055177,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAXO7B5YLCJJ4ORTSARA34DQAEK6FANCNFSM4ID3DG5A
.

recheck

recheck


2.4/alpine build for httpd fails sporadically with "gpg: keyserver receive failed"

When using the 2.4/alpine Dockerfile as is, when building I sometimes get:
+ export GNUPGHOME=/tmp/tmp.PtzTUzm20r
+ gpg --keyserver ha.pool.sks-keyservers.net --recv-keys A93D62ECC3C8EA12DB220EC934EA76E6791485A8
gpg: keybox '/tmp/tmp.PtzTUzm20r/pubring.kbx' created
gpg: keyserver receive failed: Address not available

Seems this problem occurs elsewhere too, see:
gliderlabs, issue 306 or nodejs, issue 380 for example.
Maybe some of the keyservers are not very reliable.
I did not find a way to make this reproducible.
Unrelated to this, I think an apk update should be added before using any other apk commands.

Yes, we often see issues with different servers in the sks-keyservers pools (and occasionally issues with the DNS of sks-keyservers.net itself) -- ideally, mirrors with issues would be removed from the upstream pools, but that's not always feasible (or timely), so retrying (or trying other mirrors upon failure) are our only real options.


18431 - Khanty - Society match question/suggestions

Once the song metadata corrections in theglobaljukebox/cantometrics#107 are implemented, the songs currently assigned to 18431 will fall into 3 locations:

Shuryshkarsky District, lat-lon 65.40, 64.70 - Song 3440
Beryozovo, lat-lon 63.93, 65.04 - Songs 3446, 3447, 3448
Salekhard, lat-lon 66.53, 66.6 - Songs 3441, 3442, 3443, 3444, 3445, 3449

From what I can tell, 1 and 2 both seem to match well with D-PLACE xd618, language khan1273. @kirbykat do you agree? My reasoning for matching both of these locations with xd618 is that bere1252 and sury1234 are two dialects of khan1273 that I assume correspond with Beryozovo and Shuryshkarsky, respectively.
However, 3 probably matches best with language obdo1234.
Some options are:

Keep all songs assigned to 18431, match with xd618, but flag as an unclear case.
Keep songs from locations 1 and 2 assigned to 18431, rename society "Ob Khanty" or something like that, and match with D-PLACE xd618, language khan1273. Create new society "Obdorsk Khanty" or "Salekhard Khanty", assign songs from location 3 to it, match to language obdo1234, no D-PLACE match. Society lat-lons would be average of song lat-lons.

Would love @kirbykat's opinion on this.

Decided to go with option 1 for now. Can always split later if needed.


URLSession: Fix redirection response handling

300 Multiple Choices: Do not follow the redirect, just return the body
from the response. However HEAD requests return no body.

301 Moved Permanently, 302 Found: Follow the redirect but send POST
requests as GET when following the redirect.

303 See Other: Follow the redirect but always send the request to the
new Location as a GET.

304 Not Modified: No special handling or redirects to follow since the
server decides whether to send a response based on the request headers
If-Modified-Since or If-None-Match.

305 Use Proxy, 306 Switch Proxy, 307 Temporary Redirect,
308 Permanent Redirect:
Follow the redirection but do not change the method, just repeat the
request to the new location.

This fix applies for valid redirections in the range 300-308, other
3xx codes have no specific support.

Redirection handling should now match Darwin more closely.
Resolves SR-2679: URLSession delivers redirection delegate methods
in the wrong order.
SR-11673: URLSession download task merges redirect responses.

@swift-ci test linux


Multiple mode: Search text is not cleared on tab out

When the search value does not match any option and the user tabs out the select, the text remains visible. This might lead to confusions since the user could think the value is valid.
It doesn't happen if the user clicks out. In this case, the search text is deleted.

+1 Uncommenting this solves the issue for me, thanks @iroa.  If there is an invalid or empty input I want it to reset to the matched (model) option.
// if(~[KEY.ESC,KEY.TAB].indexOf(key)){
// //TODO: SEGURO?
// ctrl.close();
// }

I can also confirm that the attribute does not work, but uncommenting that code does work.

+1

+1

+1

+1

Hey guys, please refrain from only adding +1 to issues.  It adds nothing to the discussion and clutters up the thread.  If you would like a feature implemented or bug fixed and it's not getting the attention you feel it deserves we do support user-supplied PRs.

+1

@iroa solution does work, but it loses the functionality of selecting an item when you press tab. The proper solution would be to clear it, only if no results were found.

I have the 0.17.1 version (released on 2016-05-16) and it is still not fixed. Do you have any intention to fix it?

@mihai-vasilache feel free to submit a PR that fixes the issue (including unit tests)  will be happy to review and merge. :smiley:

I came upon this issue today and I've made a PR fix it : #1659
Be free to test it out and give me your feedback !

So @user378230 asks for a PR because too many people were +1-ing it (which I think means I agree, it's an issue for me, please fix), @ahocquet provides said PR and still this remains an issue.
This has been open since Nov 2014. Update please?

+1
(not working in (0.19.6)

+1

+!


Usage of limited characters

Why are we using limited set of characters like {1,10} or {1,20} when using a + would take care of any length payload. For e.g, https://github.com/coreruleset/coreruleset/blob/914f7a5e75401061c39be75b625ea9b0e4e76d65/regex-assembly/942390.ra#L8
Same also applies for a few other rules.

This could be for performance (-> backtracking) reasons.

You may be right, but some rules use {1,100}. Also, some payloads are based on a . which could lead to FPs I think.

It is just to prevent ReDOS for engines by adding just a +. The values are just an heuristic, and as you said, sometimes they are not documented.
I remember doing the imap/smtp rules and based the expressions on the rfc.


Altitude Hold

Hello,
I am just starting with the CF quadrotor and I had some questions. Is it possible with this implementation to maintain a given altitude and control linear velocities in x and y independently?  Or do i have to send commands in thrust as well if I'm publishing on the cmd_vel topic?

The included controller is a PID position controller, controlling roll/pitch/yaw and thrust independently. You could just keep the thrust component and write a custom control portion for x and y. If you use the controller, you don't need to publish on the cmd_vel topic (there is a goal-topic instead).

So I could just use the thrust component in the controller and send a goal in height then send command directly to cmd_vel topic to control pitch, roll and yaw separately?

You can't use cmd_vel and goal at the same time. You can, however, copy the code from the current controller, keep the thrust component and compute the other values to your liking.


Reporting a possible typo in Step 47 of the Decimal-To-Binary Converter Tutorial Project

Describe the Issue
In the second paragraph of Step 47:

The call stack is a collection of function calls stored in a stack structure. When you call a function, it is added to the top or of the stack, and when it returns, it is removed from the top / end of the stack.

Per my understanding of the text, the "or" (italic and bold) should be removed.
Affected Page
https://www.freecodecamp.org/learn/javascript-algorithms-and-data-structures-v8/learn-recursion-by-building-a-decimal-to-binary-converter/step-47
Your code
There is nothing wrong with the testing for this step; it is just a typo.
Expected behavior
The "or" as pointed out above should be deleted.
Screenshots
No response
System

Device: [e.g. iPhone 6, Laptop]
OS: [e.g. iOS 14, Windows 10, Ubuntu 20.04]
Browser: [e.g. Chrome, Safari]
Version: [e.g. 22]

Additional context
No response

Thanks for opening this issue.
This looks something that can be fixed by "first time" code contributors to this repository. Here are the files that you should be looking at to work on a fix:
List of files:

https://github.com/freeCodeCamp/freeCodeCamp/blob/main/curriculum/challenges/english/15-javascript-algorithms-and-data-structures-22/learn-recursion-by-building-a-decimal-to-binary-converter/645cbb5ab1296e49946adb6e.md

Please make sure you read our guidelines for contributing, we prioritize contributors following the instructions in our guides. Join us in our chat room or the forum if you need help contributing, our moderators will guide you through this.
Sometimes we may get more than one pull requests. We typically accept the most quality contribution followed by the one that is made first.
Happy contributing.


Add PHP file support

Like the other issues. This extension sounds awesome but does not work with .php files.

I was digging into this to see if it's possible and what I've found is:

A specific language's autocompletion is always used
This extension is using the Custom Data Extension Contributes, which only supports .html and .css file extensions

This means that in order to have htmx tags available, the specific language being used for autocompletion would have to include htmx tag in their own extension.
An example of this is issue: support jsx where the suggestion was to use another package with built in htmx support for jsx (which is a .js or .jsx extension).
Similar Issues:
Add .pug files
add .astro files support
The scope of this extension only applies to autocompletion for .html files.
https://code.visualstudio.com/api/extension-guides/custom-data-extension


Update README.md

Updating the using part of the README file.

Thanks for the PR!
As a small improvement, could you mark the method async, and add an await on the list assignment?
If you don't have time, that's fine, I'll merge and update afterwards.  As a quick heads-up, I haven't done this yet in GH, but will try my best to make sure your contribution is attributed to you.
Thanks again!

Alright! I assume that is the improvement needed, right?
:)

Otherwise, I feel that the entire thing can be revamped a bit more, to show more in-depth examples directly there, such that it is easier for absolute beginners to use.
Once I have the time to familiarise with this, maybe I can help a little, if you don't mind? :)

Oops... Seems I'm not up to the job. Sorry for the mistakes!

No problem, I'm fumbling around to figure out how best to merge - thanks for bearing with me as I try this for the first time =D.
Hope you are finding the library useful, if you have improvements, I would love the help!
Thanks,
Mike

Sure!
I always liked attempting to help in other's GitHub projects, as it seems like a great and fun way to learn programming.


Sep2016 doc fixes

Two docs issues.
When this is merged, please resolve DOCUMENT-581, as well as the PUP ticket cited in the commit messages below.
Lemme know if I should be targeting a different branch to accommodate release timing or whatevs.

CLA signed by all contributors.

+1 to changes - state of branches unknown though, would have merged otherwise

Maybe @geoffnichols can advise on branch. I'm out of that loop this time around.


Added a Snake Game

🛠 Fixes Issue  #4
👨💻 Changes proposed and Brief Description
A small snake game that illustrates how js works

[ ] My code doesn't break any part of the project
[ ] This PR does not contain plagiarized content.
[ ] My Addition/Changes works properly and matches the overall repo pattern.
[ ] The title of my pull request is a short description of the requested changes.

📄 Note to reviewers
Use arrow keys in laptop/desktop to start playing
📷 Screenshots

Empty folder


Make apps belonging to deleted/disabled unavailable

What would you like to be added:
Applications that belong to the deleted/disabled environment need some kind of action.
I would say simply:

all applications belonging to the deleted environment should be deleted immediately.
all applications belonging to the disabled environment should be disabled immediately.

Why is this needed:

I think the fundamental motivation of disabling/deleting environments is just wanting to operate applications in bulk. Based on this premise, I propose a new behavior for each operation on the web.
When deleting an environment:

All applications that belong to the environment get deleted as well
If there is any Piped that has permission to the environment to be deleted, it will show a warning that prompts to delete it from the environment list. Like for example, let's say we're trying to delete the env named "nakabonne-dev". We have to delete that on the Piped setting page:

When disabling an environment:

All applications that belong to the environment get disabled as well

When enabling an environment:

Nothing to do other than deleting the env

When enabling an application:

Check if the environment that the application belongs to, and returns an error if that environment is still disabled.

What would you say? If you feel it gets a little bit complicated, one thing that we can pick up is to stop providing the disabling feature for environments. It could be enough to come with the capability to delete.

We settled on just supporting the deleting feature for now. Once pushing the delete button on the Environment page, it:

checks if there is any Piped that has permission to the environment to be deleted.

If there is, it shows a warning that prompts to delete it from the environment list, and cancel deleting.

shows a popup to confirm the belonging applications will get deleted
deletes the environment and all applications within that.


Create a function that returns the license link If there is no license, return an empty string

figured out. completed.


Make bootstrap error message more informative and better-fitting

Now this better fits standard vscode extension activation failure message and suggests enabling verbose logs.

bors r+


error[E0308]  [E0053] [E0277]

After I executed cargo update and then executed cargo build, I encountered many similar errors as follows:

Can you help me resolve them? thanks!

ityfuzz depends on some old features of revm, therefore alloy and some other related packages.


Remove unnecessary S3 API call

When creating a Resource from an ObjectSummary, we already know that the
object exists. Otherwise, we would not have an ObjectSummary about it.
So we can remove the exists() check, which causes a HEAD request for
every single matching object.
This reduces the number of HTTP calls from n+1 to 1.

thanks @cbuehler


⚠ otzivi-tut has degraded performance

In 1728157, otzivi-tut (https://отзывы-тут.рф/) experienced degraded performance:

HTTP code: 200
Response time: 8634 ms

Resolved: otzivi-tut performance has improved in b61b252.


Optimize exports

Most importantly I've added a cache for the reified old versions of workflows and contents. This seemed to be amazingly slow even if dealing with the latest version. I'm also preloading subjects and handling the check for retiredness less stupidly.

LGTM - rebase?


shrinking memory

Currently at no stage do we shrink memory. Ideally we could have a rule running in the background that does something like: "if usage hasn't exceeded 25% in the last 10 seconds, half the amount of items kept in the stack".
We could run this in the background using an async_std::stream::interval inside of a task::spawn kept inside of Pin<Box<JoinHandle>> inside the Pool. We would never await it, and just quietly let it run in the background.
The only downside here is that it ties itself to async-std; but this is probably better than creating a new timer from scratch, spawning a dedicated timer thread, or adding built-in timing logic that's run on each call. I kind of wish this was built into the stdlib so it would be easy to rely on, but alas.

Hmmm, could you explain why you using the timer from async-std is better than a decided timer thread?
I could also imagine a heuristic based on usage instead of time.

Another ideas:

We can provide an API for setting a limit for the free queue. If the limit is reached, then we do not push new items.
We can use time as @yoshuawuyts proposed, but instead of having a task we can trigger shrinking on Pool::get and ItemGuard::drop.

My reasoning for not shrinking based on usage is because it would be hit on every operation. E.g. if we serve a million requests/second, we'd be doing extra (atomic) operations on every one of those. Instead sampling every n millis should provide the same insight at less cost, and checking if we should shrink at most every n seconds is probably the best way to protect against spikes.
But yeah it might very well be that I overestimated these costs, and we notice the overhead of doing this is not big enough that it matters. Probably should test it out (:


Fixed BillingReports request method

Fixed BillingReports request method when there is no report available for specified period (204 No content)

Thanks for your contribution!


HTTP Error 401 when downloading playlist from ufcfightpass.com

Checklist

[x] I'm reporting a broken site support
[x] I've verified that I'm running youtube-dl version 2020.05.29
[x] I've checked that all provided URLs are alive and playable in a browser
[x] I've checked that all URLs and arguments with special characters are properly quoted or escaped
[x] I've searched the bugtracker for similar issues including closed ones

Verbose log

[debug] System config: []
[debug] User config: []
[debug] Custom config: []
[debug] Command-line args: ['-v', '--write-sub', '--playlist-reverse', '-f', 'bestvideo[height<=?1300][container=mp4_dash]+bestaudio/best[height<=?1300]', '--fragment-retries=infinite', '--username', 'PRIVATE', '--password', 'PRIVATE', 'https://ufcfightpass.com/playlist/1861']
[debug] Encodings: locale cp1252, fs mbcs, out cp437, pref cp1252
[debug] youtube-dl version 2020.05.29
[debug] Python version 3.4.4 (CPython) - Windows-10-10.0.18362
[debug] exe versions: ffmpeg 4.2.2, ffprobe 4.2.2
[debug] Proxy map: {}
[UFCTV] Logging in
[UFCTV] 1861: Downloading JSON metadata
[download] Downloading playlist: UFC 2005 REPLAYS
[UFCTV] playlist UFC 2005 REPLAYS: Collected 10 video ids (downloading 10 of them)
[download] Downloading video 1 of 10
[UFCTV] 32534: Downloading JSON metadata
[UFCTV] 32534: Downloading JSON metadata
[UFCTV] 32534: Downloading m3u8 information
[UFCTV] 32534: Downloading MPD manifest
[download] UFC 51 - Super Saturday-32534.mp4 has already been downloaded and merged
[download] Downloading video 2 of 10
[UFCTV] 31561: Downloading JSON metadata
[UFCTV] 31561: Downloading JSON metadata
[UFCTV] 31561: Downloading m3u8 information
[UFCTV] 31561: Downloading MPD manifest
[download] TUF 1 Finale - TUF 1 Finale-31561.mp4 has already been downloaded and merged
[download] Downloading video 3 of 10
[UFCTV] 30494: Downloading JSON metadata
[UFCTV] 30494: Downloading JSON metadata
[UFCTV] 30494: Downloading m3u8 information
[UFCTV] 30494: Downloading MPD manifest
[download] UFC 52 - Couture vs Liddell 2-30494.mp4 has already been downloaded and merged
[download] Downloading video 4 of 10
[UFCTV] 30482: Downloading JSON metadata
[UFCTV] 30482: Downloading JSON metadata
[UFCTV] 30482: Downloading m3u8 information
[UFCTV] 30482: Downloading MPD manifest
[debug] Invoking downloader on 'https://dve-streams.akamaized.net/MjAxOQ/Mw/M_TQ/NzE_0NzM/REFTSA/MQ/master.mpd?hdnea=exp=1590785870~acl=/MjAxOQ/Mw/M_TQ/NzE_0NzM/REFTSA/MQ/*~id=39ceb221-d55a-422e-aa34-cdaa59d51bb1~hmac=ad1e3ed84e6c09803dce4dc14f7b09dc9784b3d5c9df31d63a62a01e719bbe55'
[dashsegments] Total fragments: 1155
[download] Destination: UFC 53 - Heavy Hitters-30482.fdash-6.mp4
[download] 100% of 2.42GiB in 42:44
[debug] Invoking downloader on 'https://dve-streams.akamaized.net/MjAxOQ/Mw/M_TQ/NzE_0NzM/REFTSA/MQ/master.mpd?hdnea=exp=1590785870~acl=/MjAxOQ/Mw/M_TQ/NzE_0NzM/REFTSA/MQ/*~id=39ceb221-d55a-422e-aa34-cdaa59d51bb1~hmac=ad1e3ed84e6c09803dce4dc14f7b09dc9784b3d5c9df31d63a62a01e719bbe55'
[dashsegments] Total fragments: 1155
[download] Destination: UFC 53 - Heavy Hitters-30482.fdash-5.m4a
[download] 100% of 108.15MiB in 10:54
[ffmpeg] Merging formats into "UFC 53 - Heavy Hitters-30482.mp4"
[debug] ffmpeg command line: ffmpeg -y -loglevel "repeat+info" -i "file:UFC 53 - Heavy Hitters-30482.fdash-6.mp4" -i "file:UFC 53 - Heavy Hitters-30482.fdash-5.m4a" -c copy -map "0:v:0" -map "1:a:0" "file:UFC 53 - Heavy Hitters-30482.temp.mp4"
Deleting original file UFC 53 - Heavy Hitters-30482.fdash-6.mp4 (pass -k to keep)
Deleting original file UFC 53 - Heavy Hitters-30482.fdash-5.m4a (pass -k to keep)
[download] Downloading video 5 of 10
[UFCTV] 31195: Downloading JSON metadata
ERROR: Unable to download JSON metadata: HTTP Error 401: Unauthorized (caused by HTTPError()); please report this issue on https://yt-dl.org/bug . Make sure you are using the latest version; type  youtube-dl -U  to update. Be sure to call youtube-dl with the --verbose flag and include its complete output.
  File "C:\Users\dst\AppData\Roaming\Build archive\youtube-dl\ytdl-org\tmpxtvjzx45\build\youtube_dl\extractor\common.py", line 627, in _request_webpage
  File "C:\Users\dst\AppData\Roaming\Build archive\youtube-dl\ytdl-org\tmpxtvjzx45\build\youtube_dl\YoutubeDL.py", line 2238, in urlopen
  File "C:\Python\Python34\lib\urllib\request.py", line 470, in open
  File "C:\Python\Python34\lib\urllib\request.py", line 580, in http_response
  File "C:\Python\Python34\lib\urllib\request.py", line 508, in error
  File "C:\Python\Python34\lib\urllib\request.py", line 442, in _call_chain
  File "C:\Python\Python34\lib\urllib\request.py", line 588, in http_error_default

Description

Fails with an HTTP Error 401 when trying to download a playlist, but it only happens after yt-dl finished downloading the previous video on the list.
Notice in the above log there's no problem going through the previously-downloaded videos (1st-3rd out of 10), there's no problem downloading a video which wasn't previously downloaded (4th), the error only comes up with the next one (5th).
Restarting yt-dl with the exact same command will do the same thing - it'll go through the list, skip the now-downloaded video (4th), download the one which yt-dl failed at (5th), and fail with the next one (6th out of 10).
Starting yt-dl with each specific video url instead of playlist url won't have this issue whether running in series or in parallel.
Happens from both ends of the list, as in with and without --playlist-reverse.
I suspect maybe the authentication gets dropped once yt-dl finishes downloading a video for some reason, and yt-dl would have to re-authenticate after every downloaded video in a list?
Edit: Forgot to provide example url:
https://ufcfightpass.com/playlist/1861
It happens with every playlist I tried there.

Updated to youtube-dl version 2020.06.06
Same issue.
Can provide verbose log if required but it kinda looks the same.

I'm having this same issue running version 2021.04.26.
Worth mentioning is that it seems to fail after having downloaded 2 videos (i.e on the third video attempted)
Running the exact same command again Downloads the next 2 videos in the same playlist ( this is how all the earlier videos in the playlist were downloaded)
Issue occurs no matter which playlist is attempted
youtube-dl https://ufcfightpass.com/playlist/3926/ufc-hall-of-fame-georges-st-pierre --verbose
[debug] System config: []
[debug] User config: ['-o', '%(title)s.%(ext)s', '--netrc']
[debug] Custom config: []
[debug] Command-line args: ['https://ufcfightpass.com/playlist/3926/ufc-hall-of-fame-georges-st-pierre', '--verbose']
[debug] Encodings: locale UTF-8, fs utf-8, out utf-8, pref UTF-8
[debug] youtube-dl version 2021.04.26
[debug] Python version 3.9.5 (CPython) - Linux-5.10.36-2-MANJARO-x86_64-with-glibc2.33
[debug] exe versions: ffmpeg 4.4, ffprobe 4.4, rtmpdump 2.4
[debug] Proxy map: {}
[UFCTV] Logging in
[UFCTV] 3926: Downloading JSON metadata
[download] Downloading playlist: UFC Hall of Fame: Georges St-Pierre
[UFCTV] playlist UFC Hall of Fame: Georges St-Pierre: Collected 23 video ids (downloading 23 of them)
[download] Downloading video 1 of 23
[UFCTV] 60726: Downloading JSON metadata
[UFCTV] 60726: Downloading JSON metadata
[UFCTV] 60726: Downloading m3u8 information
[UFCTV] 60726: Downloading MPD manifest
[debug] Default format spec: bestvideo+bestaudio/best
[download] Georges St-Pierre vs Michael Bisping UFC 217.mp4 has already been downloaded and merged
[download] Downloading video 2 of 23
[UFCTV] 31444: Downloading JSON metadata
[UFCTV] 31444: Downloading JSON metadata
[UFCTV] 31444: Downloading m3u8 information
[UFCTV] 31444: Downloading MPD manifest
[debug] Default format spec: bestvideo+bestaudio/best
[download] Georges St-Pierre vs. Johny Hendricks UFC 167.mp4 has already been downloaded and merged
[download] Downloading video 3 of 23
[UFCTV] 30293: Downloading JSON metadata
[UFCTV] 30293: Downloading JSON metadata
[UFCTV] 30293: Downloading m3u8 information
[UFCTV] 30293: Downloading MPD manifest
[debug] Default format spec: bestvideo+bestaudio/best
[download] Georges St-Pierre vs. Nick Diaz UFC 158.mp4 has already been downloaded and merged
[download] Downloading video 4 of 23
[UFCTV] 30574: Downloading JSON metadata
[UFCTV] 30574: Downloading JSON metadata
[UFCTV] 30574: Downloading m3u8 information
[UFCTV] 30574: Downloading MPD manifest
[debug] Default format spec: bestvideo+bestaudio/best
[download] Georges St-Pierre vs. Carlos Condit UFC 154.mp4 has already been downloaded and merged
[download] Downloading video 5 of 23
[UFCTV] 30212: Downloading JSON metadata
[UFCTV] 30212: Downloading JSON metadata
[UFCTV] 30212: Downloading m3u8 information
[UFCTV] 30212: Downloading MPD manifest
[debug] Default format spec: bestvideo+bestaudio/best
[download] Georges St-Pierre vs. Jake Shields UFC 129.mp4 has already been downloaded and merged
[download] Downloading video 6 of 23
[UFCTV] 30294: Downloading JSON metadata
[UFCTV] 30294: Downloading JSON metadata
[UFCTV] 30294: Downloading m3u8 information
[UFCTV] 30294: Downloading MPD manifest
[debug] Default format spec: bestvideo+bestaudio/best
[download] Georges St-Pierre vs. Josh Koscheck UFC 124.mp4 has already been downloaded and merged
[download] Downloading video 7 of 23
[UFCTV] 30121: Downloading JSON metadata
[UFCTV] 30121: Downloading JSON metadata
[UFCTV] 30121: Downloading m3u8 information
[UFCTV] 30121: Downloading MPD manifest
[debug] Default format spec: bestvideo+bestaudio/best
[debug] Invoking downloader on 'https://dve-streams.akamaized.net/MjAxOQ/Mw/M_TQ/NzE_xMTM/SE-xT_/MQ/video/3036576/index.m3u8?hdntl=exp=1622223104~acl=%2F*~id=8b509cd7-8e09-42fa-a64a-518addc816f4~data=hdntl~hmac=4ff3e405b2e1a21e48d1a4eaa8f9faa7d8d98a7bc91d083f20c871b642d67f6c'
[hlsnative] Downloading m3u8 manifest
[hlsnative] Total fragments: 443
[download] Destination: Georges St-Pierre vs. Dan Hardy UFC 111.fhls-3353.mp4
[download] 100% of 991.90MiB in 04:15
[debug] Invoking downloader on 'https://dve-streams.akamaized.net/MjAxOQ/Mw/M_TQ/NzE_xMTM/REFTSA/MQ/master.mpd?hdnea=exp=1622136714~acl=/MjAxOQ/Mw/M_TQ/NzE_xMTM/REFTSA/MQ/~id=09cceace-1f87-42c5-a0c8-03ad1a936914~hmac=31cf539572e2c8553a630d6cc548ecc49e0aff8b750e93cee48542f1edf8d62a'
[dashsegments] Total fragments: 444
[download] Destination: Georges St-Pierre vs. Dan Hardy UFC 111.fdash-4.m4a
[download] 100% of 41.44MiB in 02:19
[ffmpeg] Merging formats into "Georges St-Pierre vs. Dan Hardy UFC 111.mp4"
[debug] ffmpeg command line: ffmpeg -y -loglevel repeat+info -i 'file:Georges St-Pierre vs. Dan Hardy UFC 111.fhls-3353.mp4' -i 'file:Georges St-Pierre vs. Dan Hardy UFC 111.fdash-4.m4a' -c copy -map 0:v:0 -map 1:a:0 'file:Georges St-Pierre vs. Dan Hardy UFC 111.temp.mp4'
Deleting original file Georges St-Pierre vs. Dan Hardy UFC 111.fhls-3353.mp4 (pass -k to keep)
Deleting original file Georges St-Pierre vs. Dan Hardy UFC 111.fdash-4.m4a (pass -k to keep)
[download] Downloading video 8 of 23
[UFCTV] 30205: Downloading JSON metadata
[UFCTV] 30205: Downloading JSON metadata
[UFCTV] 30205: Downloading m3u8 information
[UFCTV] 30205: Downloading MPD manifest
[debug] Default format spec: bestvideo+bestaudio/best
[debug] Invoking downloader on 'https://dve-streams.akamaized.net/MjAxOQ/Mw/M_TQ/NzE_xOTc/SE-xT_/MQ/video/3005546/index.m3u8?hdntl=exp=1622223509~acl=%2F~id=18da939b-c9bd-46fd-b157-ae58504c4eca~data=hdntl~hmac=373046c75e1e8a4d99db743499b8c623d10e31044c4f562c501dbc2b66f27f61'
[hlsnative] Downloading m3u8 manifest
[hlsnative] Total fragments: 391
[download] Destination: Georges St-Pierre vs BJ Penn UFC 94.fhls-3331.mp4
[download] 100% of 867.08MiB in 03:31
[debug] Invoking downloader on 'https://dve-streams.akamaized.net/MjAxOQ/Mw/M_TQ/NzE_xOTc/REFTSA/MQ/master.mpd?hdnea=exp=1622137119~acl=/MjAxOQ/Mw/M_TQ/NzE_xOTc/REFTSA/MQ/*~id=5d0b0501-4f7b-4c89-9349-8f4dac17476d~hmac=38c3c140901e292e8cf71fa03eacb13786bfa53519c53d15cb79ecf138f275e2'
[dashsegments] Total fragments: 392
[download] Destination: Georges St-Pierre vs BJ Penn UFC 94.fdash-5.m4a
[download] 100% of 36.31MiB in 02:34
[ffmpeg] Merging formats into "Georges St-Pierre vs BJ Penn UFC 94.mp4"
[debug] ffmpeg command line: ffmpeg -y -loglevel repeat+info -i 'file:Georges St-Pierre vs BJ Penn UFC 94.fhls-3331.mp4' -i 'file:Georges St-Pierre vs BJ Penn UFC 94.fdash-5.m4a' -c copy -map 0:v:0 -map 1:a:0 'file:Georges St-Pierre vs BJ Penn UFC 94.temp.mp4'
Deleting original file Georges St-Pierre vs BJ Penn UFC 94.fhls-3331.mp4 (pass -k to keep)
Deleting original file Georges St-Pierre vs BJ Penn UFC 94.fdash-5.m4a (pass -k to keep)
[download] Downloading video 9 of 23
[UFCTV] 32155: Downloading JSON metadata
ERROR: Unable to download JSON metadata: HTTP Error 401: Unauthorized (caused by <HTTPError 401: 'Unauthorized'>); please report this issue on https://yt-dl.org/bug . Make sure you are using the latest version; see  https://yt-dl.org/update  on how to update. Be sure to call youtube-dl with the --verbose flag and include its complete output.
File "/usr/lib/python3.9/site-packages/youtube_dl/extractor/common.py", line 634, in _request_webpage
return self._downloader.urlopen(url_or_request)
File "/usr/lib/python3.9/site-packages/youtube_dl/YoutubeDL.py", line 2279, in urlopen
return self._opener.open(req, timeout=self._socket_timeout)
File "/usr/lib/python3.9/urllib/request.py", line 523, in open
response = meth(req, response)
File "/usr/lib/python3.9/urllib/request.py", line 632, in http_response
response = self.parent.error(
File "/usr/lib/python3.9/urllib/request.py", line 561, in error
return self._call_chain(*args)
File "/usr/lib/python3.9/urllib/request.py", line 494, in _call_chain
result = func(*args)
File "/usr/lib/python3.9/urllib/request.py", line 641, in http_error_default
raise HTTPError(req.full_url, code, msg, hdrs, fp)


Added better installation method

This is probably what post users want

In the install section, I prefer to leave just the basic npm install command. In the later instructions, we can add --save-dev.


Generate UML diagrams from source

Having a diagrams of all the data structures of BDG-Formats would help a newcomer get started in the project.
Many tools allow us to generate such a diagram automatically from Java sources, like UMLGraph which is open source.
I'll submit a pull request shortly that achieves this feature.

Closed by #48.


Distributed Tracing

Add distributed tracing support to Core
- [x] Azure.Core abstraction layer
- [x] CodeGen to light up feature
- [x] OTel adapter
- [ ] Beta Release
- [ ] Stable Release

Looking at this from the lens of Service Bus we're missing some features (or it could be that they're not 1:1 with the Java/.NET layers)

Links, which we can use to link multiple spans together, don't exist (yet). This is different than the parent/child relationship between spans. From @lmolkova's gist: builder.addLink

Getting a SpanContext, which has fields like the TraceID, SpanID and trace options (unsure of this last one). getDiagnosticId


Fix warn found by https://github.com/apache/incubator-nuttx/pull/7391

Summary
Found by https://github.com/apache/incubator-nuttx/pull/7391
Impact
Minor
Testing
Pass CI

@pkarashchenko could you merge this simple change? I can continue on https://github.com/apache/incubator-nuttx/pull/ only after this patch get merged.

Yes. Just waiting for CI to pass


@qualweb/qw-page: fix unit tests

The unit tests launch a Puppeteer instance at the beginning of a test but doesn't correctly close it again (the statements are commented out).
The tests should probably be refactored to move Puppeteer launch/close into setup/teardown functions (check the @qualweb/act-rules package for how this was done in an earlier pass).

Duplicate of #13


Use the in-cluster ECP resources by default

Ref: https://issues.redhat.com/browse/EC-143

/retest
quay.io was down which is likely the root cause of the failure


Optimizing of ../priv/static/js/app.js failed. L12175:31 SyntaxError: Unexpected token: operator (>)

Able to build this project (that uses react-native-web) in dev.
But when I run yarn deploy, I get the entitled error.
Looked around online to no avail...

shitty error — sorry bro


Add background to MapboxVector layer

This pull request makes it so the MapboxVector layer picks up the background from the style. This is achieved by adding a polygon as first feature to each tile, which covers the whole tile extent and is filled with the background's color and opacity.
Fixes #13023.

At some point, we could add support for a background option on vector (or all) layers.  Not sure how often it would get used, but it would be pretty straightforward to handle it at the layer renderer level.

Actually I was thinking the same. I'probably start working on a background option soon, now that you also suggest it.


Run tests on PRs that change the javascript dependencies

Tests did not get run on https://github.com/ietf-tools/datatracker/pull/3954, and I think it would have helped if they had been.

Fixed by 2b94db216128d629dc344b85afb8035ec59b6330


⚠ Bofrost.si has degraded performance

In b8cec9e, Bofrost.si (https://www.bofrost.si) experienced degraded performance:

HTTP code: 200
Response time: 2436 ms

Resolved: Bofrost.si performance has improved in 04cf9bb.