/Users/nikola/src/giantswarm/cluster-test-suites/internal/common/apps.go:46
  {"level":"info","ts":"2023-11-29T15:29:36+01:00","msg":"Checking if App status for t-amqxana-observability-bundle is equal to 'deployed': deployed"}
  {"level":"info","ts":"2023-11-29T15:29:36+01:00","msg":"Checking if App status for t-amqxana-prometheus-agent is equal to 'deployed': deployed"}
  {"level":"info","ts":"2023-11-29T15:29:36+01:00","msg":"Checking if App status for t-amqxana-prometheus-operator-app is equal to 'deployed': deployed"}
  {"level":"info","ts":"2023-11-29T15:29:37+01:00","msg":"Checking if App status for t-amqxana-prometheus-operator-crd is equal to 'deployed': deployed"}
• [0.551 seconds]
------------------------------
Common tests basic should be able to connect to MC cluster
/Users/nikola/src/giantswarm/cluster-test-suites/internal/common/basic.go:35
• [0.167 seconds]
------------------------------
Common tests basic should be able to connect to WC cluster
/Users/nikola/src/giantswarm/cluster-test-suites/internal/common/basic.go:39
• [0.230 seconds]
------------------------------
Common tests basic has all the control-plane nodes running
/Users/nikola/src/giantswarm/cluster-test-suites/internal/common/basic.go:43
  {"level":"info","ts":"2023-11-29T15:29:42+01:00","msg":"Checking for ready nodes"}
  {"level":"info","ts":"2023-11-29T15:29:42+01:00","msg":"3 nodes ready, expecting 3"}
  {"level":"info","ts":"2023-11-29T15:29:47+01:00","msg":"Checking for ready nodes"}
  {"level":"info","ts":"2023-11-29T15:29:47+01:00","msg":"3 nodes ready, expecting 3"}
  {"level":"info","ts":"2023-11-29T15:29:52+01:00","msg":"Checking for ready nodes"}
  {"level":"info","ts":"2023-11-29T15:29:52+01:00","msg":"3 nodes ready, expecting 3"}
  {"level":"info","ts":"2023-11-29T15:29:57+01:00","msg":"Checking for ready nodes"}
  {"level":"info","ts":"2023-11-29T15:29:57+01:00","msg":"3 nodes ready, expecting 3"}
  {"level":"info","ts":"2023-11-29T15:30:02+01:00","msg":"Checking for ready nodes"}
  {"level":"info","ts":"2023-11-29T15:30:02+01:00","msg":"3 nodes ready, expecting 3"}
  {"level":"info","ts":"2023-11-29T15:30:07+01:00","msg":"Checking for ready nodes"}
  {"level":"info","ts":"2023-11-29T15:30:07+01:00","msg":"3 nodes ready, expecting 3"}
  {"level":"info","ts":"2023-11-29T15:30:12+01:00","msg":"Checking for ready nodes"}
  {"level":"info","ts":"2023-11-29T15:30:12+01:00","msg":"3 nodes ready, expecting 3"}
  {"level":"info","ts":"2023-11-29T15:30:17+01:00","msg":"Checking for ready nodes"}
  {"level":"info","ts":"2023-11-29T15:30:17+01:00","msg":"3 nodes ready, expecting 3"}
  {"level":"info","ts":"2023-11-29T15:30:22+01:00","msg":"Checking for ready nodes"}
  {"level":"info","ts":"2023-11-29T15:30:22+01:00","msg":"3 nodes ready, expecting 3"}
  {"level":"info","ts":"2023-11-29T15:30:27+01:00","msg":"Checking for ready nodes"}
  {"level":"info","ts":"2023-11-29T15:30:27+01:00","msg":"3 nodes ready, expecting 3"}
  {"level":"info","ts":"2023-11-29T15:30:32+01:00","msg":"Checking for ready nodes"}
  {"level":"info","ts":"2023-11-29T15:30:32+01:00","msg":"3 nodes ready, expecting 3"}
  {"level":"info","ts":"2023-11-29T15:30:37+01:00","msg":"Checking for ready nodes"}
  {"level":"info","ts":"2023-11-29T15:30:37+01:00","msg":"3 nodes ready, expecting 3"}
• [65.135 seconds]
------------------------------
Common tests basic has all the worker nodes running
/Users/nikola/src/giantswarm/cluster-test-suites/internal/common/basic.go:61
  {"level":"info","ts":"2023-11-29T15:30:47+01:00","msg":"Checking for ready nodes"}
  {"level":"info","ts":"2023-11-29T15:30:48+01:00","msg":"1 nodes ready, expecting between 1 and 2"}
  {"level":"info","ts":"2023-11-29T15:30:52+01:00","msg":"Checking for ready nodes"}
  {"level":"info","ts":"2023-11-29T15:30:53+01:00","msg":"1 nodes ready, expecting between 1 and 2"}
  {"level":"info","ts":"2023-11-29T15:30:57+01:00","msg":"Checking for ready nodes"}
  {"level":"info","ts":"2023-11-29T15:30:58+01:00","msg":"1 nodes ready, expecting between 1 and 2"}
  {"level":"info","ts":"2023-11-29T15:31:02+01:00","msg":"Checking for ready nodes"}
  {"level":"info","ts":"2023-11-29T15:31:03+01:00","msg":"1 nodes ready, expecting between 1 and 2"}
  {"level":"info","ts":"2023-11-29T15:31:07+01:00","msg":"Checking for ready nodes"}
  {"level":"info","ts":"2023-11-29T15:31:08+01:00","msg":"1 nodes ready, expecting between 1 and 2"}
  {"level":"info","ts":"2023-11-29T15:31:12+01:00","msg":"Checking for ready nodes"}
  {"level":"info","ts":"2023-11-29T15:31:13+01:00","msg":"1 nodes ready, expecting between 1 and 2"}
  {"level":"info","ts":"2023-11-29T15:31:17+01:00","msg":"Checking for ready nodes"}
  {"level":"info","ts":"2023-11-29T15:31:18+01:00","msg":"1 nodes ready, expecting between 1 and 2"}
  {"level":"info","ts":"2023-11-29T15:31:22+01:00","msg":"Checking for ready nodes"}
  {"level":"info","ts":"2023-11-29T15:31:23+01:00","msg":"1 nodes ready, expecting between 1 and 2"}
  {"level":"info","ts":"2023-11-29T15:31:27+01:00","msg":"Checking for ready nodes"}
  {"level":"info","ts":"2023-11-29T15:31:28+01:00","msg":"1 nodes ready, expecting between 1 and 2"}
  {"level":"info","ts":"2023-11-29T15:31:32+01:00","msg":"Checking for ready nodes"}
  {"level":"info","ts":"2023-11-29T15:31:33+01:00","msg":"1 nodes ready, expecting between 1 and 2"}
  {"level":"info","ts":"2023-11-29T15:31:37+01:00","msg":"Checking for ready nodes"}
  {"level":"info","ts":"2023-11-29T15:31:38+01:00","msg":"1 nodes ready, expecting between 1 and 2"}
  {"level":"info","ts":"2023-11-29T15:31:42+01:00","msg":"Checking for ready nodes"}
  {"level":"info","ts":"2023-11-29T15:31:43+01:00","msg":"1 nodes ready, expecting between 1 and 2"}
• [65.391 seconds]
------------------------------
Common tests basic has all of it's Pods in the Running state
/Users/nikola/src/giantswarm/cluster-test-suites/internal/common/basic.go:87
  {"level":"info","ts":"2023-11-29T15:31:49+01:00","msg":"All (67) pods currently in a running or completed state"}
  {"level":"info","ts":"2023-11-29T15:31:50+01:00","msg":"All (67) pods currently in a running or completed state"}
  {"level":"info","ts":"2023-11-29T15:31:51+01:00","msg":"All (67) pods currently in a running or completed state"}
  {"level":"info","ts":"2023-11-29T15:31:52+01:00","msg":"All (67) pods currently in a running or completed state"}
  {"level":"info","ts":"2023-11-29T15:31:53+01:00","msg":"All (67) pods currently in a running or completed state"}
  {"level":"info","ts":"2023-11-29T15:31:54+01:00","msg":"All (67) pods currently in a running or completed state"}
  {"level":"info","ts":"2023-11-29T15:31:55+01:00","msg":"All (67) pods currently in a running or completed state"}
  {"level":"info","ts":"2023-11-29T15:31:56+01:00","msg":"All (67) pods currently in a running or completed state"}
  {"level":"info","ts":"2023-11-29T15:31:57+01:00","msg":"All (67) pods currently in a running or completed state"}
  {"level":"info","ts":"2023-11-29T15:31:58+01:00","msg":"All (67) pods currently in a running or completed state"}
• [11.001 seconds]
------------------------------
Common tests cert-manager ClusterIssuers cert-manager default ClusterIssuers are present and ready
/Users/nikola/src/giantswarm/cluster-test-suites/internal/common/certmanager.go:34
  {"level":"info","ts":"2023-11-29T15:31:58+01:00","msg":"Checking ClusterIssuer 'selfsigned-giantswarm'"}
  {"level":"info","ts":"2023-11-29T15:31:59+01:00","msg":"ClusterIssuer 'selfsigned-giantswarm' is present"}
  {"level":"info","ts":"2023-11-29T15:31:59+01:00","msg":"Found status.condition with type 'Ready' and status 'True' in ClusterIssuer 'selfsigned-giantswarm'"}
  {"level":"info","ts":"2023-11-29T15:31:59+01:00","msg":"Checking ClusterIssuer 'letsencrypt-giantswarm'"}
  {"level":"info","ts":"2023-11-29T15:31:59+01:00","msg":"ClusterIssuer 'letsencrypt-giantswarm' is present"}
  {"level":"info","ts":"2023-11-29T15:31:59+01:00","msg":"Found status.condition with type 'Ready' and status 'True' in ClusterIssuer 'letsencrypt-giantswarm'"}
• [0.319 seconds]
------------------------------
Common tests dns sets up the api DNS records
/Users/nikola/src/giantswarm/cluster-test-suites/internal/common/dns.go:53
  {"level":"info","ts":"2023-11-29T15:31:59+01:00","msg":"resolved domain api.t-amqxana.gaws.gigantic.io to [<IP_ADDRESS> <IP_ADDRESS> <IP_ADDRESS>]"}
• [0.425 seconds]
------------------------------
Common tests dns sets up the bastion DNS records
/Users/nikola/src/giantswarm/cluster-test-suites/internal/common/dns.go:67
  {"level":"info","ts":"2023-11-29T15:31:59+01:00","msg":"resolved domain bastion1.t-amqxana.gaws.gigantic.io to [<IP_ADDRESS>]"}
