Infite loop when using parameter "--terragrunt-use-partial-parse-config-cache"

Describe the bug
Infite loop when using parameter "--terragrunt-use-partial-parse-config-cache". I believe this is an implementation problem, I do not have any cycles in the code, I can normally use run-all with validate, apply and destroy, but I was looking for some performance improvements since my repository is quite large. Debug logs are looping between modules: kms, acm-certificate, iam-service-linked-role-for-opensearch, kms - as seen below.
DEBU[0026] Cache hit for '/Users/michal/Projekty/personal/terraform/aws-infrastructure-template/live/product-1/environments/dev/shared-region/kms/terragrunt.hcl' (partial parsing), decodeList: '[3 0 1]'.  prefix=[/Users/michal/Projekty/personal/terraform/aws-infrastructure-template/live/product-1/environments/dev/shared-region/kms]
DEBU[0026] Setting download directory for module /Users/michal/Projekty/personal/terraform/aws-infrastructure-template/live/product-1/environments/dev/shared-region/kms to /Users/michal/Projekty/personal/terraform/aws-infrastructure-template/live/product-1/environments/dev/shared-region/kms/.terragrunt-cache
DEBU[0026] Cache hit for '/Users/michal/Projekty/personal/terraform/aws-infrastructure-template/live/product-1/environments/dev/shared-region/opensearch/acm-certificate/terragrunt.hcl' (partial parsing), decodeList: '[3 0 1]'.  prefix=[/Users/michal/Projekty/personal/terraform/aws-infrastructure-template/live/product-1/environments/dev/shared-region/opensearch/acm-certificate]
DEBU[0026] Setting download directory for module /Users/michal/Projekty/personal/terraform/aws-infrastructure-template/live/product-1/environments/dev/shared-region/opensearch/acm-certificate to /Users/michal/Projekty/personal/terraform/aws-infrastructure-template/live/product-1/environments/dev/shared-region/opensearch/acm-certificate/.terragrunt-cache
DEBU[0026] Cache hit for '/Users/michal/Projekty/personal/terraform/aws-infrastructure-template/live/product-1/environments/dev/global/iam/iam-service-linked-role-for-opensearch/terragrunt.hcl' (partial parsing), decodeList: '[3 0 1]'.  prefix=[/Users/michal/Projekty/personal/terraform/aws-infrastructure-template/live/product-1/environments/dev/global/iam/iam-service-linked-role-for-opensearch]
DEBU[0026] Setting download directory for module /Users/michal/Projekty/personal/terraform/aws-infrastructure-template/live/product-1/environments/dev/global/iam/iam-service-linked-role-for-opensearch to /Users/michal/Projekty/personal/terraform/aws-infrastructure-template/live/product-1/environments/dev/global/iam/iam-service-linked-role-for-opensearch/.terragrunt-cache
DEBU[0026] Cache hit for '/Users/michal/Projekty/personal/terraform/aws-infrastructure-template/live/product-1/environments/dev/shared-region/kms/terragrunt.hcl' (partial parsing), decodeList: '[3 0 1]'.  prefix=[/Users/michal/Projekty/personal/terraform/aws-infrastructure-template/live/product-1/environments/dev/shared-region/kms]
DEBU[0026] Setting download directory for module /Users/michal/Projekty/personal/terraform/aws-infrastructure-template/live/product-1/environments/dev/shared-region/kms to /Users/michal/Projekty/personal/terraform/aws-infrastructure-template/live/product-1/environments/dev/shared-region/kms/.terragrunt-cache

