Update main.tf

Bump cloudposse/terraform-aws-ecr version from 0.6.0 to 0.7.0, because of https://github.com/cloudposse/terraform-aws-ecr/pull/27.

On second thought, I may try updating modules to use older 0.11 tags.  I tried using this repository as is with 0.12.5, and had this massive error output following a terraform plan

  on .terraform/modules/jenkins.cicd.build/main.tf line 142, in data "aws_iam_policy_document" "permissions_cache_bucket":
 142:       "${aws_s3_bucket.cache_bucket.arn}",

Because aws_s3_bucket.cache_bucket has "count" set, its attributes must be
accessed on specific instances.

For example, to correlate with indices of a referring resource, use:
    aws_s3_bucket.cache_bucket[count.index]

Error: Missing resource instance key

  on .terraform/modules/jenkins.cicd.build/main.tf line 143, in data "aws_iam_policy_document" "permissions_cache_bucket":
 143:       "${aws_s3_bucket.cache_bucket.arn}/*",

Because aws_s3_bucket.cache_bucket has "count" set, its attributes must be
accessed on specific instances.

For example, to correlate with indices of a referring resource, use:
    aws_s3_bucket.cache_bucket[count.index]

Error: Missing resource instance key

  on .terraform/modules/jenkins.cicd.build/main.tf line 150, in resource "aws_iam_role_policy_attachment" "default":
 150:   policy_arn = "${aws_iam_policy.default.arn}"

Because aws_iam_policy.default has "count" set, its attributes must be
accessed on specific instances.

For example, to correlate with indices of a referring resource, use:
    aws_iam_policy.default[count.index]

Error: Missing resource instance key

  on .terraform/modules/jenkins.cicd.build/main.tf line 151, in resource "aws_iam_role_policy_attachment" "default":
 151:   role       = "${aws_iam_role.default.id}"

Because aws_iam_role.default has "count" set, its attributes must be accessed
on specific instances.

For example, to correlate with indices of a referring resource, use:
    aws_iam_role.default[count.index]

Error: Missing resource instance key

  on .terraform/modules/jenkins.cicd.build/main.tf line 163, in resource "aws_codebuild_project" "default":
 163:   service_role = "${aws_iam_role.default.arn}"

Because aws_iam_role.default has "count" set, its attributes must be accessed
on specific instances.

For example, to correlate with indices of a referring resource, use:
    aws_iam_role.default[count.index]

Error: Missing resource instance key

  on .terraform/modules/jenkins.cicd.label/outputs.tf line 2, in output "id":
   2:   value = "${null_resource.default.triggers.id}"

Because null_resource.default has "count" set, its attributes must be accessed
on specific instances.

For example, to correlate with indices of a referring resource, use:
    null_resource.default[count.index]

Error: Missing resource instance key

  on .terraform/modules/jenkins.cicd.label/outputs.tf line 6, in output "name":
   6:   value = "${null_resource.default.triggers.name}"

Because null_resource.default has "count" set, its attributes must be accessed
on specific instances.

For example, to correlate with indices of a referring resource, use:
    null_resource.default[count.index]

Error: Missing resource instance key

  on .terraform/modules/jenkins.cicd.label/outputs.tf line 10, in output "namespace":
  10:   value = "${null_resource.default.triggers.namespace}"

Because null_resource.default has "count" set, its attributes must be accessed
on specific instances.

For example, to correlate with indices of a referring resource, use:
    null_resource.default[count.index]

Error: Missing resource instance key

  on .terraform/modules/jenkins.cicd.label/outputs.tf line 14, in output "stage":
  14:   value = "${null_resource.default.triggers.stage}"

Because null_resource.default has "count" set, its attributes must be accessed
on specific instances.

For example, to correlate with indices of a referring resource, use:
    null_resource.default[count.index]

Error: Missing resource instance key

  on .terraform/modules/jenkins.cicd.label/outputs.tf line 18, in output "attributes":
  18:   value = "${null_resource.default.triggers.attributes}"

Because null_resource.default has "count" set, its attributes must be accessed
on specific instances.

For example, to correlate with indices of a referring resource, use:
    null_resource.default[count.index]

Error: Missing resource instance key

  on .terraform/modules/jenkins.cicd.label/outputs.tf line 27, in output "tags":
  27:         "Name", "${null_resource.default.triggers.id}",

Because null_resource.default has "count" set, its attributes must be accessed
on specific instances.

For example, to correlate with indices of a referring resource, use:
    null_resource.default[count.index]

Error: Missing resource instance key

  on .terraform/modules/jenkins.cicd.label/outputs.tf line 28, in output "tags":
  28:         "Namespace", "${null_resource.default.triggers.namespace}",

Because null_resource.default has "count" set, its attributes must be accessed
on specific instances.

For example, to correlate with indices of a referring resource, use:
    null_resource.default[count.index]

Error: Missing resource instance key

  on .terraform/modules/jenkins.cicd.label/outputs.tf line 29, in output "tags":
  29:         "Stage", "${null_resource.default.triggers.stage}"

Because null_resource.default has "count" set, its attributes must be accessed
on specific instances.

For example, to correlate with indices of a referring resource, use:
    null_resource.default[count.index]

Error: Incorrect attribute value type

  on .terraform/modules/jenkins.efs.dns/main.tf line 7, in resource "aws_route53_record" "default":
   7:   records = ["${var.records}"]

Inappropriate value for attribute "records": element 0: string required.

Error: Missing resource instance key

  on .terraform/modules/jenkins.efs_backup.backups_label/outputs.tf line 2, in output "id":
   2:   value = "${null_resource.default.triggers.id}"

Because null_resource.default has "count" set, its attributes must be accessed
on specific instances.

For example, to correlate with indices of a referring resource, use:
    null_resource.default[count.index]

Error: Missing resource instance key

  on .terraform/modules/jenkins.efs_backup.backups_label/outputs.tf line 6, in output "name":
   6:   value = "${null_resource.default.triggers.name}"

Because null_resource.default has "count" set, its attributes must be accessed
on specific instances.

For example, to correlate with indices of a referring resource, use:
    null_resource.default[count.index]

Error: Missing resource instance key

  on .terraform/modules/jenkins.efs_backup.backups_label/outputs.tf line 10, in output "namespace":
  10:   value = "${null_resource.default.triggers.namespace}"

Because null_resource.default has "count" set, its attributes must be accessed
on specific instances.

For example, to correlate with indices of a referring resource, use:
    null_resource.default[count.index]

Error: Missing resource instance key

  on .terraform/modules/jenkins.efs_backup.backups_label/outputs.tf line 14, in output "stage":
  14:   value = "${null_resource.default.triggers.stage}"

Because null_resource.default has "count" set, its attributes must be accessed
on specific instances.

For example, to correlate with indices of a referring resource, use:
    null_resource.default[count.index]

Error: Missing resource instance key

  on .terraform/modules/jenkins.efs_backup.backups_label/outputs.tf line 18, in output "attributes":
  18:   value = "${null_resource.default.triggers.attributes}"

Because null_resource.default has "count" set, its attributes must be accessed
on specific instances.

For example, to correlate with indices of a referring resource, use:
    null_resource.default[count.index]

Error: Missing resource instance key

  on .terraform/modules/jenkins.efs_backup.backups_label/outputs.tf line 27, in output "tags":
  27:         "Name", "${null_resource.default.triggers.id}",

Because null_resource.default has "count" set, its attributes must be accessed
on specific instances.

For example, to correlate with indices of a referring resource, use:
    null_resource.default[count.index]

Error: Missing resource instance key

  on .terraform/modules/jenkins.efs_backup.backups_label/outputs.tf line 28, in output "tags":
  28:         "Namespace", "${null_resource.default.triggers.namespace}",

Because null_resource.default has "count" set, its attributes must be accessed
on specific instances.

For example, to correlate with indices of a referring resource, use:
    null_resource.default[count.index]

Error: Missing resource instance key

  on .terraform/modules/jenkins.efs_backup.backups_label/outputs.tf line 29, in output "tags":
  29:         "Stage", "${null_resource.default.triggers.stage}"

Because null_resource.default has "count" set, its attributes must be accessed
on specific instances.

For example, to correlate with indices of a referring resource, use:
    null_resource.default[count.index]

Error: Missing resource instance key

  on .terraform/modules/jenkins.efs_backup.datapipeline_label/outputs.tf line 2, in output "id":
   2:   value = "${null_resource.default.triggers.id}"

Because null_resource.default has "count" set, its attributes must be accessed
on specific instances.

For example, to correlate with indices of a referring resource, use:
    null_resource.default[count.index]

Error: Missing resource instance key

  on .terraform/modules/jenkins.efs_backup.datapipeline_label/outputs.tf line 6, in output "name":
   6:   value = "${null_resource.default.triggers.name}"

Because null_resource.default has "count" set, its attributes must be accessed
on specific instances.

For example, to correlate with indices of a referring resource, use:
    null_resource.default[count.index]

Error: Missing resource instance key

  on .terraform/modules/jenkins.efs_backup.datapipeline_label/outputs.tf line 10, in output "namespace":
  10:   value = "${null_resource.default.triggers.namespace}"

Because null_resource.default has "count" set, its attributes must be accessed
on specific instances.

For example, to correlate with indices of a referring resource, use:
    null_resource.default[count.index]

Error: Missing resource instance key

  on .terraform/modules/jenkins.efs_backup.datapipeline_label/outputs.tf line 14, in output "stage":
  14:   value = "${null_resource.default.triggers.stage}"

Because null_resource.default has "count" set, its attributes must be accessed
on specific instances.

For example, to correlate with indices of a referring resource, use:
    null_resource.default[count.index]

Error: Missing resource instance key

  on .terraform/modules/jenkins.efs_backup.datapipeline_label/outputs.tf line 18, in output "attributes":
  18:   value = "${null_resource.default.triggers.attributes}"

Because null_resource.default has "count" set, its attributes must be accessed
on specific instances.

For example, to correlate with indices of a referring resource, use:
    null_resource.default[count.index]

Error: Missing resource instance key

  on .terraform/modules/jenkins.efs_backup.datapipeline_label/outputs.tf line 27, in output "tags":
  27:         "Name", "${null_resource.default.triggers.id}",

Because null_resource.default has "count" set, its attributes must be accessed
on specific instances.

For example, to correlate with indices of a referring resource, use:
    null_resource.default[count.index]

Error: Missing resource instance key

  on .terraform/modules/jenkins.efs_backup.datapipeline_label/outputs.tf line 28, in output "tags":
  28:         "Namespace", "${null_resource.default.triggers.namespace}",

Because null_resource.default has "count" set, its attributes must be accessed
on specific instances.

For example, to correlate with indices of a referring resource, use:
    null_resource.default[count.index]

Error: Missing resource instance key

  on .terraform/modules/jenkins.efs_backup.datapipeline_label/outputs.tf line 29, in output "tags":
  29:         "Stage", "${null_resource.default.triggers.stage}"

Because null_resource.default has "count" set, its attributes must be accessed
on specific instances.

For example, to correlate with indices of a referring resource, use:
    null_resource.default[count.index]

