Latest version fails (or succeeds) silently...

Running the latest version of the action v12.1815.0 with Checkov version 2.1.290, Checkov will either fail with no output or succeed with no output.
  "" "" "" "" "" "" "" "" "sarif" "" "WARNING" "" "" "" "" "" "" "" "--user 0"
2022-10-25T14:44:13.9922928Z BC_FROM_BRANCH=get_it_working
2022-10-25T14:44:13.9923421Z BC_TO_BRANCH=
2022-10-25T14:44:13.9943560Z BC_PR_ID=get_it_working
2022-10-25T14:44:13.9944472Z BC_PR_URL=https://github.com/FoxoTech/tf-privilege-escalation/pull/get_it_working
2022-10-25T14:44:13.9947753Z BC_COMMIT_HASH=99f956885233698ca257205f632254854b197946
2022-10-25T14:44:13.9948376Z BC_COMMIT_URL=https://github.com/FoxoTech/tf-privilege-escalation/commit/99f956885233698ca257205f632254854b197946
2022-10-25T14:44:13.9994901Z BC_AUTHOR_NAME=jfechner-foxo
2022-10-25T14:44:13.9995247Z BC_AUTHOR_URL=https://github.com/jfechner-foxo
2022-10-25T14:44:13.9995486Z BC_RUN_ID=22
2022-10-25T14:44:13.9995869Z BC_RUN_URL=https://github.com/FoxoTech/tf-privilege-escalation/actions/runs/3321825690
2022-10-25T14:44:13.9996334Z BC_REPOSITORY_URL=https://github.com/FoxoTech/tf-privilege-escalation
2022-10-25T14:44:13.9996633Z running checkov on directory: .
2022-10-25T14:44:13.9996932Z checkov -d .       --output sarif
2022-10-25T14:44:16.7097101Z 2022-10-25 14:44:16,709 [MainThread  ] [WARNI]  Failed to download module terraform-aws-modules/lambda/aws:4.0.1 (for external modules, the --download-external-modules flag is required)
2022-10-25T14:44:16.7103087Z 2022-10-25 14:44:16,710 [MainThread  ] [WARNI]  Failed to download module terraform-aws-modules/step-functions/aws:None (for external modules, the --download-external-modules flag is required)
2022-10-25T14:44:16.7108472Z 2022-10-25 14:44:16,710 [MainThread  ] [WARNI]  Failed to download module git@github.com:FoxoTech/tf-module-bucket.git?ref=v0.0.16:None (for external modules, the --download-external-modules flag is required)
2022-10-25T14:44:16.7113307Z 2022-10-25 14:44:16,711 [MainThread  ] [WARNI]  Failed to download module cloudposse/label/null:0.24.1 (for external modules, the --download-external-modules flag is required)

Quiet flag is not set, and even if it was, it should still show failures.
 "" "" "" "" "" "" "" "" "sarif" "" "WARNING" "" "" "" "" "" "" "" "--user 0"
