Attestation: Verifier evaluate failed: SGX Verifier: REPORT_DATA is different from that in SGX Quote

When I try to create enclave-cc in HW mode with an encrypted image which requires attestation, it fails with the following error.
$ kubectl describe pod enclave-cc-pod
...
Events:
  Type     Reason     Age                  From               Message
  ----     ------     ----                 ----               -------
  Normal   Scheduled  11m                  default-scheduler  Successfully assigned default/enclave-cc-pod to b77r44u11-node
  Warning  Failed     11m                  kubelet            Failed to pull image "docker.io/niteeshkd/occlum-test:enc2": rpc error: code = Internal desc = Security validate failed: RCAR handshake failed: KBS attest unauthorized, Error Info: ErrorInformation { error_type: "https://github.com/confidential-containers/kbs/errors/AttestationFailed", detail: "Attestation failed: status: Aborted, message: \"Attestation: Verifier evaluate failed: SGX Verifier: REPORT_DATA is different from that in SGX Quote\", details: [], metadata: MetadataMap { headers: {\"content-type\": \"application/grpc\", \"date\": \"Thu, 07 Mar 2024 19:40:50 GMT\", \"content-length\": \"0\"} }" }

KBS log:
$ docker logs trustee-kbs-1
...
[2024-03-07T19:46:30Z INFO  actix_web::middleware::logger] <IP_ADDRESS> "POST /kbs/v0/attest HTTP/1.1" 401 406 "-" "attestation-agent-kbs-client/0.1.0" 0.034660
[2024-03-07T19:51:42Z INFO  api_server::http::resource] Get pkey from auth header
[2024-03-07T19:51:42Z INFO  actix_web::middleware::logger] <IP_ADDRESS> "GET /kbs/v0/resource/default/security-policy/test HTTP/1.1" 401 173 "-" "attestation-agent-kbs-client/0.1.0" 0.000337
[2024-03-07T19:51:42Z INFO  api_server::http::attest] request: Json(Request { version: "0.1.0", tee: Sgx, extra_params: "" })
[2024-03-07T19:51:42Z INFO  actix_web::middleware::logger] <IP_ADDRESS> "POST /kbs/v0/auth HTTP/1.1" 200 74 "-" "attestation-agent-kbs-client/0.1.0" 0.000170
[2024-03-07T19:51:42Z INFO  api_server::http::attest] Cookie 8e202b8ec1344f2a8d4e0c87f66f2a10 attestation Json(Attestation { tee_pubkey: TeePubKey { kty: "RSA", alg: "RSA1_5", k_mod: "tMPfNbkqhn0UkiM1XJBRzVsmxw_A-KJP7Zsd_havVdj1V_GOIr54dEx2c4bvz0J4QnNsblytJ04wM2WA2K1eOQm7TbiOmRdM9MCEPXXTCTCzh-51CqWB8bJnzT-ky9mqTUjgEmZoEjU_eb_vsCE0MKtqe9NnHK6Qc1YNhlfl9xkHfmLDob8egka5lY3JVED_RBdTbkicyCsRNbsn7dJTBLTCSvexDwDRKnDzRv7RES2o6Ys_6JGS2KVNSiZl1-HkUw2-sI39atLB4QY0eebA4jOKPdEl8Ph7Ghc6agXQP_erYbqEUQed89K32iR0CwjucsQc-ZDIVkKrDusPojCUyw", k_exp: "AQAB" }, tee_evidence: "{\"quote\":\"AwACAAAAAAAKAA....VJUSUZJQ0FURS0tLS0tCgA=\"}" })
[2024-03-07T19:51:42Z INFO  actix_web::middleware::logger] <IP_ADDRESS> "POST /kbs/v0/attest HTTP/1.1" 401 406 "-" "attestation-agent-kbs-client/0.1.0" 0.033967

AS log:
$ docker logs trustee-as-1
[2024-03-07T19:35:00Z INFO  grpc_as] CoCo AS:
    v0.1.0
    commit:
    buildtime: 2024-03-06 18:40:46 +00:00
[2024-03-07T19:35:00Z INFO  grpc_as::grpc] Listen socket: <IP_ADDRESS>:50004
[2024-03-07T19:35:00Z INFO  attestation_service::rvps] connect to remote RVPS: http://rvps:50003
[2024-03-07T19:35:00Z INFO  attestation_service::token::simple] No Token Signer key in config file, create an ephemeral key and without CA pubkey cert
[2024-03-07T19:40:50Z WARN  verifier] The input REPORT_DATA of SGX is shorter than 64 bytes, will be padded with '\0'.
[2024-03-07T19:41:05Z WARN  verifier] The input REPORT_DATA of SGX is shorter than 64 bytes, will be padded with '\0'.
[2024-03-07T19:41:29Z WARN  verifier] The input REPORT_DATA of SGX is shorter than 64 bytes, will be padded with '\0'.
[2024-03-07T19:42:18Z WARN  verifier] The input REPORT_DATA of SGX is shorter than 64 bytes, will be padded with '\0'.
[2024-03-07T19:43:42Z WARN  verifier] The input REPORT_DATA of SGX is shorter than 64 bytes, will be padded with '\0'.
[2024-03-07T19:46:30Z WARN  verifier] The input REPORT_DATA of SGX is shorter than 64 bytes, will be padded with '\0'.
[2024-03-07T19:51:42Z WARN  verifier] The input REPORT_DATA of SGX is shorter than 64 bytes, will be padded with '\0'.

$ sudo cat /run/containerd/agent-enclave/<cid>/stderr
...
[2024-03-07T19:51:42Z INFO  enclave_agent::services::images] Pulling "docker.io/niteeshkd/occlum-test:enc2"
[2024-03-07T19:51:42Z INFO  image_rs::resource::kbs] secure channel uses native-aa
[2024-03-07T19:51:42Z WARN  kbs_protocol::client::rcar_client] Authenticating with KBS failed. Perform a new RCAR handshake: ErrorInformation {
        error_type: "https://github.com/confidential-containers/kbs/errors/InvalidRequest",
        detail: "The request is invalid: parse Authorization header failed: invalid Header provided",
    }
[2024-03-07T19:56:46Z INFO  enclave_agent::services::images] Pulling "docker.io/niteeshkd/occlum-test:enc2"
[2024-03-07T19:56:46Z INFO  image_rs::resource::kbs] secure channel uses native-aa
[2024-03-07T19:56:46Z WARN  kbs_protocol::client::rcar_client] Authenticating with KBS failed. Perform a new RCAR handshake: ErrorInformation {
        error_type: "https://github.com/confidential-containers/kbs/errors/InvalidRequest",
        detail: "The request is invalid: parse Authorization header failed: invalid Header provided",
    }

I used the main branch of coco operator to deploy enclave-cc runtimeclass .
@mythi @Xynnn007

I used the main branch of coco operator to deploy enclave-cc runtimeclass .

@niteeshkd I think this gives you v0.8.0 "runtime payload" (enclave-cc installation) but the KBS/AS setup does not match the same release. There were breaking changes on KBS/AS side after v0.8.0 so it's probably best to install "latest" runtime payload to get this to work with Trustee

@mythi You are right that using the latest runtime payload the above error disappears.
Now, i am getting the following error while strating enclave-cc in HW mode.
$ kubectl describe pod enclave-cc-pod
...
   Command:
     /run/rune/boot_instance/build/bin/occlum-run
     /bin/hello_world
   State:          Waiting
     Reason:       ImagePullBackOff
   Last State:     Terminated
     Reason:       StartError
     Message:      failed to create containerd task: failed to create shim task: OCI runtime create failed: runc create failed: unable to start container process: exec: "/run/rune/boot_instance/build/bin/occlum-run": stat /run/rune/boot_instance/build/bin/occlum-run: no such file or directory: unknown
...
   Events:
 Type     Reason     Age                From               Message
 ----     ------     ----               ----               -------
 Normal   Scheduled  2m                 default-scheduler  Successfully assigned default/enclave-cc-pod to b77r44u11-node
 Normal   Pulled     76s                kubelet            Successfully pulled image "docker.io/niteeshkd/occlum-test:enc2" in 43.273s (43.273s including waiting)
 Normal   Created    76s                kubelet            Created container hello-world
 Warning  Failed     76s                kubelet            Error: failed to create containerd task: failed to create shim task: OCI runtime create failed: runc create failed: unable to start container process: exec: "/run/rune/boot_instance/build/bin/occlum-run": stat /run/rune/boot_instance/build/bin/occlum-run: no such file or directory: unknown
 Normal   BackOff    47s                kubelet            Back-off pulling image "docker.io/niteeshkd/occlum-test:enc2"
 Warning  Failed     47s                kubelet            Error: ImagePullBackOff
 Normal   Pulling    34s (x4 over 2m)   kubelet            Pulling image "docker.io/niteeshkd/occlum-test:enc2"
 Warning  Failed     34s (x3 over 75s)  kubelet            Failed to pull image "docker.io/niteeshkd/occlum-test:enc2": rpc error: code = Internal desc = failed to mount "sefs" to "/run/enclave-cc/containers/occlum-test_enc2/rootfs", with error: EIO: I/O error
 Warning  Failed     34s (x3 over 75s)  kubelet            Error: ErrImagePull
 Warning  BackOff    7s (x3 over 74s)   kubelet            Back-off restarting failed container hello-world in pod enclave-cc-pod_default(0f9bfba9-57ac-41e0-bb25-ef69f14c657a)

$ sudo journalctl -xeu containerd | tail -5
Mar 11 16:07:24 b77r44u11-node containerd[3063892]: time="2024-03-11T16:07:24.147019416Z" level=info msg="TaskManager get ImageService succeed." id=e5d510757f43820213cd11494c775ff571df3eff74e9b895a5148b6418bcbfaf
Mar 11 16:07:24 b77r44u11-node containerd[3063892]: time="2024-03-11T16:07:24.147774067Z" level=info msg="New client" source=agent_enclave_container url="tcp://<IP_ADDRESS>:7788"
Mar 11 16:07:24 b77r44u11-node containerd[3063892]: time="2024-03-11T16:07:24.909635703Z" level=error msg="agent enclave container pull image" error="rpc error: code = Internal desc = failed to mount \"sefs\" to \"/run/enclave-cc/containers/occlum-test_enc2/rootfs\", with error: EIO: I/O error" source=agent_enclave_container
Mar 11 16:07:24 b77r44u11-node containerd[3063892]: time="2024-03-11T16:07:24.909749099Z" level=error msg="rune runtime PullImage err. rpc error: code = Internal desc = failed to mount \"sefs\" to \"/run/enclave-cc/containers/occlum-test_enc2/rootfs\", with error: EIO: I/O error"
Mar 11 16:07:24 b77r44u11-node containerd[3063892]: time="2024-03-11T16:07:24.910018032Z" level=error msg="PullImage \"docker.io/niteeshkd/occlum-test:enc2\" failed" error="rpc error: code = Internal desc = failed to mount \"sefs\" to \"/run/enclave-cc/containers/occlum-test_enc2/rootfs\", with error: EIO: I/O error

$ sudo cat /run/containerd/agent-enclave/a9b06d3331debf8de387fd004be59dc6849bdba4e46aeb96027b02cd45694dc5/stderr
[2024-03-11T16:01:08Z INFO  enclave_agent] ttRPC server started: "tcp://<IP_ADDRESS>:7788"
[2024-03-11T16:01:08Z INFO  enclave_agent::services::images] Pulling "docker.io/niteeshkd/occlum-test:enc2"
[2024-03-11T16:01:08Z INFO  image_rs::resource::kbs] secure channel uses native-aa
[2024-03-11T16:01:09Z WARN  kbs_protocol::client::rcar_client] Authenticating with KBS failed. Perform a new RCAR handshake: ErrorInformation {
        error_type: "https://github.com/confidential-containers/kbs/errors/InvalidRequest",
        detail: "The request is invalid: parse Authorization header failed: invalid Header provided",
    }