Error: Missing resource instance key

  on .terraform/modules/jenkins.efs_backup.label/outputs.tf line 2, in output "id":
   2:   value = "${null_resource.default.triggers.id}"

Because null_resource.default has "count" set, its attributes must be accessed
on specific instances.

For example, to correlate with indices of a referring resource, use:
    null_resource.default[count.index]

Error: Missing resource instance key

  on .terraform/modules/jenkins.efs_backup.label/outputs.tf line 6, in output "name":
   6:   value = "${null_resource.default.triggers.name}"

Because null_resource.default has "count" set, its attributes must be accessed
on specific instances.

For example, to correlate with indices of a referring resource, use:
    null_resource.default[count.index]

Error: Missing resource instance key

  on .terraform/modules/jenkins.efs_backup.label/outputs.tf line 10, in output "namespace":
  10:   value = "${null_resource.default.triggers.namespace}"

Because null_resource.default has "count" set, its attributes must be accessed
on specific instances.

For example, to correlate with indices of a referring resource, use:
    null_resource.default[count.index]

Error: Missing resource instance key

  on .terraform/modules/jenkins.efs_backup.label/outputs.tf line 14, in output "stage":
  14:   value = "${null_resource.default.triggers.stage}"

Because null_resource.default has "count" set, its attributes must be accessed
on specific instances.

For example, to correlate with indices of a referring resource, use:
    null_resource.default[count.index]

Error: Missing resource instance key

  on .terraform/modules/jenkins.efs_backup.label/outputs.tf line 18, in output "attributes":
  18:   value = "${null_resource.default.triggers.attributes}"

Because null_resource.default has "count" set, its attributes must be accessed
on specific instances.

For example, to correlate with indices of a referring resource, use:
    null_resource.default[count.index]

Error: Missing resource instance key

  on .terraform/modules/jenkins.efs_backup.label/outputs.tf line 27, in output "tags":
  27:         "Name", "${null_resource.default.triggers.id}",

Because null_resource.default has "count" set, its attributes must be accessed
on specific instances.

For example, to correlate with indices of a referring resource, use:
    null_resource.default[count.index]

Error: Missing resource instance key

  on .terraform/modules/jenkins.efs_backup.label/outputs.tf line 28, in output "tags":
  28:         "Namespace", "${null_resource.default.triggers.namespace}",

Because null_resource.default has "count" set, its attributes must be accessed
on specific instances.

For example, to correlate with indices of a referring resource, use:
    null_resource.default[count.index]

Error: Missing resource instance key

  on .terraform/modules/jenkins.efs_backup.label/outputs.tf line 29, in output "tags":
  29:         "Stage", "${null_resource.default.triggers.stage}"

Because null_resource.default has "count" set, its attributes must be accessed
on specific instances.

For example, to correlate with indices of a referring resource, use:
    null_resource.default[count.index]

Error: Missing resource instance key

  on .terraform/modules/jenkins.efs_backup.logs_label/outputs.tf line 2, in output "id":
   2:   value = "${null_resource.default.triggers.id}"

Because null_resource.default has "count" set, its attributes must be accessed
on specific instances.

For example, to correlate with indices of a referring resource, use:
    null_resource.default[count.index]

Error: Missing resource instance key

  on .terraform/modules/jenkins.efs_backup.logs_label/outputs.tf line 6, in output "name":
   6:   value = "${null_resource.default.triggers.name}"

Because null_resource.default has "count" set, its attributes must be accessed
on specific instances.

For example, to correlate with indices of a referring resource, use:
    null_resource.default[count.index]

Error: Missing resource instance key

  on .terraform/modules/jenkins.efs_backup.logs_label/outputs.tf line 10, in output "namespace":
  10:   value = "${null_resource.default.triggers.namespace}"

Because null_resource.default has "count" set, its attributes must be accessed
on specific instances.

For example, to correlate with indices of a referring resource, use:
    null_resource.default[count.index]

Error: Missing resource instance key

  on .terraform/modules/jenkins.efs_backup.logs_label/outputs.tf line 14, in output "stage":
  14:   value = "${null_resource.default.triggers.stage}"

Because null_resource.default has "count" set, its attributes must be accessed
on specific instances.

For example, to correlate with indices of a referring resource, use:
    null_resource.default[count.index]

Error: Missing resource instance key

  on .terraform/modules/jenkins.efs_backup.logs_label/outputs.tf line 18, in output "attributes":
  18:   value = "${null_resource.default.triggers.attributes}"

Because null_resource.default has "count" set, its attributes must be accessed
on specific instances.

For example, to correlate with indices of a referring resource, use:
    null_resource.default[count.index]

Error: Missing resource instance key

  on .terraform/modules/jenkins.efs_backup.logs_label/outputs.tf line 27, in output "tags":
  27:         "Name", "${null_resource.default.triggers.id}",

Because null_resource.default has "count" set, its attributes must be accessed
on specific instances.

For example, to correlate with indices of a referring resource, use:
    null_resource.default[count.index]

Error: Missing resource instance key

  on .terraform/modules/jenkins.efs_backup.logs_label/outputs.tf line 28, in output "tags":
  28:         "Namespace", "${null_resource.default.triggers.namespace}",

Because null_resource.default has "count" set, its attributes must be accessed
on specific instances.

For example, to correlate with indices of a referring resource, use:
    null_resource.default[count.index]

Error: Missing resource instance key

  on .terraform/modules/jenkins.efs_backup.logs_label/outputs.tf line 29, in output "tags":
  29:         "Stage", "${null_resource.default.triggers.stage}"

Because null_resource.default has "count" set, its attributes must be accessed
on specific instances.

For example, to correlate with indices of a referring resource, use:
    null_resource.default[count.index]

Error: Missing resource instance key

  on .terraform/modules/jenkins.efs_backup.resource_role_label/outputs.tf line 2, in output "id":
   2:   value = "${null_resource.default.triggers.id}"

Because null_resource.default has "count" set, its attributes must be accessed
on specific instances.

For example, to correlate with indices of a referring resource, use:
    null_resource.default[count.index]

Error: Missing resource instance key

  on .terraform/modules/jenkins.efs_backup.resource_role_label/outputs.tf line 6, in output "name":
   6:   value = "${null_resource.default.triggers.name}"

Because null_resource.default has "count" set, its attributes must be accessed
on specific instances.

For example, to correlate with indices of a referring resource, use:
    null_resource.default[count.index]

Error: Missing resource instance key

  on .terraform/modules/jenkins.efs_backup.resource_role_label/outputs.tf line 10, in output "namespace":
  10:   value = "${null_resource.default.triggers.namespace}"

Because null_resource.default has "count" set, its attributes must be accessed
on specific instances.

For example, to correlate with indices of a referring resource, use:
    null_resource.default[count.index]

Error: Missing resource instance key

  on .terraform/modules/jenkins.efs_backup.resource_role_label/outputs.tf line 14, in output "stage":
  14:   value = "${null_resource.default.triggers.stage}"

Because null_resource.default has "count" set, its attributes must be accessed
on specific instances.

For example, to correlate with indices of a referring resource, use:
    null_resource.default[count.index]

Error: Missing resource instance key

  on .terraform/modules/jenkins.efs_backup.resource_role_label/outputs.tf line 18, in output "attributes":
  18:   value = "${null_resource.default.triggers.attributes}"

Because null_resource.default has "count" set, its attributes must be accessed
on specific instances.

For example, to correlate with indices of a referring resource, use:
    null_resource.default[count.index]

Error: Missing resource instance key

  on .terraform/modules/jenkins.efs_backup.resource_role_label/outputs.tf line 27, in output "tags":
  27:         "Name", "${null_resource.default.triggers.id}",

Because null_resource.default has "count" set, its attributes must be accessed
on specific instances.

For example, to correlate with indices of a referring resource, use:
    null_resource.default[count.index]

Error: Missing resource instance key

  on .terraform/modules/jenkins.efs_backup.resource_role_label/outputs.tf line 28, in output "tags":
  28:         "Namespace", "${null_resource.default.triggers.namespace}",

Because null_resource.default has "count" set, its attributes must be accessed
on specific instances.

For example, to correlate with indices of a referring resource, use:
    null_resource.default[count.index]

Error: Missing resource instance key

  on .terraform/modules/jenkins.efs_backup.resource_role_label/outputs.tf line 29, in output "tags":
  29:         "Stage", "${null_resource.default.triggers.stage}"

Because null_resource.default has "count" set, its attributes must be accessed
on specific instances.

For example, to correlate with indices of a referring resource, use:
    null_resource.default[count.index]

Error: Missing resource instance key

  on .terraform/modules/jenkins.efs_backup.role_label/outputs.tf line 2, in output "id":
   2:   value = "${null_resource.default.triggers.id}"

Because null_resource.default has "count" set, its attributes must be accessed
on specific instances.

For example, to correlate with indices of a referring resource, use:
    null_resource.default[count.index]

Error: Missing resource instance key

  on .terraform/modules/jenkins.efs_backup.role_label/outputs.tf line 6, in output "name":
   6:   value = "${null_resource.default.triggers.name}"

Because null_resource.default has "count" set, its attributes must be accessed
on specific instances.

For example, to correlate with indices of a referring resource, use:
    null_resource.default[count.index]

Error: Missing resource instance key

  on .terraform/modules/jenkins.efs_backup.role_label/outputs.tf line 10, in output "namespace":
  10:   value = "${null_resource.default.triggers.namespace}"

Because null_resource.default has "count" set, its attributes must be accessed
on specific instances.

For example, to correlate with indices of a referring resource, use:
    null_resource.default[count.index]

Error: Missing resource instance key

  on .terraform/modules/jenkins.efs_backup.role_label/outputs.tf line 14, in output "stage":
  14:   value = "${null_resource.default.triggers.stage}"

Because null_resource.default has "count" set, its attributes must be accessed
on specific instances.

For example, to correlate with indices of a referring resource, use:
    null_resource.default[count.index]

Error: Missing resource instance key

  on .terraform/modules/jenkins.efs_backup.role_label/outputs.tf line 18, in output "attributes":
  18:   value = "${null_resource.default.triggers.attributes}"

Because null_resource.default has "count" set, its attributes must be accessed
on specific instances.

For example, to correlate with indices of a referring resource, use:
    null_resource.default[count.index]

Error: Missing resource instance key

  on .terraform/modules/jenkins.efs_backup.role_label/outputs.tf line 27, in output "tags":
  27:         "Name", "${null_resource.default.triggers.id}",

Because null_resource.default has "count" set, its attributes must be accessed
on specific instances.

For example, to correlate with indices of a referring resource, use:
    null_resource.default[count.index]

Error: Missing resource instance key

  on .terraform/modules/jenkins.efs_backup.role_label/outputs.tf line 28, in output "tags":
  28:         "Namespace", "${null_resource.default.triggers.namespace}",

Because null_resource.default has "count" set, its attributes must be accessed
on specific instances.

For example, to correlate with indices of a referring resource, use:
    null_resource.default[count.index]

Error: Missing resource instance key

  on .terraform/modules/jenkins.efs_backup.role_label/outputs.tf line 29, in output "tags":
  29:         "Stage", "${null_resource.default.triggers.stage}"

Because null_resource.default has "count" set, its attributes must be accessed
on specific instances.