2022-10-20T19:32:50.6660214Z BC_FROM_BRANCH=get_it_working
2022-10-20T19:32:50.6660478Z BC_TO_BRANCH=
2022-10-20T19:32:50.6697862Z BC_PR_ID=get_it_working
2022-10-20T19:32:50.6698544Z BC_PR_URL=https://github.com/FoxoTech/tf-privilege-escalation/pull/get_it_working
2022-10-20T19:32:50.6698941Z BC_COMMIT_HASH=b340abe8ce406a7417c2abe1c8e7c704f8d2d361
2022-10-20T19:32:50.6699503Z BC_COMMIT_URL=https://github.com/FoxoTech/tf-privilege-escalation/commit/b340abe8ce406a7417c2abe1c8e7c704f8d2d361
2022-10-20T19:32:50.6699929Z BC_AUTHOR_NAME=jfechner-foxo
2022-10-20T19:32:50.6700277Z BC_AUTHOR_URL=https://github.com/jfechner-foxo
2022-10-20T19:32:50.6700515Z BC_RUN_ID=20
2022-10-20T19:32:50.6700938Z BC_RUN_URL=https://github.com/FoxoTech/tf-privilege-escalation/actions/runs/3292387682
2022-10-20T19:32:50.6701441Z BC_REPOSITORY_URL=https://github.com/FoxoTech/tf-privilege-escalation
2022-10-20T19:32:50.6701760Z running checkov on directory: .
2022-10-20T19:32:50.6702065Z checkov -d .       --output sarif
2022-10-20T19:32:53.4663996Z 2022-10-20 19:32:53,465 [MainThread  ] [WARNI]  Failed to download module terraform-aws-modules/lambda/aws:4.0.1 (for external modules, the --download-external-modules flag is required)
2022-10-20T19:32:53.4670288Z 2022-10-20 19:32:53,466 [MainThread  ] [WARNI]  Failed to download module terraform-aws-modules/step-functions/aws:None (for external modules, the --download-external-modules flag is required)
2022-10-20T19:32:53.4676586Z 2022-10-20 19:32:53,467 [MainThread  ] [WARNI]  Failed to download module git@github.com:FoxoTech/tf-module-bucket.git?ref=v0.0.16:None (for external modules, the --download-external-modules flag is required)
2022-10-20T19:32:53.4681866Z 2022-10-20 19:32:53,467 [MainThread  ] [WARNI]  Failed to download module cloudposse/label/null:0.24.1 (for external modules, the --download-external-modules flag is required)
2022-10-20T19:32:54.6584369Z ##[warning]The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
2022-10-20T19:32:54.6610255Z
2022-10-20T19:32:54.6611721Z        _               _
2022-10-20T19:32:54.6612040Z    ___| |__   ___  ___| | _______   __
2022-10-20T19:32:54.6612713Z   / __| '_ \ / _ \/ __| |/ / _ \ \ / /
2022-10-20T19:32:54.6613032Z  | (__| | | |  __/ (__|   < (_) \ V /
2022-10-20T19:32:54.6613273Z   \___|_| |_|\___|\___|_|\_\___/ \_/
2022-10-20T19:32:54.6666542Z
2022-10-20T19:32:54.6668855Z By bridgecrew.io | version: 2.1.277
2022-10-20T19:32:54.6671716Z Update available 2.1.277 -> 2.1.280
2022-10-20T19:32:54.6673453Z Run pip3 install -U checkov to update
2022-10-20T19:32:54.6675616Z
2022-10-20T19:32:54.6676193Z terraform scan results:
2022-10-20T19:32:54.6677794Z
2022-10-20T19:32:54.6679975Z Passed checks: 49, Failed checks: 0, Skipped checks: 6
2022-10-20T19:32:54.6681174Z
2022-10-20T19:32:54.6689162Z Check: CKV_AWS_107: "Ensure IAM policies does not allow credentials exposure"
2022-10-20T19:32:54.6691431Z 	PASSED for resource: aws_iam_policy_document.cw_role_policy_doc
2022-10-20T19:32:54.6692769Z 	File: /apigateway.tf:1-16
2022-10-20T19:32:54.6694463Z 	Guide: https://docs.bridgecrew.io/docs/ensure-iam-policies-do-not-allow-credentials-exposure
2022-10-20T19:32:54.6696032Z Check: CKV_AWS_110: "Ensure IAM policies does not allow privilege escalation"
2022-10-20T19:32:54.6697311Z 	PASSED for resource: aws_iam_policy_document.cw_role_policy_doc
2022-10-20T19:32:54.6698528Z 	File: /apigateway.tf:1-16
2022-10-20T19:32:54.6699985Z 	Guide: https://docs.bridgecrew.io/docs/ensure-iam-policies-does-not-allow-privilege-escalation
2022-10-20T19:32:54.6701597Z Check: CKV_AWS_1: "Ensure IAM policies that allow full "*-*" administrative privileges are not created"
2022-10-20T19:32:54.6702923Z 	PASSED for resource: aws_iam_policy_document.cw_role_policy_doc
2022-10-20T19:32:54.6704124Z 	File: /apigateway.tf:1-16
2022-10-20T19:32:54.6705322Z 	Guide: https://docs.bridgecrew.io/docs/iam_23
2022-10-20T19:32:54.6706685Z Check: CKV_AWS_109: "Ensure IAM policies does not allow permissions management / resource exposure without constraints"
2022-10-20T19:32:54.6708081Z 	PASSED for resource: aws_iam_policy_document.cw_role_policy_doc
2022-10-20T19:32:54.6709376Z 	File: /apigateway.tf:1-16
2022-10-20T19:32:54.6710982Z 	Guide: https://docs.bridgecrew.io/docs/ensure-iam-policies-do-not-allow-permissions-management-resource-exposure-without-constraint
2022-10-20T19:32:54.6712568Z Check: CKV_AWS_108: "Ensure IAM policies does not allow data exfiltration"
2022-10-20T19:32:54.6713901Z 	PASSED for resource: aws_iam_policy_document.cw_role_policy_doc
2022-10-20T19:32:54.6715172Z 	File: /apigateway.tf:1-16
2022-10-20T19:32:54.6716552Z 	Guide: https://docs.bridgecrew.io/docs/ensure-iam-policies-do-not-allow-data-exfiltration
2022-10-20T19:32:54.6719149Z Check: CKV_AWS_111: "Ensure IAM policies does not allow write access without constraints"
2022-10-20T19:32:54.6721108Z 	PASSED for resource: aws_iam_policy_document.cw_role_policy_doc
2022-10-20T19:32:54.6722908Z 	File: /apigateway.tf:1-16
2022-10-20T19:32:54.6725115Z 	Guide: https://docs.bridgecrew.io/docs/ensure-iam-policies-do-not-allow-write-access-without-constraint
2022-10-20T19:32:54.6727340Z Check: CKV_AWS_49: "Ensure no IAM policies documents allow "*" as a statement's actions"
2022-10-20T19:32:54.6729127Z 	PASSED for resource: aws_iam_policy_document.cw_role_policy_doc
2022-10-20T19:32:54.6730947Z 	File: /apigateway.tf:1-16
2022-10-20T19:32:54.6732587Z 	Guide: https://docs.bridgecrew.io/docs/bc_aws_iam_43
2022-10-20T19:32:54.6739306Z Check: CKV_AWS_107: "Ensure IAM policies does not allow credentials exposure"
2022-10-20T19:32:54.6739970Z 	PASSED for resource: aws_iam_policy_document.cw_role_assume_role_policy
2022-10-20T19:32:54.6740461Z 	File: /apigateway.tf:34-46
2022-10-20T19:32:54.6741016Z 	Guide: https://docs.bridgecrew.io/docs/ensure-iam-policies-do-not-allow-credentials-exposure
2022-10-20T19:32:54.6741581Z Check: CKV_AWS_110: "Ensure IAM policies does not allow privilege escalation"
2022-10-20T19:32:54.6742029Z 	PASSED for resource: aws_iam_policy_document.cw_role_assume_role_policy
2022-10-20T19:32:54.6742515Z 	File: /apigateway.tf:34-46
2022-10-20T19:32:54.6743077Z 	Guide: https://docs.bridgecrew.io/docs/ensure-iam-policies-does-not-allow-privilege-escalation
2022-10-20T19:32:54.6743791Z Check: CKV_AWS_1: "Ensure IAM policies that allow full "*-*" administrative privileges are not created"
2022-10-20T19:32:54.6744270Z 	PASSED for resource: aws_iam_policy_document.cw_role_assume_role_policy
2022-10-20T19:32:54.6744739Z 	File: /apigateway.tf:34-46
2022-10-20T19:32:54.6745050Z 	Guide: https://docs.bridgecrew.io/docs/iam_23
2022-10-20T19:32:54.6745548Z Check: CKV_AWS_109: "Ensure IAM policies does not allow permissions management / resource exposure without constraints"
2022-10-20T19:32:54.6746046Z 	PASSED for resource: aws_iam_policy_document.cw_role_assume_role_policy
2022-10-20T19:32:54.6746486Z 	File: /apigateway.tf:34-46
2022-10-20T19:32:54.6747266Z 	Guide: https://docs.bridgecrew.io/docs/ensure-iam-policies-do-not-allow-permissions-management-resource-exposure-without-constraint
2022-10-20T19:32:54.6747996Z Check: CKV_AWS_108: "Ensure IAM policies does not allow data exfiltration"
2022-10-20T19:32:54.6748438Z 	PASSED for resource: aws_iam_policy_document.cw_role_assume_role_policy
2022-10-20T19:32:54.6748817Z 	File: /apigateway.tf:34-46
2022-10-20T19:32:54.6749399Z 	Guide: https://docs.bridgecrew.io/docs/ensure-iam-policies-do-not-allow-data-exfiltration
2022-10-20T19:32:54.6749986Z Check: CKV_AWS_111: "Ensure IAM policies does not allow write access without constraints"
2022-10-20T19:32:54.6750446Z 	PASSED for resource: aws_iam_policy_document.cw_role_assume_role_policy
2022-10-20T19:32:54.6750826Z 	File: /apigateway.tf:34-46
2022-10-20T19:32:54.6751472Z 	Guide: https://docs.bridgecrew.io/docs/ensure-iam-policies-do-not-allow-write-access-without-constraint
2022-10-20T19:32:54.6752207Z Check: CKV_AWS_49: "Ensure no IAM policies documents allow "*" as a statement's actions"
2022-10-20T19:32:54.6752660Z 	PASSED for resource: aws_iam_policy_document.cw_role_assume_role_policy
2022-10-20T19:32:54.6753038Z 	File: /apigateway.tf:34-46
2022-10-20T19:32:54.6753418Z 	Guide: https://docs.bridgecrew.io/docs/bc_aws_iam_43
2022-10-20T19:32:54.6753859Z Check: CKV_AWS_107: "Ensure IAM policies does not allow credentials exposure"
2022-10-20T19:32:54.6754338Z 	PASSED for resource: aws_iam_policy_document.access_log_key_policy
2022-10-20T19:32:54.6754718Z 	File: /apigateway.tf:140-173
2022-10-20T19:32:54.6755310Z 	Guide: https://docs.bridgecrew.io/docs/ensure-iam-policies-do-not-allow-credentials-exposure
2022-10-20T19:32:54.6755895Z Check: CKV_AWS_110: "Ensure IAM policies does not allow privilege escalation"
2022-10-20T19:32:54.6756286Z 	PASSED for resource: aws_iam_policy_document.access_log_key_policy
2022-10-20T19:32:54.6756752Z 	File: /apigateway.tf:140-173
2022-10-20T19:32:54.6757350Z 	Guide: https://docs.bridgecrew.io/docs/ensure-iam-policies-does-not-allow-privilege-escalation
2022-10-20T19:32:54.6758077Z Check: CKV_AWS_1: "Ensure IAM policies that allow full "*-*" administrative privileges are not created"
2022-10-20T19:32:54.6758739Z 	PASSED for resource: aws_iam_policy_document.access_log_key_policy
2022-10-20T19:32:54.6759204Z 	File: /apigateway.tf:140-173
2022-10-20T19:32:54.6759562Z 	Guide: https://docs.bridgecrew.io/docs/iam_23
2022-10-20T19:32:54.6760001Z Check: CKV_AWS_108: "Ensure IAM policies does not allow data exfiltration"
2022-10-20T19:32:54.6760388Z 	PASSED for resource: aws_iam_policy_document.access_log_key_policy
2022-10-20T19:32:54.6760817Z 	File: /apigateway.tf:140-173
2022-10-20T19:32:54.6761395Z 	Guide: https://docs.bridgecrew.io/docs/ensure-iam-policies-do-not-allow-data-exfiltration
2022-10-20T19:32:54.6762007Z Check: CKV_AWS_49: "Ensure no IAM policies documents allow "*" as a statement's actions"
2022-10-20T19:32:54.6762454Z 	PASSED for resource: aws_iam_policy_document.access_log_key_policy
2022-10-20T19:32:54.6762874Z 	File: /apigateway.tf:140-173
2022-10-20T19:32:54.6763280Z 	Guide: https://docs.bridgecrew.io/docs/bc_aws_iam_43
2022-10-20T19:32:54.6769401Z Check: CKV_AWS_63: "Ensure no IAM policies documents allow "*" as a statement's actions"
2022-10-20T19:32:54.6769858Z 	PASSED for resource: aws_iam_policy.apigw_cwl_policy
2022-10-20T19:32:54.6770330Z 	File: /apigateway.tf:18-32
2022-10-20T19:32:54.6770723Z 	Guide: https://docs.bridgecrew.io/docs/iam_48
2022-10-20T19:32:54.6771371Z Check: CKV_AWS_62: "Ensure IAM policies that allow full "*-*" administrative privileges are not created"
2022-10-20T19:32:54.6771821Z 	PASSED for resource: aws_iam_policy.apigw_cwl_policy
2022-10-20T19:32:54.6772216Z 	File: /apigateway.tf:18-32
2022-10-20T19:32:54.6772519Z 	Guide: https://docs.bridgecrew.io/docs/iam_47
2022-10-20T19:32:54.6773036Z Check: CKV_AWS_61: "Ensure AWS IAM policy does not allow assume role permission across all services"
2022-10-20T19:32:54.6774077Z 	PASSED for resource: aws_iam_role.apigw_cloudwatch_role
2022-10-20T19:32:54.6775722Z 	File: /apigateway.tf:48-61
2022-10-20T19:32:54.6776095Z 	Guide: https://docs.bridgecrew.io/docs/bc_aws_iam_45
2022-10-20T19:32:54.6776639Z Check: CKV_AWS_60: "Ensure IAM role allows only specific services or principals to assume it"
2022-10-20T19:32:54.6777095Z 	PASSED for resource: aws_iam_role.apigw_cloudwatch_role
2022-10-20T19:32:54.6777450Z 	File: /apigateway.tf:48-61
2022-10-20T19:32:54.6777812Z 	Guide: https://docs.bridgecrew.io/docs/bc_aws_iam_44
2022-10-20T19:32:54.6778273Z Check: CKV_AWS_237: "Ensure Create before destroy for API GATEWAY"
2022-10-20T19:32:54.6778718Z 	PASSED for resource: aws_api_gateway_rest_api.apigw
2022-10-20T19:32:54.6779069Z 	File: /apigateway.tf:72-89
2022-10-20T19:32:54.6779654Z 	Guide: https://docs.bridgecrew.io/docs/ensure-aws-api-gateway-enables-create-before-destroy
2022-10-20T19:32:54.6780459Z Check: CKV_AWS_59: "Ensure there is no open access to back-end resources through API"
2022-10-20T19:32:54.6780846Z 	PASSED for resource: aws_api_gateway_method.apigw
2022-10-20T19:32:54.6781314Z 	File: /apigateway.tf:103-109
2022-10-20T19:32:54.6781819Z 	Guide: https://docs.bridgecrew.io/docs/public_6-api-gateway-authorizer-set
2022-10-20T19:32:54.6782939Z Check: CKV_AWS_217: "Ensure Create before destroy for API deployments"
2022-10-20T19:32:54.6783310Z 	PASSED for resource: aws_api_gateway_deployment.apigw
2022-10-20T19:32:54.6783779Z 	File: /apigateway.tf:121-134
2022-10-20T19:32:54.6784376Z 	Guide: https://docs.bridgecrew.io/docs/ensure-aws-api-deployments-enable-create-before-destroy
2022-10-20T19:32:54.6784928Z Check: CKV_AWS_7: "Ensure rotation for customer created CMKs is enabled"
2022-10-20T19:32:54.6785288Z 	PASSED for resource: aws_kms_key.access_log_group_key
2022-10-20T19:32:54.6785692Z 	File: /apigateway.tf:175-190
2022-10-20T19:32:54.6786088Z 	Guide: https://docs.bridgecrew.io/docs/logging_8
2022-10-20T19:32:54.6786429Z Check: CKV_AWS_227: "Ensure KMS key is enabled"
2022-10-20T19:32:54.6786798Z 	PASSED for resource: aws_kms_key.access_log_group_key
2022-10-20T19:32:54.6787211Z 	File: /apigateway.tf:175-190
2022-10-20T19:32:54.6787733Z 	Guide: https://docs.bridgecrew.io/docs/ensure-aws-key-management-service-kms-key-is-enabled
2022-10-20T19:32:54.6788865Z Check: CKV_AWS_33: "Ensure KMS key policy does not contain wildcard (*) principal"
2022-10-20T19:32:54.6789289Z 	PASSED for resource: aws_kms_key.access_log_group_key
2022-10-20T19:32:54.6789727Z 	File: /apigateway.tf:175-190
2022-10-20T19:32:54.6790294Z 	Guide: https://docs.bridgecrew.io/docs/ensure-kms-key-policy-does-not-contain-wildcard-principal
2022-10-20T19:32:54.6790897Z Check: CKV_AWS_158: "Ensure that CloudWatch Log Group is encrypted by KMS"
2022-10-20T19:32:54.6791369Z 	PASSED for resource: aws_cloudwatch_log_group.apigw_access_log_group
2022-10-20T19:32:54.6791814Z 	File: /apigateway.tf:192-206
2022-10-20T19:32:54.6792397Z 	Guide: https://docs.bridgecrew.io/docs/ensure-that-cloudwatch-log-group-is-encrypted-by-kms
2022-10-20T19:32:54.6792970Z Check: CKV_AWS_66: "Ensure that CloudWatch Log Group specifies retention days"
2022-10-20T19:32:54.6793366Z 	PASSED for resource: aws_cloudwatch_log_group.apigw_access_log_group
2022-10-20T19:32:54.6793794Z 	File: /apigateway.tf:192-206
2022-10-20T19:32:54.6794171Z 	Guide: https://docs.bridgecrew.io/docs/logging_13
2022-10-20T19:32:54.6794540Z Check: CKV_AWS_76: "Ensure API Gateway has Access Logging enabled"
2022-10-20T19:32:54.6794982Z 	PASSED for resource: aws_api_gateway_stage.stage
2022-10-20T19:32:54.6795381Z 	File: /apigateway.tf:208-232
2022-10-20T19:32:54.6795750Z 	Guide: https://docs.bridgecrew.io/docs/logging_17
2022-10-20T19:32:54.6796208Z Check: CKV_AWS_73: "Ensure API Gateway has X-Ray Tracing enabled"
2022-10-20T19:32:54.6797346Z 	PASSED for resource: aws_api_gateway_stage.stage
2022-10-20T19:32:54.6803777Z 	File: /apigateway.tf:208-232
2022-10-20T19:32:54.6804142Z 	Guide: https://docs.bridgecrew.io/docs/logging_15
2022-10-20T19:32:54.6804603Z Check: CKV_AWS_120: "Ensure API Gateway caching is enabled"
2022-10-20T19:32:54.6805034Z 	PASSED for resource: aws_api_gateway_stage.stage
2022-10-20T19:32:54.6805493Z 	File: /apigateway.tf:208-232
2022-10-20T19:32:54.6805990Z 	Guide: https://docs.bridgecrew.io/docs/ensure-aws-api-gateway-caching-is-enabled
2022-10-20T19:32:54.6806520Z Check: CKV_AWS_225: "Ensure API Gateway method setting caching is enabled"
2022-10-20T19:32:54.6806938Z 	PASSED for resource: aws_api_gateway_method_settings.all
2022-10-20T19:32:54.6807313Z 	File: /apigateway.tf:273-283
2022-10-20T19:32:54.6807944Z 	Guide: https://docs.bridgecrew.io/docs/ensure-aws-api-gateway-method-settings-enable-caching
2022-10-20T19:32:54.6808615Z Check: CKV_AWS_63: "Ensure no IAM policies documents allow "*" as a statement's actions"
2022-10-20T19:32:54.6809046Z 	PASSED for resource: aws_iam_policy.assume_policy
2022-10-20T19:32:54.6809416Z 	File: /assume_policy.tf:1-30
2022-10-20T19:32:54.6809773Z 	Guide: https://docs.bridgecrew.io/docs/iam_48
2022-10-20T19:32:54.6810397Z Check: CKV_AWS_62: "Ensure IAM policies that allow full "*-*" administrative privileges are not created"
2022-10-20T19:32:54.6810847Z 	PASSED for resource: aws_iam_policy.assume_policy
2022-10-20T19:32:54.6811200Z 	File: /assume_policy.tf:1-30
2022-10-20T19:32:54.6811570Z 	Guide: https://docs.bridgecrew.io/docs/iam_47
2022-10-20T19:32:54.6812029Z Check: CKV_AWS_107: "Ensure IAM policies does not allow credentials exposure"
2022-10-20T19:32:54.6812425Z 	PASSED for resource: aws_iam_policy_document.dynamodb_key_policy
2022-10-20T19:32:54.6812837Z 	File: /dynamodb.tf:1-14
2022-10-20T19:32:54.6813430Z 	Guide: https://docs.bridgecrew.io/docs/ensure-iam-policies-do-not-allow-credentials-exposure
2022-10-20T19:32:54.6813983Z Check: CKV_AWS_110: "Ensure IAM policies does not allow privilege escalation"
2022-10-20T19:32:54.6814662Z 	PASSED for resource: aws_iam_policy_document.dynamodb_key_policy
2022-10-20T19:32:54.6815088Z 	File: /dynamodb.tf:1-14
2022-10-20T19:32:54.6815694Z 	Guide: https://docs.bridgecrew.io/docs/ensure-iam-policies-does-not-allow-privilege-escalation
2022-10-20T19:32:54.6816410Z Check: CKV_AWS_1: "Ensure IAM policies that allow full "*-*" administrative privileges are not created"
2022-10-20T19:32:54.6817019Z 	PASSED for resource: aws_iam_policy_document.dynamodb_key_policy
2022-10-20T19:32:54.6817550Z 	File: /dynamodb.tf:1-14
2022-10-20T19:32:54.6817918Z 	Guide: https://docs.bridgecrew.io/docs/iam_23
2022-10-20T19:32:54.6818302Z Check: CKV_AWS_108: "Ensure IAM policies does not allow data exfiltration"
2022-10-20T19:32:54.6818736Z 	PASSED for resource: aws_iam_policy_document.dynamodb_key_policy
2022-10-20T19:32:54.6819189Z 	File: /dynamodb.tf:1-14
2022-10-20T19:32:54.6819765Z 	Guide: https://docs.bridgecrew.io/docs/ensure-iam-policies-do-not-allow-data-exfiltration
2022-10-20T19:32:54.6820373Z Check: CKV_AWS_49: "Ensure no IAM policies documents allow "*" as a statement's actions"
2022-10-20T19:32:54.6820813Z 	PASSED for resource: aws_iam_policy_document.dynamodb_key_policy
2022-10-20T19:32:54.6821219Z 	File: /dynamodb.tf:1-14
2022-10-20T19:32:54.6821561Z 	Guide: https://docs.bridgecrew.io/docs/bc_aws_iam_43
2022-10-20T19:32:54.6822003Z Check: CKV_AWS_7: "Ensure rotation for customer created CMKs is enabled"
2022-10-20T19:32:54.6822405Z 	PASSED for resource: aws_kms_key.dynamodb_key
2022-10-20T19:32:54.6822792Z 	File: /dynamodb.tf:16-31
2022-10-20T19:32:54.6823097Z 	Guide: https://docs.bridgecrew.io/docs/logging_8
2022-10-20T19:32:54.6823535Z Check: CKV_AWS_227: "Ensure KMS key is enabled"
2022-10-20T19:32:54.6823881Z 	PASSED for resource: aws_kms_key.dynamodb_key
2022-10-20T19:32:54.6824215Z 	File: /dynamodb.tf:16-31
2022-10-20T19:32:54.6824789Z 	Guide: https://docs.bridgecrew.io/docs/ensure-aws-key-management-service-kms-key-is-enabled
2022-10-20T19:32:54.6825391Z Check: CKV_AWS_33: "Ensure KMS key policy does not contain wildcard (*) principal"
2022-10-20T19:32:54.6825805Z 	PASSED for resource: aws_kms_key.dynamodb_key
2022-10-20T19:32:54.6826136Z 	File: /dynamodb.tf:16-31
2022-10-20T19:32:54.6826735Z 	Guide: https://docs.bridgecrew.io/docs/ensure-kms-key-policy-does-not-contain-wildcard-principal
2022-10-20T19:32:54.6827329Z Check: CKV_AWS_119: "Ensure DynamoDB Tables are encrypted using a KMS Customer Managed CMK"
2022-10-20T19:32:54.6827807Z 	PASSED for resource: aws_dynamodb_table.wait_time
2022-10-20T19:32:54.6828152Z 	File: /dynamodb.tf:33-59
2022-10-20T19:32:54.6828684Z 	Guide: https://docs.bridgecrew.io/docs/ensure-that-dynamodb-tables-are-encrypted
2022-10-20T19:32:54.6829207Z Check: CKV_AWS_41: "Ensure no hard coded AWS access key and secret key exists in provider"
2022-10-20T19:32:54.6829568Z 	PASSED for resource: aws.default
2022-10-20T19:32:54.6829961Z 	File: /main.tf:20-22
2022-10-20T19:32:54.6830319Z 	Guide: https://docs.bridgecrew.io/docs/bc_aws_secrets_5
2022-10-20T19:32:54.6830777Z Check: CKV2_AWS_4: "Ensure API Gateway stage have logging level defined as appropriate"
2022-10-20T19:32:54.6831162Z 	PASSED for resource: aws_api_gateway_stage.stage
2022-10-20T19:32:54.6831604Z 	File: /apigateway.tf:208-232
2022-10-20T19:32:54.6832262Z 	Guide: https://docs.bridgecrew.io/docs/ensure-api-gateway-stage-have-logging-level-defined-as-appropiate
2022-10-20T19:32:54.6832808Z Check: CKV2_AWS_16: "Ensure that Auto Scaling is enabled on your DynamoDB tables"
2022-10-20T19:32:54.6833239Z 	PASSED for resource: aws_dynamodb_table.wait_time
2022-10-20T19:32:54.6833639Z 	File: /dynamodb.tf:33-59
2022-10-20T19:32:54.6834255Z 	Guide: https://docs.bridgecrew.io/docs/ensure-that-auto-scaling-is-enabled-on-your-dynamodb-tables
2022-10-20T19:32:54.6834838Z Check: CKV_AWS_109: "Ensure IAM policies does not allow permissions management / resource exposure without constraints"
2022-10-20T19:32:54.6835348Z 	SKIPPED for resource: aws_iam_policy_document.access_log_key_policy
2022-10-20T19:32:54.6835745Z 	Suppress comment: Honestly...WTF?
2022-10-20T19:32:54.6836160Z 	File: /apigateway.tf:140-173
2022-10-20T19:32:54.6836910Z 	Guide: https://docs.bridgecrew.io/docs/ensure-iam-policies-do-not-allow-permissions-management-resource-exposure-without-constraint
2022-10-20T19:32:54.6837645Z Check: CKV_AWS_111: "Ensure IAM policies does not allow write access without constraints"
2022-10-20T19:32:54.6838116Z 	SKIPPED for resource: aws_iam_policy_document.access_log_key_policy
2022-10-20T19:32:54.6838615Z 	Suppress comment: Honestly...WTF?
2022-10-20T19:32:54.6839037Z 	File: /apigateway.tf:140-173
2022-10-20T19:32:54.6839683Z 	Guide: https://docs.bridgecrew.io/docs/ensure-iam-policies-do-not-allow-write-access-without-constraint
2022-10-20T19:32:54.6840361Z Check: CKV_AWS_109: "Ensure IAM policies does not allow permissions management / resource exposure without constraints"
2022-10-20T19:32:54.6840808Z 	SKIPPED for resource: aws_iam_policy_document.dynamodb_key_policy
2022-10-20T19:32:54.6841185Z 	Suppress comment: Again...WTF?
2022-10-20T19:32:54.6841590Z 	File: /dynamodb.tf:1-14
2022-10-20T19:32:54.6842329Z 	Guide: https://docs.bridgecrew.io/docs/ensure-iam-policies-do-not-allow-permissions-management-resource-exposure-without-constraint
2022-10-20T19:32:54.6843089Z Check: CKV_AWS_111: "Ensure IAM policies does not allow write access without constraints"
2022-10-20T19:32:54.6843551Z 	SKIPPED for resource: aws_iam_policy_document.dynamodb_key_policy
2022-10-20T19:32:54.6843967Z 	Suppress comment: Again...WTF?
2022-10-20T19:32:54.6844293Z 	File: /dynamodb.tf:1-14
2022-10-20T19:32:54.6844935Z 	Guide: https://docs.bridgecrew.io/docs/ensure-iam-policies-do-not-allow-write-access-without-constraint
2022-10-20T19:32:54.6845520Z Check: CKV_AWS_28: "Ensure Dynamodb point in time recovery (backup) is enabled"
2022-10-20T19:32:54.6845932Z 	SKIPPED for resource: aws_dynamodb_table.wait_time
2022-10-20T19:32:54.6846292Z 	Suppress comment: Not going to do PITR for now
2022-10-20T19:32:54.6846689Z 	File: /dynamodb.tf:33-59
2022-10-20T19:32:54.6847048Z 	Guide: https://docs.bridgecrew.io/docs/general_6
2022-10-20T19:32:54.6847424Z Check: CKV2_AWS_29: "Ensure public API gateway are protected by WAF"
2022-10-20T19:32:54.6847838Z 	SKIPPED for resource: aws_api_gateway_stage.stage
2022-10-20T19:32:54.6848244Z 	Suppress comment: IDK where this even belongs
2022-10-20T19:32:54.6848650Z 	File: /apigateway.tf:208-232
2022-10-20T19:32:54.6849169Z 	Guide: https://docs.bridgecrew.io/docs/ensure-public-api-gateway-are-protected-by-waf
2022-10-20T19:32:54.6849499Z
2022-10-20T19:32:54.6849628Z secrets scan results:
2022-10-20T19:32:54.6849798Z
2022-10-20T19:32:54.6850007Z Passed checks: 0, Failed checks: 0, Skipped checks: 1
2022-10-20T19:32:54.6850234Z
2022-10-20T19:32:54.6850397Z Check: CKV_SECRET_14: "Slack Token"
2022-10-20T19:32:54.6850715Z 	SKIPPED for resource: 0934c73425323020504d743d1cf9a1c6126daefe
2022-10-20T19:32:54.6851250Z 	Suppress comment: We'll have to figure this out somewhere else or use the encryptinator
2022-10-20T19:32:54.6851729Z 	File: /send_notification_lambda.tf:33-34
2022-10-20T19:32:54.6852100Z 	Guide: https://docs.bridgecrew.io/docs/git_secrets_14
2022-10-20T19:32:54.6852342Z
2022-10-20T19:32:54.6852484Z github_actions scan results:
2022-10-20T19:32:54.6852669Z
2022-10-20T19:32:54.6852851Z Passed checks: 67, Failed checks: 0, Skipped checks: 0
2022-10-20T19:32:54.6853064Z
2022-10-20T19:32:54.6853324Z Check: CKV_GHA_6: "Found artifact build without evidence of cosign sbom attestation in pipeline"
2022-10-20T19:32:54.6853693Z 	PASSED for resource: jobs.jobs
2022-10-20T19:32:54.6856187Z 	File: /.github/workflows/root.yml:9-86
2022-10-20T19:32:54.6857107Z 	Guide: https://docs.bridgecrew.io/docs/found-artifact-build-without-evidence-of-cosign-sbom-attestation-in-pipeline
2022-10-20T19:32:54.6857752Z Check: CKV_GHA_3: "Suspicious use of curl with secrets"
2022-10-20T19:32:54.6858060Z 	PASSED for resource: jobs.yor
2022-10-20T19:32:54.6858538Z 	File: /.github/workflows/root.yml:10-31
2022-10-20T19:32:54.6859085Z 	Guide: https://docs.bridgecrew.io/docs/suspicious-use-of-curl-with-secrets
2022-10-20T19:32:54.7057932Z Check: CKV_GHA_3: "Suspicious use of curl with secrets"
2022-10-20T19:32:54.7058370Z 	PASSED for resource: jobs.checkov
2022-10-20T19:32:54.7058838Z 	File: /.github/workflows/root.yml:31-45
2022-10-20T19:32:54.7059323Z 	Guide: https://docs.bridgecrew.io/docs/suspicious-use-of-curl-with-secrets
2022-10-20T19:32:54.7059757Z Check: CKV_GHA_3: "Suspicious use of curl with secrets"
2022-10-20T19:32:54.7060342Z 	PASSED for resource: jobs.terraform
2022-10-20T19:32:54.7060679Z 	File: /.github/workflows/root.yml:45-86
2022-10-20T19:32:54.7061124Z 	Guide: https://docs.bridgecrew.io/docs/suspicious-use-of-curl-with-secrets
2022-10-20T19:32:54.7061538Z Check: CKV_GHA_2: "Ensure run commands are not vulnerable to shell injection"
2022-10-20T19:32:54.7061827Z 	PASSED for resource: jobs.yor
2022-10-20T19:32:54.7062140Z 	File: /.github/workflows/root.yml:10-31
2022-10-20T19:32:54.7062672Z 	Guide: https://docs.bridgecrew.io/docs/ensure-run-commands-are-not-vulnerable-to-shell-injection
2022-10-20T19:32:54.7063144Z Check: CKV_GHA_2: "Ensure run commands are not vulnerable to shell injection"
2022-10-20T19:32:54.7063448Z 	PASSED for resource: jobs.checkov
2022-10-20T19:32:54.7063762Z 	File: /.github/workflows/root.yml:31-45
2022-10-20T19:32:54.7064277Z 	Guide: https://docs.bridgecrew.io/docs/ensure-run-commands-are-not-vulnerable-to-shell-injection
2022-10-20T19:32:54.7064768Z Check: CKV_GHA_2: "Ensure run commands are not vulnerable to shell injection"
2022-10-20T19:32:54.7065080Z 	PASSED for resource: jobs.terraform
2022-10-20T19:32:54.7065441Z 	File: /.github/workflows/root.yml:45-86
2022-10-20T19:32:54.7065964Z 	Guide: https://docs.bridgecrew.io/docs/ensure-run-commands-are-not-vulnerable-to-shell-injection
2022-10-20T19:32:54.7066481Z Check: CKV_GHA_5: "Found artifact build without evidence of cosign sign execution in pipeline"
2022-10-20T19:32:54.7066818Z 	PASSED for resource: jobs.jobs
2022-10-20T19:32:54.7067141Z 	File: /.github/workflows/root.yml:9-86
2022-10-20T19:32:54.7067531Z 	Guide: https://docs.bridgecrew.io/docs/no-evidence-of-signing
2022-10-20T19:32:54.7067899Z Check: CKV_GHA_4: "Suspicious use of netcat with IP address"
2022-10-20T19:32:54.7068189Z 	PASSED for resource: jobs.yor
2022-10-20T19:32:54.7068499Z 	File: /.github/workflows/root.yml:10-31
2022-10-20T19:32:54.7068970Z 	Guide: https://docs.bridgecrew.io/docs/suspicious-use-of-netcat-with-ip-address
2022-10-20T19:32:54.7069382Z Check: CKV_GHA_4: "Suspicious use of netcat with IP address"
2022-10-20T19:32:54.7069673Z 	PASSED for resource: jobs.checkov
2022-10-20T19:32:54.7069980Z 	File: /.github/workflows/root.yml:31-45
2022-10-20T19:32:54.7070446Z 	Guide: https://docs.bridgecrew.io/docs/suspicious-use-of-netcat-with-ip-address
2022-10-20T19:32:54.7070858Z Check: CKV_GHA_4: "Suspicious use of netcat with IP address"
2022-10-20T19:32:54.7071137Z 	PASSED for resource: jobs.terraform
2022-10-20T19:32:54.7071463Z 	File: /.github/workflows/root.yml:45-86
2022-10-20T19:32:54.7071928Z 	Guide: https://docs.bridgecrew.io/docs/suspicious-use-of-netcat-with-ip-address
2022-10-20T19:32:54.7072487Z Check: CKV_GHA_1: "Ensure ACTIONS_ALLOW_UNSECURE_COMMANDS isn't true on environment variables"
2022-10-20T19:32:54.7072804Z 	PASSED for resource: jobs.yor
2022-10-20T19:32:54.7073122Z 	File: /.github/workflows/root.yml:10-31
2022-10-20T19:32:54.7073674Z 	Guide: https://docs.bridgecrew.io/docs/ensure-actions_allow_unsecure_commands-isnt-true-on-environment-variables
2022-10-20T19:32:54.7074296Z Check: CKV_GHA_1: "Ensure ACTIONS_ALLOW_UNSECURE_COMMANDS isn't true on environment variables"
2022-10-20T19:32:54.7074617Z 	PASSED for resource: jobs.checkov
2022-10-20T19:32:54.7074940Z 	File: /.github/workflows/root.yml:31-45
2022-10-20T19:32:54.7075487Z 	Guide: https://docs.bridgecrew.io/docs/ensure-actions_allow_unsecure_commands-isnt-true-on-environment-variables
2022-10-20T19:32:54.7076090Z Check: CKV_GHA_1: "Ensure ACTIONS_ALLOW_UNSECURE_COMMANDS isn't true on environment variables"
2022-10-20T19:32:54.7076414Z 	PASSED for resource: jobs.terraform
2022-10-20T19:32:54.7076743Z 	File: /.github/workflows/root.yml:45-86
2022-10-20T19:32:54.7077285Z 	Guide: https://docs.bridgecrew.io/docs/ensure-actions_allow_unsecure_commands-isnt-true-on-environment-variables
2022-10-20T19:32:54.7078097Z Check: CKV_GHA_7: "The build output cannot be affected by user parameters other than the build entry point and the top-level source location. GitHub Actions workflow_dispatch inputs MUST be empty. "
2022-10-20T19:32:54.7078674Z 	PASSED for resource: jobs.on
2022-10-20T19:32:54.7078970Z 	File: /.github/workflows/root.yml:2-5
2022-10-20T19:32:54.7080160Z 	Guide: https://docs.bridgecrew.io/docs/the-build-output-cannot-be-affected-by-user-parameters-other-than-the-build-entry-point-and-the-top-level-source-location-github-actions-workflow_dispatch-inputs-must-be-empty
2022-10-20T19:32:54.7081159Z Check: CKV_GHA_3: "Suspicious use of curl with secrets"
2022-10-20T19:32:54.7081477Z 	PASSED for resource: jobs.yor.steps.actions/checkout@v2
2022-10-20T19:32:54.7081843Z 	File: /.github/workflows/root.yml:13-17
2022-10-20T19:32:54.7082292Z 	Guide: https://docs.bridgecrew.io/docs/suspicious-use-of-curl-with-secrets
2022-10-20T19:32:54.7082665Z Check: CKV_GHA_3: "Suspicious use of curl with secrets"
2022-10-20T19:32:54.7082983Z 	PASSED for resource: jobs.yor.steps.Setup Terraform
2022-10-20T19:32:54.7083342Z 	File: /.github/workflows/root.yml:16-20
2022-10-20T19:32:54.7083781Z 	Guide: https://docs.bridgecrew.io/docs/suspicious-use-of-curl-with-secrets
2022-10-20T19:32:54.7084165Z Check: CKV_GHA_3: "Suspicious use of curl with secrets"
2022-10-20T19:32:54.7084485Z 	PASSED for resource: jobs.yor.steps.Terraform init
2022-10-20T19:32:54.7084843Z 	File: /.github/workflows/root.yml:19-28
2022-10-20T19:32:54.7085274Z 	Guide: https://docs.bridgecrew.io/docs/suspicious-use-of-curl-with-secrets
2022-10-20T19:32:54.7085660Z Check: CKV_GHA_3: "Suspicious use of curl with secrets"
2022-10-20T19:32:54.7085962Z 	PASSED for resource: jobs.yor.steps.Run yor
2022-10-20T19:32:54.7086302Z 	File: /.github/workflows/root.yml:27-31
2022-10-20T19:32:54.7086731Z 	Guide: https://docs.bridgecrew.io/docs/suspicious-use-of-curl-with-secrets
2022-10-20T19:32:54.7087108Z Check: CKV_GHA_3: "Suspicious use of curl with secrets"
2022-10-20T19:32:54.7087423Z 	PASSED for resource: jobs.checkov.steps.Checkout
2022-10-20T19:32:54.7087763Z 	File: /.github/workflows/root.yml:35-39
2022-10-20T19:32:54.7088213Z 	Guide: https://docs.bridgecrew.io/docs/suspicious-use-of-curl-with-secrets
2022-10-20T19:32:54.7088599Z Check: CKV_GHA_3: "Suspicious use of curl with secrets"
2022-10-20T19:32:54.7088915Z 	PASSED for resource: jobs.checkov.steps.Run Checkov
2022-10-20T19:32:54.7089254Z 	File: /.github/workflows/root.yml:38-45
2022-10-20T19:32:54.7089695Z 	Guide: https://docs.bridgecrew.io/docs/suspicious-use-of-curl-with-secrets
2022-10-20T19:32:54.7090071Z Check: CKV_GHA_3: "Suspicious use of curl with secrets"
2022-10-20T19:32:54.7090375Z 	PASSED for resource: jobs.terraform.steps.Checkout
2022-10-20T19:32:54.7090735Z 	File: /.github/workflows/root.yml:49-53
2022-10-20T19:32:54.7091180Z 	Guide: https://docs.bridgecrew.io/docs/suspicious-use-of-curl-with-secrets
2022-10-20T19:32:54.7091556Z Check: CKV_GHA_3: "Suspicious use of curl with secrets"
2022-10-20T19:32:54.7091873Z 	PASSED for resource: jobs.terraform.steps.AWS Credentials
2022-10-20T19:32:54.7092236Z 	File: /.github/workflows/root.yml:52-59
2022-10-20T19:32:54.7092685Z 	Guide: https://docs.bridgecrew.io/docs/suspicious-use-of-curl-with-secrets
2022-10-20T19:32:54.7093047Z Check: CKV_GHA_3: "Suspicious use of curl with secrets"
2022-10-20T19:32:54.7093380Z 	PASSED for resource: jobs.terraform.steps.Setup Terraform
2022-10-20T19:32:54.7093746Z 	File: /.github/workflows/root.yml:58-62
2022-10-20T19:32:54.7094359Z 	Guide: https://docs.bridgecrew.io/docs/suspicious-use-of-curl-with-secrets
2022-10-20T19:32:54.7094736Z Check: CKV_GHA_3: "Suspicious use of curl with secrets"
2022-10-20T19:32:54.7095071Z 	PASSED for resource: jobs.terraform.steps.Terraform init
2022-10-20T19:32:54.7095447Z 	File: /.github/workflows/root.yml:61-70
2022-10-20T19:32:54.7095974Z 	Guide: https://docs.bridgecrew.io/docs/suspicious-use-of-curl-with-secrets
2022-10-20T19:32:54.7096416Z Check: CKV_GHA_3: "Suspicious use of curl with secrets"
2022-10-20T19:32:54.7096802Z 	PASSED for resource: jobs.terraform.steps.Terraform formatting check
2022-10-20T19:32:54.7097192Z 	File: /.github/workflows/root.yml:69-73
2022-10-20T19:32:54.7097800Z 	Guide: https://docs.bridgecrew.io/docs/suspicious-use-of-curl-with-secrets
2022-10-20T19:32:54.7098184Z Check: CKV_GHA_3: "Suspicious use of curl with secrets"
2022-10-20T19:32:54.7098528Z 	PASSED for resource: jobs.terraform.steps.Terraform validation
2022-10-20T19:32:54.7098896Z 	File: /.github/workflows/root.yml:72-81
2022-10-20T19:32:54.7099333Z 	Guide: https://docs.bridgecrew.io/docs/suspicious-use-of-curl-with-secrets
2022-10-20T19:32:54.7099708Z Check: CKV_GHA_3: "Suspicious use of curl with secrets"
2022-10-20T19:32:54.7100046Z 	PASSED for resource: jobs.terraform.steps.Terraform apply
2022-10-20T19:32:54.7100408Z 	File: /.github/workflows/root.yml:80-86
2022-10-20T19:32:54.7100843Z 	Guide: https://docs.bridgecrew.io/docs/suspicious-use-of-curl-with-secrets
2022-10-20T19:32:54.7101257Z Check: CKV_GHA_2: "Ensure run commands are not vulnerable to shell injection"
2022-10-20T19:32:54.7101613Z 	PASSED for resource: jobs.yor.steps.actions/checkout@v2
2022-10-20T19:32:54.7101962Z 	File: /.github/workflows/root.yml:13-17
2022-10-20T19:32:54.7102492Z 	Guide: https://docs.bridgecrew.io/docs/ensure-run-commands-are-not-vulnerable-to-shell-injection
2022-10-20T19:32:54.7102967Z Check: CKV_GHA_2: "Ensure run commands are not vulnerable to shell injection"
2022-10-20T19:32:54.7103301Z 	PASSED for resource: jobs.yor.steps.Setup Terraform
2022-10-20T19:32:54.7103659Z 	File: /.github/workflows/root.yml:16-20
2022-10-20T19:32:54.7104196Z 	Guide: https://docs.bridgecrew.io/docs/ensure-run-commands-are-not-vulnerable-to-shell-injection
2022-10-20T19:32:54.7104676Z Check: CKV_GHA_2: "Ensure run commands are not vulnerable to shell injection"
2022-10-20T19:32:54.7105008Z 	PASSED for resource: jobs.yor.steps.Terraform init
2022-10-20T19:32:54.7105368Z 	File: /.github/workflows/root.yml:19-28
2022-10-20T19:32:54.7105904Z 	Guide: https://docs.bridgecrew.io/docs/ensure-run-commands-are-not-vulnerable-to-shell-injection
2022-10-20T19:32:54.7106389Z Check: CKV_GHA_2: "Ensure run commands are not vulnerable to shell injection"
2022-10-20T19:32:54.7106713Z 	PASSED for resource: jobs.yor.steps.Run yor
2022-10-20T19:32:54.7107053Z 	File: /.github/workflows/root.yml:27-31
2022-10-20T19:32:54.7107588Z 	Guide: https://docs.bridgecrew.io/docs/ensure-run-commands-are-not-vulnerable-to-shell-injection
2022-10-20T19:32:54.7108051Z Check: CKV_GHA_2: "Ensure run commands are not vulnerable to shell injection"
2022-10-20T19:32:54.7108394Z 	PASSED for resource: jobs.checkov.steps.Checkout
2022-10-20T19:32:54.7108748Z 	File: /.github/workflows/root.yml:35-39
2022-10-20T19:32:54.7109274Z 	Guide: https://docs.bridgecrew.io/docs/ensure-run-commands-are-not-vulnerable-to-shell-injection
2022-10-20T19:32:54.7109735Z Check: CKV_GHA_2: "Ensure run commands are not vulnerable to shell injection"
2022-10-20T19:32:54.7110084Z 	PASSED for resource: jobs.checkov.steps.Run Checkov
2022-10-20T19:32:54.7110438Z 	File: /.github/workflows/root.yml:38-45
2022-10-20T19:32:54.7110956Z 	Guide: https://docs.bridgecrew.io/docs/ensure-run-commands-are-not-vulnerable-to-shell-injection
2022-10-20T19:32:54.7111435Z Check: CKV_GHA_2: "Ensure run commands are not vulnerable to shell injection"
2022-10-20T19:32:54.7111916Z 	PASSED for resource: jobs.terraform.steps.Checkout
2022-10-20T19:32:54.7112340Z 	File: /.github/workflows/root.yml:49-53
2022-10-20T19:32:54.7112857Z 	Guide: https://docs.bridgecrew.io/docs/ensure-run-commands-are-not-vulnerable-to-shell-injection
2022-10-20T19:32:54.7113335Z Check: CKV_GHA_2: "Ensure run commands are not vulnerable to shell injection"
2022-10-20T19:32:54.7113700Z 	PASSED for resource: jobs.terraform.steps.AWS Credentials
2022-10-20T19:32:54.7114070Z 	File: /.github/workflows/root.yml:52-59
2022-10-20T19:32:54.7114589Z 	Guide: https://docs.bridgecrew.io/docs/ensure-run-commands-are-not-vulnerable-to-shell-injection
2022-10-20T19:32:54.7115064Z Check: CKV_GHA_2: "Ensure run commands are not vulnerable to shell injection"
2022-10-20T19:32:54.7115427Z 	PASSED for resource: jobs.terraform.steps.Setup Terraform
2022-10-20T19:32:54.7115891Z 	File: /.github/workflows/root.yml:58-62
2022-10-20T19:32:54.7116570Z 	Guide: https://docs.bridgecrew.io/docs/ensure-run-commands-are-not-vulnerable-to-shell-injection
2022-10-20T19:32:54.7117064Z Check: CKV_GHA_2: "Ensure run commands are not vulnerable to shell injection"
2022-10-20T19:32:54.7117432Z 	PASSED for resource: jobs.terraform.steps.Terraform init
2022-10-20T19:32:54.7117796Z 	File: /.github/workflows/root.yml:61-70
2022-10-20T19:32:54.7118333Z 	Guide: https://docs.bridgecrew.io/docs/ensure-run-commands-are-not-vulnerable-to-shell-injection
2022-10-20T19:32:54.7118811Z Check: CKV_GHA_2: "Ensure run commands are not vulnerable to shell injection"
2022-10-20T19:32:54.7119195Z 	PASSED for resource: jobs.terraform.steps.Terraform formatting check
2022-10-20T19:32:54.7119571Z 	File: /.github/workflows/root.yml:69-73
2022-10-20T19:32:54.7120105Z 	Guide: https://docs.bridgecrew.io/docs/ensure-run-commands-are-not-vulnerable-to-shell-injection
2022-10-20T19:32:54.7120583Z Check: CKV_GHA_2: "Ensure run commands are not vulnerable to shell injection"
2022-10-20T19:32:54.7120956Z 	PASSED for resource: jobs.terraform.steps.Terraform validation
2022-10-20T19:32:54.7121325Z 	File: /.github/workflows/root.yml:72-81
2022-10-20T19:32:54.7121857Z 	Guide: https://docs.bridgecrew.io/docs/ensure-run-commands-are-not-vulnerable-to-shell-injection
2022-10-20T19:32:54.7122337Z Check: CKV_GHA_2: "Ensure run commands are not vulnerable to shell injection"
2022-10-20T19:32:54.7122702Z 	PASSED for resource: jobs.terraform.steps.Terraform apply
2022-10-20T19:32:54.7123370Z 	File: /.github/workflows/root.yml:80-86
2022-10-20T19:32:54.7123913Z 	Guide: https://docs.bridgecrew.io/docs/ensure-run-commands-are-not-vulnerable-to-shell-injection
2022-10-20T19:32:54.7124385Z Check: CKV_GHA_4: "Suspicious use of netcat with IP address"
2022-10-20T19:32:54.7124705Z 	PASSED for resource: jobs.yor.steps.actions/checkout@v2
2022-10-20T19:32:54.7125065Z 	File: /.github/workflows/root.yml:13-17
2022-10-20T19:32:54.7125539Z 	Guide: https://docs.bridgecrew.io/docs/suspicious-use-of-netcat-with-ip-address
2022-10-20T19:32:54.7125952Z Check: CKV_GHA_4: "Suspicious use of netcat with IP address"
2022-10-20T19:32:54.7126262Z 	PASSED for resource: jobs.yor.steps.Setup Terraform
2022-10-20T19:32:54.7126614Z 	File: /.github/workflows/root.yml:16-20
2022-10-20T19:32:54.7127075Z 	Guide: https://docs.bridgecrew.io/docs/suspicious-use-of-netcat-with-ip-address
2022-10-20T19:32:54.7127461Z Check: CKV_GHA_4: "Suspicious use of netcat with IP address"
2022-10-20T19:32:54.7127782Z 	PASSED for resource: jobs.yor.steps.Terraform init
2022-10-20T19:32:54.7128136Z 	File: /.github/workflows/root.yml:19-28
2022-10-20T19:32:54.7128585Z 	Guide: https://docs.bridgecrew.io/docs/suspicious-use-of-netcat-with-ip-address
2022-10-20T19:32:54.7128962Z Check: CKV_GHA_4: "Suspicious use of netcat with IP address"
2022-10-20T19:32:54.7129267Z 	PASSED for resource: jobs.yor.steps.Run yor
2022-10-20T19:32:54.7129604Z 	File: /.github/workflows/root.yml:27-31
2022-10-20T19:32:54.7130054Z 	Guide: https://docs.bridgecrew.io/docs/suspicious-use-of-netcat-with-ip-address
2022-10-20T19:32:54.7130442Z Check: CKV_GHA_4: "Suspicious use of netcat with IP address"
2022-10-20T19:32:54.7130746Z 	PASSED for resource: jobs.checkov.steps.Checkout
2022-10-20T19:32:54.7131091Z 	File: /.github/workflows/root.yml:35-39
2022-10-20T19:32:54.7131532Z 	Guide: https://docs.bridgecrew.io/docs/suspicious-use-of-netcat-with-ip-address
2022-10-20T19:32:54.7131912Z Check: CKV_GHA_4: "Suspicious use of netcat with IP address"
2022-10-20T19:32:54.7132217Z 	PASSED for resource: jobs.checkov.steps.Run Checkov
2022-10-20T19:32:54.7132549Z 	File: /.github/workflows/root.yml:38-45
2022-10-20T19:32:54.7133008Z 	Guide: https://docs.bridgecrew.io/docs/suspicious-use-of-netcat-with-ip-address
2022-10-20T19:32:54.7133396Z Check: CKV_GHA_4: "Suspicious use of netcat with IP address"
2022-10-20T19:32:54.7133711Z 	PASSED for resource: jobs.terraform.steps.Checkout
2022-10-20T19:32:54.7134048Z 	File: /.github/workflows/root.yml:49-53
2022-10-20T19:32:54.7134786Z 	Guide: https://docs.bridgecrew.io/docs/suspicious-use-of-netcat-with-ip-address
2022-10-20T19:32:54.7135184Z Check: CKV_GHA_4: "Suspicious use of netcat with IP address"
2022-10-20T19:32:54.7135519Z 	PASSED for resource: jobs.terraform.steps.AWS Credentials
2022-10-20T19:32:54.7135873Z 	File: /.github/workflows/root.yml:52-59
2022-10-20T19:32:54.7136336Z 	Guide: https://docs.bridgecrew.io/docs/suspicious-use-of-netcat-with-ip-address
2022-10-20T19:32:54.7136736Z Check: CKV_GHA_4: "Suspicious use of netcat with IP address"
2022-10-20T19:32:54.7137056Z 	PASSED for resource: jobs.terraform.steps.Setup Terraform
2022-10-20T19:32:54.7137425Z 	File: /.github/workflows/root.yml:58-62
2022-10-20T19:32:54.7137884Z 	Guide: https://docs.bridgecrew.io/docs/suspicious-use-of-netcat-with-ip-address
2022-10-20T19:32:54.7138284Z Check: CKV_GHA_4: "Suspicious use of netcat with IP address"
2022-10-20T19:32:54.7138608Z 	PASSED for resource: jobs.terraform.steps.Terraform init
2022-10-20T19:32:54.7138980Z 	File: /.github/workflows/root.yml:61-70
2022-10-20T19:32:54.7139441Z 	Guide: https://docs.bridgecrew.io/docs/suspicious-use-of-netcat-with-ip-address
2022-10-20T19:32:54.7139831Z Check: CKV_GHA_4: "Suspicious use of netcat with IP address"
2022-10-20T19:32:54.7140187Z 	PASSED for resource: jobs.terraform.steps.Terraform formatting check
2022-10-20T19:32:54.7140568Z 	File: /.github/workflows/root.yml:69-73
2022-10-20T19:32:54.7141027Z 	Guide: https://docs.bridgecrew.io/docs/suspicious-use-of-netcat-with-ip-address
2022-10-20T19:32:54.7141411Z Check: CKV_GHA_4: "Suspicious use of netcat with IP address"
2022-10-20T19:32:54.7141756Z 	PASSED for resource: jobs.terraform.steps.Terraform validation
2022-10-20T19:32:54.7142131Z 	File: /.github/workflows/root.yml:72-81
2022-10-20T19:32:54.7142576Z 	Guide: https://docs.bridgecrew.io/docs/suspicious-use-of-netcat-with-ip-address
2022-10-20T19:32:54.7142976Z Check: CKV_GHA_4: "Suspicious use of netcat with IP address"
2022-10-20T19:32:54.7143320Z 	PASSED for resource: jobs.terraform.steps.Terraform apply
2022-10-20T19:32:54.7143691Z 	File: /.github/workflows/root.yml:80-86
2022-10-20T19:32:54.7144136Z 	Guide: https://docs.bridgecrew.io/docs/suspicious-use-of-netcat-with-ip-address
2022-10-20T19:32:54.7144692Z Check: CKV_GHA_1: "Ensure ACTIONS_ALLOW_UNSECURE_COMMANDS isn't true on environment variables"
2022-10-20T19:32:54.7145070Z 	PASSED for resource: jobs.yor.steps.actions/checkout@v2
2022-10-20T19:32:54.7145554Z 	File: /.github/workflows/root.yml:13-17
2022-10-20T19:32:54.7146096Z 	Guide: https://docs.bridgecrew.io/docs/ensure-actions_allow_unsecure_commands-isnt-true-on-environment-variables
2022-10-20T19:32:54.7146705Z Check: CKV_GHA_1: "Ensure ACTIONS_ALLOW_UNSECURE_COMMANDS isn't true on environment variables"
2022-10-20T19:32:54.7147081Z 	PASSED for resource: jobs.yor.steps.Setup Terraform
2022-10-20T19:32:54.7147423Z 	File: /.github/workflows/root.yml:16-20
2022-10-20T19:32:54.7147966Z 	Guide: https://docs.bridgecrew.io/docs/ensure-actions_allow_unsecure_commands-isnt-true-on-environment-variables
2022-10-20T19:32:54.7148577Z Check: CKV_GHA_1: "Ensure ACTIONS_ALLOW_UNSECURE_COMMANDS isn't true on environment variables"
2022-10-20T19:32:54.7148949Z 	PASSED for resource: jobs.yor.steps.Terraform init
2022-10-20T19:32:54.7149292Z 	File: /.github/workflows/root.yml:19-28
2022-10-20T19:32:54.7149837Z 	Guide: https://docs.bridgecrew.io/docs/ensure-actions_allow_unsecure_commands-isnt-true-on-environment-variables
2022-10-20T19:32:54.7150434Z Check: CKV_GHA_1: "Ensure ACTIONS_ALLOW_UNSECURE_COMMANDS isn't true on environment variables"
2022-10-20T19:32:54.7150788Z 	PASSED for resource: jobs.yor.steps.Run yor
2022-10-20T19:32:54.7151115Z 	File: /.github/workflows/root.yml:27-31
2022-10-20T19:32:54.7151653Z 	Guide: https://docs.bridgecrew.io/docs/ensure-actions_allow_unsecure_commands-isnt-true-on-environment-variables
2022-10-20T19:32:54.7152242Z Check: CKV_GHA_1: "Ensure ACTIONS_ALLOW_UNSECURE_COMMANDS isn't true on environment variables"
2022-10-20T19:32:54.7152698Z 	PASSED for resource: jobs.checkov.steps.Checkout
2022-10-20T19:32:54.7153114Z 	File: /.github/workflows/root.yml:35-39
2022-10-20T19:32:54.7153657Z 	Guide: https://docs.bridgecrew.io/docs/ensure-actions_allow_unsecure_commands-isnt-true-on-environment-variables
2022-10-20T19:32:54.7154253Z Check: CKV_GHA_1: "Ensure ACTIONS_ALLOW_UNSECURE_COMMANDS isn't true on environment variables"
2022-10-20T19:32:54.7154612Z 	PASSED for resource: jobs.checkov.steps.Run Checkov
2022-10-20T19:32:54.7154944Z 	File: /.github/workflows/root.yml:38-45
2022-10-20T19:32:54.7155474Z 	Guide: https://docs.bridgecrew.io/docs/ensure-actions_allow_unsecure_commands-isnt-true-on-environment-variables
2022-10-20T19:32:54.7156058Z Check: CKV_GHA_1: "Ensure ACTIONS_ALLOW_UNSECURE_COMMANDS isn't true on environment variables"
2022-10-20T19:32:54.7156410Z 	PASSED for resource: jobs.terraform.steps.Checkout
2022-10-20T19:32:54.7156761Z 	File: /.github/workflows/root.yml:49-53
2022-10-20T19:32:54.7157298Z 	Guide: https://docs.bridgecrew.io/docs/ensure-actions_allow_unsecure_commands-isnt-true-on-environment-variables
2022-10-20T19:32:54.7157894Z Check: CKV_GHA_1: "Ensure ACTIONS_ALLOW_UNSECURE_COMMANDS isn't true on environment variables"
2022-10-20T19:32:54.7158261Z 	PASSED for resource: jobs.terraform.steps.AWS Credentials
2022-10-20T19:32:54.7158624Z 	File: /.github/workflows/root.yml:52-59
2022-10-20T19:32:54.7159164Z 	Guide: https://docs.bridgecrew.io/docs/ensure-actions_allow_unsecure_commands-isnt-true-on-environment-variables
2022-10-20T19:32:54.7159762Z Check: CKV_GHA_1: "Ensure ACTIONS_ALLOW_UNSECURE_COMMANDS isn't true on environment variables"
2022-10-20T19:32:54.7160130Z 	PASSED for resource: jobs.terraform.steps.Setup Terraform
2022-10-20T19:32:54.7160494Z 	File: /.github/workflows/root.yml:58-62
2022-10-20T19:32:54.7161031Z 	Guide: https://docs.bridgecrew.io/docs/ensure-actions_allow_unsecure_commands-isnt-true-on-environment-variables
2022-10-20T19:32:54.7161623Z Check: CKV_GHA_1: "Ensure ACTIONS_ALLOW_UNSECURE_COMMANDS isn't true on environment variables"
2022-10-20T19:32:54.7161997Z 	PASSED for resource: jobs.terraform.steps.Terraform init
2022-10-20T19:32:54.7162366Z 	File: /.github/workflows/root.yml:61-70
2022-10-20T19:32:54.7162905Z 	Guide: https://docs.bridgecrew.io/docs/ensure-actions_allow_unsecure_commands-isnt-true-on-environment-variables
2022-10-20T19:32:54.7163490Z Check: CKV_GHA_1: "Ensure ACTIONS_ALLOW_UNSECURE_COMMANDS isn't true on environment variables"
2022-10-20T19:32:54.7163889Z 	PASSED for resource: jobs.terraform.steps.Terraform formatting check
2022-10-20T19:32:54.7164276Z 	File: /.github/workflows/root.yml:69-73
2022-10-20T19:32:54.7164814Z 	Guide: https://docs.bridgecrew.io/docs/ensure-actions_allow_unsecure_commands-isnt-true-on-environment-variables
2022-10-20T19:32:54.7165427Z Check: CKV_GHA_1: "Ensure ACTIONS_ALLOW_UNSECURE_COMMANDS isn't true on environment variables"
2022-10-20T19:32:54.7165820Z 	PASSED for resource: jobs.terraform.steps.Terraform validation
2022-10-20T19:32:54.7166207Z 	File: /.github/workflows/root.yml:72-81
2022-10-20T19:32:54.7166755Z 	Guide: https://docs.bridgecrew.io/docs/ensure-actions_allow_unsecure_commands-isnt-true-on-environment-variables
2022-10-20T19:32:54.7167345Z Check: CKV_GHA_1: "Ensure ACTIONS_ALLOW_UNSECURE_COMMANDS isn't true on environment variables"
2022-10-20T19:32:54.7167735Z 	PASSED for resource: jobs.terraform.steps.Terraform apply
2022-10-20T19:32:54.7168113Z 	File: /.github/workflows/root.yml:80-86
2022-10-20T19:32:54.7168648Z 	Guide: https://docs.bridgecrew.io/docs/ensure-actions_allow_unsecure_commands-isnt-true-on-environment-variables
2022-10-20T19:32:54.7168935Z
2022-10-20T19:32:54.7168941Z
2022-10-20T19:32:54.7169162Z Wrote output in SARIF format to the file 'results.sarif'
2022-10-20T19:32:54.8062079Z Post job cleanup.

I've pinned the version to https://github.com/bridgecrewio/checkov-action/releases/tag/v12.1810.0 and that seems to have resolved it.

I experience the same. In my case the Checkov GHA executes twice, displaying same results.

hey @jfechner-foxo thanks for reaching out. This seems to be a side-effect of resolving the deprecation issue. the result can be found currently in the GitHub output, but my fix will also bring it back to the console.

hi @gruebel , what is the git sha or tag for the action that includes this change?


Contradiction in license Element Description for MappingSet Class

In the description of the license element on https://mapping-commons.github.io/sssom/license/, it is stated as an optional element. However, in the "Induced" section at the bottom of https://mapping-commons.github.io/sssom/MappingSet/, the required property of the license element is set to true.

@ruihuang19 thank you for the issue!
@sujaypatil96 I will need your help for this.
In my template I use
{% for c in gen.all_class_objects()|sort(attribute=sort_by) -%}
{% if c.name == "mapping set" %}
{{gen.link(c)}}: {{c.description|enshorten}}

| Column/Field       | Description                                             | Required    |
|--------------------|---------------------------------------------------------|-------------|
{%- for slot in c.slots %}
{%- set slot_info = schemaview.get_slot(slot) %}
| **{{ gen.link(slot) }}**     | {{ slot_info.description | default("No description") }} | {% if slot_info.required | default(false) %}Required{% elif slot_info.recommended | default(false) %}Recommended{% else %}Optional{% endif %} |
{%- endfor %}
{%- endif %}
{%- endfor %}

To show a row in the overall table. schemaview.get_slot(slot) retrieves the general information about the slot, but I want to know the information about the slot in the context for c. So license is not required in general, but in the context of the mapping set class, it is.


Provide more infos about the profiles in the overview

When hovering over the images it would be nice to see all the tags of that profile on the index page.

https://github.com/rubymonsters/speakerinnen_liste/pull/512


Chinese and Japanese Translation

Simplified Chinese & Traditional Chinese.
Thank you for your hard work!

Added japanese translation.
Thanks to @aidasan.
" is not “ or ” Please pay attention to it.

Thanks! Could you please push this PR to the Develop Branch in stead of the Master branch?

Sorry hard to find the right one on a jap keyboard.
Sent from my iPhone

On 07 Jun 2016, at 23:26, Simon Shi<EMAIL_ADDRESS>wrote:
Added japanese translation.
Thanks to @aidasan.
" is not “ or ” Please pay attention to it.
―
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.


(v3.0.x) Ignore docs folder in CI

Kind of change

[ ] Bug fix
[ ] New non-breaking feature
[ ] New breaking feature
[ ] Documentation update
[x] Build improvement

Description
What is the goal of this pull request?
Avoid unnecessary CI runs when modifying docs.
Docs are built from docs.asciidoctor., we could have a job to build the docs and ensure they are correct, but right now this is using hardware resources for nothing :earth_africa: :leaves: .
How does it achieve that?
Use paths-ignore to ignore the 'docs/**' path.
Are there any alternative ways to implement this?
No
Are there any implications of this pull request? Anything a user must know?
No
Issue
If this PR fixes an open issue, please add a line of the form:
Fixes #Issue
Release notes
Please add a corresponding entry to the file CHANGELOG.adoc

Thanks!


enhancement: dynamic example and distinct role definition name

This PR adds two enhancements:

It adds a post-fix to the role definition names to avoid clashes during testing or for real world scenarios.
It adds an end to end sample for using the module with a dynamically defined management group structure using a yaml file.

@matt-FFFFFF If you'd like me to get the E2E tests working (with a Ready to Test label setup), let me know.

@matt-FFFFFF If you'd like me to get the E2E tests working (with a Ready to Test label setup), let me know.

That would be very useful I think feel free!

@matt-FFFFFF If you'd like me to get the E2E tests working (with a Ready to Test label setup), let me know.

That would be very useful I think feel free!

Tests are running now. There is a chance they will hit timing issue and will need to adjust the waits in the example. This is based on my experience earlier today.

awesome work @jaredfholgate LGTM


Divergence : AOT-DebugX64 vs. KBC-MIX-DebugX64

DIVERGENCE 1.1:3025129946 : AOT-DebugX64 vs. KBC-MIX-DebugX64
Please investigate.

Large runs found a few more, which I am, for now, attaching to this untriaged bug, since they have the same setting:
AOT-DebugX64 - KBC-MIX-DebugX64: !DIVERGENCE! 1.1:2000993669
AOT-DebugX64 - KBC-MIX-DebugX64: !DIVERGENCE! 1.1:1192547531

AOT-DebugX64 - KBC-MIX-DebugX64: !DIVERGENCE! 1.1:3638002724
AOT-DebugX64 - KBC-MIX-DebugX64: !DIVERGENCE! 1.1:122965272

An old friend that is fixed already by:
https://github.com/dart-lang/sdk/issues/34683
Confirmed the all work after updating to ToT.
1.1:3025129946  OK
1.1:2000993669   OK
1.1:1192547531  OK
1.1:3638002724   OK
1.1:122965272   OK
../../runtime/vm/object.cc: 2056: error: expected: thread->IsMutatorThread() || (space != Heap::kNew)
Dumping native stack trace for thread 12923
[0x000055a0b800de3f] dart::Profiler::DumpStackTrace(void*)
[0x000055a0b800de3f] dart::Profiler::DumpStackTrace(void*)
[0x000055a0b82db142] dart::Assert::Fail(char const*, ...)
[0x000055a0b7f3ac8d] Unknown symbol
[0x000055a0b7fc7ac7] dart::Mint::New(long, dart::Heap::Space)
[0x000055a0b7fc7a06] dart::Integer::New(long, dart::Heap::Space)
[0x000055a0b8134a76] dart::UnaryIntegerOpInstr::Evaluate(dart::Integer const&) const
[0x000055a0b81092a7] dart::ConstantPropagator::VisitUnaryIntegerOp(dart::UnaryIntegerOpInstr*)
[0x000055a0b81030cd] dart::ConstantPropagator::Analyze()
[0x000055a0b8102f6c] dart::ConstantPropagator::Optimize(dart::FlowGraph*)


Enforce utf-8 encoding on data sources

Nanoc defaults to the current environment encoding. If - for any reason - the default encoding is not utf-8, the compilation breaks with the following error:
Nanoc::DataSources::Filesystem::Errors::InvalidEncoding: Could not read repositories/prometheus.git/latest (2.10)/docs//storage.md because the file is not valid US-ASCII.

In this PR, I'm enforcing utf-8 encoding on all data sources.
@brian-brazil

Can we set this in one place?

Can we set this in one place?

I'm not familiar with nanoc. I looked for it in the nanoc doc and I haven't found any reference about a global setting (which I agree would be ideal).

@grobie Do you know if there's one?

I checked the source code:

nanoc doesn't offer a way to globally set the encoding on the Filesystem data source (RepoDocsDataSource extends it)
Ruby's File.read() infers the default encoding from the LANG environment variable

We may enforce it overriding the LANG env variable in the Makefile, but it's value may change on different systems (ie. UTF-8 vs C.UTF-8). All in all, I would personally suggest to enforce it for each data source in the nanoc.yaml (this PR), but I'm open to suggestions and further discussion.

I'm unhappy about the current repo docs config structure anyway, it's too convoluted when tracking multiple versions. I'd hope to simplify that in a future version. For now, it's just one line more to copy&paste, I'd go forward with that.

@brian-brazil Do you think there's interest into merging this PR?

Thanks!


Add reducers and actions

In this milestone, I have completed the following changes:

According to the project requirements:

[ ] Installed Redux Toolkit.

[ ] Created a directory that contains all the Redux logic (/src/redux)

[ ] Configured a Redux store (/src/redux/store.js)

[ ] Defined two slices - bookSlice and categorySlice

[ ] My files structures are below:

/src
|---/components
|---/redux
  |---/redux/features
    |--- /books
            | booksSlice.js
    |--- /categories
            | categoriesSlice.js
  |--- /redux/store.js
| index.js

Hello @didierganthier,
Thanks for the approval and for giving the feedback.


Add multi-file-gear rule matching

This small change to gear rules allows a gear to have multiple files automatically selected by type. To use this feature, simply add a match key to the rule mapping gear input name to file type:
"match": {
	"bval": "bval",
	"bvec": "bvec",
	"diffusion": "nifti"
}

Very cool. I'll leave it to @nagem to review the code. I'd like to see this merged asap, coordinated around SfN freeze.

Ryan, Megan and I have coordinated on the SfN freeze & have decided that non-SfN branches are clear to land on master. We'll branch off a release tag if we have more SfN core changes.
For review purposes: it should be noted that the same old behavior is left alone; this only does something new when the match key is present on a rule.

Meta: this may have been better implemented as using the gear manifest's own input specifications. That might be a good upgrade in the future, but this will serve for the high-priority use case.

Code LGTM. We should open a ticket to amend the existing issue of TokenPlacer not calling the code that would create jobs.


Issue 455 - Update system requirements for RHEL

Solves issue #455 - Update system requirements for RHEL to indicate 8GB of RAM is needed for proper functioning.

Looks like @tst-awankhede's comments have been addressed. I'm going to approve and merge.


[WIP][Experiment] Allow custom sourcing

With Ubuntu configuration of this repo, I'm running into issues with being forced into one single mirror with 3 specific components. While this makes sense for Debian, it breaks multiple architectures for i.e. archive.ubuntu.com where only amd64/i386 packages are hosted.
To be clear, this PR does not solve the multiple architecture breakage. There should ultimately be checks for whether a Packages.xz exists for a given source, which would allow for multiple source specification and multiple arch specification.
In addition to solving this problem, this exact_sources configuration enables custom sources to be added, as referenced in #45.
As a reminder, this is very much a WIP. The purpose of opening this PR is to understand whether the contributors of this project think it's a good idea to pursue and correspondingly edit.
As of the opening of this PR, the following works:
`debian_packages_lockfile(
name = "ubuntu_packages_amd64",
lock_file = "ubuntu-packages.lock",
packages_file = "ubuntu-packages.yaml",
exact_sources = ["http://archive.ubuntu.com/ubuntu/dists/jammy/main", "http://archive.ubuntu.com/ubuntu/dists/jammy/universe", ]
)
debian_packages_lockfile(
name = "ubuntu_packages_arm64",
lock_file = "ubuntu-packages-arm.lock",
packages_file = "ubuntu-packages-arm.yaml",
exact_sources = ["http://ports.ubuntu.com/ubuntu-ports/dists/jammy/main", "http://ports.ubuntu.com/ubuntu-ports/dists/jammy/universe"]
)`

Hello @HunterCrosland, thanks for your contribution.
rules_debian_packages is being deprecated in favor of rules_distroless.
IIRC it already fully covers this usecase.


Align with Password policy recommendations for Office 365

I recommend we update the password section to more closely align with Password policy recommendations for Office 365, in particular, Don't require character composition requirements.
https://docs.microsoft.com/en-us/office365/admin/misc/password-policy-recommendations?view=o365-worldwide

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 8234ffd6-eecf-088e-6ac4-76a750c123a9
Version Independent ID: 7dfd076b-7c10-948d-4a48-3ddefc3c8795
Content: Install SharePoint Servers 2016 or 2019 across multiple servers
Content Source: SharePoint/SharePointServer/install/install-sharepoint-server-2016-across-multiple-servers.md
Product: sharepoint-server-itpro
GitHub Login: @MikePlumleyMSFT
Microsoft Alias: mikeplum

These are two very different use cases and using the recommendations for Office 365 would not be appropriate for SharePoint Server service accounts.

@sguitardude Thank you for submitting feedback. We understand that this issue has been resolved.
Please feel free to re-open this issue if there is a specific area of the docs that we can improve or make better. Thank you.


python38Packages.zeroc-ice: 3.7.5 -> 3.7.6

Automatic update generated by nixpkgs-update tools. This update was made based on information from passthru.updateScript.
meta.description for python38Packages.zeroc-ice is: "Comprehensive RPC framework with support for Python, C++, .NET, Java, JavaScript and more."
meta.homepage for python38Packages.zeroc-ice is: "https://zeroc.com/"
meta.changelog for python38Packages.zeroc-ice is: ""
Updates performed

Ran passthru.UpdateScript

To inspect upstream changes
Impact

Checks done (click to expand)

built on NixOS

Warning: a test defined in passthru.tests did not pass

/nix/store/9sbrjcaa108dnm2g6kq8x9ra3m6m63gs-python3.8-zeroc-ice-3.7.6/bin/slice2py passed the binary check.

/nix/store/9sbrjcaa108dnm2g6kq8x9ra3m6m63gs-python3.8-zeroc-ice-3.7.6/bin/.slice2py-wrapped passed the binary check.

2 of 2 passed binary check by having a zero exit code.

2 of 2 passed binary check by having the new version present in output.

found 3.7.6 with grep in /nix/store/9sbrjcaa108dnm2g6kq8x9ra3m6m63gs-python3.8-zeroc-ice-3.7.6

found 3.7.6 in filename of file in /nix/store/9sbrjcaa108dnm2g6kq8x9ra3m6m63gs-python3.8-zeroc-ice-3.7.6

directory tree listing: https://gist.github.com/3a23b3cd83449ae64f2839a5e094a726

du listing: https://gist.github.com/074120c822f0065c360069720f57b623

Rebuild report (if merged into master) (click to expand)

8 total rebuild path(s)

2 package rebuild(s)

2 x86_64-linux rebuild(s)
2 i686-linux rebuild(s)
2 x86_64-darwin rebuild(s)
2 aarch64-linux rebuild(s)

First fifty rebuilds by attrpath
python38Packages.zeroc-ice
python39Packages.zeroc-ice

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/9sbrjcaa108dnm2g6kq8x9ra3m6m63gs-python3.8-zeroc-ice-3.7.6 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A python38Packages.zeroc-ice https://github.com/r-ryantm/nixpkgs/archive/ee1d9e128f119c3f9eae0312a8ff27adb40dfc09.tar.gz

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/9sbrjcaa108dnm2g6kq8x9ra3m6m63gs-python3.8-zeroc-ice-3.7.6
ls -la /nix/store/9sbrjcaa108dnm2g6kq8x9ra3m6m63gs-python3.8-zeroc-ice-3.7.6/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1

2 packages built:

python38Packages.zeroc-ice
python39Packages.zeroc-ice

Maintainer pings
cc @abbradar for testing.

Result of nixpkgs-review pr 135405 at ee1d9e12 run on x86_64-linux 1

2 packages built successfully:

python38Packages.zeroc-ice
python39Packages.zeroc-ice

2 suggestions:

warning: no-python-tests
Test runner could not discover any test cases: ‘Ran 0 tests in 0.000s’
Near pkgs/development/python-modules/zeroc-ice/default.nix:17:0:
   |
17 |     description = "Comprehensive RPC framework with support for Python, C++, .NET, Java, JavaScript and more.";
   | ^

warning: unclear-gpl
gpl2 is a deprecated license, please check if project uses gpl2Plus or gpl2Only and change meta.license accordingly.
Near pkgs/development/python-modules/zeroc-ice/default.nix:16:5:
   |
16 |     license = licenses.gpl2;
   |     ^


fix non-binary conditionals in frontend

Fix for the issue described in #51 where the Definition for IR for ast.BoolOp's with more than 2 operands (e.g. of the form a and b and c) was not constructed correctly.

It looks fine to me. As soon as we have confirmation that this effectively fixes #51 we can close the issue.

Thanks for the quick fix and patience on validation! So sorry, I finally had a moment to try it out -- and it does fix my use case! Thank you!


added a new theorem about subgroups, added some simp lemmas

Formalized and proved a theorem that states that if H is a subgroup of G, then H is a subgroup of the normalizer of H in G. Added simp lemmas that are true by definition to avoid unfolding. I replaced all the unfold tactics with rewrites in the sheet.

Thanks for the feedback! I'm hoping to eventually merge my branch (ch3/woh/sheet2) into our main chapter 3 branch (ch3/subgroup_defs, which I hopefully will rename soon. By chance, could you edit this PR to targe that branch? That'd be much appreciated.


Evaluation during filtering/sorting is problematic

All the evaluations (in-cell, plot etc.) refer to the real (not-the filtered) data. They are not compatible with proxy.

Note

In Excel, filtering does not alter the order. Loc-selection is safe.
In Excel, sorting is in-place.


long term: retire perl code that routes MIxS terms into NMDC schema

see also #252

Use mixs-source code. The most recently updated code is at https://github.com/turbomam/mixs-source, but that will be integrated into [https://github.com/GenomicsStandardsConsortium/mixs any day now.

@sujaypatil96 Today is mid-sprint so I’m checking in to see how you’re doing with your assigned GitHub issues.  Please update this issue and let me know if you’re still actively working on it and it’s on track for finishing by the end of June. If you’re not working on it due to other priorities let me know if you plan to work on it in July or if it should be moved to the backlog for reprioritization.

Checked with @sujaypatil96 and this one isn't high priority for next month so I'm removing from the sprint and adding the backlog label.

now implemented with  GNU make rules and Python, especially using the sheets_and_friends package.


Add top navbar to all pages in Vue client

The Angular client had a black navbar at the top, showing the name Cardshifter along with the current user's name after they log in. Eventually it will also have some navigation menus to go to other places. This needs to be added to the Vue client.

This is resolved and has been committed to develop and master.


Could you please add ** to your list?

Sorry I'm blind

Sorry for my laziness, I will add more information in recent days. : )


Tags without own commits gettings wrong dates

Hey @CookPete,
thanks for this nice package.
Actual behaviour
Tags without own commits getting wrong dates.
Expected behaviour
Tags without commits should display the correct dates.
Steps to reproduce

commit things
tag v1.0.9-rc
tag v1.0.9 without new commits

Screenshots

Configuration
<EMAIL_ADDRESS>

This should be fixed in 2.1.0. Previously it was using the date of the first commit in that release. For releases without commits (like in your example) it was falling back to the current date. It now grabs the date of each tag instead.


connect to next traj shouldn't always be plucked

This doesn't seem to be occuring now. I don't know why it was before.


Add on throws error upon staring anki

Bug/Issue Description
A short description of the issue.
Anki 23.12.1 (1a1d4d54)  (ao)
Python 3.9.15 Qt 6.6.1 PyQt 6.6.1
Platform: Linux-6.6.7-arch1-1-x86_64-with-glibc2.38
When loading Study Time Stats:
Traceback (most recent call last):
File "aqt.addons", line 245, in loadAddons
File "/home/rif/.local/share/Anki2/addons21/1247171202/init.py", line 8, in
from .src import toolbar
File "/home/rif/.local/share/Anki2/addons21/1247171202/src/toolbar.py", line 12, in
from .options import TimeStatsOptionsDialog
File "/home/rif/.local/share/Anki2/addons21/1247171202/src/options.py", line 41, in
from ..res.ui.cell_item import Ui_CellWidget
File "/home/rif/.local/share/Anki2/addons21/1247171202/res/ui/cell_item.py", line 11, in
from PyQt5 import QtCore, QtGui, QtWidgets
ModuleNotFoundError: No module named 'PyQt5'
To Reproduce
Steps to reproduce:

Go to '...'
Click on '....'
Scroll down to '....'
See error

Screenshots/Visuals
If necessary/applicable, add some screenshots to help explain the issue.
System/Debug Info
You can get this from Anki in Help -> About -> Copy Debug Info,
Additional Context
Any other context that might seem important.

Should be fixed in the most recent release (v2.1.0), hopefully! Will have to see.
Thanks for reporting!


Bump DC/OS version to 1.10.3

High-level description
This changes the DC/OS version for the upcoming 1.10.3 release.
Corresponding DC/OS tickets (obligatory)
https://jira.mesosphere.com/browse/DCOS_OSS-1966
Checklist for all PRs

[ ] Included a test which will fail if code is reverted but test is not. If there is no test please explain here:
[ ] Read the DC/OS contributing guidelines
[ ] Followed relevant code rules Rules for Packages and Systemd

Checklist for component/package updates:
If you are changing components or packages in DC/OS (e.g. you are bumping the sha or ref of anything underneath packages), then in addition to the above please also include:

[ ] Change log from the last version integrated (this should be a link to commits for easy verification and review): example
[ ] Test Results: [link to CI job test results for component]
[ ] Code Coverage (if available): [link to code coverage report]

@mesosphere-mergebot bump-ee


[Question] GCP artifacts

Hi, first of all thanks for this action!
I have a question regarding cleanup in gcp artifacts. If I open the artifacts in GCP console there is a <name> one and a <name>/cache, this it cleanup both or only the <name> one?

By default, it will only clean up <name>. If you specify -recursive, it will do both.

Thanks!

Forgot to ask my followup: If -recursive is also enabled and /cache is also cleared, this will only slow down the next build right? Since that cache layer will then be removed?


Feature Request: docker image

Hello,
It would be great to have a docker image for this fantastic tool :)
It would make it easier to deploy
Best