[2024-03-11T16:01:09Z INFO  sigstore::cosign::client_builder] Rekor public key not provided. Rekor integration disabled
[2024-03-11T16:01:09Z INFO  sigstore::cosign::client_builder] No Fulcio cert has been provided. Fulcio integration disabled
[2024-03-11T16:01:10Z INFO  sigstore::cosign::signature_layers] Ignoring bundle, rekor public key not provided to verification client bundle="{\"SignedEntryTimestamp\":\"MEUCIQC4lVD0V5TL6h0SPaqQe6RVGLW2YvnpqtYvvbWiwwqYxwIgXvKBs2F8wqMtcRMxSfDkpQa3kYQha5jfnsR5l0lmTqo=\",\"Payload\":{\"body\":\"eyJhcGlWZXJzaW9uIjoiMC4wLjEiLCJraW5kIjoiaGFzaGVkcmVrb3JkIiwic3BlYyI6eyJkYXRhIjp7Imhhc2giOnsiYWxnb3JpdGhtIjoic2hhMjU2IiwidmFsdWUiOiI1ZDI5N2ExZTZmNWRkYTkwYjRjY2Q5N2QwNGU2MGVjMmM3MzdhYmE5MjI3ODFhNWRjZWRmNWUzM2I1NDE3YTY4In19LCJzaWduYXR1cmUiOnsiY29udGVudCI6Ik1FVUNJUUNRWHo2enJnYWJYQmVXVEJiWWI2RUYvcmcyT2JwZEtDcXhaZlZzbzlkVmRnSWdadkxMRTFreG9CaVovVzlhd2VIYVdmYTduN0VSaTlZdUhkVHlScUp5NzU4PSIsInB1YmxpY0tleSI6eyJjb250ZW50IjoiTFMwdExTMUNSVWRKVGlCUVZVSk1TVU1nUzBWWkxTMHRMUzBLVFVacmQwVjNXVWhMYjFwSmVtb3dRMEZSV1VsTGIxcEplbW93UkVGUlkwUlJaMEZGUmpKcE9GcGxNakZXTmtnd0t6aHZPRTE2Wnk5c1dtdHZZekkwWlFwWWJXNXVUWFF5ZDFBMU9YSkxNMWRGVTI5QlNtWTBhazFHZWpKRmNVVmpkRE1yTkdVMmIxTnZXalJTVGpWa09GcHFlbHBsVTJ4aFZUWjNQVDBLTFMwdExTMUZUa1FnVUZWQ1RFbERJRXRGV1MwdExTMHRDZz09In19fX0=\",\"integratedTime\":1709836174,\"logIndex\":76402918,\"logID\":\"c0d23d6ad406973f9559f3ba2d1ca01f84147d8ffc5b8445c224f98b9591801d\"}}"
[2024-03-11T16:01:11Z WARN  kbs_protocol::client::rcar_client] Authenticating with KBS failed. Perform a new RCAR handshake: ErrorInformation {
        error_type: "https://github.com/confidential-containers/kbs/errors/InvalidRequest",
        detail: "The request is invalid: parse Authorization header failed: invalid Header provided",
    }
[2024-03-11T16:01:40Z INFO  enclave_agent::services::images] Pull image "docker.io/niteeshkd/occlum-test:enc2" successfully
[2024-03-11T16:01:41Z INFO  enclave_agent::services::images] Pulling "docker.io/niteeshkd/occlum-test:enc2"
[2024-03-11T16:01:41Z INFO  image_rs::resource::kbs] secure channel uses native-aa
[2024-03-11T16:01:56Z INFO  enclave_agent::services::images] Pulling "docker.io/niteeshkd/occlum-test:enc2"
[2024-03-11T16:01:56Z INFO  image_rs::resource::kbs] secure channel uses native-aa
[2024-03-11T16:02:22Z INFO  enclave_agent::services::images] Pulling "docker.io/niteeshkd/occlum-test:enc2"
[2024-03-11T16:02:22Z INFO  image_rs::resource::kbs] secure channel uses native-aa
[2024-03-11T16:03:03Z INFO  enclave_agent::services::images] Pulling "docker.io/niteeshkd/occlum-test:enc2"
[2024-03-11T16:03:03Z INFO  image_rs::resource::kbs] secure channel uses native-aa
[2024-03-11T16:04:32Z INFO  enclave_agent::services::images] Pulling "docker.io/niteeshkd/occlum-test:enc2"
[2024-03-11T16:04:32Z INFO  image_rs::resource::kbs] secure channel uses native-aa
[2024-03-11T16:07:24Z INFO  enclave_agent::services::images] Pulling "docker.io/niteeshkd/occlum-test:enc2"
[2024-03-11T16:07:24Z INFO  image_rs::resource::kbs] secure channel uses native-aa

Any suggestion?
@Xynnn007

The above problem also appars while luanching enclave-cc in SIM mode using the operator/tests/e2e/enclave-cc-pod-sim.yaml .
$ kubectl apply -f tests/e2e/enclave-cc-pod-sim.yaml

$ kubectl describe pod enclave-cc-pod-sim
...
      Message:      failed to create containerd task: failed to create shim task: OCI runtime create failed: runc create failed: unable to start container process: exec: "/run/rune/boot_instance/build/bin/occlum-run": stat /run/rune/boot_instance/build/bin/occlum-run: no such file or directory: unknown
...
Events:
  Type     Reason     Age                    From               Message
  ----     ------     ----                   ----               -------
  Normal   Scheduled  6m42s                  default-scheduler  Successfully assigned default/enclave-cc-pod-sim to b77r44u11-node
  Normal   Pulled     6m38s                  kubelet            Successfully pulled image "docker.io/huaijin20191223/scratch-base:v1.8" in 4.169s (4.169s including waiting)
  Normal   Created    6m38s                  kubelet            Created container hello-world
  Warning  Failed     6m37s                  kubelet            Error: failed to create containerd task: failed to create shim task: OCI runtime create failed: runc create failed: unable to start container process: exec: "/run/rune/boot_instance/build/bin/occlum-run": stat /run/rune/boot_instance/build/bin/occlum-run: no such file or directory: unknown
  Warning  Failed     5m45s (x3 over 6m37s)  kubelet            Failed to pull image "docker.io/huaijin20191223/scratch-base:v1.8": rpc error: code = Internal desc = failed to mount "sefs" to "/run/enclave-cc/containers/scratch-base_v1.8/rootfs", with error: EIO: I/O error
  Warning  Failed     5m45s (x3 over 6m37s)  kubelet            Error: ErrImagePull
  Normal   BackOff    5m11s (x2 over 6m11s)  kubelet            Back-off pulling image "docker.io/huaijin20191223/scratch-base:v1.8"
  Warning  Failed     5m11s (x2 over 6m11s)  kubelet            Error: ImagePullBackOff
  Warning  BackOff    4m14s (x8 over 6m36s)  kubelet            Back-off restarting failed container hello-world in pod enclave-cc-pod-sim_default(c6bd97f7-a71f-4df3-976c-1c54a0ccb40e)
  Normal   Pulling    91s (x6 over 6m42s)    kubelet            Pulling image "docker.io/huaijin20191223/scratch-base:v1.8"

After replacing "boot_instance" by "occlum_instance" in pod yaml file, the error stat /run/rune/boot_instance/build/bin/occlum-run: no such file or directory disappeared but the other error failed to mount \"sefs\" to \"/run/enclave-cc/containers/scratch-base_v1.8/rootfs\", with error: EIO: I/O error"  is still there.
$ kubectl apply -f tests/e2e/enclave-cc-pod-sim.yaml

$ kubectl describe pod enclave-cc-pod-sim
...
Events:
  Type     Reason     Age                    From               Message
  ----     ------     ----                   ----               -------
  Normal   Scheduled  7m2s                   default-scheduler  Successfully assigned default/enclave-cc-pod-sim to b77r44u11-node
  Normal   Pulled     6m57s                  kubelet            Successfully pulled image "docker.io/huaijin20191223/scratch-base:v1.8" in 4.81s (4.81s including waiting)
  Normal   Created    6m57s                  kubelet            Created container hello-world
  Normal   Started    6m57s                  kubelet            Started container hello-world
  Warning  Failed     6m5s (x3 over 6m56s)   kubelet            Failed to pull image "docker.io/huaijin20191223/scratch-base:v1.8": rpc error: code = Internal desc = failed to mount "sefs" to "/run/enclave-cc/containers/scratch-base_v1.8/rootfs", with error: EIO: I/O error
  Warning  Failed     6m5s (x3 over 6m56s)   kubelet            Error: ErrImagePull
  Normal   BackOff    5m25s (x2 over 6m32s)  kubelet            Back-off pulling image "docker.io/huaijin20191223/scratch-base:v1.8"
  Warning  Failed     5m25s (x2 over 6m32s)  kubelet            Error: ImagePullBackOff
  Warning  BackOff    4m33s (x8 over 6m55s)  kubelet            Back-off restarting failed container hello-world in pod enclave-cc-pod-sim_default(b50cd147-7d21-44de-9ef5-4436de2cf1fe)
  Normal   Pulling    113s (x6 over 7m2s)    kubelet            Pulling image "docker.io/huaijin20191223/scratch-base:v1.8"

@niteeshkd can you share the agent log too

@mythi did you mean the content of /run/containerd/agent-enclave/<cid>stderr ?  It is here.
$ sudo cat /run/containerd/agent-enclave/428de9f548296340f18cba718d8441a87de54c28007ac98c78f58de6f4fbd0a5/stderr
[2024-03-11T19:43:08Z INFO  enclave_agent] ttRPC server started: "tcp://<IP_ADDRESS>:7788"
[2024-03-11T19:43:08Z INFO  enclave_agent::services::images] Pulling "docker.io/huaijin20191223/scratch-base:v1.8"
[2024-03-11T19:43:09Z INFO  enclave_agent::services::images] Pull image "docker.io/huaijin20191223/scratch-base:v1.8" successfully
[2024-03-11T19:43:10Z INFO  enclave_agent::services::images] Pulling "docker.io/huaijin20191223/scratch-base:v1.8"
[2024-03-11T19:43:23Z INFO  enclave_agent::services::images] Pulling "docker.io/huaijin20191223/scratch-base:v1.8"
[2024-03-11T19:44:01Z INFO  enclave_agent::services::images] Pulling "docker.io/huaijin20191223/scratch-base:v1.8"
[2024-03-11T19:45:58Z INFO  enclave_agent::services::images] Pulling "docker.io/huaijin20191223/scratch-base:v1.8"

There's probably something missing on the operator side we haven't updated since moving to the new unified bundle in this repo. Is it possible to retry so that the images downloaded by enclave agent are removed?

I re-deployed the operator after cloning it fresh and modifying the following files.
$ git diff
diff --git a/config/samples/enclave-cc/base/ccruntime-enclave-cc.yaml b/config/samples/enclave-cc/base/ccruntime-enclave-cc.yaml
index 1fbc5cd..cc42e03 100644
--- a/config/samples/enclave-cc/base/ccruntime-enclave-cc.yaml
+++ b/config/samples/enclave-cc/base/ccruntime-enclave-cc.yaml
@@ -9,7 +9,7 @@ spec:
       node.kubernetes.io/worker: ""
   config:
     installType: bundle
-    payloadImage: quay.io/confidential-containers/runtime-payload:enclave-cc-HW-cc-kbc-v0.8.0
+    payloadImage: quay.io/confidential-containers/runtime-payload-ci:enclave-cc-HW-cc-kbc-latest
     installDoneLabel:
       confidentialcontainers.org/enclave-cc: "true"
     uninstallDoneLabel:
@@ -161,6 +161,7 @@ spec:
       - name: "CONFIGURE_CC"
         value: "yes"
       - name: "DECRYPT_CONFIG"
-        value: "ewogICAgImtleV9wcm92aWRlciI6ICJwcm92aWRlcjphdHRlc3RhdGlvbi1hZ2VudDpzYW1wbGVfa2JjOjoxMjcuMC4wLjE6NTAwMDAiLAogICAgInNlY3VyaXR5X3ZhbGlkYXRlIjogZmFsc2UKfQo="
+        #value: "ewogICAgImtleV9wcm92aWRlciI6ICJwcm92aWRlcjphdHRlc3RhdGlvbi1hZ2VudDpzYW1wbGVfa2JjOjoxMjcuMC4wLjE6NTAwMDAiLAogICAgInNlY3VyaXR5X3ZhbGlkYXRlIjogZmFsc2UKfQo="
+        value: "ewogICAgImtleV9wcm92aWRlciI6ICJwcm92aWRlcjphdHRlc3RhdGlvbi1hZ2VudDpjY19rYmM6Omh0dHA6Ly8wLjAuMC4wOjgwODAiLAogICAgInNlY3VyaXR5X3ZhbGlkYXRlIjogZmFsc2UgCn0K"
       - name: "OCICRYPT_CONFIG"
         value: "ewogICAgImtleS1wcm92aWRlcnMiOiB7CiAgICAgICAgImF0dGVzdGF0aW9uLWFnZW50IjogewogICAgICAgICAgICAibmF0aXZlIjogImF0dGVzdGF0aW9uLWFnZW50IgogICAgICAgIH0KICAgIH0KfQo="
diff --git a/config/samples/enclave-cc/sim/kustomization.yaml b/config/samples/enclave-cc/sim/kustomization.yaml
index 932528c..4b58e1a 100644
--- a/config/samples/enclave-cc/sim/kustomization.yaml
+++ b/config/samples/enclave-cc/sim/kustomization.yaml
@@ -4,7 +4,7 @@ resources:
 nameSuffix: -sgx-mode-sim

 images:
-- name: quay.io/confidential-containers/runtime-payload
-  newTag: enclave-cc-SIM-sample-kbc-v0.8.0
+- name: quay.io/confidential-containers/runtime-payload-ci
+  newTag: enclave-cc-SIM-sample-kbc-latest
 - name: quay.io/confidential-containers/reqs-payload
   newTag: latest
