can not resize pvc

Following https://hwameistor.io/docs/quick_start/create_stateful/advanced/expand
When I resize a pvc from 10Gi to 20Gi, the status of PVC not changed, but relate PV was changed.
root@gsc-cluster-master01:~# kubectl -n mcamel-system get pvc elasticsearch-data-mcamel-common-es-cluster-masters-es-masters-0 -o yaml
apiVersion: v1
kind: PersistentVolumeClaim
metadata:
  annotations:
    pv.kubernetes.io/bind-completed: "yes"
    pv.kubernetes.io/bound-by-controller: "yes"
    volume.beta.kubernetes.io/storage-provisioner: lvm.hwameistor.io
    volume.kubernetes.io/selected-node: gsc-cluster-worker02
    volume.kubernetes.io/storage-provisioner: lvm.hwameistor.io
  creationTimestamp: "2023-02-02T07:14:36Z"
  finalizers:
  - kubernetes.io/pvc-protection
  labels:
    common.k8s.elastic.co/type: elasticsearch
    elasticsearch.k8s.elastic.co/cluster-name: mcamel-common-es-cluster-masters
    elasticsearch.k8s.elastic.co/statefulset-name: mcamel-common-es-cluster-masters-es-masters
  name: elasticsearch-data-mcamel-common-es-cluster-masters-es-masters-0
  namespace: mcamel-system
  resourceVersion: "7466590"
  uid: df53cd45-9d6f-44a1-9cf1-4d267bdee2e0
spec:
  accessModes:
  - ReadWriteOnce
  resources:
    requests:
      storage: 20Gi
  storageClassName: hwameistor-storage-lvm-hdd
  volumeMode: Filesystem
  volumeName: pvc-df53cd45-9d6f-44a1-9cf1-4d267bdee2e0
status:
  accessModes:
  - ReadWriteOnce
  capacity:
    storage: 10Gi
  conditions:
  - lastProbeTime: null
    lastTransitionTime: "2023-02-08T06:59:29Z"
    message: Waiting for user to (re-)start a pod to finish file system resize of
      volume on node.
    status: "True"
    type: FileSystemResizePending
  phase: Bound
root@gsc-cluster-master01:~# kubectl -n mcamel-system describe pvc elasticsearch-data-mcamel-common-es-cluster-masters-es-masters-0
Name:          elasticsearch-data-mcamel-common-es-cluster-masters-es-masters-0
Namespace:     mcamel-system
StorageClass:  hwameistor-storage-lvm-hdd
Status:        Bound
Volume:        pvc-df53cd45-9d6f-44a1-9cf1-4d267bdee2e0
Labels:        common.k8s.elastic.co/type=elasticsearch
               elasticsearch.k8s.elastic.co/cluster-name=mcamel-common-es-cluster-masters
               elasticsearch.k8s.elastic.co/statefulset-name=mcamel-common-es-cluster-masters-es-masters
Annotations:   pv.kubernetes.io/bind-completed: yes
               pv.kubernetes.io/bound-by-controller: yes
               volume.beta.kubernetes.io/storage-provisioner: lvm.hwameistor.io
               volume.kubernetes.io/selected-node: gsc-cluster-worker02
               volume.kubernetes.io/storage-provisioner: lvm.hwameistor.io
Finalizers:    [kubernetes.io/pvc-protection]
Capacity:      10Gi
Access Modes:  RWO
VolumeMode:    Filesystem
Used By:       mcamel-common-es-cluster-masters-es-masters-0
Conditions:
  Type                      Status  LastProbeTime                     LastTransitionTime                Reason  Message
  ----                      ------  -----------------                 ------------------                ------  -------
  FileSystemResizePending   True    Mon, 01 Jan 0001 00:00:00 +0000   Wed, 08 Feb 2023 14:59:29 +0800           Waiting for user to (re-)start a pod to finish file system resize of volume on node.
Events:
  Type     Reason                    Age                From                                Message
  ----     ------                    ----               ----                                -------
  Warning  ExternalExpanding         19m                volume_expand                       Ignoring the PVC: didn't find a plugin capable of expanding the volume; waiting for an external controller to process this PVC.
  Warning  VolumeResizeFailed        13m                external-resizer lvm.hwameistor.io  resize volume "pvc-df53cd45-9d6f-44a1-9cf1-4d267bdee2e0" by resizer "lvm.hwameistor.io" failed: rpc error: code = Unknown desc = volume expansion not completed yet
  Warning  VolumeResizeFailed        13m                external-resizer lvm.hwameistor.io  resize volume "pvc-df53cd45-9d6f-44a1-9cf1-4d267bdee2e0" by resizer "lvm.hwameistor.io" failed: rpc error: code = Unknown desc = volume expansion in progress
  Normal   Resizing                  13m (x3 over 13m)  external-resizer lvm.hwameistor.io  External resizer is resizing volume pvc-df53cd45-9d6f-44a1-9cf1-4d267bdee2e0
  Normal   FileSystemResizeRequired  13m                external-resizer lvm.hwameistor.io  Require file system resize of volume on node

root@gsc-cluster-master01:~# kubectl -n hwameistor logs hwameistor-local-storage-csi-controller-7c5468dbf7-fdxwl resizer
---
I0208 06:59:28.359395       1 connection.go:183] GRPC request: {"capacity_range":{"required_bytes":21474836480},"volume_capability":{"AccessType":{"Mount":{"fs_type":"xfs"}},"access_mode":{"mode":1}},"volume_id":"pvc-df53cd45-9d6f-44a1-9cf1-4d267bdee2e0"}
I0208 06:59:28.359623       1 event.go:282] Event(v1.ObjectReference{Kind:"PersistentVolumeClaim", Namespace:"mcamel-system", Name:"elasticsearch-data-mcamel-common-es-cluster-masters-es-masters-0", UID:"df53cd45-9d6f-44a1-9cf1-4d267bdee2e0", APIVersion:"v1", ResourceVersion:"7466558", FieldPath:""}): type: 'Normal' reason: 'Resizing' External resizer is resizing volume pvc-df53cd45-9d6f-44a1-9cf1-4d267bdee2e0
I0208 06:59:28.384806       1 connection.go:185] GRPC response: {}
I0208 06:59:28.384866       1 connection.go:186] GRPC error: rpc error: code = Unknown desc = volume expansion not completed yet
E0208 06:59:28.384908       1 controller.go:272] Error syncing PVC: resize volume "pvc-df53cd45-9d6f-44a1-9cf1-4d267bdee2e0" by resizer "lvm.hwameistor.io" failed: rpc error: code = Unknown desc = volume expansion not completed yet
I0208 06:59:28.384930       1 controller.go:281] Started PVC processing "mcamel-system/elasticsearch-data-mcamel-common-es-cluster-masters-es-masters-0"
I0208 06:59:28.385550       1 event.go:282] Event(v1.ObjectReference{Kind:"PersistentVolumeClaim", Namespace:"mcamel-system", Name:"elasticsearch-data-mcamel-common-es-cluster-masters-es-masters-0", UID:"df53cd45-9d6f-44a1-9cf1-4d267bdee2e0", APIVersion:"v1", ResourceVersion:"7466558", FieldPath:""}): type: 'Warning' reason: 'VolumeResizeFailed' resize volume "pvc-df53cd45-9d6f-44a1-9cf1-4d267bdee2e0" by resizer "lvm.hwameistor.io" failed: rpc error: code = Unknown desc = volume expansion not completed yet
I0208 06:59:28.400066       1 connection.go:182] GRPC call: /csi.v1.Controller/ControllerExpandVolume
I0208 06:59:28.400099       1 connection.go:183] GRPC request: {"capacity_range":{"required_bytes":21474836480},"volume_capability":{"AccessType":{"Mount":{"fs_type":"xfs"}},"access_mode":{"mode":1}},"volume_id":"pvc-df53cd45-9d6f-44a1-9cf1-4d267bdee2e0"}
I0208 06:59:28.400640       1 event.go:282] Event(v1.ObjectReference{Kind:"PersistentVolumeClaim", Namespace:"mcamel-system", Name:"elasticsearch-data-mcamel-common-es-cluster-masters-es-masters-0", UID:"df53cd45-9d6f-44a1-9cf1-4d267bdee2e0", APIVersion:"v1", ResourceVersion:"7466558", FieldPath:""}): type: 'Normal' reason: 'Resizing' External resizer is resizing volume pvc-df53cd45-9d6f-44a1-9cf1-4d267bdee2e0
I0208 06:59:28.405929       1 connection.go:185] GRPC response: {}
I0208 06:59:28.405961       1 connection.go:186] GRPC error: rpc error: code = Unknown desc = volume expansion in progress
E0208 06:59:28.406022       1 controller.go:272] Error syncing PVC: resize volume "pvc-df53cd45-9d6f-44a1-9cf1-4d267bdee2e0" by resizer "lvm.hwameistor.io" failed: rpc error: code = Unknown desc = volume expansion in progress
I0208 06:59:28.406061       1 event.go:282] Event(v1.ObjectReference{Kind:"PersistentVolumeClaim", Namespace:"mcamel-system", Name:"elasticsearch-data-mcamel-common-es-cluster-masters-es-masters-0", UID:"df53cd45-9d6f-44a1-9cf1-4d267bdee2e0", APIVersion:"v1", ResourceVersion:"7466558", FieldPath:""}): type: 'Warning' reason: 'VolumeResizeFailed' resize volume "pvc-df53cd45-9d6f-44a1-9cf1-4d267bdee2e0" by resizer "lvm.hwameistor.io" failed: rpc error: code = Unknown desc = volume expansion in progress
I0208 06:59:29.388155       1 controller.go:281] Started PVC processing "mcamel-system/elasticsearch-data-mcamel-common-es-cluster-masters-es-masters-0"
I0208 06:59:29.396146       1 connection.go:182] GRPC call: /csi.v1.Controller/ControllerExpandVolume
I0208 06:59:29.396157       1 connection.go:183] GRPC request: {"capacity_range":{"required_bytes":21474836480},"volume_capability":{"AccessType":{"Mount":{"fs_type":"xfs"}},"access_mode":{"mode":1}},"volume_id":"pvc-df53cd45-9d6f-44a1-9cf1-4d267bdee2e0"}
I0208 06:59:29.396600       1 event.go:282] Event(v1.ObjectReference{Kind:"PersistentVolumeClaim", Namespace:"mcamel-system", Name:"elasticsearch-data-mcamel-common-es-cluster-masters-es-masters-0", UID:"df53cd45-9d6f-44a1-9cf1-4d267bdee2e0", APIVersion:"v1", ResourceVersion:"7466586", FieldPath:""}): type: 'Normal' reason: 'Resizing' External resizer is resizing volume pvc-df53cd45-9d6f-44a1-9cf1-4d267bdee2e0
I0208 06:59:29.397702       1 connection.go:185] GRPC response: {"capacity_bytes":21474836480,"node_expansion_required":true}
I0208 06:59:29.397734       1 connection.go:186] GRPC error: <nil>
I0208 06:59:29.397758       1 controller.go:447] Resize volume succeeded for volume "pvc-df53cd45-9d6f-44a1-9cf1-4d267bdee2e0", start to update PV's capacity
I0208 06:59:29.397763       1 controller.go:537] Resize volume succeeded for volume "pvc-df53cd45-9d6f-44a1-9cf1-4d267bdee2e0", start to update PV's capacity
I0208 06:59:29.423300       1 controller.go:453] Update capacity of PV "pvc-df53cd45-9d6f-44a1-9cf1-4d267bdee2e0" to 20Gi succeeded
I0208 06:59:29.440553       1 controller.go:475] Mark PVC "mcamel-system/elasticsearch-data-mcamel-common-es-cluster-masters-es-masters-0" as file system resize required
I0208 06:59:29.441031       1 event.go:282] Event(v1.ObjectReference{Kind:"PersistentVolumeClaim", Namespace:"mcamel-system", Name:"elasticsearch-data-mcamel-common-es-cluster-masters-es-masters-0", UID:"df53cd45-9d6f-44a1-9cf1-4d267bdee2e0", APIVersion:"v1", ResourceVersion:"7466586", FieldPath:""}): type: 'Normal' reason: 'FileSystemResizeRequired' Require file system resize of volume on node

