add uptime robot

Execution result of "run-all plan" in "infrastructure/cloud"
time=2023-10-26T21:00:17Z level=error msg=Error: Error in function call

 prefix=[/github/workspace/infrastructure/cloud/b2/bucket]
time=2023-10-26T21:00:17Z level=error msg=  on /github/workspace/infrastructure/terragrunt.hcl line 19, in locals:
 prefix=[/github/workspace/infrastructure/cloud/b2/bucket]
time=2023-10-26T21:00:17Z level=error msg=  19:   uptime_robot_api_key = get_env("UPTIME_ROBOT_API_KEY")
 prefix=[/github/workspace/infrastructure/cloud/b2/bucket]
time=2023-10-26T21:00:17Z level=error msg=
 prefix=[/github/workspace/infrastructure/cloud/b2/bucket]
time=2023-10-26T21:00:17Z level=error msg=Call to function "get_env" failed: EnvVarNotFound: Required environment variable
UPTIME_ROBOT_API_KEY - not found.

 prefix=[/github/workspace/infrastructure/cloud/b2/bucket]
time=2023-10-26T21:00:17Z level=error msg=Encountered error while evaluating locals in file /github/workspace/infrastructure/terragrunt.hcl prefix=[/github/workspace/infrastructure/cloud/b2/bucket]
time=2023-10-26T21:00:17Z level=error msg=Error processing module at '/github/workspace/infrastructure/cloud/b2/bucket/terragrunt.hcl'. How this module was found: Terragrunt config file found in a subdirectory of /github/workspace/infrastructure/cloud. Underlying error: /github/workspace/infrastructure/terragrunt.hcl:19,26-34: Error in function call; Call to function "get_env" failed: EnvVarNotFound: Required environment variable UPTIME_ROBOT_API_KEY - not found.
time=2023-10-26T21:00:17Z level=error msg=Unable to determine underlying exit code, so Terragrunt will exit with error code 1

Execution result of "run-all plan" in "infrastructure/cloud"
time=2023-10-26T21:07:08Z level=error msg=Error: Error in function call

 prefix=[/github/workspace/infrastructure/cloud/b2/bucket]
time=2023-10-26T21:07:08Z level=error msg=  on /github/workspace/infrastructure/terragrunt.hcl line 19, in locals:
 prefix=[/github/workspace/infrastructure/cloud/b2/bucket]
time=2023-10-26T21:07:08Z level=error msg=  19:   uptime_robot_api_key = get_env("UPTIME_ROBOT_API_KEY")
 prefix=[/github/workspace/infrastructure/cloud/b2/bucket]
time=2023-10-26T21:07:08Z level=error msg=
 prefix=[/github/workspace/infrastructure/cloud/b2/bucket]
time=2023-10-26T21:07:08Z level=error msg=Call to function "get_env" failed: EnvVarNotFound: Required environment variable
UPTIME_ROBOT_API_KEY - not found.

 prefix=[/github/workspace/infrastructure/cloud/b2/bucket]
time=2023-10-26T21:07:08Z level=error msg=Encountered error while evaluating locals in file /github/workspace/infrastructure/terragrunt.hcl prefix=[/github/workspace/infrastructure/cloud/b2/bucket]
time=2023-10-26T21:07:08Z level=error msg=Error processing module at '/github/workspace/infrastructure/cloud/b2/bucket/terragrunt.hcl'. How this module was found: Terragrunt config file found in a subdirectory of /github/workspace/infrastructure/cloud. Underlying error: /github/workspace/infrastructure/terragrunt.hcl:19,26-34: Error in function call; Call to function "get_env" failed: EnvVarNotFound: Required environment variable UPTIME_ROBOT_API_KEY - not found.
time=2023-10-26T21:07:08Z level=error msg=Unable to determine underlying exit code, so Terragrunt will exit with error code 1

Execution result of "run-all plan" in "infrastructure/cloud"
time=2023-10-26T21:07:43Z level=error msg=Error: Error in function call

 prefix=[/github/workspace/infrastructure/cloud/b2/bucket]
time=2023-10-26T21:07:43Z level=error msg=  on /github/workspace/infrastructure/terragrunt.hcl line 19, in locals:
 prefix=[/github/workspace/infrastructure/cloud/b2/bucket]
time=2023-10-26T21:07:43Z level=error msg=  19:   uptime_robot_api_key = get_env("UPTIME_ROBOT_API_KEY")
 prefix=[/github/workspace/infrastructure/cloud/b2/bucket]
time=2023-10-26T21:07:43Z level=error msg=
 prefix=[/github/workspace/infrastructure/cloud/b2/bucket]
time=2023-10-26T21:07:43Z level=error msg=Call to function "get_env" failed: EnvVarNotFound: Required environment variable
UPTIME_ROBOT_API_KEY - not found.

 prefix=[/github/workspace/infrastructure/cloud/b2/bucket]
time=2023-10-26T21:07:43Z level=error msg=Encountered error while evaluating locals in file /github/workspace/infrastructure/terragrunt.hcl prefix=[/github/workspace/infrastructure/cloud/b2/bucket]
time=2023-10-26T21:07:43Z level=error msg=Error processing module at '/github/workspace/infrastructure/cloud/b2/bucket/terragrunt.hcl'. How this module was found: Terragrunt config file found in a subdirectory of /github/workspace/infrastructure/cloud. Underlying error: /github/workspace/infrastructure/terragrunt.hcl:19,26-34: Error in function call; Call to function "get_env" failed: EnvVarNotFound: Required environment variable UPTIME_ROBOT_API_KEY - not found.
time=2023-10-26T21:07:43Z level=error msg=Unable to determine underlying exit code, so Terragrunt will exit with error code 1

Execution result of "run-all plan" in "infrastructure/cloud"
time=2023-10-26T21:10:17Z level=error msg=Error: Error in function call

 prefix=[/github/workspace/infrastructure/cloud/b2/bucket]
time=2023-10-26T21:10:17Z level=error msg=  on /github/workspace/infrastructure/terragrunt.hcl line 19, in locals:
 prefix=[/github/workspace/infrastructure/cloud/b2/bucket]
time=2023-10-26T21:10:17Z level=error msg=  19:   uptime_robot_api_key = get_env("UPTIME_ROBOT_API_KEY")
 prefix=[/github/workspace/infrastructure/cloud/b2/bucket]
time=2023-10-26T21:10:17Z level=error msg=
 prefix=[/github/workspace/infrastructure/cloud/b2/bucket]
time=2023-10-26T21:10:17Z level=error msg=Call to function "get_env" failed: EnvVarNotFound: Required environment variable
UPTIME_ROBOT_API_KEY - not found.

 prefix=[/github/workspace/infrastructure/cloud/b2/bucket]
time=2023-10-26T21:10:17Z level=error msg=Encountered error while evaluating locals in file /github/workspace/infrastructure/terragrunt.hcl prefix=[/github/workspace/infrastructure/cloud/b2/bucket]
time=2023-10-26T21:10:17Z level=error msg=Error processing module at '/github/workspace/infrastructure/cloud/b2/bucket/terragrunt.hcl'. How this module was found: Terragrunt config file found in a subdirectory of /github/workspace/infrastructure/cloud. Underlying error: /github/workspace/infrastructure/terragrunt.hcl:19,26-34: Error in function call; Call to function "get_env" failed: EnvVarNotFound: Required environment variable UPTIME_ROBOT_API_KEY - not found.
time=2023-10-26T21:10:17Z level=error msg=Unable to determine underlying exit code, so Terragrunt will exit with error code 1

Execution result of "run-all plan" in "infrastructure/cloud"
time=2023-10-26T21:12:27Z level=error msg=Error: Error in function call

 prefix=[/github/workspace/infrastructure/cloud/b2/bucket]
time=2023-10-26T21:12:27Z level=error msg=  on /github/workspace/infrastructure/terragrunt.hcl line 19, in locals:
 prefix=[/github/workspace/infrastructure/cloud/b2/bucket]
time=2023-10-26T21:12:27Z level=error msg=  19:   uptime_robot_api_key = get_env("UPTIME_ROBOT_API_KEY")
 prefix=[/github/workspace/infrastructure/cloud/b2/bucket]
time=2023-10-26T21:12:27Z level=error msg=
 prefix=[/github/workspace/infrastructure/cloud/b2/bucket]
time=2023-10-26T21:12:27Z level=error msg=Call to function "get_env" failed: EnvVarNotFound: Required environment variable
UPTIME_ROBOT_API_KEY - not found.

 prefix=[/github/workspace/infrastructure/cloud/b2/bucket]
time=2023-10-26T21:12:27Z level=error msg=Encountered error while evaluating locals in file /github/workspace/infrastructure/terragrunt.hcl prefix=[/github/workspace/infrastructure/cloud/b2/bucket]
time=2023-10-26T21:12:27Z level=error msg=Error processing module at '/github/workspace/infrastructure/cloud/b2/bucket/terragrunt.hcl'. How this module was found: Terragrunt config file found in a subdirectory of /github/workspace/infrastructure/cloud. Underlying error: /github/workspace/infrastructure/terragrunt.hcl:19,26-34: Error in function call; Call to function "get_env" failed: EnvVarNotFound: Required environment variable UPTIME_ROBOT_API_KEY - not found.
time=2023-10-26T21:12:27Z level=error msg=Unable to determine underlying exit code, so Terragrunt will exit with error code 1

Execution result of "run-all plan" in "infrastructure/cloud"
time=2023-10-26T21:15:09Z level=info msg=The stack at /github/workspace/infrastructure/cloud will be processed in the following order for command plan:
Group 1
- Module /github/workspace/infrastructure/cloud/b2/bucket
- Module /github/workspace/infrastructure/cloud/cloudflare/access
- Module /github/workspace/infrastructure/cloud/cloudflare/tunnel
- Module /github/workspace/infrastructure/cloud/uptime-robot/otaru

Group 2
- Module /github/workspace/infrastructure/cloud/cloudflare/dns

Initializing the backend...

Initializing the backend...

Initializing the backend...

Initializing the backend...

Successfully configured the backend "s3"! Terraform will automatically
use this backend unless the backend configuration changes.

Successfully configured the backend "s3"! Terraform will automatically
use this backend unless the backend configuration changes.

Successfully configured the backend "s3"! Terraform will automatically
use this backend unless the backend configuration changes.

Successfully configured the backend "s3"! Terraform will automatically
use this backend unless the backend configuration changes.

Initializing provider plugins...
- Finding vexxhost/uptimerobot versions matching "~> 0.8"...

Initializing provider plugins...
- Reusing previous version of cloudflare/cloudflare from the dependency lock file
- Reusing previous version of hashicorp/aws from the dependency lock file
- Reusing previous version of backblaze/b2 from the dependency lock file
- Reusing previous version of cloudflare/cloudflare from the dependency lock file
- Reusing previous version of integrations/github from the dependency lock file
- Reusing previous version of vexxhost/uptimerobot from the dependency lock file

Initializing provider plugins...
- Reusing previous version of integrations/github from the dependency lock file
- Reusing previous version of integrations/github from the dependency lock file
- Reusing previous version of vexxhost/uptimerobot from the dependency lock file
- Reusing previous version of hashicorp/aws from the dependency lock file
- Reusing previous version of hashicorp/aws from the dependency lock file
- Reusing previous version of backblaze/b2 from the dependency lock file

