add cyberchef

Execution result of "run-all plan" in "infrastructure/cloud"
time=2024-04-01T15:24:23Z level=info msg=The stack at /github/workspace/infrastructure/cloud will be processed in the following order for command plan:
Group 1
- Module /github/workspace/infrastructure/cloud/aws/jung2bot-dev/dynamodb
- Module /github/workspace/infrastructure/cloud/aws/jung2bot-dev/sqs
- Module /github/workspace/infrastructure/cloud/aws/jung2bot/dynamodb
- Module /github/workspace/infrastructure/cloud/aws/jung2bot/sqs
- Module /github/workspace/infrastructure/cloud/b2/bucket
- Module /github/workspace/infrastructure/cloud/cloudflare/access
- Module /github/workspace/infrastructure/cloud/cloudflare/tunnel
- Module /github/workspace/infrastructure/cloud/uptime-robot/otaru

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

Initializing the backend...

Initializing the backend...

Initializing the backend...

Initializing the backend...

Initializing the backend...

Initializing the backend...

Initializing the backend...

Initializing the backend...

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

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

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

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

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

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

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

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

Initializing provider plugins...
- Reusing previous version of integrations/github from the dependency lock file
Initializing modules...
Downloading registry.terraform.io/terraform-aws-modules/sqs/aws 4.1.1 for sqs...
Downloading registry.terraform.io/terraform-aws-modules/sqs/aws 4.1.1 for sqs...

Initializing provider plugins...
- Finding vexxhost/uptimerobot versions matching "~> 0.8"...
- Reusing previous version of vexxhost/uptimerobot from the dependency lock file
Downloading registry.terraform.io/terraform-aws-modules/dynamodb-table/aws 4.0.1 for dynamodb_table...
Initializing modules...
Downloading registry.terraform.io/terraform-aws-modules/dynamodb-table/aws 4.0.1 for dynamodb_table...
- Reusing previous version of hashicorp/aws from the dependency lock file
- Reusing previous version of hashicorp/aws from the dependency lock file
- Reusing previous version of backblaze/b2 from the dependency lock file
- Reusing previous version of backblaze/b2 from the dependency lock file
- Reusing previous version of cloudflare/cloudflare from the dependency lock file
- Reusing previous version of cloudflare/cloudflare from the dependency lock file
- Reusing previous version of integrations/github from the dependency lock file

Initializing provider plugins...
- Reusing previous version of cloudflare/cloudflare from the dependency lock file

Initializing provider plugins...
- Reusing previous version of backblaze/b2 from the dependency lock file
- Reusing previous version of integrations/github from the dependency lock file
- Reusing previous version of vexxhost/uptimerobot from the dependency lock file
- Reusing previous version of cloudflare/cloudflare from the dependency lock file
- Reusing previous version of hashicorp/aws from the dependency lock file
- Reusing previous version of integrations/github from the dependency lock file
- Reusing previous version of backblaze/b2 from the dependency lock file
- Finding vexxhost/uptimerobot versions matching "~> 0.8"...
- sqs in .terraform/modules/sqs

Initializing provider plugins...
- Reusing previous version of vexxhost/uptimerobot from the dependency lock file
- sqs in .terraform/modules/sqs
- Reusing previous version of hashicorp/aws from the dependency lock file

Initializing provider plugins...
- Reusing previous version of vexxhost/uptimerobot from the dependency lock file
- Reusing previous version of hashicorp/aws from the dependency lock file
- Reusing previous version of hashicorp/aws from the dependency lock file
- Reusing previous version of backblaze/b2 from the dependency lock file
- Reusing previous version of backblaze/b2 from the dependency lock file
- dynamodb_table in .terraform/modules/dynamodb_table

Initializing provider plugins...
- Reusing previous version of hashicorp/aws from the dependency lock file
- Reusing previous version of cloudflare/cloudflare from the dependency lock file
- Reusing previous version of cloudflare/cloudflare from the dependency lock file
- Reusing previous version of backblaze/b2 from the dependency lock file
- Reusing previous version of integrations/github from the dependency lock file
- dynamodb_table in .terraform/modules/dynamodb_table

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

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

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

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

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

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

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

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

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

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

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

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

Terraform has been successfully initialized!
- Installed hashicorp/aws v5.31.0 (signed by HashiCorp)

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

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

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

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

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

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

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

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

Terraform has been successfully initialized!
- Installed cloudflare/cloudflare v4.21.0 (self-signed, key ID C76001609EE3B136)

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

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