For example, to correlate with indices of a referring resource, use:
    null_resource.default[count.index]

Error: Missing resource instance key

  on .terraform/modules/jenkins.efs_backup.sns_label/outputs.tf line 2, in output "id":
   2:   value = "${null_resource.default.triggers.id}"

Because null_resource.default has "count" set, its attributes must be accessed
on specific instances.

For example, to correlate with indices of a referring resource, use:
    null_resource.default[count.index]

Error: Missing resource instance key

  on .terraform/modules/jenkins.efs_backup.sns_label/outputs.tf line 6, in output "name":
   6:   value = "${null_resource.default.triggers.name}"

Because null_resource.default has "count" set, its attributes must be accessed
on specific instances.

For example, to correlate with indices of a referring resource, use:
    null_resource.default[count.index]

Error: Missing resource instance key

  on .terraform/modules/jenkins.efs_backup.sns_label/outputs.tf line 10, in output "namespace":
  10:   value = "${null_resource.default.triggers.namespace}"

Because null_resource.default has "count" set, its attributes must be accessed
on specific instances.

For example, to correlate with indices of a referring resource, use:
    null_resource.default[count.index]

Error: Missing resource instance key

  on .terraform/modules/jenkins.efs_backup.sns_label/outputs.tf line 14, in output "stage":
  14:   value = "${null_resource.default.triggers.stage}"

Because null_resource.default has "count" set, its attributes must be accessed
on specific instances.

For example, to correlate with indices of a referring resource, use:
    null_resource.default[count.index]

Error: Missing resource instance key

  on .terraform/modules/jenkins.efs_backup.sns_label/outputs.tf line 18, in output "attributes":
  18:   value = "${null_resource.default.triggers.attributes}"

Because null_resource.default has "count" set, its attributes must be accessed
on specific instances.

For example, to correlate with indices of a referring resource, use:
    null_resource.default[count.index]

Error: Missing resource instance key

  on .terraform/modules/jenkins.efs_backup.sns_label/outputs.tf line 27, in output "tags":
  27:         "Name", "${null_resource.default.triggers.id}",

Because null_resource.default has "count" set, its attributes must be accessed
on specific instances.

For example, to correlate with indices of a referring resource, use:
    null_resource.default[count.index]

Error: Missing resource instance key

  on .terraform/modules/jenkins.efs_backup.sns_label/outputs.tf line 28, in output "tags":
  28:         "Namespace", "${null_resource.default.triggers.namespace}",

Because null_resource.default has "count" set, its attributes must be accessed
on specific instances.

For example, to correlate with indices of a referring resource, use:
    null_resource.default[count.index]

Error: Missing resource instance key

  on .terraform/modules/jenkins.efs_backup.sns_label/outputs.tf line 29, in output "tags":
  29:         "Stage", "${null_resource.default.triggers.stage}"

Because null_resource.default has "count" set, its attributes must be accessed
on specific instances.

For example, to correlate with indices of a referring resource, use:
    null_resource.default[count.index]

