versions: Bump components to match kata 3.9.0

Following the bump of the guest-components and trustee in
https://github.com/kata-containers/kata-containers/pull/10313
to pick up the 0.10.0 and 0.10.1 versions of the
guest-components and trustee, and the kata containers 3.9.0
release, we need to bump versions to say in sync

FYI - I saw the nginx deploy test pass, so removed the timeout increase commit and it's back failing. Locally it is fine too:
=== RUN   TestLibvirtCreateNginxDeployment/Nginx_image_deployment_test/Access_for_nginx_deployment_test
=== NAME  TestLibvirtCreateNginxDeployment/Nginx_image_deployment_test
    nginx_deployment.go:136: Deleting webserver deployment...
    nginx_deployment.go:141: Deleting deployment nginx-deployment...
    nginx_deployment.go:148: Deployment nginx-deployment has been successfully deleted within 120s
--- PASS: TestLibvirtCreateNginxDeployment (147.60s)
    --- PASS: TestLibvirtCreateNginxDeployment/Nginx_image_deployment_test (147.60s)

The test is becoming a problem that is slowing PRs down a lot :(

I'm putting a hold on this as the KBS test is failing, which is very relevant to the PR changes. I'll try and debug it locally to see if I can uncover anything 🤞

Locally all the tests pass (including the CI skipped ones) except the KBS release test:
--- FAIL: TestLibvirtKbsKeyRelease (220.56s)
    --- PASS: TestLibvirtKbsKeyRelease/DoTestKbsKeyReleaseForFailure_test (110.16s)
        --- PASS: TestLibvirtKbsKeyRelease/DoTestKbsKeyReleaseForFailure_test/Kbs_key_release_is_failed (5.12s)
    --- FAIL: TestLibvirtKbsKeyRelease/KbsKeyReleasePod_test (110.18s)
        --- FAIL: TestLibvirtKbsKeyRelease/KbsKeyReleasePod_test/Kbs_key_release_is_successful (5.12s)
FAIL
FAIL	github.com/confidential-containers/cloud-api-adaptor/src/cloud-api-adaptor/test/e2e	2186.679s
FAIL

Looking at the log of the KBS it seems like the GET request was never made to it?
[2024-09-24T11:11:40Z INFO  kbs] Using config file /etc/kbs/kbs-config.toml
[2024-09-24T11:11:40Z WARN  attestation_service::rvps] No RVPS address provided and will launch a built-in rvps
[2024-09-24T11:11:40Z INFO  attestation_service::token::simple] No Token Signer key in config file, create an ephemeral key and without CA pubkey cert
[2024-09-24T11:11:40Z INFO  kbs] Starting HTTP server at [<IP_ADDRESS>:8080]
[2024-09-24T11:11:40Z INFO  actix_server::builder] starting 4 workers
[2024-09-24T11:11:40Z INFO  actix_server::server] Tokio runtime found; starting in existing Tokio runtime
[2024-09-24T13:07:50Z ERROR kbs::http::error] Set secret failed: write local fs
[2024-09-24T13:07:50Z INFO  actix_web::middleware::logger] <IP_ADDRESS> "POST /kbs/v0/resource/reponame/workload_key/key.bin HTTP/1.1" 401 125 "-" "kbs-client/0.1.0" 0.002763
[2024-09-24T13:07:50Z INFO  actix_web::middleware::logger] <IP_ADDRESS> "POST /kbs/v0/resource-policy HTTP/1.1" 200 0 "-" "kbs-client/0.1.0" 0.003217
[2024-09-24T13:07:50Z INFO  actix_web::middleware::logger] <IP_ADDRESS> "POST /kbs/v0/attestation-policy HTTP/1.1" 200 0 "-" "kbs-client/0.1.0" 0.000831
[2024-09-24T13:13:20Z INFO  actix_web::middleware::logger] <IP_ADDRESS> "POST /kbs/v0/attestation-policy HTTP/1.1" 200 0 "-" "kbs-client/0.1.0" 0.001487

The set secret did have an error though, so I'm not sure if that is also related?

When I use the kbs-client manually I also see the error:
./kbs-client --url http://<IP_ADDRESS>:30488 config --auth-private-key ../../kbs/config/kubernetes/base/kbs.key set-resource --path reponame/workload_key/key.bin --resource-file ../../kbs/config/kubernetes/overlays/x86_64/key.bin
Error: Request Failed, Response: "{\"type\":\"https://github.com/confidential-containers/kbs/errors/SetSecretFailed\",\"detail\":\"Set secret failed: write local fs\"}"

When I use the kbs-client manually I also see the error:
./kbs-client --url http://<IP_ADDRESS>:30488 config --auth-private-key ../../kbs/config/kubernetes/base/kbs.key set-resource --path reponame/workload_key/key.bin --resource-file ../../kbs/config/kubernetes/overlays/x86_64/key.bin
Error: Request Failed, Response: "{\"type\":\"https://github.com/confidential-containers/kbs/errors/SetSecretFailed\",\"detail\":\"Set secret failed: write local fs\"}"

After over an hour of debugging it looks like the set secret error is a red-herring and not the cause of the issue 😖. It might be something we consider changing anyway

There is maybe 3 hours down the drain, but I've ended up with https://github.com/confidential-containers/cloud-api-adaptor/pull/2055 to refactor the tests and avoid the error, but even with this code it's still failing for me!

Ok, through manual testing I'm managed to track down the problem with the failing test. With the 0.10.0 guest-components we can't talk to the cdh from the workload
# kubectl exec --stdin --tty kbs-key-release -n coco-pp-e2e-test-9a681be7 -- wget -q -O- http://<IP_ADDRESS>:8006/cdh/resource/reponame/workload_key/key.bin
wget: can't connect to remote host (<IP_ADDRESS>): Connection refused
command terminated with exit code 1

vs with our current version of guest-components (that is 2 months old):
# kubectl exec --stdin --tty kbs-key-release -n coco-pp-e2e-test-af08b3f2 -- wget -q -O- http://<IP_ADDRESS>:8006/cdh/resource/reponame/workload_key/key.bin
This is my cluster name:

I'm not sure if the reason for the change though

Ok, through manual testing I'm managed to track down the problem with the failing test. With the 0.10.0 guest-components we can't talk to the cdh from the workload
# kubectl exec --stdin --tty kbs-key-release -n coco-pp-e2e-test-9a681be7 -- wget -q -O- http://<IP_ADDRESS>:8006/cdh/resource/reponame/workload_key/key.bin
wget: can't connect to remote host (<IP_ADDRESS>): Connection refused
command terminated with exit code 1

vs with our current version of guest-components (that is 2 months old):
# kubectl exec --stdin --tty kbs-key-release -n coco-pp-e2e-test-af08b3f2 -- wget -q -O- http://<IP_ADDRESS>:8006/cdh/resource/reponame/workload_key/key.bin
This is my cluster name:

I'm not sure of the reason for the change though

there should be a hint of what's going wrong in the log journals of those services

note: there is also a protocol change so GC 0.9 will not be able to talk to KBS 0.10 afaik

there should be a hint of what's going wrong in the log journals of those services

Sorry it took some time for me to get the ssh-able podvm image working. There is nothing in the cdh journal as it didn't start properly:
confidential-data-hub.service - Confidential Data Hub TTRPC API Server
     Loaded: loaded (/etc/systemd/system/confidential-data-hub.service; disabled; vendor preset: enabled)
     Active: failed (Result: exit-code) since Wed 2024-09-25 12:59:36 UTC; 4min 11s ago
TriggeredBy: ● confidential-data-hub.path
    Process: 1012 ExecStart=/bin/bash -c if [ -f /run/peerpod/cdh.toml ];      then /usr/local/bin/confidential-data-hub -c /run/peerpod/cdh.toml;      else /usr/local/bin/confidential-data-hub;      fi (code=exited, s>
   Main PID: 1012 (code=exited, status=1/FAILURE)

If I try and launch it manually:
/usr/local/bin/confidential-data-hub -c /run/peerpod/cdh.toml
[2024-09-25T13:05:51Z INFO  confidential_data_hub::config] Use configuration file /run/peerpod/cdh.toml
Error: init Hub failed: kbs client creation failed: Kbs client error: create AA token provider failed: Attestation Agent token provider error: ttrpc connect failed Nix error: EACCES: Permission denied

Bisecting and picking guest-components 8e90d7430476cf7759fbbb75d1cd6364095dd63a (with the old KBS) the test fails, but the cdh service starts. It's log shows the error:
Sep 25 13:20:08 podvm-kbs-key-release-bb7fab84 bash[873]: [2024-09-25T13:20:08Z INFO  confidential_data_hub::hub] get resource called: kbs:///reponame/workload_key/key.bin
Sep 25 13:20:12 podvm-kbs-key-release-bb7fab84 bash[873]: [2024-09-25T13:20:12Z ERROR ttrpc_cdh::ttrpc_server] [ttRPC CDH] GetResource :
Sep 25 13:20:12 podvm-kbs-key-release-bb7fab84 bash[873]:     get resource failed
Sep 25 13:20:12 podvm-kbs-key-release-bb7fab84 bash[873]:     Caused by: Kbs client error: get resource failed: get token failed: Attestation Agent token provider error: cal ttrpc failed: rpc status: Status { code: INTERNAL, message: "[ERROR:attestation-agent] AA-KBC get token failed", details: [], special_fields: SpecialFields { unknown_fields: UnknownFields { fields: None }, cached_size: CachedSize { size: 0 } } }

If I try and launch it manually:
/usr/local/bin/confidential-data-hub -c /run/peerpod/cdh.toml
[2024-09-25T13:05:51Z INFO  confidential_data_hub::config] Use configuration file /run/peerpod/cdh.toml
Error: init Hub failed: kbs client creation failed: Kbs client error: create AA token provider failed: Attestation Agent

that's concerning. this doesn't have anything to do with kbs or protocol incompatibilities. that looks like CDH fails to open the AA socket.

Sorry, I found that there was logging in CDH I missed:
$ sudo journalctl -u confidential-data-hub.service
-- Logs begin at Wed 2024-09-25 13:59:31 UTC, end at Wed 2024-09-25 14:02:10 UTC. --
Sep 25 14:00:43 podvm-kbs-key-release-dafc1ee4 systemd[1]: Started Confidential Data Hub TTRPC API Server.
Sep 25 14:00:43 podvm-kbs-key-release-dafc1ee4 bash[877]: [2024-09-25T14:00:43Z INFO  confidential_data_hub::config] Use configuration file /run/peerpod/cdh.toml
Sep 25 14:00:43 podvm-kbs-key-release-dafc1ee4 bash[877]: [2024-09-25T14:00:43Z INFO  kms::plugins::kbs::cc_kbc] Use KBS public key cert
Sep 25 14:00:43 podvm-kbs-key-release-dafc1ee4 bash[877]: Error: init Hub failed: kbs client creation failed: Kbs client error: create kbs client failed: builder error
Sep 25 14:00:43 podvm-kbs-key-release-dafc1ee4 systemd[1]: confidential-data-hub.service: Main process exited, code=exited, status=1/FAILURE
Sep 25 14:00:43 podvm-kbs-key-release-dafc1ee4 systemd[1]: confidential-data-hub.service: Failed with result 'exit-code'.
Sep 25 14:00:44 podvm-kbs-key-release-dafc1ee4 systemd[1]: confidential-data-hub.service: Scheduled restart job, restart counter is at 1.
Sep 25 14:00:44 podvm-kbs-key-release-dafc1ee4 systemd[1]: Stopped Confidential Data Hub TTRPC API Server.
Sep 25 14:00:44 podvm-kbs-key-release-dafc1ee4 systemd[1]: Started Confidential Data Hub TTRPC API Server.
Sep 25 14:00:44 podvm-kbs-key-release-dafc1ee4 bash[969]: [2024-09-25T14:00:44Z INFO  confidential_data_hub::config] Use configuration file /run/peerpod/cdh.toml
Sep 25 14:00:44 podvm-kbs-key-release-dafc1ee4 bash[969]: [2024-09-25T14:00:44Z INFO  kms::plugins::kbs::cc_kbc] Use KBS public key cert
Sep 25 14:00:44 podvm-kbs-key-release-dafc1ee4 bash[969]: Error: init Hub failed: kbs client creation failed: Kbs client error: create kbs client failed: builder error
Sep 25 14:00:44 podvm-kbs-key-release-dafc1ee4 systemd[1]: confidential-data-hub.service: Main process exited, code=exited, status=1/FAILURE
Sep 25 14:00:44 podvm-kbs-key-release-dafc1ee4 systemd[1]: confidential-data-hub.service: Failed with result 'exit-code'.
Sep 25 14:00:46 podvm-kbs-key-release-dafc1ee4 systemd[1]: confidential-data-hub.service: Scheduled restart job, restart counter is at 2.
Sep 25 14:00:46 podvm-kbs-key-release-dafc1ee4 systemd[1]: Stopped Confidential Data Hub TTRPC API Server.
Sep 25 14:00:46 podvm-kbs-key-release-dafc1ee4 systemd[1]: Started Confidential Data Hub TTRPC API Server.
Sep 25 14:00:46 podvm-kbs-key-release-dafc1ee4 bash[983]: [2024-09-25T14:00:46Z INFO  confidential_data_hub::config] Use configuration file /run/peerpod/cdh.toml
Sep 25 14:00:46 podvm-kbs-key-release-dafc1ee4 bash[983]: [2024-09-25T14:00:46Z INFO  kms::plugins::kbs::cc_kbc] Use KBS public key cert
Sep 25 14:00:46 podvm-kbs-key-release-dafc1ee4 bash[983]: Error: init Hub failed: kbs client creation failed: Kbs client error: create kbs client failed: builder error
Sep 25 14:00:46 podvm-kbs-key-release-dafc1ee4 systemd[1]: confidential-data-hub.service: Main process exited, code=exited, status=1/FAILURE
Sep 25 14:00:46 podvm-kbs-key-release-dafc1ee4 systemd[1]: confidential-data-hub.service: Failed with result 'exit-code'.
Sep 25 14:00:47 podvm-kbs-key-release-dafc1ee4 systemd[1]: confidential-data-hub.service: Scheduled restart job, restart counter is at 3.
Sep 25 14:00:47 podvm-kbs-key-release-dafc1ee4 systemd[1]: Stopped Confidential Data Hub TTRPC API Server.
Sep 25 14:00:47 podvm-kbs-key-release-dafc1ee4 systemd[1]: Started Confidential Data Hub TTRPC API Server.
Sep 25 14:00:47 podvm-kbs-key-release-dafc1ee4 bash[988]: [2024-09-25T14:00:47Z INFO  confidential_data_hub::config] Use configuration file /run/peerpod/cdh.toml
Sep 25 14:00:47 podvm-kbs-key-release-dafc1ee4 bash[988]: [2024-09-25T14:00:47Z INFO  kms::plugins::kbs::cc_kbc] Use KBS public key cert
Sep 25 14:00:47 podvm-kbs-key-release-dafc1ee4 bash[988]: Error: init Hub failed: kbs client creation failed: Kbs client error: create kbs client failed: builder error
Sep 25 14:00:47 podvm-kbs-key-release-dafc1ee4 systemd[1]: confidential-data-hub.service: Main process exited, code=exited, status=1/FAILURE
Sep 25 14:00:47 podvm-kbs-key-release-dafc1ee4 systemd[1]: confidential-data-hub.service: Failed with result 'exit-code'.
Sep 25 14:00:48 podvm-kbs-key-release-dafc1ee4 systemd[1]: confidential-data-hub.service: Scheduled restart job, restart counter is at 4.
Sep 25 14:00:48 podvm-kbs-key-release-dafc1ee4 systemd[1]: Stopped Confidential Data Hub TTRPC API Server.
Sep 25 14:00:48 podvm-kbs-key-release-dafc1ee4 systemd[1]: Started Confidential Data Hub TTRPC API Server.
Sep 25 14:00:48 podvm-kbs-key-release-dafc1ee4 bash[993]: [2024-09-25T14:00:48Z INFO  confidential_data_hub::config] Use configuration file /run/peerpod/cdh.toml
Sep 25 14:00:48 podvm-kbs-key-release-dafc1ee4 bash[993]: [2024-09-25T14:00:48Z INFO  kms::plugins::kbs::cc_kbc] Use KBS public key cert
Sep 25 14:00:48 podvm-kbs-key-release-dafc1ee4 bash[993]: Error: init Hub failed: kbs client creation failed: Kbs client error: create kbs client failed: builder error
Sep 25 14:00:48 podvm-kbs-key-release-dafc1ee4 systemd[1]: confidential-data-hub.service: Main process exited, code=exited, status=1/FAILURE
Sep 25 14:00:48 podvm-kbs-key-release-dafc1ee4 systemd[1]: confidential-data-hub.service: Failed with result 'exit-code'.
Sep 25 14:00:49 podvm-kbs-key-release-dafc1ee4 systemd[1]: confidential-data-hub.service: Scheduled restart job, restart counter is at 5.
Sep 25 14:00:49 podvm-kbs-key-release-dafc1ee4 systemd[1]: Stopped Confidential Data Hub TTRPC API Server.
Sep 25 14:00:49 podvm-kbs-key-release-dafc1ee4 systemd[1]: confidential-data-hub.service: Start request repeated too quickly.
Sep 25 14:00:49 podvm-kbs-key-release-dafc1ee4 systemd[1]: confidential-data-hub.service: Failed with result 'exit-code'.
Sep 25 14:00:49 podvm-kbs-key-release-dafc1ee4 systemd[1]: Failed to start Confidential Data Hub TTRPC API Server.

I've tried about 10 different combinations in the /run/peerpod/cdh.toml (including some from the cdh config unit tests) and couldn't get them to work, so I've messaged Ding for advice, which hopefully will get us back on track.

All the libvirt tests worked manually for me:
time="2024-09-26T17:49:16Z" level=info msg="Deploying kbs"
time="2024-09-26T17:49:16Z" level=info msg="creating key.bin"
time="2024-09-26T17:49:16Z" level=info msg="Creating kbs install overlay"
time="2024-09-26T17:49:16Z" level=info msg="Customize the overlay yaml file"
time="2024-09-26T17:49:16Z" level=info msg="Updating kbs image with \"ghcr.io/confidential-containers/key-broker-service\""
time="2024-09-26T17:49:16Z" level=info msg="Updating kbs image tag with \"built-in-as-v0.10.1\""
time="2024-09-26T17:49:16Z" level=info msg="Creating kbs install overlay"
time="2024-09-26T17:49:16Z" level=info msg="Install Kbs"
Wait for the kbs deployment be available
time="2024-09-26T17:49:36Z" level=info msg="kbsEndpoint: http://<IP_ADDRESS>:32466"
time="2024-09-26T17:49:36Z" level=info msg="Podvm uploading"
time="2024-09-26T17:49:36Z" level=trace msg="UploadPodvm()"
time="2024-09-26T17:49:38Z" level=info msg="Install Cloud API Adaptor"
time="2024-09-26T17:49:38Z" level=info msg="Deploy the Cloud API Adaptor"
time="2024-09-26T17:49:38Z" level=info msg="Install the controller manager"
time="2024-09-26T17:49:40Z" level=trace msg="/usr/local/bin/kubectl apply -k https://github.com/confidential-containers/operator/config/default?ref=main, output: namespace/confidential-containers-system created\ncustomresourcedefinition.apiextensions.k8s.io/ccruntimes.confidentialcontainers.org created\nserviceaccount/cc-operator-controller-manager created\nrole.rbac.authorization.k8s.io/cc-operator-leader-election-role created\nclusterrole.rbac.authorization.k8s.io/cc-operator-manager-role created\nclusterrole.rbac.authorization.k8s.io/cc-operator-metrics-reader created\nclusterrole.rbac.authorization.k8s.io/cc-operator-proxy-role created\nrolebinding.rbac.authorization.k8s.io/cc-operator-leader-election-rolebinding created\nclusterrolebinding.rbac.authorization.k8s.io/cc-operator-manager-rolebinding created\nclusterrolebinding.rbac.authorization.k8s.io/cc-operator-proxy-rolebinding created\nconfigmap/cc-operator-manager-config created\nservice/cc-operator-controller-manager-metrics-service created\ndeployment.apps/cc-operator-controller-manager created\n"
Wait for the cc-operator-controller-manager deployment be available
time="2024-09-26T17:50:45Z" level=info msg="Customize the overlay yaml file"
time="2024-09-26T17:50:46Z" level=trace msg="/usr/local/bin/kubectl apply -k https://github.com/confidential-containers/operator/config/samples/ccruntime/peer-pods?ref=main, output: ccruntime.confidentialcontainers.org/ccruntime-peer-pods created\n"
time="2024-09-26T17:50:46Z" level=info msg="Install the cloud-api-adaptor"
Wait for the cloud-api-adaptor-daemonset DaemonSet be available
Wait for the pod cloud-api-adaptor-daemonset-h7z7h be ready
Wait for the cc-operator-daemon-install DaemonSet be available
Wait for the pod cc-operator-daemon-install-m5sbh be ready
Wait for the kata-remote runtimeclass be created
time="2024-09-26T17:53:08Z" level=info msg="Installing peerpod-ctrl"
time="2024-09-26T17:53:11Z" level=trace msg="/usr/bin/make -C ../peerpod-ctrl deploy, output: make[1]: Entering directory '/root/go/src/github.com/confidential-containers/cloud-api-adaptor/src/peerpod-ctrl'\ntest -s /root/go/src/github.com/confidential-containers/cloud-api-adaptor/src/peerpod-ctrl/bin/controller-gen || GOBIN=/root/go/src/github.com/confidential-containers/cloud-api-adaptor/src/peerpod-ctrl/bin go install<EMAIL_ADDRESS>rbac:roleName=manager-role crd webhook paths=\"./...\" output:crd:artifacts:config=config/crd/bases\ncd config/manager && /root/go/src/github.com/confidential-containers/cloud-api-adaptor/src/peerpod-ctrl/bin/kustomize edit set image controller=quay.io/confidential-containers/peerpod-ctrl:latest\n/root/go/src/github.com/confidential-containers/cloud-api-adaptor/src/peerpod-ctrl/bin/kustomize build config/default | kubectl apply -f -\n# Warning: 'patchesStrategicMerge' is deprecated. Please use 'patches' instead. Run 'kustomize edit fix' to update your Kustomization automatically.\nnamespace/confidential-containers-system configured\ncustomresourcedefinition.apiextensions.k8s.io/peerpods.confidentialcontainers.org created\nserviceaccount/peerpod-ctrl-controller-manager created\nrole.rbac.authorization.k8s.io/peerpod-ctrl-leader-election-role created\nclusterrole.rbac.authorization.k8s.io/peerpod-ctrl-manager-role created\nclusterrole.rbac.authorization.k8s.io/peerpod-ctrl-metrics-reader created\nclusterrole.rbac.authorization.k8s.io/peerpod-ctrl-proxy-role created\nrolebinding.rbac.authorization.k8s.io/peerpod-ctrl-leader-election-rolebinding created\nclusterrolebinding.rbac.authorization.k8s.io/peerpod-ctrl-manager-rolebinding created\nclusterrolebinding.rbac.authorization.k8s.io/peerpod-ctrl-proxy-rolebinding created\nservice/peerpod-ctrl-controller-manager-metrics-service created\ndeployment.apps/peerpod-ctrl-controller-manager created\nmake[1]: Leaving directory '/root/go/src/github.com/confidential-containers/cloud-api-adaptor/src/peerpod-ctrl'\n"
time="2024-09-26T17:53:11Z" level=info msg="Wait for the peerpod-ctrl deployment to be available"
time="2024-09-26T17:53:46Z" level=info msg="Creating namespace 'coco-pp-e2e-test-f525ce84'..."
time="2024-09-26T17:53:46Z" level=info msg="Wait for namespace 'coco-pp-e2e-test-f525ce84' be ready..."
time="2024-09-26T17:53:51Z" level=info msg="Wait for default serviceaccount in namespace 'coco-pp-e2e-test-f525ce84'..."
time="2024-09-26T17:53:51Z" level=info msg="default serviceAccount exists, namespace 'coco-pp-e2e-test-f525ce84' is ready for use"
=== RUN   TestLibvirtCreateSimplePod
=== RUN   TestLibvirtCreateSimplePod/SimplePeerPod_test
    assessment_runner.go:264: Waiting for containers in pod: simple-test are ready
=== RUN   TestLibvirtCreateSimplePod/SimplePeerPod_test/PodVM_is_created
time="2024-09-26T17:55:31Z" level=trace msg="Test pod running on node peer-pods-worker-0"
=== NAME  TestLibvirtCreateSimplePod/SimplePeerPod_test
    assessment_runner.go:617: Deleting pod simple-test...
    assessment_runner.go:624: Pod simple-test has been successfully deleted within 60s
--- PASS: TestLibvirtCreateSimplePod (105.06s)
    --- PASS: TestLibvirtCreateSimplePod/SimplePeerPod_test (105.06s)
        --- PASS: TestLibvirtCreateSimplePod/SimplePeerPod_test/PodVM_is_created (0.03s)
=== RUN   TestLibvirtCreatePodWithConfigMap
=== RUN   TestLibvirtCreatePodWithConfigMap/ConfigMapPeerPod_test
    assessment_runner.go:264: Waiting for containers in pod: busybox-configmap-pod are ready
=== RUN   TestLibvirtCreatePodWithConfigMap/ConfigMapPeerPod_test/Configmap_is_created_and_contains_data
    assessment_runner.go:435: Output when execute test commands:
=== NAME  TestLibvirtCreatePodWithConfigMap/ConfigMapPeerPod_test
    assessment_runner.go:560: Deleting Configmap... busybox-configmap
    assessment_runner.go:617: Deleting pod busybox-configmap-pod...
    assessment_runner.go:624: Pod busybox-configmap-pod has been successfully deleted within 60s
--- PASS: TestLibvirtCreatePodWithConfigMap (110.14s)
    --- PASS: TestLibvirtCreatePodWithConfigMap/ConfigMapPeerPod_test (110.14s)
        --- PASS: TestLibvirtCreatePodWithConfigMap/ConfigMapPeerPod_test/Configmap_is_created_and_contains_data (5.09s)
=== RUN   TestLibvirtCreatePodWithSecret
=== RUN   TestLibvirtCreatePodWithSecret/SecretPeerPod_test
    assessment_runner.go:264: Waiting for containers in pod: busybox-secret-pod are ready
=== RUN   TestLibvirtCreatePodWithSecret/SecretPeerPod_test/Secret_has_been_created_and_contains_data
    assessment_runner.go:435: Output when execute test commands:
=== NAME  TestLibvirtCreatePodWithSecret/SecretPeerPod_test
    assessment_runner.go:567: Deleting Secret... busybox-secret
    assessment_runner.go:617: Deleting pod busybox-secret-pod...
    assessment_runner.go:624: Pod busybox-secret-pod has been successfully deleted within 60s
--- PASS: TestLibvirtCreatePodWithSecret (110.15s)
    --- PASS: TestLibvirtCreatePodWithSecret/SecretPeerPod_test (110.15s)
        --- PASS: TestLibvirtCreatePodWithSecret/SecretPeerPod_test/Secret_has_been_created_and_contains_data (5.11s)
=== RUN   TestLibvirtCreatePeerPodContainerWithExternalIPAccess
=== RUN   TestLibvirtCreatePeerPodContainerWithExternalIPAccess/IPAccessPeerPod_test
    assessment_runner.go:264: Waiting for containers in pod: busybox-priv are ready
=== RUN   TestLibvirtCreatePeerPodContainerWithExternalIPAccess/IPAccessPeerPod_test/Peer_Pod_Container_Connected_to_External_IP
    assessment_runner.go:435: Output when execute test commands:
=== NAME  TestLibvirtCreatePeerPodContainerWithExternalIPAccess/IPAccessPeerPod_test
    assessment_runner.go:617: Deleting pod busybox-priv...
    assessment_runner.go:624: Pod busybox-priv has been successfully deleted within 60s
--- PASS: TestLibvirtCreatePeerPodContainerWithExternalIPAccess (110.14s)
    --- PASS: TestLibvirtCreatePeerPodContainerWithExternalIPAccess/IPAccessPeerPod_test (110.14s)
        --- PASS: TestLibvirtCreatePeerPodContainerWithExternalIPAccess/IPAccessPeerPod_test/Peer_Pod_Container_Connected_to_External_IP (5.10s)
=== RUN   TestLibvirtCreatePeerPodWithJob
=== RUN   TestLibvirtCreatePeerPodWithJob/JobPeerPod_test
=== RUN   TestLibvirtCreatePeerPodWithJob/JobPeerPod_test/Job_has_been_created
    assessment_helpers.go:292: SUCCESS: job-pi-jzwff - Completed - LOG: 3.14156
    assessment_runner.go:336: Output Log from Pod: 3.14156
=== NAME  TestLibvirtCreatePeerPodWithJob/JobPeerPod_test
    assessment_runner.go:600: Deleting Job... job-pi
    assessment_runner.go:607: Deleting pods created by job... job-pi-jzwff
--- PASS: TestLibvirtCreatePeerPodWithJob (95.05s)
    --- PASS: TestLibvirtCreatePeerPodWithJob/JobPeerPod_test (95.05s)
        --- PASS: TestLibvirtCreatePeerPodWithJob/JobPeerPod_test/Job_has_been_created (0.02s)
=== RUN   TestLibvirtCreatePeerPodAndCheckUserLogs
    common_suite.go:165: Skipping Test until issue kata-containers/kata-containers#5732 is Fixed
--- SKIP: TestLibvirtCreatePeerPodAndCheckUserLogs (0.00s)
=== RUN   TestLibvirtCreatePeerPodAndCheckWorkDirLogs
=== RUN   TestLibvirtCreatePeerPodAndCheckWorkDirLogs/WorkDirPeerPod_test
=== RUN   TestLibvirtCreatePeerPodAndCheckWorkDirLogs/WorkDirPeerPod_test/Peer_pod_with_work_directory_has_been_created
    assessment_runner.go:366: Log output of peer pod:/other
=== NAME  TestLibvirtCreatePeerPodAndCheckWorkDirLogs/WorkDirPeerPod_test
    assessment_runner.go:617: Deleting pod workdirpod...
    assessment_runner.go:624: Pod workdirpod has been successfully deleted within 60s
--- PASS: TestLibvirtCreatePeerPodAndCheckWorkDirLogs (105.06s)
    --- PASS: TestLibvirtCreatePeerPodAndCheckWorkDirLogs/WorkDirPeerPod_test (105.06s)
        --- PASS: TestLibvirtCreatePeerPodAndCheckWorkDirLogs/WorkDirPeerPod_test/Peer_pod_with_work_directory_has_been_created (5.02s)
=== RUN   TestLibvirtCreatePeerPodAndCheckEnvVariableLogsWithImageOnly
=== RUN   TestLibvirtCreatePeerPodAndCheckEnvVariableLogsWithImageOnly/EnvVariablePeerPodWithImageOnly_test
=== RUN   TestLibvirtCreatePeerPodAndCheckEnvVariableLogsWithImageOnly/EnvVariablePeerPodWithImageOnly_test/Peer_pod_with_environmental_variables_has_been_created
    assessment_runner.go:366: Log output of peer pod:KUBERNETES_SERVICE_PORT=443
        KUBERNETES_PORT=tcp://<IP_ADDRESS>:443
        HOSTNAME=env-variable-in-image
        SHLVL=1
        HOME=/root
        KUBERNETES_PORT_443_TCP_ADDR=<IP_ADDRESS>
        PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
        KUBERNETES_PORT_443_TCP_PORT=443
        KUBERNETES_PORT_443_TCP_PROTO=tcp
        KUBERNETES_PORT_443_TCP=tcp://<IP_ADDRESS>:443
        KUBERNETES_SERVICE_PORT_HTTPS=443
        ISPRODUCTION=false
        KUBERNETES_SERVICE_HOST=<IP_ADDRESS>
        PWD=/
=== NAME  TestLibvirtCreatePeerPodAndCheckEnvVariableLogsWithImageOnly/EnvVariablePeerPodWithImageOnly_test
    assessment_runner.go:617: Deleting pod env-variable-in-image...
    assessment_runner.go:624: Pod env-variable-in-image has been successfully deleted within 60s
--- PASS: TestLibvirtCreatePeerPodAndCheckEnvVariableLogsWithImageOnly (105.05s)
    --- PASS: TestLibvirtCreatePeerPodAndCheckEnvVariableLogsWithImageOnly/EnvVariablePeerPodWithImageOnly_test (105.05s)
        --- PASS: TestLibvirtCreatePeerPodAndCheckEnvVariableLogsWithImageOnly/EnvVariablePeerPodWithImageOnly_test/Peer_pod_with_environmental_variables_has_been_created (5.02s)
=== RUN   TestLibvirtCreatePeerPodAndCheckEnvVariableLogsWithDeploymentOnly
=== RUN   TestLibvirtCreatePeerPodAndCheckEnvVariableLogsWithDeploymentOnly/EnvVariablePeerPodWithDeploymentOnly_test
=== RUN   TestLibvirtCreatePeerPodAndCheckEnvVariableLogsWithDeploymentOnly/EnvVariablePeerPodWithDeploymentOnly_test/Peer_pod_with_environmental_variables_has_been_created
    assessment_runner.go:366: Log output of peer pod:KUBERNETES_PORT=tcp://<IP_ADDRESS>:443
        KUBERNETES_SERVICE_PORT=443
        HOSTNAME=env-variable-in-config
        SHLVL=1
        HOME=/root
        KUBERNETES_PORT_443_TCP_ADDR=<IP_ADDRESS>
        PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
        KUBERNETES_PORT_443_TCP_PORT=443
        KUBERNETES_PORT_443_TCP_PROTO=tcp
        KUBERNETES_SERVICE_PORT_HTTPS=443
        KUBERNETES_PORT_443_TCP=tcp://<IP_ADDRESS>:443
        ISPRODUCTION=true
        KUBERNETES_SERVICE_HOST=<IP_ADDRESS>
        PWD=/
=== NAME  TestLibvirtCreatePeerPodAndCheckEnvVariableLogsWithDeploymentOnly/EnvVariablePeerPodWithDeploymentOnly_test
    assessment_runner.go:617: Deleting pod env-variable-in-config...
    assessment_runner.go:624: Pod env-variable-in-config has been successfully deleted within 60s
--- PASS: TestLibvirtCreatePeerPodAndCheckEnvVariableLogsWithDeploymentOnly (105.06s)
    --- PASS: TestLibvirtCreatePeerPodAndCheckEnvVariableLogsWithDeploymentOnly/EnvVariablePeerPodWithDeploymentOnly_test (105.06s)
        --- PASS: TestLibvirtCreatePeerPodAndCheckEnvVariableLogsWithDeploymentOnly/EnvVariablePeerPodWithDeploymentOnly_test/Peer_pod_with_environmental_variables_has_been_created (5.02s)
=== RUN   TestLibvirtCreatePeerPodAndCheckEnvVariableLogsWithImageAndDeployment
=== RUN   TestLibvirtCreatePeerPodAndCheckEnvVariableLogsWithImageAndDeployment/EnvVariablePeerPodWithBoth_test
=== RUN   TestLibvirtCreatePeerPodAndCheckEnvVariableLogsWithImageAndDeployment/EnvVariablePeerPodWithBoth_test/Peer_pod_with_environmental_variables_has_been_created
    assessment_runner.go:366: Log output of peer pod:KUBERNETES_SERVICE_PORT=443
        KUBERNETES_PORT=tcp://<IP_ADDRESS>:443
        HOSTNAME=env-variable-in-both
        SHLVL=1
        HOME=/root
        KUBERNETES_PORT_443_TCP_ADDR=<IP_ADDRESS>
        PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
        KUBERNETES_PORT_443_TCP_PORT=443
        KUBERNETES_PORT_443_TCP_PROTO=tcp
        KUBERNETES_SERVICE_PORT_HTTPS=443
        KUBERNETES_PORT_443_TCP=tcp://<IP_ADDRESS>:443
        ISPRODUCTION=true
        KUBERNETES_SERVICE_HOST=<IP_ADDRESS>
        PWD=/
=== NAME  TestLibvirtCreatePeerPodAndCheckEnvVariableLogsWithImageAndDeployment/EnvVariablePeerPodWithBoth_test
    assessment_runner.go:617: Deleting pod env-variable-in-both...
    assessment_runner.go:624: Pod env-variable-in-both has been successfully deleted within 60s
--- PASS: TestLibvirtCreatePeerPodAndCheckEnvVariableLogsWithImageAndDeployment (105.05s)
    --- PASS: TestLibvirtCreatePeerPodAndCheckEnvVariableLogsWithImageAndDeployment/EnvVariablePeerPodWithBoth_test (105.05s)
        --- PASS: TestLibvirtCreatePeerPodAndCheckEnvVariableLogsWithImageAndDeployment/EnvVariablePeerPodWithBoth_test/Peer_pod_with_environmental_variables_has_been_created (5.02s)
=== RUN   TestLibvirtCreateNginxDeployment
=== RUN   TestLibvirtCreateNginxDeployment/Nginx_image_deployment_test
    nginx_deployment.go:106: Creating nginx deployment...
    nginx_deployment.go:163: Current deployment available replicas: 0
    nginx_deployment.go:163: Current deployment available replicas: 0
    nginx_deployment.go:163: Current deployment available replicas: 0
    nginx_deployment.go:163: Current deployment available replicas: 0
    nginx_deployment.go:163: Current deployment available replicas: 0
    nginx_deployment.go:163: Current deployment available replicas: 0
    nginx_deployment.go:163: Current deployment available replicas: 0
    nginx_deployment.go:163: Current deployment available replicas: 0
    nginx_deployment.go:163: Current deployment available replicas: 0
    nginx_deployment.go:163: Current deployment available replicas: 0
    nginx_deployment.go:163: Current deployment available replicas: 0
    nginx_deployment.go:163: Current deployment available replicas: 0
    nginx_deployment.go:163: Current deployment available replicas: 2
    nginx_deployment.go:111: nginx deployment is available now
=== RUN   TestLibvirtCreateNginxDeployment/Nginx_image_deployment_test/Access_for_nginx_deployment_test
=== NAME  TestLibvirtCreateNginxDeployment/Nginx_image_deployment_test
    nginx_deployment.go:136: Deleting webserver deployment...
    nginx_deployment.go:141: Deleting deployment nginx-deployment...
    nginx_deployment.go:148: Deployment nginx-deployment has been successfully deleted within 120s
--- PASS: TestLibvirtCreateNginxDeployment (135.03s)
    --- PASS: TestLibvirtCreateNginxDeployment/Nginx_image_deployment_test (135.03s)
        --- PASS: TestLibvirtCreateNginxDeployment/Nginx_image_deployment_test/Access_for_nginx_deployment_test (0.00s)
=== RUN   TestLibvirtDeletePod
=== RUN   TestLibvirtDeletePod/DeletePod_test
    assessment_runner.go:264: Waiting for containers in pod: deletion-test are ready
=== RUN   TestLibvirtDeletePod/DeletePod_test/Deletion_complete
=== NAME  TestLibvirtDeletePod/DeletePod_test
    assessment_runner.go:617: Deleting pod deletion-test...
    assessment_runner.go:624: Pod deletion-test has been successfully deleted within 60s
--- PASS: TestLibvirtDeletePod (105.04s)
    --- PASS: TestLibvirtDeletePod/DeletePod_test (105.04s)
        --- PASS: TestLibvirtDeletePod/DeletePod_test/Deletion_complete (0.00s)
=== RUN   TestLibvirtPodToServiceCommunication
=== RUN   TestLibvirtPodToServiceCommunication/TestExtraPods_test
    assessment_runner.go:264: Waiting for containers in pod: test-server are ready
    assessment_runner.go:297: webserver service is available on cluster IP: <IP_ADDRESS>
    assessment_runner.go:301: Provision extra pod test-client
    assessment_helpers.go:385: Waiting for containers in pod: test-client are ready
=== RUN   TestLibvirtPodToServiceCommunication/TestExtraPods_test/Failed_to_test_extra_pod.
=== NAME  TestLibvirtPodToServiceCommunication
    common_suite.go:428: Success to access nginx service. <!DOCTYPE html>
        <html>
        <head>
        <title>Welcome to nginx!</title>
        <style>
        html { color-scheme: light dark; }
        body { width: 35em; margin: 0 auto;
        font-family: Tahoma, Verdana, Arial, sans-serif; }
        </style>
        </head>
        <body>
        <h1>Welcome to nginx!</h1>
        <p>If you see this page, the nginx web server is successfully installed and
        working. Further configuration is required.</p>

        <p>For online documentation and support please refer to
        <a href="http://nginx.org/">nginx.org</a>.<br/>
        Commercial support is available at
        <a href="http://nginx.com/">nginx.com</a>.</p>

        <p><em>Thank you for using nginx.</em></p>
        </body>
        </html>
=== NAME  TestLibvirtPodToServiceCommunication/TestExtraPods_test/Failed_to_test_extra_pod.
    assessment_runner.go:532: Output when execute test commands:<!DOCTYPE html>
        <html>
        <head>
        <title>Welcome to nginx!</title>
        <style>
        html { color-scheme: light dark; }
        body { width: 35em; margin: 0 auto;
        font-family: Tahoma, Verdana, Arial, sans-serif; }
        </style>
        </head>
        <body>
        <h1>Welcome to nginx!</h1>
        <p>If you see this page, the nginx web server is successfully installed and
        working. Further configuration is required.</p>

        <p>For online documentation and support please refer to
        <a href="http://nginx.org/">nginx.org</a>.<br/>
        Commercial support is available at
        <a href="http://nginx.com/">nginx.com</a>.</p>

        <p><em>Thank you for using nginx.</em></p>
        </body>
        </html>
=== NAME  TestLibvirtPodToServiceCommunication/TestExtraPods_test
    assessment_runner.go:617: Deleting pod test-server...
    assessment_runner.go:624: Pod test-server has been successfully deleted within 60s
    assessment_runner.go:630: Deleting pod test-client...
    assessment_runner.go:636: Pod test-client has been successfully deleted within 60s
    assessment_runner.go:652: Deleting Service... nginx-server
--- PASS: TestLibvirtPodToServiceCommunication (235.20s)
    --- PASS: TestLibvirtPodToServiceCommunication/TestExtraPods_test (235.20s)
        --- PASS: TestLibvirtPodToServiceCommunication/TestExtraPods_test/Failed_to_test_extra_pod. (5.10s)
=== RUN   TestLibvirtPodsMTLSCommunication
=== RUN   TestLibvirtPodsMTLSCommunication/TestPodsMTLSCommunication_test
    assessment_runner.go:264: Waiting for containers in pod: mtls-server are ready
    assessment_runner.go:297: webserver service is available on cluster IP: <IP_ADDRESS>
    assessment_runner.go:301: Provision extra pod mtls-client
    assessment_helpers.go:385: Waiting for containers in pod: mtls-client are ready
=== RUN   TestLibvirtPodsMTLSCommunication/TestPodsMTLSCommunication_test/Pods_communication_with_mTLS
=== NAME  TestLibvirtPodsMTLSCommunication
    common_suite.go:522: Success to access nginx service. <!DOCTYPE html>
        <html>
        <head>
        <title>Welcome to nginx!</title>
        <style>
        html { color-scheme: light dark; }
        body { width: 35em; margin: 0 auto;
        font-family: Tahoma, Verdana, Arial, sans-serif; }
        </style>
        </head>
        <body>
        <h1>Welcome to nginx!</h1>
        <p>If you see this page, the nginx web server is successfully installed and
        working. Further configuration is required.</p>

        <p>For online documentation and support please refer to
        <a href="http://nginx.org/">nginx.org</a>.<br/>
        Commercial support is available at
        <a href="http://nginx.com/">nginx.com</a>.</p>

        <p><em>Thank you for using nginx.</em></p>
        </body>
        </html>
=== NAME  TestLibvirtPodsMTLSCommunication/TestPodsMTLSCommunication_test/Pods_communication_with_mTLS
    assessment_runner.go:532: Output when execute test commands:<!DOCTYPE html>
        <html>
        <head>
        <title>Welcome to nginx!</title>
        <style>
        html { color-scheme: light dark; }
        body { width: 35em; margin: 0 auto;
        font-family: Tahoma, Verdana, Arial, sans-serif; }
        </style>
        </head>
        <body>
        <h1>Welcome to nginx!</h1>
        <p>If you see this page, the nginx web server is successfully installed and
        working. Further configuration is required.</p>

        <p>For online documentation and support please refer to
        <a href="http://nginx.org/">nginx.org</a>.<br/>
        Commercial support is available at
        <a href="http://nginx.com/">nginx.com</a>.</p>

        <p><em>Thank you for using nginx.</em></p>
        </body>
        </html>
=== NAME  TestLibvirtPodsMTLSCommunication/TestPodsMTLSCommunication_test
    assessment_runner.go:560: Deleting Configmap... nginx-conf
    assessment_runner.go:567: Deleting Secret... server-certs
    assessment_runner.go:586: Deleting extra Secret... curl-certs
    assessment_runner.go:617: Deleting pod mtls-server...
    assessment_runner.go:624: Pod mtls-server has been successfully deleted within 60s
    assessment_runner.go:630: Deleting pod mtls-client...
    assessment_runner.go:636: Pod mtls-client has been successfully deleted within 60s
    assessment_runner.go:652: Deleting Service... nginx-mtls
--- PASS: TestLibvirtPodsMTLSCommunication (225.27s)
    --- PASS: TestLibvirtPodsMTLSCommunication/TestPodsMTLSCommunication_test (225.27s)
        --- PASS: TestLibvirtPodsMTLSCommunication/TestPodsMTLSCommunication_test/Pods_communication_with_mTLS (5.12s)
=== RUN   TestLibvirtKbsKeyRelease
time="2024-09-26T18:21:22Z" level=info msg="set key resource: ../../kbs/config/kubernetes/overlays/x86_64/key.bin"
time="2024-09-26T18:21:22Z" level=trace msg="./kbs-client --url http://<IP_ADDRESS>:32466 config --auth-private-key ../../kbs/config/kubernetes/base/kbs.key set-resource --path reponame/workload_key/key.bin --resource-file ../../kbs/config/kubernetes/overlays/x86_64/key.bin, output: Error: Request Failed, Response: \"{\\\"type\\\":\\\"https://github.com/confidential-containers/kbs/errors/SetSecretFailed\\\",\\\"detail\\\":\\\"Set secret failed: write local fs\\\"}\"\n"
time="2024-09-26T18:21:22Z" level=info msg="EnableKbsCustomizedPolicy: ../../kbs/sample_policies/allow_all.rego"
time="2024-09-26T18:21:22Z" level=trace msg="./kbs-client --url http://<IP_ADDRESS>:32466 config --auth-private-key ../../kbs/config/kubernetes/base/kbs.key set-resource-policy --policy-file ../../kbs/sample_policies/allow_all.rego, output: Set resource policy success \n policy: CnBhY2thZ2UgcG9saWN5CgpkZWZhdWx0IGFsbG93ID0gdHJ1ZQoK\n"
time="2024-09-26T18:21:22Z" level=info msg="EnableKbsCustomizedPolicy: ../../kbs/sample_policies/deny_all.rego"
time="2024-09-26T18:21:22Z" level=trace msg="./kbs-client --url http://<IP_ADDRESS>:32466 config --auth-private-key ../../kbs/config/kubernetes/base/kbs.key set-attestation-policy --policy-file ../../kbs/sample_policies/deny_all.rego, output: Set attestation policy success \n policy: CnBhY2thZ2UgcG9saWN5CgpkZWZhdWx0IGFsbG93ID0gZmFsc2UK\n"
=== PAUSE TestLibvirtKbsKeyRelease
=== RUN   TestLibvirtRestrictivePolicyBlocksExec
=== RUN   TestLibvirtRestrictivePolicyBlocksExec/PodVMwithPolicyBlockingExec_test
    assessment_runner.go:264: Waiting for containers in pod: policy-exec-rejected are ready
=== RUN   TestLibvirtRestrictivePolicyBlocksExec/PodVMwithPolicyBlockingExec_test/Pod_which_blocks_Exec_Process
=== NAME  TestLibvirtRestrictivePolicyBlocksExec
    common_suite.go:636: Exec process was blocked Internal error occurred: error executing command in container: failed to exec in container: failed to start exec "c45bbc5d05b899e67b2f44a79a6cc3f35bac14af607cb8619c3c5212d8a4af78": cannot enter container 6e1ca9a0ebcb2a181384757fb70de5c31f4deeb88778580cca21889803dec7dd, with err rpc error: code = PermissionDenied desc = "ExecProcessRequest is blocked by policy: ": unknown
=== NAME  TestLibvirtRestrictivePolicyBlocksExec/PodVMwithPolicyBlockingExec_test/Pod_which_blocks_Exec_Process
    assessment_runner.go:435: Output when execute test commands:
=== NAME  TestLibvirtRestrictivePolicyBlocksExec/PodVMwithPolicyBlockingExec_test
    assessment_runner.go:617: Deleting pod policy-exec-rejected...
    assessment_runner.go:624: Pod policy-exec-rejected has been successfully deleted within 60s
--- PASS: TestLibvirtRestrictivePolicyBlocksExec (110.09s)
    --- PASS: TestLibvirtRestrictivePolicyBlocksExec/PodVMwithPolicyBlockingExec_test (110.09s)
        --- PASS: TestLibvirtRestrictivePolicyBlocksExec/PodVMwithPolicyBlockingExec_test/Pod_which_blocks_Exec_Process (5.05s)
=== RUN   TestLibvirtPermissivePolicyAllowsExec
=== RUN   TestLibvirtPermissivePolicyAllowsExec/PodVMwithPermissivePolicy_test
    assessment_runner.go:264: Waiting for containers in pod: policy-all-allowed are ready
=== RUN   TestLibvirtPermissivePolicyAllowsExec/PodVMwithPermissivePolicy_test/Pod_which_allows_all_kata_agent_APIs
    assessment_runner.go:435: Output when execute test commands:
=== NAME  TestLibvirtPermissivePolicyAllowsExec/PodVMwithPermissivePolicy_test
    assessment_runner.go:617: Deleting pod policy-all-allowed...
    assessment_runner.go:624: Pod policy-all-allowed has been successfully deleted within 60s
--- PASS: TestLibvirtPermissivePolicyAllowsExec (110.15s)
    --- PASS: TestLibvirtPermissivePolicyAllowsExec/PodVMwithPermissivePolicy_test (110.15s)
        --- PASS: TestLibvirtPermissivePolicyAllowsExec/PodVMwithPermissivePolicy_test/Pod_which_allows_all_kata_agent_APIs (5.11s)
=== RUN   TestLibvirtCreatePeerPodWithAuthenticatedImageWithoutCredentials
    libvirt_test.go:152: Authenticated Image Name not exported
--- SKIP: TestLibvirtCreatePeerPodWithAuthenticatedImageWithoutCredentials (0.00s)
=== RUN   TestLibvirtCreatePeerPodWithAuthenticatedImageWithValidCredentials
    libvirt_test.go:161: Registry Credentials, or authenticated image name not exported
--- SKIP: TestLibvirtCreatePeerPodWithAuthenticatedImageWithValidCredentials (0.00s)
=== CONT  TestLibvirtKbsKeyRelease
    common_suite.go:573: Do test kbs key release failure case
=== RUN   TestLibvirtKbsKeyRelease/DoTestKbsKeyReleaseForFailure_test
    assessment_runner.go:264: Waiting for containers in pod: kbs-failure are ready
=== RUN   TestLibvirtKbsKeyRelease/DoTestKbsKeyReleaseForFailure_test/Kbs_key_release_is_failed
=== NAME  TestLibvirtKbsKeyRelease
    common_suite.go:592: PASS as failed to access key.bin:
=== NAME  TestLibvirtKbsKeyRelease/DoTestKbsKeyReleaseForFailure_test/Kbs_key_release_is_failed
    assessment_runner.go:435: Output when execute test commands:
=== NAME  TestLibvirtKbsKeyRelease/DoTestKbsKeyReleaseForFailure_test
    assessment_runner.go:617: Deleting pod kbs-failure...
    assessment_runner.go:624: Pod kbs-failure has been successfully deleted within 60s
=== NAME  TestLibvirtKbsKeyRelease
    libvirt_test.go:131: KBS normal cases
time="2024-09-26T18:26:52Z" level=info msg="EnableKbsCustomizedPolicy: ../../kbs/sample_policies/allow_all.rego"
time="2024-09-26T18:26:52Z" level=trace msg="./kbs-client --url http://<IP_ADDRESS>:32466 config --auth-private-key ../../kbs/config/kubernetes/base/kbs.key set-attestation-policy --policy-file ../../kbs/sample_policies/allow_all.rego, output: Set attestation policy success \n policy: CnBhY2thZ2UgcG9saWN5CgpkZWZhdWx0IGFsbG93ID0gdHJ1ZQoK\n"
    common_suite.go:549: Do test kbs key release
=== RUN   TestLibvirtKbsKeyRelease/KbsKeyReleasePod_test
    assessment_runner.go:264: Waiting for containers in pod: kbs-key-release are ready
=== RUN   TestLibvirtKbsKeyRelease/KbsKeyReleasePod_test/Kbs_key_release_is_successful
=== NAME  TestLibvirtKbsKeyRelease
    common_suite.go:557: Success to get key.bin: This is my cluster name:
=== NAME  TestLibvirtKbsKeyRelease/KbsKeyReleasePod_test/Kbs_key_release_is_successful
    assessment_runner.go:435: Output when execute test commands: This is my cluster name:
=== NAME  TestLibvirtKbsKeyRelease/KbsKeyReleasePod_test
    assessment_runner.go:617: Deleting pod kbs-key-release...
    assessment_runner.go:624: Pod kbs-key-release has been successfully deleted within 60s
--- PASS: TestLibvirtKbsKeyRelease (214.71s)
    --- PASS: TestLibvirtKbsKeyRelease/DoTestKbsKeyReleaseForFailure_test (109.26s)
        --- PASS: TestLibvirtKbsKeyRelease/DoTestKbsKeyReleaseForFailure_test/Kbs_key_release_is_failed (9.23s)
    --- PASS: TestLibvirtKbsKeyRelease/KbsKeyReleasePod_test (105.26s)
        --- PASS: TestLibvirtKbsKeyRelease/KbsKeyReleasePod_test/Kbs_key_release_is_successful (5.22s)
PASS
ok  	github.com/confidential-containers/cloud-api-adaptor/src/cloud-api-adaptor/test/e2e	2745.866s

On the CI the TestLibvirtPodToServiceCommunication seems to be an issue that breaks the others, so I'll try and skip it to see if we can get a pass


npm build fails, but local use with npm start is OK

I have been using npm start, and there have been no issues.  I tried npm build and got the following:
$ npm run build

<EMAIL_ADDRESS>build C:\d-client
react-scripts build

Creating an optimized production build...
Failed to compile.
Failed to minify the code from this file:
    ./node_modules/zustand/index.js:5

Read more here: http://bit.ly/2tRViJ9
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR<EMAIL_ADDRESS>build: react-scripts build
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the<EMAIL_ADDRESS>build script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
npm ERR! A complete log of this run can be found in:

here is the complete log:
0 info it worked if it ends with ok
1 verbose cli [ 'C:\Program Files\nodejs\node.exe',
1 verbose cli   'C:\Users\e\AppData\Roaming\npm\node_modules\npm\bin\npm-cli.js',
1 verbose cli   'run',
1 verbose cli   'build' ]
2 info using<EMAIL_ADDRESS>3 info using<EMAIL_ADDRESS>4 verbose run-script [ 'prebuild', 'build', 'postbuild' ]
5 info lifecycle<EMAIL_ADDRESS><EMAIL_ADDRESS>6 info lifecycle<EMAIL_ADDRESS><EMAIL_ADDRESS>7 verbose lifecycle<EMAIL_ADDRESS>unsafe-perm in lifecycle true
8 verbose lifecycle<EMAIL_ADDRESS>PATH: C:\Users\e\AppData\Roaming\npm\node_modules\npm\node_modules\npm-lifecycle\node-gyp-bin;C:\d-client\node_modules.bin;C:\Program Files  ........removed..........
9 verbose lifecycle<EMAIL_ADDRESS>CWD: C:\d-client
10 silly lifecycle<EMAIL_ADDRESS>Args: [ '/d /s /c', 'react-scripts build' ]
11 silly lifecycle<EMAIL_ADDRESS>Returned: code: 1  signal: null
12 info lifecycle<EMAIL_ADDRESS>Failed to exec build script
13 verbose stack Error<EMAIL_ADDRESS>build: react-scripts build
13 verbose stack Exit status 1
13 verbose stack     at EventEmitter. (C:\Users\e\AppData\Roaming\npm\node_modules\npm\node_modules\npm-lifecycle\index.js:304:16)
13 verbose stack     at emitTwo (events.js:126:13)
13 verbose stack     at EventEmitter.emit (events.js:214:7)
13 verbose stack     at ChildProcess. (C:\Users\e\AppData\Roaming\npm\node_modules\npm\node_modules\npm-lifecycle\lib\spawn.js:55:14)
13 verbose stack     at emitTwo (events.js:126:13)
13 verbose stack     at ChildProcess.emit (events.js:214:7)
13 verbose stack     at maybeClose (internal/child_process.js:925:16)
13 verbose stack     at Process.ChildProcess._handle.onexit (internal/child_process.js:209:5)
14 verbose pkgid<EMAIL_ADDRESS>15 verbose cwd C:\d-client
16 verbose Windows_NT 10.0.18362
17 verbose argv "C:\Program Files\nodejs\node.exe" "C:\Users\e\AppData\Roaming\npm\node_modules\npm\bin\npm-cli.js" "run" "build"
18 verbose node v8.11.3
19 verbose npm  v6.3.0
20 error code ELIFECYCLE
21 error errno 1
22 error<EMAIL_ADDRESS>build: react-scripts build
22 error Exit status 1
23 error Failed at the<EMAIL_ADDRESS>build script.
23 error This is probably not a problem with npm. There is likely additional logging output above.
24 verbose exit [ 1, true ]

Any idea why this is not building.  I do think the problem is with zustrand, as run build was working before adding this.

found solution.  needed to update my npm react-scripts package to greater than 2.x.x.  This fixed the problem


[Event Request] Report 12115 "Calculate End Year Costs" - Function "InitPurchFields" - New Event OnBeforeInitPurchFields

Hello, we need the possibility to extend the Function "InitPurchFields" on "Calculate End Year Costs" Report (12115) as follows:
    procedure InitPurchFields()

    //new-s
    var
        IsHandled: Boolean;
    //new-e

    begin

        //new-s
        IsHandled := false;
        OnBeforeInitPurchFields(ItemCostHistory, IsHandled);
        if IsHandled then
            exit;
        //new-e

        GetBefStartItemQtyAndCost(ItemCostHistory."Purchase Quantity", ItemCostHistory."Purchase Amount");
        SetItemLedgerEntryFilters(ItemLedgEntry, StartingDate, ReferenceDate, '%1', ItemLedgEntry."Entry Type"::Purchase);
        if ItemLedgEntry.FindSet() then
            repeat
                ItemLedgEntry.CalcFields("Purchase Amount (Expected)", "Purchase Amount (Actual)");
                ItemCostHistory."Purchase Amount" += ItemLedgEntry."Purchase Amount (Actual)" + ItemLedgEntry."Purchase Amount (Expected)";
                ItemCostHistory."Purchase Quantity" += ItemLedgEntry.Quantity;
            until ItemLedgEntry.Next() = 0;
    end;

    [IntegrationEvent(false, false)]
    local procedure OnBeforeInitPurchFields(var ItemCostHistory: Record "Item Cost History"; var IsHandled: Boolean)
    begin
    end;

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


feature request: formula for ODBC package

Thanks for this helpful tap. Has there been any consideration of adding the Instant Client ODBC package? I routinely connect to Oracle Database via ODBC, so this would be very helpful.

The contents of the ODBC package can be separated into three parts:

the ODBC driver: libsqora.dylib.12.1
a setup script: odbc_update_ini.sh
help files

The ODBC driver is the essential component required to configure an ODBC connection to Oracle Database, e.g., using unixODBC. The setup script creates two files:

the ODBC driver configuration file odbcinst.ini, which by default goes into /usr/local/etc
the data source configuration file odbc.ini, which by default goes into ~ (as .odbc.ini)

The key thing is to install the ODBC driver libsqora.dylib.12.1, presumably into /usr/local/Cellar/instantclient-odbc, and then symlink it into /usr/local/lib. There are issues with the setup script, so I would propose not installing/running it at all, and requiring that the user configure odbcinst.ini and odbc.ini.
So, essentially, the only thing that the formula would need to do is copy libsqora.dylib.12.1 from the zip file into the appropriate location in /usr/local/Cellar, and then symlink it into /usr/local/lib. The user would then need to set up the ODBC driver and data sources on their own.
Does this make sense? I've never written any Ruby, but I can try to adapt an existing formula for a PR if helpful.

Thank you for all this information! Unfortunately, I don't have time for this right now. But if you could prepare a PR mimicking the other formulas I would consider merging it.


Fix #33282 - don't use entire queries as columns in GROUP BY

When upgrading LAVA (https://lavasoftware.org/) to Django 3.2, I found
some exceptions like this:
django.db.utils.ProgrammingError: more than one row returned by a
subquery used as an expression
I bisected those to commit<PHONE_NUMBER>6165986ad07e91f9d3aca721ff38ec
("Refs #27149 -- Moved subquery expression resolving to Query"). In it,
Query as made a subclass of BaseExpression.
BaseExpression.get_group_by_cols() depends no the value of
contains_aggregate, which is set to False by default. However, when
the RHS is a subquery, it does not make sense to add it to GROUP BY.
Unfortunately I could not produce an unit test that could reproduce this
issue, and can only trigger it on the LAVA codebase. This change both
fixes it for me and does not cause any of the existing unit tests to
fail.

Closing per comment.


[release-2.4] updated slo recording rule metric label filter

Related Issue: https://github.com/open-cluster-management/backlog/issues/17736
Signed-off-by: dislbenn<EMAIL_ADDRESS>

/retest

/test test-e2e

/test test-e2e

/test test-e2e

/lgtm


Animation disappear when switching app from background to foreground

Hi,
First thank you for the great work on this nice component.
I have noticed when switching from background to foreground, the pulse animation disappear.
This is reproducible in the example app too.

Same here.

I'm sorry, I'll fix soon.


[SPARKTA-423][WEB]: Add slider to policy wizard in order to hide the policy step navigation bar

LGTM


Ocean color - download issue

Notebook description
Hi Mattia,
I need to modify the template you've shared (https://github.com/bopen/c3s-eqc-toolbox-template/blob/main/notebooks/wp5/ocean_color.ipynb) to download 5 different variables at different latitude slices.
But, as already happened before, the kernel stops working as I modify the request, likely because of their size.
I kept using your template by changing each variable name at a time (and latitude ranges), but I was wondering if it's possibile to create a template to download all 5 variables at once.
Could you please help?
Notebook link or upload
No response
Anything else we need to know?
No response
Environment

Which variables do you need to download?

I only see 2 variable options in the CDS form: https://cds.climate.copernicus.eu/cdsapp#!/dataset/satellite-ocean-colour?tab=form

All you need is to re-run the whole notebook using that slices?

It took forever, but it worked out.

It took forever

The running time should be a linear function of the number of months processed, which is in line with the code design. The dataset you are processing is quite big and the VM has limited resources. It takes some time, but it's stable and it's a one-time computation because of the cache.

but it worked out.

Great. (We've been running the same code simultaneously. As I mentioned yesterday, I was running the notebook overnight to cache the new diagnostics requested yesterday).
Here is the latest template, where lat0/lat1 are now in the parameters section: https://github.com/bopen/c3s-eqc-toolbox-template/blob/main/notebooks/wp5/ocean_color.ipynb

@chiaravol,
You need me to generalise this notebook to include reflectance variables, right?
Masking should only be applied to chl data, correct?
Anything else?

Looks like you need different regions for Rrs: https://github.com/bopen/c3s-eqc-toolbox-template/issues/92#issuecomment-1671605866

We can use the same regions as in the ocean color map template. But, again, I might need to run it over different regions.

In this case the region does affect the cache and it's not for plotting purposes only (we are caching spatial averages).
So you'll have to ask us to populate the cache if you'll need different regions.

ok,I will :)

Hi Mattia, Could you also add and cache the region lat (50, -50) and long(180, -180).
Thank you in advance!

On it!

Done. chlor_a, Rrs_443, Rrs_560 are cached.
Here is the latest template: https://github.com/bopen/c3s-eqc-toolbox-template/blob/main/notebooks/wp5/ocean_color_timeseries.ipynb

What do you mean? I added the link to the notebook in my last comment: https://github.com/bopen/c3s-eqc-toolbox-template/blob/main/notebooks/wp5/ocean_color_timeseries.ipynb

Following the link, I cannot run that notebook

I'm not sure I understand.
As always, that's the link to the template stored on GitHub. And as usual, you need to download it to the VM to run it.

Oh..sorry...my bad.
Just another thing...I guess we have forgotten to not account for chl>100 and chl<0.001 in the maps template.
I've added a line for that, but you want maybe verify and modify the public template


Checkpoints to run demo and dataset

Great work, is it possible for me to know when will the checkpoints to run the demo locally and complete datasets be released?

Hi, thanks for your interest.
We have now released TimeChat-7b checkpoint and local demo. Feel free to contact us if there are any problems.


How to use this extension for python2 project

I have some projects still use python2 for historic reasons，but this extension not support python2 interpreter, how to solve it

@Aya-Yang Try this and let me know.

Set pylint.interpreter to python3 : "pylint.interpreter": ["/usr/bin/python3"]
Set pylint.path to pylint from python2 environment: "pylint.path": ["<path-to-pylint-binary"]


New CI image

polkadot companion: https://github.com/paritytech/polkadot/pull/1194

@TriplEight can this really be merged?

@gavofyork yes, right after https://gitlab.parity.io/parity/infrastructure/scripts/-/jobs/545541 is successful.
The new paritytech/ci-linux:staging image is being tested with test-linux-stable and check-web-wasm tests before being published as paritytech/ci-linux:staging which will be used in Substrate's CI.

bot merge


tor-browser-bundle-bin: 11.5.2 -> 11.5.4

Description of changes
Security and bugfix update: https://blog.torproject.org/new-release-tor-browser-1154/

Tor Browser 11.5.4 backports the following security updates from Firefox ESR 102.3 to to Firefox ESR 91.13 on Windows, macOS and Linux:

CVE-2022-40959
CVE-2022-40960
CVE-2022-40958
CVE-2022-40956
CVE-2022-40962

In addition, I add a mirror for old TBB release files. This may be preferable to #191492.
Things done

Built on platform(s)

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

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

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

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

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module
[ ] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[X] Fits CONTRIBUTING.md.

Pings
@FliegendeWurst @lourkeur

Result of nixpkgs-review run on x86_64-linux 1

1 package built:

tor-browser-bundle-bin

Maybe it would still be good to hear @SuperSandro2000's opinion on the fallback URL.

I moved archive.torproject.org up as second mirror and kept the non-torproject.org mirrors as fallback, as you had discussed. Thanks for the feedback!
Please check again if this is ok now.


data persistance

Which folders do I need to put in a volume, if I want to safe the data in the server between rebuilds or updates?

According to the installation guide, you should make sure to preserve  the file .htconfig.php located at the root of the installation directory.


[RAFT] Directly decrease pr.next when receive rejection from follower

ASK FOR HELP
My Confusion
when leader receives rejection from follower, leader should  decrease corresponding progress.next.
I think when in ProgressStateReplicate, we should set pr.Next = pr.last + 1.  I don't know the reason why we set pr.Next = pr.Match + 1 instead.
Message.RejectHint indicates largest index the follower has. So RejectHint+1 is exactly what follower expects.
https://github.com/coreos/etcd/blob/master/raft/progress.go#L139
func (pr *Progress) maybeDecrTo(rejected, last uint64) bool {
	if pr.State == ProgressStateReplicate {
		// the rejection must be stale if the progress has matched and "rejected"
		// is smaller than "match".
		if rejected <= pr.Match {
			return false
		}
		// directly decrease next to match + 1
		pr.Next = pr.Match + 1
		return true
	}

	// the rejection must be stale if "rejected" does not match next - 1
	if pr.Next-1 != rejected {
		return false
	}

	if pr.Next = min(rejected, last+1); pr.Next < 1 {
		pr.Next = 1
	}
	pr.resume()
	return true
}

pr.Next = pr.last + 1

what is pr.last?

Sorry for mistake.
pr.Next=last  + 1
that is to say:
pr.Next= RejectHint + 1

@shenlanse We probably could do that. I do not really remember the reason for decreasing it directly to match. probably it is because rejected is not even introduced at that time. you might want to figure it out by looking through git history. i will give it more thoughts too.

@xiang90  all  right, thanks

I think maybe because:
RejectHint is the last index of follower, but the corresponding term of the last entry might is not same with current leader.
If we set pr.Next=RejectHint + 1, then when leader send messages again to this follower according to progress, matchTerm might return false, so follower will reject again with same last index.
But if we set pr.Next=pr.Match +1, follower will accept it (matchTerm return true) definitely.
If what i said above is right, then we can optimize the algo. when follower rejects the entry, it will not only return RejectHint but also return term of last entry. So when leader get this response, it can make a decision:
(1) set pr.Next=last + 1
(2) set pr.Next=pr.Match + 1

@xiang90  What i want to express is that pr.match+1~last entry of follower might is different from current leader. That is to say, pr.match+1~last entry of follower might contain garbage entrys.


Add Managed Identity retry logic

Implements retry logic for MI scenarios, as per https://github.com/AzureAD/microsoft-authentication-library-for-java/issues/690
The main changes are:

Refactor HttpHelper to not have static methods, and it now extends a new IHttpHelper interface
Add new HttpHelperManagedIdentity class that extends HttpHelper and implements MI-specific HTTP behavior (currently just the retry logic)
Refactor ServiceBundle to take IHttpHelper as a parameter, so that the now non-static methods in HttpHelper can still be accessed

Issue https://github.com/AzureAD/microsoft-authentication-library-for-java/issues/690 also mentioned adding a way to disable this MI retry logic. Since MSAL Java doesn't have an API to disable the normal retry logic, there will be a different PR for the main library to add it

I would recommend adding unit tests that verify retry / not based on the returned status codes.


[Documentation/Feature] Enable only to certain languages

I only want to enable this plugin for clojure, because I find the colours to be distracting in non-lisp languages.
Is there a way to do so?
P.S: Which is the colorscheme used on the latter screenshots, and which colours for the rainbows is it using?

i added a link to the instructions to README.md


getWidgetDiagnostics method can't working ?

this my example (python)

getWidgetDiagnostics is not support ?

It is not released yet. I'll do it tonight.

v 2.8.0 should have the command.


[SPARK-32704][SQL][TESTS] Check any physical rule instead of a specific rule in the test

What changes were proposed in this pull request?
This PR only checks if there's any physical rule runs instead of a specific rule. This is rather just a trivial fix to make the tests more robust.
In fact, I faced a test failure from a in-house fork that applies a different physical rule that makes CollapseCodegenStages ineffective.
Why are the changes needed?
To make the test more robust by unrelated changes.
Does this PR introduce any user-facing change?
No, test-only
How was this patch tested?
Manually tested. Jenkins tests should pass.

@maropu, would you mind taking a look please?

Test build #128730 has started for PR 29766 at commit 80ac7d2.

Merged build finished. Test PASSed.

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

Thanks for the fix! LGTM.

Merged to master.
Thank you @maropu!

Test build #128730 has finished for PR 29766 at commit 80ac7d2.

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

Merged build finished. Test PASSed.

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


HDH-201 migrate-videos-from-iframe-to-doc-video-component

Harness Developer Pull Request
Thanks for helping us make the Developer Hub better. The PR will be looked at
by the CODEOWNERS.
What Type of PR is This?

[ ] Issue
[ ] Feature
[x] Maintenance/Chore

If tied to an Issue, list the Issue(s) here:

Issue(s)

House Keeping
Some items to keep track of. Screen shots of changes are optional but would help the maintainers review quicker.

[x] Tested Locally
[ ] Optional Screen Shoot.

Please check the Execution Link of the Pipeline for the Website Draft URL. This is located in the Preview Step behind the Harness VPN and also is available in #hdh_alerts. E.g Website Draft URL: https://unique-id--harness-developer.netlify.app. Current Draft URL is: https://6562e4846234c43b92e42308--harness-developer.netlify.app

Please check the Execution Link of the Pipeline for the Website Draft URL. This is located in the Preview Step behind the Harness VPN and also is available in #hdh_alerts. E.g Website Draft URL: https://unique-id--harness-developer.netlify.app. Current Draft URL is: https://6564ba2a3cb158007c9726d5--harness-developer.netlify.app

Please check the Execution Link of the Pipeline for the Website Draft URL. This is located in the Preview Step behind the Harness VPN and also is available in #hdh_alerts. E.g Website Draft URL: https://unique-id--harness-developer.netlify.app. Current Draft URL is: https://6564ba7f0e765b0665cf9c54--harness-developer.netlify.app

Approved wrt CI topics, but I still see Wistia links in other areas.

@rohanmaharjan100 I think we can close this, we took forward in other PRs. Thanks!

Yeah..lets close it.


Added link to publickey and telegram, small bugfix regarding siteurl

@de-live-gdev
Thanks for your PR!
I wonder what "publickey" means :cold_sweat: Could you tell me?
BTW, bugfix part is going to be cared on #11, so could you please remove it from this PR?
thanks.

publickey is meant for a page or a link to OpenPGP key.
Will be removed those days


Detect the new products in the SDK and Viewer: D435f, D435if, D455f, D456

Tracked on [LRS-657]

We need to search all of the old device names, see if someone is the code used the specific camera name to add some logic.
If so we need to add the new name as well
C++ and python wrapper

We need to search all of the old device names, see if someone is the code used the specific camera name to add some logic. If so we need to add the new name as well C++ and python wrapper

Meanwhile, I didn't find any used device by name only using a device by a pid.
I will look for it later.

Please rebase and solve conflicts
This branch has conflicts that must be resolved

I don't see the new changes, please push


V4.0 pcb usability for 3x5

If I understand the fixes from 4.0 to 4.1 correctly, I should refrain from shortening my 4.0 pcbs to 3x5? Will this inevitably render the pcb functionless, or is there a workaround?

Please do not use 3x5 in v4.0, the PCB will be unusable. There is no workaround.

Ok, thank you for the quick clarification!


Cannot access PowerToys or Settings menu

Environment
Windows build number: Version 10.0.18362.836
PowerToys version:  0.18.0
PowerToy module for which you are reporting the bug (if applicable):

Steps to reproduce
Install PowerToys 0.18.0 via the preferred .msi method on updated Windows 10 machine, attempt to run.
Expected behavior
PowerToys should be available post-install, following the dependency install included after the initial install.
Actual behavior
Tray icon appears, but there is no access to any windows, menus, functions or features. The program is visibly running in the background as a 7MB process, but provides no activity when attempting to call forward any menu or window. Thus, I have no capability to utilize any of the PowerToys functions.

I had the same issue. I tried running a repair and it didn't work, so tried rebooting and it still didn't work. So I uninstalled it and re-installed it and this time the installer invoked a separate installer that I don't remember the name of (something with Desktop in the name, which I think on the first install was blocked by my firewall because I even have outgoing blocked by default). This time it installed fine, and it seemed to work, but settings wouldn't show up. I exited out and ran as administrator, then settings worked fine.

I had the same issue. I tried running a repair and it didn't work, so tried rebooting and it still didn't work. So I uninstalled it and re-installed it and this time the installer invoked a separate installer that I don't remember the name of (something with Desktop in the name, which I think on the first install was blocked by my firewall because I even have outgoing blocked by default). This time it installed fine, and it seemed to work, but settings wouldn't show up. I exited out and ran as administrator, then settings worked fine.

I reinstalled several times, but have not seen another installer pop up after the PowerToys one except the very first time I installed, which was to install a specific dependency (.net?). The program still opens and runs in the background, now informing me that it failed to assign the hotkey Alt + Space. Attempting to access the program or the settings menu still results in nothing launching, so I am still unfortunately effectively locked out of PowerToys.

Hi @ListeningGarden
the installer should have installed the .NET Core 3.1 Desktop Runtime, you can installed it manually https://dotnet.microsoft.com/download/dotnet-core/thank-you/runtime-desktop-3.1.4-windows-x64-installer and verify if that fixes the problem.
Thanks.

Hi @ListeningGarden
the installer should have installed the .NET Core 3.1 Desktop Runtime, you can installed it manually https://dotnet.microsoft.com/download/dotnet-core/thank-you/runtime-desktop-3.1.4-windows-x64-installer and verify if that fixes the problem.
Thanks.

enricogior,
This was installed on my first attempt to install and run PowerToys. I have uninstalled and reinstalled using the individual module provided. However, PowerToys still refuses to show any windows including the settings window, so I am still unable to use any functionality of the program.

Some further information, since I totally blanked on checking Event Viewer before:
Faulting application name: PowerLauncher.exe, version: <IP_ADDRESS>, time stamp: 0x5e222541
Faulting module name: d3d9.dll, version: 10.0.18362.387, time stamp: 0xc808fce5
Exception code: 0xc0000005
Fault offset: 0x00000000000ac44e
Faulting process id: 0x644
Faulting application start time: 0x01d62e3b9a7ce14a
Faulting application path: C:\Program Files\PowerToys\modules\launcher\PowerLauncher.exe
Faulting module path: C:\WINDOWS\SYSTEM32\d3d9.dll
Report Id: 5542d4d5-1598-49f9-87ea-ca864d9b9305
Faulting package full name:
Faulting package-relative application ID:

Fault bucket<PHONE_NUMBER>798010219, type 4
Event Name: APPCRASH
Response: Not available
Cab Id: 0

Problem signature:
P1: PowerLauncher.exe
P2: <IP_ADDRESS>
P3: 5e222541
P4: d3d9.dll
P5: 10.0.18362.387
P6: c808fce5
P7: c0000005
P8:<PHONE_NUMBER>0ac44e
P9:
P10:

Attached files:
*local paths*

These files may be available here:
*local path*

Analysis symbol:
Rechecking for solution: 0
Report Id: 5542d4d5-1598-49f9-87ea-ca864d9b9305
Report Status: 268435456
Hashed bucket: 653fdd297d8cfde7dda406946ad94d6b
Cab Guid: 0

Since the update, the settings dialog opens but it does not render correctly anymore, check the attached GIF.
The menu items appear briefly but disappear on focus / refresh.

Since the update, the settings dialog opens but it does not render correctly anymore, check the attached GIF.
The menu items appear briefly but disappear on focus / refresh.

This is a different issue altogether, see the last few posts on #243 for latest developments - if there's no new open issue for what you're experiencing please open one so as to not pull focus on the issue I've reported. Thank you!

I had similar issues. I couldn't get the settings window to open, and I kept being told I needed to install .NET Core, despite having done so. I tried repairing the installs for both .NET Core and Powertoys. I also individually removed and reinstalled both Powertoys and .NET Core.
When I removed Powertoys, then .NET Core, and then installed Powertoys, allowing the process to also install .NET Core, I now have full functionality again.

In my case, it was blocked through RivaTuner (MSI Afterburner). Maybe this information helps other people with this problem.

with 0.20, is this still an issue?

Updated to 0.20.1, and reactivated RTSS detection for both PowerToys.exe and PowerToysSettings.exe. The program still crashes as it had before. Removing RTSS detection of those two allows access as expected. I would consider this still an issue until the conflict between the two that causes the crash is resolved.

@ListeningGarden just so everyone is 100% on same page, rtss is the rivatuner, correct?

@crutkas RTSS is related to RivaTuner but is actively developed and has different functions. Some people use the terms interchangeably even though they are two distinct programs. It's a bit confusing, sorry! To make sure we're looking at the same thing, RTSS can be found here.

@ryanbodrug-microsoft / @enricogior unsure which area is crashing but this should be investigated

@ListeningGarden can you share a screenshot of the RTSS profile which causes the crash? I installed RTSS and ran it and I was still able to run PowerToys. I'm not to familiar with RTSS so a screenshot of the exact configuration could help. I change the app detection level but it still worked fine with everything else as default.

I've updated PowerToys to 0.23.2 and am now unable to replicate the bug. After testing, all tools appear to function and the settings app launches when requested, even with RTSS forced to use high detection on the various exes. I'm not entirely sure why, so feel free to ask if you have something under the hood you need me to peek at so we know where it was going wrong and why it isn't now. Otherwise, we might be able to close this one?


Rename SetDutyCycle::get_max_duty_cycle

The get_ prefix is discouraged as per the Rust API Guidelines, the method should be named max_duty_cycle.

LGTM, can you send a PR?


Go to File does not find files in directory junctions

If you have a parent folder with two directory junctions pointing somewhere else, "Go to File" ( or Ctrl+P ) will not be able to find the file you are looking for. However, if you put one of the directory junctions as your workspace folder "Go to File" will be able to find any existing file in the folder with no problem.
My current setup has two folders in two complete different locations and to edit them I have two junctions inside a folder with .git and .vscode. There doesn't seem to be an issue with other editors like Sublime Text 3

Forgot to mention: Before January update this was working just fine (albeit really slowly)

@NullScope is this on Windows or OSX? Can you provide steps how you setup the junctions?

@bpasero This is on Windows.
Here are the steps to reproduce the bug:

Create one folder called FolderTest ( e.g C:/FolderTest )
Create two child folders called FolderOne and FolderTwo ( e.g C:/FolderTest/FolderOne & C:/FolderTest/FolderTwo )
Fill both folders with random files ( e.g C:/FolderTest/FolderOne/random.txt )
Create one folder somewhere else called JunctionFolder ( e.g Documents/JunctionFolder )
Use mklink in cmd with administrative rights and create two junctions inside the folder

In my case the commands were:
mklink /D "D:\Users\Bruno Ribeiro\Documents\JunctionFolder\FolderOne" "C:\FolderTest\FolderOne"
mklink /D "D:\Users\Bruno Ribeiro\Documents\JunctionFolder\FolderTwo" "C:\FolderTest\FolderTwo"

Now open a brand new window in Visual Studio Code without any project folders
Drag-in JunctionFolder into Visual Studio Code

Now try to open a random file inside FolderOne using "Go to File" ( or Ctrl+P ) and Visual Code Studio will say there were no results found, however the sidemenu can navigate the files just fine.

Now open again a brand new window
Drag-in JunctionFolder/FolderOne

Doing the exact same search using "Go to File" ( or Ctrl+P ) and Visual Code Studio will be able to find the file instantly.
My project is much more complicated than this obviously as it works under an framework with a lot more child folders. But for git it has to be setup as the two top folders while my project is sitting as one of the many child folders inside those two folders.

@NullScope excellent steps for me to verify. the issue is that since January release, quick open and full text search fail to work over links pointing to directories.
@alexandrudima please verify on windows and mac/linux

@bpasero Thank you! Glad to hear you are able to fix this issue!

Verified search and ctrl+p in windows and linux.
@bpasero If the code is different for mac than for linux, please also assign another person for verification.

Should be good, thanks!


Todo before publication

Todo list:

[x] Migrate the project to: https://github.com/edbiomedai/targene-paper
[ ] Update README.md
[ ] Check the sieve variance once it is rerun

FTO:

[x] Rerun FTO with weighted fluctuation
[x] Rerun FTO analyses to check if anything changed
[ ] Run FTO negative controls permutation tests
[ ] Update README.md

Hair color:

[x] Rerun hair/skin colour with weighted fluctuation
[x] Add hair color to the run since this is the original reproducibility attempt
[x] Rerun skin colour analyses to check if anything changed
[ ] Investigate failed TMLEs (missing results and a failed Process)
[ ] Potentially run negative controls permutation tests
[ ] Update README.md

VDR:

[x] Rerun VDR with weighted fluctuation
[x] Rerun VDR analyses to check if anything changed
[ ] Potentially run negative controls permutation tests
[ ] Update README.md

Environmental Interaction:

[x] Ask Josh for the setup
[x] Run
[ ] Update README.md

[ ] Update non-linearity plot.
[ ] Compute the number of time we cover the gene ATLAS (continuous) or Neale v2.