k3s deployment/service status incorrect after a few restarts of both master nodes.

Environmental Info:
K3s Version:
v1.18.6+k3s1
Node(s) CPU architecture, OS, and Version:
uname -a
Linux tpvm 5.3.0-40-generic #32~18.04.1-Ubuntu SMP Mon Feb 3 14:05:59 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux
Cluster Configuration:
2 Masters - I understand this is not recommended but thats what one of our customer has
Both running on Ubuntu 18.04
Mariadb is the backend for both using galera cluster.
Describe the bug:

Initial deployment of the application services is fine. However very occasionally when both nodes are rebooted together (to simulate a double fault, to check if there is a split brain), we see that only a few (4 services) are deployed on both nodes from the output
k3s kubectl -n  get pods -o wide
It takes a really long time (2-3 hours) for k3s to return back to a state of sanity if at all. In a lot of cases we've had to restart k3s using systemctl restart k3s on both nodes to get it to reflect the right deployment status and pods.
I've verified that mariadb is functional and responds to all queries as needed. k3s database is available too.
Steps To Reproduce:

Installed K3s:
deployed application
restart both nodes together a few times (about 5-6 cycles)

Expected behavior:

All the pods/services to show up in the right state and if they need to be deployed - k3s should do it.
Actual behavior:

Only a few pods show up as deployed and running and rest of them are not shown.
Additional context / logs:

Heres the application deployment state
kube-system pods are fine
kube-system Pods :
NAME                       READY   STATUS    RESTARTS   AGE     IP             NODE    NOMINATED NODE   READINESS GATES
node-local-dns-266pf       1/1     Running   44         2d4h    <IP_ADDRESS>   tpvm2   <none>           <none>
coredns-6dbbdcb79c-q7tf8   1/1     Running   0          7m21s   <IP_ADDRESS>    tpvm2   <none>           <none>
node-local-dns-sj9bx       1/1     Running   8          2d4h    <IP_ADDRESS>   tpvm1   <none>           <none>
coredns-6dbbdcb79c-gg7jn   1/1     Running   2          8h      <IP_ADDRESS>    tpvm1   <none>           <none>
traefik-7b487b687b-gsxlb   1/1     Running   2          8h      <IP_ADDRESS>    tpvm1   <none>           <none>

Nodes :
NAME    STATUS   ROLES    AGE    VERSION        INTERNAL-IP    EXTERNAL-IP   OS-IMAGE             KERNEL-VERSION     CONTAINER-RUNTIME         LABELS
tpvm2   Ready    master   2d4h   v1.18.6+k3s1   <IP_ADDRESS>   <none>        Ubuntu 18.04.4 LTS   5.3.0-40-generic   containerd://1.3.3-k3s2   beta.kubernetes.io/arch=amd64,beta.kubernetes.io/os=linux,keepalived=standby,kubernetes.io/arch=amd64,kubernetes.io/hostname=tpvm2,kubernetes.io/os=linux,node-role.kubernetes.io/master=true
tpvm1   Ready    master   2d4h   v1.18.6+k3s1   <IP_ADDRESS>   <none>        Ubuntu 18.04.4 LTS   5.3.0-40-generic   containerd://1.3.3-k3s2   beta.kubernetes.io/arch=amd64,beta.kubernetes.io/os=linux,keepalived=active,kubernetes.io/arch=amd64,kubernetes.io/hostname=tpvm1,kubernetes.io/os=linux,node-role.kubernetes.io/master=true

EFA Application status:
NAME                                   READY   STATUS    RESTARTS   AGE     IP             NODE    NOMINATED NODE   READINESS GATES
**pod/gosystem-service-df9698f84-2mr2z   1/1     Running   0          7m23s   <IP_ADDRESS>   tpvm2   <none>           <none>
pod/gosystem-service-df9698f84-6gkwx   1/1     Running   2          8h      <IP_ADDRESS>   tpvm1   <none>           <none>
pod/rabbitmq-1                         1/1     Running   0          6m48s   <IP_ADDRESS>    tpvm2   <none>           <none>
pod/rabbitmq-0                         1/1     Running   2          8h      <IP_ADDRESS>    tpvm1   <none>           <none>**

None of the pods shown in bold are displayed as running
NAME                             TYPE        CLUSTER-IP      EXTERNAL-IP   PORT(S)                          AGE    SELECTOR
service/rabbitmq                 NodePort    <IP_ADDRESS>    <none>        15672:31672/TCP,5672:30672/TCP   2d4h   app=rabbitmq
**service/gofabric-service         ClusterIP   <IP_ADDRESS>    <none>        8081/TCP                         2d4h   app=gofabric-service
service/goinventory-service      ClusterIP   <IP_ADDRESS>    <none>        8082/TCP                         2d4h   app=goinventory-service
service/gotenant-service         ClusterIP   <IP_ADDRESS>   <none>        8083/TCP                         2d4h   app=gotenant-service
service/efa-api-docs             ClusterIP   <IP_ADDRESS>     <none>        80/TCP                           2d4h   app=efa-api-docs**
**service/goraslog-service         ClusterIP   <IP_ADDRESS>    <none>        8091/TCP                         2d4h   app=goraslog-service
service/gonotification-service   ClusterIP   <IP_ADDRESS>   <none>        8088/TCP                         2d4h   app=gonotification-service
service/goauth-service           ClusterIP   <IP_ADDRESS>     <none>        8080/TCP                         2d4h   app=goauth-service
service/gorbac-service           ClusterIP   <IP_ADDRESS>     <none>        8089/TCP                         2d4h   app=gorbac-service
service/goopenstack-service      ClusterIP   <IP_ADDRESS>   <none>        8085/TCP                         2d4h   app=goopenstack-service
service/govcenter-service        ClusterIP   <IP_ADDRESS>    <none>        8086/TCP                         2d4h   app=govcenter-service
service/gohyperv-service         ClusterIP   <IP_ADDRESS>   <none>        8087/TCP                         2d4h   app=gohyperv-service**
service/gosystem-service         ClusterIP   <IP_ADDRESS>   <none>        8090/TCP                         2d4h   app=gosystem-service

NAME                               READY   UP-TO-DATE   AVAILABLE   AGE   CONTAINERS   IMAGES           SELECTOR
deployment.apps/gosystem-service   2/2     2            2           47h   gosystem     gosystem:2.3.0   app=gosystem-service

NAME                                         DESIRED   CURRENT   READY   AGE   CONTAINERS   IMAGES           SELECTOR
replicaset.apps/gosystem-service-df9698f84   2         2         2       47h   gosystem     gosystem:2.3.0   app=gosystem-service,pod-template-hash=df9698f84

NAME                        READY   AGE   CONTAINERS      IMAGES
statefulset.apps/rabbitmq   2/2     47h   rabbitmq-node   rabbitmq:2.3.0