Initializing provider plugins...
- Finding vexxhost/uptimerobot versions matching "~> 0.8"...
- Reusing previous version of backblaze/b2 from the dependency lock file
- Reusing previous version of cloudflare/cloudflare from the dependency lock file
- Reusing previous version of hashicorp/aws from the dependency lock file
- Installing vexxhost/uptimerobot v0.8.2...
- Reusing previous version of backblaze/b2 from the dependency lock file
- Installing cloudflare/cloudflare v4.17.0...
- Reusing previous version of cloudflare/cloudflare from the dependency lock file
- Installing hashicorp/aws v5.21.0...
- Reusing previous version of integrations/github from the dependency lock file
- Installing vexxhost/uptimerobot v0.8.2...
- Installed vexxhost/uptimerobot v0.8.2 (self-signed, key ID 8FF00CD0B5FEAF59)
- Installing hashicorp/aws v5.21.0...
- Installed vexxhost/uptimerobot v0.8.2 (self-signed, key ID 8FF00CD0B5FEAF59)
- Installing hashicorp/aws v5.21.0...
- Installed cloudflare/cloudflare v4.17.0 (self-signed, key ID C76001609EE3B136)
- Installing integrations/github v5.40.0...
- Installed integrations/github v5.40.0 (signed by a HashiCorp partner, key ID 38027F80D7FD5FB2)
- Installing vexxhost/uptimerobot v0.8.2...
- Installed vexxhost/uptimerobot v0.8.2 (self-signed, key ID 8FF00CD0B5FEAF59)
- Installing hashicorp/aws v5.22.0...
- Installed hashicorp/aws v5.21.0 (signed by HashiCorp)
- Installing backblaze/b2 v0.8.4...
- Installed hashicorp/aws v5.21.0 (signed by HashiCorp)
- Installing backblaze/b2 v0.8.4...
- Installed hashicorp/aws v5.21.0 (signed by HashiCorp)
- Installing backblaze/b2 v0.8.4...
- Installed backblaze/b2 v0.8.4 (signed by a HashiCorp partner, key ID 83D9CAF4848490D6)
- Installing cloudflare/cloudflare v4.16.0...
- Installed backblaze/b2 v0.8.4 (signed by a HashiCorp partner, key ID 83D9CAF4848490D6)
- Installing cloudflare/cloudflare v4.16.0...
- Installed cloudflare/cloudflare v4.16.0 (self-signed, key ID C76001609EE3B136)
- Installed hashicorp/aws v5.22.0 (signed by HashiCorp)
- Installing backblaze/b2 v0.8.4...
- Installing integrations/github v5.40.0...
- Installed backblaze/b2 v0.8.4 (signed by a HashiCorp partner, key ID 83D9CAF4848490D6)
- Installing cloudflare/cloudflare v4.16.0...
- Installed cloudflare/cloudflare v4.16.0 (self-signed, key ID C76001609EE3B136)
- Installing integrations/github v5.40.0...
- Installed cloudflare/cloudflare v4.16.0 (self-signed, key ID C76001609EE3B136)
- Installed integrations/github v5.40.0 (signed by a HashiCorp partner, key ID 38027F80D7FD5FB2)
- Installing integrations/github v5.40.0...
- Installing vexxhost/uptimerobot v0.8.2...
- Installed integrations/github v5.40.0 (signed by a HashiCorp partner, key ID 38027F80D7FD5FB2)

Partner and community providers are signed by their developers.
If you'd like to know more about provider signing, you can read about it here:
https://www.terraform.io/docs/cli/plugins/signing.html

Terraform has made some changes to the provider dependency selections recorded
in the .terraform.lock.hcl file. Review those changes and commit them to your
version control system if they represent changes you intended to make.

Terraform has been successfully initialized!
- Installed vexxhost/uptimerobot v0.8.2 (self-signed, key ID 8FF00CD0B5FEAF59)

Partner and community providers are signed by their developers.
If you'd like to know more about provider signing, you can read about it here:
https://www.terraform.io/docs/cli/plugins/signing.html

Terraform has made some changes to the provider dependency selections recorded
in the .terraform.lock.hcl file. Review those changes and commit them to your
version control system if they represent changes you intended to make.

Terraform has been successfully initialized!
- Installed backblaze/b2 v0.8.4 (signed by a HashiCorp partner, key ID 83D9CAF4848490D6)

Partner and community providers are signed by their developers.
If you'd like to know more about provider signing, you can read about it here:
https://www.terraform.io/docs/cli/plugins/signing.html

Terraform has made some changes to the provider dependency selections recorded
in the .terraform.lock.hcl file. Review those changes and commit them to your
version control system if they represent changes you intended to make.

Terraform has been successfully initialized!
- Installed integrations/github v5.40.0 (signed by a HashiCorp partner, key ID 38027F80D7FD5FB2)

Partner and community providers are signed by their developers.
If you'd like to know more about provider signing, you can read about it here:
https://www.terraform.io/docs/cli/plugins/signing.html

Terraform has made some changes to the provider dependency selections recorded
in the .terraform.lock.hcl file. Review those changes and commit them to your
version control system if they represent changes you intended to make.

Terraform has been successfully initialized!
cloudflare_tunnel.this: Refreshing state... [id=de250703-6c08-400d-b568-bc0aa34cabaf]
data.uptimerobot_account.this: Reading...
data.uptimerobot_account.this: Read complete after 1s [id=2023-10-26 21:15:39.607122792 +0000 UTC]
data.uptimerobot_alert_contact.this: Reading...
cloudflare_access_application.this: Refreshing state... [id=bcaa03ae-0a94-42ad-935c-487ca0a80723]
data.github_ip_ranges.this: Reading...
data.github_ip_ranges.this: Read complete after 0s [id=github-ip-ranges]
data.uptimerobot_alert_contact.this: Read complete after 0s [id=01487022]
uptimerobot_monitor.this: Refreshing state... [id=795551117]
cloudflare_access_policy.this: Refreshing state... [id=1b62d9cb-f555-4d23-b815-dfe3f92bd2a1]
cloudflare_access_policy.github: Refreshing state... [id=2a1fc41f-8d41-4f1f-8e72-91b0970ab129]
cloudflare_access_policy.uptime_robot: Refreshing state... [id=fd540ff0-edd5-4f64-b683-a8dd575af941]

No changes. Your infrastructure matches the configuration.

Terraform has compared your real infrastructure against your configuration
and found no differences, so no changes are needed.
b2_bucket.this: Refreshing state... [id=62c5440382b735a482bf081b]
data.github_ip_ranges.this: Reading...
data.github_ip_ranges.this: Read complete after 0s [id=github-ip-ranges]

No changes. Your infrastructure matches the configuration.

Terraform has compared your real infrastructure against your configuration
and found no differences, so no changes are needed.

Terraform used the selected providers to generate the following execution
plan. Resource actions are indicated with the following symbols:
  ~ update in-place

