What am I missing?

Must be something obvious. Trying to use Tinymce on non-admin page forms.
Did the setup type steps. I don't see any JS or such being installed. So fine, downloaded my own tinymce.js. Include it in path. Init doesn't seem to be called.
At the point of downloading my only tinymce.js and calling init myself, what is the plugin doing for me?
I also noticed that  {{ form.media }} has no output, so perhaps that  is part of the problem?
On Django 1.11...
What am I missing?

To tell what is wrong I need to see your code. Also I have no idea why you don't see any JS files because django-tinymce4-lite package contains a number of JS files that comprise TinyMCE editor. Naturally, you need to set up serving static files in your project.
Regarding {{ form.media }}, you need to have form variable in your template context that holds a Django Form object. It is automatically added by CRUD-oriented Django CBVs but if you define your view manually, you need to use a respective context variable name.
See test_tinymce project for an example of using TinyMCE widget on a non-admin page.

@romanvm So it should just pick up static files during collect static? I am using Pipeline with a bit of a fancy setup, so I am guessing it is somehow missing the static files from this. It fails to find the static files in both this, or the django-tinymce4 that you forked from (so not a this repo problem). But most other apps I install work fine. Maybe there is some hidden default that is making things fail with pipeline, hummm

I'm not familiar with Django-Pipeline so I cannot tell anything about it. But generally you need to run collectstatic to collect static files from all apps, both yours and third-party.
As for forms, if your forms use the same set of js/css files, you need to add links to those files only once. Just use a correct form name from your template context, e.g. {{ foo_form_1.media }}.

Since there is no follow-up, I'm closing this issue.


fix(SDK): replace call to SteamVR_Util.Event as no longer in 1.2.0

The SteamVR Plugin has been updated to version 1.2.0 and the method
SteamVR_Util.Event is no longer present and has not been deprecated
which causes errors to be thrown in VRTK as this method was used within
the SteamVR Controller SDK.
This fix updates the code to use the SteamVR_Events.SystemAction to
process the logic.
However, this method is not backward compatible with the SteamVR 1.1.0
plugin. To resolve this, the old code has been left in and wrapped in
a custom scripting define symbol of STEAMVR_1_1_0_OR_OLDER and if
a developer is still using an older version of the SteamVR plugin
such as 1.1.0 or earlier then they will need to add this custom
scripting define symbol in the Edit -> Project Settings -> Player
menu within the Scripting Define Symbol text box.

Superseded by https://github.com/thestonefox/VRTK/pull/813


Regenerate xdr

This extends #4 with regeneration of the XDR and an update to all the code that uses it to the changes that have occurred upstream (primarily "Currency" => "Asset"). It also used a local fork of xdrgen as provided in stellar/xdrgen#11 to get around activerecord's clever "classify" inflector thingy.

:+1:   Thanks so much for doing this! :)


feat(Forms): add highlightAutofill functionality

FX-3780
Description
This is a follow-up to https://github.com/toptal/picasso/pull/3439. In this PR we introduce highlightAutofill on final-form level. Users can enable this feature in form config.
How to test

check the new example in storybook

Screenshots

Development checks

[x] Add changeset according to guidelines (if needed)
[x] Read CONTRIBUTING.md and Component API principles
[x] Make sure that additions and changes on design follow Toptal's BASE design, and it's been already discussed with designers at #-base-core
[x] Annotate all props in component with documentation
[x] Create examples for component
[x] Ensure that deployed demo has expected results and good examples
[x] Ensure the changed/created components have not caused accessibility issues. How to use accessibility plugin in storybook.
[x] Self reviewed
[x] Covered with tests

Breaking change

N/A codemod is created and showcased in the changeset
N/A test alpha package of Picasso in StaffPortal

All development checks should be done and set checked to pass the
GitHub Bot: TODOLess action

PR commands

List of available commands:

@toptal-bot run package:alpha-release - Release alpha version
@toptal-anvil ping reviewers - Ping FX team for review

PR Review Guidelines

When to approve? ✅
You are OK with merging this PR and

You have no extra requests.
You have optional requests.

