task Create Bucket fails 409

was taking a look at: iterative/blog-tpi-bees and my impatience resulted in an error... 🔥
git clone git@github.com:iterative/blog-tpi-bees.git
cd blog-tpi-bees/
vim main.tf
terraform init
terraform apply
# 3 minutes later I decide that is too long and Ctrl-C
terraform destroy
vim main.tf #change to a different region
terraform apply
# ERR

Relevant terraform outputs:
terraform init
dabarnes@ubuntu:~/tests/blog-tpi-bees$ terraform init

Initializing the backend...

Initializing provider plugins...
- Finding iterative/iterative versions matching ">= 0.9.9"...
- Installing iterative/iterative v0.10.9...
- Installed iterative/iterative v0.10.9 (self-signed, key ID 910A9EF2910B1E37)

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 created a lock file .terraform.lock.hcl to record the provider
selections it made above. Include this file in your version control repository
so that Terraform can guarantee to make the same selections by default when
you run "terraform init" in the future.

Terraform has been successfully initialized!

You may now begin working with Terraform. Try running "terraform plan" to see
any changes that are required for your infrastructure. All Terraform commands
should now work.

If you ever set or change modules or backend configuration for Terraform,
rerun this command to reinitialize your working directory. If you forget, other
commands will detect it and remind you to do so if necessary.

1st terraform apply
dabarnes@ubuntu:~/tests/blog-tpi-bees$ terraform apply
2022-04-26T16:23:06.850-0700 [INFO]  provider: configuring client automatic mTLS
2022-04-26T16:23:06.881-0700 [INFO]  provider.terraform-provider-iterative_v0.10.9: configuring server automatic mTLS: timestamp=2022-04-26T16:23:06.881-0700
2022-04-26T16:23:06.905-0700 [INFO]  provider: configuring client automatic mTLS
2022-04-26T16:23:06.937-0700 [INFO]  provider.terraform-provider-iterative_v0.10.9: configuring server automatic mTLS: timestamp=2022-04-26T16:23:06.937-0700
2022-04-26T16:23:06.958-0700 [INFO]  provider.terraform-provider-iterative_v0.10.9: 2022/04/26 16:23:06 [WARN] Truncating attribute path of 0 diagnostics for TypeSet: timestamp=2022-04-26T16:23:06.958-0700
2022-04-26T16:23:06.961-0700 [INFO]  provider: configuring client automatic mTLS
2022-04-26T16:23:06.993-0700 [INFO]  provider.terraform-provider-iterative_v0.10.9: configuring server automatic mTLS: timestamp=2022-04-26T16:23:06.993-0700
2022-04-26T16:23:07.016-0700 [INFO]  provider.terraform-provider-iterative_v0.10.9: 2022/04/26 16:23:07 [WARN] Truncating attribute path of 0 diagnostics for TypeSet: timestamp=2022-04-26T16:23:07.016-0700

Terraform used the selected providers to generate the following execution plan. Resource actions are indicated with the following symbols:
  + create

Terraform will perform the following actions:

  # iterative_task.tpi-examples-basic will be created
  + resource "iterative_task" "tpi-examples-basic" {
      + addresses       = (known after apply)
      + cloud           = "aws"
      + disk_size       = 30
      + events          = (known after apply)
      + id              = (known after apply)
      + image           = "ubuntu"
      + logs            = (known after apply)
      + machine         = "t3.small"
      + name            = "tpi-examples-basic "
      + parallelism     = 1
      + region          = "us-east-2"
      + script          = <<-EOT
            #!/bin/bash
            sudo apt update
            sudo apt install -y python3-pip
            pip3 install -r requirements.txt
            python3 src/train.py
        EOT
      + spot            = 0
      + ssh_private_key = (sensitive value)
      + ssh_public_key  = (sensitive value)
      + status          = (known after apply)
      + timeout         = 86400

      + storage {
          + output  = "shared"
          + workdir = "."
        }
    }

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

Do you want to perform these actions?
  Terraform will perform the actions described above.
  Only 'yes' will be accepted to approve.

  Enter a value: yes