Hi @PeterOsinski
Docker allows an easy deployment and flexibility if you need several instances of lodgy. You can for example add directly to the docker compose of the project a container with logdy. It also provides an isolation and a flexible management when you have all of your app running with docker.
I did create a container for testing and it works well, and add it to my docker compose :
services:
  caddy:
   ...

  logdy:
    image: logdy
    container_name: logdy
    read_only: true
    volumes:
      - /home/docker/caddy/logs/access.log:/var/log/access.log:ro
      - /home/docker/caddy/logs/error.log:/var/log/error.log:ro
      - /home/docker/logdy:/config
    restart: unless-stopped
    security_opt:
      - no-new-privileges=true
    command: ["./logdy", "--ui-ip", "<IP_ADDRESS>", "--config", "/config/logdy.json", "follow", "/var/log"]

and a very simple dockerfile
FROM alpine:latest

ENV LOGDY_VERSION=0.13.0

ADD "https://github.com/logdyhq/logdy-core/releases/download/v${LOGDY_VERSION}/logdy_linux_amd64" /usr/local/bin/logdy

RUN chmod +x /usr/local/bin/logdy

ENTRYPOINT ["/usr/local/bin/logdy"]

CMD ["--ui-ip", "<IP_ADDRESS>", "--config", "/config/logdy.json", "follow", "/var/log"]