Add nit: to your comment. (ex. nit: I'd rename this variable from makeCircle to getCircle)

When to request changes? ❌
You are not OK with merging this PR because

Something is broken after the changes.
Acceptance criteria is not reached.
Code is dirty.

When to comment (neither ✅ nor ❌)
You want your comments to be addressed before merging this PR in cases like:

There are leftovers like unnecessary logs, comments, etc.
You have an opinionated comment regarding the code that requires a discussion.
You have questions.

How to handle the comments?

An owner of a comment is the only one who can resolve it.
An owner of a comment must resolve it when it's addressed.
A PR owner must reply with ✅ when a comment is addressed.

@toptal-anvil ping reviewers


Filtering by charts

IS there a way of enhancing functionality of the app through connecting the chart to the map by allowing features to be filtered through chart click?

This is probably possible but not something I plan on implementing any time soon. This project needs a thorough update to upgrade to the latest Leaflet/Bootstrap versions and I'd probably replace the C3 charts with a more actively developed charting library. I don't currently have the time to devote to this at the moment, but maintainers and PR's are always welcome!


Strange error message from LND Channel Backup Recovery

After SSD failure I set up new raspiblitz and started emergency recovery by seed and scb (file from RTL channel backup, renamed to "channel.backup"). ONCHAIN funds are recovered so far but "Lightning Progress: recoverscan" finished with a strange message:

*** channel.backup Recovery ***
Running ... (please wait)
FAIL # SOMETHING WENT WRONG:
[lncli] unable to restore chan backups: rpc error: code = Unknown desc = unable to unpack chan backup: chacha20poly1305: message                    authentication failed
--> ERROR BACKGROUND:
The WORD SEED is not matching the channel.backup file.
Either there was an error in the word seed list or
or the channel.backup file is from another RaspiBlitz.
#################
To try upload of channel.backup again:
MAINMENU > REPAIR > REPAIR-LND > RETRYSCB
Press ENTER to continue for now ...
I feel confused: The WORD SEED should be correct or the ONCHAIN funds couldn't be recovered. The "channel.backup" file is of course from another Raspiblitz- from the failed one.
If I try to upload the channel.backup and RETRYSCB again, the error will appear again.
Thanks for investigating.

*** SOLVED ***
I restored channel backup directly in the RTL software and it worked. Conclusion: The RTL channel backup won't work with Raspiblitz' "Restore SCB" function.


[BEAM-7181] Unskip a passing test on Python 3.

Thank you for your contribution! Follow this checklist to help us incorporate your contribution quickly and easily:

[ ] Choose reviewer(s) and mention them in a comment (R: @username).
[ ] Format the pull request title like [BEAM-XXX] Fixes bug in ApproximateQuantiles, where you replace BEAM-XXX with the appropriate JIRA issue, if applicable. This will automatically link the pull request to the issue.
[ ] If this contribution is large, please file an Apache Individual Contributor License Agreement.

Run Python PostCommit

Run Python PostCommit

this looks fine to me. Thanks Valentyn!

Run Python_PVR_Flink PreCommit


added CODEOWNERS

We should probably also add everyone to package.json contributors instead of just me as author


Second select is opening from two clicks

Bug report:
It is not possible to select second dropdown using mouse from one click if first dropdown is opened. This also apply to other components like dropdown, autocomplete.
What is the expected behavior?
Each component should be selectable with one mouse click.
What is the current behavior?
It requires two mouse clicks to open second select if value was not selected in the first dropdown.
What are the steps to reproduce?

Go to https://material.angular.io/components/select/overview.
Open first select.
While it is opened click on second select.
Second select is not opened because click event will be applied to invisible overlay to close first select.
Click again on second select, now second select is opened.

Which versions of Angular, Material, OS, TypeScript, browsers are affected?
All versions, can be reproduced in demo page.
Is there anything else we should know?
Adding overlay is good approach, I'm also using it in https://github.com/ng-select/ng-select. It allows to get rid of global document click event listener in each select, but in this case it can be quite annoying for users.

Closing as a duplicate of https://github.com/angular/material2/issues/9320.


add cloud sql instances

Add Cloud SQL instance module
Add Cloud Instance deployment

Ran Plan for dir: deployment/cloud workspace: default
Show Output
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:

  # module.cloudsql.google_sql_database_instance.instance will be created
+ resource "google_sql_database_instance" "instance" {
      + available_maintenance_versions = (known after apply)
      + connection_name                = (known after apply)
      + database_version               = "POSTGRES_15"
      + deletion_protection            = false
      + dns_name                       = (known after apply)
      + encryption_key_name            = (known after apply)
      + first_ip_address               = (known after apply)
      + id                             = (known after apply)
      + instance_type                  = (known after apply)
      + ip_address                     = (known after apply)
      + maintenance_version            = (known after apply)
      + master_instance_name           = (known after apply)
      + name                           = "fta-mstr-cloudsql-main"
      + private_ip_address             = (known after apply)
      + project                        = "fta-platform"
      + psc_service_attachment_link    = (known after apply)
      + public_ip_address              = (known after apply)
      + region                         = "asia-southeast2"
      + self_link                      = (known after apply)
      + server_ca_cert                 = (sensitive value)
      + service_account_email_address  = (known after apply)

      + replica_configuration (known after apply)

      + settings {
          + activation_policy     = "ALWAYS"
          + availability_type     = "ZONAL"
          + connector_enforcement = (known after apply)
          + disk_autoresize       = true
          + disk_autoresize_limit = 0
          + disk_size             = 10
          + disk_type             = "PD_SSD"
          + edition               = "ENTERPRISE"
          + pricing_plan          = "PER_USE"
          + tier                  = "db-f1-micro"
          + user_labels           = (known after apply)
          + version               = (known after apply)

          + backup_configuration {
              + enabled                        = true
              + location                       = "asia-southeast2"
              + point_in_time_recovery_enabled = true
              + start_time                     = "03:00"
              + transaction_log_retention_days = (known after apply)

              + backup_retention_settings (known after apply)
            }

          + insights_config (known after apply)

          + ip_configuration {
              + ipv4_enabled    = false
              + private_network = "https://www.googleapis.com/compute/v1/projects/fta-platform/global/networks/fta-mstr-vpc-main"
              + server_ca_mode  = (known after apply)
              + ssl_mode        = "ALLOW_UNENCRYPTED_AND_ENCRYPTED"
            }

          + location_preference (known after apply)

          + maintenance_window {
              + day          = 7
              + hour         = 3
              + update_track = "stable"
            }
        }
    }

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

:arrow_forward: To apply this plan, comment:atlantis apply -d deployment/cloud

:put_litter_in_its_place: To delete this plan and lock, click here
:repeat: To plan this project again, comment:atlantis plan -d deployment/cloud

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

:fast_forward: To apply all unapplied plans from this Pull Request, comment:atlantis apply

:put_litter_in_its_place: To delete all plans and locks from this Pull Request, comment:atlantis unlock

Ran Plan for dir: deployment/cloud workspace: default
Plan Error
Show Output
running "/usr/bin/terraform plan -input=false -refresh -out \"/home/atlantis/.atlantis/repos/greyhats13/fta_iac/11/default/deployment/cloud/default.tfplan\"" in "/home/atlantis/.atlantis/repos/greyhats13/fta_iac/11/default/deployment/cloud": exit status 1
╷
│ Error: Error acquiring the state lock
│
│ Error message: writing
│ "gs://fta-mstr-gcs-tfstate/fta/cloud/deployment/default.tflock" failed:
│ googleapi: Error 412: At least one of the pre-conditions you specified did
│ not hold., conditionNotMet
│ Lock Info:
│   ID:<PHONE_NUMBER>160883
│   Path:      gs://fta-mstr-gcs-tfstate/fta/cloud/deployment/default.tflock
│   Operation: OperationTypeApply
│   Who<EMAIL_ADDRESS>│   Version:   1.7.5
│   Created:   2024-09-18 10:00:25.026228 +0000 UTC
│   Info:
│
│
│ Terraform acquires a state lock to protect the state from being written
│ by multiple users at the same time. Please resolve the issue above and try
│ again. For most commands, you can disable locking with the "-lock=false"
│ flag, but this is not recommended.
╵

atlantis plan

Ran Plan for dir: deployment/cloud workspace: default
Show Output
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:

  # module.cloudsql_main.google_sql_database_instance.instance will be created
+ resource "google_sql_database_instance" "instance" {
      + available_maintenance_versions = (known after apply)
      + connection_name                = (known after apply)
      + database_version               = "POSTGRES_15"
      + deletion_protection            = false
      + dns_name                       = (known after apply)
      + encryption_key_name            = (known after apply)
      + first_ip_address               = (known after apply)
      + id                             = (known after apply)
      + instance_type                  = (known after apply)
      + ip_address                     = (known after apply)
      + maintenance_version            = (known after apply)
      + master_instance_name           = (known after apply)
      + name                           = "fta-mstr-cloudsql-main"
      + private_ip_address             = (known after apply)
      + project                        = "fta-platform"
      + psc_service_attachment_link    = (known after apply)
      + public_ip_address              = (known after apply)
      + region                         = "asia-southeast2"
      + self_link                      = (known after apply)
      + server_ca_cert                 = (sensitive value)
      + service_account_email_address  = (known after apply)

      + replica_configuration (known after apply)

      + settings {
          + activation_policy     = "ALWAYS"
          + availability_type     = "ZONAL"
          + connector_enforcement = (known after apply)
          + disk_autoresize       = true
          + disk_autoresize_limit = 0
          + disk_size             = 10
          + disk_type             = "PD_SSD"
          + edition               = "ENTERPRISE"
          + pricing_plan          = "PER_USE"
          + tier                  = "db-f1-micro"
          + user_labels           = (known after apply)
          + version               = (known after apply)

          + backup_configuration {
              + enabled                        = true
              + location                       = "asia-southeast2"
              + point_in_time_recovery_enabled = true
              + start_time                     = "03:00"
              + transaction_log_retention_days = (known after apply)

              + backup_retention_settings (known after apply)
            }

          + insights_config (known after apply)

          + ip_configuration {
              + ipv4_enabled    = false
              + private_network = "https://www.googleapis.com/compute/v1/projects/fta-platform/global/networks/fta-mstr-vpc-main"
              + server_ca_mode  = (known after apply)
              + ssl_mode        = "ALLOW_UNENCRYPTED_AND_ENCRYPTED"
            }

          + location_preference (known after apply)

          + maintenance_window {
              + day          = 7
              + hour         = 3
              + update_track = "stable"
            }
        }
    }

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

:arrow_forward: To apply this plan, comment:atlantis apply -d deployment/cloud

:put_litter_in_its_place: To delete this plan and lock, click here
:repeat: To plan this project again, comment:atlantis plan -d deployment/cloud

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

:fast_forward: To apply all unapplied plans from this Pull Request, comment:atlantis apply

:put_litter_in_its_place: To delete all plans and locks from this Pull Request, comment:atlantis unlock

Ran Plan for dir: deployment/cloud workspace: default
Plan Error
Show Output
running "/usr/bin/terraform plan -input=false -refresh -out \"/home/atlantis/.atlantis/repos/greyhats13/fta_iac/11/default/deployment/cloud/default.tfplan\"" in "/home/atlantis/.atlantis/repos/greyhats13/fta_iac/11/default/deployment/cloud": exit status 1
╷
│ Error: Reference to undeclared module
│
│   on outputs.tf line 164, in output "cloudsql_instance_name":
│  164:   value = module.cloudsql_instance.instance_name
│
│ No module call named "cloudsql_instance" is declared in the root module.
╵
╷
│ Error: Reference to undeclared module
│
│   on outputs.tf line 168, in output "cloudsql_instance_connection_name":
│  168:   value = module.cloudsql_instance.instance_connection_name
│
│ No module call named "cloudsql_instance" is declared in the root module.
╵
╷
│ Error: Reference to undeclared module
│
│   on outputs.tf line 172, in output "cloudsql_instance_self_link":
│  172:   value = module.cloudsql_instance.instance_self_link
│
│ No module call named "cloudsql_instance" is declared in the root module.
╵

Ran Plan for dir: deployment/cloud workspace: default
Plan Error
Show Output
running "/usr/bin/terraform plan -input=false -refresh -out \"/home/atlantis/.atlantis/repos/greyhats13/fta_iac/11/default/deployment/cloud/default.tfplan\"" in "/home/atlantis/.atlantis/repos/greyhats13/fta_iac/11/default/deployment/cloud": exit status 1
╷
│ Error: Reference to undeclared module
│
│   on outputs.tf line 164, in output "cloudsql_instance_name":
│  164:   value = module.cloudsql_instance_main.instance_name
│
│ No module call named "cloudsql_instance_main" is declared in the root
│ module.
╵
╷
│ Error: Reference to undeclared module
│
│   on outputs.tf line 168, in output "cloudsql_instance_connection_name":
│  168:   value = module.cloudsql_instance_main.instance_connection_name
│
│ No module call named "cloudsql_instance_main" is declared in the root
│ module.
╵
╷
│ Error: Reference to undeclared module
│
│   on outputs.tf line 172, in output "cloudsql_instance_self_link":
│  172:   value = module.cloudsql_instance_main.instance_self_link
│
│ No module call named "cloudsql_instance_main" is declared in the root
│ module.
╵

Ran Plan for dir: deployment/cloud workspace: default
Show Output
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:

  # module.cloudsql_instance_main.google_sql_database_instance.instance will be created
+ resource "google_sql_database_instance" "instance" {
      + available_maintenance_versions = (known after apply)
      + connection_name                = (known after apply)
      + database_version               = "POSTGRES_15"
      + deletion_protection            = false
      + dns_name                       = (known after apply)
      + encryption_key_name            = (known after apply)
      + first_ip_address               = (known after apply)
      + id                             = (known after apply)
      + instance_type                  = (known after apply)
      + ip_address                     = (known after apply)
      + maintenance_version            = (known after apply)
      + master_instance_name           = (known after apply)
      + name                           = "fta-mstr-cloudsql-main"
      + private_ip_address             = (known after apply)
      + project                        = "fta-platform"
      + psc_service_attachment_link    = (known after apply)
      + public_ip_address              = (known after apply)
      + region                         = "asia-southeast2"
      + self_link                      = (known after apply)
      + server_ca_cert                 = (sensitive value)
      + service_account_email_address  = (known after apply)

      + replica_configuration (known after apply)

      + settings {
          + activation_policy     = "ALWAYS"
          + availability_type     = "ZONAL"
          + connector_enforcement = (known after apply)
          + disk_autoresize       = true
          + disk_autoresize_limit = 0
          + disk_size             = 10
          + disk_type             = "PD_SSD"
          + edition               = "ENTERPRISE"
          + pricing_plan          = "PER_USE"
          + tier                  = "db-f1-micro"
          + user_labels           = (known after apply)
          + version               = (known after apply)

          + backup_configuration {
              + enabled                        = true
              + location                       = "asia-southeast2"
              + point_in_time_recovery_enabled = true
              + start_time                     = "03:00"
              + transaction_log_retention_days = (known after apply)

              + backup_retention_settings (known after apply)
            }

          + insights_config (known after apply)

          + ip_configuration {
              + ipv4_enabled    = false
              + private_network = "https://www.googleapis.com/compute/v1/projects/fta-platform/global/networks/fta-mstr-vpc-main"
              + server_ca_mode  = (known after apply)
              + ssl_mode        = "ALLOW_UNENCRYPTED_AND_ENCRYPTED"
            }

          + location_preference (known after apply)

          + maintenance_window {
              + day          = 7
              + hour         = 3
              + update_track = "stable"
            }
        }
    }

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

Changes to Outputs:
+ cloudsql_instance_connection_name  = (known after apply)
+ cloudsql_instance_name             = "fta-mstr-cloudsql-main"
+ cloudsql_instance_self_link        = (known after apply)

:arrow_forward: To apply this plan, comment:atlantis apply -d deployment/cloud

:put_litter_in_its_place: To delete this plan and lock, click here
:repeat: To plan this project again, comment:atlantis plan -d deployment/cloud

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

:fast_forward: To apply all unapplied plans from this Pull Request, comment:atlantis apply

:put_litter_in_its_place: To delete all plans and locks from this Pull Request, comment:atlantis unlock

atlantis apply

Ran Apply for dir: deployment/cloud workspace: default
Apply Error
running "/usr/bin/terraform apply -input=false \"/home/atlantis/.atlantis/repos/greyhats13/fta_iac/11/default/deployment/cloud/default.tfplan\"" in "/home/atlantis/.atlantis/repos/greyhats13/fta_iac/11/default/deployment/cloud": exit status 1
module.cloudsql_instance_main.google_sql_database_instance.instance: Creating...
╷
│ Error: Error, failed to create instance fta-mstr-cloudsql-main: googleapi: Error 400: Invalid request: Incorrect Service Networking config for instance: fta-platform:fta-mstr-cloudsql-main:SERVICE_NETWORKING_NOT_ENABLED., invalid
│
│   with module.cloudsql_instance_main.google_sql_database_instance.instance,
│   on ../../modules/gcp/cloudsql/cloudsql.tf line 2, in resource "google_sql_database_instance" "instance":
│    2: resource "google_sql_database_instance" "instance" {
│
╵

Ran Plan for dir: deployment/cloud workspace: default
Plan Error
Show Output
running "/usr/bin/terraform plan -input=false -refresh -out \"/home/atlantis/.atlantis/repos/greyhats13/fta_iac/11/default/deployment/cloud/default.tfplan\"" in "/home/atlantis/.atlantis/repos/greyhats13/fta_iac/11/default/deployment/cloud": exit status 1
╷
│ Error: Error acquiring the state lock
│
│ Error message: writing
│ "gs://fta-mstr-gcs-tfstate/fta/cloud/deployment/default.tflock" failed:
│ googleapi: Error 412: At least one of the pre-conditions you specified did
│ not hold., conditionNotMet
│ Lock Info:
│   ID:<PHONE_NUMBER>855161
│   Path:      gs://fta-mstr-gcs-tfstate/fta/cloud/deployment/default.tflock
│   Operation: OperationTypeApply
│   Who<EMAIL_ADDRESS>│   Version:   1.7.5
│   Created:   2024-09-18 11:59:23.704906 +0000 UTC
│   Info:
│
│
│ Terraform acquires a state lock to protect the state from being written
│ by multiple users at the same time. Please resolve the issue above and try
│ again. For most commands, you can disable locking with the "-lock=false"
│ flag, but this is not recommended.
╵

atlantis apply

Ran Apply for 0 projects:

atlantis plan

Ran Plan for dir: deployment/cloud workspace: default
Show Output
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:

  # module.cloudsql_instance_main.google_compute_global_address.private_service_ip will be created
+ resource "google_compute_global_address" "private_service_ip" {
      + address            = (known after apply)
      + address_type       = "INTERNAL"
      + creation_timestamp = (known after apply)
      + effective_labels   = {
          + "goog-terraform-provisioned" = "true"
        }
      + id                 = (known after apply)
      + label_fingerprint  = (known after apply)
      + name               = "fta-mstr-cloudsql-main-private-ip-address"
      + network            = "projects/fta-platform/global/networks/fta-mstr-vpc-main"
      + prefix_length      = 16
      + project            = "fta-platform"
      + purpose            = "VPC_PEERING"
      + self_link          = (known after apply)
      + terraform_labels   = {
          + "goog-terraform-provisioned" = "true"
        }
    }

  # module.cloudsql_instance_main.google_service_networking_connection.private_vpc_connection will be created
+ resource "google_service_networking_connection" "private_vpc_connection" {
      + id                      = (known after apply)
      + network                 = "projects/fta-platform/global/networks/fta-mstr-vpc-main"
      + peering                 = (known after apply)
      + reserved_peering_ranges = (known after apply)
      + service                 = "servicenetworking.googleapis.com"
    }

  # module.cloudsql_instance_main.google_sql_database_instance.instance will be created
+ resource "google_sql_database_instance" "instance" {
      + available_maintenance_versions = (known after apply)
      + connection_name                = (known after apply)
      + database_version               = "POSTGRES_15"
      + deletion_protection            = false
      + dns_name                       = (known after apply)
      + encryption_key_name            = (known after apply)
      + first_ip_address               = (known after apply)
      + id                             = (known after apply)
      + instance_type                  = (known after apply)
      + ip_address                     = (known after apply)
      + maintenance_version            = (known after apply)
      + master_instance_name           = (known after apply)
      + name                           = "fta-mstr-cloudsql-main"
      + private_ip_address             = (known after apply)
      + project                        = "fta-platform"
      + psc_service_attachment_link    = (known after apply)
      + public_ip_address              = (known after apply)
      + region                         = "asia-southeast2"
      + self_link                      = (known after apply)
      + server_ca_cert                 = (sensitive value)
      + service_account_email_address  = (known after apply)

      + replica_configuration (known after apply)

      + settings {
          + activation_policy     = "ALWAYS"
          + availability_type     = "ZONAL"
          + connector_enforcement = (known after apply)
          + disk_autoresize       = true
          + disk_autoresize_limit = 0
          + disk_size             = 10
          + disk_type             = "PD_SSD"
          + edition               = "ENTERPRISE"
          + pricing_plan          = "PER_USE"
          + tier                  = "db-f1-micro"
          + user_labels           = (known after apply)
          + version               = (known after apply)

          + backup_configuration {
              + enabled                        = true
              + location                       = "asia-southeast2"
              + point_in_time_recovery_enabled = true
              + start_time                     = "03:00"
              + transaction_log_retention_days = (known after apply)

              + backup_retention_settings (known after apply)
            }

          + insights_config (known after apply)

          + ip_configuration {
              + enable_private_path_for_google_cloud_services = true
              + ipv4_enabled                                  = false
              + private_network                               = "https://www.googleapis.com/compute/v1/projects/fta-platform/global/networks/fta-mstr-vpc-main"
              + server_ca_mode                                = (known after apply)
              + ssl_mode                                      = "ALLOW_UNENCRYPTED_AND_ENCRYPTED"
            }

          + location_preference (known after apply)

          + maintenance_window {
              + day          = 7
              + hour         = 3
              + update_track = "stable"
            }
        }
    }

  # module.gcp_project.google_project_service.project["service_networking"] will be created
+ resource "google_project_service" "project" {
      + disable_dependent_services = true
      + disable_on_destroy         = true
      + id                         = (known after apply)
      + project                    = "fta-platform"
      + service                    = "servicenetworking.googleapis.com"

      + timeouts {
          + create = "30m"
          + update = "40m"
        }
    }

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

Changes to Outputs:
+ cloudsql_instance_connection_name  = (known after apply)
+ cloudsql_instance_self_link        = (known after apply)

:arrow_forward: To apply this plan, comment:atlantis apply -d deployment/cloud

:put_litter_in_its_place: To delete this plan and lock, click here
:repeat: To plan this project again, comment:atlantis plan -d deployment/cloud

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

:fast_forward: To apply all unapplied plans from this Pull Request, comment:atlantis apply

:put_litter_in_its_place: To delete all plans and locks from this Pull Request, comment:atlantis unlock

atlantis apply

Ran Apply for dir: deployment/cloud workspace: default
Apply Error
Show Output
running "/usr/bin/terraform apply -input=false \"/home/atlantis/.atlantis/repos/greyhats13/fta_iac/11/default/deployment/cloud/default.tfplan\"" in "/home/atlantis/.atlantis/repos/greyhats13/fta_iac/11/default/deployment/cloud": exit status 1
module.gcp_project.google_project_service.project["service_networking"]: Creating...
module.gcp_project.google_project_service.project["service_networking"]: Still creating... [10s elapsed]
module.gcp_project.google_project_service.project["service_networking"]: Still creating... [20s elapsed]
module.gcp_project.google_project_service.project["service_networking"]: Creation complete after 24s [id=fta-platform/servicenetworking.googleapis.com]
module.cloudsql_instance_main.google_compute_global_address.private_service_ip: Creating...
module.cloudsql_instance_main.google_compute_global_address.private_service_ip: Still creating... [10s elapsed]
module.cloudsql_instance_main.google_compute_global_address.private_service_ip: Creation complete after 13s [id=projects/fta-platform/global/addresses/fta-mstr-cloudsql-main-private-ip-address]
module.cloudsql_instance_main.google_service_networking_connection.private_vpc_connection: Creating...
module.cloudsql_instance_main.google_service_networking_connection.private_vpc_connection: Still creating... [10s elapsed]
╷
│ Error: Error waiting for Create Service Networking Connection: Error code 9, message: Allocated IP range '<IP_ADDRESS>' not found in network.
│ Help Token: AaUeqG5cZu98J40DAN4ReKj_czMjGMnM9cnwCwU3MioCTMcCF0dL-G_yJxM-syiN3pVYBVMccEl8tFJaoqGyTK_SWB8NABD7N8hR2Ysiduvqsbo7
│
│   with module.cloudsql_instance_main.google_service_networking_connection.private_vpc_connection,
│   on ../../modules/gcp/cloudsql/cloudsql.tf line 13, in resource "google_service_networking_connection" "private_vpc_connection":
│   13: resource "google_service_networking_connection" "private_vpc_connection" {
│
╵

Ran Plan for dir: deployment/cloud workspace: default
Plan Error
Show Output
running "/usr/bin/terraform plan -input=false -refresh -out \"/home/atlantis/.atlantis/repos/greyhats13/fta_iac/11/default/deployment/cloud/default.tfplan\"" in "/home/atlantis/.atlantis/repos/greyhats13/fta_iac/11/default/deployment/cloud": exit status 1
╷
│ Error: Reference to undeclared module
│
│   on outputs.tf line 164, in output "cloudsql_instance_name":
│  164:   value = module.cloudsql_instance_main.instance_name
│
│ No module call named "cloudsql_instance_main" is declared in the root
│ module.
╵
╷
│ Error: Reference to undeclared module
│
│   on outputs.tf line 168, in output "cloudsql_instance_connection_name":
│  168:   value = module.cloudsql_instance_main.instance_connection_name
│
│ No module call named "cloudsql_instance_main" is declared in the root
│ module.
╵
╷
│ Error: Reference to undeclared module
│
│   on outputs.tf line 172, in output "cloudsql_instance_self_link":
│  172:   value = module.cloudsql_instance_main.instance_self_link
│
│ No module call named "cloudsql_instance_main" is declared in the root
│ module.
╵

Ran Plan for dir: deployment/cloud workspace: default
Show Output
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:

  # module.cloudsql_instance_main.google_compute_global_address.private_service_ip will be destroyed
  # (because google_compute_global_address.private_service_ip is not in configuration)
- resource "google_compute_global_address" "private_service_ip" {
      - address            = "<IP_ADDRESS>" -> null
      - address_type       = "INTERNAL" -> null
      - creation_timestamp = "2024-09-18T05:05:21.558-07:00" -> null
      - effective_labels   = {
          - "goog-terraform-provisioned" = "true"
        } -> null
      - id                 = "projects/fta-platform/global/addresses/fta-mstr-cloudsql-main-private-ip-address" -> null
      - label_fingerprint  = "vezUS-42LLM=" -> null
      - name               = "fta-mstr-cloudsql-main-private-ip-address" -> null
      - network            = "https://www.googleapis.com/compute/v1/projects/fta-platform/global/networks/fta-mstr-vpc-main" -> null
      - prefix_length      = 16 -> null
      - project            = "fta-platform" -> null
      - purpose            = "VPC_PEERING" -> null
      - self_link          = "https://www.googleapis.com/compute/v1/projects/fta-platform/global/addresses/fta-mstr-cloudsql-main-private-ip-address" -> null
      - terraform_labels   = {
          - "goog-terraform-provisioned" = "true"
        } -> null
        # (2 unchanged attributes hidden)
    }

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

Changes to Outputs:
- cloudsql_instance_name             = "fta-mstr-cloudsql-main" -> null

:arrow_forward: To apply this plan, comment:atlantis apply -d deployment/cloud

:put_litter_in_its_place: To delete this plan and lock, click here
:repeat: To plan this project again, comment:atlantis plan -d deployment/cloud

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

:fast_forward: To apply all unapplied plans from this Pull Request, comment:atlantis apply

:put_litter_in_its_place: To delete all plans and locks from this Pull Request, comment:atlantis unlock

atlantis apply

Ran Plan for dir: deployment/cloud workspace: default
Show Output
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:

  # module.cloudsql_instance_main.google_compute_global_address.private_service_ip will be created
+ resource "google_compute_global_address" "private_service_ip" {
      + address            = (known after apply)
      + address_type       = "INTERNAL"
      + creation_timestamp = (known after apply)
      + effective_labels   = {
          + "goog-terraform-provisioned" = "true"
        }
      + id                 = (known after apply)
      + label_fingerprint  = (known after apply)
      + name               = "fta-mstr-cloudsql-main-private-ip-address"
      + network            = "projects/fta-platform/global/networks/fta-mstr-vpc-main"
      + prefix_length      = 16
      + project            = "fta-platform"
      + purpose            = "VPC_PEERING"
      + self_link          = (known after apply)
      + terraform_labels   = {
          + "goog-terraform-provisioned" = "true"
        }
    }

  # module.cloudsql_instance_main.google_service_networking_connection.private_vpc_connection will be created
+ resource "google_service_networking_connection" "private_vpc_connection" {
      + id                      = (known after apply)
      + network                 = "projects/fta-platform/global/networks/fta-mstr-vpc-main"
      + peering                 = (known after apply)
      + reserved_peering_ranges = (known after apply)
      + service                 = "servicenetworking.googleapis.com"
    }

  # module.cloudsql_instance_main.google_sql_database_instance.instance will be created
+ resource "google_sql_database_instance" "instance" {
      + available_maintenance_versions = (known after apply)
      + connection_name                = (known after apply)
      + database_version               = "POSTGRES_15"
      + deletion_protection            = false
      + dns_name                       = (known after apply)
      + encryption_key_name            = (known after apply)
      + first_ip_address               = (known after apply)
      + id                             = (known after apply)
      + instance_type                  = (known after apply)
      + ip_address                     = (known after apply)
      + maintenance_version            = (known after apply)
      + master_instance_name           = (known after apply)
      + name                           = "fta-mstr-cloudsql-main"
      + private_ip_address             = (known after apply)
      + project                        = "fta-platform"
      + psc_service_attachment_link    = (known after apply)
      + public_ip_address              = (known after apply)
      + region                         = "asia-southeast2"
      + self_link                      = (known after apply)
      + server_ca_cert                 = (sensitive value)
      + service_account_email_address  = (known after apply)

      + replica_configuration (known after apply)

      + settings {
          + activation_policy     = "ALWAYS"
          + availability_type     = "ZONAL"
          + connector_enforcement = (known after apply)
          + disk_autoresize       = true
          + disk_autoresize_limit = 0
          + disk_size             = 10
          + disk_type             = "PD_SSD"
          + edition               = "ENTERPRISE"
          + pricing_plan          = "PER_USE"
          + tier                  = "db-f1-micro"
          + user_labels           = (known after apply)
          + version               = (known after apply)

          + backup_configuration {
              + enabled                        = true
              + location                       = "asia-southeast2"
              + point_in_time_recovery_enabled = true
              + start_time                     = "03:00"
              + transaction_log_retention_days = (known after apply)

              + backup_retention_settings (known after apply)
            }

          + insights_config (known after apply)

          + ip_configuration {
              + enable_private_path_for_google_cloud_services = true
              + ipv4_enabled                                  = false
              + private_network                               = "https://www.googleapis.com/compute/v1/projects/fta-platform/global/networks/fta-mstr-vpc-main"
              + server_ca_mode                                = (known after apply)
              + ssl_mode                                      = "ALLOW_UNENCRYPTED_AND_ENCRYPTED"
            }

          + location_preference (known after apply)

          + maintenance_window {
              + day          = 7
              + hour         = 3
              + update_track = "stable"
            }
        }
    }

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

:arrow_forward: To apply this plan, comment:atlantis apply -d deployment/cloud

:put_litter_in_its_place: To delete this plan and lock, click here
:repeat: To plan this project again, comment:atlantis plan -d deployment/cloud

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

:fast_forward: To apply all unapplied plans from this Pull Request, comment:atlantis apply

:put_litter_in_its_place: To delete all plans and locks from this Pull Request, comment:atlantis unlock

Ran Apply for dir: deployment/cloud workspace: default
Apply Error
Show Output
running "/usr/bin/terraform apply -input=false \"/home/atlantis/.atlantis/repos/greyhats13/fta_iac/11/default/deployment/cloud/default.tfplan\"" in "/home/atlantis/.atlantis/repos/greyhats13/fta_iac/11/default/deployment/cloud": exit status 1
module.cloudsql_instance_main.google_compute_global_address.private_service_ip: Creating...
module.cloudsql_instance_main.google_compute_global_address.private_service_ip: Still creating... [10s elapsed]
module.cloudsql_instance_main.google_compute_global_address.private_service_ip: Creation complete after 13s [id=projects/fta-platform/global/addresses/fta-mstr-cloudsql-main-private-ip-address]
module.cloudsql_instance_main.google_service_networking_connection.private_vpc_connection: Creating...
module.cloudsql_instance_main.google_service_networking_connection.private_vpc_connection: Still creating... [10s elapsed]
╷
│ Error: Error waiting for Create Service Networking Connection: Error code 9, message: Allocated IP range '<IP_ADDRESS>' not found in network.
│ Help Token: AaUeqG7f-KrAg5hL4pm02I5E__J30_3YwiiHQC2zOKuLCmZPrUQcY1232OH1dDlMQ24r54eKr0MokSUjMd1AbSVPf7jEYaxA_EkkBnPc5pptmQDj
│
│   with module.cloudsql_instance_main.google_service_networking_connection.private_vpc_connection,
│   on ../../modules/gcp/cloudsql/cloudsql.tf line 12, in resource "google_service_networking_connection" "private_vpc_connection":
│   12: resource "google_service_networking_connection" "private_vpc_connection" {
│
╵

Ran Plan for dir: deployment/cloud workspace: default
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.

:arrow_forward: To apply this plan, comment:atlantis apply -d deployment/cloud

:put_litter_in_its_place: To delete this plan and lock, click here
:repeat: To plan this project again, comment:atlantis plan -d deployment/cloud

:fast_forward: To apply all unapplied plans from this Pull Request, comment:atlantis apply

:put_litter_in_its_place: To delete all plans and locks from this Pull Request, comment:atlantis unlock

Ran Plan for dir: deployment/cloud workspace: default
Show Output
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:

  # module.cloudsql_instance_main.google_compute_global_address.private_ip_address will be created
+ resource "google_compute_global_address" "private_ip_address" {
      + address            = (known after apply)
      + address_type       = "INTERNAL"
      + creation_timestamp = (known after apply)
      + effective_labels   = {
          + "goog-terraform-provisioned" = "true"
        }
      + id                 = (known after apply)
      + label_fingerprint  = (known after apply)
      + name               = "fta-mstr-cloudsql-main-private-ip-address"
      + network            = "projects/fta-platform/global/networks/fta-mstr-vpc-main"
      + prefix_length      = 16
      + project            = "fta-platform"
      + purpose            = "VPC_PEERING"
      + self_link          = (known after apply)
      + terraform_labels   = {
          + "goog-terraform-provisioned" = "true"
        }
    }

  # module.cloudsql_instance_main.google_service_networking_connection.private_vpc_connection will be created
+ resource "google_service_networking_connection" "private_vpc_connection" {
      + id                      = (known after apply)
      + network                 = "projects/fta-platform/global/networks/fta-mstr-vpc-main"
      + peering                 = (known after apply)
      + reserved_peering_ranges = [
          + "fta-mstr-cloudsql-main-private-ip-address",
        ]
      + service                 = "servicenetworking.googleapis.com"
    }

  # module.cloudsql_instance_main.google_sql_database_instance.instance will be created
+ resource "google_sql_database_instance" "instance" {
      + available_maintenance_versions = (known after apply)
      + connection_name                = (known after apply)
      + database_version               = "POSTGRES_15"
      + deletion_protection            = false
      + dns_name                       = (known after apply)
      + encryption_key_name            = (known after apply)
      + first_ip_address               = (known after apply)
      + id                             = (known after apply)
      + instance_type                  = (known after apply)
      + ip_address                     = (known after apply)
      + maintenance_version            = (known after apply)
      + master_instance_name           = (known after apply)
      + name                           = "fta-mstr-cloudsql-main"
      + private_ip_address             = (known after apply)
      + project                        = "fta-platform"
      + psc_service_attachment_link    = (known after apply)
      + public_ip_address              = (known after apply)
      + region                         = "asia-southeast2"
      + self_link                      = (known after apply)
      + server_ca_cert                 = (sensitive value)
      + service_account_email_address  = (known after apply)

      + replica_configuration (known after apply)

      + settings {
          + activation_policy     = "ALWAYS"
          + availability_type     = "ZONAL"
          + connector_enforcement = (known after apply)
          + disk_autoresize       = true
          + disk_autoresize_limit = 0
          + disk_size             = 10
          + disk_type             = "PD_SSD"
          + edition               = "ENTERPRISE"
          + pricing_plan          = "PER_USE"
          + tier                  = "db-f1-micro"
          + user_labels           = (known after apply)
          + version               = (known after apply)

          + backup_configuration {
              + enabled                        = true
              + location                       = "asia-southeast2"
              + point_in_time_recovery_enabled = true
              + start_time                     = "03:00"
              + transaction_log_retention_days = (known after apply)

              + backup_retention_settings (known after apply)
            }

          + insights_config (known after apply)

          + ip_configuration {
              + enable_private_path_for_google_cloud_services = true
              + ipv4_enabled                                  = false
              + private_network                               = "https://www.googleapis.com/compute/v1/projects/fta-platform/global/networks/fta-mstr-vpc-main"
              + server_ca_mode                                = (known after apply)
              + ssl_mode                                      = "ALLOW_UNENCRYPTED_AND_ENCRYPTED"
            }

          + location_preference (known after apply)

          + maintenance_window {
              + day          = 7
              + hour         = 3
              + update_track = "stable"
            }
        }
    }

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

:arrow_forward: To apply this plan, comment:atlantis apply -d deployment/cloud

:put_litter_in_its_place: To delete this plan and lock, click here
:repeat: To plan this project again, comment:atlantis plan -d deployment/cloud

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

:fast_forward: To apply all unapplied plans from this Pull Request, comment:atlantis apply

:put_litter_in_its_place: To delete all plans and locks from this Pull Request, comment:atlantis unlock

Did you mean to use atlantis instead of atlatnis?

atllantis apply

atlantis apply

Ran Apply for 2 projects:

dir: deployment/cloud workspace: default
dir: deployment/service/fta_users workspace: default

1. dir: deployment/cloud workspace: default
Show Output
Apply complete! Resources: 0 added, 0 changed, 0 destroyed.

Outputs:

bucket_name = "fta-mstr-gcs-tfstate"
bucket_self_link = "https://www.googleapis.com/storage/v1/b/fta-mstr-gcs-tfstate"
bucket_url = "gs://fta-mstr-gcs-tfstate"
cloudsql_instance_connection_name = "fta-platform:asia-southeast2:fta-mstr-cloudsql-main"
cloudsql_instance_name = "fta-mstr-cloudsql-main"
cloudsql_instance_self_link = "https://sqladmin.googleapis.com/sql/v1beta4/projects/fta-platform/instances/fta-mstr-cloudsql-main"
gitops_repo_fullname = "greyhats13/fta_gitops"
gitops_repo_http_clone_url = "https://github.com/greyhats13/fta_gitops.git"
gitops_repo_ssh_clone_url = "git@github.com:greyhats13/fta_gitops.git"
gsm_iac_secret_data = <sensitive>
iac_repo_fullname = "greyhats13/fta_iac"
iac_repo_http_clone_url = "https://github.com/greyhats13/fta_iac.git"
iac_repo_ssh_clone_url = "git@github.com:greyhats13/fta_iac.git"
main_dns_id = "projects/fta-platform/managedZones/fta-mstr-dns-main"
main_dns_managed_zone_id =<PHONE_NUMBER>482091992
main_dns_name = "fta.blast.co.id."
main_dns_name_servers = tolist([
  "ns-cloud-b1.googledomains.com.",
  "ns-cloud-b2.googledomains.com.",
  "ns-cloud-b3.googledomains.com.",
  "ns-cloud-b4.googledomains.com.",
])
main_dns_zone_name = "fta-mstr-dns-main"
main_dns_zone_visibility = "public"
main_firewall_ids = {
  "icmp" = "projects/fta-platform/global/firewalls/fta-mstr-vpc-main-allow-icmp"
  "internal" = "projects/fta-platform/global/firewalls/fta-mstr-vpc-main-allow-internal"
  "rdp" = "projects/fta-platform/global/firewalls/fta-mstr-vpc-main-allow-rdp"
  "ssh" = "projects/fta-platform/global/firewalls/fta-mstr-vpc-main-allow-ssh"
}
main_firewall_self_links = {
  "icmp" = "https://www.googleapis.com/compute/v1/projects/fta-platform/global/firewalls/fta-mstr-vpc-main-allow-icmp"
  "internal" = "https://www.googleapis.com/compute/v1/projects/fta-platform/global/firewalls/fta-mstr-vpc-main-allow-internal"
  "rdp" = "https://www.googleapis.com/compute/v1/projects/fta-platform/global/firewalls/fta-mstr-vpc-main-allow-rdp"
  "ssh" = "https://www.googleapis.com/compute/v1/projects/fta-platform/global/firewalls/fta-mstr-vpc-main-allow-ssh"
}
main_nat_id = "fta-platform/asia-southeast2/fta-mstr-vpc-main-router/fta-mstr-vpc-main-nat"
main_pods_secondary_range_name = "pods-range"
main_router_id = "projects/fta-platform/regions/asia-southeast2/routers/fta-mstr-vpc-main-router"
main_router_self_link = "https://www.googleapis.com/compute/v1/projects/fta-platform/regions/asia-southeast2/routers/fta-mstr-vpc-main-router"
main_services_secondary_range_name = "services-range"
main_subnet_ip_cidr_range = "<IP_ADDRESS>/16"
main_subnet_self_link = "https://www.googleapis.com/compute/v1/projects/fta-platform/regions/asia-southeast2/subnetworks/fta-mstr-vpc-main-subnet"
main_vpc_gateway_ipv4 = ""
main_vpc_id = "projects/fta-platform/global/networks/fta-mstr-vpc-main"
main_vpc_self_link = "https://www.googleapis.com/compute/v1/projects/fta-platform/global/networks/fta-mstr-vpc-main"
security_cryptokey_id = "projects/fta-platform/locations/global/keyRings/fta-mstr-kms-main-keyring/cryptoKeys/fta-mstr-kms-main-cryptokey"
security_keyring_id = "projects/fta-platform/locations/global/keyRings/fta-mstr-kms-main-keyring"
security_service_account_email =<EMAIL_ADDRESS>security_service_account_id =<EMAIL_ADDRESS>

2. dir: deployment/service/fta_users workspace: default
Apply complete! Resources: 0 added, 0 changed, 0 destroyed.

Apply Summary
2 projects, 2 successful, 0 failed, 0 errored


List of tnetstrings implementations

Even if the implementations are easy, it would be nice to have an official list of available implementation for various languages. Probably also on http://tnetstrings.org/

Another!
https://bitbucket.org/mahlon/nim-tnetstring

nice
On Mon, Jun 1, 2015 at 8:28 AM, Mahlon E. Smith<EMAIL_ADDRESS>wrote:

Another!
https://bitbucket.org/mahlon/nim-tnetstring
—
Reply to this email directly or view it on GitHub
https://github.com/zedshaw/mongrel2/issues/80#issuecomment-107583901.

--
| Henry Finucane

"I hear aphorisms are popular"


specify which priority wins - ones with higher or lower number?

For https://github.com/tangrams/tangram-docs/blob/master/docs/Syntax-Reference/layers.md#priority it appears to not be specified.
For https://github.com/tangrams/tangram-docs/blob/master/docs/Syntax-Reference/draw.md#order it is not entirely clear but "In this case, higher-ordered layers will be drawn over lower-ordered layers." indicated that higher values win with lower ones in case of a conflict.
Issue triggered by https://github.com/westnordost/StreetComplete/pull/1930 where I am confused by order, priority and why noncollide markers collide.

Because 10 appears to win with 1 and 0 appears to win with 1 and 1 appears to win with 2.

Put simply: lower values win for priority (priority: 1 has precedence over priority: 2) and higher values win for order (order: 2 has precedence over order: 1). There are subtleties though, and the docs should probably clarify a bit more.

For https://github.com/tangrams/tangram-docs/blob/master/docs/Syntax-Reference/layers.md#priority it appears to not be specified.

There are two distinct parts of the scene configuration named priority. One is the property you linked above - this is a property on layers. When a feature matches multiple "sibling" layers, the layer priority determines the order in which the layers are applied.
The other priority is a property on drawn features like labels, and its behavior is described here: https://github.com/tangrams/tangram-docs/blob/master/docs/Syntax-Reference/draw.md#priority

For https://github.com/tangrams/tangram-docs/blob/master/docs/Syntax-Reference/draw.md#order it is not entirely clear but "In this case, higher-ordered layers will be drawn over lower-ordered layers." indicated that higher values win with lower ones in case of a conflict.

The documentation is worded this way because order only affects the drawing order of features that are at the same elevation. If you have a rooftop drawn at 5m elevation with order: 1 overlapping a road drawn at 0m elevation with order: 2, the rooftop will still be drawn on top. If you have two overlapping roads drawn at 0m elevation, the one with the higher order will be drawn on top.
Does this help? If these clarifications make sense I can add them to the documentation.

Does this help?

Yes! Though I am unsure how one may handle part about looking at wrong priority. Add "you may be looking for $LINK"?

Resolved by https://github.com/tangrams/tangram-docs/pull/271


New Helm v3 Template Processor

Is your feature request related to a problem? Please describe.

No.
Describe the solution you'd like

I would like a helm v3 template processor. The current eunomia helm template processor uses helm v2.
Describe alternatives you've considered

Creating a eunomia helm v3 template processor that is not part of the main eunomia repo.
What version of eunomia are you using?
kubectl exec $EUNOMIA_POD curl localhost:8383/metrics Output
$ kubectl get -n eunomia-operator endpoints/eunomia-operator -o jsonpath='{.subsets[*].addresses[*].targetRef.name}' | xargs -I% kubectl exec -n eunomia-operator % -- curl -sS localhost:8383/metrics | grep eunomia_build_info

eunomia version: v0.1.6
Additional context

N/A

My vote would be to upgrade the current one to helm 3. There's no reason to keep the old one around at this point...


Disable Travis CI for 3.0 branch

What is the purpose of the change
Disable Travis CI for 3.0 branch
Brief changelog
remove .travis.yml

related discussion https://lists.apache.org/thread.html/rb0bf764a4b4b852d3f463e60a910239ad09bb766e9894491e398004a%40<dev.dubbo.apache.org>

Codecov Report

Merging #7343 (e5b187b) into 3.0 (e0cba81) will decrease coverage by 0.47%.
The diff coverage is n/a.

@@             Coverage Diff              @@
##                3.0    #7343      +/-   ##
============================================
- Coverage     57.50%   57.02%   -0.48%
+ Complexity      357      356       -1
============================================
  Files           983      983
  Lines         40141    40141
  Branches       5997     5976      -21
============================================
- Hits          23083    22891     -192
- Misses        14347    14528     +181
- Partials       2711     2722      +11

Impacted Files
Coverage Δ
Complexity Δ

...figcenter/file/FileSystemDynamicConfiguration.java
31.42% <0.00%> (-30.96%)
0.00% <0.00%> (ø%)

...bo/config/event/listener/LoggingEventListener.java
37.50% <0.00%> (-25.00%)
0.00% <0.00%> (ø%)

.../registry/multicast/MulticastServiceDiscovery.java
53.84% <0.00%> (-23.08%)
0.00% <0.00%> (ø%)

...bo/rpc/cluster/support/FailbackClusterInvoker.java
52.45% <0.00%> (-18.04%)
0.00% <0.00%> (ø%)

...in/java/org/apache/dubbo/common/utils/JVMUtil.java
81.13% <0.00%> (-11.33%)
0.00% <0.00%> (ø%)

...e/dubbo/remoting/transport/netty4/NettyClient.java
60.86% <0.00%> (-10.15%)
0.00% <0.00%> (ø%)

.../client/metadata/ServiceInstanceMetadataUtils.java
61.79% <0.00%> (-8.99%)
0.00% <0.00%> (ø%)

...ig/metadata/ServiceInstanceHostPortCustomizer.java
64.00% <0.00%> (-8.00%)
0.00% <0.00%> (ø%)

...org/apache/dubbo/rpc/protocol/AbstractInvoker.java
57.14% <0.00%> (-7.15%)
0.00% <0.00%> (ø%)

...he/dubbo/common/threadpool/ThreadlessExecutor.java
56.52% <0.00%> (-6.53%)
0.00% <0.00%> (ø%)

... and 31 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 e0cba81...e5b187b. Read the comment docs.


PR 2 : S3 Mini provisioner Test 2

test this please

test this please

test this please

test this please

test this please

test this please

test this please

test this please

test this please

test this please

test this please

test this please

test this please

test this please

test this please

test this please

test this please

test this please

test this please


Bring Deno implementation up-to-date

We now have a Deno implementation, however it doesn't implement the full spec yet (as far as I'm available).
In order to have all implementations up-to-date someone should implement the full spec

Should be solved by #63