Snippet from k3s log
UTC m=+84.188481318) (total time: 825.040748ms):
Sep 21 04:41:59 tpvm1 k3s[6898]: Trace[828730383]: [210.253647ms] [148.022431ms] Transaction committed
Sep 21 04:41:59 tpvm1 k3s[6898]: Trace[828730383]: [824.788648ms] [597.583792ms] Transaction committed
Sep 21 04:41:59 tpvm1 k3s[6898]: I0921 04:41:59.325841    6898 trace.go:116] Trace[1910865096]: "Patch" url:/api/v1/nodes/tpvm1/status,user-agent:k3s/v1.18.6+k3s1 (linux/amd64) kubernetes/6f56fa1,client:<IP_ADDRESS> (started: 2020-09-21 04:41:58.499442872 +0000 UTC m=+84.187910903) (total time: 826.345513ms):
Sep 21 04:41:59 tpvm1 k3s[6898]: Trace[1910865096]: [211.024937ms] [164.592602ms] About to apply patch
Sep 21 04:41:59 tpvm1 k3s[6898]: Trace[1910865096]: [825.74856ms] [602.701377ms] Object stored in database
Sep 21 04:41:59 tpvm1 k3s[6898]: I0921 04:41:59.337388    6898 flannel.go:78] Wrote subnet file to /run/flannel/subnet.env
Sep 21 04:41:59 tpvm1 k3s[6898]: I0921 04:41:59.337436    6898 flannel.go:82] Running backend.
Sep 21 04:41:59 tpvm1 k3s[6898]: I0921 04:41:59.337460    6898 vxlan_network.go:60] watching for new subnet leases
Sep 21 04:41:59 tpvm1 k3s[6898]: I0921 04:41:59.341740    6898 iptables.go:145] Some iptables rules are missing; deleting and recreating rules
Sep 21 04:41:59 tpvm1 k3s[6898]: I0921 04:41:59.341791    6898 iptables.go:167] Deleting iptables rule: -s <IP_ADDRESS>/16 -d <IP_ADDRESS>/16 -j RETURN
Sep 21 04:41:59 tpvm1 k3s[6898]: I0921 04:41:59.346613    6898 iptables.go:145] Some iptables rules are missing; deleting and recreating rules
Sep 21 04:41:59 tpvm1 k3s[6898]: I0921 04:41:59.346663    6898 iptables.go:167] Deleting iptables rule: -s <IP_ADDRESS>/16 -j ACCEPT
Sep 21 04:41:59 tpvm1 k3s[6898]: I0921 04:41:59.348736    6898 iptables.go:167] Deleting iptables rule: -s <IP_ADDRESS>/16 ! -d <IP_ADDRESS>/4 -j MASQUERADE --random-fully
Sep 21 04:41:59 tpvm1 k3s[6898]: I0921 04:41:59.351873    6898 iptables.go:167] Deleting iptables rule: -d <IP_ADDRESS>/16 -j ACCEPT
Sep 21 04:41:59 tpvm1 k3s[6898]: I0921 04:41:59.353126    6898 iptables.go:167] Deleting iptables rule: ! -s <IP_ADDRESS>/16 -d <IP_ADDRESS>/24 -j RETURN
Sep 21 04:41:59 tpvm1 k3s[6898]: I0921 04:41:59.357227    6898 iptables.go:155] Adding iptables rule: -s <IP_ADDRESS>/16 -j ACCEPT
Sep 21 04:41:59 tpvm1 k3s[6898]: I0921 04:41:59.357778    6898 iptables.go:167] Deleting iptables rule: ! -s <IP_ADDRESS>/16 -d <IP_ADDRESS>/16 -j MASQUERADE --random-fully
Sep 21 04:41:59 tpvm1 k3s[6898]: I0921 04:41:59.364990    6898 iptables.go:155] Adding iptables rule: -s <IP_ADDRESS>/16 -d <IP_ADDRESS>/16 -j RETURN
Sep 21 04:41:59 tpvm1 k3s[6898]: I0921 04:41:59.368728    6898 iptables.go:155] Adding iptables rule: -d <IP_ADDRESS>/16 -j ACCEPT
Sep 21 04:41:59 tpvm1 k3s[6898]: I0921 04:41:59.378027    6898 iptables.go:155] Adding iptables rule: -s <IP_ADDRESS>/16 ! -d <IP_ADDRESS>/4 -j MASQUERADE --random-fully
Sep 21 04:41:59 tpvm1 k3s[6898]: I0921 04:41:59.401472    6898 iptables.go:155] Adding iptables rule: ! -s <IP_ADDRESS>/16 -d <IP_ADDRESS>/24 -j RETURN
Sep 21 04:41:59 tpvm1 k3s[6898]: I0921 04:41:59.407979    6898 iptables.go:155] Adding iptables rule: ! -s <IP_ADDRESS>/16 -d <IP_ADDRESS>/16 -j MASQUERADE --random-fully
Sep 21 04:41:59 tpvm1 k3s[6898]: I0921 04:41:59.598824    6898 trace.go:116] Trace[461530964]: "GuaranteedUpdate etcd3" type:*core.Node (started: 2020-09-21 04:41:58.841194832 +0000 UTC m=+84.529662917) (total time: 757.577244ms):
Sep 21 04:41:59 tpvm1 k3s[6898]: Trace[461530964]: [298.637888ms] [295.065824ms] Transaction committed
Sep 21 04:41:59 tpvm1 k3s[6898]: Trace[461530964]: [613.0544ms] [284.380964ms] Transaction committed
Sep 21 04:41:59 tpvm1 k3s[6898]: Trace[461530964]: [757.362642ms] [140.77655ms] Transaction committed
Sep 21 04:41:59 tpvm1 k3s[6898]: I0921 04:41:59.599537    6898 trace.go:116] Trace[1890489218]: "Patch" url:/api/v1/nodes/tpvm1/status,user-agent:k3s/v1.18.6+k3s1 (linux/amd64) kubernetes/6f56fa1,client:<IP_ADDRESS> (started: 2020-09-21 04:41:58.840978204 +0000 UTC m=+84.529446224) (total time: 758.496695ms):
Sep 21 04:41:59 tpvm1 k3s[6898]: Trace[1890489218]: [299.019289ms] [295.887714ms] About to apply patch
Sep 21 04:41:59 tpvm1 k3s[6898]: Trace[1890489218]: [613.457856ms] [285.273143ms] About to apply patch
Sep 21 04:41:59 tpvm1 k3s[6898]: Trace[1890489218]: [757.928449ms] [141.813096ms] Object stored in database
Sep 21 04:42:00 tpvm1 k3s[6898]: I0921 04:42:00.215171    6898 reconciler.go:224] operationExecutor.VerifyControllerAttachedVolume started for volume "default-token-l7qm7" (UniqueName: "kubernetes.io/secret/b8b4eca1-6108-4638-8159-f6b6aa905042-default-token-l7qm7") pod "gosystem-service-df9698f84-6gkwx" (UID: "b8b4eca1-6108-4638-8159-f6b6aa905042")
Sep 21 04:42:00 tpvm1 k3s[6898]: I0921 04:42:00.215275    6898 reconciler.go:224] operationExecutor.VerifyControllerAttachedVolume started for volume "containerd-vol" (UniqueName: "kubernetes.io/host-path/b8b4eca1-6108-4638-8159-f6b6aa905042-containerd-vol") pod "gosystem-service-df9698f84-6gkwx" (UID: "b8b4eca1-6108-4638-8159-f6b6aa905042")
Sep 21 04:42:00 tpvm1 k3s[6898]: I0921 04:42:00.215558    6898 reconciler.go:224] operationExecutor.VerifyControllerAttachedVolume started for volume "gosystem-log-pv" (UniqueName: "kubernetes.io/host-path/b8b4eca1-6108-4638-8159-f6b6aa905042-gosystem-log-pv") pod "gosystem-service-df9698f84-6gkwx" (UID: "b8b4eca1-6108-4638-8159-f6b6aa905042")
Sep 21 04:42:00 tpvm1 k3s[6898]: I0921 04:42:00.215781    6898 reconciler.go:224] operationExecutor.VerifyControllerAttachedVolume started for volume "timezone" (UniqueName: "kubernetes.io/host-path/b8b4eca1-6108-4638-8159-f6b6aa905042-timezone") pod "gosystem-service-df9698f84-6gkwx" (UID: "b8b4eca1-6108-4638-8159-f6b6aa905042")
Sep 21 04:42:00 tpvm1 k3s[6898]: I0921 04:42:00.215938    6898 reconciler.go:224] operationExecutor.VerifyControllerAttachedVolume started for volume "master-node" (UniqueName: "kubernetes.io/configmap/b8b4eca1-6108-4638-8159-f6b6aa905042-master-node") pod "gosystem-service-df9698f84-6gkwx" (UID: "b8b4eca1-6108-4638-8159-f6b6aa905042")
Sep 21 04:42:00 tpvm1 k3s[6898]: I0921 04:42:00.316293    6898 reconciler.go:224] operationExecutor.VerifyControllerAttachedVolume started for volume "config-volume" (UniqueName: "kubernetes.io/configmap/9aa71317-c2b5-4d81-934e-86ce2205c4e0-config-volume") pod "rabbitmq-0" (UID: "9aa71317-c2b5-4d81-934e-86ce2205c4e0")
Sep 21 04:42:00 tpvm1 k3s[6898]: E0921 04:42:00.618946    6898 remote_runtime.go:128] StopPodSandbox "6b367d2095ec346ab27a5c9a52ea4f6c1e206e714dca79e82de1ba777bb961d9" from runtime service failed: rpc error: code = Unknown desc = an error occurred when try to find sandbox "6b367d2095ec346ab27a5c9a52ea4f6c1e206e714dca79e82de1ba777bb961d9": does not exist
Sep 21 04:42:00 tpvm1 k3s[6898]: E0921 04:42:00.619041    6898 kuberuntime_manager.go:895] Failed to stop sandbox {"containerd" "6b367d2095ec346ab27a5c9a52ea4f6c1e206e714dca79e82de1ba777bb961d9"}
Sep 21 04:42:00 tpvm1 k3s[6898]: E0921 04:42:00.619135    6898 kuberuntime_manager.go:674] killPodWithSyncResult failed: failed to "KillPodSandbox" for "b8b4eca1-6108-4638-8159-f6b6aa905042" with KillPodSandboxError: "rpc error: code = Unknown desc = an error occurred when try to find sandbox \"6b367d2095ec346ab27a5c9a52ea4f6c1e206e714dca79e82de1ba777bb961d9\": does not exist"
Sep 21 04:42:00 tpvm1 k3s[6898]: E0921 04:42:00.619195    6898 pod_workers.go:191] Error syncing pod b8b4eca1-6108-4638-8159-f6b6aa905042 ("gosystem-service-df9698f84-6gkwx_efa(b8b4eca1-6108-4638-8159-f6b6aa905042)"), skipping: failed to "KillPodSandbox" for "b8b4eca1-6108-4638-8159-f6b6aa905042" with KillPodSandboxError: "rpc error: code = Unknown desc = an error occurred when try to find sandbox \"6b367d2095ec346ab27a5c9a52ea4f6c1e206e714dca79e82de1ba777bb961d9\": does not exist"
Sep 21 04:42:00 tpvm1 k3s[6898]: I0921 04:42:00.877256    6898 topology_manager.go:219] [topologymanager] RemoveContainer - Container ID: f8421036708a5e1b6d973d44b3999735b9bcc64aa6dbfc3419635f256d7ab753
Sep 21 04:42:01 tpvm1 k3s[6898]: I0921 04:42:01.019400    6898 reconciler.go:224] operationExecutor.VerifyControllerAttachedVolume started for volume "config" (UniqueName: "kubernetes.io/configmap/67a440e7-b008-405d-894f-be23e54e16ad-config") pod "traefik-7b487b687b-gsxlb" (UID: "67a440e7-b008-405d-894f-be23e54e16ad")
Sep 21 04:42:01 tpvm1 k3s[6898]: I0921 04:42:01.019495    6898 reconciler.go:224] operationExecutor.VerifyControllerAttachedVolume started for volume "ssl" (UniqueName: "kubernetes.io/secret/67a440e7-b008-405d-894f-be23e54e16ad-ssl") pod "traefik-7b487b687b-gsxlb" (UID: "67a440e7-b008-405d-894f-be23e54e16ad")
Sep 21 04:42:01 tpvm1 k3s[6898]: I0921 04:42:01.019566    6898 reconciler.go:224] operationExecutor.VerifyControllerAttachedVolume started for volume "traefik-token-r46zr" (UniqueName: "kubernetes.io/secret/67a440e7-b008-405d-894f-be23e54e16ad-traefik-token-r46zr") pod "traefik-7b487b687b-gsxlb" (UID: "67a440e7-b008-405d-894f-be23e54e16ad")
Sep 21 04:42:01 tpvm1 k3s[6898]: I0921 04:42:01.019731    6898 reconciler.go:224] operationExecutor.VerifyControllerAttachedVolume started for volume "rabbitmq-log-pv" (UniqueName: "kubernetes.io/host-path/9aa71317-c2b5-4d81-934e-86ce2205c4e0-rabbitmq-log-pv") pod "rabbitmq-0" (UID: "9aa71317-c2b5-4d81-934e-86ce2205c4e0")
Sep 21 04:42:01 tpvm1 k3s[6898]: I0921 04:42:01.020021    6898 reconciler.go:224] operationExecutor.VerifyControllerAttachedVolume started for volume "rabbitmq-token-47gpx" (UniqueName: "kubernetes.io/secret/9aa71317-c2b5-4d81-934e-86ce2205c4e0-rabbitmq-token-47gpx") pod "rabbitmq-0" (UID: "9aa71317-c2b5-4d81-934e-86ce2205c4e0")
Sep 21 04:42:01 tpvm1 k3s[6898]: W0921 04:42:01.049304    6898 kuberuntime_container.go:758] No ref for container {"containerd" "f8421036708a5e1b6d973d44b3999735b9bcc64aa6dbfc3419635f256d7ab753"}
Sep 21 04:42:01 tpvm1 k3s[6898]: I0921 04:42:01.826736    6898 reconciler.go:224] operationExecutor.VerifyControllerAttachedVolume started for volume "coredns-token-gztjp" (UniqueName: "kubernetes.io/secret/a6931c84-6426-496c-9959-12e755897cd1-coredns-token-gztjp") pod "coredns-6dbbdcb79c-gg7jn" (UID: "a6931c84-6426-496c-9959-12e755897cd1")
Sep 21 04:42:01 tpvm1 k3s[6898]: I0921 04:42:01.826907    6898 reconciler.go:224] operationExecutor.VerifyControllerAttachedVolume started for volume "config-volume" (UniqueName: "kubernetes.io/configmap/a6931c84-6426-496c-9959-12e755897cd1-config-volume") pod "coredns-6dbbdcb79c-gg7jn" (UID: "a6931c84-6426-496c-9959-12e755897cd1")
Sep 21 04:42:01 tpvm1 k3s[6898]: I0921 04:42:01.826944    6898 reconciler.go:157] Reconciler: start to sync state
Sep 21 04:42:03 tpvm1 k3s[6898]: E0921 04:42:03.035028    6898 remote_runtime.go:128] StopPodSandbox "484b2c97584008d0dd73e2c0993acc4ef444800bb6b41b97baed245d06cfd8c2" from runtime service failed: rpc error: code = Unknown desc = an error occurred when try to find sandbox "484b2c97584008d0dd73e2c0993acc4ef444800bb6b41b97baed245d06cfd8c2": does not exist
Sep 21 04:42:03 tpvm1 k3s[6898]: E0921 04:42:03.035114    6898 kuberuntime_manager.go:895] Failed to stop sandbox {"containerd" "484b2c97584008d0dd73e2c0993acc4ef444800bb6b41b97baed245d06cfd8c2"}
Sep 21 04:42:03 tpvm1 k3s[6898]: E0921 04:42:03.035205    6898 kuberuntime_manager.go:674] killPodWithSyncResult failed: failed to "KillPodSandbox" for "9aa71317-c2b5-4d81-934e-86ce2205c4e0" with KillPodSandboxError: "rpc error: code = Unknown desc = an error occurred when try to find sandbox \"484b2c97584008d0dd73e2c0993acc4ef444800bb6b41b97baed245d06cfd8c2\": does not exist"
Sep 21 04:42:03 tpvm1 k3s[6898]: E0921 04:42:03.035274    6898 pod_workers.go:191] Error syncing pod 9aa71317-c2b5-4d81-934e-86ce2205c4e0 ("rabbitmq-0_efa(9aa71317-c2b5-4d81-934e-86ce2205c4e0)"), skipping: failed to "KillPodSandbox" for "9aa71317-c2b5-4d81-934e-86ce2205c4e0" with KillPodSandboxError: "rpc error: code = Unknown desc = an error occurred when try to find sandbox \"484b2c97584008d0dd73e2c0993acc4ef444800bb6b41b97baed245d06cfd8c2\": does not exist"
Sep 21 04:42:03 tpvm1 k3s[6898]: E0921 04:42:03.063837    6898 remote_runtime.go:128] StopPodSandbox "801ee008449e4e3235a97efe431f44603b89fc9fd6c7f0dd69b0b30b8779d484" from runtime service failed: rpc error: code = Unknown desc = an error occurred when try to find sandbox "801ee008449e4e3235a97efe431f44603b89fc9fd6c7f0dd69b0b30b8779d484": does not exist
Sep 21 04:42:03 tpvm1 k3s[6898]: E0921 04:42:03.063972    6898 kuberuntime_manager.go:895] Failed to stop sandbox {"containerd" "801ee008449e4e3235a97efe431f44603b89fc9fd6c7f0dd69b0b30b8779d484"}
Sep 21 04:42:03 tpvm1 k3s[6898]: E0921 04:42:03.064062    6898 kuberuntime_manager.go:674] killPodWithSyncResult failed: failed to "KillPodSandbox" for "67a440e7-b008-405d-894f-be23e54e16ad" with KillPodSandboxError: "rpc error: code = Unknown desc = an error occurred when try to find sandbox \"801ee008449e4e3235a97efe431f44603b89fc9fd6c7f0dd69b0b30b8779d484\": does not exist"
Sep 21 04:42:03 tpvm1 k3s[6898]: E0921 04:42:03.064121    6898 pod_workers.go:191] Error syncing pod 67a440e7-b008-405d-894f-be23e54e16ad ("traefik-7b487b687b-gsxlb_kube-system(67a440e7-b008-405d-894f-be23e54e16ad)"), skipping: failed to "KillPodSandbox" for "67a440e7-b008-405d-894f-be23e54e16ad" with KillPodSandboxError: "rpc error: code = Unknown desc = an error occurred when try to find sandbox \"801ee008449e4e3235a97efe431f44603b89fc9fd6c7f0dd69b0b30b8779d484\": does not exist"
Sep 21 04:42:03 tpvm1 k3s[6898]: E0921 04:42:03.326670    6898 remote_runtime.go:128] StopPodSandbox "b9fe6430019ea5b39f1c9309de7cd15b140f93de2a56127adf1177cdcb06c7d4" from runtime service failed: rpc error: code = Unknown desc = an error occurred when try to find sandbox "b9fe6430019ea5b39f1c9309de7cd15b140f93de2a56127adf1177cdcb06c7d4": does not exist
Sep 21 04:42:03 tpvm1 k3s[6898]: E0921 04:42:03.326753    6898 kuberuntime_manager.go:895] Failed to stop sandbox {"containerd" "b9fe6430019ea5b39f1c9309de7cd15b140f93de2a56127adf1177cdcb06c7d4"}
Sep 21 04:42:03 tpvm1 k3s[6898]: E0921 04:42:03.326845    6898 kuberuntime_manager.go:674] killPodWithSyncResult failed: failed to "KillPodSandbox" for "a6931c84-6426-496c-9959-12e755897cd1" with KillPodSandboxError: "rpc error: code = Unknown desc = an error occurred when try to find sandbox \"b9fe6430019ea5b39f1c9309de7cd15b140f93de2a56127adf1177cdcb06c7d4\": does not exist"
Sep 21 04:42:03 tpvm1 k3s[6898]: E0921 04:42:03.326897    6898 pod_workers.go:191] Error syncing pod a6931c84-6426-496c-9959-12e755897cd1 ("coredns-6dbbdcb79c-gg7jn_kube-system(a6931c84-6426-496c-9959-12e755897cd1)"), skipping: failed to "KillPodSandbox" for "a6931c84-6426-496c-9959-12e755897cd1" with KillPodSandboxError: "rpc error: code = Unknown desc = an error occurred when try to find sandbox \"b9fe6430019ea5b39f1c9309de7cd15b140f93de2a56127adf1177cdcb06c7d4\": does not exist"
Sep 21 04:42:04 tpvm1 k3s[6898]: I0921 04:42:04.948399    6898 topology_manager.go:219] [topologymanager] RemoveContainer - Container ID: 69c3df5bd22e77698bbac65c62f6593ddf5669748fa44f6f15dcc06f462ca440
Sep 21 04:47:27 tpvm1 k3s[6898]: I0921 04:47:27.577530    6898 log.go:172] http: TLS handshake error from <IP_ADDRESS>:40308: EOF
Sep 21 04:48:41 tpvm1 k3s[6898]: I0921 04:48:41.176989    6898 log.go:172] http: TLS handshake error from <IP_ADDRESS>:41090: EOF
Sep 21 04:48:41 tpvm1 k3s[6898]: I0921 04:48:41.177163    6898 log.go:172] http: TLS handshake error from <IP_ADDRESS>:41082: EOF
Sep 21 04:48:46 tpvm1 k3s[6898]: I0921 04:48:46.209068    6898 log.go:172] http: TLS handshake error from <IP_ADDRESS>:41564: EOF
Sep 21 04:48:46 tpvm1 k3s[6898]: I0921 04:48:46.214946    6898 log.go:172] http: TLS handshake error from <IP_ADDRESS>:41566: EOF
Sep 21 04:48:49 tpvm1 k3s[6898]: I0921 04:48:49.921872    6898 log.go:172] http: TLS handshake error from <IP_ADDRESS>:41828: EOF
Sep 21 04:48:51 tpvm1 k3s[6898]: I0921 04:48:51.886601    6898 log.go:172] http: TLS handshake error from <IP_ADDRESS>:41986: EOF
Sep 21 04:48:55 tpvm1 k3s[6898]: I0921 04:48:55.764969    6898 log.go:172] http: TLS handshake error from <IP_ADDRESS>:42276: EOF
Sep 21 04:48:55 tpvm1 k3s[6898]: I0921 04:48:55.769969    6898 log.go:172] http: TLS handshake error from <IP_ADDRESS>:42272: EOF
Sep 21 04:48:55 tpvm1 k3s[6898]: I0921 04:48:55.770240    6898 log.go:172] http: TLS handshake error from <IP_ADDRESS>:42270: EOF
Sep 21 04:48:55 tpvm1 k3s[6898]: I0921 04:48:55.770474    6898 log.go:172] http: TLS handshake error from <IP_ADDRESS>:42266: EOF