Terraform will perform the following actions:

  # cloudflare_access_policy.uptime_robot will be updated in-place
  ~ resource "cloudflare_access_policy" "uptime_robot" {
        id             = "fd540ff0-edd5-4f64-b683-a8dd575af941"
        name           = "UptimeRobot IP List"
        # (4 unchanged attributes hidden)

      ~ include {
          ~ ip                      = [
              - "<IP_ADDRESS>/32",
              - "<IP_ADDRESS>/32",
              - "<IP_ADDRESS>/32",
              - "<IP_ADDRESS>/32",
              - "<IP_ADDRESS>/32",
              - "<IP_ADDRESS>/32",
              - "<IP_ADDRESS>/32",
              - "<IP_ADDRESS>/32",
              - "<IP_ADDRESS>/32",
              - "<IP_ADDRESS>/32",
              - "<IP_ADDRESS>/32",
              - "<IP_ADDRESS>/32",
              - "<IP_ADDRESS>/32",
              - "<IP_ADDRESS>/32",
              - "<IP_ADDRESS>/32",
              - "<IP_ADDRESS>/32",
              - "<IP_ADDRESS>/32",
              - "<IP_ADDRESS>/32",
              - "<IP_ADDRESS>/32",
              - "<IP_ADDRESS>/32",
              - "<IP_ADDRESS>/32",
              - "<IP_ADDRESS>/32",
              - "<IP_ADDRESS>/32",
              - "<IP_ADDRESS>/32",
              - "<IP_ADDRESS>/32",
              - "<IP_ADDRESS>/32",
              - "<IP_ADDRESS>/32",
              - "<IP_ADDRESS>/32",
              - "<IP_ADDRESS>/32",
              - "<IP_ADDRESS>/32",
              - "<IP_ADDRESS>/32",
              - "<IP_ADDRESS>/32",
              - "<IP_ADDRESS>/32",
              - "<IP_ADDRESS>/32",
              - "<IP_ADDRESS>/32",
              - "<IP_ADDRESS>/32",
              - "<IP_ADDRESS>/32",
              - "<IP_ADDRESS>/32",
              - "<IP_ADDRESS>/32",
              - "<IP_ADDRESS>/32",
              - "<IP_ADDRESS>/32",
              - "<IP_ADDRESS>/32",
              - "<IP_ADDRESS>/32",
              - "<IP_ADDRESS>/32",
              - "<IP_ADDRESS>/32",
              - "<IP_ADDRESS>/32",
              - "<IP_ADDRESS>/32",
              - "<IP_ADDRESS>/32",
              - "<IP_ADDRESS>/32",
              - "<IP_ADDRESS>/32",
              - "<IP_ADDRESS>/32",
              - "<IP_ADDRESS>/32",
              - "<IP_ADDRESS>/32",
              - "<IP_ADDRESS>/32",
              - "<IP_ADDRESS>/32",
              - "<IP_ADDRESS>/32",
              - "<IP_ADDRESS>/32",
              - "<IP_ADDRESS>/32",
              - "<IP_ADDRESS>/32",
              - "<IP_ADDRESS>/32",
              - "<IP_ADDRESS>/32",
              - "<IP_ADDRESS>/32",
              - "<IP_ADDRESS>/32",
              - "<IP_ADDRESS>/32",
              - "<IP_ADDRESS>/32",
              - "<IP_ADDRESS>/32",
              - "<IP_ADDRESS>/32",
              - "<IP_ADDRESS>/32",
              - "<IP_ADDRESS>/32",
              - "<IP_ADDRESS>/32",
              - "<IP_ADDRESS>/32",
              - "<IP_ADDRESS>/32",
              - "<IP_ADDRESS>/32",
              - "<IP_ADDRESS>/32",
              - "<IP_ADDRESS>/32",
              - "<IP_ADDRESS>/32",
              - "<IP_ADDRESS>/32",
              - "<IP_ADDRESS>/32",
              - "<IP_ADDRESS>/32",
              - "<IP_ADDRESS>/32",
              - "<IP_ADDRESS>/32",
              - "<IP_ADDRESS>/32",
              - "<IP_ADDRESS>/32",
              - "<IP_ADDRESS>/32",
              - "<IP_ADDRESS>/32",
              - "<IP_ADDRESS>/32",
              - "<IP_ADDRESS>/32",
              - "<IP_ADDRESS>/32",
              - "2607:ff68:107::3/128",
              - "2607:ff68:107::4/128",
              - "2607:ff68:107::5/128",
              - "2607:ff68:107::6/128",
              - "2607:ff68:107::7/128",
              - "2607:ff68:107::8/128",
              - "2607:ff68:107::9/128",
              - "2607:ff68:107::10/128",
              - "2607:ff68:107::11/128",
              - "2607:ff68:107::12/128",
              - "2607:ff68:107::13/128",
              - "2607:ff68:107::14/128",
              - "2607:ff68:107::15/128",
              - "2607:ff68:107::16/128",
              - "2607:ff68:107::17/128",
              - "2607:ff68:107::18/128",
              - "2607:ff68:107::19/128",
              - "2607:ff68:107::20/128",
              - "2607:ff68:107::21/128",
              - "2607:ff68:107::22/128",
              - "2607:ff68:107::23/128",
              - "2607:ff68:107::24/128",
              - "2607:ff68:107::25/128",
              - "2607:ff68:107::26/128",
              - "2607:ff68:107::27/128",
              - "2607:ff68:107::28/128",
              - "2607:ff68:107::29/128",
              - "2607:ff68:107::30/128",
              - "2607:ff68:107::31/128",
              - "2607:ff68:107::32/128",
              - "2607:ff68:107::33/128",
              - "2607:ff68:107::34/128",
              - "2607:ff68:107::35/128",
              - "2607:ff68:107::36/128",
              - "2607:ff68:107::37/128",
              - "2607:ff68:107::38/128",
              - "2607:ff68:107::39/128",
              - "2607:ff68:107::40/128",
              - "2607:ff68:107::41/128",
              - "2607:ff68:107::42/128",
              - "2607:ff68:107::43/128",
              - "2607:ff68:107::44/128",
              - "2607:ff68:107::45/128",
              - "2607:ff68:107::46/128",
              - "2607:ff68:107::47/128",
              - "2607:ff68:107::48/128",
              - "2607:ff68:107::49/128",
              - "2607:ff68:107::50/128",
              - "2607:ff68:107::51/128",
              - "2607:ff68:107::52/128",
              - "2607:ff68:107::53/128",
              - "2607:ff68:107::54/128",
              - "2607:ff68:107::55/128",
              - "2607:ff68:107::56/128",
              - "2607:ff68:107::57/128",
              - "2607:ff68:107::58/128",
              - "2607:ff68:107::59/128",
              - "2607:ff68:107::60/128",
              - "2607:ff68:107::61/128",
              - "2607:ff68:107::62/128",
              - "2a03:b0c0:2:d0::fa3:e001/128",
              - "2a03:b0c0:1:d0::e54:a001/128",
              - "2604:a880:800:10::4e6:f001/128",
              - "2604:a880:cad:d0::122:7001/128",
              - "2a03:b0c0:3:d0::33e:4001/128",
              - "2600:1f16:775:3a01:70d6:601a:1eb5:dbb9/128",
              - "2600:1f11:56a:9000:23:651b:dac0:9be4/128",
              - "2a03:b0c0:3:d0::44:f001/128",
              - "2a03:b0c0:0:1010::2b:b001/128",
              - "2a03:b0c0:1:d0::22:5001/128",
              - "2604:a880:400:d0::4f:3001/128",
              - "2400:6180:0:d0::16:d001/128",
              - "2604:a880:cad:d0::18:f001/128",
              - "2600:1f18:179:f900:88b2:b3d:e487:e2f4/128",
              - "2600:1f18:179:f900:1977:916:ee3d:711e/128",
              - "2a05:d014:1815:3400:588a:ee17:65c3:3b09/128",
              - "2600:1f16:775:3a00:b729:c226:2737:fe49/128",
              + "<IP_ADDRESS>",
              + "<IP_ADDRESS>",
              + "<IP_ADDRESS>",
              + "<IP_ADDRESS>",
              + "<IP_ADDRESS>",
              + "<IP_ADDRESS>",
              + "<IP_ADDRESS>",
              + "<IP_ADDRESS>",
              + "<IP_ADDRESS>",
              + "<IP_ADDRESS>",
              + "<IP_ADDRESS>",
              + "<IP_ADDRESS>",
              + "<IP_ADDRESS>",
              + "<IP_ADDRESS>",
              + "<IP_ADDRESS>",
              + "<IP_ADDRESS>",
              + "<IP_ADDRESS>",
              + "<IP_ADDRESS>",
              + "<IP_ADDRESS>",
              + "<IP_ADDRESS>",
              + "<IP_ADDRESS>",
              + "<IP_ADDRESS>",
              + "<IP_ADDRESS>",
              + "<IP_ADDRESS>",
              + "<IP_ADDRESS>",
              + "<IP_ADDRESS>",
              + "<IP_ADDRESS>",
              + "<IP_ADDRESS>",
              + "<IP_ADDRESS>",
              + "<IP_ADDRESS>",
              + "<IP_ADDRESS>",
              + "<IP_ADDRESS>",
              + "<IP_ADDRESS>",
              + "<IP_ADDRESS>",
              + "<IP_ADDRESS>",
              + "<IP_ADDRESS>",
              + "<IP_ADDRESS>",
              + "<IP_ADDRESS>",
              + "<IP_ADDRESS>",
              + "<IP_ADDRESS>",
              + "<IP_ADDRESS>",
              + "<IP_ADDRESS>",
              + "<IP_ADDRESS>",
              + "<IP_ADDRESS>",
              + "<IP_ADDRESS>",
              + "<IP_ADDRESS>",
              + "<IP_ADDRESS>",
              + "<IP_ADDRESS>",
              + "<IP_ADDRESS>",
              + "<IP_ADDRESS>",
              + "<IP_ADDRESS>",
              + "<IP_ADDRESS>",
              + "<IP_ADDRESS>",
              + "<IP_ADDRESS>",
              + "<IP_ADDRESS>",
              + "<IP_ADDRESS>",
              + "<IP_ADDRESS>",
              + "<IP_ADDRESS>",
              + "<IP_ADDRESS>",
              + "<IP_ADDRESS>",
              + "<IP_ADDRESS>",
              + "<IP_ADDRESS>",
              + "<IP_ADDRESS>",
              + "<IP_ADDRESS>",
              + "<IP_ADDRESS>",
              + "<IP_ADDRESS>",
              + "<IP_ADDRESS>",
              + "<IP_ADDRESS>",
              + "<IP_ADDRESS>",
              + "<IP_ADDRESS>",
              + "<IP_ADDRESS>",
              + "<IP_ADDRESS>",
              + "<IP_ADDRESS>",
              + "<IP_ADDRESS>",
              + "<IP_ADDRESS>",
              + "<IP_ADDRESS>",
              + "<IP_ADDRESS>",
              + "<IP_ADDRESS>",
              + "<IP_ADDRESS>",
              + "<IP_ADDRESS>",
              + "<IP_ADDRESS>",
              + "<IP_ADDRESS>",
              + "<IP_ADDRESS>",
              + "<IP_ADDRESS>",
              + "<IP_ADDRESS>",
              + "<IP_ADDRESS>",
              + "<IP_ADDRESS>",
              + "<IP_ADDRESS>",
              + "2607:ff68:107::3",
              + "2607:ff68:107::4",
              + "2607:ff68:107::5",
              + "2607:ff68:107::6",
              + "2607:ff68:107::7",
              + "2607:ff68:107::8",
              + "2607:ff68:107::9",
              + "2607:ff68:107::10",
              + "2607:ff68:107::11",
              + "2607:ff68:107::12",
              + "2607:ff68:107::13",
              + "2607:ff68:107::14",
              + "2607:ff68:107::15",
              + "2607:ff68:107::16",
              + "2607:ff68:107::17",
              + "2607:ff68:107::18",
              + "2607:ff68:107::19",
              + "2607:ff68:107::20",
              + "2607:ff68:107::21",
              + "2607:ff68:107::22",
              + "2607:ff68:107::23",
              + "2607:ff68:107::24",
              + "2607:ff68:107::25",
              + "2607:ff68:107::26",
              + "2607:ff68:107::27",
              + "2607:ff68:107::28",
              + "2607:ff68:107::29",
              + "2607:ff68:107::30",
              + "2607:ff68:107::31",
              + "2607:ff68:107::32",
              + "2607:ff68:107::33",
              + "2607:ff68:107::34",
              + "2607:ff68:107::35",
              + "2607:ff68:107::36",
              + "2607:ff68:107::37",
              + "2607:ff68:107::38",
              + "2607:ff68:107::39",
              + "2607:ff68:107::40",
              + "2607:ff68:107::41",
              + "2607:ff68:107::42",
              + "2607:ff68:107::43",
              + "2607:ff68:107::44",
              + "2607:ff68:107::45",
              + "2607:ff68:107::46",
              + "2607:ff68:107::47",
              + "2607:ff68:107::48",
              + "2607:ff68:107::49",
              + "2607:ff68:107::50",
              + "2607:ff68:107::51",
              + "2607:ff68:107::52",
              + "2607:ff68:107::53",
              + "2607:ff68:107::54",
              + "2607:ff68:107::55",
              + "2607:ff68:107::56",
              + "2607:ff68:107::57",
              + "2607:ff68:107::58",
              + "2607:ff68:107::59",
              + "2607:ff68:107::60",
              + "2607:ff68:107::61",
              + "2607:ff68:107::62",
              + "2a03:b0c0:2:d0::fa3:e001",
              + "2a03:b0c0:1:d0::e54:a001",
              + "2604:a880:800:10::4e6:f001",
              + "2604:a880:cad:d0::122:7001",
              + "2a03:b0c0:3:d0::33e:4001",
              + "2600:1f16:775:3a01:70d6:601a:1eb5:dbb9",
              + "2600:1f11:56a:9000:23:651b:dac0:9be4",
              + "2a03:b0c0:3:d0::44:f001",
              + "2a03:b0c0:0:1010::2b:b001",
              + "2a03:b0c0:1:d0::22:5001",
              + "2604:a880:400:d0::4f:3001",
              + "2400:6180:0:d0::16:d001",
              + "2604:a880:cad:d0::18:f001",
              + "2600:1f18:179:f900:88b2:b3d:e487:e2f4",
              + "2600:1f18:179:f900:1977:916:ee3d:711e",
              + "2a05:d014:1815:3400:588a:ee17:65c3:3b09",
              + "2600:1f16:775:3a00:b729:c226:2737:fe49",
            ]
            # (11 unchanged attributes hidden)
        }
    }

Plan: 0 to add, 1 to change, 0 to destroy.

No changes. Your infrastructure matches the configuration.

Terraform has compared your real infrastructure against your configuration
and found no differences, so no changes are needed.

Initializing the backend...

Successfully configured the backend "s3"! Terraform will automatically
use this backend unless the backend configuration changes.

Initializing provider plugins...
- Reusing previous version of hashicorp/aws from the dependency lock file
- Reusing previous version of backblaze/b2 from the dependency lock file
- Reusing previous version of cloudflare/cloudflare from the dependency lock file
- Reusing previous version of integrations/github from the dependency lock file
- Finding vexxhost/uptimerobot versions matching "~> 0.8"...
- Installing hashicorp/aws v5.21.0...
- Installed hashicorp/aws v5.21.0 (signed by HashiCorp)
- Installing backblaze/b2 v0.8.4...
- Installed backblaze/b2 v0.8.4 (signed by a HashiCorp partner, key ID 83D9CAF4848490D6)
- Installing cloudflare/cloudflare v4.16.0...
- Installed cloudflare/cloudflare v4.16.0 (self-signed, key ID C76001609EE3B136)
- Installing integrations/github v5.40.0...
- Installed integrations/github v5.40.0 (signed by a HashiCorp partner, key ID 38027F80D7FD5FB2)
- Installing vexxhost/uptimerobot v0.8.2...
- Installed vexxhost/uptimerobot v0.8.2 (self-signed, key ID 8FF00CD0B5FEAF59)

Partner and community providers are signed by their developers.
If you'd like to know more about provider signing, you can read about it here:
https://www.terraform.io/docs/cli/plugins/signing.html

Terraform has made some changes to the provider dependency selections recorded
in the .terraform.lock.hcl file. Review those changes and commit them to your
version control system if they represent changes you intended to make.

Terraform has been successfully initialized!
cloudflare_record.internal_record["longhorn_internal"]: Refreshing state... [id=9d9e7849509ddd1ca1420bfb93085ddb]
cloudflare_record.internal_record["argocd_internal"]: Refreshing state... [id=ad2633b9ce86a1786416dd851cb5c4d3]
cloudflare_record.public_record: Refreshing state... [id=16e19a8901e14239e7345e3922f318f9]
cloudflare_record.internal_record["kiali_internal"]: Refreshing state... [id=3e29d0bc6567b4c0fecd6db58e432160]
cloudflare_record.internal_record["sftpgo_internal"]: Refreshing state... [id=d53e66b848b3967bd5a9885eb2c8e08c]
cloudflare_record.internal_record["jellyfin_internal"]: Refreshing state... [id=62786f77078b02d784342427605ba9e9]
cloudflare_record.internal_record["adguard_internal"]: Refreshing state... [id=5803590e9218027a34aae666383f8211]

No changes. Your infrastructure matches the configuration.

Terraform has compared your real infrastructure against your configuration
and found no differences, so no changes are needed.