Error: Unsupported argument

  on .terraform/modules/jenkins.efs_backup/iam.tf line 7, in data "aws_iam_policy_document" "resource_role":
   7:     principals = {

An argument named "principals" is not expected here. Did you mean to define a
block of type "principals"?

Error: Unsupported argument

  on .terraform/modules/jenkins.efs_backup/iam.tf line 45, in data "aws_iam_policy_document" "role":
  45:     principals = {

An argument named "principals" is not expected here. Did you mean to define a
block of type "principals"?

Error: Missing resource instance key

  on .terraform/modules/jenkins.elastic_beanstalk_application.label/outputs.tf line 2, in output "id":
   2:   value = "${null_resource.default.triggers.id}"

Because null_resource.default has "count" set, its attributes must be accessed
on specific instances.

For example, to correlate with indices of a referring resource, use:
    null_resource.default[count.index]

Error: Missing resource instance key

  on .terraform/modules/jenkins.elastic_beanstalk_application.label/outputs.tf line 6, in output "name":
   6:   value = "${null_resource.default.triggers.name}"

Because null_resource.default has "count" set, its attributes must be accessed
on specific instances.

For example, to correlate with indices of a referring resource, use:
    null_resource.default[count.index]

Error: Missing resource instance key

  on .terraform/modules/jenkins.elastic_beanstalk_application.label/outputs.tf line 10, in output "namespace":
  10:   value = "${null_resource.default.triggers.namespace}"

Because null_resource.default has "count" set, its attributes must be accessed
on specific instances.

For example, to correlate with indices of a referring resource, use:
    null_resource.default[count.index]

Error: Missing resource instance key

  on .terraform/modules/jenkins.elastic_beanstalk_application.label/outputs.tf line 14, in output "stage":
  14:   value = "${null_resource.default.triggers.stage}"

Because null_resource.default has "count" set, its attributes must be accessed
on specific instances.

For example, to correlate with indices of a referring resource, use:
    null_resource.default[count.index]

Error: Missing resource instance key

  on .terraform/modules/jenkins.elastic_beanstalk_application.label/outputs.tf line 18, in output "attributes":
  18:   value = "${null_resource.default.triggers.attributes}"

Because null_resource.default has "count" set, its attributes must be accessed
on specific instances.

For example, to correlate with indices of a referring resource, use:
    null_resource.default[count.index]

Error: Missing resource instance key

  on .terraform/modules/jenkins.elastic_beanstalk_application.label/outputs.tf line 27, in output "tags":
  27:         "Name", "${null_resource.default.triggers.id}",

Because null_resource.default has "count" set, its attributes must be accessed
on specific instances.

For example, to correlate with indices of a referring resource, use:
    null_resource.default[count.index]

Error: Missing resource instance key

  on .terraform/modules/jenkins.elastic_beanstalk_application.label/outputs.tf line 28, in output "tags":
  28:         "Namespace", "${null_resource.default.triggers.namespace}",

Because null_resource.default has "count" set, its attributes must be accessed
on specific instances.

For example, to correlate with indices of a referring resource, use:
    null_resource.default[count.index]

Error: Missing resource instance key

  on .terraform/modules/jenkins.elastic_beanstalk_application.label/outputs.tf line 29, in output "tags":
  29:         "Stage", "${null_resource.default.triggers.stage}"

Because null_resource.default has "count" set, its attributes must be accessed
on specific instances.

For example, to correlate with indices of a referring resource, use:
    null_resource.default[count.index]

Error: Incorrect attribute value type

  on .terraform/modules/jenkins.elastic_beanstalk_environment/main.tf line 313, in resource "aws_security_group" "default":
 313:     security_groups = ["${var.security_groups}"]

Inappropriate value for attribute "security_groups": element 0: string
required.

Error: Invalid function argument

  on .terraform/modules/jenkins.label_slaves/main.tf line 80, in locals:
  80:     attributes  = "${lower(join(local.delimiter, local.attributes))}"
    |----------------
    | local.attributes is tuple with 1 element

Invalid value for "lists" parameter: element 0: string required.

Error: Invalid value for module argument

  on .terraform/modules/jenkins/main.tf line 71, in module "ecr":
  71:   attributes = ["${compact(concat(var.attributes, list("ecr")))}"]

The given value is not suitable for child module variable "attributes" defined
at .terraform/modules/jenkins.ecr/variables.tf:24,1-22: element 0: string
required.```

Yikes right?

The same happened to me @adambarthelson

closing since the module was converted to TF 0.12 with all latest versions of submodules


Sarama Offset Management

Hey guys,
Been using sarama for sometime now in our processing pipeline! Loving it. I am making an effort to upgrade to the master and I noticed last I check there was some progress on enabling offset tracking, currently I am waiting for acknowledge  and storing that offset in memcached and going off that since offset tracking was reliable back in then.
I was hoping to see an example of where I can reliably get latest offset in order to track my progress through various topics and partitions, also remain tolerant through restarts and consumers no where to start back up on. I would love to get rid of this offset storage mechanism I have built and hoping current sarama has a fix.
If you could provide simple example of this, would be fantastic!
Thanks!

OffsetManager exists and is functional for storing/retrieving offsets on the kafka brokers themselves. However, you'd have to connect it to the consumer manually. https://github.com/bsm/sarama-cluster wraps that functionality to provide an automatic self-balancing consumer if that's more what you're looking for?

that says it supports 0.9+ we are still on 0.8.

Sarama itself only supports Kafka's built-in offset management, which is only available in kafka 0.9 and later. https://github.com/wvanbergen/kafka wraps it to use zookeeper for offset management.

That library also has an example consumer that you could use as a starting point. Closing this issue.


tasks before submission

[ ] A readme/help with implementation examples
[ ] fix the typo
[ ] issue template for submitting tools
[ ] adding manual keyword lists

@EvaMart

and references


[Feature] MultiTarget.

Heya guys! 👋
So a few months back we introduced the StructsAPI(#427), but we didn't really document that nor made a demo. Maybe it was for the better? Because we can use structs really without introducing this API at all. What we couldn't do was to avoid creating multiple providers for multiple targets.
So I thought about this and came up with an idea. I've renamed our StructTarget to MultipleTarget, because you can use this with any type you want, that conforms to TargetType. Additionally, I've made a new target in Demo project, called DemoMultiTarget, that shows how you can use any of the network API that we have (Giphy, GitHub etc.) with just one provider and the MultipleTarget. I've made a new target because it would be hard to see through everything that is now in the Demo target & VC. That way (with usage of new Shared directory), we can reuse most of the code and make two clear examples of different usages.
The last thing I did was to make an example file & link it in the Readme.
I think this could help large projects in splitting logic (or at least I'm pretty sure I will use it in my bigger projects) & make it easier to maintain.
I think that's it! Please comment anything you find strange/bad/superbad in the PR 😈
Cheers! 🎉

Current coverage is 83.14% (diff: 92.98%)

Merging #784 into master will decrease coverage by 2.79%

@@             master       #784   diff @@
==========================================
  Files            30         34     +4
  Lines          2618       2706    +88
  Methods           0          0
  Messages          0          0
  Branches          0          0
==========================================
  Hits           2250       2250
- Misses          368        456    +88
  Partials          0          0

Powered by Codecov. Last update c12f6b1...a08cc6e

Thanks Ash! 🙇

Any idea why Danger didn't run here? Only saw the linter issues here: https://github.com/Moya/Moya/pull/787#issuecomment-262306591. (Fixed those in 7d8489f, FWIW)


add more ide related folder to gitignore

This PR adds more IDE related folder to .gitignore folder

@stotko PTAL, thanks!

Thanks for the contribution! I'm just wondering: Is @zubingtan a colleague of yours and you are submitting this change on behalf of him?

Thanks for the contribution! I'm just wondering: Is @zubingtan a colleague of yours and you are submitting this change on behalf of him?

@zubingtan is me.  Maybe I mix git accounts locally in my computer. It does seem a bit wired...


layouts have to be added to widgets before child widgets are added to layout

If you change the example script in forms.py on lines 86-88 like so:
    layout2.add_widget(Button("View Data", self._view), 1)
    layout2.add_widget(Button("Quit", self._quit), 2)
    layout2.add_widget(self._reset_button, 0)

then you get a very puzzling error:
File "test.py", line 180, in <module>
  Screen.wrapper(demo, catch_interrupt=True, arguments=[last_scene])
File "/usr/local/lib/python3.6/site-packages/asciimatics/screen.py", line 1021, in wrapper
  func(screen, *arguments)
File "test.py", line 171, in demo
  Scene([ContactView(screen, contacts)], -1, name="Edit Contact")
File "test.py", line 148, in __init__
  layout2.add_widget(Button("OK", self._ok), 0)
File "/usr/local/lib/python3.6/site-packages/asciimatics/widgets.py", line 759, in add_widget
  if widget.name in self._frame.data:

AttributeError: 'NoneType' object has no attribute 'data'
The requirement that layouts be added to the parent before further children are added to the layout was surprising to me, and the exception did not help me find the solution to the problem. It would be better if layouts could be added to their parents at any time, but if this is not possible then a more descriptive error would be helpful.

Breaking that ordering will have all sorts of knock-on problems with object initialisation.  It would be necessary to defer everything to the last minute, which means this is likely to be hard.  I'll have a think about this and see what's possible.

Yeah - it proved messy.  I've added a more informative Error.

Thanks!


Frightufur Sheep Attack

Problem when try to get their own boost attacking defense position monster... U_U

Fixed in v<IP_ADDRESS>


Link to github project is incorrect

https://github.com/mpenkov/csvinsight
Should be https://github.com/profoundnetworks/csvinsight

This looks like it got fixed:
(csvi)sergeyich:csvinsight misha$ grep github docs/*.rst
docs/installation.rst:    $ git clone git://github.com/ProfoundNetworks/csvinsight
docs/installation.rst:    $ curl  -OL https://github.com/ProfoundNetworks/csvinsight/tarball/master
docs/installation.rst:.. _Github repo: https://github.com/ProfoundNetworks/csvinsight
docs/installation.rst:.. _tarball: https://github.com/ProfoundNetworks/csvinsight/tarball/master


Should open truss support all native HTML elements?

Native elements are of course not BaseOpenTrussComponents, but that's not actually a requirement to render something using the OT engine. Do we want to limit what is used and have people create more OT-compatible components? Or, do we think it's okay to break that paradigm a bit and use what HTML gives us?
What do you think @open-truss/engineers?

Or, do we think it's okay to break that paradigm a bit and use what HTML gives us?

I'm :+1: on being able to render any component, even POHTML ones 😄


Using ppx_expect does not work with reason

I'm trying to use ppx_expect. I transformed this ocaml sample:
let%expect_test _ =
  print_endline "Hello, world!";
  [%expect{|
    Hello, world!!
  |}]

To reason:
let%expect_test "foo" = {
  print_endline("Hello, world!");
  %expect
  {|
    Hello, world!!
  |};
};

Then I don't get any output when I run esy dune runtest. Running the ocaml example does give a failing test:
--- test/example_.ml    2018-12-01 16:34:20.423049283 +0100
+++ test/example_.ml.corrected  2018-12-01 16:37:38.770332016 +0100
@@ -1,5 +1,5 @@
 let%expect_test _ =
   print_endline "Hello, world!!";
   [%expect{|
-    Hello, world!
+    Hello, world!!
   |}]
\ No newline at end of file

I assume that this is a problem with ppx_expect, not with reason. I assume that the ppx_expect evaluator only supports .ml source files

Yes, if the extension point syntax is different in reason then ppx_expect would need to be updated to support it. Looking at the example, I guess that extension points in reason don't have [ and ]? Although, it's a bit odd that you see no output at all.

Hmm, I just tried and the corrected file is generated but is named test.re.ml.corrected rather than test.re.corrected. It's probably the same issue as https://github.com/ocsigen/js_of_ocaml/issues/716 and it should be fixed by ppxlib 0.4.0 that was just released.

I confirm that it works well with ppxlib 0.4.0


Counting the number of filtered entries that contains a custom field

Question
I'm having trouble counting the entries after a filter is applied. I have three different counts that I'm needing to display along with the results. Each of the counts has a new set variable. The entries are not showing the defined query, instead it shows the results of the last set variable. Here is an example.
{# Results of the query #}
{% set entryQuery = craft.entries()
    .section('jobs')
    .search(search)
    .driverType(driverType)
    .truckType(truckType)
%}

{# count of the above query #}
{{ entryQuery|length }}

{# count of the above entryQuery that was posted within the last 14 days #}
{% set start = now|date_modify('-14 days')|atom %}
{% set end = now|atom %}

{% set countNew = entryQuery
    .postdate(['and', ">= #{start}", "< #{end}"])
%}
{{ countNew|length }}

{# count of the above entryQuery that has a custom field of .highNeeds(true) within the entry #}
{% set highNeeds = craft.app.fields.getFieldByHandle('highNeeds') %}
{% set countHighNeeds = entryQuery
    .highNeeds(true)
%}
{{ countHighNeeds|length }}

{# List of queried entries #}
{% for entry in entryQuery %}
This is showing only the entries with a custom field of .highNeeds(true).
{% endfor %}

The last set is overriding the original entryQuery and not showing all the results. It's only displaying the ones marked with .highNeeds(true) in the entry even through I'm calling entryQuery in the for statement in the template for the listings. I'm not calling any of the variables associated with the counts.
Why is the last defined variable set overriding the original entryQuery when it's called?
Additional context
Add any other context or screenshots about the support request here.

Each time you add parameters to entryQuery, it is applied further down the template. To avoid this you can use the clone tag as explained in the Craft docs at https://craftcms.com/docs/3.x/entries-fields.html#working-with-entries-field-data
You should also use entryQuery.count() instead of entryQuery|length.

Well, a 10 second fix for a 3 hour problem. Thanks, @bencroker. Works like a champ.

Glad to hear it!


selector with vue-styled-components

I can not reach an styled component under a wrapper.  I want to use a selector inside it but when i check it from chrome dev tools, styles doesn't seem correct.
export const ButtonWrapper = styled.div`
	display: flex;

	${PrimaryButton} {
		background: red;
	}
`;

i have a same problem

Same here

Duplicated Issue, please see #97.


Help Creating a Plugin to Run Commands on Startup

Hello, there is currently no way to run commands automatically before hyper starts so I want to make a plugin to do this.
I'm trying to use the onApp method and send a command to the terminal. Something like:
exports.onApp = (app) => {
app.runCommand('echo Hello World');
}
I've looked through the docs and there I can't think of a good way to implement this.
Any input is greatly appreciated :)

You can't by that way. At the time the terminal isn't rendered so you can't invoke pty actions.

Hi again, I tried a different approach using middleware and exec (similar to https://github.com/hharnisc/hypercwd) which doesn't work because exec creates a new shell and i want the modifications to be done to main shell. Is there a way i can send commands to the shell using process (like u can to the child-process using exec)?
Also is there a way I can access the terminal directly and write to it? Like this from term.js:
write(data) {
this.term.io.writeUTF8(data);
}
Thanks

Might this be possible with the onWindow method?
https://github.com/zeit/hyper/blob/5773a83dc3211bd76efe4803176ab8b3df4a14be/app/index.js#L310
https://github.com/zeit/hyper/blob/7df5cbac0832ab2e14b20d9fb3a7e371bf2018ae/app/session.js#L73
Perhaps you could use window.sessions and run Session#write(data) on each?

@curz46 I ran with your idea for a bit and came across this issue.
exports.onWindow = function (win) {
win.sessions.get(uid);  //works fine
win.sessions.get(uid).write('blah');  //crashes
};
I'm guessing we don't have access to the write function. I tried bypassing write and just doing win.sessions.get(id).pty.stdin.write('hi'); but that doesn't work either
Is there some way I can use the function rpc.on('data', ..) perhaps?
https://github.com/zeit/hyper/blob/5773a83dc3211bd76efe4803176ab8b3df4a14be/app/index.js#L256

I managed to get it write to the terminal with this:
exports.onWindow = function (window) {
    setTimeout(() => {
        window.sessions.forEach(session => {
            session.write('clear')
        })
    }, 2500)
}

The timeout was the minimum milliseconds I had to wait for it to be visibly written to the terminal. I can't actually find an API method that is called once a session has completely loaded, so maybe you'll have to constantly query if a new session is available using setInterval or something. Note that the command here isn't sent, I'm not sure how to fake an "enter".
https://gyazo.com/16f85392fd827ef667865a245bafee88

You can enter by sending the hex code for enter/return to the terminal the same way you wrote to the terminal. session.write('\x0a');
Also I was able to get output with a Timeout as low as 1000. I'm on OSX Sierra, maybe that has something to do with it.
This is my current code and it works perfectly:
exports.onWindow = function (win) {
     setTimeout(() => {
       win.sessions.forEach(session => {
            session.write('echo hello world');
            session.write('\x0a');
        })
    }, 1000)
};
I have created a git repo if you would like to work together on this: https://github.com/DanInglis/hyper-run


add Thread/get support & References to previous method results

Hello, isn't the method thread_get part missing from the index.ts file?

Hello, isn't the method thread_get part missing from the index.ts file?

I'm trying to add thread test with james:memory. I want to implement one request combining 4 methods (Email/query + Email/get + Thread/get + Email/get) as the description in https://jmap.io/client.html#cold-boot
But I cannot get thread work. I forged some .eml files with related Message-ID/In-Reply-To/References header. Then I use james-cli ImportEml command to import them. But the system didn't recognize threads. May you give me some tips?

But I cannot get thread work. I forged some .eml files with related Message-ID/In-Reply-To/References header. Then I use james-cli ImportEml command to import them. But the system didn't recognize threads. May you give me some tips?

@quantranhong1999 ?

I have done my research about memory-app ThreadIdGuessingAlgorithm implementation. Maybe it was just a naiveAlgorighm?
Anyway, it won't stop the test's logical.:)

I have done my research about memory-app ThreadIdGuessingAlgorithm implementation. Maybe it was just a naiveAlgorighm?

We are using SearchThreadIdGuessingAlgorithm (search on memory) implementation for memory-app.

docker exec e26fd3fdb97c james-cli AddUser user1@localhost password
provisioning mailbox (by fetchSession/login...)
docker exec e26fd3fdb97c james-cli ListUserMailboxes user1@localhost
docker exec e26fd3fdb97c james-cli ImportEml "#private" user1@localhost INBOX /root/conf/1.eml
docker exec e26fd3fdb97c james-cli ImportEml "#private" user1@localhost Sent /root/conf/2.eml
docker exec e26fd3fdb97c james-cli ImportEml "#private" user1@localhost INBOX /root/conf/3.eml
I expect INBOX should be only 1 thread. but mailbox_get shows two threads in INBOX
eml.zip
.

What is the James memory version you are using? BTW can you try Email/query and then Email/get threadId properties to see the mapping between messageId and threadId first?

Good to hear that :')

But collapseThreads result is still multiple threads.

We (in James) did not implement it just yet (as it would require to push aggregation down to the search engine)
Contributions welcomed for the willing ;-)

But collapseThreads result is still multiple threads.

We (in James) did not implement it just yet (as it would require to push aggregation down to the search engine)
Contributions welcomed for the willing ;-)

Now, this pull request just remains ResultReference test. :)

How is the keystore generated? I used a keypair on my pull request #62 I don't know which method is better, but I personally prefair to not have binary files is possible. I think the best method would be to generate the keypair/keystore when running tests if none is found on the directory, and ignore it on .gitignore

https://www.npmjs.com/package/keypair is our need.
I'll remove ResultReference object from this pr because now I think it should be in another pull request. This PR is too complex and putting multiple arguments in one request is another complex thing.

Ready to merge for me.
Thank you for your contribution!


[add] Livro de Javascript

Foi adicionado a segunda edição do livro, traduzido para Português, Eloquent Javascript.

Thanks for your contribution.
Could you please change it, as Travis says, to adhere to our formatting guidelines?
Thanks again!

Thank you. One last thing, which will be covered by travis sooner or later, is alphabetical ordering. Could you please reorder your insertion in alphabetical order? Thanks!


Fix issue #445: Explicitly convert plain outputs to str() before writing out to files

Fixes issue #445

I modified this PR to just create the needed dirs in the CompiledFile class for all input types vs creating in jinja2 explicitly.
After investigating more it makes sense that converting to str() can be done explicitly in Kadet anyway so enforcing the conversion isn't necessary.


How to add some Documentation to a *.stories.yml file

I am trying to add some Documentation to a *.stories.yml file.
But the DocsPage is never shown on the Docs tab in Storybook. Is the addon docs supported or since we use a "server" Storybook framework this is not possible?
My setup:

cl_server: 2.x-dev
drupal: 10.1.0-alpha1
Storybook: 7.0.20
@lullabot/storybook-drupal-addon: 1.0.27

Hello @theodorosploumis
I've been able to add docs to components using Storybook 7 and CL Server, but still struggling to make it work with AutoDocs
Here is an example of button.mdx inside the component folder
{/* Button.mdx */}

import { Canvas, Meta, Primary, Title, Subtitle } from '@storybook/blocks';
import * as ButtonStories from './button.stories.yml';

<Meta of={ButtonStories} name="Documentation"/>

<Title />
<Subtitle />

Bootstrap includes several predefined button styles, each serving its own semantic purpose, with a few extras thrown in for more control.

## Default buttons

<Primary />

<Canvas of={ButtonStories.Default_button} />

The .btn classes are designed to be used with the `button` element. However, you can also use these classes on `a` or `input` elements (though some browsers may apply a slightly different rendering).

When using button classes on `a` elements that are used to trigger in-page functionality (like collapsing content), rather than linking to new pages or sections within the current page, these links should be given a role="button" to appropriately convey their purpose to assistive technologies such as screen readers.

## Outline variants

<Canvas of={ButtonStories.Outlined_button} />

Notice that import * as ButtonStories from './button.stories.yml'; is mandatory as it is used by the component <Meta of={ButtonStories} name="Documentation"/>to be able to put the docs in the sidebar alongside the correct component.
Another option is to skip the import and use a title:
<Meta title="/path/to/your/component" name="Custom docs"/>, but the Meta component is very relevant in order to tell Storybook where to render the docs or to wich component does it belong to.
More info here
And, of course, the main.js should parse the *.mdx files:
const config = {
  stories: [
    "../web/themes/**/*.mdx",
    "../web/themes/**/*.stories.@(json|yml)",
    "../web/modules/**/*.mdx",
    "../web/modules/**/*.stories.@(json|yml)",
  ],
}

I will try to put all this together on the official docs, see this issue

@idiazroncero Can you paste the button.stories.yml here? I am missing some tags and I am not sure what they mean on the yml file (eg the <Primary />).
Thanks!

I'm just working on documenting how to map *.stories.yml values to Storybook Doc block elements. This is a rather complex button.stories.yml i'm using, please note I'm deliberately "overusing" all possible properties here and your example could and even should be less verbose:
title: Radix/Button
tags:
  - autodocs

parameters:
  componentSubtitle: Bootstrap 5 Button Component
  docs:
    description:
      component: Buttons express actions the user can make on the page

argTypes:
  type:
    name: type
    type:
      name: 'string'
      required: true
    description: The button type
    table:
      category: Styling
      type:
        summary: string
        # detail: Bootstrap includes several predefined button styles, each serving its own semantic purpose, with a few extras thrown in for more control.
      defaultValue:
        summary: primary
        # detail: Available styles are predefined by Bootstrap 5 and can be extended.
    control:
      type: radio
    options:
      Primary: primary
      Secondary: secondary
      Success: success
      Danger: danger
      Warning: warning
      Info: info
      Dark: dark
      Light: light
      Link: link

  outline:
    type: boolean
    name: outline
    description: Wether the button renders with an outline instead of a solid background.
    table:
      category: Styling
      type:
        summary: boolean
      defaultValue:
        summary: false

  button_content:
    type: string
    name: button_content
    description: A slot for the button content. It can take a simple string or valid twig markup.
    table:
      category: Content
      type:
        summary: string

  tag:
    type: string
    name: tag
    description: The HTML element that gets rendered as a button. If Link, `url` prop is required
    table:
      category: Behavior
      type:
        summary: string
      defaultValue:
        summary: button
    options:
      Button: button
      Link: a
      Input: input
    control: radio

  url:
    type: string
    name: url
    description: A URL for tag:Link elements.
    table:
      category: Behavior
      type:
        summary: string

  disabled:
    type: boolean
    name: disabled
    description: Wether the button is disabled
    table:
      category: Behavior
      type:
        summary: boolean
      defaultValue:
        summary: false

  # attributes:
  #   type: \Drupal\Core\Template\Attribute
  #   name: attributes
  #   description: The Drupal Attributes object
  #   table:
  #     category: Drupal
  #     type:
  #       summary: \Drupal\Core\Template\Attribute

stories:
  - name: Default button
    primary: true
    args:
      type: primary
      outline: false
      tag: button
      disabled: false
      button_content: Default Button
    parameters:
      docs:
        description:
          story: 'By defaut, the button is a solid, `<button>` HTML element. Use the props to turn it into a link or input, disable it, change its color or its styling to outline and more.'
  - name: Outlined button
    args:
      type: primary
      tag: button
      outline: true
      disabled: false
      button_content: Outline Button
  - name: Linked button
    args:
      type: primary
      outline: false
      tag: a
      url: https://canamo.net
      disabled: false
      button_content: Link as a button
  - name: Disabled input button
    args:
      type: primary
      outline: false
      tag: input
      disabled: true
      button_content: Link as a button

With this button.mdx :+1:
{/* DocumentationTemplate.mdx */}

import { ArgTypes, Meta, Title, Subtitle, Description, Primary } from '@storybook/blocks';
import * as ButtonStories from './button.stories.yml';

{/*
  * 👇 The isTemplate property is required to tell Storybook that this is a template
  * See https://storybook.js.org/docs/react/api/doc-block-meta
  * to learn how to use
*/}

<Meta of={ButtonStories} />

<Title />
<Subtitle />
<Description of={ButtonStories}/>
<Description of={ButtonStories.Default_button}/>

# Default implementation

<Primary />

## Inputs

The component accepts the following inputs (props):

<ArgTypes of={ButtonStories.Default_button}/>

(and of course the component defined on its button.twig and button.component.yml
I get this:

Thanks a lot. Your example helped me find another cool thing with Storybook 7.x.
While looking at the Migration to 7.x docs I realized that now we can embed the raw content of any file inside Storybook using the Doc source without a 3rd party loader!
We can embed anything to Storybook now. Markdown files, twig files, JS files, CSS files etc.
See an exmaple of using the raw content of the Twig file:
// example.mdx
import {Source, Meta} from '@storybook/blocks';
import * as CurrentStories from './example.stories.yml';
import templateSource from './example.twig?raw'; // This is magic! See https://github.com/storybookjs/storybook/blob/next/MIGRATION.md#add-strict-mode

<Meta of={CurrentStories} />

### Source code

[//]: # (This works)
<Source code={templateSource} />

[//]: # (Also, this works)
<pre>
  {templateSource}
</pre>

Well, that's awesome! Thanks.
By the way, after digging through the docs I've put together a reference *.stories.yml snippet with all the possible options a developer might need to use, as well as referencing the related Doc Blocks where possible.
You can see it here

Thank you, Ignacio , Theodoros, :+1:  :1st_place_medal:
This issue helped me a lot.

Issue #3381466: Fixed the Button component when having the HTML tag prop as anchor to provide a Link functionality caveat

Thanks for this issue! I just linked to it from the README.md.


Create New Users - Analysis

This task is to track the analysis efforts.

Working on UI design analysis of the screens.

Working on UI design analysis of the screens.

Task is completed.


[Bug] Combo picker window does not pop up

Expected behavior
After pressing Shift+Win+Return/Enter should appear.
Actual behavior
After pressing Shift+Win+Return/Enter BT icon appears in the task bar, but no combo picker window pops up. If I hover over the BT icon in the taskbar I can see the snapshot of the combo picker. If I click on the icon in the task bar it disappears.
Steps to reproduce the behavior
Beeftext version (e.g. Beeftext v7.0 Portable Edition).
11.0
Operating system version (e.g Windows 10)
Edition	Windows 10 Pro Version	21H1 Installed on	28.05.2020 OS build	19043.1165
Experience	Windows Feature Experience Pack 120.2212.3530.0

Thanks for reporting. I'm aware of this issue, the problem is that it happen in some rather random context. I have not yet found a way to reproduce it at will.

I currently have a similar situation. I just installed the app on Windows 10 for context. Activating it causes it to pop up behind other windows. Clicking on the taskbar icon and putting it in focus brings it to the front and makes it usable. I just think it's not being given focus when it's launched

Thanks for your input. I will be investigating, this is very annoying. The root cause is a 'feature' of Windows that prevent applications from 'stealing' the focus, in order to prevent invasive pop-ups installed by malware. Other applications manage to properly pop-up in any case. I'm an avid keypihrina user, and they do a good job at displaying properly, so I know it's possible.
I will investigate potential link to the change of display configuration.

good luck! thanks for looking out. if you'd like another example, PowerToys  does it quite nicely. They implemented it based on this repo

Can you please test the following build? I'm not sure it fixes the issue, as I cannot reproduce it at will.

Beeftext-12.0-Installer.zip
Beeftext-12.0-PortableEdition.zip

I tested and recorded a video of my findings, including as much detail as i could think to
https://youtu.be/DYGPGkr80-E
I hope this helps! video is still processing at the time of comment, so you might wanna give it some time to be available and HD

Thanks for the very detailed video 👍 .
Regarding the position of the picker when called from the desktop, you're right, it is naively computed from the desktop geometry as seen by Qt. I can improve that.
I'm rather surprised by the positioning on the screen with a different scaling. I have to look at how Qt handles this.
As for the window popping up below the currently active one, I still have to investigate.

no problem!
i mean the desktop position isn't a bit problem at all - how often are people gonna be using beeftext when renaming desktop shortcuts? maybe if they have like sticky notes on their desktop, idk
good luck! :)

Hi @domportera.
I've made some changes to the way Beeftext handle the combo picker shortcut. The conditions for Windows to allow a window to pop-up on top of other windows is rather strict, and the change I implemented could be helpful.
The drawback of this is that this method forbids the use of the Windows key in a shortcut. I've made a test build, The shortcut is hard-coded: Ctrl+Alt+Shift+Enter. You can disable it in the preferences, but any change of the shortcut will have no effect.
Please let me know if it fixes the problem for you:

Beeftext-12.0-Installer.zip
Beeftext-12.0-PortableEdition.zip

PS: this build also include the for #454.

this seems to work right off the bat! The combo picker is consistently coming up. However, #454 doesn't seem to be fixed for me - the picker is still showing up at the center of my displays when the desktop is in focus

Good to know (except for #454). I'll work on getting the fixed properly implemented with the shortcut modifiable.


Refactor action.yml to use the isogenerator container file we build rather than individual make steps in the action

This would ensure we are using the isogenerator container to build rather than having a separate build process and re-implementing steps in the action each time we do an update.

I kinda did some of the work in this repo
https://github.com/rsturla/eternal-iso-generator
However I could not split the build into multiple steps because the files are written to the /isogenerator directory.  The only way to share these build artifacts would be to somehow mount the /isogenerator folder in the image without clearing out the code that's already in directory from the repo.
I decided to use docker run commands because that way the end user's workflows do not need to provide privileged access to the host, or run the workflow on a Fedora container, as we are doing now.


camera shown only on one device

Hi, ive come with another issue, i only have the camera on the first device ive added, if i open home app on other devices (ipad or macbook) i cant find the camera/door sensor ive got on iphone. Also the sensor is not firing up only sometimes.

@divemasterjm Sorry to hear you are having more issues.  The "external" devices in homebridge can apparently get into a funky state.  First, make sure you only have the ring plugin running in a single instance of homebridge, and make sure you don't have any other ring camera plugins (like homebridge-platform-ring-video-doorbell) running, as these can mess with notification reliability.  Assuming that is all good, your best bet is to strip out the existing cameras from your homebridge config and re-add them.  Here are the steps for cleanup:

Stop homebridge
Go into your ~/.homebridge/persist directory and finding any AccessoryInfo.${uniqueId}.json files that relate to your camera.  You can open them up and they have the device name right at the start of the file.  Keep track of the ${uniqueId} values for your cameras. Delete each camera's AccessoryInfo.${uniqueId}.json and associated IdentifierCache.${uniqueId}.json file
Remove the cameras from HomeKit via the Home app
Start homebridge
Re-add the cameras like you did the first time around

Hopefully that gets you straightened out.  Let me know if you run into any other issues or if this doesn't resolve the problem

i tried everything you told me, still doesnt work, have you think to put also the ring sensor?

By ring sensor, do you mean a sensor that gets triggered when you press the doorbell? If so, it is already present.  HomeKit hides it behind the scenes as part of the camera, but it should still trigger notifications when the doorbell is pressed.  Do you want to see it as a separate sensor like it was in homebridge-platform-ring-video-doorbell?

yes is very useful if you want to do any actions when triggered, like play sound trouhgt homepod, ive been investigating a bit, the prroblem of camera on others is ios 13 beta.

Ahh, great to know you tracked that issue down!  I haven't tried ios 13 beta yet, but I'll hold off now that I know it's causing issues.  Thanks for letting me know!
As for the sensor switch, I'll look into getting it added.

@divemasterjm I've added a StatelessProgrammableSwitch in v3.3.0.  You can add actions to the Single Press event.  Notifications for doorbell presses are handled separately, as part of the main camera feed settings

@divemasterjm I've added a StatelessProgrammableSwitch in v3.3.0. You can add actions to the Single Press event. Notifications for doorbell presses are handled separately, as part of the main camera feed settings

pretty cool that you added this. Anyway to make it an option in parameters so that if people don't want it they can disable it?

Thanks, I will give a try, if you some beta test just tell me. I’ve got appletv 4 and iPad running iOS 13 and HomePod, iPad Pro, MacBook and iPhone XS Max on Las iOS 12.

Hi, after trying 3.3.0 i have no snapshot image on camera anymore

After disabling iOS 13, still have problems on others devices only on the one I’ve added camera

@divemasterjm sorry to hear you are still having issues.  I would recommend going through the remove/add process again that I detailed before.  Probably something weird in HomeKit on ios 13 beta

After 24h of sync, now is working except sensor which is in another thread, thanks for your support.

I still cannot get the ring camera screenshot to show up on a second device (invited user via homekit). I am on the latest version of your module and I followed your instructions above by deleting the files and re-adding the camera. I just can’t get it to show the camera screenshot on my wife’s phone. Any help would be appreciated.

@briangot2 See #45.  Do you have a doorbell_v3? (Check the Model section in the camera settings in the Home app)

Yes. doorbell_v3


ee10 new class needed for com.google.apphosting.runtime.jetty.ee10.ParseBlobUploadHandler

There is a ParseBlobUploadFilter.java there, but it should be a ParseBlobUploadHandler
How can we clone it from the ee8 directory which uses org.eclipse.jetty.ee8.nested.HandlerWrapper that is not available in ee10.

Or maybe the filter is correct there, it was done for ee10 and is correctly registered. We can close this bug if this is correct.

This was done because it is not simple to wrap the parameters from a jetty-core handler.
I have now restricted the filter to be only on REQUEST dispatcher type. But we are investigating to see how this can be done with a jetty-core handler, which may require us to make some changes in Jetty 12.


SUGGESTED FEATURE - Map tile

Hello, this is an idea to make use of the empty tiles in the output videos.

In one, the info from the event.json could be displayed (i.e. coordinates, city, timestamp)
In the other, a map with a red dot on the coordinates from event.json.
Anyone interested?

Great idea!

I also think it sounds like a good idea. For what it's worth, I added an option to prepend a map of the event location at the start of the video here, https://github.com/ehendrix23/tesla_dashcam/pull/154, which is now available after some fixups of my mistakes by @ehendrix23.
I don't know enough about ffmpeg to figure out how to add it in one of the empty tiles though, unfortunately.

I also think it sounds like a good idea. For what it's worth, I added an option to prepend a map of the event location at the start of the video here, #154, which is now available after some fixups of my mistakes by @ehendrix23.

This is actually a very good step, thanks. If you can generate already the one-frame video, looking at the code it should not be impossible to add it to one of the unused frames.

Hi there, is this mod working on linux?
I get tesla_dashcam: error: unrecognized arguments: --title-screen-map

@MarcFinns , it should be --title_screen_map. I think it maybe changed since the first version of the pull request.

I got an even bigger error, The entire video is the map.

I got an even bigger error, The entire video is the map.

Can you open another issue for this and then run it with DEBUG log level and provide that together with full command (including parameters)?

I ran a little test and figured out how to add a map tile in the top left corner with a manual ffmpeg command based on what the script generates. The magic line was this:
[right1][map] overlay=eof_action=repeat:repeatlast=1:x=0:y=0 [map1];

The important bit is to turn on "repeat" and set "repeatlast=1" or it'll just flash the image briefly and go black.
You also need to add a new input with the map image (most of the code is already there from the title screen option).
I'm not familiar enough with the script to turn this into a full PR, esp. when you want to support multiple layouts and such, but it might be a good starting point.
My full command looks something like this:
cmd = ['ffmpeg',
 '-loglevel',
 'info',
 '-i',
 'test_data/2023-05-26_14-04-18/2023-05-26_14-03-15-front.mp4',
 '-i',
 'test_data/2023-05-26_14-04-18/2023-05-26_14-03-15-back.mp4',
 '-i',
 'test_data/2023-05-26_14-04-18/2023-05-26_14-03-15-left_repeater.mp4',
 '-i',
 'test_data/2023-05-26_14-04-18/2023-05-26_14-03-15-right_repeater.mp4',
 '-i',
 'test_data/map.png',
 '-filter_complex',
    'color=duration=59.85:s=1920x960:c=black, fps=24 [base];'
    '[0:v] setpts=PTS-STARTPTS, scale=640x480  [front];'
    '[1:v] setpts=PTS-STARTPTS, scale=640x480 , hflip [rear];'
    '[2:v] setpts=PTS-STARTPTS, scale=640x480 , hflip [left];'
    '[3:v] setpts=PTS-STARTPTS, scale=640x480 , hflip [right];'
    '[4]null[map];'
    '[base][front] overlay=eof_action=pass:repeatlast=0:x=640:y=0 [front1];'
    '[front1][rear] overlay=eof_action=pass:repeatlast=0:x=640:y=480 [rear1];'
    '[rear1][left] overlay=eof_action=pass:repeatlast=0:x=0:y=480 [left1];'
    '[left1][right] overlay=eof_action=pass:repeatlast=0:x=1280:y=480 [right1];'
    '[right1][map] overlay=eof_action=repeat:repeatlast=1:x=0:y=0 [map1];'
    "[map1] drawtext=fontfile=/usr/share/fonts/opentype/freefont/FreeSans.otf:fontcolor=white:fontsize=24:borderw=2:bordercolor=black@1.0:x=(w/2-text_w/2):y=(h-(text_h)-10):text='%{pts\\:localtime\\:1685075595\\:%x "
    "%X}' [tmp0]",
 '-map',
 '[tmp0]',
 '-preset',
 'medium',
 '-crf',
 '28',
 '-c:v',
 'libx264',
 '-metadata',
 'creation_time=2023-05-26T04:33:15.000000Z',
 '-metadata',
 'description=Created by tesla_dashcam v0.1.21b2',
 '-metadata',
 'title=SENTRY: 05/26/23 14:03:19',
 '-y',
 'test_data/output/2023-05-26T14-03-15.mp4']


App2Service support

This is an initial draft for supporting App2Service flows.
What is missing:

In Spring applications the certificate is not available in the security context, see https://github.com/SAP/cloud-security-services-integration-library/issues/1332
ProofToken data is not passed back to the application. Tbd how data is passed from a validator to the application. Maybe extending the Token interface for this?
ProofToken data does not contain the plan. I guess this would be needed for AMS to be able to react on it.
X509Certificate is using X500Principal.RFC1779 formatting, while standard in identity broker is RFC2253.  Also the trim() looks a bit weird.

closing, as outdated approach


华为2340*1080无法适配有什么好的建议或解决问题的思路吗

Environment

[x] Autosize Version:
[x] Target Android Version:
[x] Device Model:
[x] Device Resolution:
[x] Design Size On AndroidManifest:

Bug Description:

Log:

Screenshot

Related Code:

Others:

Environment

[x]  Autosize Version:
[x]  Target Android Version:
[x]  Device Model:
[x]  Device Resolution:
[x]  Design Size On AndroidManifest:

Bug Description:
Log:

Screenshot
Related Code:

Others:

兄弟 你的这个适配解决了么


Connect API - failed to GetFileWithUUID

Your environment
SDK Version: v1.2.0
Connect Server Version: 1.5.0
OS: Ubuntu 20.04.2 LTS
Go Version: go1.17.2 linux/amd64
What happened?
I was trying to download all the documents of a particular vault using the sdk, I noticed that a few files were not downloaded and when I checked the docker logs for the connect API service I saw the error
log_message":"(W) Server: (failed to GetFileWithUUID), attempting to decrypt message with KID  using KID , client used wrong Key","timestamp":"2022-02-21T07:23:18.570941261Z
I'm using the method client.GetFileContent() to get the file content
I also saw a old post for the cli : https://1password.community/discussion/87002/op-get-document-fails-with-a-500-error , I think it might be the same issue, I re-uploaded the file and the issue was solved but Is there a way I can gracefully handle this in code without the need to re-upload the file?
What did you expect to happen?
To get the file content without any issue
Steps to reproduce
this only happens for a few files

@amitjoseph I have noticed this happen on Document type secrets that I copied from one vault to another, using the 1Password app. - I was able to fix them by deleting them and re-uploading them, (instead of copying from another vault.) Hope that helps.


Simplify HttpContextAccessor (now singleton)

MVC tests all pass with this change so looks good I think
cc @davidfowl @lodejard @divega

@davidfowl Restored the callcontext/asynclocal logic

After the changes, :shipit: !

Merged 16a811479eb4f098387b0bcd6702e25003ae6c59 still need to update the test


Strip top level danger from DSL JSON

As discussed in #42 we could trim the bytes off the DSL JSON data until the top level danger object is removed.
The code is pretty nasty but it basically:

deletes all bytes up until the second { from the start
removes all bytes up to and including the first } from the end

It's 13 leading bytes and 2 trailing bytes... but this method should account for any fluctuation

Fails

:no_entry_sign:

` failed.

Log
Ran with: Dangerfile.swift /tmp/danger-dsl.json /tmp/danger-response.json
Failed to parse JSON:
keyNotFound(Danger.DSL.(CodingKeys in _125A41DBF2E88FF661E0539497E789E1).danger, Swift.DecodingError.Context(codingPath: [], debugDescription: "No value associated with key danger (\"danger\").", underlyingError: nil))
Updating packages...
$ cd "/home/travis/build/danger/danger-swift/" && swift --version
Swift version 4.0 (swift-4.0-RELEASE)
Target: x86_64-unknown-linux-gnu
$ cd "/home/travis/.danger-swift/Packages/Generated/" && swift package --enable-prefetching update

$ cd "/home/travis/.danger-swift/Scripts/Cache/-home-travis-build-danger-danger-swift-_dangerfile_imports/.build/" && ln -s "/home/travis/.danger-swift/Packages/Generated/.build/checkouts/" "checkouts"

$ cd "/home/travis/.danger-swift/Scripts/Cache/-home-travis-build-danger-danger-swift-_dangerfile_imports/.build/" && ln -s "/home/travis/.danger-swift/Packages/Generated/.build/repositories/" "repositories"

$ cd "/home/travis/.danger-swift/Scripts/Cache/-home-travis-build-danger-danger-swift-_dangerfile_imports/" && ln -s "/home/travis/.danger-swift/Packages/Generated/Package.resolved" "Package.resolved"

$ cd "/home/travis/.danger-swift/Scripts/Cache/-home-travis-build-danger-danger-swift-_dangerfile_imports/" && ln -s "/home/travis/build/danger/danger-swift/_dangerfile_imports.swift" "OriginalFile"

$ cd "/home/travis/.danger-swift/Scripts/Cache/-home-travis-build-danger-danger-swift-_dangerfile_imports/" && readlink OriginalFile
/home/travis/build/danger/danger-swift/_dangerfile_imports.swift
Cloning https://github.com/JohnSundell/Files.git...
$ cd "/home/travis/.danger-swift/Packages/Temp/" && git clone https://github.com/JohnSundell/Files.git Clone -q

Resolving latest major version for https://github.com/JohnSundell/Files.git...
Updating packages...
$ cd "/home/travis/build/danger/danger-swift/" && swift --version
Swift version 4.0 (swift-4.0-RELEASE)
Target: x86_64-unknown-linux-gnu
$ cd "/home/travis/.danger-swift/Packages/Generated/" && swift package --enable-prefetching update
Fetching https://github.com/JohnSundell/Files.git
Cloning https://github.com/JohnSundell/Files.git
Resolving https://github.com/JohnSundell/Files.git at 2.0.1
$ cd "/home/travis/build/danger/danger-swift/" && swift --version
Swift version 4.0 (swift-4.0-RELEASE)
Target: x86_64-unknown-linux-gnu
$ cd "/home/travis/.danger-swift/Scripts/Cache/-home-travis-build-danger-danger-swift-_dangerfile_imports/" && swift build -C /home/travis/.danger-swift/Scripts/Cache/-home-travis-build-danger-danger-swift-_dangerfile_imports/ --enable-prefetching
Compile Swift Module 'Files' (1 sources)
Compile Swift Module '_dangerfile_imports' (1 sources)
Linking ./.build/x86_64-unknown-linux/debug/_dangerfile_imports
Updating https://github.com/JohnSundell/Files.git
Cloning https://github.com/JohnSundell/Files.git
Resolving https://github.com/JohnSundell/Files.git at 2.0.1
Running: /home/travis/.swiftenv/shims/swiftc --driver-mode=swift -L .build/debug -I .build/debug -lDanger -L .build/debug -I .build/debug -L /home/travis/.danger-swift/Scripts/Cache/-home-travis-build-danger-danger-swift-_dangerfile_imports/.build/debug -I /home/travis/.danger-swift/Scripts/Cache/-home-travis-build-danger-danger-swift-_dangerfile_imports/.build/debug Dangerfile.swift /tmp/danger-dsl.json /tmp/danger-response.json
Dangerfile eval failed at Dangerfile.swift
Could not get the results JSON file at /tmp/danger-response.json

  Generated by :no_entry_sign: dangerJS

Ok looks like I misunderstood the issue 😅 😅

Yeah, think it is that the STDIN that gets passed into the runner side might have that first danger stripped, not sure, don't have time to look in


get the TBA to pay it's own fees? [TS, Starknet.js]

TBA's should pay fees when execute is called.
Roadblock: Paymasters

Hi @Darlington02, if this has not been fixed, I would like to jump on it.

Hey @princeibs the reason this remains a pending issue is, it'd be tricky to implement without paymasters. I have an idea hacking around SNIP-9, but DYOR and let me know what you come up with. We could hop on a call if need be

Alright. I will surely make some research and update you on my findings


Docker-in-Docker issue.

Hey! Thanks for the work you'd done getting systemd running in an Ubuntu container. I'm trying to utilise what you've done using a a container within a container (Chef/Kitchen testing) and using the test container documented in the README I get the following error:
[root@698c28dc0f10 ~]# docker logs 69d925db484b
The systemd cgroup hierarchy is already mounted at /sys/fs/cgroup/systemd.
Your Docker host is now configured for running systemd containers!
[root@698c28dc0f10 ~]# docker run -d --name systemd --security-opt seccomp=unconfined --tmpfs /run --tmpfs /run/lock -v /sys/fs/cgroup:/sys/fs/cgroup:ro -t solita/ubuntu-systemd
7675be4a3fb0440c834739f7af790b4a4ca58b896769b065c4c0ca0a8edaf26e
[root@698c28dc0f10 ~]# docker logs systemd
systemd 229 running in system mode. (+PAM +AUDIT +SELINUX +IMA +APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT +GNUTLS +ACL +XZ -LZ4 +SECCOMP +BLKID +ELFUTILS +KMOD -IDN)
Detected virtualization docker.
Detected architecture x86-64.

Welcome to Ubuntu 16.04.2 LTS!

Set hostname to <7675be4a3fb0>.
Initializing machine ID from random generator.
Cannot determine cgroup we are running in: No medium found
Failed to allocate manager object: No medium found
[!!!!!!] Failed to allocate manager object, freezing.
Freezing execution.

Unfortunately I don't have much experience with Docker-in-Docker nor the time to investigate this issue. If you can come up with a change to solita/ubuntu-systemd that fixes the problem, I'd be happy to merge it and credit you as a contributor.
I don't know the details of your situation but, as a workaround, perhaps you could start sibling containers instead of child containers? (See "The solution" at the end of the article.) I've used that approach successfully when I've needed to use Docker in a container.

Thanks for the reply. I'll let you know what I come up with.
On 25 July 2017 at 10:47, Timo Mihaljov<EMAIL_ADDRESS>wrote:

Unfortunately I don't have much experience with Docker-in-Docker nor the
time to investigate this issue. If you can come up with a change to
solita/ubuntu-systemd that fixes the problem, I'd be happy to merge it
and credit you as a contributor.
I don't know the details of your situation but, as a workaround, perhaps
you could start sibling containers
https://jpetazzo.github.io/2015/09/03/do-not-use-docker-in-docker-for-ci/
instead of child containers? (See "The solution" at the end of the
article.) I've used that approach successfully when I've needed to use
Docker in a container.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/solita/docker-systemd/issues/10#issuecomment-317687090,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AE6NkjhnQ6NWBe9uNzvQpL5sGFXTvSbRks5sRbmwgaJpZM4OiMaI
.


Add lazy decorator

Q
A

Is bugfix?
❌

New feature?
✔

Breaks BC?
❌

Fixed issues

I think better create separate package for proxy decorator. If user need this, him can install this new package and use decorator in factory or container.

I think better create separate package for proxy decorator. If user need this, him can install this new package and use decorator in factory or container.

Why do you think so?

https://github.com/yiisoft/definitions/pull/58


Not displayed on wrapped lines

Problem
We might want to display the indent indicators on wrapped lines.
See :help breakindent

Here it looks a bit odd not to have indicators on the wrapped line.
Steps to reproduce
:set breakindent
Expected behavior
Have the indent indicators correctly displayed on breakindent-ed wrapped lines.
Neovim version (nvim -v)
NVIM v0.9.2

mb, duplicate of #577


Clang crashes on IR input created by JIT compiler

Clang will crash compiling some IR. At present this can be seen when enabling the JIT compiler for SkotOS.
The cause is that the JIT compiler will put at most one entry for any predecessor block in a PHI node, while clang expects multiple entries in the case of a switch with more than one case jumping to the PHI node's block. The JIT compiler could be made to comply with clang's requirements by reversing commit fd4172982d59ca52de40b2792d64f2ec8e2c800e.
The LLVM team is considering changing over to having at most a single PHI node entry per predecessor block, which would make the JIT compiler's current behaviour correct. The issue is tracked here.

This issue is preventing using the LLVM libraries as an inline compiler, since that would crash the actual JIT compiler rather than clang.

Solved by commit 770c7be8d85975a033aaef35cb3c01be3405fe91.


[WIP] perl: build deterministically

removes a uname, username and date mention in the output
resets the hash seed for the build
sets configuration date to $SOURCE_DATE_EPOCH

Motivation for this change
As it is, Perl does not build deterministically because some information about the build system as well as the build date is written to the output. This patch seeks to remedy this situation.
Things done

[x] Tested using sandboxing
Built on platform(s)

[x] NixOS (x86-64 and ppc64le)
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nox --run "nox-review wip" (I have no time to rebuild all of nixpkgs)
[ ] Tested execution of all binary files (only those used in the build of further packages, e. g. the bootstrap files or a NixOS system)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[x] Fits CONTRIBUTING.md.

Nice, thank you for working on this! Please add comments to your changes, explaining the reasons. It would be ideal to propose upstream changes that make patches unnecessary.
Also you shouldn't put the details in the commit headline, they should be in the description text.

Added a comment in the Nix expression and reformatted the commit message.
How would I go about contacting Perl upstream maintainers? I fear I am not used to contributing such long-established projects (or open-source projects in general to some extent) …

Yeah it can be a bit intimidating. You usually start by looking at the meta homepage attribute and go from there. In this case that leads to https://www.perl.org/community.html. Maybe just ask on their IRC if this is an issue they'd consider fixing and how best to go about it?

cc @volth

LGTM, but it would be nice to see the rationale
.
I see that we gave up the neurotic goal of total reproducibility keeping it only for the packages which really need it (for example, fontforge which builds fixed-output-derivations of fonts and leaks own compilation time/user into the font metadata)

The idea is that since the bootstrap files are pulled in as trusted binaries, they (and everything on the path to building them) should at least be reproducible. With a second patch to make-bootstrap-tools.nix I have everything except GCC building deterministically and idempotently on my machines (and, on my as of yet unpublished ppc64le port, all of it). So this is one step to making this critical piece of infrastructure reproducible.
Re: fontforge building fixed-output derivations: those don't result in the same file on ppc64le BTW.

After talking to some perl packagers and looking into how Debian package their perl, I've rewritten the PR to use some config overrides instead of using a patch to rip out offending lines. I don't have the time to test it in any real capacity today, I'll write back tomorrow.

LGTM, but it would be nice to see the rationale
.
I see that we gave up the neurotic goal of total reproducibility keeping it only for the packages which really need it (for example, fontforge which builds fixed-output-derivations of fonts and leaks own compilation time/user into the font metadata)

Did we give that up? I think it is a very practical goal with big advantages. Everything is not practical, but I'm happy about every additional reproducible package. I see that the effort has stalled a bit, but I would be sad if we actually gave that up.
@CrystalGamma nice, keep us updated when you tested it.

And you even found a place to report it upstream, awesome :)

I've run the test suite, and it seems to produce one more failure than staging, which is weird since it seems to be a part of the language itself rather than anything interacting with the system. I'll investigate it some more …

Are there any updates on this pull request, please?

Any updates?

Hi! I agree that perl binaries should be reproducible, will try to have a look at this PR a bit later.
Some links on the current status in Debian/Arch:

https://ismypackagereproducibleyet.org/?pkg=perl&query=query (In openSUSE it's marked as reproducible)
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/perl.html
https://tests.reproducible-builds.org/archlinux/core/perl/perl-5.32.0-3-x86_64.pkg.tar.zst.html
https://bugs.debian.org/972559

Rebased this PR against master in https://github.com/stigtsp/nixpkgs/commit/ebfa2534e97fb3e8150deed2618f0a862aae8af6, and did a build (with --check) of perldevel on two separate NixOS machines.
The both return:
$ nix-hash --type sha256 /nix/store/ysmbh64nhzjhjkvjh0cl5pv6ikc7njqk-perl-5.33.4
f8fc41bb8faafc5e644caf71d3ef18ca1cc103c424c9b254e4364fd225d78280
Both outputs give the same hash, appears to be reproducible.

Running NixOS on my MacBook Pro 11,1:
$ git remote add -f stigtsp git\@github.com\:stigtsp/nixpkgs
$ git checkout ebfa2534e97fb3e8150deed2618f0a862aae8af6
$ nix-hash --type sha256 $(nix-build -A perldevel)
# -- snip --
f8fc41bb8faafc5e644caf71d3ef18ca1cc103c424c9b254e4364fd225d78280

@CrystalGamma Sorry, this has taken a while. But are you available to continue this PR? If not, I'm happy to move your contributions to a new PR and work on finishing it.

openSUSE's reproducibility patches:
https://github.com/bmwiedemann/openSUSE/blob/master/packages/p/perl/perl-reproducible.patch
https://github.com/bmwiedemann/openSUSE/blob/master/packages/p/perl/perl-reproducible2.patch (to drop ASLR influences in the last bits)

openSUSE's reproducibility patches:
https://github.com/bmwiedemann/openSUSE/blob/master/packages/p/perl/perl-reproducible.patch
https://github.com/bmwiedemann/openSUSE/blob/master/packages/p/perl/perl-reproducible2.patch (to drop ASLR influences in the last bits)


Upgrade Sentry Client

Again...

@EdOverflow has looked into tooling to help us stay up to date with (Python) deps. Have those tickets handy, @EdOverflow?

@whit537 I do not believe there are any open tickets. This may have simply been a discussion on the Slack channel.

I was thinking of the pyup integration, e.g., https://github.com/gratipay/gratipay.com/pull/4376.


Add a link to this git repository

Might be worth adding an easily accessable "feedback/suggstions" button on the site.

That's definitely a good idea, will add that in the next update


issues with pychopper and direct cDNA

Hi there,
On the ONT community website, there is a warning against using pychopper for direct cDNA data using the LSK114 kit claiming that  "Pychopper currently miss-classsifies The reads generated with Direct cDNA Sequencing are not being classified correctly in the analysis workflow, leading to ≥80% data loss of full-read transcripts"
I was wondering if you are more familiar with this issue and have an idea of restrander's performance with direct cDNA protocols from ONT.
Thanks,
Sowmya

Hi Sowmya,
As far as I know, Restrander should have no issue with direct cDNA data using the LSK114 kit. I've just added a config file for it using the primers from this document. If you download the latest version of Restrander, you can try it out using ./restrander input.fq.gz output.fq.gz config/DCS-LSK114.json.
We don't have any local DCS LSK114 data to test it on - if you do try it out, please let me know if it works, or if there are any issues!
Thanks
Jakob

Thanks Jakob! Will test this out.
Sowmya


Issue generation job exits without completing after failure

Describe the bug
If a repository in data.csv exists but does not allow for issue creation (issues turned off, repository is archived) the job will fail at that point. Any issues in repositories before that are created, but the job exits and does not create any further issues.
I noticed that in the test run, scenarios where repositories simply do not exist seem to proceed with a warning just fine.
Steps to reproduce the behavior

Use a data.csv file with a repository that exists but is not able to create an issue
Note in the logs the failure, and that no subsequent issues are created

Expected behavior
The job should fail entirely or repositories should be noted in the logs, but the job should continue.

The check for repo existence gracefully handles request errors.
We should wrap the API call in createIssues and createComments to catch and warn on request errors, so that one buggy repo doesn't halt the entire operation.


Add StrMap.mapWithKey

Please take a look! Thanks. 😃
P.S. I added a test for Map.mapWithKey while I was at it.

Looks good to me 👍

I think the tests will pass when we finish updating the core libraries, this is due to transformers needing functional dependencies adding for the latest compiler.

👍 Looks great, thanks!

Merged as #74. Thanks!


Planning to support latest Calendar.io version ? (2.4.0) ?

Hi sir,
Congratz with your great work !!
Do you plan to update your software to the latest Calendar.io version ?
Thanks in advance for your reply,
Johnny (Belgium)

You mean FullCalendar, right? :)
Of course, once I can get some spare time.
FullCalendar internals change quite drastically
even for minor versions, so it is not that trivial.