Bump on this one to get some 👀

Two nodes is fine for Kuberenetes. Can you reproduce this with a traditional mysql instance, or without keepalived? I don't have any sort of smoking gun for either, but those are both interesting departures from a stock configuration.
When you say the "pods are not running" - what exactly do you mean? Kubernetes clearly thinks they are. Do you have some output from crictl or docker (depending on your backend) showing the containers for those pods in some other state?

Thanks @brandond - i'll get the details when I reproduce the issues.
The pods dont show up as running when we run k3s kubectl -n <namespace> get pods, they seem to show up in the deployment. In most cases restarting k3s service seems to fix the issue, which to me implies that its not a Kubernetes issue, but a k3s issue causing it to not reconcile properly. The other pods are missing (not shown as Terminated/Init/Running or any other state)
Keepalived is just used to ensure Virtual IP fails over and the keepalived scripts help up cordon and uncordon a node and very importantly label the nodes. Its not directly playing a role in k3s function.
We cant use mysql - k3s uses the mariadb cluster as its backend as well.

The pods dont show up as running when we run k3s kubectl -n <namespace> get pods, they seem to show up in the deployment. In most cases restarting k3s service seems to fix the issue, which to me implies that its not a Kubernetes issue, but a k3s issue causing it to not reconcile properly. The other pods are missing (not shown as Terminated/Init/Running or any other state)

You're saying that the deployment's pod counts (ready/up-to-date/available) don't line up with the actual number of pods?

We cant use mysql - k3s uses the mariadb cluster as its backend as well.

Right, I don't necessarily mean mysql, mariadb is fine - I just mean do you get the same behavior from a non-clustered database?

You're saying that the deployment's pod counts (ready/up-to-date/available) don't line up with the actual number of pods?

Yes the pod counts dont line up with the actual number of pods. I am not sure if the Reconciliation.go isnt kicking in or something.

Right, I don't necessarily mean mysql, mariadb is fine - I just mean do you get the same behavior from a non-clustered database?

Yep its the same behavior with Clustered vs Non Clustered DB.

The above issue might be related to the bug in kine https://github.com/rancher/kine/issues/61 that was fixed recently and hence i'll check if the newer release of k3s fixes this issue as well

That bug was only present in a limited number of k3s releases so it's unlikely that it's the cause of what you were running into. I am curious if a newer release still shows this behavior though.


Add shell auto complete for kool command

Cobra provides some help for generating auto completion out-of-the-box, we should include that as an optional step on the installation script.
Docs:

https://github.com/spf13/cobra/blob/master/shell_completions.md
https://github.com/spf13/cobra/blob/master/bash_completions.md

#83 has accomplished this! We just need to add this to documentation now on Getting started.


Update sbt-scalafix, scalafix-core, ... to 0.9.29

Updates

ch.epfl.scala:sbt-scalafix
ch.epfl.scala:scalafix-core
ch.epfl.scala:scalafix-interfaces
ch.epfl.scala:scalafix-rules

from 0.9.27 to 0.9.29.
GitHub Release Notes - Version Diff
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

Files still referring to the old version number
The following files still refer to the old version number (0.9.27).
You might want to review and update them manually.
build.sbt

Ignore future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "ch.epfl.scala" } ]

labels: library-update, semver-patch, old-version-remains

Tests failing are probable a side effect of https://github.com/scalacenter/scalafix/pull/1376? I was blocked by this to try to migrate a 2.13.6 project - I ended up bumping the versions manually, but I assume it's blocking other people that do not know the internals.

it's weird since semanticdb is enabled and the files exist. So maybe scalafix doesn't take semanticdbTargetRoot ? I am investigating

The issue was as you said: scalafix-interfaces has been updated and I needed to update scala 2.13 version.


[5.1] Add empty comments to empty classes

As this already the case in \Illuminate\Contracts\Broadcasting\ShouldBroadcastNow and in stubs

:+1:


Adding Descriptive Comments or Reviews Directly Upon PR Creation

Description
We are using GitHub Actions to integrate with pr-agent. The current configuration is as follows:
on:
  pull_request:
  issue_comment:
jobs:
  pr_agent_job:
    runs-on: ubuntu-latest
    permissions:
      issues: write
      pull-requests: write
      contents: write
    name: Run pr agent on every pull request, respond to user comments
    steps:
      - name: PR Agent action step
        id: pragent
        uses: Codium-ai/pr-agent@main
        env:
          OPENAI_KEY: ${{ secrets.OPENAI_KEY }}
          GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}

The workflow is successfully triggered when a new pull request is created. However, we have two issues:

We want to automatically add descriptive comments or reviews to the PR right after it's created.
Adding "/review" or any other command in the PR comments does not seem to trigger anything.

Hi @hmedat
i just checked github-app on an example repo, and it works.
By default, 'review' is applied automatically to any new PR
Share a log message, it will probably reveal what went wrong.
Triple-check to ensure you defined the keys properly in your repo 'settings'.

@hmedat you have not responded. i am assuming the issue was solved. re-open it if its not


Anyway to check/listen if user paste data from clipboard?

For example lets say I have following mask:
BC - * * * * - * * *
When user paste clipboard text BC-12AF-FGH it skips last GH part and starts pasting from 3rd char and output becomes BC-BC12-AFF.
Is there any way to fix this?
I tried to use ng-paste and update ng-model value, but didn't work.

Just make sure to select all in the field before pasting values if you want to overwrite what is already in the field.

It worked, but any other way to work around without selecting all in the field?
thanks

Expected functionality for pasting content is for that content to begin where the cursor is in the field. I would guess then that moving the cursor to be before the already entered content would cause that content to be removed if your pasted value is >= the length of the mask.


preset: accepts a single value; would be great if it accepts an array too.

Example in the nodes:
Now:
   {
        "id": "thing1",
        "label": "thing 1",
        "preset": "generalThings",
        "fill": "green"
  }

Would be nice:
   {
        "id": "thing1",
        "label": "thing 1",
        "preset": ["generalThings", "coloredThings"]
  }

The expected behaviour would be:

load properties of "generalThings"
load properties of "coloredThings" (overrides properties with same name also present in "generalThings")
load local properties (overrides properties with same name in either preset

It will be slightly different.
A preset won't just blindly overwrite stuff. If a key is already present and you load in a preset that has that key as well, the original key-value (so NOT the one in the preset) is used.
So the order of 'parsing':

Load in local properties.
Load in presets: if a key is not present yet, copy the key-value from the preset into the individual node/edge.
Load general properties

So the priority: local > preset > global default
An example:
{
    "graph": {},
    "node": {
        "fill": "yellow",
        "shape": "circle",
        "topText": "star",
        "presets": {
            "preset1": {
                "fill": "blue",
                "shape": "8-star"
            },
            "preset2": {
                "strokeDasharray": "dashed",
                "fill": "green",
                "shape": "square"
            }
        }
    },
    "edge": {}
}

[
    {
        "preset": [
            "preset1",
            "preset2"
        ],
        "fill": "red"
    }
]

This config results in this:

Why is  fill red?
Local properties have highest priority, so fill is red.
Why is shape 8-star?
After the local properties, the presets are loaded. So first we load in preset1. We already have a fill, so this is ignored. We do not have a shape red. So the value of preset1 is used.

Bigger example (with edges):
{
    "graph": {},
    "node": {
        "fill": "yellow",
        "shape": "circle",
        "topText": "star",
        "presets": {
            "preset1": {
                "fill": "blue",
                "shape": "8-star"
            },
            "preset2": {
                "strokeDasharray": "dashed",
                "fill": "green",
                "shape": "square"
            }
        }
    },
    "edge": {
        "type": "smoothstep",
        "presets" : {
            "preset1": {
                "strokeDasharray": "dashed",
                "animation": "default"
            },
            "preset2" : {
                "strokeDasharray": "dotted",
                "label": "label"
            }
        }
    }
}

[
    {
        "id": "1",
        "preset": [
            "preset1",
            "preset2"
        ],
        "fill": "red",
        "position": {
            "x": 45,
            "y": -90
        }
    },
    {
        "id": "2",
        "position": {
            "x": -60,
            "y": 15
        }
    }
]

[
    {
        "type": "straight",
        "source": "1",
        "target": "2"
    }
]

Results in:

So shape is not square, because first preset wins; priority is: local > preset1 > preset2 > global.
I would have expected shape square, priority: local > preset2 > preset1 > global.
But if you document this clearly, I can live with your choice.

Worth to mention: the current solution only accepts arrays now (even vor single elements), so all earlier exports are invalid now. Couldn't the word "also" from my original request be interpreted, meaning this property can be a single string or an array of strings?

Worth to mention: the current solution only accepts arrays now (even vor single elements), so all earlier exports are invalid now. Couldn't the word "also" from my original request be interpreted, meaning this property can be a single string or an array of strings?

+1000
@TiboStr make sure you don't break existing configs without warning :)


fix(msgraph): user.select was not passed along everywhere

Signed-off-by: Johannes Grumboeck<EMAIL_ADDRESS>Hey, I just made a Pull Request!
This PR fixes #16637
I looked that userSelect is used wherever there's a fetch of user identities from Microsoft Graph.
I also "cleaned" up the order of the function arguments so that it always follows the order pattern expand, filter, search, select.
:heavy_check_mark: Checklist

[x] A changeset describing the change and affected packages. (more info)
[ ] Added or updated documentation
[ ] Tests for new functionality and regression tests for bug fixes
[ ] Screenshots attached (for UI changes)
[x] All your commits have a Signed-off-by line in the message. (more info)

@benjdlambert can you help merging this PR?

Alright!


indent example html properly

@dmitrig01
This file is basically a potato soup of tabs and spaces and bad indentations. we can't lint it because it's html file by nature.

ping @dmitrig01
FYI this is an NOP PR.

:+1:


SearchBar Styles inconsistency in Android and IOS

Environment
Provide version numbers for the following components (information can be retrieved by running tns info in your project folder or by inspecting the package.json of the project):

NativeScript-Angular: 4.2.0

Describe the bug
Trying to utilize NativeScript's SearchBar component to customize its styles. In this process I'm not finding a consistency with IOS and Android screens. Here I'm attaching the screenshots please verify.
Expected behavior
Android Styles to match with IOS styles. Both the screens should look same.
Additional context
IOS Screen:

Android Screen:

@M-kothakapu from one hand, both controls are having conceptual differences coming from the native APIs (iOS vs Android) so it is expected that the SearchBar will look differently on iOS vs Android. However, we have created a base abstraction that should allow you to change the background color, font color on both platforms.
Can you please clarify what UI are you expecting to see? The best approach would be to create a Playground with the styles you have applied.

@M-kothakapu from one hand, both controls are having conceptual differences coming from the native APIs (iOS vs Android) so it is expected that the SearchBar will look differently on iOS vs Android. However, we have created a base abstraction that should allow you to change the background color, font color on both platforms.
Can you please clarify what UI are you expecting to see? The best approach would be to create a Playground with the styles you have applied.

I agree with you. I got an alternative solution where I used a Text Field to customize the search bar to my required styles instead of utilizing the actual search bar of NS.

Fixed in an alternative solution.


faudio: 22.04 -> 22.08

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://repology.org/metapackage/faudio/versions.
meta.description for faudio is: "XAudio reimplementation focusing to develop a fully accurate DirectX audio library"
meta.homepage for faudio is: "https://github.com/FNA-XNA/FAudio"
meta.changelog for faudio is: ""
Updates performed

Version update

To inspect upstream changes

Release on GitHub

Compare changes on GitHub

Impact

Checks done (click to expand)

built on NixOS
The tests defined in passthru.tests, if any, passed
found 22.06 with grep in /nix/store/c19v0dqy8cxxqzkaxq5wdx8lgdwi7fl4-faudio-22.06
found 22.06 in filename of file in /nix/store/c19v0dqy8cxxqzkaxq5wdx8lgdwi7fl4-faudio-22.06

Rebuild report (if merged into master) (click to expand)

2 total rebuild path(s)

2 package rebuild(s)

2 x86_64-linux rebuild(s)
0 x86_64-darwin rebuild(s)

First fifty rebuilds by attrpath
faudio
rpcs3

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/c19v0dqy8cxxqzkaxq5wdx8lgdwi7fl4-faudio-22.06 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A faudio https://github.com/r-ryantm/nixpkgs/archive/53f200ed5d27f50c45c974ef2feb9f2731f044e0.tar.gz

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/c19v0dqy8cxxqzkaxq5wdx8lgdwi7fl4-faudio-22.06
ls -la /nix/store/c19v0dqy8cxxqzkaxq5wdx8lgdwi7fl4-faudio-22.06/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1

2 packages built:

faudio
rpcs3

Maintainer pings
cc @marius851000 for testing.

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://repology.org/metapackage/faudio/versions.
meta.description for faudio is: "XAudio reimplementation focusing to develop a fully accurate DirectX audio library"
meta.homepage for faudio is: "https://github.com/FNA-XNA/FAudio"
meta.changelog for faudio is: ""
Updates performed

Version update

To inspect upstream changes

Release on GitHub

Compare changes on GitHub

Impact

Checks done (click to expand)

built on NixOS
The tests defined in passthru.tests, if any, passed
found 22.08 with grep in /nix/store/dzwkpapag9p3dy43r5rd7qjcx0039i7i-faudio-22.08
found 22.08 in filename of file in /nix/store/dzwkpapag9p3dy43r5rd7qjcx0039i7i-faudio-22.08

Rebuild report (if merged into master) (click to expand)

2 total rebuild path(s)

2 package rebuild(s)

First fifty rebuilds by attrpath
faudio
rpcs3

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/dzwkpapag9p3dy43r5rd7qjcx0039i7i-faudio-22.08 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A faudio https://github.com/r-ryantm/nixpkgs/archive/39818451f4d491cf4693341d7c843e4ccd32ca77.tar.gz

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/dzwkpapag9p3dy43r5rd7qjcx0039i7i-faudio-22.08
ls -la /nix/store/dzwkpapag9p3dy43r5rd7qjcx0039i7i-faudio-22.08/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1

2 packages built:

faudio
rpcs3

Maintainer pings
cc @marius851000 for testing.

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

2 packages built:

faudio
rpcs3


Error in fine tuning the BERT for value grouping

Once the fine-tuning data generation is completed, the multi-task fine-tuning is raising the following error

How to resolve this issue?

Likely an issue with sentence-transformers version. What version are you using?


[rocksdb] update to v6.26.1

Update the RocksDB port to latest upstream release v6.26.1.

All features are tested successfully in the following triplet:

x86-windows
x64-windows
x64-windows-static

Thanks for the update!


On backup path update, the .git folder should be moved.

I'll take this. So a user wants to update their backup path and we move the .git folder to the new path? Do we want to keep their old paths .git configs?

Yep, we should preserve the .git config (and the way we're going to do that is by literally moving the .git/ directory.)

https://github.com/alichtman/shallow-backup/pull/99


[Request-For-External]  Codeunit 8 "AccSchedManagement"   ConflictAmountType

Can you please set the funktion ConflictAmountType from local to global?
procedure ConflictAmountType(AccSchedLine: Record "Acc. Schedule Line"; ColumnLayoutAmtType: Enum "Account Schedule Amount Type"; var AmountType: Enum "Account Schedule Amount Type"): Boolean
    begin

Thanks for reporting this. We agree, and we’ll publish a fix asap, either in an update for the current version or in the next major release. Please do not reply to this, as we do not monitor closed issues. If you have follow-up questions or requests, please create a new issue where you reference this one.


Add admin tokens to access tokens perms table

Description
Add admin tokens to the tokens permissions table to help surface more detail on the permissions available to these tokens.
Checklist:

[x] I have reviewed the style guide.

@djgrove did you see the note above? ☝


In and Out color is too light to see clearly

First, nice theme!
I think the In [] and Out [] color is too light, is it possiable to change the brightness?

Yes, I agree. I'm even more concerned about the color for comments in the cells, which is even harder to see since the background within the cell is lighter, and thus the comments are harder to discern. I won't have time to work on this right away, but I'll try to test a few different options. Thanks for bringing this up!

Version 0.3.6 fixes this as well as the color of the comments. Let me know if you have any feedback!

Thanks for your quickly fix.
I tried reinstalling the extension and the version is still 0.3.1. The output is the following:
> C:\Users\secsi\AppData\Local\Continuum\anaconda3\npm.CMD pack @oriolmirosa/jupyterlab_materialdarker
oriolmirosa-jupyterlab_materialdarker-0.3.6.tgz
> C:\Users\secsi\AppData\Local\Continuum\anaconda3\npm.CMD pack<EMAIL_ADDRESS>oriolmirosa-jupyterlab_materialdarker-0.3.1.tgz
Incompatible extension:

"<EMAIL_ADDRESS>is not compatible with the current JupyterLab
Conflicting Dependencies:
JupyterLab              Extension        Package
>=0.16.3 <0.17.0        >=0.18.2 <0.19.0 @jupyterlab/application
>=0.16.4 <0.17.0        >=0.18.2 <0.19.0 @jupyterlab/apputils

Found compatible version: 0.3.1
> C:\Users\secsi\AppData\Local\Continuum\anaconda3\npm.CMD pack<EMAIL_ADDRESS>oriolmirosa-jupyterlab_materialdarker-0.3.1.tgz
> node C:\Users\secsi\AppData\Local\Continuum\anaconda3\lib\site-packages\jupyterlab\staging\yarn.js install
yarn install v1.5.1
info No lockfile found.
[1/4] Resolving packages...
warning @oriolmirosa/jupyterlab_materialdarker > npm ><EMAIL_ADDRESS>This version mistakenly dropped node@4 compatibility in a semver-patch release. Please stay on 1.6.2 or update to 2 or latest
warning @oriolmirosa/jupyterlab_materialdarker > npm ><EMAIL_ADDRESS>this version has a breaking change. use 1.1.0 or upgrade to latest
warning @oriolmirosa/jupyterlab_materialdarker > npm > npm-registry-fetch > make-fetch-happen > socks-proxy-agent ><EMAIL_ADDRESS>If using 2.x branch, please upgrade to at least 2.1.6 to avoid a serious bug with socket data flow and an import issue introduced in 2.1.0
warning css-loader > cssnano > postcss-merge-rules ><EMAIL_ADDRESS>Browserslist 2 could fail on reading Browserslist >3.0 config used in other tools.
warning css-loader > cssnano > postcss-merge-rules > caniuse-api ><EMAIL_ADDRESS>Browserslist 2 could fail on reading Browserslist >3.0 config used in other tools.
warning css-loader > cssnano > autoprefixer ><EMAIL_ADDRESS>Browserslist 2 could fail on reading Browserslist >3.0 config used in other tools.
[2/4] Fetching packages...
info<EMAIL_ADDRESS>The platform "win32" is incompatible with this module.
info<EMAIL_ADDRESS>is an optional dependency and failed compatibility check. Excluding it from installation.
[3/4] Linking dependencies...
warning "@jupyterlab/json-extension ><EMAIL_ADDRESS>has incorrect peer dependency<EMAIL_ADDRESS>warning "@jupyterlab/json-extension ><EMAIL_ADDRESS>has incorrect peer dependency<EMAIL_ADDRESS>warning "@jupyterlab/vdom-extension ><EMAIL_ADDRESS>has incorrect peer dependency<EMAIL_ADDRESS>[4/4] Building fresh packages...
success Saved lockfile.
Done in 637.34s.
> node C:\Users\secsi\AppData\Local\Continuum\anaconda3\lib\site-packages\jupyterlab\staging\yarn.js run build:prod
yarn run v1.5.1
$ webpack --config webpack.prod.config.js
Hash:<PHONE_NUMBER>cdbd00aac2
Version: webpack 2.7.0
Time: 37167ms
                                 Asset     Size  Chunks                    Chunk Names
        vendor.6a86007c210613833369.js  1.57 MB       2  [emitted]  [big]  vendor
  912ec66d7572ff821749319396470bde.svg   444 kB          [emitted]  [big]
  674f50d287a8c48dc19ba404d20fe713.eot   166 kB          [emitted]
 fee66e712a8a08eef5805a46892932ad.woff    98 kB          [emitted]
af7ae505a9eed503f8b8e6982036873e.woff2  77.2 kB          [emitted]
             0.279ec850a9242db04c85.js   465 kB       0  [emitted]  [big]
          main.343a89ba2a406596a6ea.js  2.25 MB       1  [emitted]  [big]  main
  b06871f281fee6b241d60582ae9369b9.ttf   166 kB          [emitted]
      manifest.7512b7c82077057246ae.js  1.62 kB       3  [emitted]         manifest
         0.279ec850a9242db04c85.js.map  1.35 MB       0  [emitted]
      main.343a89ba2a406596a6ea.js.map  7.67 MB       1  [emitted]         main
    vendor.6a86007c210613833369.js.map  5.69 MB       2  [emitted]         vendor
  manifest.7512b7c82077057246ae.js.map  8.24 kB       3  [emitted]         manifest
                            index.html  1.53 kB          [emitted]
[/sZe]<EMAIL_ADDRESS>33.3 kB {2} [built]
[2Kj9]<EMAIL_ADDRESS>1.38 kB {2} [built]
[6nap] ./~/ajv/lib/ajv.js 15.2 kB {2} [built]
[cYMN]<EMAIL_ADDRESS>21 kB {2} [built]
[dyOy] ./~/url-parse/index.js 11.4 kB {2} [built]
[hKoQ] ./~/es6-promise/dist/es6-promise.js 28.6 kB {2} [built]
[kzCB] ./~/path-posix/index.js 6.94 kB {2} [built]
[l9te]<EMAIL_ADDRESS>18.1 kB {2} [built]
[lMhA]<EMAIL_ADDRESS>33.7 kB {2} [built]
[nh00]<EMAIL_ADDRESS>4.24 kB {2} [built]
[o73R] ./~/sanitize-html/index.js 11.2 kB {2} [built]
[qzHn]<EMAIL_ADDRESS>721 bytes {2} [built]
[rplX] ./~/whatwg-fetch/fetch.js 13 kB {1} [built]
   [8] multi @phosphor/algorithm @phosphor/application @phosphor/commands @phosphor/coreutils @phosphor/datagrid @phosphor/disposable @phosphor/domutils @phosphor/dragdrop @phosphor/messaging @phosphor/properties @phosphor/signaling @phosphor/virtualdom @phosphor/widgets ajv ansi_up codemirror comment-json es6-promise marked moment path-posix react react-dom sanitize-html url-parse xterm 328 bytes {2} [built]
   [9] multi whatwg-fetch ./build/index.out.js 40 bytes {1} [built]
    + 2215 hidden modules
Child html-webpack-plugin for "index.html":
    [3IRH] (webpack)/buildin/module.js 517 bytes {0} [built]
    [DuR2] (webpack)/buildin/global.js 509 bytes {0} [built]
    [GTAU] ./~/html-loader!./templates/partial.html 420 bytes {0} [built]
    [M4fF] ./~/lodash/lodash.js 540 kB {0} [built]
    [vxCX] ./~/html-webpack-plugin/lib/loader.js!./templates/template.html 1.41 kB {0} [built]
Done in 40.81s.

There seems to be a compatibility problem. My jupyterlab version is 0.32.1. How to solve this problem?

Yes, the extension has been updated to jupyterlab 0.34, so for it to work you should update to that version. Are you unable to do so?
Your other option is to use an earlier version of the materialdarker extension, but that won't have the fixes that include the new colors in 0.3.6. You can see the versions available in the 'versions' tab of this page:
https://www.npmjs.com/package/@oriolmirosa/jupyterlab_materialdarker
If you want to install 0.3.2, you would do this:
jupyter labextension install<EMAIL_ADDRESS>


Event Query Language (EQL) for Opensearch

Event Query Language (EQL) is a query language for event-based time series data, such as logs, metrics, and traces.
Is there any way , I can use EQL in opensearch for searching logs ?
Something like EQL search in ElasticSearch.
It is very useful for security analytics and Correlation rule.

Can someone from @opensearch-project/sql team add your comments?

[Triage - attendees 1 2 3 4]
@saeed-mcu Thanks for filing. We do not support Event Query Language today. However, have you looked at the features offered by the https://github.com/opensearch-project/security-analytics plugin? Also the https://github.com/opensearch-project/sql plugin offers additional query options that may be useful here as well.


[Feature] Deduplication

This PR adds support for enabling deduplication for realtime table, via a top level table config. At a high level, primaryKey (as defined in the table schema) hashes are stored into in-memory data structures, and each incoming row is validated against it. Duplicate rows are dropped. The expectation while using this feature,  is for the stream to be partitioned by the primary key, strictReplicaGroup routing to be enabled and the configured stream consumer type to be lowLevel. These requirements are therefore mandated via tableConfig API's input validations.
Design doc: https://docs.google.com/document/d/17sOSRQ1slff30z7jDc0ec5qKwv0xSfPkDjpMOY07POQ/edit?usp=sharing

Codecov Report

Merging #8708 (c722833) into master (d3c97d5) will decrease coverage by 1.74%.
The diff coverage is 53.91%.

@@             Coverage Diff              @@
##             master    #8708      +/-   ##
============================================
- Coverage     69.67%   67.92%   -1.75%
- Complexity     4571     4578       +7
============================================
  Files          1722     1727       +5
  Lines         89862    89932      +70
  Branches      13335    13347      +12
============================================
- Hits          62610    61089    -1521
- Misses        22920    24583    +1663
+ Partials       4332     4260      -72

Flag
Coverage Δ

integration1
?

integration2
25.42% <9.56%> (+0.22%)
:arrow_up:

unittests1
66.11% <49.56%> (-0.05%)
:arrow_down:

unittests2
14.32% <0.00%> (-0.01%)
:arrow_down:

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

Impacted Files
Coverage Δ

...ent/local/dedup/PartitionDedupMetadataManager.java
0.00% <0.00%> (ø)

...segment/local/dedup/TableDedupMetadataManager.java
0.00% <0.00%> (ø)

...org/apache/pinot/spi/config/table/DedupConfig.java
0.00% <0.00%> (ø)

...rg/apache/pinot/spi/config/table/UpsertConfig.java
85.71% <ø> (-1.25%)
:arrow_down:

...he/pinot/spi/utils/builder/TableConfigBuilder.java
81.37% <0.00%> (-1.14%)
:arrow_down:

...org/apache/pinot/spi/config/table/TableConfig.java
62.82% <40.00%> (-0.70%)
:arrow_down:

...he/pinot/common/utils/config/TableConfigUtils.java
81.81% <42.85%> (-2.01%)
:arrow_down:

...ata/manager/realtime/RealtimeTableDataManager.java
65.88% <50.00%> (-2.40%)
:arrow_down:

...local/indexsegment/mutable/MutableSegmentImpl.java
56.95% <50.00%> (-0.51%)
:arrow_down:

...rg/apache/pinot/segment/local/utils/HashUtils.java
71.42% <60.00%> (-28.58%)
:arrow_down:

... and 153 more

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 d3c97d5...c722833. Read the comment docs.

@saurabhd336 Please add documentation for this in Import Data section. You can create a new page titled Stream Ingestion with Dedup


Error occurred while proxying request localhost:3000/api/auth/login to http://localhost:5000/ [ECONNREFUSED] (https://nodejs.org/api/errors.html#errors_common_system_errors)

After following the installation steps, I tried to ran the project using the npm run dev command as given in the instruction. The landing page was successfully displayed but when I tried to signed in with the github it didnt forwarded me to the notes page instead a error was thrown
ERROR:
 <e> [webpack-dev-server] [HPM] Error occurred while proxying request localhost:3000/api/auth/login to http://localhost:5000/ [ECONNREFUSED] (https://nodejs.org/api/errors.html#errors_common_system_errors)

Can you please tell me where did I went wrong and what to do to solve the problem?
Node Version: v14.21.3
npm Version: 9.7.1
System Configuration
Host Name: RISHI-PC
OS Name: Microsoft Windows 11 Home Single Language
OS Version: 10.0.22621 N/A Build 22621
OS Manufacturer: Microsoft Corporation
OS Configuration: Standalone Workstation
OS Build Type: Multiprocessor Free
Registered Owner: Rishi
Registered Organization: N/A
Product ID: 00356-24514-74975-AAOEM
Original Install Date: 9/28/2022, 1:52:50 PM
System Boot Time: 7/30/2023, 12:28:46 PM
System Manufacturer: LENOVO
System Model: 82K2
System Type: x64-based PC
Processor(s): 1 Processor(s) Installed.
[01]: AMD64 Family 25 Model 80 Stepping 0 AuthenticAMD ~1908 Mhz
BIOS Version: LENOVO H3CN30WW(V2.00), 6/28/2021
Windows Directory: C:\WINDOWS
System Directory: C:\WINDOWS\system32
Boot Device: \Device\HarddiskVolume1
System Locale: en-us;English (United States)
Input Locale: 00004009
Time Zone: (UTC+05:30) Chennai, Kolkata, Mumbai, New Delhi
Total Physical Memory: 5,996 MB
Available Physical Memory: 281 MB
Virtual Memory: Max Size: 19,834 MB
Screenshots

I also couldn't set up the repo using the npm run dev. Try Docker. It works for me but changes your Authorization callback URL to port 5000 instead.

Faced same error
Create a .env file in the root of the project, and add the app's client ID and secret. Remove DEMO variable to enable GitHub integration.
CLIENT_ID=xxx
CLIENT_SECRET=xxxx
DEMO=true


Improve first-run experience

I cloned the repository (ok) and got it running via docker-compose up and navigating to localhost:5000.
I expected to see something useful, but got nothing; the homepage tells me to review my devices, but I go to Devices and am told that I have no devices and no way to add them. Now am hunting around in config/api/production.py, various defaults.py for something to turn on.
Reading further I think I need to add a PLUGINS = { } dictionary to instance/config.py? But I have no idea what a successful value looks like.
I'm running on a Mac and it looks like JAMF is a security setting I could use? but I'm confused about that because the configuration seems to involve a hostname, which implies signing up for some service and sending my data to it, which I don't really want to do.
It would be nice if it were easier to get started and add devices, or if there were configuration examples that you could easily copy/paste from, or an easier pointer to the place you need to configure everything.

Thanks for your interest in using Stethoscope!
Unfortunately, I think Stethoscope is solving a different problem than what you have in mind. Stethoscope is designed to be deployed by an organization with an existing database of device information, e.g., JAMF, LANDESK, Google's MDM, etc. Stethoscope's primary purpose is to take device data from these sources and provide security advice regarding the configuration of those devices. It does not collect the information directly from individual devices.

Thanks for the clarification @andrewmwhite.


V1.1.0

:warning: Please install the  to ensure uploads and comments are reliably processed by Codecov.
Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 77.95%. Comparing base (e7ecc96) to head (7ceb3a3).
Report is 1 commits behind head on main.

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
Additional details and impacted files
@@            Coverage Diff             @@
##             main      #22      +/-   ##
==========================================
- Coverage   78.63%   77.95%   -0.69%
==========================================
  Files           6        6
  Lines         323      322       -1
==========================================
- Hits          254      251       -3
- Misses         69       71       +2

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


Please remove the Debian folder from the repository

Hi,
I'm the package maintainer for python-rtslib-fb in Debian. I maintain my package using git.debian.org, where all of the packaging is stored. Unfortunately, upstream holding a debian folder is a very bad idea, as it prevents me from merging your latest tags (ie: it create merge conflicts in my Git when I do so).
Could you please remove the debian folder, or at least rename it to something like "debian-upstream", or alternatively, push it to a separate branch (which is perfect for using git-buildpackage, especially if you privde a debian/gbp.conf file)?
Also, I would very much enjoy having contribution within the OpenStack packaging team, to improve the package. The packaging improvements will go to both Debian and Ubuntu (as they sync the package from Debian).
Best would be if you could release a new tag without that debian folder asap, and then I'll be able to package and upload that to Debian Sid.
Thanks in advance.

Hi Thomas,
Thank you for packaging python-rtslib-fb in Debian.
I looked at the Debian package and noticed the following patch that changes the path to the configuration file:
Description: Fix path for the /etc/target/saveconfig.json
 The default path is /etc/target, which IMO is a way too generic. So I changed
 this to /etc/rtslib-fb-target/saveconfig.json
Author: Thomas Goirand<EMAIL_ADDRESS>Forwarded: no
Last-Update: 2014-01-25

I worry that when someone switches from installing rtslib-fb from sources to installing the Debian package, the target configuration will not be restored anymore. I would prefer to have the same configuration file in both cases. Maybe you are right and /etc/target/saveconfig.json is too generic. I can't think of a better name at the moment though.


Couple quick questions

As I get used to Pade coming from Spark, I noticed a couple things I've missed from Spark.
Get Users Attention:   Is this possible in Pade?  I'm guessing not since it is browser oriented but it was nice to be able to shake the window when you knew the other user was involved in something else on the PC.
Contact list on the side.  This is a bigger deal to me.  We have lots of contact in our list and I've noticed that you can't scroll down the list to view the contacts but have to filter for them (unless I'm missing something).   Is there a way to scroll down in the list?

Get Users Attention: Is this possible in Pade?

I use desktop notifications to get attention. In groupchat, I use mentions (@nickname) in a message. In normal chat, I just type any message.
If Pade window is minimized or not in focus, the user gets a desktop notification like this

Also the pade icon on the windows toolbar flashes like this

I've noticed that you can't scroll down the list to view the contacts

You can, you use the scroll wheel of the mouse. The scroll bar is missing because of space.

Most of the time, I am only interested in my active conversations. I switch view to the active conversations list

There is also a directory search tool using the two people icon on the toolbar to search for contacts and use to open a chat or invite them to the opened/active groupchat


AttributeError: coref_clusters

Win 10
spacy==2.0.8
neuralcoref==3.0
en-coref-lg==3.0.0
I get the following error when I run the demo code.

doc = nlp(u'My sister has a dog. She loves him.')
Traceback (most recent call last):
File "", line 1, in
doc = nlp(u'My sister has a dog. She loves him.')
File "D:\anaconda3\lib\site-packages\spacy\language.py", line 341, in call
doc = proc(doc)
File "neuralcoref.pyx", line 566, in en_coref_lg.neuralcoref.neuralcoref.NeuralCoref.call
File "neuralcoref.pyx", line 785, in en_coref_lg.neuralcoref.neuralcoref.NeuralCoref.set_annotations
File "D:\anaconda3\lib\site-packages\spacy\tokens\underscore.py", line 45, in set
return self.setattr(name, value)
File "D:\anaconda3\lib\site-packages\spacy\tokens\underscore.py", line 37, in setattr
raise AttributeError(name)
AttributeError: coref_clusters

Hi @linkwithkk,
Can you try updating to the latest version of spacy (I recommend doing that in a conda environment)?
You can do that, for example, by installing NeuralCoref in a clean environment with:
pip install --upgrade --force-reinstall --no-cache-dir MODEL_URL

Received the same error in macos, any solution @thomwolf ?
Tried :  pip install --upgrade --force-reinstall --no-cache-dir MODEL_URL
but did not work

@thomwolf Thanks, upgrading to Spacy2.0.11 works on Windows 10

@thomwolf Thanks, upgrading to spacy-2.0.12 worked form me as well on Linux

@linkwithkk does this work for you?

Hi guys. I ended up taking a different approach for my problem.
However i tried it now with 2.0.11 and it works.

This is fixed now.


fix: test coverage when using jest projects

Codecov Report

Merging #25 (12d21ac) into master (55e1d1a) will decrease coverage by 66.62%.
The diff coverage is n/a.

:exclamation: Current head 12d21ac differs from pull request most recent head 4a8ee2e. Consider uploading reports for the commit 4a8ee2e to get more accurate results

@@             Coverage Diff             @@
##           master      #25       +/-   ##
===========================================
- Coverage   96.25%   29.62%   -66.63%
===========================================
  Files           5       14        +9
  Lines          80      270      +190
  Branches       12       38       +26
===========================================
+ Hits           77       80        +3
- Misses          3      190      +187

Flag
Coverage Δ

unittests
29.62% <ø> (-66.63%)
:arrow_down:

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

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


[3.x] [HTML5] Debug HTTP server refactor with SSL support, PWA export.

3.x version of:
#47386
#47974
#48159

Thanks!


Helm command that sets release status

Hi helm maintainers!
I would like to propose a helm subcommand that can be used to update the status of the latest revision of a release.
Such a command is useful when a helm release is stuck in pending-upgrade (or any other) status. The most common cause is that the helm process was killed in the middle of an operation. Attempting helm upgrade in this state results in the following error:
Error: UPGRADE FAILED: another operation (install/upgrade/rollback) is in progress

Setting the release status to deployed allows running helm upgrade again. I have a script that does exactly this, but it would be convenient to be able to do it with helm cli. Furthermore, this exact situation generates regular support requests that could be resolved with this command in the future. Some users even resort to reinstalling the helm release, accepting downtime in the process (e.g. https://github.com/helm/helm/issues/11565).
It could be implemented as a "ignore status" flag on upgrade / rollback commands as well, but I imagine that would tempt users to set the flag by default in CI environments which is dangerous.
I would be happy to implement the proposed functionality if the helm project is inclined to accept such a contribution!

I just came across the helm plugin https://github.com/k3s-io/helm-set-status which claims to do exactly what I am proposing to implement in helm cli itself.

@Nick-Triller I think that you can try to use https://github.com/k3s-io/helm-set-status. but please notice that This plugin alters the internal state of helm releases. Use with care!.

Glad to see you found a solution. Closing this issue then.

Hi @joejulian,
We already had a solution when I created the issue (our own script that works like helm-set-status plugin). My intention was to propose implementing a command such as helm-set-status in helm cli itself because so many helm users run into this problem at some point.


joda-time-api

Repository URL
https://github.com/jonesbusy/joda-time-api-plugin
New Repository Name
joda-time-api-plugin
Description
See https://github.com/jenkinsci/bom/pull/2723 for context
GitHub users to have commit permission
@jonesbusy
Jenkins project users to have release permission
jonesbusy
Issue tracker
GitHub issues

Security audit, information and commands
The security team is auditing all the hosting requests, to ensure a better security by default.
This message informs you that a Jenkins Security Scan was triggered on your repository.
It takes ~10 minutes to complete.
Commands
The bot will parse all comments, and it will check if any line start with a command.
Security team only:

/audit-ok => the audit is complete, the hosting can continue :tada:.
/audit-skip => the audit is not necessary, the hosting can continue :tada:.
/audit-findings => the audit reveals some issues that require corrections :pencil2:.

Anyone:

/request-security-scan => the findings from the Jenkins Security Scan were corrected, this command will re-scan your repository :mag:.
/audit-review => the findings from the audit were corrected, this command will ping the security team to review the findings :eyes:.
	It's only applicable when the previous audit required changes.

Only one command can be requested per comment.

(automatically generated message, version: 1.26.21)

/hosting host


CVE-2014-3155 and CVE-2013-6657

Please make sure the travis tests pass or the PR can't be merged.


Issue when trying to generate new view themes

Hi
I have an issue when installing the theme on rails 6
for example rails g kaminari:views github

raceback (most recent call last):
17: from bin/rails:4:in <main>'         16: from bin/rails:4:in require'
15: from C:/Ruby/Ruby26-x64/lib/ruby/gems/2.6.0/gems/railties-6.0.0/lib/rails/commands.rb:18:in <top (required)>'         14: from C:/Ruby/Ruby26-x64/lib/ruby/gems/2.6.0/gems/railties-6.0.0/lib/rails/command.rb:46:in invoke'
13: from C:/Ruby/Ruby26-x64/lib/ruby/gems/2.6.0/gems/railties-6.0.0/lib/rails/command/base.rb:65:in perform'         12: from C:/Ruby/Ruby26-x64/lib/ruby/gems/2.6.0/gems/thor-0.20.3/lib/thor.rb:387:in dispatch'
11: from C:/Ruby/Ruby26-x64/lib/ruby/gems/2.6.0/gems/thor-0.20.3/lib/thor/invocation.rb:126:in invoke_command'         10: from C:/Ruby/Ruby26-x64/lib/ruby/gems/2.6.0/gems/thor-0.20.3/lib/thor/command.rb:27:in run'
9: from C:/Ruby/Ruby26-x64/lib/ruby/gems/2.6.0/gems/railties-6.0.0/lib/rails/commands/generate/generate_command.rb:26:in perform'          8: from C:/Ruby/Ruby26-x64/lib/ruby/gems/2.6.0/gems/railties-6.0.0/lib/rails/generators.rb:276:in invoke'
7: from C:/Ruby/Ruby26-x64/lib/ruby/gems/2.6.0/gems/thor-0.20.3/lib/thor/base.rb:466:in start'          6: from C:/Ruby/Ruby26-x64/lib/ruby/gems/2.6.0/gems/thor-0.20.3/lib/thor/group.rb:219:in dispatch'
5: from C:/Ruby/Ruby26-x64/lib/ruby/gems/2.6.0/gems/thor-0.20.3/lib/thor/group.rb:31:in help'          4: from C:/Ruby/Ruby26-x64/lib/ruby/gems/2.6.0/gems/kaminari-0.16.3/lib/generators/kaminari/views_generator.rb:19:in banner'
3: from C:/Ruby/Ruby26-x64/lib/ruby/gems/2.6.0/gems/kaminari-0.16.3/lib/generators/kaminari/views_generator.rb:39:in themes'          2: from C:/Ruby/Ruby26-x64/lib/ruby/gems/2.6.0/gems/kaminari-0.16.3/lib/generators/kaminari/views_generator.rb:99:in get_files_in_master'
1: from C:/Ruby/Ruby26-x64/lib/ruby/gems/2.6.0/gems/kaminari-0.16.3/lib/generators/kaminari/views_generator.rb:99:in open' C:/Ruby/Ruby26-x64/lib/ruby/gems/2.6.0/gems/kaminari-0.16.3/lib/generators/kaminari/views_generator.rb:99:in initialize': Invalid argument @ rb_sysopen - https://api.github.com/repos/amatsuda/kaminari_themes/git/refs/heads/master (Errno::EINVAL)

I encountered this issue as well. Kaminari repo says it's fixed so it's probably a matter of versions we're running. I just copied the files from this repo.
ref: https://github.com/kaminari/kaminari/issues/1047


Customizable Map.forEachFeatureAtPixel

Map.forEachFeatureAtPixel should have additional prototype with FeatureAtPixelOptions for customizations.
Will provide a patch soon.
Unrelated to this issue, I would like to ask @TDesjardins if this workflow "file an issue" -> "provide a patch" is valid? I looks like there are considerable amount of missing features in gwt-ol3 (which is completely understandable) so I'll have to spam this project a bit. I could pack several improvements in one pull request, but then I risk that because of one misimplemented feature whole pull request gets rejected. Note that I don't mind filing an issue for each feature implemented, I'm just asking if that is OK with maintainer.

@gkresic Please provide pull requests by feature! If you pack several improvements in one pull request the review is not possible. It's not neccessary to open an issue, but this maybe saves you from wasting your time (e.g double implementation or an existing feature). It isn't spam it's communication ;-)


Feat/type of force tags

Includes an initial training dataset with labels, accompanied with exploration notebook
Trello Card:
https://trello.com/c/iOSrB5Oj/31-extracting-type-of-violence-from-data

The technique here is really awesome. You did this really quickly and learned all this incredibly well. Thanks for your hard work on this.

Awesome work implementing Snorkel. This is a big step towards hitting MVP this week


Remove unused messages object in SessionInfo schema

What type of PR is this?

correction

What this PR does / why we need it:

Remove unused messages object in the SessionInfo schema

Which issue(s) this PR fixes:
Fixes #309
Special notes for reviewers:
As discussed in today's call
Changelog input
Removed unused `messages` object in the `SessionInfo` schema

LGTM

@hdamker I guess we can merge. I do not expect now any turn-around.


Use experimental CF CRs to drive workload runtime

Background
We want to get a better understanding of what building a CF v3 API that is backed by custom resources actually looks like.
Assume you already have a "staged" app/runnable app image. Consider making an app we can use to demo and experiment with. Other teams have found spring-pet-clinic to be a good candidate since it is Java (what most CF devs use) and relies on a MySQL database.
Using the CRDs (probably App, Process, Droplet) we created in #1, let's see how useful they are in driving the underlying workload runtime (e.g. Knative, Eirini LRP, Kubernetes Deployments, etc.). We should build some experimental controllers to reconcile these CRs and create the necessary workload resources.
The goal of this spike is to answer the following questions:

Are these the right CRDs? Are they missing anything? Can anything be simplified?

Are these definitions hard to work with? Is there enough info to make a runnable application?

Think about environment variables, secrets, etc. Maybe we need AppEnvironmentVariables CR?
What would a common "workload runtime" abstraction CR look like? We envision these CRs as being a pluggable extension point for us and others in the OSS community to build off of.

Scenario: Applying pre-made CRs makes a running workload
Given a set of example custom resources and controllers installed on the cluster,
When Ikubectl apply <app/process/droplet>,
Then I see that my application is running (and can curl it/access it, etc)
(Note: Out of band, this requires an LB service to access the application).
Deliverable

A set of experimental controllers with instructions to install them
Example custom resources to deploy the sample app
Keep a journal of what was difficult, what was easy, etc.

Dev Notes

Refer to the bottom part of this Miro board frame for inspiration.
This could possibly be one controller that watches the CRDs (App, Process, Droplet) and makes an Eirini LRP
The Droplet should already be pointing at an image (do not include build staging)
We are only concerned with Creation, not delete or update in the controllers

Dev Provided Acceptance Steps:
Fill me in

Work is currently on the rebased-workloads-from-crds-spike-tme-155 branch.

How to update the Status subresource for Droplets

kubectl proxy &

NAMESPACE=default
DROPLET_NAME=kpack-droplet-guid

curl -k -s -X PATCH -H "Accept: application/json, */*" \
-H "Content-Type: application/merge-patch+json" \
<IP_ADDRESS>:8001/apis/apps.cloudfoundry.org/v1alpha1/namespaces/$NAMESPACE/droplets/$DROPLET_NAME/status \
--data '{"status":{"image": {"reference": "cloudfoundry/httpbin", "pullSecretName": ""}, "conditions": []}}'

Tim and I did another spike exploration on this branch where the App Controller reads the Processes and references the Droplet to create the LRPs for each process.

One thing @heycait and I are thinking through is how can we get changes to either an App, Process, or Droplet to trigger updating the Eirini LRP.
A couple thoughts we want to explore are:

What does an App Controller that watches Apps and all Process/Droplets that it owns look like (which we're exploring on the spike-app-controller branch linked in the comment above)
What does propagating state from the App and Droplet to the Processes look like (which loosely is what main is doing). In this case individual App and Droplet reconcilers would react to their corresponding changes and update the relevant Processes which then triggers the Process controller to update the LRP
???

Still thinking all this through and exploring... just noting down what we're thinking about

Tim found some guidance one how to design controllers. See this doc.

Example: If you need to update all Services in response to a Node being added - Reconciler Services but Watch Nodes (transformed to Service object name / Namespaces) instead of Reconciling Nodes and updating Services

We should have the Process watch for changes to the Application and Droplet instead. We are therefore going back to the original spike with all the things happening within the Process Controller.
The next step is to determine how we can get the controller to watch for changes to these other objects and trigger Reconciles on them. As the code stands now, the Process Controller only Reconciles on changes to the Process itself. However, this presents a problem of ordering. If the Process is applied first, followed by the App and Droplet, the Process would never creating a running LRP and would need to be deleted and applied again.

I know this spike is assuming that an app/process/droplet CR already exists, but I'm curious to know if we've thought about the order in which each of these gets created? Right now, it seems like they are referring to each other mainly through fields in the spec, but I'm wondering how much we can rely on knowing what to fill in for those fields ahead of time. Is the shim setting all the spec fields?

@angelachin ideally the order in which they're created doesn't actually matter and the controller will just no-op if an app isn't runnable yet (e.g. a staged Droplet isn't assigned / doesn't exist yet) and it will re-reconcile once the resources it is watching change. I am imagining the shim / controllers does set the spec fields on the users behalf in response to imperative actions taken via the CF APIs. For example, a user might make the following request to set the current Droplet on an App:
curl "https://api.example.org/v3/apps/[guid]/relationships/current_droplet" \
  -X PATCH \
  -H "Authorization: bearer [token]" \
  -H "Content-type: application/json" \
  -d '{ "data": { "guid": "[droplet_guid]" } }'

The shim in this case would update the Spec.CurrentDropletRef field on the corresponding App. The user could also do this themselves by directly updating the App CR.
For many of the V3 CF APIs, relationships are represented this way and set by API users:
https://v3-apidocs.cloudfoundry.org/version/3.101.0/index.html#relationships
I realize that while this is most convenient for representing the existing CF APIs it is perhaps not the most "Kubernetes native" way to model this, though.
It may be a bit trickier to reason about, but alternatively we could use the selector.matchLabels pattern and have parent object claim children that match the selectors. An App would adopt Droplets, Processes, Builds, etc. like how a ReplicaSet adopts Pods.
I think there are some unanswered questions here about what happens if multiple Apps try to adopt the same resources and it may make validations around uniqueness/ownership more difficult (I'm picturing orphaned resources be a problem).

Cool. I think the struggle with relationship mapping could be helped a lot by having a "AppManifest"-like CRD that is the entry point for both our shim and a user directly editing with kubectl. That way that resource could own all of these child resources and show the relationship between them.
If the shim is setting the spec fields, that makes sense to me. The main thing we want to avoid is having a controller editing a spec field-- I believe that general k8s controller development assumes controllers should only ever be creating new resources or updating the status fields.

The main thing we want to avoid is having a controller editing a spec field-- I believe that general k8s controller development assumes controllers should only ever be creating new resources or updating the status fields.

I'm not sure I 100% agree with this.
From the K8s api-conventions doc:

The specification is a complete description of the desired state, including configuration settings provided by the user, default values expanded by the system, and properties initialized or otherwise changed after creation by other ecosystem components (e.g., schedulers, auto-scalers), and is persisted in stable storage with the API object.

IMO the Spec/Status distinction just becomes a Desired State vs Actual State question and if controllers have input into what the desired state should be then it should be valid for them to modify an object's Spec. I think we'll have instances of this where we need to be able to set reasonable defaults for things like memory/disk limits, health checks, etc. that the user can also set but are free to omit.
There's examples of this in the default types like how users can set clusterIP on a Service Spec, but if they omit it the controller will populate it or how when creating a Job the Pod selector is both user specifiable / controller defaultable.

I think we'll have instances of this where we need to be able to set reasonable defaults for things like memory/disk limits, health checks, etc. that the user can also set but are free to omit.
Yeah I agree. I think my initial wording/position isn't entirely correct. I think what I want to call out is to think critically about a controller updating the spec field so that we don't clobber something that a user has provided. I agree that I think it gets back to Desired vs Actual state, and for the most part since controllers are reconciling resources, I'd expect them to be updating the actual state and thus the status fields.

Yep, makes sense @angelachin!

As an aside, I've added a couple of diagrams to our Miro board to help folks visualize what the controller is doing and what data ends up on the Eirini LRP.
For posterity, copies are attached below, but any updates will be made on the Miro.

Looks like all of this work in on the main branch, so closing this issue out.


SignalR stops working when deploying the working app to Azure

Hey folks,
I wrote a simple SignalR demo app, which works fine in my dev box. But when published to Azure app, I get the following error. Any guidance to fix it ?

signalr-client-1.0.0-alpha1-final.js:662 WebSocket connection to 'wss://testdecompression.azurewebsites.net/gameHub?id=1e90719e-8749-4805-b100-28a943ee6724' failed: Error during WebSocket handshake: Unexpected response code: 503
Promise @ signalr-client-1.0.0-alpha1-final.js:662

Did you enable webSockets in you Azure app service? As far as I remember webSockets are disabled by default.

@moozzyk 👍 That was indeed what I had missed. Thanks for the help. This issue was a false alarm, hence marking it as closed.

Took me a while to find this! That was indeed my problem. The client was getting 503. This fixed the issue.

I have the same issue. Works locally, but not on Azure. 503.
I have enabled web sockets, as well as ARR and Always On.
Using 1.0.0-preview2-final for both server and angular client.


TAJO-1940: Implement HBaseTablespace::getTableVolume() method.

This patch depends on TAJO-1990, TAJO-1991 and TAJO-2007. It is almost done. It only needs some more unit tests.

rebased.

Thanks @hyunsik. This patch looks good to me overall. I have one suggestion.
It looks that getTableVolume() works well, but we need to verify its behaviour. How about adding any test?

Added unit tests and rebased the patch.

Yes, that's why I placed the test in TestHbaseTable. As you know, Hbase cluster requires lots of additional memory, and we are suffering from memory problem of unit tests.

Rebased and reflected a comment.

I've tested the latest patch manually.
Before you commit, please add some comments about the difference between the original RegionSizeCalculator and the copied one on https://github.com/apache/tajo/pull/910#discussion-diff-50492684.
Here is my +1.

Thank you. I've added some note for that.


Problem with string parameters

Hi,
I am experimenting with using Hera and came across an issue. I have 2 tasks. The first task dumps out the parameters with which the second task can fan out. When I try to do this with only 1 parameter, it works fine. Even with 2 parameters it works fine, if both parameters used are int. Below is a working example.
def generate():
    chunk_number_list = list(range(0, 10))
    json.dump([{"chunk_number": chunk_number, "chunk": chunk_number} for chunk_number in chunk_number_list], sys.stdout)

def consume(chunk_number, chunk):
    print(chunk_number, chunk)

consume_task = Task(
    "consume",
    consume,
    input_from=InputFrom(name="generate", parameters=["chunk_number", "chunk"]),)

But when I change the generate to output a string, I get an error.
def generate():
    chunk_number_list = list(range(0, 10))
    json.dump([{"chunk_number": chunk_number, "chunk": "s"} for chunk_number in chunk_number_list], sys.stdout)

The error is
json.decoder.JSONDecodeError: Expecting value: line 1 column 1 (char 0)

Any pointers on what the issue may be? Thanks for the help.

Hello @vikramsg! Thank you for submitting the issue 🙂  We've identified this issue internally at @dynotx as we also pass string parameters between jobs. The main reason is the the string needs to be JSON encoded in order for decoding to work. I have a fix for this that does not require users to perform any sort of string encoding themselves. I will mark this issue as a bug report and will deploy the fix in 3.3, which has a PR open. I will tag you in the PR that provides the fix and will try your specific example as a test.


Update list editor with tabs and improved UI

Reviewer:
@sammacbeth
CC:
@GuiltyDolphin
Description:
The current list editor is functional, but to make it easier to use should have a better UI.
This PR uses the existing extension styles (in base.css) and replaces the list chooser dropdown with tabs, to save clicks.
See internal task: https://app.asana.com/0/0/1206280121954707/f
Steps to test this PR:

Once built, open list-editor.html
Check that the tabs change the textarea content.
Check that the buttons still work, e.g. remote file is loaded.

Automated tests:

[ ] Unit tests
[ ] Integration tests

Reviewer Checklist:

[ ] Ensure the PR solves the problem
[ ] Review every line of code
[ ] Ensure the PR does no harm by testing the changes thoroughly
[ ] Get help if you're uncomfortable with any of the above!
[ ] Determine if there are any quick wins that improve the implementation

PR Author Checklist:

[ ] Get advice or leverage existing code
[ ] Agree on technical approach with reviewer (if the changes are nuanced)
[ ] Ensure that there is a testing strategy (and documented non-automated tests)
[ ] Ensure there is a documented monitoring strategy (if necessary)
[ ] Consider systems implications

@sammacbeth Great, thank you for both of these reviews/merges.


It would be useful if * it was explained directly in the window

I would use this text "* Marks currently selected JDK (in JAVA_HOME)" somewhere in window (or You have better idea?).
I think it would be useful.

I was thinking about that too...was just not sure where to put it...maybe add a tooltip that appears on mouse over...have to think about it...

With version 17.0.5 the tooltip on the entry with the '*' will start with '(Currently in use)'.


Multiprocessing start_method does not work after import

Minimal, reproducible code sample, a copy-pastable example if possible
Hi, not sure if this is a numcodecs bug or not, but whenever I set multiprocessing start_method, there seems to be an error when I use libraries with numcodecs:
import numcodecs
import multiprocessing as mp
mp.set_start_method("spawn")
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
  File "/usr/lib/python3.10/multiprocessing/context.py", line 247, in set_start_method
    raise RuntimeError('context has already been set')
RuntimeError: context has already been set

Doing it the other way around seems to work:
import multiprocessing as mp
mp.set_start_method("spawn")
from numcodecs.abc import Codec

Full example with minimal reproduction:
$ python3 -m venv venv
$ . venv/bin/activate
$ pip install numcodecs
Collecting numcodecs
  Using cached numcodecs-0.13.0-cp310-cp310-manylinux_2_17_x86_64.manylinux2014_x86_64.whl (8.6 MB)
Collecting numpy>=1.7
  Using cached numpy-2.0.1-cp310-cp310-manylinux_2_17_x86_64.manylinux2014_x86_64.whl (19.5 MB)
Installing collected packages: numpy, numcodecs
Successfully installed numcodecs-0.13.0 numpy-2.0.1
$ python
Python 3.10.12 (main, Jul 29 2024, 16:56:48) [GCC 11.4.0] on linux
Type "help", "copyright", "credits" or "license" for more information.
>>> from numcodecs.abc import Codec
>>> import multiprocessing as mp
>>> mp.set_start_method("spawn")
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
  File "/usr/lib/python3.10/multiprocessing/context.py", line 247, in set_start_method
    raise RuntimeError('context has already been set')
RuntimeError: context has already been set

Problem description
Using libraries with numcodec, I am not able to control multiprocessing
Version and installation information
Python version 3.10 and 3.11.
numcodecs version 0.11.0 and 0.13 (latest).
I have tried in Ubuntu Linux 22.04, Windows, and using an Ubuntu docker image (22.04)

Actually discovered it's this line: https://github.com/zarr-developers/numcodecs/blob/8b53fc135373d526338399c2dc582673cd560f87/numcodecs/blosc.pyx#L79
which happens globally, and thus prevents later configuration of set_start_method.
Minimal reproducible example:
>>> import multiprocessing
>>> exit()
(venv) PS D:\pd-l1-work> python
Python 3.11.0 (main, Oct 24 2022, 18:26:48) [MSC v.1933 64 bit (AMD64)] on win32
Type "help", "copyright", "credits" or "license" for more information.
>>> import multiprocessing
>>> x = multiprocessing.Lock()
>>> multiprocessing.set_start_method("spawn")
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
  File "C:\Python311\Lib\multiprocessing\context.py", line 247, in set_start_method
    raise RuntimeError('context has already been set')
RuntimeError: context has already been set

On second thought, I'll close this as it might not be a bug 😄


Add try blocks to catch missing access-control key

Bugfix for Missing access_control key

This issue should not occur in production but has appeared during testing as temporary catalogs are added to the STAC-FastApi deployment
Added try-catch blocks to ensure this issue does not lead to wrong HTTP responses
Only entries that contain access_control specification, and are accessible to the user, will be returned to the users, others will be logged but discarded from the response

Looks all good. My doubt ->await self.database.find_catalog(catalog_path=catalog_path) , Is this method already getting handled for exceptions? Thanks

All access-control is handled in the core/core.py code and not in database_logic.py so no additional exception handling is required here.


Automated cherry pick of #1986: fix: init sysadmin as system user

Cherry pick of #1986 on release/2.10.0.
#1986: fix: init sysadmin as system user

Codecov Report

:exclamation: No coverage uploaded for pull request base (release/2.10.0@18a7346). Click here to learn what that means.
The diff coverage is 0%.

@@               Coverage Diff                @@
##             release/2.10.0   #1987   +/-   ##
================================================
  Coverage                  ?   7.61%
================================================
  Files                     ?     410
  Lines                     ?   63173
  Branches                  ?       0
================================================
  Hits                      ?    4812
  Misses                    ?   57950
  Partials                  ?     411

Flag
Coverage Δ

#aFlag
7.61% <0%> (?)

Impacted Files
Coverage Δ

pkg/keystone/models/users.go
2.32% <0%> (ø)

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 18a7346...9413360. Read the comment docs.

/approve
/lgtm


⚠ GitLab Server has degraded performance

In dbef230, GitLab Server (https://gitlab01.its-telekom.eu) experienced degraded performance:

HTTP code: 200
Response time: 6198 ms

Resolved: GitLab Server performance has improved in 29f2ee9.


python311Packages.pyrainbird: 4.0.0 -> 4.0.1

Diff: https://github.com/allenporter/pyrainbird/compare/refs/tags/4.0.0...4.0.1
Changelog: https://github.com/allenporter/pyrainbird/releases/tag/4.0.1
Description of changes

Things done

Built on platform(s)

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

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

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

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

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

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

[ ] Fits CONTRIBUTING.md.

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

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

5 packages built:

home-assistant-component-tests.rainbird
python310Packages.pyrainbird
python310Packages.pyrainbird.dist
python311Packages.pyrainbird
python311Packages.pyrainbird.dist


The current way of subdirectory detection is not properly compatible with windows

Because the path format is different, additional processing may be required
Such as:\ and /

I am working on a big refactor on branch refactor. I can probably also do a rewrite of the path handling features.


[Bug] get_keepbits returning a negative integer value for .grib datasets

xbitinfo version: 0.1.dev587+g10a08dd
Python version: 3.9.18
Operating System: `macOS Sonoma Version 14.4 (23E214) (Apple M1 Processor)

Description
Was trying the xbitinfo and following the tutorial presented and when compressing the .grib datasets it seems that the compression fails as the get_keepbits function returns negative values.
What I Did
import xbitinfo as xb
import xarray as xr

dataset = xr.tutorial.load_dataset("era5-2mt-2019-03-uk.grib").astype("float32")
info_p_bit = xb.get_bitinformation(dataset, dim="longitude", implementation="python")
keepbits = xb.get_keepbits(
    info_p_bit, 0.99
)  # returns negative number due to lossy compression
ds_bitrounded = xb.xr_bitround(
    dataset, keepbits
)  # raises a warning as keepbits is negative

i want to fix this issue please assign me this issue.

@sarthakvyas16 before assigning you to the issue it would be good to hear your ideas and discuss them.

ok let me explain.
First of all i m review the implementation of get_keepbits. Understand its expected input, output, and the logic that leads to the computation of the return value after that Check the input being fed into get_keepbits. Ensure that the .grib datasets are formatted correctly and do not contain any corrupted or unexpected values and then ensure that all variables used in the calculations are of the correct data type. Sometimes, implicit type conversions can lead to unexpected negative values and tracing the calculation which help us to identify where the negative entity is originating.
and many more things which use to sortout bug.If you are satisfy by my Point of view , then assign me this issue.


How to trigger the printer to open the cash drawer ?

@MinaZakaria Hi!
What do you mean by Cash Drawer?

The Cash Drawer is the place that contains the money.
So times we need to open the drawer when printing the receipt to add more money.
There is a cable that connects from the Epson printer to the drawer. and then it wait for a command from the printer to open the cash drawer

@MinaZakaria  Thanks for the explanation!
Actually, to provide this functionality we need to add the corresponding method addPulse to handleCommand method for iOS and Android. Unfortunately, at the time I don't have the capacity to add it. But if you have, I'd really appreciate it )
https://github.com/tr3v3r/react-native-esc-pos-printer/blob/ba2ed89970993471d4538f1be6146be7a89ff671/ios/EscPosPrinter.m#L481
https://github.com/tr3v3r/react-native-esc-pos-printer/blob/ba2ed89970993471d4538f1be6146be7a89ff671/android/src/main/java/com/reactnativeescposprinter/EscPosPrinterModule.java#L487
Than we can just use it like:
 printing()
 .addText('text')
 .addImage('logo.png`)
 .addPulse( // args )
 .addCut()

Here the method specification:

@MinaZakaria a quick way to do this
import Encoder from 'esc-pos-encoder';
       ....
        const encoder = new Encoder();
        const printing = new EscPosPrinter.printing();
        encoder.pulse(0, 100, 100);
        const status = await printing.data(encoder.encode()).send();

This works for me

Version 1.5.0 adds this functionality


fix(material/progress-bar): do not adjust color if it is not defined as a color

Do not adjust color if the $color resolved to something different from a color (e.g. a CSS variable).
This is a regression. It was introduced in https://github.com/angular/components/commit/f384c24b943d7eb36fc73cfe81abb8b08a90e1b7 and fixes #25981

Testing all the possibilities for the progress-bar (buffer, query, indeterminate...), I have seen that using CSS variables has many adverse effects, therefore, I have closed the PR, since it does not correct the problem at all.
I think this can only be resolved when https://github.com/material-components/material-components-web/issues/4709 is resolved.


Azure Cosmos Db extension error no such file or directory when browsing azure document db

<Please be sure to remove any private information before submitting.>
Repro steps:
connected to my azure document db, but I can't browse a particular document
Action: cosmosDB.openDocument
Error type: ENOENT
Error Message: ENOENT: no such file or directory, open 'C:\Users\xxxxxxx\AppData\Local\Temp\vscode-cosmosdb-editor\xxxxxx
-cosmos-document.json'
Version: 0.10.0
OS: win32

@eric-couch This is always a particular document only?  Is there anything unusual about the _id of that document?
cc @PrashanthCorp


Update detect-enable-and-disable-smbv1-v2-v3.md

Some Windows versions are dealt with on this page, but "Applies to" doesn't mention them.

@DaPadrePedro : Thanks for your contribution! The author(s) have been notified to review your proposed change.

Hi @DaPadrePedro.  These OS versions are now out of support. https://docs.microsoft.com/en-us/troubleshoot/windows-server/windows-server-eos-faq/end-of-support-windows-server-2008-2008r2. #please-close.


V2 HMR

Attempt to add HMR and dev mode back into v2
Todo

[ ] Make it work

Not working off this branch anymore