diff --git a/tests/e2e/enclave-cc-pod-sim.yaml b/tests/e2e/enclave-cc-pod-sim.yaml
index 7749eed..18ce321 100644
--- a/tests/e2e/enclave-cc-pod-sim.yaml
+++ b/tests/e2e/enclave-cc-pod-sim.yaml
@@ -13,5 +13,5 @@ spec:
       value: "0"
     workingDir: "/run/rune/boot_instance/"
     command:
-    - /run/rune/boot_instance/build/bin/occlum-run
+    - /run/rune/occlum_instance/build/bin/occlum-run
     - /bin/hello_world

Then,  i retried launching the enclave-cc in SIM mode. I still see the same errors.
$ kubectl apply -f tests/e2e/enclave-cc-pod-sim.yaml
$ kubectl describe pod enclave-cc-pod-sim
...
Events:
  Type     Reason     Age                   From               Message
  ----     ------     ----                  ----               -------
  Normal   Scheduled  5m47s                 default-scheduler  Successfully assigned default/enclave-cc-pod-sim to b77r44u11-node
  Normal   Pulled     5m40s                 kubelet            Successfully pulled image "docker.io/huaijin20191223/scratch-base:v1.8" in 6.58s (6.58s including waiting)
  Normal   Created    5m40s                 kubelet            Created container hello-world
  Normal   Started    5m39s                 kubelet            Started container hello-world
  Normal   BackOff    5m11s                 kubelet            Back-off pulling image "docker.io/huaijin20191223/scratch-base:v1.8"
  Warning  Failed     5m11s                 kubelet            Error: ImagePullBackOff
  Normal   Pulling    4m8s (x5 over 5m46s)  kubelet            Pulling image "docker.io/huaijin20191223/scratch-base:v1.8"
  Warning  Failed     4m8s (x4 over 5m38s)  kubelet            Failed to pull image "docker.io/huaijin20191223/scratch-base:v1.8": rpc error: code = Internal desc = failed to mount "sefs" to "/run/enclave-cc/containers/scratch-base_v1.8/rootfs", with error: EIO: I/O error
  Warning  Failed     4m8s (x4 over 5m38s)  kubelet            Error: ErrImagePull
  Warning  BackOff    44s (x19 over 5m37s)  kubelet            Back-off restarting failed container hello-world in pod enclave-cc-pod-sim_default(46ce8bba-1e05-4668-9f3d-3b989fa0b592)

$ sudo cat /run/containerd/agent-enclave/25c5da12bb20face9a56fd0c58944bfaac3b82601af57c34dcb22875ba65e4ce/stderr
[2024-03-12T17:56:59Z INFO  enclave_agent] ttRPC server started: "tcp://<IP_ADDRESS>:7788"
[2024-03-12T17:56:59Z INFO  enclave_agent::services::images] Pulling "docker.io/huaijin20191223/scratch-base:v1.8"
[2024-03-12T17:56:59Z INFO  enclave_agent::services::images] Pull image "docker.io/huaijin20191223/scratch-base:v1.8" successfully
[2024-03-12T17:57:01Z INFO  enclave_agent::services::images] Pulling "docker.io/huaijin20191223/scratch-base:v1.8"
[2024-03-12T17:57:13Z INFO  enclave_agent::services::images] Pulling "docker.io/huaijin20191223/scratch-base:v1.8"

Looks like workingDir is not updated in the yaml?

You are right. That was my mistake. I did not notice that. After correcting it, i am able to launch enclave-cc in SIM mode which is a good news.
When I try to launch encalve-cc with an encrypted image in HW mode, it fails with the similar message. I tried redeploying operator but that did not help.
$ cat enclave-cc-pod-encrypted.yaml
apiVersion: v1
kind: Pod
metadata:
  name: enclave-cc-pod
spec:
  containers:
  #- image: ghcr.io/confidential-containers/test-container-enclave-cc:encrypted
  #- image: docker.io/niteeshkd/occlum-hello-world:enc
  - image: docker.io/niteeshkd/occlum-test:enc2
    imagePullPolicy: IfNotPresent
    name: hello-world
    resources:
      limits:
        sgx.intel.com/epc: 256Mi
    env:
    - name: OCCLUM_RELEASE_ENCLAVE
      value: "1"
    workingDir: "/run/rune/occlum_instance/"
    command:
    - /run/rune/occlum_instance/build/bin/occlum-run
    - /bin/hello_world
  runtimeClassName: enclave-cc

  $ kubectl apply -f ./enclave-cc-pod-encrypted.yaml

  $ kubectl describe pod enclave-cc-pod
  ...
  Events:
  Type     Reason     Age                From               Message
  ----     ------     ----               ----               -------
  Normal   Scheduled  81s                default-scheduler  Successfully assigned default/enclave-cc-pod to b77r44u11-node
  Normal   Pulled     36s                kubelet            Successfully pulled image "docker.io/niteeshkd/occlum-test:enc2" in 43.662s (43.662s including waiting)
  Normal   Created    36s                kubelet            Created container hello-world
  Normal   Started    36s                kubelet            Started container hello-world
  Normal   Pulling    13s (x3 over 80s)  kubelet            Pulling image "docker.io/niteeshkd/occlum-test:enc2"
  Warning  Failed     12s (x2 over 23s)  kubelet            Failed to pull image "docker.io/niteeshkd/occlum-test:enc2": rpc error: code = Internal desc = failed to mount "sefs" to "/run/enclave-cc/containers/occlum-test_enc2/rootfs", with error: EIO: I/O error
  Warning  Failed     12s (x2 over 23s)  kubelet            Error: ErrImagePull
  Normal   BackOff    1s                 kubelet            Back-off pulling image "docker.io/niteeshkd/occlum-test:enc2"
  Warning  Failed     1s                 kubelet            Error: ImagePullBackOff

$ sudo cat /run/containerd/agent-enclave/abf30082d10898dd4a033864f5d6a3fce9080aa930f60ae53c0d744c44fef1a5/stderr
[2024-03-12T20:57:03Z INFO  enclave_agent] ttRPC server started: "tcp://<IP_ADDRESS>:7788"
[2024-03-12T20:57:03Z INFO  enclave_agent::services::images] Pulling "docker.io/niteeshkd/occlum-test:enc2"
[2024-03-12T20:57:04Z INFO  image_rs::resource::kbs] secure channel uses native-aa
[2024-03-12T20:57:04Z WARN  kbs_protocol::client::rcar_client] Authenticating with KBS failed. Perform a new RCAR handshake: ErrorInformation {
        error_type: "https://github.com/confidential-containers/kbs/errors/InvalidRequest",
        detail: "The request is invalid: parse Authorization header failed: invalid Header provided",
    }
[2024-03-12T20:57:05Z INFO  sigstore::cosign::client_builder] Rekor public key not provided. Rekor integration disabled
[2024-03-12T20:57:05Z INFO  sigstore::cosign::client_builder] No Fulcio cert has been provided. Fulcio integration disabled
[2024-03-12T20:57:05Z INFO  sigstore::cosign::signature_layers] Ignoring bundle, rekor public key not provided to verification client bundle="{\"SignedEntryTimestamp\":\"MEUCIQC4lVD0V5TL6h0SPaqQe6RVGLW2YvnpqtYvvbWiwwqYxwIgXvKBs2F8wqMtcRMxSfDkpQa3kYQha5jfnsR5l0lmTqo=\",\"Payload\":{\"body\":\"eyJhcGlWZXJzaW9uIjoiMC4wLjEiLCJraW5kIjoiaGFzaGVkcmVrb3JkIiwic3BlYyI6eyJkYXRhIjp7Imhhc2giOnsiYWxnb3JpdGhtIjoic2hhMjU2IiwidmFsdWUiOiI1ZDI5N2ExZTZmNWRkYTkwYjRjY2Q5N2QwNGU2MGVjMmM3MzdhYmE5MjI3ODFhNWRjZWRmNWUzM2I1NDE3YTY4In19LCJzaWduYXR1cmUiOnsiY29udGVudCI6Ik1FVUNJUUNRWHo2enJnYWJYQmVXVEJiWWI2RUYvcmcyT2JwZEtDcXhaZlZzbzlkVmRnSWdadkxMRTFreG9CaVovVzlhd2VIYVdmYTduN0VSaTlZdUhkVHlScUp5NzU4PSIsInB1YmxpY0tleSI6eyJjb250ZW50IjoiTFMwdExTMUNSVWRKVGlCUVZVSk1TVU1nUzBWWkxTMHRMUzBLVFVacmQwVjNXVWhMYjFwSmVtb3dRMEZSV1VsTGIxcEplbW93UkVGUlkwUlJaMEZGUmpKcE9GcGxNakZXTmtnd0t6aHZPRTE2Wnk5c1dtdHZZekkwWlFwWWJXNXVUWFF5ZDFBMU9YSkxNMWRGVTI5QlNtWTBhazFHZWpKRmNVVmpkRE1yTkdVMmIxTnZXalJTVGpWa09GcHFlbHBsVTJ4aFZUWjNQVDBLTFMwdExTMUZUa1FnVUZWQ1RFbERJRXRGV1MwdExTMHRDZz09In19fX0=\",\"integratedTime\":1709836174,\"logIndex\":76402918,\"logID\":\"c0d23d6ad406973f9559f3ba2d1ca01f84147d8ffc5b8445c224f98b9591801d\"}}"
[2024-03-12T20:57:06Z WARN  kbs_protocol::client::rcar_client] Authenticating with KBS failed. Perform a new RCAR handshake: ErrorInformation {
        error_type: "https://github.com/confidential-containers/kbs/errors/InvalidRequest",
        detail: "The request is invalid: parse Authorization header failed: invalid Header provided",
    }
[2024-03-12T20:57:35Z INFO  enclave_agent::services::images] Pull image "docker.io/niteeshkd/occlum-test:enc2" successfully
[2024-03-12T20:57:47Z INFO  enclave_agent::services::images] Pulling "docker.io/niteeshkd/occlum-test:enc2"
[2024-03-12T20:57:47Z INFO  image_rs::resource::kbs] secure channel uses native-aa
[2024-03-12T20:57:58Z INFO  enclave_agent::services::images] Pulling "docker.io/niteeshkd/occlum-test:enc2"
[2024-03-12T20:57:58Z INFO  image_rs::resource::kbs] secure channel uses native-aa
[2024-03-12T20:58:34Z INFO  enclave_agent::services::images] Pulling "docker.io/niteeshkd/occlum-test:enc2"
[2024-03-12T20:58:34Z INFO  image_rs::resource::kbs] secure channel uses native-aa

$ docker logs trustee-as-1
[2024-03-12T20:56:02Z INFO  grpc_as] CoCo AS:
    v0.1.0
    commit:
    buildtime: 2024-03-06 18:40:46 +00:00
[2024-03-12T20:56:02Z INFO  grpc_as::grpc] Listen socket: <IP_ADDRESS>:50004
[2024-03-12T20:56:02Z INFO  attestation_service::rvps] connect to remote RVPS: http://rvps:50003
[2024-03-12T20:56:02Z INFO  attestation_service::token::simple] No Token Signer key in config file, create an ephemeral key              and without CA pubkey cert
[2024-03-12T20:57:04Z WARN  verifier] The input REPORT_DATA of SGX is shorter than 64 bytes, will be padded with '\0'.
[2024-03-12T20:57:04Z INFO  verifier::sgx::claims]
    Parsed Evidence claims map:
    {"body": Object {"attributes.flags": String("0500000000000000"), "attributes.xfrm": String("e700000000000000"), "config_id": String("0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000<PHONE_NUMBER>000000000"), "config_svn": String("0000"), "cpu_svn": String("0606131503ff00040000000000000000"), "isv_ext_prod_i d": String("00000000000000000000000000000000"), "isv_family_id": String("00000000000000000000000000000000"), "isv_prod_id":  String("0000"), "isv_svn": String("0000"), "misc_select": String("00000000"), "mr_enclave": String("33789b6aca278dbe3a5442 cf3fe4ea530d7d9560d743ca6bd50729d10f7d4ec6"), "mr_signer": String("83d719e77deaca1470f6baf62a4d774303c899db69020f9c70ee1dfc08c7ce9e"), "report_data": String("48b12112e96c50e1040f9c745b7df078a04fd3ec05264ebd0093dd638c2a85edca1c47878a19b668c525d029fb5eb5d200000000000000000000000000000000"), "reserved1": String("000000000000000000000000"), "reserved2": String("0000000000000000000000000000000000000000000000000000000000000000"), "reserved3": String("0000000000000000000000000000000000000000000000000000000000000000"), "reserved4": String("000000000000000000000000000000000000000000000000000000000000000000000000000000000000")}, "header": Object {"att_key_data_0": String("00000000"), "att_key_type": String("0200"), "pce_svn": String("0f00"), "qe_svn": String("0a00"), "user_data": String("c2001edae03836fe7b2d57a05245d94f00000000"), "vendor_id": String("939a7233f79c4ca9940a0db3957f0607"), "version": String("0300")}, "init_data": String("00000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000"), "report_data": String("48b12112e96c50e1040f9c745b7df078a04fd3ec05264ebd0093dd638c2a85edca1c47878a19b668c525d029fb5eb5d200000000000000000000000000000000")}