Thanks, I can help for testing and implementing!

Hi,
I did a test here: https://github.com/azertylr/logdy-docker/

@PeterOsinski Just submitted #56. Dockerfile tries to be as much generic and unopinionated as possible, to serve as many usage scenarios as possible (e.g. not size-optimized, yet).
It will work for @azertylr's docker-compose.yml scenario, although the service will need a command key for passing the command switches and a more detailed build section to point to the Dockerfile Github repo URL.
Everyone's welcomed to take it for a spin and provide feedback on the PR.

@azertylr: now that #56 is merged, you might want to tweak your Compose manifest by adding a build section which references this repo's URL and see if it works for you.
See Compose Build Specification for how to make a service build from a repo URL.

Hello,
It is working great :) my docker-compose:
Thanks!
services:
  logdy:
    build: https://github.com/logdyhq/logdy-core.git
    container_name: logdy
    read_only: true
    volumes:
      - /home/docker/caddy/logs:/var/log:ro
      - /home/docker/logdy/logdy_caddy2.json:/config/logdy.json
    restart: unless-stopped
    security_opt:
      - no-new-privileges=true

Just something I've just noticed, image is 935.6 MB, versus 87 MB for the exe file :(

Just something I've just noticed, image is 935.6 MB, versus 87 MB for the exe file :(

