Cannot pull image apache/spark-py:v3.3.2 in peer pod vm using CAA

When trying to run the image apache/spark-py:v3.3.2 with CAA the kata-agent cannot pull the image inside the peer pod vm. CAA shows these errors:
...
2023/04/05 04:17:56 [adaptor/proxy] CreateContainer: failed to call PullImage, probably because the image has already been pulled. ignored: rpc error: code = Internal desc = failed to handle layer: hasher sha256 : channel: send failed "SendError(..)"
2023/04/05 04:18:00 [adaptor/proxy] CreateContainer: failed to call PullImage, probably because the image has already been pulled. ignored: rpc error: code = Internal desc = failed to handle layer: hasher sha256 : unpack destination "/run/image/layers/sha256_844c2c952c2d7eab58fbb2f5ce42b2ca7dbaa0bd71b28bc12368c9966631a9d7" already exists
...

The pod goes into CrashLoopBackOff:
$ kubectl get pods
NAME         READY   STATUS             RESTARTS      AGE
spark-test   0/1     CrashLoopBackOff   2 (84s ago)   5m32s

Here is the config to deploy the pod:
apiVersion: v1
kind: Pod
metadata:
  name: spark-test
  namespace: default
spec:
  runtimeClassName: kata
  containers:
  - name: spark-test
    image: apache/spark-py:v3.3.2

CAA daemonset logs:
2023/04/05 04:17:48 [adaptor/proxy] CreateContainer: containerID:91bc38697f6011ff5a046ee1b250a728f1a03db3d20b9c2f35787caa35f317ef
2023/04/05 04:17:48 [adaptor/proxy]     annotations:
2023/04/05 04:17:48 [adaptor/proxy]         io.kubernetes.cri.container-name: spark-test
2023/04/05 04:17:48 [adaptor/proxy]         io.kubernetes.cri.sandbox-id: 5f11913cdc19aa93c0bf3443eb3953d155d0e6947911554679095f2941fee1b2
2023/04/05 04:17:48 [adaptor/proxy]         io.kubernetes.cri.container-type: container
2023/04/05 04:17:48 [adaptor/proxy]         io.katacontainers.pkg.oci.container_type: pod_container
2023/04/05 04:17:48 [adaptor/proxy]         io.kubernetes.cri.sandbox-namespace: default
2023/04/05 04:17:48 [adaptor/proxy]         io.kubernetes.cri.image-name: docker.io/apache/spark-py:v3.3.2
2023/04/05 04:17:48 [adaptor/proxy]         io.kubernetes.cri.sandbox-name: spark-test
2023/04/05 04:17:48 [adaptor/proxy]         io.kubernetes.cri.sandbox-uid: 4e020719-3dbc-4e95-9531-a9f1a95303a4
2023/04/05 04:17:48 [adaptor/proxy]         io.katacontainers.pkg.oci.bundle_path: /run/containerd/io.containerd.runtime.v2.task/k8s.io/91bc38697f6011ff5a046ee1b250a728f1a03db3d20b9c2f35787caa35f317ef
2023/04/05 04:17:48 [adaptor/proxy]     mounts:
2023/04/05 04:17:48 [adaptor/proxy]         destination:/proc source:proc type:proc
2023/04/05 04:17:48 [adaptor/proxy]         destination:/dev source:tmpfs type:tmpfs
2023/04/05 04:17:48 [adaptor/proxy]         destination:/dev/pts source:devpts type:devpts
2023/04/05 04:17:48 [adaptor/proxy]         destination:/dev/mqueue source:mqueue type:mqueue
2023/04/05 04:17:48 [adaptor/proxy]         destination:/sys source:sysfs type:sysfs
2023/04/05 04:17:48 [adaptor/proxy]         destination:/sys/fs/cgroup source:cgroup type:cgroup
2023/04/05 04:17:48 [adaptor/proxy]         destination:/etc/hosts source:/run/kata-containers/shared/containers/91bc38697f6011ff5a046ee1b250a728f1a03db3d20b9c2f35787caa35f317ef-56d825e176a3a8cc-hosts type:bind
2023/04/05 04:17:48 [adaptor/proxy]         destination:/dev/termination-log source:/run/kata-containers/shared/containers/91bc38697f6011ff5a046ee1b250a728f1a03db3d20b9c2f35787caa35f317ef-7f3cf25df4117d5e-termination-log type:bind
2023/04/05 04:17:48 [adaptor/proxy]         destination:/etc/hostname source:/run/kata-containers/shared/containers/91bc38697f6011ff5a046ee1b250a728f1a03db3d20b9c2f35787caa35f317ef-ae86af1ce7e34e11-hostname type:bind
2023/04/05 04:17:48 [adaptor/proxy]         destination:/etc/resolv.conf source:/run/kata-containers/shared/containers/91bc38697f6011ff5a046ee1b250a728f1a03db3d20b9c2f35787caa35f317ef-e6df0557895e703a-resolv.conf type:bind
2023/04/05 04:17:48 [adaptor/proxy]         destination:/dev/shm source:/run/kata-containers/sandbox/shm type:bind
2023/04/05 04:17:48 [adaptor/proxy]         destination:/var/run/secrets/kubernetes.io/serviceaccount source:/run/kata-containers/shared/containers/91bc38697f6011ff5a046ee1b250a728f1a03db3d20b9c2f35787caa35f317ef-292303cda75db44d-serviceaccount type:bind
2023/04/05 04:17:48 [adaptor/proxy] getImageName: got image from annotations: docker.io/apache/spark-py:v3.3.2
2023/04/05 04:17:48 [adaptor/proxy] CreateContainer: calling PullImage for "docker.io/apache/spark-py:v3.3.2" before CreateContainer (cid: "91bc38697f6011ff5a046ee1b250a728f1a03db3d20b9c2f35787caa35f317ef")
2023/04/05 04:17:49 [adaptor/proxy] CreateContainer: failed to call PullImage, probably because the image has already been pulled. ignored: rpc error: code = Internal desc = failed to handle layer: hasher sha256 : channel: send failed "SendError(..)"
2023/04/05 04:17:50 [adaptor/proxy] CreateContainer: failed to call PullImage, probably because the image has already been pulled. ignored: rpc error: code = Internal desc = failed to handle layer: hasher sha256 : channel: send failed "SendError(..)"
2023/04/05 04:17:50 [adaptor/proxy] CreateContainer: failed to call PullImage, probably because the image has already been pulled. ignored: rpc error: code = Internal desc = failed to handle layer: hasher sha256 : channel: send failed "SendError(..)"
2023/04/05 04:17:51 [adaptor/proxy] CreateContainer: failed to call PullImage, probably because the image has already been pulled. ignored: rpc error: code = Internal desc = failed to handle layer: hasher sha256 : channel: send failed "SendError(..)"
2023/04/05 04:17:54 [adaptor/proxy] CreateContainer: failed to call PullImage, probably because the image has already been pulled. ignored: rpc error: code = Internal desc = failed to handle layer: hasher sha256 : channel: send failed "SendError(..)"
2023/04/05 04:17:56 [adaptor/proxy] CreateContainer: failed to call PullImage, probably because the image has already been pulled. ignored: rpc error: code = Internal desc = failed to handle layer: hasher sha256 : channel: send failed "SendError(..)"
2023/04/05 04:18:00 [adaptor/proxy] CreateContainer: failed to call PullImage, probably because the image has already been pulled. ignored: rpc error: code = Internal desc = failed to handle layer: hasher sha256 : unpack destination "/run/image/layers/sha256_844c2c952c2d7eab58fbb2f5ce42b2ca7dbaa0bd71b28bc12368c9966631a9d7" already exists
2023/04/05 04:18:07 [adaptor/proxy] CreateContainer: failed to call PullImage, probably because the image has already been pulled. ignored: rpc error: code = Internal desc = failed to handle layer: hasher sha256 : channel: send failed "SendError(..)"
2023/04/05 04:18:21 [adaptor/proxy] CreateContainer: failed to call PullImage, probably because the image has already been pulled. ignored: rpc error: code = Internal desc = failed to handle layer: hasher sha256 : unpack destination "/run/image/layers/sha256_a274d4cf0f7fcca90eb88d5dacafa75b0b78b1c53f92b3e0c80be16583f4dfc5" already exists
2023/04/05 04:18:47 [adaptor/proxy] CreateContainer: failed to call PullImage, probably because the image has already been pulled. ignored: rpc error: code = Internal desc = failed to handle layer: hasher sha256 : channel: send failed "SendError(..)"
2023/04/05 04:18:47 [adaptor/proxy] PullImage fails: All attempts fail:
#1: rpc error: code = Internal desc = failed to handle layer: hasher sha256 : channel: send failed "SendError(..)"
#2: rpc error: code = Internal desc = failed to handle layer: hasher sha256 : channel: send failed "SendError(..)"
#3: rpc error: code = Internal desc = failed to handle layer: hasher sha256 : channel: send failed "SendError(..)"
#4: rpc error: code = Internal desc = failed to handle layer: hasher sha256 : channel: send failed "SendError(..)"
#5: rpc error: code = Internal desc = failed to handle layer: hasher sha256 : channel: send failed "SendError(..)"
#6: rpc error: code = Internal desc = failed to handle layer: hasher sha256 : channel: send failed "SendError(..)"
#7: rpc error: code = Internal desc = failed to handle layer: hasher sha256 : unpack destination "/run/image/layers/sha256_844c2c952c2d7eab58fbb2f5ce42b2ca7dbaa0bd71b28bc12368c9966631a9d7" already exists
#8: rpc error: code = Internal desc = failed to handle layer: hasher sha256 : channel: send failed "SendError(..)"
#9: rpc error: code = Internal desc = failed to handle layer: hasher sha256 : unpack destination "/run/image/layers/sha256_a274d4cf0f7fcca90eb88d5dacafa75b0b78b1c53f92b3e0c80be16583f4dfc5" already exists
#10: rpc error: code = Internal desc = failed to handle layer: hasher sha256 : channel: send failed "SendError(..)"

