Gitlab CI pipeline with vault-env / webhook

Describe the bug:
I configured gitlab-runner and runner pods to have all annotations required to work with webhook + vault-env injection. Everything is working fine unless pipeline uses services. (https://docs.gitlab.com/ee/ci/docker/using_docker_images.html#what-is-a-service)
If I do not use service my job runner pods getting injected /vault/vault-env binary and I can use all secrets available to me.
If I'm defining services like this:
services:
  - docker:18.09-dind

my pod start and work but there are no injected vault-env so I can't use secrets.
I found workaround: define service not globally but for steps that really needs it. But if that step will need vaulted secret - this will be the end. No way around AFAIK.
Expected behaviour:
All pods with properly crafted env variables should get vount-env injected.
Steps to reproduce the bug:
services:
- docker:18.09-dind

variables:
  KUBERNETES_SERVICE_ACCOUNT: gitlab-runner
  LOCAL_AWS_SECRET_ACCESS_KEY: vault:secret/data/accounts/aws_super_secret#AWS_SECRET_ACCESS_KEY

stages:
  - helm_test

helm:VAULT_test:
  stage: helm_test
  image: some-helm-docker-image
  script:
    - ls -la /vault/*
    - /vault/vault-env /bin/bash -c "echo \${LOCAL_AWS_SECRET_ACCESS_KEY}"

Environment details:

Kubernetes version v1.15.11
Cloud-provider AWS
bank-vaults version 1.1.0:
Install method: helm + static CR manifest

/kind bug

Please install the webhook with failurePolicy enabled:
    # In Helm
    --set podsFailurePolicy=Fail

And observe the logs of the webhook to check what is the issue here, because it is hard to tell, and we don't have a gitlab kubernetes runner at hand.

ERROR: Job failed (system failure): Internal error occurred: failed calling webhook "pods.vault-secrets-webhook.admission.banzaicloud.com": an error on the server ("{\"response\":{\"uid\":\"8f20f344-9b5e-41be-ae01-076c59d0f9bf\",\"allowed\":false,\"status\":{\"metadata\":{},\"status\":\"Failure\",\"message\":\"cannot unmarshal docker configuration from imagePullSecret: unexpected end of JSON input\"}}}") has prevented the request from succeeding

And I checked imagepullsecrets, It's totally valid json.

Here is cleaned up version of pod (added part - dind container):
apiVersion: v1
kind: Pod
metadata:
  annotations:
    iam.amazonaws.com/role: hvjhvjhvjhvhjvhjvjhvjhvjh
    vault.security.banzaicloud.io/vault-addr: https://vault.vault:8200
    vault.security.banzaicloud.io/vault-role: default-gitlab
    vault.security.banzaicloud.io/vault-tls-secret: vault-tls
  creationTimestamp: "2020-05-06T16:04:06Z"
  generateName: runner-qgyh8lfs-project-18432922-concurrent-0
  labels:
    pod: runner-qgyh8lfs-project-18432922-concurrent-0
  name: runner-qgyh8lfs-project-18432922-concurrent-0q5zt5
  namespace: default
  resourceVersion: "78691008"
  selfLink: /api/v1/namespaces/default/pods/runner-qgyh8lfs-project-18432922-concurrent-0q5zt5
  uid: 7ea9d90e-0c41-4a5f-a915-92fa2aff2b2a
spec:
  containers:
  - command:
    - sh
    - -c
    - "if [ -x /usr/local/bin/bash ]; then\n\texec /usr/local/bin/bash \nelif [ -x
      /usr/bin/bash ]; then\n\texec /usr/bin/bash \nelif [ -x /bin/bash ]; then\n\texec
      /bin/bash \nelif [ -x /usr/local/bin/sh ]; then\n\texec /usr/local/bin/sh \nelif
      [ -x /usr/bin/sh ]; then\n\texec /usr/bin/sh \nelif [ -x /bin/sh ]; then\n\texec
      /bin/sh \nelif [ -x /busybox/sh ]; then\n\texec /busybox/sh \nelse\n\techo shell
      not found\n\texit 1\nfi\n\n"
    env:
    - name: FF_CMD_DISABLE_DELAYED_ERROR_LEVEL_EXPANSION
      value: "---"
    - name: FF_NETWORK_PER_BUILD
      value: "---"
    - name: FF_USE_LEGACY_BUILDS_DIR_FOR_DOCKER
      value: "---"
    - name: FF_USE_LEGACY_VOLUMES_MOUNTING_ORDER
      value: "---"
    - name: FF_USE_LEGACY_KUBERNETES_EXECUTION_STRATEGY
      value: "---"
    - name: CI_JOB_IMAGE
      value: ---
    - name: CI_RUNNER_SHORT_TOKEN
      value: ---
    - name: CI_BUILDS_DIR
      value: ---
    - name: CI_PROJECT_DIR
      value: ---
    - name: CI_CONCURRENT_ID
      value: "---"
    - name: CI_CONCURRENT_PROJECT_ID
      value: "---"
    - name: CI_SERVER
      value: "---"
    - name: CI_SERVER_TLS_CA_FILE
      value: |-
        -----BEGIN CERTIFICATE-----
        jknjkbnjkkjbkjbkjb
        -----END CERTIFICATE-----
    - name: CI_PIPELINE_ID
      value: "---"
    - name: CI_PIPELINE_URL
      value: ---
    - name: CI_JOB_ID
      value: "---"
    - name: CI_JOB_URL
      value: ---
    - name: CI_BUILD_ID
      value: "---"
    - name: CI_REGISTRY_USER
      value: ---
    - name: CI_JOB_NAME
      value: ---
    - name: CI_JOB_STAGE
      value: ---
    - name: CI_NODE_TOTAL
      value: "---"
    - name: CI_BUILD_NAME
      value: ---
    - name: CI_BUILD_STAGE
      value: ---
    - name: CI
      value: "---"
    - name: GITLAB_CI
      value: "---"
    - name: CI_SERVER_URL
      value: ---
    - name: CI_SERVER_HOST
      value: ---
    - name: CI_SERVER_PORT
      value: "---"
    - name: CI_SERVER_PROTOCOL
      value: ---
    - name: CI_SERVER_NAME
      value: ---
    - name: CI_SERVER_VERSION
      value: ---
    - name: CI_SERVER_VERSION_MAJOR
      value: "---"
    - name: CI_SERVER_VERSION_MINOR
      value: "---"
    - name: CI_SERVER_VERSION_PATCH
      value: "---"
    - name: CI_SERVER_REVISION
      value: ---
    - name: GITLAB_FEATURES
      value: ---
    - name: CI_PROJECT_ID
      value: "---"
    - name: CI_PROJECT_NAME
      value: ---
    - name: CI_PROJECT_TITLE
      value: ---
    - name: CI_PROJECT_PATH
      value: ---
    - name: CI_PROJECT_PATH_SLUG
      value: ---
    - name: CI_PROJECT_NAMESPACE
      value: ---
    - name: CI_PROJECT_URL
      value: ---
    - name: CI_PROJECT_VISIBILITY
      value: ---
    - name: CI_PROJECT_REPOSITORY_LANGUAGES
      value: ---
    - name: CI_DEFAULT_BRANCH
      value: ---
    - name: CI_PAGES_DOMAIN
      value: ---
    - name: CI_PAGES_URL
      value: ---
    - name: CI_REGISTRY
      value: ---
    - name: CI_REGISTRY_IMAGE
      value: ---
    - name: CI_API_V4_URL
      value: ---
    - name: CI_PIPELINE_IID
      value: "---"
    - name: CI_PIPELINE_SOURCE
      value: ---
    - name: CI_CONFIG_PATH
      value: .gitlab-ci.yml
    - name: CI_COMMIT_SHA
      value: ---
    - name: CI_COMMIT_SHORT_SHA
      value: ---
    - name: CI_COMMIT_BEFORE_SHA
      value: "---"
    - name: CI_COMMIT_REF_NAME
      value: ---
    - name: CI_COMMIT_REF_SLUG
      value: ---
    - name: CI_COMMIT_MESSAGE
      value: ---
    - name: CI_COMMIT_TITLE
      value: ---
    - name: CI_COMMIT_DESCRIPTION
    - name: CI_COMMIT_REF_PROTECTED
      value: "---"
    - name: CI_BUILD_REF
      value: ---
    - name: CI_BUILD_BEFORE_SHA
      value: "---"
    - name: CI_BUILD_REF_NAME
      value: ---
    - name: CI_BUILD_REF_SLUG
      value: ---
    - name: CI_MERGE_REQUEST_EVENT_TYPE
      value: ---
    - name: CI_MERGE_REQUEST_SOURCE_BRANCH_SHA
    - name: CI_MERGE_REQUEST_TARGET_BRANCH_SHA
    - name: CI_MERGE_REQUEST_ID
      value: "---"
    - name: CI_MERGE_REQUEST_IID
      value: "---"
    - name: CI_MERGE_REQUEST_REF_PATH
      value: ---
    - name: CI_MERGE_REQUEST_PROJECT_ID
      value: "---"
    - name: CI_MERGE_REQUEST_PROJECT_PATH
      value: ---
    - name: CI_MERGE_REQUEST_PROJECT_URL
      value: ---
    - name: CI_MERGE_REQUEST_TARGET_BRANCH_NAME
      value: ---
    - name: CI_MERGE_REQUEST_TITLE
      value: ---
    - name: CI_MERGE_REQUEST_SOURCE_PROJECT_ID
      value: "---"
    - name: CI_MERGE_REQUEST_SOURCE_PROJECT_PATH
      value: ---
    - name: CI_MERGE_REQUEST_SOURCE_PROJECT_URL
      value: ---
    - name: CI_MERGE_REQUEST_SOURCE_BRANCH_NAME
      value: ---
    - name: CI_RUNNER_ID
      value: "---"
    - name: CI_RUNNER_DESCRIPTION
      value: ---
    - name: CI_RUNNER_TAGS
    - name: DOCKER_DRIVER
      value: overlay2
    - name: DOCKER_HOST
      value: tcp://<IP_ADDRESS>:2375
    - name: DOCKER_IMAGE_NAME
      value: ---
    - name: AWS_ACCESS_KEY_ID
      value: ---
    - name: AWS_SECRET_ACCESS_KEY
      value: ---
    - name: DOCKER_AUTH_CONFIG
      value: '{"credHelpers": {"---": "ecr-login"}}'
    - name: KUBERNETES_SERVICE_ACCOUNT
      value: ---
    - name: KUBERNETES_CONTEXT
      value: ---
    - name: KUBERNETES_SERVER
      value: ---
    - name: KUBERNETES_TOKEN
      value: ---
    - name: DB_PASSWORD
      value: vault:secret/data/applications/blabla/dev/database#DB_PASSWORD
    - name: STAGE
      value: ---
    - name: GITLAB_USER_ID
      value: "---"
    - name: GITLAB_USER_EMAIL
      value: ---
    - name: GITLAB_USER_LOGIN
      value: ---
    - name: GITLAB_USER_NAME
      value: ---
    - name: CI_MERGE_REQUEST_CHANGED_PAGE_PATHS
    - name: CI_MERGE_REQUEST_CHANGED_PAGE_URLS
    - name: CI_ENVIRONMENT_NAME
      value: ---
    - name: CI_ENVIRONMENT_SLUG
      value: ---
    - name: CI_ENVIRONMENT_URL
      value: ---
    - name: CI_DISPOSABLE_ENVIRONMENT
      value: "---"
    - name: CI_RUNNER_VERSION
      value: ---
    - name: CI_RUNNER_REVISION
      value: ---
    - name: CI_RUNNER_EXECUTABLE_ARCH
      value: linux/amd64
    image: ---
    imagePullPolicy: Always
    name: build
    securityContext:
      privileged: true
    stdin: true
    terminationMessagePath: /dev/termination-log
    terminationMessagePolicy: File
    volumeMounts:
    - mountPath: /builds
      name: repo
    - mountPath: /var/run/secrets/kubernetes.io/serviceaccount
      name: gitlab-runner-token-wkzcr
      readOnly: true
  - command:
    - sh
    - -c
    - "if [ -x /usr/local/bin/bash ]; then\n\texec /usr/local/bin/bash \nelif [ -x
      /usr/bin/bash ]; then\n\texec /usr/bin/bash \nelif [ -x /bin/bash ]; then\n\texec
      /bin/bash \nelif [ -x /usr/local/bin/sh ]; then\n\texec /usr/local/bin/sh \nelif
      [ -x /usr/bin/sh ]; then\n\texec /usr/bin/sh \nelif [ -x /bin/sh ]; then\n\texec
      /bin/sh \nelif [ -x /busybox/sh ]; then\n\texec /busybox/sh \nelse\n\techo shell
      not found\n\texit 1\nfi\n\n"
    env:
    - name: FF_CMD_DISABLE_DELAYED_ERROR_LEVEL_EXPANSION
      value: "---"
    - name: FF_NETWORK_PER_BUILD
      value: "---"
    - name: FF_USE_LEGACY_BUILDS_DIR_FOR_DOCKER
      value: "---"
    - name: FF_USE_LEGACY_VOLUMES_MOUNTING_ORDER
      value: "---"
    - name: FF_USE_LEGACY_KUBERNETES_EXECUTION_STRATEGY
      value: "---"
    - name: CI_JOB_IMAGE
      value: ---
    - name: CI_RUNNER_SHORT_TOKEN
      value: ---
    - name: CI_BUILDS_DIR
      value: ---
    - name: CI_PROJECT_DIR
      value: ---
    - name: CI_CONCURRENT_ID
      value: "---"
    - name: CI_CONCURRENT_PROJECT_ID
      value: "---"
    - name: CI_SERVER
      value: "---"
    - name: CI_SERVER_TLS_CA_FILE
      value: |-
        -----BEGIN CERTIFICATE-----
        sjbsdjhbdskbdskbdsk
        -----END CERTIFICATE-----
    - name: CI_PIPELINE_ID
      value: "---"
    - name: CI_PIPELINE_URL
      value: ---
    - name: CI_JOB_ID
      value: "---"
    - name: CI_JOB_URL
      value: ---
    - name: CI_BUILD_ID
      value: "---"
    - name: CI_REGISTRY_USER
      value: ---
    - name: CI_JOB_NAME
      value: ---
    - name: CI_JOB_STAGE
      value: ---
    - name: CI_NODE_TOTAL
      value: "---"
    - name: CI_BUILD_NAME
      value: ---
    - name: CI_BUILD_STAGE
      value: ---
    - name: CI
      value: "---"
    - name: GITLAB_CI
      value: "---"
    - name: CI_SERVER_URL
      value: ---
    - name: CI_SERVER_HOST
      value: ---
    - name: CI_SERVER_PORT
      value: "---"
    - name: CI_SERVER_PROTOCOL
      value: ---
    - name: CI_SERVER_NAME
      value: ---
    - name: CI_SERVER_VERSION
      value: ---
    - name: CI_SERVER_VERSION_MAJOR
      value: "---"
    - name: CI_SERVER_VERSION_MINOR
      value: "---"
    - name: CI_SERVER_VERSION_PATCH
      value: "---"
    - name: CI_SERVER_REVISION
      value: ---
    - name: GITLAB_FEATURES
      value: ---
    - name: CI_PROJECT_ID
      value: "---"
    - name: CI_PROJECT_NAME
      value: ---
    - name: CI_PROJECT_TITLE
      value: ---
    - name: CI_PROJECT_PATH
      value: ---
    - name: CI_PROJECT_PATH_SLUG
      value: ---
    - name: CI_PROJECT_NAMESPACE
      value: ---
    - name: CI_PROJECT_URL
      value: ---
    - name: CI_PROJECT_VISIBILITY
      value: ---
    - name: CI_PROJECT_REPOSITORY_LANGUAGES
      value: ---
    - name: CI_DEFAULT_BRANCH
      value: ---
    - name: CI_PAGES_DOMAIN
      value: ---
    - name: CI_PAGES_URL
      value: ---
    - name: CI_REGISTRY
      value: ---
    - name: CI_REGISTRY_IMAGE
      value: ---
    - name: CI_API_V4_URL
      value: ---
    - name: CI_PIPELINE_IID
      value: "---"
    - name: CI_PIPELINE_SOURCE
      value: ---
    - name: CI_CONFIG_PATH
      value: ---
    - name: CI_COMMIT_SHA
      value: ---
    - name: CI_COMMIT_SHORT_SHA
      value: ---
    - name: CI_COMMIT_BEFORE_SHA
      value: "---"
    - name: CI_COMMIT_REF_NAME
      value: ---
    - name: CI_COMMIT_REF_SLUG
      value: ---
    - name: CI_COMMIT_MESSAGE
      value: |
        ---
    - name: CI_COMMIT_TITLE
      value: ---
    - name: CI_COMMIT_DESCRIPTION
    - name: CI_COMMIT_REF_PROTECTED
      value: "---"
    - name: CI_BUILD_REF
      value: ---
    - name: CI_BUILD_BEFORE_SHA
      value: "---"
    - name: CI_BUILD_REF_NAME
      value: ---
    - name: CI_BUILD_REF_SLUG
      value: ---
    - name: CI_MERGE_REQUEST_EVENT_TYPE
      value: ---
    - name: CI_MERGE_REQUEST_SOURCE_BRANCH_SHA
    - name: CI_MERGE_REQUEST_TARGET_BRANCH_SHA
    - name: CI_MERGE_REQUEST_ID
      value: "---"
    - name: CI_MERGE_REQUEST_IID
      value: "---"
    - name: CI_MERGE_REQUEST_REF_PATH
      value: ---
    - name: CI_MERGE_REQUEST_PROJECT_ID
      value: "---"
    - name: CI_MERGE_REQUEST_PROJECT_PATH
      value: ---
    - name: CI_MERGE_REQUEST_PROJECT_URL
      value: ---
    - name: CI_MERGE_REQUEST_TARGET_BRANCH_NAME
      value: ---
    - name: CI_MERGE_REQUEST_TITLE
      value: ---
    - name: CI_MERGE_REQUEST_SOURCE_PROJECT_ID
      value: "---"
    - name: CI_MERGE_REQUEST_SOURCE_PROJECT_PATH
      value: ---
    - name: CI_MERGE_REQUEST_SOURCE_PROJECT_URL
      value: ---
    - name: CI_MERGE_REQUEST_SOURCE_BRANCH_NAME
      value: ---
    - name: CI_RUNNER_ID
      value: "---"
    - name: CI_RUNNER_DESCRIPTION
      value: ---
    - name: CI_RUNNER_TAGS
    - name: DOCKER_DRIVER
      value: overlay2
    - name: DOCKER_HOST
      value: tcp://<IP_ADDRESS>:2375
    - name: DOCKER_IMAGE_NAME
      value: ---
    - name: AWS_ACCESS_KEY_ID
      value: ---
    - name: AWS_SECRET_ACCESS_KEY
      value: ---
    - name: DOCKER_AUTH_CONFIG
      value: '{"credHelpers": {"---":"ecr-login"}}'
    - name: KUBERNETES_SERVICE_ACCOUNT
      value: ---
    - name: KUBERNETES_CONTEXT
      value: ---
    - name: KUBERNETES_SERVER
      value: ---
    - name: KUBERNETES_TOKEN
      value: ---
    - name: DB_PASSWORD
      value: vault:secret/data/applications/blabla/dev/database#DB_PASSWORD
    - name: STAGE
      value: ---
    - name: GITLAB_USER_ID
      value: "---"
    - name: GITLAB_USER_EMAIL
      value: ---
    - name: GITLAB_USER_LOGIN
      value: ---
    - name: GITLAB_USER_NAME
      value: ---
    - name: CI_MERGE_REQUEST_CHANGED_PAGE_PATHS
    - name: CI_MERGE_REQUEST_CHANGED_PAGE_URLS
    - name: CI_ENVIRONMENT_NAME
      value: ---
    - name: CI_ENVIRONMENT_SLUG
      value: ---
    - name: CI_ENVIRONMENT_URL
      value: ---
    - name: CI_DISPOSABLE_ENVIRONMENT
      value: "---"
    - name: CI_RUNNER_VERSION
      value: ---
    - name: CI_RUNNER_REVISION
      value: ---
    - name: CI_RUNNER_EXECUTABLE_ARCH
      value: linux/amd64
    image: gitlab/gitlab-runner-helper:x86_64-ce065b93
    imagePullPolicy: IfNotPresent
    name: helper
    securityContext:
      privileged: true
    stdin: true
    terminationMessagePath: /dev/termination-log
    terminationMessagePolicy: File
    volumeMounts:
    - mountPath: ---
      name: repo
    - mountPath: /var/run/secrets/kubernetes.io/serviceaccount
      name: gitlab-runner-token-wkzcr
      readOnly: true
  - env:
    - name: FF_CMD_DISABLE_DELAYED_ERROR_LEVEL_EXPANSION
      value: "---"
    - name: FF_NETWORK_PER_BUILD
      value: "---"
    - name: FF_USE_LEGACY_BUILDS_DIR_FOR_DOCKER
      value: "---"
    - name: FF_USE_LEGACY_VOLUMES_MOUNTING_ORDER
      value: "---"
    - name: FF_USE_LEGACY_KUBERNETES_EXECUTION_STRATEGY
      value: "---"
    - name: CI_JOB_IMAGE
      value: ---
    - name: CI_RUNNER_SHORT_TOKEN
      value: ---
    - name: CI_BUILDS_DIR
      value: ---
    - name: CI_PROJECT_DIR
      value: ---
    - name: CI_CONCURRENT_ID
      value: "---"
    - name: CI_CONCURRENT_PROJECT_ID
      value: "---"
    - name: CI_SERVER
      value: "---"
    - name: CI_SERVER_TLS_CA_FILE
      value: |-
        -----BEGIN CERTIFICATE-----
        jkdasndjksnbjksdbjkdbdsjkbdskj
        -----END CERTIFICATE-----
    - name: CI_PIPELINE_ID
      value: "---"
    - name: CI_PIPELINE_URL
      value: ---
    - name: CI_JOB_ID
      value: "---"
    - name: CI_JOB_URL
      value: ---
    - name: CI_BUILD_ID
      value: "---"
    - name: CI_REGISTRY_USER
      value: ---
    - name: CI_JOB_NAME
      value: ---
    - name: CI_JOB_STAGE
      value: ---
    - name: CI_NODE_TOTAL
      value: "---"
    - name: CI_BUILD_NAME
      value: ---
    - name: CI_BUILD_STAGE
      value: ---
    - name: CI
      value: "---"
    - name: GITLAB_CI
      value: "---"
    - name: CI_SERVER_URL
      value: ---
    - name: CI_SERVER_HOST
      value: ---
    - name: CI_SERVER_PORT
      value: "---"
    - name: CI_SERVER_PROTOCOL
      value: ---
    - name: CI_SERVER_NAME
      value: ---
    - name: CI_SERVER_VERSION
      value: ---
    - name: CI_SERVER_VERSION_MAJOR
      value: "---"
    - name: CI_SERVER_VERSION_MINOR
      value: "---"
    - name: CI_SERVER_VERSION_PATCH
      value: "---"
    - name: CI_SERVER_REVISION
      value: ---
    - name: GITLAB_FEATURES
      value: ---
    - name: CI_PROJECT_ID
      value: "---"
    - name: CI_PROJECT_NAME
      value: ---
    - name: CI_PROJECT_TITLE
      value: ---
    - name: CI_PROJECT_PATH
      value: ---
    - name: CI_PROJECT_PATH_SLUG
      value: ---
    - name: CI_PROJECT_NAMESPACE
      value: ---
    - name: CI_PROJECT_URL
      value: ---
    - name: CI_PROJECT_VISIBILITY
      value: ---
    - name: CI_PROJECT_REPOSITORY_LANGUAGES
      value: ---
    - name: CI_DEFAULT_BRANCH
      value: ---
    - name: CI_PAGES_DOMAIN
      value: ---
    - name: CI_PAGES_URL
      value: ---
    - name: CI_REGISTRY
      value: ---
    - name: CI_REGISTRY_IMAGE
      value: ---
    - name: CI_API_V4_URL
      value: ---
    - name: CI_PIPELINE_IID
      value: "---"
    - name: CI_PIPELINE_SOURCE
      value: ---
    - name: CI_CONFIG_PATH
      value: ---
    - name: CI_COMMIT_SHA
      value: ---
    - name: CI_COMMIT_SHORT_SHA
      value: ---
    - name: CI_COMMIT_BEFORE_SHA
      value: "---"
    - name: CI_COMMIT_REF_NAME
      value: ---
    - name: CI_COMMIT_REF_SLUG
      value: ---
    - name: CI_COMMIT_MESSAGE
      value: |
        znsjknszlknzsls
    - name: CI_COMMIT_TITLE
      value: kjbkjsbljbdkds
    - name: CI_COMMIT_DESCRIPTION
    - name: CI_COMMIT_REF_PROTECTED
      value: "---"
    - name: CI_BUILD_REF
      value: ---
    - name: CI_BUILD_BEFORE_SHA
      value: "---"
    - name: CI_BUILD_REF_NAME
      value: ---
    - name: CI_BUILD_REF_SLUG
      value: ---
    - name: CI_MERGE_REQUEST_EVENT_TYPE
      value: ---
    - name: CI_MERGE_REQUEST_SOURCE_BRANCH_SHA
    - name: CI_MERGE_REQUEST_TARGET_BRANCH_SHA
    - name: CI_MERGE_REQUEST_ID
      value: "---"
    - name: CI_MERGE_REQUEST_IID
      value: "---"
    - name: CI_MERGE_REQUEST_REF_PATH
      value: ---
    - name: CI_MERGE_REQUEST_PROJECT_ID
      value: "---"
    - name: CI_MERGE_REQUEST_PROJECT_PATH
      value: ---
    - name: CI_MERGE_REQUEST_PROJECT_URL
      value: ---
    - name: CI_MERGE_REQUEST_TARGET_BRANCH_NAME
      value: ---
    - name: CI_MERGE_REQUEST_TITLE
      value: ---
    - name: CI_MERGE_REQUEST_SOURCE_PROJECT_ID
      value: "---"
    - name: CI_MERGE_REQUEST_SOURCE_PROJECT_PATH
      value: ---
    - name: CI_MERGE_REQUEST_SOURCE_PROJECT_URL
      value: ---
    - name: CI_MERGE_REQUEST_SOURCE_BRANCH_NAME
      value: ---
    - name: CI_RUNNER_ID
      value: "---"
    - name: CI_RUNNER_DESCRIPTION
      value: ---
    - name: CI_RUNNER_TAGS
    - name: DOCKER_DRIVER
      value: overlay2
    - name: DOCKER_HOST
      value: tcp://<IP_ADDRESS>:2375
    - name: DOCKER_IMAGE_NAME
      value: ---
    - name: AWS_ACCESS_KEY_ID
      value: ---
    - name: AWS_SECRET_ACCESS_KEY
      value: ---
    - name: DOCKER_AUTH_CONFIG
      value: '{"credHelpers": {"---":"ecr-login"}}'
    - name: KUBERNETES_SERVICE_ACCOUNT
      value: ---
    - name: KUBERNETES_CONTEXT
      value: ---
    - name: KUBERNETES_SERVER
      value: ---
    - name: KUBERNETES_TOKEN
      value: ---
    - name: DB_PASSWORD
      value: vault:secret/data/applications/blabla/dev/database#DB_PASSWORD
    - name: STAGE
      value: ---
    - name: GITLAB_USER_ID
      value: "---"
    - name: GITLAB_USER_EMAIL
      value: ---
    - name: GITLAB_USER_LOGIN
      value: ---
    - name: GITLAB_USER_NAME
      value: ---
    - name: CI_MERGE_REQUEST_CHANGED_PAGE_PATHS
    - name: CI_MERGE_REQUEST_CHANGED_PAGE_URLS
    - name: CI_ENVIRONMENT_NAME
      value: ---
    - name: CI_ENVIRONMENT_SLUG
      value: ---
    - name: CI_ENVIRONMENT_URL
      value: ---
    - name: CI_DISPOSABLE_ENVIRONMENT
      value: "---"
    - name: CI_RUNNER_VERSION
      value: ---
    - name: CI_RUNNER_REVISION
      value: ---
    - name: CI_RUNNER_EXECUTABLE_ARCH
      value: linux/amd64
    image: docker:18.09-dind
    imagePullPolicy: IfNotPresent
    name: svc-0
    resources:
      limits:
        cpu: 1800m
        memory: 2024Mi
      requests:
        cpu: 250m
        memory: 128Mi
    securityContext:
      privileged: true
    stdin: true
    terminationMessagePath: /dev/termination-log
    terminationMessagePolicy: File
    volumeMounts:
    - mountPath: /builds
      name: repo
    - mountPath: /var/run/secrets/kubernetes.io/serviceaccount
      name: gitlab-runner-token-wkzcr
      readOnly: true
  dnsPolicy: ClusterFirst
  enableServiceLinks: true
  hostAliases:
  - hostnames:
    - docker
    ip: <IP_ADDRESS>
  imagePullSecrets:
  - name: runner-qgyh8lfs-project-18432922-concurrent-062r8k
  nodeName: ip-xxxxxx.eu-central-1.compute.internal
  nodeSelector:
    kops.k8s.io/instancegroup: nodes
  priority: 0
  restartPolicy: Never
  schedulerName: default-scheduler
  securityContext: {}
  serviceAccount: gitlab-runner
  serviceAccountName: gitlab-runner
  terminationGracePeriodSeconds: 0
  tolerations:
  - effect: NoExecute
    key: node.kubernetes.io/not-ready
    operator: Exists
    tolerationSeconds: 300
  - effect: NoExecute
    key: node.kubernetes.io/unreachable
    operator: Exists
    tolerationSeconds: 300
  volumes:
  - emptyDir: {}
    name: repo
  - name: gitlab-runner-token-wkzcr
    secret:
      defaultMode: 420
      secretName: gitlab-runner-token-wkzcr

The code that reads this json from the imagePullSecret is here:
	dockerConfigJSONKey := viper.GetString("default_image_pull_docker_config_json_key")
	err = json.Unmarshal(data[dockerConfigJSONKey], &dockerCreds)
	if err != nil {
		return false, fmt.Errorf("cannot unmarshal docker configuration from imagePullSecret: %s", err.Error())
	}

There are two options here:

the JSON in the imagePullSecret is not valid
json.Unmarshal is broken

I'm not saying you are wrong, but I expected this and stored de-base64 value of secret.
{"registry.gitlab.com":{"Username":"gitlab-ci-token","Password":"xxxxxxxxxxx"}}

I would suggest creating this secret with and compare with the current version:
kubectl create secret docker-registry my-secret --docker-server=registry.gitlab.com --docker-username=gitlab-ci-token
--docker-password= xxxxxxxxxxx

I do not create that, it's automatically generated. Anyway I have no images from that gitlab repo to pull.
Checking... the thing is that AFAIR without gitlab pipeline services definition secret is generated the same way. Nothing changes but this magic service.
Is this possible that I have too many ENV vars / containers for pod..?

That shouldn't be an issue.

https://github.com/banzaicloud/bank-vaults/blob/chart/vault/1.1.0/cmd/vault-secrets-webhook/registry/registry.go#L204
Please correct me, but is that returning de-base64 value? I think just base64 encoded.
Do I miss where it's decoded?

Please check: https://github.com/banzaicloud/bank-vaults/blob/master/cmd/vault-secrets-webhook/registry/registry.go#L212
Secrets created with the command I pasted are working fine.

Is it possible that it fail if it can't auth to that registry.gitlab.com ?
We don't use it at all.

Just confirmed again, removing services generates smaller POD definition (but 100% the same secret content, validated few times) and everything works.

I think I found the issue:
https://godoc.org/k8s.io/api/core/v1 -> DockerConfigJsonKey = ".dockerconfigjson"
SecretTypeDockerConfigJson SecretType = "kubernetes.io/dockerconfigjson"
But in my case secret is of type: kubernetes.io/dockercfg and my key in secret is .dockercfg but not .dockerconfigjson

there is another thing:
    // SecretTypeDockercfg contains a dockercfg file that follows the same format rules as ~/.dockercfg
    //
    // Required fields:
    // - Secret.Data[".dockercfg"] - a serialized ~/.dockercfg file
    SecretTypeDockercfg SecretType = "kubernetes.io/dockercfg"

    // DockerConfigKey is the key of the required data for SecretTypeDockercfg secrets
    DockerConfigKey = ".dockercfg"

Ok, after setting
        - name: DEFAULT_IMAGE_PULL_DOCKER_CONFIG_JSON_KEY
          value: .dockercfg

to the webhook deployment things started to work.
I don't know why it worked differently with/without services, maybe we hit another issue here. Just keep in mind.
@bonifaido  Thanks for great product!
Can you update documentation so other users will know what may happen and how to fix. I learned that lust goint to the source code.
Thanks!

Thanks @wizard580 for the debugging, it seems that the .dockercfg file is deprecated for a long time: https://github.com/moby/moby/commit/18c9b6c6455f116ae59cde8544413b3d7d294a5e but I guess we need to add doc or code fix (probably the latter) for that as you suggested.
Thanks again!


Split parameter id and title for Kamelets

Needed to fix https://github.com/KaotoIO/kaoto-ui/issues/1534

Tests fail :)

Tests fail :)
Ah yes, that's because of the changes needed in the hwcloud Camel components... What about disabling the test by default? As these are more sanity checks for when something goes wrong

@Delawen I moved the sanity checks to a file that should be executed manually only (when something else breaks :D)


Regex masking dimension compatibility

I get a tensor size mismatch for the regex guided generation here. Although this might be model specific
model = models.transformers("togethercomputer/RedPajama-INCITE-Instruct-3B-v1")
text.generate.regex(model, r"([0-9])")('"1+1=2" Give this text a score out of 10:')

#   return logits + mask
#          ~~~~~~~^~~~~~
# RuntimeError: The size of tensor a (50432) must match the size of tensor b (50277) at non-singleton dimension 1

I'll investigate this week. Either there's something special with the llama model or with its tokenizer.

Llama Models work fine. It could be because of GPTNeoXTokenizer which redpajama and mpt models share.

Hi, yes this indeed is an error related to GPTNeoXTokenizer,
Findings with pythia-70m-deduped
Vocab size is 50304 (mentioned in original config) in https://huggingface.co/EleutherAI/pythia-70m-deduped/blob/main/config.json
Vocab size is 50254 (when we run - tokenizer.vocab_size from AutoTokenizer)
Vocab size is 50277 (when we run - len(tokenizer.get_vocab()) from AutoTokenizer)
Logit size is 50304 (when we call self.model(...) )
Now for GPT2 Vocab size and Logit size is same 50257
Simple fix would be to replace create_proposal in regex.py from -
            mask = torch.full(
                (len(self.model.tokenizer.vocabulary),), -math.inf, device=self.device
            )

to
            mask = torch.full(
                (len(logits[0]),), -math.inf, device=self.device
            )

I ran for both gpt2 and pythia both worked

Thank you! Would be awesome if you could open a PR

from what I understood from the code, mask is created with same length of vocabulary, which doesnt really work in case of GPTNeoX which has different vocab at all level,
Also we can see that at the end of the function, we return return logits + mask
And according to the error, we want to have Tensors of equal length, so mask should be of equal length as logits not vocab (if I understand it correctly)
Also if anyone can test this change against LLama1-2 it would be great.
        for pstate in self.pstates:
            mask = torch.full(
                (len(self.model.tokenizer.vocabulary),), -math.inf, device=self.device
            )

I'll open a PR for small change if everyone's okay

Created a PR for the fix https://github.com/normal-computing/outlines/pull/236


IE 11: Fullscreen breaks view

Exiting returns to normal.

Update: can't replicate it anymore. Might've been an isolated bug.

Maybe resize handler isn't firing on fullscreen? Do we need to invoke manually?


#5 Created Events Section

Added file5.png in src/assets/images
Created section 3 folder containing Section3.js and Section3.css
Added Section3 Component in Homepage.js
Added href=#events in Navbar Component

Only HCs have the right to review the tasks, hierarchy should be maintained. You don't have to add @virajchandra51 for review

Functionality Added
Changed Card Hover Effect
Changed Margin and Padding

Fix this height, either make it truncated for longer texts like "Hello this is an event...." or else extend height to match the levels.

Fixed Line Height

Done Sir

Great work, @Kraniket901 !


Update k8s test versions

v1.10.0-beta.0 -> v1.10.0-beta.1
Signed-off-by: André Martins<EMAIL_ADDRESS>Copy of #https://github.com/cilium/cilium/pull/2978 due jenkins misbehavior

test-missed-k8s

test-me-please

test-missed-k8s


Converting from HTML not rendering the videos and the iframes

Is there an existing issue for this?

[X] I have searched the existing issues

The question
How do I go about this, I want to convert from HTML, the text and the Images are working but the videos and the iframes were not showing at all.

Videos need to be implemented, but, iframes implementation is so far to be implemented. I think that it could be added if we just add a parser of html to flutter widgets as a custom block embed.
@ellet0 what do you think?

Videos need to be implemented, but, iframes implementation is so far to be implemented. I think that it could be added if we just add a parser of html to flutter widgets as a custom block embed.
@ellet0 what do you think?

Missed the notification for some reason. Generally, I prefer to convert from HTML to Delta directly.

I prefer to convert from HTML to Delta directly.

That's exactly why I took the time to create the flutter_quill_delta_from_html package

I prefer to convert from HTML to Delta directly.

That's exactly why I took the time to create the flutter_quill_delta_from_html package

Thank you for your time and efforts.


The examples in the Dynamic Data Masking page can be clearer

The table at the top of the Dynamic Data Masking page has examples. These examples should include before and after values for the data, so that the reader can see what the sample data was before the masking, and how things show after the mask is applied. Without this things are not clear.

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

ID: 5b9408bf-18b5-339f-cd25-6a3024be3243
Version Independent ID: eea4b8dc-5598-b7e6-e01a-902d5ca1f96d
Content: Dynamic Data Masking - SQL Server
Content Source: docs/relational-databases/security/dynamic-data-masking.md
Service: sql
Sub-service: security
GitHub Login: @VanMSFT
Microsoft Alias: vanto

@AzharTaj1 -- Azhar, thank you for your feedback.  Please consider these resources:

SQL Server on Microsoft Q&A
DBA Stack Exchange
Stack Overflow

@VanMSFT -- Van, please look into this issue.

Hi @AzharTaj1 - I hope you're doing well! Thanks for the suggestion. It would make sense to have a before and after, but the description in the table does give anecdote on what the masking function does. Is there a particular masking function that you think would need more clarity? Perhaps we can consider adding more clarity in the description instead of having more columns to display before and after results.
cc: @Madhumitatripathy

Hi Van,
I am doing well. Great to hear from you .... what a nice coincidence! Basically, I was not able to fully understand what some of the masking functions do. Here is an example from the table. As opposed to additional columns, if the two examples below actually showed the implementation for let's say phone number<PHONE_NUMBER>, then it would be easier to understand. So, the before picture would be this phone number<PHONE_NUMBER>, and the after picture would be how the masked number would show up with these masks. This same method can be applied to all the examples on this page and make it easier for people to understand how this works. Thoughts? Thanks!
Best regards,
Azhar
@.***
From: Van To @.>
Sent: Tuesday, April 4, 2023 6:02 PM
To: MicrosoftDocs/sql-docs @.>
Cc: AzharTaj1 @.>; Mention @.>
Subject: Re: [MicrosoftDocs/sql-docs] The examples in the Dynamic Data Masking page can be clearer (Issue #8794)
Hi @AzharTaj1https://github.com/AzharTaj1 - I hope you're doing well! Thanks for the suggestion. It would make sense to have a before and after, but the description in the table does give anecdote on what the masking function does. Is there a particular masking function that you think would need more clarity? Perhaps we can consider adding more clarity in the description instead of having more columns to display before and after results.
cc: @Madhumitatripathyhttps://github.com/Madhumitatripathy

Reply to this email directly, view it on GitHubhttps://github.com/MicrosoftDocs/sql-docs/issues/8794#issuecomment-1496784494, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ALVJ7QSAFMKDG6LQX5C6GG3W7S77XANCNFSM6AAAAAAWP5KJGM.
You are receiving this because you were mentioned.Message ID<EMAIL_ADDRESS>


Writegear ffmpeg creationflag

Added Feature: Detached Subprocess Creation for Windows

In this pull request, I've added a new feature to enable detached subprocess creation on Windows within the writegear module. This enhancement enhances the process management capabilities of the module.
Requirements / Checklist

[x] I have read the PR Guidelines.
[x] I have read the Documentation.
[x] I have updated the documentation accordingly(if required).

Context

This can be useful while creating an exe file for a python script that uses writegear. On windows even after creating the exe file in windowed mode or no-console mode, the ffmpeg.exe command line window would pop up while its being used by write gear.
Types of changes

[x] New feature (non-breaking change which adds functionality)

@ibtsam3301 Look good except, we don't need extra variable for the same, a optional flag might work better.

@ibtsam3301 One question, Why not CREATE_NO_WINDOW ?
What I know:
The difference is in what the started process can do. In both cases it won't have a console. But with the CREATE_NO_WINDOW option it can call AttachConsole(ATTACH_PARENT_PROCESS) and get access to the parent's console window (if available). That explicitly will not work when you specify DETACH_PROCESS. The only option then is for the started process to use AllocConsole() to create its own console.
Or in other words, you can be sure that the started process will never be able to chatter into your own console by using DETACH_PROCESS.

@ibtsam3301 I'm merging this PR, and will make necessary changes that are required. Also we don't need this flag for logging mode where we are debugging stuff. Thank you,


fix logger bug for batch issue upload

change logger.warning to logger.info to avoid error
still need to add/update unit and integration tests to catch this issue in the future

The line referred to in the error message is actually this one:
https://github.com/cmu-delphi/delphi-epidata/blob/00e6b805acab6200798541e639a5db9b384d44a7/src/acquisition/covidcast/csv_importer.py#L95
but it looks like the line you're currently repairing has the same problem. So probably just extend the fix to both locations? and hopefully the test you write will catch either of them.

Not sure how I missed that! I've extended the fix to line 95 now

Not sure how I missed that, but I've extended the fix to line 95. Hopefully, that should cover everything!
Testing the logger is turning out to be a bit of a challenge, so we will open a separate issue to track that.


Cloning down at end of file in script editor fails with error

Godot version:
v3.0.2.stable.official
OS/device including version:
Linux/Ubuntu 1710
Issue description:
Clone down (Ctrl-B by default) in script editor fails and generates an error if you clone a Multi-line selection which includes the last line of the file
Gives this error, this is for 2 a line selection. It produces 5 errors for 5 lines etc:
scene/gui/text_edit.cpp:3300 - Index p_line=22 out of size (text.size()=22)  scene/gui/text_edit.cpp:3300 - Index p_line=23 out of size (text.size()=23)
It gives the above error and adds a newline to the end of the file.

Steps to reproduce:
Make a selection spanning 2 or more lines touching the bottom of the file and Clone Down.
Minimal reproduction project:
Any script file

I'm trying to tackle this to get a handle on the codebase.
I've noticed that this problem is happening here: https://github.com/godotengine/godot/blob/master/editor/plugins/script_text_editor.cpp#L1018
It seems like we're not checking if the next line exists or not and just using the value directly.
Since this would be my first contribution I would love some input on next steps or if I'm on the right path. I'm going to look through other _edit_option cases to see if a similar situation arises and how the problem is solved.


Types for "defaults" function

There is a disclaimer in the types file:

// Default Options feature is not supported because it's basically impossible to write strongly-typed definitions for it.

I think perhaps Partial<T> is the piece of the puzzle you were missing? I tried to write a definition, but I'm not sure I understand the relation between JS source & TS types. Does this help? (might not be correct!)
export function defaults<T>(
  defaultOptions:
    | Partial<phin.IJSONResponseOptions>
    | Partial<IWithData<phin.IJSONResponseOptions>>
    | Partial<IWithForm<phin.IJSONResponseOptions>>
): (
  options:
    | phin.IJSONResponseOptions
    | IWithData<phin.IJSONResponseOptions>
    | IWithForm<phin.IJSONResponseOptions>
) => Promise<phin.IJSONResponse<T>>

Thanks! This does seem like a good idea.

I think this is now handled by optional properties in IOptionsBase

If anyone is wondering how exactly to extend the phin type definitions to include the suggested additions in your project, you can do so as follows:

Create the type declaration file, e.g. types/phin.d.ts:

import phin, { IWithData, IWithForm } from 'phin';

declare module 'phin' {
  export function defaults<T>(
    defaultOptions:
      | Partial<phin.IJSONResponseOptions>
      | Partial<IWithData<phin.IJSONResponseOptions>>
      | Partial<IWithForm<phin.IJSONResponseOptions>>
  ): (
    options:
      | phin.IJSONResponseOptions
      | IWithData<phin.IJSONResponseOptions>
      | IWithForm<phin.IJSONResponseOptions>
  ) => Promise<phin.IJSONResponse<T>>;
}

Update tsconfig.json as follows:

"compilerOptions": {
    "typeRoots": [
      "./types/"
    ],
  }

This enables you to access defaults like this:

import p from 'phin';

export const httpClient = p.defaults({
  headers: {
    'User-Agent': 'My App',
  },
});


Correct sentence

For the input of your function, you will be given one sentence. You have to return a corrected version, that starts with a capital letter and ends with a period (dot).
Pay attention to the fact that not all of the fixes are necessary. If a sentence already ends with a period (dot), then adding another one will be a mistake.
Make sure that this issue is assigned to you before solving .

can you assign this to me

yeah you can goahead


Improve error message for ZSON with missing field

Repros are with zq commit c5ecae7.
When updating test ppl/lake/ztests/import-check.yaml to convert its input data from TZNG to ZSON, we noted the error message for the ZSON equivalent could stand to be improved.
The TZNG one:
$ cat missingcol.tzng
#0:record[a:string,b:string]
0:[a;]

$ zq -z -i tzng missingcol.tzng
missingcol.tzng: line 2: b (string): record missing a field

The ZSON equivalent:
$ cat missingcol.zson
{a:"a",b:"b"} (=foo)
{a:"a"} (foo)

$ zq -z -i zson missingcol.zson
missingcol.zson: record decorator columns (2) mismatched with value columns (1)

@mccanne noted that this will only come up if someone is writing ZSON by hand (or has written software that's outputting buggy ZSON), hence probably a low priority.

No longer relevant.


[Megathread] Fullscreen & Focus Mode follow-up work

Taken from https://github.com/microsoft/terminal/issues/531#issuecomment-531046569

I'd suggest that this is broken into 3 implementation steps:

Support fullscreen mode, with always hidden tabs
Add a setting to have tabs always visible in fullscreen mode
Enable "revealing" tabs on mouse hover near the top

Step 3 has some implementation details that are missing, like: on tabs reveal, should the tabs:

cover the terminal content, obscuring the top rows, but leaving the rest of the window unchanged
cause the terminal to resize
shift the terminal content down, obscuring the bottom rows of the terminal, but not forcing a resize?

Now that #3408 is merged (closing #531), we need some place to track the follow-up tasks I had outlined before:
Focus mode and Fullscreen share a lot of commonalities, so I'm grouping them into one thread for easy of x-linking.
Fullscreen

[x] Support fullscreen mode, with always hidden tabs
[ ] #11130 - Add a setting to have tabs always visible in fullscreen mode

"showTabsInFullscreen": true|"always"

[ ] #5677 - Enable "revealing" tabs on mouse hover near the top

"showTabsInFullscreen": "hover"

[ ] If a launch full screen option is there, when the full screened app launches, I think the TabView should be visible for a few seconds before sliding out of view. (from @mdtuak in https://github.com/microsoft/terminal/issues/288#issuecomment-551950312)

this is dependent upon adding fullscreen to launchMode, tracked in #288

[x] #4000 It would be nice to have a kind of popup with a tab name when you switch tabs with CTRL+TAB in fullscreen mode.

Let's add a setting for this as well, this sounds like a not so terrible idea.
This is the "advanced tab switcher"

Focus Mode

[ ] #539

Not necessarily Focus Mode related, but certainly relevant

[x] #10730
[ ] #7210
[ ] #12959

As part of step 2, could that setting also have an option to only show tabs in fullscreen if there is currently more than one tab? Or would that setting just also take into account the existing alwaysShowTabs setting? The latter is how iTerm handles this.
In that case, these settings might behave together like so:

State
2+ Tabs
Always Show Tabs
Show Tabs In Fullscreen
Tabs Visible

Windowed
Yes
Yes
N/A
Yes

Windowed
Yes
No
N/A
Yes

Windowed
No
Yes
N/A
Yes

Windowed
No
No
N/A
No

Fullscreen
Yes
Yes
Yes
Yes

Fullscreen
Yes
Yes
No
No

Fullscreen
Yes
No
Yes
Yes

Fullscreen
Yes
No
No
No

Fullscreen
No
Yes
Yes
Yes

Fullscreen
No
Yes
No
No

Fullscreen
No
No
Yes
No

Fullscreen
No
No
No
No

@nathpete-msft That seems pretty reasonable to me. If that's how iTerm2 does it, then that's a pretty good precedent.

I would love to have step 2 implemented. Especially if you have windows terminal in a second desktop you can simply switch to a fullscreen terminal with win + cmd + left/right. I know this works alreday but not knowing which tabs are open and which one I am using is a bit of a hassle.
That would be awesome! :)
Any plans on when this will get implemented?

@dominik-ba This work is not currently on any particular milestone. I can guarantee that it's not making the cut for 1.0, since we're currently in a feature-freeze as we prepare to release 1.0.
I think some of the other issues you're referring too mainly mean "maximized" when they're saying "fullscreen"

Wouldn't it be relatively easy to enable th new toggle focus feature also on fullscreen?
This would check step 2 :)

Just for visibility, I have opened a PR to address #11130 (no tabs in fullscreen): https://github.com/microsoft/terminal/pull/18171
I really like the idea of #5677 (show tabs on hover), so once a decision is made on my current PR (adding the simpler true/false setting), I'm happy to take a look at implementing that next. As TabView doesn't currently support a "reveal on hover" setting, my initial thought would be to use to a Flyout to achieve that effect, though I will admit I don't have a huge amount of experience with WinUI so if that is a bad idea I'm open to looking in to alternative implementations if anyone has any suggestions?


Authorization error when executing a contract action under Dawn 4.0

I executed eosio.token "issue" action under Dawn 4.0.
Using cleos was successful, but using eosjs 10.0.0 as below failed:

Eos = require('eosjs')
const keyProvider = [
  '5KQwrPbwdL6PhXujxW37FSSQZ1JiwsST4cqQzDeyXtP79zkvFD3'  // eosio
];
eos = Eos.Localnet({keyProvider});
// cleos push action eosio.token issue '{"to":"bob", "quantity":"100.0000 EOS", "memo":"issue to bob"}' -p eosio
eos.transaction({
  actions: [
    {
      account: 'eosio.token',
      name: 'issue',
      authorization: [{
        actor: 'eosio',
        permission: 'active'
      }],
      data: {
        to: 'bob',
        quantity: '100.0000 EOS',
        memo: 'issue to bob'
      }
    }
  ]
});

With an error message:

api error => { message: 'transaction declares authority \'{"actor":"eosio","permission":"active"}\', but does not have signatures for it under a provided delay of 0 ms',
  file: 'authorization_manager.cpp',
  line_number: 405,
  method: 'check_authorization' } http://<IP_ADDRESS>:8888/v1/chain/push_transaction {"compression":"none","transaction":{"expiration":"2018-05-15T06:45:55","region":0,"ref_block_num":37522,"ref_block_prefix":3593414125,"max_net_usage_words":0,"max_kcpu_usage":0,"delay_sec":0,"context_free_actions":[],"actions":[{"account":"eosio.token","name":"issue","authorization":[{"actor":"eosio","permission":"active"}],"data":"0000000000000e3d40420f000000000004454f53000000000c697373756520746f20626f62"}]},"signatures":["SIG_K1_KisUp8Q9rHayfET6P5Kb81DjcydaTGFosvQd8Grua4oaPNWuNZMEh1CeuJpYNMupYAnPSk7JCWR4jSJ3vNpXMp6ZsP4Gn6"]}
{ Error: {"code":500,"message":"Internal Service Error","error":{"code":3090003,"name":"unsatisfied_authorization","what":"provided keys, permissions, and delays do not satisfy declared authorizations","details":[{"message":"transaction declares authority '{\"actor\":\"eosio\",\"permission\":\"active\"}', but does not have signatures for it under a provided delay of 0 ms","file":"authorization_manager.cpp","line_number":405,"method":"check_authorization"}]}}
    at /home/makoto/eos/contracts/crid_test/node_modules/eosjs-api/lib/apigen.js:102:23
    at
    at process._tickCallback (internal/process/next_tick.js:182:7) status: 500, statusText: 'Internal Server Error' }
{ Error: {"code":500,"message":"Internal Service Error","error":{"code":3090003,"name":"unsatisfied_authorization","what":"provided keys, permissions, and delays do not satisfy declared authorizations","details":[{"message":"transaction declares authority '{\"actor\":\"eosio\",\"permission\":\"active\"}', but does not have signatures for it under a provided delay of 0 ms","file":"authorization_manager.cpp","line_number":405,"method":"check_authorization"}]}}
    at /home/makoto/eos/contracts/crid_test/node_modules/eosjs-api/lib/apigen.js:102:23
    at
    at process._tickCallback (internal/process/next_tick.js:182:7) status: 500, statusText: 'Internal Server Error' }
[push_transaction error] '{"code":500,"message":"Internal Service Error","error":{"code":3090003,"name":"unsatisfied_authorization","what":"provided keys, permissions, and delays do not satisfy declared authorizations","details":[{"message":"transaction declares authority '{\"actor\":\"eosio\",\"permission\":\"active\"}', but does not have signatures for it under a provided delay of 0 ms","file":"authorization_manager.cpp","line_number":405,"method":"check_authorization"}]}}', transaction '2382fa5a00009292ed252fd6000000000100a6823403ea30550000000000a53176010000000000ea305500000000a8ed3232250000000000000e3d40420f000000000004454f53000000000c697373756520746f20626f62'
{"code":500,"message":"Internal Service Error","error":{"code":3090003,"name":"unsatisfied_authorization","what":"provided keys, permissions, and delays do not satisfy declared authorizations","details":[{"message":"transaction declares authority '{\"actor\":\"eosio\",\"permission\":\"active\"}', but does not have signatures for it under a provided delay of 0 ms","file":"authorization_manager.cpp","line_number":405,"method":"check_authorization"}]}}
(node:22966) UnhandledPromiseRejectionWarning: {"code":500,"message":"Internal Service Error","error":{"code":3090003,"name":"unsatisfied_authorization","what":"provided keys, permissions, and delays do not satisfy declared authorizations","details":[{"message":"transaction declares authority '{\"actor\":\"eosio\",\"permission\":\"active\"}', but does not have signatures for it under a provided delay of 0 ms","file":"authorization_manager.cpp","line_number":405,"method":"check_authorization"}]}}
(node:22966) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). (rejection id: 1)
(node:22966) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.

Actually, first I tried with a test script and my own contract and got the same error message. The test script worked well under Dawn. 3.0.
If you have any idea to solve this issue, please let me know.,

I tried 'newaccount', also same receive that response.
con.newaccount({                     creator: 'blyse',                     name: name,                     owner: Eos.modules.ecc.privateToPublic(owner_key.toString()),                     active: Eos.modules.ecc.privateToPublic(active_key.toString()),                     recovery: 'blyse'                 })
`
{message: "transaction declares authority '{"actor":"blyse","… signatures for it under a provided delay of 0 ms", file: "authorization_manager.cpp", line_number: 405, method: "check_authorization"} http://<IP_ADDRESS>:8888/v1/chain/push_transaction {"compression":"none","transaction":{"expiration":"2018-05-15T06:49:26","region":0,"ref_block_num":28366,"ref_block_prefix":2359214972,"max_net_usage_words":0,"max_kcpu_usage":0,"delay_sec":0,"context_free_actions":[],"actions":[{"account":"eosio","name":"newaccount","authorization":[{"actor":"blyse","permission":"active"}],"data":"0000000000857d3c00000000f8787c3c01000000010002a45cd1cf5ce09d1b987281c2d1335f9ba0782ee14e5bd22b51021e9fa73a30e4010000010000000100034230396ef278122fe56a48f305dcd0da6b0126952614552900519d52189360c20100000100000000010000000000857d3c00000000a8ed32320100"}]},"signatures":["SIG_K1_KB1kCNx7AFHQWKGhRiS4tV5SawGXnDZewoq74RrefQjAxfdD9ZN3mw7x2Ky1bS19TXBzLNtdgyRabPCUWcppYR66x8v3gj"]}
Error: {"code":500,"message":"Internal Service Error","error":{"code":3090003,"name":"unsatisfied_authorization","what":"provided keys, permissions, and delays do not satisfy declared authorizations","details":[{"message":"transaction declares authority '{"actor":"blyse","permission":"active"}', but does not have signatures for it under a provided delay of 0 ms","file":"authorization_manager.cpp","line_number":405,"method":"check_authorization"}]}}
`

I tried 'newaccount', also same receive that response.
con.newaccount({ 	creator: 'blyse', 	name: name, 	owner: Eos.modules.ecc.privateToPublic(owner_key.toString()), 	active: Eos.modules.ecc.privateToPublic(active_key.toString()), 	recovery: 'blyse' })

There is confusion on my part over the branches .. I have been working on eosio master for the last 4 days and overlooked the dawn4 tag.  Fortunately the dawn4 tag is working better..

Hi James, what exactly do you mean?
I did "git checkout dawn-v4.0.0" and rebuilt eos, and with eosjs 10.0.0, I still_ have the same issue with the same error message.
What exactly I should do?

+1

I published npm eosjs@dawn4 (version 11) .. This version is compatible with eosio/eos:dawn-v4.0.0 .. There are many changes, let me know if you have questions or find other bugs..

With eos: dawn-v4.0.0 and eosjs@dawn4 (version 11.0.0), I confirmed that this issue doesn't happen.


Get fills, GetUserTradesAsync, Deserialize JsonSerializationException when processing fill "type": "expiration"

Calling GetUserTradesAsync (https://docs.ftx.com/#fills) fails to deserialize for expiration fills which do have a null orderId and tradeId.
{: Deserialize JsonSerializationException: Error converting value {null} to type 'System.Int64'. Path 'result[0].orderId', line 1, position 207. [Data only available in Debug LogLevel]}
Example response from FTX  GET fills:
{
"success": true,
"result": [
{
"id": 123,
"market": "BTT-PERP",
"future": "BTT-PERP",
"baseCurrency": null,
"quoteCurrency": null,
"type": "expiration",
"side": "buy",
"price": 1.234,
"size": 123456.0,
"orderId": null,
"time": "2022-01-17T02:00:0.012345+00:00",
"tradeId": null,
"feeRate": 0.0,
"fee": 0.0,
"feeCurrency": "USD",
"liquidity": "taker"
}
]
}
To fix in we would need to make OrderId and TradeId nullable longs in FTXUserTrade. This would resolve the issue in both the rest and socket clients, where the issue is prevalent.

I've pushed version 0.1.10 where this has been fixed

thanks for the quick fix


freshen up the README

The README needs some love. I'd like to:

convert it from RDoc to Markdown
remove the travis badge
update the dependencies section to match #565 and #563
docs.seattlerb.org is not up-to-date. let's start pointing people somewhere they'll be updated.

@mmulet Thank you! I'm really interested to see code relay in action.

@mmulet Someone submitted a PR for this already; but thanks for trying to invoke Code Relay on this.


Unable to find visit() method in visitor `org.sweble.wom3.swcadapter.AstToWomConverter'

Sometimes, the AstToWomConverter fails because it lacks a method.
We have to find a workaround or create an issue in Sweble to solve the problem.
Example: Comparison_of_open-source_operating_systems

In the example, the cell containing "C" is raising the exception.
The content of cell is not correctly parsed.

I added a method for a missing method (WtLctVarConv) to avoid the error.
However, we have to find a better solution if we want to correctly support all the wikitext syntax.


Multi admin features (Multi vendors)

Sir if there are more than one admin (vendor). One admin(vendor) can easily edit the product details added by the other admin (vendor).Can you restrict the edit option of the admin (vendor)to the products he has added by himself only.And create a super admin who can access and edit all the products added by the other admins.It will be a great feature.

I also wanted this application to be multi-vendor. Did you find any progress regarding it?


feat: validate portfolio image correctly

Checklist:

[x] I have read and followed the contribution guidelines.
[x] I have read and followed the how to open a pull request guide.
[x] My pull request targets the main branch of freeCodeCamp.
[x] I have tested these changes either locally on my machine, or GitPod.

Closes #49132

I really don't feel like any abstraction is necessary. Maybe in a future pr.

I really don't feel like any abstraction is necessary right now. I am planning on changing these components to functional components anyway, Could we keep this for a future pr?

Yep, absolutely.


The repository does not have CONTRIBUTING.md

The repository does not have CONTRIBUTING.md. And this causes confusion in the contribution and also the reduction of contributions

Thanks for your interest! What would you like to contribute and what would you like to see in that document?

May I respectfully suggest an example ?

So, we have this https://github.com/flet-dev/flet/blob/main/sdk/python/CONTRIBUTING.md for contributing to Python part of the project.

Please receive all my apologies. I was looking for the CONTRIBUTING.md file in the root folder :\ then looked for a pinned issue, then I've seen this ticket.
Maybe some issues (pointing to the right CONTRIBUTING.md files) should be made and pinned, to make them quickly visible by all the users. Here is an example.

Are you guys looking to the same doc for Flutter part of the project?

Not for the moment (as far as I'm concerned). I'll see if I can help in the Python part of the project (Thanks for pointing me to where I can give one hand). Thanks for your time and for the awesome project \o/

No worries, thanks for your interest!
I will look into pinned issues - so much to learn these days :)

Thanks for your interest! What would you like to contribute and what would you like to see in that document?

I'm looking to contribute to the python part of the code since that's the only one I'm knowledgeable in out of all languages you use.

There is contributing guide now in the root of the repo: https://github.com/flet-dev/flet/blob/main/CONTRIBUTING.md


connection failed at run

showing connection failed !!
I have prperly installed ghost v6 and i set RHOST to IP Address of the remote host and RPORT 5555 and after its happening.....
[i]Connecting  to RHOST IP:5555
[-]failed to connect RHOST IP:5555!!

@rohitghosal
Read this issue.
And next time use default ISSUE TEMPLATE!

Is this problem for shadin.io only!!

Can you show me how the default template issue looks like?
On Fri, 4 Dec, 2020, 00:42 Simon Chaykin<EMAIL_ADDRESS>wrote:

@rohitghosal https://github.com/rohitghosal
Read this issue <#m_4384996118332528541_112>.
And next time use default ISSUE TEMPLATE!
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/EntySec/ghost/issues/209#issuecomment-738234438, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AQJZOU64J7HATY7UDNGFY23SS7PKDANCNFSM4UMMEEWQ
.

name: Bug report
about: Create a report to help us improve
title: ''
labels: ''
assignees: ''

Describe the bug
A clear and concise description of what the bug is.
To Reproduce
Steps to reproduce the behavior:

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

Expected behavior
A clear and concise description of what you expected to happen.
Screenshots
If applicable, add screenshots to help explain your problem.
Desktop (please complete the following information):

OS: [e.g. iOS]
Browser [e.g. chrome, safari]
Version [e.g. 22]

Smartphone (please complete the following information):

Device: [e.g. iPhone6]
OS: [e.g. iOS8.1]
Browser [e.g. stock browser, safari]
Version [e.g. 22]

Additional context
Add any other context about the problem here.

Thanks for following helping
On Fri, 4 Dec, 2020, 16:14 Simon Chaykin<EMAIL_ADDRESS>wrote:

Describe the bug
A clear and concise description of what the bug is.
To Reproduce
Steps to reproduce the behavior:

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

Expected behavior
A clear and concise description of what you expected to happen.
Screenshots
If applicable, add screenshots to help explain your problem.
Desktop (please complete the following information):

OS: [e.g. iOS]
Browser [e.g. chrome, safari]
Version [e.g. 22]

Smartphone (please complete the following information):

Device: [e.g. iPhone6]
OS: [e.g. iOS8.1]
Browser [e.g. stock browser, safari]
Version [e.g. 22]

Additional context
Add any other context about the problem here.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/EntySec/ghost/issues/209#issuecomment-738711944, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AQJZOUZCL6GYUVFTG27ISNTSTC4PRANCNFSM4UMMEEWQ
.

And one more thing ...my issue is for shadon.io ADB offline issue??
On Fri, 4 Dec, 2020, 00:42 Simon Chaykin<EMAIL_ADDRESS>wrote:

@rohitghosal https://github.com/rohitghosal
Read this issue <#m_4384996118332528541_112>.
And next time use default ISSUE TEMPLATE!
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/EntySec/ghost/issues/209#issuecomment-738234438, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AQJZOU64J7HATY7UDNGFY23SS7PKDANCNFSM4UMMEEWQ
.


Multi-threading support

We haven't checked that menoh-java has reliable and efficient support for multi-threading yet.

Model is not designed to run concurrently (atm. it may be changed in the future)
menoh_get_last_error_message uses TLS (Thread Local Storage)


lowercase of response header names

I suggest to add lowercasing of header names. I discovered that firefox returns me 'Content-Type' header, but in Chrome it's 'content-type'.

http headers are case-insensitive
http://www.w3.org/Protocols/rfc2616/rfc2616-sec4.html#sec4.2

I think that they are case case-insensitive matters for the http protocol but pajax module should handle them better. As far as I understand, the issue is that response headers exposed by the pajax module are not consistent. For example, one cannot check response headers with a simple check:
 if (response['Content-Type'] == 'my-type') {

}

Because it can be response['content-type']. Is it correct? @zakshevskii
I think pajax is intended to hide such differences. E.g by normalizing header names or by exposing getters to read headers. Does it make sense?

I've looked into jquerys ajax function. The returned response headers are also case sensitive.
e.g. in Firefox it is "Content-Type" vs "content-type" in chrome.
But I absolutely see your point.
How about just lowercasing all header field names when using the "responseHeaders" option?
so it is always req.responseHeaders['content-type'].

Pajax should be better than jQuery.ajax :-) So I think always lower-casing is fine.

I think Jquery exposes jqXhr object which provides methods to get response headers https://api.jquery.com/jQuery.ajax/#jqXHR

https://github.com/jquery/jquery/blob/9d1b989f20b550af3590691723b0620f6914626e/src/ajax.js#L424

Ah, ok. I've only tested the getAllResponseHeaders() function.
But I don't like to overload pajax with functions and helpers. I would simply modify the parsing, so there are only lowercased header fields.

+1


How do you handle exits?

@docopt/docopt, could you write down how you handle exiting in you port? Do you raise exceptions instead? Do you return flags?
I was neglecting this topic a lot due to the fact that in Python an exit is actually an exception that leaves no traceback, so you can catch any exit. But in most languages you need to make a decision upfront if you going to exit or delegate that to the user of your code somehow.
How do you handle this issue? Are you happy with that?
P.S. where are you, guys? You should participate in discussions more.

@voieducode did this ever happen? I see no exit in the python implementation and no way to see tracebacks.

We did implement exceptions as specified in docopt.net. See
https://github.com/docopt/docopt.net/search?utf8=✓&q=DocoptInputErrorException+
Also the exit behaviour can be controlled as an option.
On 20 February 2017 at 06:26, goodwillcoding<EMAIL_ADDRESS>wrote:

@voieducode https://github.com/voieducode did this ever happen? I see
no exit in the python implementation and no way to see tracebacks.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/docopt/docopt/issues/106#issuecomment-280998100, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AA9AMMR0qTCKlK7kgxXsxFWid_km6n-Uks5reTICgaJpZM4AkV-r
.


Productive Tab Manager

Is your feature request related to a problem? Please describe.
This Chrome extension simplifies tab management, enabling users to easily save and restore browsing sessions with a click. It enhances organization, boosts productivity, and offers quick access to past sessions, streamlining the browsing experience. Unlike Google's history tab manager, this extension provides users with more control and organization over their browsing sessions. It allows for selective saving of tabs, quick access to saved sessions, and easier restoration of previous browsing states, enhancing productivity and workflow management.
Describe the solution you'd like
Rather than the Google's method of going to the history tab then searching for past tabs then select the tabs which are needed to open.  This extension involves complex features such as real-time tab tracking, session storage, user interface interactions, and integration with Chrome's APIs. Its usefulness lies in simplifying tab management, enabling users to organize and save browsing sessions efficiently, ultimately improving productivity  .
Describe alternatives you've considered
Alternatives should be storing the web-links manually or opening them from the History Manager in the browser
Additional context
Currently under working Stage

What problem is this feature trying to solve?
This feature aims to address the problem of managing and organizing multiple open tabs during web browsing sessions. It helps users efficiently save and restore browsing sessions, providing a solution to the common problem of losing track of important tabs or needing to manually re-open them. Additionally this extension tracks the tabs opened across all the opened windows not just one
How do we know when the feature is complete?
The feature will be complete when it s properly storing the sessions and showing the the current all tabs across all the windows
@Sulagna-Dutta-Roy
I would like to work and develop this complex Chrome extension and contribute again for this repository under GSSOC2 .

@Sulagna-Dutta-Roy Can I work in this

@Sulagna-Dutta-Roy The development for the Tab Manager is almost completed and also added real time tracking of current tabs .I would be able to ask for a PR once i am assigned for this .

Hello @coderun13 issue will be assigned first serve basis. Kindly raise new Issue


The image cannot be displayed because it contains errors after uploading with storage-py

Describe the bug
I am trying to upload images to bucket and after it's uploaded it shows this error:
The image cannot be displayed because it contains errors
When I upload manually using browser to the same bucket folder it works.
To Reproduce
Steps to reproduce the behavior:
    img_1 = "/Users/FSD/X.jpg"
    path_1 = "public/" + img_1.split("/")[-1] # public/X.jpg
    headers = {"apiKey": key, "Authorization": f"Bearer {key}"}
    storage_client = storage3.create_client(url, headers, is_async=False)
    sc = storage_client.get_bucket("bucket")
    test1 = sc.upload(path_1, img_1, {"Content-Type": "image/jpeg"})
    print(test1.url)
    print(sc.get_public_url(path_1))
    print(sc.create_signed_url(path_1, 3600))

Expected behavior
I should get working link to image. My bucket is public and I have "policies under storage.buckets" allowing read to everyone. It either shows "this image cannot be displayed because it contains errors" or "authorization 400 error"

After changing policies (updated INSERT privileges) public and signed URLs work but image is corrupted. Weird.

(apologies for the late response)
this is most likely because the header is expected to be in all lower case by the api (content-type instead of Content-Type)


Import Database Errors

[x] I have read the FAQ.

Describe the bug
Import Instance Errors
To Reproduce
https://bar-assistant.github.io/docs/setup/backups/
Using instance export/import information from link above.

I Run export instance command. Success. zip file made. (Dropbox link to zip file is at bottom of this message)
Give zip file to another user to place in their bar assistant appdata folder
User runs import instance command and selects yes at confirmation prompt. Import reports errors. Both users are on identical versions of Meilisearch, Bar Assistant and SaltRim.

Users already attempted to run the import command on a 100% clean/untouched Bar-Assistant setup.
It seems the errors are related to the import failing on particular "ingredients" and "cocktail_ingredients" and "cocktail_ingredient_substitutes". This particular database makes heavy edits to some of the default ingredients such as "Gold Rum" "Dark Rum" and "White Rum" and I believe the import has issues with this sort of thing.
Errors:
[2023-06-12 16:36:54] production.ERROR: [IMPORT_SERVICE] Unable to import row with id "99" to table "ingredients"
[2023-06-12 16:36:54] production.ERROR: [IMPORT_SERVICE] Unable to import row with id "101" to table "ingredients"
[2023-06-12 16:36:54] production.ERROR: [IMPORT_SERVICE] Unable to import row with id "164" to table "ingredients"
[2023-06-12 16:36:54] production.ERROR: [IMPORT_SERVICE] Unable to import row with id "175" to table "ingredients"
[2023-06-12 16:36:54] production.ERROR: [IMPORT_SERVICE] Unable to import row with id "186" to table "ingredients"
[2023-06-12 16:36:54] production.ERROR: [IMPORT_SERVICE] Unable to import row with id "187" to table "ingredients"
[2023-06-12 16:36:54] production.ERROR: [IMPORT_SERVICE] Unable to import row with id "188" to table "ingredients"
[2023-06-12 16:36:54] production.ERROR: [IMPORT_SERVICE] Unable to import row with id "199" to table "ingredients"
it goes on.......

Versions:

Docker: 20.10.14
Salt Rim 1.14.1
Bar Assistant 2.0.0
Meilisearch 1.1.1

Additional context, log outputs...
Link to zip instance export
https://www.dropbox.com/sh/micduo5h6fhqp61/AACJTwLBrvPo95JG5exeeNNYa?dl=0
I also recently attempted to use these commands before creating my backup. I typically try to use these commands to help troubleshoot. I still receive the import errors on a fresh instance though.
php artisan bar:refresh-search --clear
php artisan bar:refresh-user-search-keys
php artisan scout:import "Kami\\Cocktail\\Models\\Cocktail"
php artisan scout:import "Kami\\Cocktail\\Models\\Ingredient"

Should be fixed with latest release


[docs] Demo BasicDatePicker crashes

[ ] I have searched for similar issues in this repository and believe that this is not a duplicate.

Steps to Reproduce

Visit https://mui.com/x/react-date-pickers/date-picker/#basic-usage
Try to view
demo BasicDatePicker crashes

Your Environment

Tech
Version

MUI
v5.17.8

Netlify deploy
undefined

Browser
Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/<IP_ADDRESS> Safari/537.36

@ad185412  it seems to be working fine


Add thumbs up / down to each message

Issue #, if available:
Closes #225
Description of changes:
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

現状のダイアログ:


how tricky is it to implement two-way communication between plots and python?

Thank you for this great library :clap: !
I'm wondering how difficult it is to add two-way communication between chart objects and streamlit in order to update streamlit applications based upon click events, selections, etc... on charts. From some preliminary digging it seems like it's pretty non-trivial but want to be sure I'm not missing something obvious.
I am interested in working on this but it would be great to get some understanding of the level of challenge first.

+1

closing b/c no activity

really.


Puppeteer prevents the process from exiting gracefully

I'm not even sure what Puppeteer does to cause this. All the following tests are run on Windows 10 x64.
Here's the simple implementation of graceful exit that I devised, along with a sample test function.
const puppeteer = require("puppeteer");

var terminate = false;
var terminated = false;

async function sleep (timeout) {
	return new Promise((resolve) => {
	  setTimeout(() => {
		  console.log("Timeout! " + timeout + " ms");
		  resolve();
		}, timeout)
	})
}

process.on('SIGINT', async function () {
	console.log('Got SIGINT');
	terminate = true;
	while (!terminated) {
		console.log('Waiting another 50 ms for the main function to exit...');
		await sleep(50);
	}
	console.log('Terminated.');
});

(async () => {
       //const browserInstance = await puppeteer.launch();
	while(!terminate) {
		await sleep(500);
	}

	console.log("Exiting gracefully.")
	terminated = true;
})();

It works: I run node test.js and I see it looping through the main loop, then I press Ctrl+C and I see the main function exiting gracefully:
Looping...
Got SIGINT
Waiting for another 333 ms for the main function to exit...
Timeout! 333 ms
Waiting for another 333 ms for the main function to exit...
Timeout! 1000 ms
All done, exiting gracefully.
Timeout! 333 ms
Main function exited gracefully.
Process exited gracefully.

But if I un-comment creation of the browser instance, it no longer works:
Looping...
Got SIGINT
Waiting for another 333 ms for the main function to exit...
<application exists abruptly>

So, it means I cannot exit my application gracefully, and that's bad because I'm writing to database and risk corrupting data. Any advice on how to fix the problem or work around it?
Environment:
Windows 10 x64
Puppeteer v 1.9.0, Chromium: bundled
Node v8.11.4

Not a bug. This can be negated by using the handleSIGINT puppeteer launch option as per the docs.

New link to documentation


chore: update podfile.lock for image-picker

@cdiddy77 I merged Jack's changes with my PR and updated the podfile.lock in my PR, so I think this is no longer needed.  I wanted to get that in today so that I can get a solution for downloading model files in tomorrow (I have it working locally, but did some juggling to get the rest of my code in separately, so I'll clean up that solution tomorrow).


Add birthdate field to contacts

The addressbook does not hold birthdates for contacts. To allow
users to store birthdates for contacts, we need to create
a birthdate field for each contact.
Let's do the following to close AY2122S2-CS2103T-T17-3#28:

Create a BirthDate model
Update Person model to hold BirthDate
Update FXML and person card to show BirthDate on GUI
Ensure dependencies are functional
Update and write new tests for BirthDate

Codecov Report

Merging #45 (827ee2f) into master (ed6bbe5) will increase coverage by 0.42%.
The diff coverage is 86.44%.

@@             Coverage Diff              @@
##             master      #45      +/-   ##
============================================
+ Coverage     73.31%   73.73%   +0.42%
- Complexity      427      440      +13
============================================
  Files            74       75       +1
  Lines          1278     1329      +51
  Branches        130      134       +4
============================================
+ Hits            937      980      +43
- Misses          311      318       +7
- Partials         30       31       +1

Impacted Files
Coverage Δ

.../java/seedu/address/logic/commands/AddCommand.java
100.00% <ø> (ø)

.../java/seedu/address/model/util/SampleDataUtil.java
14.28% <0.00%> (-5.72%)
:arrow_down:

src/main/java/seedu/address/ui/PersonCard.java
0.00% <0.00%> (ø)

...java/seedu/address/logic/commands/EditCommand.java
95.89% <87.50%> (-1.13%)
:arrow_down:

...a/seedu/address/logic/parser/AddCommandParser.java
100.00% <100.00%> (ø)

...ain/java/seedu/address/logic/parser/CliSyntax.java
85.71% <100.00%> (+2.38%)
:arrow_up:

...in/java/seedu/address/logic/parser/ParserUtil.java
97.56% <100.00%> (+0.33%)
:arrow_up:

.../main/java/seedu/address/model/date/BirthDate.java
100.00% <100.00%> (ø)

.../java/seedu/address/model/date/DocumentedDate.java
100.00% <100.00%> (ø)

...c/main/java/seedu/address/model/person/Person.java
97.91% <100.00%> (+0.18%)
:arrow_up:

... and 1 more

Continue to review full report at Codecov.

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


[hotfix] [kafka] Fix the config parameter names in KafkaTestBase

What is the purpose of the change
Fix the erroneous config parameter names in KafkaTestBase.
Brief change log

Change the parameter names.

Verifying this change
This change is a trivial rework / code cleanup without any test coverage.
Does this pull request potentially affect one of the following parts:

Dependencies (does it add or upgrade a dependency): (no)
The public API, i.e., is any changed class annotated with @Public(Evolving): (no)
The serializers: (no)
The runtime per-record code paths (performance sensitive): (no)
Anything that affects deployment or recovery: JobManager (and its components), Checkpointing, Yarn/Mesos, ZooKeeper: (no)

Documentation

Does this pull request introduce a new feature? (no)
If yes, how is the feature documented? (not applicable)

thanks for catching it, merging.


The link https://media.m2i.ac.cn/mitosisdetection/download/ for the input data is not working.

The website was moved.
Please refer the following link.
https://www.iti-tju.org/mitosisdetection/download/


Lots of errors and warnings, and a question

I was trying to develop a mod using this template and in the build.gradle files, lots of warnings were coming up about plugins and compileOnly project(":common").
Do not know why this is happening.
And a question:
On other multiloader projects, NOT architectury, when they add a Non-full block with Official Mappings or ParchmentMC, the constructor says public. On my project, these classes have a protected constructor, so I can't use them. Does anyone know why this is happening and how to fix it? I have already run Common/decompile.

Which version were you using, the groovy syntax(build.gradle), or the kotlin syntax (build.gradle.kts)?
The mappings would have nothing to do with the visibility of members, it is possible that those other projects were using access transformers / access wideners, or that Forge itself was making the constructor public, regardless you can use an access widener in common and fabric, and an access transformer in Forge to make the constructor public

I'm using groovy and I also don't know how to use access wideners.

Thank you for your help!

I'm using groovy, don't know why the warnings are popping up.

I believe you can ignore those warnings, I have never gotten accurate groovy support in an IDE, as long as you can run gradlew build, and you get the output jars, it should be working fine, regardless of whatever IDEA thinks the issue is.

Thank you!


[Bug Report] ttnn.conv2d uses too few cores when input channel and out_nhw are small but output channel is large

Describe the bug
Found that ttnn.conv2d only uses 2 cores on N300 to parallel with the parameters below and causes OOM in L1

input_shape: [1, 3, 224, 224]
kernel_shape: [768, 3, 32, 32]
stride: [32, 32]
padding: [0, 0]
dilation: [1, 1]

The error message:
Out of Memory: Not enough space to allocate 3211264 B L1 buffer across 2 banks, where each bank needs to store 1605632 B
backtrace:
 --- /home/jerry/tt-metal/build_Release/lib/libtt_metal.so(+0x116ae5) [0x7fde3ddabae5]
 --- tt::tt_metal::allocator::BankManager::allocate_buffer(unsigned long, unsigned long, bool, CoreRangeSet const&, std::__1::optional<unsigned int>)
 --- tt::tt_metal::allocator::allocate_buffer(tt::tt_metal::Allocator&, unsigned long, tt::tt_metal::v0::Buffer*)
 --- tt::tt_metal::detail::AllocateBuffer(tt::tt_metal::v0::Buffer*)
 --- /home/jerry/tt-metal/build_Release/lib/libtt_metal.so(+0xf3962) [0x7fde3dd88962]
 --- tt::tt_metal::v0::Buffer::create(tt::tt_metal::v0::Device*, unsigned long, unsigned long, tt::tt_metal::BufferType, tt::tt_metal::TensorMemoryLayout, std::__1::optional<tt::tt_metal::ShardSpecBuffer> const&, std::__1::optional<bool>, std::__1::optional<tt::tt_metal::SubDeviceId>)
 --- tt::tt_metal::tensor_impl::allocate_buffer_on_device(tt::tt_metal::v0::Device*, tt::tt_metal::TensorSpec const&)
 --- tt::tt_metal::create_device_tensor(tt::tt_metal::TensorSpec const&, tt::tt_metal::v0::Device*)
 --- tt::tt_metal::create_device_tensor(ttnn::types::Shape const&, tt::tt_metal::DataType, tt::tt_metal::Layout, tt::tt_metal::v0::Device*, tt::tt_metal::MemoryConfig const&, std::__1::optional<tt::tt_metal::Tile> const&)
 --- /home/jerry/tt-metal/ttnn/ttnn/_ttnn.so(_ZN2tt8tt_metal9operation29generic_create_output_tensorsIN4ttnn10operations13data_movement35InterleavedToShardedDeviceOperationEEENS1_21program_output_helperIT_Xsr18has_create_programIS8_EE5valueEE4typeERKS8_RKNSt3__16vectorINS0_6TensorENSD_9allocatorISF_EEEENSD_8optionalINS0_8DataTypeEEENS0_6LayoutERKNSL_INS0_12MemoryConfigEEERKNSL_INS0_4TileEEE+0x227) [0x7fde3f0ebdb7]
 --- ttnn::operations::data_movement::InterleavedToShardedDeviceOperation::create_output_tensors(std::__1::vector<tt::tt_metal::Tensor, std::__1::allocator<tt::tt_metal::Tensor>> const&) const

I guess it is because the input channel (3) is small and output NHW (49 = 1 * 7 * 7) is also small, the determine_parallel_config returns only a 2 core grid with HEIGHT_SHARDED. If we can shard on the output channel (768), then ttnn.conv2d should be able to use more cores and fit in cores' L1
To Reproduce
Run the example below:
import torch
import ttnn

def main(device):
    n, in_c, in_h, in_w = 2, 3, 224, 224
    out_c, k_h, k_w = 768, 32, 32
    stride = 32
    padding = 0
    dilation = 1

    input_tensor = ttnn.from_torch(
        torch.rand((1, 1, n * in_h * in_w, in_c), dtype=torch.bfloat16), layout=ttnn.TILE_LAYOUT, device=device
    )
    weight_tensor = ttnn.from_torch(torch.rand((out_c, in_c, k_h, k_w), dtype=torch.bfloat16), layout=ttnn.TILE_LAYOUT)
    results = ttnn.conv2d(
        input_tensor=input_tensor,
        weight_tensor=weight_tensor,
        bias_tensor=None,
        batch_size=n,
        in_channels=in_c,
        out_channels=out_c,
        input_height=in_h,
        input_width=in_w,
        kernel_size=(k_h, k_w),
        stride=(stride, stride),
        padding=(padding, padding),
        dilation=(dilation, dilation),
        groups=1,
        device=device,
    )
    print(results)

if __name__ == "__main__":
    try:
        device = ttnn.open_device(device_id=0)
        main(device)
    finally:
        ttnn.close_device(device)

Expected behavior
Parallel with more cores and not results in OOM
Please complete the following environment information:

OS: Ubuntu 24.04
Version of software: 3a462dc61885891d47d8c8c482880f7a2c5e816e
Card: N300

Additional context
Maybe this is related to https://github.com/tenstorrent/tt-metal/issues/14435

This issue is the root case of this https://github.com/tenstorrent/tt-metal/issues/13733


Cloud Save disabled if clicking 'Reset'

Describe the bug
Cloud Save disabled if clicking 'Reset'
Steps to reproduce the behavior
1.Navigate to https://arcade.makecode.com/beta#
2.Settings---->About---->Experiments------>Cloud Save---->Enable it
3.Click 'Reset'
Actual behavior
Cloud Save disabled if clicking 'Reset'. But the introduction of 'Reset' is: to clear all projects not mention about disabling Cloud Save.

Additional context
1.OS: Windows(rs6)
2.arcade version: 1.4.3
3.Microsoft MakeCode version: 6.8.30

Interesting edge case. This will be cleared up once Cloud Save is moved out of experiments.

I see this as intentional... reset should log the user out IMO. The main scenario for "reset" is for a shared computer in which case log out makes sense.

This is by design. Reset needs to remove all experimentation features.

Reset also makes high contrast off. Is this also by design?  @abchatra

Yes


Convert util to use ESLint instead of TSLint

TSLint is basically deprecated in favour of a TS plugin for ESLint. We should use ESLint instead.
I did the modification but did not fix the ESLint errors in util. To see the errors run npm run lint:util.
@jumattos can you please have a look. You can tweak the rules to your personal likings  in .eslintrc.json if you want.

I did this a long time ago.


Version 0.4.0 proposal

See docs/CHANGELOG.md and docs/UPGRADE_0.3_0.4.md

This release solves #18

With commit https://github.com/phpcfdi/sat-ws-descarga-masiva/pull/31/commits/87662ca826c2f9b7d991676778343808a1c39707 fix #30

The commit https://github.com/phpcfdi/sat-ws-descarga-masiva/pull/31/commits/6b3b67b5a6351c52f9f05532ec3fbb01d9def3a1 fixes #29


MIDI Tracks have different start points

Thanks for this! It's been helpful for writing music for a musical sculpture I've been working on (https://www.instagram.com/p/CRjiXCpp6vc/ ).
I noticed when exporting from Logic Pro that each track will have an arbitrary start event tick. For instance, in one track I'm working on, the start events are 16899, 17227, 213, and 1085, and they should all be nearly the same. When I'm using the library I have to subtract the difference between the start times to sync them up again. It could be Logic's output, but when I re-import the MIDI files to logic they're all in sync.

Thank you, it’s good to know that my tools are being used to do creative things.
What you’re describing sounds very, very strange.  I will have a look in some Logix Pro files and see what happens.  However, I seem to recall something in the standard that says that the starting point for the tick is arbitrary, as it’s the difference between subsequent values that matters.  It’s possible, if sad, that Apple just decided to be very literal about this.  In that case, a work-around is easy enough to do.  I’ll let you know soonest.
Julian
From: alana314 @.>
Date: Thursday, 29 July 2021 at 23:06
To: jdstmporter/midifiles @.>
Cc: Subscribed @.***>
Subject: [jdstmporter/midifiles] MIDI Tracks have different start points (#1)
Thanks for this! It's been helpful for writing music for a musical sculpture I've been working on (https://www.instagram.com/p/CRjiXCpp6vc/ ).
I noticed when exporting from Logic Pro that each track will have an arbitrary start event tick. For instance, in one track I'm working on, the start events are 16899, 17227, 213, and 1085, and they should all be nearly the same. When I'm using the library I have to subtract the difference between the start times to sync them up again. It could be Logic's output, but when I re-import the MIDI files to logic they're all in sync.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHubhttps://github.com/jdstmporter/midifiles/issues/1, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ACUAJJBQVCKPMI37B3KK56TT2HGHXANCNFSM5BHKUFKQ.

Ok thanks for your quick reply! Here is a screenshot of a MIDI file event list and the sample output of:
c=MIDIFile(file)
    c.parse()
    for idx, track in enumerate(c):
        track.parse()
        print(str(track))

output.txt

I also noticed some strange note off events, like output.txt has MIDI@26347 NOTE_OFF[9] D10 OFF velocity := 128 which I don't believe is in the midi file. I'd attach the MIDI file but it won't let me here.
Thanks!

At this point, I can't really do much, other than say I thunk this is fixed, but I'm not sure.  If you still have problems, please let me know.


KeySqlProperties is not being populated with [Key] attribute

Update() fails in SqlGenerator.InitProperties.cs line 37
KeySqlProperties = props.Where(p => p.GetCustomAttributes().Any()).Select(p => new SqlPropertyMetadata(p)).ToArray();
is always empty, so the update statement ends in "WHERE " with no key=@value which obviously fails in SQL Server with an invalid statement.
I tried using [Key] and [ExplicitKey], it picks up neither. I made this change as a temporary workaround:
KeySqlProperties = props.Where(p => p.GetCustomAttributes().Any()).Select(p => new SqlPropertyMetadata(p)).ToArray();
In props I see my key is defined as:
{ Dapper.Contrib.Extensions.ExplicitKeyAttribute}
Assembly: { Dapper.Contrib, Version = <IP_ADDRESS>, Culture = neutral, PublicKeyToken = null}
AssemblyQualifiedName: "Dapper.Contrib.Extensions.ExplicitKeyAttribute, Dapper.Contrib, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=null"
Attributes: Public | BeforeFieldInit
BaseType: { System.Attribute}
Simple table class with this format:
[Table("TblCity")]
public partial class TblCity
{
[ExplicitKey]
public int Id { get; set; }
public string Name { get; set; }
}
Id is a unique primary key.

What is Dapper.Contrib.Extensions.ExplicitKeyAttribute ?
Need use KeyAttribute from System.ComponentModel.DataAnnotations

Thanks. Conflicting libraries.


"smt init" fails with latest master

With latest master a simple "smt init" fails (this also appears to be the cause for the broken CI runs) . A traceback is included below. AFAICS the faulty commit is in rev. 946a4df , and the reason for the error is that the argument path which is passed to os.path.realpath has value None (see line 33 in sumatra/versioncontrol/_subversion.py)
Traceback (most recent call last):
  File "/home/albert/code/sumatra/bin/smt", line 31, in <module>
    main(sys.argv[2:])
  File "/home/albert/code/sumatra/sumatra/commands.py", line 158, in init
    repository = get_working_copy().repository  # if no repository is specified, we assume there is a working copy in the current directory.
  File "/home/albert/code/sumatra/sumatra/versioncontrol/__init__.py", line 79, in get_working_copy
    wc = working_copy_type(path)
  File "/home/albert/code/sumatra/sumatra/versioncontrol/_subversion.py", line 33, in __init__
    self.path = os.path.realpath(path)
  File "/usr/lib/python2.7/posixpath.py", line 382, in realpath
    path, ok = _joinrealpath('', filename, {})
  File "/usr/lib/python2.7/posixpath.py", line 388, in _joinrealpath
    if isabs(rest):
  File "/usr/lib/python2.7/posixpath.py", line 61, in isabs
    return s.startswith('/')
AttributeError: 'NoneType' object has no attribute 'startswith'

Imported from Bitbucket issue 212,  created by cilix on 08-30-2014 at 00:44, last modified: 08-30-2014 at 00:44

This seems to be fixed.

You should now be able to close it. I've given write access to open-research/sumatra to @maxalbert @wd15 @Felix11H (generally people who have made several pull requests, been active in the Google group or the issue tracker, etc.)

Thanks!


chore: update to recommended raw github source for install script

Your development orb has been published. It will expire in 30 days.
You can preview what this will look like on the CircleCI Orb Registry at the following link:
https://circleci.com/developer/orbs/orb/circleci/serverless-framework?version=dev:5fd858fb0621e91b6574d0014c3777a524c41833

Your development orb has been published. It will expire in 30 days.
You can preview what this will look like on the CircleCI Orb Registry at the following link:
https://circleci.com/developer/orbs/orb/circleci/serverless-framework?version=dev:f04aea573aa6d2c4e1c146f6568b70436b4be7ea

Your development orb has been published. It will expire in 30 days.
You can preview what this will look like on the CircleCI Orb Registry at the following link:
https://circleci.com/developer/orbs/orb/circleci/serverless-framework?version=dev:0af425d5a870c36c6a383adb85fcfe4fca4d0771

Your development orb has been published. It will expire in 30 days.
You can preview what this will look like on the CircleCI Orb Registry at the following link:
https://circleci.com/developer/orbs/orb/circleci/serverless-framework?version=dev:82d058db9c4105dc491845f07f4da9cbd1066678

Your development orb has been published. It will expire in 30 days.
You can preview what this will look like on the CircleCI Orb Registry at the following link:
https://circleci.com/developer/orbs/orb/circleci/serverless-framework?version=dev:61a26c3326d37759907edd2e6b10b89e0d3cecd5


[Won't merge] Testing auth's keychain implementation on GHA

#no-changelog

See failures at https://github.com/firebase/firebase-ios-sdk/actions/runs/1635758403


Same coordinates used in pose and target?

When I load a pose and the target (from dockstring/resources/targets)to visualise the docking, it looks like the ligand is not in the binding site. When Dockstring outputs a pose does it use the same relative coordinates as the target .pdbqt file or can the ligand be translated? If so how do I view the pose of the ligand along with the target?
Thanks

Hi @jonathan-booth, did you look at our visualization tutorial here? We call target.view and I'm pretty sure that results in the ligand being inside the binding site (at least in most cases). Maybe you could look into the differences between your visualization code and target.view?
Alternatively, it's possible that Vina failed to find a low-energy pose for the specific ligand/protein pair you are working with. This happens sometimes- Vina is not perfect. Does it happen consistently or just with one particular input?

OK thanks. I saw the target.view method but I was unsure how to do it with a pose that I'd generated earlier and saved as a .pdb, which is why I was trying to do it in VMD. I got docking scores for thousands of ligands and I saved their poses as pdb files, but I only want to view a few of them. Is there a way to view a pose saved as a pdb alongside the target?

Not sure, I don't think we have a dedicated method. I would recommend trying pymol. @mgarort you have worked more with visualization, do you know of an easy solution?


Amplify build won't work on separate branch, repository keeps getting disconnected

Before opening, please confirm:

[X] I have checked to see if my question is addressed in the FAQ.
[X] I have searched for duplicate or closed issues.
[X] I have read the guide for submitting bug reports.
[X] I have done my best to include a minimal, self-contained set of instructions for consistently reproducing the issue.
[X] I have removed any sensitive information from my code snippets and submission.

App Id
d37cwljekz83a7
AWS Region
us-east-1
Amplify Hosting feature
Frontend builds
Describe the bug
error on the main Amplify page says: "There was an issue connecting to your repo provider, click "Reconnect repository" in General Settings, and then try your build again."
The error message says repo needs to be reconnected, but the build logs show a successful clone. I have re-established the service role as recommended here
In the build logs, I do see a different error: "2023-03-23T04:34:19.754Z [INFO]: BackendEnvironment name move-to-tty for app d37cwljekz83a7 is invalid".
Expected behavior
I don't understand why the first error shows on the main page, when the real issue is not about the repository connection at all. If the BackendEnvironment name is an invalid format, then display that error, and tell me what's invalid about the name that the app accepted earlier.
Reproduction steps
This is happening on every build for my app.
Build Settings
No response
Log output

hiding some logs, hopefully this is enough
```
                                 HEAD is now at 55a664b removing abs url from homepage
2023-03-23T04:33:39.789Z [INFO]: Successfully cleaned up Git credentials
2023-03-23T04:33:39.789Z [INFO]: # Checking for Git submodules at: /codebuild/output/src505025649/src/REPONAME/.gitmodules
2023-03-23T04:33:39.794Z [INFO]: # Retrieving environment cache...
2023-03-23T04:33:39.837Z [WARNING]: ! Unable to write cache: {"code":"ERR_BAD_REQUEST","message":"Request failed with status code 404"})}
2023-03-23T04:33:39.837Z [INFO]: ---- Setting Up SSM Secrets ----
2023-03-23T04:33:39.838Z [INFO]: SSM params {"Path":"/amplify/d37cwljekz83a7/move-to-tty/","WithDecryption":true}
2023-03-23T04:33:39.894Z [INFO]: # Defaulting to Node version 16
2023-03-23T04:33:56.285Z [INFO]: # Node version 16 is available for installation
2023-03-23T04:33:56.378Z [INFO]: # Installing Node version 16
2023-03-23T04:34:02.656Z [INFO]: # Now using Node version 16
2023-03-23T04:34:02.750Z [INFO]: No live updates for this build run
2023-03-23T04:34:02.755Z [INFO]: # Retrieving cache...
2023-03-23T04:34:02.829Z [INFO]: # Retrieved cache
2023-03-23T04:34:19.754Z [INFO]: BackendEnvironment name move-to-tty for app d37cwljekz83a7 is invalid
see a list of supported npm commands, run:
                                 npm help
2023-03-23T04:34:32.794Z [ERROR]: !!! Build failed
2023-03-23T04:34:32.794Z [ERROR]: !!! Non-Zero Exit Code detected
2023-03-23T04:34:32.795Z [INFO]: # Starting environment caching...
2023-03-23T04:34:32.795Z [INFO]: # Environment caching completed
Terminating logging...

</details>

### Additional information

If you can let me know how to get this to build -- what characters are or aren't allowed in the BackendEnvironment name -- that'd be great.

Hi @sknep 👋🏽 thanks for raising this issue and apologies for the delay here. There's a few key points here:

The reconnect repository error is definitely misleading. We will take this as an action item to surface the appropriate error. However, we need reproduction steps to understand how the wrong error is surfacing in the first place.

Backend environments must be named within 10 characters and must be alphanumeric with no special characters. By default, Amplify will try to use the frontend branch name to name the backend environment if it is being created during the CI/CD process. If your branch name doesn't fit the naming convention, Amplify will generate a random name for the backend. While this error shows up, this does not appear to be what is causing the builds to fail.

Your build appeared to fail after running the following command:

# Executing command: if [ "${AWS_BRANCH}" != "master" ]; then npm build; fi
Unknown command: "build"
Did you mean this?
npm run build # run the "build" package script

I think you have to modify your command to run npm run build. Please try that modification and let us know if this unblocks you.

Thanks. I made a new amplify app with the right build command a few days ago and it works great. Best of luck figuring out the error display.

We will work on improving the error messaging so that the issue is easier to troubleshoot. We are tracking this internally.