2022-04-26T16:23:10.644-0700 [INFO]  provider: configuring client automatic mTLS
2022-04-26T16:23:10.678-0700 [INFO]  provider.terraform-provider-iterative_v0.10.9: configuring server automatic mTLS: timestamp=2022-04-26T16:23:10.678-0700
2022-04-26T16:23:10.702-0700 [INFO]  provider.terraform-provider-iterative_v0.10.9: 2022/04/26 16:23:10 [WARN] Truncating attribute path of 0 diagnostics for TypeSet: timestamp=2022-04-26T16:23:10.702-0700
iterative_task.tpi-examples-basic: Creating...
2022-04-26T16:23:10.704-0700 [INFO]  provider.terraform-provider-iterative_v0.10.9: 2022/04/26 16:23:10 [DEBUG] setting computed for "addresses" from ComputedKeys: timestamp=2022-04-26T16:23:10.704-0700
2022-04-26T16:23:10.704-0700 [INFO]  provider.terraform-provider-iterative_v0.10.9: 2022/04/26 16:23:10 [DEBUG] setting computed for "events" from ComputedKeys: timestamp=2022-04-26T16:23:10.704-0700
2022-04-26T16:23:10.704-0700 [INFO]  provider.terraform-provider-iterative_v0.10.9: 2022/04/26 16:23:10 [DEBUG] setting computed for "logs" from ComputedKeys: timestamp=2022-04-26T16:23:10.704-0700
2022-04-26T16:23:10.704-0700 [INFO]  provider.terraform-provider-iterative_v0.10.9: 2022/04/26 16:23:10 [DEBUG] setting computed for "status" from ComputedKeys: timestamp=2022-04-26T16:23:10.704-0700
TPI [INFO] Creation may take several minutes (consider increasing `timeout` https://registry.terraform.io/providers/iterative/iterative/latest/docs/resources/task#timeout).

Interrupt received.
Please wait for Terraform to exit or data loss may occur.
Gracefully shutting down...

2022-04-26T16:26:18.289-0700 [INFO]  provider.terraform-provider-iterative_v0.10.9: 2022/04/26 16:26:18 ERROR : data/bee_imgs/bee_imgs/016_038.png: Failed to copy: RequestCanceled: request context canceled
caused by: context canceled: timestamp=2022-04-26T16:26:18.280-0700
2022-04-26T16:26:18.289-0700 [INFO]  provider.terraform-provider-iterative_v0.10.9: 2022/04/26 16:26:18 ERROR : data/bee_imgs/bee_imgs/016_011.png: Failed to copy: RequestCanceled: request context canceled
caused by: context canceled: timestamp=2022-04-26T16:26:18.280-0700
2022-04-26T16:26:18.289-0700 [INFO]  provider.terraform-provider-iterative_v0.10.9: 2022/04/26 16:26:18 ERROR : data/bee_imgs/bee_imgs/016_004.png: Failed to copy: RequestCanceled: request context canceled
caused by: context canceled: timestamp=2022-04-26T16:26:18.280-0700
2022-04-26T16:26:18.289-0700 [INFO]  provider.terraform-provider-iterative_v0.10.9: 2022/04/26 16:26:18 ERROR : data/bee_imgs/bee_imgs/016_010.png: Failed to copy: RequestCanceled: request context canceled
caused by: context canceled: timestamp=2022-04-26T16:26:18.280-0700
╷
│ Error: execution halted
│
│
╵
╷
│ Error: execution halted
│
│
╵
╷
│ Error: RequestCanceled: request context canceled
│ caused by: context canceled
│
│   with iterative_task.tpi-examples-basic,
│   on main.tf line 5, in resource "iterative_task" "tpi-examples-basic":
│    5: resource "iterative_task" "tpi-examples-basic" {
│
╵
╷
│ Error: operation error Auto Scaling: DeleteAutoScalingGroup, https response error StatusCode: 0, RequestID: , canceled, context canceled
│
│   with iterative_task.tpi-examples-basic,
│   on main.tf line 5, in resource "iterative_task" "tpi-examples-basic":
│    5: resource "iterative_task" "tpi-examples-basic" {
│
╵

terraform destroy
dabarnes@ubuntu:~/tests/blog-tpi-bees$ terraform destroy
2022-04-26T16:26:23.544-0700 [INFO]  provider: configuring client automatic mTLS
2022-04-26T16:26:23.577-0700 [INFO]  provider.terraform-provider-iterative_v0.10.9: configuring server automatic mTLS: timestamp=2022-04-26T16:26:23.577-0700
2022-04-26T16:26:23.602-0700 [INFO]  provider: configuring client automatic mTLS
2022-04-26T16:26:23.633-0700 [INFO]  provider.terraform-provider-iterative_v0.10.9: configuring server automatic mTLS: timestamp=2022-04-26T16:26:23.633-0700
2022-04-26T16:26:23.655-0700 [INFO]  provider.terraform-provider-iterative_v0.10.9: 2022/04/26 16:26:23 [WARN] Truncating attribute path of 0 diagnostics for TypeSet: timestamp=2022-04-26T16:26:23.655-0700
2022-04-26T16:26:23.658-0700 [INFO]  provider: configuring client automatic mTLS
2022-04-26T16:26:23.690-0700 [INFO]  provider.terraform-provider-iterative_v0.10.9: configuring server automatic mTLS: timestamp=2022-04-26T16:26:23.690-0700
iterative_task.tpi-examples-basic: Refreshing state... [id=tpi-tpi-examples-basic-63n5cpxk-2tqun9ry]
TPI [INFO] Reading resources... (this may happen several times)
TPI [INFO] [1/9] Reading DefaultVPC...
TPI [INFO] [2/9] Reading DefaultVPCSubnet...
TPI [INFO] [3/9] Reading Image...
TPI [INFO] [4/9] Reading Bucket...
TPI [INFO] [5/9] Reading SecurityGroup...
TPI [INFO] [6/9] Reading KeyPair...
TPI [INFO] [7/9] Reading Credentials...
TPI [INFO] [8/9] Reading LaunchTemplate...
TPI [INFO] [9/9] Reading AutoScalingGroup...
TPI [INFO] Read completed
TPI [INFO] Reading resources... (this may happen several times)
TPI [INFO] [1/9] Reading DefaultVPC...
TPI [INFO] [2/9] Reading DefaultVPCSubnet...
TPI [INFO] [3/9] Reading Image...
TPI [INFO] [4/9] Reading Bucket...
TPI [INFO] [5/9] Reading SecurityGroup...
TPI [INFO] [6/9] Reading KeyPair...
TPI [INFO] [7/9] Reading Credentials...
TPI [INFO] [8/9] Reading LaunchTemplate...
TPI [INFO] [9/9] Reading AutoScalingGroup...
TPI [INFO] Read completed
TPI [INFO] Reading resources... (this may happen several times)
TPI [INFO] [1/9] Reading DefaultVPC...
TPI [INFO] [2/9] Reading DefaultVPCSubnet...
TPI [INFO] [3/9] Reading Image...
TPI [INFO] [4/9] Reading Bucket...
TPI [INFO] [5/9] Reading SecurityGroup...
TPI [INFO] [6/9] Reading KeyPair...
TPI [INFO] [7/9] Reading Credentials...
TPI [INFO] [8/9] Reading LaunchTemplate...
TPI [INFO] [9/9] Reading AutoScalingGroup...
TPI [INFO] Read completed
TPI [INFO] aws t3.small in us-east-2
TPI [INFO]
TPI [INFO] Status: queued •
2022-04-26T16:26:33.846-0700 [INFO]  provider.terraform-provider-iterative_v0.10.9: 2022/04/26 16:26:33 [WARN] Truncating attribute path of 0 diagnostics for TypeSet: timestamp=2022-04-26T16:26:33.846-0700
2022-04-26T16:26:33.854-0700 [INFO]  provider: configuring client automatic mTLS
2022-04-26T16:26:33.893-0700 [INFO]  provider.terraform-provider-iterative_v0.10.9: configuring server automatic mTLS: timestamp=2022-04-26T16:26:33.893-0700

Terraform used the selected providers to generate the following execution plan. Resource actions are indicated with the following symbols:
  - destroy

Terraform will perform the following actions:

  # iterative_task.tpi-examples-basic will be destroyed
  - resource "iterative_task" "tpi-examples-basic" {
      - addresses       = [] -> null
      - cloud           = "aws" -> null
      - disk_size       = 30 -> null
      - events          = [] -> null
      - id              = "tpi-tpi-examples-basic-63n5cpxk-2tqun9ry" -> null
      - image           = "ubuntu" -> null
      - logs            = [] -> null
      - machine         = "t3.small" -> null
      - name            = "tpi-examples-basic " -> null
      - parallelism     = 1 -> null
      - region          = "us-east-2" -> null
      - script          = <<-EOT
            #!/bin/bash
            sudo apt update
            sudo apt install -y python3-pip
            pip3 install -r requirements.txt
            python3 src/train.py
        EOT -> null
      - spot            = 0 -> null
      - ssh_private_key = (sensitive value)
      - ssh_public_key  = (sensitive value)
      - status          = {
          - "running" = 0
        } -> null
      - timeout         = 86400 -> null

      - storage {
          - output  = "shared" -> null
          - workdir = "." -> null
        }
    }

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

  Terraform will destroy all your managed infrastructure, as shown above.
  There is no undo. Only 'yes' will be accepted to confirm.

  Enter a value: yes

2022-04-26T16:26:37.305-0700 [INFO]  provider: configuring client automatic mTLS
2022-04-26T16:26:37.340-0700 [INFO]  provider.terraform-provider-iterative_v0.10.9: configuring server automatic mTLS: timestamp=2022-04-26T16:26:37.338-0700
iterative_task.tpi-examples-basic: Destroying... [id=tpi-tpi-examples-basic-63n5cpxk-2tqun9ry]
TPI [INFO] Destruction may take several minutes (consider increasing `timeout` https://registry.terraform.io/providers/iterative/iterative/latest/docs/resources/task#timeout).  Resources: 1 destroyed.

2nd terraform apply
dabarnes@ubuntu:~/tests/blog-tpi-bees$ terraform apply
2022-04-26T16:28:28.907-0700 [INFO]  provider: configuring client automatic mTLS
2022-04-26T16:28:28.942-0700 [INFO]  provider.terraform-provider-iterative_v0.10.9: configuring server automatic mTLS: timestamp=2022-04-26T16:28:28.942-0700
2022-04-26T16:28:28.965-0700 [INFO]  provider: configuring client automatic mTLS
2022-04-26T16:28:28.996-0700 [INFO]  provider.terraform-provider-iterative_v0.10.9: configuring server automatic mTLS: timestamp=2022-04-26T16:28:28.995-0700
2022-04-26T16:28:29.019-0700 [INFO]  provider.terraform-provider-iterative_v0.10.9: 2022/04/26 16:28:29 [WARN] Truncating attribute path of 0 diagnostics for TypeSet: timestamp=2022-04-26T16:28:29.019-0700
2022-04-26T16:28:29.022-0700 [INFO]  provider: configuring client automatic mTLS
2022-04-26T16:28:29.053-0700 [INFO]  provider.terraform-provider-iterative_v0.10.9: configuring server automatic mTLS: timestamp=2022-04-26T16:28:29.053-0700
2022-04-26T16:28:29.075-0700 [INFO]  provider.terraform-provider-iterative_v0.10.9: 2022/04/26 16:28:29 [WARN] Truncating attribute path of 0 diagnostics for TypeSet: timestamp=2022-04-26T16:28:29.075-0700

Terraform used the selected providers to generate the following execution plan. Resource actions are indicated with the following symbols:
  + create

Terraform will perform the following actions:

  # iterative_task.tpi-examples-basic will be created
  + resource "iterative_task" "tpi-examples-basic" {
      + addresses       = (known after apply)
      + cloud           = "aws"
      + disk_size       = 30
      + events          = (known after apply)
      + id              = (known after apply)
      + image           = "ubuntu"
      + logs            = (known after apply)
      + machine         = "t3.small"
      + name            = "tpi-examples-basic "
      + parallelism     = 1
      + region          = "us-west"
      + script          = <<-EOT
            #!/bin/bash
            sudo apt update
            sudo apt install -y python3-pip
            pip3 install -r requirements.txt
            python3 src/train.py
        EOT
      + spot            = 0
      + ssh_private_key = (sensitive value)
      + ssh_public_key  = (sensitive value)
      + status          = (known after apply)
      + timeout         = 86400

      + storage {
          + output  = "shared"
          + workdir = "."
        }
    }

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

Do you want to perform these actions?
  Terraform will perform the actions described above.
  Only 'yes' will be accepted to approve.

  Enter a value: yes

2022-04-26T16:28:30.881-0700 [INFO]  provider: configuring client automatic mTLS
2022-04-26T16:28:30.912-0700 [INFO]  provider.terraform-provider-iterative_v0.10.9: configuring server automatic mTLS: timestamp=2022-04-26T16:28:30.912-0700
2022-04-26T16:28:30.935-0700 [INFO]  provider.terraform-provider-iterative_v0.10.9: 2022/04/26 16:28:30 [WARN] Truncating attribute path of 0 diagnostics for TypeSet: timestamp=2022-04-26T16:28:30.935-0700
iterative_task.tpi-examples-basic: Creating...
2022-04-26T16:28:30.939-0700 [INFO]  provider.terraform-provider-iterative_v0.10.9: 2022/04/26 16:28:30 [DEBUG] setting computed for "events" from ComputedKeys: timestamp=2022-04-26T16:28:30.939-0700
2022-04-26T16:28:30.939-0700 [INFO]  provider.terraform-provider-iterative_v0.10.9: 2022/04/26 16:28:30 [DEBUG] setting computed for "addresses" from ComputedKeys: timestamp=2022-04-26T16:28:30.939-0700
2022-04-26T16:28:30.939-0700 [INFO]  provider.terraform-provider-iterative_v0.10.9: 2022/04/26 16:28:30 [DEBUG] setting computed for "status" from ComputedKeys: timestamp=2022-04-26T16:28:30.939-0700
2022-04-26T16:28:30.939-0700 [INFO]  provider.terraform-provider-iterative_v0.10.9: 2022/04/26 16:28:30 [DEBUG] setting computed for "logs" from ComputedKeys: timestamp=2022-04-26T16:28:30.939-0700
TPI [INFO] Creation may take several minutes (consider increasing `timeout` https://registry.terraform.io/providers/iterative/iterative/latest/docs/resources/task#timeout). Please wait.
╷
│ Error: operation error S3: CreateBucket, https response error StatusCode: 409, RequestID: 59A2YHE2FD93V5VE, HostID: ZhiCW18MkagKK0DmFj2pSZvrkLAANKr3KtFG28hidkuqXbSbe4lO0OUeBhNjxEae5Oh3zojGPts=, api error OperationAborted: A conflicting conditional operation is currently in progress against this resource. Please try again.
│
│   with iterative_task.tpi-examples-basic,
│   on main.tf line 5, in resource "iterative_task" "tpi-examples-basic":
│    5: resource "iterative_task" "tpi-examples-basic" {
│
╵
╷
│ Error: failed to create
│
│   with iterative_task.tpi-examples-basic,
│   on main.tf line 5, in resource "iterative_task" "tpi-examples-basic":
│    5: resource "iterative_task" "tpi-examples-basic" {
│
╵

TF_LOG_PROVIDER=TRACE terraform apply
dabarnes@ubuntu:~/tests/blog-tpi-bees$ TF_LOG_PROVIDER=TRACE terraform apply
2022-04-26T16:35:20.724-0700 [INFO]  provider: configuring client automatic mTLS
2022-04-26T16:35:20.731-0700 [DEBUG] provider: starting plugin: path=.terraform/providers/registry.terraform.io/iterative/iterative/0.10.9/linux_amd64/terraform-provider-iterative_v0.10.9 args=[.terraform/providers/registry.terraform.io/iterative/iterative/0.10.9/linux_amd64/terraform-provider-iterative_v0.10.9]
2022-04-26T16:35:20.732-0700 [DEBUG] provider: plugin started: path=.terraform/providers/registry.terraform.io/iterative/iterative/0.10.9/linux_amd64/terraform-provider-iterative_v0.10.9 pid=55570
2022-04-26T16:35:20.732-0700 [DEBUG] provider: waiting for RPC address: path=.terraform/providers/registry.terraform.io/iterative/iterative/0.10.9/linux_amd64/terraform-provider-iterative_v0.10.9
2022-04-26T16:35:20.756-0700 [INFO]  provider.terraform-provider-iterative_v0.10.9: configuring server automatic mTLS: timestamp=2022-04-26T16:35:20.756-0700
2022-04-26T16:35:20.764-0700 [DEBUG] provider: using plugin: version=5
2022-04-26T16:35:20.764-0700 [DEBUG] provider.terraform-provider-iterative_v0.10.9: plugin address: address=/tmp/plugin181832840 network=unix timestamp=2022-04-26T16:35:20.763-0700
2022-04-26T16:35:20.775-0700 [TRACE] provider.stdio: waiting for stdio data
2022-04-26T16:35:20.777-0700 [DEBUG] provider.stdio: received EOF, stopping recv loop: err="rpc error: code = Unavailable desc = transport is closing"
2022-04-26T16:35:20.779-0700 [DEBUG] provider: plugin process exited: path=.terraform/providers/registry.terraform.io/iterative/iterative/0.10.9/linux_amd64/terraform-provider-iterative_v0.10.9 pid=55570
2022-04-26T16:35:20.779-0700 [DEBUG] provider: plugin exited
2022-04-26T16:35:20.780-0700 [INFO]  provider: configuring client automatic mTLS
2022-04-26T16:35:20.787-0700 [DEBUG] provider: starting plugin: path=.terraform/providers/registry.terraform.io/iterative/iterative/0.10.9/linux_amd64/terraform-provider-iterative_v0.10.9 args=[.terraform/providers/registry.terraform.io/iterative/iterative/0.10.9/linux_amd64/terraform-provider-iterative_v0.10.9]
2022-04-26T16:35:20.788-0700 [DEBUG] provider: plugin started: path=.terraform/providers/registry.terraform.io/iterative/iterative/0.10.9/linux_amd64/terraform-provider-iterative_v0.10.9 pid=55578
2022-04-26T16:35:20.788-0700 [DEBUG] provider: waiting for RPC address: path=.terraform/providers/registry.terraform.io/iterative/iterative/0.10.9/linux_amd64/terraform-provider-iterative_v0.10.9
2022-04-26T16:35:20.812-0700 [INFO]  provider.terraform-provider-iterative_v0.10.9: configuring server automatic mTLS: timestamp=2022-04-26T16:35:20.811-0700
2022-04-26T16:35:20.820-0700 [DEBUG] provider.terraform-provider-iterative_v0.10.9: plugin address: address=/tmp/plugin2892143703 network=unix timestamp=2022-04-26T16:35:20.819-0700
2022-04-26T16:35:20.820-0700 [DEBUG] provider: using plugin: version=5
2022-04-26T16:35:20.831-0700 [TRACE] provider.stdio: waiting for stdio data
2022-04-26T16:35:20.835-0700 [INFO]  provider.terraform-provider-iterative_v0.10.9: 2022/04/26 16:35:20 [WARN] Truncating attribute path of 0 diagnostics for TypeSet: timestamp=2022-04-26T16:35:20.835-0700
2022-04-26T16:35:20.836-0700 [DEBUG] provider.stdio: received EOF, stopping recv loop: err="rpc error: code = Unavailable desc = transport is closing"
2022-04-26T16:35:20.838-0700 [DEBUG] provider: plugin process exited: path=.terraform/providers/registry.terraform.io/iterative/iterative/0.10.9/linux_amd64/terraform-provider-iterative_v0.10.9 pid=55578
2022-04-26T16:35:20.838-0700 [DEBUG] provider: plugin exited
2022-04-26T16:35:20.838-0700 [INFO]  provider: configuring client automatic mTLS
2022-04-26T16:35:20.846-0700 [DEBUG] provider: starting plugin: path=.terraform/providers/registry.terraform.io/iterative/iterative/0.10.9/linux_amd64/terraform-provider-iterative_v0.10.9 args=[.terraform/providers/registry.terraform.io/iterative/iterative/0.10.9/linux_amd64/terraform-provider-iterative_v0.10.9]
2022-04-26T16:35:20.846-0700 [DEBUG] provider: plugin started: path=.terraform/providers/registry.terraform.io/iterative/iterative/0.10.9/linux_amd64/terraform-provider-iterative_v0.10.9 pid=55587
2022-04-26T16:35:20.846-0700 [DEBUG] provider: waiting for RPC address: path=.terraform/providers/registry.terraform.io/iterative/iterative/0.10.9/linux_amd64/terraform-provider-iterative_v0.10.9
2022-04-26T16:35:20.870-0700 [INFO]  provider.terraform-provider-iterative_v0.10.9: configuring server automatic mTLS: timestamp=2022-04-26T16:35:20.870-0700
2022-04-26T16:35:20.878-0700 [DEBUG] provider.terraform-provider-iterative_v0.10.9: plugin address: address=/tmp/plugin3554886002 network=unix timestamp=2022-04-26T16:35:20.878-0700
2022-04-26T16:35:20.878-0700 [DEBUG] provider: using plugin: version=5
2022-04-26T16:35:20.890-0700 [TRACE] provider.stdio: waiting for stdio data
2022-04-26T16:35:20.893-0700 [INFO]  provider.terraform-provider-iterative_v0.10.9: 2022/04/26 16:35:20 [WARN] Truncating attribute path of 0 diagnostics for TypeSet: timestamp=2022-04-26T16:35:20.893-0700
2022-04-26T16:35:20.895-0700 [DEBUG] provider.stdio: received EOF, stopping recv loop: err="rpc error: code = Unavailable desc = transport is closing"
2022-04-26T16:35:20.897-0700 [DEBUG] provider: plugin process exited: path=.terraform/providers/registry.terraform.io/iterative/iterative/0.10.9/linux_amd64/terraform-provider-iterative_v0.10.9 pid=55587
2022-04-26T16:35:20.897-0700 [DEBUG] provider: plugin exited

Terraform used the selected providers to generate the following execution plan. Resource actions are indicated with the following symbols:
  + create

Terraform will perform the following actions:

  # iterative_task.tpi-examples-basic will be created
  + resource "iterative_task" "tpi-examples-basic" {
      + addresses       = (known after apply)
      + cloud           = "aws"
      + disk_size       = 30
      + events          = (known after apply)
      + id              = (known after apply)
      + image           = "ubuntu"
      + logs            = (known after apply)
      + machine         = "t3.small"
      + name            = "tpi-examples-basic "
      + parallelism     = 1
      + region          = "us-west"
      + script          = <<-EOT
            #!/bin/bash
            sudo apt update
            sudo apt install -y python3-pip
            pip3 install -r requirements.txt
            python3 src/train.py
        EOT
      + spot            = 0
      + ssh_private_key = (sensitive value)
      + ssh_public_key  = (sensitive value)
      + status          = (known after apply)
      + timeout         = 86400

      + storage {
          + output  = "shared"
          + workdir = "."
        }
    }

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

Do you want to perform these actions?
  Terraform will perform the actions described above.
  Only 'yes' will be accepted to approve.

  Enter a value: yes

2022-04-26T16:35:24.512-0700 [INFO]  provider: configuring client automatic mTLS
2022-04-26T16:35:24.520-0700 [DEBUG] provider: starting plugin: path=.terraform/providers/registry.terraform.io/iterative/iterative/0.10.9/linux_amd64/terraform-provider-iterative_v0.10.9 args=[.terraform/providers/registry.terraform.io/iterative/iterative/0.10.9/linux_amd64/terraform-provider-iterative_v0.10.9]
2022-04-26T16:35:24.520-0700 [DEBUG] provider: plugin started: path=.terraform/providers/registry.terraform.io/iterative/iterative/0.10.9/linux_amd64/terraform-provider-iterative_v0.10.9 pid=55612
2022-04-26T16:35:24.520-0700 [DEBUG] provider: waiting for RPC address: path=.terraform/providers/registry.terraform.io/iterative/iterative/0.10.9/linux_amd64/terraform-provider-iterative_v0.10.9
2022-04-26T16:35:24.546-0700 [INFO]  provider.terraform-provider-iterative_v0.10.9: configuring server automatic mTLS: timestamp=2022-04-26T16:35:24.546-0700
2022-04-26T16:35:24.554-0700 [DEBUG] provider: using plugin: version=5
2022-04-26T16:35:24.554-0700 [DEBUG] provider.terraform-provider-iterative_v0.10.9: plugin address: address=/tmp/plugin1681772421 network=unix timestamp=2022-04-26T16:35:24.553-0700
2022-04-26T16:35:24.567-0700 [TRACE] provider.stdio: waiting for stdio data
2022-04-26T16:35:24.570-0700 [INFO]  provider.terraform-provider-iterative_v0.10.9: 2022/04/26 16:35:24 [WARN] Truncating attribute path of 0 diagnostics for TypeSet: timestamp=2022-04-26T16:35:24.570-0700
iterative_task.tpi-examples-basic: Creating...
2022-04-26T16:35:24.572-0700 [INFO]  provider.terraform-provider-iterative_v0.10.9: 2022/04/26 16:35:24 [DEBUG] setting computed for "events" from ComputedKeys: timestamp=2022-04-26T16:35:24.572-0700
2022-04-26T16:35:24.572-0700 [INFO]  provider.terraform-provider-iterative_v0.10.9: 2022/04/26 16:35:24 [DEBUG] setting computed for "logs" from ComputedKeys: timestamp=2022-04-26T16:35:24.572-0700
2022-04-26T16:35:24.572-0700 [INFO]  provider.terraform-provider-iterative_v0.10.9: 2022/04/26 16:35:24 [DEBUG] setting computed for "addresses" from ComputedKeys: timestamp=2022-04-26T16:35:24.572-0700
2022-04-26T16:35:24.572-0700 [INFO]  provider.terraform-provider-iterative_v0.10.9: 2022/04/26 16:35:24 [DEBUG] setting computed for "status" from ComputedKeys: timestamp=2022-04-26T16:35:24.572-0700
TPI [INFO] Creation may take several minutes (consider increasing `timeout` https://registry.terraform.io/providers/iterative/iterative/latest/docs/resources/task#timeout). Please wait.
2022-04-26T16:35:24.574-0700 [TRACE] provider.stdio: received data: channel=STDERR len=110
2022-04-26T16:35:24.574-0700 [TRACE] provider.stdio: waiting for stdio data
2022-04-26T16:35:24.857-0700 [TRACE] provider.stdio: received data: channel=STDERR len=55
2022-04-26T16:35:24.857-0700 [TRACE] provider.stdio: waiting for stdio data
2022-04-26T16:35:24.936-0700 [TRACE] provider.stdio: received data: channel=STDERR len=55
2022-04-26T16:35:24.936-0700 [TRACE] provider.stdio: waiting for stdio data
2022-04-26T16:35:25.481-0700 [TRACE] provider.stdio: received data: channel=STDERR len=55
2022-04-26T16:35:25.481-0700 [TRACE] provider.stdio: waiting for stdio data
2022-04-26T16:35:25.988-0700 [TRACE] provider.stdio: received data: channel=STDERR len=220
2022-04-26T16:35:25.988-0700 [TRACE] provider.stdio: waiting for stdio data
2022-04-26T16:35:26.070-0700 [TRACE] provider.stdio: received data: channel=STDERR len=55
2022-04-26T16:35:26.070-0700 [TRACE] provider.stdio: waiting for stdio data
2022-04-26T16:35:26.153-0700 [TRACE] provider.stdio: received data: channel=STDERR len=55
2022-04-26T16:35:26.153-0700 [TRACE] provider.stdio: waiting for stdio data
2022-04-26T16:35:26.422-0700 [TRACE] provider.stdio: received data: channel=STDERR len=55
2022-04-26T16:35:26.422-0700 [TRACE] provider.stdio: waiting for stdio data
2022-04-26T16:35:26.458-0700 [TRACE] provider.stdio: received data: channel=STDERR len=55
2022-04-26T16:35:26.458-0700 [TRACE] provider.stdio: waiting for stdio data
2022-04-26T16:35:26.823-0700 [TRACE] provider.stdio: received data: channel=STDERR len=55
2022-04-26T16:35:26.823-0700 [TRACE] provider.stdio: waiting for stdio data
2022-04-26T16:35:26.887-0700 [TRACE] provider.stdio: received data: channel=STDERR len=55
2022-04-26T16:35:26.887-0700 [TRACE] provider.stdio: waiting for stdio data
2022-04-26T16:35:27.185-0700 [TRACE] provider.stdio: received data: channel=STDERR len=55
2022-04-26T16:35:27.186-0700 [TRACE] provider.stdio: waiting for stdio data
2022-04-26T16:35:27.265-0700 [TRACE] provider.stdio: received data: channel=STDERR len=110
2022-04-26T16:35:27.265-0700 [TRACE] provider.stdio: waiting for stdio data
2022-04-26T16:35:27.305-0700 [TRACE] provider.stdio: received data: channel=STDERR len=55
2022-04-26T16:35:27.305-0700 [TRACE] provider.stdio: waiting for stdio data
╷
│ Error: operation error S3: CreateBucket, https response error StatusCode: 409, RequestID: AHVV3JBFBP0KJNW2, HostID: aQNQT3SprqbnqOnO6BqftOJazOqhXLb2srjIDM7eZeiOR9zMQl8hBvws4yzZEhJ8WfOv9n3rtyw=, api error OperationAborted: A conflicting conditional operation is currently in progress against this resource. Please try again.
│
│   with iterative_task.tpi-examples-basic,
│   on main.tf line 5, in resource "iterative_task" "tpi-examples-basic":
│    5: resource "iterative_task" "tpi-examples-basic" {
│
╵
╷
│ Error: failed to create
│
│   with iterative_task.tpi-examples-basic,
│   on main.tf line 5, in resource "iterative_task" "tpi-examples-basic":
│    5: resource "iterative_task" "tpi-examples-basic" {
│
╵
2022-04-26T16:35:27.309-0700 [DEBUG] provider.stdio: received EOF, stopping recv loop: err="rpc error: code = Unavailable desc = transport is closing"
2022-04-26T16:35:27.312-0700 [DEBUG] provider: plugin process exited: path=.terraform/providers/registry.terraform.io/iterative/iterative/0.10.9/linux_amd64/terraform-provider-iterative_v0.10.9 pid=55612
2022-04-26T16:35:27.312-0700 [DEBUG] provider: plugin exited

name - (Optional) Discouraged and may be removed in future - change the resource name instead, i.e. resource "iterative_task" "some_other_example_name". Deterministic task name (e.g. name="Hello, World!" always produces id="tpi-hello-world-5kz6ldls-57wo7rsp").

That's the “expected” behavior and there is nothing we can do to solve this issue. You can avoid it by not specifying the name field, so a new name is generated for every run.

hmmm, but why the name a conflict for the create bucket operation?
AWS event:
  "eventTime": "2022-04-27T00:21:03Z",
    "eventSource": "s3.amazonaws.com",
    "eventName": "CreateBucket",
    "awsRegion": "us-west-1",
    "sourceIPAddress": "<IP_ADDRESS>",
    "userAgent": "[aws-sdk-go-v2/1.11.0 os/linux lang/go/1.17.8 md/GOOS/linux md/GOARCH/amd64 api/s3/1.18.0]",
    "errorCode": "OperationAborted",
    "errorMessage": "A conflicting conditional operation is currently in progress against this resource. Please try again.",
    "requestParameters": {
        "CreateBucketConfiguration": {
            "LocationConstraint": "us-west-1",
            "xmlns": "http://s3.amazonaws.com/doc/2006-03-01/"
        },
        "bucketName": "tpi-tpi-examples-basic-63n5cpxk-2tqun9ry",
        "Host": "tpi-tpi-examples-basic-63n5cpxk-2tqun9ry.s3.us-west-1.amazonaws.com"
    },
    "responseElements": null,
    "additionalEventData": {
        "SignatureVersion": "SigV4",
        "CipherSuite": "ECDHE-RSA-AES128-GCM-SHA256",
        "bytesTransferredIn": 153,
        "AuthenticationMethod": "AuthHeader",
        "x-amz-id-2": "d5ltZLOpYM0MCnDXf0cj/188ucBmIJW/IwMgeSUOyGlwHpt45y7hlTVEgWLIWlz1HIoD292Ztwc=",
        "bytesTransferredOut": 335
    },
    "requestID": "89DCAM5G4V7HMDB9",
    "eventID": "e62864f9-84dd-4df8-afaa-4cd7e92f19f2",
    "readOnly": false,
    "eventType": "AwsApiCall",
    "managementEvent": true,
    "recipientAccountId": "548501963152",
    "eventCategory": "Management",
    "tlsDetails": {
        "tlsVersion": "TLSv1.2",
        "cipherSuite": "ECDHE-RSA-AES128-GCM-SHA256",
        "clientProvidedHostHeader": "tpi-tpi-examples-basic-63n5cpxk-2tqun9ry.s3.us-west-1.amazonaws.com"
    }
}

why the name a conflict for the create bucket operation?

Because the old & new buckets had exactly the same name.

You were trying to create a new bucket while the old one was still queued for deletion.

I see, and that takes time on the AWS for them to fully complete, and thus the error.


Can't format with prettier twig-melody plugin

Hi,
I added this prettier plugin for html twig files, and installed a local prettier in my dev dependencies.
But when I try to format a "html.twig" file, here's the error I get :
TypeError: Cannot read property 'replace' of undefined     at /home/isos/.config/nvim/plugged/coc.nvim/build/index.js:32818:41     at Array.forEach (<anonymous>)     at Document.applyEdits (/home/isos/.config/nvim/plugged/coc.nvim/build/index.js:32817:15)     at Object.<anonymous> (/home/isos/.config/coc/extensions/node_modules/coc-prettier/lib/index.js:229:32)     at Generator.next (<anonymous>)     at fulfilled (/home/isos/.config/coc/extensions/node_modules/coc-prettier/lib/index.js:115:58)
When I format with the local prettier in node_modules, it works, the local prettier doesn't seems to be used for this filetype. Is there something I'm missing ?

I saw on one issues that it's because of the default supported languages, maybe a pull request which ignore the supported languages when a local prettier is installed would solve the problem ? @chemzqm  tell me if that kind of solution can work, I'll see if I can make it.

Any luck with this?
I also have issues getting coc-prettier to work with prettier-plugin-twig-melody even though npx prettier --write works as expected. It seems to have a conflict with something bundled with coc-prettier.
My filetype is html.twig. If I change the filetype to twig, coc-prettier will format it as I expect. I thought prettier.onlyUseLocalVersion could resolve the issue, but it did not help.

:h g:coc_filetype_map

Yes I already use file maps. coc-prettier must have extraneous formatting because of the HTML file type, which is undesirable when using with a Prettier extension for Twig. There should be a way to avoid this unexpected formatting.


System contracts test coverage

https://truffleframework.com/   @RookieLinLucy

Do I need to test these functions: triggerCallback,toBytes and getCodeSize?


Enable file handling with project specific S3 storages

Is your feature request related to a problem? Please describe.
Handling of files over S3 storages is currently restricted to the DigiWF specific storage. Its not possible to handle files in project specific storages.
Describe the solution you'd like
Within a project specific process, it should be possible to handle files with project specific S3 storages.
Describe alternatives you've considered
n/a
Additional context
The S3 client lib starter is already upgraded to handle project specific S3 storages.
https://github.com/it-at-m/digiwf-s3-integration/tree/dev/digiwf-s3-integration-client-starter
Example method:
https://github.com/it-at-m/digiwf-s3-integration/blob/dev/digiwf-s3-integration-client/src/main/java/io/muenchendigital/digiwf/s3/integration/client/repository/DocumentStorageFileRepository.java#L62

Known affected Repos:
https://github.com/it-at-m/digiwf-cosys-integration
https://github.com/it-at-m/digiwf-email-integration


An Error Occurred page in case click on History button

Description the bug
Version test: v1.0.1(137)
Steps:
1.Go to the Tokens screen
2.Click on the History button
3.Observe the history displayed
Actual: An Error Occurred page
https://user-images.githubusercontent.com/117999489/236106311-d3933676-273c-4f25-8c8d-3eee00349bfa.mov
Expect: Display History screen

Version test: v1.0.1(139)
Validation passed.


<IP_ADDRESS>:3000: socket: too many open files

Reporter is not closing connections to the Grafana, after max open files is reached (usually 1024) starts returning Code HTTP 500
Internal Server Error .  It means that after 1024 is reporter not usable.
lsof -p
grafana-r 7654 root    5u     IPv4 38595998      0t0      TCP localhost:51240->localhost:3000 (ESTABLISHED)
grafana-r 7654 root    6u     IPv4 37998345      0t0      TCP localhost:57772->localhost:3000 (ESTABLISHED)
grafana-r 7654 root    7u     IPv4 37998346      0t0      TCP localhost:57774->localhost:3000 (ESTABLISHED)
grafana-r 7654 root    8u     IPv4 37998347      0t0      TCP localhost:57776->localhost:3000 (ESTABLISHED)

x1024
Reporter output:
http: Accept error: accept tcp [::]:8686: accept4: too many open files; retrying in 1s
Grafana Version: 7.2.2
Reporter GIT version.

It there any parameter to force closing connection streams after PDF is read?
Any other workaround (increase max open files does not count)?

Today I have faced the same problem. Temporay added a job to restart reporter service once a day.

Today I have faced the same problem. Temporary added a job to restart reporter service once a day.

how can I restart the reporter?

My solution：Modify the api.go file
First, add the code to import

Then add the following code to the GetDashboard method

Add the same code to the GetPanelPng method

Finally, recompile and install grafana-Reporter

The above is my solution, I am not sure whether it will cause other adverse effects


support for addHttpHeader & sslSecurity

Adding support for addHttpHeader which will help passing plain http headers to the request & sslSecurity

Hi pokryVa, I am not maintaining this repository anymore. I you intend to use this project, I can give you admin rights on the repository, or even on npmjs.org project (do not known if you will be able to push directly from your fork).  Please let me know (If you create a new version with different name from your fork, i will put a message on my repo to explain it is not maintained anymore and redirect people to yours).

Hi, I accept the challenge :) I appreciete your idea to pass the repo. If I'm unable to maintain it (I'm not really a dev, no prior experience to publishing to npm either, but I'll do my best) - I will pass it further too.

I added you as maintainer on npmjs (i supposed you had the same username), you should be able to publish your version and override mine. Let me know if it does not work.


[gsoc] add metrics : [metrics collected] + [local aggregation]

What is the purpose of the change
relevance issues : https://github.com/apache/dubbo/issues/9886,
Add two modules for observability.
Brief changelog
[gsoc] add metrics : [metrics collected] + [local aggregation]
Verifying this change

Checklist

[x] Make sure there is a GitHub_issue field for the change (usually before you start working on it). Trivial changes like typos do not require a GitHub issue. Your pull request should address just this issue, without pulling in other changes - one PR resolves one issue.
[ ] Each commit in the pull request should have a meaningful subject line and body.
[ ] Write a pull request description that is detailed enough to understand what the pull request does, how, and why.
[ ] Check if is necessary to patch to Dubbo 3 if you are work on Dubbo 2.7
[ ] Write necessary unit-test to verify your logic correction, more mock a little better when cross module dependency exist. If the new feature or significant change is committed, please remember to add sample in dubbo samples project.
[ ] Add some description to dubbo-website project if you are requesting to add a feature.
[ ] GitHub Actions works fine on your own branch.
[ ] If this contribution is large, please follow the Software Donation Guide.

Codecov Report

Merging #10331 (2699910) into 3.1 (fcdfe33) will decrease coverage by 0.30%.
The diff coverage is n/a.

@@             Coverage Diff              @@
##                3.1   #10331      +/-   ##
============================================
- Coverage     65.70%   65.40%   -0.31%
- Complexity      319      320       +1
============================================
  Files          1233     1233
  Lines         53736    53695      -41
  Branches       8113     8089      -24
============================================
- Hits          35307    35118     -189
- Misses        14591    14714     +123
- Partials       3838     3863      +25

Impacted Files
Coverage Δ

...in/java/org/apache/dubbo/config/MetricsConfig.java
19.04% <ø> (ø)

...dubbo/remoting/zookeeper/ZookeeperTransporter.java
50.00% <0.00%> (-38.89%)
:arrow_down:

...ng/zookeeper/curator5/Curator5ZookeeperClient.java
43.47% <0.00%> (-28.02%)
:arrow_down:

...dubbo/common/status/support/LoadStatusChecker.java
41.66% <0.00%> (-25.00%)
:arrow_down:

.../remoting/api/SingleProtocolConnectionManager.java
61.53% <0.00%> (-23.08%)
:arrow_down:

...nt/metadata/ServiceInstanceHostPortCustomizer.java
65.78% <0.00%> (-21.06%)
:arrow_down:

...ache/dubbo/remoting/transport/AbstractChannel.java
75.00% <0.00%> (-12.50%)
:arrow_down:

...che/dubbo/registry/client/NopServiceDiscovery.java
44.44% <0.00%> (-11.12%)
:arrow_down:

...mmon/threadpool/support/fixed/FixedThreadPool.java
80.00% <0.00%> (-7.50%)
:arrow_down:

.../common/threadpool/serial/SerializingExecutor.java
70.37% <0.00%> (-7.41%)
:arrow_down:

... and 100 more

Continue to review full report at Codecov.

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


Create and Save Map

Demonstrates creating and saving a map to a user's own portal.

@vGandhi and @john0005 could you please review?

Some initial thoughts. When I can actually get it to login in I will review some more.

will address after next week

@john0005 This is ready for a second review.

Looks good. If we could some how add what exactly what the user needs enter to run the application that would be nice.
I know for the portal url you can put http://www.arcgis.com/ and the Client ID is easy to find out once you make you application. The only hard part is what to put for Redirect URI.
I feel like the sample will be hard to get working if you don't know how to get the Redirect URI working. I know the one that you sent me can work for anyone but not sure for if that can be give out.

@john0005 Can you take another look?

Looks good. One thing that I noticed that could be added is a Progress Indicator when the save button is hit.

@john0005 good call. I've added the progress indicator. Merging.


Compilation failure with glibc 2.17 - no getentropy available

Hi, thanks first of all for this great allocator! :) We at tremor love it!
Yesterday we tried to compile it on our CI system to create a release and it failed.
The CI system is this slightly outdated centos docker image: https://github.com/tremor-rs/tremor-runtime/blob/main/packaging/builder-images/Dockerfile.x86_64-unknown-linux-gnu
It contains GCC 9.3.1 and glibc 2.17 and we use it to compile our Rust application including the snmalloc-rs binding which points to: https://github.com/microsoft/snmalloc/tree/e3a7eab78923e84cb2301797590583279880cf6c
Unfortunately this old glibc doesnt contain getentropy yet, which is included since 2.25.
it fails with the following error message:
 /root/.cargo/registry/src/github.com-1ecc6299db9ec823/snmalloc-sys-0.2.27/snmalloc/src/override/../mem/../mem/../pal/pal_posix.h:294:23: error: 'getentropy' was not declared in this scope; did you mean 'get_entropy64'?
    294 |         if (getentropy(&result, sizeof(result)) != 0)
        |             ~~~~~~~~~~^~~~~~~~~~~~~~~~~~~~~~~~~
        |             get_entropy64

I dont know if it makes sense to provide a fix for such an ancient libc, but wanted to report anyways.

I have attached a lengthy and verbose compilation log, maybe this will shed some light on what is happening:
error: failed to run custom build command for `snmalloc-sys v0.2.27`

Caused by:
  process didn't exit successfully: `/snmalloc_test/target/debug/build/snmalloc-sys-6b891a7b439974c7/build-script-build` (exit code: 101)
  --- stdout
  running: "cmake" "-Wdev" "--debug-output" "/root/.cargo/registry/src/github.com-1ecc6299db9ec823/snmalloc-sys-0.2.27/snmalloc" "-DSNMALLOC_RUST_SUPPORT=ON" "-DCMAKE_INSTALL_PREFIX=/snmalloc_test/target/debug/build/snmalloc-sys-01fa996f117ac3c2/out" "-DCMAKE_C_FLAGS= -ffunction-sections -fdata-sections -fPIC -m64" "-DCMAKE_C_COMPILER=/opt/rh/devtoolset-9/root/usr/bin/cc" "-DCMAKE_CXX_FLAGS= -ffunction-sections -fdata-sections -fPIC -m64" "-DCMAKE_CXX_COMPILER=/opt/rh/devtoolset-9/root/usr/bin/c++" "-DCMAKE_ASM_FLAGS= -ffunction-sections -fdata-sections -fPIC -m64" "-DCMAKE_ASM_COMPILER=/opt/rh/devtoolset-9/root/usr/bin/cc" "-DCMAKE_BUILD_TYPE=Release" "-DCMAKE_VERBOSE_MAKEFILE:BOOL=ON"
  Running with debug output on.
  -- The C compiler identification is GNU 9.3.1
     Called from: [3]   /usr/share/cmake3/Modules/CMakeDetermineCompilerId.cmake
                  [2]   /usr/share/cmake3/Modules/CMakeDetermineCCompiler.cmake
                  [1]   /root/.cargo/registry/src/github.com-1ecc6299db9ec823/snmalloc-sys-0.2.27/snmalloc/CMakeLists.txt
  -- The CXX compiler identification is GNU 9.3.1
     Called from: [3]   /usr/share/cmake3/Modules/CMakeDetermineCompilerId.cmake
                  [2]   /usr/share/cmake3/Modules/CMakeDetermineCXXCompiler.cmake
                  [1]   /root/.cargo/registry/src/github.com-1ecc6299db9ec823/snmalloc-sys-0.2.27/snmalloc/CMakeLists.txt
  -- Check for working C compiler: /opt/rh/devtoolset-9/root/usr/bin/cc
     Called from: [3]   /usr/share/cmake3/Modules/CMakeTestCompilerCommon.cmake
                  [2]   /usr/share/cmake3/Modules/CMakeTestCCompiler.cmake
                  [1]   /root/.cargo/registry/src/github.com-1ecc6299db9ec823/snmalloc-sys-0.2.27/snmalloc/CMakeLists.txt
  -- Check for working C compiler: /opt/rh/devtoolset-9/root/usr/bin/cc - works
     Called from: [3]   /usr/share/cmake3/Modules/CMakeTestCompilerCommon.cmake
                  [2]   /usr/share/cmake3/Modules/CMakeTestCCompiler.cmake
                  [1]   /root/.cargo/registry/src/github.com-1ecc6299db9ec823/snmalloc-sys-0.2.27/snmalloc/CMakeLists.txt
  -- Detecting C compiler ABI info
     Called from: [3]   /usr/share/cmake3/Modules/CMakeDetermineCompilerABI.cmake
                  [2]   /usr/share/cmake3/Modules/CMakeTestCCompiler.cmake
                  [1]   /root/.cargo/registry/src/github.com-1ecc6299db9ec823/snmalloc-sys-0.2.27/snmalloc/CMakeLists.txt
  -- Detecting C compiler ABI info - done
     Called from: [3]   /usr/share/cmake3/Modules/CMakeDetermineCompilerABI.cmake
                  [2]   /usr/share/cmake3/Modules/CMakeTestCCompiler.cmake
                  [1]   /root/.cargo/registry/src/github.com-1ecc6299db9ec823/snmalloc-sys-0.2.27/snmalloc/CMakeLists.txt
  -- Detecting C compile features
     Called from: [3]   /usr/share/cmake3/Modules/CMakeDetermineCompileFeatures.cmake
                  [2]   /usr/share/cmake3/Modules/CMakeTestCCompiler.cmake
                  [1]   /root/.cargo/registry/src/github.com-1ecc6299db9ec823/snmalloc-sys-0.2.27/snmalloc/CMakeLists.txt
  -- Detecting C compile features - done
     Called from: [3]   /usr/share/cmake3/Modules/CMakeDetermineCompileFeatures.cmake
                  [2]   /usr/share/cmake3/Modules/CMakeTestCCompiler.cmake
                  [1]   /root/.cargo/registry/src/github.com-1ecc6299db9ec823/snmalloc-sys-0.2.27/snmalloc/CMakeLists.txt
  -- Check for working CXX compiler: /opt/rh/devtoolset-9/root/usr/bin/c++
     Called from: [3]   /usr/share/cmake3/Modules/CMakeTestCompilerCommon.cmake
                  [2]   /usr/share/cmake3/Modules/CMakeTestCXXCompiler.cmake
                  [1]   /root/.cargo/registry/src/github.com-1ecc6299db9ec823/snmalloc-sys-0.2.27/snmalloc/CMakeLists.txt
  -- Check for working CXX compiler: /opt/rh/devtoolset-9/root/usr/bin/c++ - works
     Called from: [3]   /usr/share/cmake3/Modules/CMakeTestCompilerCommon.cmake
                  [2]   /usr/share/cmake3/Modules/CMakeTestCXXCompiler.cmake
                  [1]   /root/.cargo/registry/src/github.com-1ecc6299db9ec823/snmalloc-sys-0.2.27/snmalloc/CMakeLists.txt
  -- Detecting CXX compiler ABI info
     Called from: [3]   /usr/share/cmake3/Modules/CMakeDetermineCompilerABI.cmake
                  [2]   /usr/share/cmake3/Modules/CMakeTestCXXCompiler.cmake
                  [1]   /root/.cargo/registry/src/github.com-1ecc6299db9ec823/snmalloc-sys-0.2.27/snmalloc/CMakeLists.txt
  -- Detecting CXX compiler ABI info - done
     Called from: [3]   /usr/share/cmake3/Modules/CMakeDetermineCompilerABI.cmake
                  [2]   /usr/share/cmake3/Modules/CMakeTestCXXCompiler.cmake
                  [1]   /root/.cargo/registry/src/github.com-1ecc6299db9ec823/snmalloc-sys-0.2.27/snmalloc/CMakeLists.txt
  -- Detecting CXX compile features
     Called from: [3]   /usr/share/cmake3/Modules/CMakeDetermineCompileFeatures.cmake
                  [2]   /usr/share/cmake3/Modules/CMakeTestCXXCompiler.cmake
                  [1]   /root/.cargo/registry/src/github.com-1ecc6299db9ec823/snmalloc-sys-0.2.27/snmalloc/CMakeLists.txt
  -- Detecting CXX compile features - done
     Called from: [3]   /usr/share/cmake3/Modules/CMakeDetermineCompileFeatures.cmake
                  [2]   /usr/share/cmake3/Modules/CMakeTestCXXCompiler.cmake
                  [1]   /root/.cargo/registry/src/github.com-1ecc6299db9ec823/snmalloc-sys-0.2.27/snmalloc/CMakeLists.txt
  -- Performing Test CONST_QUALIFIED_MALLOC_USABLE_SIZE
     Called from: [2]   /usr/share/cmake3/Modules/CheckCSourceCompiles.cmake
                  [1]   /root/.cargo/registry/src/github.com-1ecc6299db9ec823/snmalloc-sys-0.2.27/snmalloc/CMakeLists.txt
  -- Performing Test CONST_QUALIFIED_MALLOC_USABLE_SIZE - Failed
     Called from: [2]   /usr/share/cmake3/Modules/CheckCSourceCompiles.cmake
                  [1]   /root/.cargo/registry/src/github.com-1ecc6299db9ec823/snmalloc-sys-0.2.27/snmalloc/CMakeLists.txt
  -- Looking for pthread.h
     Called from: [3]   /usr/share/cmake3/Modules/CheckIncludeFile.cmake
                  [2]   /usr/share/cmake3/Modules/FindThreads.cmake
                  [1]   /root/.cargo/registry/src/github.com-1ecc6299db9ec823/snmalloc-sys-0.2.27/snmalloc/CMakeLists.txt
  -- Looking for pthread.h - found
     Called from: [3]   /usr/share/cmake3/Modules/CheckIncludeFile.cmake
                  [2]   /usr/share/cmake3/Modules/FindThreads.cmake
                  [1]   /root/.cargo/registry/src/github.com-1ecc6299db9ec823/snmalloc-sys-0.2.27/snmalloc/CMakeLists.txt
  -- Performing Test CMAKE_HAVE_LIBC_PTHREAD
     Called from: [3]   /usr/share/cmake3/Modules/CheckCSourceCompiles.cmake
                  [2]   /usr/share/cmake3/Modules/FindThreads.cmake
                  [1]   /root/.cargo/registry/src/github.com-1ecc6299db9ec823/snmalloc-sys-0.2.27/snmalloc/CMakeLists.txt
  -- Performing Test CMAKE_HAVE_LIBC_PTHREAD - Failed
     Called from: [3]   /usr/share/cmake3/Modules/CheckCSourceCompiles.cmake
                  [2]   /usr/share/cmake3/Modules/FindThreads.cmake
                  [1]   /root/.cargo/registry/src/github.com-1ecc6299db9ec823/snmalloc-sys-0.2.27/snmalloc/CMakeLists.txt
  -- Looking for pthread_create in pthreads
     Called from: [4]   /usr/share/cmake3/Modules/CheckLibraryExists.cmake
                  [3]   /usr/share/cmake3/Modules/FindThreads.cmake
                  [2]   /usr/share/cmake3/Modules/FindThreads.cmake
                  [1]   /root/.cargo/registry/src/github.com-1ecc6299db9ec823/snmalloc-sys-0.2.27/snmalloc/CMakeLists.txt
  -- Looking for pthread_create in pthreads - not found
     Called from: [4]   /usr/share/cmake3/Modules/CheckLibraryExists.cmake
                  [3]   /usr/share/cmake3/Modules/FindThreads.cmake
                  [2]   /usr/share/cmake3/Modules/FindThreads.cmake
                  [1]   /root/.cargo/registry/src/github.com-1ecc6299db9ec823/snmalloc-sys-0.2.27/snmalloc/CMakeLists.txt
  -- Looking for pthread_create in pthread
     Called from: [4]   /usr/share/cmake3/Modules/CheckLibraryExists.cmake
                  [3]   /usr/share/cmake3/Modules/FindThreads.cmake
                  [2]   /usr/share/cmake3/Modules/FindThreads.cmake
                  [1]   /root/.cargo/registry/src/github.com-1ecc6299db9ec823/snmalloc-sys-0.2.27/snmalloc/CMakeLists.txt
  -- Looking for pthread_create in pthread - found
     Called from: [4]   /usr/share/cmake3/Modules/CheckLibraryExists.cmake
                  [3]   /usr/share/cmake3/Modules/FindThreads.cmake
                  [2]   /usr/share/cmake3/Modules/FindThreads.cmake
                  [1]   /root/.cargo/registry/src/github.com-1ecc6299db9ec823/snmalloc-sys-0.2.27/snmalloc/CMakeLists.txt
  -- Found Threads: TRUE
     Called from: [4]   /usr/share/cmake3/Modules/FindPackageMessage.cmake
                  [3]   /usr/share/cmake3/Modules/FindPackageHandleStandardArgs.cmake
                  [2]   /usr/share/cmake3/Modules/FindThreads.cmake
                  [1]   /root/.cargo/registry/src/github.com-1ecc6299db9ec823/snmalloc-sys-0.2.27/snmalloc/CMakeLists.txt
  -- Looking for backtrace
     Called from: [4]   /usr/share/cmake3/Modules/CheckSymbolExists.cmake
                  [3]   /usr/share/cmake3/Modules/CheckSymbolExists.cmake
                  [2]   /usr/share/cmake3/Modules/FindBacktrace.cmake
                  [1]   /root/.cargo/registry/src/github.com-1ecc6299db9ec823/snmalloc-sys-0.2.27/snmalloc/CMakeLists.txt
  -- Looking for backtrace - found
     Called from: [4]   /usr/share/cmake3/Modules/CheckSymbolExists.cmake
                  [3]   /usr/share/cmake3/Modules/CheckSymbolExists.cmake
                  [2]   /usr/share/cmake3/Modules/FindBacktrace.cmake
                  [1]   /root/.cargo/registry/src/github.com-1ecc6299db9ec823/snmalloc-sys-0.2.27/snmalloc/CMakeLists.txt
  -- backtrace facility detected in default set of libraries
     Called from: [2]   /usr/share/cmake3/Modules/FindBacktrace.cmake
                  [1]   /root/.cargo/registry/src/github.com-1ecc6299db9ec823/snmalloc-sys-0.2.27/snmalloc/CMakeLists.txt
  -- Found Backtrace: /usr/include
     Called from: [4]   /usr/share/cmake3/Modules/FindPackageMessage.cmake
                  [3]   /usr/share/cmake3/Modules/FindPackageHandleStandardArgs.cmake
                  [2]   /usr/share/cmake3/Modules/FindBacktrace.cmake
                  [1]   /root/.cargo/registry/src/github.com-1ecc6299db9ec823/snmalloc-sys-0.2.27/snmalloc/CMakeLists.txt
  -- Adding test: perf-contention-1
     Called from: [1]   /root/.cargo/registry/src/github.com-1ecc6299db9ec823/snmalloc-sys-0.2.27/snmalloc/CMakeLists.txt
  -- Single threaded test: perf-contention-1
     Called from: [1]   /root/.cargo/registry/src/github.com-1ecc6299db9ec823/snmalloc-sys-0.2.27/snmalloc/CMakeLists.txt
  -- Adding test: perf-contention-16
     Called from: [1]   /root/.cargo/registry/src/github.com-1ecc6299db9ec823/snmalloc-sys-0.2.27/snmalloc/CMakeLists.txt
  -- Single threaded test: perf-contention-16
     Called from: [1]   /root/.cargo/registry/src/github.com-1ecc6299db9ec823/snmalloc-sys-0.2.27/snmalloc/CMakeLists.txt
  -- Adding test: perf-contention-oe
     Called from: [1]   /root/.cargo/registry/src/github.com-1ecc6299db9ec823/snmalloc-sys-0.2.27/snmalloc/CMakeLists.txt
  -- Single threaded test: perf-contention-oe
     Called from: [1]   /root/.cargo/registry/src/github.com-1ecc6299db9ec823/snmalloc-sys-0.2.27/snmalloc/CMakeLists.txt
  -- Adding test: perf-contention-malloc
     Called from: [1]   /root/.cargo/registry/src/github.com-1ecc6299db9ec823/snmalloc-sys-0.2.27/snmalloc/CMakeLists.txt
  -- Single threaded test: perf-contention-malloc
     Called from: [1]   /root/.cargo/registry/src/github.com-1ecc6299db9ec823/snmalloc-sys-0.2.27/snmalloc/CMakeLists.txt
  -- Adding test: perf-contention-check
     Called from: [1]   /root/.cargo/registry/src/github.com-1ecc6299db9ec823/snmalloc-sys-0.2.27/snmalloc/CMakeLists.txt
  -- Single threaded test: perf-contention-check
     Called from: [1]   /root/.cargo/registry/src/github.com-1ecc6299db9ec823/snmalloc-sys-0.2.27/snmalloc/CMakeLists.txt
  -- Adding test: perf-external_pointer-1
     Called from: [1]   /root/.cargo/registry/src/github.com-1ecc6299db9ec823/snmalloc-sys-0.2.27/snmalloc/CMakeLists.txt
  -- Single threaded test: perf-external_pointer-1
     Called from: [1]   /root/.cargo/registry/src/github.com-1ecc6299db9ec823/snmalloc-sys-0.2.27/snmalloc/CMakeLists.txt
  -- Adding test: perf-external_pointer-16
     Called from: [1]   /root/.cargo/registry/src/github.com-1ecc6299db9ec823/snmalloc-sys-0.2.27/snmalloc/CMakeLists.txt
  -- Single threaded test: perf-external_pointer-16
     Called from: [1]   /root/.cargo/registry/src/github.com-1ecc6299db9ec823/snmalloc-sys-0.2.27/snmalloc/CMakeLists.txt
  -- Adding test: perf-external_pointer-oe
     Called from: [1]   /root/.cargo/registry/src/github.com-1ecc6299db9ec823/snmalloc-sys-0.2.27/snmalloc/CMakeLists.txt
  -- Single threaded test: perf-external_pointer-oe
     Called from: [1]   /root/.cargo/registry/src/github.com-1ecc6299db9ec823/snmalloc-sys-0.2.27/snmalloc/CMakeLists.txt
  -- Adding test: perf-external_pointer-malloc
     Called from: [1]   /root/.cargo/registry/src/github.com-1ecc6299db9ec823/snmalloc-sys-0.2.27/snmalloc/CMakeLists.txt
  -- Single threaded test: perf-external_pointer-malloc
     Called from: [1]   /root/.cargo/registry/src/github.com-1ecc6299db9ec823/snmalloc-sys-0.2.27/snmalloc/CMakeLists.txt
  -- Adding test: perf-external_pointer-check
     Called from: [1]   /root/.cargo/registry/src/github.com-1ecc6299db9ec823/snmalloc-sys-0.2.27/snmalloc/CMakeLists.txt
  -- Single threaded test: perf-external_pointer-check
     Called from: [1]   /root/.cargo/registry/src/github.com-1ecc6299db9ec823/snmalloc-sys-0.2.27/snmalloc/CMakeLists.txt
  -- Adding test: perf-low_memory-1
     Called from: [1]   /root/.cargo/registry/src/github.com-1ecc6299db9ec823/snmalloc-sys-0.2.27/snmalloc/CMakeLists.txt
  -- Single threaded test: perf-low_memory-1
     Called from: [1]   /root/.cargo/registry/src/github.com-1ecc6299db9ec823/snmalloc-sys-0.2.27/snmalloc/CMakeLists.txt
  -- Adding test: perf-low_memory-16
     Called from: [1]   /root/.cargo/registry/src/github.com-1ecc6299db9ec823/snmalloc-sys-0.2.27/snmalloc/CMakeLists.txt
  -- Single threaded test: perf-low_memory-16
     Called from: [1]   /root/.cargo/registry/src/github.com-1ecc6299db9ec823/snmalloc-sys-0.2.27/snmalloc/CMakeLists.txt
  -- Adding test: perf-low_memory-oe
     Called from: [1]   /root/.cargo/registry/src/github.com-1ecc6299db9ec823/snmalloc-sys-0.2.27/snmalloc/CMakeLists.txt
  -- Single threaded test: perf-low_memory-oe
     Called from: [1]   /root/.cargo/registry/src/github.com-1ecc6299db9ec823/snmalloc-sys-0.2.27/snmalloc/CMakeLists.txt
  -- Adding test: perf-low_memory-malloc
     Called from: [1]   /root/.cargo/registry/src/github.com-1ecc6299db9ec823/snmalloc-sys-0.2.27/snmalloc/CMakeLists.txt
  -- Single threaded test: perf-low_memory-malloc
     Called from: [1]   /root/.cargo/registry/src/github.com-1ecc6299db9ec823/snmalloc-sys-0.2.27/snmalloc/CMakeLists.txt
  -- Adding test: perf-low_memory-check
     Called from: [1]   /root/.cargo/registry/src/github.com-1ecc6299db9ec823/snmalloc-sys-0.2.27/snmalloc/CMakeLists.txt
  -- Single threaded test: perf-low_memory-check
     Called from: [1]   /root/.cargo/registry/src/github.com-1ecc6299db9ec823/snmalloc-sys-0.2.27/snmalloc/CMakeLists.txt
  -- Adding test: perf-singlethread-1
     Called from: [1]   /root/.cargo/registry/src/github.com-1ecc6299db9ec823/snmalloc-sys-0.2.27/snmalloc/CMakeLists.txt
  -- Single threaded test: perf-singlethread-1
     Called from: [1]   /root/.cargo/registry/src/github.com-1ecc6299db9ec823/snmalloc-sys-0.2.27/snmalloc/CMakeLists.txt
  -- Adding test: perf-singlethread-16
     Called from: [1]   /root/.cargo/registry/src/github.com-1ecc6299db9ec823/snmalloc-sys-0.2.27/snmalloc/CMakeLists.txt
  -- Single threaded test: perf-singlethread-16
     Called from: [1]   /root/.cargo/registry/src/github.com-1ecc6299db9ec823/snmalloc-sys-0.2.27/snmalloc/CMakeLists.txt
  -- Adding test: perf-singlethread-oe
     Called from: [1]   /root/.cargo/registry/src/github.com-1ecc6299db9ec823/snmalloc-sys-0.2.27/snmalloc/CMakeLists.txt
  -- Single threaded test: perf-singlethread-oe
     Called from: [1]   /root/.cargo/registry/src/github.com-1ecc6299db9ec823/snmalloc-sys-0.2.27/snmalloc/CMakeLists.txt
  -- Adding test: perf-singlethread-malloc
     Called from: [1]   /root/.cargo/registry/src/github.com-1ecc6299db9ec823/snmalloc-sys-0.2.27/snmalloc/CMakeLists.txt
  -- Single threaded test: perf-singlethread-malloc
     Called from: [1]   /root/.cargo/registry/src/github.com-1ecc6299db9ec823/snmalloc-sys-0.2.27/snmalloc/CMakeLists.txt
  -- Adding test: perf-singlethread-check
     Called from: [1]   /root/.cargo/registry/src/github.com-1ecc6299db9ec823/snmalloc-sys-0.2.27/snmalloc/CMakeLists.txt
  -- Single threaded test: perf-singlethread-check
     Called from: [1]   /root/.cargo/registry/src/github.com-1ecc6299db9ec823/snmalloc-sys-0.2.27/snmalloc/CMakeLists.txt
  -- Adding test: func-bits-1
     Called from: [1]   /root/.cargo/registry/src/github.com-1ecc6299db9ec823/snmalloc-sys-0.2.27/snmalloc/CMakeLists.txt
  -- Adding test: func-bits-16
     Called from: [1]   /root/.cargo/registry/src/github.com-1ecc6299db9ec823/snmalloc-sys-0.2.27/snmalloc/CMakeLists.txt
  -- Adding test: func-bits-oe
     Called from: [1]   /root/.cargo/registry/src/github.com-1ecc6299db9ec823/snmalloc-sys-0.2.27/snmalloc/CMakeLists.txt
  -- Adding test: func-bits-malloc
     Called from: [1]   /root/.cargo/registry/src/github.com-1ecc6299db9ec823/snmalloc-sys-0.2.27/snmalloc/CMakeLists.txt
  -- Adding test: func-bits-check
     Called from: [1]   /root/.cargo/registry/src/github.com-1ecc6299db9ec823/snmalloc-sys-0.2.27/snmalloc/CMakeLists.txt
  -- Adding test: func-external_pagemap-1
     Called from: [1]   /root/.cargo/registry/src/github.com-1ecc6299db9ec823/snmalloc-sys-0.2.27/snmalloc/CMakeLists.txt
  -- Adding test: func-external_pagemap-16
     Called from: [1]   /root/.cargo/registry/src/github.com-1ecc6299db9ec823/snmalloc-sys-0.2.27/snmalloc/CMakeLists.txt
  -- Adding test: func-external_pagemap-oe
     Called from: [1]   /root/.cargo/registry/src/github.com-1ecc6299db9ec823/snmalloc-sys-0.2.27/snmalloc/CMakeLists.txt
  -- Adding test: func-external_pagemap-malloc
     Called from: [1]   /root/.cargo/registry/src/github.com-1ecc6299db9ec823/snmalloc-sys-0.2.27/snmalloc/CMakeLists.txt
  -- Adding test: func-external_pagemap-check
     Called from: [1]   /root/.cargo/registry/src/github.com-1ecc6299db9ec823/snmalloc-sys-0.2.27/snmalloc/CMakeLists.txt
  -- Adding test: func-first_operation-1
     Called from: [1]   /root/.cargo/registry/src/github.com-1ecc6299db9ec823/snmalloc-sys-0.2.27/snmalloc/CMakeLists.txt
  -- Adding test: func-first_operation-16
     Called from: [1]   /root/.cargo/registry/src/github.com-1ecc6299db9ec823/snmalloc-sys-0.2.27/snmalloc/CMakeLists.txt
  -- Adding test: func-first_operation-oe
     Called from: [1]   /root/.cargo/registry/src/github.com-1ecc6299db9ec823/snmalloc-sys-0.2.27/snmalloc/CMakeLists.txt
  -- Adding test: func-first_operation-malloc
     Called from: [1]   /root/.cargo/registry/src/github.com-1ecc6299db9ec823/snmalloc-sys-0.2.27/snmalloc/CMakeLists.txt
  -- Adding test: func-first_operation-check
     Called from: [1]   /root/.cargo/registry/src/github.com-1ecc6299db9ec823/snmalloc-sys-0.2.27/snmalloc/CMakeLists.txt
  -- Adding test: func-fixed_region-1
     Called from: [1]   /root/.cargo/registry/src/github.com-1ecc6299db9ec823/snmalloc-sys-0.2.27/snmalloc/CMakeLists.txt
  -- Adding test: func-fixed_region-16
     Called from: [1]   /root/.cargo/registry/src/github.com-1ecc6299db9ec823/snmalloc-sys-0.2.27/snmalloc/CMakeLists.txt
  -- Adding test: func-fixed_region-oe
     Called from: [1]   /root/.cargo/registry/src/github.com-1ecc6299db9ec823/snmalloc-sys-0.2.27/snmalloc/CMakeLists.txt
  -- Adding test: func-fixed_region-malloc
     Called from: [1]   /root/.cargo/registry/src/github.com-1ecc6299db9ec823/snmalloc-sys-0.2.27/snmalloc/CMakeLists.txt
  -- Adding test: func-fixed_region-check
     Called from: [1]   /root/.cargo/registry/src/github.com-1ecc6299db9ec823/snmalloc-sys-0.2.27/snmalloc/CMakeLists.txt
  -- Adding test: func-malloc-1
     Called from: [1]   /root/.cargo/registry/src/github.com-1ecc6299db9ec823/snmalloc-sys-0.2.27/snmalloc/CMakeLists.txt
  -- Adding test: func-malloc-16
     Called from: [1]   /root/.cargo/registry/src/github.com-1ecc6299db9ec823/snmalloc-sys-0.2.27/snmalloc/CMakeLists.txt
  -- Adding test: func-malloc-oe
     Called from: [1]   /root/.cargo/registry/src/github.com-1ecc6299db9ec823/snmalloc-sys-0.2.27/snmalloc/CMakeLists.txt
  -- Adding test: func-malloc-malloc
     Called from: [1]   /root/.cargo/registry/src/github.com-1ecc6299db9ec823/snmalloc-sys-0.2.27/snmalloc/CMakeLists.txt
  -- Adding test: func-malloc-check
     Called from: [1]   /root/.cargo/registry/src/github.com-1ecc6299db9ec823/snmalloc-sys-0.2.27/snmalloc/CMakeLists.txt
  -- Adding test: func-memory-1
     Called from: [1]   /root/.cargo/registry/src/github.com-1ecc6299db9ec823/snmalloc-sys-0.2.27/snmalloc/CMakeLists.txt
  -- Adding test: func-memory-16
     Called from: [1]   /root/.cargo/registry/src/github.com-1ecc6299db9ec823/snmalloc-sys-0.2.27/snmalloc/CMakeLists.txt
  -- Adding test: func-memory-oe
     Called from: [1]   /root/.cargo/registry/src/github.com-1ecc6299db9ec823/snmalloc-sys-0.2.27/snmalloc/CMakeLists.txt
  -- Adding test: func-memory-malloc
     Called from: [1]   /root/.cargo/registry/src/github.com-1ecc6299db9ec823/snmalloc-sys-0.2.27/snmalloc/CMakeLists.txt
  -- Adding test: func-memory-check
     Called from: [1]   /root/.cargo/registry/src/github.com-1ecc6299db9ec823/snmalloc-sys-0.2.27/snmalloc/CMakeLists.txt
  -- Adding test: func-memory_usage-1
     Called from: [1]   /root/.cargo/registry/src/github.com-1ecc6299db9ec823/snmalloc-sys-0.2.27/snmalloc/CMakeLists.txt
  -- Adding test: func-memory_usage-16
     Called from: [1]   /root/.cargo/registry/src/github.com-1ecc6299db9ec823/snmalloc-sys-0.2.27/snmalloc/CMakeLists.txt
  -- Adding test: func-memory_usage-oe
     Called from: [1]   /root/.cargo/registry/src/github.com-1ecc6299db9ec823/snmalloc-sys-0.2.27/snmalloc/CMakeLists.txt
  -- Adding test: func-memory_usage-malloc
     Called from: [1]   /root/.cargo/registry/src/github.com-1ecc6299db9ec823/snmalloc-sys-0.2.27/snmalloc/CMakeLists.txt
  -- Adding test: func-memory_usage-check
     Called from: [1]   /root/.cargo/registry/src/github.com-1ecc6299db9ec823/snmalloc-sys-0.2.27/snmalloc/CMakeLists.txt
  -- Adding test: func-pagemap-1
     Called from: [1]   /root/.cargo/registry/src/github.com-1ecc6299db9ec823/snmalloc-sys-0.2.27/snmalloc/CMakeLists.txt
  -- Adding test: func-pagemap-16
     Called from: [1]   /root/.cargo/registry/src/github.com-1ecc6299db9ec823/snmalloc-sys-0.2.27/snmalloc/CMakeLists.txt
  -- Adding test: func-pagemap-oe
     Called from: [1]   /root/.cargo/registry/src/github.com-1ecc6299db9ec823/snmalloc-sys-0.2.27/snmalloc/CMakeLists.txt
  -- Adding test: func-pagemap-malloc
     Called from: [1]   /root/.cargo/registry/src/github.com-1ecc6299db9ec823/snmalloc-sys-0.2.27/snmalloc/CMakeLists.txt
  -- Adding test: func-pagemap-check
     Called from: [1]   /root/.cargo/registry/src/github.com-1ecc6299db9ec823/snmalloc-sys-0.2.27/snmalloc/CMakeLists.txt
  -- Adding test: func-release-rounding-1 only for release configs
     Called from: [1]   /root/.cargo/registry/src/github.com-1ecc6299db9ec823/snmalloc-sys-0.2.27/snmalloc/CMakeLists.txt
  -- Adding test: func-release-rounding-16 only for release configs
     Called from: [1]   /root/.cargo/registry/src/github.com-1ecc6299db9ec823/snmalloc-sys-0.2.27/snmalloc/CMakeLists.txt
  -- Adding test: func-release-rounding-oe only for release configs
     Called from: [1]   /root/.cargo/registry/src/github.com-1ecc6299db9ec823/snmalloc-sys-0.2.27/snmalloc/CMakeLists.txt
  -- Adding test: func-release-rounding-malloc only for release configs
     Called from: [1]   /root/.cargo/registry/src/github.com-1ecc6299db9ec823/snmalloc-sys-0.2.27/snmalloc/CMakeLists.txt
  -- Adding test: func-release-rounding-check only for release configs
     Called from: [1]   /root/.cargo/registry/src/github.com-1ecc6299db9ec823/snmalloc-sys-0.2.27/snmalloc/CMakeLists.txt
  -- Adding test: func-sandbox-1
     Called from: [1]   /root/.cargo/registry/src/github.com-1ecc6299db9ec823/snmalloc-sys-0.2.27/snmalloc/CMakeLists.txt
  -- Adding test: func-sandbox-16
     Called from: [1]   /root/.cargo/registry/src/github.com-1ecc6299db9ec823/snmalloc-sys-0.2.27/snmalloc/CMakeLists.txt
  -- Adding test: func-sandbox-oe
     Called from: [1]   /root/.cargo/registry/src/github.com-1ecc6299db9ec823/snmalloc-sys-0.2.27/snmalloc/CMakeLists.txt
  -- Adding test: func-sandbox-malloc
     Called from: [1]   /root/.cargo/registry/src/github.com-1ecc6299db9ec823/snmalloc-sys-0.2.27/snmalloc/CMakeLists.txt
  -- Adding test: func-sandbox-check
     Called from: [1]   /root/.cargo/registry/src/github.com-1ecc6299db9ec823/snmalloc-sys-0.2.27/snmalloc/CMakeLists.txt
  -- Adding test: func-sizeclass-1
     Called from: [1]   /root/.cargo/registry/src/github.com-1ecc6299db9ec823/snmalloc-sys-0.2.27/snmalloc/CMakeLists.txt
  -- Adding test: func-sizeclass-16
     Called from: [1]   /root/.cargo/registry/src/github.com-1ecc6299db9ec823/snmalloc-sys-0.2.27/snmalloc/CMakeLists.txt
  -- Adding test: func-sizeclass-oe
     Called from: [1]   /root/.cargo/registry/src/github.com-1ecc6299db9ec823/snmalloc-sys-0.2.27/snmalloc/CMakeLists.txt
  -- Adding test: func-sizeclass-malloc
     Called from: [1]   /root/.cargo/registry/src/github.com-1ecc6299db9ec823/snmalloc-sys-0.2.27/snmalloc/CMakeLists.txt
  -- Adding test: func-sizeclass-check
     Called from: [1]   /root/.cargo/registry/src/github.com-1ecc6299db9ec823/snmalloc-sys-0.2.27/snmalloc/CMakeLists.txt
  -- Adding test: func-statistics-1
     Called from: [1]   /root/.cargo/registry/src/github.com-1ecc6299db9ec823/snmalloc-sys-0.2.27/snmalloc/CMakeLists.txt
  -- Adding test: func-statistics-16
     Called from: [1]   /root/.cargo/registry/src/github.com-1ecc6299db9ec823/snmalloc-sys-0.2.27/snmalloc/CMakeLists.txt
  -- Adding test: func-statistics-oe
     Called from: [1]   /root/.cargo/registry/src/github.com-1ecc6299db9ec823/snmalloc-sys-0.2.27/snmalloc/CMakeLists.txt
  -- Adding test: func-statistics-malloc
     Called from: [1]   /root/.cargo/registry/src/github.com-1ecc6299db9ec823/snmalloc-sys-0.2.27/snmalloc/CMakeLists.txt
  -- Adding test: func-statistics-check
     Called from: [1]   /root/.cargo/registry/src/github.com-1ecc6299db9ec823/snmalloc-sys-0.2.27/snmalloc/CMakeLists.txt
  -- Adding test: func-thread_alloc_external-1
     Called from: [1]   /root/.cargo/registry/src/github.com-1ecc6299db9ec823/snmalloc-sys-0.2.27/snmalloc/CMakeLists.txt
  -- Adding test: func-thread_alloc_external-16
     Called from: [1]   /root/.cargo/registry/src/github.com-1ecc6299db9ec823/snmalloc-sys-0.2.27/snmalloc/CMakeLists.txt
  -- Adding test: func-thread_alloc_external-oe
     Called from: [1]   /root/.cargo/registry/src/github.com-1ecc6299db9ec823/snmalloc-sys-0.2.27/snmalloc/CMakeLists.txt
  -- Adding test: func-thread_alloc_external-malloc
     Called from: [1]   /root/.cargo/registry/src/github.com-1ecc6299db9ec823/snmalloc-sys-0.2.27/snmalloc/CMakeLists.txt
  -- Adding test: func-thread_alloc_external-check
     Called from: [1]   /root/.cargo/registry/src/github.com-1ecc6299db9ec823/snmalloc-sys-0.2.27/snmalloc/CMakeLists.txt
  -- Adding test: func-two_alloc_types-1
     Called from: [1]   /root/.cargo/registry/src/github.com-1ecc6299db9ec823/snmalloc-sys-0.2.27/snmalloc/CMakeLists.txt
  -- Adding test: func-two_alloc_types-16
     Called from: [1]   /root/.cargo/registry/src/github.com-1ecc6299db9ec823/snmalloc-sys-0.2.27/snmalloc/CMakeLists.txt
  -- Adding test: func-two_alloc_types-oe
     Called from: [1]   /root/.cargo/registry/src/github.com-1ecc6299db9ec823/snmalloc-sys-0.2.27/snmalloc/CMakeLists.txt
  -- Adding test: func-two_alloc_types-malloc
     Called from: [1]   /root/.cargo/registry/src/github.com-1ecc6299db9ec823/snmalloc-sys-0.2.27/snmalloc/CMakeLists.txt
  -- Adding test: func-two_alloc_types-check
     Called from: [1]   /root/.cargo/registry/src/github.com-1ecc6299db9ec823/snmalloc-sys-0.2.27/snmalloc/CMakeLists.txt
  -- Configuring done
  -- Generating /snmalloc_test/target/debug/build/snmalloc-sys-01fa996f117ac3c2/out/build
     Called from: [1]   /root/.cargo/registry/src/github.com-1ecc6299db9ec823/snmalloc-sys-0.2.27/snmalloc/CMakeLists.txt
  -- Generating done
  -- Build files have been written to: /snmalloc_test/target/debug/build/snmalloc-sys-01fa996f117ac3c2/out/build
  running: "cmake" "--build" "." "--target" "snmallocshim-1mib-rust" "--config" "Release" "--"
  /usr/bin/cmake3 -S/root/.cargo/registry/src/github.com-1ecc6299db9ec823/snmalloc-sys-0.2.27/snmalloc -B/snmalloc_test/target/debug/build/snmalloc-sys-01fa996f117ac3c2/out/build --check-build-system CMakeFiles/Makefile.cmake 0
  /usr/bin/gmake  -f CMakeFiles/Makefile2 snmallocshim-1mib-rust
  gmake[1]: Entering directory `/snmalloc_test/target/debug/build/snmalloc-sys-01fa996f117ac3c2/out/build'
  /usr/bin/cmake3 -S/root/.cargo/registry/src/github.com-1ecc6299db9ec823/snmalloc-sys-0.2.27/snmalloc -B/snmalloc_test/target/debug/build/snmalloc-sys-01fa996f117ac3c2/out/build --check-build-system CMakeFiles/Makefile.cmake 0
  /usr/bin/cmake3 -E cmake_progress_start /snmalloc_test/target/debug/build/snmalloc-sys-01fa996f117ac3c2/out/build/CMakeFiles 1
  /usr/bin/gmake  -f CMakeFiles/Makefile2 CMakeFiles/snmallocshim-1mib-rust.dir/all
  gmake[2]: Entering directory `/snmalloc_test/target/debug/build/snmalloc-sys-01fa996f117ac3c2/out/build'
  /usr/bin/gmake  -f CMakeFiles/snmallocshim-1mib-rust.dir/build.make CMakeFiles/snmallocshim-1mib-rust.dir/depend
  gmake[3]: Entering directory `/snmalloc_test/target/debug/build/snmalloc-sys-01fa996f117ac3c2/out/build'
  cd /snmalloc_test/target/debug/build/snmalloc-sys-01fa996f117ac3c2/out/build && /usr/bin/cmake3 -E cmake_depends "Unix Makefiles" /root/.cargo/registry/src/github.com-1ecc6299db9ec823/snmalloc-sys-0.2.27/snmalloc /root/.cargo/registry/src/github.com-1ecc6299db9ec823/snmalloc-sys-0.2.27/snmalloc /snmalloc_test/target/debug/build/snmalloc-sys-01fa996f117ac3c2/out/build /snmalloc_test/target/debug/build/snmalloc-sys-01fa996f117ac3c2/out/build /snmalloc_test/target/debug/build/snmalloc-sys-01fa996f117ac3c2/out/build/CMakeFiles/snmallocshim-1mib-rust.dir/DependInfo.cmake --color=
  Dependee "/snmalloc_test/target/debug/build/snmalloc-sys-01fa996f117ac3c2/out/build/CMakeFiles/snmallocshim-1mib-rust.dir/DependInfo.cmake" is newer than depender "/snmalloc_test/target/debug/build/snmalloc-sys-01fa996f117ac3c2/out/build/CMakeFiles/snmallocshim-1mib-rust.dir/depend.internal".
  Dependee "/snmalloc_test/target/debug/build/snmalloc-sys-01fa996f117ac3c2/out/build/CMakeFiles/CMakeDirectoryInformation.cmake" is newer than depender "/snmalloc_test/target/debug/build/snmalloc-sys-01fa996f117ac3c2/out/build/CMakeFiles/snmallocshim-1mib-rust.dir/depend.internal".
  Scanning dependencies of target snmallocshim-1mib-rust
  gmake[3]: Leaving directory `/snmalloc_test/target/debug/build/snmalloc-sys-01fa996f117ac3c2/out/build'
  /usr/bin/gmake  -f CMakeFiles/snmallocshim-1mib-rust.dir/build.make CMakeFiles/snmallocshim-1mib-rust.dir/build
  gmake[3]: Entering directory `/snmalloc_test/target/debug/build/snmalloc-sys-01fa996f117ac3c2/out/build'
  [100%] Building CXX object CMakeFiles/snmallocshim-1mib-rust.dir/src/override/rust.cc.o
  /opt/rh/devtoolset-9/root/usr/bin/c++  -DBACKTRACE_HEADER=\"execinfo.h\" -DSNMALLOC_EXPORT="__attribute__((visibility(\"default\")))" -I/root/.cargo/registry/src/github.com-1ecc6299db9ec823/snmalloc-sys-0.2.27/snmalloc/src  -ffunction-sections -fdata-sections -fPIC -m64 -O2 -DNDEBUG -fvisibility=hidden   -Wall -Wextra -Werror -Wundef -fno-exceptions -fno-rtti -g -fomit-frame-pointer -ftls-model=initial-exec -mcx16 -std=gnu++17 -o CMakeFiles/snmallocshim-1mib-rust.dir/src/override/rust.cc.o -c /root/.cargo/registry/src/github.com-1ecc6299db9ec823/snmalloc-sys-0.2.27/snmalloc/src/override/rust.cc
  gmake[3]: Leaving directory `/snmalloc_test/target/debug/build/snmalloc-sys-01fa996f117ac3c2/out/build'
  gmake[2]: Leaving directory `/snmalloc_test/target/debug/build/snmalloc-sys-01fa996f117ac3c2/out/build'
  gmake[1]: Leaving directory `/snmalloc_test/target/debug/build/snmalloc-sys-01fa996f117ac3c2/out/build'

  --- stderr
  CMake Warning at CMakeLists.txt:79 (message):
    Not generating clangformat target, no clang-format tool found
  Call Stack (most recent call first):
    CMakeLists.txt:366 (clangformat_targets)

     Called from: [2]   /root/.cargo/registry/src/github.com-1ecc6299db9ec823/snmalloc-sys-0.2.27/snmalloc/CMakeLists.txt
                  [1]   /root/.cargo/registry/src/github.com-1ecc6299db9ec823/snmalloc-sys-0.2.27/snmalloc/CMakeLists.txt
  CMake Warning:
    Manually-specified variables were not used by the project:

      CMAKE_ASM_COMPILER
      CMAKE_ASM_FLAGS

  In file included from /root/.cargo/registry/src/github.com-1ecc6299db9ec823/snmalloc-sys-0.2.27/snmalloc/src/override/../mem/../mem/../pal/pal_linux.h:5,
                   from /root/.cargo/registry/src/github.com-1ecc6299db9ec823/snmalloc-sys-0.2.27/snmalloc/src/override/../mem/../mem/../pal/pal.h:17,
                   from /root/.cargo/registry/src/github.com-1ecc6299db9ec823/snmalloc-sys-0.2.27/snmalloc/src/override/../mem/../mem/sizeclass.h:3,
                   from /root/.cargo/registry/src/github.com-1ecc6299db9ec823/snmalloc-sys-0.2.27/snmalloc/src/override/../mem/allocstats.h:4,
                   from /root/.cargo/registry/src/github.com-1ecc6299db9ec823/snmalloc-sys-0.2.27/snmalloc/src/override/../mem/alloc.h:10,
                   from /root/.cargo/registry/src/github.com-1ecc6299db9ec823/snmalloc-sys-0.2.27/snmalloc/src/override/../mem/globalalloc.h:4,
                   from /root/.cargo/registry/src/github.com-1ecc6299db9ec823/snmalloc-sys-0.2.27/snmalloc/src/override/../mem/slowalloc.h:3,
                   from /root/.cargo/registry/src/github.com-1ecc6299db9ec823/snmalloc-sys-0.2.27/snmalloc/src/override/malloc.cc:1,
                   from /root/.cargo/registry/src/github.com-1ecc6299db9ec823/snmalloc-sys-0.2.27/snmalloc/src/override/rust.cc:2:
  /root/.cargo/registry/src/github.com-1ecc6299db9ec823/snmalloc-sys-0.2.27/snmalloc/src/override/../mem/../mem/../pal/pal_posix.h: In static member function 'static uint64_t snmalloc::PALPOSIX<OS>::get_entropy64()':
  /root/.cargo/registry/src/github.com-1ecc6299db9ec823/snmalloc-sys-0.2.27/snmalloc/src/override/../mem/../mem/../pal/pal_posix.h:294:13: error: there are no arguments to 'getentropy' that depend on a template parameter, so a declaration of 'getentropy' must be available [-fpermissive]
    294 |         if (getentropy(&result, sizeof(result)) != 0)
        |             ^~~~~~~~~~
  /root/.cargo/registry/src/github.com-1ecc6299db9ec823/snmalloc-sys-0.2.27/snmalloc/src/override/../mem/../mem/../pal/pal_posix.h:294:13: note: (if you use '-fpermissive', G++ will accept your code, but allowing the use of an undeclared name is deprecated)
  /root/.cargo/registry/src/github.com-1ecc6299db9ec823/snmalloc-sys-0.2.27/snmalloc/src/override/../mem/../mem/../pal/pal_posix.h: In instantiation of 'static uint64_t snmalloc::PALPOSIX<OS>::get_entropy64() [with OS = snmalloc::PALLinux; uint64_t = long unsigned int]':
  /root/.cargo/registry/src/github.com-1ecc6299db9ec823/snmalloc-sys-0.2.27/snmalloc/src/override/../mem/entropy.h:13:30:   required from 'std::enable_if_t<pal_supports<snmalloc::Entropy, PAL>, long unsigned int> snmalloc::get_entropy64() [with PAL = snmalloc::PALLinux; std::enable_if_t<pal_supports<snmalloc::Entropy, PAL>, long unsigned int> = long unsigned int]'
  /root/.cargo/registry/src/github.com-1ecc6299db9ec823/snmalloc-sys-0.2.27/snmalloc/src/override/../mem/entropy.h:37:37:   required from 'void snmalloc::LocalEntropy::init() [with PAL = snmalloc::PALLinux]'
  /root/.cargo/registry/src/github.com-1ecc6299db9ec823/snmalloc-sys-0.2.27/snmalloc/src/override/../mem/alloc.h:722:7:   required from 'snmalloc::Allocator<NeedsInitialisation, InitThreadAllocator, MemoryProvider, ChunkMap, IsQueueInline>::Allocator(MemoryProvider&, ChunkMap&&, snmalloc::RemoteAllocator*, bool) [with bool (* NeedsInitialisation)(void*) = snmalloc::needs_initialisation; void* (* InitThreadAllocator)(snmalloc::function_ref<void*(void*)>) = snmalloc::init_thread_allocator; MemoryProvider = snmalloc::MemoryProviderStateMixin<snmalloc::PALLinux, snmalloc::DefaultArenaMapTemplate<snmalloc::PALLinux, snmalloc::GlobalPagemapTemplate<snmalloc::default_auth_pagemap, snmalloc::ForAuthmap> > >; ChunkMap = snmalloc::DefaultChunkMap<>; bool IsQueueInline = true]'
  /root/.cargo/registry/src/github.com-1ecc6299db9ec823/snmalloc-sys-0.2.27/snmalloc/src/override/../mem/largealloc.h:278:14:   required from 'T* snmalloc::MemoryProviderStateMixin<PAL, ArenaMap>::alloc_chunk(Args&& ...) [with T = snmalloc::Allocator<snmalloc::needs_initialisation, snmalloc::init_thread_allocator, snmalloc::MemoryProviderStateMixin<snmalloc::PALLinux, snmalloc::DefaultArenaMapTemplate<snmalloc::PALLinux, snmalloc::GlobalPagemapTemplate<snmalloc::default_auth_pagemap, snmalloc::ForAuthmap> > >, snmalloc::DefaultChunkMap<>, true>; long unsigned int alignment = 4096; Args = {snmalloc::MemoryProviderStateMixin<snmalloc::PALLinux, snmalloc::DefaultArenaMapTemplate<snmalloc::PALLinux, snmalloc::GlobalPagemapTemplate<snmalloc::default_auth_pagemap, snmalloc::ForAuthmap> > >&}; PAL = snmalloc::PALLinux; ArenaMap = snmalloc::DefaultArenaMapTemplate<snmalloc::PALLinux, snmalloc::GlobalPagemapTemplate<snmalloc::default_auth_pagemap, snmalloc::ForAuthmap> >]'
  /root/.cargo/registry/src/github.com-1ecc6299db9ec823/snmalloc-sys-0.2.27/snmalloc/src/override/../mem/pool.h:60:9:   required from 'T* snmalloc::Pool<T, MemoryProvider>::acquire(Args&& ...) [with Args = {snmalloc::MemoryProviderStateMixin<snmalloc::PALLinux, snmalloc::DefaultArenaMapTemplate<snmalloc::PALLinux, snmalloc::GlobalPagemapTemplate<snmalloc::default_auth_pagemap, snmalloc::ForAuthmap> > >&}; T = snmalloc::Allocator<snmalloc::needs_initialisation, snmalloc::init_thread_allocator, snmalloc::MemoryProviderStateMixin<snmalloc::PALLinux, snmalloc::DefaultArenaMapTemplate<snmalloc::PALLinux, snmalloc::GlobalPagemapTemplate<snmalloc::default_auth_pagemap, snmalloc::ForAuthmap> > >, snmalloc::DefaultChunkMap<>, true>; MemoryProvider = snmalloc::MemoryProviderStateMixin<snmalloc::PALLinux, snmalloc::DefaultArenaMapTemplate<snmalloc::PALLinux, snmalloc::GlobalPagemapTemplate<snmalloc::default_auth_pagemap, snmalloc::ForAuthmap> > >]'
  /root/.cargo/registry/src/github.com-1ecc6299db9ec823/snmalloc-sys-0.2.27/snmalloc/src/override/../mem/globalalloc.h:34:29:   required from 'Alloc* snmalloc::AllocPool<MemoryProvider, Alloc>::acquire() [with MemoryProvider = snmalloc::MemoryProviderStateMixin<snmalloc::PALLinux, snmalloc::DefaultArenaMapTemplate<snmalloc::PALLinux, snmalloc::GlobalPagemapTemplate<snmalloc::default_auth_pagemap, snmalloc::ForAuthmap> > >; Alloc = snmalloc::Allocator<snmalloc::needs_initialisation, snmalloc::init_thread_allocator, snmalloc::MemoryProviderStateMixin<snmalloc::PALLinux, snmalloc::DefaultArenaMapTemplate<snmalloc::PALLinux, snmalloc::GlobalPagemapTemplate<snmalloc::default_auth_pagemap, snmalloc::ForAuthmap> > >, snmalloc::DefaultChunkMap<>, true>]'
  /root/.cargo/registry/src/github.com-1ecc6299db9ec823/snmalloc-sys-0.2.27/snmalloc/src/override/../mem/slowalloc.h:25:59:   required from here
  /root/.cargo/registry/src/github.com-1ecc6299db9ec823/snmalloc-sys-0.2.27/snmalloc/src/override/../mem/../mem/../pal/pal_posix.h:294:23: error: 'getentropy' was not declared in this scope; did you mean 'get_entropy64'?
    294 |         if (getentropy(&result, sizeof(result)) != 0)
        |             ~~~~~~~~~~^~~~~~~~~~~~~~~~~~~~~~~~~
        |             get_entropy64
  gmake[3]: *** [CMakeFiles/snmallocshim-1mib-rust.dir/src/override/rust.cc.o] Error 1
  gmake[2]: *** [CMakeFiles/snmallocshim-1mib-rust.dir/all] Error 2
  gmake[1]: *** [CMakeFiles/snmallocshim-1mib-rust.dir/rule] Error 2
  gmake: *** [snmallocshim-1mib-rust] Error 2
  thread 'main' panicked at '
  command did not execute successfully, got: exit code: 2

  build script failed, must exit now', /root/.cargo/registry/src/github.com-1ecc6299db9ec823/cmake-0.1.45/src/lib.rs:894:5

So we could add some detection for this in the CMake logic. We could check if a call to getentropy compiles, and if not fall back.  There is one example of checking for compilation here:
https://github.com/microsoft/snmalloc/blob/e77a5d9c588171a3bcafce3f27b526bb06138e24/CMakeLists.txt#L23-L35
The check could then be integrated into the Pal for POSIXs systems.  This might simplify other systems @devnexen has been fixing when I break them.
I am deep into something else at the moment, but will happily take a PR for this.  Otherwise, it will be a few weeks before I can get round to it.

https://github.com/microsoft/snmalloc/pull/307#discussion_r602920747

I can happily take a stab at a PR.
How would a fallback look like? Should it use the getrandom syscall?

I have been falling back to the std::random_device, so if you don't set the Entropy flag if we don't detect getentropy call working in CMake.
https://github.com/microsoft/snmalloc/blob/e77a5d9c588171a3bcafce3f27b526bb06138e24/src/pal/pal_posix.h#L122
If you disable the Pal providing entropy, then the rest of the code will do the fallback for you.
You might need to define a fake getentropy prototype to appease the constexpr compiler gods.
https://github.com/microsoft/snmalloc/blob/e77a5d9c588171a3bcafce3f27b526bb06138e24/src/pal/pal_netbsd.h#L6-L14
And there is probably some simplification across the various POSIX pals, if we have the getentropy call as an ifdef.

Closed by #329


[Fixes #332 & #333]Fixed the bug in create host page. Added hostname validation and some css fixes.

What type of PR is this?
/kind bug fix
What this PR does / why we need it:
This PR is required to fix issues raised in the Create Host page.
Which issue(s) this PR fixes:
Fixes #332 #333
Test Report Added?:
/kind TESTED
Test Report:
Availability Zone dropdown

Hostname Validation

Special notes for your reviewer:

@kumarashit @NajmudheenCT Please review and merge.

Please raise PR on Master branch

Also, if the master is behind development, please raise PR to port the changes

Please sync to master

@kumarashit  Closing since new PR is raised to master #336


Can't run on android emulator

It works fine when running on ios, but when trying to build the app on android emulator Im getting this errror
couldn't find DSO to load: libhermes.so
SoSource 0:
com.facebook.soloader. DirectorySoSource|root = /data/app/~~2skIF1vR2hLrjwckKm_HAQ==/ com. tasecombo.unite-CUOuiWiEraGVkcsvJD7q
MA==/lib/arm64 flags = 0]
SoSource 1:
com.facebook.soloader. DirectApkSoSourcelroot = (/data/app/~~2skIIvR2hLrjwckKm_HAQ==/ com.tasecombo.unite-CUOuiWiEraGVkcsJD7g MA==/base.apk!/lib/arm64-v8a,)]

I had to change these lines in build.gradle
enableHermes: true,
def enableHermes = project.ext.react.get("enableHermes", true);

It is likely a side effect, as you can see here, enableHermes has been replaced by hermesEnabled in recent versions
Please share more details about your environment and the commands you use. Here is what should be used
git clone git@github.com:teslamotors/react-native-camera-kit.git
cd react-native-camera-kit
yarn bootstrap
yarn example android


steroids.layers.popAll() only works if the tab containing the target layer stack is visible

Reproduce:

Have an app with two tabs.
Navigate a few layers deep in tab A.
Switch to tab B.
Send a window.postMessage from tab B to a WebView in the tab A layer stack, instructing it to call steroids.layers.popAll().
The call fails since tab A is not on screen.

To circumvent this, starting with iOS Scanner v3.1.3, you can use steroids.layers.replace() to replace the current layer stack with the root view, e.g.
var rootView = steroids.views.WebView(
  {
    location: "index.html",
    id: "index.html" // this matches the value of config.steroids.location or the location field of a tab object
  }
);
steroids.layers.replace(rootView);

Note that the target preloaded WebView has to be in the layer stack that is being replaced.

:+1:


Custom icons are not persistent

Reported by flasheater on 12 Dec 2014 23:48 UTC
Possibly related to #32.

Set custom Icon using the Google Photos app
Switch to another app and switch back
Icon is now back to default.

Android Cyanogenmod 11
Nexus 5

Comment by jfreak on 22 Jun 2015 09:19 UTC
I think it might be persisted. But when trying to open it something happens.
I see this in my logcat:
W/ActivityManager(  745): Permission Denial: opening provider com.google.android.apps.photos.contentprovider.MediaContentProvider from ProcessRecord{1339b35b 15646:org.fedorahosted.freeotp/u0a82} (pid=15646, uid=10082) that is not exported from uid 10065
Maybe something happens with the URL. The icons I selected a few versions back show up nicely.
Nexus 5. Stock 5.1.1

Comment by jfreak on 18 Aug 2015 18:30 UTC
I tried to debug this a bit further.
It seems the URIs look similar to this content://com.google.android.apps.photos.contentprovider/0/1/content%3A%2F%2Fmedia%2Fexternal%2Fimages%2Fmedia%2F75209/ACTUAL when selected from the Google Photos app.
From what I understand this URI is only valid from the process that initially got it. That means that as soon as you leave the app again it will get a new UID and therefore the URI is no longer valid.
A possible workaround is discussed here: http://stackoverflow.com/questions/30527045/choosing-photo-using-new-google-photos-app-is-broken.
As I see it there are three possible solutions.
One is to cache a copy of the image locally before the Token is persisted and persist it with a URI to the local cache.
The other is to get the URI through some other app that returns the URI from the file system.
The third option is to get the URI for the file system by decoding the URI from Google Photos.
The first solution is probably the cleanest. Then FreeOTP will not be dependent on files on the filesystem anymore. The files can be deleted but the icon is still available for FreeOTP from its local copy.

Comment by jfreak on 16 Oct 2015 06:59 UTC
Until the patch gets accepted I found another workaround: http://blog.vester.org/2015/10/freeotp-icon-fix.html
Basically you have to extract the tokens from a backup and edit the references to the images and then restore a backup with the changes.

Comment by mattdm on 10 Dec 2015 12:33 UTC
On the almost anniversary of this issue... any chance of a new release with this fix? I use FreeOTP for a number of different systems, and this would be really nice to have.

Comment by bjabram on 27 Jan 2016 12:22 UTC
According to the Google Play store this was fixed in v1.5 (17) but I am still experiencing this problem. I can choose the icon but when I reopen the app the icons are missing. Nexus 5, Android 6.0.1

Comment by jonfen on 15 Feb 2016 10:23 UTC
Yes, still an issue on Nexus 5, Android 6.0.1

Comment by jfenal on 5 Apr 2016 08:04 UTC
Still an issue on a Samsung GS6, Lollipop, using images local to the phone.

Comment by whereisaaron on 25 May 2016 16:47 UTC
Still an issue with v1.5 (17) on Samsung S6 with Android 6.0.1. This problem didn't occur with the same version on Android 5.1 on Samsung S6. Appears to be a Marshmallow incompatibility.
Old icons selected before upgrading to Android 6 are still there and persistent. But new icons you add or edit under Android 6 do not get persisted past a restart.
The icon doesn't disappear until the app is restarted. Switching back and forth to the app while it is still runnning and in memory the icon is still there.

Comment by corppneq on 10 Jun 2016 23:47 UTC
+1
(Android 6.0.1 - Build MTC19T - Nexus 5X)

Comment by mattdm on 15 Sep 2016 14:42 UTC
Still want :)

+1

+1

Can someone comment on when this fix will hit the Play Store? The last update appears to be from 2016. Barring that, does FDroid have a newer version? (A cursory check did not indicate that was the case.)

+1

Is this fixed?  I just installed FreeOTP Version 1.5 (17) and it seems to have this exact problem.  Thanks!

Still an issue in Version 17 (1.5), Android Pie

The issue seems to be related to Google Fotos. Install Another Image Gallery app (e.g. Simple Gallery) and use it to select the picture. It works fine, while Google Fotos suffers the issues mentioned above

Right on point, icons stopped resetting after selecting them with a different gallery app. Thank you.


Io disconnected and can not recover from it

Here is the log:
23:48:56 VERB EventStreamManager grpcEmit(EVENT_TYPE_HEARTBEAT[1], {"data":"[object Object]"})
23:49:16 VERB EventStreamManager grpcEmit(EVENT_TYPE_HEARTBEAT[1], {"data":"[object Object]"})
23:49:28 WARN Io initWebSocket() close event[1006: ]
23:49:28 VERB Io reconnect()
23:49:28 WARN Io reconnect() will reconnect after 0 s
23:49:28 VERB Io initWebSocket()
23:49:36 VERB Io send() without a connected websocket, eventBuffer.length = 1
23:49:36 VERB EventStreamManager grpcEmit(EVENT_TYPE_HEARTBEAT[1], {"data":"[object Object]"})
23:49:56 VERB Io send() without a connected websocket, eventBuffer.length = 2
23:49:56 VERB EventStreamManager grpcEmit(EVENT_TYPE_HEARTBEAT[1], {"data":"[object Object]"})
23:50:16 VERB Io send() without a connected websocket, eventBuffer.length = 3
23:50:16 VERB EventStreamManager grpcEmit(EVENT_TYPE_HEARTBEAT[1], {"data":"[object Object]"})
23:50:36 VERB Io send() without a connected websocket, eventBuffer.length = 4
23:50:36 VERB EventStreamManager grpcEmit(EVENT_TYPE_HEARTBEAT[1], {"data":"[object Object]"})

Seems like when the Io get disconnected, the connection won't be recovered, and the eventBuffer keep growing.

Thanks for reporting this issue.
This is known and our oss chat bot is experiencing this problem everyday.
Will investigate it in the following weeks.

Thanks for reply such fast.
I've looked into the code and found that after the initWebSocket() function call, there is no open event triggered, seems pretty weird, maybe this is where we can start the investigation.

Hi @huan how's this issue going?

I have not got time to look into it yet.
If we can have a minimum reproducible code, then I believe it will be very easy to be fixed.


Initial Ambari theme support

This is very minimal theme support for Ambari 2.1+ and will be expanded with additional options in future pull requests, as needed.

One minor comment, otherwise LGTM...


Testing many images at once

In this PR, we are bringing the possibility to test several images at once and the results are downloaded into a csv file.

This PR is done over #53, so 53 has to be merged before this one.

The CSV download didn't work on my machine. I pushed a fix. @MarcelTorne can you check that it works correctly on your side as well?

The CSV download didn't work on my machine. I pushed a fix. @MarcelTorne can you check that it works correctly on your side as well?

This is working on my side too! Thank you very much for the fix Martin!


Update build system for AVIF

Switch to Makefile build
Remove package.json and napa
Rebuilds are not flakey anymore (after what I said on chat)
Updated to libavif 0.8 and libaom 2.0
Ran clang-format

Remove package.json

Hmm do we want this? I've kept it in other places, assuming that we want to be able to do npm run build in arbitrary folder instead of fiddling with Docker options in the command-line.

I mean, the package.json doesn’t do much more than calling ../build-cpp.sh. But yeah, might be nice to use it as “documentation”. I’ll re-add it.

I’ll merge this tomorrow if there are no other remarks (and CI passes)

The open conversation with ENABLE_EXAMPLES remark still stands. It doesn't cost anything to disable it, and seems relevant to the "build system" PR.

Yeah, I saw that comment via email, because GH’s UI is horrible. Testing that flag now…

The flag worked! Nice find!

Glad to hear!
Overall, I think I'd remove few more intermediate variables, but if you find it cleaner that way, I don't have any strong opinion and this should be good to go :)
I've moved non-build-system related comments to the original PR.


Add an action to Completed Build Menu

I need to insert a menu here. ms.vss-build-web.completed-build-menu does not give desired results. Is there a way to insert a menu here ? My requirement is to allow users download a report on every build completion. Had been unable to find an entry point for same.

This repo is for tasks (/tasks) in this repo.  You can create an issue on developer community for service.