Hu Azam,
Thanks for replying.
REALLY looking forward to your solution.
And if I can contribute somewhere / somehow ... please let me know.
Johnny

Hi,azam.
fullcalendar doesn't have render.
This contains renderSkeletonHtml etc.
I tried to change your source.
But, FullCalendar's Docs is not enough.

@hnp-play
FC changed some of the signatures of the View class after I wrote this module, so what you are seeing is correct if you are using FC later than v2.3.1. You can try downgrading FC to v2.3.1 though.


Document the Let's Encrypt preferred chain feature

In https://github.com/jetstack/cert-manager/pull/3208 (https://github.com/jetstack/cert-manager/issues/1700) we introduce a new field on the ACME issuer spec which allows a user to specify a preferredChain.
We should document when and how to use this with Let's Encrypt and link to LE documentation of this feature.
/kind feature

@wallrj can we move this to the websire repo?

Quite important documentation now that Let's Encrypt is changing its chain: https://letsencrypt.org/2020/11/06/own-two-feet.html

We have documentation over at https://cert-manager.io/docs/release-notes/release-notes-1.0/#preferred-chain
We should copy this into a better place.
Closing this issue as it is related to the website.
/close


adding more unit tests to db_read_utils module and cleaning up lit_processing programs

to add 'no cover' to the untestable functions and adding dqm resource loading related programs and PubMed PMC downloading/Full text searching programs to the ignore list in the .coveragerc file