SqlCommand.Parameters having same variable declared twice

Hi,
I am working in some interceptor for multi-tenant application and when I was doing  INSERT behavior, I found something strange.
Here is my code that change DbInsertCommandTree:
public class DbInsertCommandTreeHandler : CommandTreeHandlerBase
{
    private const string COLUMN_NAME = "TenantId";

    protected override bool CanHandle(DbCommandTree command)
    {
        return command is DbInsertCommandTree;
    }

    protected override DbCommandTree Handle(DbCommandTree command)
    {
        var insertCommandTree = command as DbInsertCommandTree;

        var dbSetClauses = insertCommandTree.SetClauses.Cast<DbSetClause>().ToList();

        var setClause = dbSetClauses.FirstOrDefault(HasColumn);
        if (setClause != null)
        {
            dbSetClauses.RemoveAll(HasColumn);
            dbSetClauses.Add(CreateSetClause(setClause));

            return new DbInsertCommandTree(insertCommandTree.MetadataWorkspace,
                insertCommandTree.DataSpace,
                insertCommandTree.Target,
                dbSetClauses.Cast<DbModificationClause>().ToList().AsReadOnly(),
                insertCommandTree.Returning);
        }
        return insertCommandTree;
    }

    private static DbSetClause CreateSetClause(DbSetClause expression)
    {
        var propertyExpression = expression.Property as DbPropertyExpression;
        return DbExpressionBuilder.SetClause(propertyExpression, propertyExpression.ResultType.Parameter("tenantId"));
    }

    private static bool HasColumn(DbSetClause setClause)
    {
        return (setClause.Property as DbPropertyExpression).Property.Name == COLUMN_NAME;
    }
}

When testing my code in test app, I received this exception:
The variable name '@tenantId' has already been declared. Variable names must be unique within a query batch or stored procedure.

So I added a breackpoint in my custom IDbCommandInterceptor in ReaderExecuting method. Then I saw that DbCommand had 10 parameters, first one was tenantId and last one @tenantId, I digged in my code to check were the first parameter came from. I didn't found it. The command tree generated from my DbInsertCommandTreeHandler produced this:
DbInsertCommandTree
|_Parameters
| |_tenantId : Edm.Int64
|_Target : 'target'
| |_Scan : CodeFirstDatabase.Contato
|_SetClauses
| |_DbSetClause
| | |_Property
| | | |_Var(target).Nome
| | |_Value
| |   |_'Alberto'
| |_DbSetClause
| | |_Property
| | | |_Var(target).Endereço_Rua
| | |_Value
| |   |_'Avenida F'
| |_DbSetClause
| | |_Property
| | | |_Var(target).Endereço_Bairro
| | |_Value
| |   |_'Benfica'
| |_DbSetClause
| | |_Property
| | | |_Var(target).Endereço_Complemento
| | |_Value
| |   |_null
| |_DbSetClause
| | |_Property
| | | |_Var(target).Endereço_Numero
| | |_Value
| |   |_1
| |_DbSetClause
| | |_Property
| | | |_Var(target).Endereço_Cep
| | |_Value
| |   |_0
| |_DbSetClause
| | |_Property
| | | |_Var(target).Telefone
| | |_Value
| |   |_'30211083'
| |_DbSetClause
| | |_Property
| | | |_Var(target).Celular
| | |_Value
| |   |_'86234779'
| |_DbSetClause
| | |_Property
| | | |_Var(target).Inativo
| | |_Value
| |   |_False
| |_DbSetClause
|   |_Property
|   | |_Var(target).TenantId
|   |_Value
|     |_@tenantId
|_Returning
  |_NewInstance : Record['Id'=Edm.Int64]
    |_Column : 'Id'
      |_Var(target).Id

So, I cloned EF repository and started to debug EF source code, and I realized that EF were adding the parameter tenantId twice.
In System.Data.Entity.SqlServer.SqlGen.DmlSqlGenerator at lines 248 ~ 267 EF create parameters from the SetClauses.
When code flow reach in System.Data.Entity.SqlServer.SqlProviderServices at lines 257 ~ 286 EF create SqlParameters from command tree parameters(commandTree.Parameters) and then add to SqlCommand.Parameters.
After that in lines 289 ~ 302 EF get parameters generated from DmlSqlGenerator and then add to SqlCommand.Parameters.
And then the SqlCommand.Parameters have parameter tenantId duplicated. One from commandTree.Parameters and another from commandTree.SetClauses.
I that behavior normal?

@divega any feedback?

@AlbertoMonteiro just to confirm, if you remove the interceptor, do you still see a failure?

@divega no, it works properly

@divega I created this repo with a project reproducing the issue.
https://github.com/AlbertoMonteiro/EFIssueSimulator

@divega @rowanmiller any feedback?

@AlbertoMonteiro thanks for putting together a repro. I haven't found any time to look into this so clearing up milestone so that we can design what to do with it in the next triage.

@divega @rowanmiller I can try fix it and make a pull request, but I don't know where is the best place to put the unit test for this kind of issue involving a interceptor, can you tell me?

If there is a bug in interception a test in test/EntityFramework/FunctionalTests/Interception/CommandTreeInterceptionTests.cs should be appropriate, but I am not sure that is the case.

@AlbertoMonteiro would the scenario work if DbInsertCommandTreeHandler.CreateSetClause you create a DbExpression representing constant with the proper value for the TenantId, rather than parameter (that you assign value later, in the MultiTenantInterceptor)?
Something like:
        private static DbSetClause CreateSetClause(DbPropertyExpression propertyExpression)
            => DbExpressionBuilder.SetClause(
                propertyExpression,
                propertyExpression.ResultType.Constant(TenantId));

EF already parameterizes all constants in the DML statements as part of its SQL generation.
We looked into enabling the scenario/approach you were trying, but EF has made a few assumptions around parameters in DML (i.e. we assume there would never be any created by the user). Fixing those assumptions requires changes in the providers, which makes it a non viable solution.

closing this as we believe we have found a reasonable workaround, please re-open if it doesn't work and we will re-evaluate and/or look for better workarounds.


Update EventsQueryHandler exception parameter naming

Previous behavior used before parameter name with throwing an exception for the after parameter.
Also, remove trailing whitespace from related test.

Cool, got it.


About vendor identification

This is our sample context:
Value = 00-4bf92f3577b34da6a3ce929d0e0e4736-00f067aa0ba902b7-01
base16(<Version>) = 00
base16(<TraceId>) = 4bf92f3577b34da6a3ce929d0e0e4736
base16(<SpanId>) = 00f067aa0ba902b7
base16(<TraceOptions>) = 01  // sampled

And if I am an implementation developer (skywalking APM auther), how can I know about this is my context or cross-tracer-implementation context? By now, because of skywalking have more context than these field, so we are going to set two HEAD_NAMEs. So if we found the other one, we know it's our context. But I think this is not an elegant way.
How about doing a field which represent vendor? And maintain a list for these codes. By having this, the users will know how to use this outer-trace-id, and where to query the real trace, if they have more than two tracing system.

Why do you need to know if it is your context or others context? You cannot guarantee anyway because you don't sign this and you don't deal with authentication (I expect) to be able to make sure even if I send you a context with "skywalking" bit set.
If you can give me some concrete examples how would you use this, it would be great. I think it is a bit hard to respect this bit and trust this bit (similar problems with trace-options which I mentioned in the doc).

Hops will treat opaque and/or truncate. So cant know for sure. You could
add correlation field (buddy field) depending on propagation semantics
might tell trace was yours originally. If correlation field is propagated
with semantics (ex if you change the trace id you must invalidate) it could
work. Vendor registry could be problematic and endanger such an idea

This issue is a bit out of range than just propagation and interop. In my mind, when we have interop, on tracer can get the traceid and spanid from head. And I hope we can do more on UI. The UI can provide a link for each vendor, user can goto the target tracer system. From I known, almost all the tracer provided indenpendency trace query page.
This is not an urgent requirement. But I think in some day, if tracer can interop, and have a list, it's fun for tracer system users.

This https://github.com/openzipkin/zipkin/issues/1262#issuecomment-333317113 made me think of this issue. If we treat the trace ID as an opaque N-bytes array, then the systems like sky-walking and X-Ray may be able to pack their trace-id representation into such array, but they will loose their own semantics like the timestamp part in X-Ray's model. That effectively means they will be forced to send another header, either to indicate that it's 'their' trace-id, or to repeat the whole thing again (even more likely). Aside from the duplication issue, this puts the service meshes like Envoy back to square one - they don't have a definitive set of headers they need to understand.
If we had a byte identifying the vendor (or, rather, the identifier for a trace-id schema) then the semantics within the blob could be preserved.

Since every vendor candidate build their identifiers in multiple ways and
IMO there is not such a way to support all the possible structures, would
it be a idea to support a long enough traceID field and standarize the max
length allowing vendors to send their traceID padded with 0 on the left?
Ex. My traceID is 123456 but the standard says 8 length traceID so we
treat it as 00123456?
lør. 30. sep. 2017, 18.06 skrev Yuri Shkuro<EMAIL_ADDRESS>
This openzipkin/zipkin#1262 (comment)
https://github.com/openzipkin/zipkin/issues/1262#issuecomment-333317113
made me think of this issue. If we treat the trace ID as an opaque N-bytes
array, then the systems like sky-walking and X-Ray may be able to pack
their trace-id representation into such array, but they will loose their
own semantics like the timestamp part in X-Ray's model. That effectively
means they will be forced to send another header, either to indicate that
it's 'their' trace-id, or to repeat the whole thing again (even more
likely). Aside from the duplication issue, this puts the service meshes
like Envoy back to square one - they don't have a definitive set of headers
they need to understand.
If we had a byte identifying the vendor (or, rather, the identifier for a
trace-id schema) then the semantics within the blob could be preserved.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/TraceContext/tracecontext-spec/issues/14#issuecomment-333318217,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AC7sAsdBP1Zb_42xMs1mqB1jdqmwtI86ks5snmbxgaJpZM4PaZCj
.

--
José Carlos Chávez
Spain: (+34) 672921339
Perú: (+51) 708-5422 Anexo 918
https://github.com/jcchavezs

This openzipkin/zipkin#1262 (comment)
https://github.com/openzipkin/zipkin/issues/1262#issuecomment-333317113
made me think of this issue. If we treat the trace ID as an opaque N-bytes
array, then the systems like sky-walking and X-Ray may be able to pack
their trace-id representation into such array, but they will loose their
own semantics like the timestamp part in X-Ray's model. That effectively
means they will be forced to send another header, either to indicate that
it's 'their' trace-id, or to repeat the whole thing again (even more
likely). Aside from the duplication issue, this puts the service meshes
like Envoy back to square one - they don't have a definitive set of headers
they need to understand.

The referenced comment is about a tactical hack to tunnel amazon's
propagated original timestamp field into zipkin's trace ID. It wasn't a
comment for the trace-context spec, rather a tactical concern which is why
I didn't bring it up here. I didn't bring it up here as I didn't want to
speculate about how Amazon will interact with this spec.
If I were to speculate, Amazon's timestamp field might be sent in the
correlation header, which is needed for baggage anyway right? Or if it were
common, it could be an additional field. Whatever's in the root ID matters
at the point of origin, where it is created. If this spec is only about
envoy, and envoy supported the correlation header, the timestamp field
could also be there, or a vendor ID. To Fabian's earlier point, if we
define a correlation header and it isn't usable, the feature could be
suspect.
Anyway, and more to this point, so far amazon hasn't had a chance to speak
for themselves, and speaking for them or rushing in absence of them could
lead us to false conclusions. For example, we don't know if they'd ever use
this format, or it needs to change in more dramatic ways. Might be helpful
to park specific concerns about amazon until they are present in this
conversation?  They will definitely be present Nov 1 (also folks from
fastly and linkerd will be present if remote to discuss the part about
intermediaries and if fixed set is actually a requirement outside envoy).

Ex. My traceID is 123456 but the standard says 8 length traceID so we
treat it as 00123456?

