[BUG] Power loss causes volume unable to mount

Description:
Hard reset of k3s cluster causes intermittent volume failure to recover.
MountVolume.SetUp failed for volume "pvc-0e0511b0-019e-4305-af82-fa524b1a088f" : rpc error: code = InvalidArgument desc = There is no block device frontend for volume pvc-0e0511b0-019e-4305-af82-fa524b1a088f
Deleting pod or pvc does not help.
To Reproduce
Steps to reproduce the behavior:
0. Install latest k3s on fresh (in my case 6-node) baremetal debian 10 cluster.
Verified cluster working ok with longhorn for multiple applications (kafka, spark, cassandra, etc).

Install YugabyteDB kubernetes demo
https://docs.yugabyte.com/latest/deploy/kubernetes/single-zone/oss/helm-chart/
Create some tables and insert some data.
Power off entire cluster.
Restart cluster and wait until all pods come back up (may take a while).

Occasionally a pod is stuck in ContainerCreating because volume does not mount.
In my case most of the pods were ok, only one of 3 masters could not start. Restarting pod did not help.
Expected behavior
Automatic recovery after power loss
Log
attached output of:
kubectl logs -n longhorn-system longhorn-manager-dtr84
Environment:

Longhorn version: image: longhornio/longhorn-manager:v0.8.1
Kubernetes version: k3s latest
Node OS type and version: recent debian 10

Additional context
Add any other context about the problem here.
longhorn.log
grep for affected pvc (0e0) in all manager instances logs:
0e0.log

@threedliteguy Can you try v1.0.0? We've fixed a few issues regarding the power down cases in v1.0.0.
Also, power down immediately after data are written is like pulling a hard drive, there can be data stored by the filesystem's cache but hasn't been written to the underlying block device yet. It's possible that the disk might need fsck or similar to recover the data later. But in your case, the error message there is no block device frontend indicates likely something wrong with the volume reattach process.

I upgraded to 1.0.0 and tried the same test and did not have any issue this time, although I may have to try a few more times to be sure.

I restarted everything with 'shutdown now' a second time, and this time 3 out of about 87 pods failed to attach volumes (events below from 'describe'). I wonder if it's helpful to increase priority of longhorn-system pods so that they are able to start before the other dependent application pods.
kubectl  describe pod cassandra-4
Warning  FailedMount  22m (x11 over 29m)    kubelet, a3.localdomain  MountVolume.MountDevice failed for volume "pvc-a7eb03bb-66e0-44b8-bc9e-a522c91e671d" : kubernetes.io/csi: attacher.MountDevice failed to create newCsiDriverClient: driver name driver.longhorn.io not found in the list of registered CSI drivers
Warning  FailedMount  8m33s (x7 over 20m)   kubelet, a3.localdomain  MountVolume.SetUp failed for volume "pvc-a7eb03bb-66e0-44b8-bc9e-a522c91e671d" : rpc error: code = InvalidArgument desc = There is no block device frontend for volume pvc-a7eb03bb-66e0-44b8-bc9e-a522c91e671d
Warning  FailedMount  6m35s (x10 over 27m)  kubelet, a3.localdomain  Unable to attach or mount volumes: unmounted volumes=[cassandra-data], unattached volumes=[cassandra-data default-token-7xmc9]: timed out waiting for the condition
Warning  FailedMount  2m28s (x2 over 18m)   kubelet, a3.localdomain  Unable to attach or mount volumes: unmounted volumes=[cassandra-data], unattached volumes=[default-token-7xmc9 cassandra-data]: timed out waiting for the condition
kubectl -n yb-demo describe pod yb-tserver-2
Warning  FailedMount  22m (x11 over 28m)   kubelet, a3.localdomain  MountVolume.MountDevice failed for volume "pvc-9e382fd9-fcdf-47d4-be5d-79d3dc487cbf" : kubernetes.io/csi: attacher.MountDevice failed to create newCsiDriverClient: driver name driver.longhorn.io not found in the list of registered CSI drivers
Warning  FailedMount  21m (x11 over 28m)   kubelet, a3.localdomain  MountVolume.MountDevice failed for volume "pvc-a3d3e76f-e644-485e-812e-75a8942376e1" : kubernetes.io/csi: attacher.MountDevice failed to create newCsiDriverClient: driver name driver.longhorn.io not found in the list of registered CSI drivers
Warning  FailedMount  18m (x2 over 20m)    kubelet, a3.localdomain  MountVolume.SetUp failed for volume "pvc-9e382fd9-fcdf-47d4-be5d-79d3dc487cbf" : rpc error: code = InvalidArgument desc = There is no block device frontend for volume pvc-9e382fd9-fcdf-47d4-be5d-79d3dc487cbf
Warning  FailedMount  12m                  kubelet, a3.localdomain  Unable to attach or mount volumes: unmounted volumes=[datadir1 datadir0], unattached volumes=[datadir1 default-token-znkvc datadir0]: timed out waiting for the condition
Warning  FailedMount  7m55s (x4 over 20m)  kubelet, a3.localdomain  Unable to attach or mount volumes: unmounted volumes=[datadir0 datadir1], unattached volumes=[default-token-znkvc datadir0 datadir1]: timed out waiting for the condition
Warning  FailedMount  105s (x8 over 26m)   kubelet, a3.localdomain  Unable to attach or mount volumes: unmounted volumes=[datadir0 datadir1], unattached volumes=[datadir0 datadir1 default-token-znkvc]: timed out waiting for the condition
This pod is in Running Not Ready status, the previous two examples are in Unknown status.
kubectl  describe pod zoo-0 -n kafka
Warning  Unhealthy       39m (x5818 over 17h)   kubelet, a0.localdomain  Readiness probe errored: rpc error: code = DeadlineExceeded desc = failed to exec in container: timeout 1s exceeded: context deadline exceeded
Warning  FailedMount     28m                    kubelet, a0.localdomain  Unable to attach or mount volumes: unmounted volumes=[data], unattached volumes=[data default-token-rtpk7 configmap config]: timed out waiting for the condition
Warning  FailedMount     27m (x9 over 30m)      kubelet, a0.localdomain  MountVolume.MountDevice failed for volume "pvc-c0c5f06b-8b4c-4611-b083-80b8d84c4814" : kubernetes.io/csi: attacher.MountDevice failed to create newCsiDriverClient: driver name driver.longhorn.io not found in the list of registered CSI drivers
Warning  FailedMount     24m (x2 over 26m)      kubelet, a0.localdomain  Unable to attach or mount volumes: unmounted volumes=[data], unattached volumes=[configmap config data default-token-rtpk7]: timed out waiting for the condition
Warning  FailedMount     23m (x2 over 25m)      kubelet, a0.localdomain  MountVolume.SetUp failed for volume "pvc-c0c5f06b-8b4c-4611-b083-80b8d84c4814" : rpc error: code = InvalidArgument desc = There is no block device frontend for volume pvc-c0c5f06b-8b4c-4611-b083-80b8d84c4814
Warning  FailedMount     22m                    kubelet, a0.localdomain  Unable to attach or mount volumes: unmounted volumes=[data], unattached volumes=[config data default-token-rtpk7 configmap]: timed out waiting for the condition
Normal   SandboxChanged  21m                    kubelet, a0.localdomain  Pod sandbox changed, it will be killed and re-created.
Normal   Pulled          21m                    kubelet, a0.localdomain  Container image "solsson/kafka-initutils@sha256:f6d9850c6c3ad5ecc35e717308fddb47daffbde18eb93e98e031128fe8b899ef" already present on machine
Normal   Created         21m                    kubelet, a0.localdomain  Created container init-config
Normal   Started         21m                    kubelet, a0.localdomain  Started container init-config
Normal   Pulled          21m                    kubelet, a0.localdomain  Container image "solsson/kafka:2.4.1@sha256:79761e15919b4fe9857ec00313c9df799918ad0340b684c0163ab7035907bb5a" already present on machine
Normal   Created         21m                    kubelet, a0.localdomain  Created container zookeeper
Normal   Started         21m                    kubelet, a0.localdomain  Started container zookeeper
Warning  Unhealthy       20m (x4 over 21m)      kubelet, a0.localdomain  Readiness probe failed:
Warning  Unhealthy       3m35s (x102 over 20m)  kubelet, a0.localdomain  Readiness probe errored: rpc error: code = DeadlineExceeded desc = failed to exec in container: timeout 1s exceeded: context deadline exceeded

More info if this helps -
Rebooting cluster once again resulted in a fewer number of stuck pods that time around.
Then I found that if I cordon the node the stuck pod(s) is on, delete the pod, wait for it to start on another node, then uncordon the node, then it usually ran ok instead of being stuck in Unknown or ContainerCreating.  One pod also failed on the next node too so I cordoned it also and then it worked on the 3rd node.  After everything was back up, the original test data was still there in yugabyte, cassandra and kafka.

UI is using alipayobjectshttps://atlas.eff.org//domains/alipayobjects.com.html
On Monday, June 8, 2020, 04:25:17 AM CDT, Shuo Wu<EMAIL_ADDRESS>wrote:

After reboot, it seems that Longhorn doesn't reattach the volume correctly then Kubernetes fails to remount it. Hence the error There is no block device frontend is triggered.
https://github.com/longhorn/longhorn-manager/blob/3124dd576c695f3f35cbb711517eea341ddd10a9/csi/node_server.go#L52
I failed to reproduce it on a regular K8S cluster. I am not sure if there will be any differences for the Longhorn on K3S + Debian 10, or there is something wrong with my reproducing steps.
Can you check the reproducing steps?:

Deploy a 6-node K8S cluster.
shuo-longhorn-cluster-3-master-1   Ready    controlplane,etcd,worker   171m   v1.17.4
shuo-longhorn-cluster-3-worker-1   Ready    worker                     54m    v1.17.4
shuo-longhorn-cluster-3-worker-2   Ready    worker                     167m   v1.17.4
shuo-longhorn-cluster-3-worker-3   Ready    worker                     168m   v1.17.4
shuo-longhorn-cluster-3-worker-4   Ready    worker                     169m   v1.17.4
shuo-longhorn-cluster-3-worker-5   Ready    worker                     168m   v1.17.4

Deploy yb-demo:
kubectl create namespace yb-demo

helm install yb-demo yugabytedb/yugabyte
--set resource.master.requests.cpu=0.5,resource.master.requests.memory=0.5Gi,
resource.tserver.requests.cpu=0.5,resource.tserver.requests.memory=0.5Gi,
storage.master.storageClass=longhorn,storage.tserver.storageClass=longhorn
--namespace yb-demo

Power off all nodes and wait for a while.
Power on all nodes and wait for recovery.

Finally, all yb workloads becomes running. The event logs are like:
Warning  FailedMount             3m53s                  kubelet, shuo-longhorn-cluster-3-worker-1  Unable to attach or mount volumes: unmounted volumes=[datadir0 datadir1], unattached volumes=[default-token-h7c8w datadir0 datadir1]: timed out waiting for the condition
Warning  FailedMount             3m5s (x9 over 5m19s)   kubelet, shuo-longhorn-cluster-3-worker-1  MountVolume.MountDevice failed for volume "pvc-9a9a0da8-8a28-4a07-b00e-bc2283a42ff5" : kubernetes.io/csi: attacher.MountDevice failed to create newCsiDriverClient: driver name driver.longhorn.io not found in the list of registered CSI drivers
Warning  FailedMount             2m25s (x9 over 4m45s)  kubelet, shuo-longhorn-cluster-3-worker-1  MountVolume.MountDevice failed for volume "pvc-bf314b3a-da43-403e-a9b3-79d015c3c9e6" : kubernetes.io/csi: attacher.MountDevice failed to create newCsiDriverClient: driver name driver.longhorn.io not found in the list of registered CSI drivers
Warning  FailedMount             96s                    kubelet, shuo-longhorn-cluster-3-worker-1  Unable to attach or mount volumes: unmounted volumes=[datadir0 datadir1], unattached volumes=[datadir0 datadir1 default-token-h7c8w]: timed out waiting for the condition
Normal   SandboxChanged          22s                    kubelet, shuo-longhorn-cluster-3-worker-1  Pod sandbox changed, it will be killed and re-created.
Normal   Pulled                  10s                    kubelet, shuo-longhorn-cluster-3-worker-1  Container image "yugabytedb/yugabyte:<IP_ADDRESS>-b17" already present on machine
Normal   Created                 10s                    kubelet, shuo-longhorn-cluster-3-worker-1  Created container yb-master
Normal   Started                 9s                     kubelet, shuo-longhorn-cluster-3-worker-1  Started container yb-master
Normal   Pulled                  9s                     kubelet, shuo-longhorn-cluster-3-worker-1  Container image "busybox:1.31" already present on machine
Normal   Created                 9s                     kubelet, shuo-longhorn-cluster-3-worker-1  Created container yb-cleanup
If possible, can you generate a support bundle after reproducing and send it to us?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or unsubscribe.

UI is using alipayobjectshttps://atlas.eff.org//domains/alipayobjects.com.html