$ docker logs trustee-kbs-1
[2024-03-12T20:56:02Z INFO  kbs] Using config file /etc/kbs-config.toml
[2024-03-12T20:56:02Z INFO  api_server::attestation::coco::grpc] Default AS connection pool size (100) is used
[2024-03-12T20:56:02Z INFO  api_server::attestation::coco::grpc] connect to remote AS [http://as:50004] with pool size 100
[2024-03-12T20:56:02Z INFO  api_server] Starting HTTP server at [<IP_ADDRESS>:8080]
[2024-03-12T20:56:02Z INFO  actix_server::builder] starting 192 workers
[2024-03-12T20:56:02Z INFO  actix_server::server] Tokio runtime found; starting in existing Tokio runtime
[2024-03-12T20:57:04Z INFO  api_server::http::resource] Get pkey from auth header
[2024-03-12T20:57:04Z INFO  actix_web::middleware::logger] <IP_ADDRESS> "GET /kbs/v0/resource/default/security-policy/test HTTP/1.1" 401 173 "-" "attestation-agent-kbs-client/0.1.0" 0.000294
[2024-03-12T20:57:04Z INFO  api_server::http::attest] request: Json(Request { version: "0.1.0", tee: Sgx, extra_params: "" })
[2024-03-12T20:57:04Z INFO  actix_web::middleware::logger] <IP_ADDRESS> "POST /kbs/v0/auth HTTP/1.1" 200 74 "-" "attestation-agent-kbs-client/0.1.0" 0.000230
[2024-03-12T20:57:04Z INFO  api_server::http::attest] Cookie 2b17aa83a18645f189218e60bd9b1378 attestation Json(Attestation { tee_pubkey: TeePubKey { kty: "RSA", alg: "RSA1_5", k_mod: "y19Ke-OzcVrOdULIedUxtGkrzKOAAtFU1yIl6aMmrXrbC2DeHATMMC6yhvGs4oQQZBCsluKdnsERI_MTfli5IKFqDHTBkLF3hcwGhc26FdVu3w-7HyVtHyVjBeb3k_2yDnsEcUHKeIX3OHS0ry1kCNWgwMf4fpuQOahKwl9goODuysm1v3of06tLoYLsec-ARIij6zb0Y5nAvH7M3pYV2IjzD8GOC7GvSsRaQmFCjaQDKo2Rr6NTgb_lYRArEeT3nX1m8UHtGwAeWD7hL3fgkJHHlh7ooNOMAQW5IA9Z0leXoAfFm8VvkBhvIO4ezxRpt2gp6f74E14NYQ7adCKHTQ", k_exp: "AQAB" }, tee_evidence: "{\"quote\":\"[encoded data, 6308 characters]\"}" })
...

@niteeshkd You need to add a file under the storage path of kbs. s.t. kbs-storage/default/security-policy/test
{
    "default": [{"type": "insecureAcceptAnything"}],
    "transports": {}
}

@Xynnn007 I have added that file.
$ tree data/kbs-storage
data/kbs-storage
+-- default
    +-- cosign-key
    |   +-- 1
    +-- image-kek
    |   +-- 29e4566e-f7b8-494b-8ea6-8d09d41e6a2e
    +-- security-policy
        +-- test

$ cat data/kbs-storage/default/security-policy/test
{
    "default": [{"type": "reject"}],
    "transports": {
        "docker": {
            "docker.io/niteeshkd/occlum-test:enc2": [
                {
                    "type": "sigstoreSigned",
                    "keyPath": "kbs:///default/cosign-key/1"
                }
            ]
        }
    }
}

@niteeshkd Could you show the whole log of kbs? If it is too long, please send me via slack. You can find me Ding in the channel https://cloud-native.slack.com/archives/C0496GDCBAR

Just slacked .
https://cloud-native.slack.com/archives/C0496GDCBAR/p1710299603786749

I checked the KBS side log, there is an entry
[2024-03-12T20:57:06Z INFO  api_server::http::resource] Resource description: ResourceDesc { repository_name: "default", resource_type: "image-kek", resource_tag: "29e4566e-f7b8-494b-8ea6-8d09d41e6a2e" }
[2024-03-12T20:57:06Z INFO  actix_web::middleware::logger] <IP_ADDRESS> "GET /kbs/v0/resource/default/image-kek/29e4566e-f7b8-494b-8ea6-8d09d41e6a2e HTTP/1.1" 200 530 "-" "attestation-agent-kbs-client/0.1.0" 0.003895

The 200 here http:ok status means that the image decryption key is retrieved by enclave-agent successfully. So the next steps would be downloading the encrypted tar and decrypt.
Thus we can see
[2024-03-12T20:57:35Z INFO  enclave_agent::services::images] Pull image "docker.io/niteeshkd/occlum-test:enc2" successfully

The image pulling is done. However I am confused why at 2024-03-12T20:57:47Z, s.t. only 12 seconds later it retries to pull image.
[2024-03-12T20:57:47Z INFO  enclave_agent::services::images] Pulling "docker.io/niteeshkd/occlum-test:enc2"

While the error looks different here, I was suggesting earlier to test with our image to make sure the image does not have issues.

@mythi I tested with the image mentioned at ci-setup . It works fine.
The docker image (i.e. docker.io/niteeshkd/occlum-test:unenc ) which i built using occlum dev container works fine when i don't use attestation (i.e. "security_validate":  false ).
But, when I use its encrypted image docker.io/niteeshkd/occlum-test:enc2  with attestatation (i.e. "security_validate":  true ), then it does not work. I am creating the encrypted image using skopeo with trustee coco-keyprovider listening at port 50000. I use the following steps to encrypt it and register its key with trustee KBS.
$ cat ocicrypt.conf
{
  "key-providers": {
	"attestation-agent": {
	  "grpc": "<IP_ADDRESS>:50000"
}}}

$ OCICRYPT_KEYPROVIDER_CONFIG=ocicrypt.conf skopeo copy --insecure-policy --encryption-key provider:attestation-agent docker://docker.io/niteeshkd/occlum-test:unenc docker://docker.io/niteeshkd/occlum-test:enc2

I noticed that when i pull the encrypted docker image niteeshkd/occlum-test:enc2 , it complains as follows.
$ docker pull docker.io/niteeshkd/occlum-test:enc2
enc2: Pulling from niteeshkd/occlum-test
f53005d5071f: Extracting [==================================================>]  15.44MB/15.44MB
failed to register layer: archive/tar: invalid tar header

But, I don't see such issue while pulling with the unencrypted docker image niteeshkd/occlum-test:unenc or  the image mentioned at ci-setup which is labelled with enc_key & keyid.
So, it seems either skopeo with coco-keyprovider has some issue while creating encrypted image and pushing it to the docker or docker has some issue while pulling an encrypted image. This could be the cause of the entries trying to pull encrypted image multiple times in the agent log.

I tried to put the enc_key and key_id labels through Dockefile to create an encrypted image from occlum dev container and then launch the enclave-cc coco with that image as done with the image mentioned at ci-setup .  I still see the same error although I am able to pull this image manually using docker without any error.
I used the occlum/occlum:0.30.1-ubuntu20.04 to create occlum dev container and create a sample hello_world. I used the following Dockerfile to create the encrypted image.
oot@0b70e247146f:~/niteesh/occlum-instance# occlum run /bin/hello_world
Hello SGX-coco World

root@0b70e247146f:~/niteesh/occlum-instance# cat Dockerfile
FROM scratch
ADD image /
LABEL enc_key="LLLOhvkqFcGMzZrVzt6vPWlj/F/bgYMNe45vhQpdxAA="
LABEL key_id="kbs:///default/image-kek/11111d96-dccd-46a3-9244-93644d76745f"

I've lost track what your setup is. There is no need to "which i built using occlum dev container" since enclave-cc is giving the same result transparently. Anyway, /bin/hello_world is there so this image should be fine.

But, when I use its encrypted image docker.io/niteeshkd/occlum-test:enc2 with attestatation (i.e. "security_validate":  true

Note that security_validate is about signature checks and AFAIU, your policy is set to require sigstore signature for it in the registry. If the policy is set as @Xynnn007 suggested, you might see different results.
The other image does not have any encrypted layers:
$ skopeo inspect --raw docker://niteeshkd/test-image-occlum:enc | jq  '.layers[].mediaType'
"application/vnd.docker.image.rootfs.diff.tar.gzip"

@mythi In my setup, I was trying to build an image from occlum dev container and then encrypt it using skopeo & trustee keyprovider and then i was signing it using cosign. It was giving the problem while using encrypted or encrypted+signed image. I did not have any issue while using the image which you suggested.  Looking at this working image, i was modifying my dockerfile to embed enc_key and key_id to findout the cause of building image from occlum dev container.  That did not help.
Now, it is very strange that I resetup the occlum environment, rebuilt the app and recreated the image in occlum dev container. I don't know what happened this time that everything is working fine now. I am able to launch enclave-cc with the signed encrypted image built from occlum dev container.
Here is the log of enclave agent which looks different now.
$ sudo cat /run/containerd/agent-enclave/7b6c43cd35acec6332cb74ff4ccf86ea396731b7e5cc7a4c034b9dae1c33198f/stderr
[2024-03-15T03:23:45Z INFO  enclave_agent] ttRPC server started: "tcp://<IP_ADDRESS>:7788"
[2024-03-15T03:23:45Z INFO  enclave_agent::services::images] Pulling "docker.io/niteeshkd/test-occlum:enc"
[2024-03-15T03:23:45Z INFO  image_rs::resource::kbs] secure channel uses native-aa
[2024-03-15T03:23:46Z WARN  kbs_protocol::client::rcar_client] Authenticating with KBS failed. Perform a new RCAR handshake: ErrorInformation {
        error_type: "https://github.com/confidential-containers/kbs/errors/InvalidRequest",
        detail: "The request is invalid: parse Authorization header failed: invalid Header provided",
    }
[2024-03-15T03:23:46Z INFO  sigstore::cosign::client_builder] Rekor public key not provided. Rekor integration disabled
[2024-03-15T03:23:46Z INFO  sigstore::cosign::client_builder] No Fulcio cert has been provided. Fulcio integration disabled
[2024-03-15T03:23:47Z INFO  sigstore::cosign::signature_layers] Ignoring bundle, rekor public key not provided to verification client bundle="{\"SignedEntryTimestamp\":\"MEUCIB/yEmxE45+EwCoCKsX3ksbDSocM+a2wIyzP/wXjCR9sAiEAmAq+vnzuXWpJSbr1PJ2WKmEn+WWf/ZfAP0drBt2zQK4=\",\"Payload\":{\"body\":\"eyJhcGlWZXJzaW9uIjoiMC4wLjEiLCJraW5kIjoiaGFzaGVkcmVrb3JkIiwic3BlYyI6eyJkYXRhIjp7Imhhc2giOnsiYWxnb3JpdGhtIjoic2hhMjU2IiwidmFsdWUiOiI4MDBjN2UzYjNiYzc2MTg2ZDRjNWQ4ZjcxOWM3MTk2ZDVjNGUzZjIyMjJiZWY4ODljOTg1NGE5NTRkZTg1NjFkIn19LCJzaWduYXR1cmUiOnsiY29udGVudCI6Ik1FVUNJSE9WbmlieXhSeWlUVDRkZGorQU5WZ1g5WVAzNTN6STlEVjdhM2hkMFBLQkFpRUFuTVZJQnVVbzBwZExsYk9DRGlJS3JMcUJROG04a3Rja0g1VitTQVFRaSt3PSIsInB1YmxpY0tleSI6eyJjb250ZW50IjoiTFMwdExTMUNSVWRKVGlCUVZVSk1TVU1nUzBWWkxTMHRMUzBLVFVacmQwVjNXVWhMYjFwSmVtb3dRMEZSV1VsTGIxcEplbW93UkVGUlkwUlJaMEZGUmpKcE9GcGxNakZXTmtnd0t6aHZPRTE2Wnk5c1dtdHZZekkwWlFwWWJXNXVUWFF5ZDFBMU9YSkxNMWRGVTI5QlNtWTBhazFHZWpKRmNVVmpkRE1yTkdVMmIxTnZXalJTVGpWa09GcHFlbHBsVTJ4aFZUWjNQVDBLTFMwdExTMUZUa1FnVUZWQ1RFbERJRXRGV1MwdExTMHRDZz09In19fX0=\",\"integratedTime\":1710472940,\"logIndex\":78368684,\"logID\":\"c0d23d6ad406973f9559f3ba2d1ca01f84147d8ffc5b8445c224f98b9591801d\"}}"
[2024-03-15T03:23:47Z WARN  kbs_protocol::client::rcar_client] Authenticating with KBS failed. Perform a new RCAR handshake: ErrorInformation {
        error_type: "https://github.com/confidential-containers/kbs/errors/InvalidRequest",
        detail: "The request is invalid: parse Authorization header failed: invalid Header provided",
    }
[2024-03-15T03:24:17Z INFO  enclave_agent::services::images] Pull image "docker.io/niteeshkd/test-occlum:enc" successfully

$ kubectl describe pod enclave-cc-pod
...
Events:
  Type    Reason     Age   From               Message
  ----    ------     ----  ----               -------
  Normal  Scheduled  13m   default-scheduler  Successfully assigned default/enclave-cc-pod to b77r44u11-node
  Normal  Pulling    13m   kubelet            Pulling image "docker.io/niteeshkd/test-occlum:enc"
  Normal  Pulled     13m   kubelet            Successfully pulled image "docker.io/niteeshkd/test-occlum:enc" in 44.352s (44.352s including waiting)
  Normal  Created    13m   kubelet            Created container hello-world
  Normal  Started    13m   kubelet            Started container hello-world

$ kubectl logs enclave-cc-pod
Hello SGX coco World!
Hello SGX coco World!

@mythi @Xynnn007 Thank you so much for your helps! Now, we can close both the issues (i.e. this one and issue#301 )

@niteeshkd great that it works for you now! Not sure what was the glitch but with enclave-cc you should not have the need to do any occlum builds for your image. Perhaps the double-occlum setup was the reason...
Anyway, closing.

@mythi @Xynnn007 , Just to be clear, i did some more investigation using occlum dev container build environment and found the following.
If the program, as given below, exits immediately , there is no issue in creating enclave-cc with the unencrypted image containing that program. But, enclave-cc can not be created with the encrypted image containing that program.
#include <stdio.h>
int main() {
    printf("Hello World\n");
    return 0;
}

If the program, as given below, does not exit immediately, then enclave-cc can be created using both unencrypted and encrypted image containing that program.
#include <stdio.h>
#include <unistd.h>
int main() {
    while(1) {
        printf("Hello World\n");
        sleep(1);
    }
}


Export waypoint

As the title state, it will become handy if the waypoints are exported too

Waypoints are not part of the map, JourneyMap tools takes the map tiles and merges them into on image.
Waypoints are only renderable in game.


Controller Pointers Base Branch

Overview
This branch adds a basic line pointer example to the MRTK:
https://github.com/Railboy/MixedRealityToolkit-Unity/tree/Controller_Pointers_Base
Issues
This is a subset of the pointer examples we're working on in #1486. Some changes were necessary to make these classes function in the current dev branch. Those changes have been marked with a comment:
// This will be enabled when multi-pointer support is incorporated
If we open a PR we'll want to strip these out - they're just to facilitate discussion.
Minor issues that are addressed in #1486:

Cursor lags behind pointer's target point
Single cursor is swapped between multiple pointers
IPointerInput.OwnsInput can result in false positives

Files

Adds ControllerPointerBase.cs, FocusPointerInput.cs, InteractibleHighlight.cs and LinePointer.cs classes to HoloToolkit/UX/Scripts/Pointers
Adds ControllerPointerExamples scene to HoloToolkit-Examples/UX/Scenes.
Adds LinePointerBasic prefab to HoloToolkit-Examples/UX/Prefabs
Minor changes to several Line classes.

Questions
Do we feel this is worth merging? How could it be improved?

Closing issues older than 180 days. If this is still an issue, please reactivate with recent information.


⚠ ClamAV has degraded performance

In 1fa3a55, ClamAV (https://spamassassin.apache.org/) experienced degraded performance:

HTTP code: 200
Response time: 55 ms

Resolved: ClamAV performance has improved in d3b5fe3.


Use the WhichBrowser PHP API

I’ve added a dedicated PHP API for WhichBrowser and split the project into a separate parser and server.
This pull request changes the package which is used to ‘whichbrowser/parser’ and updates the provider to use the proper API.

Awesome!
It seems there is an error with a missing method. Does that method exist or is just a typo?
I could grab your PR as well tomorrow, if you dont find time for it.
https://travis-ci.org/ThaDafinser/UserAgentParser/jobs/91246109#L140

Forgot to merge it. Should be fixed now.

I merged it here: #17 ...i need to learn more from git sometime, how to add commit to a existing PR.
Anyway your commit contribution is still ok.
Thank you :+1:


Add default to JSON schema when const is True

Change Summary
Right now for the following Model:
from pydantic import BaseModel, Field

class MyModel(BaseModel):
    x: int = Field(default=0, const=True)

The JSON schema is:
{
  "title": "MyModel",
  "type": "object",
  "properties": {
    "x": {
      "title": "X",
      "const": 0,
      "type": "integer"
    }
  }
}

Which will include the default:
{
  "title": "MyModel",
  "type": "object",
  "properties": {
    "x": {
      "title": "X",
      "const": 0,
      "default": 0,
      "type": "integer"
    }
  }
}

I couldn't find the reason why it was introduced in #2094 but seems like the main purpose was something else.
Related issue number
Fixes https://github.com/samuelcolvin/pydantic/issues/4031
Checklist

[x] Unit tests for the changes exist
[x] Tests pass on CI and coverage remains at 100%
[ ] Documentation reflects the changes where applicable
[x] changes/<pull request or issue id>-<github username>.md file added describing change
(see changes/README.md for details)
[x] My PR is ready to review, please add a comment including the phrase "please review" to assign reviewers

please review

I couldn't find the reason why it was introduced in https://github.com/samuelcolvin/pydantic/pull/2094 but seems like the main purpose was something else.

The and not field.field_info.const was introduced originally in Implement const keyword in Schema and just reformatted in https://github.com/samuelcolvin/pydantic/pull/2094. IMO, seems the original implementation was wrong.

IMO the const keyword should be deprecated in favor of Literal. With Literal, is the behaviour the expected one?

@PrettyWood Not entirely sure, but they will produce different schemas which seem equivalent 🤷
with const it will include: "const": 10 and with Literal it will include "enum": [10]

@PrettyWood
Not sure if I understand correctly but this will not include a default either:
class Test(BaseModel):
    x: Literal[10]

{"title": "Test", "type": "object", "properties": {"x": {"title": "X", "enum": [10], "type": "integer"}}, "required": ["x"]}

But this will which I'm not sure if is correct:
class Test(BaseModel):
    x: Literal[10] = Field(default=10)

{"title": "Test", "type": "object", "properties": {"x": {"title": "X", "default": 10, "enum": [10], "type": "integer"}}}

And about the const deprecation, const=True will produce "const": 10 in schema but Literal[10] will produce "enum": [10] which should serve the same purpose but they are both possible according the the json schema, I could not find any references to the difference though.

IMO the const keyword should be deprecated in favor of Literal. With Literal, is the behaviour the expected one? edit: I don't say we should deprecate it now or that this PR should not be merged! :P

I think what @PrettyWood means is that Literal[10] (just one option in the literal), should result in "const": 10 in the schema? I think he just means we should get rid of the kwarg from Field (at least that's what I think he means :raised_eyebrow:)

thanks so much for this.


How to install Python dependencies

We should add a guide on how to install Python dependencies

@04anubhavv

@04anubhavv

i have a private repo with more features :D
I will make it public soon
and let you  know

i have a private repo with more features :D
I will make it public soon
and let you  know


how to generate new testing hash code

I don't know how to generate new hash code for testing.
Because I wan to do refresh with different code, there are only several testing codes within the project.

You can create a new personal hash on our platform, mobfox.com. That's where you'll eventually create your live hash as well.
Regards,


Bug: Attempting to continue conversation with Ollama model will fallback to default model

Describe the bug
When attempting to continue the conversation with an Ollama-based model, it will automatically fall back to the default model instead of continuing the conversation with Ollama.
Setup
Please complete the following information along with version numbers, if applicable.

OS: macOS 14.4.1
Shell: fish
Terminal Emulator: WezTerm
Terminal Multiplexer: WezTerm

To Reproduce
Steps to reproduce the behavior:

Type mods --setings
Insert:

apis:
  openai:
    base-url: https://api.openai.com/v1
    models:
      gpt-4:
        aliases: ["4"]
        max-input-chars: 24500
        fallback: gpt-3.5-turbo
  ollama:
    base-url: http://localhost:11434/v1
    api-key-env: NA
    models:
      "llama3:8b":
        aliases: ["llama3"]
        max-input-chars: 4000
default-model: gpt-4

install ollama
run ollama pull llama3:8b
type mods -M
choose llama3:8b
type whatever
run mods -C or mods -<SHA>
see that it is falling back to default GPT-4k
See error

hmmm, yes, currently it'll continue the conversation using the default-model always.
good find, thanks!


Is there a way to directly install it.

I read https://github.com/thekordy/ticketit/wiki/How-to-install-Ticketit and followed documentation but i am not able to install it as i bit new in laravel stuff and having lots of trouble in installing ticketit
Can you provide copy of working dir or web installer so we can just clone it and composer update,, so it canbe ready in 10 sec ?

I have not tried that before, let me try it locally and see if that could work.

@thekordy Thanx and waiting for the package .... if you can provide it soon as possible that would be fine, thank you and kudo for the project

A mi tambien me serviria tener un package con esta aplicacion. Gracias

I have started working on one 'pre-configured' app, I'll upload it probably tomorrow

balping that would be fantastic!

I created a repo which makes the installation a lot easier. I could install ticketit under a minute (well, the database had been created before and composer packages were in cache, but still)
So check it out: https://github.com/balping/ticketit-app
I've also updated the readme of ticketit to reference this installer

Great!!!
balping you're the best!!
It is usable 100%
thank you very much.

So check it out: https://github.com/balping/ticketit-app

Looks perfect, very well done @balping :+1:

Am using windows. The installation via the cmd is a not working for my case. Kindly suggest for me a way out


Gotty multi users, Docker and Helm

Hi all, and thanks to the author for this wonderful project,
I wanted to used Gotty for a personal project with a basic authentication for multiple users. I found another project were this functionnality was added : https://github.com/KubeOperator/webkubectl. In this project the Gotty original code was updated to support a credential file for basic authentication for multiple users. As the project also changes many others things in the Gotty original project, i have moved only the changes concerning the multiple users authentication in another repository. I also added a DockerFile and a Helm Chart to deploy it in a containerized environment. You can see those changes in this repository : https://github.com/stevelaclasse/gotty-multi-users-Docker.
I hope it may help someone.
(This was originaly posted in the original GitHub gotty repository : https://github.com/yudai/gotty/issues/342)

I Personnaly used gotty to customize a web ssh application with basic web authentification, as the private key is set in the helm chart and deployed during the chart installation.


Migrating plugin to V3❓

Question
I'm trying to migrate vision-camera-ocr to vision camera v3 so I decided to do a fork of the original package, because it seems unmaintained.
This is the fork: https://github.com/francesco-clementi-92/vision-camera-ocr
After struggling really a lot I managed to make it work for android, but the first time that I try yarn run android the camera is blank.
If I disable by commenting the frameProcessor prop, then enable it again, it will work correctly.
Any idea on what could be the cause?
To replicate, go to the example folder, run
When the app starts on your device you will see a black screen. Comment the frameProcessor prop:
<Camera
        style={[StyleSheet.absoluteFill]}
        //frameProcessor={frameProcessor}
        device={device}
        isActive={true}
        pixelFormat="yuv"
        onLayout={(event: LayoutChangeEvent) => {
          setPixelRatio(
            event.nativeEvent.layout.width /
              PixelRatio.getPixelSizeForLayoutSize(
                event.nativeEvent.layout.width,
              ),
          );
        }}
        //orientation={'portrait'}
      />

save and then uncomment it again.
It will work
What I tried
No response
VisionCamera Version
3.6.4
Additional information

[ ] I am using Expo
[X] I have read the Troubleshooting Guide
[X] I agree to follow this project's Code of Conduct
[X] I searched for similar questions in the issues page as well as in the discussions page and found none.

Hey - thanks for the effort in migrating it to V3, but what you're describing is a bug report, not a question - so please  create a new issue with the bug report template filled out (and logs included). Thanks!

I actually think that the problem is with my migration of the package, but I’ll open a new issue

Hi @francesco-clementi-92, I saw that you managed to make your plugin work with V3, right?
Why the author haven't mentioned you yet in the documentation? vision-camera-ocr does not work with V3 and is not maintained anymore.

You are right, I need to publish the package to the author documentation, but I do not have time to mantain it.
I’ll publish it and I’ll try to find someone to support the maintaining effort.
In the meantime feel free to test it

Thanks for your contribution @francesco-clementi-92 . The plugin does not work with the latest version of vision-camera. Therefore, I need to fallback to version 3.6.
Do you know any other plugin that can recognize texts on V3?


B-20334 I-13046 Remove extra spaces from LOA string MAIN

Agility ticket

Warnings

:warning:
This PR does not include changes to unit tests, even though it affects app code.

  Generated by :no_entry_sign: dangerJS against 4ad48dcf56fd57f7f7cf680e6ea561b7c3de62c8


Sync master branch with experimental

This PR adds the functionality from the experimental branch to the master branch:

New-MAASImage option with  MAAS 2.0 compatibility
Unit tests with Pester
Set 'Network-Level' authentication' as required
Enable swap in sysprep specialize
Added option of purging updates for faster winupdates clean
Added shrink retry with increased size and better logging

nit: a typo in comppression

We need to put a check here:
foreach ($i in $values.GetEnumerator()) {
Set-IniFileValue -Path $configIniPath -Section "DEFAULT" -Key $i.Key -Value $i.Value
}
for empty values of $i.value -- otherwise we will get an error
foreach ($i in $values.GetEnumerator()) {
if ($i.Value) {
Set-IniFileValue -Path $configIniPath -Section "DEFAULT" -Key $i.Key -Value $i.Value
}
}

Hi，How can I use this to build baremetal windows image？


Improve an explanatory comment in Dictionary

It took me a little while to figure out why we were fatalError()ing in such a convoluted way in Dictionary.init(uniqueKeysWithValues:); the next person to look at this code won’t waste that time.

@swift-ci please smoke test

@swift-ci please smoke test linux platform

@swift-ci please smoke test linux platform


Cannot configure onDelete and onUpdate for implicit many-to-many relations

Bug description
Prisma seems to set ON DELETE CASCADE and ON UPDATE CASCADE for implicit many-to-many relations, regardless of onDelete and onUpdate.
How to reproduce
Run prisma migrate dev with schema shown later.
It creates following migration.sql:
-- CreateTable
CREATE TABLE "Track" (
    "id" TEXT NOT NULL PRIMARY KEY,
    "title" TEXT NOT NULL
);

-- CreateTable
CREATE TABLE "Playlist" (
    "id" TEXT NOT NULL PRIMARY KEY,
    "name" TEXT NOT NULL
);

-- CreateTable
CREATE TABLE "_PlaylistToTrack" (
    "A" TEXT NOT NULL,
    "B" TEXT NOT NULL,
    FOREIGN KEY ("A") REFERENCES "Playlist" ("id") ON DELETE CASCADE ON UPDATE CASCADE,
    FOREIGN KEY ("B") REFERENCES "Track" ("id") ON DELETE CASCADE ON UPDATE CASCADE
);

-- CreateIndex
CREATE UNIQUE INDEX "_PlaylistToTrack_AB_unique" ON "_PlaylistToTrack"("A", "B");

-- CreateIndex
CREATE INDEX "_PlaylistToTrack_B_index" ON "_PlaylistToTrack"("B");

Execution log of prisma migrate dev:
  prisma:loadEnv project root found at D:\projects\prisma-starter\package.json +0ms
  prisma:tryLoadEnv Environment variables loaded from D:\projects\prisma-starter\.env +0ms
  prisma:tryLoadEnv Environment variables not found at undefined +2ms
Environment variables loaded from ..\.env
  prisma:engines binaries to download libquery-engine, migration-engine, introspection-engine, prisma-fmt +0ms
Prisma schema loaded from schema.prisma
  prisma:getConfig Using CLI Query Engine (Node-API Library) at<EMAIL_ADDRESS>+0ms
Datasource "db": SQLite database "dev.db" at "file:./dev.db"

  prisma:getDMMF Using CLI Query Engine (Node-API) at<EMAIL_ADDRESS>+0ms
  prisma:getConfig Using CLI Query Engine (Node-API Library) at<EMAIL_ADDRESS>+19ms
  prisma:getConfig Using CLI Query Engine (Node-API Library) at<EMAIL_ADDRESS>+3ms
SQLite database dev.db created at file:./dev.db

  prisma:migrateEngine:rpc starting migration engine with binary<EMAIL_ADDRESS>+0ms
  prisma:migrateEngine:rpc SENDING RPC CALL {"id":1,"jsonrpc":"2.0","method":"devDiagnostic","params":{"migrationsDirectoryPath":"D:\\projects\\prisma-starter\\prisma\\migrations"}} +4ms
  prisma:migrateEngine:stderr {"timestamp":"2021-12-24T18:07:33.1040321Z","level":"INFO","fields":{"message":"Starting migration engine RPC server","git_hash":"8746e055198f517658c08a0c426c7eec87f5a85f"},"target":"migration_engine"} +0ms
  prisma:migrateEngine:stderr {"timestamp":"2021-12-24T18:07:33.1055052Z","level":"INFO","fields":{"message":"Starting a sqlite connection."},"target":"quaint::single"} +1ms
  prisma:migrate:dev {
  prisma:migrate:dev   devDiagnostic: '{\n  "action": {\n    "tag": "createMigration"\n  }\n}'
  prisma:migrate:dev } +0ms
  prisma:migrateEngine:rpc SENDING RPC CALL {"id":2,"jsonrpc":"2.0","method":"applyMigrations","params":{"migrationsDirectoryPath":"D:\\projects\\prisma-starter\\prisma\\migrations"}} +25ms
  prisma:migrateEngine:stderr {"timestamp":"2021-12-24T18:07:33.1200232Z","level":"INFO","fields":{"message":"Analysis run in 6ms","analysis_duration_ms":6},"target":"migration_core::commands::apply_migrations","span":{"name":"ApplyMigrations"},"spans":[{"name":"ApplyMigrations"}]} +14ms
  prisma:migrateEngine:stderr {"timestamp":"2021-12-24T18:07:33.1200675Z","level":"INFO","fields":{"message":"All the migrations executed in 0ms","apply_migrations_duration_ms":0},"target":"migration_core::commands::apply_migrations","span":{"name":"ApplyMigrations"},"spans":[{"name":"ApplyMigrations"}]} +1ms
  prisma:migrateEngine:rpc SENDING RPC CALL {"id":3,"jsonrpc":"2.0","method":"evaluateDataLoss","params":{"migrationsDirectoryPath":"D:\\projects\\prisma-starter\\prisma\\migrations","prismaSchema":"generator client {\n  provider        = \"prisma-client-js\"\n  previewFeatures = [\"interactiveTransactions\"]\n}\n\ndatasource db {\n  provider = \"sqlite\"\n  url      = env(\"DATABASE_URL\")\n}\n\nmodel Track {\n  id
   String     @id\n  title     String\n  playlists Playlist[] @relation(onDelete: Restrict, onUpdate: Restrict)\n}\n\nmodel Playlist {\n  id     String  @id\n  name   String\n  tracks Track[] @relation(onDelete: Restrict, onUpdate: Restrict)\n}\n"}} +10ms
  prisma:migrate:dev {
  prisma:migrate:dev   evaluateDataLossResult: { migrationSteps: 5, warnings: [], unexecutableSteps: [] }
  prisma:migrate:dev } +16ms
√ Enter a name for the new migration: ... init
  prisma:migrateEngine:rpc SENDING RPC CALL {"id":4,"jsonrpc":"2.0","method":"createMigration","params":{"migrationsDirectoryPath":"D:\\projects\\prisma-starter\\prisma\\migrations","migrationName":"init","draft":false,"prismaSchema":"generator client {\n  provider        = \"prisma-client-js\"\n  previewFeatures = [\"interactiveTransactions\"]\n}\n\ndatasource db {\n  provider = \"sqlite\"\n  url      = env(\"DATABASE_URL\")\n}\n\nmodel Track {\n  id        String     @id\n  title     String\n  playlists Playlist[] @relation(onDelete: Restrict, onUpdate: Restrict)\n}\n\nmodel Playlist {\n  id     String  @id\n  name   String\n  tracks Track[] @relation(onDelete: Restrict, onUpdate: Restrict)\n}\n"}} +2s
  prisma:migrate:dev {
  prisma:migrate:dev   createMigrationResult: { generatedMigrationName: '20211224180735_init' }
  prisma:migrate:dev } +2s
  prisma:migrateEngine:rpc SENDING RPC CALL {"id":5,"jsonrpc":"2.0","method":"applyMigrations","params":{"migrationsDirectoryPath":"D:\\projects\\prisma-starter\\prisma\\migrations"}} +7ms
  prisma:migrateEngine:stderr {"timestamp":"2021-12-24T18:07:35.440042Z","level":"INFO","fields":{"message":"Analysis run in 1ms","analysis_duration_ms":1},"target":"migration_core::commands::apply_migrations","span":{"name":"ApplyMigrations"},"spans":[{"name":"ApplyMigrations"}]} +2s
  prisma:migrateEngine:stderr {"timestamp":"2021-12-24T18:07:35.4402261Z","level":"INFO","fields":{"message":"Applying `20211224180735_init`","script":"-- CreateTable\nCREATE TABLE \"Track\" (\n    \"id\" TEXT NOT
NULL PRIMARY KEY,\n    \"title\" TEXT NOT NULL\n);\n\n-- CreateTable\nCREATE TABLE \"Playlist\" (\n    \"id\" TEXT NOT NULL PRIMARY KEY,\n    \"name\" TEXT NOT NULL\n);\n\n-- CreateTable\nCREATE TABLE \"_PlaylistToTrack\" (\n    \"A\" TEXT NOT NULL,\n    \"B\" TEXT NOT NULL,\n    FOREIGN KEY (\"A\") REFERENCES \"Playlist\" (\"id\") ON DELETE CASCADE ON UPDATE CASCADE,\n    FOREIGN KEY (\"B\") REFERENCES \"Track\" (\"id\") ON DELETE CASCADE ON UPDATE CASCADE\n);\n\n-- CreateIndex\nCREATE UNIQUE INDEX \"_PlaylistToTrack_AB_unique\" ON \"_PlaylistToTrack\"(\"A\", \"B\");\n\n-- CreateIndex\nCREATE INDEX \"_PlaylistToTrack_B_index\" ON \"_PlaylistToTrack\"(\"B\");\n"},"target":"migration_core::commands::apply_migrations","span":{"migration_name":"20211224180735_init","name":"Applying migration"},"spans":[{"name":"ApplyMigrations"},{"migration_name":"20211224180735_init","name":"Applying migration"}]} +1ms
  prisma:migrateEngine:stderr {"timestamp":"2021-12-24T18:07:35.4472245Z","level":"INFO","fields":{"message":"Applying migration `20211224180735_init`","migrate_action":"log"},"target":"sql_migration_connector::sql_database_step_applier","span":{"migration_name":"20211224180735_init","name":"apply_script"},"spans":[{"name":"ApplyMigrations"},{"migration_name":"20211224180735_init","name":"Applying migration"},{"migration_name":"20211224180735_init","name":"apply_script"}]} +7ms
Applying migration `20211224180735_init`
  prisma:migrateEngine:stderr {"timestamp":"2021-12-24T18:07:35.4733953Z","level":"INFO","fields":{"message":"Migration executed in 33ms","migration_duration_ms":33},"target":"migration_core::commands::apply_migrations","span":{"migration_name":"20211224180735_init","name":"Applying migration"},"spans":[{"name":"ApplyMigrations"},{"migration_name":"20211224180735_init","name":"Applying migration"}]} +25ms
  prisma:migrateEngine:stderr {"timestamp":"2021-12-24T18:07:35.4734654Z","level":"INFO","fields":{"message":"All the migrations executed in 33ms","apply_migrations_duration_ms":33},"target":"migration_core::commands::apply_migrations","span":{"name":"ApplyMigrations"},"spans":[{"name":"ApplyMigrations"}]} +1ms

The following migration(s) have been created and applied from new schema changes:

migrations/
  └─<PHONE_NUMBER>0735_init/
    └─ migration.sql

Your database is now in sync with your schema.

Running generate... (Use --skip-generate to skip the generators)
  prisma:getConfig Using CLI Query Engine (Node-API Library) at: D:\projects\prisma-starter\node_modules\prisma\query_engine-windows.dll.node +3s
  prisma:getDMMF Using CLI Query Engine (Node-API) at: D:\projects\prisma-starter\node_modules\prisma\query_engine-windows.dll.node +3s
  prisma:generator prismaCLIDir D:\projects\prisma-starter\node_modules\prisma +0ms
  prisma:generator prismaClientDir D:\projects\prisma-starter\node_modules\@prisma\client +1ms
  prisma:generator baseDir D:\projects\prisma-starter\prisma +0ms
  prisma:generator typescriptPath D:\projects\prisma-starter\node_modules\typescript +5ms
  prisma:GeneratorProcess 2021-12-24T18:07:36.022Z prisma:client:generator requiredEngine: libqueryEngine +0ms
  prisma:getGenerators neededVersions {
  "8746e055198f517658c08a0c426c7eec87f5a85f": {
    "engines": [
      "libqueryEngine"
    ],
    "binaryTargets": []
  }
} +0ms
  prisma:getGenerators {
  prisma:getGenerators   generatorBinaryPaths: {
  prisma:getGenerators     libqueryEngine: {
  prisma:getGenerators       windows: 'D:\\projects\\prisma-starter\\node_modules\\prisma\\query_engine-windows.dll.node'
  prisma:getGenerators     }
  prisma:getGenerators   }
Running generate... - Prisma Client
✔ Generated Prisma Client (3.7.0 | library) to .\..\node_modules\@prisma\client in 328ms

  prisma:migrate:seed {
  prisma:migrate:seed   prismaConfig: {
  prisma:migrate:seed     data: undefined,
  prisma:migrate:seed     packagePath: 'D:\\projects\\prisma-starter\\package.json'
  prisma:migrate:seed   }
  prisma:migrate:seed } +0ms
  prisma:migrate:seed {
  prisma:migrate:seed   detected: { seedPath: 'seed.', numberOfSeedFiles: 0, js: '', ts: '', sh: '' }
  prisma:migrate:seed } +4ms

  prisma:getConfig Using CLI Query Engine (Node-API Library) at<EMAIL_ADDRESS>+896ms

Expected behavior
I think ON DELETE(UPDATE) CASCADE should be ON DELETE(UPDATE) RESTRICT here.
Prisma information
prisma.schema:
generator client {
  provider = "prisma-client-js"
}

datasource db {
  provider = "sqlite"
  url      = "file:./dev.db"
}

model Track {
  id        String     @id
  title     String
  playlists Playlist[] @relation(onDelete: Restrict, onUpdate: Restrict)
}

model Playlist {
  id     String  @id
  name   String
  tracks Track[] @relation(onDelete: Restrict, onUpdate: Restrict)
}

Environment & setup

OS: Windows 10 x64
Database: SQLite
Node.js version: v16.10.0

Prisma Version
  prisma:loadEnv project root found at D:\projects\prisma-starter\package.json +0ms
  prisma:tryLoadEnv Environment variables loaded from D:\Projects\projects\prisma-starter\.env +0ms
  prisma:tryLoadEnv Environment variables not found at undefined +1ms
Environment variables loaded from ..\.env
  prisma:engines binaries to download libquery-engine, migration-engine, introspection-engine, prisma-fmt +0ms
  prisma:getConfig Using CLI Query Engine (Node-API Library) at<EMAIL_ADDRESS>+0ms
prisma                  : 3.7.0
@prisma/client          : 3.7.0
Current platform        : windows
Query Engine (Node-API) : libquery-engine 8746e055198f517658c08a0c426c7eec87f5a85f (at<EMAIL_ADDRESS>Migration Engine        : migration-engine-cli 8746e055198f517658c08a0c426c7eec87f5a85f (at<EMAIL_ADDRESS>Introspection Engine    : introspection-core 8746e055198f517658c08a0c426c7eec87f5a85f (at<EMAIL_ADDRESS>Format Binary           : prisma-fmt 8746e055198f517658c08a0c426c7eec87f5a85f (at<EMAIL_ADDRESS>Default Engines Hash    : 8746e055198f517658c08a0c426c7eec87f5a85f
Studio                  : 0.445.0
  prisma:getConfig Using CLI Query Engine (Node-API Library) at<EMAIL_ADDRESS>+6ms

This is actually a validation problem, as setting onDelete and onUpdate on implicit m:n relations is indeed not supported - but the schema is shown as valid. Instead it should fail to validate and thus make clear that it is currently not possible to influence this.

Thanks. But cascade deletion is a problem for us, are there any plans to support this feature?

That would be a new feature request then. Currently there is no way to customize this, and you would need to model the relation explicitly at the cost of having a less convenient API unfortunately. (Do you maybe want to open the feature request issue and provide some context? That would be neat. Thanks.)

This should have been changed with 3.8.0 - can you please confirm?

Confirmed. Thanks!
(BTW I think implicit many-to-many relations is more explicit than just saying many-to-many relations)

Thanks for the feedback.
That is a very good point.


[SERV-584] Configure Solr index for data retrieval

I essentially ported the old schema and config to the new Solr configuration API syntax. I have spun up a front-end locally and confirmed that data retrieval works, but search does not.

So the build is failing due to lines in one of the shell scripts being longer than 120 chars. Should we make an exception for this file?

So the build is failing due to lines in one of the shell scripts being longer than 120 chars. Should we make an exception for this file?

I actually meant to ask you about that shell script but looking at this PR now I think I might know the answer. Was curious why you didn't write the configuration in Java since there is a Java API and it would fit in better with our tests. I'm guessing now it's because you were doing the setup through this extra container and didn't want to install Java on it and going through a build, etc. when you could just use the shell script?

I wasn't aware there was a Java SDK; do you have a link to it?

I haven't done this myself since I last used Solr when it preferred config files, but I guess I just assumed that, if they're providing an HTTP API and deprecating editing the files, they've also incorporated it into their official SDKs, too(!) -- not to say one couldn't do the same thing you're doing through curl with a plain Java HTTP client.
Glancing at the Javadocs (i.e., not looking deeply, so I could be mistaken), is this not what we need for the schema? https://solr.apache.org/docs/9_0_0/solrj/org/apache/solr/client/solrj/request/schema/package-summary.html and https://solr.apache.org/docs/9_0_0/solrj/org/apache/solr/client/solrj/request/ConfigSetAdminRequest.html for the configsets?

Turns out I was mistaken about the Schema and Config APIs being the preferred way to configure Solr; I've changed it back to the config file setup.
Search still isn't working, so I have created SERV-595 for fixing that.


Late to the party

So yeah :smile:, anyway, I write this here in case it is something you find interesting.
tl;dr proposal for a non-evented approach for undertaker, maybe not using what I've done but something better.
I have been working for a while now around the same idea of composing async functions using async-done and have come up with a different approach for all of this with no events and one method for series and/or parallel. This is how it looks like:
var tornado = require('tornado').create(); // <- the "registry"

tornado.set(':handle(\\d+)', function(next){
 console.log(this.params.handle);
  setTimeout(next, Math.random()*10);
});

function handle(next){
  setTimeout(next, Math.random()*10);
}

var series = tornado.stack('1 2', handle, {wait: true}); // => function
var parallel = tornado.stack('3 4', handle); // => function
series(1, 2); parallel(1, 2);
// passing arguments to each handle works from here or with next(null, 1, 2);

The same logic applies for nesting one "stack" with another as you do with bach. As you see I have added path to regex to the mix (because why not) and string arguments don't have to necessarily be separated by a comma. A space is just fine.

Quite late :wink: This seems like a pretty cool use of async-done but it doesn't map nicely to gulp. undertaker doesn't make async-done evented, it just adds task timing events to the execution of the functions, which is quite hard to do without controlling the entire stack.  Trust me, I first tried to implement bach on top of async and it was a nightmare, which led me to write now-and-later that allows extension points on the composed function.

Haha, thanks. I wanted to write anyway. The idea of a simple way to do async composition is just so pleasant, not only for gulp but in general. The way bach api looks like and composes is just, at least for me, what it should be to compose async functions.
Yean, control over the arguments that will construct the stack is really important otherwise all is a nightmare. Nesting, and the timing thing (or any other thing like error handling that has to be done between start and end) was the hardest to figure out. For that using async-done for completion of everything but callbacks was the solution. Provide a callback from outside and use it to glue everything. I'll write some pseudocode
function compose(

function compose(stack){
  var args = arguments;
}

I've end up writing real code. Skipped the normal checks like this instanceof and requires. All that would have been required is util.moduleName.
var store = {}; // lets say here we store things to map a string to a function

function Stack(){} // so we can identify composed functions

Stack.prototype.onHandle = function(next){
  // measure times or other things
}

Stack.prototype.onHandleError = function(err){
  if(err instanceof Error){ throw err; }
}

function compose(stack, site){
  var stackArguments, end, result;

  if(stack instanceof Stack){ tick(); }
  else {
     stackArguments = arguments;
     tick.stack = new Stack();
     return tick;
  }

  function next(err){
     stack.onHandleError(err, next);
     if(end || next.end){ return result; }
     end = true;
     stack.onHandle.apply(stack, args);
     if(site.next){ compose(stack, site); }
     return result;
  }

  function tick(err){
     if(stackArguments){
       stack = new Stack();
       next.wait = stack.wait;
       stack.onHandleError(err, next);
       var host = arg instanceof Stack && arg
       return compose(stack, {
        args: util.slice(stackArguments, host ? -1 : 0),
        index: -1,
        host: host
       });
     }

     var handle = site.next = site.args[++site.index];
     var type = typeof handle;

     if(type === 'string'){
        handle = store[site.next];
     }

     if(type !== 'function'){
        throw new TypeError('site should be string or function');
     } else if(handle.stack instanceof Stack){
        site.args[0] = stack;
     } else {
        site.args[0] = next;
     }

     var args = util.slice(site.args); // so we don't lose what was done before
     util.asyncDone(function(){
        stack.onHandle.apply(stack, args);
        result = handle.apply(stack, args);
        if(next.wait){ return result; }
        if(site.next){ compose(stack, site); }
        return result;
     }, next);
  }
}

Ok


Getting error: File C:\Program Files\WindowsPowerShell\Modules\MicrosoftTeams\5.5.0\MicrosoftTeams.psm1 cannot be loaded because running scripts is disabled on this system.

Prerequisites

[X] Write a descriptive title.
[X] Make sure you are able to repro it on the latest released version
[X] Search the existing issues.
[X] Refer to the FAQ.
[X] Refer to Differences between Windows PowerShell 5.1 and PowerShell.

Steps to reproduce
I am trying to run PowerShell script from ASP.NET CORE C# WebAPI. Please see the environment details below:
Environment: Windows 10 Enterprise
.NET SDKs installed:
  3.1.403 [C:\Program Files\dotnet\sdk]
  7.0.200 [C:\Program Files\dotnet\sdk]
  7.0.201 [C:\Program Files\dotnet\sdk]
  7.0.306 [C:\Program Files\dotnet\sdk]
  7.0.400 [C:\Program Files\dotnet\sdk]
  8.0.100-preview.3.23178.7 [C:\Program Files\dotnet\sdk]
  8.0.101 [C:\Program Files\dotnet\sdk]

The API runs on .NET 7: here is .csproj file
<Project Sdk="Microsoft.NET.Sdk.Web">

  <PropertyGroup>
    <TargetFramework>net7.0</TargetFramework>
    <Nullable>enable</Nullable>
    <ImplicitUsings>enable</ImplicitUsings>
  </PropertyGroup>
  <ItemGroup>
    <PackageReference Include="Microsoft.PowerShell.SDK" Version="7.3.9" />
  </ItemGroup>

The API Code:
using System.Diagnostics;
using System.Management.Automation;
using System.Management.Automation.Runspaces;

public static ScriptResult Run2(string filePath, Dictionary<string,string> parameters)
{
    string myScript = File.ReadAllText(filePath);

    ScriptResult scriptResult = new ScriptResult();

    using (System.Management.Automation.PowerShell ps = System.Management.Automation.PowerShell.Create())
    {

        ps.AddScript(myScript);
        foreach (var kvp in parameters)
        {
            ps.AddParameter(kvp.Key, kvp.Value);
        }

        var result = ps.Invoke();
        if (ps.HadErrors)
        {
            string errorMessage = "";
            foreach (var error in ps.Streams.Error)
            {
                errorMessage += error.ToString() + "\n"; <-- This is where I am getting the error message
            }
            throw new Exception(errorMessage);
        }
        foreach (var PSObject in result)
        {
            var x = PSObject.ToString();
        }
    }

    return scriptResult;

}

Output of Get-ExecutionPolicy -List
        Scope ExecutionPolicy
        ----- ---------------
MachinePolicy       Undefined
   UserPolicy       Undefined
      Process       Undefined
  CurrentUser    Unrestricted
 LocalMachine          Bypass

Note: The script contains following line:
Import-Module MicrosoftTeams

##script to get token##

Connect-MicrosoftTeams -AccessTokens @("$graphToken", "$teamsToken") | Out-Null

$getUserSettings = Get-CSOnlineUser -Identity $UserEmail -ErrorAction 'stop'

$output = @{
  UserConfig = $getUserSettings
}

$output | ConvertTo-JSON

Write-Output $output

Expected behavior
The API should return the output from the PowerShell script.

Actual behavior
Getting error:

File C:\Program Files\WindowsPowerShell\Modules\MicrosoftTeams\5.5.0\MicrosoftTeams.psm1 cannot be loaded because running scripts is disabled on this system. For more information, see about_Execution_Policies at https://go.microsoft.com/fwlink/?LinkID=135170.

### Error details

_No response_

### Environment data

```powershell
Name                           Value
----                           -----
PSVersion                      5.1.19041.4046
PSEdition                      Desktop
PSCompatibleVersions           {1.0, 2.0, 3.0, 4.0...}
BuildVersion                   10.0.19041.4046
CLRVersion                     4.0.30319.42000
WSManStackVersion              3.0
PSRemotingProtocolVersion      2.3
SerializationVersion           <IP_ADDRESS>

### Visuals

_No response_

As explained in this answer to your equivalent Stack Overflow question in detail, you need to override the ambient execution policy on a per-process basis, as part of your PowerShell SDK calls, to ensure that script execution is permitted from your project. This is shown in the following example:
// Create an initial default session state.
var iss = InitialSessionState.CreateDefault2();

// Set its script-file execution policy (for the current session (process) only).
// 'Bypass' uncondtionally allows script execution.
iss.ExecutionPolicy = Microsoft.PowerShell.ExecutionPolicy.Bypass;

// Create a PowerShell instance with a runspace based on the
// initial session state and run a sample script to show
// that the process-level Bypass policy took effect.
using (PowerShell ps = PowerShell.Create(iss))
{
  Console.WriteLine(
    ps.AddScript(@"Get-ExecutionPolicy -List | Out-String").Invoke()[0]
  );
}


Fix PLL enable.

This change fixes a bug wherein the PLL is never ready since the code to enable the PLL has some problematic writes that turn off the HSE or HSI osc input.
The PLL enable code included self.cr.write where we needed self.cr.modify to prevent the other register bits from resetting to default. The svd2rust register write resets everything. Modify changes bits without touching others.

Good catch, thanks for the fix!
In the interest of formatting and consistency, I have one request:
Please use:
use crate::{
    pac::CRS,
    syscfg::SYSCFG,
};

Instead of:
 use crate::{pac::CRS, syscfg::SYSCFG};

No problem. I fixed the formatting. Rustfmt was auto-formatting that away

Thanks!


chore: update docker hub image push

This light PR aims at moving docker image push from GitHub releases to actual merges

Hello, sorry for the late review and thanks a lot for the modification!


[feat]Redesign Hero section

Would you like to have a new feature? Please describe.
I am looking  some dev who can redesign the Hero section  completely a/c to the design provided .
The design is in design folder present inside the root.
Write code for navbar in Component/v1.0.0/hero jsx
Note: Please visit to V1.0.0 branch and make that changes into that branch only and push changes into v1.0 0 branch only not in main branch.
All the communication regarding the designing part will done  in Discord only.
How would this feature be beneficial for the project
No response
Additional context
Deadline: Within 5 days of issue assigned.

@Vikash-8090-Yadav I can do this after completing Navbar 🤔

@Vikash-8090-Yadav I can do this after completing Navbar 🤔

Yah,sure.

@Vikash-8090-Yadav I want to work on this issue. Since I have created PR for one feature and you said I can work on new feature, so please assign this to me!
Thanks..

Thanks

@Vikash-8090-Yadav Just want to let you know that now I am working on this issue. Actually, due to exams I didn't get time, sorry for that, Will get a PR soon for this!

@Vikash-8090-Yadav I have created a PR for this today.
PR No - #178


Include Multus CNI logs in EKS Logs Collector script

Description of changes:
As of today, the Multus CNI is supported by EKS. The EKS Logs Collector script does not currently include logs for this component. Since CNI troubleshooting is a key use case for this script, we should ensure Multus logs are included here.
I've added a new function to collect the Multus CNI Pod logs. Let me know if you have any feedback.
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

Hi cgchinmay@
The test for the PR is as follows:

Connect to a Worker Node via SSH.
Download the script via the normal steps:

curl -O https://raw.githubusercontent.com/awslabs/amazon-eks-ami/master/log-collector-script/linux/eks-log-collector.sh
sudo bash eks-log-collector.sh

Observe the output includes "Trying to collect Multus logs..."
Extract the log bundle, and verify the var_log dir contains the kube-system_kube-multus-ds log directory. This will contain the Multus logs (if you have Multus installed).

Thanks, Will validate it and then close the PR

Hi @cgchinmay let me know if there's any other information you need from me to help out with this.


Update Aerie version to 2.11.0

Test mission model (banana nation) provided with Aerie CLI is 2.11.0, tests are failing without this update.

Good catch; I remember feeling like I was missing something when I did that upgrade...
To fix the integration tests, can you add numpy<2.0.0 in the pyproject.toml while you're at it?

Set numpy to ^1.19.5, which is the latest version compatible with Python 3.6 and will also enforce <2.0.0.


Permute the pass pipeline to coalesce before setting up the matmul

Required for #2834
Two reasons to do this - one, it properly tags the layouts with their memory order very early in the TTGIR pipeline. And two, it moves our TTGIR pipeline closer to upstream. I am splitting the change to isolate any regressions or undesired behavior caused by this change vs changing the DPAS layouts in #2834.
cc #2354

Benchmark run: https://benchmarks.glados.intel.com/d/1pXX4hUSz/microbenchmarks?orgId=1&var-tag=ci|ci-adv|ci-dflt|movecoalesce&var-bench=All&var-device=Intel(R) Data Center GPU Max 1550&var-compiler=triton&var-compiler=xetla&var-compiler=onednn&var-backend=All&var-baseline_backend=xetla-ci-XPU 1550&var-target_backend=triton-ci-XPU 1550
Results appear to be in line with main, all deviations in the plots are within a min/max run from the last few days. This is ready for review.

I wonder whether FlashAttention (using the default codegen path + dev IGC) is ok. @alexbaden ?

Is that covered by the attn plot in the microbenchmarks link I posted above?

Is that covered by the attn plot in the microbenchmarks link I posted above?

No, need to run with igc-18251 runner.

Flash attention looks ok (as do the rest of the devigc benchmarks): https://benchmarks.glados.intel.com/d/1pXX4hUSz/microbenchmarks?orgId=1&var-tag=ci|ci-adv|ci-dflt|movecoalesce|movecoalescedevigc|igc-18251&var-bench=All&var-device=Intel(R) Data Center GPU Max 1550&var-compiler=triton&var-compiler=xetla&var-compiler=onednn&var-backend=All&var-baseline_backend=xetla-ci-XPU 1550&var-target_backend=triton-ci-XPU 1550


Not able to identify my location using GPS on Android mobile devices.

Steps to create:
Device used (Samsung Galaxy)
-Login with valid emailid,password.
-click on request help.
-click on medical.
-click on share my location

@nivetheatha  The message indicates the browser geolocation didn't work. There could be a few different reasons for this.
Did you give permission to "use your device's location"?
If so maybe it couldn't get geolocation from the device for some reason.
What browser are you using and do other sites work with geolocation? Samsung Android worked fine for me.
Anyways, it's expected that this might not work sometimes so that's why I put the specific message prompts the user to input the address.

It's not working in Samsung internet browser.
But working well in chrome and firefox.

:man_shrugging: Hmmm it is working for me in Samsung Browser.
Anyways, I think we should close this issue. The browser's Geolocation API can not always be relied on to work depending on various issues with browser, device, user not providing permission, other random issues. That's why we suggest they manually enter the address in such a case.

Ok will close this issue.


Dealing with different versions of ARM embedded gcc for examples

Different examples have different required versions of ARM embedded gcc. For example, most work fine with 4.9.x but both the cc2650 and da15000 recommend 5.4.x. The standard package manager per platform (brew, apt-get, etc.) don't have a standard way to install multiple versions of the ARM gcc, making it difficult to switch between platforms. Although that might not be typical among most users, is there a best-practice or mod we can add to the convenience make files to point to different  build versions? Like a flag to override $(CC)? Use the specific named version, ie arm-none-eabi-gcc-4.9.3?
Might also be handy for debian users as the name of the executable changed.

My general process for dealing with multiple versions of tools on Linux is simply to install them into different paths.  For example, I have:
/opt:
    gcc-arm-none-eabi-4_7-2013q3
    gcc-arm-none-eabi-4_8-2014q3
    gcc-arm-none-eabi-4_9-2015q3
    gcc-arm-none-eabi-5_4-2016q2
    gcc-arm-none-eabi-5_4-2016q3

Then I simply configure my $PATH to point to the proper directory when compiling.
Alternatively, if you look in each of the example convenience Makefiles (e.g. examples/Makefile-cc2538), you'll see the following where you can specify all the tools:
AR                              = arm-none-eabi-ar
CCAS                            = arm-none-eabi-as
CPP                             = arm-none-eabi-cpp
CC                              = arm-none-eabi-gcc
CXX                             = arm-none-eabi-g++
LD                              = arm-none-eabi-ld
STRIP                           = arm-none-eabi-strip
NM                              = arm-none-eabi-nm
RANLIB                          = arm-none-eabi-ranlib
OBJCOPY                         = arm-none-eabi-objcopy

Feel free to change those to whatever executable names/paths you like.

Fair enough :) I hacked together a little shell script because I'm lazy. Hopefully it would be useful for someone else.


[AI Agent idea] Anagram Generator

Description
AI agent to help generate anagram from a given word
Additional Information
No response

/assign @Hushmi


Readme incorrectly states to use an invalid constructor

Readme states in several places to call:
RiotApi api = new RiotApi("YOUR-API-KEY-HERE");
However, there is no RiotAPI(String) constructor.

Which version of the library are you using?

I see that now. I wrote this based on the current code base, which seems significantly different. Disregard.

Yeah, we should really have a development branch. Sorry about that.


Installation Questions

Hi, the website seems to be running into issues, so I wanted to re-host this myself and am running into some questions during installation:

Make sure onto_lib for python3 is in the python path, and all OBO ontology files required by onto_lib are present. (For now, the easiest way to accomplish this is to copy onto_lib and the OBO files into /build-db-script/onto_lib . You might have to edit the onto_lib python files to tell it where to look for the OBO files.)

Where are these files located, or where can they be obtained from? I don't see any reference to these files anywhere.

SRA metadata subset DB : SQLite file : a byproduct of the MetaSRA pipeline

Where is this file located?
Very excited to get this up and running--thanks for the help!

Thanks for alerting us to issues with the website!  We're working on figuring it out now and should hopefully have it up again soon.
Here are the OBO files:
https://github.com/deweylab/MetaSRA-pipeline/tree/master/map_sra_to_ontology/obo
As far as I can find, we haven't published the SRA subset DB file anywhere - you can get it from running the MetaSRA pipeline.  @mbernste would know better.
https://github.com/deweylab/MetaSRA-pipeline/tree/master/map_sra_to_ontology

The website is back up and running!
As far as doing a local installation of the website, I can definitely upload the SRA subset DB in the coming days. This database is a subset of the SRAdb (https://www.bioconductor.org/packages/release/bioc/html/SRAdb.html) that we use in the back-end of the website.


Fixed scene tree update after changing node name in tool script

Propagate notifications to scene tree editor when a node is renamed by script, so that the tree view is updated when changing the name of a node in a tool script.
Fixes #18102

Thanks!


Allow configuration of funding stream information on configured Testnets

Motivation
This is useful for testing changes in NU6 to the funding streams

Duplicate of #8367.


SSUI - upgrade jscs and gulp-jscs to current versions (2.7.0 and 3.0.2)

maximumLineLength.allow* is obsolete now, using allExcept
Jscs-gulp now doesn't report without a reporter, added console & fail to keep the existing behaviour
Also fixed rcfile/rcFile typo.

(as of, jscs-dev/node-jscs#2040, the value of 120 will be enough for jscs again)


Is MKCL's worth learning ?

Hi, sir,
I am Shrinesh, passed 10th SSC board exam and moving on to 11th now, as I am still a student and my dream is to be a programmer I want to learn computer languages.
I found this in my locals where a computer institute (not so big or renowned, in a village), which offers MKCL'S courses and one of them is where it's been taught C,C++, Scratch and web development... I want to know is it worth learning there , and is MKCL good and offers valued courses ?

What's MKCL?

A Brand providing courses to learn at local net cafe's. I sent this mail a
long ago... And please don't worry about trying to get knowledge about it
sir, as I now know that it's waste of time
On Thu 16 Apr, 2020, 6:01 PM Tanay Pratap<EMAIL_ADDRESS>wrote:

What's MKCL?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/tanaypratap/ama/issues/114#issuecomment-614622715,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AMKPPXBG2H6O24AFTP6SFDTRM33AZANCNFSM4HW5Y3NQ
.

And money too
On Thu 16 Apr, 2020, 8:23 PM Shrinesh Kamble<EMAIL_ADDRESS>wrote:

A Brand providing courses to learn at local net cafe's. I sent this mail a
long ago... And please don't worry about trying to get knowledge about it
sir, as I now know that it's waste of time
On Thu 16 Apr, 2020, 6:01 PM Tanay Pratap<EMAIL_ADDRESS>wrote:

What's MKCL?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/tanaypratap/ama/issues/114#issuecomment-614622715,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AMKPPXBG2H6O24AFTP6SFDTRM33AZANCNFSM4HW5Y3NQ
.

Good. Thanks. Closing this issues.