Kata-agent logs:
Apr 05 04:14:41 podvm-spark-test-5f11913c kata-agent[736]: {"msg":"Attestation Agent already running","level":"INFO","ts":"2023-04-05T04:14:41.214738181Z","pid":"736","subsystem":"rpc","source":"agent","name":"kata-agent","version":"0.1.0"}
Apr 05 04:14:41 podvm-spark-test-5f11913c kata-agent[736]: {"msg":"image_client.config.auth set to: true","level":"INFO","ts":"2023-04-05T04:14:41.214784197Z","name":"kata-agent","version":"0.1.0","pid":"736","subsystem":"rpc","source":"agent"}
Apr 05 04:14:41 podvm-spark-test-5f11913c kata-agent[736]: {"msg":"enable_signature_verification set to: false","level":"INFO","ts":"2023-04-05T04:14:41.214823621Z","pid":"736","version":"0.1.0","name":"kata-agent","source":"agent","subsystem":"rpc"}
Apr 05 04:14:41 podvm-spark-test-5f11913c kata-agent[736]: {"msg":"pull image \"d130063b369633459a88c0e576cb13b01f81e1502c6b98c03147e5d8baa08cd5\", bundle path \"/run/kata-containers/d130063b369633459a88c0e576cb13b01f81e1502c6b98c03147e5d8baa08cd5\"","level":"INFO","ts":"2023-04-05T04:14:41.2148607Z","name":"kata-agent","source":"agent","subsystem":"rpc","version":"0.1.0","pid":"736"}
Apr 05 04:14:41 podvm-spark-test-5f11913c kata-agent[1232]: [2023-04-05T04:14:41Z ERROR attestation_agent::rpc::getresource::grpc] Call AA-KBC to get resource failed: Resource path offline_fs_kbc must start with '/'
Apr 05 04:14:41 podvm-spark-test-5f11913c kata-agent[736]: {"msg":"pull and unpack image \"docker.io/apache/spark-py:v3.3.2\", cid: \"d130063b369633459a88c0e576cb13b01f81e1502c6b98c03147e5d8baa08cd5\", with image-rs failed with \"failed to handle layer: hasher sha256 : unpack destination \\\"/run/image/layers/sha256_12cca292b13cb58fadde25af113ddc4ac3b0c5e39ab3f1290a6ba62ec8237afd\\\" already exists\". ","level":"ERRO","ts":"2023-04-05T04:14:41.830237139Z","source":"agent","subsystem":"rpc","name":"kata-agent","pid":"736","version":"0.1.0"}
Apr 05 04:15:07 podvm-spark-test-5f11913c kata-agent[736]: {"msg":"Attestation Agent already running","level":"INFO","ts":"2023-04-05T04:15:07.524971984Z","name":"kata-agent","pid":"736","version":"0.1.0","subsystem":"rpc","source":"agent"}
Apr 05 04:15:07 podvm-spark-test-5f11913c kata-agent[736]: {"msg":"image_client.config.auth set to: true","level":"INFO","ts":"2023-04-05T04:15:07.52500195Z","subsystem":"rpc","version":"0.1.0","pid":"736","source":"agent","name":"kata-agent"}
Apr 05 04:15:07 podvm-spark-test-5f11913c kata-agent[736]: {"msg":"enable_signature_verification set to: false","level":"INFO","ts":"2023-04-05T04:15:07.525026586Z","source":"agent","subsystem":"rpc","pid":"736","name":"kata-agent","version":"0.1.0"}
Apr 05 04:15:07 podvm-spark-test-5f11913c kata-agent[736]: {"msg":"pull image \"d130063b369633459a88c0e576cb13b01f81e1502c6b98c03147e5d8baa08cd5\", bundle path \"/run/kata-containers/d130063b369633459a88c0e576cb13b01f81e1502c6b98c03147e5d8baa08cd5\"","level":"INFO","ts":"2023-04-05T04:15:07.525053267Z","source":"agent","subsystem":"rpc","pid":"736","version":"0.1.0","name":"kata-agent"}
Apr 05 04:15:07 podvm-spark-test-5f11913c kata-agent[1232]: [2023-04-05T04:15:07Z ERROR attestation_agent::rpc::getresource::grpc] Call AA-KBC to get resource failed: Resource path offline_fs_kbc must start with '/'
Apr 05 04:15:07 podvm-spark-test-5f11913c kata-agent[736]: {"msg":"rpc call from shim to agent: \"copy_file\"","level":"INFO","ts":"2023-04-05T04:15:07.802989422Z","source":"agent","subsystem":"rpc","name":"kata-agent","pid":"736","version":"0.1.0"}
Apr 05 04:15:07 podvm-spark-test-5f11913c kata-agent[736]: {"msg":"rpc call from shim to agent: \"copy_file\"","level":"INFO","ts":"2023-04-05T04:15:07.804759519Z","version":"0.1.0","source":"agent","name":"kata-agent","pid":"736","subsystem":"rpc"}
Apr 05 04:15:07 podvm-spark-test-5f11913c kata-agent[736]: {"msg":"rpc call from shim to agent: \"copy_file\"","level":"INFO","ts":"2023-04-05T04:15:07.806288003Z","name":"kata-agent","source":"agent","pid":"736","version":"0.1.0","subsystem":"rpc"}
Apr 05 04:15:07 podvm-spark-test-5f11913c kata-agent[736]: {"msg":"rpc call from shim to agent: \"copy_file\"","level":"INFO","ts":"2023-04-05T04:15:07.807788575Z","subsystem":"rpc","pid":"736","version":"0.1.0","source":"agent","name":"kata-agent"}
Apr 05 04:15:07 podvm-spark-test-5f11913c kata-agent[736]: {"msg":"rpc call from shim to agent: \"copy_file\"","level":"INFO","ts":"2023-04-05T04:15:07.809162169Z","source":"agent","version":"0.1.0","subsystem":"rpc","name":"kata-agent","pid":"736"}
Apr 05 04:15:07 podvm-spark-test-5f11913c kata-agent[736]: {"msg":"rpc call from shim to agent: \"copy_file\"","level":"INFO","ts":"2023-04-05T04:15:07.81072098Z","version":"0.1.0","name":"kata-agent","source":"agent","pid":"736","subsystem":"rpc"}
Apr 05 04:15:07 podvm-spark-test-5f11913c kata-agent[736]: {"msg":"rpc call from shim to agent: \"copy_file\"","level":"INFO","ts":"2023-04-05T04:15:07.812207495Z","name":"kata-agent","source":"agent","version":"0.1.0","pid":"736","subsystem":"rpc"}
Apr 05 04:15:07 podvm-spark-test-5f11913c kata-agent[736]: {"msg":"rpc call from shim to agent: \"copy_file\"","level":"INFO","ts":"2023-04-05T04:15:07.813477976Z","source":"agent","subsystem":"rpc","pid":"736","name":"kata-agent","version":"0.1.0"}
Apr 05 04:15:07 podvm-spark-test-5f11913c kata-agent[736]: {"msg":"rpc call from shim to agent: \"copy_file\"","level":"INFO","ts":"2023-04-05T04:15:07.814862401Z","subsystem":"rpc","version":"0.1.0","pid":"736","name":"kata-agent","source":"agent"}
Apr 05 04:15:07 podvm-spark-test-5f11913c kata-agent[736]: {"msg":"rpc call from shim to agent: \"copy_file\"","level":"INFO","ts":"2023-04-05T04:15:07.816078169Z","source":"agent","name":"kata-agent","version":"0.1.0","pid":"736","subsystem":"rpc"}
Apr 05 04:15:07 podvm-spark-test-5f11913c kata-agent[736]: {"msg":"rpc call from shim to agent: \"copy_file\"","level":"INFO","ts":"2023-04-05T04:15:07.817436304Z","pid":"736","source":"agent","name":"kata-agent","subsystem":"rpc","version":"0.1.0"}
Apr 05 04:15:07 podvm-spark-test-5f11913c kata-agent[736]: {"msg":"rpc call from shim to agent: \"copy_file\"","level":"INFO","ts":"2023-04-05T04:15:07.818777747Z","source":"agent","pid":"736","name":"kata-agent","subsystem":"rpc","version":"0.1.0"}
Apr 05 04:15:07 podvm-spark-test-5f11913c kata-agent[736]: {"msg":"rpc call from shim to agent: \"copy_file\"","level":"INFO","ts":"2023-04-05T04:15:07.820504433Z","source":"agent","name":"kata-agent","version":"0.1.0","subsystem":"rpc","pid":"736"}
Apr 05 04:15:07 podvm-spark-test-5f11913c kata-agent[736]: {"msg":"Attestation Agent already running","level":"INFO","ts":"2023-04-05T04:15:07.824790024Z","version":"0.1.0","source":"agent","pid":"736","subsystem":"rpc","name":"kata-agent"}
Apr 05 04:15:07 podvm-spark-test-5f11913c kata-agent[736]: {"msg":"image_client.config.auth set to: true","level":"INFO","ts":"2023-04-05T04:15:07.824814399Z","version":"0.1.0","name":"kata-agent","subsystem":"rpc","source":"agent","pid":"736"}
Apr 05 04:15:07 podvm-spark-test-5f11913c kata-agent[736]: {"msg":"enable_signature_verification set to: false","level":"INFO","ts":"2023-04-05T04:15:07.824838084Z","version":"0.1.0","source":"agent","name":"kata-agent","pid":"736","subsystem":"rpc"}
Apr 05 04:15:07 podvm-spark-test-5f11913c kata-agent[736]: {"msg":"pull image \"3266064cb61326d958f2407843b32653fe469c92aa95f63acdb9053f2084f4e2\", bundle path \"/run/kata-containers/3266064cb61326d958f2407843b32653fe469c92aa95f63acdb9053f2084f4e2\"","level":"INFO","ts":"2023-04-05T04:15:07.824866888Z","subsystem":"rpc","name":"kata-agent","source":"agent","pid":"736","version":"0.1.0"}
Apr 05 04:15:07 podvm-spark-test-5f11913c kata-agent[1232]: [2023-04-05T04:15:07Z ERROR attestation_agent::rpc::getresource::grpc] Call AA-KBC to get resource failed: Resource path offline_fs_kbc must start with '/'
Apr 05 04:15:08 podvm-spark-test-5f11913c kata-agent[736]: {"msg":"pull and unpack image \"docker.io/apache/spark-py:v3.3.2\", cid: \"3266064cb61326d958f2407843b32653fe469c92aa95f63acdb9053f2084f4e2\", with image-rs failed with \"failed to handle layer: hasher sha256 : channel: send failed \\\"SendError(..)\\\"\". ","level":"ERRO","ts":"2023-04-05T04:15:08.079851409Z","version":"0.1.0","source":"agent","name":"kata-agent","pid":"736","subsystem":"rpc"}
Apr 05 04:15:08 podvm-spark-test-5f11913c kata-agent[736]: {"msg":"Attestation Agent already running","level":"INFO","ts":"2023-04-05T04:15:08.224440433Z","source":"agent","name":"kata-agent","subsystem":"rpc","version":"0.1.0","pid":"736"}
Apr 05 04:15:08 podvm-spark-test-5f11913c kata-agent[736]: {"msg":"image_client.config.auth set to: true","level":"INFO","ts":"2023-04-05T04:15:08.224472353Z","subsystem":"rpc","version":"0.1.0","source":"agent","name":"kata-agent","pid":"736"}
Apr 05 04:15:08 podvm-spark-test-5f11913c kata-agent[736]: {"msg":"enable_signature_verification set to: false","level":"INFO","ts":"2023-04-05T04:15:08.224498902Z","pid":"736","name":"kata-agent","source":"agent","subsystem":"rpc","version":"0.1.0"}
Apr 05 04:15:08 podvm-spark-test-5f11913c kata-agent[736]: {"msg":"pull image \"3266064cb61326d958f2407843b32653fe469c92aa95f63acdb9053f2084f4e2\", bundle path \"/run/kata-containers/3266064cb61326d958f2407843b32653fe469c92aa95f63acdb9053f2084f4e2\"","level":"INFO","ts":"2023-04-05T04:15:08.224527466Z","source":"agent","subsystem":"rpc","version":"0.1.0","name":"kata-agent","pid":"736"}
Apr 05 04:15:08 podvm-spark-test-5f11913c kata-agent[1232]: [2023-04-05T04:15:08Z ERROR attestation_agent::rpc::getresource::grpc] Call AA-KBC to get resource failed: Resource path offline_fs_kbc must start with '/'
Apr 05 04:15:08 podvm-spark-test-5f11913c kata-agent[736]: {"msg":"pull and unpack image \"docker.io/apache/spark-py:v3.3.2\", cid: \"3266064cb61326d958f2407843b32653fe469c92aa95f63acdb9053f2084f4e2\", with image-rs failed with \"failed to handle layer: hasher sha256 : unpack destination \\\"/run/image/layers/sha256_844c2c952c2d7eab58fbb2f5ce42b2ca7dbaa0bd71b28bc12368c9966631a9d7\\\" already exists\". ","level":"ERRO","ts":"2023-04-05T04:15:08.449126341Z","name":"kata-agent","subsystem":"rpc","source":"agent","version":"0.1.0","pid":"736"}
Apr 05 04:15:08 podvm-spark-test-5f11913c kata-agent[736]: {"msg":"Attestation Agent already running","level":"INFO","ts":"2023-04-05T04:15:08.736637732Z","subsystem":"rpc","source":"agent","version":"0.1.0","pid":"736","name":"kata-agent"}
Apr 05 04:15:08 podvm-spark-test-5f11913c kata-agent[736]: {"msg":"image_client.config.auth set to: true","level":"INFO","ts":"2023-04-05T04:15:08.736667417Z","pid":"736","subsystem":"rpc","version":"0.1.0","source":"agent","name":"kata-agent"}
Apr 05 04:15:08 podvm-spark-test-5f11913c kata-agent[736]: {"msg":"enable_signature_verification set to: false","level":"INFO","ts":"2023-04-05T04:15:08.736705358Z","source":"agent","version":"0.1.0","name":"kata-agent","subsystem":"rpc","pid":"736"}
Apr 05 04:15:08 podvm-spark-test-5f11913c kata-agent[736]: {"msg":"pull image \"3266064cb61326d958f2407843b32653fe469c92aa95f63acdb9053f2084f4e2\", bundle path \"/run/kata-containers/3266064cb61326d958f2407843b32653fe469c92aa95f63acdb9053f2084f4e2\"","level":"INFO","ts":"2023-04-05T04:15:08.736731948Z","name":"kata-agent","subsystem":"rpc","source":"agent","pid":"736","version":"0.1.0"}
Apr 05 04:15:08 podvm-spark-test-5f11913c kata-agent[1232]: [2023-04-05T04:15:08Z ERROR attestation_agent::rpc::getresource::grpc] Call AA-KBC to get resource failed: Resource path offline_fs_kbc must start with '/'
Apr 05 04:15:09 podvm-spark-test-5f11913c kata-agent[736]: unequal uncompressed digest "sha256:bbdc8443262651100e95d67ff7bbe78449f6c3b5fcbb7182873095d956165f74" config diff_id "sha256:bfbb1867344d5721aa875ab3e16716c61967b8753f3dc905e115003c350a163b"
Apr 05 04:15:09 podvm-spark-test-5f11913c kata-agent[736]: {"msg":"pull and unpack image \"docker.io/apache/spark-py:v3.3.2\", cid: \"3266064cb61326d958f2407843b32653fe469c92aa95f63acdb9053f2084f4e2\", with image-rs failed with \"failed to handle layer: unequal uncompressed digest \\\"sha256:bbdc8443262651100e95d67ff7bbe78449f6c3b5fcbb7182873095d956165f74\\\" config diff_id \\\"sha256:bfbb1867344d5721aa875ab3e16716c61967b8753f3dc905e115003c350a163b\\\"\". ","level":"ERRO","ts":"2023-04-05T04:15:09.801869529Z","source":"agent","name":"kata-agent","version":"0.1.0","subsystem":"rpc","pid":"736"}
Apr 05 04:15:10 podvm-spark-test-5f11913c kata-agent[736]: {"msg":"Attestation Agent already running","level":"INFO","ts":"2023-04-05T04:15:10.219304985Z","subsystem":"rpc","name":"kata-agent","pid":"736","version":"0.1.0","source":"agent"}
Apr 05 04:15:10 podvm-spark-test-5f11913c kata-agent[736]: {"msg":"image_client.config.auth set to: true","level":"INFO","ts":"2023-04-05T04:15:10.219334681Z","version":"0.1.0","pid":"736","source":"agent","name":"kata-agent","subsystem":"rpc"}
Apr 05 04:15:10 podvm-spark-test-5f11913c kata-agent[736]: {"msg":"enable_signature_verification set to: false","level":"INFO","ts":"2023-04-05T04:15:10.219359327Z","subsystem":"rpc","source":"agent","name":"kata-agent","pid":"736","version":"0.1.0"}
Apr 05 04:15:10 podvm-spark-test-5f11913c kata-agent[736]: {"msg":"pull image \"3266064cb61326d958f2407843b32653fe469c92aa95f63acdb9053f2084f4e2\", bundle path \"/run/kata-containers/3266064cb61326d958f2407843b32653fe469c92aa95f63acdb9053f2084f4e2\"","level":"INFO","ts":"2023-04-05T04:15:10.219385696Z","pid":"736","name":"kata-agent","source":"agent","subsystem":"rpc","version":"0.1.0"}
Apr 05 04:15:10 podvm-spark-test-5f11913c kata-agent[1232]: [2023-04-05T04:15:10Z ERROR attestation_agent::rpc::getresource::grpc] Call AA-KBC to get resource failed: Resource path offline_fs_kbc must start with '/'
Apr 05 04:15:10 podvm-spark-test-5f11913c kata-agent[736]: {"msg":"pull and unpack image \"docker.io/apache/spark-py:v3.3.2\", cid: \"3266064cb61326d958f2407843b32653fe469c92aa95f63acdb9053f2084f4e2\", with image-rs failed with \"failed to handle layer: hasher sha256 : channel: send failed \\\"SendError(..)\\\"\". ","level":"ERRO","ts":"2023-04-05T04:15:10.471300085Z","version":"0.1.0","source":"agent","name":"kata-agent","pid":"736","subsystem":"rpc"}
Apr 05 04:15:11 podvm-spark-test-5f11913c kata-agent[736]: {"msg":"Attestation Agent already running","level":"INFO","ts":"2023-04-05T04:15:11.289106006Z","name":"kata-agent","pid":"736","subsystem":"rpc","source":"agent","version":"0.1.0"}
Apr 05 04:15:11 podvm-spark-test-5f11913c kata-agent[736]: {"msg":"image_client.config.auth set to: true","level":"INFO","ts":"2023-04-05T04:15:11.289140671Z","name":"kata-agent","version":"0.1.0","subsystem":"rpc","source":"agent","pid":"736"}
Apr 05 04:15:11 podvm-spark-test-5f11913c kata-agent[736]: {"msg":"enable_signature_verification set to: false","level":"INFO","ts":"2023-04-05T04:15:11.289165327Z","name":"kata-agent","version":"0.1.0","source":"agent","pid":"736","subsystem":"rpc"}
Apr 05 04:15:11 podvm-spark-test-5f11913c kata-agent[736]: {"msg":"pull image \"3266064cb61326d958f2407843b32653fe469c92aa95f63acdb9053f2084f4e2\", bundle path \"/run/kata-containers/3266064cb61326d958f2407843b32653fe469c92aa95f63acdb9053f2084f4e2\"","level":"INFO","ts":"2023-04-05T04:15:11.289191536Z","source":"agent","subsystem":"rpc","name":"kata-agent","version":"0.1.0","pid":"736"}
Apr 05 04:15:11 podvm-spark-test-5f11913c kata-agent[1232]: [2023-04-05T04:15:11Z ERROR attestation_agent::rpc::getresource::grpc] Call AA-KBC to get resource failed: Resource path offline_fs_kbc must start with '/'
Apr 05 04:15:11 podvm-spark-test-5f11913c kata-agent[736]: {"msg":"pull and unpack image \"docker.io/apache/spark-py:v3.3.2\", cid: \"3266064cb61326d958f2407843b32653fe469c92aa95f63acdb9053f2084f4e2\", with image-rs failed with \"failed to handle layer: hasher sha256 : channel: send failed \\\"SendError(..)\\\"\". ","level":"ERRO","ts":"2023-04-05T04:15:11.885727044Z","name":"kata-agent","subsystem":"rpc","source":"agent","pid":"736","version":"0.1.0"}
Apr 05 04:15:13 podvm-spark-test-5f11913c kata-agent[736]: {"msg":"Attestation Agent already running","level":"INFO","ts":"2023-04-05T04:15:13.5015377Z","source":"agent","pid":"736","version":"0.1.0","name":"kata-agent","subsystem":"rpc"}
Apr 05 04:15:13 podvm-spark-test-5f11913c kata-agent[736]: {"msg":"image_client.config.auth set to: true","level":"INFO","ts":"2023-04-05T04:15:13.501569851Z","subsystem":"rpc","name":"kata-agent","source":"agent","version":"0.1.0","pid":"736"}
Apr 05 04:15:13 podvm-spark-test-5f11913c kata-agent[736]: {"msg":"enable_signature_verification set to: false","level":"INFO","ts":"2023-04-05T04:15:13.501594217Z","version":"0.1.0","source":"agent","name":"kata-agent","subsystem":"rpc","pid":"736"}
Apr 05 04:15:13 podvm-spark-test-5f11913c kata-agent[736]: {"msg":"pull image \"3266064cb61326d958f2407843b32653fe469c92aa95f63acdb9053f2084f4e2\", bundle path \"/run/kata-containers/3266064cb61326d958f2407843b32653fe469c92aa95f63acdb9053f2084f4e2\"","level":"INFO","ts":"2023-04-05T04:15:13.501620375Z","source":"agent","pid":"736","version":"0.1.0","subsystem":"rpc","name":"kata-agent"}
Apr 05 04:15:13 podvm-spark-test-5f11913c kata-agent[1232]: [2023-04-05T04:15:13Z ERROR attestation_agent::rpc::getresource::grpc] Call AA-KBC to get resource failed: Resource path offline_fs_kbc must start with '/'
Apr 05 04:15:13 podvm-spark-test-5f11913c kata-agent[736]: {"msg":"pull and unpack image \"docker.io/apache/spark-py:v3.3.2\", cid: \"3266064cb61326d958f2407843b32653fe469c92aa95f63acdb9053f2084f4e2\", with image-rs failed with \"failed to handle layer: hasher sha256 : channel: send failed \\\"SendError(..)\\\"\". ","level":"ERRO","ts":"2023-04-05T04:15:13.725458537Z","pid":"736","subsystem":"rpc","name":"kata-agent","source":"agent","version":"0.1.0"}
Apr 05 04:15:16 podvm-spark-test-5f11913c kata-agent[736]: {"msg":"Attestation Agent already running","level":"INFO","ts":"2023-04-05T04:15:16.936826874Z","subsystem":"rpc","version":"0.1.0","name":"kata-agent","source":"agent","pid":"736"}
Apr 05 04:15:16 podvm-spark-test-5f11913c kata-agent[736]: {"msg":"image_client.config.auth set to: true","level":"INFO","ts":"2023-04-05T04:15:16.936874353Z","source":"agent","version":"0.1.0","name":"kata-agent","subsystem":"rpc","pid":"736"}
Apr 05 04:15:16 podvm-spark-test-5f11913c kata-agent[736]: {"msg":"enable_signature_verification set to: false","level":"INFO","ts":"2023-04-05T04:15:16.936913917Z","name":"kata-agent","pid":"736","subsystem":"rpc","source":"agent","version":"0.1.0"}
Apr 05 04:15:16 podvm-spark-test-5f11913c kata-agent[736]: {"msg":"pull image \"3266064cb61326d958f2407843b32653fe469c92aa95f63acdb9053f2084f4e2\", bundle path \"/run/kata-containers/3266064cb61326d958f2407843b32653fe469c92aa95f63acdb9053f2084f4e2\"","level":"INFO","ts":"2023-04-05T04:15:16.93695803Z","subsystem":"rpc","source":"agent","version":"0.1.0","pid":"736","name":"kata-agent"}
Apr 05 04:15:16 podvm-spark-test-5f11913c kata-agent[1232]: [2023-04-05T04:15:16Z ERROR attestation_agent::rpc::getresource::grpc] Call AA-KBC to get resource failed: Resource path offline_fs_kbc must start with '/'
Apr 05 04:15:17 podvm-spark-test-5f11913c kata-agent[736]: {"msg":"pull and unpack image \"docker.io/apache/spark-py:v3.3.2\", cid: \"3266064cb61326d958f2407843b32653fe469c92aa95f63acdb9053f2084f4e2\", with image-rs failed with \"failed to handle layer: hasher sha256 : channel: send failed \\\"SendError(..)\\\"\". ","level":"ERRO","ts":"2023-04-05T04:15:17.645872939Z","version":"0.1.0","source":"agent","subsystem":"rpc","pid":"736","name":"kata-agent"}
Apr 05 04:15:24 podvm-spark-test-5f11913c kata-agent[736]: {"msg":"Attestation Agent already running","level":"INFO","ts":"2023-04-05T04:15:24.10754002Z","name":"kata-agent","subsystem":"rpc","version":"0.1.0","source":"agent","pid":"736"}
Apr 05 04:15:24 podvm-spark-test-5f11913c kata-agent[736]: {"msg":"image_client.config.auth set to: true","level":"INFO","ts":"2023-04-05T04:15:24.107570737Z","version":"0.1.0","pid":"736","subsystem":"rpc","source":"agent","name":"kata-agent"}
Apr 05 04:15:24 podvm-spark-test-5f11913c kata-agent[736]: {"msg":"enable_signature_verification set to: false","level":"INFO","ts":"2023-04-05T04:15:24.107596115Z","name":"kata-agent","pid":"736","subsystem":"rpc","source":"agent","version":"0.1.0"}
Apr 05 04:15:24 podvm-spark-test-5f11913c kata-agent[736]: {"msg":"pull image \"3266064cb61326d958f2407843b32653fe469c92aa95f63acdb9053f2084f4e2\", bundle path \"/run/kata-containers/3266064cb61326d958f2407843b32653fe469c92aa95f63acdb9053f2084f4e2\"","level":"INFO","ts":"2023-04-05T04:15:24.107622634Z","pid":"736","name":"kata-agent","subsystem":"rpc","source":"agent","version":"0.1.0"}
Apr 05 04:15:24 podvm-spark-test-5f11913c kata-agent[1232]: [2023-04-05T04:15:24Z ERROR attestation_agent::rpc::getresource::grpc] Call AA-KBC to get resource failed: Resource path offline_fs_kbc must start with '/'
Apr 05 04:15:24 podvm-spark-test-5f11913c kata-agent[736]: {"msg":"pull and unpack image \"docker.io/apache/spark-py:v3.3.2\", cid: \"3266064cb61326d958f2407843b32653fe469c92aa95f63acdb9053f2084f4e2\", with image-rs failed with \"failed to handle layer: hasher sha256 : channel: send failed \\\"SendError(..)\\\"\". ","level":"ERRO","ts":"2023-04-05T04:15:24.379634412Z","subsystem":"rpc","source":"agent","pid":"736","version":"0.1.0","name":"kata-agent"}