It is happening because the dockerfile's base image is the golang:1 and this is a big one, i'll try my best to sumbit a pr today with a multistep docker build that reduces the image size.

@azertylr : Glad to know it's working for you and thanks for sharing your Docker Compose snippet. I think it'll make for a good usage example, once Docker usage it's settled. As you noticed, size was not a priority initially and I don't think should be yet.
@borosr : A size optimization would be a desirable improvement down the road and much appreciated, indeed. But there are a few follow-up improvements which might come later that I think would be easier without the size improvements, to come later.
For the full context and rationale of the Dockerfile check out #56. Even better, if you have any feedback, I think that perhaps there will be a better place to discuss the Docker image implementation details and maybe spin off relevant issues.
@PeterOsinski : Also, to properly scope the Docker efforts from here on, I'd like to know your stance as maintainer on how much you're up to add to the project in terms of future maintenance. Do you prefer keeping it as minimal as possible (ie. just a canonical "just builds :tm:, you figure out usage"  Dockerfile in repo, no built public image) or do you want to fully support Docker usage (public image, docs, etc.)?
Needless to say, there's no right answer, as it depends entirely on how much time and effort you feel like to commit to this specific feature in the future.


Open PR - Archie Shah

Open PR in repo : https://github.com/Rakesh9100/Beautiify
Issue: https://github.com/Rakesh9100/Beautiify/issues/1287
PR : https://github.com/Rakesh9100/Beautiify/pull/1320
Added an entire component in the project which is a level 3 contribution. Please merge this and add 45 points to the leaderboard.