root@gsc-cluster-master01:~# kubectl get pv
pvc-df53cd45-9d6f-44a1-9cf1-4d267bdee2e0   20Gi       RWO            Delete           Bound    mcamel-system/elasticsearch-data-mcamel-common-es-cluster-masters-es-masters-0                hwameistor-storage-lvm-hdd            5d23h

Output of lsblk:
NAME                              MAJ:MIN RM   SIZE RO TYPE MOUNTPOINTS
loop0                               7:0    0     4K  1 loop /snap/bare/5
loop2                               7:2    0  63.3M  1 loop /snap/core20/1778
loop3                               7:3    0   6.3M  1 loop /snap/curl/1435
loop4                               7:4    0 163.3M  1 loop /snap/firefox/1635
loop5                               7:5    0 239.1M  1 loop /snap/firefox/2311
loop6                               7:6    0 400.8M  1 loop /snap/gnome-3-38-2004/112
loop7                               7:7    0 346.3M  1 loop /snap/gnome-3-38-2004/119
loop8                               7:8    0  91.7M  1 loop /snap/gtk-common-themes/1535
loop9                               7:9    0  45.9M  1 loop /snap/snap-store/582
loop10                              7:10   0  45.9M  1 loop /snap/snap-store/638
loop11                              7:11   0  49.8M  1 loop /snap/snapd/17950
loop12                              7:12   0   284K  1 loop /snap/snapd-desktop-integration/14
loop13                              7:13   0   304K  1 loop /snap/snapd-desktop-integration/49
loop14                              7:14   0  63.3M  1 loop /snap/core20/1822
sr0                                11:0    1  1024M  0 rom
vda                               252:0    0   100G  0 disk
├─vda1                            252:1    0     1M  0 part
├─vda2                            252:2    0   513M  0 part /boot/efi
└─vda3                            252:3    0  99.5G  0 part /var/lib/kubelet/pods/aa0ac9a5-4e11-4dbf-a8cd-52028aa8beef/volume-subpaths/nginxconf/kpanda-nginx/2
                                                            /var/lib/kubelet/pods/45c08a26-964e-4243-989b-26cef3efb50d/volume-subpaths/luascripts/fluent-bit/6
                                                            /var/lib/kubelet/pods/45c08a26-964e-4243-989b-26cef3efb50d/volume-subpaths/luascripts/fluent-bit/5
                                                            /var/lib/kubelet/pods/45c08a26-964e-4243-989b-26cef3efb50d/volume-subpaths/luascripts/fluent-bit/4
                                                            /var/lib/kubelet/pods/45c08a26-964e-4243-989b-26cef3efb50d/volume-subpaths/luascripts/fluent-bit/3
                                                            /var/lib/kubelet/pods/45c08a26-964e-4243-989b-26cef3efb50d/volume-subpaths/luascripts/fluent-bit/2
                                                            /var/lib/kubelet/pods/45c08a26-964e-4243-989b-26cef3efb50d/volume-subpaths/config/fluent-bit/1
                                                            /var/lib/kubelet/pods/45c08a26-964e-4243-989b-26cef3efb50d/volume-subpaths/config/fluent-bit/0
                                                            /var/lib/kubelet/pods/99e59302-02db-4dbd-bb36-f33a5559e0e4/volume-subpaths/nginxconf/kpanda-nginx/1
                                                            /var/snap/firefox/common/host-hunspell
                                                            /
vdb                               252:16   0   100G  0 disk
├─LocalStorage_PoolHDD-pvc--65b26d3e--7853--4f10--b3fc--86e52fd872bd
│                                 253:0    0     1G  0 lvm  /var/lib/kubelet/pods/6b6a7da7-cae9-4333-b379-3210525fcdcf/volumes/kubernetes.io~csi/pvc-65b26d3e-7853-4f10-b3fc-86e52fd872bd/mount
├─LocalStorage_PoolHDD-pvc--cd01e456--d3a2--4efc--bb41--68a9057402b0
│                                 253:1    0    20G  0 lvm  /var/lib/kubelet/pods/29373d0a-7fc7-452b-b08f-b5334f0a3b92/volumes/kubernetes.io~csi/pvc-cd01e456-d3a2-4efc-bb41-68a9057402b0/mount
└─LocalStorage_PoolHDD-pvc--ff439978--b7fa--4791--9403--a6845f0d898d
                                  253:2    0     2G  0 lvm  /var/lib/kubelet/pods/3612acac-34e3-4d3f-bf6e-728e63b8ae4d/volumes/kubernetes.io~csi/pvc-ff439978-b7fa-4791-9403-a6845f0d898d/mount

Output of blkid:
# paste output here

Output of kubectl version:
Client Version: v1.25.0
Kustomize Version: v4.5.7
Server Version: v1.24.10

Output of kubectl get lsn -o yaml:
# paste output here

Cloud Provider/Platform (AKS, GKE, Minikube etc.):
Kubernetes

And pod can not be re-created, it returns
  Type     Reason                  Age                  From                     Message
  ----     ------                  ----                 ----                     -------
  Normal   Scheduled               3m                   hwameistor-scheduler     Successfully assigned mcamel-system/mcamel-common-es-cluster-masters-es-masters-0 to gsc-cluster-worker02
  Normal   SuccessfulAttachVolume  2m59s                attachdetach-controller  AttachVolume.Attach succeeded for volume "pvc-df53cd45-9d6f-44a1-9cf1-4d267bdee2e0"
  Warning  FailedMount             57s                  kubelet                  Unable to attach or mount volumes: unmounted volumes=[elasticsearch-data], unattached volumes=[elastic-internal-transport-certificates elastic-internal-elasticsearch-plugins-local elastic-internal-unicast-hosts elastic-internal-elasticsearch-config-local elastic-internal-scripts elastic-internal-xpack-file-realm downward-api elastic-internal-probe-user elasticsearch-data elastic-internal-remote-certificate-authorities elastic-internal-http-certificates elastic-internal-elasticsearch-bin-local elastic-internal-elasticsearch-config elasticsearch-logs]: timed out waiting for the condition
  Warning  FailedMount             42s (x9 over 2m50s)  kubelet                  MountVolume.Setup failed while expanding volume for volume "pvc-df53cd45-9d6f-44a1-9cf1-4d267bdee2e0" : Expander.NodeExpand failed to expand the volume : rpc error: code = Unknown desc = exit status 1

kubelet logs:
2月 08 15:29:28 gsc-cluster-worker02 kubelet[1402]: E0208 15:29:28.345694    1402 kubelet.go:1709] "Unable to attach or mount volumes for pod; skipping pod" err="unmounted volumes=[elasticsearch-data], unattached volumes=[elastic-internal-elasticsearch-config elastic-internal-remote-certificate-authorities elastic-internal-unicast-hosts elastic-internal-elasticsearch-plugins-local elastic-internal-http-certificates elastic-internal-probe-user elasticsearch-logs elastic-internal-elasticsearch-bin-local elastic-internal-elasticsearch-config-local downward-api elastic-internal-transport-certificates elasticsearch-data elastic-internal-scripts elastic-internal-xpack-file-realm]: timed out waiting for the condition" pod="mcamel-system/mcamel-common-es-cluster-masters-es-masters-0"
2月 08 15:29:28 gsc-cluster-worker02 kubelet[1402]: E0208 15:29:28.345729    1402 pod_workers.go:951] "Error syncing pod, skipping" err="unmounted volumes=[elasticsearch-data], unattached volumes=[elastic-internal-elasticsearch-config elastic-internal-remote-certificate-authorities elastic-internal-unicast-hosts elastic-internal-elasticsearch-plugins-local elastic-internal-http-certificates elastic-internal-probe-user elasticsearch-logs elastic-internal-elasticsearch-bin-local elastic-internal-elasticsearch-config-local downward-api elastic-internal-transport-certificates elasticsearch-data elastic-internal-scripts elastic-internal-xpack-file-realm]: timed out waiting for the condition" pod="mcamel-system/mcamel-common-es-cluster-masters-es-masters-0" podUID=2d0dce0d-e9f1-4a3d-9901-60e0a7052541
2月 08 15:29:28 gsc-cluster-worker02 kubelet[1402]: E0208 15:29:28.758265    1402 kubelet_volumes.go:245] "There were many similar errors. Turn up verbosity to see them." err="orphaned pod \"2f067891-21f3-40ad-89d4-2e4553191098\" found, but error occurred when trying to remove the volumes dir: not a directory" numErrs=4
2月 08 15:29:30 gsc-cluster-worker02 kubelet[1402]: E0208 15:29:30.774039    1402 kubelet_volumes.go:245] "There were many similar errors. Turn up verbosity to see them." err="orphaned pod \"2f067891-21f3-40ad-89d4-2e4553191098\" found, but error occurred when trying to remove the volumes dir: not a directory" numErrs=4
2月 08 15:29:32 gsc-cluster-worker02 kubelet[1402]: E0208 15:29:32.759629    1402 kubelet_volumes.go:245] "There were many similar errors. Turn up verbosity to see them." err="orphaned pod \"2f067891-21f3-40ad-89d4-2e4553191098\" found, but error occurred when trying to remove the volumes dir: not a directory" numErrs=4
2月 08 15:29:34 gsc-cluster-worker02 kubelet[1402]: E0208 15:29:34.757349    1402 kubelet_volumes.go:245] "There were many similar errors. Turn up verbosity to see them." err="orphaned pod \"2f067891-21f3-40ad-89d4-2e4553191098\" found, but error occurred when trying to remove the volumes dir: not a directory" numErrs=4
2月 08 15:29:36 gsc-cluster-worker02 kubelet[1402]: E0208 15:29:36.764129    1402 kubelet_volumes.go:245] "There were many similar errors. Turn up verbosity to see them." err="orphaned pod \"2f067891-21f3-40ad-89d4-2e4553191098\" found, but error occurred when trying to remove the volumes dir: not a directory" numErrs=4
2月 08 15:29:38 gsc-cluster-worker02 kubelet[1402]: E0208 15:29:38.769493    1402 kubelet_volumes.go:245] "There were many similar errors. Turn up verbosity to see them." err="orphaned pod \"2f067891-21f3-40ad-89d4-2e4553191098\" found, but error occurred when trying to remove the volumes dir: not a directory" numErrs=4
2月 08 15:29:40 gsc-cluster-worker02 kubelet[1402]: E0208 15:29:40.755431    1402 kubelet_volumes.go:245] "There were many similar errors. Turn up verbosity to see them." err="orphaned pod \"2f067891-21f3-40ad-89d4-2e4553191098\" found, but error occurred when trying to remove the volumes dir: not a directory" numErrs=4
2月 08 15:29:42 gsc-cluster-worker02 kubelet[1402]: E0208 15:29:42.766184    1402 kubelet_volumes.go:245] "There were many similar errors. Turn up verbosity to see them." err="orphaned pod \"2f067891-21f3-40ad-89d4-2e4553191098\" found, but error occurred when trying to remove the volumes dir: not a directory" numErrs=4
2月 08 15:29:42 gsc-cluster-worker02 kubelet[1402]: I0208 15:29:42.882948    1402 operation_generator.go:616] "MountVolume.WaitForAttach entering for volume \"pvc-df53cd45-9d6f-44a1-9cf1-4d267bdee2e0\" (UniqueName: \"kubernetes.io/csi/lvm.hwameistor.io^pvc-df53cd45-9d6f-44a1-9cf1-4d267bdee2e0\") pod \"mcamel-common-es-cluster-masters-es-masters-0\" (UID: \"2d0dce0d-e9f1-4a3d-9901-60e0a7052541\") DevicePath \"csi-7d470aee93bf59342548873422200d154e5987417622c837fd701d4df812a6f0\"" pod="mcamel-system/mcamel-common-es-cluster-masters-es-masters-0"
2月 08 15:29:42 gsc-cluster-worker02 kubelet[1402]: I0208 15:29:42.884670    1402 operation_generator.go:626] "MountVolume.WaitForAttach succeeded for volume \"pvc-df53cd45-9d6f-44a1-9cf1-4d267bdee2e0\" (UniqueName: \"kubernetes.io/csi/lvm.hwameistor.io^pvc-df53cd45-9d6f-44a1-9cf1-4d267bdee2e0\") pod \"mcamel-common-es-cluster-masters-es-masters-0\" (UID: \"2d0dce0d-e9f1-4a3d-9901-60e0a7052541\") DevicePath \"csi-7d470aee93bf59342548873422200d154e5987417622c837fd701d4df812a6f0\"" pod="mcamel-system/mcamel-common-es-cluster-masters-es-masters-0"
2月 08 15:29:42 gsc-cluster-worker02 kubelet[1402]: E0208 15:29:42.903041    1402 operation_generator.go:708] MountVolume.NodeExpandVolume failed with Expander.NodeExpand failed to expand the volume : rpc error: code = Unknown desc = exit status 1
2月 08 15:29:42 gsc-cluster-worker02 kubelet[1402]: E0208 15:29:42.903099    1402 nestedpendingoperations.go:348] Operation for "{volumeName:kubernetes.io/csi/lvm.hwameistor.io^pvc-df53cd45-9d6f-44a1-9cf1-4d267bdee2e0 podName: nodeName:}" failed. No retries permitted until 2023-02-08 15:31:44.903083379 +0800 CST m=+433274.359576853 (durationBeforeRetry 2m2s). Error: MountVolume.Setup failed while expanding volume for volume "pvc-df53cd45-9d6f-44a1-9cf1-4d267bdee2e0" (UniqueName: "kubernetes.io/csi/lvm.hwameistor.io^pvc-df53cd45-9d6f-44a1-9cf1-4d267bdee2e0") pod "mcamel-common-es-cluster-masters-es-masters-0" (UID: "2d0dce0d-e9f1-4a3d-9901-60e0a7052541") : Expander.NodeExpand failed to expand the volume : rpc error: code = Unknown desc = exit status 1
2月 08 15:29:44 gsc-cluster-worker02 kubelet[1402]: E0208 15:29:44.755156    1402 kubelet_volumes.go:245] "There were many similar errors. Turn up verbosity to see them." err="orphaned pod \"2f067891-21f3-40ad-89d4-2e4553191098\" found, but error occurred when trying to remove the volumes dir: not a directory" numErrs=4
2月 08 15:29:46 gsc-cluster-worker02 kubelet[1402]: E0208 15:29:46.757742    1402 kubelet_volumes.go:245] "There were many similar errors. Turn up verbosity to see them." err="orphaned pod \"2f067891-21f3-40ad-89d4-2e4553191098\" found, but error occurred when trying to remove the volumes dir: not a directory" numErrs=4
2月 08 15:29:48 gsc-cluster-worker02 kubelet[1402]: E0208 15:29:48.756365    1402 kubelet_volumes.go:245] "There were many similar errors. Turn up verbosity to see them." err="orphaned pod \"2f067891-21f3-40ad-89d4-2e4553191098\" found, but error occurred when trying to remove the volumes dir: not a directory" numErrs=4