@azurebrd Thanks for looking over the code.
The additional unit tests are for db retrieving functions (mainly for data exporting and pubmed update).


Use mirror:// source in linux-firmware

The linux-firmware package currently fetches a .tar.gz from git snapshots:
https://github.com/NixOS/nixpkgs/blob/479ba708b0932deeac25062919817e10b85db816/pkgs/os-specific/linux/firmware/linux-firmware/default.nix#L15-L18
For tagged versions, this could instead be sourced from a kernel.org mirror and additionally use .tar.xz for reduced download sizes, e.g.:
src = pkgs.fetchurl {
  url = "mirror://kernel/linux/kernel/firmware/linux-firmware-20240115.tar.xz";
  hash = "sha256-q3yv8Ju7nmjiuKfD6G0ytl9kRMqk74sKq8qVA9osZ40=";
};

On the downside, this may introduce additional complexity in the update.sh script.
/cc @K900

Do we actually care here? It'll basically never be a cache miss for 99% of people.

True - more of a nice to have.


Adding native/introduced, genera, and family counts to summary statement

suggestion from @eflowerproject

how's that @eflowerproject @tmesaglio ?

Excellent!
On Mon, 25 Sept 2023 at 13:23, Will Cornwell @.***>
wrote:

how's that @eflowerproject https://github.com/eflowerproject @tmesaglio
https://github.com/tmesaglio ?
—
Reply to this email directly, view it on GitHub
https://github.com/traitecoevo/infinitylists/issues/69#issuecomment-1732844849,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ANDLDAOMPUADIHDJBTAN7WLX4D2MPANCNFSM6AAAAAA5CRUEPA
.
You are receiving this because you were mentioned.Message ID:
@.***>

--
Dr Hervé Sauquet (he/him)
Head of Plant Discovery and Evolution Research, Senior Research Scientist
Australian Institute of Botanical Science, Royal Botanic Gardens and Domain
Trust
Locked Bag 6002, Mount Annan, NSW 2567, Australia
E-mail: @.*** (or @.***)
Tel: +61 410 798 181 (mobile)
www.eflower.org | www.sauquetlab.org | RBGDT profile
https://www.rbgsyd.nsw.gov.au/Science/Our-science-staff/Dr-Herve-Sauquet
Adjunct Associate Professor, University of New South Wales
Research Affiliate, University of Sydney
Associate Editor, Frontiers in Plant Science
https://www.frontiersin.org/journals/plant-science/sections/plant-systematics-and-evolution
| International Journal of Plant Sciences
https://www.journals.uchicago.edu/journals/ijps/about | Taxon
http://www.ingentaconnect.com/content/iapt/tax