Sorry, I cannot follow what you are talking about...

I went to create a support bundle so I think I needed to set up the ui by adding an Ingress. But when I tested with curl it showed an alipayobjects url, which would be a security issue.

Do you mean the ingress/UI setup in Longhorn doc doesn't work? If YES, we can file a separate issue to track that.

yes

Can you file a bug then? I don't know the details of this UI issue, including the setup and the reproducing steps.

Made reboot on nodes, have same issue. Any way to solve it? Detaching makes same error. After reattach redis just don't start back. It can't read file seems.
1:M 13 Aug 2020 15:53:53.144 * Reading RDB preamble from AOF file... 1:M 13 Aug 2020 15:53:53.155 * Reading the remaining AOF tail...

Made reboot on nodes, have same issue. Any way to solve it? Detaching makes same error. After reattach redis just don't start back. It can't read file seems.
1:M 13 Aug 2020 15:53:53.144 * Reading RDB preamble from AOF file... 1:M 13 Aug 2020 15:53:53.155 * Reading the remaining AOF tail...

What's the log in longhorn-manager pods? And can you check:

If the related Longhorn volume is attached.
If the related Longhorn volume is remounted after the attachment.
If the Longhorn volume remount is propagated to the related workload.

These two docs may be helpful:
https://longhorn.io/docs/1.0.1/high-availability/node-failure/#what-to-expect-when-recovering-a-failed-kubernetes-node
https://longhorn.io/docs/1.0.1/high-availability/recover-volume/#manually-restart-workload-containers

ty, links guided me in needed direction.
i did not cheched file size, but looks like redis used up whole volume somehow(thou it's strange for nearly just started project...) after restart
Sorry for false report.

jenkins pod not running with longhorn pv
kubernetes version
[root@master01 ~]# kubectl version --short
Client Version: v1.18.6
Server Version: v1.18.6

longhorn verison
1.0.2

pv and pvc is bound
[root@master01 ~]# kubectl -n jenkins get pvc
NAME                STATUS   VOLUME                                     CAPACITY   ACCESS MODES   STORAGECLASS   AGE
jenkins-blueocean   Bound    pvc-1cf4253a-8bf2-4aab-a2d9-470add26096f   10Gi       RWO            longhorn       14m
[root@master01 ~]# kubectl -n jenkins get pv
NAME                                       CAPACITY   ACCESS MODES   RECLAIM POLICY   STATUS   CLAIM                       STORAGECLASS   REASON   AGE
pvc-1cf4253a-8bf2-4aab-a2d9-470add26096f   10Gi       RWO            Delete           Bound    jenkins/jenkins-blueocean   longhorn                14m
[root@master01 ~]#

jenkins pod describe logs
 $ kubectl -n jenkins describe pods jenkins-blueocean-6cd88c96f-rd867
......
Events:
  Type     Reason                  Age                From                     Message
  ----     ------                  ----               ----                     -------
  Warning  FailedScheduling        12m (x3 over 12m)  default-scheduler        running "VolumeBinding" filter plugin for pod "jenkins-blueocean-6cd88c96f-rd867": pod has unbound immediate PersistentVolumeClaims
  Normal   Scheduled               12m                default-scheduler        Successfully assigned jenkins/jenkins-blueocean-6cd88c96f-rd867 to node01
  Normal   SuccessfulAttachVolume  12m                attachdetach-controller  AttachVolume.Attach succeeded for volume "pvc-1cf4253a-8bf2-4aab-a2d9-470add26096f"
  Warning  FailedMount             12m (x2 over 12m)  kubelet, node01          MountVolume.MountDevice failed for volume "pvc-1cf4253a-8bf2-4aab-a2d9-470add26096f" : kubernetes.io/csi: attacher.MountDevice failed to create newCsiDriverClient: driver name driver.longhorn.io not found in the list of registered CSI drivers
  Normal   Pulling                 12m                kubelet, node01          Pulling image "jenkinsci/blueocean:latest"
  Normal   Pulled                  12m                kubelet, node01          Successfully pulled image "jenkinsci/blueocean:latest"
  Normal   Created                 12m                kubelet, node01          Created container copy-default-config
  Normal   Started                 12m                kubelet, node01          Started container copy-default-config

longhorn pods
[root@master01 ~]# kubectl -n longhorn-system get pods
NAME                                        READY   STATUS    RESTARTS   AGE
csi-attacher-5b4745c5f7-5xtd4               1/1     Running   0          16m
csi-attacher-5b4745c5f7-s4ggs               1/1     Running   0          16m
csi-attacher-5b4745c5f7-vzdnp               1/1     Running   1          53m
csi-provisioner-57d6dbf5f4-fvrsm            1/1     Running   0          16m
csi-provisioner-57d6dbf5f4-kl5zw            1/1     Running   1          16m
csi-provisioner-57d6dbf5f4-qvzfw            1/1     Running   1          53m
csi-resizer-75ff56bc48-ff99s                1/1     Running   0          16m
csi-resizer-75ff56bc48-sk7hl                1/1     Running   1          53m
csi-resizer-75ff56bc48-vh6mb                1/1     Running   0          16m
engine-image-ei-ee18f965-2vw2z              1/1     Running   1          30m
engine-image-ei-ee18f965-6nbg7              1/1     Running   1          54m
engine-image-ei-ee18f965-s568l              1/1     Running   1          54m
instance-manager-e-095893d4                 1/1     Running   0          22m
instance-manager-e-7f686501                 1/1     Running   0          15m
instance-manager-e-9d4174ce                 1/1     Running   0          15m
instance-manager-r-1206e730                 1/1     Running   0          22m
instance-manager-r-21bd2610                 1/1     Running   0          15m
instance-manager-r-ddc6c865                 1/1     Running   0          15m
longhorn-csi-plugin-8ltjd                   2/2     Running   4          30m
longhorn-csi-plugin-mkffq                   2/2     Running   3          53m
longhorn-csi-plugin-pgrrb                   2/2     Running   3          53m
longhorn-driver-deployer-6756bb8fd6-s7f9k   1/1     Running   0          16m
longhorn-manager-jnc6k                      1/1     Running   1          30m
longhorn-manager-nwt9g                      1/1     Running   2          54m
longhorn-manager-pldwq                      1/1     Running   1          54m
longhorn-ui-6fb889895f-2wt9b                1/1     Running   1          16m

longhorn manager logs
[root@master01 ~]#  kubectl -n longhorn-system logs -f longhorn-manager-nwt9g
time="2020-08-27T08:30:16Z" level=info msg="Start overwriting built-in settings with customized values"
time="2020-08-27T08:30:16Z" level=info msg="cannot list the content of the src directory /var/lib/rancher/longhorn/engine-binaries for the copy, will do nothing: Failed to execute: nsenter [--mount=/host/proc/1125/ns/mnt --net=/host/proc/1125/ns/net bash -c ls /var/lib/rancher/longhorn/engine-binaries/*], output , stderr, ls: cannot access /var/lib/rancher/longhorn/engine-binaries/*: No such file or directory\n, error exit status 2"
time="2020-08-27T08:30:16Z" level=info msg="Start upgrading"
time="2020-08-27T08:30:17Z" level=info msg="No API version upgrade is needed"
time="2020-08-27T08:30:17Z" level=info msg="Finish upgrading"
time="2020-08-27T08:30:17Z" level=info msg="Upgrade leader lost: master01"
time="2020-08-27T08:30:18Z" level=debug msg="Engine image longhornio/longhorn-engine:v1.0.2 is ready"
time="2020-08-27T08:30:18Z" level=info msg="Listening on <IP_ADDRESS>:9500"
time="2020-08-27T08:30:18Z" level=info msg="Start Longhorn replica controller"
time="2020-08-27T08:30:18Z" level=info msg="Start Longhorn Setting controller"
time="2020-08-27T08:30:18Z" level=info msg="Start Longhorn engine controller"
time="2020-08-27T08:30:18Z" level=info msg="Start Longhorn volume controller"
time="2020-08-27T08:30:18Z" level=info msg="Start Longhorn Engine Image controller"
time="2020-08-27T08:30:18Z" level=info msg="Start Longhorn node controller"
time="2020-08-27T08:30:18Z" level=info msg="Start Longhorn websocket controller"
time="2020-08-27T08:30:18Z" level=info msg="Start Longhorn Kubernetes node controller"
time="2020-08-27T08:30:18Z" level=info msg="Starting Longhorn instance manager controller"
time="2020-08-27T08:30:18Z" level=info msg="Start kubernetes controller"
time="2020-08-27T08:30:18Z" level=info msg="Event(v1.ObjectReference{Kind:\"Node\", Namespace:\"longhorn-system\", Name:\"master01\", UID:\"0cef7f09-6d64-47c0-a771-74167d67e2eb\", APIVersion:\"longhorn.io/v1beta1\", ResourceVersion:\"853980\", FieldPath:\"\"}): type: 'Warning' reason: 'Ready' Node master01 is down: the manager pod longhorn-manager-nwt9g is not running"
time="2020-08-27T08:30:18Z" level=warning msg="Starts to clean up then recreates pod for instance manager instance-manager-e-095893d4 with state error"
time="2020-08-27T08:30:18Z" level=warning msg="Starts to clean up then recreates pod for instance manager instance-manager-r-1206e730 with state error"
time="2020-08-27T08:30:18Z" level=info msg="Created instance manager pod instance-manager-r-1206e730 for instance manager instance-manager-r-1206e730"
time="2020-08-27T08:30:18Z" level=info msg="Created instance manager pod instance-manager-e-095893d4 for instance manager instance-manager-e-095893d4"
time="2020-08-27T08:30:21Z" level=info msg="Event(v1.ObjectReference{Kind:\"Node\", Namespace:\"longhorn-system\", Name:\"master01\", UID:\"0cef7f09-6d64-47c0-a771-74167d67e2eb\", APIVersion:\"longhorn.io/v1beta1\", ResourceVersion:\"854365\", FieldPath:\"\"}): type: 'Normal' reason: 'Ready' Node master01 is ready"
time="2020-08-27T08:30:21Z" level=warning msg="Error syncing Longhorn instance manager longhorn-system/instance-manager-e-095893d4: fail to sync instance manager for longhorn-system/instance-manager-e-095893d4: failed to get version: rpc error: code = Unavailable desc = all SubConns are in TransientFailure, latest connection error: connection error: desc = \"transport: Error while dialing dial tcp <IP_ADDRESS>:8500: connect: connection refused\""
time="2020-08-27T08:30:21Z" level=warning msg="Error syncing Longhorn instance manager longhorn-system/instance-manager-e-095893d4: fail to sync instance manager for longhorn-system/instance-manager-e-095893d4: failed to get version: rpc error: code = Unavailable desc = all SubConns are in TransientFailure, latest connection error: connection error: desc = \"transport: Error while dialing dial tcp <IP_ADDRESS>:8500: connect: connection refused\""
E0827 08:30:21.595172       1 instance_manager_controller.go:248] fail to sync instance manager for longhorn-system/instance-manager-e-095893d4: failed to get version: rpc error: code = Unavailable desc = all SubConns are in TransientFailure, latest connection error: connection error: desc = "transport: Error while dialing dial tcp <IP_ADDRESS>:8500: connect: connection refused"
time="2020-08-27T08:30:21Z" level=warning msg="Dropping Longhorn instance manager longhorn-system/instance-manager-e-095893d4 out of the queue: fail to sync instance manager for longhorn-system/instance-manager-e-095893d4: failed to get version: rpc error: code = Unavailable desc = all SubConns are in TransientFailure, latest connection error: connection error: desc = \"transport: Error while dialing dial tcp <IP_ADDRESS>:8500: connect: connection refused\""
time="2020-08-27T08:30:22Z" level=debug msg="Start monitoring instance manager instance-manager-r-1206e730"
<IP_ADDRESS> - - [27/Aug/2020:08:30:45 +0000] "GET /v1 HTTP/1.1" 200 3133 "" "Go-http-client/1.1"
time="2020-08-27T08:30:47Z" level=debug msg="Start monitoring instance manager instance-manager-e-095893d4"
time="2020-08-27T08:31:15Z" level=info msg="Event(v1.ObjectReference{Kind:\"Node\", Namespace:\"longhorn-system\", Name:\"node01\", UID:\"608d7008-45ca-42be-ad58-f0304acf7f75\", APIVersion:\"longhorn.io/v1beta1\", ResourceVersion:\"854068\", FieldPath:\"\"}): type: 'Warning' reason: 'Ready' Kubernetes node node01 not ready: NodeStatusUnknown"
time="2020-08-27T08:31:15Z" level=debug msg="Instance Manager Controller master01 picked up instance-manager-r-ddc6c865"
time="2020-08-27T08:31:15Z" level=info msg="Event(v1.ObjectReference{Kind:\"Node\", Namespace:\"longhorn-system\", Name:\"node02\", UID:\"698957ef-abdb-4dac-9eef-c2f71b9a0c5a\", APIVersion:\"longhorn.io/v1beta1\", ResourceVersion:\"854067\", FieldPath:\"\"}): type: 'Warning' reason: 'Ready' Kubernetes node node02 not ready: NodeStatusUnknown"
time="2020-08-27T08:31:15Z" level=debug msg="Instance Manager Controller master01 picked up instance-manager-r-21bd2610"
time="2020-08-27T08:31:17Z" level=debug msg="Instance Manager Controller master01 picked up instance-manager-e-7f686501"
time="2020-08-27T08:31:17Z" level=debug msg="Instance Manager Controller master01 picked up instance-manager-e-9d4174ce"
time="2020-08-27T08:31:18Z" level=debug msg="Engine Image Controller master01 picked up ei-ee18f965 (longhornio/longhorn-engine:v1.0.2)"
time="2020-08-27T08:36:24Z" level=info msg="Event(v1.ObjectReference{Kind:\"Node\", Namespace:\"longhorn-system\", Name:\"node02\", UID:\"698957ef-abdb-4dac-9eef-c2f71b9a0c5a\", APIVersion:\"longhorn.io/v1beta1\", ResourceVersion:\"855774\", FieldPath:\"\"}): type: 'Normal' reason: 'Ready' Node node02 is ready"
<IP_ADDRESS> - - [27/Aug/2020:08:36:51 +0000] "GET /v1 HTTP/1.1" 200 3133 "" "curl/7.58.0"
<IP_ADDRESS> - - [27/Aug/2020:08:36:52 +0000] "GET /v1 HTTP/1.1" 200 3133 "" "Go-http-client/1.1"
<IP_ADDRESS> - - [27/Aug/2020:08:37:10 +0000] "GET /v1/volumes/pvc-1cf4253a-8bf2-4aab-a2d9-470add26096f HTTP/1.1" 404 0 "" "Go-http-client/1.1"
time="2020-08-27T08:37:10Z" level=debug msg="Created volume pvc-1cf4253a-8bf2-4aab-a2d9-470add26096f: {Size:10737418240 Frontend:blockdev FromBackup: NumberOfReplicas:3 StaleReplicaTimeout:30 NodeID: EngineImage:longhornio/longhorn-engine:v1.0.2 RecurringJobs:[] BaseImage: Standby:false DiskSelector:[] NodeSelector:[] DisableFrontend:false}"
<IP_ADDRESS> - - [27/Aug/2020:08:37:10 +0000] "POST /v1/volumes HTTP/1.1" 200 973 "" "Go-http-client/1.1"
time="2020-08-27T08:37:10Z" level=info msg="Event(v1.ObjectReference{Kind:\"Node\", Namespace:\"longhorn-system\", Name:\"node01\", UID:\"608d7008-45ca-42be-ad58-f0304acf7f75\", APIVersion:\"longhorn.io/v1beta1\", ResourceVersion:\"856525\", FieldPath:\"\"}): type: 'Normal' reason: 'Ready' Node node01 is ready"
time="2020-08-27T08:37:10Z" level=debug msg="Replica controller master01 picked up pvc-1cf4253a-8bf2-4aab-a2d9-470add26096f-r-83a5b4d6"
time="2020-08-27T08:37:10Z" level=debug msg="Instance handler updated instance pvc-1cf4253a-8bf2-4aab-a2d9-470add26096f-r-83a5b4d6 state, old state , new state stopped"
time="2020-08-27T08:37:10Z" level=debug msg="Replica controller master01 picked up pvc-1cf4253a-8bf2-4aab-a2d9-470add26096f-r-cf298d0e"
time="2020-08-27T08:37:10Z" level=debug msg="Instance handler updated instance pvc-1cf4253a-8bf2-4aab-a2d9-470add26096f-r-cf298d0e state, old state , new state stopped"
<IP_ADDRESS> - - [27/Aug/2020:08:37:12 +0000] "GET /v1/volumes/pvc-1cf4253a-8bf2-4aab-a2d9-470add26096f HTTP/1.1" 200 3726 "" "Go-http-client/1.1"
<IP_ADDRESS> - - [27/Aug/2020:08:37:14 +0000] "GET /v1/volumes/pvc-1cf4253a-8bf2-4aab-a2d9-470add26096f HTTP/1.1" 200 3935 "" "Go-http-client/1.1"
<IP_ADDRESS> - - [27/Aug/2020:08:37:14 +0000] "GET /v1/nodes/node01 HTTP/1.1" 200 1583 "" "Go-http-client/1.1"
time="2020-08-27T08:37:14Z" level=debug msg="Attaching volume pvc-1cf4253a-8bf2-4aab-a2d9-470add26096f to node01 with disableFrontend set false"
<IP_ADDRESS> - - [27/Aug/2020:08:37:14 +0000] "POST /v1/volumes/pvc-1cf4253a-8bf2-4aab-a2d9-470add26096f?action=attach HTTP/1.1" 200 2528 "" "Go-http-client/1.1"
time="2020-08-27T08:37:14Z" level=debug msg="Prepare to create instance pvc-1cf4253a-8bf2-4aab-a2d9-470add26096f-r-cf298d0e"
time="2020-08-27T08:37:14Z" level=info msg="Event(v1.ObjectReference{Kind:\"Replica\", Namespace:\"longhorn-system\", Name:\"pvc-1cf4253a-8bf2-4aab-a2d9-470add26096f-r-cf298d0e\", UID:\"58fc75e4-43c1-4e61-ae61-1f1db24ef88c\", APIVersion:\"longhorn.io/v1beta1\", ResourceVersion:\"856647\", FieldPath:\"\"}): type: 'Normal' reason: 'Start' Starts pvc-1cf4253a-8bf2-4aab-a2d9-470add26096f-r-cf298d0e"
time="2020-08-27T08:37:15Z" level=debug msg="Instance pvc-1cf4253a-8bf2-4aab-a2d9-470add26096f-r-cf298d0e starts running, IP <IP_ADDRESS>"
time="2020-08-27T08:37:15Z" level=debug msg="Instance pvc-1cf4253a-8bf2-4aab-a2d9-470add26096f-r-cf298d0e starts running, Port 10000"
time="2020-08-27T08:37:15Z" level=debug msg="Instance handler updated instance pvc-1cf4253a-8bf2-4aab-a2d9-470add26096f-r-cf298d0e state, old state stopped, new state running"
<IP_ADDRESS> - - [27/Aug/2020:08:37:16 +0000] "GET /v1/volumes/pvc-1cf4253a-8bf2-4aab-a2d9-470add26096f HTTP/1.1" 200 3387 "" "Go-http-client/1.1"
<IP_ADDRESS> - - [27/Aug/2020:08:37:18 +0000] "GET /v1/volumes/pvc-1cf4253a-8bf2-4aab-a2d9-470add26096f HTTP/1.1" 200 3434 "" "Go-http-client/1.1"
<IP_ADDRESS> - - [27/Aug/2020:08:37:20 +0000] "GET /v1/volumes/pvc-1cf4253a-8bf2-4aab-a2d9-470add26096f HTTP/1.1" 200 5101 "" "Go-http-client/1.1"
<IP_ADDRESS> - - [27/Aug/2020:08:37:20 +0000] "GET /v1/volumes/pvc-1cf4253a-8bf2-4aab-a2d9-470add26096f HTTP/1.1" 200 5101 "" "Go-http-client/1.1"
<IP_ADDRESS> - - [27/Aug/2020:08:37:20 +0000] "GET /v1/nodes/node01 HTTP/1.1" 200 1584 "" "Go-http-client/1.1"
<IP_ADDRESS> - - [27/Aug/2020:08:37:22 +0000] "GET /v1/volumes/pvc-1cf4253a-8bf2-4aab-a2d9-470add26096f HTTP/1.1" 200 5101 "" "Go-http-client/1.1"