• [0.253 seconds]
------------------------------
Common tests hello world hello world app responds successfully
/Users/nikola/src/giantswarm/cluster-test-suites/internal/common/hello.go:125
  {"level":"info","ts":"2023-11-29T15:32:00+01:00","msg":"Checking if App status for t-amqxana-cert-manager is equal to 'deployed': deployed"}
  {"level":"info","ts":"2023-11-29T15:32:00+01:00","msg":"Checking if App status for t-amqxana-external-dns is equal to 'deployed': deployed"}
  {"level":"info","ts":"2023-11-29T15:32:01+01:00","msg":"Checking if App status for t-amqxana-ingress-nginx is equal to 'deployed': "}
  {"level":"info","ts":"2023-11-29T15:32:06+01:00","msg":"Checking if App status for t-amqxana-ingress-nginx is equal to 'deployed': "}
  {"level":"info","ts":"2023-11-29T15:32:11+01:00","msg":"Checking if App status for t-amqxana-ingress-nginx is equal to 'deployed': "}
  {"level":"info","ts":"2023-11-29T15:32:16+01:00","msg":"Checking if App status for t-amqxana-ingress-nginx is equal to 'deployed': deployed"}
  {"level":"info","ts":"2023-11-29T15:32:17+01:00","msg":"Checking if App status for t-amqxana-hello-world is equal to 'deployed': "}
  {"level":"info","ts":"2023-11-29T15:32:22+01:00","msg":"Checking if App status for t-amqxana-hello-world is equal to 'deployed': failed"}
  {"level":"info","ts":"2023-11-29T15:32:27+01:00","msg":"Checking if App status for t-amqxana-hello-world is equal to 'deployed': failed"}
  {"level":"info","ts":"2023-11-29T15:32:33+01:00","msg":"Checking if App status for t-amqxana-hello-world is equal to 'deployed': failed"}
  {"level":"info","ts":"2023-11-29T15:32:38+01:00","msg":"Checking if App status for t-amqxana-hello-world is equal to 'deployed': failed"}
  {"level":"info","ts":"2023-11-29T15:32:43+01:00","msg":"Checking if App status for t-amqxana-hello-world is equal to 'deployed': failed"}
  {"level":"info","ts":"2023-11-29T15:32:48+01:00","msg":"Checking if App status for t-amqxana-hello-world is equal to 'deployed': failed"}
  {"level":"info","ts":"2023-11-29T15:32:53+01:00","msg":"Checking if App status for t-amqxana-hello-world is equal to 'deployed': failed"}
  {"level":"info","ts":"2023-11-29T15:32:59+01:00","msg":"Checking if App status for t-amqxana-hello-world is equal to 'deployed': failed"}
  {"level":"info","ts":"2023-11-29T15:33:04+01:00","msg":"Checking if App status for t-amqxana-hello-world is equal to 'deployed': failed"}
  {"level":"info","ts":"2023-11-29T15:33:09+01:00","msg":"Checking if App status for t-amqxana-hello-world is equal to 'deployed': failed"}
  {"level":"info","ts":"2023-11-29T15:33:14+01:00","msg":"Checking if App status for t-amqxana-hello-world is equal to 'deployed': failed"}
  {"level":"info","ts":"2023-11-29T15:33:19+01:00","msg":"Checking if App status for t-amqxana-hello-world is equal to 'deployed': failed"}
  {"level":"info","ts":"2023-11-29T15:33:25+01:00","msg":"Checking if App status for t-amqxana-hello-world is equal to 'deployed': deployed"}
  {"level":"info","ts":"2023-11-29T15:33:25+01:00","msg":"Trying to get a successful response from https://hello-world.t-amqxana.gaws.gigantic.io"}
  {"level":"info","ts":"2023-11-29T15:33:31+01:00","msg":"Trying to get a successful response from https://hello-world.t-amqxana.gaws.gigantic.io"}
  {"level":"info","ts":"2023-11-29T15:33:36+01:00","msg":"Trying to get a successful response from https://hello-world.t-amqxana.gaws.gigantic.io"}
  {"level":"info","ts":"2023-11-29T15:33:41+01:00","msg":"Trying to get a successful response from https://hello-world.t-amqxana.gaws.gigantic.io"}
  {"level":"info","ts":"2023-11-29T15:33:46+01:00","msg":"Trying to get a successful response from https://hello-world.t-amqxana.gaws.gigantic.io"}
  {"level":"info","ts":"2023-11-29T15:33:51+01:00","msg":"Trying to get a successful response from https://hello-world.t-amqxana.gaws.gigantic.io"}
  {"level":"info","ts":"2023-11-29T15:33:56+01:00","msg":"Trying to get a successful response from https://hello-world.t-amqxana.gaws.gigantic.io"}
  {"level":"info","ts":"2023-11-29T15:34:01+01:00","msg":"Trying to get a successful response from https://hello-world.t-amqxana.gaws.gigantic.io"}
  {"level":"info","ts":"2023-11-29T15:34:07+01:00","msg":"Trying to get a successful response from https://hello-world.t-amqxana.gaws.gigantic.io"}
  {"level":"info","ts":"2023-11-29T15:34:12+01:00","msg":"Trying to get a successful response from https://hello-world.t-amqxana.gaws.gigantic.io"}
  {"level":"info","ts":"2023-11-29T15:34:17+01:00","msg":"Trying to get a successful response from https://hello-world.t-amqxana.gaws.gigantic.io"}
  {"level":"info","ts":"2023-11-29T15:34:22+01:00","msg":"Trying to get a successful response from https://hello-world.t-amqxana.gaws.gigantic.io"}
  {"level":"info","ts":"2023-11-29T15:34:27+01:00","msg":"Trying to get a successful response from https://hello-world.t-amqxana.gaws.gigantic.io"}
  {"level":"info","ts":"2023-11-29T15:34:32+01:00","msg":"Trying to get a successful response from https://hello-world.t-amqxana.gaws.gigantic.io"}
  {"level":"info","ts":"2023-11-29T15:34:37+01:00","msg":"Trying to get a successful response from https://hello-world.t-amqxana.gaws.gigantic.io"}
  {"level":"info","ts":"2023-11-29T15:34:42+01:00","msg":"Trying to get a successful response from https://hello-world.t-amqxana.gaws.gigantic.io"}
  {"level":"info","ts":"2023-11-29T15:34:47+01:00","msg":"Trying to get a successful response from https://hello-world.t-amqxana.gaws.gigantic.io"}
  {"level":"info","ts":"2023-11-29T15:34:55+01:00","msg":"Trying to get a successful response from https://hello-world.t-amqxana.gaws.gigantic.io"}
  {"level":"info","ts":"2023-11-29T15:35:03+01:00","msg":"Trying to get a successful response from https://hello-world.t-amqxana.gaws.gigantic.io"}
  {"level":"info","ts":"2023-11-29T15:35:08+01:00","msg":"Trying to get a successful response from https://hello-world.t-amqxana.gaws.gigantic.io"}
  {"level":"info","ts":"2023-11-29T15:35:13+01:00","msg":"Trying to get a successful response from https://hello-world.t-amqxana.gaws.gigantic.io"}
  {"level":"info","ts":"2023-11-29T15:35:18+01:00","msg":"Trying to get a successful response from https://hello-world.t-amqxana.gaws.gigantic.io"}
  {"level":"info","ts":"2023-11-29T15:35:23+01:00","msg":"Trying to get a successful response from https://hello-world.t-amqxana.gaws.gigantic.io"}
  {"level":"info","ts":"2023-11-29T15:35:28+01:00","msg":"Trying to get a successful response from https://hello-world.t-amqxana.gaws.gigantic.io"}
  {"level":"info","ts":"2023-11-29T15:35:33+01:00","msg":"Trying to get a successful response from https://hello-world.t-amqxana.gaws.gigantic.io"}
  {"level":"info","ts":"2023-11-29T15:35:38+01:00","msg":"Trying to get a successful response from https://hello-world.t-amqxana.gaws.gigantic.io"}
  {"level":"info","ts":"2023-11-29T15:35:44+01:00","msg":"Trying to get a successful response from https://hello-world.t-amqxana.gaws.gigantic.io"}
  {"level":"info","ts":"2023-11-29T15:35:49+01:00","msg":"Trying to get a successful response from https://hello-world.t-amqxana.gaws.gigantic.io"}
  {"level":"info","ts":"2023-11-29T15:35:54+01:00","msg":"Trying to get a successful response from https://hello-world.t-amqxana.gaws.gigantic.io"}
  {"level":"info","ts":"2023-11-29T15:35:59+01:00","msg":"Trying to get a successful response from https://hello-world.t-amqxana.gaws.gigantic.io"}
  {"level":"info","ts":"2023-11-29T15:36:04+01:00","msg":"Trying to get a successful response from https://hello-world.t-amqxana.gaws.gigantic.io"}
  {"level":"info","ts":"2023-11-29T15:36:09+01:00","msg":"Trying to get a successful response from https://hello-world.t-amqxana.gaws.gigantic.io"}
  {"level":"info","ts":"2023-11-29T15:36:14+01:00","msg":"Trying to get a successful response from https://hello-world.t-amqxana.gaws.gigantic.io"}
  {"level":"info","ts":"2023-11-29T15:36:19+01:00","msg":"Trying to get a successful response from https://hello-world.t-amqxana.gaws.gigantic.io"}
  {"level":"info","ts":"2023-11-29T15:36:25+01:00","msg":"Trying to get a successful response from https://hello-world.t-amqxana.gaws.gigantic.io"}
  {"level":"info","ts":"2023-11-29T15:36:30+01:00","msg":"Trying to get a successful response from https://hello-world.t-amqxana.gaws.gigantic.io"}
  {"level":"info","ts":"2023-11-29T15:36:35+01:00","msg":"Trying to get a successful response from https://hello-world.t-amqxana.gaws.gigantic.io"}
  {"level":"info","ts":"2023-11-29T15:36:40+01:00","msg":"Trying to get a successful response from https://hello-world.t-amqxana.gaws.gigantic.io"}
  {"level":"info","ts":"2023-11-29T15:36:45+01:00","msg":"Trying to get a successful response from https://hello-world.t-amqxana.gaws.gigantic.io"}
  {"level":"info","ts":"2023-11-29T15:36:50+01:00","msg":"Trying to get a successful response from https://hello-world.t-amqxana.gaws.gigantic.io"}
  {"level":"info","ts":"2023-11-29T15:36:55+01:00","msg":"Trying to get a successful response from https://hello-world.t-amqxana.gaws.gigantic.io"}
  {"level":"info","ts":"2023-11-29T15:37:01+01:00","msg":"Trying to get a successful response from https://hello-world.t-amqxana.gaws.gigantic.io"}
  {"level":"info","ts":"2023-11-29T15:37:06+01:00","msg":"Trying to get a successful response from https://hello-world.t-amqxana.gaws.gigantic.io"}
  {"level":"info","ts":"2023-11-29T15:37:11+01:00","msg":"Trying to get a successful response from https://hello-world.t-amqxana.gaws.gigantic.io"}
  {"level":"info","ts":"2023-11-29T15:37:16+01:00","msg":"Trying to get a successful response from https://hello-world.t-amqxana.gaws.gigantic.io"}
  {"level":"info","ts":"2023-11-29T15:37:21+01:00","msg":"Trying to get a successful response from https://hello-world.t-amqxana.gaws.gigantic.io"}
  {"level":"info","ts":"2023-11-29T15:37:26+01:00","msg":"Trying to get a successful response from https://hello-world.t-amqxana.gaws.gigantic.io"}
  {"level":"info","ts":"2023-11-29T15:37:31+01:00","msg":"Trying to get a successful response from https://hello-world.t-amqxana.gaws.gigantic.io"}
  {"level":"info","ts":"2023-11-29T15:37:36+01:00","msg":"Trying to get a successful response from https://hello-world.t-amqxana.gaws.gigantic.io"}
  {"level":"info","ts":"2023-11-29T15:37:41+01:00","msg":"Trying to get a successful response from https://hello-world.t-amqxana.gaws.gigantic.io"}
  {"level":"info","ts":"2023-11-29T15:37:47+01:00","msg":"Trying to get a successful response from https://hello-world.t-amqxana.gaws.gigantic.io"}
  {"level":"info","ts":"2023-11-29T15:37:52+01:00","msg":"Trying to get a successful response from https://hello-world.t-amqxana.gaws.gigantic.io"}
  {"level":"info","ts":"2023-11-29T15:37:57+01:00","msg":"Trying to get a successful response from https://hello-world.t-amqxana.gaws.gigantic.io"}
  {"level":"info","ts":"2023-11-29T15:38:02+01:00","msg":"Trying to get a successful response from https://hello-world.t-amqxana.gaws.gigantic.io"}
  {"level":"info","ts":"2023-11-29T15:38:07+01:00","msg":"Trying to get a successful response from https://hello-world.t-amqxana.gaws.gigantic.io"}
  {"level":"info","ts":"2023-11-29T15:38:12+01:00","msg":"Trying to get a successful response from https://hello-world.t-amqxana.gaws.gigantic.io"}
  {"level":"info","ts":"2023-11-29T15:38:17+01:00","msg":"Trying to get a successful response from https://hello-world.t-amqxana.gaws.gigantic.io"}
  {"level":"info","ts":"2023-11-29T15:38:22+01:00","msg":"Trying to get a successful response from https://hello-world.t-amqxana.gaws.gigantic.io"}
  {"level":"info","ts":"2023-11-29T15:38:28+01:00","msg":"Trying to get a successful response from https://hello-world.t-amqxana.gaws.gigantic.io"}
  {"level":"info","ts":"2023-11-29T15:38:33+01:00","msg":"Trying to get a successful response from https://hello-world.t-amqxana.gaws.gigantic.io"}
  {"level":"info","ts":"2023-11-29T15:38:38+01:00","msg":"Trying to get a successful response from https://hello-world.t-amqxana.gaws.gigantic.io"}
  {"level":"info","ts":"2023-11-29T15:38:43+01:00","msg":"Trying to get a successful response from https://hello-world.t-amqxana.gaws.gigantic.io"}
  {"level":"info","ts":"2023-11-29T15:38:48+01:00","msg":"Trying to get a successful response from https://hello-world.t-amqxana.gaws.gigantic.io"}