If you look at some trace formats, for example hierarchical, they are
variable length and can run until there's no room. Microsoft's has
truncation rules, but that doesn't mean all do. In zipkin, I know we
pad-left sometimes. I think this sort of feature, like handling all
vendors, needs a markdown sheet (not google doc, as you can't read google
doc in china) covering the various styles of ID generation and where it is
mutated (ex if IDs are derived etc). If we do what if's here, this issue
can wander to the point where it can be hard to follow. I think more
homework first, as vendor ID is a big deal.


Add night dancer by imase

Song Name
night dancer
Artist Name
imase
Source
Youtube
Youtube Link
kq9m88gUYKVBwbPG
Direct File Link
No response
Song ID
78
Start Offset [ms]
0
Extra
Created from Auto Nong.
Created for level: 92398039

Hi

reject
invalid YouTube link


Kalman Filter's properties don't work correctly

Summary
All tests for KalmanFilter fails.
Getter still returns brand new instance each call.
Related issues: #786 #802
Environment
Ubuntu: 18.04.3 LTS
Output:
  X OpenCvSharp.Tests.Video.KalmanTest.TransitionMatrix [< 1ms]
  Error Message:
   Assert.Equal() Failure
Expected: (width:2 height:2)
Actual:   (width:0 height:0)
  Stack Trace:
     at OpenCvSharp.Tests.Video.KalmanTest.IsDataEqual(Mat lhs, Mat rhs) in /workspaces/opencvsharp/test/OpenCvSharp.Tests/video/KalmanTest.cs:line 179
   at OpenCvSharp.Tests.Video.KalmanTest.TransitionMatrix() in /workspaces/opencvsharp/test/OpenCvSharp.Tests/video/KalmanTest.cs:line 55

[xUnit.net 00:01:40.52]     OpenCvSharp.Tests.Video.KalmanTest.TransitionMatrix [FAIL]

The tests passed in my environment and the CI environments (Windows by AppVeyor and Ubuntu by CircleCI). Did you rebuild the OpenCvSharpEntern (C++ lib)?

Thanks for answer, yeah, OpenCvSharpEntern was rebuilt.

The tests were successful in my environment and the CI environments

Will dig deeper tomorrow then

⛏

Another rebuild solved this problem.
Thanks for help.


Is UDMP's temperature accurate when running the latest OS?

I was comparing some charts in Grafana between the unpoller metrics and the node-exporter metrics, and I have found that one of the unpoller's temperature is much higher than the other.
These are the temperatures registered by unpoller:

And these are the ones that node-exporters read from the udm-pro:

Finally this is the output I get from the command sensors, which is in agreement with node-exporter metrics:
adt7475-i2c-4-2e
Adapter: i2c-0-mux (chan_id 3)
in1:         885.00 mV (min =  +0.00 V, max =  +2.99 V)
+3.3V:         3.23 V  (min =  +2.96 V, max =  +3.63 V)
fan1:        4393 RPM  (min =    0 RPM)
fan2:        1347 RPM  (min =    0 RPM)
fan3:        1347 RPM  (min =    0 RPM)
fan4:        1347 RPM  (min =    0 RPM)
temp1:        +57.5°C  (low  = -63.0°C, high = +191.0°C)
                       (crit = +100.0°C, hyst = +96.0°C)
Board Temp:   +54.8°C  (low  = -63.0°C, high = +191.0°C)
                       (crit = +100.0°C, hyst = +96.0°C)
temp3:        +54.5°C  (low  = -63.0°C, high = +191.0°C)
                       (crit = +100.0°C, hyst = +96.0°C)

Maybe there is an issue with the CPU temperature registered by unpoller?

this would be whatever the device API reports back, so if it differs this would be a unifi bug to file


Crashed test counts as passed.

I had a test that failed in a set where all others succeeded, and when it retried it crashed the app, but then Bluepill marked it as success. Here's the relevant portion of the output:
20170213.134303 [  INFO  ] (2) Completed: [2] Install Application
20170213.134303 [  INFO  ] (2) [2] Launch Application
20170213.134311 [  INFO  ] (2) Completed: [2] Launch Application
20170213.134312 [  INFO  ] (2) All Tests started.
20170213.134320 [ CRASH  ] (2) AnnotationTests/testCreateNote crashed app.
20170213.134320 [  ERROR ] (2) Will kill the process with appPID: 7676
20170213.134320 [  INFO  ] (2) [2] Delete Simulator
20170213.134332 [  INFO  ] (2) Completed: [2] Delete Simulator
20170213.134332 [  INFO  ] (2) Exit Status: BPExitStatusTestsAllPassed

Nothing else was retried after and Bluepill finished with success.

If it's reproducible, can you try it with the integration-test branch? I has a fix for a different problem but it's related to this area.

I can't reproduce it locally, and I've only seen it twice on one of our test machines (and only happened to see it because I was watching for a different failure).
Maybe I'll make a PR that does some validation when it returns success to make sure all the tests actually passed. The main thing I'm worried about is false positives.

@nickmshelley it would be great if you could build a test case to reproduce this 🍡

Ok I'll look into it.

In looking into this, it seems like there are a few issues... I'll submit new issues for the new ones I found.
For this issue, it can be easily reproduced by adding the following lines to testReportWithAppCrashingTestsSet:
self.config.failureTolerance = 2;
self.config.onlyRetryFailed = YES;


Simple autocrafter not working as intended (checked with EpicSquid on discord)

Issue Description:
Bug checked with EpicSquid and he can replicate it. 17h30 today in the #general channel on discord.
The simple crafter doesn't work correctly and output the ingredients instead of crafting the desired item. Further more, you get and extra "minecraft:spawn_egg" item sometimes randomly.
What you expected to happen:
I would like to get my crafter to craft! damnit :p
Steps to reproduce:

Placing a simple autocrafter next to a simple generator.
Placing a chest over the autocrafter
Turning the top face of the autocrafter to pull items from the chest to the autocrafter.
I added the simple chassis recipe on the left (like normally) annnd....
Happy wtf! The autocrafter will output the materials from the recipe and some "minecraft:spawn_egg" 💃

Affected Versions (Do not use "latest"):

EnderIO: 5.0.24
EnderCore: 0.5.22
Minecraft: 1.12.2
Forge: <IP_ADDRESS>53

Pictures:
https://imgur.com/a/53y9oKf

I also came across this issue in hourly build 386.  It also happens with the normal Crafter.
In addition, the stock single items/stacks button doesn't seem to work on the normal Crafter.

I have the same thing except for some reason it completely deleted the crafting recipe... Well more like changed the result to air. I was just having them make wooden axes for a tree farm and it did it for both the wood to planks and planks to sticks. Checked in JEI, and the recipes changed and couldn't even craft by hand after that. Didn't do it all the time, but happened a few times for both. Reloading client fixes, but it happens again after a while. Couldn't track it through the logs nor could pinpoint any specific point at which it changed... Sorry that I cant help there.


Drop support of Python 3.8

Summary by CodeRabbit

New Features

Updated workflows to support additional Python versions (3.9, 3.10, 3.11, and 3.12), enhancing compatibility with newer features and libraries.

Bug Fixes

Adjusted caching keys and import statements to align with updated Python standards, improving efficiency and maintainability.

Documentation

Enhanced comments and type hints across various files for clarity and adherence to modern best practices in type hinting.

Refactor

Replaced type hints with built-in types (e.g., dict, list, tuple) throughout the codebase to streamline type annotations and improve readability.

@coderabbitai revew


when will Filament version upgrade to 1.20.3

cause filament has some bug fix in latest version

You can make a PR to move to the latest Filament version but take care of recompiling the materials

dup of #368?

Fixed: Release 1.21.0 : Controlling Renderable culling + Fixed destroying skybox + ARCore 1.31.0 + Filament 1.21.1


MNT: test coreg UI with notebook 3d backend

This PR adds testing of the coreg UI with the notebook 3d backend. It's a very basic test for now.
The notebook app was hanging when loading trans locally, I'll add it to #8833:

[ ] the app hangs when loading trans (ipywidgets)

What do you think @larsoner ?

Nice and clean, thanks @GuillaumeFavelier !


Title change and replaced PWA with web app

Please take a look at the proposed changes. Travis recommended using nouns rather than verbs for the title so I've updated this to reflect Minimal-frame Window for Installed Desktop Web Apps.
It's long but descriptive and Travis didn't think the length was an issue. Only concern is minimal-frame may be confusing initially with minimal-ui but as it's not proposing a new display mode called minimal-frame I don't think the confusion will linger.

The current change doesn't match what we just talked about. Do you need to push up the latest changes?

Yes this I didn't push up the latest. I'll close this.


(docs) S2S WARP connector hint on iptables policy

Summary
Spent some day intensively scratching my head why i cannot access private network, just to find out the policy in iptables blocking the traffic

👋Hi there, we’re going to close this PR. All PRs prior to August 12 need to be reworked due to the platform migration to Astro.


Fixes visual bug on deed pages for some NC licenses prior to 4.0

Temporary fix for #692
Frankly it is an insult to all these nations to have this visual bug live since the introduction of the redesign.
I'd much more prefer that there was a push for cleaning this up an allowing the EU, Japan, and Guatamala to show their own currency in the NC licenses in the licenses prior to 4.0.
Description
Removes all older customised currency icons

We will review this once our resident web expert @hugosolar is back from vacation next week.


Renaming ros2 tracing events with the smacc2 prefix

This is useful to improve the readability of the tracing files and to improve the filtering.

Adding to this....
This is from the tracing.md file, the tracing event names that should be changed...
ros2:client_behavior_on_exit_end (loglevel: TRACE_DEBUG_LINE (13)) (type: tracepoint)
ros2:client_behavior_on_exit_start (loglevel: TRACE_DEBUG_LINE (13)) (type: tracepoint)
ros2:client_behavior_on_entry_end (loglevel: TRACE_DEBUG_LINE (13)) (type: tracepoint)
ros2:client_behavior_on_entry_start (loglevel: TRACE_DEBUG_LINE (13)) (type: tracepoint)
ros2:state_onExit_end (loglevel: TRACE_DEBUG_LINE (13)) (type: tracepoint)
ros2:state_onExit_start (loglevel: TRACE_DEBUG_LINE (13)) (type: tracepoint)
ros2:state_onEntry_end (loglevel: TRACE_DEBUG_LINE (13)) (type: tracepoint)
ros2:state_onEntry_start (loglevel: TRACE_DEBUG_LINE (13)) (type: tracepoint)
ros2:state_onRuntimeConfigure_end (loglevel: TRACE_DEBUG_LINE (13)) (type: tracepoint)
ros2:state_onRuntimeConfigure_start (loglevel: TRACE_DEBUG_LINE (13)) (type: tracepoint)
ros2:update_end (loglevel: TRACE_DEBUG_LINE (13)) (type: tracepoint)
ros2:update_start (loglevel: TRACE_DEBUG_LINE (13)) (type: tracepoint)
ros2:smacc_event (loglevel: TRACE_DEBUG_LINE (13)) (type: tracepoint)
to something like...
  ros2:smacc2_client_behavior_on_exit_end (loglevel: TRACE_DEBUG_LINE (13)) (type: tracepoint)
  ros2:smacc2_client_behavior_on_exit_start (loglevel: TRACE_DEBUG_LINE (13)) (type: tracepoint)
  ros2:smacc2_client_behavior_on_entry_end (loglevel: TRACE_DEBUG_LINE (13)) (type: tracepoint)
  ros2:smacc2_client_behavior_on_entry_start (loglevel: TRACE_DEBUG_LINE (13)) (type: tracepoint)
  ros2:smacc2_state_onExit_end (loglevel: TRACE_DEBUG_LINE (13)) (type: tracepoint)
  ros2:smacc2_state_onExit_start (loglevel: TRACE_DEBUG_LINE (13)) (type: tracepoint)
  ros2:smacc2_state_onEntry_end (loglevel: TRACE_DEBUG_LINE (13)) (type: tracepoint)
  ros2:smacc2_state_onEntry_start (loglevel: TRACE_DEBUG_LINE (13)) (type: tracepoint)
  ros2:smacc2_state_onRuntimeConfigure_end (loglevel: TRACE_DEBUG_LINE (13)) (type: tracepoint)
  ros2:smacc2_state_onRuntimeConfigure_start (loglevel: TRACE_DEBUG_LINE (13)) (type: tracepoint)
  ros2:smacc2_state_update_end (loglevel: TRACE_DEBUG_LINE (13)) (type: tracepoint)
  ros2:smacc2_state_update_start (loglevel: TRACE_DEBUG_LINE (13)) (type: tracepoint)
  ros2:smacc2_event (loglevel: TRACE_DEBUG_LINE (13)) (type: tracepoint)