To Reproduce
It's hard for me to provide reproduction steps as repository is very large and I am not able to reproduce it using simple example. Graph dependencies output:
digraph {
        "/Users/michal/Projekty/personal/terraform/aws-infrastructure-template/live/org-management/eu-central-1/organization" ;
        "config" ;
        "config" -> "/Users/michal/Projekty/personal/terraform/aws-infrastructure-template/live/org-management/eu-central-1/organization";
        "environments/dev/eu-central-1/core/ecs/cluster" ;
        "environments/dev/eu-central-1/core/ecs/cluster" -> "/Users/michal/Projekty/personal/terraform/aws-infrastructure-template/live/org-management/eu-central-1/organization";
        "environments/dev/eu-central-1/core/ecs/cluster" -> "environments/dev/global/iam/iam-service-linked-role-for-ecs";
        "environments/dev/eu-central-1/core/ecs/cluster" -> "environments/dev/eu-central-1/core/kms";
        "environments/dev/eu-central-1/core/ecs/kinesis-firehose-opensearch-stream" ;
        "environments/dev/eu-central-1/core/ecs/kinesis-firehose-opensearch-stream" -> "/Users/michal/Projekty/personal/terraform/aws-infrastructure-template/live/org-management/eu-central-1/organization";
        "environments/dev/eu-central-1/core/ecs/kinesis-firehose-opensearch-stream" -> "environments/dev/shared-region/opensearch/domain";
        "environments/dev/eu-central-1/core/ecs/kinesis-firehose-opensearch-stream" -> "environments/dev/eu-central-1/core/kms";
        "environments/dev/eu-central-1/core/ecs/kinesis-firehose-opensearch-stream-ism-policy" ;
        "environments/dev/eu-central-1/core/ecs/kinesis-firehose-opensearch-stream-ism-policy" -> "/Users/michal/Projekty/personal/terraform/aws-infrastructure-template/live/org-management/eu-central-1/organization";
        "environments/dev/eu-central-1/core/ecs/kinesis-firehose-opensearch-stream-ism-policy" -> "environments/dev/shared-region/opensearch/domain";
        "environments/dev/eu-central-1/core/ecs/kinesis-firehose-opensearch-stream-ism-policy" -> "environments/dev/shared-region/opensearch/random-password";
        "environments/dev/eu-central-1/core/ecs/kinesis-firehose-opensearch-stream-ism-policy" -> "environments/dev/shared-region/opensearch/custom-endpoint-dns-records";
        "environments/dev/eu-central-1/core/ecs/kinesis-firehose-opensearch-stream-ism-policy" -> "environments/dev/eu-central-1/core/ecs/kinesis-firehose-opensearch-stream";
        "environments/dev/eu-central-1/core/ecs/kinesis-firehose-opensearch-stream-role" ;
        "environments/dev/eu-central-1/core/ecs/kinesis-firehose-opensearch-stream-role" -> "/Users/michal/Projekty/personal/terraform/aws-infrastructure-template/live/org-management/eu-central-1/organization";
        "environments/dev/eu-central-1/core/ecs/kinesis-firehose-opensearch-stream-role" -> "environments/dev/shared-region/opensearch/domain";
        "environments/dev/eu-central-1/core/ecs/kinesis-firehose-opensearch-stream-role" -> "environments/dev/shared-region/opensearch/random-password";
        "environments/dev/eu-central-1/core/ecs/kinesis-firehose-opensearch-stream-role" -> "environments/dev/shared-region/opensearch/custom-endpoint-dns-records";
        "environments/dev/eu-central-1/core/ecs/kinesis-firehose-opensearch-stream-role" -> "environments/dev/eu-central-1/core/ecs/kinesis-firehose-opensearch-stream";
        "environments/dev/eu-central-1/core/ecs/kinesis-firehose-opensearch-stream-role-mapping" ;
        "environments/dev/eu-central-1/core/ecs/kinesis-firehose-opensearch-stream-role-mapping" -> "/Users/michal/Projekty/personal/terraform/aws-infrastructure-template/live/org-management/eu-central-1/organization";
        "environments/dev/eu-central-1/core/ecs/kinesis-firehose-opensearch-stream-role-mapping" -> "environments/dev/shared-region/opensearch/domain";
        "environments/dev/eu-central-1/core/ecs/kinesis-firehose-opensearch-stream-role-mapping" -> "environments/dev/shared-region/opensearch/random-password";
        "environments/dev/eu-central-1/core/ecs/kinesis-firehose-opensearch-stream-role-mapping" -> "environments/dev/shared-region/opensearch/custom-endpoint-dns-records";
        "environments/dev/eu-central-1/core/ecs/kinesis-firehose-opensearch-stream-role-mapping" -> "environments/dev/eu-central-1/core/ecs/kinesis-firehose-opensearch-stream";
        "environments/dev/eu-central-1/core/ecs/kinesis-firehose-opensearch-stream-role-mapping" -> "environments/dev/eu-central-1/core/ecs/kinesis-firehose-opensearch-stream-role";
        "environments/dev/eu-central-1/core/ecs/service-discovery-http-namespace" ;
        "environments/dev/eu-central-1/core/ecs/service-discovery-http-namespace" -> "/Users/michal/Projekty/personal/terraform/aws-infrastructure-template/live/org-management/eu-central-1/organization";
        "environments/dev/eu-central-1/core/kms" ;
        "environments/dev/eu-central-1/core/kms" -> "/Users/michal/Projekty/personal/terraform/aws-infrastructure-template/live/org-management/eu-central-1/organization";
        "environments/dev/eu-central-1/core/kms" -> "config";
        "environments/dev/eu-central-1/core/rds/db" ;
        "environments/dev/eu-central-1/core/rds/db" -> "/Users/michal/Projekty/personal/terraform/aws-infrastructure-template/live/org-management/eu-central-1/organization";
        "environments/dev/eu-central-1/core/rds/db" -> "environments/dev/eu-central-1/core/vpc/vpc";
        "environments/dev/eu-central-1/core/rds/db" -> "environments/dev/eu-central-1/core/kms";
        "environments/dev/eu-central-1/core/rds/db" -> "environments/dev/eu-central-1/core/rds/sg";
        "environments/dev/eu-central-1/core/rds/master-user-password" ;
        "environments/dev/eu-central-1/core/rds/master-user-password" -> "/Users/michal/Projekty/personal/terraform/aws-infrastructure-template/live/org-management/eu-central-1/organization";
        "environments/dev/eu-central-1/core/rds/master-user-password" -> "environments/dev/eu-central-1/core/rds/db";
        "environments/dev/eu-central-1/core/rds/sg" ;
        "environments/dev/eu-central-1/core/rds/sg" -> "/Users/michal/Projekty/personal/terraform/aws-infrastructure-template/live/org-management/eu-central-1/organization";
        "environments/dev/eu-central-1/core/rds/sg" -> "environments/dev/eu-central-1/core/vpc/vpc";
        "environments/dev/eu-central-1/core/ssm-run-command/al2023-ami" ;
        "environments/dev/eu-central-1/core/ssm-run-command/al2023-ami" -> "/Users/michal/Projekty/personal/terraform/aws-infrastructure-template/live/org-management/eu-central-1/organization";
        "environments/dev/eu-central-1/core/ssm-run-command/ec2-instance" ;
        "environments/dev/eu-central-1/core/ssm-run-command/ec2-instance" -> "/Users/michal/Projekty/personal/terraform/aws-infrastructure-template/live/org-management/eu-central-1/organization";
        "environments/dev/eu-central-1/core/ssm-run-command/ec2-instance" -> "config";
        "environments/dev/eu-central-1/core/ssm-run-command/ec2-instance" -> "environments/dev/eu-central-1/core/ssm-run-command/al2023-ami";
        "environments/dev/eu-central-1/core/ssm-run-command/ec2-instance" -> "environments/dev/eu-central-1/core/vpc/vpc";
        "environments/dev/eu-central-1/core/ssm-run-command/ec2-instance" -> "environments/dev/eu-central-1/core/ssm-run-command/sg";
        "environments/dev/eu-central-1/core/ssm-run-command/ec2-instance" -> "environments/dev/eu-central-1/core/rds/sg";
        "environments/dev/eu-central-1/core/ssm-run-command/s3-ansible-playbooks" ;
        "environments/dev/eu-central-1/core/ssm-run-command/s3-ansible-playbooks" -> "/Users/michal/Projekty/personal/terraform/aws-infrastructure-template/live/org-management/eu-central-1/organization";
        "environments/dev/eu-central-1/core/ssm-run-command/s3-ansible-playbooks" -> "config";
        "environments/dev/eu-central-1/core/ssm-run-command/s3-ansible-playbooks" -> "environments/dev/eu-central-1/core/ssm-run-command/ec2-instance";
        "environments/dev/eu-central-1/core/ssm-run-command/s3-ansible-playbooks" -> "environments/dev/eu-central-1/core/kms";
        "environments/dev/eu-central-1/core/ssm-run-command/s3-ssm-run-command-output-logs" ;
        "environments/dev/eu-central-1/core/ssm-run-command/s3-ssm-run-command-output-logs" -> "/Users/michal/Projekty/personal/terraform/aws-infrastructure-template/live/org-management/eu-central-1/organization";
        "environments/dev/eu-central-1/core/ssm-run-command/s3-ssm-run-command-output-logs" -> "config";
        "environments/dev/eu-central-1/core/ssm-run-command/s3-ssm-run-command-output-logs" -> "environments/dev/eu-central-1/core/ssm-run-command/ec2-instance";
        "environments/dev/eu-central-1/core/ssm-run-command/s3-ssm-run-command-output-logs" -> "environments/dev/eu-central-1/core/kms";
        "environments/dev/eu-central-1/core/ssm-run-command/sg" ;
        "environments/dev/eu-central-1/core/ssm-run-command/sg" -> "/Users/michal/Projekty/personal/terraform/aws-infrastructure-template/live/org-management/eu-central-1/organization";
        "environments/dev/eu-central-1/core/ssm-run-command/sg" -> "environments/dev/eu-central-1/core/vpc/vpc";
        "environments/dev/eu-central-1/core/vpc/s3-vpc-flow-logs" ;
        "environments/dev/eu-central-1/core/vpc/s3-vpc-flow-logs" -> "/Users/michal/Projekty/personal/terraform/aws-infrastructure-template/live/org-management/eu-central-1/organization";
        "environments/dev/eu-central-1/core/vpc/s3-vpc-flow-logs" -> "config";
        "environments/dev/eu-central-1/core/vpc/s3-vpc-flow-logs" -> "environments/dev/eu-central-1/core/kms";
        "environments/dev/eu-central-1/core/vpc/vpc" ;
        "environments/dev/eu-central-1/core/vpc/vpc" -> "/Users/michal/Projekty/personal/terraform/aws-infrastructure-template/live/org-management/eu-central-1/organization";
        "environments/dev/eu-central-1/core/vpc/vpc" -> "environments/dev/eu-central-1/core/vpc/s3-vpc-flow-logs";
        "environments/dev/eu-central-1/services/_data/ssm-parameter-aws-for-fluent-bit-stable" ;
        "environments/dev/eu-central-1/services/_data/ssm-parameter-aws-for-fluent-bit-stable" -> "/Users/michal/Projekty/personal/terraform/aws-infrastructure-template/live/org-management/eu-central-1/organization";
        "environments/dev/eu-central-1/services/api/alb/acm-certificate" ;
        "environments/dev/eu-central-1/services/api/alb/acm-certificate" -> "/Users/michal/Projekty/personal/terraform/aws-infrastructure-template/live/org-management/eu-central-1/organization";
        "environments/dev/eu-central-1/services/api/alb/acm-certificate" -> "config";
        "environments/dev/eu-central-1/services/api/alb/acm-certificate-dns-validation-records" ;
        "environments/dev/eu-central-1/services/api/alb/acm-certificate-dns-validation-records" -> "/Users/michal/Projekty/personal/terraform/aws-infrastructure-template/live/org-management/eu-central-1/organization";
        "environments/dev/eu-central-1/services/api/alb/acm-certificate-dns-validation-records" -> "config";
        "environments/dev/eu-central-1/services/api/alb/acm-certificate-dns-validation-records" -> "environments/dev/eu-central-1/services/api/alb/acm-certificate";
        "environments/dev/eu-central-1/services/api/alb/acm-certificate-validation-object" ;
        "environments/dev/eu-central-1/services/api/alb/acm-certificate-validation-object" -> "/Users/michal/Projekty/personal/terraform/aws-infrastructure-template/live/org-management/eu-central-1/organization";
        "environments/dev/eu-central-1/services/api/alb/acm-certificate-validation-object" -> "environments/dev/eu-central-1/services/api/alb/acm-certificate-dns-validation-records";
        "environments/dev/eu-central-1/services/api/alb/acm-certificate-validation-object" -> "environments/dev/eu-central-1/services/api/alb/acm-certificate";
        "environments/dev/eu-central-1/services/api/alb/alb" ;
        "environments/dev/eu-central-1/services/api/alb/alb" -> "/Users/michal/Projekty/personal/terraform/aws-infrastructure-template/live/org-management/eu-central-1/organization";
        "environments/dev/eu-central-1/services/api/alb/alb" -> "environments/dev/eu-central-1/core/vpc/vpc";
        "environments/dev/eu-central-1/services/api/alb/alb" -> "environments/dev/eu-central-1/services/api/alb/acm-certificate-validation-object";
        "environments/dev/eu-central-1/services/api/alb/alb" -> "environments/dev/eu-central-1/services/api/alb/s3-access-logs";
        "environments/dev/eu-central-1/services/api/alb/alb" -> "environments/dev/eu-central-1/services/api/alb/sg";
        "environments/dev/eu-central-1/services/api/alb/dns-records" ;
        "environments/dev/eu-central-1/services/api/alb/dns-records" -> "/Users/michal/Projekty/personal/terraform/aws-infrastructure-template/live/org-management/eu-central-1/organization";
        "environments/dev/eu-central-1/services/api/alb/dns-records" -> "config";
        "environments/dev/eu-central-1/services/api/alb/dns-records" -> "environments/dev/eu-central-1/services/api/alb/alb";
        "environments/dev/eu-central-1/services/api/alb/s3-access-logs" ;
        "environments/dev/eu-central-1/services/api/alb/s3-access-logs" -> "/Users/michal/Projekty/personal/terraform/aws-infrastructure-template/live/org-management/eu-central-1/organization";
        "environments/dev/eu-central-1/services/api/alb/s3-access-logs" -> "config";
        "environments/dev/eu-central-1/services/api/alb/sg" ;
        "environments/dev/eu-central-1/services/api/alb/sg" -> "/Users/michal/Projekty/personal/terraform/aws-infrastructure-template/live/org-management/eu-central-1/organization";
        "environments/dev/eu-central-1/services/api/alb/sg" -> "environments/dev/eu-central-1/core/vpc/vpc";
        "environments/dev/eu-central-1/services/api/db/db" ;
        "environments/dev/eu-central-1/services/api/db/db" -> "/Users/michal/Projekty/personal/terraform/aws-infrastructure-template/live/org-management/eu-central-1/organization";
        "environments/dev/eu-central-1/services/api/db/db" -> "environments/dev/eu-central-1/core/ssm-run-command/ec2-instance";
        "environments/dev/eu-central-1/services/api/db/db" -> "environments/dev/eu-central-1/core/ssm-run-command/s3-ssm-run-command-output-logs";
        "environments/dev/eu-central-1/services/api/db/db" -> "environments/dev/eu-central-1/core/ssm-run-command/s3-ansible-playbooks";
        "environments/dev/eu-central-1/services/api/db/db" -> "environments/dev/eu-central-1/core/rds/db";
        "environments/dev/eu-central-1/services/api/db/db" -> "environments/dev/eu-central-1/core/rds/master-user-password";
        "environments/dev/eu-central-1/services/api/db/db-schema" ;
        "environments/dev/eu-central-1/services/api/db/db-schema" -> "/Users/michal/Projekty/personal/terraform/aws-infrastructure-template/live/org-management/eu-central-1/organization";
        "environments/dev/eu-central-1/services/api/db/db-schema" -> "environments/dev/eu-central-1/core/ssm-run-command/ec2-instance";
        "environments/dev/eu-central-1/services/api/db/db-schema" -> "environments/dev/eu-central-1/core/ssm-run-command/s3-ssm-run-command-output-logs";
        "environments/dev/eu-central-1/services/api/db/db-schema" -> "environments/dev/eu-central-1/core/ssm-run-command/s3-ansible-playbooks";
        "environments/dev/eu-central-1/services/api/db/db-schema" -> "environments/dev/eu-central-1/core/rds/db";
        "environments/dev/eu-central-1/services/api/db/db-schema" -> "environments/dev/eu-central-1/core/rds/master-user-password";
        "environments/dev/eu-central-1/services/api/db/db-schema" -> "environments/dev/eu-central-1/services/api/db/db";
        "environments/dev/eu-central-1/services/api/db/db-user" ;
        "environments/dev/eu-central-1/services/api/db/db-user" -> "/Users/michal/Projekty/personal/terraform/aws-infrastructure-template/live/org-management/eu-central-1/organization";
        "environments/dev/eu-central-1/services/api/db/db-user" -> "environments/dev/eu-central-1/core/ssm-run-command/ec2-instance";
        "environments/dev/eu-central-1/services/api/db/db-user" -> "environments/dev/eu-central-1/core/ssm-run-command/s3-ssm-run-command-output-logs";
        "environments/dev/eu-central-1/services/api/db/db-user" -> "environments/dev/eu-central-1/core/ssm-run-command/s3-ansible-playbooks";
        "environments/dev/eu-central-1/services/api/db/db-user" -> "environments/dev/eu-central-1/core/rds/db";
        "environments/dev/eu-central-1/services/api/db/db-user" -> "environments/dev/eu-central-1/core/rds/master-user-password";
        "environments/dev/eu-central-1/services/api/db/db-user" -> "environments/dev/eu-central-1/services/api/db/random-password";
        "environments/dev/eu-central-1/services/api/db/db-user" -> "environments/dev/eu-central-1/services/api/db/db";
        "environments/dev/eu-central-1/services/api/db/db-user-priv" ;
        "environments/dev/eu-central-1/services/api/db/db-user-priv" -> "/Users/michal/Projekty/personal/terraform/aws-infrastructure-template/live/org-management/eu-central-1/organization";
        "environments/dev/eu-central-1/services/api/db/db-user-priv" -> "environments/dev/eu-central-1/core/ssm-run-command/ec2-instance";
        "environments/dev/eu-central-1/services/api/db/db-user-priv" -> "environments/dev/eu-central-1/core/ssm-run-command/s3-ssm-run-command-output-logs";
        "environments/dev/eu-central-1/services/api/db/db-user-priv" -> "environments/dev/eu-central-1/core/ssm-run-command/s3-ansible-playbooks";
        "environments/dev/eu-central-1/services/api/db/db-user-priv" -> "environments/dev/eu-central-1/core/rds/db";
        "environments/dev/eu-central-1/services/api/db/db-user-priv" -> "environments/dev/eu-central-1/core/rds/master-user-password";
        "environments/dev/eu-central-1/services/api/db/db-user-priv" -> "environments/dev/eu-central-1/services/api/db/random-password";
        "environments/dev/eu-central-1/services/api/db/db-user-priv" -> "environments/dev/eu-central-1/services/api/db/db";
        "environments/dev/eu-central-1/services/api/db/db-user-priv" -> "environments/dev/eu-central-1/services/api/db/db-user";
        "environments/dev/eu-central-1/services/api/db/db-user-priv" -> "environments/dev/eu-central-1/services/api/db/db-schema";
        "environments/dev/eu-central-1/services/api/db/random-password" ;
        "environments/dev/eu-central-1/services/api/db/random-password" -> "/Users/michal/Projekty/personal/terraform/aws-infrastructure-template/live/org-management/eu-central-1/organization";
        "environments/dev/eu-central-1/services/api/db/ssm-parameter" ;
        "environments/dev/eu-central-1/services/api/db/ssm-parameter" -> "/Users/michal/Projekty/personal/terraform/aws-infrastructure-template/live/org-management/eu-central-1/organization";
        "environments/dev/eu-central-1/services/api/db/ssm-parameter" -> "environments/dev/eu-central-1/core/rds/db";
        "environments/dev/eu-central-1/services/api/db/ssm-parameter" -> "environments/dev/eu-central-1/services/api/db/random-password";
        "environments/dev/eu-central-1/services/api/db/ssm-parameter" -> "environments/dev/eu-central-1/services/api/db/db";
        "environments/dev/eu-central-1/services/api/db/ssm-parameter" -> "environments/dev/eu-central-1/services/api/db/db-user";
        "environments/dev/eu-central-1/services/api/ecs-service" ;
        "environments/dev/eu-central-1/services/api/ecs-service" -> "/Users/michal/Projekty/personal/terraform/aws-infrastructure-template/live/org-management/eu-central-1/organization";
        "environments/dev/eu-central-1/services/api/ecs-service" -> "config";
        "environments/dev/eu-central-1/services/api/ecs-service" -> "environments/dev/eu-central-1/services/_data/ssm-parameter-aws-for-fluent-bit-stable";
        "environments/dev/eu-central-1/services/api/ecs-service" -> "environments/dev/eu-central-1/core/vpc/vpc";
        "environments/dev/eu-central-1/services/api/ecs-service" -> "environments/dev/eu-central-1/core/rds/sg";
        "environments/dev/eu-central-1/services/api/ecs-service" -> "environments/dev/eu-central-1/services/api/sg";
        "environments/dev/eu-central-1/services/api/ecs-service" -> "environments/dev/eu-central-1/core/kms";
        "environments/dev/eu-central-1/services/api/ecs-service" -> "environments/dev/eu-central-1/core/ecs/cluster";
        "environments/dev/eu-central-1/services/api/ecs-service" -> "environments/dev/eu-central-1/services/api/db/ssm-parameter";
        "environments/dev/eu-central-1/services/api/ecs-service" -> "environments/dev/eu-central-1/core/ecs/kinesis-firehose-opensearch-stream";
        "environments/dev/eu-central-1/services/api/ecs-service" -> "environments/dev/eu-central-1/services/api/alb/alb";
        "environments/dev/eu-central-1/services/api/ecs-service" -> "environments/dev/eu-central-1/core/ecs/service-discovery-http-namespace";
        "environments/dev/eu-central-1/services/api/sg" ;
        "environments/dev/eu-central-1/services/api/sg" -> "/Users/michal/Projekty/personal/terraform/aws-infrastructure-template/live/org-management/eu-central-1/organization";
        "environments/dev/eu-central-1/services/api/sg" -> "environments/dev/eu-central-1/core/vpc/vpc";
        "environments/dev/eu-central-1/services/api/sg" -> "environments/dev/eu-central-1/services/api/alb/sg";
        "environments/dev/eu-central-1/services/worker/ecs-service" ;
        "environments/dev/eu-central-1/services/worker/ecs-service" -> "/Users/michal/Projekty/personal/terraform/aws-infrastructure-template/live/org-management/eu-central-1/organization";
        "environments/dev/eu-central-1/services/worker/ecs-service" -> "config";
        "environments/dev/eu-central-1/services/worker/ecs-service" -> "environments/dev/eu-central-1/services/_data/ssm-parameter-aws-for-fluent-bit-stable";
        "environments/dev/eu-central-1/services/worker/ecs-service" -> "environments/dev/eu-central-1/core/vpc/vpc";
        "environments/dev/eu-central-1/services/worker/ecs-service" -> "environments/dev/eu-central-1/core/rds/sg";
        "environments/dev/eu-central-1/services/worker/ecs-service" -> "environments/dev/eu-central-1/services/worker/sg";
        "environments/dev/eu-central-1/services/worker/ecs-service" -> "environments/dev/eu-central-1/core/kms";
        "environments/dev/eu-central-1/services/worker/ecs-service" -> "environments/dev/eu-central-1/core/ecs/cluster";
        "environments/dev/eu-central-1/services/worker/ecs-service" -> "environments/dev/eu-central-1/services/api/db/ssm-parameter";
        "environments/dev/eu-central-1/services/worker/ecs-service" -> "environments/dev/eu-central-1/core/ecs/kinesis-firehose-opensearch-stream";
        "environments/dev/eu-central-1/services/worker/sg" ;
        "environments/dev/eu-central-1/services/worker/sg" -> "/Users/michal/Projekty/personal/terraform/aws-infrastructure-template/live/org-management/eu-central-1/organization";
        "environments/dev/eu-central-1/services/worker/sg" -> "environments/dev/eu-central-1/core/vpc/vpc";
        "environments/dev/global/iam/iam-role-ecs-cicd" ;
        "environments/dev/global/iam/iam-role-ecs-cicd" -> "/Users/michal/Projekty/personal/terraform/aws-infrastructure-template/live/org-management/eu-central-1/organization";
        "environments/dev/global/iam/iam-role-ecs-cicd" -> "config";
        "environments/dev/global/iam/iam-role-ecs-cicd" -> "environments/dev/global/iam/iam-role-policy-ecs-cicd";
        "environments/dev/global/iam/iam-role-policy-ecs-cicd" ;
        "environments/dev/global/iam/iam-role-policy-ecs-cicd" -> "/Users/michal/Projekty/personal/terraform/aws-infrastructure-template/live/org-management/eu-central-1/organization";
        "environments/dev/global/iam/iam-service-linked-role-for-ecs" ;
        "environments/dev/global/iam/iam-service-linked-role-for-ecs" -> "/Users/michal/Projekty/personal/terraform/aws-infrastructure-template/live/org-management/eu-central-1/organization";
        "environments/dev/global/iam/iam-service-linked-role-for-opensearch" ;
        "environments/dev/global/iam/iam-service-linked-role-for-opensearch" -> "/Users/michal/Projekty/personal/terraform/aws-infrastructure-template/live/org-management/eu-central-1/organization";
        "environments/dev/shared-region/kms" ;
        "environments/dev/shared-region/kms" -> "/Users/michal/Projekty/personal/terraform/aws-infrastructure-template/live/org-management/eu-central-1/organization";
        "environments/dev/shared-region/kms" -> "config";
        "environments/dev/shared-region/opensearch/acm-certificate" ;
        "environments/dev/shared-region/opensearch/acm-certificate" -> "/Users/michal/Projekty/personal/terraform/aws-infrastructure-template/live/org-management/eu-central-1/organization";
        "environments/dev/shared-region/opensearch/acm-certificate" -> "config";
        "environments/dev/shared-region/opensearch/acm-certificate-dns-validation-records" ;
        "environments/dev/shared-region/opensearch/acm-certificate-dns-validation-records" -> "/Users/michal/Projekty/personal/terraform/aws-infrastructure-template/live/org-management/eu-central-1/organization";
        "environments/dev/shared-region/opensearch/acm-certificate-dns-validation-records" -> "config";
        "environments/dev/shared-region/opensearch/acm-certificate-dns-validation-records" -> "environments/dev/shared-region/opensearch/acm-certificate";
        "environments/dev/shared-region/opensearch/acm-certificate-validation-object" ;
        "environments/dev/shared-region/opensearch/acm-certificate-validation-object" -> "/Users/michal/Projekty/personal/terraform/aws-infrastructure-template/live/org-management/eu-central-1/organization";
        "environments/dev/shared-region/opensearch/acm-certificate-validation-object" -> "environments/dev/shared-region/opensearch/acm-certificate-dns-validation-records";
        "environments/dev/shared-region/opensearch/acm-certificate-validation-object" -> "environments/dev/shared-region/opensearch/acm-certificate";
        "environments/dev/shared-region/opensearch/custom-endpoint-dns-records" ;
        "environments/dev/shared-region/opensearch/custom-endpoint-dns-records" -> "/Users/michal/Projekty/personal/terraform/aws-infrastructure-template/live/org-management/eu-central-1/organization";
        "environments/dev/shared-region/opensearch/custom-endpoint-dns-records" -> "config";
        "environments/dev/shared-region/opensearch/custom-endpoint-dns-records" -> "environments/dev/shared-region/opensearch/domain";
        "environments/dev/shared-region/opensearch/domain" ;
        "environments/dev/shared-region/opensearch/domain" -> "/Users/michal/Projekty/personal/terraform/aws-infrastructure-template/live/org-management/eu-central-1/organization";
        "environments/dev/shared-region/opensearch/domain" -> "environments/dev/global/iam/iam-service-linked-role-for-opensearch";
        "environments/dev/shared-region/opensearch/domain" -> "environments/dev/shared-region/kms";
        "environments/dev/shared-region/opensearch/domain" -> "environments/dev/shared-region/opensearch/acm-certificate";
        "environments/dev/shared-region/opensearch/domain" -> "environments/dev/shared-region/opensearch/acm-certificate-validation-object";
        "environments/dev/shared-region/opensearch/domain" -> "environments/dev/shared-region/opensearch/random-password";
        "environments/dev/shared-region/opensearch/random-password" ;
        "environments/dev/shared-region/opensearch/random-password" -> "/Users/michal/Projekty/personal/terraform/aws-infrastructure-template/live/org-management/eu-central-1/organization";
        "management/cicd/eu-central-1/kms" ;
        "management/cicd/eu-central-1/kms" -> "/Users/michal/Projekty/personal/terraform/aws-infrastructure-template/live/org-management/eu-central-1/organization";
        "management/cicd/eu-central-1/kms" -> "config";
        "management/cicd/eu-central-1/services/api/codecommit" ;
        "management/cicd/eu-central-1/services/api/codecommit" -> "/Users/michal/Projekty/personal/terraform/aws-infrastructure-template/live/org-management/eu-central-1/organization";
        "management/cicd/eu-central-1/services/api/ecr" ;
        "management/cicd/eu-central-1/services/api/ecr" -> "/Users/michal/Projekty/personal/terraform/aws-infrastructure-template/live/org-management/eu-central-1/organization";
        "management/cicd/eu-central-1/services/api/ecr" -> "config";
        "management/cicd/eu-central-1/services/api/ecr" -> "management/cicd/eu-central-1/kms";
        "management/cicd/eu-central-1/services/api/pipeline" ;
        "management/cicd/eu-central-1/services/api/pipeline" -> "/Users/michal/Projekty/personal/terraform/aws-infrastructure-template/live/org-management/eu-central-1/organization";
        "management/cicd/eu-central-1/services/api/pipeline" -> "management/cicd/eu-central-1/kms";
        "management/cicd/eu-central-1/services/api/pipeline" -> "management/cicd/eu-central-1/services/api/s3-pipeline-artifacts";
        "management/cicd/eu-central-1/services/api/pipeline" -> "management/cicd/eu-central-1/services/api/ecr";
        "management/cicd/eu-central-1/services/api/pipeline" -> "environments/dev/global/iam/iam-role-ecs-cicd";
        "management/cicd/eu-central-1/services/api/pipeline" -> "environments/dev/eu-central-1/core/ecs/cluster";
        "management/cicd/eu-central-1/services/api/pipeline-trigger" ;
        "management/cicd/eu-central-1/services/api/pipeline-trigger" -> "/Users/michal/Projekty/personal/terraform/aws-infrastructure-template/live/org-management/eu-central-1/organization";
        "management/cicd/eu-central-1/services/api/pipeline-trigger" -> "management/cicd/eu-central-1/services/api/codecommit";
        "management/cicd/eu-central-1/services/api/pipeline-trigger" -> "management/cicd/eu-central-1/services/api/pipeline";
        "management/cicd/eu-central-1/services/api/s3-pipeline-artifacts" ;
        "management/cicd/eu-central-1/services/api/s3-pipeline-artifacts" -> "/Users/michal/Projekty/personal/terraform/aws-infrastructure-template/live/org-management/eu-central-1/organization";
        "management/cicd/eu-central-1/services/api/s3-pipeline-artifacts" -> "config";
        "management/cicd/eu-central-1/services/api/s3-pipeline-artifacts" -> "management/cicd/eu-central-1/kms";
        "management/cicd/eu-central-1/services/worker/codecommit" ;
        "management/cicd/eu-central-1/services/worker/codecommit" -> "/Users/michal/Projekty/personal/terraform/aws-infrastructure-template/live/org-management/eu-central-1/organization";
        "management/cicd/eu-central-1/services/worker/ecr" ;
        "management/cicd/eu-central-1/services/worker/ecr" -> "/Users/michal/Projekty/personal/terraform/aws-infrastructure-template/live/org-management/eu-central-1/organization";
        "management/cicd/eu-central-1/services/worker/ecr" -> "config";
        "management/cicd/eu-central-1/services/worker/ecr" -> "management/cicd/eu-central-1/kms";
        "management/cicd/eu-central-1/services/worker/pipeline" ;
        "management/cicd/eu-central-1/services/worker/pipeline" -> "/Users/michal/Projekty/personal/terraform/aws-infrastructure-template/live/org-management/eu-central-1/organization";
        "management/cicd/eu-central-1/services/worker/pipeline" -> "management/cicd/eu-central-1/kms";
        "management/cicd/eu-central-1/services/worker/pipeline" -> "management/cicd/eu-central-1/services/worker/s3-pipeline-artifacts";
        "management/cicd/eu-central-1/services/worker/pipeline" -> "management/cicd/eu-central-1/services/worker/ecr";
        "management/cicd/eu-central-1/services/worker/pipeline" -> "environments/dev/global/iam/iam-role-ecs-cicd";
        "management/cicd/eu-central-1/services/worker/pipeline" -> "environments/dev/eu-central-1/core/ecs/cluster";
        "management/cicd/eu-central-1/services/worker/pipeline-trigger" ;
        "management/cicd/eu-central-1/services/worker/pipeline-trigger" -> "/Users/michal/Projekty/personal/terraform/aws-infrastructure-template/live/org-management/eu-central-1/organization";
        "management/cicd/eu-central-1/services/worker/pipeline-trigger" -> "management/cicd/eu-central-1/services/worker/codecommit";
        "management/cicd/eu-central-1/services/worker/pipeline-trigger" -> "management/cicd/eu-central-1/services/worker/pipeline";
        "management/cicd/eu-central-1/services/worker/s3-pipeline-artifacts" ;
        "management/cicd/eu-central-1/services/worker/s3-pipeline-artifacts" -> "/Users/michal/Projekty/personal/terraform/aws-infrastructure-template/live/org-management/eu-central-1/organization";
        "management/cicd/eu-central-1/services/worker/s3-pipeline-artifacts" -> "config";
        "management/cicd/eu-central-1/services/worker/s3-pipeline-artifacts" -> "management/cicd/eu-central-1/kms";
}