I think this issue is fixed already. cc @innobead @yasker


[Completion] Use statically-known size for completion ordering

We know the size of these arrays statically, there's no point calculating them at runtime.
Resolves rdar://119938834.

@swift-ci please test


Get rid of honeycomb errors in rails logs

Tired of seeing these in our error logs:
[2018-09-27T23:31:38] WARN  Rails : No write key defined! (Check your config's writekey value in config/initializers/honeycomb.rb) No events will be sent to Honeycomb.

abandoning this for now


Missing Response headers

Originally reported on Google Code with ID 105
What steps will reproduce the problem?
1. Submit a rest request to any response sending back response headers

What is the expected output? What do you see instead?
Only the HTTP status code + message are displayed when more response headers are passed
back.

On what operating system?
Win 7

Please provide any additional information below.

Reported by torcud on 2012-11-08 18:17:56

It was fixed when declarativeWebRequest support has been removed from the app


After upgrade to 1.18.0 Request to probe app failed

Is this the right place to submit this?

[X] This is not a security vulnerability or a crashing bug
[X] This is not a question about how to use Istio

Bug Description
Pods do not become ready after upgrading istio to 1.18.0
2023-06-15T12:15:15.006134Z	error	Request to probe app failed: Get "http://<IP_ADDRESS>:9090/health": dial tcp <IP_ADDRESS>:0-><IP_ADDRESS>:9090: connect: connection refused, original URL path = /app-health/marketplace/readyzapp URL path = /health
Version
istioctl version
client version: 1.17.2
control plane version: 1.18.0
data plane version: 1.17.2 (32 proxies), 1.18.0 (5 proxies)

kubectl version --short
Client Version: v1.27.2
Kustomize Version: v5.0.1
Server Version: v1.26.3

Additional Information
only the workloads running 1.18.0 proxies are failing
helm chart values for istiod:
global:
  proxy:
    holdApplicationUntilProxyStarts: true
    resources:
      requests:
        cpu: 1m
        memory: 128Mi
      limits:
        cpu: 2000m
        memory: 1Gi
# meshConfig:
#   outboundTrafficPolicy:
#     mode: REGISTRY_ONLY
pilot:
  autoscaleEnabled: false
  replicaCount: 2

downgrading istio to 1.17.3 resovles the issue
Affected product area

[ ] Ambient
[ ] Docs
[ ] Installation
[X] Networking
[ ] Performance and Scalability
[ ] Extensions and Telemetry
[ ] Security
[ ] Test and Release
[ ] User Experience
[ ] Developer Infrastructure
[ ] Upgrade
[ ] Multi Cluster
[ ] Virtual Machine
[ ] Control Plane Revisions

So <IP_ADDRESS>:9090 should be your pod ip and probe. if you execinto the proxy and do curl <IP_ADDRESS>:9090 does it work?
We did make a few changes in this area:

https://github.com/istio/istio/pull/43021/files#diff-f4a8d4cea1f2df10aac7cba701184f7af5f7a5e78b19c41b0c44b8204093b523R35
https://github.com/istio/istio/pull/44297

Can you give us a bit more info on your environment? Node OS and version, k8s platform, etc?
Does this happen for this one app or all of them? If just one, can you give us more info about it?

So <IP_ADDRESS>:9090 should be your pod ip and probe. if you execinto the proxy and do curl <IP_ADDRESS>:9090 does it work?
I will post the result once I am able to test it, for now I have tried to port-forward to the pod 9090 and verify that /health endpoint was working.
We did make a few changes in this area:

https://github.com/istio/istio/pull/43021/files#diff-f4a8d4cea1f2df10aac7cba701184f7af5f7a5e78b19c41b0c44b8204093b523R35
kube-probe: avoid duplicate probe headers #44297

Can you give us a bit more info on your environment? Node OS and version, k8s platform, etc?
Does this happen for this one app or all of them? If just one, can you give us more info about it?
I've tested with couple of pods in different namespaces, both exhibited this behavior.
K8s platform is AKS, I will add the rest of the info later on.

Thanks. More details on the AKS aspect may help. I talked with someone who has run 1.18 on AKS without issues but could be a certain configuration, etc. Given its happening on different pods it seems likely an environmental issue

I am having a similar issue of probes failing. The application is configured to have the probes on a different port:
          ports:
            - name: http2
              containerPort: 8080
              protocol: TCP
            - name: http-diag
              containerPort: 3434
              protocol: TCP

          livenessProbe:
            httpGet:
              path: /healthz
              port: http-diag
              scheme: HTTP

With Istio 1.17.2, application logs this for health checks:
Request finished HTTP/1.1 GET http://<IP_ADDRESS>:3434/healthz - - - 200 - text/plain 0.3456ms

With Istio 1.18, this is logged (note that the port is not the expected one):
Request finished HTTP/1.1 GET http://<IP_ADDRESS>:15020/healthz - - - 404 0 - 0.2376ms

It's an ASP.NET Core application, with health checks configured as:
app.MapHealthChecks("/healthz").RequireHost("*:3434");

This check is failing after the upgrade as it looks at the request URL.

So <IP_ADDRESS>:9090 should be your pod ip and probe. if you execinto the proxy and do curl <IP_ADDRESS>:9090 does it work?

It did work:

istio-proxy@marketplace-66c6c5bf84-mdqqc:/$ curl http://<IP_ADDRESS>:9090/health
{"status":"Healthy","totalDuration":"00:00:00.0008780","entries":{}}

corresponding logs:

Can you give us a bit more info on your environment? Node OS and version, k8s platform, etc?

AKS 1.26.3,
Node OS:

PRETTY_NAME="Debian GNU/Linux 11 (bullseye)"
NAME="Debian GNU/Linux"
VERSION_ID="11"
VERSION="11 (bullseye)"
VERSION_CODENAME=bullseye
ID=debian

https://github.com/istio/istio/pull/44297 probably changes the host processing. Before we override the port and now we don't?
To verify can you try curl <IP_ADDRESS>:9090 -H "Host: <IP_ADDRESS>:15020?
I think for https://github.com/istio/istio/issues/45482#issuecomment-1598143650 case this is almost certainly the cause but would be good to double check these are the same issue

To verify can you try curl <IP_ADDRESS>:9090 -H "Host: <IP_ADDRESS>:15020?

istio-proxy@marketplace-66c6c5bf84-8r8ms:/$ curl http://<IP_ADDRESS>:9090/health
{"status":"Healthy","totalDuration":"00:00:00.0000071","entries":{}}
istio-proxy@marketplace-66c6c5bf84-8r8ms:/$ curl -I http://<IP_ADDRESS>:9090/health -H "Host: <IP_ADDRESS>:15020"
HTTP/1.1 404 Not Found
date: Wed, 21 Jun 2023 05:19:21 GMT
server: istio-envoy
x-envoy-upstream-service-time: 0
x-envoy-decorator-operation: :0/*
transfer-encoding: chunked

#44297 probably changes the host processing. Before we override the port and now we don't?
To verify can you try curl <IP_ADDRESS>:9090 -H "Host: <IP_ADDRESS>:15020?
I think for #45482 (comment) case this is almost certainly the cause but would be good to double check these are the same issue

Would you have expected this command to succeed prior to the changes in https://github.com/istio/istio/pull/44297? Trying to understand the thought process here.
I am trying to make the fix here and I want to make sure I understand what makes the scenario captured in this issue unique and why it wasn't caught in the unit tests.

I think before the app got 9090 as the Host header port, and now it gets
15020. I could be mistaken though
On Mon, Jun 26, 2023 at 3:48 PM Jackie Elliott @.***>
wrote:

#44297 https://github.com/istio/istio/pull/44297 probably changes the
host processing. Before we override the port and now we don't?
To verify can you try curl <IP_ADDRESS>:9090 -H "Host:
<IP_ADDRESS>:15020?
I think for #45482 (comment)
https://github.com/istio/istio/issues/45482#issuecomment-1598143650
case this is almost certainly the cause but would be good to double check
these are the same issue
Would you have expected this command to succeed prior to the changes in
#44297 https://github.com/istio/istio/pull/44297? Trying to understand
the thought process here.
I am trying to make the fix here
https://github.com/istio/istio/pull/45632 and I want to make sure I
understand what makes the scenario captured in this issue unique and why it
wasn't caught in the unit tests.
—
Reply to this email directly, view it on GitHub
https://github.com/istio/istio/issues/45482#issuecomment-1608421666, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AAEYGXNTC6IIQPVCHBVRT53XNIGTNANCNFSM6AAAAAAZH22JD4
.
You are receiving this because you commented.Message ID:
@.***>

Gotcha, that makes sense. I think we're currently overriding the host of the new app request with the host of Kubelet's request to the istio-agent status server https://github.com/istio/istio/pull/44297/files#diff-8a331529c387b787b4d84fab3273afb6ce52355c663f4dee58aad15a1e832c18R710. In this case, the host of Kubelet's request would be the : 15020, and the host of the app request would be set to the same. If the host header is set on either request (which it isn't in this issue) I would expect this to override the host.
I am not sure why the application in the unit test accepts the requests at port 15020.

I think before the app got 9090 as the Host header port, and now it gets 15020. I could be mistaken though

If the app does not care about the host, then consued why there is connection refused error met

2023-06-15T12:15:15.006134Z error Request to probe app failed: Get "http://<IP_ADDRESS>:9090/health": dial tcp <IP_ADDRESS>:0-><IP_ADDRESS>:9090: connect: connection refused, original URL path = /app-health/marketplace/readyzapp URL path = /health

The issue is the app DOES care about the Host
On Mon, Jun 26, 2023 at 8:47 PM Zhonghu Xu @.***> wrote:

I think before the app got 9090 as the Host header port, and now it gets
15020. I could be mistaken though
If the app does not care about the host, then consued why there is
connection refused error met
2023-06-15T12:15:15.006134Z error Request to probe app failed: Get "
http://<IP_ADDRESS>:9090/health": dial tcp <IP_ADDRESS>:0->
<IP_ADDRESS>:9090: connect: connection refused, original URL path =
/app-health/marketplace/readyzapp URL path = /health
—
Reply to this email directly, view it on GitHub
https://github.com/istio/istio/issues/45482#issuecomment-1608743035, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AAEYGXJFCEKUCRKW564KJHDXNJJUJANCNFSM6AAAAAAZH22JD4
.
You are receiving this because you commented.Message ID:
@.***>

Not sure why "connection refused" though
On Tue, Jun 27, 2023 at 7:02 AM John Howard @.***> wrote:

The issue is the app DOES care about the Host
On Mon, Jun 26, 2023 at 8:47 PM Zhonghu Xu @.***>
wrote:

I think before the app got 9090 as the Host header port, and now it gets
15020. I could be mistaken though
If the app does not care about the host, then consued why there is
connection refused error met
2023-06-15T12:15:15.006134Z error Request to probe app failed: Get "
http://<IP_ADDRESS>:9090/health": dial tcp <IP_ADDRESS>:0->
<IP_ADDRESS>:9090: connect: connection refused, original URL path =
/app-health/marketplace/readyzapp URL path = /health
—
Reply to this email directly, view it on GitHub
https://github.com/istio/istio/issues/45482#issuecomment-1608743035,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAEYGXJFCEKUCRKW564KJHDXNJJUJANCNFSM6AAAAAAZH22JD4
.
You are receiving this because you commented.Message ID:
@.***>

I have not been able to reproduce this error on a kind cluster. I have tried testing on a fresh v1.18.0 installation and a v1.17.2 installation that I upgrade to v1.18.0. I modified the pilot/cmd/pilot-agent/status/server.go to add more logging and the host value for the request is overwritten to port 15020 and the url remains the same as prior to the changes in https://github.com/istio/istio/pull/44297, but the host value does not take precedence over the host in the URL. Does the app explicitly have to care about the host over the url or is this dependent on the protocol?
Next, I will test in an AKS cluster.

To reproduce you can run something like this:
apiVersion: apps/v1
kind: Deployment
metadata:
  name: echo
spec:
  selector:
    matchLabels:
      app: echo
  template:
    metadata:
      labels:
        app: echo
    spec:
      containers:
      - args:
        - --tcp=9090
        - --tcp=9091
        - --server-first=9091
        - --port=80
        - --grpc=7070
        - --port=443
        - --tls=443
        - --crt=/cert.crt
        - --key=/cert.key
        env:
        - name: INSTANCE_IP
          valueFrom:
            fieldRef:
              apiVersion: v1
              fieldPath: status.podIP
        image: gcr.io/istio-testing/app:latest
        imagePullPolicy: IfNotPresent
        name: echo
        readinessProbe:
          httpGet:
            path: /healthz
            port: 80
            scheme: HTTP

It won't actually fail but you can see it log the host header so it should
be close enough.
I used that to test your PR and it looks correct now
On Fri, Jun 30, 2023 at 4:34 PM Jackie Elliott @.***>
wrote:

I have not been able to reproduce this error on a kind cluster. I have
tried testing on a fresh v1.18.0 installation and a v1.17.2 installation
that I upgrade to v1.18.0. I modified the
pilot/cmd/pilot-agent/status/server.go to add more logging and the host
value for the request is overwritten to port 15020 and the url remains the
same as prior to the changes in #44297
https://github.com/istio/istio/pull/44297, but the host value does not
take precedence over the host in the URL. Does the app explicitly have to
care about the host over the url or is this dependent on the protocol?
Next, I will test in an AKS cluster.
—
Reply to this email directly, view it on GitHub
https://github.com/istio/istio/issues/45482#issuecomment-1615276126, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AAEYGXKXMRBIAU43UTS6YEDXN5O7VANCNFSM6AAAAAAZH22JD4
.
You are receiving this because you commented.Message ID:
@.***>


fix: result of npm audit fix

:tada: This PR is included in version 2.0.1 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


URGENT: Fixed iso and version issues

It looks like docker-machine recently changed their iso naming convention from boot2docker.iso to boot2docker-virtualbox.iso https://github.com/docker/machine/blob/master/drivers/virtualbox/virtualbox.go#L28
Furthermore the actual iso content versioning no-longer identifies itself as Boot2Docker-v1.766 as it previously did, but rather contains docker version information, such as Docker v1.7.1
This patch changes the iso filename and version check accordingly - Furthermore the code was made a bit more flexible by passing the machine name to the methods, with an ES6 default of the machine name returned by the name() method.
Signed-off-by: FrenchBen<EMAIL_ADDRESS>

Merging, thanks!


Shallow (Closer Than the Angels) by Digital Summer unsupported.

Check if issue with swaglyrics or whether song lyrics unavailable on Genius.

stripper -> Digital-Summer-Shallow

added


Fix/tx build UI: Fix the break UI change on the transaction builder page

##Issue
https://github.com/stellar/laboratory/issues/710
Description
Fix the break UI change on the transaction builder page. When filling in the inputs error title or success title changes conditionally breaking the transaction builder page and the user was unable to process further their transaction through UI. I was trying to execute changeTrust operation specifically where I found that bug.
Changes Made
In TxBuilderResult.js, wrapped the successTitle and errorTitle headings in the parent div, these lines were causing an error when the success heading or error heading appears conditionally.
Checklist

[*] I have tested my changes manually and they work as intended.
[*] I have mentioned the reviewers using the GitHub reviewer assignment feature and/or "@username" mentions in the description/comments.

Screenshots (if applicable)

This should be fixed in Lab v2 https://lab.stellar.org/


Inherit config from RIPGREP_CONFIG_PATH

Thanks for making repgrep, it is very capable and intuitive!
Ripgrep allows default settings to be stored in a configuration file, identified by an env. var named RIPGREP_CONFIG_PATH.
For example, I have the following in my ripgrep config file:
# Search hidden files and directories.
--hidden

# Follow symbolic links.
--follow

# Exclude directories.
--glob=!{.git}

# Sort by file path.
--sort=path

These settings don't seem to be picked up by repgrep. Would it take much for repgrep to recognize this config file?

This is definitely something I've considered doing (I even left a few comments in the code about it...).
But it's a little tricky with the APIs that clap provides. I'll have another crack at this when I get the chance.

Here's a great commit from ripgrep about its command line parsing: https://github.com/BurntSushi/ripgrep/commit/082245dadb3854238e62b91aa95a46018cf16ef1... Might take inspiration from that when I look into this more.

Initial branch here: https://github.com/acheronfail/repgrep/commit/fae11bc85a789513a6ad61bc3cc8479f4a5adeb1

Currently merged to next. Feel free to test this out. Still missing a few things before I'll make a release though!

Thanks for your attention and work on this issue. I later saw the comment in the code next to the explicit flag --no-config.
TBH, I was surprised to see the explicit disabling of the config file, and the fact that it requires any work from you to support it. My thinking is that ripgrep just picks it up and uses it, and since you're wrapping around ripgrep, repgrep shouldn't even need to peek into the config file.
After reading this -- https://github.com/acheronfail/repgrep/pull/99#issuecomment-1858768461 -- I see now that repgrep needs to intercept some command-line flags, like --pattern or --encoding.
As a user, I hope that repgrep provides as thin of a wrapper around ripgrep as possible, both to allow for native capability like respecting RIPGREP_CONFIG_PATH, and also to not disrupt/interfere with any native functionality (like the risk of repgrep parsing command-line flags differently than ripgrep would). That and it eases the development burden (less code is more maintainable code).
I read through the in-program help and saw explicit mentions of --no-config and support of RGR_JSON_FILE. After reading that, I threw this into my shell profile:
rgi() {
    TMPFILE=$(mktemp) && rg "$@" --json > $TMPFILE && RGR_JSON_FILE=$TMPFILE rgr
}

This seems to accomplish my goals of relying on native ripgrep as much as possible, and relying on repgrep solely for the interactive replacement UI (which I love, TYSM :star_struck:). While empowering, I understand this approach does not prevent me (the user) from shooting myself in the foot with unsupported flags (--binary, --files, etc.).
As a user with basic needs (replacing strings throughout utf-8 encoded text files), I'm undecided as to whether it is better to use this shell function vs. rely directly on repgrep. Am I losing out on any significant functionality with this little shell function?

As a user with basic needs (replacing strings throughout utf-8 encoded text files), I'm undecided as to whether it is better to use this shell function vs. rely directly on repgrep. Am I losing out on any significant functionality with this little shell function?

Only downsides of that approach are:

possibly printing terminal characters with --binary (as you've mentioned)
potential issues when using --fixed-strings (as I haven't tested it yet - rgr currently assumes all patterns are regular expressions, but --fixed-strings makes them substring searches)

Sounds like your rgi() {...] shell function will suit your needs perfectly.
As an aside though, I've taken this opportunity to make rgr an even thinner wrapper (before it was more opinionated) so once I do some tests and any minor changes for --fixed-strings I'll release 0.15 which should also work for your use-case. Either way, use your rgi or the next version, the choice is yours! 🙂

Ok, good to know, and I appreciate you sharing that insight. I do use capture-groups. I'll give the next version a go; thank you!

Should be fixed in 0.15


Completion of error handling

Would you like to add more error handling for return values from functions like the following?

printf ⇒ ratbag_cmd_list_supported_devices
strdup ⇒ ratbag_device_new

sprintf - yes please, printf doesn't need to
strdup - I think we should just make a wrapper that aborts if strdup fails, similar to zalloc. there is not much value in handling OOM

Are there a few update candidates left over?
How do you think about to annotate any functions with "__attribute__((warn_unused_result))"?

do we have functions where we need to warn about this? That's generally one of the flags I disable from the warning flags, too many false positives.


Add some colors to Sat and Sun

Let's change the colors of Saturday and Sunday on the calendar to #E0835D (orange). It will make it easier for the users to differentiate the weekend from the rest of the week.

Hi, I would like to handle this issue, can it be assigned to me, or is further discussion needed?

Hi, I would like to handle this issue, can it be assigned to me, or is further discussion needed?

Hi Ron! Cool! You are assigned.

Thanks!


Printers don't work inside container

Windows version: 10.0.19044 Build 19044
Docker version: 20.10.8
Container: mcr.microsoft.com/windows:1809, mcr.microsoft.com/windows:1903, mcr.microsoft.com/windows:20H2
Hyper-V enabled: yes
Repro steps:
Run simple printing script:
$sourcetxtfile = 'c:\1.txt'
$destPDFfile = 'c:\1.pdf'
Add-Type -AssemblyName System.Drawing
$txtToPDF = New-Object System.Drawing.Printing.PrintDocument
$txtToPDF.DocumentName = $sourcetxtfile
$txtToPDF.PrinterSettings = New-Object System.Drawing.Printing.PrinterSettings
$txtToPDF.PrinterSettings.PrinterName = 'Microsoft Print to PDF'
$txtToPDF.PrinterSettings.PrintToFile = $true
$txtToPDF.PrinterSettings.PrintFileName = $destPDFfile
$txtToPDF.Print()
Setup
Create file 1.txt on C:
docker run -it -v c:\:c:\ mcr.microsoft.com/windows:1809 powershell
run script
Get-WinEvent -FilterHashTable @{ LogName = "Microsoft-Windows-PrintService/Admin"; }
Actual result:
Exception calling "Print" with "0" argument(s): "Settings to access printer 'Microsoft Print to PDF' are not valid."
There are also some events:
370 Error            The print spooler failed to regenerate the printer driver information for driver Microsoft enhanced Point and Print compatibility driver for environment Windows x64. Win32 system error code 87 (0x57). This can occur after an operating system upgrade or because of data loss on the hard drive.
12/17/2021 1:59:48 PM          215 Error            Installing printer driver Microsoft enhanced Point and Print compatibility driver failed, error code 0x490, HRESULT 0x80070057. See the event user data for context information.

@arst Have you tried the following steps: https://docs.microsoft.com/en-us/virtualization/windowscontainers/deploy-containers/print-spooler
Let me know if this works for you!

@judyliu-ms Yes, I've tried top stop/start host spooler, reboot host machine, unfortunately, nothing helped.
I think that this is the same problem that was described here: https://github.com/moby/moby/issues/37124.

transferring to @msjingli who has been looking into print-related support for Windows containers.

@arst It looks like when the host is patched with an earlier CU than the binaries within the container base image. Can you please double check if your host has the latest patch? Thanks.

@arst I am going to close this issue for now. Please feel free to activate it if you see it again. Thanks!


Fixes 4013,4008: Use custom lecho for enhanced logging

Summary
This uses a custom lecho fork to accomplish two things:

log slow requests at a higher log level

do not treat non-500 errors as needing error level logging

was kinda tricky.  We need another middleware that runs around lecho to properly parse the error into the correct struct, extract the correct status, and set that on the response.  Then lecho has to re-lookup the response to get the proper status code.  I will work on contributing 1. back to lecho, but i'm not sure if the changes for 2 make sense to?

Testing steps
to test 1:
add in a time.sleep(2*time.Second)  somewhere in a handler (like listRepositories).  Watch requests get logged at warn
to test 2:
in listRepositories add some code after the filter is parsed:
 if filterData.Search == "foo" {
         return ce.NewErrorResponse(500, "Error listing repositories", "ISE")
 }

now you can make requests to:
GET http://localhost:8000/api/content-sources/v1.0/repositories/?search=foo

to trigger an ISE.  You can try to create the same repo 2x to trigger a 400.  ISEs should still be logged at error level, but 400s should be logged at Info like normal.
Checklist

[ ] Tested with snapshotting feature disabled and pulp server URL not configured if appropriate

custom lecho PR: https://github.com/content-services/lecho/pull/1/files

https://issues.redhat.com/browse/HMS-4013

https://issues.redhat.com/browse/HMS-4008

/retest

Error: undefined: lecho (typecheck)

testing 1 looks good, seeing slow requests get logged as warn: 2:26PM WRN ../lecho/middleware.go:171 > bytes_in=0 bytes_out=894 host=localhost:8000 latency=2017.993208 latency_human=2.017993208s method=GET referer= remote_ip=::1 request_id=OxeJrkomMgWkoHffKhCvzlIBaMqPfEIw status=200 uri=/api/content-sources/v1.0/repositories/ user_agent=PostmanRuntime/7.37.3
testing 2 looks good too, <500 errors logged as info: 2:32PM INF ../lecho/middleware.go:171 > error="error: code=400, title=Error creating repository, detail=Repository with this name already belongs to organization \n" bytes_in=227 bytes_out=0 host=localhost:8000 latency=5.938958 latency_human=5.938958ms method=POST referer= remote_ip=::1 request_id=qpSQNnmMxgiaGLKJOEAIDHQxxFnmiyym status=200 uri=/api/content-sources/v1.0/repositories/ user_agent=PostmanRuntime/7.37.3


Add token verification to LED sign API

basically #442 but in api/peripheral_api/routes/LedSign.js. we don't check tokens atm meaning anyone who knows curl or Postman can write whatever they want to our LED sign.

are we able to use a JSON web token for this?

and verify

Yes, that's what we are using for verification. The logic behind JWT verification for the peripheral server was implemented in PR #1027
Refer to this: https://github.com/SCE-Development/Core-v4/commit/c04343c5da063113e13ebb34ef52c2a48a3f81da


Update docs & new hooks on hotfix

Short Description and Why It's Useful

Update docs & new hooks on hotfix
Before merge, wait for: https://github.com/DivanteLtd/vue-storefront/pull/5149

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you all sign our Contributor License Agreement before we can accept your contribution.3 out of 4 committers have signed the CLA.:white_check_mark: gibkigonzo:white_check_mark: filrak:white_check_mark: Fifciu:x: hesselbergYou have signed the CLA already but the status is still pending? Let us recheck it.


add dm ghpr test

add dm it and ut test

LGTM

/hold

@zhouqiang-cl  this pr is ready.

this pr is ready~

how about update go version to 1.16, so we could fix https://github.com/pingcap/dm/pull/1698

how about updating go version to 1.16 in this PR, so we could fix pingcap/dm#1698

sounds great , i will update ci go envrionment to go.1.16 after pingcap/dm#1698 closed
/hold


register problem

when i register an account , it disappears "Your email does not match any existing open organization", this is my settings.py and i set email_password in zulip-secrets.conf:
EXTERNAL_HOST = '<IP_ADDRESS>'
ZULIP_ADMINISTRATOR =<EMAIL_ADDRESS>ADMIN_DOMAIN = 'bubi.cn'
AUTHENTICATION_BACKENDS = (
'zproject.backends.EmailAuthBackend', # Email and password
)
SSO_APPEND_DOMAIN = None
EMAIL_HOST = 'smtp.gmail.com'
EMAIL_HOST_USER =<EMAIL_ADDRESS>EMAIL_PORT = 587
EMAIL_USE_TLS = True
DEFAULT_FROM_EMAIL = "Zulip<EMAIL_ADDRESS>NOREPLY_EMAIL_ADDRESS =<EMAIL_ADDRESS>

Are you trying to sign up for an account in the @bubi.cn domain?  If not, you should follow the instructions in this email:
https://groups.google.com/d/msg/zulip-devel/M2y5O_11gcg/vYpBBv-qBQAJ

@timabbott now i sign up for the bubi.cn successfully，i want to change the ADMIN_REALM，so i follow the instructions you gave:
cd /home/zulip/deployments/current
./manage.py shell
from zerver.models import *
r = get_realm(settings.ADMIN_DOMAIN)
r.restricted_to_domain=False # Now anyone anywhere can login
r.save() # save to the database
and i restart the zulip , when i register for @gmail.com account, it does not work！it appears:Your e-mail does not match any existing open organization. Use a different e-mail address.

As currently implemented, that will allow any user to sign up, but if their email address's hostname doesn't match the realm's hostname or any of the realm aliases, they'll need to be invited.

@lightning-li I think the new Zulip 1.3.7 release fixes the issue you experienced; I recommend upgrading when you get a chance.

Hi. I've set ADMIN_REALM and ADMIN_DOMAIN to the same value and it won't go.

@grepwood can you give more detail on what problem you're experiencing?  How have you configured Zulip, and what error or traceback are you getting?

@timabbott I'm getting "not an open organization" error when I try to sign up. Here's the paste of the config http://pastebin.com/8pSGsi2N
Not getting any error traceback afaik

@grepwood there are a few possibilities:

You may need to set LDAP_APPEND_DOMAIN=ADMIN_DOMAIN if samaccountname on your LDAP server is a username, not an email address ending with @ADMIN_DOMAIN.
If you didn't set ADMIN_DOMAIN to match the domain name of your email addresses, you'll need to either set restricted_to_domain=False using the management command documented in README.prod or if you originally ADMIN_DOMAIN to one thing and then changed it, you may need to follow the procedure in README.prod to change it.


Quicksilver should check before deleting plugins within Quicksilver.app (core support)

When starting Quicksilver for the first time a  check should run before deleting plugins to make sure they are NOT in Quicksilver.app.

Great, thanks Guy :)
On 26 October 2011 08:35, Guid0mcman <
<EMAIL_ADDRESS>
When starting Quicksilver for the first time a  check should run before
deleting plugins to make sure they are NOT in Quicksilver.app.
--
Reply to this email directly or view it on GitHub:
https://github.com/quicksilver/Quicksilver/issues/529

You're welcome.
On 26 Oct 2011, at 08:37, Patrick Robertson wrote:

Great, thanks Guy :)
On 26 October 2011 08:35, Guid0mcman <
<EMAIL_ADDRESS>
When starting Quicksilver for the first time a  check should run before
deleting plugins to make sure they are NOT in Quicksilver.app.
--
Reply to this email directly or view it on GitHub:
https://github.com/quicksilver/Quicksilver/issues/529

--
Reply to this email directly or view it on GitHub:
https://github.com/quicksilver/Quicksilver/issues/529#issuecomment-2527540

This has been added to Quicksilver


Manager.init with NSURLSession: guard too strong?

In Manager.init:delegate:serverTrustPolicyManager:, why is it enforced that "The delegate of the URL session. Must equal the URL session's delegate.", i.e. why is the following line required?
guard delegate === session.delegate else { return nil }

My use case: I obtain an initialized NSURLSession from a security library (out of my control), which provides it own internal proxy object for NSURLSession.delegate, which checks and forwards NSURLSessionDelegate, NSURLSessionTaskDelegate, NSURLSessionDataDelegate and NSURLSessionDownloadDelegate calls.
To clarify, my initialization code looks something like this:
let delegate = Manager.SessionDelegate()
let session: NSURLSession = SecurityLib.initialize(sessionDelegate: delegate,
    taskDelegate: delegate, dataDelegate: delegate, downloadDelegate: delegate)
let manager = Manager(session: session, delegate: delegate)

The last line currently fails because session.delegate is a proxy object internal to SecurityLib (which forwards all delegate methods to our delegate). If I remove the guard line from Manager.swift things seem to work.

Because Alamofire use its SessionDelegate subclass to the real delegate work. It can provide block api of NSURLSessionDelegate(and its subclasses), and also provide a way to fallback to TaskDelegate, which is to each NSURLSessionTask and can provide a more specialized impementation.
If you insist using your delegate, you will lose a lot convenience of the library. I think you can try to make your delegate be a proxy of SessionDelegate by applying all callbacks to the blocks of SessionDelegate.
Hope this can help you.

The line is enforced for safety. It's to make sure you aren't trying to provide a SessionDelegate that isn't actually the delegate of the NSURLSession you're passing in. Otherwise, Alamofire won't really do much of anything for you.
Thanks for the answer @wizzardchao. You're spot on. In this particular use case @binkdotli, it's probably not worth trying to force your SecurityLib session and delegate into Alamofire. However, you could certainly still use parts of Alamofire to help build NSURLRequest objects such as ParameterEncoding and MultipartFormData.
Best of luck! 🍻

OK, thanks for taking the time to answer this.


fix: close float window when leave buffer

this is not correct. now it can works when you leave buffer.

this is not correct. now it can works when you leave buffer.

when you click buffers to switch them, the float window is not close.
https://user-images.githubusercontent.com/39482599/221352877-89b47e89-983c-49bc-913f-d3770ed96217.mov

use ++unfocus or use buffer  jump command bnext bprev . i don't use mouse.

the problem still shows up when adding ++unfocus.

is BufLeave event conflict with lspsaga's current settings? since you mentioned it is not correct.

if you used the unfocus if also append the BufLeave into it ?  if you don't use unfocus that mean you can jump into that window. it's useful to check diagnostic and jump to pos in show_line and show_buf diangostics. wincmd will also trigger BufLeave the event. please see code carefully i use bufenter instead of this.   if you want make a pr you need look code context.


Hotfix: pool creation add token bug

Description
See title
Type of change

[x] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] Dependency changes
[ ] Code refactor / cleanup
[ ] Documentation or wording changes
[ ] Other

How should this be tested?
Please provide instructions so we can test. Please also list any relevant details for your test configuration.

[ ] Try to add token in pool creation flow, there shouldn't be any errors in the console / display bugs

Visual context
Please provide any relevant visual context for UI changes or additions. This could be static screenshots or a loom screencast.
Checklist:

[ ] I have performed a self-review of my own code
[ ] I have requested at least 1 review (If the PR is significant enough, use best judgement here)
[ ] I have commented my code where relevant, particularly in hard-to-understand areas
[ ] If package-lock.json has changes, it was intentional.
[ ] The base of this PR is master if hotfix, develop if not

@garethfuller  I think something was changed in getToken function and it causing issues now. actually there is no sense in commenting that line as we don't need to show 'empty' tokens in pool summary chart

@alter-eggo locally I'm still getting vue warnings in the console about the schema:
ntime-core.esm-bundler.js:40 [Vue warn]: Component inside <Transition> renders non-element root node that cannot be animated.
  at <Create onVnodeUnmounted=fn<onVnodeUnmounted> ref=Ref< undefined > >
  at <BaseTransition appear=true persisted=false mode=undefined  ... >
  at <Transition appear="" name="appear" >
  at <RouterView key="/polygon/pool/create" >
  at <FocussedLayout>
  at <FocussedLayout>
  at <AsyncComponentWrapper>
  at <App>
  at <Anonymous>
  at <Anonymous>
  at <Root>
w


python311Packages.simpy: 4.0.1 -> 4.0.2

Automatic update generated by nixpkgs-update tools. This update was made based on information from passthru.updateScript.
meta.description for python311Packages.simpy is: Process-based discrete-event simulation framework based on standard Python
meta.homepage for python311Packages.simpy is: https://simpy.readthedocs.io/en/4.0.2/
Updates performed

Ran passthru.UpdateScript

To inspect upstream changes
Impact

Checks done (click to expand)

built on NixOS
The tests defined in passthru.tests, if any, passed
found 4.0.2 with grep in /nix/store/0kf6qwig14mymixfjaxmmav96vvrdb86-python3.11-simpy-4.0.2
found 4.0.2 in filename of file in /nix/store/0kf6qwig14mymixfjaxmmav96vvrdb86-python3.11-simpy-4.0.2

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

4 total rebuild path(s)

4 package rebuild(s)

First fifty rebuilds by attrpath
python310Packages.simpy
python310Packages.wsnsimpy
python311Packages.simpy
python311Packages.wsnsimpy

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/0kf6qwig14mymixfjaxmmav96vvrdb86-python3.11-simpy-4.0.2 \
  --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 python311Packages.simpy https://github.com/r-ryantm/nixpkgs/archive/770d4063177e38c8278517b7b2f0fa3ca2418955.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/0kf6qwig14mymixfjaxmmav96vvrdb86-python3.11-simpy-4.0.2
ls -la /nix/store/0kf6qwig14mymixfjaxmmav96vvrdb86-python3.11-simpy-4.0.2/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

1 package failed to build:

python311Packages.wsnsimpy

3 packages built:

python310Packages.simpy
python310Packages.wsnsimpy
python311Packages.simpy

Maintainer pings
cc @dmrauh @shlevy for testing.

last 10 log lines:
       > =========================== short test summary info ============================
       > FAILED docs/topical_guides/real-time-simulations.rst::real-time-simulations.rst
       > FAILED tests/test_rt.py::test_rt[0.1] - RuntimeError: Simulation too slow for real time (0.160s).
       > FAILED tests/test_rt.py::test_rt[0.05] - RuntimeError: Simulation too slow for real time (0.069s).
       > FAILED tests/test_rt.py::test_rt[0.15] - assert False
       > FAILED tests/test_rt.py::test_rt_multiple_call - RuntimeError: Simulation too slow for real time (0.083s).
       > FAILED tests/test_rt.py::test_rt_slow_sim_no_error - assert False
       > FAILED tests/test_rt.py::test_rt_sync - RuntimeError: Simulation too slow for real time (0.060s).
       > ========== 7 failed, 151 passed, 10 deselected, 11 warnings in 3.57s ===========
       > /nix/store/wc1y9miss7q2yk46rgjrfikx8r4r3fjz-stdenv-darwin/setup: line 1607: pop_var_context: head of shell_variables not a function context
       For full logs, run 'nix log /nix/store/scdwsb3g1lnj4dd4989kf3ywsg27xn7g-python3.11-simpy-4.0.2.drv'.

on darwin


Update Summary site as per template

Update the structure and files of the Summary site with the Asciidoctor Jet template.

Handled in commit 2cfd17ef919067220fc8dcf9425f85bfc64fd62d.


Binary Search in C++

Hi, I want to contribute in Hacktoberfest 2021.
Please assign me this task and also add label as Hacktoberfest-accepted.

Please assign it to me .

They are not considering dsa,cp,algorithm repository :(
all the pr will not be considered in hacktoberfest but your contribution will be for lifetime, this will help many students to practice dsa .
Thank you for your contribution :)
you can contribute to other repo


[borrow-operator] Add initial support for applying _borrow to self when calling a method.

Example: (_borrow f).callFunction()
This still does not support _borrow for get/set and more general accessors. That change will be coming in a forthcoming commit.
rdar://103888591

@swift-ci smoke test

@swift-ci smoke test macOS platform


Api

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

273 of 305 (89.51%)  changed or added relevant lines in 6 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage decreased (-0.5%) to 91.399%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

overflow/cadence.go
65
70
92.86%

overflow/argument.go
65
71
91.55%

overflow/transaction.go
122
143
85.31%

Totals

Change from base Build<PHONE_NUMBER>:
-0.5%

Covered Lines:
1881

Relevant Lines:
2058

💛  - Coveralls


The parameter is incorrect. ExitCode: 125

PLEASE DO NOT INCLUDE ANY PASSWORDS OR TOKENS IN YOUR ISSUE!!!
Describe the issue
Not sure if it connected to https://github.com/microsoft/navcontainerhelper/issues/2086 or if it is a different issue. But in trying to get the system up and running again, I've run into a different errormessage.  Thinking that it might be some refrence issue, I 've only added the imagename and now I am getting a parameter error.
Scripts used to create container and cause the issue
$containerName = 'lanitol'
$password = 'P@ssw0rd'
$securePassword = ConvertTo-SecureString -String $password -AsPlainText -Force
$credential = New-Object pscredential 'admin', $securePassword
$auth = 'UserPassword'
$artifactUrl = Get-BcArtifactUrl -type 'OnPrem' -version '18.2' -country 'dk' -select 'Latest'
$licenseFile = 'd:\nav\infar\udvikling\bc18.flf'
New-BcContainer `
    -accept_eula `
    -containerName $containerName `
    -credential $credential `
    -auth $auth `
    -artifactUrl $artifactUrl `
    -imageName 'bc18cu2' `
    -licenseFile $licenseFile `
    -updateHosts```

**Full output of scripts**

Default parameter Isolation = Process
BcContainerHelper is version 2.0.16
BcContainerHelper is running as administrator
Host is Microsoft Windows 10 Pro - 21H1
Docker Client Version is 20.10.8
Docker Server Version is 20.10.8
Removing lanitol from container hosts file
Removing lanitol-* from container hosts file
Removing D:\NAVData\ContainerHelper\Host\Extensions\lanitol
Fetching all docker images
Fetching all docker volumes
ArtifactUrl and ImageName specified
INFO: Windows 10 21H1 images are not yet available, using 2004 as these are found to work better than 20H2 on 2
1H1
WARNING: Unable to find matching generic image for your host OS. Using mcr.microsoft.com/businesscentral:10.0.1
9041.1237
Fetching all docker images
Building image bc18cu2:onprem-18.2.26217.26490-dk based on mcr.microsoft.com/businesscentral:10.0.19041.1237 wi
th https://bcartifacts.azureedge.net/onprem/18.2.26217.26490/dk
Pulling latest image mcr.microsoft.com/businesscentral:10.0.19041.1237
10.0.19041.1237: Pulling from businesscentral
295f12394c4f: Already exists
5910daff7c6f: Pulling fs layer
b34642b347fc: Pulling fs layer
.
.
.
0eebdf174f77: Pull complete
2b961c4525d9: Pull complete
20be9a8c82d4: Pull complete
Digest: sha256:16a380c3a0a014f941a4a055f035c06f17674f8388121632f80920d0f78154dc
Status: Downloaded newer image for mcr.microsoft.com/businesscentral:10.0.19041.1237
mcr.microsoft.com/businesscentral:10.0.19041.1237
Generic Tag: <IP_ADDRESS>
Container OS Version: 10.0.19041.1237 (2004)
Host OS Version: 10.0.19043.1237 (21H1)
Using Process isolation
Using license file d:\nav\infar\udvikling\bc18.flf
Files in D:\NAVData\Artifacts\xur5sljr.vu3\my:
Copying Platform Artifacts
Copying Database
Copying Licensefile
Copying ConfigurationPackages
Copying Applications
D:\NAVData\Artifacts\xur5sljr.vu3
Sending build context to Docker daemon  1.665GB
Step 1/6 : FROM mcr.microsoft.com/businesscentral:10.0.19041.1237
---> 7f58d7f88574
Step 2/6 : ENV DatabaseServer=localhost DatabaseInstance=SQLEXPRESS DatabaseName=CRONUS IsBcSandbox=N artifactU
rl=https://bcartifacts.azureedge.net/onprem/18.2.26217.26490/dk filesOnly=False
---> Running in ab0a56cfe7be
Removing intermediate container ab0a56cfe7be
---> b40ecfc7d2b8
Step 3/6 : COPY my /run/
---> 74b03eed4e87
Step 4/6 : COPY NAVDVD /NAVDVD/
---> 0e4f65328ba2
Step 5/6 : RUN \Run\start.ps1 -installOnly
---> Running in 5891187b6859
Using installer from C:\Run\150-new
Installing Business Central
Installing from DVD
Starting Local SQL Server
WARNING: Waiting for service 'SQL Server (SQLEXPRESS) (MSSQL$SQLEXPRESS)' to
start...
WARNING: Waiting for service 'SQL Server (SQLEXPRESS) (MSSQL$SQLEXPRESS)' to
start...
Starting Internet Information Server
Copying Service Tier Files
C:\NAVDVD\ServiceTier\Program Files
C:\NAVDVD\ServiceTier\System64Folder
Copying PowerShell Scripts
C:\NAVDVD\WindowsPowerShellScripts\Cloud\NAVAdministration
C:\NAVDVD\WindowsPowerShellScripts\WebSearch
Copying dependencies
Copying ReportBuilder
Importing PowerShell Modules
Determining Database Collation
Changing Database Server Collation to Danish_Greenlandic_100_CI_AS
Restoring CRONUS Demo Database
Setting CompatibilityLevel for CRONUS on localhost\SQLEXPRESS
Modifying Business Central Service Tier Config File for Docker
Creating Business Central Service Tier
Installing SIP crypto provider: 'C:\Windows\System32\NavSip.dll'
Copying Web Client Files
C:\NAVDVD\WebClient\Microsoft Dynamics NAV
Copying Client Files
C:\NAVDVD\LegacyDlls\program files\Microsoft Dynamics NAV
C:\NAVDVD\LegacyDlls\program files\Microsoft Dynamics NAV
C:\NAVDVD\LegacyDlls\systemFolder
Copying ModernDev Files
C:\NAVDVD
C:\NAVDVD\ModernDev\program files\Microsoft Dynamics NAV
Copying additional files
Copying ConfigurationPackages
C:\NAVDVD\ConfigurationPackages
Copying Test Assemblies
C:\NAVDVD\Test Assemblies
Copying Applications
C:\NAVDVD\Applications
Starting Business Central Service Tier
Importing CRONUS license file
Stopping Business Central Service Tier
Installation took 196 seconds
Installation complete
Removing intermediate container 5891187b6859
---> f89b70ac60c7
Step 6/6 : LABEL legal="http://go.microsoft.com/fwlink/?LinkId=837447"       created="202110031823"       nav="
"       cu=""       country="dk"       version="18.2.26217.26490"       platform="18.0.26213.26464"
---> Running in 9af66d7eed4b
Removing intermediate container 9af66d7eed4b
---> a675e7d9313c
Successfully built a675e7d9313c
Successfully tagged bc18cu2:onprem-18.2.26217.26490-dk
Building image took 978 seconds
Using image bc18cu2:onprem-18.2.26217.26490-dk
Creating Container lanitol
Style: onprem
Multitenant: No
Version: 18.2.26217.26490
Platform: 18.0.26213.26464
Generic Tag: <IP_ADDRESS>
Container OS Version: 10.0.19041.1237 (2004)
Host OS Version: 10.0.19043.1237 (21H1)
Using Process isolation
Using locale da-DK
Disabling the standard eventlog dump to container log every 2 seconds (use -dumpEventLog to enable)
Using license file d:\nav\infar\udvikling\bc18.flf
Files in D:\NAVData\ContainerHelper\Host\Extensions\lanitol\my:

AdditionalOutput.ps1
license.flf
MainLoop.ps1
SetupVariables.ps1
updatehosts.ps1
Creating container lanitol from image bc18cu2:onprem-18.2.26217.26490-dk
eacc644fae9fc4ecd579a582110f9e36044e29abcdc84fcaeb6468b2acabee7c
DockerDo : docker: Error response from daemon: hcsshim::CreateComputeSystem
eacc644fae9fc4ecd579a582110f9e36044e29abcdc84fcaeb6468b2acabee7c: The parameter is incorrect.
ExitCode: 125
Commandline: docker run --env licenseFile="c:\run\my\license.flf" --name lanitol --hostname lanitol --env
auth=NavUserPassword --env username="admin" --env ExitOnError=N --env locale=da-DK --env databaseServer=""
--env databaseInstance="" --volume "D:\NAVData\ContainerHelper\Host:D:\NAVData\ContainerHelper\Container"
--volume "D:\NAVData\ContainerHelper\Host\Extensions\lanitol\my:C:\Run\my" --isolation Process --restart
unless-stopped --env filesOnly=False --env enableApiServices=Y --env useSSL=N --volume
"c:\windows\system32\drivers\etc:C:\driversetc" --env securePassword=76492d1116743f0423413b16050a5345MgB8AGYAc
wBUADgAOABrAEwAZQB2AFkATABKADEAdgBsAE0ATwBXADgAbAAxAHcAPQA9AHwAMABiAGMANAAzADkAMQBiADQAOABmADIANAAzADAAOABhADg
ANQAwAGYAMABiAGUAOQBjAGMANQBiADQAMgBlADcANAA5ADQANQBjADMAMgBhADAAYQAxAGYAOAAxADkAMQBiADIANgA1ADAANwBjADYAZgA3A
DkANwBlADkAYwA= --env passwordKeyFile="c:\run\my\aes.key" --env removePasswordKeyFile=Y --env accept_eula=Y
--env accept_outdated=Y --detach bc18cu2:onprem-18.2.26217.26490-dk
At C:\Program
Files\WindowsPowerShell\Modules\BcContainerHelper\2.0.16\ContainerHandling\New-NavContainer.ps1:1757 char:15

...       if (!(DockerDo -accept_eula -accept_outdated:$accept_outdated - ...

            ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

CategoryInfo          : NotSpecified: (:) [Write-Error], WriteErrorException
FullyQualifiedErrorId : Microsoft.PowerShell.Commands.WriteErrorException,DockerDo...

**Additional context**
- does it happen all the time? Tried a few versions, and they all fail.

What is the content of c:\programdata\bccontainerhelper\bccontainerhelper.config.json ?

What is the content of c:\programdata\bccontainerhelper\bccontainerhelper.config.json ?
BcContainerHelper.config.json
{
"TelemetryConnectionString":  "",
"defaultNewContainerParameters":  {
"Credential":  {
"Password":  "01000000d08c9ddf0115d1118c7a00c04fc297eb01000000477e67b63d74a24e856457240ad8bf7a00000000020000000000106600000001000020000000658b0700d7bccf1fcf72d05600b9b14daf20617a71b5f826fbb3b689b02200f1000000000e8000000002000020000000d1b491ee6e00f90fdd234b23ba840a4d5068ccbb79b6d18a5c6266cec5ac0a6c200000006bcdf721f1a43202cb19a40939194d3d6dfcdb7fbd3764d1e4d4cad06580286a40000000f5fed33edf7a238a966697c2044edcee31019ded2d93cf6dd87d514d12ac11a84173760451b03de5b4479beb830fef7c13a1732d346bc148c821ebf9b8c57767",
"Username":  "admin"
},
"Accept_Eula":  true,
"Isolation":  "Process",
"UpdateHosts":  true,
"Auth":  "UserPassword"
},
"DOCKER_SCAN_SUGGEST":  false,
"sandboxContainersAreMultitenantByDefault":  true,
"containerHelperFolder":  "D:\NAVData\ContainerHelper\Container",
"digestAlgorithm":  "SHA256",
"TreatWarningsAsErrors":  [
"AL1026"
],
"genericImageNameFilesOnly":  "mcr.microsoft.com/businesscentral:{0}-filesonly",
"bcartifactsCacheFolder":  "D:\NAVData\Artifacts",
"TraefikUseDnsNameAsHostName":  false,
"use7zipIfAvailable":  true,
"hostHelperFolder":  "D:\NAVData\ContainerHelper\Host",
"useSharedEncryptionKeys":  true,
"usePsSession":  true,
"mapCountryCode":  {
"ae":  "w1",
"br":  "w1",
"bd":  "w1",
"co":  "w1",
"dz":  "w1",
"ee":  "w1",
"eg":  "w1",
"fo":  "dk",
"gl":  "dk",
"gr":  "w1",
"hk":  "w1",
"hr":  "w1",
"hu":  "w1",
"id":  "w1",
"ie":  "w1",
"jp":  "w1",
"ke":  "w1",
"kr":  "w1",
"lb":  "w1",
"lk":  "w1",
"lt":  "w1",
"lu":  "w1",
"lv":  "w1",
"ma":  "w1",
"mm":  "w1",
"mt":  "w1",
"my":  "w1",
"ng":  "w1",
"pe":  "w1",
"ph":  "w1",
"pl":  "w1",
"qa":  "w1",
"rs":  "w1",
"ro":  "w1",
"sa":  "w1",
"sg":  "w1",
"si":  "w1",
"th":  "w1",
"tn":  "w1",
"tw":  "w1",
"vn":  "w1",
"za":  "w1"
},
"timeStampServer":  "http://timestamp.digicert.com",
"genericImageName":  "mcr.microsoft.com/businesscentral:{0}",
"psSessionTimeout":  0,
"defaultContainerName":  "bcserver"
}
BcContainerHelper2.config.json
{
"bcartifactsCacheFolder":  "D:\Artifacts.cache",
"usePsSession":  true,
"hostHelperFolder":  "D:\BcContainerHelper",
"use7zipIfAvailable":  true,
"genericImageName":  "mcr.microsoft.com/dynamicsnav:{0}-generic",
"containerHelperFolder":  "C:\ProgramData\BcContainerHelper",
"sandboxContainersAreMultitenantByDefault":  true,
"defaultContainerName":  "bcserver",
"defaultNewContainerParameters":  {
"Credential":  {
"Password":  "01000000d08c9ddf0115d1118c7a00c04fc297eb01000000477e67b63d74a24e856457240ad8bf7a00000000020000000000106600000001000020000000658b0700d7bccf1fcf72d05600b9b14daf20617a71b5f826fbb3b689b02200f1000000000e8000000002000020000000d1b491ee6e00f90fdd234b23ba840a4d5068ccbb79b6d18a5c6266cec5ac0a6c200000006bcdf721f1a43202cb19a40939194d3d6dfcdb7fbd3764d1e4d4cad06580286a40000000f5fed33edf7a238a966697c2044edcee31019ded2d93cf6dd87d514d12ac11a84173760451b03de5b4479beb830fef7c13a1732d346bc148c821ebf9b8c57767",
"Username":  "admin"
},
"Accept_Eula":  true,
"Isolation":  "Process",
"UpdateHosts":  true,
"Auth":  "UserPassword"
}
}

I notice that containerHelperFolder is different in the two files. Don't know if that is relevant though?

containerhelperfolder is the shared folder inside the container - that should not be on D: drive - remove the setting.
Also, you should ONLY include the properties in the config file that you actually change - you should not have all defaults in there.

Hmm, removed containerhelperfolder  from the config file and got
Container Dns Name  : lanitol
Web Client          : http://lanitol/BC/
Setting lanitol to <IP_ADDRESS> in host hosts file
Files:
Cannot find path 'C:\inetpub\wwwroot\http' because it does not exist.
at , C:\Run\navstart.ps1: line 266
at , C:\Run\start.ps1: line 363
at , : line 1
Initialization of container lanitol failed
At C:\Program Files\WindowsPowerShell\Modules\BcContainerHelper\2.0.16\ContainerHandling\Wait-NavContainerReady.ps1:42 char:17

...             throw "Initialization of container $containerName failed" ...

Then removed hostHelperFolder from the config file and got the same error.
Will try a new reinstall, and only move the docker data-root- and bccontainerhelper cache- folder
NB:
Not sure why all the settings are there. All I've done is try to follow your blog-intruction with:
$bcContainerHelperConfig.hostHelperFolder = "D:\NAVData\ContainerHelper\Host"
$bcContainerHelperConfig.containerHelperFolder  = "D:\NAVData\ContainerHelper\Container"
$bcContainerHelperConfig.bcartifactsCacheFolder = "D:\NAVData\Artifacts"
$bcContainerHelperConfig | ConvertTo-Json | Set-Content "C:\ProgramData\BcContainerHelper\BcContainerHelper.config.json"

Got it, yeah - that construct writes everything in the .json file - didn't think of that:-(
That error looks like the windows defender problem - try disabling defender, create the container and re-enable to see if this is the issue.

Resetting everything and only changing data-root and cachefolder works as long as the defender is disabled :)


Tutorial sample Its_all_about_you not working

Dart Editor version 1.6.0.dev_07_00 (DEV)
Dart SDK version 1.6.0-dev.7.0
The its_all_about_you sample is not working.
Repro:
Download latest dart-tutorials-samples-master.zip, unpack.
Start Dart Editor with a clean workspace and open its_all_about_you from the samples
Click the Run button
Expected:
The browser displays a page that looks like the example from the dartlang.org tutiroals web page
Observed:
The browser displays an empty page. The editor has a message:
Uncaught ReferenceError: Platform is not defined (http://localhost:8080/packages/polymer/src/js/polymer/polymer.js:12)

This sample has been re-written, and does  not use Polymer any longer.


IndexError: list index out of range

I'm trying to run AlphaFold on a compute cluster and I keep on getting this error. I'm not sure what the issue is.
INFO:    Using cached image
/opt/conda/lib/python3.8/site-packages/absl/flags/_validators.py:203: UserWarning: Flag --preset has a non-None default value; therefore, mark_flag_as_required will pass even if flag is not specified in the command line!
warnings.warn(
I1102 01:00:48.103564<PHONE_NUMBER>33024 templates.py:880] Using precomputed obsolete pdbs /data/pdb_mmcif/obsolete.dat.
I1102 01:00:52.363656<PHONE_NUMBER>33024 tpu_client.py:54] Starting the local TPU driver.
I1102 01:00:52.606741<PHONE_NUMBER>33024 xla_bridge.py:231] Unable to initialize backend 'tpu_driver': Not found: Unable to find driver in registry given worker: local://
I1102 01:00:53.333841<PHONE_NUMBER>33024 xla_bridge.py:231] Unable to initialize backend 'tpu': Invalid argument: TpuPlatform is not available.
I1102 01:01:11.164360<PHONE_NUMBER>33024 run_alphafold.py:238] Have 5 models: ['model_1', 'model_2', 'model_3', 'model_4', 'model_5']
I1102 01:01:11.164527<PHONE_NUMBER>33024 run_alphafold.py:251] Using random seed<PHONE_NUMBER>01883188 for the data pipeline
Traceback (most recent call last):
File "/app/alphafold/run_alphafold.py", line 283, in
app.run(main)
File "/opt/conda/lib/python3.8/site-packages/absl/app.py", line 312, in run
_run_main(main, args)
File "/opt/conda/lib/python3.8/site-packages/absl/app.py", line 258, in _run_main
sys.exit(main(argv))
File "/app/alphafold/run_alphafold.py", line 255, in main
predict_structure(
File "/app/alphafold/run_alphafold.py", line 115, in predict_structure
feature_dict = data_pipeline.process(
File "/app/alphafold/alphafold/data/pipeline.py", line 118, in process
input_seqs, input_descs = parsers.parse_fasta(input_fasta_str)
File "/app/alphafold/alphafold/data/parsers.py", line 72, in parse_fasta
sequences[index] += line
IndexError: list index out of range

Can you share your input FASTA file here? I have seen this error if you have formatting issues there

A0A0K8P6T7.1.txt
This is the FASTA file I've been using. Thanks!

I was actually able to modify the formatting of my FASTA file and it was an easy fix, so I have it up and running. Thank you!


How to get sha256sum (or any other) of source archive?

Issue description
output path ‘/nix/store/i1xf3x515ncsrpxlrda23z95r8xa3j37-source’ has r:sha256 hash ‘0xv8fm67p2wkkv86v68hxx5fkb7lm906cr5v8hl6bf2hcfhx94yi’ when ‘43aa7e99dc9a476199746398a1478f4346d67f28adbe1e6a2633f7b19eaca2d7’ was expected

But why?
I get this sum with command sha256sum path_to_archive.tar.gz.

Either nix-hash for files outside of nix store or nix-prefetch-url '<nixpkgs>' -A hello.src for nixpkgs attributes
or nix-prefetch-url "http://example.com/file" for urls.

The reason for the mismatch in this case is that Nix is computing the hash of the archive's contents not the archive itself.

... as /nix/store/i1xf3x515ncsrpxlrda23z95r8xa3j37-source is not an archive but a directory tree.

nix-prefetch-url --type sha256 --unpack https://github.com/path/to/archive.tar.gz works fine.
Thanks you so much.


Filter bar tweaks

Went a bit crazier on this one. The switching behaviour bothered me, and it felt like quite a lot of what we had there was a bit unnecessary / took too much space. Ended up condensing it right down and using the same style for desktop and mobile. Say if anyone feels strongly about this.
Before:

After:

Before:

After:

Not sure if I like it on the event page.
Before:

After:

Slight Compromise:

we also lose the counts of elements for the different filters. Overall I like it for the mobile view, but not for larger, too much information and functionality (eg. doube-click to select just one type) being lost

Yup, fair enough. Added back at large screen sizes. I agree it works well.
Added an icon for search for better differentiation between elements.


create school

http://zs.sztum.pl/

@WyroczniaDesu Please provide us with a proof, which shows that the school recognizes the domain you are submitting as an official email domain for the students.
You can provide us with any of the following:

A copy of instruction (a hard-copy or electronic one) given to you by the school that tells you to use an email address in this email domain
An URL of a page at the official school website that says that students use this email domain
A reference to a recognized journal where an article was published by someone from the school, with explicit affiliation to the school, and e-mail address from the email domain
A WHOIS data that link the email domain to the school somehow
A copy of official letter from the school representative saying that the school provides e-mail addresses in this domain to the students
Anything else that can prove this fact in similar way, i.e. can be verified independently.

@WyroczniaDesu You might miss my previous comment. Please react.

@WyroczniaDesu I am sorry, this request remains unanswered for a while. I have to close it without merging. Please reopen and comment if you have an update regarding the aforementioned issue. Thank you for your understanding!


provenance: Add web end point

https://github.com/openactive/conformance-services/issues/51

Here's a sample.
It contains the raw item and the parent raw item. It even contains raw data validation results, if they exist!
Technically both raw items should be from the same publisher I think, but this will cover any eventuality (like me bodging the DB to produce this one) and provides all the info, which is the main point.

{
  "id": "17dc76c2b1fd0aa61a676c91e356349b087c12b0",
  "deleted": false,
  "data": {
    "@id": "https://visionrcl.leisurecloud.net/OpenActive/api/scheduled-sessions/20449958",
    "@type": "ScheduledSession",
    "endDate": "2020-07-29T10:00:00Z",
    "@context": [
      "https://openactive.io/",
      "https://openactive.io/ns-beta"
    ],
    "duration": "PT1H",
    "startDate": "2020-07-29T09:00:00Z",
    "identifier": 20449958,
    "superEvent": "https://visionrcl.leisurecloud.net/OpenActive/api/session-series/FC8GYMB10000720",
    "maximumAttendeeCapacity": 42,
    "remainingAttendeeCapacity": 42,
    "beta:sportsActivityLocation": [
      {
        "name": "1st Floor",
        "type": "SportsActivityLocation"
      }
    ]
  },
  "updated_at": "2020-07-24T13:27:38.259Z",
  "kind": "ScheduledSession",
  "raw_data": {
    "rpde_id": "00000000000020449958",
    "data_id": "https://visionrcl.leisurecloud.net/OpenActive/api/scheduled-sessions/20449958",
    "kind": "ScheduledSession",
    "data": {
      "id": "https://visionrcl.leisurecloud.net/OpenActive/api/scheduled-sessions/20449958",
      "type": "ScheduledSession",
      "endDate": "2020-07-29T10:00:00Z",
      "@context": [
        "https://openactive.io/",
        "https://openactive.io/ns-beta"
      ],
      "duration": "PT1H",
      "startDate": "2020-07-29T09:00:00Z",
      "identifier": 20449958,
      "superEvent": "https://visionrcl.leisurecloud.net/OpenActive/api/session-series/FC8GYMB10000720",
      "maximumAttendeeCapacity": 42,
      "remainingAttendeeCapacity": 42,
      "beta:sportsActivityLocation": [
        {
          "name": "1st Floor",
          "type": "SportsActivityLocation"
        }
      ]
    },
    "validation": {
      "done": false
    },
    "feed": {
      "name": "ScheduledSession",
      "url": "https://opendata.leisurecloud.live/api/feeds/VisionRedbridge-live-scheduled-sessions",
      "publisher": {
        "name": "Vision Redbridge Culture & Leisure Ltd Sessions and Facilities",
        "url": "https://visionrcl.leisurecloud.net/OpenActive/"
      }
    }
  },
  "parent_raw_data": {
    "rpde_id": "00000000000070959710",
    "data_id": "https://api.activenewham.org.uk/OpenActive/api/scheduled-sessions/70959710",
    "kind": "ScheduledSession",
    "data": {
      "id": "https://api.activenewham.org.uk/OpenActive/api/scheduled-sessions/70959710",
      "type": "ScheduledSession",
      "endDate": "2020-08-06T19:00:00Z",
      "@context": [
        "https://openactive.io/",
        "https://openactive.io/ns-beta"
      ],
      "duration": "PT1H",
      "startDate": "2020-08-06T18:00:00Z",
      "identifier": 70959710,
      "superEvent": "https://api.activenewham.org.uk/OpenActive/api/session-series/N4CLKEY19001217",
      "maximumAttendeeCapacity": 40,
      "remainingAttendeeCapacity": 40,
      "beta:sportsActivityLocation": [
        {
          "name": "Studio 1",
          "type": "SportsActivityLocation"
        }
      ]
    },
    "validation": {
      "done": true,
      "results": [
        {
          "path": "$[\"beta:sportsActivityLocation\"]",
          "rule": "FieldsNotInModelRule",
          "type": "experimental_fields_not_checked",
          "value": [
            {
              "name": "Studio 1",
              "type": "SportsActivityLocation"
            }
          ],
          "message": "A definition for this extension property was found, but it has not been included in the correct object type. Please check the spelling of this property and ensure that you are using it within the correct object `\"type\"`.\n\nThe types allowed for this property are:\n\n

https://schema.org/Event

https://openactive.io/Slot

https://openactive.io/FacilityUse

\n\nFor more information about extension properties, see the [extension properties guide](https://openactive.io/modelling-opportunity-data/EditorsDraft/#defining-and-using-custom-namespaces).",
          "category": "conformance",
          "severity": "failure"
        }
      ]
    },
    "feed": {
      "name": "ScheduledSession",
      "url": "https://opendata.leisurecloud.live/api/feeds/ActiveNewham-live-live-scheduled-sessions",
      "publisher": {
        "name": "activeNewham Sessions and Facilities",
        "url": "https://api.activenewham.org.uk/OpenActive/"
      }
    }
  }
}

 Add provenanceInformation block

I've added a commit to address those issues.


how to predict words Instead of characters

Hello sir ,I have implemented your project.It is working fine with mpu6050 (6 axis),but when I tried to implement with both mpu6050 and flex sensors or (only flex sensors) its performance has been decreased and it is not predicting well.
Also can we predict words instead of characters .

Please reply ...

Hi,
I've never used flex sensors so I don't know much about them. The only suggestion I can give you is to experiment with the parameters of the classifier.
With whole words the recognition is much harder, you would have to train the classifier to recognize every possible word...
Best regards

Please help me out of this.


5E SRD: Add 1st-Level Spells to Spell List

The following 1st Level Spells from the 5th Edition System Reference Document (5e SRD) need to be added in Markdown format to the site under the _posts/spells/first-level/ directory. There will be a template-spell.md file in the spells folder for use as needed.
Specifications

Post should be titled YYYY-MM-DD-spells-1-<spell_name>.md

EXAMPLE: 2020-10-10-spells-0-kaboom.md

Follow template-spell.md format for inputting spell information. Info should include:

Spell Name (Druid Splash)
School (i.e. Evocation, Necromancy)
Casting Time (i.e. 1 Bonus Action)
Range (i.e. Self / 60 Feet)
Duration (i.e. Instantaneous)
Components (i.e. V, S, M)

Pull requests should include completed spell post in the proper directory: _posts/spells/cantrips/YYYY-MM-DD-spells-1-<spell_name>.md

Spells Needed

[ ] Absorb Elements

[ ] Acid Stream (UA)

[x] Alarm

[x] Animal Friendship

[ ] Arcane Weapon

[ ] Armor of Agathys

[ ] Arms of Hadar

[x] Bane

[ ] Beast Bond

[x] Bless

[x] Burning Hands

[ ] Catapult

[ ] Cause Fear

[ ] Ceremony

[ ] Chaos Bolt

[x] Charm Person

[ ] Chromatic Orb

[x] Color Spray

[x] Command

[ ] Compelled Duel

[x] Comprehend Languages

[x] Create or Destroy Water

[x] Cure Wounds

[x] Detect Evil and Good

[x] Detect Magic

[x] Detect Poison and Disease

[x] Disguise Self

[ ] Dissonant Whispers

[ ] Distort Value

[x] Divine Favor

[ ] Earth Tremor

[ ] Ensnaring Strike

[x] Entangle

[x] Expeditious Retreat

[x] Faerie Fire

[x] False Life

[x] Feather Fall

[x] Find Familiar

[x] Fog Cloud

[ ] Gift of Alacrity

[x] Goodberry

[x] Grease

[x] Guiding Bolt

[ ] Guiding Hand (UA)

[ ] Hail of Thorns

[ ] Healing Elixir (UA)

[x] Healing Word

[x] Hellish Rebuke

[x] Heroism

[ ] Hex

[x] Hunter's Mark

[ ] Ice Knife

[ ] Id Insinuation (UA)

[x] Identify

[x] Illusory Script

[ ] Infallible Relay (UA)

[x] Inflict Wounds

[ ] Jim's Magic Missile

[x] Jump

[x] Longstrider

[x] Mage Armor

[x] Magic Missile

[ ] Magnify Gravity

[x] Protection from Evil and Good

[ ] Puppet (UA)

[x] Purify Food and Drink

[ ] Ray of Sickness

[ ] Remote Access (UA)

[x] Sanctuary

[ ] Searing Smite

[ ] Sense Emotion

[x] Shield

[x] Shield of Faith

[x] Silent Image

[x] Sleep

[ ] Snare

[x] Speak with Animals

[ ] Sudden Awakening

[ ] Tasha's Hideous Laughter

[ ] Tenser's Floating Disk

[ ] Thunderous Smite

[x] Thunderwave

[ ] Unearthly Chorus (UA)

[x] Unseen Servant

[ ] Wild Cunning (UA)

[ ] Witch Bolt

[ ] Wrathful Smite

[ ] Zephyr Strike

Cool, I'll go ahead and assign you onto this issue. Let me know if you have any questions or concerns.


Changelog for 11.2.0

Also make sure the pom, gradle and license files are updated with the appropriate version. If so ignore this comment.


yall.js is being inserted on every page

I think the plugin is only supposed to insert/load yall.js on the photos page, but it looks like the plugin is inserting it below the site footer on every page

Following up on this finally, I'm changing the plug-in to not include yall.js everywhere. Also we probably don't even need it anymore as lazy loading is built into most browsers these days.


feat: WHOIS lookup

Tool that allows fetching WHOIS information of a domain. Should be under Networking category.

This probably requires a separate backend plugin..

Done and dusted