• [419.545 seconds]
------------------------------
Common tests scale scales node by creating anti-affiniy pods
/Users/nikola/src/giantswarm/cluster-test-suites/internal/common/scale.go:81
  {"level":"info","ts":"2023-11-29T15:39:00+01:00","msg":"Checking if App status for t-amqxana-scale-hello-world is equal to 'deployed': "}
  {"level":"info","ts":"2023-11-29T15:39:05+01:00","msg":"Checking if App status for t-amqxana-scale-hello-world is equal to 'deployed': deployed"}
  {"level":"info","ts":"2023-11-29T15:39:05+01:00","msg":"Checking for increased replicas. Expected: 2, Actual: 1"}
  {"level":"info","ts":"2023-11-29T15:39:15+01:00","msg":"Checking for increased replicas. Expected: 2, Actual: 1"}
  {"level":"info","ts":"2023-11-29T15:39:26+01:00","msg":"Checking for increased replicas. Expected: 2, Actual: 1"}
  {"level":"info","ts":"2023-11-29T15:39:36+01:00","msg":"Checking for increased replicas. Expected: 2, Actual: 1"}
  {"level":"info","ts":"2023-11-29T15:39:46+01:00","msg":"Checking for increased replicas. Expected: 2, Actual: 1"}
  {"level":"info","ts":"2023-11-29T15:39:56+01:00","msg":"Checking for increased replicas. Expected: 2, Actual: 1"}
  {"level":"info","ts":"2023-11-29T15:40:06+01:00","msg":"Checking for increased replicas. Expected: 2, Actual: 1"}
  {"level":"info","ts":"2023-11-29T15:40:16+01:00","msg":"Checking for increased replicas. Expected: 2, Actual: 1"}
  {"level":"info","ts":"2023-11-29T15:40:26+01:00","msg":"Checking for increased replicas. Expected: 2, Actual: 1"}
  {"level":"info","ts":"2023-11-29T15:40:36+01:00","msg":"Checking for increased replicas. Expected: 2, Actual: 1"}
  {"level":"info","ts":"2023-11-29T15:40:46+01:00","msg":"Checking for increased replicas. Expected: 2, Actual: 1"}
  {"level":"info","ts":"2023-11-29T15:40:56+01:00","msg":"Checking for increased replicas. Expected: 2, Actual: 1"}
  {"level":"info","ts":"2023-11-29T15:41:06+01:00","msg":"Checking for increased replicas. Expected: 2, Actual: 1"}
  {"level":"info","ts":"2023-11-29T15:41:16+01:00","msg":"Checking for increased replicas. Expected: 2, Actual: 1"}
  {"level":"info","ts":"2023-11-29T15:41:26+01:00","msg":"Checking for increased replicas. Expected: 2, Actual: 1"}
  {"level":"info","ts":"2023-11-29T15:41:37+01:00","msg":"Checking for increased replicas. Expected: 2, Actual: 1"}
  {"level":"info","ts":"2023-11-29T15:41:47+01:00","msg":"Checking for increased replicas. Expected: 2, Actual: 1"}
  {"level":"info","ts":"2023-11-29T15:41:57+01:00","msg":"Checking for increased replicas. Expected: 2, Actual: 1"}
  {"level":"info","ts":"2023-11-29T15:42:07+01:00","msg":"Checking for increased replicas. Expected: 2, Actual: 1"}
  {"level":"info","ts":"2023-11-29T15:42:17+01:00","msg":"Checking for increased replicas. Expected: 2, Actual: 1"}
  {"level":"info","ts":"2023-11-29T15:42:27+01:00","msg":"Checking for increased replicas. Expected: 2, Actual: 1"}
  {"level":"info","ts":"2023-11-29T15:42:37+01:00","msg":"Checking for increased replicas. Expected: 2, Actual: 1"}
  {"level":"info","ts":"2023-11-29T15:42:47+01:00","msg":"Checking for increased replicas. Expected: 2, Actual: 1"}
  {"level":"info","ts":"2023-11-29T15:42:57+01:00","msg":"Checking for increased replicas. Expected: 2, Actual: 1"}
  {"level":"info","ts":"2023-11-29T15:43:07+01:00","msg":"Checking for increased replicas. Expected: 2, Actual: 1"}
  {"level":"info","ts":"2023-11-29T15:43:17+01:00","msg":"Checking for increased replicas. Expected: 2, Actual: 1"}
  {"level":"info","ts":"2023-11-29T15:43:27+01:00","msg":"Checking for increased replicas. Expected: 2, Actual: 1"}
  {"level":"info","ts":"2023-11-29T15:43:37+01:00","msg":"Checking for increased replicas. Expected: 2, Actual: 1"}
  {"level":"info","ts":"2023-11-29T15:43:47+01:00","msg":"Checking for increased replicas. Expected: 2, Actual: 1"}
  {"level":"info","ts":"2023-11-29T15:43:57+01:00","msg":"Checking for increased replicas. Expected: 2, Actual: 1"}
  {"level":"info","ts":"2023-11-29T15:44:08+01:00","msg":"Checking for increased replicas. Expected: 2, Actual: 1"}
  {"level":"info","ts":"2023-11-29T15:44:18+01:00","msg":"Checking for increased replicas. Expected: 2, Actual: 1"}
  {"level":"info","ts":"2023-11-29T15:44:28+01:00","msg":"Checking for increased replicas. Expected: 2, Actual: 1"}
  {"level":"info","ts":"2023-11-29T15:44:38+01:00","msg":"Checking for increased replicas. Expected: 2, Actual: 1"}
  {"level":"info","ts":"2023-11-29T15:44:48+01:00","msg":"Checking for increased replicas. Expected: 2, Actual: 1"}
  {"level":"info","ts":"2023-11-29T15:44:58+01:00","msg":"Checking for increased replicas. Expected: 2, Actual: 1"}
  {"level":"info","ts":"2023-11-29T15:45:08+01:00","msg":"Checking for increased replicas. Expected: 2, Actual: 1"}
  {"level":"info","ts":"2023-11-29T15:45:18+01:00","msg":"Checking for increased replicas. Expected: 2, Actual: 1"}
  {"level":"info","ts":"2023-11-29T15:45:28+01:00","msg":"Checking for increased replicas. Expected: 2, Actual: 1"}
  {"level":"info","ts":"2023-11-29T15:45:38+01:00","msg":"Checking for increased replicas. Expected: 2, Actual: 1"}
  {"level":"info","ts":"2023-11-29T15:45:48+01:00","msg":"Checking for increased replicas. Expected: 2, Actual: 1"}
  {"level":"info","ts":"2023-11-29T15:45:58+01:00","msg":"Checking for increased replicas. Expected: 2, Actual: 1"}
  {"level":"info","ts":"2023-11-29T15:46:08+01:00","msg":"Checking for increased replicas. Expected: 2, Actual: 1"}
  {"level":"info","ts":"2023-11-29T15:46:18+01:00","msg":"Checking for increased replicas. Expected: 2, Actual: 2"}