Expected behavior
Faster run-all execution
Versions

Terragrunt version: v0.51.0
Terraform version: 1.5.7
Environment details: MacOS Ventura 13.5

After a bit more digging I found that this problem disappears when I removed the dependency block from a file that is read by another file using read_terragrunt_config so this issue might be related to https://github.com/gruntwork-io/terragrunt/issues/1128

Hi,
will be helpful to provide example repository/hcl files on which this issue happens


PR: Make jedi_patch.py to work with Jedi 0.10.x versions

Pinging @ghisvail about this one.

Could you detail a bit more what this PR solves please?
I thought #4121 already fixed Jedi autocompletion...?
Cheers,

Jedi 0.10.2 was released some days ago and Spyder was not able to work it because #4121 was only using Jedi 0.10.0.
I thought that was fine because Jedi take some much time to do new releases. But that was not the case with 0.10.

Oh I see now. Thanks for heads-up.


BetterDiscord background not showing

Ok better discord is working ok for me its the theme thats not showing i mean the theme works its just its not showing the background help please :c how can this be fixed?....
here a pic of the background of betterdiscord

betterdiscord background is suppose to show and its not

welp having this issue now. none of those fix it. inve just broke it more than it was already.

same here.

Same I have this.

I have this issue and I need it fixed

I also have the same issue now