Agent Protocol Forwarder logs:
Apr 05 04:14:03 podvm-spark-test-5f11913c systemd[1]: Started Agent Protocol Forwarder.
Apr 05 04:14:06 podvm-spark-test-5f11913c agent-protocol-forwarder[1043]: 2023/04/05 04:14:06 [forwarder/interceptor] CreateSandbox: hostname:spark-test sandboxId:5f11913cdc19aa93c0bf3443eb3953d155d0e6947911554679095f2941fee1b2
Apr 05 04:14:06 podvm-spark-test-5f11913c agent-protocol-forwarder[1043]: 2023/04/05 04:14:06 [forwarder/interceptor]     dns:
Apr 05 04:14:06 podvm-spark-test-5f11913c agent-protocol-forwarder[1043]: 2023/04/05 04:14:06 [forwarder/interceptor]         search default.svc.cluster.local svc.cluster.local cluster.local 4jd241mn321engfadotper5ohf.bx.internal.cloudapp.net
Apr 05 04:14:06 podvm-spark-test-5f11913c agent-protocol-forwarder[1043]: 2023/04/05 04:14:06 [forwarder/interceptor]         nameserver <IP_ADDRESS>
Apr 05 04:14:06 podvm-spark-test-5f11913c agent-protocol-forwarder[1043]: 2023/04/05 04:14:06 [forwarder/interceptor]         options ndots:5
Apr 05 04:14:06 podvm-spark-test-5f11913c agent-protocol-forwarder[1043]: 2023/04/05 04:14:06 [forwarder/interceptor]
Apr 05 04:14:06 podvm-spark-test-5f11913c agent-protocol-forwarder[1043]: 2023/04/05 04:14:06 [forwarder/interceptor]       Eliminated the DNS setting above from CreateSandboxRequest to stop updating /etc/resolv.conf on the peer pod VM
Apr 05 04:14:06 podvm-spark-test-5f11913c agent-protocol-forwarder[1043]: 2023/04/05 04:14:06 [forwarder/interceptor]       See https://github.com/confidential-containers/cloud-api-adaptor/issues/98 for the details.
Apr 05 04:14:06 podvm-spark-test-5f11913c agent-protocol-forwarder[1043]: 2023/04/05 04:14:06 [forwarder/interceptor]
Apr 05 04:14:06 podvm-spark-test-5f11913c agent-protocol-forwarder[1043]: 2023/04/05 04:14:06 [forwarder/interceptor] established agent connection to /run/kata-containers/agent.sock
Apr 05 04:14:06 podvm-spark-test-5f11913c agent-protocol-forwarder[1043]: 2023/04/05 04:14:06 [forwarder/interceptor] PullImage: image: "registry.k8s.io/pause:3.7", containerID: "5f11913cdc19aa93c0bf3443eb3953d155d0e6947911554679095f2941fee1b2"
Apr 05 04:14:07 podvm-spark-test-5f11913c agent-protocol-forwarder[1043]: 2023/04/05 04:14:07 [forwarder/interceptor] CreateContainer: containerID:5f11913cdc19aa93c0bf3443eb3953d155d0e6947911554679095f2941fee1b2
Apr 05 04:14:07 podvm-spark-test-5f11913c agent-protocol-forwarder[1043]: 2023/04/05 04:14:07 [forwarder/interceptor]     namespaces:
Apr 05 04:14:07 podvm-spark-test-5f11913c agent-protocol-forwarder[1043]: 2023/04/05 04:14:07 [forwarder/interceptor]     ipc: ""
Apr 05 04:14:07 podvm-spark-test-5f11913c agent-protocol-forwarder[1043]: 2023/04/05 04:14:07 [forwarder/interceptor]     uts: ""
Apr 05 04:14:07 podvm-spark-test-5f11913c agent-protocol-forwarder[1043]: 2023/04/05 04:14:07 [forwarder/interceptor]     mount: ""
Apr 05 04:14:07 podvm-spark-test-5f11913c agent-protocol-forwarder[1043]: 2023/04/05 04:14:07 [forwarder/interceptor]     network: "/run/netns/podns"
Apr 05 04:14:07 podvm-spark-test-5f11913c agent-protocol-forwarder[1043]: 2023/04/05 04:14:07 [forwarder/interceptor] StartContainer: containerID:5f11913cdc19aa93c0bf3443eb3953d155d0e6947911554679095f2941fee1b2
Apr 05 04:14:07 podvm-spark-test-5f11913c agent-protocol-forwarder[1043]: 2023/04/05 04:14:07 [forwarder/interceptor] PullImage: image: "docker.io/apache/spark-py:v3.3.2", containerID: "d130063b369633459a88c0e576cb13b01f81e1502c6b98c03147e5d8baa08cd5"
Apr 05 04:14:09 podvm-spark-test-5f11913c agent-protocol-forwarder[1043]: 2023/04/05 04:14:09 [forwarder/interceptor] PullImage failed with error: rpc error: code = Internal desc = failed to handle layer: unequal uncompressed digest "sha256:f34f358f10db28bcd5df51d75cc2b1a55cf5f14b775a53457a517b8e410eb57e" config diff_id "sha256:138a5c6e0e9b41fbf50dc01fa27bbcbc28cf45e615cfbe9330041fdc0c593201"
Apr 05 04:14:09 podvm-spark-test-5f11913c agent-protocol-forwarder[1043]: 2023/04/05 04:14:09 [forwarder/interceptor] PullImage: image: "docker.io/apache/spark-py:v3.3.2", containerID: "d130063b369633459a88c0e576cb13b01f81e1502c6b98c03147e5d8baa08cd5"
Apr 05 04:14:10 podvm-spark-test-5f11913c agent-protocol-forwarder[1043]: 2023/04/05 04:14:10 [forwarder/interceptor] PullImage failed with error: rpc error: code = Internal desc = failed to handle layer: hasher sha256 : channel: send failed "SendError(..)"
Apr 05 04:14:10 podvm-spark-test-5f11913c agent-protocol-forwarder[1043]: 2023/04/05 04:14:10 [forwarder/interceptor] PullImage: image: "docker.io/apache/spark-py:v3.3.2", containerID: "d130063b369633459a88c0e576cb13b01f81e1502c6b98c03147e5d8baa08cd5"
Apr 05 04:14:12 podvm-spark-test-5f11913c agent-protocol-forwarder[1043]: 2023/04/05 04:14:12 [forwarder/interceptor] PullImage failed with error: rpc error: code = Internal desc = failed to handle layer: hasher sha256 : unpack destination "/run/image/layers/sha256_4f4fb700ef54461cfa02571ae0db9a0dc1e0cdb5577484a6d75e68dc38e8acc1" already exists
Apr 05 04:14:13 podvm-spark-test-5f11913c agent-protocol-forwarder[1043]: 2023/04/05 04:14:13 [forwarder/interceptor] PullImage: image: "docker.io/apache/spark-py:v3.3.2", containerID: "d130063b369633459a88c0e576cb13b01f81e1502c6b98c03147e5d8baa08cd5"
Apr 05 04:14:13 podvm-spark-test-5f11913c agent-protocol-forwarder[1043]: 2023/04/05 04:14:13 [forwarder/interceptor] PullImage failed with error: rpc error: code = Internal desc = failed to handle layer: hasher sha256 : channel: send failed "SendError(..)"
Apr 05 04:14:14 podvm-spark-test-5f11913c agent-protocol-forwarder[1043]: 2023/04/05 04:14:14 [forwarder/interceptor] PullImage: image: "docker.io/apache/spark-py:v3.3.2", containerID: "d130063b369633459a88c0e576cb13b01f81e1502c6b98c03147e5d8baa08cd5"
Apr 05 04:14:14 podvm-spark-test-5f11913c agent-protocol-forwarder[1043]: 2023/04/05 04:14:14 [forwarder/interceptor] PullImage failed with error: rpc error: code = Internal desc = failed to handle layer: hasher sha256 : channel: send failed "SendError(..)"
Apr 05 04:14:16 podvm-spark-test-5f11913c agent-protocol-forwarder[1043]: 2023/04/05 04:14:16 [forwarder/interceptor] PullImage: image: "docker.io/apache/spark-py:v3.3.2", containerID: "d130063b369633459a88c0e576cb13b01f81e1502c6b98c03147e5d8baa08cd5"
Apr 05 04:14:16 podvm-spark-test-5f11913c agent-protocol-forwarder[1043]: 2023/04/05 04:14:16 [forwarder/interceptor] PullImage failed with error: rpc error: code = Internal desc = failed to handle layer: hasher sha256 : channel: send failed "SendError(..)"
Apr 05 04:14:19 podvm-spark-test-5f11913c agent-protocol-forwarder[1043]: 2023/04/05 04:14:19 [forwarder/interceptor] PullImage: image: "docker.io/apache/spark-py:v3.3.2", containerID: "d130063b369633459a88c0e576cb13b01f81e1502c6b98c03147e5d8baa08cd5"
Apr 05 04:14:21 podvm-spark-test-5f11913c agent-protocol-forwarder[1043]: 2023/04/05 04:14:21 [forwarder/interceptor] PullImage failed with error: rpc error: code = Internal desc = failed to handle layer: hasher sha256 : channel: send failed "SendError(..)"
Apr 05 04:14:28 podvm-spark-test-5f11913c agent-protocol-forwarder[1043]: 2023/04/05 04:14:28 [forwarder/interceptor] PullImage: image: "docker.io/apache/spark-py:v3.3.2", containerID: "d130063b369633459a88c0e576cb13b01f81e1502c6b98c03147e5d8baa08cd5"
Apr 05 04:14:28 podvm-spark-test-5f11913c agent-protocol-forwarder[1043]: 2023/04/05 04:14:28 [forwarder/interceptor] PullImage failed with error: rpc error: code = Internal desc = failed to handle layer: hasher sha256 : channel: send failed "SendError(..)"
Apr 05 04:14:41 podvm-spark-test-5f11913c agent-protocol-forwarder[1043]: 2023/04/05 04:14:41 [forwarder/interceptor] PullImage: image: "docker.io/apache/spark-py:v3.3.2", containerID: "d130063b369633459a88c0e576cb13b01f81e1502c6b98c03147e5d8baa08cd5"
Apr 05 04:14:41 podvm-spark-test-5f11913c agent-protocol-forwarder[1043]: 2023/04/05 04:14:41 [forwarder/interceptor] PullImage failed with error: rpc error: code = Internal desc = failed to handle layer: hasher sha256 : unpack destination "/run/image/layers/sha256_12cca292b13cb58fadde25af113ddc4ac3b0c5e39ab3f1290a6ba62ec8237afd" already exists
Apr 05 04:15:07 podvm-spark-test-5f11913c agent-protocol-forwarder[1043]: 2023/04/05 04:15:07 [forwarder/interceptor] PullImage: image: "docker.io/apache/spark-py:v3.3.2", containerID: "d130063b369633459a88c0e576cb13b01f81e1502c6b98c03147e5d8baa08cd5"
Apr 05 04:15:07 podvm-spark-test-5f11913c agent-protocol-forwarder[1043]: 2023/04/05 04:15:07 [forwarder/interceptor] PullImage failed with error: context deadline exceeded
Apr 05 04:15:07 podvm-spark-test-5f11913c agent-protocol-forwarder[1043]: 2023/04/05 04:15:07 [forwarder/interceptor] PullImage: image: "docker.io/apache/spark-py:v3.3.2", containerID: "3266064cb61326d958f2407843b32653fe469c92aa95f63acdb9053f2084f4e2"
Apr 05 04:15:08 podvm-spark-test-5f11913c agent-protocol-forwarder[1043]: 2023/04/05 04:15:08 [forwarder/interceptor] PullImage failed with error: rpc error: code = Internal desc = failed to handle layer: hasher sha256 : channel: send failed "SendError(..)"
Apr 05 04:15:08 podvm-spark-test-5f11913c agent-protocol-forwarder[1043]: 2023/04/05 04:15:08 [forwarder/interceptor] PullImage: image: "docker.io/apache/spark-py:v3.3.2", containerID: "3266064cb61326d958f2407843b32653fe469c92aa95f63acdb9053f2084f4e2"
Apr 05 04:15:08 podvm-spark-test-5f11913c agent-protocol-forwarder[1043]: 2023/04/05 04:15:08 [forwarder/interceptor] PullImage failed with error: rpc error: code = Internal desc = failed to handle layer: hasher sha256 : unpack destination "/run/image/layers/sha256_844c2c952c2d7eab58fbb2f5ce42b2ca7dbaa0bd71b28bc12368c9966631a9d7" already exists
Apr 05 04:15:08 podvm-spark-test-5f11913c agent-protocol-forwarder[1043]: 2023/04/05 04:15:08 [forwarder/interceptor] PullImage: image: "docker.io/apache/spark-py:v3.3.2", containerID: "3266064cb61326d958f2407843b32653fe469c92aa95f63acdb9053f2084f4e2"
Apr 05 04:15:09 podvm-spark-test-5f11913c agent-protocol-forwarder[1043]: 2023/04/05 04:15:09 [forwarder/interceptor] PullImage failed with error: rpc error: code = Internal desc = failed to handle layer: unequal uncompressed digest "sha256:bbdc8443262651100e95d67ff7bbe78449f6c3b5fcbb7182873095d956165f74" config diff_id "sha256:bfbb1867344d5721aa875ab3e16716c61967b8753f3dc905e115003c350a163b"
Apr 05 04:15:10 podvm-spark-test-5f11913c agent-protocol-forwarder[1043]: 2023/04/05 04:15:10 [forwarder/interceptor] PullImage: image: "docker.io/apache/spark-py:v3.3.2", containerID: "3266064cb61326d958f2407843b32653fe469c92aa95f63acdb9053f2084f4e2"
Apr 05 04:15:10 podvm-spark-test-5f11913c agent-protocol-forwarder[1043]: 2023/04/05 04:15:10 [forwarder/interceptor] PullImage failed with error: rpc error: code = Internal desc = failed to handle layer: hasher sha256 : channel: send failed "SendError(..)"
Apr 05 04:15:11 podvm-spark-test-5f11913c agent-protocol-forwarder[1043]: 2023/04/05 04:15:11 [forwarder/interceptor] PullImage: image: "docker.io/apache/spark-py:v3.3.2", containerID: "3266064cb61326d958f2407843b32653fe469c92aa95f63acdb9053f2084f4e2"
Apr 05 04:15:11 podvm-spark-test-5f11913c agent-protocol-forwarder[1043]: 2023/04/05 04:15:11 [forwarder/interceptor] PullImage failed with error: rpc error: code = Internal desc = failed to handle layer: hasher sha256 : channel: send failed "SendError(..)"
Apr 05 04:15:13 podvm-spark-test-5f11913c agent-protocol-forwarder[1043]: 2023/04/05 04:15:13 [forwarder/interceptor] PullImage: image: "docker.io/apache/spark-py:v3.3.2", containerID: "3266064cb61326d958f2407843b32653fe469c92aa95f63acdb9053f2084f4e2"
Apr 05 04:15:13 podvm-spark-test-5f11913c agent-protocol-forwarder[1043]: 2023/04/05 04:15:13 [forwarder/interceptor] PullImage failed with error: rpc error: code = Internal desc = failed to handle layer: hasher sha256 : channel: send failed "SendError(..)"
Apr 05 04:15:16 podvm-spark-test-5f11913c agent-protocol-forwarder[1043]: 2023/04/05 04:15:16 [forwarder/interceptor] PullImage: image: "docker.io/apache/spark-py:v3.3.2", containerID: "3266064cb61326d958f2407843b32653fe469c92aa95f63acdb9053f2084f4e2"
Apr 05 04:15:17 podvm-spark-test-5f11913c agent-protocol-forwarder[1043]: 2023/04/05 04:15:17 [forwarder/interceptor] PullImage failed with error: rpc error: code = Internal desc = failed to handle layer: hasher sha256 : channel: send failed "SendError(..)"
Apr 05 04:15:24 podvm-spark-test-5f11913c agent-protocol-forwarder[1043]: 2023/04/05 04:15:24 [forwarder/interceptor] PullImage: image: "docker.io/apache/spark-py:v3.3.2", containerID: "3266064cb61326d958f2407843b32653fe469c92aa95f63acdb9053f2084f4e2"
Apr 05 04:15:24 podvm-spark-test-5f11913c agent-protocol-forwarder[1043]: 2023/04/05 04:15:24 [forwarder/interceptor] PullImage failed with error: rpc error: code = Internal desc = failed to handle layer: hasher sha256 : channel: send failed "SendError(..)"