@kebe7jun  Thanks for your feedback. :-)
It looks like failed during the NodeExpand phase. It can be confirmed by the log in the following containers.

CSI: resizer container
local-storage: member container

NOTE: If the xfs filesystem is used, the xfs_growfs tool needs to be installed on the host.

Ubuntu os missing xfs tools.
Shall we update the doc https://hwameistor.io/docs/quick_start/install/prereq?

Ubuntu os missing xfs tools. Shall we update the doc https://hwameistor.io/docs/quick_start/install/prereq?

Yes, we will update the requirements at the doc.


Update from upstream

@Rub21 @geohacker - per voice with @Rub21: let's look at latest NYC data and see what we can update from NYC.
To do this we'll want to:

Determine any changes in buildings and addresses between the NYC file we imported and the latest NYC files available on their web site.
Determine what new/modified/deleted buildings could be added/updated/removed from OSM (local OSM edits have precedence).
Queue up and execute updates.

Pre - SOTM US it would be great to at least address (1) to see what the opportunity of improvement is.
cc @aaronlidman @ruthmaben

Determine any changes in buildings and addresses between the NYC file we imported and the latest NYC files available on their web site.

Sounds good. Need more info on the files here. I found this says last updated on April 29 2015. Where is the old file?

@lxbarth if you send me the date of the file used for the import, I can send the deltas.

@lxbarth The file from https://data.cityofnewyork.us/Housing-Development/Building-Footprints/tb92-6tj8 and  https://github.com/osmlab/nycbuildings/blob/master/Makefile#L11 are the same from date Apr, 2015,
@lxbarth do you know if someone has the old building footprints file?

Here are the files imported:

Address points http://cl.ly/080a2K2A3y0k/download/NYC_AddressPoint.zip
Buildings http://cl.ly/3b1e0i0q1s2i

@colinreilly - the building file is 09/13. I'm not sure about the date on the address points.

I have someone working on this - they just got sidetracked on a few other things - hope to have the deltas for you Monday. I assumed the same date Sept '13 for the address points. If you've already done the work you can at least use this as a validation check or reference.


Crashes at launch after 2.2 install

I tried installing 2.2 on two devices - my main work machine and a Big Sur VM, both running 11.3.1. Works flawlessly on my main machine, but on the VM, the app crashes every time I click the menu bar icon. After the crash, it appears to reload, then clicking the button crashes it again.
I uninstalled/reinstalled it to see if the .pkg had misfired, no change. I removed all MDM configs for the app, no change. Tried uploading a new mobileconfig that included the badge for uptime, no change. Reboot, no change.
Attaching crash report - any idea on what's causing this? If there's a fix, I can build it into my deployment or uninstallation script as needed.
supportMenu2.2_crashLog.txt

Hi @xirianlight we were able to reproduce and it turns out the crash is related to a query to get the Mac's introduction year. A fix will come soon. As a workaround, you could simulate a 'real world' serial number in the VM's config file

@xirianlight v2.2.1 was just released and I believe the crash is fixed when no serial number is set.


No import quick fix where I expect one

I would expext an "add import" quickfix like below but here I don't get one

I don't know what context causes this. (Annotation, array literal, const, ...)

@scheglov

https://codereview.chromium.org/2546993004

It was fixed, but I forgot to close it.


kubectl: enclose non-printing escape sequences with '[' ']'

fixes: #1232
solution: https://superuser.com/questions/333564/reverse-history-search-in-bash-followed-by-arrow-keys-causes-cursor-to-display-a
Signed-off-by: zhuangqh<EMAIL_ADDRESS>

/lgtm
/approve


add a function to head/db to return a list of all series ID's in Head