I just got that issue too, at about the same time as Mewy69


pipeline: start merging files in groups

In an effort to reduce memory pressure when merging large groups of files we're starting to merge them in smaller groups.

Codecov Report
Attention: 16 lines in your changes are missing coverage. Please review.

Comparison is base (bcbeed0) 47.10% compared to head (c037dd2) 47.23%.

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
Additional details and impacted files
@@            Coverage Diff             @@
##           master     #205      +/-   ##
==========================================
+ Coverage   47.10%   47.23%   +0.12%
==========================================
  Files          87       87
  Lines        3821     3851      +30
==========================================
+ Hits         1800     1819      +19
- Misses       1705     1716      +11
  Partials      316      316

Files
Coverage Δ

internal/pipeline/merging.go
60.93% <60.97%> (+0.44%)
:arrow_up:

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


{} uses copy constructor, while = does not

Just a little annoyance I encountered while writing to_json functions for a large number of in house classes.  Ideally I'd like it if the {} operator behaved the same as the = operator.
Given the following code:
using json = nlohmann::json;

class A {
private:
	std::string          _val;

	// by including the mutex we've implicitly deleted our copy constructor
	std::recursive_mutex _mutex;

public:
	A() : _val("Hello World") {};

	friend void to_json(json &j, const A &a) {
		j = {
			{"val", a._val}
		};
	}
};

int main(int argc, char* argv[]) {

	json j = {};
	A a;

        // This line compiles and runs completely fine.
        j["data"]["A"] =  a;

        //this line will fail to compile, due to the implicitly deleted A::A(const A&)
	j["data"] = {{"A", a}};

        std::cout << j.dump() << std::endl;
	return 0;
}

Could you paste the complete error output? Knowing where the copy happens would help a lot :)

Xcode:
main.cpp:36:24: error: call to implicitly-deleted copy constructor of 'A'
    j["data"] = {{"A", a}};
                       ^
main.cpp:13:26: note: copy constructor of 'A' is implicitly deleted because
      field '_mutex' has an inaccessible copy constructor
    std::recursive_mutex _mutex;
                         ^
./json.hpp:6785:22: note: passing argument to parameter 'args' here
    json_ref(Args... args)
                     ^
1 error generated.

Oops, missing forwarding references it seems

Aha? I have no idea how to fix this.

I'll fix it byt tonight, if there is no surprises with json_ref.

Thanks a lot! I have no time right now to wrap my head around this...

@jllansford PR #807 fixed the issue. Could you please check if this works for you?

I've been away for a few days but got around to testing the fix today and it works great.
Thanks for the prompt reply and fix.


Add checkDeviceNameFormat RPC

r? @maxtaco
Fix for CORE-2749

Our other Check* RPCs (e.g. signup.checkUsernameAvailable) return error strings rather than booleans, which is nice because it avoids hard-coding validation logic in the desktop app, perhaps this RPC could too?

OK, here's the hint when it fails.

:+1:


Allow the user to override img_type in upload_image

Whenever the image format and the img_type are both not set to png, reddit converts the image to RGBA mode, which may be useful if the user wishes to have a png automatically converted from any given color mode to RGBA. This is also useful in the case that the optimization that matches the format causes the image to lose quality / data, which in my experience has happened to some jpegs in the past.
If a value of "jpeg" is given it is gracefully accepted and converted to "jpg", because strangely, if "jpeg" is sent to the server, given how the validator checks the value, it will default to "png".
Implemented with the "upload_as" kwarg, because this also dictates the end file type on reddit's cdn.

@bboe I removed the jpeg option but wouldn't factoring img_type calculation out mean duplicating code required to verify that the file is a jpeg / png?

Thanks. I'll make the other change.

Please see 97d7f25c11518239fa4a71108215dcfa4c8be31e if interested in what I was asking for.


Suggestion: Add glfw example

Hi Jason!
I think it would be really helpful if you would throw in an example of "how to use with glfw - draw triangle".
If you need help writing up some examples i can help you out.
At a first look your library seems very promising and i am really looking forward to giving it a Go! ;)

In a more general sense, I crated this tutorial using vulkan-go. It covers the most general parts of using Go with Vulkan based on Vulkan tutorial.
It is probably a good idea to update it to use my own library. Most of the implementation would be the same. The creation of and access fields of the structs would be different, but it would provide a better test. Once I convert handles into receivers, so that the API looks more like GLFW's go API rather than the straight C API, I'll take a stab at rewriting the tutorial again.
If you have other examples (like maybe using SDL instead of GLFW, or other non-graphics use-cases for GPU programming) that would also be awesome.

Changing your own tutorial to use this library definitely makes sense!
I have a truck load of graphics libraries(glTF2.0, image library with support for AMDs Compressonator, etc..) i can make publicly available, when i convert them to support Vulkan instead of OpenGL, but no other non-graphics libraries comes to mind.
For OpenGL i made a CPU state library, that makes OpenGL a lot more efficient by handling uniforms to avoid re-binding already set value, VBO trimming, automated mesh generated based on existing primitives available in the shader. It would be fun the create this type of middleware for Vulkan as well.
I have worked with OpengGL for years and i am finally ready to transition to Vulkan, super excited!

It is really high level (and mostly code rather than explaining what is happening), but a first attempt was checked in @ https://github.com/ibd1279/vks/tree/main/tutorial .

Nice summary!
go get -u github.com/ibd1279/vks returns:
vk_wrapper.go:6: ./vk_wrapper.h:7:10: fatal error: vulkan/vulkan.h: No such file or directory
Which makes sense since the Vulkan header is missing.
Is the install then: Download the package manually and add desired vulkan.h to the directory?

I need to add this to the README: You need to download and install the Vulkan SDK. The mac installer (at least the most recent one), seems to handle everything. Not sure about the other languages yet.
I should probably also expand the beginning of my tutorial to include more of the details from the Vulkan-Tutorial on environment setup.

I am currently using Windows 10.
In my case the VulkanSDK is installed in: "C:\VulkanSDK[version]" and the header is in "C:\VulkanSDK[version]\Include\vulkan".
In regards to the vulkan/vulkan.h. On your machine, is the vulkan directory a part of your environment variables, as in "export PATH=.... or how does it locate the vulkan.h file?


Correct ossl_sleep for threaded model by introducing sleep() - 3.0,3.1,3.2

This fix handles situations where ossl_sleep() receives a millis value equal or greater than 1000, which breaks platforms where this is not legal.
Fixes: #23961

This PR is in a state where it requires action by @openssl/committers but the last update was 30 days ago

This pull request is ready to merge

Merged to the 3.1 and 3.0 branches. Thank you for your contribution.
This does not apply to 3.2. If there is still anything needed to fix on 3.2 in regards to ossl_sleep please open a new PR against 3.2.


TensorFlow 2.0 has no attribute 'ConfigProto'; fix proposed

Nice project! Thanks for putting it together!
I found a breaking issue today, with a simple fix.  The versioning strings ask for TensorFlow >=1.14, but there's some internal code that relies on a TF configuration object that was changed in TF2.0.  A workaround is to change the tensorflow requirement strings in setup.py and requirements.txt from "tensorflow>=1.14",  to  "tensorflow>=1.14,<2.0",
I did a pip install fer in a new virtualenv and then started following the usage instructions. Here's a session dump:
In [1]: import tensorflow
In [2]: tensorflow.__version__
Out[2]: '2.0.0'
In [3]: from fer import FER
In [4]: detector = FER()
---------------------------------------------------------------------------
AttributeError                            Traceback (most recent call last)
<ipython-input-2-a308cfd708c0> in <module>
----> 1 detector = FER()

~/td_venv/lib/python3.7/site-packages/fer/fer.py in __init__(self, cascade_file, mtcnn, emotion_model, scale_factor, min_face_size, min_neighbors, offsets, compile)
    110                 "fer", "data/emotion_model.hdf5"
    111             )
--> 112             self.config = tf.ConfigProto(log_device_placement=False)
    113             self.config.gpu_options.allow_growth = True
    114

AttributeError: module 'tensorflow' has no attribute 'ConfigProto'

Here's a workaround  for TF1/TF2 compatibility that I think would also resolve things.
I'll send a PR later on if I can get something working smoothly. Cheers!

Hi Evan, thanks for your message and proposed fix. I would be happy to
review a PR.
Cheers,
Justin
On Fri, Nov 1, 2019 at 11:23 PM Evan Jones<EMAIL_ADDRESS>wrote:

Nice project! Thanks for putting it together!
I found a breaking issue today, with a simple fix. The versioning strings
ask for TensorFlow >=1.14, but there's some internal code that relies on a
TF configuration object that was changed in TF2.0. A workaround is to
change the tensorflow requirement strings in setup.py and requirements.txt
from "tensorflow>=1.14", to "tensorflow>=1.14,<2.0",
I did a pip install fer in a new virtualenv and then started following
the usage instructions. Here's a session dump:
In [1]: import tensorflow
In [2]: tensorflow.version
Out[2]: '2.0.0'
In [3]: from fer import FER
In [4]: detector = FER()
AttributeError                            Traceback (most recent call last) in
----> 1 detector = FER()
~/td_venv/lib/python3.7/site-packages/fer/fer.py in init(self, cascade_file, mtcnn, emotion_model, scale_factor, min_face_size, min_neighbors, offsets, compile)
110                 "fer", "data/emotion_model.hdf5"
111             )
--> 112             self.config = tf.ConfigProto(log_device_placement=False)
113             self.config.gpu_options.allow_growth = True
114
AttributeError: module 'tensorflow' has no attribute 'ConfigProto'
Here's a workaround https://stackoverflow.com/a/56994817 for TF1/TF2
compatibility that I think would also resolve things.
I'll send a PR later on if I can get something working smoothly. Cheers!
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/justinshenk/fer/issues/7?email_source=notifications&email_token=ACOLMZBOKMVCT6K6SFKG4DTQRST4ZA5CNFSM4JIAUZD2YY3PNVWWK3TUL52HS4DFUVEXG43VMWVGG33NNVSW45C7NFSM4HWHJAEQ,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ACOLMZFFMUZA37B3FJ7MRZDQRST4ZANCNFSM4JIAUZDQ
.

Hi @justinshenk I started using fer and had this issue. I did install from pip3 as I have python 3.6
Finally to get the fix from master i cloned this repo manually and that let me start.
No idea why pip isn't picking the right one, just wanted to let you know error still showed then

Fixed in v20.0.0 with dc46da3830160465ea03d68290650c72d1b52504.  Now works with pip install -U fer.


Debug don't output while set in script.

The debug output is only shown when auto is set true or when cmd opt is given.
Problematic part
Line 296 - 306: No check if bool is given by (func) arg.

False flag, the check is in bs_debug itself.


Add waits for select network responses

There are a few cases where server response times are much higher than usual. In these cases the tests may be waiting on an element to change, but could instead wait for a response from the server before proceeding. See https://docs.cypress.io/guides/guides/network-requests.html#Waiting
This should help with reducing any flakiness that might have been resolved by adding custom timeouts for elements. The best practice is not to wait (and fail) on the DOM, but wait on the server response instead. Then, failures will more accurately reflect the root cause (the server).
Examples would include adding a server, waiting to receive data from a newly added layer, changing existing query areas, filters, date change, etc. Investigate.

With work that is being completed on #398, this will soon be OBE.


Server crashes on paper-76 (1.14.2) after chests seem to get loaded

[23:51:06] [Server thread/ERROR]: [ShopChest] No Chest found in world 'world' at location: 12412; 67; -10133
[23:51:06] [Server thread/ERROR]: [ShopChest] No Chest found in world 'world' at location: 12410; 67; -10133
[23:51:07] [Server thread/ERROR]: [ShopChest] No Chest found in world 'world' at location: 1344; 6; 714
[23:51:07] [Server thread/ERROR]: [ShopChest] No Chest found in world 'world' at location: 1348; 6; 714
[23:51:07] [Server thread/ERROR]: [ShopChest] No Chest found in world 'world' at location: 306; 63; 142
[23:51:08] [Server thread/ERROR]: [ShopChest] No Chest found in world 'world' at location: 1346; 6; 714
[23:51:16] [Paper Watchdog Thread/ERROR]: --- DO NOT REPORT THIS TO PAPER - THIS IS NOT A BUG OR A CRASH  - git-Paper-76 (MC: 1.14.2) ---
[23:51:16] [Paper Watchdog Thread/ERROR]: The server has not responded for 10 seconds!  Leave a message if that is not the case.


fix swift: fixed missing Content-Type headers issue

Signed-off-by: Martin Chodur<EMAIL_ADDRESS>Fixes https://github.com/thanos-io/thanos/issues/713
@sudhi-vm PTAL as a maintainer of the Swift storage integration

[x] I added CHANGELOG entry for this change.
[ ] Change is not relevant to the end user.

Changes

Enabling the Full option in ListOpts. This should provide missing headers for the gophercloud library to be able to determine content-type of the response.
Fix GetRange which did not handle the length: -1 correctly as not set but used it leading to incorrect range bytes=1--1 instead of bytes=1-. See the Range parameter of the GET method in the Swift API docs.

Verification
Before, two acceptance e2e tests for object storage were failing
=== RUN   TestObjStore_AcceptanceTest_e2e
=== PAUSE TestObjStore_AcceptanceTest_e2e
=== CONT  TestObjStore_AcceptanceTest_e2e
--- FAIL: TestObjStore_AcceptanceTest_e2e (0.94s)
=== RUN   TestObjStore_AcceptanceTest_e2e/inmem
    --- PASS: TestObjStore_AcceptanceTest_e2e/inmem (0.00s)
=== RUN   TestObjStore_AcceptanceTest_e2e/filesystem
=== PAUSE TestObjStore_AcceptanceTest_e2e/filesystem
    TestObjStore_AcceptanceTest_e2e: foreach.go:32: GCS found in THANOS_TEST_OBJSTORE_SKIP array. Skipping.
    TestObjStore_AcceptanceTest_e2e: foreach.go:32: S3 found in THANOS_TEST_OBJSTORE_SKIP array. Skipping.
    TestObjStore_AcceptanceTest_e2e: foreach.go:32: AZURE found in THANOS_TEST_OBJSTORE_SKIP array. Skipping.
=== CONT  TestObjStore_AcceptanceTest_e2e/filesystem
    --- PASS: TestObjStore_AcceptanceTest_e2e/filesystem (0.01s)
=== RUN   TestObjStore_AcceptanceTest_e2e/swift
    TestObjStore_AcceptanceTest_e2e/swift: swift.go:316: created temporary container for swift tests with name test-65c69e700dd980c8-testobjstore-acceptancetest-e2e-swift
=== PAUSE TestObjStore_AcceptanceTest_e2e/swift
    TestObjStore_AcceptanceTest_e2e: foreach.go:32: COS found in THANOS_TEST_OBJSTORE_SKIP array. Skipping.
    TestObjStore_AcceptanceTest_e2e: foreach.go:32: ALIYUNOSS found in THANOS_TEST_OBJSTORE_SKIP array. Skipping.