Important Commits
Most of the commits that built this part of the code occurred from 5/18/2021 to 5/28/2021.
Important Files
https://github.com/robosoft-ai/SMACC2/blob/master/smacc2/scripts/trace.sh
https://github.com/robosoft-ai/SMACC2/tree/master/smacc2/include/smacc2/smacc_tracing


Add some request and response fields

Currently Snap also returns redirect_url too when creating snap token
Here is the sample response:
{
    "token": "SNAP_TOKEN",
    "redirect_url": "SNAP_WEB_URL"
}

Also based on snap-docs.midtrans.com, Snap request also supports custom_field1, custom_field2 and custom_field3 .

Thanks Raka for the PR 👍


Dart language syntax highlighting

Hi! I just found this great theme collection, I'm happily using it in VS and I also wanted to use it in Code.
However Dart doesn't have full syntax highlighting, many tokens are just white.
See the example.
Default:

Essex:

Rei:

I'm not sure if this is a bug or a feature request, maybe it's necessary for Dart to add some special mapping or something? Could you please look at it?
Thank you!

Sure, I'll add that when I get around to updating this plugin.
Do you have a sample dart codebase I could use?

Great! I currently don't have my own, but I found [this] (https://github.com/apgapg/rx_dart_samples/tree/master/lib) might be enough.

Hey! So I almost got it all complete, the version I just released should have most of the fixes.
However, it will not be enabled by default until #160 is in.
Until then, just put this line in your settings json
	"editor.semanticHighlighting.enabled": true,

and the syntax highlighting for Dart files should be more colorful 🎨

I just tried it, looks like it's working:

Looks great! Thanks for the update!


API returns 200 on invalid language

POST to https://emkc.org/api/v1/piston/execute with a language that isn't whitelisted will result in a 200 with the response
{"output":""}

Here's some code to reproduce it:
fetch('https://emkc.org/api/v1/piston/execute', {
	method: 'POST',
	headers: {
		'Content-Type': 'application/json'
	},
	body: JSON.stringify({ language: 'randomstuff123', source: 'potatoes', args: [] }),
}).then(res => res.json()).then(console.log);

Also, omitting the fields altogether will result in the same response:
body: '{}',

Also, omitting the fields altogether will result in the same response:
body: '{}',

Ran piston locally, but couldn't reproduce the bug. The problem seems to be with the public instance.

Ran piston locally, but couldn't reproduce the bug. The problem seems to be with the public instance.

This will reproduce it with python.
import requests, json

inputs = {
    "language": "nolang",
    "source": "print('hello world!')",
    "args": [
        "1",
    ]
           }

response = requests.post('https://emkc.org/api/v1/piston/execute', json=inputs).json()
print(json.dumps(response, indent=2))

output observed.
{
  "output": ""
}

This will reproduce it with python.
import requests, json

inputs = {
    "language": "nolang",
    "source": "print('hello world!')",
    "args": [
        "1",
    ]
           }

response = requests.post('https://emkc.org/api/v1/piston/execute', json=inputs).json()
print(json.dumps(response, indent=2))

output observed.
{
  "output": ""
}

What would you guys suggest? 403?

What would you guys suggest? 403?

It returns an error code locally, the problem is in the public instance.

It returns an error code locally, the problem is in the public instance.

it'll end up being a 400. it shouldn't be returning 200, I'll fix this tomorrow

it'll end up being a 400. it shouldn't be returning 200, I'll fix this tomorrow

The issue is no more
{"message": "Unsupported language language supplied"}```

The issue is no more
{"message": "Unsupported language language supplied"}```


Added grunt-cli for those who don't have it installed globally

This cli approach helps to prevent initial errors.
Also, changed development instructions section to run using npm script instead of grunt.

@afonsof

Done! @afonsof


Use logr instead of log/slog

Describe the feature request
Use logr instead of log/slog
Why do you personally want this feature to be implemented?
https://github.com/TwiN/k8s-ttl-controller/pull/102#issuecomment-2534486024
How long have you been using this project?
No response
Additional information
No response

Thank you for suggesting this library - I appreciate the opportunity to explore it. I gave it a try and found that it currently doesn't seem to support logs in JSON format, which is something I was hoping for in our use case.
If there’s a workaround or something I might have missed, I’d be happy to revisit it.

Oh I was suggesting you implement it in the library itself (if you were up to the challenge).
Again, though, only if you're up for it. If not, ill pick this up when I have some time

No worries :)


Custom Function for Dates Table

Dates table with Fiscal Year and Academic Year fields

Custom function for Dates table with Fiscal Year and Academic Year fields


"Address already in use" when doing a change in server code

I wanted to try out how the reload of both client and server worked and it failed when changing server code. I did a minor change to defaultWishList to get something visual out, but when it tried to reload the server it seemed like the old process were still alive since it got a conflict on the address.
Repro steps:

./build.sh run
login
Do a minor change to defaultWishList
Failed

Info

Operating system : OSX
Branch : master
Dotnet info:

.NET Command Line Tools (1.0.1)

Product Information:
 Version:            1.0.1
 Commit SHA-1 hash:  005db40cd1

Runtime Environment:
 OS Name:     Mac OS X
 OS Version:  10.12
 OS Platform: Darwin
 RID:         osx.10.12-x64
 Base Path:   /usr/local/share/dotnet/sdk/1.0.1

Let me know if anything more is needed.

do you have another service on that port? Did it start suave correctly on "build.sh run" ?
Can you please check if ports 8080 and 8085 are ok? One is suave and the other is webpack dev server

It did start up fine the first time and I could go to the wish list page, but after I changed the code I got the conflict. If I would have something running on any of 8080 or 8085 I would have got a conflict when it started the first time, but I didn't.

the webpack dev seems to work as expected, but the API dies.

(yes but errors on startup are not really goo to see here)
The question is why dotnet run --watch doesn't kill the old service
2017-03-15 10:47 GMT+01:00 Tomas Jansson<EMAIL_ADDRESS>
It did start up fine the first time and I could go to the wish list page,
but after I changed the code I got the conflict. If I would have something
running on any of 8080 or 8085 I would have got a conflict when it started
the first time, but I didn't.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/fable-compiler/fable-suave-scaffold/issues/71#issuecomment-286691826,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AADgNGSRlIY-DPBRvwGSqRqi2TMMPvsbks5rl7PFgaJpZM4Mdn2c
.

Is it anything I can run to get some more info?

I dunno.
2017-03-15 10:50 GMT+01:00 Tomas Jansson<EMAIL_ADDRESS>
Is it anything I can run to get some more info?
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/fable-compiler/fable-suave-scaffold/issues/71#issuecomment-286692369,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AADgNNORtZW7zQTPUNwxYx1PT-3eGgpcks5rl7RMgaJpZM4Mdn2c
.

I'll see if I find some time later this week or next week to figure it out, now back to java land... :/

Looks like it is dotnet, I'll register a bug in dotnet tomorrow and put a link here to it. I ran it manually without success. When running it manually it didn't even try to do a re-run, and when killed it with ctrl-c the port was still bound to the port for a while so I couldn't do a restart right away.

/cc @enricosada

the dotnet run --watch command doesnt exits.
@mastoj if your issue is with dotnet watch, open an issue in https://github.com/aspnet/DotNetTools because watch is an external tool.

Opened this issue: https://github.com/aspnet/DotNetTools/issues/278
Althought, I'm not 100 % sure it is a dotnet issue. It might be that chrome is holding on to the ports because the app does reload correctly if I don't visit a page.


Fixed bug where inserted lines did not work.

This stems from a type conversion error which affects released versions of the
game. When performing float operations, Godot will haphazardly store the result
as a float or an int depending on the circumstances. In the Godot editor, it
likes storing them as ints more often. But when exported, it likes storing them
as floats more often.

This bug stems from Godot #41336. TileMap is inherently designed to work with both float values (via methods like get_cellv) and int values (via methods like get_cell). 99% of the time these play well together, but if you are not careful you can end up referencing used_cell.y under the assumption that it is an int, when it is actually a float -- resulting in unpredictable results.
Worse yet, these variable types can be different when the game is exported with debug mode on or off.


Add gatsby-plugin-astroturf to readme

I made a little something! ✨
I wasn't sure where to put it, is here ok?

I moved them below the "Usage" and renamed the title to "Extensions", is that better? I realized that "Plugins" might sound like they are plugins for astroturf.


Add AWS SDK Extension package to registry

Adds a reference to the python package which allows OpenTelemetry Python users to configure the generation of traces to be compatible for the AWS X-Ray service.

lgtm thanks!


Gamebreaker pawn evaporated and game frozen

Could not load UnityEngine.Texture2D at Things/Pawn/Humanlike/Apparel/AdvancedHelmet/AdvancedHelmet_west in any active mod or in base resources.
Verse.Log:Error(String, Boolean)
Verse.ContentFinder1:Verse.ContentFinder1[[UnityEngine.Texture2D, UnityEngine.CoreModule, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=null]].Get_Patch1(String, Boolean)
RimThreaded.Ticklist_Patch:MainThreadWaitLoop()
RimThreaded.Ticklist_Patch:Tick(TickList)
Verse.TickList:Verse.TickList.Tick_Patch1(TickList)
Verse.TickManager:Verse.TickManager.DoSingleTick_Patch1(TickManager)
Verse.TickManager:TickManagerUpdate()
Verse.Game:Verse.Game.UpdatePlay_Patch2(Game)
Verse.Root_Play:Update()

Could not load UnityEngine.Texture2D at Things/Pawn/Humanlike/Apparel/FlakVest/FlakVest_Hulk_west in any active mod or in base resources.
Verse.Log:Error(String, Boolean)
Verse.ContentFinder1:Verse.ContentFinder1[[UnityEngine.Texture2D, UnityEngine.CoreModule, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=null]].Get_Patch1(String, Boolean)
RimThreaded.Ticklist_Patch:MainThreadWaitLoop()
RimThreaded.Ticklist_Patch:Tick(TickList)
Verse.TickList:Verse.TickList.Tick_Patch1(TickList)
Verse.TickManager:Verse.TickManager.DoSingleTick_Patch1(TickManager)
Verse.TickManager:TickManagerUpdate()
Verse.Game:Verse.Game.UpdatePlay_Patch2(Game)
Verse.Root_Play:Update()

Getting this one while trying to wear gear. If you want the modlist its a smaller list than what i sent to you directly