PR is getting reviewed one by one and merged, you can remove the point label from here @sanjay-kv


VERSION is not updated

Hi all, just to inform that the file VERSION is not up to date. That can be confusing because I was referring to this file during my development. It takes me a few minutes to understand that it wasn't the right version :)
I can make a pull request if you prefer.

Fixed in #249


OnePlus 5 not detected as Phone

Not deteccting ONEPLUS 5 device as phone.
User Agent: Mozilla/5.0 (Linux; Android 8.0.0; ONEPLUS A5000 Build/OPR6.170623.013) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/64.0.3282.137 Mobile Safari/537.36

as stated in the text when creating an issue, please open issues like that in Mobile-Detect PHP project.


Orbot does not allow Tor to open on iPad

After opening Orbot, the TOR page with search bar does not open. Orbot often repeatedly shows "Connecting" then stops then shows "Ready to Connect". "Start" repeats this loop.

After closing Orbot, Safari cannot open regularly used web sites (e.g. Axios, NYTimes, etc. "Cannot connect to server". VPN is not connected in settings. Power-off/Power-on and ORBOT VPN automatically launches and Safari cannot connect to web sites. Turn off VPN and Safari still cannot connect and Orbot VPN continues to launch. In Orbot settings I have auto restart on error and disable orbot for non-onion traffic. Only solution is to delete the Orbot app. to allow Safari to operate normally.

I'm afraid the root of these problems is a bug which Apple introduced in iOS 16.5. It seems, the Network Extension (the piece which runs the "VPN" code) doesn't seem to stop for some time, even though iOS reports it stopped.
A version 1.6.2 of Orbot is already in the pipeline and hopefully released soon, which might reduce your issues a little.
Regarding the cannot-browse-after-stop: Did you try waiting it out or restarting your phone?

Thanks for the explanation. It’s good to know it is a recognized problem and work is underway. Luckily I can use my Airbook Tor during the interim. Regarding “waiting it out”, we haven’t done that since teletype/telex.Best Regards,  FrankOn Aug 29, 2023, at 5:47 AM, Benjamin Erhart @.***> wrote:
I'm afraid the root of these problems is a bug which Apple introduced in iOS 16.5. It seems, the Network Extension (the piece which runs the "VPN" code) doesn't seem to stop for some time, even though iOS reports it stopped.
A version 1.6.2 of Orbot is already in the pipeline and hopefully released soon, which might reduce your issues a little.
Regarding the cannot-browse-after-stop: Did you try waiting it out or restarting your phone?
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you authored the thread.Message ID: @.***>


withMap HoC removes prop typings from components

NPM package: 4.0.0
The withMap HoC from react-mapbox-gl/src/context is removing the prop typings from the components that it wraps.
To see the problem, import Cluster import { Cluster } from "react-mapbox-gl"; (or any other component wrapped with withMap), and inspect it's type. You'll see something along these lines: const Cluster: <T>(props: T) => JSX.Element
T is the unconstrained type of the props being passed in. Cluster has a required prop of ClusterMarkerFactory, but with the lack of typings it'll give no error no matter what is or isn't passed.
If instead the unwrapped version of Cluster is directly imported: import { Cluster } from "react-mapbox-gl/src/cluster";, then you'll find that you get an error about the missing required prop: Property 'ClusterMarkerFactory' is missing in type '{}'.
So how can this be fixed? By improving the typings on withMap:
type Omit<T, K> = Pick<T, Exclude<keyof T, keyof K>>;
interface HasMapProp { map: MapboxGl.Map | undefined; }

// Typing - Take in a component which must have a "map" prop.
export const withMap = <TProps extends HasMapProp>(Component: React.ComponentType<TProps>):
// Typing - Return a component function (Stateless Functional Component) which has the same props, except without "map".
React.SFC<Omit<TProps, HasMapProp>> =>
// The actual code performing the injection
    (props) => {
        return (
            <MapContext.Consumer>
                {map => <Component map={map} {...props} />}
            </MapContext.Consumer>
        );
    };

This improves the typings in two ways, first it means withMap can only be applied to components which can take a map prop, and second it means the wrapped component (such as Cluster) is returned with the same props that it was passed in with, except for map, which has been injected by the HoC.
Giving it a quick test with const WrappedCluster = withMap(Cluster); <WrappedCluster /> gives us the correct error Property 'ClusterMarkerFactory' is missing in type '{}'., and from the prop list in the typings we can see map has been removed: const WrappedCluster: React.StatelessComponent<Pick<Props, "children" | "ClusterMarkerFactory" | "radius" | "maxZoom" | "minZoom" | "extent" | "nodeSize" | "log" | "zoomOnClick" | "zoomOnClickPadding" | "style" | "className" | "tabIndex">>
I wanted to submit this as a PR, but I had trouble getting the project to build.
I had a look around but couldn't find any info on the tooling that you use.
I tried to use VSCode on Win10, and that allowed me to experiment a bit, but the Demos especially had build errors (e.g. TS2307: Cannot find module '../../../'.) and I didn't feel confident pushing code that I couldn't fully test and show was working.
This post is a result of going through context.tsx due to this issue so if you do fix these typings, it'd be great if you could also action that issue, exposing MapContext and withMap!
This fixes the missing prop types, but my original issue was how to make a custom control that works like ZoomControl and the others.
If I can get some guidance on setting up a development environment then I'd be more than happy to submit this as a PR, with all the due diligence required.

Hi, thanks for the detailed issue! I'll try and take care of this soon. For future reference, the issue you were seeing with examples is that they depend on the main package being built locally (so npm run-script build in the repo root).

Ran into some type issues, where I can't guarantee that the argument of withMap indeed supports Map | undefined as the map prop's type. Will try and look more into it tomorrow, but this is a bit nasty, giving a false sense of security while in fact runtime type errors can arise.


[Fix #5403] making the heredoc delimeter pattern more precise

Adjusting the pattern for valid heredoc delimiters to allow delimiters containing END or EO. Also this allows the use of EOF which is in the list of allowed acronyms. This will fix #5403.
Also the pattern is now consolidated into one regex term.
The reason for tolerating white space characters around it is to avoid collisions with something other rules are taking care of already (i.e. indentation).

The work on this is done. Sorry for the format mess, will create PR next time only after local cleanup.

@mcfisch: I approved the PR, but you'll need to squash your commits, rebase, and fix the CHANGELOG. 🙇


Polygon URL issue

Having used both particle.js and your library before, I can not seem to get the URL component of my polygon params to correctly locate my svg I have tried putting it and changing the path to almost everything I can think of. Here are the errors from the console:

This was me testing the url route:
"/jp_poygon_singlePath.svg"
as its at the root of my project ... I have tried to fetch it from numerous other places as well. Please help.
Things that may be affecting it:
react-router ? although the canvas is showing up correctly in the desired location
https://github.com/jp-signum/jp_sig_reactv1.git is the repository

You have to serve the svg file in a public folder:
is http://localhost:3000/jp_polygon_singlePath.svg accessible navigating from the browser ? If not, the script cannot download the svg.

ahhhhh I see after moving it to my public folder and readjusting the url it now seems to be accessing the svg correctly however nothing is drawing on the canvas. I have removed all styling and anything I can think of from the parent components and container yet it does not seem to be working. Any suggestions on how to debug this? I am assuming its the svg ? I have the script in the body of my body

First try a minimal particles settings, then adjust the css (it may be possible that white particles are rendered upon white background, thus they are not visible). After you got a minimal template, proceed with the svg polygon.

when starting with a minimal setting I get this error

hey looks like i was able to figure it out thanks for the help

sorry have you ever seen anything like this happen ? and do you know where this might originate

obviously those static lines arent supposed to be there

Open your file with a svg editor and check if the path is correct

yeah I made it in adobe illustrator, after trying a few different things I realized there were some transforms being added and I was able to remove them before exporting the svg because simply deleting them from the svg code didnt solve the problem. I was able to do this by using the reset bounding box property in AI  ...... just in case anyway has a similar issue.
Thanks for answering quickly and helping me out !!!! much appreciated :)

Hi, @jp-signum! I am having the exact same issues as you. May I know how you were able to solve it? Thanks in advance!

@ambwani what issue is that?


Redis SSL Support [#556]

Purpose
Add support for Redis SSL connections to Elasticache.
Changes
Exposes simple config variables to enable Redis SSL connections.  Testing isn't included here - I think we can wait until we are hosting an instance of Fidesops that uses Elasticache.
Checklist

[ ] Update CHANGELOG.md file

[ ] Merge in main so the most recent CHANGELOG.md file is being appended to
[ ] Add description within the Unreleased section in an appropriate category. Add a new category from the list at the top of the file if the needed one isn't already there.
[ ] Add a link to this PR at the end of the description with the PR number as the text. example: #1

[ ] Applicable documentation updated (guides, quickstart, postman collections, tutorial, fidesdemo, database diagram.
If docs updated (select one):

[ ] documentation complete, or draft/outline provided (tag docs-team to complete/review on this branch)
[ ] documentation issue created (tag docs-team to complete issue separately)

[ ] Good unit test/integration test coverage
[ ] This PR contains a DB migration. If checked, the reviewer should confirm with the author that the down_revision correctly references the previous migration before merging
[ ] The Run Unsafe PR Checks label has been applied, and checks have passed, if this PR touches any external services

Ticket
Fixes #556

updated, thanks @sanders41


PowerToys Run - launching software on same screen and quick launcher

Description of the new feature / enhancement
Currently, when using multiple monitors the PowerToys Launcher follows the cursor - i.e. I hit the key combination and it shows on the screen that currently has focus. However, presently the application that gets launched shows on the primary monitor, not the one in focus.  The current behaviour seems to be consistent testing across several programs e.g. Windows Terminal, Excel, Windows Explorer, etc.
It would be great it if the application launched on the same screen that the quick launcher displayed, which is probably typically the same as the currently in-focus screen / the screen that the cursor is currently on.
Scenario when this would be used?
This is useful for a typical multimonitor workflow - it's likely that the screen where someone initiates a launch is also the screen where they would like to use the program in question.
Supporting information
No response

Hopefully not a duplicate suggestion, tried searching the archive but didn't have a lot of luck, there's a lot there!

In FancyZones you can activate "move newly created windows to the current active monitor" to achive this.


Pull

Pull in for a long while.

Sigh... merge conflicts are hairier the longer the separation from upstream


Apprate popup show every times

Apprate plugin popup show every time at lunch, even after choosing "No, Thanks".
Settings and more informations here : https://github.com/pushandplay/cordova-plugin-apprate#dont-call-rate-dialog-immediately
Since v2.0.0

v2.0.1 released

#319 v2.0.0 is ok


Feature/configurable parameters

Add configuration file for Iroha config.json and methods to work with it. Config manipulation system was reworked in general.

Looks good to me.


bugfix: 框架依赖环境变量调整错误 (closed #823)

Codecov Report

Merging #824 (388e8e1) into V2.2.16-rc (9d2e9f7) will increase coverage by 45.88%.
The diff coverage is 0.00%.

@@               Coverage Diff               @@
##           V2.2.16-rc     #824       +/-   ##
===============================================
+ Coverage       25.16%   71.05%   +45.88%
===============================================
  Files              21      294      +273
  Lines            1037    21597    +20560
===============================================
+ Hits              261    15346    +15085
- Misses            776     6251     +5475

Impacted Files
Coverage Δ

config/default.py
79.61% <0.00%> (+75.78%)
:arrow_up:

apps/node_man/handlers/policy.py
83.37% <0.00%> (ø)

...end/components/collections/agent_new/components.py
100.00% <0.00%> (ø)

apps/core/remote/constants.py
100.00% <0.00%> (ø)

apps/node_man/periodic_tasks/sync_cmdb_host.py
64.08% <0.00%> (ø)

apps/core/encrypt/models.py
100.00% <0.00%> (ø)

apps/node_man/serializers/cloud.py
100.00% <0.00%> (ø)

common/api/modules/bk_node.py
100.00% <0.00%> (ø)

apps/backend/agent/signals.py
66.66% <0.00%> (ø)

apps/backend/subscription/steps/__init__.py
82.35% <0.00%> (ø)

... and 277 more

Continue to review full report at Codecov.

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


server time out

My client has a website on Joomla. We are facing the email notification issue. Neither admin nor customer getting an email for placed order.
We are using sendgrid, swiftmailer for mail purpose. We tried testing SMTP credentials through Joomla server section of test mail. Those credentials working fine.
But when we are applying the same credentials into the code, we are facing the issue of server time out. We want to resolve this issue ASAP.
I am not sure but I think it might be because of updates of swift or other plugins related to it.

PHP Version: 5.6 Stable

Its saying - Connection to smtp.sendgrid.net:465 Timed Out
Any help would appreciated.

Hello @maddy2018,
Thanks for submitting a GitHub issue! We are very sorry that you are running into this problem. In order to better serve you, as this does not present itself as a library specific issue, we would like to ask that you reach out to our support team at https://support.sendgrid.com.
Thank you!
SendGrid DX Team


Method addPropertyChangedListener load the object

Hi,
In the proxy of my class with the NOTIFY changeTrackingPolicy, the method addPropertyChangedListener load the class.
public function addPropertyChangedListener(\Doctrine\Common\PropertyChangedListener $listener)
{
    $this->__load();
    return parent::addPropertyChangedListener($listener);
}

This has as consequence that when i loaded my object that have a referenceone to another object, this another object is loaded too, even if i don't use it.
Is it possible to not load the object when adding the listener (added by the UnitOfWork) ?
Thanks,

Looks like correct behavior to me. You are interacting with an object that is yet to be loaded, and therefore it should be loaded before that interaction.

This is triggered by the UnitOfWork internally when notify policy injects the listener. The proxy generator should exempt this method. I am a bit confused this has never occured in the ORM before (or nobody reported it). Maybe we inject the listener specifically after proxy load.

Indeed ORM seem to omit uninitialized Proxies (for instance https://github.com/doctrine/doctrine2/blob/1e7e8f216a899ad2ae4f38e208b5b26ce7f503ec/lib/Doctrine/ORM/UnitOfWork.php#L3104-L3106), we need to make ODM better here :)

#1160 was merged manually in https://github.com/doctrine/mongodb-odm/commit/e3468b2d2a8895bc2b560b69272e75772f08c815


Arduino resetting - Looking for guidance

I'm working on an automotive project and would like to alter the frequency of my ptScheduler task (ptCalculateRpm) based on engine RPM. When I implement this as shown below the Arduino goes into a reset loop ... something is not happy.
Is this an edge case anti-pattern or am I missing something ?
The definition of the object is:
ptScheduler ptCalculateRpm = ptScheduler(PT_TIME_200MS);
The code that contains my desires is:
  if (ptCalculateRpm.call()) {
    detachInterrupt(digitalPinToInterrupt(rpmSignalPin));
    currentRpm = calculateRpm();
    attachInterrupt(digitalPinToInterrupt(rpmSignalPin), updateRpmPulse, RISING);
    // Change frequency of rpm calculation depending on RPM to avoid high error
    if (currentRpm > 1500) {
      ptCalculateRpm = ptScheduler(PT_TIME_50MS);
    } else {
      ptCalculateRpm = ptScheduler(PT_TIME_200MS);
    }
  }

Hi David. I can see one issue with your code.
ptCalculateRpm = ptScheduler(PT_TIME_50MS);

This line actually creates a new ptScheduler object every time you call it, which is not what you want. To change the interval of a task, you can directly change the interval variable as shown below.
ptCalculateRpm.sequenceList [0] = PT_TIME_50MS;

This alters the first interval. Depending on how many intervals you have, you can call each of them as sequeceList[1], sequeceList[2], etc. For a task with a single interval, you can only change sequeceList[0].
The change will have an immediate effect when you call the call() function next time, and the effect can be unpredictable depending on how much time is already elapsed. To get a predictable behavior upon changing the interval, you can call the reset() function just after changing the task interval. This will reset all state and counter variables associated with the task. But the intervals will not be changed.

Thanks for the prompt and excellent feedback !! All fixed now :) Using the reset caused some needle twitching as the calculation evaluated to zero and it seems quite happy without needing it ... very happy now :)
For completeness the final code snip is as below:
  // Check the pretty tiny scheduler tasks and call as needed
  if (ptCalculateRpm.call()) {
    detachInterrupt(digitalPinToInterrupt(rpmSignalPin));
    currentRpm = calculateRpm();
    attachInterrupt(digitalPinToInterrupt(rpmSignalPin), updateRpmPulse, RISING);
    // Change frequency of rpm calculation depending on RPM to avoid high error
    if (currentRpm >= 1500 && ptCalculateRpm.sequenceList [0] != PT_TIME_50MS) {
      ptCalculateRpm.sequenceList [0] = PT_TIME_50MS;
    } else if (currentRpm < 1500 && ptCalculateRpm.sequenceList [0] != PT_TIME_200MS) {
      ptCalculateRpm.sequenceList [0] = PT_TIME_200MS;
    }
  }

Glad it worked 😀


Added language classifier for python

Adding language classifier (and other classifier as well) will help in better organization of  library on pypi.
I am open to adding other classifier. Please suggest any other, if it is needed.

Thanks! merged.