• [440.149 seconds]
------------------------------
Common tests storage has a at least one storage class available
/Users/nikola/src/giantswarm/cluster-test-suites/internal/common/storage.go:40
• [11.001 seconds]
------------------------------
Common tests storage when a pod uses a persistent volume claim runs successfully
/Users/nikola/src/giantswarm/cluster-test-suites/internal/common/storage.go:62
• [33.404 seconds]
------------------------------
[DeferCleanup (Suite)]
/Users/nikola/src/giantswarm/cluster-test-suites/providers/capa/standard/capa_suite_test.go:68
  {"level":"info","ts":"2023-11-29T15:47:04+01:00","msg":"Checking if Cluster 't-amqxana' still exists"}
  {"level":"info","ts":"2023-11-29T15:47:14+01:00","msg":"Checking if Cluster 't-amqxana' still exists"}
  {"level":"info","ts":"2023-11-29T15:47:24+01:00","msg":"Checking if Cluster 't-amqxana' still exists"}
  {"level":"info","ts":"2023-11-29T15:47:34+01:00","msg":"Checking if Cluster 't-amqxana' still exists"}
  {"level":"info","ts":"2023-11-29T15:47:44+01:00","msg":"Checking if Cluster 't-amqxana' still exists"}
  {"level":"info","ts":"2023-11-29T15:47:54+01:00","msg":"Checking if Cluster 't-amqxana' still exists"}
  {"level":"info","ts":"2023-11-29T15:48:04+01:00","msg":"Checking if Cluster 't-amqxana' still exists"}
  {"level":"info","ts":"2023-11-29T15:48:14+01:00","msg":"Checking if Cluster 't-amqxana' still exists"}
  {"level":"info","ts":"2023-11-29T15:48:24+01:00","msg":"Checking if Cluster 't-amqxana' still exists"}
  {"level":"info","ts":"2023-11-29T15:48:34+01:00","msg":"Checking if Cluster 't-amqxana' still exists"}
  {"level":"info","ts":"2023-11-29T15:48:44+01:00","msg":"Checking if Cluster 't-amqxana' still exists"}
  {"level":"info","ts":"2023-11-29T15:48:54+01:00","msg":"Checking if Cluster 't-amqxana' still exists"}
  {"level":"info","ts":"2023-11-29T15:49:04+01:00","msg":"Checking if Cluster 't-amqxana' still exists"}
  {"level":"info","ts":"2023-11-29T15:49:15+01:00","msg":"Checking if Cluster 't-amqxana' still exists"}
  {"level":"info","ts":"2023-11-29T15:49:25+01:00","msg":"Checking if Cluster 't-amqxana' still exists"}
  {"level":"info","ts":"2023-11-29T15:49:35+01:00","msg":"Checking if Cluster 't-amqxana' still exists"}
  {"level":"info","ts":"2023-11-29T15:49:45+01:00","msg":"Checking if Cluster 't-amqxana' still exists"}
  {"level":"info","ts":"2023-11-29T15:49:55+01:00","msg":"Checking if Cluster 't-amqxana' still exists"}
  {"level":"info","ts":"2023-11-29T15:50:05+01:00","msg":"Checking if Cluster 't-amqxana' still exists"}
  {"level":"info","ts":"2023-11-29T15:50:15+01:00","msg":"Checking if Cluster 't-amqxana' still exists"}
  {"level":"info","ts":"2023-11-29T15:50:25+01:00","msg":"Checking if Cluster 't-amqxana' still exists"}
  {"level":"info","ts":"2023-11-29T15:50:35+01:00","msg":"Checking if Cluster 't-amqxana' still exists"}
  {"level":"info","ts":"2023-11-29T15:50:45+01:00","msg":"Checking if Cluster 't-amqxana' still exists"}
  {"level":"info","ts":"2023-11-29T15:50:55+01:00","msg":"Checking if Cluster 't-amqxana' still exists"}
  {"level":"info","ts":"2023-11-29T15:51:05+01:00","msg":"Checking if Cluster 't-amqxana' still exists"}
  {"level":"info","ts":"2023-11-29T15:51:15+01:00","msg":"Checking if Cluster 't-amqxana' still exists"}
  {"level":"info","ts":"2023-11-29T15:51:25+01:00","msg":"Checking if Cluster 't-amqxana' still exists"}
  {"level":"info","ts":"2023-11-29T15:51:35+01:00","msg":"Checking if Cluster 't-amqxana' still exists"}
  {"level":"info","ts":"2023-11-29T15:51:46+01:00","msg":"Checking if Cluster 't-amqxana' still exists"}
  {"level":"info","ts":"2023-11-29T15:51:56+01:00","msg":"Checking if Cluster 't-amqxana' still exists"}
  {"level":"info","ts":"2023-11-29T15:52:06+01:00","msg":"Checking if Cluster 't-amqxana' still exists"}
  {"level":"info","ts":"2023-11-29T15:52:16+01:00","msg":"Checking if Cluster 't-amqxana' still exists"}
  {"level":"info","ts":"2023-11-29T15:52:26+01:00","msg":"Checking if Cluster 't-amqxana' still exists"}
  {"level":"info","ts":"2023-11-29T15:52:36+01:00","msg":"Checking if Cluster 't-amqxana' still exists"}
  {"level":"info","ts":"2023-11-29T15:52:46+01:00","msg":"Checking if Cluster 't-amqxana' still exists"}
  {"level":"info","ts":"2023-11-29T15:52:56+01:00","msg":"Checking if Cluster 't-amqxana' still exists"}
  {"level":"info","ts":"2023-11-29T15:53:06+01:00","msg":"Checking if Cluster 't-amqxana' still exists"}
  {"level":"info","ts":"2023-11-29T15:53:16+01:00","msg":"Checking if Cluster 't-amqxana' still exists"}
  {"level":"info","ts":"2023-11-29T15:53:26+01:00","msg":"Checking if Cluster 't-amqxana' still exists"}
  {"level":"info","ts":"2023-11-29T15:53:36+01:00","msg":"Checking if Cluster 't-amqxana' still exists"}
  {"level":"info","ts":"2023-11-29T15:53:46+01:00","msg":"Checking if Cluster 't-amqxana' still exists"}
  {"level":"info","ts":"2023-11-29T15:53:56+01:00","msg":"Checking if Cluster 't-amqxana' still exists"}
  {"level":"info","ts":"2023-11-29T15:54:06+01:00","msg":"Checking if Cluster 't-amqxana' still exists"}
  {"level":"info","ts":"2023-11-29T15:54:17+01:00","msg":"Checking if Cluster 't-amqxana' still exists"}
  {"level":"info","ts":"2023-11-29T15:54:27+01:00","msg":"Checking if Cluster 't-amqxana' still exists"}
  {"level":"info","ts":"2023-11-29T15:54:37+01:00","msg":"Checking if Cluster 't-amqxana' still exists"}
  {"level":"info","ts":"2023-11-29T15:54:47+01:00","msg":"Checking if Cluster 't-amqxana' still exists"}
  {"level":"info","ts":"2023-11-29T15:54:57+01:00","msg":"Checking if Cluster 't-amqxana' still exists"}
  {"level":"info","ts":"2023-11-29T15:55:07+01:00","msg":"Checking if Cluster 't-amqxana' still exists"}
  {"level":"info","ts":"2023-11-29T15:55:17+01:00","msg":"Checking if Cluster 't-amqxana' still exists"}
  {"level":"info","ts":"2023-11-29T15:55:27+01:00","msg":"Checking if Cluster 't-amqxana' still exists"}
  {"level":"info","ts":"2023-11-29T15:55:37+01:00","msg":"Checking if Cluster 't-amqxana' still exists"}
  {"level":"info","ts":"2023-11-29T15:55:47+01:00","msg":"Checking if Cluster 't-amqxana' still exists"}
  {"level":"info","ts":"2023-11-29T15:55:57+01:00","msg":"Checking if Cluster 't-amqxana' still exists"}
  {"level":"info","ts":"2023-11-29T15:56:07+01:00","msg":"Checking if Cluster 't-amqxana' still exists"}
  {"level":"info","ts":"2023-11-29T15:56:17+01:00","msg":"Checking if Cluster 't-amqxana' still exists"}
  {"level":"info","ts":"2023-11-29T15:56:27+01:00","msg":"Checking if Cluster 't-amqxana' still exists"}
  {"level":"info","ts":"2023-11-29T15:56:37+01:00","msg":"Checking if Cluster 't-amqxana' still exists"}
  {"level":"info","ts":"2023-11-29T15:56:48+01:00","msg":"Checking if Cluster 't-amqxana' still exists"}
  {"level":"info","ts":"2023-11-29T15:56:58+01:00","msg":"Checking if Cluster 't-amqxana' still exists"}
  {"level":"info","ts":"2023-11-29T15:57:08+01:00","msg":"Checking if Cluster 't-amqxana' still exists"}
  {"level":"info","ts":"2023-11-29T15:57:18+01:00","msg":"Checking if Cluster 't-amqxana' still exists"}
  {"level":"info","ts":"2023-11-29T15:57:28+01:00","msg":"Checking if Cluster 't-amqxana' still exists"}
  {"level":"info","ts":"2023-11-29T15:57:38+01:00","msg":"Checking if Cluster 't-amqxana' still exists"}
  {"level":"info","ts":"2023-11-29T15:57:48+01:00","msg":"Checking if Cluster 't-amqxana' still exists"}
  {"level":"info","ts":"2023-11-29T15:57:58+01:00","msg":"Checking if Cluster 't-amqxana' still exists"}
  {"level":"info","ts":"2023-11-29T15:58:08+01:00","msg":"Checking if Cluster 't-amqxana' still exists"}
  {"level":"info","ts":"2023-11-29T15:58:18+01:00","msg":"Checking if Cluster 't-amqxana' still exists"}
  {"level":"info","ts":"2023-11-29T15:58:28+01:00","msg":"Checking if Cluster 't-amqxana' still exists"}
  {"level":"info","ts":"2023-11-29T15:58:38+01:00","msg":"Checking if Cluster 't-amqxana' still exists"}
  {"level":"info","ts":"2023-11-29T15:58:48+01:00","msg":"Checking if Cluster 't-amqxana' still exists"}
  {"level":"info","ts":"2023-11-29T15:58:58+01:00","msg":"Checking if Cluster 't-amqxana' still exists"}
  {"level":"info","ts":"2023-11-29T15:59:09+01:00","msg":"Checking if Cluster 't-amqxana' still exists"}
  {"level":"info","ts":"2023-11-29T15:59:19+01:00","msg":"Checking if Cluster 't-amqxana' still exists"}
  {"level":"info","ts":"2023-11-29T15:59:29+01:00","msg":"Checking if Cluster 't-amqxana' still exists"}
  {"level":"info","ts":"2023-11-29T15:59:39+01:00","msg":"Checking if Cluster 't-amqxana' still exists"}
  {"level":"info","ts":"2023-11-29T15:59:49+01:00","msg":"Checking if Cluster 't-amqxana' still exists"}
  {"level":"info","ts":"2023-11-29T15:59:59+01:00","msg":"Checking if Cluster 't-amqxana' still exists"}
  {"level":"info","ts":"2023-11-29T16:00:09+01:00","msg":"Checking if Cluster 't-amqxana' still exists"}
  {"level":"info","ts":"2023-11-29T16:00:19+01:00","msg":"Checking if Cluster 't-amqxana' still exists"}
  {"level":"info","ts":"2023-11-29T16:00:29+01:00","msg":"Checking if Cluster 't-amqxana' still exists"}
  {"level":"info","ts":"2023-11-29T16:00:39+01:00","msg":"Checking if Cluster 't-amqxana' still exists"}
  {"level":"info","ts":"2023-11-29T16:00:49+01:00","msg":"Checking if Cluster 't-amqxana' still exists"}
  {"level":"info","ts":"2023-11-29T16:00:59+01:00","msg":"Checking if Cluster 't-amqxana' still exists"}
  {"level":"info","ts":"2023-11-29T16:01:09+01:00","msg":"Checking if Cluster 't-amqxana' still exists"}
  {"level":"info","ts":"2023-11-29T16:01:19+01:00","msg":"Checking if Cluster 't-amqxana' still exists"}
  {"level":"info","ts":"2023-11-29T16:01:30+01:00","msg":"Checking if Cluster 't-amqxana' still exists"}
  {"level":"info","ts":"2023-11-29T16:01:40+01:00","msg":"Checking if Cluster 't-amqxana' still exists"}
  {"level":"info","ts":"2023-11-29T16:01:50+01:00","msg":"Checking if Cluster 't-amqxana' still exists"}
  {"level":"info","ts":"2023-11-29T16:02:00+01:00","msg":"Checking if Cluster 't-amqxana' still exists"}
  {"level":"info","ts":"2023-11-29T16:02:10+01:00","msg":"Checking if Cluster 't-amqxana' still exists"}
  {"level":"info","ts":"2023-11-29T16:02:20+01:00","msg":"Checking if Cluster 't-amqxana' still exists"}
  {"level":"info","ts":"2023-11-29T16:02:30+01:00","msg":"Checking if Cluster 't-amqxana' still exists"}
  {"level":"info","ts":"2023-11-29T16:02:40+01:00","msg":"Checking if Cluster 't-amqxana' still exists"}
  {"level":"info","ts":"2023-11-29T16:02:50+01:00","msg":"Checking if Cluster 't-amqxana' still exists"}
  {"level":"info","ts":"2023-11-29T16:03:00+01:00","msg":"Checking if Cluster 't-amqxana' still exists"}
  {"level":"info","ts":"2023-11-29T16:03:10+01:00","msg":"Checking if Cluster 't-amqxana' still exists"}
  {"level":"info","ts":"2023-11-29T16:03:20+01:00","msg":"Checking if Cluster 't-amqxana' still exists"}
  {"level":"info","ts":"2023-11-29T16:03:30+01:00","msg":"Checking if Cluster 't-amqxana' still exists"}
  {"level":"info","ts":"2023-11-29T16:03:41+01:00","msg":"Checking if Cluster 't-amqxana' still exists"}
  {"level":"info","ts":"2023-11-29T16:03:51+01:00","msg":"Checking if Cluster 't-amqxana' still exists"}
  {"level":"info","ts":"2023-11-29T16:04:01+01:00","msg":"Checking if Cluster 't-amqxana' still exists"}
  {"level":"info","ts":"2023-11-29T16:04:11+01:00","msg":"Checking if Cluster 't-amqxana' still exists"}
  {"level":"info","ts":"2023-11-29T16:04:21+01:00","msg":"Checking if Cluster 't-amqxana' still exists"}
  {"level":"info","ts":"2023-11-29T16:04:31+01:00","msg":"Checking if Cluster 't-amqxana' still exists"}
  {"level":"info","ts":"2023-11-29T16:04:41+01:00","msg":"Checking if Cluster 't-amqxana' still exists"}
  {"level":"info","ts":"2023-11-29T16:04:51+01:00","msg":"Checking if Cluster 't-amqxana' still exists"}
  {"level":"info","ts":"2023-11-29T16:05:01+01:00","msg":"Checking if Cluster 't-amqxana' still exists"}
  {"level":"info","ts":"2023-11-29T16:05:11+01:00","msg":"Checking if Cluster 't-amqxana' still exists"}
  {"level":"info","ts":"2023-11-29T16:05:21+01:00","msg":"Checking if Cluster 't-amqxana' still exists"}
  {"level":"info","ts":"2023-11-29T16:05:31+01:00","msg":"Checking if Cluster 't-amqxana' still exists"}
  {"level":"info","ts":"2023-11-29T16:05:41+01:00","msg":"Checking if Cluster 't-amqxana' still exists"}
  {"level":"info","ts":"2023-11-29T16:05:51+01:00","msg":"Checking if Cluster 't-amqxana' still exists"}
  {"level":"info","ts":"2023-11-29T16:06:02+01:00","msg":"Checking if Cluster 't-amqxana' still exists"}
  {"level":"info","ts":"2023-11-29T16:06:12+01:00","msg":"Checking if Cluster 't-amqxana' still exists"}
  {"level":"info","ts":"2023-11-29T16:06:22+01:00","msg":"Checking if Cluster 't-amqxana' still exists"}
  {"level":"info","ts":"2023-11-29T16:06:32+01:00","msg":"Checking if Cluster 't-amqxana' still exists"}
  {"level":"info","ts":"2023-11-29T16:06:32+01:00","msg":"Checking if Organization 't-9x2zyj8' still exists"}
  {"level":"info","ts":"2023-11-29T16:06:42+01:00","msg":"Checking if Organization 't-9x2zyj8' still exists"}
  {"level":"info","ts":"2023-11-29T16:06:52+01:00","msg":"Checking if Organization 't-9x2zyj8' still exists"}
  {"level":"info","ts":"2023-11-29T16:07:02+01:00","msg":"Checking if Organization 't-9x2zyj8' still exists"}
  {"level":"info","ts":"2023-11-29T16:07:12+01:00","msg":"Checking if Organization 't-9x2zyj8' still exists"}
  {"level":"info","ts":"2023-11-29T16:07:22+01:00","msg":"Checking if Organization 't-9x2zyj8' still exists"}
  {"level":"info","ts":"2023-11-29T16:07:32+01:00","msg":"Checking if Organization 't-9x2zyj8' still exists"}
  {"level":"info","ts":"2023-11-29T16:07:42+01:00","msg":"Checking if Organization 't-9x2zyj8' still exists"}
  {"level":"info","ts":"2023-11-29T16:07:53+01:00","msg":"Checking if Organization 't-9x2zyj8' still exists"}
  {"level":"info","ts":"2023-11-29T16:08:03+01:00","msg":"Checking if Organization 't-9x2zyj8' still exists"}
  {"level":"info","ts":"2023-11-29T16:08:13+01:00","msg":"Checking if Organization 't-9x2zyj8' still exists"}
  {"level":"info","ts":"2023-11-29T16:08:23+01:00","msg":"Checking if Organization 't-9x2zyj8' still exists"}
  {"level":"info","ts":"2023-11-29T16:08:33+01:00","msg":"Checking if Organization 't-9x2zyj8' still exists"}
  {"level":"info","ts":"2023-11-29T16:08:43+01:00","msg":"Checking if Organization 't-9x2zyj8' still exists"}
  {"level":"info","ts":"2023-11-29T16:08:54+01:00","msg":"Checking if Organization 't-9x2zyj8' still exists"}
  {"level":"info","ts":"2023-11-29T16:09:04+01:00","msg":"Checking if Organization 't-9x2zyj8' still exists"}
  {"level":"info","ts":"2023-11-29T16:09:14+01:00","msg":"Checking if Organization 't-9x2zyj8' still exists"}
[DeferCleanup (Suite)] PASSED [1330.344 seconds]
------------------------------

Ran 14 of 14 Specs in 3404.167 seconds
SUCCESS! -- 14 Passed | 0 Failed | 0 Pending | 0 Skipped
PASS

Ginkgo ran 1 suite in 56m51.561811875s
Test Suite Passed


(Some) nested tests are not printed at all

Reproducer: https://github.com/rkraneis/tree-reporter
Context: https://github.com/rkraneis/tree-reporter/blob/2a656ebb9e4c5c39371b5fd4e849c326641437fb/README.md
Actual:
├─ io.github.rkraneis.treereporter.OuterTest - 0.036s
│  └─ ✔ test - 0.011s
├─ ── InnerSub2 - 0.001s
│     ├─ ✔ testFromBase - 0s
│     └─ ✔ testInnerSub2 - 0.001s

Expected:
├─ io.github.rkraneis.treereporter.OuterTest - 0.036s
│  └─ ✔ test - 0.011s
├─ ── Inner1 - 0.001s
│     └─ ✔ testInner1 - 0.001s
├─ ── Inner2 - 0.001s
│     └─ ✔ testInner2 - 0.001s
├─ ── InnerSub1 - 0.001s
│     ├─ ✔ testFromBase - 0s
│     └─ ✔ testInnerSub1 - 0.001s
├─ ── InnerSub2 - 0.001s
│     ├─ ✔ testFromBase - 0s
│     └─ ✔ testInnerSub2 - 0.001s

The tests themselves are executed (Tests run: 7, Failures: 0, Errors: 0, Skipped: 0).
N.B.: I started my own tree view printer a while ago (basically just as a copy of what the junit jupiter console launcher does), but didn't like the messy setup (test execution listener). Your POM based version would be much better, setup-wise.

Yeah, there's a bug when there is more than one @Nested class in the same Test file, interesting how I did not test this scenario before!
Not so easy but I'll be looking for a fix ASAP! Thanks!


plugins/gimp: Add support for encoding JPEG XL animations

plugins/gimp: Add support for encoding JPEG XL animations
Closes https://github.com/libjxl/libjxl/issues/1864.
Because I use the same semantics as the GIMP's existing GIF and WebP plugins, one can open a WebP and then immediately save a JPEG XL. E.g.:

Note: This assumes the acceptance of my other PR's for the GIMP plugin, #1863 and #1870. This should be merged only when those are merged. It became too difficult to try to maintain separate histories given how intertwined some of my (necessary) changes are.

Could you rebase so it's easier to see what's new?

https://github.com/libjxl/libjxl/pull/1874/commits/fb8948eda09b50beaaa039dfbb5ee342c14f3f04

I took the liberty to make a squashed rebase, so that only the 4 files that have been changed show up in the review here...

Thanks, wasn't sure how

rebasing once more, because https://github.com/libjxl/libjxl/pull/1903 just landed and that modifies the same files (this one was trivial to rebase, though..)

@jonsneyers I think we should move forward on this and even accept a version that can later be improved. Better to have slighly buggy animation support than none...

I plan to rebase and resovle the conflicts after https://github.com/libjxl/libjxl/pull/2190 is merged...


General improvements

README.md

Add badges.

rebar3.config

Do refactoring

Makefile

Do refactoring

Add doc folder

Add documentation generation presetts

Fix xref warning related to tests.
Add examples of using Exif data API.

exif_reader_app Simple OTP Application.
exif_web_viewer EXIF data web viewer.

The PR Fix typo is this PR too.

@rustkas Sorry, in the meantime rebar3 is updated and will not run on 22 anymore.
Could you change the test matrix:
https://github.com/erlangpack/erlang_exif/blob/master/.github/workflows/test.yml#L21
To 23, 24, 25 ?

I found that I could edit your branch for this small change :-)

Thanks again!

Thanks again!

Thank you! Studying this project was fun.

It is very important to take a break from a project for a while and get back to it. I have found small shortcomings which I would like to fix.


Add auth0 example

After talking to @luisrudge I decided to update the example to reflect changes in 2.0 and move it into the next.js repo so it can be easily found.

I'm a bit of a newb with auth, but is it safe to use cookies that aren't httpOnly?
See https://github.com/zeit/next.js/issues/153#issuecomment-264215442

https://github.com/zeit/next.js/issues/153#issuecomment-272393862
Going to have a look at @iaincollins's starter setup 👍

@timneutkens you can also look at my project for ideas:
https://github.com/relatenow/relate/
I took some ideas from @iaincollins' project back then. Would be interested in any feedback.

AFAIK, there are 2 places that store the jwt token here:

localStorage

and cookie

I know that cookie is required for next.js server to render a page properly when user is authenticated. If there is a need for gathering info from external API, the server will request the API on behalf of user (using the jwt token from cookie). But this mean the site is now vulnerable for CSRF attack isn't it?

Also storing jwt token in localStorage or cookie would make the site vulnerable for XSS attack.

Could you explain a little these things @timneutkens ? I'm new to authentication mechanisms.

@thangngoc89 cc @luisrudge

Closing this one in favor of Iain's work which is more secure.

@timneutkens could you drop a link to lain's work?

https://github.com/iaincollins/nextjs-starter

@timneutkens thank you


Exception on heavy load in springboot

we are using springboot-starter redisson client on cloud foundry and using AWS Redis cluster, 99% operations are read only, i am using RMapCache<String, String>  and I am using default config, not changed threads/nettry threads etc.
During load testing (max 200 requests per second), getting below different exception intermittently (DNS , out of memory, readtimout) and once we get these exception , they are not recovered.
Could please let me know how we can fine tune the configs to support heavy reads?.
DNS Logs:
java.net.UnknownHostException: failed to resolve 'clustercfg.rg-guid.iroxbd.dc.cache.amazonaws.com'
Caused by: io.netty.resolver.dns.DnsNameResolverException: [/<IP_ADDRESS>:98] failed to send a query via UDP (no stack trace available)
Read timeout Logs:
org.redisson.client.RedisTimeoutException: Command still hasn't been written into connection! Try to increase nettyThreads setting. Payload size in bytes: 57.
ERROR [redisson-netty-2-20] - [org.redisson.client.handler.ErrorsLoggingHandler] [] - Exception occured. Channel: [id: 0xf41c0518, L:/10.129.202 ! R:rg-c-0001-001.rg-cbc.cache.amazonaws.com/:1473]
java.lang.OutOfMemoryError: Direct buffer memory
at java.base/java.nio.Bits.reserveMemory(Unknown Source)
at java.base/java.nio.DirectByteBuffer.(Unknown Source)
at java.base/java.nio.ByteBuffer.allocateDirect(Unknown Source)

which netty version do you use?


paging component example

What kind of change does this PR introduce? (check at least one)

[ ] Bugfix
[ ] Feature
[ ] Code style update
[ ] Refactor
[ ] Build-related changes
[x] Other, please describe: an example of a paging component is added

Does this PR introduce a breaking change? (check one)

[ ] Yes
[x] No

Same as #7898


Temporary fix for classy-prelude

Add the conversions betwen (String/Text) and FilePath once again.
Will have to be removed again if classy-prelude is removed.
Temporary fix for #491.

Thanks. This is a serious problem for stability of IHaskell lately, so either a) IHaskell needs to be added to Stackage or b) classy-prelude needs to be removed.
(a) should happen anyways and I will do it soonish (well, next two months) and I think I will also do (b) in the shorter term (next month)

There's a mistake in here, I'll fix it in a moment.


Doesn't work with babel-preset-airbnb

[!] (babel plugin) Error: It looks like your Babel configuration specifies a module transformer. Please disable it. See https://github.com/rollup/rollup-plugin-babel#configuring-babel for more information
package.json
  "devDependencies": {
    "babel-core": "^6.26.3",
    "babel-plugin-external-helpers": "^6.22.0",
    "babel-plugin-transform-function-bind": "^6.22.0",
    "babel-preset-airbnb": "^2.5.1",
    "babel-preset-env": "^1.7.0",
    "babel-runtime": "^6.26.0",
    "rollup": "^0.60.7",
    "rollup-plugin-babel": "^3.0.4",
    "rollup-plugin-commonjs": "^9.1.3",
    "rollup-plugin-node-resolve": "^3.3.0",
    "rollup-plugin-uglify": "^4.0.0"
  }

.babelrc
{
  presets: [
    [
      "env",
      {
        modules: false
      }
    ],
    "airbnb"
  ],
  plugins: ["external-helpers", "transform-function-bind"]
}

rollup.config.js
// Rollup plugins
import babel from "rollup-plugin-babel";
import resolve from "rollup-plugin-node-resolve";
import commonjs from "rollup-plugin-commonjs";
import { uglify } from "rollup-plugin-uglify";

export default {
  input: "src/index.js",
  output: {
    file: "./show.js",
    format: "iife"
  },
  plugins: [
    babel({
      exclude: "node_modules/**",
      runtimeHelpers: true
    }),
    resolve({
      jsnext: true,
      main: true,
      browser: true
    }),
    commonjs(),
    uglify({
      compress: {
        screw_ie8: true,
        warnings: false
      },
      output: {
        comments: false
      },
      sourceMap: false
    })
  ]
};

babel-preset-airbnb debug output
babel-preset-env: `DEBUG` option

Using targets:
{
  "android": "30",
  "chrome": "35",
  "edge": "14",
  "explorer": "9",
  "firefox": "52",
  "safari": "8",
  "ucandroid": "1"
}

Modules transform: false

Using plugins:
  check-es2015-constants {"android":"30","chrome":"35","explorer":"9","safari":"8","ucandroid":"1"}
  transform-es2015-arrow-functions {"android":"30","chrome":"35","explorer":"9","safari":"8","ucandroid":"1"}
  transform-es2015-block-scoped-functions {"android":"30","chrome":"35","explorer":"9","safari":"8","ucandroid":"1"}
  transform-es2015-block-scoping {"android":"30","chrome":"35","explorer":"9","safari":"8","ucandroid":"1"}
  transform-es2015-classes {"android":"30","chrome":"35","explorer":"9","safari":"8","ucandroid":"1"}
  transform-es2015-computed-properties {"android":"30","chrome":"35","explorer":"9","ucandroid":"1"}
  transform-es2015-destructuring {"android":"30","chrome":"35","edge":"14","explorer":"9","firefox":"52","safari":"8","ucandroid":"1"}
  transform-es2015-duplicate-keys {"android":"30","chrome":"35","explorer":"9","safari":"8","ucandroid":"1"}
  transform-es2015-for-of {"android":"30","chrome":"35","edge":"14","explorer":"9","firefox":"52","safari":"8","ucandroid":"1"}
  transform-es2015-function-name {"android":"30","chrome":"35","edge":"14","explorer":"9","firefox":"52","safari":"8","ucandroid":"1"}
  transform-es2015-literals {"android":"30","chrome":"35","explorer":"9","firefox":"52","safari":"8","ucandroid":"1"}
  transform-es2015-object-super {"android":"30","chrome":"35","explorer":"9","safari":"8","ucandroid":"1"}
  transform-es2015-parameters {"android":"30","chrome":"35","explorer":"9","firefox":"52","safari":"8","ucandroid":"1"}
  transform-es2015-shorthand-properties {"android":"30","chrome":"35","explorer":"9","safari":"8","ucandroid":"1"}
  transform-es2015-spread {"android":"30","chrome":"35","explorer":"9","safari":"8","ucandroid":"1"}
  transform-es2015-sticky-regex {"android":"30","chrome":"35","explorer":"9","safari":"8","ucandroid":"1"}
  transform-es2015-typeof-symbol {"android":"30","chrome":"35","explorer":"9","safari":"8","ucandroid":"1"}
  transform-es2015-unicode-regex {"android":"30","chrome":"35","explorer":"9","safari":"8","ucandroid":"1"}
  transform-exponentiation-operator {"android":"30","chrome":"35","explorer":"9","safari":"8","ucandroid":"1"}
  syntax-trailing-function-commas {"android":"30","chrome":"35","explorer":"9","safari":"8","ucandroid":"1"}
[!] (babel plugin) Error: It looks like your Babel configuration specifies a module transformer. Please disable it. See https://github.com/rollup/rollup-plugin-babel#configuring-babel for more information
src/index.js

U'd have to share a repository with the issue reproduced, without it I'm not being able to tell what's the culprit.

babel-preset-airbnb adds commonjs transform too. You have to disable it.

Many thanks Mateusz!

Not a problem 😃


Running with "hlx run" fails with "Could not find Markdown" error and 404

fstab.json points to the an adobe.sharepoint.com URL which requires a login and permission, not sure if that's ok:
https://adobe.sharepoint.com/sites/TheBlog/Shared Documents/theblog?csf=1&e=8Znxth
Opening that URL with my Adobe credentials says "You need permission to access this item".
If I try to run theblog with "hlx run" I get this error which looks related and http://localhost:3000 returns a 404:

[hlx] error: Could not find Markdown at https://adobeioruntime.net/api/v1/web/helix/helix-services/word2md@latest?rid=auACneEt2mwwuW29wnzHvl6EyuUu%2BKTf&src=helix%2Fgithub.com--davidnuescheler--theblog%2Fmaster&path=%2Findex.docx&shareLink=https%3A%2F%2Fadobe.sharepoint.com%2Fsites%2FTheBlog%2FShared%2520Documents%2Ftheblog%3Fcsf%3D1%26e%3D8Znxth