As part of rewriting the remote write (https://github.com/prometheus/prometheus/pull/4588) I'm keeping track of series records that we read out of the WAL so we can use the reference ID's when reading samples records to build the full metric for sending. However, at the moment that map of reference ID's to labels could grow endlessly. Within TSDB's Head, when truncation it trims series references that are no longer relevant. In the remote write changes, I can detect when a checkpoint is created, and make the call to get the series ID's that this PR adds.
Signed-off-by: Callum Styan<EMAIL_ADDRESS>

@gouthamve @krasi-georgiev
cc: @fabxc

@fabxc any thoughts here? Not sure if making this data available outside Head in this way is okay with you. Same with #401
Is any of the work for this: https://docs.google.com/document/d/1TEqqE_Stq04drhjSU1I7Ctmuy0dpsvlPL1AKxqEQoSg/edit?disco=AAAACHODOcM&ts=5b8826c0 going to be open source


Connect/disconnect during onStart/onStop or onResume/onPause?

Hi, according to Android documentation, onStart/onStop are the callbacks for when Activity starts to be visible/invisible, and onResume/onPause are for when Activity is in foreground or not. This is especially true for Android N in split screen mode, when Activity may be paused but still visible. With that in mind, should we connect/disconnect API client during onStart/onStop instead of onResume/onPause as in BaseDemoActivity?

I'd recommend onResume/onPause because you want to handle clean up here:
"onPause() is where you deal with the user leaving your activity. Most importantly, any changes made by the user should at this point be committed (usually to the ContentProvider holding the data)."
https://developer.android.com/reference/android/app/Activity
Also in cases of low memory the system might kill paused activities so you'd probably want to have cleaned up.


add firewall.tendrl.yml playbook

Based on
https://github.com/Tendrl/documentation/wiki/Tendrl-firewall-settings
Implements https://github.com/usmqe/usmqe-setup/issues/161

@dahorak I based this playbook on our firewall.skyrings.yml playbook where are tasks arranged in a similar way: https://github.com/usmqe/usmqe-setup/blob/master/roles/firewall-skyrings/tasks/main.yml
It seems more clear to me to set it this way with description containing name of service which port is set but I have no problem with your suggestions and I can change it.

Ok, I agree with this implementation (without some loop)... you are right that this will be more clearer.

@dahorak You are right that it does not make any sense to keep both firewall_tendrl.yml and firewall.tendrl.yml playbooks but I would keep firewall.tendrl.yml as the naming corresponds with firewall.skyrings.yml playbook which is not going anywhere. I would wait for @mbukatov's response and after that I will change it according to your suggestion.

@fbalak if you want to remove firewall_tendrl.yml and replace it by firewall.tendrl.yml, then you will  have to consider the content from the old file and add it to the new one. And also change the reference to this files in other playbooks (I'm aware of: ci_default_pre_setup.yml).

@dahorak's suggestion to preserve content of dropped firewall_tendrl.yml seems to make sense at first, but when I review it's actual content, I see that only firewalld installation and ceph firewall roles are there. I don't think that either of those is worth preserving at this moment. We don't test with ceph right now and if we want to keep the ceph tasks there, we should have gluster firewall setup there as well. But we don't do that right now.
For this reason, I would rather drop firewall_tendrl.yml as @fbalak did, but as @dahorak point's out, we still needs to change the name of firewall playbook in other playbooks.
Besides that, there is firewall_tendrl_workaround.yml which should be dropped as well.

@mbukatov yep, that's good point. I would maybe preserve also the installation of firewalld...
@fbalak so my suggestion is:

add installation of firewalld to the firewall.tendrl.yml playbook,
remove  firewall_tendrl.yml and firewall_tendrl_workaround.yml playbooks,
update ci_default_pre_setup.yml (change reference from firewall_tendrl.yml to firewall.tendrl.yml and remove workaround playbook).

@dahorak I agree with you. I would just remove firewall_tendrl_workaround.yml in separate PR as this PR resolves https://github.com/usmqe/usmqe-setup/issues/161 and another would resolve https://github.com/usmqe/usmqe-setup/issues/70


upbound: 0.21.0 -> 0.24.0

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://github.com/upbound/up/releases.
meta.description for upbound is: CLI for interacting with Upbound Cloud, Upbound Enterprise, and Universal Crossplane (UXP)
meta.homepage for upbound is: https://upbound.io
Updates performed

Golang update

To inspect upstream changes

Release on GitHub

Compare changes on GitHub

Impact
Checks done

built on NixOS
The tests defined in passthru.tests, if any, passed
found 0.22.1 with grep in /nix/store/xkka19ipiyddg847jngb2q2i4i4vb77z-upbound-0.22.1
found 0.22.1 in filename of file in /nix/store/xkka19ipiyddg847jngb2q2i4i4vb77z-upbound-0.22.1

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

1 total rebuild path(s)

1 package rebuild(s)

First fifty rebuilds by attrpath
upbound

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/xkka19ipiyddg847jngb2q2i4i4vb77z-upbound-0.22.1 \
  --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 upbound https://github.com/r-ryantm/nixpkgs/archive/933b7048f10f9c85b5fef7e6fa8a4ebd1bdc77fb.tar.gz

Or:
nix build github:r-ryantm/nixpkgs/933b7048f10f9c85b5fef7e6fa8a4ebd1bdc77fb#upbound

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/xkka19ipiyddg847jngb2q2i4i4vb77z-upbound-0.22.1
ls -la /nix/store/xkka19ipiyddg847jngb2q2i4i4vb77z-upbound-0.22.1/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 built:

upbound

Maintainer pings
cc @lucperkins for testing.

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://github.com/upbound/up/releases.
meta.description for upbound is: CLI for interacting with Upbound Cloud, Upbound Enterprise, and Universal Crossplane (UXP)
meta.homepage for upbound is: https://upbound.io
Updates performed

Golang update

To inspect upstream changes

Release on GitHub

Compare changes on GitHub

Impact
Checks done

built on NixOS
The tests defined in passthru.tests, if any, passed
found 0.24.0 with grep in /nix/store/hvc76q9zcizqdraivjmgbs3kzwg2cakj-upbound-0.24.0
found 0.24.0 in filename of file in /nix/store/hvc76q9zcizqdraivjmgbs3kzwg2cakj-upbound-0.24.0

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

1 total rebuild path(s)

1 package rebuild(s)

First fifty rebuilds by attrpath
upbound

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/hvc76q9zcizqdraivjmgbs3kzwg2cakj-upbound-0.24.0 \
  --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 upbound https://github.com/r-ryantm/nixpkgs/archive/c75bacb542058bcc1d35422dec4044af1c85d8e3.tar.gz

Or:
nix build github:r-ryantm/nixpkgs/c75bacb542058bcc1d35422dec4044af1c85d8e3#upbound

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/hvc76q9zcizqdraivjmgbs3kzwg2cakj-upbound-0.24.0
ls -la /nix/store/hvc76q9zcizqdraivjmgbs3kzwg2cakj-upbound-0.24.0/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 built:

upbound

Maintainer pings
cc @lucperkins for testing.


Make PathBuilder thread safe

#1869

Well at least the builds now pass. :sweat_smile:
My comment is indeed addressed now.
The only things I can think of is declaring ConcurrentMap instead. And using Maps.newConcurrentMap() (it doesn't use a different implementation, it only does so when you want special keys (soft, or weak)).
But other than that, I think that all points are addressed.

Looks great. PathBuilder should indeed be threadsafe.


Feature Request: Configable Slot Loss

Any possibility of a config option to allow  "Lose # unlocked slots on death", instead of losing all/nothing?  Or even just a third option for losing only 1 slot.

Added this feature with 2.1.0


capturing trim ranges is non-deterministic

I encountered this issue by accident while investigating a hang.  I've observed the behavior on Windows with NVIDIA graphics; I haven't attempted to reproduce on other platforms.
The attached trace is a retrace (i.e. a captured trace created by replaying the original trace) of vkcube:
gfxr.zip
Use that attached trace to create a trimmed trace, setting VK_LAYER_PATH to point at any particular GFXR build:
> set GFXRECON_CAPTURE_FRAMES=11-31
> set VK_INSTANCE_LAYERS=VK_LAYER_LUNARG_gfxreconstruct
> set VK_LAYER_PATH=...
> .../gfxrecon-replay.exe --sfa gfxrecon_capture_20220314T172704.gfxr
[gfxrecon] WARNING - Replay tool has detected that the capture layer is enabled
[gfxrecon] INFO - Settings Loader: Found option "GFXRECON_CAPTURE_FRAMES" with value "11-31"
[gfxrecon] INFO - Initializing GFXReconstruct capture layer
[gfxrecon] INFO -   GFXReconstruct Version 0.9.11-dev (dev:2426205)
[gfxrecon] INFO -   Vulkan Header Version 1.3.204
[gfxrecon] INFO - Recording graphics API capture to gfxrecon_capture_frames_11_through_31_20220314T17
5237.gfxr
[gfxrecon] INFO - Finished recording graphics API capture
Total time: 0.324695 seconds
Replay FPS: 307.981336 fps, 0.324695 seconds, 100 frames, framerange 1-100

Repeat the above gfxrecon-replay.exe command several times, to produce several trimmed traces.
Then examine the sizes of all the created trimmed traces:
> dir *.gfxr
 Volume in drive C has no label.
 Volume Serial Number is 4205-A61B

 Directory of C:\Users\lunarg\work\LunarG\gfxreconstruct

03/14/2022  05:27 PM           143,939 gfxrecon_capture_20220314T172704.gfxr
03/14/2022  05:52 PM            58,051 gfxrecon_capture_frames_11_through_31_20220314T175237.gfxr
03/14/2022  05:54 PM            58,064 gfxrecon_capture_frames_11_through_31_20220314T175436.gfxr
03/14/2022  05:54 PM            58,070 gfxrecon_capture_frames_11_through_31_20220314T175439.gfxr
03/14/2022  05:54 PM            58,034 gfxrecon_capture_frames_11_through_31_20220314T175441.gfxr
03/14/2022  05:54 PM            58,067 gfxrecon_capture_frames_11_through_31_20220314T175442.gfxr
               6 File(s)        434,225 bytes
               0 Dir(s)  3,660,963,663,872 bytes free

Note how every trimmed trace has a slightly different size.
Expectation is that all trimmed traces created with the same replay tool, capture layer, original trace, and settings will produce traces of the same size (though possibly different in meta-data, e.g. if the trace includes its capture time).

If it's helpful, I reproduced with:
> build\tools\replay\Release\gfxrecon-replay.exe --version
gfxrecon-replay.exe version info:
  GFXReconstruct Version 0.9.11-dev (dev:2426205)
  Vulkan Header Version 1.3.204

Working theory is that individual captures have slightly different data, like timestamps or pointer values.  On compression, those streams of data will result in slightly different compressed file sizes.

Working theory seems to be confirmed; after decompressing each capture with NONE, I see:
03/14/2022  06:09 PM           845,012 NONE-1.gfxr
03/14/2022  06:10 PM           845,012 NONE-2.gfxr
03/14/2022  06:10 PM           845,012 NONE-3.gfxr
03/14/2022  06:10 PM           845,012 NONE-4.gfxr
03/14/2022  06:11 PM           845,012 NONE-5.gfxr

Closing.


Last Buy price doesn't match with graphic arts of binance

Description
The Last Buy price doesn't match with the graphic arts value of binance. Its seems a bug ?
Screenshots
Here can you see that the boy have bought this coin with the price of 1.216

Within the Binance app i`ll can see the buy moment in time. Thats today at 8:42

But when i`ll look at this screenshot. The current time 8:42 doesnt match the buy value of 1.216?

This seems a bug

Something must be wrong.
Let me share my latest trading.
XRPDOWNUSDT buy order was placed at 30/Mar 15:17:13 and executed at 30/Mar 15:17:56

And my candle configuration was 2h/80

And the chart is showing the correct timestamp with the order

Something must be wrong (not with the bot)
What was your setting for candles?
1h with 100 candles.
But that doesn't match with the buy moment. The current value at that time seems around +/-1.165 not 1.216

@BramFr
If you click the arrow, then you can see trade details.
What time is that transaction filled?

Indeed looks like a valid buy...
Didn't know the arrow (trade details) function :)


container affinity

Currently there is service affinity like:
affinity:
  - service==mysql

But there are some (raw docker) cases when one would like to schedule a service in the same machine as where a container is running (see https://github.com/jeroenpeeters/docker-ssh)
Affinity setting container==mysql-1 would ensure this.

There is containeraffinity: https://github.com/kontena/kontena/blob/master/server/app/services/scheduler/filter/affinity.rb#L25
Should be documented... :)

hnnngggh


Release plan (next)

This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to master, this PR will be updated.
⚠⚠⚠⚠⚠⚠
master is currently in pre mode so this branch has prereleases rather than normal releases. If you want to exit prereleases, run changeset pre exit on master.
⚠⚠⚠⚠⚠⚠
Releases
<EMAIL_ADDRESS>Patch Changes

Updated dependencies [d4e1d36]:

<EMAIL_ADDRESS><EMAIL_ADDRESS>

<EMAIL_ADDRESS>Patch Changes

#166 d4e1d36 Thanks @aralroca! - Added jsx-dev-runtime to re-enable Bun support in development mode.

Updated dependencies []:

<EMAIL_ADDRESS>

<EMAIL_ADDRESS>Patch Changes

Updated dependencies [d4e1d36]:

<EMAIL_ADDRESS>

@aralroca when this PR gets merged, v4.0.0-next.3 will be released, would you mind trying it out to see if it gets fixed?


some changes

remove subprocess module
make config file optional
make python2 compatible
no longer start/enable service

And a few more small things.

Hi mdegans,
Thanks for your pull request.
I will address the changes individually:
Python 2 compatibility: it is nice to have compatibility with python 2.
However, both are pre-installed on the nano, so we should go with the more recent version, sice python 2 is no longer being used in development, and even parts of the linux distros are transitioning to python 3.
We don't want to build new software based on legacy systems.
Verdict: compatibility yes, but use python 3 as main.
Changes in readme: I realize you want to clean up the process, but removing information is not helpful.
Installation:
Similarly, i tried to containerize the config and bin files into folders to not clutter the high-level directories with non-obvious filenames.
Configuration:
I would prefer having a template that users can adapt, rather than having to create it themselves, which is more work.
I want the installation and configuration to be as simple as possible without much work or possibly for user error (that's why the try catch also catches JSONDecodeErrors etc...)
No longer start and enable service:
Your opinion may differ, but having users do this manually is just an additional step of work for the user, which is not necessary as I see it. I can imagine users accidentally skipping these steps and then wonder why it's not running or not automatically starting on boot. I don't see any reason to make this step manual.

Re: Python3 It's as you wish. The way it's written now, both work. I could have sworn it wasn't on my rootfs to begin with but I double checked and it you are right, it was.
Re: installation I changed the installation path because I had never seen a binary installed to a subfolder of /bin like that and as a result it precludes calling your script manually, without systemd. I forgot, actually it should really be /usr/local/bin
configuration It's as you prefer. As it's patched, it will fall back to a default without a configuration and if one is found, it attempts to load it. I didn't want to catch any JSONDecodeErrors because if there is one, it's clear what's wrong when the error is raised. Of course if you feel it's not clear enough you could...
except JSONDecodeError as err:
    raise RuntimeError("Config file is not valid json, please see someurl for example") from err

...and then the user gets a descriptive error with the full traceback.
re: starting/stopping
It's up to man :) it's your script. Like you said, it's personal preference

You're right about /usr/local/bin.
I will also add a more informative error when the config isn't loaded so users can see in the service status.
I'll take your feedback into account regarding these points, and I'm now closing this pull request.


Discussion after running the Jansen and Rit experiment

I have been running the algorithm for the Jansen and Rit model. The results are impressive (see outputs for different time lengths: 1/4 second, 1/2 second and 1 second)  although it required some manual tuning. Here is a list of things that I would like to understand better (bullet) and I would like to do (todo list):

If you look at the outputs in all the experiments, the mcmc sometimes gets stuck in local areas, giving a long sequence of rejection (all parameters get stuck), suggesting local maxima in the joint posterior distribution.  This may create problems for the adaptive method since when the sampler get stuck, the transition steps shrinks to 0.
For discussions: the kernel needs to be manually tuned depending on the length of observation we use.
I want to make sure that \sigma_y of both the real process and the auxiliary process updates when the chain accept a new position for \sigma_y. Is this specified just by this line?
[x] I did not understand how to turn off the adaptive scheme for the transition kernel of the mcmc
[x] I would like to try to give another prior to the parameters (it could fix the first bullet, smoothing the posterior density), can anybody guide me on doing that (I was just thinking at Gaussian priors)?
Thanks

moved on!


(v4) GLSLify error when using Webpack

Running my Pixi app after bundling with Webpack results in the following error:
browser.js:2 Uncaught Error: It appears that you're using glslify in browserify without its transform applied. Make sure that you've set up glslify as a source transform
Some research suggests this is a common problem among Webpack users. https://gist.github.com/mjackson/ecd3914ebee934f4daf4#gistcomment-1842689
This solution seems to work for some people, but I still haven't gotten it working. I'm posting an issue to see if we can come up with a common guideline for making Pixi work in a webpack app.
To reproduce the problem, simply make a webpack app with the following contents:
var PIXI = require('pixi.js');
var renderer = new PIXI.WebGLRenderer(256, 256);

Hi @Adam-Meisen ! Had this issue pop up a few times now and I have recently experienced it myself first hand! Time to get it fied I think 💃
Would replacing glsify with raw text do the trick you think? We are not using anything specific to glslify just yet..
Thoughts welcome! 👍

I only just discovered this library, so I'm afraid I really have no idea how gslify is used internally, but from some searching it seems like it's a very vague error message with many potential causes. What you suggested would probably work. Though ideally I'd like to figure out what causes this, sidestepping it entirely probably isn't a bad idea.
I still haven't managed to get it working, even with ify-loader, browserify-versionify, and glslify, though, so I've been using the cdn build of the library.

+1 to fix it, for now i use the pre-build version
`import PIXI from 'pixi.js/bin/pixi.js'

I'm not super familiar with Webpack. Could someone make a simple test project/repo that reproduces this issue so I could use to debug?

You can reproduce this with the following:

npm install pixi.js webpack

webpack.config.js
index.js
From the project's root folder:

webpack --config webpack.config.js

The resulting (projectroot)/scripts/bundle.js can be accessed in a web browser and will reproduce the glslify error.  Just wrote and tested it myself very quickly, if this doesn't work let me know and I'll try to fix it for you.

There's some issues closed here regarding this problem, such as https://github.com/pixijs/pixi.js/issues/2439#issuecomment-243820323. Not sure how PIXI could provide out-of-the-box compatibility without these custom configuration on host project though.
You can successfully require it using webpack by using the configuration below. I tested only on webpack 2.x, but should be fine on 1.x as well.
webpack.config.js:
  module: {
    loaders: [
      /// ...
      { test: /node_modules\/pixi\.js/, loader: 'ify' },
    ]
  },

package.json:
"devDependencies": {
  "browserify-versionify": "^1.0.6",
  "glslify": "^5.1.0",
  "ify-loader": "^1.0.3",
  "pixi.js": "^4.0.0"
}

Unfortunately, even with all of that, it still doesn't work for me.

@Adam-Meisen that's odd. Do you mind sharing your webpack.config.js and package.json so I can have a look? Cheers!

+1 I also have this issue.  I followed @stephanedemotte's temporary solution for now.

Hey, sorry about the wait, I went ahead and pared my project down to a reasonable minimum to make it as easy as possible to identify the problem.
As you can see in package.json, I've included all the modules that people have said are necessary to fix the problem.
    "browserify-versionify": "^1.0.6",
    "glslify": "^5.1.0",
    "ify-loader": "^1.0.3",

https://gist.github.com/Adam-Meisen/db219b1815633400844b350788a11a6e
Save the files to a directory and run webpack, then open index.html in a browser or serve it with webpack-dev-server.

@Adam-Meisen hey, looks good for me. Do you have any errors with that configuration? It worked here:

My Node and NPM version is the following:
$ node --version
v6.3.0
$ npm --version
3.10.3

I'm on Windows, running node 6.3.1 and npm 3.10.6.

Forgot to mention I'm using OSX. There must be something to do with this issue: https://github.com/stackgl/glslify/issues/77

@endel The above solution also not working for me - same issue as @Adam-Meisen.  Still getting the glslify error.

@xTiming can you confirm the operating system you're using?

@endel Windows 10, using Chrome as a browser.

@endel @xTiming Hi, guys. I found a way.
webpack.config.js
module: {
        loaders: [
            ...
            { test: path.resolve(__dirname, 'node_modules', 'pixi.js'), loader: 'ify' },
            ...
        ]
    },

The window separator is .
Unlike its os x.

It is seen as well in the window10.

The solution @kimorkim posted works well, but it messes up all the typings from DefinitelyTyped. Is there some way to alias 'pixi.js' to the binary version?

for typings, i refer to external js files.
  externals: {
      // require("jquery") is external and available
      //  on the global var jQuery
      "pixi.js": "PIXI"
  },

import * as PIXI from "pixi.js";

I created a sample share.
https://github.com/ossas/sudoku_example2
Tell me if you ever have a problem

Closing this for now since it seems like there are solutions in here. Additionally for v5 we will be dropping glslfy and probably browserify as well.


feat(fuselage): create ContextualBar component

Proposed changes (including videos or screenshots)

Create ContextualBar component on Fuselage

Issue(s)

Further comments

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


Availability of dev-kit?

Hello,
I wonder when the dev kit will be available. I would like to reference this when doing my research.
Thank you.

We plan to make it available next month.


Move catppuccin/vscode's flake here

catppuccin/vscode does not have a maintainer that is well versed in Nix anymore. As a result, I would very much appreciate if the maintenance burden of that flake can be moved into here.
I'm presently unsure of the pros and cons of this decision so I would appreciate if someone more inclined with Nix can comment down below what the pros and cons of moving the flake are 👍
Also let me know if this is a bad idea. It feels obvious to me that the flake should be moved but frankly Nix is a bundle of unknowns unknowns to me at the minute.
Thanks in advance as I know @isabelroses @getchoo is doing some preliminary work in order to support this.

Making this a port request to fit in with other issues 🥴
I think we'll be able to do something like this:
{
  config,
  lib,
  pkgs,
  ...
}:

let
  cfg = config.catppuccin.vscode;

  settingsFormat = pkgs.formats.json { };
in

{
  options.catppuccin.vscode = lib.ctp.mkCatppuccinOpt { name = "Visual Studio Code"; } // {
    settings = lib.mkOption {
      type = settingsFormat.type;
      default = { };
      apply = lib.mapAttrs' (name: lib.nameValuePair "catppuccin.${name}");
      description = ''
        Extra extension settings. See https://github.com/catppuccin/vscode?tab=readme-ov-file#catppuccin-settings
        for all options.
      '';
    };
  };

  config = lib.mkIf cfg.enable {
    programs.vscode = {
      extension = [ config.catppuccin.sources.vscode ];
      userSettings = lib.mkMerge [
        {
          "workbench.colorTheme" = "Catppuccin " + lib.ctp.toUpper cfg.flavor;
          "catppuccin.accentColor" = cfg.accent;
        }
        (lib.mkIf (cfg.settings != { }) cfg.settings)
      ];
    };
  };
}

This is going to be dependent on https://github.com/catppuccin/nix/pull/384 though, so putting this in the v2.0.0 milestone as well


Larger resolutions should not keep the full window of events in memory

Instead they should rely on snapshots of smaller resolutions. This means that we need to ensure that a resolution chain for is always composed of multiples of smaller resolutions. When writing we can then use a single ingest function instead of ingest-at-resolution which will get the list of snapshots, it will be up to ingest to propagate a smaller resolution snapshot to a larger one.
To keep code as readable as possible, volatiles should be tried out.

Alternatively, we could use monoids and finalizers. Most of the things are easily expressed as monoids, especially ones that we have at the moment.
For example, sum is a monoid that starts with 0 and sums each next item with itself. count would be an starting with 0 too and append operation will just increment the value of count by 1. min and max are kind of working out of the box as well.
Where it gets a bit harier, which is mean, we can still go with rolling mean: we calculate the rolling sum and rolling count, and here we'd need a finalizer, which would divide sum by count. This way it'd be possible to calculate everything in a constant space: you alwasys keep a single item in memory per aggregate which sets you free from the need to create rules for cascading ingestion. Moreover, mean of means would not be a correct mean. The rest of metrics should of course work.
For mor sophisticated cases, if we ever want to calculate the quartiles, there's P^2 algorithm: http://www.cs.wustl.edu/~jain/papers/ftp/psqr.pdf
Also, there's another interesting paper on the subject: http://www.vldb.org/pvldb/vol8/p702-tangwongsan.pdf

I think it's an expected trade-off to lose precision for higher resolutions and it is already the case for RRD, Whisper and friends. So having a mean of means is a compromise we can afford.

But I agree on moving to constant space, for mean, augment-snap was already built following this logic

I havent realized, current implementation is exactly what I have described, which is great!
agument-snap is using exactly that logic, you're absolutely right here. The only difference is that all the items for the snapshot are still kept in memory until the snapshot is flushed and augment-snap is only called when the old snapshot is yielded by the grouping function. We could improve it even further and augment-snap, only keeping the first window item timestamp and the intermediate state.

Yep, that's what i'm in the process of doing, it makes no sense to keep the window when we can augment in constant time. I'm also considering a different change, I'm thinking of having a separate snapshot thread, which would walk the list of buckets held in memory at every resolution interval which would produce a single coherent payload of snaps to send over to cassandra. This would make the workload on cassandra much more simple to deal with.

This is what I'm headed for for keeping values constant-time:
 (defrecord MetricMonoid [count minv maxv sum]
  MetricWriter
  (augment [this val]
    (assert (not (nil? val)))
    (MetricMonoid. (inc count)
                   (if minv (min minv val) val)
                   (if maxv (max maxv val) val)
                   (+ sum val)))
  (snapshot [this]
    (MetricSnapshot. (double / sum count) minv maxv sum)))

Wow <3 looks amazing

The remaining question will be (and would love your ideas on the subject @ifesdjeen): how do we guarantee safe access to the monoids.
This ties-in to the guarantees that disruptor can provide. For instance, if we knew that disruptor callbacks were always called on a single thread and did not overlap, we could make the monoids volatile and vswap! to apply augment. The alternative is to use an atom, which means going through the expensive CAS mechanism for every monoid augment call.
Regardless of the choice there, we would end up with the following structure:

A global non-blocking hashmap, indexed with metric paths, whose values whould be a Meric containing only a resolution chain: (defrecord Metric [resolutions])
In the above, :resolutions would be a list of (defrecord MetricResolutions [precision period slots]) where :slots would be a hash-map of timeslot to metric monoid.

Propagating a new metric to the engine would mean looking up the exec-plan for the metric name,
fetching or creating it in the global nbhm, then for each resolution, fetch or create the appropriate time slot to augment it with the new metric value.
If it doesn't prove to be too memory hungry we could devise an initial plan where:

The global metric list is an org.cliffc.high_scale_lib.NonBlockingHashMap instance.
Timeslots of a resolution are in an org.cliffc.high_scale_lib.NonBlockingHashMap instance.
Metric monoids would be stored in atoms.

If we can make sure that access to metric monoids are thread isolated, we could move on to using volatiles for the monoids.
(defrecord Metric [resolutions])

re: disruptor callbacks, since we're using it for the fast computation, I think the best is to avoid context switches on the :ingestq and have just one thread (I'm not sure if it's possible with Disruptor DSL, but we can always opt-out for using RingBuffer directly there).
If we decide that we need more parallelism, we can use multiple ring buffers each of which will guarantee it's own local order, and partition across them. This way we can use volatile since each ring buffer only has access to it's own data segment..
Other than that - your description and idea sounds very very good.

OK, thanks. to be very clear, what situation are we in right now? Does it just boil down to creating a disruptor with a threadpool of size 1 ?

I like the idea of sharding on several ringbuffers by the way, down the line. I'll start with a simple mechanism that uses nonblocking hashmaps and atoms, and we'll see how this performs, it will be easy to optomize hotspots from there.

Yes, threadpool of 1... Or writing a custom consumer that spins in it's own thread without using the Disruptor DSL.

I like the idea of sharding on several ringbuffers by the way, down the line.

Perfect!

And to close-off the initial discussion, this speaks against spilling over from resolution to resolution, but rather in favor of creating a monoid per metric/resolution tuple, as @ifesdjeen mentioned in the initial reply. I'll open a PR that builds on this discussion (hopefully shortly).


code usage

DO NOT REMOVE OR SKIP THE ISSUE TEMPLATE

[X] I understand that I will be blocked if I remove or skip any mandatory* field

Checklist

[X] I'm asking a question and not reporting a bug or requesting a feature
[X] I've looked through the README
[X] I've verified that I'm running yt-dlp version 2022.11.11 (update instructions) or later (specify commit)
[X] I've searched the bugtracker for similar questions including closed ones. DO NOT post duplicates
[X] I've read the guidelines for opening an issue

Please make sure the question is worded well enough to be understood
I want to get the best video and the best multiple custom audio, let him skip if there is no one, how can I make this code successful
D:\高清修复音乐录影带>yt-dlp --proxy http://<IP_ADDRESS>:10809 --merge-output-format mp4 --audio-multistreams --video-multistreams --compat-options no-live-chat --all-subs --embed-subs --add-metadata --external-downloader aria2c --external-downloader-args "-x 16 -k 1M" -o "%(title)s" -f (272/337/315/313/308/271/303/248)+(258/-i)+(380/-i)+(328/-i)+ba+140 https://www.youtube.com/watch?v=G1NfAJGPps8
WARNING: External Downloader arguments given without specifying name. The arguments will be given to aria2c
[youtube] G1NfAJGPps8: Downloading webpage
WARNING: [youtube] Unable to download webpage: HTTP Error 429: Too Many Requests
[youtube] G1NfAJGPps8: Downloading android player API JSON
[youtube] G1NfAJGPps8: Downloading iframe API JS
[youtube] G1NfAJGPps8: Downloading player c4225c42
[youtube] G1NfAJGPps8: Downloading web player API JSON
[youtube] G1NfAJGPps8: Downloading initial data API JSON
WARNING: [youtube] IncompleteRead(29394 bytes read, 1236 more expected). Retrying (1/3)...
[youtube] G1NfAJGPps8: Downloading initial data API JSON
WARNING: [youtube] IncompleteRead(25221 bytes read, 6248 more expected). Retrying (2/3)...
[youtube] G1NfAJGPps8: Downloading initial data API JSON
WARNING: [youtube] IncompleteRead(30544 bytes read, 529 more expected). Retrying (3/3)...
[youtube] G1NfAJGPps8: Downloading initial data API JSON
ERROR: [youtube] G1NfAJGPps8: Requested format is not available. Use --list-formats for a list of available formats
Provide verbose output that clearly demonstrates the problem

[ ] Run your yt-dlp command with -vU flag added (yt-dlp -vU <your command line>)
[ ] Copy the WHOLE output (starting with [debug] Command-line config) and insert it below

Complete Verbose Output
yt-dlp --merge-output-format mp4 --audio-multistreams --video-multistreams --compat-options no-live-chat --all-subs --embed-subs --add-metadata --external-downloader aria2c --external-downloader-args "-x 16 -k 1M" -o “%(title)s” -f (272/337/315/313/308/271/303/248)+(258/-i)+(380/-i)+(328/-i)+ba+140 https://www.youtube.com/watch?v=G1NfAJGPps8

Likely network issue your end (probably the proxy)

Likely network issue your end (probably the proxy)

I want the best video +258+328+380+251+140 and let it skip if there is no 258/328/380 audio, instead of giving an error that there is no clarity available

yt-dlp --proxy http://<IP_ADDRESS>:10809 --merge-output-format mp4 --audio-multistreams --video-multistreams --compat-options no-live-chat --all-subs --embed-subs --add-metadata --external-downloader aria2c --external-downloader-args "-x 16 -k 1M" -o “%(title)s” -i -f (272/337/315/313/308/271/303/248)+(258+328+380+256+251+140) https://www.youtube.com/watch?v=lnOjB7UcM04&list=PLOS_sffDs6Q7X2QuYkeCUHvpSNDm-cC8O&index=52
this link is worked！

yt-dlp --proxy http://<IP_ADDRESS>:10809 --merge-output-format mp4 --audio-multistreams --video-multistreams --compat-options no-live-chat --all-subs --embed-subs --add-metadata --external-downloader aria2c --external-downloader-args "-x 16 -k 1M" -o “%(title)s” -i -f (272/337/315/313/308/271/303/248)+(258+328+380+256+251+140) https://www.youtube.com/watch?v=cEvDvJBTJW4
this on is failed！
D:\高清修复音乐录影带>yt-dlp --proxy http://<IP_ADDRESS>:10809 --merge-output-format mp4 --audio-multistreams --video-multistreams --compat-options no-live-chat --all-subs --embed-subs --add-metadata --external-downloader aria2c --external-downloader-args "-x 16 -k 1M" -o "%(title)s" -i -f (272/337/315/313/308/271/303/248)+(258+328+380+256+251+140) https://www.youtube.com/watch?v=cEvDvJBTJW4
WARNING: External Downloader arguments given without specifying name. The arguments will be given to aria2c
[youtube] cEvDvJBTJW4: Downloading webpage
WARNING: [youtube] Unable to download webpage: <urlopen error EOF occurred in violation of protocol (_ssl.c:1131)>
[youtube] cEvDvJBTJW4: Downloading android player API JSON
[youtube] cEvDvJBTJW4: Downloading iframe API JS
[youtube] cEvDvJBTJW4: Downloading player c4225c42
WARNING: [youtube] Download of https://www.youtube.com/s/player/c4225c42/player_ias.vflset/en_US/base.js failed: IncompleteRead(586838 bytes read, 2090 more expected)
[youtube] cEvDvJBTJW4: Downloading tv embedded player API JSON
[youtube] cEvDvJBTJW4: Downloading player c4225c42
[youtube] cEvDvJBTJW4: Downloading web player API JSON
[youtube] cEvDvJBTJW4: Downloading web embedded client config
[youtube] cEvDvJBTJW4: Downloading web embedded player API JSON
[youtube] cEvDvJBTJW4: Downloading initial data API JSON
WARNING: [youtube] Remote end closed connection without response. Retrying (1/3)...
[youtube] cEvDvJBTJW4: Downloading initial data API JSON
WARNING: [youtube] Remote end closed connection without response. Retrying (2/3)...
[youtube] cEvDvJBTJW4: Downloading initial data API JSON
ERROR: [youtube] cEvDvJBTJW4: Requested format is not available. Use --list-formats for a list of available formats

let it skip if there is no 258/328/380 audio

Skip what?

let it skip if there is no 258/328/380 audio

Skip what?
Skip if not available

let it skip if there is no 258/328/380 audio

Skip what?

like this
(272/337/315/313/308/271/303/248)+258+328+380+251+140

Sorry, but I don't understand what u want. Unless you can explain better, I cannot help

I just want the best video and multiple audios with the highest bit rate. For example, YouTube has 384kb 5.1-channel audio, but few videos provide it. I want to keep all the 384KB audio, and skip it if it is not provided. Yes, just keep 128KB of audio

My current plan is like this (272/337/315/313/308/271/303)+(328/ba)+(380/140), but I can only keep two audios at most, otherwise it will be repeated, or else That is, when there is no available clarity, an error will be reported, and there is no way to download

Closed due to inactivity


[SPARK-26978][SQL][FOLLOWUP] Initialize date-time constants by foldable expressions

What changes were proposed in this pull request?
Reverted initialization of date-time constants in DateTimeUtils introduced by #23878. As a comment in Delta repo states, the compiler can do additional optimizations if values can be calculated at compile time: https://github.com/delta-io/delta/blob/master/src/main/scala/org/apache/spark/sql/delta/util/DateTimeUtils.scala#L63-L75
How was this patch tested?
This was tested by existing test suites.

@srowen @hvanhovell Please, review the PR.

Test build #107537 has started for PR 25116 at commit b3bd3a3.

Can one of the admins verify this patch?

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/testing-k8s-prb-make-spark-distribution-unified/12663/
Test PASSed.

Test build #107537 has finished for PR 25116 at commit b3bd3a3.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/107537/
Test PASSed.

Merging to master.


middleware proof of concept

Example Use:
serialize(compile(`...`), stringify) // default
serialize(compile(`...`), middleware([prefixer, stringify])) // middlware
function prefixer (current, callback) { if (current.type === DECLARATION) current.value = prefix(current.value) }

This tries to avoid a double pass.

@thysultan could you prepare a short writeup about the current middleware design? I have started to dig into it but would be a lot easier for me (and future plugin authors) if it would be documented at least a little bit

Thanks


Default main to Main in executables

Currently, if the user does not specify a main: in an executable section, they get an invalid .cabal file, since main-is is missing then.
Suggestion: default main: to Main.
Presumably, this should be done at the very end of the inference process to not interfere with #188, for instance.  Only if just before writing the .cabal file we don't have a main, supply main-is: Main.

For me there are a couple of open questions that I currently don't have the time to look into (none exhaustive):
1. There can be multiple executable sections. How would you handle this.

Each executable section that does not supply main: gets main: Main.
Of course you cannot drop main: if you have several executables in the same subdirectory.  But I think this is self-evident.

2. What exactly is the difference between `Main` and `Main.hs`. We already overload the meaning of `main`.

cabal understands Main, which it seems to expand to Main.hs or Main.lhs.  But hpack would not have to worry.

3. How to handle conditionals?

Not sure.  I would have to understand conditionals first. There isn't much documentation on them, at least TheFourShowcases do not use them a lot.  In a minimal implementation, one could abstain from the features if conditionals appear in executables or vice versa, this would probably still serve the other 99%.

4. Would you want to look at the file system at all?

Dunno, a MVP might not have to.

5. What is the weight benefit ratio from a users perspective?

It seems that DRY is the philosophy/religion of hpack, so these are higher goals that cannot be judged just by mundane economic calculations... :D

@andreasabel, main-is: Main is not accepted by Cabal (at least, with modern versions) - I suspect that was a bug that has been fixed.
@sol, main-is: Main.hs for an executable seems to me to be a sensible default, and consistent with the DRY philosophy. If you were to give it the green light, I would have a go at implementing it.

@mpilgrem would you be ok to do a proof of concept before I make a final call?
Things I would like to have answered
Dogfeed it on hpack itself
https://github.com/sol/hpack/blob/bb472cce37d477c8d4dd619d22cdbb4f956c3e82/package.yaml#L57
Presumably we can remove this line.  Is that an improvement?
What error messages does Cabal produce if there is no Main.hs
https://github.com/sol/hpack/blob/bb472cce37d477c8d4dd619d22cdbb4f956c3e82/package.yaml#L65
What does Cabal feedback to the user if you remove this line?

Hpack does not promote conventions.

I guess this should be added to the design principles.  Something along the lines of "Hpack is universal. It does not promote any particular set of conventions.".

On error messages:

No main-is (required since Cabal 1.0)

Cabal (the library) complains that No 'main-is' field found for executable foo-exe

main-is: Main.hs, no Main.hs
Cabal complains that can't find source for Main in . (or whatever directory)

main-is: Main.hs, no main exported by Main.hs
GHC complains that The IO action ‘main’ is not exported by module ‘Main’


What is the plan of 3.0 release?

Soon I will need this module for a new project and would like to know what is holding 3.0 release or when it will be released. I will use it with zend-expressive and would be a lot easier to do it than with 2.0

so if everyone agrees maybe someone can tag release?

"just did it"

thanks


Makes startup errors readable.

What's this PR do?
Fixes an issue with empty error text like this:

It makes it look like this:

How should this be reviewed?
heroku local
Relevant tickets
@deadlybutter, do you remember the ticket?
Checklist

[ ] Tested on staging.

cc @aaronschachter

Looks good to me!


terminus_font_ttf: 4.46.0 -> 4.47.0

Semi-automatic update generated by https://github.com/ryantm/nixpkgs-update tools. This update was made based on information from https://repology.org/metapackage/terminus-font-ttf/versions.
meta.description for terminus_font_ttf is: '"A clean fixed width TTF font"'.

Checks done (click to expand)

built on NixOS
/bin/sh passed the binary check.
1 of 1 passed binary check by having a zero exit code.
0 of 1 passed binary check by having the new version present in output.
found 4.47.0 with grep in /nix/store/35j1czsrvm0k505jxfh23nhpkm3z0q82-terminus-font-ttf-4.47.0
directory tree listing: https://gist.github.com/dceee0938c8dd8d33adb52393fd1636a
du listing: https://gist.github.com/844d8d76a9e1f5408b0d12acf09cbb66

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

4 total rebuild path(s)
1 package rebuild(s)
1 x86_64-linux rebuild(s)
1 i686-linux rebuild(s)
1 x86_64-darwin rebuild(s)
1 aarch64-linux rebuild(s)
First fifty rebuilds by attrpath
terminus_font_ttf

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/35j1czsrvm0k505jxfh23nhpkm3z0q82-terminus-font-ttf-4.47.0 \
  --option binary-caches 'https://cache.nixos.org/ https://r-ryantm.cachix.org/' \
  --option trusted-public-keys '
  r-ryantm.cachix.org-1:gkUbLkouDAyvBdpBX0JOdIiD2/DP1ldF3Z3Y6Gqcc4c=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(r-ryantm's Cachix cache is only trusted for this store-path realization.)
Or, build yourself:
nix-build -A terminus_font_ttf https://github.com/r-ryantm/nixpkgs/archive/bff3660f63f76fe42afb0b27b5f0782cd3328a99.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/35j1czsrvm0k505jxfh23nhpkm3z0q82-terminus-font-ttf-4.47.0
ls -la /nix/store/35j1czsrvm0k505jxfh23nhpkm3z0q82-terminus-font-ttf-4.47.0/bin

Whoops I only bumped one of these in #53238, thanks!


OCPBUGS-26115: Add Snyk file to exclude vendor directory on scan

Hello! This is a PR to add a snyk file to exclude the vendors folder while scanning the repo. Thanks!

/retest-required

/lgtm
/approve


Document that shareDeepLink does not work on mobile

This page should mention that shareDeepLink does not work on mobile platforms yet.

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 45541337-ecd7-5cf6-cbe4-3f0d2f39aa79
Version Independent ID: 6b4203f0-2844-06c9-eaa3-9cc03e6f76c0
Content: Create deep links - Teams
Content Source: msteams-platform/concepts/build-and-test/deep-links.md
Product: msteams
GitHub Login: @laujan
Microsoft Alias: lajanuar

Issue closed by PR#2383


Installed on date (Windows)

OS:
Windows 10
Issue Descriptions:
In the Control Panel, this application is listed as being installed in September of 2016.
Steps to Reproduce:
View the program in Uninstall or change a program section of the Control Panel on Windows.

OK, I have no idea how this app could cause this and it appears under the correct date on my machines.  I would suggest this is a bug in windows or possibly your computers date/time glitched out :+1:
This date is handled by core windows installer API's and not set by me :smile:

Very strange.  Definitely not my system and its the only app on my PC reflecting the wrong date.

@mikeytusa You can peruse through the code if you want, I don't think I even reference a date object once :laughing:
It's probably just a symptom of 1 of thousands of windows bugs :cactus:

No worries.  I'm not throwing blame.  Just hopefully helping to squash bugs.  Loving the project, great job! :)


Use a separate bullet for each completed task when using /review

Currently multiple completed items are just grouped together in a single paragraph, joined by "and", which doesn't make it easy to see each individual item. Would be great to break each completed task to a separate bullet so easier to take at a glance.
Also when I try to review past completed tasks (say for yesterday) I only get the first item.

The bullet points are per "work period" rather than per task, so you can see "in my first 25 minutes, I did Task A, Task B and Task C, and in my second 25 minutes, I did Task D and Task E". So this is very much by design.
Regarding the second point, can you create a separate issue with the steps to replicate, and I'll try and look into it? I've not been able to replicate it after a quick look.


Add strict types declarations

Codecov Report

Merging #6 into master will not change coverage.
The diff coverage is n/a.

@@             Coverage Diff             @@
##              master        #6   +/-   ##
===========================================
  Coverage     100.00%   100.00%
  Complexity       102       102
===========================================
  Files             17        17
  Lines            327       327
===========================================
  Hits             327       327

Flag
Coverage Δ
Complexity Δ

#unittests
100.00% <ø> (ø)
102.00 <ø> (ø)

Impacted Files
Coverage Δ
Complexity Δ

src/Executors/NginxConfigExecutor.php
100.00% <ø> (ø)
4.00 <0.00> (ø)

src/Executors/PhpExtensionsExecutor.php
100.00% <ø> (ø)
8.00 <0.00> (ø)

Continue to review full report at Codecov.

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


Fix typo

IPSec -> IPsec

@fabferri
Can you review the proposed changes?
IMPORTANT: When the changes are ready for publication, adding a #sign-off comment is the best way to signal that the PR is ready for the review team to merge.
#label:"aq-pr-triaged"
@MicrosoftDocs/public-repo-pr-review-team


No package available

Hi
Thanks for your cool script. It's exactly what I need for my personal project. Do you have any plans about releasing the package on npmjs?
It would really simplify development and deployment.
Thanks in advance
Michael

Thank you so much for opening up this issue and for the kind comment!
I've never created a package on npmjs, but I think this is a good idea.  I'm down.  :)
If you're willing to share your personal project, we could list it in our ReadMe.
Regardless, it would be great to hear more about it.
Hope that you have a nice day!

If you need any support let me know. I'm glad to help you set up your package, so you only need to publish it.
I plan to add a crossword plugin for editor.js. I think I'll open source the plugin as soon as it works.

That would be great!  If you setup the package, then I'll review it and submit it.  If you like, you can add the package to a new branch and do a pull request.
Also, adding the crossword plugin to editor.js sounds great!  I'm excited to see how it turns out.  :)
Thank you again!

Ok, I'll setup a package in the coming days and create a pull request.

Awesome!  :)

Still working on this.  :)

Looking forward to the package being available on npm. ;-)
Thank you for your work. In case you have questions or need additional support feel free to contact me again.

Package is now available!
Link: https://www.npmjs.com/package/crossword-layout-generator
Thank you again for all of your help!  :)


Improve warning description

Issue: #8759
I started with fixing the typos. I'm not sure how to reproduce the warning message. Is it enough to say:
warning(stylesWithOverrides[key], 'You are trying to override a style that does not exist: ${key}');

@agatac Thanks for working on this issue. It that we could display the path people are trying to override that is wrong: ${name}.${key} with the extra informations that it's key that is wrong, not the name.

If I understood you correctly, the final message would be:
warning(stylesWithOverrides[key], 'You are trying to override a style that does not exist. Check the key in ${name}.${key}');

Should I commit changes?

@agatac This sounds good to me. Or maybe:
warning(
  stylesWithOverrides[key],
  [
    'Material-UI: you are trying to override a style that does not exist.',
    `Fix the ${key} key of \`theme.overrides.${name}\`.`,
  ].join('\n')
);

Looks like I had to create a new pull request as this one is merged. #8783


False Positive on [sentry-core-common-1.8.0.jar] for CVE-2013-7286

False positive on library sentry-core-common-1.8.0.jar - reported as cpe:2.3:a:apache:sentry::::::::
<dependency>
    <groupId>org.apache.sentry</groupId>
    <artifactId>sentry-core-common</artifactId>
    <version>1.8.0</version>
</dependency>

CVE-2013-7286 , This vulnerability should be the product sentry of mobileiron .
This record in the software table may be wrong .

Agree with your analyses and brought the issue to the attention of the maintainers of the NVD to fix it at the source rather than with a suppression in DependencyCheck.
Thanks for reporting.

Resolved by an update of the affected software in the NVD.
Note however that Apache Sentry is in Apache's attic as of december 2020 so you may want to reconsider continued use (or fork the project to take it under maintenance)


handle errors better; this should stop all panics

its not the sexiest; but this made this library actually work for me consistently. These changes have been tested rigorously. The error checking was adjusted so that we actually return errors instead of swallowing them and continuing.

inactive


members list and viewing multiple images broken

don't remember when it happened but it was pretty recent
colors of people in the members list are lighter than normal

this also happens when there's multiple images in a message

this doesn't happen when there's one image, only when there's more than one

nice, that works. ty


Insert index directives with a Sphinx extension

Currently index directives are being inserted by sed before Sphinx builds anything. This is a hack job quick workaround for not having any metadata to indicate what should be indexed.
I couldn't find a Sphinx extension to create index directives based on the heading level, but perhaps there is one, or perhaps writing an extension to do it wouldn't be too hard.

#17 is pretty much the same thing, but as a Sphinx extension.


Scrolling through terminals

I use several terminals in VSCode and quite often I miss the feature that I can scroll on the dropdown menu to switch the terminals.

Is this some OS feature? What OS?

This is something that is available on some apps on elementaryOS.
I use multiple terminals all the time, so I would find it useful.

This issue seems to originate from an upstream component and is not something VSCode can fix by making a change to the code. As such, I will go ahead and close it. If you can identify the component that is causing the issue, please report it upstream:

for UI, OS integration: https://github.com/electron/electron
for Rendering: https://bugs.chromium.org/p/chromium/issues/list
for file IO: https://github.com/nodejs/node

Thanks for understanding.


SB-678: Implement Java-based tests for Nuget

@carlspring regarding this, maybe we need something more strict for checksum validation?

@carlspring, @sbespalov
I've got the same problem on my branch build and pull 299

I removed unnecessary code from the failed test here https://github.com/strongbox/strongbox/pull/299/commits/e26879c6b80bf0187335d66387aa31b85c5fba96 and PR passed. Unfortunately I wasn't able to find out what was the root cause.

@carlspring now the PR is ready.


Updating to docker 1.13-dev

Hey Ender - what about the tagging issue (I sent an email about this). The initial doc had a step for tagging the nano server image as nanoserver, and then step 4 is
docker run -it nanoserver cmd

The tag step was removed, from what I can tell step 4 no longer works as is, rather needs to be updated to:
docker run -it microsoft/nanoserver cmd

Also, will we update all docs to use 1.13-dev or only the Windows 10 doc?

@neilpeterson fixed. We only want Windows 10 on 1.13-dev, since Windows Server is on TP5 so things are still stable there as far as we know.


Clustered stacked bar when comparing scenarios

Hello all and thank you for the great work.
I have been using pyam the past couple of weeks and had no problem with anything until recently. I'm trying to produce a clustered stacked bar plot for comparing the same variables for the same year between different scenarios.
The code im using is:
data = df_nz.filter(**args, variable=("Emissions|CH4", "Emissions|HFC", "Emissions|N2O",
                                      "Emissions|PFC", "Emissions|SF6")).filter(region=("China"), keep=True)
ax = data.plot.bar(bars="variable", x="year", stacked=True, position=1.5, width=.2, cmap="tab20",linewidth=0.5,edgecolor = "black")

args2 = dict(scenario=("B"), year=[2015,2030, 2050])
data2 = df_nz.filter(**args2, variable=("Emissions|CH4", "Emissions|HFC", "Emissions|N2O",
                                      "Emissions|PFC", "Emissions|SF6")).filter(region=("China"), keep=True)
data2.plot.bar(ax=ax, bars="variable", x="year", stacked=True, position=-0.5, width=.2, cmap="tab20",linewidth=0.5,edgecolor = "black")

args3 = dict(scenario=("C"), year=[2015,2030, 2050])
data3 = df_nz.filter(**args3, variable=("Emissions|CH4", "Emissions|HFC", "Emissions|N2O",
                                      "Emissions|PFC", "Emissions|SF6")).filter(region=("China"), keep=True)
data3.plot.bar(ax=ax, bars="variable", x="year", stacked=True, position=0.5, width=.2, cmap="tab20",linewidth=0.5,edgecolor = "black")

plt.show()

So this produces a graph which is almost what I want but not exactly (see below). the 2015 values are the same for all scenarios so ideally only 1 of the 3 bars should be present there, but changing the 'year' for 2 of the scenarios overwrites the other one so you end up with 2030 and 2050 bars only.
Additionally the graph shows only the year on the x-axis. I would like to add the scenario per respective column name as well.
I have tried everything I could think on the above (and checked pyam's documentation as well) but nothing seems to work exactly how I would like to.
Any ideas or documentation on this I might have missed?
Thank you!

Thanks for the feedback, @gdafn, and happy to see that you find the package useful!
For this particular use case, you are pushing the pyam plotting gallery beyond its current scope: I don't think that multi-tiered x-axis labels are supported by the connection between pyam and matplotlib. If you want to explore how to implement this, I'm happy to review any PRs (or guide you in how to get started with submitting a feature extension to the repo).
As a quick-fix: you could create a new scenario (called "reference" or "history") which only has the 2015 values, and then you plot that reference scenario together with the scenario data for 2030 and 2050 - maybe this produces a figure closer to what you have in mind...

Thanks for the reply @danielhuppmann ! I will try to implement the quick-fix, I had already started on that indeed.

Please join our mailing list of Slack workspace for updates, new releases or discussing follow-up questions!
https://pyam-iamc.readthedocs.io/en/stable/contributing.html


NumberColumn.gini

This doesn't need to be part of the core codebase, but it would be nice to have it for the cookbook.

Migrated to agate-stats.


Make Configuration accept MetricsFactory, not Metrics

Metrics is an internal class, MetricsFactory is what we expect users to provide.

Coverage increased (+0.006%) to 98.571% when pulling 7ca6baf0d7c1c25676c9500f379efff6bd39b077 on accept-metrics-factory into 0fba520cb5694aa0f6ca087f82966697e6575f91 on master.

Coverage increased (+0.006%) to 98.571% when pulling 7ca6baf0d7c1c25676c9500f379efff6bd39b077 on accept-metrics-factory into 0fba520cb5694aa0f6ca087f82966697e6575f91 on master.


i18n support

This great theme definitely needs internationalization.
I like how the language selection with a dropdown is done here , although the implementation (see the source code here) is pretty inelegant and would work only for the landing page. Also, language names might be replaced by flags or 2-letter abbreviations, and "Other languages" might be replaced by currently active language flag/abbreviation.
The implementation would require a long-running pull request and joint efforts for:

i18n:

extract all the strings
fix the link referencing
change the configuration file format for the landing page, with backward compatibility
adopt the UI for RTL support (optional at the first steps)

l10n:

add localization for a minimal set of languages

To proceed with that, I would ask the community if some efforts have already been put into it, and if any pitfalls have been found with that.
Also, I would like to know who else would contribute.

I second this request.  It will be a great addition.

Hello! I would contribute to the implementation of language support.


Add ability to add orders

Orders are placed by customer and are received by tenants. Right?

Yes. But for now, let's aim for a simple workflow where a tenant back office user would create the order.


Need help with using HandOff

@cleemullins @DDEfromOR
How to initiate agent transfer from BOT?
I executed,  https://directline.botframework.com/v3/directline/conversations
but getting this error.
also i see hanfoff BOt sample  connecting to,  {http://localhost:1661/v3/conversations/e3ea8aa1-e16b-11e9-a476-af445dff8373|livechat/handoff} and am not sure how to setup this. which project i should run to enable this URL to respond. I dont have this running in my local and not sure it is.

Hi @arunprasathv,
You can use the library to pass the handoff request to an app connected to your bot via Direct Line APIs. Normally that app would be aware of the concept of a human agent: when handoff request is received, it should interpret that as a request to redirect all subsequent messages with that conversation ID to a human agent. That is the work that you need to do in your app.
Use client-facing Direct Line APIs to start a conversation (POST to v3/directline/conversations), then post an activity to that conversation (POST to v3/directline/conversations/{conversation-id}/activities) with a certain keyword, such as 'human'. Your bot will then recognize that and initiate the handoff, as shown here.
Call v3/directline/conversations/{conversation-id}/activities to retrieve messages sent to your app. One of the messages will be of type 'handoff' containing the payload from the call (context and transcript) and conversation ID. It should look like this:
{
            "type": "handoff",
            "id": "xxx",
            "timestamp": "2019-09-27T16:54:56.7548357Z",
            "channelId": "directline",
            "from": {
                "id": "mybot"
            },
            "conversation": {
                "id": "xxx"
            },
            "channelData": {
                "Skill": "credit cards",
                "MSCallerId": "CCI"
            },
            "transcript": {
                // skipped
            }

Information provided above. Closing due to inactivity.
Please feel free to reopen if the issue persists.


[dialog] add a new property : contentInnerStyle

@hai-cea I have taken your returns into account.

Thanks @oliviertassinari


Saved both raw and processed textract output

Overview
Textract's processed output seems to be missing some form key-value data from the PDF. This PR saves both the processed and raw response from Textract to help debug the issue.
scripts/process_pdfs.py generates two JSON files for each PDF: the raw response from Amazon Textract and the processed key-value form data. Respectively, they are stored in textract_responses/ and final/.
Testing Instructions

Navigate to final/ and examine the script's output

Handles #10

thanks @antidipyramid! I'll handle the merge conflict!


closes #635: added ga4gh.utils.seqfetcher to fetch remote sequences by accession and interval

NOTE: I interpreted this issue (#635) as adding the sequence fetching functionality. Will work on #719 next to use this code to update test data.

This is useful code, but I have difficulty seeing it merged with minor modifications... this functionality is probably only relevant in the scripts directory (especially in download_data.py which is the module which is responsible for downloads at present), i.e. not as part of the main ga4gh package

This code is super useful, and I like it a lot. The style is clear, and I have no trouble following it. However, it doesn't agree with some of the stylistic conventions that we've adopted and worked hard to maintain, so I'd be uncomfortable about merging the code in as it is. There's also some new additions in terms of doctests, which we'd need to integrate into CI to be truly useful. Some specific points:

Since we only need the code for one script, I suggest we just absorb all the code into this script. We can always migrate the code into the central code base if we need to fetch sequences in the future. I'm not quite as concerned about maintaining uniformity of style in the scripts.

As we are planning a conversion to snake case in the near future, I could be persuaded to make an exception and include it in to download_data.py.

What do you think @dcolligan? I'm not quite sure where to put the unit tests and what to do with the doctests.
Anyway, thanks for this @reece, it is a great addition and we'll definitely use some version of this code.

Some of the functionality in scripts is getting really built out, and could use tests of its own... this contribution definitely fits under that heading.  Whether we want to run those tests every time as part of the core test suite is debatable; I'd lean towards no.  That goes double if we relax the requirements of the test suite to be able to call out over the network.

I agree with Danny's comments and that the code doesn't belong in server proper. Please reject this PR.
Re: doctests: Since this code is not core and unlikely to change, the doctests (as invoked with python seqfetcher.py) are useful for development. For the failure reason's Jerome mentioned, they should not be run with package testing.
I did take a look at download_data.py, but couldn't grok what it was doing on the first pass and therefore haven't attempted a second take at these issues.
Options: Sketch what you think should happen, and I'll take a stab. Or, feel free to reassign the issues to yourselves and use this code (or not). Your choice.

OK, I'll close this PR then. I'll play with the code here and create a new issue, with an eye to reusing as much as possible of this framework. I'll @mention you @reece, and you can have first refusal on tackling it. (It might take a few days to materialise, as I'm at a conference at the moment.)


Why my html report shows so simple, not colorful likes your ReadMe？Do I need to specify an html template？

HtmlTestRunner version: 1.2.1
Python version: 3.7
Operating System: windows / centos 7.6

Description
too simple, not colorful like ReadMe.
it is onle white.
What I Did
    runner = HtmlTestRunner.HTMLTestRunner(
        output=test_edge_site.test_dir + '/output/unittest/html', combine_reports=True, report_name='test_detail',
        add_timestamp=False)
    runner.run(suite)

Paste the command(s) you ran and the output.
If there was a crash, please include the traceback here.

pic?

As far as I can see, the HtmlTestRunner take Jinjia as a default template.


Feature: performance improvements + package moving

Widget initialization without waiting for DOMContentLoaded event.
INP metric performance improvement.
Moved package to @68publishers/cookie-consent

💡 Also merge https://github.com/68publishers/cookie-consent/pull/83 with the new release

How did you manage to improve INP? Did you setTimeout on some function call?

@bennetsadyba Basically, yes. I wrapped in setTimeout() actions that are executed when the consent is given.
In particular, this delays communication with GTM until the next frame, so the cookie bar can hide immediately - faster response.


[Question / Documentation] Does it work on Linux + mono too? Could the readme mention this?

Would it be possible to add "supported platforms" or something in the main readme, to indicate whether
this works on linux as well? If it were to work on both windows and linux this would be quite ideal. I could
use gnuplot but I found it to be not hugely user friendly, so I am looking for alternatives. I use linux primarily
though, only my second computer uses Win10 and I am rarely using it usually.

Hi @rubyFeedback,
Thanks for pointing this out!
ScottPlot does work on Linux (and MacOS)
However, this information should be more explicitly stated. I'll add a note to the primary readme as you suggest.
Note that Linux and MacOS may require a couple extra setup steps:

https://scottplot.net/faq/dependencies/


(PUP-8528) Remove write only yaml node terminus

The write_only_yaml node terminus was used to "determine the list of
nodes that the master knows about"[1] and predated widespread puppetdb
adoption. The write_only_yaml has been deprecated[2] since 4.10.5, and
this commit removes it.
Note this should result in a puppetserver speedup as it no longer will
need to serialize node data as YAML to disk.
[1] https://projects.puppetlabs.com/issues/16753
[2] https://tickets.puppetlabs.com/browse/PUP-6060

jenkins please test this

CLA signed by all contributors.


Hyphenation algorithm not UTF8-clean

I haven't looked into how this got allowed yet, but I just spotted a stray single-character hyphenation in a Turkish book I'm reviewing.

Also worth reviewing is whether breaking after a single syllable ending in a soft-g is allowed. It might be but I have an idea it's less than ideal:

Looks like the first issue is a Unicode bug. In fact, the _hyphenate subroutine assumes that each character in the string is a byte long. The minimum left-hand of the string to be maintained before hyphenation is two bytes, but two bytes here is one character.

SILE now gives the same answers as TeX does. TeX: öǧ-re-ni-yo-ruz İmanlı
This is SILE 0.9.4-unreleased
> showHyphenationPoints("öǧreniyoruz", "tr")
"öǧ-re-ni-yo-ruz"
> showHyphenationPoints("İmanlı", "tr")
"İmanlı"