Terraform has been successfully initialized!
cloudflare_tunnel.this: Refreshing state... [id=de250703-6c08-400d-b568-bc0aa34cabaf]
data.uptimerobot_account.this: Reading...
data.uptimerobot_account.this: Read complete after 1s [id=2024-04-01 15:25:01.344837174 +0000 UTC]
data.uptimerobot_alert_contact.this: Reading...
data.uptimerobot_alert_contact.this: Read complete after 1s [id=01487022]
uptimerobot_monitor.this: Refreshing state... [id=795551117]
cloudflare_access_application.this: Refreshing state... [id=bcaa03ae-0a94-42ad-935c-487ca0a80723]
data.github_ip_ranges.this: Reading...
data.github_ip_ranges.this: Read complete after 0s [id=github-ip-ranges]
cloudflare_access_policy.telegram: Refreshing state... [id=3a7f9d55-4ddb-40bf-9671-793283e54b52]
cloudflare_access_policy.github: Refreshing state... [id=2a1fc41f-8d41-4f1f-8e72-91b0970ab129]
cloudflare_access_policy.uptime_robot: Refreshing state... [id=fd540ff0-edd5-4f64-b683-a8dd575af941]
cloudflare_access_policy.this: Refreshing state... [id=1b62d9cb-f555-4d23-b815-dfe3f92bd2a1]
b2_bucket.this: Refreshing state... [id=62c5440382b735a482bf081b]
data.github_ip_ranges.this: Reading...
data.github_ip_ranges.this: Read complete after 1s [id=github-ip-ranges]
data.aws_caller_identity.current: Reading...
module.sqs["event"].aws_sqs_queue.this[0]: Refreshing state... [id=https://sqs.eu-west-1.amazonaws.com/477397881710/jung2bot-prod-event-queue]
data.aws_caller_identity.current: Read complete after 0s [id=477397881710]
aws_sqs_queue_policy.this["event"]: Refreshing state... [id=https://sqs.eu-west-1.amazonaws.com/477397881710/jung2bot-prod-event-queue]

No changes. Your infrastructure matches the configuration.

Terraform has compared your real infrastructure against your configuration
and found no differences, so no changes are needed.
data.aws_caller_identity.current: Reading...
module.sqs["event"].aws_sqs_queue.this[0]: Refreshing state... [id=https://sqs.eu-west-1.amazonaws.com/477397881710/jung2bot-dev-event-queue]
data.aws_caller_identity.current: Read complete after 0s [id=477397881710]

No changes. Your infrastructure matches the configuration.

Terraform has compared your real infrastructure against your configuration
and found no differences, so no changes are needed.
module.dynamodb_table["messages"].aws_dynamodb_table.this[0]: Refreshing state... [id=jung2bot-dev-messages]
module.dynamodb_table["chatIds"].aws_dynamodb_table.this[0]: Refreshing state... [id=jung2bot-dev-chatIds]
aws_sqs_queue_policy.this["event"]: Refreshing state... [id=https://sqs.eu-west-1.amazonaws.com/477397881710/jung2bot-dev-event-queue]
module.dynamodb_table["chatIds"].aws_dynamodb_table.autoscaled[0]: Refreshing state... [id=jung2bot-prod-chatIds]
module.dynamodb_table["messages"].aws_dynamodb_table.autoscaled[0]: Refreshing state... [id=jung2bot-prod-messages]

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

Terraform will perform the following actions:

  # cloudflare_access_policy.this will be updated in-place
  ~ resource "cloudflare_access_policy" "this" {
        id             = "1b62d9cb-f555-4d23-b815-dfe3f92bd2a1"
        name           = "Cluster IP List"
        # (5 unchanged attributes hidden)

      ~ include {
          ~ ip                      = (sensitive value)
            # (11 unchanged attributes hidden)
        }
    }

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

No changes. Your infrastructure matches the configuration.

Terraform has compared your real infrastructure against your configuration
and found no differences, so no changes are needed.
module.dynamodb_table["messages"].aws_appautoscaling_target.table_write[0]: Refreshing state... [id=table/jung2bot-prod-messages]
module.dynamodb_table["chatIds"].aws_appautoscaling_target.table_write[0]: Refreshing state... [id=table/jung2bot-prod-chatIds]
module.dynamodb_table["messages"].aws_appautoscaling_target.table_read[0]: Refreshing state... [id=table/jung2bot-prod-messages]
module.dynamodb_table["chatIds"].aws_appautoscaling_target.table_read[0]: Refreshing state... [id=table/jung2bot-prod-chatIds]

No changes. Your infrastructure matches the configuration.

Terraform has compared your real infrastructure against your configuration
and found no differences, so no changes are needed.
module.dynamodb_table["messages"].aws_appautoscaling_policy.table_read_policy[0]: Refreshing state... [id=DynamoDBReadCapacityUtilization:table/jung2bot-prod-messages]
module.dynamodb_table["chatIds"].aws_appautoscaling_policy.table_write_policy[0]: Refreshing state... [id=DynamoDBWriteCapacityUtilization:table/jung2bot-prod-chatIds]
module.dynamodb_table["messages"].aws_appautoscaling_policy.table_write_policy[0]: Refreshing state... [id=DynamoDBWriteCapacityUtilization:table/jung2bot-prod-messages]
module.dynamodb_table["chatIds"].aws_appautoscaling_policy.table_read_policy[0]: Refreshing state... [id=DynamoDBReadCapacityUtilization:table/jung2bot-prod-chatIds]

No changes. Your infrastructure matches the configuration.

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

No changes. Your infrastructure matches the configuration.

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

No changes. Your infrastructure matches the configuration.

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

Initializing the backend...

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

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

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

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

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

No changes. Your infrastructure matches the configuration.

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


Readme: unite syntax highlighting

:+1:

@TomasVotruba Nice touch-up, thanks a ton! :smile:

:+1:


Linear scan of a repository with lots (200+) of tags causes pull IO timeout

This was originally reported at https://github.com/GoogleCloudPlatform/docker-registry/issues/22
It seems when performing "docker pull foo/bar:sometag" the repository performs a linear scan of ALL tags in "foo/bar".  When backed by object storage systems like GCS, this can take a long time.  It has broken image distribution for us.

Just as a fun data-point, I started to run into this problem right around 1700 tags for a repo, backed with S3. We are doing continuous builds, so I am able to workaround by periodically deleting large repos and re-pushing as needed.

I have the similar problems @bshi , my storage backend is s3-ceph,So has this problem been solved yet? urgently!!!


hybrid server side api

this implements the beginnings of the server side API for API nodes. this is relatively in flux API, and as such, haven't wrote a doc with the endpoints or made a client library for it as of yet. it would be nice to start lining up trains so we can start mashing some of this stuff together, even if everything is in flux, so here goes.
follows from discussion in #531. there are stubs for UpdateCall atm, we should discuss how we want this to work based on functionality highlighted here -- discuss elsewhere, probably. also, cannot really test this reliably until we can shut off the agent, which is in another patch.
anyway, choo choo

@hhexo @msgodf could you review please ?

closing for #581


update to latest snowflake

anti-fingerprinting changes made
see: https://gitlab.torproject.org/tpo/anti-censorship/pluggable-transports/snowflake/-/issues/40014

Updated to Snowflake 2.0.1 in 2e67e8d9e34a44c1490c7e34d534f91fd750d287
@bitmold, can you please test in Orbot? Esp. Snowflake Proxy start/stop has changed a lot.

This issue might be worth revisiting for snowflake 2.1.0

+- Issue 40098: Remove support for legacy one shot mode
+- Issue 40079: Make connection summary at proxy privacy preserving
+- Issue 40076: Add snowflake event API for notifications of connection events
+- Issue 40084: Increase capacity of client address map at the server
+- Issue 40060: Further clean up snowflake server logs
+- Issue 40089: Validate proxy and client supplied strings at broker
+- Issue 40014: Update version of DTLS library to include fingerprinting fixes
+- Issue 40075: Support recurring NAT type check in standalone proxy

Among other things, there's an official event API that IPtProxy should be using

My mistake on this, it looks like these callbacks are for the client, not for hosting a proxy

All your suggested changes available for your enjoyment: https://jitpack.io/#tladesignz/IPtProxy/1.5.0

(Snowflake now at 2.1.0)


Parvatibai Genba Moze college of Engineering Pune

www.pgmozecoepune.in
https://www.pgmozecoepune.in/information-technology-department/
Prof. Abidali Shaikh
Head of Information Technology Department

@pgmoze First stage of verification passed, official domain for Parvatibai Genba Moze College of Engineering Pune is pgmozecoepune.in as far as I verified. This is just an informational note. Pull request is still in the review. I appreciate your patience while waiting for the final decision.

We offer 4 year Engineering Degree in Computer Engineering,   Information Technology , Artificial Intelligence and Data Science .
We also offer Master of Computer Applications.
Address : Parvatibai Genba Moze College Of Engineering Gat No. 1178, Wagheshwar Temple, Talathi Office, MOZE Campus, Wagholi, Pune, Maharashtra 412207, India

@pgmoze Pull request merged. Thank you.


pushing initial code and test

I confirm these files are made available under CC0 1.0 Universal (https://creativecommons.org/publicdomain/zero/1.0/legalcode)
Issue: https://github.com/awslabs/aws-config-rules/issues/165
Description of changes:

@hary10, thank you for the PR.
@jongogogo, kindly verify the PR


artbot: keep a revision history

arts that are recorded over we need to keep the old versions saved as past revisions. think we should use git for this it can already handle all the stuff we would want out of it.
this will be especially helpful if a troll attacks the arts current backup of the whole repo are made

Also important to git mv the file if it already exists because our art system is case insensitive, should do a quick search of the existing arts for conflicts too


Question: Where is the src directory?

Hi,
Just an observation. I can see the end result but was wondering if there was a src directory that you use to build the final file and if that was ever available?
Thanks,
John

bignumber.min.js is built from bignumber.js which is also in the root directory.


issue with include in c++

We have written the needed data into your clipboard because it was too large to send. Please paste.

Please provide more details and steps


[BUG]Integrate clone volume dialog

Describe the bug

To Reproduce
Steps to reproduce the behavior:

Go to Volume list
Click menu action
You'll see both of Clone Volume and Clone

Expected behavior

It's expected to integrate that two action like below.

Support bundle

Environment

Harvester ISO version:
Underlying Infrastructure (e.g. Baremetal with Dell PowerEdge R630):

Additional context
Add any other context about the problem here.

close as resolved.

Test Information

Environment: qemu/KVM single node
Harvester Version: master-937f333c-head
ui-source Option: Auto

Verify Steps:

Install Harvester with any nodes
Follow Steps to reproduce in https://github.com/harvester/harvester/issues/2855#issue-1391947204


Change exposed port for deepforge-stable

We should change the shared port for editor.deepforge.org (i.e. deepforge-stable)
https://github.com/deepforge-dev/deepforge/blob/e384d1d86233c44e8841bc03bd342dd0efa0dbb0/.deployment/docker-compose-overrides.yml#L23
Since, 8889 is used by the deepforge-latest.
https://github.com/deepforge-dev/deepforge/blob/e384d1d86233c44e8841bc03bd342dd0efa0dbb0/docker/docker-compose.yml#L15-L16

@brollb I have changed the nginx config to proxy pass port 9000 for editor.deepforge.org. I think we should change it here as well.


Regex substitution of literal escape chars interprets them instead

Regex substitution of literal escape chars interprets them instead.  For example:
$tsnr =~ s'tsnr'\t \n\r';

doesn't escape the escape sequences on the RHS of the re.sub call.

Fixed in v1.001


Imported XSLT changes not being updated when pipeline saved

Changes made to an XSLT that is imported into another are not being reflected even when the pipeline is saved to try and import the new changes (as used to happen).  The only way I could get it to work was to clear the XSLT Pool Cache.
Probably connected to #2937
This is in b.203 so may have been fixed in later versions.

Fixed in >7.0.1


Multiple Carbonite inserts in a single transaction

Hello, how does one make multiple carbonite inserts in a transaction that touches multiple tables?
                Ecto.Multi.new()
                |> Carbonite.Multi.insert_transaction(%{meta: %{type: "account_updated"}})
                |> Ecto.Multi.update("account", account_changeset)
                |> Carbonite.Multi.insert_transaction(%{meta: %{type: "create_wallet"}})
                |> Ecto.Multi.insert("wallet", %Wallet{create_params | wallet_id: wallet_id, uri: uri})
                |> Test.Repo.transaction()} do

This always fails with :carbonite_transaction is already a member of the Ecto.Multi: but in this case, what would you recommend as a best practise for including Carbonite in a transaction that hits multiple tables at one go?
Thanks.

Hello @gaslit,
I think the problem that you are running into is more a conceptual one.
Originally we designed carbonite in a way, that the changes from one transaction are grouped together, so it is later on visible what changes are related.
So in your example, if the creation of a wallet, triggers the update in the account, that update of the account happened because the wallet was created. Not entirely sure about your example, but lets say the above change was happening because you onboarded a user, that clicked on the account confirmation link and now you can create a wallet for them. Then then it would be more like this:
Ecto.Multi.new()
|> Carbonite.Multi.insert_transaction(%{meta: %{type: "onboard_account"}})
|> Ecto.Multi.update("account", account_changeset)
|> Ecto.Multi.insert("wallet", %Wallet{create_params | wallet_id: wallet_id, uri: uri})
|> Test.Repo.transaction()}

Since the changes happened in the same transaction, there is no need to add a second carbonite transaction to it, since that would defeat the purpose of the library https://github.com/bitcrowd/carbonite#how-it-works
(The only place where it might make sense to have two or more carbonite transactions in there, is if you installed carbonite in multiple DB schemas (prefixes). I that case you could use Carbonite.insert_transaction with Ect.Multi.run, but I guess that is not what you are looking for)

Hi Andi,
Appreciate your kind help - but in your example, I wouldnt be able to update the account and wallet tables as it will violate the triggers:
install_carbonite.exs (Migrations exs)
      Carbonite.Migrations.create_trigger("account")
      Carbonite.Migrations.put_trigger_config("account", :primary_key_columns, ["purse_proxy_id"])
      Carbonite.Migrations.create_trigger("wallet")
      Carbonite.Migrations.put_trigger_config("wallet", :primary_key_columns, ["wallet_id"])

And will generate an error as Carbonite will require an insert_transaction for both account and wallet.
Many thanks Andi.

as it will violate the triggers

The triggers just require a carbonite transaction to be there. You can happily use the same one for the updated account and the wallet. As said before, the idea behind carbonite is to relate changes in different models into one transaction

And will generate an error as Carbonite will require an insert_transaction for both account and wallet.

Have you really tried? This should not produce an error. If you are getting one still I'd be curious what the error really is.
Maybe you can provide a minimal example of it in case you really run into something, so I can help better.
Cheers,
Andi

Hi Andi,
This is so embarrassing. All is fine now. Many thanks for the kind help.
I ripped out the old code and redid it.
reason: %Postgrex.Error{connection_id: 2259956, message: nil, postgres: %{code: :foreign_key_violation, file: "pl_exec.c", line: "3873", message: "UPDATE on table public.wallet without prior INSERT into carbonite_default.transactions", pg_code: "23503", routine: "exec_stmt_raise", severity: "ERROR", unknown: "ERROR", where: "PL/pgSQL function carbonite_default.capture_changes() line 1 at RAISE"}

I got this error because I placed the Carbonite.Multi.insert_transaction after some queries - and then misinterpreted the above error as requiring a Carbonite.Multi.insert_transaction for every affected table which obviously didnt work. Hope the above might be of help to anyone with the same issue.
All is good now Andi and i really appreciate your kind help.
A question:

So your recommendation is for Carbonite to record a transaction in totality in a single Carbonite row. Any tips if one is very finicky about data pollution (to keep the rows as concise and clean as possible)?

Many thanks

So your recommendation is for Carbonite to record a transaction in totality in a single Carbonite row.

It is not only my recommendation, it is the only thing that you can do in carbonite by design.
-> 1 db transaction <=> 1 carbonite transaction <=> multiple changes tracked
Under the hood carbonite will reference the changes that you do with the triggers by db transaction id, so it is not easily possible to do anything else with carbonite (which is the reason, why Carbonite.insert_transaction will ignore subsequent calls in the same database transaction.

Any tips if one is very finicky about data pollution

I am not quite sure on what you mean here. Carbonite will record any change on the tracked schemas into the changes of a transaction. If you later want to clean your data a bit you might also do so with the Carbonite.Outbox.


'OpenXmlElementList' does not contain a definition for 'GetItem'

Missing method for getting item from OpenXmlElementList class.
Starting from version: 3.0.0
Working version: 2.20.0
Error	CS1061	'OpenXmlElementList' does not contain a definition for 'GetItem' and no accessible extension method 'GetItem' accepting a first argument of type 'OpenXmlElementList' could be found (are you missing a using directive or an assembly reference?)

Can you share your code sample?
Did you try:
OpenXmlElementList list = ....;
var item = list[index];

There were a number of breaking changes from v2.x - not sure if this one got documented, but let me know if it works and I'll make sure the docs are updated.

Tried, seems to work. I was just not finding any breaking change in the docs regarding that method.

@twsouthwick what exactly is needed here? Code change or documentation?

Docs update

Docs update

How to do that??

Can you share your code sample?
Did you try:
OpenXmlElementList list = ....;
var item = list[index];

There were a number of breaking changes from v2.x - not sure if this one got documented, but let me know if it works and I'll make sure the docs are updated.

Where to write this??

@Babufrik123
https://github.com/OfficeDev/open-xml-docs/blob/main/docs/migration/migrate-v2-to-v3.md
Happy to take a PR to update that or any other doc changes :)

@Babufrik123
https://github.com/OfficeDev/open-xml-docs/blob/main/docs/migration/migrate-v2-to-v3.md
Happy to take a PR to update that or any other doc changes :)

Can u please explain in detail what exactly nedds to be done to use getitem().

OpenXmlElementList list = ....;
var item = list.GetItem(index);

to
OpenXmlElementList list = ....;
var item = list[index];

OpenXmlElementList list = ....;
var item = list.GetItem(index);

to
OpenXmlElementList list = ....;
var item = list[index];

OpenXmlElementList list = ....;
var item = list.GetItem(index);

to
OpenXmlElementList list = ....;
var item = list[index];

Hi twsouthwick,
I still didnt unterstand, can u please give a step by step guide. Actually I m reading data from excel to data table using document open xml and there that getitem() is required.But due to latest version I m not able to use that.I m attaching the link of my code please refer that and share what to do.
https://www.aspsnippets.com/Articles/1463/Read-and-Import-Excel-data-to-DataTable-using-OpenXml-in-ASPNet-with-C-and-VBNet/

What I supplied is the only step needed. The call to GetItem needs to be changed to an indexer.

doc.WorkbookPart.SharedStringTablePart.SharedStringTable.ChildElements.GetItem(int.Parse(value)).InnerText
How will you rewrite this?

What I supplied is the only step needed. The call to GetItem needs to be changed to an indexer.

doc.WorkbookPart.SharedStringTablePart.SharedStringTable.ChildElements.GetItem(int.Parse(value)).InnerText
How will you rewrite this?

What I supplied is the only step needed. The call to GetItem needs to be changed to an indexer.

doc.WorkbookPart.SharedStringTablePart.SharedStringTable.ChildElements.GetItem(int.Parse(value)).InnerText
Help me rewrite this. U can see getitem here

What I supplied is the only step needed. The call to GetItem needs to be changed to an indexer.

doc.WorkbookPart.SharedStringTablePart.SharedStringTable.ChildElements.GetItem(int.Parse(value)).InnerText
Help me rewrite this. U can see getitem here

doc.WorkbookPart.SharedStringTablePart.SharedStringTable.ChildElements.[int.Parse(value)].InnerText

Thanks @BazInTheAZ :) @Babufrik123 I'd recommend taking a look at some of C# specifications so you can understand the syntax here: https://learn.microsoft.com/dotnet/csharp/programming-guide/indexers


WebView state is not saved/restored breaking rotation

The WebView's state isn't saved in the bundle so it is lost when the activity hosting it is suspended (such as due a configuration change like device rotation).
TurbolinksView should implement the save and restore instance methods, something like this:
@Override
protected Parcelable onSaveInstanceState() {
	// Create a bundle to put super parcelable in
	Bundle bundle = new Bundle();
	bundle.putParcelable("super", super.onSaveInstanceState());
	webView.saveState(bundle);
	return bundle;
}

@Override
protected void onRestoreInstanceState(Parcelable state) {
	Bundle bundle = (Bundle) state;
	webView.restoreState(bundle);
	super.onRestoreInstanceState(bundle.getParcelable("super"));
}

I'm just not sure how to get the webView in order to submit a PR.

@candrews We've found for most activities we don't need to save specific activity instance state for device rotation, since the majority of the UI is the WebView and its state is managed by Turbolinks (and swapping native resources are not necessary). We have the following on our <activity> declarations in our manifest to avoid automatic activity restarts for orientation or screen size changes:
android:configChanges="keyboard|keyboardHidden|orientation|screenSize"

https://developer.android.com/guide/topics/resources/runtime-changes.html#HandlingTheChange
The library doesn't not manage the activity lifecycle, and I don't see us changing that anytime soon. If, however you'd like to manage the activity lifecycle and instance state, you can easily obtain a reference to the webview in your activity from:
TurbolinksSession.getDefault().getWebView()

With the WebView reference, you can save any instance state you'd like.

I agree that having the Activity use TurbolinksSession.getDefault().getWebView() to save/restore state is a good workaround and I'm doing that today - but, it does seem surprising that TurbolinksView doesn't save/restore state because other views do. For example, if I simply put a WebView in my layout, it would automatically have it's state saved/restored, but changing that WebView to a TurbolinksView doesn't.

@candrews I agree that it would probably be beneficial as a default. Curious, do you have other instance state that you're managing for native UI?
We're going to cut a new version of the library soon. Currently, there's not a direct way to access the WebView in TurbolinksView. If there's a straightforward way of doing that without it turning into a leaky reference, we can save the instance state easily like you mentioned.

I do not currently have any other instance state that I'm managing for the native UI.
I feel like there has to be away to do this... TurbolinksView has a reference to TurbolinksSession and that has the WebView so can it be retrieved using that chain?

@candrews If you have a code suggestion, we'd be happy to look at it via a pull request. That's often the best way to move along an issue you feel strongly about. Thanks!

@candrews Version 1.0.3 has just been released. Note that the WebView can now be obtained internally in TurbolinksView via:
refreshLayout..getChildAt(1)

A test has also been added for this:
https://github.com/turbolinks/turbolinks-android/blob/master/turbolinks/src/test/java/com/basecamp/turbolinks/TurbolinksViewTest.java#L38


fix: php serialize_precision should be -1 in php >= 7.1, fixes #5092

The Issue

#5092

How This PR Solves The Issue
Change the affected serialize_precision values
Manual Testing Instructions

ddev ssh and php -r "var_dump(0.6);" - should show float(0.6)

Automated Testing Overview
Added TestPHPConfig

Looks good to me, I downloaded the binary from this PR and tested against https://github.com/hanoii/ddev-pr-5227
With v1.22 I get:
ddev exec 'php -r "var_dump((float) 0.6);"'
float(0.59999999999999998)

With the binary from this PR I get:
ddev exec 'php -r "var_dump((float) 0.6);"'
float(0.6)

This on PHP 8.1 - I haven't tested any other PHP version

I went ahead and tried 7.4 and 7.0, output was fine on both
ddev exec 'php -r "var_dump((float) 0.6);"'
float(0.6)


Improved feature parity: ALG logging profiles

Is your feature request related to a problem? Please describe.
It is not possible to create an ALG logging profile with AS3
Describe the solution you'd like
I would like to create an ALG logging profile with AS3, as it is feasible with the CLI (create ltm alg-log-profile) or the GUI (Local Traffic / Profiles / Other / ALG Logging).
The configurable parameters should be the same as with the CLI/GUI.
Describe alternatives you've considered
I create the ALG logging profiles out of AS3 (with non declarative commands).
Additional context

@LaurentGravier please can you reach out to me<EMAIL_ADDRESS>I would like to have a call/email/chat with you to understand better the use case. There may be other ways to look at this issue that could work better.

@LaurentGravier @sunitharonan and I are looking at this issue. BTW we dont see the "tmsh" commands to create this profile
root@(ocp-02)(cfg-sync In Sync)(Standby)(/Common)(tmos)# create alg-log-profile ?
Syntax Error: "alg-log-profile" unexpected argument
root@(ocp-02)(cfg-sync In Sync)(Standby)(/Common)(tmos)# create alg-log-profile

@mdditt2000 @sunitharonan
It looks like this profile requires the CGNAT module to be provisioned.

Yes, CGNAT module has to be provisioned to be able to use command create alg-log-profile in CLI mode.
Theoretically, the AFM module is sufficient for making CGNAT, but because of the ALG log profiles, it remains necessary to provision the CGNAT module.  By the way, such provisioning is not necessary if you want to create ALG log profiles with the GUI. This is described in bug tracker ID 1097973.

This has been resolved with AUTOTOOL-3491 backlog item  in As3 3.43.0. Thanks.


Use join() in Mesos executor to collect task threads

We decided not to join each thread, but we are now ending each task before shutting down the executor, via 897f1b70b7b8fb9b7cba90d7d6cfb85eed79c854


Add custom task failure notification doc

Closes #1255.

Closing this. Will address feedback in a new PR targeting master.


RSD Sqlite not accepted

Describe the bug
RSD Sqlite extension is not tolerated
Error: : invalid sqlite file extension

To Reproduce
Steps to reproduce the behavior:
dblab --db ~/Data.rsd --driver sqlite

Expected behavior
Accept .rsd as valid .sqlite alternative
OS (please complete the following information):

Ubuntu 22.04 64bit / Linux 6.5.0-35-generic
Version dblab : 0.24.0

@matbgn I made a PR (#215) to address this issue. I removed all validation on sqlite file extensions, since it can be any, sqlite will figure out if the file is valid.

I just tried your branch and it works! Thanks


Boba Bedrock (anchorage) upgrade

Ready for review
Highest similarity: .83 for karak, but latest version of the op stack contracts.

discovery error:

Errors during discovery: 3
SystemConfig(0x158Fd5715F16Ac1F2Dc959A299B383aAaf9B59EB): {
        batcherHash: Execution reverted
        opStackDA: Dependency error: Execution reverted
        sequencerInbox: Dependency error: Execution reverted
}

but it discovers the 3 values correctly

genesisTimestamp in .ts should be boba genesis or boba bedrock genesis?
~upgradeability TODO~

taken from Optimism: we should subtract 1 only after upgrade block and not override past blocks

cool, and genesisTimestamp stays at the boba network genesis correct?

taken from Optimism: we should subtract 1 only after upgrade block and not override past blocks

cool, and genesisTimestamp stays at the boba network genesis correct?

no it should be the genesis timestamp of the upgrade, see opStack template code for the reason. Also, we are missing a way to add nonTemplate tracked tx, pls go to matt

nontemplateTxs for opstack is merged and now used here. I also added the vanilla opstack trackedTxs in the .ts since they are not additive in the template.
timestamp of upgrade:<PHONE_NUMBER>
genesisTimestamp:<PHONE_NUMBER>
boba l2 bedrock block: 1149019


Update default trace endpoint and allow downgrades

This is for parity with the Ruby ddtrace gem: https://github.com/DataDog/dd-trace-rb/blob/d3a6a87743546fe5f428db4b4535a5ad12c75138/lib/ddtrace/transport/traces.rb#L113-L126
I'm having some trouble unit testing, so I'm going to pull my branch into another service I have and try testing it out in a more "integrated" fashion

There seem to be more problems with the library than are worth fixing.  Switching to datadog-apm-sync instead


Business Knowledge Model Decision Table

We need to create decision tables linked to Business Knowledge Models - the same as with Decisions.
I understand that on a lower implementation level Decision Tables get executed regardless their origin (Decision / Business Knowledge), but in terms of modelling and documentation I need to differentiate it as it will make it more clear for business and for communicating to others – hence the need to conform to standards. We need to get models signed-off and approved before we can progress to implementation stage.

Thank you for your feedback. @falko what is your opinion on this?

@HeinnE I don't fully understand what you want to achieve and how a BKM would help. Could you give an example diagram?

If you just need an annotation, you could try to work with BPMN-style text annotations.

DMN_formal-16-06-01.pdf
@falko Please refer to the OMG Group DMN Standard attached - Fig 2 on page 17 & Fig 9 page 24 as examples. Business Knowledge gets modelled separately as input for the Decision Table associated with the decision. I need to differentiate between the Business Knowledge decision table as from the Decision logic - hope it makes better sense now.

Here are the figures that you mentioned...
Figure 2 – DMN Constructs:

Figure 9 - Business knowledge model and corresponding decision table:

What do you want to express by your distinction between a Decision Table implementing a Decision versus a Decision Table encapsulated inside a BKM that is invoked by a Decision? BKMs are primarily meant for reuse of decision logic. Do you want to make your Decision Table reusable or invokable? If so, have you thought about using simple Information Requirements to reuse a Decision Table?

@HeinnE since we haven't heard back from you, I'll close this issue.

Hi @falko ,
I would like to iterate over the following model:

using a literal expression that looks like
for something in somethings return someLevel(something)

For this I believe I need either a decision service, which calls the whole DRD, or the possibility to invoke the decision tables through business knowledge models.
For the latter option, using business knowledge models, this could look like the below for the top 2 levels of the original model:

Note that the Business Knowledge Models would be invoking the decision tables that you see here visually on the right.
For the bottom part,

I believe it would be best to model the iteration version as a boxed context, with two context entries each of which calls one of the decision tables.


this plugin is suit for form but grid editor is good layout

this plugin is suit for form control but in grid editor is not good layout

Hi!
Any update about the time selector on grid filters?
Thank you!


Fixed Reset related ~line 43 Warning typos

@medgarmedgar might not be using this account anymore due to a recent development.

Would you accept a whitespace improvement suggestion from me, although it might seem cosmetic to you?
I am constantly seeking to implement MarkDown indent marker compatibility spacing for the Note blobs (note, tip, important, warning, and so on).
Several of my own Pull Requests to Microsoft Docs are focused entirely on this specific subject.
Feel free to tell me if you require a MarkDown sourced reference for this spacing codestyle.

Would you accept a whitespace improvement suggestion from me, although it might seem cosmetic to you?
I am constantly seeking to implement MarkDown indent marker compatibility spacing for the Note blobs (note, tip, important, warning, and so on).
Several of my own Pull Requests to Microsoft Docs are focused entirely on this specific subject.
Feel free to tell me if you require a MarkDown sourced reference for this spacing codestyle.

I'm completely fine with that, I assume this will not affect the final output and I'll get a chance to preview before it's posted? If I'm The typos I fixed have been on for a while and I'd like them updated as soon as we can.

Sure, it is unrelated to your own changes nor will it affect those. The suggestion will be posed for you to approve & commit at your own leisure.

Although there are quite a few inconsistencies regarding this specific MarkDown codestyle in this rather long page, I will refrain from suggesting any more changes. My goal here is mostly to spread the awareness about the single space between the MarkDown indent marker ( > ) and any following text being the de facto standard, whereas cases of a missing space is mentioned as "lazy coding" in MarkDown documentation.

Uhm, is this PR being closed to make place for a new PR in the private branches?

Uhm, is this PR being closed to make place for a new PR in the private branches?

My apologies. My first time on the process. I just want this merged and change visible in public doc as soon as possible, my assumption was I needed to close this to have that happen?

Thank you. As you can see, the only way to get a PR published is to wait for one of the MS Docs maintainers or page managers to merge an open PR when it has been properly reviewed and deemed to be ready.
The next time you open a Pull Request and you are confident that all changes have been applied, simply comment with a single line saying only the following:
#sign-off

Also: Thank you for your contribution and the kind cooperation on my offer to improve your posted content.

Thank you. As you can see, the only way to get a PR published is to wait for one of the MS Docs maintainers or page managers to merge an open PR when it has been properly reviewed and deemed to be ready.
The next time you open a Pull Request and you are confident that all changes have been applied, simply comment with a single line saying only the following:
#sign-off

Thanks. They have also communicated they will grant write permissions so I can merge my PRs.

Very well, that sounds great. I wish you all the best in your future work in the MSDocs private repository.


How to integrate NativeExpressAdView to FirebaseRecyclerAdapter ?

Hello,
I'm wondering if there is any good way of integrating native ad express to FirebaseRecyclerAdapter ?
I'm struggling with the problem, how to connect NativeExpressAdView with your FirebaseArray container ? Any samples or suggestions ?

@stasbar there's nothing specific about FirebaseRecyclerAdapter that should make it easier or harder to use an AdView versus a regular RecyclerAdapter.  Github issues should be reserved for possible bugs in the library (with code and logs) or specific feature requests.  Please ask this question on StackOverflow.


Nested object discriminator field doesn't get serialized to str properly in model_dump

Initial Checks

[X] I confirm that I'm using Pydantic V2

Description
If using a discriminator field for a nested object as seen in the example code, the model_dump function does not serialize that discriminator field from SomeEnum to str.
I would have expected that discriminator field to be serialized automatically.
Example Code
from enum import Enum
from pydantic import BaseModel, Field
from typing import Literal

class SomeEnum(str, Enum):
    A = "a"
    B = "b"
    C = "c"

class InnerClass(BaseModel):
    field: Literal[SomeEnum.A, SomeEnum.B]

class OuterClass(BaseModel):
    inner: InnerClass = Field(discriminator="field")

def test_inner_class():
    inner = InnerClass(field=SomeEnum.A)
    d = inner.model_dump(mode="json")
    assert d["field"] == "a"

def test_outer_class():
    outer = OuterClass(inner=InnerClass(field=SomeEnum.A))
    d = outer.model_dump(mode="json", by_alias=True)

    assert not isinstance(d["inner"]["field"], SomeEnum)
    assert isinstance(d["inner"]["field"], str)
    assert str(d["inner"]["field"]) == "a"

if __name__ == "__main__":
  test_inner_class() # Works as expected
  test_outer_class() # assert error

Python, Pydantic & OS Version
pydantic version: 2.7.0
        pydantic-core version: 2.18.1
          pydantic-core build: profile=release pgo=true
                 install path: /Users/kent/Library/Caches/pypoetry/virtualenvs/pydantic-test-3SUq0Hnt-py3.11/lib/python3.11/site-packages/pydantic
               python version: 3.11.1 (main, Mar 16 2023, 12:51:25) [Clang 13.1.6 (clang-13<IP_ADDRESS>.5)]
                     platform: macOS-12.5.1-arm64-arm-64bit
             related packages: typing_extensions-4.11.0
                       commit: unknown

I don't know if this is unexpected or even fixable behavior, but created a PR with failing test case. I may delve into the code and see if there is an easy fix for this and add it for your review. If the PR is unwanted, please close, I won't be offended.

@kf-novi,
Thanks for reporting this. I don't actually know if this is a bug - why would you use a discriminator here, if the type isn't a union?
Just a note - this isn't a regression in 2.7.0, but rather has been present throughout recent minor releases.

The bug exists whether or not you use a union. I should have made that
clear.
On Sat, Apr 13, 2024 at 16:27 Sydney Runkle @.***>
wrote:

@kf-novi https://github.com/kf-novi,
Thanks for reporting this. I don't actually know if this is a bug - why
would you use a discriminator here, if the type isn't a union?
Just a note - this isn't a regression in 2.7.0, but rather has been
present throughout recent minor releases.
—
Reply to this email directly, view it on GitHub
https://github.com/pydantic/pydantic/issues/9235#issuecomment-2053796194,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/A5CBQT6PHMSSAU3RAFQKMEDY5G5P5AVCNFSM6AAAAABGE4QDWGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDANJTG44TMMJZGQ
.
You are receiving this because you were mentioned.Message ID:
@.***>

Ah I see, thanks

I did investigate a fix and quickly discovered it would be in pydantic
core. Rust and serde are not my native languages so I spun out
pretty quickly.
On Sat, Apr 13, 2024 at 17:22 Sydney Runkle @.***>
wrote:

Ah I see, thanks
—
Reply to this email directly, view it on GitHub
https://github.com/pydantic/pydantic/issues/9235#issuecomment-2053816267,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/A5CBQT72GQW6RI77SMGEOULY5HD3FAVCNFSM6AAAAABGE4QDWGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDANJTHAYTMMRWG4
.
You are receiving this because you were mentioned.Message ID:
@.***>

Yep, makes sense. Especially now that we've moved the enum validation logic over there.

This appears to be a regression in pydantic/pydantic-core. This bug does not exist in 2.6.4 but does exist in 2.7.0.
pydantic-core version for my 2.6.4 install is 2.16.3
pydantic-core version for my 2.7.0 install is 2.18.1

Did some further investigation. I got as far back as pydantic-core 2.17.0 with this bug still in place. serialize_as_any was added to to_python in 2.17.0 so that was the farthest back I could easily go in my search for this regression.
So, my guess is this bug was introduced in pydantic-core 2.17.0. Not sure about the particular feature or commit that introduced it. Hopefully that helps track it down!

🤔 I rigged up pydantic-core on my dev box and started rolling back changes. The commit that causes the regression seems to be https://github.com/pydantic/pydantic-core/commit/71d54a243f52550847716cb4208944667ebc16ee which is the upgrade to PyO3 0.21 beta.

I've traced the issue to src/serializers/type_serializers/literal.rs
In pydantic/pydantic-core@91c3541 the line in question is 125. Before pyo3 0.21.0 the "inner" value is dog but after, it's SomeEnum.DOG
I don't know why this is happening. I'm having fun tracking this down so I'll see if I figure it out or not.
If I'm abusing the issue comments, please tell me and I'll stop posting new ones and edit the old ones.

@kf-novi,
No worries at all! Always good to have a live discussion re debugging. Ping me if you have any questions (though admittedly, @davidhewitt will be able to help much more promptly with the pyo3 upgrade stuff).

@davidhewitt I found the behavior change!
In src/serializers/type_serializers/literal.rs line 92, the previous commit had
return Ok(OutputValue::OkStr(s));

and in the upgrade to pyo3 v0.21, it was changed to
return Ok(OutputValue::OkStr(py_str.clone()))

py_str.to_string() returns "SomeEnum.DOG" but py_str.to_str()?.to_string() returns "dog"
My proposed fix is
return Ok(OutputValue::OkStr(PyString::new_bound(value.py(), s)));

I think @kfreezen will create the PR for this one 😁 you can do with it what you will from there.

Thanks for the great detective work here. Is there any update with respect to a released fix?

I have a PR that fixes in pydantic-core. It needs a unit test but I’m
stumped on what needs to be written and where
On Fri, Jun 14, 2024 at 05:18 Matthew Ferrera @.***>
wrote:

Thanks for the great detective work here. Is there any update with respect
to a released fix?
—
Reply to this email directly, view it on GitHub
https://github.com/pydantic/pydantic/issues/9235#issuecomment-2167901781,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/A5CBQT4NZAVMHFOXKSU7F3LZHLNS3AVCNFSM6AAAAABGE4QDWGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCNRXHEYDCNZYGE
.
You are receiving this because you were mentioned.Message ID:
@.***>

pydantic-core#1286 for those interested
On Fri, Jun 14, 2024 at 05:22 kf-novi @.***> wrote:

I have a PR that fixes in pydantic-core. It needs a unit test but I’m
stumped on what needs to be written and where
On Fri, Jun 14, 2024 at 05:18 Matthew Ferrera @.***>
wrote:

Thanks for the great detective work here. Is there any update with
respect
to a released fix?
—
Reply to this email directly, view it on GitHub
<
https://github.com/pydantic/pydantic/issues/9235#issuecomment-2167901781>,

or unsubscribe
<
https://github.com/notifications/unsubscribe-auth/A5CBQT4NZAVMHFOXKSU7F3LZHLNS3AVCNFSM6AAAAABGE4QDWGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCNRXHEYDCNZYGE>

.
You are receiving this because you were mentioned.Message ID:
@.***>

—
Reply to this email directly, view it on GitHub
https://github.com/pydantic/pydantic/issues/9235#issuecomment-2167910196,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AACUWLH2TBF75KEFC2EI2KTZHLOADAVCNFSM6AAAAABGE4QDWGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCNRXHEYTAMJZGY
.
You are receiving this because you were mentioned.Message ID:
@.***>

@kfreezen @kf-novi,
Amazing work here! Thanks for digging into this!!

Fixed by https://github.com/pydantic/pydantic-core/pull/1286


SQL fixtures needed for tileserver operation

There are several sets of database fixtures needed for the tileserver to operate correctly. These include a variety of resources each with a different level of coupling to the tileserver Python code:

Table definitions for the cache system
Tile utility functions
Function definitions that create tiles for certain layers (e.g., the carto and maps layers)

These need to be created for the tileserver to operate properly. However, there are a few factors to consider with this design:

Some tile layers (e.g., paleogeography layers) are defined in the Macrostrat repository. There is a two-way dependency between the tileserver code and that schema.
We've tried to automatically apply these fixtures on tileserver spin-up before, but we've had problems with table locks since we've run that SQL synchronously
We've got a new migrations system that makes applying these fixtures potentially relatively simple, but it would be tedious to define a new migration every time tile layer definitions change

It seems like the right approach would be to either

Move the bulk of this SQL to the Macrostrat repository, which would come at the cost of having the tileserver be in control of its own layer definitions
Re-implement more of this code as static SQL called on-demand in the tileserver codebase (which would reduce some of the 'move-fast' benefits of having function-defined layers), and we'd still need to move the table defs etc.
Figure out how to get the fixtures to run properly on tileserver spin-up.
some combination of the above

At some level this problem is analogous to some of the API design/dependency issues created by the PostgREST APIs. Architectural input is welcome

We've tried to automatically apply these fixtures on tileserver spin-up before, but we've had problems with table locks since we've run that SQL synchronously
…
Figure out how to get the fixtures to run properly on tileserver spin-up.

I think I need to hear more details on what exactly is contending for the table locks. In the abstract, I'd have two tasks that can be run completely independently of each other:

Applying fixtures to the database
Starting and running the tileserver

Then, we run these tasks in sequence, one after the other. In a k8s Pod definition, (1) becomes an init_container and (2) becomes a normal container. K8s will guarantee that (1) completes successfully before (2). The process of applying the fixtures shouldn't step on anything else's toes (because the tileserver proper isn't running yet), and the tileserver can simply assume that the database is laid out properly when it starts (so it doesn't to worry about sequencing start-up tasks before serving "real" requests).

@brianaydemir in this design would it also be possible to apply the fixtures "on demand" while the pods are running? Right now we tend to apply database fixtures by command-line since they require a fairly long toolchain.
I guess a related question is — what is the right way to run migrations (including the more general ones produced by @mwestphall is working on) in production? Is it in some sort of containerized workflow as you laid out above, ensuring that the "right" state of the database is present at all times? Or do we simply run migrations ourselves and update containers in coordination with that? I guess it gets complicated because different containers will depend on different "subsystems" to be at their most up-to-date schema...

@davenquinn As long as the database is up and running, the only things stopping you from making changes to it are the other services trying to make use of it in its current state.
I guess one thing to consider is the way we run K8s and services on it is that we have a(nother) Git repository that declaratively specifies what the state of the services on the cluster should be, so there's a general expectation that everything needed to get a service up and running is in that YAML. So, if a service requires the database be in a particular state, the service and its definition would, ideally, ensure that.


tk diff -t requires the resource type to be lower case

when doing tk show it shows me resource types, such as ConfigMap in camel case. but when i try to do tk diff and use the -t parameter to select one specific resource i need to specify the resource type in lower case (configmap) for it to work, when i write it ConfigMap then tk seems to not find the resource. I think this should be case insensitive.

Already fixed, needs review though


HBASE-28420 Update the procedure's field to store for ServerRemoteProcedure (#5816)

HBASE-28420 Update the procedure's field to store for ServerRemoteProcedure (#5816)

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Comment

+0 :ok:
reexec
0m 54s
Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  1s
No case conflicting files found.

+0 :ok:
prototool
0m  1s
prototool was not available.

+1 :green_heart:
hbaseanti
0m  0s
Patch does not have any anti-patterns.

+1 :green_heart:
@author
0m  0s
The patch does not contain any @author tags.

_ branch-2 Compile Tests _

+0 :ok:
mvndep
0m 11s
Maven dependency ordering for branch

+1 :green_heart:
mvninstall
3m  0s
branch-2 passed

+1 :green_heart:
compile
3m 14s
branch-2 passed

+1 :green_heart:
checkstyle
0m 47s
branch-2 passed

+1 :green_heart:
spotless
0m 47s
branch has no errors when running spotless:check.

+1 :green_heart:
spotbugs
3m 21s
branch-2 passed

_ Patch Compile Tests _

+0 :ok:
mvndep
0m 16s
Maven dependency ordering for patch

+1 :green_heart:
mvninstall
2m 46s
the patch passed

+1 :green_heart:
compile
3m 13s
the patch passed

+1 :green_heart:
cc
3m 13s
the patch passed

+1 :green_heart:
javac
3m 13s
the patch passed

+1 :green_heart:
checkstyle
0m 44s
the patch passed

+1 :green_heart:
whitespace
0m  0s
The patch has no whitespace issues.

+1 :green_heart:
hadoopcheck
9m 23s
Patch does not cause any errors with Hadoop 2.10.2 or 3.3.6.

+1 :green_heart:
hbaseprotoc
1m  5s
the patch passed

-1 :x:
spotless
0m 37s
patch has 23 errors when running spotless:check, run spotless:apply to fix.

+1 :green_heart:
spotbugs
3m 35s
the patch passed

_ Other Tests _

+1 :green_heart:
asflicense
0m 22s
The patch does not generate ASF License warnings.

36m  7s

Subsystem
Report/Notes

Docker
ClientAPI=1.45 ServerAPI=1.45 base: https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-5960/1/artifact/yetus-general-check/output/Dockerfile

GITHUB PR
https://github.com/apache/hbase/pull/5960

Optional Tests
dupname asflicense cc hbaseprotoc spotless prototool javac spotbugs hadoopcheck hbaseanti checkstyle compile

uname
Linux 4a23ee552ab6 5.4.0-174-generic #193-Ubuntu SMP Thu Mar 7 14:29:28 UTC 2024 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
branch-2 / 7869f7f7e8

Default Java
Eclipse Adoptium-11.0.17+8

spotless
https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-5960/1/artifact/yetus-general-check/output/patch-spotless.txt

Max. process+thread count
80 (vs. ulimit of 30000)

modules
C: hbase-protocol-shaded hbase-server U: .

Console output
https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-5960/1/console

versions
git=2.34.1 maven=3.8.6 spotbugs=4.7.3

Powered by
Apache Yetus 0.12.0 https://yetus.apache.org

This message was automatically generated.

@Umeshkumar9414 you will have to run spotless:apply

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Comment

+0 :ok:
reexec
2m 46s
Docker mode activated.

-0 :warning:
yetus
0m  4s
Unprocessed flag(s): --brief-report-file --spotbugs-strict-precheck --whitespace-eol-ignore-list --whitespace-tabs-ignore-list --quick-hadoopcheck

_ Prechecks _

_ branch-2 Compile Tests _

+0 :ok:
mvndep
0m 12s
Maven dependency ordering for branch

+1 :green_heart:
mvninstall
2m 35s
branch-2 passed

+1 :green_heart:
compile
1m  2s
branch-2 passed

+1 :green_heart:
shadedjars
5m  8s
branch has no errors when building our shaded downstream artifacts.

+1 :green_heart:
javadoc
0m 32s
branch-2 passed

_ Patch Compile Tests _

+0 :ok:
mvndep
0m 12s
Maven dependency ordering for patch

+1 :green_heart:
mvninstall
2m 15s
the patch passed

+1 :green_heart:
compile
1m  0s
the patch passed

+1 :green_heart:
javac
1m  0s
the patch passed

+1 :green_heart:
shadedjars
5m  6s
patch has no errors when building our shaded downstream artifacts.

+1 :green_heart:
javadoc
0m 30s
the patch passed

_ Other Tests _

+1 :green_heart:
unit
0m 23s
hbase-protocol-shaded in the patch passed.

-1 :x:
unit
213m 16s
hbase-server in the patch failed.

239m 54s

Subsystem
Report/Notes

Docker
ClientAPI=1.43 ServerAPI=1.43 base: https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-5960/1/artifact/yetus-jdk8-hadoop2-check/output/Dockerfile

GITHUB PR
https://github.com/apache/hbase/pull/5960

Optional Tests
unit javac javadoc shadedjars compile

uname
Linux 497e0d16a344 5.4.0-1103-aws #111~18.04.1-Ubuntu SMP Tue May 23 20:04:10 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
branch-2 / 7869f7f7e8

Default Java
Temurin-1.8.0_352-b08

unit
https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-5960/1/artifact/yetus-jdk8-hadoop2-check/output/patch-unit-hbase-server.txt

Test Results
https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-5960/1/testReport/

Max. process+thread count
4279 (vs. ulimit of 30000)

modules
C: hbase-protocol-shaded hbase-server U: .

Console output
https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-5960/1/console

versions
git=2.34.1 maven=3.8.6

Powered by
Apache Yetus 0.12.0 https://yetus.apache.org

This message was automatically generated.

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Comment

+0 :ok:
reexec
0m 50s
Docker mode activated.

-0 :warning:
yetus
0m  5s
Unprocessed flag(s): --brief-report-file --spotbugs-strict-precheck --whitespace-eol-ignore-list --whitespace-tabs-ignore-list --quick-hadoopcheck

_ Prechecks _

_ branch-2 Compile Tests _

+0 :ok:
mvndep
0m 12s
Maven dependency ordering for branch

+1 :green_heart:
mvninstall
3m 49s
branch-2 passed

+1 :green_heart:
compile
1m 40s
branch-2 passed

+1 :green_heart:
shadedjars
7m  0s
branch has no errors when building our shaded downstream artifacts.

+1 :green_heart:
javadoc
0m 38s
branch-2 passed

_ Patch Compile Tests _

+0 :ok:
mvndep
0m 16s
Maven dependency ordering for patch

+1 :green_heart:
mvninstall
3m 24s
the patch passed

+1 :green_heart:
compile
1m 46s
the patch passed

+1 :green_heart:
javac
1m 46s
the patch passed

+1 :green_heart:
shadedjars
7m 11s
patch has no errors when building our shaded downstream artifacts.

+1 :green_heart:
javadoc
0m 48s
the patch passed

_ Other Tests _

+1 :green_heart:
unit
0m 44s
hbase-protocol-shaded in the patch passed.

+1 :green_heart:
unit
257m 47s
hbase-server in the patch passed.

291m  4s

Subsystem
Report/Notes

Docker
ClientAPI=1.45 ServerAPI=1.45 base: https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-5960/1/artifact/yetus-jdk11-hadoop3-check/output/Dockerfile

GITHUB PR
https://github.com/apache/hbase/pull/5960

Optional Tests
unit javac javadoc shadedjars compile

uname
Linux cd14a4c6cd66 5.4.0-174-generic #193-Ubuntu SMP Thu Mar 7 14:29:28 UTC 2024 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
branch-2 / 7869f7f7e8

Default Java
Eclipse Adoptium-11.0.17+8

Test Results
https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-5960/1/testReport/

Max. process+thread count
4595 (vs. ulimit of 30000)

modules
C: hbase-protocol-shaded hbase-server U: .

Console output
https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-5960/1/console

versions
git=2.34.1 maven=3.8.6

Powered by
Apache Yetus 0.12.0 https://yetus.apache.org

This message was automatically generated.

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Comment

+0 :ok:
reexec
0m 52s
Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  1s
No case conflicting files found.

+0 :ok:
prototool
0m  1s
prototool was not available.

+1 :green_heart:
hbaseanti
0m  0s
Patch does not have any anti-patterns.

+1 :green_heart:
@author
0m  0s
The patch does not contain any @author tags.

_ branch-2 Compile Tests _

+0 :ok:
mvndep
0m 13s
Maven dependency ordering for branch

+1 :green_heart:
mvninstall
2m 45s
branch-2 passed

+1 :green_heart:
compile
3m 13s
branch-2 passed

+1 :green_heart:
checkstyle
0m 46s
branch-2 passed

+1 :green_heart:
spotless
0m 43s
branch has no errors when running spotless:check.

+1 :green_heart:
spotbugs
3m 15s
branch-2 passed

_ Patch Compile Tests _

+0 :ok:
mvndep
0m 12s
Maven dependency ordering for patch

+1 :green_heart:
mvninstall
2m 42s
the patch passed

+1 :green_heart:
compile
3m 21s
the patch passed

+1 :green_heart:
cc
3m 21s
the patch passed

+1 :green_heart:
javac
3m 21s
the patch passed

+1 :green_heart:
checkstyle
0m 45s
the patch passed

+1 :green_heart:
whitespace
0m  0s
The patch has no whitespace issues.

+1 :green_heart:
hadoopcheck
9m 13s
Patch does not cause any errors with Hadoop 2.10.2 or 3.3.6.

+1 :green_heart:
hbaseprotoc
1m  6s
the patch passed

+1 :green_heart:
spotless
0m 43s
patch has no errors when running spotless:check.

+1 :green_heart:
spotbugs
3m 32s
the patch passed

_ Other Tests _

+1 :green_heart:
asflicense
0m 20s
The patch does not generate ASF License warnings.

35m 34s

Subsystem
Report/Notes

Docker
ClientAPI=1.45 ServerAPI=1.45 base: https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-5960/2/artifact/yetus-general-check/output/Dockerfile

GITHUB PR
https://github.com/apache/hbase/pull/5960

Optional Tests
dupname asflicense cc hbaseprotoc spotless prototool javac spotbugs hadoopcheck hbaseanti checkstyle compile

uname
Linux e2e433918fd8 5.4.0-174-generic #193-Ubuntu SMP Thu Mar 7 14:29:28 UTC 2024 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
branch-2 / 700b5a46ee

Default Java
Eclipse Adoptium-11.0.17+8

Max. process+thread count
81 (vs. ulimit of 30000)

modules
C: hbase-protocol-shaded hbase-server U: .

Console output
https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-5960/2/console

versions
git=2.34.1 maven=3.8.6 spotbugs=4.7.3

Powered by
Apache Yetus 0.12.0 https://yetus.apache.org

This message was automatically generated.

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Comment

+0 :ok:
reexec
0m 40s
Docker mode activated.

-0 :warning:
yetus
0m  5s
Unprocessed flag(s): --brief-report-file --spotbugs-strict-precheck --whitespace-eol-ignore-list --whitespace-tabs-ignore-list --quick-hadoopcheck

_ Prechecks _

_ branch-2 Compile Tests _

+0 :ok:
mvndep
0m 11s
Maven dependency ordering for branch

+1 :green_heart:
mvninstall
2m 59s
branch-2 passed

+1 :green_heart:
compile
1m 26s
branch-2 passed

+1 :green_heart:
shadedjars
5m 24s
branch has no errors when building our shaded downstream artifacts.

+1 :green_heart:
javadoc
0m 38s
branch-2 passed

_ Patch Compile Tests _

+0 :ok:
mvndep
0m 19s
Maven dependency ordering for patch

+1 :green_heart:
mvninstall
2m 53s
the patch passed

+1 :green_heart:
compile
1m 23s
the patch passed

+1 :green_heart:
javac
1m 23s
the patch passed

+1 :green_heart:
shadedjars
5m 24s
patch has no errors when building our shaded downstream artifacts.

+1 :green_heart:
javadoc
0m 37s
the patch passed

_ Other Tests _

+1 :green_heart:
unit
0m 36s
hbase-protocol-shaded in the patch passed.

+1 :green_heart:
unit
243m 14s
hbase-server in the patch passed.

270m 47s

Subsystem
Report/Notes

Docker
ClientAPI=1.45 ServerAPI=1.45 base: https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-5960/2/artifact/yetus-jdk11-hadoop3-check/output/Dockerfile

GITHUB PR
https://github.com/apache/hbase/pull/5960

Optional Tests
unit javac javadoc shadedjars compile

uname
Linux 6c73cd899d78 5.4.0-174-generic #193-Ubuntu SMP Thu Mar 7 14:29:28 UTC 2024 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
branch-2 / 700b5a46ee

Default Java
Eclipse Adoptium-11.0.17+8

Test Results
https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-5960/2/testReport/

Max. process+thread count
4586 (vs. ulimit of 30000)

modules
C: hbase-protocol-shaded hbase-server U: .

Console output
https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-5960/2/console

versions
git=2.34.1 maven=3.8.6

Powered by
Apache Yetus 0.12.0 https://yetus.apache.org

This message was automatically generated.

It's nice to see all the tests passed here as well. It gave me a hard time in the master branch. @virajjasani , @Apache9  please approve and merge.


fix: fix zip command for asset release

:tada: This PR is included in version 1.1.0-dev.12 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:

:tada: This PR is included in version 1.1.0-dev.3 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


Python Executable not found

Hi there,
I am using jekyll-relative-url-check-html and jekyll-relative-url-check-markdown hooks on Linux without any issues.
But when running pre-commit on Windows, the python exe is not found in jekyll-relative-url-check-markdown (jekyll-relative-url-check-html seems to work fine).
(envwin) PS C:\Repos\testrepo> pre-commit run --all-files
Jekyll Relative URL HTML.............................(no files to check)Skipped
Jekyll Relative URL Markdown.............................................Failed
- hook id: jekyll-relative-url-check-markdown
- exit code: 1

Executable `C:Users<user>.cachepre-commitreporc87owgcpy_env-python3.11Scriptspython.EXE` not found

(envwin) PS C:\Repos\testrepo>

(I replaced the User name by  in the example above)
Thanks for support/help.

Thanks for the report! As a first step, could you try to pip3 install the package and then check if you can use it from the command line? This would help to figure out if this is a problem with the pre-commit config, or of the python packaging.

Thanks or the quick respond.
I tried the "test it" lines from README.md and it seems like there is the same issue:
PS C:\Repos\testrepo> pre-commit try-repo https://github.com/klieret/jekyll-relative-url-check jekyll-relative-url-check-html --verbose --all-files
===============================================================================
Using config:
===============================================================================
repos:
-   repo: https://github.com/klieret/jekyll-relative-url-check
    rev: c9fbb1d965eeb57277df6a26ebfb4524b998d701
    hooks:
    -   id: jekyll-relative-url-check-html
===============================================================================
[INFO] Initializing environment for https://github.com/klieret/jekyll-relative-url-check.
[INFO] Installing environment for https://github.com/klieret/jekyll-relative-url-check.
[INFO] Once installed this environment will be reused.
[INFO] This may take a few minutes...
Jekyll Relative URL HTML.............................(no files to check)Skipped
- hook id: jekyll-relative-url-check-html

PS C:\Repos\testrepo> pre-commit try-repo https://github.com/klieret/jekyll-relative-url-check jekyll-relative-url-check-markdown --verbose --all-files
===============================================================================
Using config:
===============================================================================
repos:
-   repo: https://github.com/klieret/jekyll-relative-url-check
    rev: c9fbb1d965eeb57277df6a26ebfb4524b998d701
    hooks:
    -   id: jekyll-relative-url-check-markdown
===============================================================================
[INFO] Initializing environment for https://github.com/klieret/jekyll-relative-url-check.
[INFO] Installing environment for https://github.com/klieret/jekyll-relative-url-check.
[INFO] Once installed this environment will be reused.
[INFO] This may take a few minutes...
Jekyll Relative URL Markdown.............................................Failed
- hook id: jekyll-relative-url-check-markdown
- duration: 0.01s
- exit code: 1

Executable `C:UserskastAppDataLocalTemptmpjtstlma2repozkdwg_rxpy_env-python3.11Scriptspython.EXE` not found

I am using Python 3.10.12 on Windows 10.

OK after some googling I found this: https://stackoverflow.com/questions/73136027/executable-scriptspython-exe-not-found-for-pre-commit-lose-slashes
This seems to describe the problem you're facing right?
It seems like this is on me to fix, then :)

Hi, right it looks like this is the problem.

Can you run pre-commit autoupdate and try again?

Good work, bug is fixed 👍


fix: TabBar with scrollEnable to take into consideration the content margins

If you want to use a custom TabBar like
<TabBar
      {...tabBarProps}
      scrollEnabled={true}
      contentContainerStyle={{marginLeft: 14}}
/>

currently, the last tab will be cut with 14px, as it does not take into consideration these kind of spacing.
This PR fixes that.
Motivation
The last tab item is cut with with the amount you put as padding / margin to the contentContainer.
Test plan
Let me know if you need any screenshots, but should be straitforward

Closing this as stale


python precision handling

how did you handling precision of python?
i use round()

I think you are right.

There are many ways to do that. You can do it using format(). But round() is the most convenient.