Could you share the rev of the image-rs you're using? There was once a similiar  bug  and fixed in https://github.com/confidential-containers/image-rs/issues/76 and

@Xynnn007 using rev: "v0.4.0"

@Xynnn007 surprisingly facing the issue only with the specific image as mentioned by @surajssd

@surajssd @bpradipt
What is the rev of attestation-agent?
Also, could you share the image? maybe it is caused by some unknown and special structure of the image

I test this image locally with image-rs and error @arronwy
running 1 test
test image::tests::test_pull_image ... FAILED

failures:

---- image::tests::test_pull_image stdout ----
unequal uncompressed digest "sha256:f34f358f10db28bcd5df51d75cc2b1a55cf5f14b775a53457a517b8e410eb57e" config diff_id "sha256:138a5c6e0e9b41fbf50dc01fa27bbcbc28cf45e615cfbe9330041fdc0c593201"
thread 'image::tests::test_pull_image' panicked at 'failed to download image: failed to handle layer: unequal uncompressed digest "sha256:f34f358f10db28bcd5df51d75cc2b1a55cf5f14b775a53457a517b8e410eb57e" config diff_id "sha256:138a5c6e0e9b41fbf50dc01fa27bbcbc28cf45e615cfbe9330041fdc0c593201"', src/image.rs:391:17
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace

Found an image that works: apache/spark-py:v3.2.1.

@surajssd @bpradipt can you help to verify this issue with this PR: https://github.com/confidential-containers/image-rs/pull/133 , I verified locally which works with apache/spark-py:v3.2.1

I met this error too. Kata-cc erro log:
E0701 17:13:53.582871  120863 remote_image.go:242] "PullImage from image service failed" err=<
	rpc error: code = Internal desc = Failed to pull image, run with reconnect

	Caused by:
	    rpc status: code: INTERNAL message: "failed to handle layer: hasher sha256 : channel: send failed \"SendError(..)\""
 > image="nydus-dedup-registry.cn-hangzhou.cr.aliyuncs.com/mushu/nginx:encrypted-oci"
FATA[0003] creating container: rpc error: code = Internal desc = Failed to pull image, run with reconnect

Caused by:
    rpc status: code: INTERNAL message: "failed to handle layer: hasher sha256 : channel: send failed \"SendError(..)\""

I used skopeo and coco_key_provider to encrypt docker.io/nginx:latest，and then pushed it to my personal registry.
The manifest
{
    "Name": "nydus-dedup-registry.cn-hangzhou.cr.aliyuncs.com/mushu/nginx",
    "Digest": "sha256:991932cf1a484929694f2edf3de44b73f6a6715115ae620b35edcbe79eac6e07",
    "RepoTags": [
        "encrypted-oci",
    ],
    "Created": "2023-06-14T07:16:35.543292113Z",
    "DockerVersion": "",
    "Labels": {
        "maintainer": "NGINX Docker Maintainers<EMAIL_ADDRESS>    },
    "Architecture": "amd64",
    "Os": "linux",
    "Layers": [
        "sha256:03f24c598427ec46a7b7488be88fc56c0315090aea7d6d1bcdde0b861aafdb09",
        "sha256:8ac16fe224741576d83860c772f41e88f414179903de60b2bca699087924929d",
        "sha256:ac7a90487a28c9196668207302788c9b2eba48ed9d0460404feb128907346dcc",
        "sha256:c5a49b8256df90f8563046a0bd308a903b33652ec7806b0196e504f0a5d898d0",
        "sha256:2bf509b714b652fa88e111ec297234893609aa20ab055babb8ec0b822f2cb34e",
        "sha256:d2533d8e0fa450a7660850e0c9de5e2ff7a1f1535bd8ac9484f93dd81e35ab6c",
        "sha256:0cc537cda66b568add2abbeb932d4771002d472ae899ae1ee3105ddf3e047d8f"
    ],
    "Env": [
        "PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin",
        "NGINX_VERSION=1.25.1",
        "NJS_VERSION=0.7.12",
        "PKG_RELEASE=1~bookworm"
    ]
}


pkg/authorization: add audit logging

Summary
This adds audit logs for remaining authorizers.
Related issue(s)
Fixes #1307

/assign s-urbaniak

/lgtm
/approve


Can't scan SPDX license-list-data

Scanning any project that is giant, or contains https://github.com/spdx/license-list-data will cause yesiscan to struggle and probably eventually oom. Since yesiscan itself contains the spdx license-list-data as a git submodule, this will not work. We eventually need to optimize the project, and gradually write out larger datasets as we collect them, since it will eventually be too much to store in memory.
Since these use cases are rare, we are punting on this issue for now, but we can revisit it in the future.

This will be very difficult to do, it is very complex to write this feature. Will need more than a week or more at least. Will also need to involve the caching layer perhaps.

We need to find a way to exclude the files, later we will redesign the way we run to support bigger projects.


Error after updating from 1.9.3 -> 1.9.5: only yarn v2/v3 with nodeLinker: node-modules is supported at this time

What version of Turborepo are you using?
1.9.5
What package manager are you using / does the bug impact?
Yarn v2/v3 (node_modules linker only)
What operating system are you using?
Linux
Describe the Bug
When upgrading 1.9.3 -> 1.9.5 it now prints an error:
Error: only yarn v2/v3 with `nodeLinker: node-modules` is supported at this time

We've been using turbo for many months now with Yarn PnP seemingly without problems, so it's surprising that it says this is not supported.
Expected Behavior
Keeps working as well as it did in version 1.9.3
To Reproduce
Probably need a yarn berry project that is not using the node-modules linker and compare the behavior between 1.9.3 and 1.9.5
Reproduction Repo
No response

It's surprising and frustrating when a feature that's supported is suddenly discontinued without warning. Could you tell me when yarn pnp will be available to its users again?

Could you tell me when yarn pnp will be available to its users again?

FWIW from what I can tell they have never "officially" supported yarn PnP.  However, it has been working fine in Yarn PnP for us for some time, so I'm not sure what the blocker is.

Hi, yeah it does seem that we accidentally permitted yarn PnP, when that was never the intention. We're currently investigating what precise features do not work well with PnP so we can restrict accordingly.

My yarn PnP project was working fine until this upgrade.

Hi, yeah it does seem that we accidentally permitted yarn PnP, when that was never the intention. We're currently investigating what precise features do not work well with PnP so we can restrict accordingly.

Seems like they are not even sure yet why it should be blocked, but did so.

There were multiple problems in the past that prevented us from working with yarn3 PnP. Over the past six or nine months we've worked through a lot of them as a side effect of work we were doing, but "supporting PnP" wasn't the primary goal of those efforts.
So, as it stands, we actually believe we support it, but have not written the tests that would confirm that.
The issue here is that we previously did not hard error in all scenarios with yarn PnP, which was a "bug" that we "fixed."
Your reports of it working increase our confidence that we just need to confirm everything with tests, so we're working on that!

This is released in 1.9.8.


added remove method to semaphore

Thank you for your library! Please add the ability to delete a semaphore after use, like CacheInterface delete method.

Thank you for your advice. I have add a 'remove method' in the Semaphore class, and it should only be called after the semaphore resource is created and it should not be locked.


Remove voting weight from readOnlyValues

Removes the rest of the useReadOnlyValues hook and state.
I'm not super confident with the changes in here. A lot of the code that I removed seemed unused, which gave me pause. Would appreciate some more context if anyone has it.
For example

were we ever using the votingWeight that came from readOnlyValues for getting voting weight of LinearERC20 strategies? Didn't look like it...
was the refetchUserTokens param in the getCanVote function, which triggered a call to a function, ever doing anything substantial? Seems like that function it called never really affected any state, so why were we calling it?
Does it matter that we're no longer "refreshing" the readOnlyValues after Delegation transaction happens?

Does it matter that we're no longer "refreshing" the readOnlyValues after Delegation transaction happens?
were we ever using the votingWeight that came from readOnlyValues for getting voting weight of LinearERC20 strategies? Didn't look like it...

At some point we were using global voting weight way more to derive whether user can propose or can vote.
This was before we went into relying on isProposer and getVotingWeight from strategy contract - which is a better way.
So yeah, removing this global votingWeight thingy sounds like a good idea


chore: replace full query logs with simpler logging

This PR resolves CX-1131
Description
This replaces the full loggerMiddleware with a simpler logging setup where most lines end up looking like this
RELAY MyProfilePaymentQuery {"count": 100} fetched in 0.7s with response {"me": {"creditCards": {"edges": [Array], "pageInfo": [Object]}, "id": "TWU6NWFiZjVlNWM4YjNiODE3OWU5ZDAxZGIz", "name": "David J Sheldrick"}}

in case of errors it looks like this
RELAY MyProfilePaymentQuery {"count": 100} fetched in 0.6s with errors

     1. The blah failed to do blah
     2. Error fetching blah from blah

The big difference is that we no longer log out the full query text, which is easily findable in the __generated__ folder.
PR Checklist (tick all before merging)

[x] I have included screenshots or videos to illustrate my changes, or I have not changed anything that impacts the UI.
[x] I have added tests for my changes, or my changes don't require testing, or I have included a link to a separate Jira ticket covering the tests.
[x] I have documented any follow-up work that this PR will require, or it does not require any.
[x] I have added an app state migration, or my changes do not require one. (What are migrations?)
[x] I have added a CHANGELOG.yml entry or my changes do not require one.

I apologize 😿 I missed this

#squashongreen


Cannot Optionalize Class Getters

TypeScript Version:  2.2.1
Code
class Person {
  firstName: string;
  lastName: string;

  get fullName?() {
    return this.firstName + ' ' + this.lastName;
  }
}

Expected behavior:
Since fullName is optional the following should work:
const Me: Person = {
  firstName: 'Foo',
  lastName: 'Bar'
}

Actual behavior:
A syntax error occurs on this line get fullName?() {
I'm not sure if omitting the ability to optionalize getters was by design or not. If it was by design, I'd love to know the reasoning behind it.

A class is an implementation of a type. if you want to declare an optional property i suggest adding an interface Person:
interface Person {
   firstName: string;
   lastName: string;

  readonly fullName?;
}

Thanks! I'm aware that that's a possibility.
I suppose I just don't understand why the language would disallow marking getters as optional when everything else on a class can be marked as optional. It seems inconsistent. Is there a good reason for this inconsistency? Forgive me if I misunderstand, but the "A class is an implementation of a type" reasoning seems more like a how-the-compiler-works reason as opposed to a how-the-language-should-work reason. I'm interested in the later.

Accessors (getters/setters) are just properties. you can declare methods and properties as option. but you can not have an implementation to an optional property or a method.

That explains how things work currently but not why.

@mhegazy Like bradenhs said, class methods can be made optional as seen here: https://github.com/Microsoft/TypeScript/pull/8625#issue-155070042
class Bar {
    h?() {
        return 2;
    }
}

As can be seen, it's an optional method that also has a body/implementation specified.
That's the same thing we'd like for class getters/setters, like so:
class Bar {
    get h?() {
        return 2;
    }
}

However, this doesn't compile currently, which seems inconsistent when class methods work with it fine.

@mhegazy seems inconsistent to allow (bodied) optional method but not getters. Thoughts?

If this suggestion is accepted would you guys take a PR for it? (I don't know much about the TypeScript code base but this doesn't seem like it would be a complicated task).

@ahejlsberg I saw that you implemented the ability to optionalize class properties in https://github.com/Microsoft/TypeScript/pull/8625. Is there a specific reason the ability to optionalize getters was omitted from that PR?

Accepting PRs to allow this with similar semantics as optional methods.

I think I'll take a stab at this. It would allow for some better patterns in the state management library I'm creating for my CS498R class (nearly graduated).

Finally had some time to go ahead and implement this. Take a look at the PR here #16344.

To anyone who is skimming through this conversation and wonders why last comment was as much time ago as 29. Jan: the more up-to-date conversation (up to 26 days ago) is on https://github.com/Microsoft/TypeScript/pull/16344

Related to this issue, I wish to propose that setters allow optional arguments, as it seems inconsistent when compared to regular methods, e.g.
class C {
    setX(n?: number) {} // Allowed.
    set x(n?: number) {} // Not allowed: "A 'set' accessor cannot have an optional parameter."
}

The main problem being, you cannot forbid passing undefined to such a setter. Even in a strict setting, the following is valid TypeScript code:
class C {
    set x(n: number) {}
}

const c = new C
c.x = undefined

@inad9300 see #2521

I'm not sure @inad9300 's question is actually about #2521.  set x(n: number | undefined) { } is valid and probably what they meant to specify.  It's not just that setters can't have optional parameters, it's that setters must always have exactly one parameter (and its type must be the same as the getter, if specified).  They also can't have two or ten parameters.
If you think about it for a second, though, it makes sense.  The setter is called when an assignment operator is encountered, but a syntactically valid assignment always has exactly one l-value and one r-value, even if that r-value is undefined.  Thus, you can't ever call the setter function with anything other than exactly one argument, so it doesn't make sense to support declaring it with anything other than exactly one parameter.

any update?
I am tired of writing entity.id(), i want entity.id but still creating the entity without id is not possible
const entity = new Entityt({name:'xyz}) // property id is missing
This should be allowed, which is only possible when id  can be optional property.

You don't need this to solve your specific use case.  You could just declare your class with constructor(other: {name: string}) or constructor(other: Partial<Entity>) or even constructor(other: Omit<Entity, "id">).

@RyanCavanaugh is there any update on this issue? it has literally been years now.

I didn't even notice when I made my previous comments that there are actually at least two issues in this ticket.  One, can I declare a class whose getters are optional?  (I still don't understand the actual use case here -- if you don't new a class instance from an existing implementation, instanceof doesn't work.) Two, why can't I make the argument to a setter optional? (Setters are only called when doing assignments, and there's always exactly one r-value, even if it's explicit null or undefined.)
@xtianus79  are you trying to get an update on "issue one"?  If so, the linked PR #16344 has some back-and-forth but looks like it needs some extra discussion before it gets resolved.

@thw0rted use case could be to not have to use them in call signatures eg when using classes as interfaces

I hadn't thought about the "classes as interfaces" thing because I don't actually do that myself.  Are there particular times when it makes more sense than just writing an explicit interface definition?  If you're making methods (and getters) optional entirely so that you can use the class as an interface, wouldn't it mean that reads always need conditional access even though you know that, for actual instances of the class, they're always defined?

Oof. I just ran into this myself. Funny thing is the IDE (PhpStorm) doesn't see get foo?() as a problem 😵
For now I did get foo?(): string|null which compiles but doesn't seem to be recognized by the IDE. Oh well.

would love to see get fullName?() { implemented as well 👍  (or another solution for getters)

would love to see get fullName?() { implemented as well 👍  (or another solution for getters)

would love to see get fullName?() { implemented as well 👍 (or another solution for getters)

Not done since 2017 😵

would love to see get fullName?() { implemented as well 👍 (or another solution for getters)

Not done since 2017 😵

I support this.

would love to see get fullName?() { implemented as well 👍 (or another solution for getters)

I support this.

would love to see get fullName?() { implemented as well 👍 (or another solution for getters)

this is so hellish to provide custom api !
We work a lot with getter setter and it adding so complicate thing with ts!
My solution is using Implement with interface , but is make thing complicate.
class Plugin {_uid:string}

interface IPerson {
	plugin?:Partial<Plugin>;
}
class Person implements IPerson {
	static create(param:IPerson){return new Person}

	private __PluginUUID: string = null;
	get Plugin(): Plugin {
		return $Composite.getLocalInstance(this.__PluginUUID);
	}
	set Plugin(data: Plugin) {
		this.__PluginUUID = data._uid;
	}
	set plugin(data: Partial<Plugin>) {
		this.__PluginUUID = data._uid;
	}
}

const foo = Person.create({
	plugin:{_uid:''},
})

See this comment for details, but modern class field behavior makes optionalizing getters and setters kind of a tricky territory, since checking for their existence is very awkward. While, relationally, we can probably make up rules for working with them, making them useful in control flow and the like seems much harder; given there's very little apparent demand for it and they seem very awkward to use, maybe we'll just continue to not allow them for now - at least until a better way to handle them in control flow and type guarding becomes apparent (because common assignment patterns potentially throwing would be super annoying).

This feature is sorely needed :/ It's a one-off case that can't even be solved by bypassing this compile error with an option or something.

Just stumbled into this and I'm super disappointed this functionality doesn't exist... it creates some really JavaScript-y errors if you aren't super intentional about checking your potentially undefined getter values ☹


Add .whitesource and configs file to activate whitesource integration

Signed-off-by: Zelin Hao<EMAIL_ADDRESS>opensearch-project/security-dashboards-plugin pull request intake form

Category: (Enhancement, New feature, Bug fix, Test fix, Refactoring, Maintenance, Documentation)

This is a new feature.

Github Issue # or road-map entry, if available:

Description of changes:

We @bbarani already enable the access of WhiteSource integration with Github.com for this repo. However, the automatic PR of .whitesource is not created. We asked for the support from WhiteSource side and they suggested we could raise one by ourselves. This PR will also set the WhiteSource integration config mode LOCAL so it will be using the whitesource.config in the root directory. Dashboards team can modify this configuration on their own to customize it. We are providing the one we had for all repos at this time.
Another PR we created for the same issue. https://github.com/opensearch-project/OpenSearch-Dashboards/pull/999
Please be aware that when this PR is merged, WhiteSource integration might be automatically created CVEs Github issues like these in build repo.

Why these changes are required?

This WhiteSource plugin will help us scan vulnerability on PR level and create issues for CVEs based on level set in "minSeverityLevel": "LOW")

What is the old behavior before changes and new behavior after changes? (Please add any example/logs/screen-shot if available)

Testing done: (Please provide details of testing done: Unit testing, integration testing and manual testing)

TO-DOs, if any: (Please describe pending items and provide Github issues# for each of them)

Is it backport from main branch? (If yes, please add backport PR # and commits #)

By making a contribution to this project, I certify that:
(a) The contribution was created in whole or in part by me and I
have the right to submit it under the open source license
indicated in the file; or
(b) The contribution is based upon previous work that, to the best
of my knowledge, is covered under an appropriate open source
license and I have the right under that license to submit that
work with modifications, whether created in whole or in part
by me, under the same open source license (unless I am
permitted to submit under a different license), as indicated
in the file; or
(c) The contribution was provided directly to me by some other
person who certified (a), (b) or (c) and I have not modified
it.
(d) I understand and agree that this project and the contribution
are public and that a record of the contribution (including all
personal information I submit with it, including my sign-off) is
maintained indefinitely and may be redistributed consistent with
this project or the open source license(s) involved.
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

Thanks @zelinh! A PR just merged to master that fixes CI. Please rebase master and push again.


Update finagle-mysql to 21.11.0

Updates com.twitter:finagle-mysql from 21.9.0 to 21.11.0.
Changelog
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

Ignore future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "com.twitter", artifactId = "finagle-mysql" } ]

labels: library-update, early-semver-minor, semver-spec-minor

Superseded by #2349.


Cannot call model's function

I can't call model's function as described in the readme documentation.
Is there an example how to call model's function using this module?
thank you.

What kind of error are you getting?.

In my case I'm getting a 404 error.


Client Allocation Request for: Lcunyun

Client Allocation Questions
Core Information

Name: Lcunyun
Website / Social Media: http://ipfs.lcunyun.com/
Region: Greater China
DataCap Requested: 1.5TiB
Addresses to be Notarized: f3upvqixcfedlpvbinrtssgsr2adc6ek2vc2jbj3bwu4do2vwzj45m2wysabdww6uitx5luj73cwmhbbgusqoq
Notary Requested: swatchliu

@xjlz2022 Please subscribe to notifications for this Issue to be aware of updates. Notaries may request additional information on the Issue.

Thanks for your request. Can you kindly add more information here?
Is your company located in Greater China？
Please give the following information and provide links to social media/news mentions.
Duration of establishment,
Number of employees,
Business scope and products or services,
Social media link (Weibo, WeChat, Douyin, Zhihu, Facebook, Twitter, Linkedin, e.g.)
Data size to be stored,
Have you already applied for DataCap to another notary, and whether it is accepted or rejected? Is there any reliable DataCap left?
Would you like to submit more company information on www.bytebase.cn?
Would you like to accept our face-to-face visit?

Yes. We are located at Chongqing.
Our company was established in 2020.
We have 120 employees.
We provide mainly conducts business in the field of blockchain distributed storage. Our goal is to construct an interoperable, safe and fast distributed storage node, and to provide trusted, controllable and scalable storage nodes and data storage scheme for enterprises, units and government agencies with storage needs.
Wechat: 星际量子数字永生
Now we need 1.5TiB to store our data.
No, this is the first time we apply for datacap.
Sure, if you want more information about our company, we'll provide it by email.
With pleasure! We are located at Chongqing and welcome you!


Made Unit Calculator responsive

Fixes Issue🛠

Closes #878
Description👨💻

The Unit Calculator interface is adjusted for mobile screens.
Margin added at both ends.
Font size is decreased.

Type of change📄

[x] New feature (non-breaking change which adds functionality)

How this has been tested✅
Tested using inspect element
Checklist✅

[x] My code follows the style guidelines of this project
[x] I have performed a self-review of my own code
[x] I have added demonstration in the form of GIF/video file
[x] I am an Open Source Contributor

Screenshots/GIF📷
Mobile view

Merged 🥳 @m3kvt


Allow for versions of Node.js above 12

Hi there, thanks for this package!
A quick PR to allow for versions of Node.js above 12

Oh tks for contributing @karlhorky. LGTM!

Released in latest npm version, too!

Glad to help, thanks for the merge and release!


Add a test for llama finetuning with FP8 precision

What does this PR do?
Adding example test case for the combination of Llama2-7B + MPI + LoRA + FP8 precision

Fixes # (issue)
Before submitting

[ ] This PR fixes a typo or improves the docs (you can dismiss the other checks if that's the case).
[ ] Did you make sure to update the documentation with your changes?
[ ] Did you write any new necessary tests?

The docs for this PR live here. All of your documentation changes will be reflected on that endpoint. The docs are available until 30 days after the last update.


postLoginHandler

Hi There,
Is it possible to retrieve the access_token from a username/password login in the postLoginHandler.
I have a seperate token I would like to send back with the access_token and I can't quite work out the source.

Hi @Adam-Burke , thanks for getting in touch!  It doesn't look like we pass this back to you in a convenient way, but we are responding with the access token in a cookie, so it is possible to reach into the response and find the header that we set for the cookie, this looks like it does the trick:
app.use(stormpath.init(app, {
  expand: {
    customData: true
  },
  postLoginHandler: function(account, req, res) {
    var accessToken;
    var match = res._headers['set-cookie'].filter(function(cookieStr){
      return cookieStr.match(/access_token=[^;]+/);
    });
    if (match.length === 1) {
      accessToken = match[0].split('=')[1];
    }
    console.log('accessToken?', accessToken);
  }
}));

Can you try this and let me know if it works for you?

Hi @robertjd,
Thanks for your help. I'm using the json api stateless version so it seems as expected that there is no set-cookie header. Is it possible to have to authResult appended to the request object. I've added it in continueWithHandlers as a workaround in the get-token.js
Cheers,
Adam.


undefined symbol: _ZN12class_loader11ClassLoader31setUnmanagedInstanceBeenCreatedEb

When i build ROS2, im getting this error,
Can anyone help me to fix this issue..
Note:
I follow the steps, which is mentioned in the below link,
https://docs.ros.org/en/foxy/Installation/Ubuntu-Development-Setup.html

What does ROS have to do with this repository?


Can't remove virtualenv

When using this plugin, if I ran pipenv --rm in the directory managed by pipenv, it would fail.
$ pipenv --rm
Courtesy Notice: Pipenv found itself running within a virtual environment, so it will automatically use that environment, instead of creating its own for any project. You can set PIPENV_IGNORE_VIRTUALENVS=1 to force pipenv to ignore that environment and create its own instead. You can set PIPENV_VERBOSITY=-1 to suppress this warning.
You are attempting to remove a virtualenv that Pipenv did not create. Aborting.
Aborted!

Thanks for bringing this to my attention @tomyun!
It looks like I wasn't setting the PIPENV_ACTIVE variable, which is what pipenv uses to ensure that it has activated the environment correctly.
pipenv --rm should now work as expected:


Updated CHANGELOG.md and package.json for 1.0.0-rc.19

Codecov Report

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

@@          Coverage Diff          @@
##           master   #273   +/-   ##
=====================================
  Coverage     100%   100%
=====================================
  Files          58     58
  Lines        1349   1349
  Branches      200    200
=====================================
  Hits         1349   1349

Flag
Coverage Δ

#builder
100% <ø> (ø)
:arrow_up:

#runtime
100% <ø> (ø)
:arrow_up:

#srcapp
100% <ø> (ø)
:arrow_up:

Continue to review full report at Codecov.

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


Release

Add TraisBuddy node in .travis.yml
Huge code refactoring

Hey @bluzi,
Your changes look good to me!


About Darksiders Warmastered Edition bad performance

So this game has well known issues related to Media Foundation.
Aside that, the game has really bad performance on official Proton 5.0.9 with AMD Ryzen 5 2600 and Nvidia GTX 1060, which is strange since it should be a d3d11game. Frame rate constantly drops from 60 fps to 20 fps, with both cpu and gpu loads sitting around 30 - 40%
Obviously it works flawlessly on Windows.
If you show me a tutorial on how to make a d3d11 api trace i'll be glad to post the log.

Does it run as badly with DXVK on Windows as well?

So @K0bin has had a look at the game and it seems like this game tries to read data that's supposed to be write-only, i.e. a game bug.


Zod: preprocess enable except on response?

Thanks developers for this awesome tool.
I have a question for zod preprocess.
Expectation
zod preprocess is enabled on body. (In my environment, preprocess is enabled on response only)
Version
  System:
    OS: macOS 13.6.7
    CPU: (8) arm64 Apple M1 Pro
    Memory: 84.08 MB / 32.00 GB
    Shell: 3.2.57 - /bin/bash
  npmPackages:
    axios: ^1.7.4 => 1.7.4
    msw: ^2.3.0 => 2.3.0
    orval: ^7.0.1 => 7.0.1
    react: ^18 => 18.3.1
    swr: ^2.2.5 => 2.2.5
    zod: ^3.23.8 => 3.23.8

My configuration
https://orval.dev/reference/configuration/output#preprocess
orval.config.js
module.exports = {
  client: {
    input: {
      target: './swagger.yaml',
    },
    output: {
      mode: 'tags-split',
      client: 'swr',
      target: 'src/gen/endpoints',
      schemas: 'src/gen/models',
      mock: true,
    },
  },
  zod: {
    input: {
      target: './swagger.yaml',
    },
    output: {
      mode: 'tags-split',
      client: 'zod',
      target: 'src/gen/endpoints',
      fileExtension: '.zod.ts',
      override: {
        zod: {
          strict: {
            response: true,
            query: true,
            param: true,
            header: true,
            body: true
          },
          coerce: {
            response: true,
            query: true,
            param: true,
            header: true,
            body: true
          },
          preprocess: {
            body: { // This does not work
              name: 'bar',
              path: './src/mutators.ts',
            },
          },
        },
      },
    },
  },
}

I read this code and I was convinced preprocess is enabled on response only now.
Do you have a plan to be enable preprocess except on response.
In addition do you have method to enable preprocess except on response without orval.config.js at the moment.

@mktktmr is this your issue: https://github.com/orval-labs/orval/issues/1586 ???

@mktktmr is this your issue: #1586 ???

No. I want to use zod preprocess in request body.
So, I think #1586 is different to this issue.

How about this one https://github.com/orval-labs/orval/issues/1575 ???

@melloware Thanks. #1575 is almost same. I think that both issues mention that preprocess does not work except on response.
      // ...
      override: {
        zod: {
          preprocess: {
            response: { /**/ }, // work well
            body: { /**/ }, // This does not work (mentioned by this issue)
            query: { /**/ }, // This does not work (mentioned by #1575)
            param: { /**/ }, // Maybe this does not work too
            header: { /**/ }, // Maybe This does not work too
          },

@mktktmr thanks for the clarification.  Interested in investigating and providing a PR?  If it works for Resposne then it should be easy to implement that code for the other sections?

@melloware I see. I'll give it a try.


Motion commands in visual mode

There are a few motion commands that do not seem to work in visual mode:

arrow keys
most word motions (e E w W b B …) only w and B seem to work
others?

The arrow keys make the visual selection disappear, but the status bar still says VISUAL and pressing any Vim motion key restores it.

hi, any update on this bug ?

@dylandjian  Almost motions were fixed. But it doesn't support arrow keys.

arrow keys -> #57


Display the old color in ColorPicker for easier comparison

This only affects ColorPickerButton nodes that spawn a ColorPicker, not standalone ColorPickers. The old color is on the left, the new color is on the right.
This partially addresses #7366.
Preview

In hopes for this to get merged before 3.2.3 release maybe worth resolving the conflicting file? 🙂

Rebased and tested again. It still works as expected:

I've rebased and tested it locally, works as intended. Though for a very specific case of the editor theme it may be worth to have some border around the colors, or something:

I've rebased and tested it locally, works as intended. Though for a very specific case of the editor theme it may be worth to have some border around the colors, or something:

@pycbouh Good catch, but I'd prefer adding the border in a separate PR.

@pycbouh Good catch, but I'd prefer adding the border in a separate PR.

I think it will be better when clicking on the old color box. And the color will reset to an old one. This should help those who pick the wrong color and don't want to close a modal.

Rebased and tested again:

Why don't we expose that for any ColorPicker? Not even as an option. The API is sound, it can be exposed to the user, I think.
We can do it in another PR, I'm just not sure why the limitation is here in the first place.

Unlike ColorPickerButtons which let you toggle the ColorPicker's visibility, standalone ColorPickers are always visible by default. Therefore, we need to define some API to reset the old color (or manually set it to an arbitrary value).

Yes, and you've defined it already 🙂
void ColorPicker::set_old_color(const Color &p_color) {
	old_color = p_color;
}

@pycbouh It should be easy to expose those properties but I'd still leave it to a future PR to ensure we can get everything right (including hiding the Old Color property in the inspector when the Display Old Color property is unchecked).

Thanks!

This would need a dedicated PR to backport to 3.x and handle the theme and callback changes.


feat: schematize channel data and bug fixes

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


CreatePersistentSubscription conversations are now completed

Previously, when the server sent a Success response to a CreatePersistentSubscription command, we set the Result of the conversation but did not mark the conversation complete. This meant that the dispatcher would try to resend the conversation on a re-connection and explode.

LGTM