=== CONT  TestObjStore_AcceptanceTest_e2e/swift
    TestObjStore_AcceptanceTest_e2e/swift: testing.go:130: testing.go:130:

        	exp: "test-data@"

        	got: "@test-data@"

        Diff:
        --- Expected
        +++ Actual
        @@ -1 +1 @@
        -test-data@
        +@test-data@

    TestObjStore_AcceptanceTest_e2e/swift: testing.go:58: iterating over bucket objects failed: Cannot extract names from response with content-type: []
    TestObjStore_AcceptanceTest_e2e/swift: swift.go:321: deleting container test-65c69e700dd980c8-testobjstore-acceptancetest-e2e-swift failed: Expected HTTP response code [] when accessing [DELETE https://test-swift-proxy.test.dszn.cz/v1/AUTH_ddbe05efeb1142508d781a92d63a781e/test-65c69e700dd980c8-testobjstore-acceptancetest-e2e-swift], but got 409 instead

Conflict

There was a conflict when trying to complete your request.

    --- FAIL: TestObjStore_AcceptanceTest_e2e/swift (2.01s)
FAIL

Process finished with exit code 1

Now all tests are passing
=== RUN   TestObjStore_AcceptanceTest_e2e
=== PAUSE TestObjStore_AcceptanceTest_e2e
=== CONT  TestObjStore_AcceptanceTest_e2e
--- PASS: TestObjStore_AcceptanceTest_e2e (0.91s)
=== RUN   TestObjStore_AcceptanceTest_e2e/inmem
    --- PASS: TestObjStore_AcceptanceTest_e2e/inmem (0.00s)
=== RUN   TestObjStore_AcceptanceTest_e2e/filesystem
=== PAUSE TestObjStore_AcceptanceTest_e2e/filesystem
    TestObjStore_AcceptanceTest_e2e: foreach.go:32: GCS found in THANOS_TEST_OBJSTORE_SKIP array. Skipping.
    TestObjStore_AcceptanceTest_e2e: foreach.go:32: S3 found in THANOS_TEST_OBJSTORE_SKIP array. Skipping.
    TestObjStore_AcceptanceTest_e2e: foreach.go:32: AZURE found in THANOS_TEST_OBJSTORE_SKIP array. Skipping.
=== CONT  TestObjStore_AcceptanceTest_e2e/filesystem
    --- PASS: TestObjStore_AcceptanceTest_e2e/filesystem (0.00s)
=== RUN   TestObjStore_AcceptanceTest_e2e/swift
    TestObjStore_AcceptanceTest_e2e/swift: swift.go:324: created temporary container for swift tests with name test-281cd3eb693829b6-testobjstore-acceptancetest-e2e-swift
=== PAUSE TestObjStore_AcceptanceTest_e2e/swift
    TestObjStore_AcceptanceTest_e2e: foreach.go:32: COS found in THANOS_TEST_OBJSTORE_SKIP array. Skipping.
    TestObjStore_AcceptanceTest_e2e: foreach.go:32: ALIYUNOSS found in THANOS_TEST_OBJSTORE_SKIP array. Skipping.
=== CONT  TestObjStore_AcceptanceTest_e2e/swift
    --- PASS: TestObjStore_AcceptanceTest_e2e/swift (4.92s)
PASS

Process finished with exit code 0

To be honest I do not know how this could have worked for anyone else. If it did maybe it could have been cased by different version of Swift for example? Or changes in the Gophercloud library?
I'd be really glad to hear from anyone using Swift already what version of Swift they have and how the Thanos is configured exactly.
Our Thanos objstore config for Swift:
type: SWIFT
config:
  auth_url: "https://foo.bar:5000/v3/"
  username: "thanos"
  user_domain_name: "general_dev"
  password: "*****"
  domain_name: "general_dev"
  project_name: "s_98"
  project_domain_name: "general_dev"
  region_name: "Test"
  container_name: "thanos"

Output of the /info of our Swift cluster
{
  "bulk_delete": {
    "max_failed_deletes": 1000,
    "max_deletes_per_request": 10000
  },
  "container_quotas": {},
  "tempurl": {
    "outgoing_remove_headers": [
      "x-object-meta-*"
    ],
    "incoming_remove_headers": [
      "x-timestamp"
    ],
    "incoming_allow_headers": [],
    "methods": [
      "GET",
      "HEAD",
      "PUT",
      "POST",
      "DELETE"
    ],
    "outgoing_allow_headers": [
      "x-object-meta-public-*"
    ]
  },
  "bulk_upload": {
    "max_failed_extractions": 1000,
    "max_containers_per_extraction": 10000
  },
  "container_sync": {
    "realms": {}
  },
  "ratelimit": {
    "account_ratelimit": 10,
    "max_sleep_time_seconds": 10,
    "container_ratelimits": [
      [
        0,
        20
      ]
    ],
    "container_listing_ratelimits": [
      [
        0,
        200
      ]
    ]
  },
  "slo": {
    "max_manifest_segments": 1000,
    "min_segment_size": 1,
    "max_manifest_size": 2097152
  },
  "account_quotas": {},
  "swift": {
    "max_file_size":<PHONE_NUMBER>,
    "account_listing_limit": 10000,
    "account_autocreate": true,
    "max_meta_count": 90,
    "max_meta_value_length": 256,
    "container_listing_limit": 10000,
    "extra_header_count": 0,
    "max_meta_overall_size": 4096,
    "version": "2.15.1",
    "max_meta_name_length": 128,
    "max_header_size": 8192,
    "policies": [
      {
        "name": "Policy-0",
        "aliases": "Policy-0"
      },
      {
        "default": true,
        "name": "dev-test",
        "aliases": "dev-test"
      }
    ],
    "max_object_name_length": 1024,
    "max_account_name_length": 256,
    "strict_cors_mode": true,
    "allow_account_management": true,
    "max_container_name_length": 256
  },
  "swift3": {
    "max_upload_part_num": 1000,
    "allow_multipart_uploads": true,
    "max_bucket_listing": 1000,
    "version": "1.11.1.dev142",
    "max_parts_listing": 1000,
    "max_multi_delete_objects": 1000
  }
}

Linting failed due to OOM kill, but I do not have the permission to rerun it :/

Tested this with https://github.com/beaukode/docker-swift-onlyone-authv2-keystone. What has tripped me is that the default region is called RegionOne. I have used the following exports:
OS_AUTH_URL=http://<IP_ADDRESS>:5000/v2.0
OS_PASSWORD=s3cr3t
OS_PROJECT_NAME=admin
OS_REGION_NAME=RegionOne
OS_USERNAME=admin
THANOS_TEST_OBJSTORE_SKIP=GCS,S3,AZURE,COS,ALIYUNOSS

Not sure how no one has noticed this yet. Thanks a lot.

I have fixed up the CHANGELOG.md file so that it could be merged. At first, I have done it via the Web UI but I forgot to add a DCO there so I have done that via the command-line now. I hope you don't mind. Merging on green!

I guess I'll merge this to fix the current code as-is and then let's work on https://github.com/thanos-io/thanos/pull/2732

Cool thanks :+1:
When I realized there are bigger issues with the Swift integration I kind of abandoned this and switched to the refactor of the Swift support.


Add CustomEvent Polyfill for better IE support

In IE the code raises an error when creating a CustomEvent:
TypeError: Object doesn't support this action
The code tries to account for this by checking if CustomEvent exists on the window object, which it does in IE, but not as a function as it is invoked.

Thanks for your contribution @csgulyas.


[doc request] from CDN

Very much appreciate the work you've done but I am new to Vue and having difficulty integrating.
The Basic example seems to be for a .vue file.
But I am just using the CDN and html/css/js files. So need to define Swatches as a component so I can include it in my vue instance under components.
Could you please add a doc example so I can do something in codepen like this.
E.g.
var swatches = {
  template: '
<swatches v-model="color" />
',
  data () {
      return { color: '#1CA085' }
    }
}
var vm = new Vue({
  el: '#app',
	selectedColorHex: '',
  data: pattern_data,
  components: {
    swatches,
  },

or maybe its
components: {
  'swatches': VueSwatches
}

Looking at your new 2.0 branch it might be:
components: {
Swatches: window['vue-swatches'],
}
but not quite right yet...

Hi, like it's written in the Basic Usage

components: { Swatches }, // window.VueSwatches.default - from CDN

so, you need to import the component like this
{
  components: {
  {
    Swatches: window.VueSwatches.default
  }
}

let me know if that solves your problem

yes it does. sorry I did not understand that correctly


T8N return an error when asked BLOCKHASH in state test mode

Original issue:
https://github.com/ethereum/execution-spec-tests/issues/899
here is the evmdump:
http://retesteth.ethdevops.io/temp/pyspecs/frontier__scenarios__test_scenarios__test_blockhash_bug/
error:
.venv/lib/python3.12/site-packages/requests/models.py:974: in json
    return complexjson.loads(self.text, **kwargs)
/usr/lib/python3.12/json/__init__.py:346: in loads
    return _default_decoder.decode(s)
/usr/lib/python3.12/json/decoder.py:337: in decode
    obj, end = self.raw_decode(s, idx=_w(s, 0).end())
/usr/lib/python3.12/json/decoder.py:355: in raw_decode
    raise JSONDecodeError("Expecting value", s, err.value) from None
E   json.decoder.JSONDecodeError: Expecting value: line 1 column 1 (char 0)

During handling of the above exception, another exception occurred:
tests/frontier/scenarios/test_scenarios.py:257: in test_scenarios
    state_test(env=tx_env, pre=pre, post=post, tx=tx, post_hint=hint)
src/pytest_plugins/filler/filler.py:836: in __init__
    fixture = self.generate(
src/ethereum_test_specs/state.py:188: in generate
    return self.make_state_test_fixture(t8n, fork, eips, self.post_hint)
src/ethereum_test_specs/state.py:139: in make_state_test_fixture
    transition_tool_output = t8n.evaluate(
src/ethereum_clis/transition_tool.py:487: in evaluate
    return self._evaluate_server(t8n_data=t8n_data, debug_output_path=debug_output_path)
src/ethereum_clis/transition_tool.py:314: in _evaluate_server
    output: TransitionToolOutput = TransitionToolOutput.model_validate(response.json())
.venv/lib/python3.12/site-packages/requests/models.py:978: in json
    raise RequestsJSONDecodeError(e.msg, e.doc, e.pos)
E   requests.exceptions.JSONDecodeError: Expecting value: line 1 column 1 (char 0)
------------------------------------------------------------------------- Captured stderr call --------------------------------------------------------------------------
----------------------------------------
Exception occurred during processing of request from ['local', 0]
Traceback (most recent call last):
  File "/usr/lib/python3.12/socketserver.py", line 318, in _handle_request_noblock
    self.process_request(request, client_address)
  File "/usr/lib/python3.12/socketserver.py", line 349, in process_request
    self.finish_request(request, client_address)
  File "/home/wins/.cache/ethereum-spec-evm-resolver/Cancun/src/ethereum_spec_tools/evm_tools/daemon.py", line 91, in finish_request
    super().finish_request(request, client_address)
  File "/usr/lib/python3.12/socketserver.py", line 362, in finish_request
    self.RequestHandlerClass(request, client_address, self)
  File "/usr/lib/python3.12/socketserver.py", line 761, in __init__
    self.handle()
  File "/usr/lib/python3.12/http/server.py", line 436, in handle
    self.handle_one_request()
  File "/usr/lib/python3.12/http/server.py", line 424, in handle_one_request
    method()
  File "/home/wins/.cache/ethereum-spec-evm-resolver/Cancun/src/ethereum_spec_tools/evm_tools/daemon.py", line 66, in do_POST
    main(args=args, out_file=out_wrapper, in_file=input)
  File "/home/wins/.cache/ethereum-spec-evm-resolver/Cancun/src/ethereum_spec_tools/evm_tools/__init__.py", line 109, in main
    return t8n_tool.run()
           ^^^^^^^^^^^^^^

To confirm, the expected behaviour here is that when the chain does not contain a block at the given number (so for example current block has number 8 but it has no parent), you keccak the string representation of the missing block number?
If my above understanding is correct, we will not implement this behaviour. There are other ways we could provide fake block hashes (like pushing empty blocks before beginning the test), but this is just too weird for us to include in the spec itself.


Can proxy flatmap_filter be used to change the incoming request

Describe what are you trying to do
Can I use proxy flatmap_filter be used to change the incoming request something like this  inside extra_config of an endpoint
"proxy": {
              "flatmap_filter": [
                  {
                      "type": "move",
                      "args": ["contact.0.contactMedium.0.characteristic.street1", "contactmoved.0.address1"]
                  },
                    {
                      "type": "move",
                      "args": ["contact.0.contactMedium.0.characteristic.city", "contactmoved.0.city"]
                  },
                    {
                      "type": "move",
                      "args": ["contact.0.contactMedium.0.characteristic.contactNumber", "contactmoved.0.phoneNumber"]
                  }
]
        }

My requirement actually is to modify incoming request properties to different property names.
Also is it possible to take JSON Array Nth element to copy into a JSON Map? something like this contact[0] to "contactMoved": {.....}

The flat map filter only works for the responses. If you want to modify the requests you can use:

Lua
Request modifiers


Rebased: Keytab & TLS support for Flink on Mesos Setup

Rebased #2734 to the latest master.

Rebased again to the latest Mesos changes to make sure tests pass.

Tests passed. Merging.


[18.0-fr1][make]Update force-bump target for 18.0-fr1

/hold I need to test if this target results in a correct version bumps on 18.0-fr1.

/approve

@gibizer once the commits on main move forwards the branch should diverge. But this will take time.

/lgtm

/retest

/retest


_meta/_permissions

POST to /users.  It'll either return an existing user from their openid or else create it
PUT to /bookmarks/fpad/clients/<id>/certifications/_meta/_permissions a doc like:

{
  users: {
    10: { read: true, write: true, owner: true },
  },
}

The cloud will then create the doc inside of /shares/ that looks like:
{ 11 (a cert): {_id: '11', _rev: '0-0'}}

The fpad sharing indexer will watch for particular content types (certifications) and put the resource in the correct place (e.g. /bookmarks/certifications for gary)

-owner means they can write to _permissions
-users have permission of children docs that they have permission to, not parents.

implemented


fix: Use random_password resource instead of random_id

Description

Use random_password.result instead of random_id.hex since this is a resource specifically intended for secrets

Motivation and Context
Fixes #158
Breaking Changes
None
How Has This Been Tested?

[ ] I have tested and validated these changes using one or more of the provided examples/* projects

Not stale.
On Sun, 27 Mar 2022, 01:09 github-actions[bot], @.***>
wrote:

This PR has been automatically marked as stale because it has been open 30
days
with no activity. Remove stale label or comment or this PR will be closed
in 10 days
—
Reply to this email directly, view it on GitHub
https://github.com/terraform-aws-modules/terraform-aws-atlantis/pull/259#issuecomment-1079798924,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AB2KHPXYASQ5G7OTTKNBZDTVB6RMZANCNFSM5OSTUU7A
.
You are receiving this because you commented.Message ID:
@.***
com>


Add Tx.NamedQueryContext

Add Tx.NamedQueryContext method

Is there anything holding this change back?

Maybe the lack of maintainers for this project... 🤔

@jmoiron Any update on this one ?

Fixes #447.

Hello, @ardan-bkennedy, and I recently stepped in to help maintain this project.
We are sorting the opened issues and pull requests, and I think this would be better served by #724.
Thank you for your contribution.


[docs]: The operator publishReplay needs an adoption of the description and example

Please check those that apply

[ ] typo
[x] documentation doesn't exist
[ ] documentation needs clarification
[ ] error(s) in example
[x] needs example

Description Of The Issue
The operator publishReplay is missing:

short description
description
examples

We may want to fix this.

This is deprecated and will be removed in favor of connect.


translatable nestedform

This is a follow up on https://github.com/wintercms/wn-translate-plugin/pull/30 as it was accidently closed bei github during a branch update.

Thé main branch needs to be merged into this branch, there's too much noise

@mjauvin can you do it? You need to merge main into wip/translatable-nestedforms on this repo directly first

@mjauvin can you do it? You need to merge main into wip/translatable-nestedforms on this repo directly first

@LukeTowers I just merged main into wip/translatable-nestedform but nothing has changed.

@mjauvin apply my suggestion to regenerate the diff on github. Also in the future please ensure that allow edits from maintainers is checked when creating a PR so that I can apply them directly.

@mjauvin apply my suggestion to regenerate the diff on github. Also in the future please ensure that allow edits from maintainers is checked when creating a PR so that I can apply them directly.

@LukeTowers I didn't create this PR, and can't commit to it either.

@mjauvin whoops my bad, mistook StudioBosco for StudioAzura 🤦

@der-On can you make this PR editable by maintainers and apply my suggestion?

@der-On can you make this PR editable by maintainers and apply my suggestion?

Seem's like I cannot make it editable after it was created.

@der-On you can recreate the PR if you are able to extract the changes required, or rebase?

Can this one be closed @der-On ?

Can this one be closed @der-On ?

Oh yes, please.


server oauth

WIP
Relates to #1533

Really need to pick this up again

Is this testable on prod or the test server?

u need to ask @Askaholic but I am pretty sure it is a little buggy

The answer will be no https://github.com/FAForever/server/pull/591
You will need to deploy the PR on test which is not the easiest thing to do cause you also need to make the required config changes

Maybe I can help you some day

Going to combine with #2175


make the ear plugin compatible with the configuration cache

This PR replaces the obsolete PR https://github.com/gradle/gradle/pull/23384
Fixes https://github.com/gradle/gradle/issues/19725
Context
The core plugin "ear" is not compatible with the configuration cache despite being marked as such
https://github.com/gradle/gradle/issues/19725

All code contributions are due to https://github.com/huybrechts , I merely made a merge after a year of inactivity.

Hello again, @JonasMorrissey. Thanks for the PR!
Unfortunately this is not enough to make the ear plugin fully compatible with the configuration cache as you can see in https://github.com/gradle/gradle/pull/23606 which incorporates a simplified version of these changes.
Next step would be to fix those tests marked with @ToBeFixedForConfigurationCache if that's something you'd like to do.

Superseded by https://github.com/gradle/gradle/pull/23606


added icons for entries without icons

Certain entries in the visualization and data storage sections didn't have icons, which was inconsistent with every other entry

Project name:
Project website/repository:
License:

Checklist for new projects:

[x] The project is open-source and accessible.
[x] Searched the existing entries to make sure this is not a duplicate.
[x] Contains only a single addition (make separate PRs if adding more than one).
[x] Added the link to the bottom of the relevant category.
[x] Add icon from the media/icon/ folder if applicable (like ![Python](media/icon/python.png) ).
[x] Created a new category only if necessary.
[x] Checked spelling and grammar.
[x] Removed trailing whitespace and periods.
[x] Confirm the dash – is not a minus -.
[x] Used title-casing (AP style) for project name.

Thank you @hmccree!


Add the key type to the known_hosts file

This is silly, but ssh refuses the key otherwise. Ansible fact doesn't
put this little header in place, we have to put it in manually.
Also turn ssh back on

+1


Fix tests to expect a non-match, not an error

In https://github.com/rspec/rspec-expectations/pull/1449, the Include
matcher is fixed so that it doesn't raise an error when types don't
match. Instead, the actual and expected will be deemed to not match.

Closing as the root PR was closed


TEAM PAGE

DESCRIPTION :
I want to design the TEAM PAGE OF CODERS EVOKE Website.
FEATURES :

Image of each team member with their name and designation.
Will be displayed in the form of Cards UI
(optional) message/quote from each team member can be added with their image and name.

You can also suggest some changes to this idea.

@pushpakumari5117 Go ahead. Just keep on thing in mind to make the theme similar to home page or whole website.

hey @neelshah2409 this issue is already created by me #82 look ,
hey @pushpakumari5117 let her make a PR  after u can update according to you , got it ??

hey @neelshah2409 this issue is already created by me #82 look ,
hey @pushpakumari5117 let her make a PR after u can update according to you , got it ??

@Ayan-thecodeking The issue you mentioned is regarding the Events Page. Is the Team page and Events page the same?

so sorry @pushpakumari5117 go ahead ...and plz design the page related to home page what we have ...
make it responsive

so sorry @pushpakumari5117 go ahead ...and plz design the page related to home page what we have ...
make it responsive

@pushpakumari5117 have u started ??

so sorry @pushpakumari5117 go ahead ...and plz design the page related to home page what we have ...
make it responsive

@pushpakumari5117 have u started ??

@Ayan-thecodeking Not yet....today only you gave me permission to work on that...so I haven't started yet.

so sorry @pushpakumari5117 go ahead ...and plz design the page related to home page what we have ...
make it responsive

@pushpakumari5117 have u started ??

@Ayan-thecodeking Not yet....today only you gave me permission to work on that...so I haven't started yet.

Yup @pushpakumari5117 no issues ...u can start now

any updates @pushpakumari5117

any updates @pushpakumari5117

@Ayan-thecodeking I am working on it.

any updates @pushpakumari5117

@Ayan-thecodeking I am working on it.

let me know @pushpakumari5117 when u are going to make a PR

Hey @Ayan-thecodeking should I work on this issue?


Update and extend the docs.

This commit contains changes only in readme.md which extend it's content.
Please review and merge if possible. :) thanks for this module

Bump topic


Feature/semesters

Implemented SemesterController with Manager Class and Endpoints
Description
This pull request includes the implementation of the SemesterController with the manager class and the specified endpoints. The following changes were made:
Here are the endpoints for the SemesterController in Markdown format:
SemesterController Endpoints
Create a Semester

Endpoint: POST /semesters
Description: Creates a new semester.
Request Body:{
  "id": "long",
  "name": "string",
  "description": "string",
  "degreeId": "long",
  "userId": "long"
}

  •	Response:
  •	201 Created: Semester successfully created.
  •	400 Bad Request: Invalid or missing request body.
  •	409 Conflict: Semester with the given ID already exists.

Get All Semesters
•	Endpoint: GET /semesters
•	Description: Retrieves all semesters for the authenticated user.
•	Response:
•	200 OK: Returns a list of semesters in JSON format.
•	400 Bad Request: User ID is missing from the principal.

Update a Semester
•	Endpoint: PATCH /semesters/{id}
•	Description: Updates an existing semester’s name and description.
•	Request Body:

{
"name": "string",
"description": "string"
}
•	Response:
•	200 OK: Semester successfully updated.
•	400 Bad Request: Invalid or missing request body or semester ID.
•	404 Not Found: Semester with the given ID does not exist.

Delete a Semester
•	Endpoint: DELETE /semesters/{id}
•	Description: Deletes an existing semester.
•	Response:
•	200 OK: Semester successfully deleted.
•	400 Bad Request: Semester ID or user ID is missing.
•	403 Forbidden: User is not authorized to delete this semester.
•	404 Not Found: Semester with the given ID does not exist.

Missing tests but i want to merge this first and do a refactor afterwards to write the tests, functionality should work as expected

the POST endpoint should not receive an id. they are generated by the server.


Sensor Cape Needs to be populated

I have populated the first sensor board. I will be creating the build of materials for the sensor board so the backup boards can be populated.

The boards need to be redesigned, so there is no need to populate the boards.


add unleash-proxy-client as dep

unleash-proxy-client is now a devDep, and it should be an actual dep, since it is used for the client.

@pvinis It's bundled as a part of the package when built with webpack, rendering the need for being an actual dependency moot - hence the devDependency.


CAMEL-21317: Camel jbang kubernetes documentation fix route/ingress

… traits
Description
Update documentation to match the actual behavior.
Target

[X] I checked that the commit is targeting the correct branch (note that Camel 3 uses camel-3.x, whereas Camel 4 uses the main branch)

Tracking

[X] If this is a large change, bug fix, or code improvement, I checked there is a JIRA issue filed for the change (usually before you start working on it).

Apache Camel coding standards and style

[X] I checked that each commit in the pull request has a meaningful subject line and body.

[X] I have run mvn clean install -DskipTests locally from root folder and I have committed all auto-generated changes.

@davsclaus @oscerd Is there any point for a backport of this documentation fix on 4.8.x ?

no the files in root/docs is not version specific.


refactor(tasks): use go time in task struct

Closes #14522
This PR updates the internal Task struct to use Go time.Time and time.Duration objects for time values instead of timestamp strings.
Continuation of refactoring work started in https://github.com/influxdata/influxdb/pull/15406

[ ] Rebased/mergeable
[ ] Tests pass

leaving a note about the smoke test that failed this in PR on 11/4
__________________________ TestSmoke.test_tasks_smoke __________________________
src/cloud/rest_api/smoke/test_smoke.py:364: in test_tasks_smoke
    time_task_created_seconds = litmus_util.utc_to_local(self, time_task_created, '%Y-%m-%dT%H:%M:%SZ')
src/util/litmus_utils.py:98: in utc_to_local
    datetime_obj = datetime.strptime(utc_iso_string, string_format)
/usr/local/lib/python2.7/_strptime.py:332: in _strptime
    (data_string, format))
E   ValueError: time data '2019-11-05T02:12:34.543138654Z' does not match format '%Y-%m-%dT%H:%M:%SZ'
====================== 1 failed, 1 passed in 6.43 seconds ======================
. https://circleci.com/gh/influxdata/influxdb/69468?utm_campaign=vcs-integration-link&utm_medium=referral&utm_source=github-build-link

That part of the smoke test is waiting for a task to execute, it's expecting a time stamp to be something like 2019-11-05T02:07:27Z and it's getting this format 2019-11-05T02:12:34.543138654Z


Support forwarder adding custom headers dynamically

#261 added support of configuring custom headers to the forwarder. In a multi-tenant environment such as gostatsd deployed as daemonset and shared by multiple pods, we'd like to have support of injecting custom headers from pod metadata.
This could be configured by a pair of flags, similar to the existing annotation/label-tag-regex flags of cloud providers.
[k8s]
annotation-custom-header-regex = '^gostatsd.atlassian.io/(?P<Service-Name>.*)$'
label-custom-header-regex= ''

If matched, forwarder will include the header Service-Name with the matched substring in the pod annotation.
Do you think this is a feature fit into gostatsd?

As a hypothetical, if there's a single node, with three pods (serviceA, serviceB, and gostatsd-forwarder), where gostatsd-forwarder is configured in a forwarder configuration, pointing to https://gostatsd-upstream
serviceA and serviceB both send to gostatsd-forwarder
Every interval, gostatsd-forwarder makes three requests to https://gostatsd-upstream:

Intermal metrics (no additional headers, or possibly x-service-name: gostatsd-forwarder)
serviceA metrics (with header x-service-name: serviceA)
serviceB metrics (with header x-service-name: serviceB)

Is that a correct understanding of the request?
If so, it seems like there's potential for additional load issues upstream, as there's now twice as much http "stuff" to manage.
If I was to implement it, I'd suggest doing it as a tag->header rewrite, and keep k8s out of it (other than the cloud provider adding the tag), but overall I'm not entirely certain it's a good idea because of the additional volume of requests.
Is this a workaround to help with scaling, due to clustering still not being done?

If so, it seems like there's potential for additional load issues upstream, as there's now twice as much http "stuff" to manage.

What's the upstream load difference between single-gostatsd-forwarder-for-all and one-gostatsd-forwarder-per-service?

The total number of requests may not be a problem to https://gostatsd-upstream. Since we binpack many services in a single node, number of total internal-metrics requests would drop, and total number of serviceN metrics would be similar with before.

If I was to implement it, I'd suggest doing it as a tag->header rewrite, and keep k8s out of it
Good call.

Is this a workaround to help with scaling, due to clustering still not being done?
Yes

@beanliu consider it as:
Old work = http + serviceAmetrics + serviceBmetrics + internalMetrics
New work = (3*http) + serviceAmetrics + serviceBmetrics + internalMetrics + splittingMetrics
There's also some other places for overhead to creep in, such as compress(serviceA) + compress(serviceB) + compress(internalMetrics) > compress(serviceA + serviceB + internalMetrics).
That being said - where is the load being applied? If it's an additional 0.5% CPU usage across 100 nodes, that kind of doesn't matter to the forwarder, it's in the noise.  If it's all going to a central upstream server, then that's 100 work units turning in to 300 work units, which is potentially a problem.  But if it's sharded upstream, then that's 100 work units going to 3 different servers (which is why I asked :)
@hligit I don't think binpacking would change the equation, I assume you binpack now, so there can only be a multiplier.  Although since it's to facilitate sharding, then that load gets split out, so it's probably not a concern.
Ideally it would be possible to configure it such that you don't need ...

serviceA->aggregator 1
serviceB->aggregator 2
internal->aggregator 1

... you would only have:

serviceB -> special aggregator
serviceA+internal -> default aggregator (in a single request)

I'm very mixed on it, honestly.  It's a lot of infrastructure to work around the actual problem, which is lack of horizontal scaling. But horizontal scaling also doesn't seem to have a lot of forward progress :(

Not sure if I understand that correctly.
I'll defined the scenarios in details so that we have consensus of what we are talking about.
Base case: one-service-container-with-one-gostatsd-forwarder: A service container and a gostatsd forwarder are deployed on a node.
k8sA case: multiple-service-container-with-one-gostatsd-forwarder-with-dynamic-http-header-based-on-service-tag: N service containers and a gostatsd forwarder are deployed on a node, and the gostatsd forwarder would group metrics by service and dispatch data to backend with service header.
k8sB case: multiple-service-container-with-one-gostatsd-forwarder: N service containers and a gostatsd forwarder are deployed on a node, and the forwarder just dump any batch to backend.

Old work = http + serviceAmetrics + serviceBmetrics + internalMetrics
New work = (3*http) + serviceAmetrics + serviceBmetrics + internalMetrics + splittingMetrics
@tiedotguy I assume here the "Old work" = k8sB and "New work" = k8sA?

My point is that k8sA is no worse than the base case. The overhead of k8sB may be smaller than k8sA but that just moving workload to backends as we always need sharding.

@tiedotguy FYI, in the above cases, the https://gostatsd-upstream would just be a proxy that dispatch data to different shards of aggregator based on service header.

I agrree for k8sA and k8sB, however in Base, does that refer to exactly one service + forwarder per node? (ie, the "micros" model), or does that refer to a service in k8s where the pod includes a gostatsd forwarder, and there may be multiple such pods on a single node?

does that refer to exactly one service + forwarder per node? (ie, the "micros" model)

yes.
Maybe there's another case: k8sC - multiple-service-container-and-multiple-gostatsd-forwarder-on-a-node, but that's seems pretty trivial.

We could implement the dispatch-based-on-metrics-service-tag logic outside gostatsd (middleware always wins), so the question is does it make any sense to include this in gostatsd? or is there better solution for k8scompute?

@tiedotguy @beanliu It boils down to two cases: dedicated(sidecar) or shared(daemonset). We have gostatsd deployed as sidecars in k8s and are considering moving to daemonset(shared) to reduce the memory footprint. We use quite large EC2 instances and there could be dozens of service pods and gostatsd sidecars on a single node.
I shared the mixed feeling of this too, thus raised issue to gather thoughts here.

Ok, gotcha. The difference with Base/k8sC vs k8sA is there's effectively no binpacking in Base, so no need for a dynamic aspect (which if I've kept up to date, is the current situation in Micros)
I agree that k8sA and Base are pretty much the same from the backends perspective.  From the forwarders perspective it's a bit more work (not a lot) because on Base it's 1 service, and on k8sA it's N+1.  As mentioned above though, I don't think it's a big deal for the forwarder tier, it's more the backend, which I know has been problematic.
It could be in or out of gostatsd, or somewhere in between (ie, something consuming gostatsd as a library, since there's a bunch of reusable stuff there).
A couple hypothetical options:

add dynamic headers in to the forwarder code, deploy as-is, let your existing infra handle it
add url routing to the forwarder code, deploy as a new forwarder tier
do 2, but do it in a new binary (ideally in the same repo, but if you need custom logic I can understand it not being open source), consuming gostatsd as a library.

@hligit interesting, I didn't realize you were doing that in k8s, I thought it was daemonset already.
I don't have a great answer. Assuming the only problem is scaling, then the right solution is clustering.  There's certainly unrelated usages of headers though (such as a dev/prod split), and it will get you where you need to go fastest, and isn't actually that much work (MetricMap.Split is a good starting spot)
It feels wrong, but ultimately results are what matters.

Then again, clustering has appeared on a backlog :P

I mean, if you're trying to motivate me to work on it...


:tada: Waifus for Denver

:wrench: new options for denver waifu
:zap: use known series instead of artists
:zap: use anything-4.0 model

Thank you for your contribution to the KodaDot NFT gallery.
👇 _ Let's make a quick check before the contribution.
PR Type

[ ] Bugfix
[ ] Feature
[ ] Refactoring

Context

[ ] Closes #<issue_number>
[ ] Requires deployment <>

Before submitting pull request, please make sure:

[ ] My contribution builds clean without any errors or warnings
[ ] I've merged recent default branch -- main and I've no conflicts
[ ] I've tried to respect high code quality standards
[ ] I've didn't break any original functionality
[ ] I've posted a screenshot of demonstrated change in this PR

Optional

[ ] I've tested it at </bsx/collection>
[ ] I've tested PR on mobile
[ ] I've written unit tests 🧪
[ ] I've found edge cases

Had issue bounty label?

[ ] Fill up your KSM address: Payout

Community participation

[ ] Are you at KodaDot Discord?

Screenshot 📸

[ ] My fix has changed something on UI; a screenshot is best to understand changes for others.

@JustLuuuu please check if options are enough

@JustLuuuu please check if options are enough

already gave you my feedback. I'm excited to see new waifus coming 🥰


Large processing time

I trained a model with my dataset using efficientdet 0. Although I got pretty good accuracy, I got large processing time (around 3 seconds for every test image) when using inference code. I thought efficientdet 0 must have very small processing time. Does anyone know is that normal or i made a mistake somewhere in code?

EfficientDet-D0 takes 16ms on my GPU (RTX 2070 Max Q) and around 160ms on CPU. It takes 3 seconds only when predicting on the first image. Can you share the code?

You are right. I changed inference.py code such that only process 1 image at a time. I mean I eliminate this line of code :
for image_path in glob.glob('datasets/VOC2007/JPEGImages/*.jpg'):
As you said, I changed back the code so that a list of images went through the function and I got 3s for first image and 0.2s for other ones.
Thanks alot for your help


Restrict pvp warnings to selected unit types ...

Primary i need an option to restrict any pvp warnings to only the current target to reduce warning spamming ...

May be it could be an idea also restricting to other unit types (arena n, targetoftarget, focus, class, etc.)

Closing this - unfortunately this is not really possible because there is only limited information available for a lot of spells and who casted them


sdkInfo: null in apktool.yml

Information

Apktool Version (apktool -version) - 2.2.0
Operating System (Mac, Linux, Windows) - Windows & OSX
APK From? (Playstore, ROM, Other) - Other / Local one

Steps to Reproduce

apktool  d myapp.apk

When decompiling a local apk I have, sdkInfo is set to "null".
Only happens with my local apk, wasn't able to reproduce yet.
The original AndroidManifest.xml has <uses-sdk android:minSdkVersion="18" targetSdkVersion="23"/>, which doesn't reflect in the generated apktool.yml.
That's how the complete apktool.yml looks like:
!!brut.androlib.meta.MetaInfo
apkFileName: myapp.apk
compressionType: false
doNotCompress:
- arsc
- json
isFrameworkApk: false
packageInfo:
  forcedPackageId: '127'
  renameManifestPackage: null
sdkInfo: null
sharedLibrary: false
unknownFiles: {}
usesFramework:
  ids:
  - 1
  tag: null
version: 2.2.0
versionInfo:
  versionCode: '656'
  versionName: 1.1.10938.656

Having null as sdkInfo leads to a generated AndroidManifest.xml when rebuilding the apk with apktool b, which produces problems.

Not sure how to replicate this with your steps. I tried
sdkInfo: null

and it completed. I also removed the attribute completely. I also removed the values from manifest prior to decode also with no errors.
Can't duplicate at all. A stacktrace or reproducible example would be next step here.

Closing due to no response in over a month. Can easily reopen if additional details are provided.


Fix flags, naming, and datadragon locales for Chinese Traditional and Chinese Simplifed

@dwhwang Thanks for this! You'll have to update the translate lib tests as well. :) https://github.com/dustinblackman/Championify/blob/master/tests/translate.coffee
Not sure why your htmllint is failing on CI as you didn't change any. I'll take a look in to it tonight.

My local gulp test is failing either. Here's what what I got:
app\index.html
  line 11  col 5  <title> must be present in <head> tag.


[BUG] page.offResponse doesn't work

Steps
`
Playwright playwright = Playwright.create();
BrowserType.LaunchOptions options = new BrowserType.LaunchOptions().setHeadless(false);
Browser browser = playwright.chromium().launch(options);
    BrowserContext browserContext = browser.newContext();

    Page page = browserContext.newPage();

    page.onResponse(response -> {
        System.out.println("onResponse :" + response.url());
    });

    page.navigate("https://www.google.com");
    page.waitForLoadState(LoadState.NETWORKIDLE);

    page.offResponse(r -> {
        System.out.println("remove onResponse");
    });

    page.navigate("https://www.facebook.com/");

    page.waitForLoadState(LoadState.NETWORKIDLE);

`
Expected
Do not output Facebook's response
Actual
Output Facebook's response。
[Describe actual behavior]
### Tasks

There are two different instances of the handler in your code snippet, you add one and remove the other (which has not been added so it's a no-op). You should make sure that the same handler instance is removed as was added, which can be achieved by storing it in a variable:
    Consumer<Response> responseConsumer = response -> {
        System.out.println("onResponse :" + response.url());
    });
    page.onResponse(responseConsumer);

    page.navigate("https://www.google.com");
    page.waitForLoadState(LoadState.NETWORKIDLE);

    page.offResponse(responseConsumer);


⚠ Bofrost.fr has degraded performance

In 2a4b0d2, Bofrost.fr (https://www.bofrost.fr) experienced degraded performance:

HTTP code: 200
Response time: 882 ms

Resolved: Bofrost.fr performance has improved in fe69cb6 after 6 minutes.


Automatic export does not export when a collection changes

When I add a new paper to the Library, automatic exports are triggered. But when I move an item from a collection to another collection, automatic exports involving one of the collections affected are not triggered.

Which one is not triggered? The one where the item is move to, or the one where the item is moved out of?

Both. When I move an item into a collection, or when I remove an item from a collection, that is supposed to be exported automatically, nothing happens.

I'll need you to generate a debug report, I can't replicate this on my end. When moving references, both collections are triggered for autoexport.

I will really need your help on this as I cannot reproduce it on my end.

Now it is working fine. Just like the other issue I created. Once I disabled BBT, and enabled it again, they were both fixed. I am sorry I cannot be of more help. If I find a way to reproduce it consistently I will post here. Let's not rule out the possibility that I might have messed something up or that my system had something wrong :)  I am closing this in the mean time. Thanks for the hard work on this plugin.

That's OK.


Port Open id metadata cache refresh if key is missing

Is your feature request related to a problem? Please describe.
A five day cache refresh has caused issues with bots picking up new openid metadata documents
https://github.com/microsoft/botbuilder-js/pull/2466
Describe the solution you'd like
Refresh once every 24 hours, or once an hour if a key is not found.

Duplicate of 1210


Add Opting Out / In

The later versions of Mixpanel have the ability to opt in/out of collecting data for GDPR purposes. This adds support for those as well as updating the Mixpanel library.

Can you resolve the merge conflicts? Thanks for this PR, will be nice to have it included.

@kyleclegg it looks like another PR already merged changes a while ago to add this missing functionality: https://github.com/davodesign84/react-native-mixpanel/pull/180
closing this PR

Great, thanks.


Webhooks

Description of Changes
Related Issues

Codecov Report

Merging #6 (5fc4aea) into main (cae6463) will not change coverage.
The diff coverage is 100.00%.

@@            Coverage Diff            @@
##              main        #6   +/-   ##
=========================================
  Coverage   100.00%   100.00%
=========================================
  Files           13        17    +4
  Lines           70       118   +48
  Branches         7        16    +9
=========================================
+ Hits            70       118   +48

Impacted Files
Coverage Δ

src/config.ts
100.00% <100.00%> (ø)

src/consts.ts
100.00% <100.00%> (ø)

src/index.ts
100.00% <100.00%> (ø)

src/middleware/index.ts
100.00% <100.00%> (ø)

src/middleware/validateWebhook.ts
100.00% <100.00%> (ø)

src/types/index.ts
100.00% <100.00%> (ø)

src/utils/index.ts
100.00% <100.00%> (ø)

src/utils/signatureIsValid.ts
100.00% <100.00%> (ø)

src/events/getManyEvents.ts
100.00% <0.00%> (ø)

:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more