There is no index.docx at the root folder. This is work in progress (see #17).
Check https://github.com/davidnuescheler/theblog#the-blog for working urls.


Release version 1.0.0

Since we would like to release version 1.0.0 soon, please help to list the issues which must be fixed before we can release it. Please also mark the process, such as on-going, in PR, merged into dev-master, etc.

#534 fixed the build process while enabling CUDA. It must be merged before release. Tag @hunghaoti for notification.

https://github.com/Cytnx-dev/Cytnx/pull/528/commits/562f093c2d00b4bf39f1e5643bca973fb1174613 marks a public (but may not be an API) function as deprecated. We may also want to cherry-pick the commit.

#534 fixed the build process while enabling CUDA. It must be merged before release. Tag @hunghaoti for notification.

I have merged it.

[[deprecated]] attribute

Please ignore the comments I left above. Per the offline discussion, we are putting our C++ API into unstable mode. We will change the C++ API without notification, which means changing the C++ API will not need to pump the version up and will not block this release.

We made some changes in the API, which should also be changed in the API documentation. These are:

Contract, Contracts are merged into Contract
Contract_, Contracts_ are merged into Contract_
.relabel, .relabels are merged into .relabel
.relabel_, .relabels_ are merged into .relabel_
Svd_truncate has an additional optional argument min_blockdim to define a minimum dimension for each block

The code examples need to be changed accordingly such that all code works with version 1.0

I will write in the release note.


fix(onboard): remove extra multiplication of RP to avoid overflow

Closes #19884
(As debugged by @stuartcarnie) Retention policies in onboarding requests are already proper time.Durations, so multiplying by an extra time.Hour factor causes the values to be incorrect and potentially overflow.

[ ] CHANGELOG.md updated with a link to the PR (not the Issue)
[ ] Well-formatted commit messages
[ ] Rebased/mergeable
[ ] Tests pass
[ ] http/swagger.yml updated (if modified Go structs or API)
[ ] Feature flagged (if modified API)
[ ] Documentation updated or issue created (provide link to issue/pr)
[ ] Signed CLA (if not already signed)

@danxmoran you will need to update the onboarding unit tests:
service_onboarding_test.go:44: Onboarding: true
        onboarding.go:223: onboarding results are different -got/+want
            diff   (*influxdb.OnboardingResults)(
            - 	&{
            - 		User: &influxdb.User{ID: s"068ec83bbb042000", Name: "admin", Status: "active"},
            - 		Org: &influxdb.Organization{
            - 			ID:   s"7e98146b111fe339",
            - 			Name: "org1",
            - 			CRUDLog: influxdb.CRUDLog{
            - 				CreatedAt: s"2020-11-02 22:46:03.821569357 +0"...,
            - 				UpdatedAt: s"2020-11-02 22:46:03.821569544 +0"...,
            - 			},
            - 		},
            - 		Bucket: &influxdb.Bucket{
            - 			ID:              s"d218c3d8c079ca59",
            - 			OrgID:           s"7e98146b111fe339",
            - 			Name:            "bucket1",
            - 			RetentionPeriod: s"168ns",
            - 			CRUDLog: influxdb.CRUDLog{
            - 				CreatedAt: s"2020-11-02 22:46:03.821641188 +0"...,
            - 				UpdatedAt: s"2020-11-02 22:46:03.821641264 +0"...,
            - 			},
            - 		},
            - 		Auth: &influxdb.Authorization{
            - 			ID:          s"068ec83bcb7ad000",
            - 			Token:       "hA1O0tWXCHxSXdxqu0I25sDw4SEPlwayKmx0mpI833CZpGC2WAIcydbE95ANXnvM"...,
            - 			Status:      "active",
            - 			Description: "admin's Token",
            - 			OrgID:       s"7e98146b111fe339",
            - 			UserID:      s"068ec83bbb042000",
            - 			Permissions: []influxdb.Permission{
            - 				s"read:authorizations", s"write:authorizations", s"read:buckets",
            - 				s"write:buckets", ...,
            - 			},
            - 			CRUDLog: influxdb.CRUDLog{
            - 				CreatedAt: s"2020-11-02 22:46:03.821670074 +0"...,
            - 				UpdatedAt: s"2020-11-02 22:46:03.821670074 +0"...,
            - 			},
            - 		},
            - 	},

Note to self: Need to update CHANGELOG as well


Buyer beware: GD1144 badges are being sold as B1248 badges

After trawling offerings on eBay and AliExpress, there is definitely some funny business going on re: labeling and marketing of LED badges. Listings often show a unit with a 1248 pixels LED matrix, but then go on to describe a resolution of 1144.
In the case of the first batch of "b1248"s that I bought, they shipped in boxes claiming they were b1248 units. On inspection, they actually had a matrix of 11*44 pixels, and sure enough, on inspecting the internals, they were GD1144s (this was spelled out on the PCB).
The GD1144s seem to be flooding the market at present, at the lower cost end of the spectrum (<$15 USD). While this may be good for some (those who just want to scroll text or static images), it doesn't aid us with this project.
Simply put: it appears to be increasingly difficult to buy b1248's with confidence.
I might have to buy some b1236s if things don't work out obtaining genuine b1248s via eBay or AliExpress... but similar dodgy labelling may be at play with those smaller screen badges.
I really want to put your firmware to work, and as we've discussed, the GD1144 has a totally different circuit and the hardware is not compatible.

I imagine they will be harder to find as time goes on. Especially since it makes sense for the manufacturer to cost reduce (while only being outwardly similar).

Some cause for cautious optimism: the eBay seller who sold me the GD1144's labelled as b1248's is going to make amends by sending me another batch of (hopefully) the correct product. it could be 3 weeks or more before they arrive though. How does that mesh with your programming schedule?

I'll hopefully have something usable by then.

Excellent! I'll be sure to have some content ready to test the device to capacity. I think I'll focus on 2-bit imagery first.

For achieving high quality animation playback using bundled software with 2018-generation badges, I've had to forego a line and four columns of resolution in order to achieve the best available software and playback speed combo. The GD1144 does the job well with images loaded via MiniLED 9.92 software. What it CAN'T do is display 2-bit images (halftones).

@Danimations What USB serial driver works with these GD1144s?  I bought some in Huaqiangbei that were labeled b1248 and they came with a CD with PL2303 drivers, but the USB Vendor ID / Product ID don't match anything like PL2303 and upon internal inspection turn out to have the GD32F150 mcu.


MATLAB kernal for vscode-jupyter

Applies To

[x] Notebooks (.ipynb files)
[ ] Interactive Window and/or Cell Scripts (.py files with #%% markers)

What happened?
I can't start the MATLAB kernal for vscode-jupyter.
However, I can start a jupyter notebook server first and then connect to the exsiting sever successfully.
I hope that someone could sovel my problem

VS Code Version
1.90.1
Jupyter Extension Version
v2024.5.0
Jupyter logs
16:46:10.801 [info] Starting Kernel (Python Path: ~\AppData\Local\Programs\Python\Python38\python.exe, Unknown, 3.8.10) for 'd:\~\MATLAB\test.ipynb' (disableUI=false)
16:46:10.885 [info] Launching Raw Kernel MATLAB Kernel # python3
16:46:10.892 [warn] Failed to get activated env vars for ~\AppData\Local\Programs\Python\Python38\python.exe in 6ms
16:46:10.961 [info] Process Execution: python3 -m jupyter_matlab_kernel -f c:\Users\~\AppData\Roaming\jupyter\runtime\kernel-v2-10456sZYT6dxreasj.json
    > cwd: d:\~\MATLAB
16:46:11.040 [error] Disposing kernel process due to an error Error: The kernel died. Error: ... View Jupyter [log](command:jupyter.viewOutput) for further details.
    > Kernel Id = .jvsc74a57bd0d737386cadcd4604dd2f91820450be9b8af88eb737c8003ede15abd8ab989e9b#jupyter_matlab_kernel.c:\Users\~\AppData\Local\Programs\Python\Python38\python.exe.\.python3#-m#jupyter_matlab_kernel#-f#{connection_file}
    > Interpreter Id = c:\USERS\~\APPDATA\LOCAL\PROGRAMS\PYTHON\PYTHON38\PYTHON.EXE
    > at ChildProcess.<anonymous> (c:\Users\~\.vscode\extensions\ms-toolsai.jupyter-2024.5.0-win32-x64\dist\extension.node.js:309:44339)
    > stdErr =
16:46:11.041 [error]
16:46:11.043 [error] Failed to connect raw kernel session: Error: The kernel died. Error: ... View Jupyter [log](command:jupyter.viewOutput) for further details.
16:46:11.043 [error] Failed to connect raw kernel session: Error: The kernel died. Error: ... View Jupyter [log](command:jupyter.viewOutput) for further details.
16:46:11.043 [warn] Failed to shutdown kernel, .jvsc74a57bd0d737386cadcd4604dd2f91820450be9b8af88eb737c8003ede15abd8ab989e9b#jupyter_matlab_kernel.c:\Users\~\AppData\Local\Programs\Python\Python38\python.exe.\.python3#-m#jupyter_matlab_kernel#-f#{connection_file} [TypeError: Cannot read properties of undefined (reading 'dispose')
	at DT.shutdown (c:\Users\~\.vscode\extensions\ms-toolsai.jupyter-2024.5.0-win32-x64\dist\extension.node.js:314:13629)
	at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
	at async _T.shutdown (c:\Users\~\.vscode\extensions\ms-toolsai.jupyter-2024.5.0-win32-x64\dist\extension.node.js:314:22107)]
16:46:11.044 [warn] Error occurred while trying to start the kernel, options.disableUI=false Error: The kernel died. Error: ... View Jupyter [log](command:jupyter.viewOutput) for further details.
    > Kernel Id = .jvsc74a57bd0d737386cadcd4604dd2f91820450be9b8af88eb737c8003ede15abd8ab989e9b#jupyter_matlab_kernel.c:\Users\~\AppData\Local\Programs\Python\Python38\python.exe.\.python3#-m#jupyter_matlab_kernel#-f#{connection_file}
    > Interpreter Id = c:\USERS\~\APPDATA\LOCAL\PROGRAMS\PYTHON\PYTHON38\PYTHON.EXE
    > at ChildProcess.<anonymous> (c:\Users\~\.vscode\extensions\ms-toolsai.jupyter-2024.5.0-win32-x64\dist\extension.node.js:309:44339)
    > stdErr =
16:46:11.044 [warn] Kernel Error, context = start Error: The kernel died. Error: ... View Jupyter [log](command:jupyter.viewOutput) for further details.
    > Kernel Id = .jvsc74a57bd0d737386cadcd4604dd2f91820450be9b8af88eb737c8003ede15abd8ab989e9b#jupyter_matlab_kernel.c:\Users\~\AppData\Local\Programs\Python\Python38\python.exe.\.python3#-m#jupyter_matlab_kernel#-f#{connection_file}
    > Interpreter Id = c:\USERS\~\APPDATA\LOCAL\PROGRAMS\PYTHON\PYTHON38\PYTHON.EXE
    > at ChildProcess.<anonymous> (c:\Users\~\.vscode\extensions\ms-toolsai.jupyter-2024.5.0-win32-x64\dist\extension.node.js:309:44339)
    > stdErr =
16:46:11.058 [warn] Failed to get activated env vars for ~\AppData\Local\Programs\Python\Python38\python.exe in 13ms
16:46:11.064 [info] Process Execution: ~\AppData\Local\Programs\Python\Python38\python.exe -c "import ipykernel;print('6af208d0-cb9c-427f-b937-ff563e17efdf')"
16:46:11.303 [info] Dispose Kernel 'd:\~\MATLAB\test.ipynb' associated with 'd:\~\MATLAB\test.ipynb'
16:46:11.305 [error] Error in execution Error: The kernel died. Error: ... View Jupyter [log](command:jupyter.viewOutput) for further details.
    > Kernel Id = .jvsc74a57bd0d737386cadcd4604dd2f91820450be9b8af88eb737c8003ede15abd8ab989e9b#jupyter_matlab_kernel.c:\Users\~\AppData\Local\Programs\Python\Python38\python.exe.\.python3#-m#jupyter_matlab_kernel#-f#{connection_file}
    > Interpreter Id = c:\USERS\~\APPDATA\LOCAL\PROGRAMS\PYTHON\PYTHON38\PYTHON.EXE
    > at ChildProcess.<anonymous> (c:\Users\~\.vscode\extensions\ms-toolsai.jupyter-2024.5.0-win32-x64\dist\extension.node.js:309:44339)
    > stdErr =
16:46:11.305 [error] Error in execution (get message for cell) Error: The kernel died. Error: ... View Jupyter [log](command:jupyter.viewOutput) for further details.
    > Kernel Id = .jvsc74a57bd0d737386cadcd4604dd2f91820450be9b8af88eb737c8003ede15abd8ab989e9b#jupyter_matlab_kernel.c:\Users\~\AppData\Local\Programs\Python\Python38\python.exe.\.python3#-m#jupyter_matlab_kernel#-f#{connection_file}
    > Interpreter Id = c:\USERS\~\APPDATA\LOCAL\PROGRAMS\PYTHON\PYTHON38\PYTHON.EXE
    > at ChildProcess.<anonymous> (c:\Users\~\.vscode\extensions\ms-toolsai.jupyter-2024.5.0-win32-x64\dist\extension.node.js:309:44339)
    > stdErr =
16:46:11.312 [info] Process Execution: ~\AppData\Local\Programs\Python\Python38\python.exe -c "import ipykernel;print('6af208d0-cb9c-427f-b937-ff563e17efdf')"

Coding Language and Runtime Version
No response
Language Extension Version (if applicable)
No response
Anaconda Version (if applicable)
No response
Running Jupyter locally or remotely?
None

associated add support for matlab

@p1um3r Can you try installing matlab in a virtual environment and see if you still run into this same issue?
Also, please can you share the install steps for matlab (that you have used) on Windows

This issue has been closed automatically because it needs more information and has not had recent activity. See also our issue reporting guidelines.
Happy Coding!


Authentication error while testing my application.

Hi,
I am using django-rest-framework-social-oauth2 along with django rest framework to develop an app. All was running well and good but when it came to testing the code, I found a bizzare error.
At the start of my testing code, I created a superuser and an application registered to him. Afterwards, I called the /auth/convert-token endpoint with my facebook access token. While it did return me an access_token, subsequent calling of other endpoints with this returned access_token always failed with the message,
"Authentication credentials were not provided"
I tried to investigate it by placing breakpoints in the function create_token of rest_framework_social_oauth2.views where I found that the AccessToken.objects.create call was not actually creating a new row in my test database (I found this by placing breakpoints after the call and investigating with external database viewer).
Note that this behavior is explicit to the testing code.
Can you please tell me what seems to be the problem here?
I am using django 1.8 with postgresql as backend and django-oauth-toolkit 0.8.1
and django-rest-framework-social-oauth2 0.0.8

Hello,
Does creating a token in the shell using the same lines as in convert_token works ?
Is convert_token returning an access and refresh token ?

Yeah.. as I told you, this problem is explicit to unit testing. Also, convert_token is returning the access_token and the refresh_token.
The problem as I understand is caused because the AccessToken and the RefreshToken model that is created is somehow not flushed into the test database. The Application model, however, works just fine. I don't know why this is the case though but I am beginning to think that this has something to do with the django oauth toolkit and not the rest framework social oauth. In any case, I am currently unable to test my app because of this.

Could you post here your test so I can reproduce ?

Here's my code. Note that the error happens in test_B_user_retrieve_details
from django.test import TestCase
from django.contrib.auth.models import User
from oauth2_provider.models import Application

access_token = ""

class UserCreateTestCase(TestCase):

    @classmethod
    def setUpClass(cls):
        # create Super user
        try:
            # do we already have a user?
            User.objects.get(username="admin")

        except User.DoesNotExist:
            User.objects.create(username="admin", first_name="admin",
                            last_name="admin", is_staff=True<EMAIL_ADDRESS>password="admin")

            Application.objects.create(name="MyApp", client_type="Public",
                                       authorization_grant_type="Resource owner password-based", user_id=1)

        super(UserCreateTestCase, cls).setUpClass()

    def test_A_get_access_token(self):
        """
        Register a valid facebook user here
        """
        valid_access_token = <valid_access_token>
        header = "Bearer facebook-app " + valid_access_token

        # convert token
        res = self.client.get("/api/v1/auth/convert-token", {}, HTTP_AUTHORIZATION=header)
        print res.data

        self.assertIn('access_token', res.data, "Couldn't generate access_token")

	# save this access_token
        global access_token
        access_token = res.data['access_token']

    def test_B_user_retrieve_details(self):
            """
	    This always runs after the test_A_get_access_token..
            """
	    # Here /users/1 is an endpoint that returns the details about user. Nothing fancy, just a view that inherits from
	    # generics.RetrieveAPIView
        res = self.client.get("/users/1", {"access_token": access_token})
	    # Here, res.data, instead of containing information about the user, throws "Credential invalid" message
        print res.data

Here are the libraries that I am using.. (obtained from pip freeze)
Django==1.8.2
Jinja2==2.7.3
MarkupSafe==0.23
Pillow==2.9.0
PyJWT==1.3.0
PyYAML==3.11
Pygments==2.0.2
argparse==1.2.1
django-activity-stream==0.6.0
django-braces==1.8.0
django-debug-toolbar==1.3.0
django-jinja==1.4.1
django-jsonfield==0.9.13
django-oauth-toolkit==0.8.1
django-rest-framework-social-oauth2==0.0.8
django-rest-swagger==0.3.2
djangorestframework==3.1.3
djorm-ext-pgfulltext==0.10
elasticsearch==1.6.0
elasticsearch-dsl==0.0.4
httpie==0.9.2
httpsig==1.1.2
oauthlib==0.7.2
psycopg2==2.6
pycrypto==2.6.1
python-dateutil==2.4.2
python-openid==2.2.5
python-social-auth==0.2.10
pytz==2015.4
requests==2.7.0
requests-oauthlib==0.5.0
six==1.9.0
sqlparse==0.1.15
stream-django==1.2.4
stream-python==2.3.2
urllib3==1.10.4
wsgiref==0.1.2

I couldn't reproduce your issue but your tests are probably wrong.
First, if you're going to unittest, all your tests should be independent from each other: you need to get rid of this access_token global.
Second I see two mistakes in your code:
 Application.objects.create(name="MyApp", client_type="Public" should be  Application.objects.create(name="Owner", client_type="Public" and
res = self.client.get("/users/1", {"access_token": access_token}) should be
res = self.client.get("/users/1", {}, HTTP_AUTHORIZATION="Bearer " + access_token)

I don't understand why I must use
Application.objects.create(name="Owner", client_type="Public" instead of Application.objects.create(name="MyApp", client_type="Public"
Also, using
res = self.client.get("/users/1", {}, HTTP_AUTHORIZATION="Bearer " + access_token)
only changed the error message.. now it says
{'status': 401, 'message': u'Invalid token header. No credentials provided.'}
I agree when you say that unit tests are meant to be independent but in this particular case, I had to make an exception.

I am curious though, what did you get when you tried reproducing this code??

Owner corresponds to the default value of the PROPRIETARY_APPLICATION_NAME setting.
If you want to name your application otherwise you need to define this setting.
This is prone to change anyway as it is not flexible enough.
Regarding the tests, they passed. Which authentication classes did you enabled for your view ?

Did you manage to get this to work ?

The authentication classes that I enabled are OAuth2Authetication and SocialAuthentication.
And as for managing to getting it work, I couldn't. Anyways, I am closing this issue because I don't think it pertains to this particular library. Many thanks for your replies.

@PraveshKoirala I am facing the same issue. Did you ever find the solution for it?

Forgot about it but maybe move the convert-token code to setUp method? It was probably due to the nature of the unit tests being self-contained (i.e. inside a transaction)... Give it a try maybe.

If you have similar problem this is what Ive discovered: while testing DRF (and most likely django also) creates an empty test database, you can see it after all tests was completed it prints
Destroying test database for alias 'default'...
So what I did for my tests is made a base class with a method that creates a user, token and then
client.credentials(HTTP_AUTHORIZATION='Token ' + token)

and then inherited it in every test class. You can also do it in the setUp() method, but I had many test classes so I did this way so that I don't need to write it several times.


IRazorViewEngine.FindView Precompiled Views and Non compiled views different behaviours

Is this a Bug or Feature request?:
Bug
Steps to reproduce (preferrably a link to a GitHub repo with a repro project):

Have a view in a non root path (/Views/Controller/View).
Use FindView with a Path like: 'MyTemplates/MyView' which isn't in the default paths.
When the view is not compile, it finds a View. When its compiled no.

Description of the problem:
The reason is the path that it tests. When it isn't compiled, it test 'Views//MyTemplates/MyView.cshtml' and the File methods its uses can succesfully find the view. But when its compiled, it can't find it, as it isn't a correct Path.
Version of Microsoft.AspNetCore.Mvc or Microsoft.AspNetCore.App or Microsoft.AspNetCore.All:
2.0.6
Correction
They must behave the same, and probably the precompiled behaviour is the good one, as Views//Controller/View is not a correct path. Its pretty annoying to have different behaviours when publishing.

Likely a dup of https://github.com/aspnet/Mvc/issues/7535. See my comments here - https://github.com/aspnet/Mvc/issues/7535#issuecomment-375738070. Does that help?

I have no issue here, I just changed ViewLocationFormats and its ok. The actual issue is the different behavior between compiled and no compiled views. This is because when you are working on visual studio you think it works as it can find views with a double slash (because there's no controller) but, when you publish, it stops working, which can be a hard issue to find. Especially for new Net developers.

The actual issue is the different behavior between compiled and no compiled views.

Yup, we addressed the differences as part of the 2.1.0 release. More pertinently, as of 2.1.0, in the default case, views are compiled as part of build. If there are other issues in this area that we haven't addressed they should show up during your regular dev builds.

Closing this as a dupe.


Show equivalent pytest command

This is just a quick change to help users trouble-shoot problems with pytest.  When there is a failure, we print out the command they can run at the shell to duplicate the error.

Testing failures of code coverage


Spellcheck

Was trying to turn off my brain, so I ran https://github.com/EWSoftware/VSSpellChecker on the solution.
There are some whitespace trimming diffs, so looking at it with the ?w=1 might be a good idea.
This is mostly just comment fixes in the unit tests, but the XSD changes might have an affect on the translations.

@nschonni,
Thanks for your contribution.
To ensure that the project team has proper rights to use your work, please complete the Contribution License Agreement at https://cla2.dotnetfoundation.org.
It will cover your contributions to all .NET Foundation-managed open source projects.
Thanks,
.NET Foundation Pull Request Bot

@nschonni, thanks for signing the contribution license agreement. We will now validate the agreement and then the pull request.
Thanks, .NET Foundation Pull Request Bot

Thanks for the contribution!


RTL indicator back to start after clicking space

Hello
When enabling force RTL in flutter gallery app I have founded two issue
When clicking space the indicator back to the start
When long pressing on the text input field I got a bad state error ( I think this error related to the first one).
Please see my explanation video.
https://drive.google.com/file/d/16wujF0f5KcqT71mybRbsDafWks86T_f1/view?usp=drivesdk

cc @jason-simmons I believe you have worked with the bidi code? Thoughts?

I believe this is symptomatic of a larger issue of how we handle RTL languages.
Consider the following tests for bounding rects:

RTL version:

I'll file a more broad bug for RTL handling.

Thanks Gary,
Do you have any suggestions to work around this issue before it's been fixed in Flutter, our app is in production stage and it will target mainly Arabs users ( RTL ) .

The issue #17087 is actually the same problem. This is another way of producing the same problem.
The problem is in this line:
https://github.com/flutter/flutter/blob/7ce28d1277056e2471b323e3f1ff45a8d43731ca/packages/flutter/lib/src/rendering/editable.dart#L931
Explanation: After a long press (in a way that causes a selection to a white space), The property selection.isCollapsed is returning true (because selection.start != selection.end). However, the getBoxesForSelection is not returning any boxes (I'm assuming because it is white space) and the two lines following the one referenced above are trying to access the first and last boxes which is an error.
Possible solutions:

Changing getBoxesForSelection to return the box containing the white space.
Changing selection.isCollapsed to take into consideration the cases that will make getBoxesForSelection not return any box.

I hope this will help solving this issue faster.
Thank you

We have since landed multiple changes that improve handling of RTL carets. Please verify if this fixed.

The two problems described above has been solved but I think solving them cause other problem.
Now when you write Arabic words and try to delete them, everything works fine, but if you tried to write English words then try to delete them flutter will be stuck after deleting one word and will never respond to the delete button from the keyboard.
The problem appears on a physical device as well as on the Android emulator.
The following video describes the problem.
Flutter Version
[√] Flutter: is fully installed. (Channel master, v1.18.0-9.0.pre.14, on Microsoft Windows [Version 10.0.17763.805],
    locale en-US)
[√] Android toolchain - develop for Android devices: is fully installed. (Android SDK version 29.0.1)
[√] Chrome - develop for the web: is fully installed.
[√] Android Studio: is fully installed. (version 3.5)
[√] IntelliJ IDEA Community Edition: is fully installed. (version 2019.1)
[√] VS Code: is fully installed. (version 1.44.2)
[√] Connected device: is fully installed. (3 available)

Sample Code
import 'package:flutter/material.dart';
import 'package:flutter_localizations/flutter_localizations.dart';

void main() => runApp(MyApp());

class MyApp extends StatelessWidget {
  @override
  Widget build(BuildContext context) {
    return MaterialApp(
      localizationsDelegates: [
        GlobalMaterialLocalizations.delegate,
        GlobalWidgetsLocalizations.delegate,
      ],
      supportedLocales: [Locale("ar")],
      locale: Locale("ar"),
      home: Scaffold(
        appBar: AppBar(),
        body: Padding(
          padding: EdgeInsets.all(8),
          child: TextField(),
        ),
      ),
    );
  }
}

I believe this PR: https://github.com/flutter/engine/pull/17960 is being worked on to handle deleting better, although I thought @alimahdiyar 's previous patch resolved deleting arabic/english mixes.

@FlutterIODev Yeah, I was able to repro that bug. Let me file another issue on it and track it separately. We should close this one as the original reported bug is fixed.

Let's continue work to resolve the new issue here: https://github.com/flutter/flutter/issues/56149


[Spring] Add Application Live View and Dev Tool Portal

This checklist is used to make sure that common guidelines for a pull request are followed.

For new extensions:

[x] My extension description/summary conforms to the Extension Summary Guidelines.

About Extension Publish
There is a pipeline to automatically build, upload and publish extension wheels.
Once your pull request is merged into main branch, a new pull request will be created to update src/index.json automatically.
The precondition is to put your code inside this repository and upgrade the version in the pull request but do not modify src/index.json.

Spring

Will update change log and set up together with #5504 and #5457

Update version and changelog in #5532

May I ask why all tests are mock tests. Could you add some scenario tests for these new commands?

May I ask why all tests are mock tests. Could you add some scenario tests for these new commands?

Added


feat: upgrade cdk pipeline(Typescript) to use modern api.

Announcing CDK Pipelines GA, CI/CD for CDK Apps. With this launch CDK pipelines have support for modern API. We have updated the modern API to be easier to work with and customize, and will be the preferred API going forward.
Fixes https://github.com/aws-samples/aws-cdk-intro-workshop/issues/261

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

@pankajagrawal16 Would you mind resolving the merge conflicts?


Adding Prism and generic ReproReferencedMetric base class for Repro metrics

In my Repro library I have functionality to run unit tests on-demand. Github Actions supports Docker, so when I merge a metric I first run the metric-specific unit tests with Github Actions on the CPU. Should I also add that here?

Sounds like a good idea, if it's not too hard to do 🤔


merge package from arlac77/npm-package-template

package.json

chore(package<EMAIL_ADDRESS>

Codecov Report

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

@@          Coverage Diff          @@
##           master   #347   +/-   ##
=====================================
  Coverage      75%    75%
=====================================
  Files           1      1
  Lines           8      8
=====================================
  Hits            6      6
  Misses          2      2

Continue to review full report at Codecov.

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

Coverage remained the same at 70.0% when pulling fa122e12f8b1e9fdad67d21b881b5f8c5fff312b on template-sync-1 into 5ea9675a1bc5fc9391abb8ddd4d3e549b0424fec on master.


Implemented a housing price case

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


FR: Autocorrect should ignore "Extra Auto-Correct Source Files"

Is Your Feature Request Related to a Problem? Please Describe.
The auto-correct rule has an option to specify a file of custom words instead of (or in addition to) the builtin list of words. However if you run the linter on this file it switches all the "word to find" words with the replaced version which inherently removes that configuration in the first place. I have lint on ctrl+s and a muscle memory to just hit this after making changes to a file and didn't realize it was undoing my word list at first.
Describe the Solution You'd Like
The auto-correct rule should be completely skipped on any files that are set for Extra Auto-Correct Source Files. Or if it's not too much more complicated then it should ignore the table of words it's going to pull from to not destroy it's own configuration.

Hey @jjspace . Thanks for the input. Could you explain why the current ways of ignoring a file or turning off linting for a part of file (ranged ignored) are not adequate to handle this scenario?
If the intent is to have this automatic, would it make sense to just auto-ignore these files?
Ignoring for a single rule is not how the logic is designed at this time unless you use the disabled key in the YAML. It is theoretically possible to ignore a single rule if they are one of the files that are storing the configuration for extra auto-correct words, but unless it is well documented this will likely confuse people. Could you explain how you would propose that the user be informed of the fact that the files that are in the list would only have auto-correct mispellings disabled automatically?
Thanks for helping me think through this.

Could you explain why the current ways of ignoring a file or turning off linting for a part of file (ranged ignored) are not adequate to handle this scenario?

I didn't realize that there was a setting to ignore files, I'm sure others will miss that too. Even with that what if I want to use the other rules, like updating the properties for last edited date and stuff? I don't want to completely ignore the file. The ranged ignore could work but what if I want it to still autoformat the table?
But in general, why should it require the user to take extra actions to prevent the rule from breaking in the first place?

If the intent is to have this automatic, would it make sense to just auto-ignore these files?

This would be a way to do it, I think the best way would be to ignore those specific files from specifically this rule.
I think in the larger context this whole "create a table in a file somewhere" feels like abusing the system a little bit. This sort of configuration should live in the settings itself but that's probably a much larger change

Ignoring for a single rule is not how the logic is designed at this time unless you use the disabled key in the YAML

It sounds like the logic to ignore a single rule for a specific file is already implemented, I think this would just be forced on for the auto-correct rule on these specific files?

Could you explain how you would propose that the user be informed of the fact that the files that are in the list would only have auto-correct mispellings disabled automatically?

I think adding a single extra line under the "Extra ... Files" setting that says something like this would be enough:

These are files that have a markdown table in them that have the initial word and the word to correct it to (these are case insensitive corrections). Note: the tables used should have the starting and ending | indicators present for each line.
Files included in this list will not have auto-correct applied to them.

Could you explain why the current ways of ignoring a file or turning off linting for a part of file (ranged ignored) are not adequate to handle this scenario?

I didn't realize that there was a setting to ignore files, I'm sure others will miss that too. Even with that what if I want to use the other rules, like updating the properties for last edited date and stuff? I don't want to completely ignore the file. The ranged ignore could work but what if I want it to still autoformat the table? But in general, why should it require the user to take extra actions to prevent the rule from breaking in the first place?

The main issue with doing something without the user knowing is that it should be obvious that the change would apply. Since there is no current way to ignore a specific rule for a specific file minus what is done in the frontmatter for rules being disabled it does not seem intuitive to me that a user would expect the rule to be auto disabled for the files as that would imply that the Linter may be doing the same for other files which is false. That is the main reason, beyond assuming users would store these files in a location that would not be linted/would be ignored by the Linter like templates. I am not opposed to doing it in this case so long as users are made aware of this change.

If the intent is to have this automatic, would it make sense to just auto-ignore these files?

This would be a way to do it, I think the best way would be to ignore those specific files from specifically this rule. I think in the larger context this whole "create a table in a file somewhere" feels like abusing the system a little bit. This sort of configuration should live in the settings itself but that's probably a much larger change

While I do agree to some extent that this feature would be nice to ingrain in the settings themselves, it was specifically asked that the custom auto-correct values be kept in a file in the vault. This allows users to better handle what rules they want disabled versus enabled by handling versioning and other more complex setups on their own. At this point, it would be a breaking change to change this which I am not necessarily opposed to doing, but I would want more than 1 opinion on this if a change were to be made to make this easier for users.

Ignoring for a single rule is not how the logic is designed at this time unless you use the disabled key in the YAML

It sounds like the logic to ignore a single rule for a specific file is already implemented, I think this would just be forced on for the auto-correct rule on these specific files?

That is not entirely true. In concept, it exists. However it is never auto-on because that would lead to confusion as to which rules are on and which are off for certain files. That is why I much prefer that the user specify the value in the YAML that they want the rule disabled for the file (better yet would be to list them like templates and add them to the ignored folder/file list). But if there is a good enough way to make this clear and obvious to the users, I am not opposed to auto turning off the auto-correct rule for these config files.

Could you explain how you would propose that the user be informed of the fact that the files that are in the list would only have auto-correct mispellings disabled automatically?

I think adding a single extra line under the "Extra ... Files" setting that says something like this would be enough:

These are files that have a markdown table in them that have the initial word and the word to correct it to (these are case insensitive corrections). Note: the tables used should have the starting and ending | indicators present for each line.
Files included in this list will not have auto-correct applied to them.

This proposal is possible. I would likely need to include that text in yellow since it is a warning to users. But it could be added.

I am including a warning and working on logic to not run the auto-correct rule on the custom auto-correct files. I will hopefully have something for the next release.

The changes for this have been merged into master and should go out in the next release. Please let us know if there are issues on master or in the next release. Thanks for the input on this feature!


refactor(generator): move schema fixes into adhesives

No-op, with #138 we'll have another 'adhesive' that fixes a bunch of things around the openapi spec, this PR collects these fixes into an adhesives directory.

rebased following #141

Alright, patches might be a better name, let me change that

rebased.


Include beta indicator on Appwrite Cloud

What does this PR do?
To help emphasize Appwrite Cloud is still in beta
Test Plan
Cloud
Navbar Desktop

Navbar Mobile

Sign In Desktop

Sign In Mobile

Self-hosted
Navbar

Login

Related PRs and Issues
None
Have you read the Contributing Guidelines on issues?
Yes

@stnguyen90 I can't login, how does all of that look on mobile?

@eldadfux I've added screenshots of mobile.


HNC: Update kubectl hns config set-type to allow force updating

Part of #1102, #1076
Changing the sync mode to Propagate may cause source object overwriting. The HNCConfig webhook will deny such requests, but we will allow user to fix it quickly with a force update.
We can achieve it in either of the two ways (depending on which is easier to implement):

Add a confirmation prompt that users can say yes to proceed (as suggested in https://github.com/kubernetes-sigs/multi-tenancy/issues/1102#issuecomment-692086619)
Add a --force flag that users can use directly.

For either approach, we will first list the conflicts, show the warning and a link to the doc.  Then we will tell user how to fix, e.g. rename objects and retry, answer yes to the confirmation prompt, or run kubectl hns config set-type --force.

/assign @GinnyJI
/cc @adrianludwin

@GinnyJI I believe this is done, correct?

Did we link to the doc as we said we would?

fixed by #1169 .
Doc link -  http://bit.ly/hnc-propagation-conflict


Move RegisterAggregator implementation

The SQLiteConn.RegisterAggregator implementation was defined in
sqlite3_trace.go file, which is guarded with a build constraint. This
change simply moves RegisterAggregator to the main sqlite3.go file,
and moves accompanying unit tests.
The rationale for this move is that it was not possible for downstream
using packages to use RegisterAggregator without also specifying (and
notifying the user) the 'trace' build tag.

It's worth noting that (philosophically) this should probably be used/tested in the same place as RegisterFunc. Also, worth mentioning is that the additional GOTAGS=trace environment in the travis-ci configuration is no longer necessary, as the *_trace_test.go only tested the RegisterAggregator func.

Coverage increased (+2.2%) to 68.903% when pulling 7174000f779db8d51c898c082640cb2f475cd8d3 on kenshaw:move-registeraggregator into 615c193e01d8d462eef7ee390171506f531a1c9a on mattn:master.

Just bumping this to determine if this will be merged or not. If there is anything that I need to change in this PR to get it included, please let me know. Thanks!

LGTM. I'll check more something for merge.

Thank you!

Thanks for the merge -- really appreciate all the work you do @mattn on this project and others. Cheers!


🐛 !Bug Report: Issue#1222 Seems to be Working Fine

📜 Description
In an attempt to recreate the highlighted bug in issue#1222 (https://github.com/arc53/DocsGPT/issues/1222), I soon realized the bug had already been fixed earlier by @ManishMadan2882.
👟 Reproduction steps
Please follow the provided reproduction steps in issue#1222 (https://github.com/arc53/DocsGPT/issues/1222)
👍 Expected behavior
The highlighted behavior in issue#1222
👎 Actual Behavior with Screenshots
Please have a look at the video review: https://drive.google.com/file/d/1kWsnrlGWnIHathFUjMEJaxEPOuDEuoQI/view?usp=sharing
💻 Operating system
Linux
What browsers are you seeing the problem on?
No response
🤖 What development environment are you experiencing this bug on?
Docker
🔒 Did you set the correct environment variables in the right path? List the environment variable names (not values please!)
No response
📃 Provide any additional context for the Bug.
No response
📖 Relevant log output
No response
👀 Have you spent some time to check if this bug has been raised before?

[X] I checked and didn't find similar issue

🔗 Are you willing to submit PR?
None
🧑⚖ Code of Conduct

[X] I agree to follow this project's Code of Conduct

Hi @utin-francis-peter,
Just tested on the docker deployment main (Chrome, MacOS).

Try typing this as the input:
AaaaaaaaaaaaaaaaaaaAaaaaaaaaaaaaaaaaaaAaaaaaaaaaaaaaaaaaaAaaaaaaaaaaaaaaaaaaAaaaaaaaaaaaaaaaaaaAaaaaaaaaaaaaaaaaaaAaaaaaaaaaaaaaaaaaaAaaaaaaaaaaaaaaaaaaAaaaaaaaaaaaaaaaaaaAaaaaaaaaaaaaaaaaaaAaaaaaaaaaaaaaaaaaaAaaaaaaaaaaaaaaaaaaAaaaaaaaaaaaaaaaaaaAaaaaaaaaaaaaaaaaaaAaaaaaaaaaaaaaaaaaaAaaaaaaaaaaaaaaaaaaAaaaaaaaaaaaaaaaaaaAaaaaaaaaaaaaaaaaaaAaaaaaaaaaaaaaaaaaaAaaaaaaaaaaaaaaaaaaAaaaaaaaaaaaaaaaaaaAaaaaaaaaaaaaaaaaaaAaaaaaaaaaaaaaaaaaaAaaaaaaaaaaaaaaaaaaAaaaaaaaaaaaaaaaaaaAaaaaaaaaaaaaaaaaaaAaaaaaaaaaaaaaaaaaaAaaaaaaaaaaaaaaaaaaAaaaaaaaaaaaaaaaaaaAaaaaaaaaaaaaaaaaaaAaaaaaaaaaaaaaaaaaaAaaaaaaaaaaaaaaaaaaAaaaaaaaaaaaaaaaaaaAaaaaaaaaaaaaaaaaaaAaaaaaaaaaaaaaaaaaaAaaaaaaaaaaaaaaaaaaAaaaaaaaaaaaaaaaaaaAaaaaaaaaaaaaaaaaaaAaaaaaaaaaaaaaaaaaaAaaaaaaaaaaaaaaaaaaAaaaaaaaaaaaaaaaaaa

Hi @utin-francis-peter
I submitted the fix for long sentences basically tested it for code snippets in the input, but I think it fails for long words as mentions in #1222
Thanks!


Integration test error: Execution failed for task ':distDocker'. "Could not find property 'jar' on task ':docker'

I have run

./gradlwe build

and it fails with these errors.
Also, I tried to go to the example/simple folder and run the following command:

./gradlew docker

But it fails too, providing this message "Could not find property 'jar' on task ':docker'

I cannot see any faults with this when running locally.
Can you provide some more info on your environment and stack Trace/info mode on gradle build?

I have downloaded the source code in a zip file. I have decompressed it and I have run ./gradlew build .Then, the errors appeared.
This is the information you requested:

openjdk version "1.8.0_131"
OpenJDK Runtime Environment (build 1.8.0_131-8u131-b11-0ubuntu<IP_ADDRESS>-b11)
OpenJDK 64-Bit Server VM (build 25.131-b11, mixed mode)

Any idea?

yes, by using the zip download I managed to reproduce your error. This created an folder called gradle-docker-master. This has one big problem, the artifact published to maven local will then be called gradle-docker-master instead of gradle-docker as it is supposed to be named.
If you download the zip, it seems you must make sure the unpacked folder is called gradle-docker. In that case it worked for me.
Could you try this?

I have tried this and you are right. If I renamed the folder to gradle-docker it works. Thank you very much!


Use Directory.Build.props instead of Common.proj

@slide Any idea why test_codecs would fail on Travis? Is there a Mono update?