Exception drawing Morris: System.NullReferenceException: Object reference not set to an instance of an object
at RimThreaded.Building_Door_Patch.get_DoorPowerOn (RimWorld.Building_Door __instance, System.Boolean& __result) [0x00011] in :0
at (wrapper dynamic-method) RimWorld.Building_Door.RimWorld.Building_Door.get_DoorPowerOn_Patch1(RimWorld.Building_Door)
at (wrapper dynamic-method) RimWorld.Building_Door.RimWorld.Building_Door.get_SlowsPawns_Patch1(RimWorld.Building_Door)
at Verse.AI.Pawn_PathFollower.NextCellDoorToWaitForOrManuallyOpen () [0x0001f] in :0
at Verse.PawnTweener.MovedPercent () [0x00048] in :0
at Verse.PawnTweener.TweenedPosRoot () [0x00021] in :0
at Verse.PawnTweener.ResetTweenedPosToRoot () [0x00000] in :0
at Verse.PawnTweener.PreDrawPosCalculation () [0x0001d] in :0
at Verse.Pawn_DrawTracker.get_DrawPos () [0x00000] in :0
at Verse.Pawn.get_DrawPos () [0x00006] in :0
at Verse.Thing.Draw () [0x00000] in :0
at Verse.ThingWithComps.Draw () [0x00000] in :0
at RimThreaded.Verse_DynamicDrawManager_Patch.DrawDynamicThings (Verse.DynamicDrawManager __instance) [0x0013f] in :0
Verse.Log:Error(String, Boolean)
RimThreaded.Verse_DynamicDrawManager_Patch:DrawDynamicThings(DynamicDrawManager)
Verse.DynamicDrawManager:Verse.DynamicDrawManager.DrawDynamicThings_Patch1(DynamicDrawManager)
Verse.Map:Verse.Map.MapUpdate_Patch3(Map)
Verse.Game:Verse.Game.UpdatePlay_Patch2(Game)
Verse.Root_Play:Update()

Exception drawing Door70432: System.NullReferenceException: Object reference not set to an instance of an object
at RimThreaded.Building_Door_Patch.get_DoorPowerOn (RimWorld.Building_Door __instance, System.Boolean& __result) [0x00011] in :0
at (wrapper dynamic-method) RimWorld.Building_Door.RimWorld.Building_Door.get_DoorPowerOn_Patch1(RimWorld.Building_Door)
at (wrapper dynamic-method) RimWorld.Building_Door.RimWorld.Building_Door.get_TicksToOpenNow_Patch1(RimWorld.Building_Door)
at RimWorld.Building_Door.Draw () [0x00017] in :0
at RimThreaded.Verse_DynamicDrawManager_Patch.DrawDynamicThings (Verse.DynamicDrawManager __instance) [0x0013f] in :0
Verse.Log:Error(String, Boolean)
RimThreaded.Verse_DynamicDrawManager_Patch:DrawDynamicThings(DynamicDrawManager)
Verse.DynamicDrawManager:Verse.DynamicDrawManager.DrawDynamicThings_Patch1(DynamicDrawManager)
Verse.Map:Verse.Map.MapUpdate_Patch3(Map)
Verse.Game:Verse.Game.UpdatePlay_Patch2(Game)
Verse.Root_Play:Update()

Exception drawing ThingOverlay for Morris: System.NullReferenceException: Object reference not set to an instance of an object
at RimThreaded.Building_Door_Patch.get_DoorPowerOn (RimWorld.Building_Door __instance, System.Boolean& __result) [0x00011] in :0
at (wrapper dynamic-method) RimWorld.Building_Door.RimWorld.Building_Door.get_DoorPowerOn_Patch1(RimWorld.Building_Door)
at (wrapper dynamic-method) RimWorld.Building_Door.RimWorld.Building_Door.get_SlowsPawns_Patch1(RimWorld.Building_Door)
at Verse.AI.Pawn_PathFollower.NextCellDoorToWaitForOrManuallyOpen () [0x0001f] in :0
at Verse.PawnTweener.MovedPercent () [0x00048] in :0
at Verse.PawnTweener.TweenedPosRoot () [0x00021] in :0
at Verse.PawnTweener.ResetTweenedPosToRoot () [0x00000] in :0
at Verse.PawnTweener.PreDrawPosCalculation () [0x0001d] in :0
at Verse.Pawn_DrawTracker.get_DrawPos () [0x00000] in :0
at Verse.Pawn.get_DrawPos () [0x00006] in :0
at Verse.GenMapUI.LabelDrawPosFor (Verse.Thing thing, System.Single worldOffsetZ) [0x00000] in :0
at (wrapper dynamic-method) Verse.PawnUIOverlay.Verse.PawnUIOverlay.DrawPawnGUIOverlay_Patch1(Verse.PawnUIOverlay)
at Verse.Pawn.DrawGUIOverlay () [0x00006] in :0
at Verse.ThingOverlays.ThingOverlaysOnGUI () [0x0005e] in :0
Verse.Log:Error(String, Boolean)
Verse.ThingOverlays:ThingOverlaysOnGUI()
RimWorld.MapInterface:MapInterfaceOnGUI_BeforeMainTabs()
RimWorld.UIRoot_Play:UIRootOnGUI()
Verse.Root:Verse.Root.OnGUI_Patch1(Root)

Root level exception in OnGUI(): System.NullReferenceException: Object reference not set to an instance of an object
at RimThreaded.Building_Door_Patch.get_DoorPowerOn (RimWorld.Building_Door __instance, System.Boolean& __result) [0x00011] in :0
at (wrapper dynamic-method) RimWorld.Building_Door.RimWorld.Building_Door.get_DoorPowerOn_Patch1(RimWorld.Building_Door)
at (wrapper dynamic-method) RimWorld.Building_Door.RimWorld.Building_Door.get_SlowsPawns_Patch1(RimWorld.Building_Door)
at Verse.AI.Pawn_PathFollower.NextCellDoorToWaitForOrManuallyOpen () [0x0001f] in :0
at Verse.PawnTweener.MovedPercent () [0x00048] in :0
at Verse.PawnTweener.TweenedPosRoot () [0x00021] in :0
at Verse.PawnTweener.ResetTweenedPosToRoot () [0x00000] in :0
at Verse.PawnTweener.PreDrawPosCalculation () [0x0001d] in :0
at Verse.Pawn_DrawTracker.get_DrawPos () [0x00000] in :0
at Verse.Pawn.get_DrawPos () [0x00006] in :0
at Verse.TooltipGiverList.DispenseAllThingTooltips () [0x0009c] in :0
at RimWorld.MapInterface.MapInterfaceOnGUI_BeforeMainTabs () [0x00074] in :0
at RimWorld.UIRoot_Play.UIRootOnGUI () [0x0001f] in :0
at (wrapper dynamic-method) Verse.Root.Verse.Root.OnGUI_Patch1(Verse.Root)
Verse.Log:Error(String, Boolean)
Verse.Root:Verse.Root.OnGUI_Patch1(Root)

Quit to Menu followed with CTD

Root level exception in OnGUI(): System.NullReferenceException: Object reference not set to an instance of an object
at RimThreaded.Building_Door_Patch.get_DoorPowerOn (RimWorld.Building_Door __instance, System.Boolean& __result) [0x00011] in :0
at (wrapper dynamic-method) RimWorld.Building_Door.RimWorld.Building_Door.get_DoorPowerOn_Patch1(RimWorld.Building_Door)
at (wrapper dynamic-method) RimWorld.Building_Door.RimWorld.Building_Door.get_SlowsPawns_Patch1(RimWorld.Building_Door)
at Verse.AI.Pawn_PathFollower.NextCellDoorToWaitForOrManuallyOpen () [0x0001f] in :0
at Verse.PawnTweener.MovedPercent () [0x00048] in :0
at Verse.PawnTweener.TweenedPosRoot () [0x00021] in :0
at Verse.PawnTweener.ResetTweenedPosToRoot () [0x00000] in :0
at Verse.PawnTweener.PreDrawPosCalculation () [0x0001d] in :0
at Verse.Pawn_DrawTracker.get_DrawPos () [0x00000] in :0
at Verse.Pawn.get_DrawPos () [0x00006] in :0
at Verse.GenUI.ThingsUnderMouse (UnityEngine.Vector3 clickPos, System.Single pawnWideClickRadius, RimWorld.TargetingParameters clickParams) [0x00036] in :0
at RimWorld.Selector+d__39.MoveNext () [0x0009e] in :0
at System.Collections.Generic.List1[T]..ctor (System.Collections.Generic.IEnumerable1[T] collection) [0x00077] in <567df3e0919241ba98db88bec4c6696f>:0
at System.Linq.Enumerable.ToList[TSource] (System.Collections.Generic.IEnumerable`1[T] source) [0x00018] in <351e49e2a5bf4fd6beabb458ce2255f3>:0
at RimWorld.Selector.SelectUnderMouse () [0x0004c] in :0
at RimWorld.Selector.HandleMapClicks () [0x001c2] in :0
at RimWorld.Selector.SelectorOnGUI () [0x00000] in :0
at RimWorld.MapInterface.HandleLowPriorityInput () [0x0000f] in :0
at RimWorld.UIRoot_Play.UIRootOnGUI () [0x000d3] in :0
at (wrapper dynamic-method) Verse.Root.Verse.Root.OnGUI_Patch1(Verse.Root)
Verse.Log:Error(String, Boolean)
Verse.Root:Verse.Root.OnGUI_Patch1(Root)
New and semi-related to current issues

Closing bug. Many bugs have been fixed since this was reported. Please reopen in new bug report using the new templates if this issue persists.


Lack of documentation for steps in interpreters.py

Hello, thank you for your work.
I have been trying to run the attack on YOLOv3 using python3 yolov3.py 0.
However, I have not been able to get it to work.
After running, I encounter this error:
Traceback (most recent call last):
  File "yolov3.py", line 44, in <module>
    rad_coco(load_model, get_index, group_dimension=9, attack_dimension=4, transfer_enhance=['SI'])
  File "/content/RAD/rad.py", line 194, in rad_coco
    **kwargs,
  File "/content/RAD/rad.py", line 73, in __init__
    self.analysis = build_lrp(self.model.model_attack, self.index_place)
  File "/content/RAD/utils.py", line 165, in build_lrp
    analyzer = SGLRP(partial_model, target_id=target_id, multi=multi, relu=True, low=tf.reduce_min(inp), high=tf.reduce_max(inp), allow_lambda_layers=True)
  File "/content/RAD/interpreters.py", line 288, in __init__
    super(SGLRP, self).__init__(model, target_id=target_id, low=low, high=high, **kwargs)
  File "/content/RAD/interpreters.py", line 126, in __init__
    self.target_analyzer = self._get_target_analyzer(**kwargs)
  File "/content/RAD/interpreters.py", line 292, in _get_target_analyzer
    return _SGLRPTarget(self.model, target_id=self.target_id, multi=self.multi, **kwargs)
  File "/content/RAD/interpreters.py", line 221, in __init__
    super(_SGLRPBase, self).__init__(model, neuron_selection_mode="all", **kwargs)
  File "/content/RAD/innvestigate/analyzer/deeptaylor.py", line 184, in __init__
    model, **kwargs)
  File "/content/RAD/innvestigate/analyzer/deeptaylor.py", line 49, in __init__
    super(DeepTaylor, self).__init__(model, *args, **kwargs)
  File "/content/RAD/innvestigate/analyzer/base.py", line 592, in __init__
    super(ReverseAnalyzerBase, self).__init__(model, **kwargs)
  File "/content/RAD/innvestigate/analyzer/base.py", line 341, in __init__
    super(AnalyzerNetworkBase, self).__init__(model, **kwargs)
  File "/content/RAD/innvestigate/analyzer/base.py", line 73, in __init__
    self._do_model_checks()
  File "/content/RAD/innvestigate/analyzer/base.py", line 98, in _do_model_checks
    checked = kgraph.model_contains(self._model, check)
  File "/content/RAD/innvestigate/utils/keras/graph.py", line 419, in model_contains
    tmp = [layer for layer in layers if condition(layer)]
  File "/content/RAD/innvestigate/utils/keras/graph.py", line 419, in <listcomp>
    tmp = [layer for layer in layers if condition(layer)]
  File "/content/RAD/innvestigate/analyzer/base.py", line 349, in <lambda>
    layer, activation="softmax"),
  File "/content/RAD/innvestigate/utils/keras/checks.py", line 219, in contains_activation
    raise Exception("Cannot detect activation type.")
Exception: Cannot detect activation type.

I think it is related to the comment in interpreters.py, where the following is mentioned
"""rewrite from https://github.com/uchidalab/softmaxgradient-lrp"""
"""enable attention gradient in tensorflow and Multi-Node SGLRP if specify multi=True"""
""" !!! need to modify source code in innvestigate to run"""

Could a step by step guide be provided on how to do that?

The specific modification on the iNNvestigate library could be seen in https://github.com/Sizhe-Chen/DAmageNet readme/generation part

The specific modification on the iNNvestigate library could be seen in https://github.com/Sizhe-Chen/DAmageNet readme/generation part

Thank you for that, however I am still getting the error in the original post.
The error could be related to this instruction, since I realised that multi is true when using yolov3.
"""enable attention gradient in tensorflow and Multi-Node SGLRP if specify multi=True"""
Could you guide me in how to "enable attention gradient"? Your help will be greatly appreciated, thank you!

Thanks for pointing out the missing of instructions. Besides replacing base.py in iNNvestigate, it is also necessary to replace deeptaylor.py in the same folder. deeptaylor.py has been uploaded to this reposity, and the problem is indeed located at UpSampling2D.

Thank you, that solved the issue.


Handle the scenarios that there is no data for storage group

Description
Before this change, there are 2 scenarios which are not handled by query.

Query schema if the storage group exists but there is no timeseries inside it.
Query the data if the storage group exists but there is no timeseries and data inside it.

After this change, the query in these two scenarios are like:

query schema

query data

Coverage increased (+0.02%) to 53.611% when pulling d2ea020556cd51b76f6978557f4d124cdd5fa40b on xingtanzjr/fix_empty_partition into c6f9d0a0854cdd83fa07decf2960245d972cbf46 on master.


Modifying some text on the UI final page

Regarding the UI final step ("Download configuration files for your OSMOSE model") -
Could you please replace the following text:

When you are ready, press "Download configuration files".

with that one:

When you are ready, press "Submit".

?
Many thanks.

@agruss2 The change is now implemented in the UI final step.
Please verify.

The present issue has been solved; I am therefore going to close it. Many thanks.


make an arduino library and add it to the library manager

This is an awesome project! Finally I can make a quick gui for a prototype!
It would be great if this was a library and manageble through the arduino library manager.

Thanks,
Yes, it was considered and definitely should be put in backlog. There are few things to consider:

I could pack the existing involt-basic sketch into a library but there are users who (for example) add additional pins to involtReceive function or other things there. I don't know how to handle these changes within library for end-user.
It makes sense if I make more sketches for future communication methods. It will be easier to maintain.
Does the existing sketch has readability issues? At current version, there is no need of adding additional step to make Involt work. (downloading and installing library).
Finally, it would be great if Involt as library would be put directly into Arduino IDE/library manager without external download. How to achieve that?

The main reason for me to have a library is to remove code from the main file.

I'm not a really good programmer, but you could do all the setup in the constructor. Maybe an approach like in the library serialcommand where you define the functions on different commands in the setup funktion would work. If I have time I will look into it.
You can write different definitions for different plattforms, e.g. when you use an esp it automatically knows to not use serial but http-requests.
No, the sketch is easy to read.
I found this link, where they describe how to make a library for the manager: https://github.com/arduino/Arduino/wiki/Library-Manager-FAQ


Don't show env when there isn't

What this PR does / why we need it:
This PR removes unneeded and odd Skeletons.

Which issue(s) this PR fixes:
Fixes #
Does this PR introduce a user-facing change?:

NONE

/trigger web-test

/trigger web-test

Nice, just the web-test on CI's taking so long
/approve


fix sha256 tests expecting incorrect hash

I take it you're on Windows @No-one-important? This might be a line endings issue. Changing the expectation as you suggest would presumably cause tests to fail on other platforms, so I'll see if I can figure out a platform-independent solution.

I doubt that is the problem as the file still contains Linux line endings but generates a different hash the base branch

--- FAIL: ExamplePipe_SHA256Sums (0.00s)
got:
4aea3d470d3f667fdd2dcdb9dbbc77db43872cfbfac1ce15682c4928eae9a146
want:
a562c9c95e2ff3403e7ffcd8508c6b54d47d5f251387758d3e63dbaaa8296341
FAIL
exit status 1
FAIL    github.com/bitfield/script      1.295s

that is the one I have addressed and this is running the tests directly after cloning the repo
there are some other tests that fail which are possibly line endings and some that are windows using backslashes in filepaths
full output attached
tests.txt

This is puzzling. The SHA256 hash of the file is exactly a562c9c95e2ff3403e7ffcd8508c6b54d47d5f251387758d3e63dbaaa8296341. There's no doubt about that: you can verify it using an online tool like this, or with a tool like gsha256sum:
gsha256sum testdata/test.txt
a562c9c95e2ff3403e7ffcd8508c6b54d47d5f251387758d3e63dbaaa8296341  testdata/test.txt

This doesn't explain why you're getting a different hash. The only thing I can think of is that maybe Go is reading different bytes for some platform-related reason.
Could you please run this program on your machine and paste the output?
package main

import (
	"fmt"
	"io"
	"log"
	"os"
)

func main() {
	f, err := os.Open("testdata/test.txt")
	if err != nil {
		log.Fatal(err)
	}
	defer f.Close()
	data, err := io.ReadAll(f)
	if err != nil {
		log.Fatal(err)
	}
	fmt.Println(data)
}

I get:
[84 104 105 115 32 105 115 32 116 104 101 32 102 105 114 115 116 32 108 105 110 101 32 105 110 32 116 104 101 32 102 105 108 101 46 10 72 101 108 108 111 44 32 119 111 114 108 100 46 10 84 104 105 115 32 105 115 32 97 110 111 116 104 101 114 32 108 105 110 101 32 105 110 32 116 104 101 32 102 105 108 101 46 10]

[84 104 105 115 32 105 115 32 116 104 101 32 102 105 114 115 116 32 108 105 110 101 32 105 110 32 116 104 101 32 102 105 108 101 46 13 10 72 101 108 108 111 44 32 119 111 114 108 100 46 13 10 84 104 105 115 32 105 115 32 97 110 111 116 104 101 114 32 108 105 110 101 32 105 110 32 116 104 101 32 102 105 108 101 46 13 10]
when is run _____@DESKTOP-I0MU8LO MINGW64 ~/test/script (master) $ sha256sum testdata/test.txt
in git bash on windows
I get
4aea3d470d3f667fdd2dcdb9dbbc77db43872cfbfac1ce15682c4928eae9a146 *testdata/test.txt

There you go. Look at the last few bytes of the file, as reported by macOS and Windows respectively:
108 101 46 10

vs
108 101 46 13 10

No wonder you're getting a different hash; you're hashing a different file!
I'll change the test to hash a string instead; that should fix your issue.


[BEAM-5539] Beam Dependency Update Request: google-cloud-pubsub

for testing

Follow this checklist to help us incorporate your contribution quickly and easily:

[ ] Format the pull request title like [BEAM-XXX] Fixes bug in ApproximateQuantiles, where you replace BEAM-XXX with the appropriate JIRA issue, if applicable. This will automatically link the pull request to the issue.
[ ] If this contribution is large, please file an Apache Individual Contributor License Agreement.

It will help us expedite review of your Pull Request if you tag someone (e.g. @username) to look at it.
 Is there anything I should check further?

No, test coverage in pre and postcommits should be enough.

@ccy for merge please

Thanks, this LGTM.


Protégé fails to import OMO

Description of the issue
Since merging PR #616 Protégé fails to open the OEO. It stops working while trying to open OMO, see last line of this screenshot:

Protégé just hangs at this step, the only possibility is to force terminate Protégé.
Ideas of solution
If you already have ideas for the solution describe them here
Workflow checklist

[ ] I am aware of the workflow for this repository

Oh dear! It works for me without even pausing for a second :-(. Protege saves all the "special" problems for you @l-emele !
What happens if you go to http://purl.obolibrary.org/obo/omo.owl in a web browser? (You should get redirected to a file)

My browser redirects to this URL: https://raw.githubusercontent.com/information-artifact-ontology/ontology-metadata/v2020-06-08/omo.owl
The content in the browser look seems to be the correct owl file.

I also can't replicate your problem. When I try to open the ontology, everything works fine.

I just did a test: On a local branch, I replaced in the oeo-shared.omn the URL http://purl.obolibrary.org/obo/omo.owl with the URL https://raw.githubusercontent.com/information-artifact-ontology/ontology-metadata/v2020-06-08/omo.owl.
So we can narrow down the problem that the redirect is causing the problem. Maybe because the original URL is a http, the redirected on a https?

We had issues before with redirects, see #426.

I seem to remember something about some redirection problem in the OWL API that was fixed in a recent version. Just double checking which version of Protege you are using?

I am currently using Version 5.5.0 Build beta-4.
According to https://protege.stanford.edu/products.php#desktop-protege, the latest version is 5.5.0 (without beta). I'll download now that version and test whether this causes the problem, too.

Using version 5.5.0 (stable) solves the problem. I documented in https://github.com/OpenEnergyPlatform/ontology/wiki/Protégé that this version should be used.
I'll close this issue now.


iOS metal seems to require compile-time constant sampler for sample_compare

Hi, I've raised an issue #529 several days ago. You said "no constexpr samplers are needed" because you tested on OSX, it seems that only iOS metal requires this. I upgraded my iOS system and Xcode to the latest version, but the issue still remains. Is there any way to deal with this problem? Otherwise, maybe I have to use sample instead of sample_compare on iOS.

If iOS truly requires this, MoltenVK would need to add emulation support here because SPIRV-Cross would need another interface which lets you set constant sampler state ahead of time. I don't think there is much I can do right now. Please file a bug on MoltenVK if you're using that.

Can you add a new interface while remain backward compatibility? We can not do PCF shadow mapping without this feature in our in house engine, which has nothing to do with MoltenVK.
Thank you.

If you're using the API only, I could add something like:
void CompilerMSL::remap_constexpr_sampler(unsigned id, const MSLConstexprSamplerData &)

However, I don't know how this works in MSL, so please paste some example shaders how you'd like the resulting MSL code to look.

The sampler remapped could be declared at the beginning of the entry point function, and passed to those functions that use this sampler. Just like:
#pragma clang diagnostic ignored "-Wmissing-prototypes"

#include <metal_stdlib>
#include <simd/simd.h>

using namespace metal;

struct main0_in
{
    float3 vUV [[user(locn0)]];
};

struct main0_out
{
    float FragColor [[color(0)]];
};

float Samp(thread const float3& uv, thread depth2d<float> uTex, thread sampler uSamp)
{
    return uTex.sample_compare(uSamp, uv.xy, uv.z);
}

fragment main0_out main0(main0_in in [[stage_in]], depth2d<float> uTex [[texture(0)]], depth2d<float> uTex2 [[texture(1)]], sampler uSamp [[sampler(0)]], sampler uSamp2 [[sampler(1)]])
{
    constexpr sampler uSamp_(address::clamp_to_edge, mip_filter::none, min_filter::linear, mag_filter::linear, compare_func::less);
    constexpr sampler uSamp2_(address::clamp_to_edge, mip_filter::none, min_filter::nearest, mag_filter::nearest, compare_func::less_equal);

    main0_out out = {};
    out.FragColor = uTex.sample_compare(uSamp_, in.vUV.xy, in.vUV.z);
    out.FragColor += Samp(in.vUV, uTex2, uSamp2_);
    return out;
}

Ok, that seems reasonable enough.

Got something WIP that should solve your problem. Please check it out and give feedback if this fixes your issue.

We will test it ASAP

This seems to resolve the issue we had. Thanks very much! @HansKristian-ARM


[Dropdown] Changing delimiter of the multiselect input

Now this is the way is filling the input :
                       <input name="multipleElement" type="hidden" value="value1, value2">
Is it possible to change it to:
                       <input name="multipleElement" type="hidden" value="value1; value2">

The setting has the exact name you would guess
https://github.com/Semantic-Org/Semantic-UI/blob/master/src/definitions/modules/dropdown.js#L3503