[7.10.2] Can't create index pattern

Chart version:
7.10.2
Kubernetes version:
1.19.3
Kubernetes provider: E.g. GKE (Google Kubernetes Engine)
AKS
Helm Version:
Version:"v3.4.2"
helm get release output
e.g. helm get elasticsearch (replace elasticsearch with the name of your helm release)

Output of helm get all elasticsearch
NAME: elasticsearch
LAST DEPLOYED: Fri Jan 15 10:42:11 2021
NAMESPACE: elastic
STATUS: deployed
REVISION: 1
USER-SUPPLIED VALUES:
antiAffinity: soft
antiAffinityTopologyKey: kubernetes.io/hostname
clusterHealthCheckParams: wait_for_status=green&timeout=1s
clusterName: elasticsearch
esConfig:
  elasticsearch.yml: |
    logger.org.elasticsearch.discovery: DEBUG
    # xpack.security.enabled: true
    # xpack.security.transport.ssl.enabled: true
    # xpack.security.transport.ssl.verification_mode: certificate
    # xpack.security.transport.ssl.keystore.path: /usr/share/elasticsearch/config/certs/elastic-certificates.p12
    # xpack.security.transport.ssl.truststore.path: /usr/share/elasticsearch/config/certs/elastic-certificates.p12
    # xpack.security.http.ssl.enabled: true
    # xpack.security.http.ssl.truststore.path: /usr/share/elasticsearch/config/certs/elastic-certificates.p12
    # xpack.security.http.ssl.keystore.path: /usr/share/elasticsearch/config/certs/elastic-certificates.p12
esJavaOpts: -Xmx256m -Xms256m
esMajorVersion: ""
extraContainers: ""
extraEnvs:
- name: ELASTIC_PASSWORD
  valueFrom:
    secretKeyRef:
      key: password
      name: elastic-credentials
- name: ELASTIC_USERNAME
  valueFrom:
    secretKeyRef:
      key: username
      name: elastic-credentials
extraInitContainers: ""
extraVolumeMounts: ""
extraVolumes: ""
fsGroup: ""
fullnameOverride: ""
httpPort: 9200
image: docker.elastic.co/elasticsearch/elasticsearch
imagePullPolicy: IfNotPresent
imagePullSecrets: []
imageTag: 7.10.2
ingress:
  annotations: {}
  enabled: false
  hosts:
  - chart-example.local
  path: /
  tls: []
initResources: {}
keystore: []
labels: {}
lifecycle: {}
masterService: ""
masterTerminationFix: false
maxUnavailable: 1
minimumMasterNodes: 1
nameOverride: ""
networkHost: <IP_ADDRESS>
nodeAffinity: {}
nodeGroup: master
nodeSelector: {}
persistence:
  annotations: {}
  enabled: true
podAnnotations: {}
podManagementPolicy: Parallel
podSecurityContext:
  fsGroup: 1000
  runAsUser: 1000
podSecurityPolicy:
  create: false
  name: ""
  spec:
    fsGroup:
      rule: RunAsAny
    privileged: true
    runAsUser:
      rule: RunAsAny
    seLinux:
      rule: RunAsAny
    supplementalGroups:
      rule: RunAsAny
    volumes:
    - secret
    - configMap
    - persistentVolumeClaim
priorityClassName: ""
protocol: http
rbac:
  create: false
  serviceAccountName: ""
readinessProbe:
  failureThreshold: 3
  initialDelaySeconds: 60
  periodSeconds: 30
  successThreshold: 3
  timeoutSeconds: 15
replicas: 2
resources:
  limits:
    cpu: 500m
    memory: 800Mi
  requests:
    cpu: 500m
    memory: 800Mi
roles:
  data: "true"
  ingest: "true"
  master: "true"
schedulerName: ""
secretMounts:
- name: elastic-certificates
  path: /usr/share/elasticsearch/config/certs
  secretName: elastic-certificates
securityContext:
  capabilities:
    drop:
    - ALL
  runAsNonRoot: true
  runAsUser: 1000
service:
  annotations: {}
  httpPortName: http
  labels: {}
  labelsHeadless: {}
  loadBalancerSourceRanges: []
  nodePort: ""
  transportPortName: transport
  type: ClusterIP
sidecarResources: {}
sysctlInitContainer:
  enabled: true
sysctlVmMaxMapCount: 262144
terminationGracePeriod: 120
tolerations: []
transportPort: 9300
updateStrategy: RollingUpdate
volumeClaimTemplate:
  accessModes:
  - ReadWriteOnce
  resources:
    requests:
      storage: 10Gi
  storageClassName: managed-premium

COMPUTED VALUES:
antiAffinity: soft
antiAffinityTopologyKey: kubernetes.io/hostname
clusterHealthCheckParams: wait_for_status=green&timeout=1s
clusterName: elasticsearch
enableServiceLinks: true
envFrom: []
esConfig:
  elasticsearch.yml: |
    logger.org.elasticsearch.discovery: DEBUG
    # xpack.security.enabled: true
    # xpack.security.transport.ssl.enabled: true
    # xpack.security.transport.ssl.verification_mode: certificate
    # xpack.security.transport.ssl.keystore.path: /usr/share/elasticsearch/config/certs/elastic-certificates.p12
    # xpack.security.transport.ssl.truststore.path: /usr/share/elasticsearch/config/certs/elastic-certificates.p12
    # xpack.security.http.ssl.enabled: true
    # xpack.security.http.ssl.truststore.path: /usr/share/elasticsearch/config/certs/elastic-certificates.p12
    # xpack.security.http.ssl.keystore.path: /usr/share/elasticsearch/config/certs/elastic-certificates.p12
esJavaOpts: -Xmx256m -Xms256m
esMajorVersion: ""
extraContainers: ""
extraEnvs:
- name: ELASTIC_PASSWORD
  valueFrom:
    secretKeyRef:
      key: password
      name: elastic-credentials
- name: ELASTIC_USERNAME
  valueFrom:
    secretKeyRef:
      key: username
      name: elastic-credentials
extraInitContainers: ""
extraVolumeMounts: ""
extraVolumes: ""
fsGroup: ""
fullnameOverride: ""
hostAliases: []
httpPort: 9200
image: docker.elastic.co/elasticsearch/elasticsearch
imagePullPolicy: IfNotPresent
imagePullSecrets: []
imageTag: 7.10.2
ingress:
  annotations: {}
  enabled: false
  hosts:
  - chart-example.local
  path: /
  tls: []
initResources: {}
keystore: []
labels: {}
lifecycle: {}
masterService: ""
masterTerminationFix: false
maxUnavailable: 1
minimumMasterNodes: 1
nameOverride: ""
networkHost: <IP_ADDRESS>
nodeAffinity: {}
nodeGroup: master
nodeSelector: {}
persistence:
  annotations: {}
  enabled: true
  labels:
    enabled: false
podAnnotations: {}
podManagementPolicy: Parallel
podSecurityContext:
  fsGroup: 1000
  runAsUser: 1000
podSecurityPolicy:
  create: false
  name: ""
  spec:
    fsGroup:
      rule: RunAsAny
    privileged: true
    runAsUser:
      rule: RunAsAny
    seLinux:
      rule: RunAsAny
    supplementalGroups:
      rule: RunAsAny
    volumes:
    - secret
    - configMap
    - persistentVolumeClaim
priorityClassName: ""
protocol: http
rbac:
  create: false
  serviceAccountAnnotations: {}
  serviceAccountName: ""
readinessProbe:
  failureThreshold: 3
  initialDelaySeconds: 60
  periodSeconds: 30
  successThreshold: 3
  timeoutSeconds: 15
replicas: 2
resources:
  limits:
    cpu: 500m
    memory: 800Mi
  requests:
    cpu: 500m
    memory: 800Mi
roles:
  data: "true"
  ingest: "true"
  master: "true"
  remote_cluster_client: "true"
schedulerName: ""
secretMounts:
- name: elastic-certificates
  path: /usr/share/elasticsearch/config/certs
  secretName: elastic-certificates
securityContext:
  capabilities:
    drop:
    - ALL
  runAsNonRoot: true
  runAsUser: 1000
service:
  annotations: {}
  externalTrafficPolicy: ""
  httpPortName: http
  labels: {}
  labelsHeadless: {}
  loadBalancerIP: ""
  loadBalancerSourceRanges: []
  nodePort: ""
  transportPortName: transport
  type: ClusterIP
sidecarResources: {}
sysctlInitContainer:
  enabled: true
sysctlVmMaxMapCount: 262144
terminationGracePeriod: 120
tolerations: []
transportPort: 9300
updateStrategy: RollingUpdate
volumeClaimTemplate:
  accessModes:
  - ReadWriteOnce
  resources:
    requests:
      storage: 10Gi
  storageClassName: managed-premium

HOOKS:
---
# Source: elasticsearch/templates/test/test-elasticsearch-health.yaml
apiVersion: v1
kind: Pod
metadata:
  name: "elasticsearch-azvbj-test"
  annotations:
    "helm.sh/hook": test
    "helm.sh/hook-delete-policy": hook-succeeded
spec:
  securityContext:
    fsGroup: 1000
    runAsUser: 1000
  containers:
  - name: "elasticsearch-vinsr-test"
    image: "docker.elastic.co/elasticsearch/elasticsearch:7.10.2"
    imagePullPolicy: "IfNotPresent"
    command:
      - "sh"
      - "-c"
      - |
        #!/usr/bin/env bash -e
        curl -XGET --fail 'elasticsearch-master:9200/_cluster/health?wait_for_status=green&timeout=1s'
  restartPolicy: Never
MANIFEST:
---
# Source: elasticsearch/templates/poddisruptionbudget.yaml
apiVersion: policy/v1beta1
kind: PodDisruptionBudget
metadata:
  name: "elasticsearch-master-pdb"
spec:
  maxUnavailable: 1
  selector:
    matchLabels:
      app: "elasticsearch-master"
---
# Source: elasticsearch/templates/configmap.yaml
apiVersion: v1
kind: ConfigMap
metadata:
  name: elasticsearch-master-config
  labels:
    heritage: "Helm"
    release: "elasticsearch"
    chart: "elasticsearch"
    app: "elasticsearch-master"
data:
  elasticsearch.yml: |
    logger.org.elasticsearch.discovery: DEBUG
    # xpack.security.enabled: true
    # xpack.security.transport.ssl.enabled: true
    # xpack.security.transport.ssl.verification_mode: certificate
    # xpack.security.transport.ssl.keystore.path: /usr/share/elasticsearch/config/certs/elastic-certificates.p12
    # xpack.security.transport.ssl.truststore.path: /usr/share/elasticsearch/config/certs/elastic-certificates.p12
    # xpack.security.http.ssl.enabled: true
    # xpack.security.http.ssl.truststore.path: /usr/share/elasticsearch/config/certs/elastic-certificates.p12
    # xpack.security.http.ssl.keystore.path: /usr/share/elasticsearch/config/certs/elastic-certificates.p12
---
# Source: elasticsearch/templates/service.yaml
kind: Service
apiVersion: v1
metadata:
  name: elasticsearch-master
  labels:
    heritage: "Helm"
    release: "elasticsearch"
    chart: "elasticsearch"
    app: "elasticsearch-master"
  annotations:
    {}
spec:
  type: ClusterIP
  selector:
    release: "elasticsearch"
    chart: "elasticsearch"
    app: "elasticsearch-master"
  ports:
  - name: http
    protocol: TCP
    port: 9200
  - name: transport
    protocol: TCP
    port: 9300
---
# Source: elasticsearch/templates/service.yaml
kind: Service
apiVersion: v1
metadata:
  name: elasticsearch-master-headless
  labels:
    heritage: "Helm"
    release: "elasticsearch"
    chart: "elasticsearch"
    app: "elasticsearch-master"
  annotations:
    service.alpha.kubernetes.io/tolerate-unready-endpoints: "true"
spec:
  clusterIP: None # This is needed for statefulset hostnames like elasticsearch-0 to resolve
  # Create endpoints also if the related pod isn't ready
  publishNotReadyAddresses: true
  selector:
    app: "elasticsearch-master"
  ports:
  - name: http
    port: 9200
  - name: transport
    port: 9300
---
# Source: elasticsearch/templates/statefulset.yaml
apiVersion: apps/v1
kind: StatefulSet
metadata:
  name: elasticsearch-master
  labels:
    heritage: "Helm"
    release: "elasticsearch"
    chart: "elasticsearch"
    app: "elasticsearch-master"
  annotations:
    esMajorVersion: "7"
spec:
  serviceName: elasticsearch-master-headless
  selector:
    matchLabels:
      app: "elasticsearch-master"
  replicas: 2
  podManagementPolicy: Parallel
  updateStrategy:
    type: RollingUpdate
  volumeClaimTemplates:
  - metadata:
      name: elasticsearch-master
    spec:
      accessModes:
      - ReadWriteOnce
      resources:
        requests:
          storage: 10Gi
      storageClassName: managed-premium
  template:
    metadata:
      name: "elasticsearch-master"
      labels:
        release: "elasticsearch"
        chart: "elasticsearch"
        app: "elasticsearch-master"
      annotations:

        configchecksum: bb7cc7c26950ce11b1bd1944ed558b73bb37b4952c3f58a2ef1c6e545ead6a5
    spec:
      securityContext:
        fsGroup: 1000
        runAsUser: 1000
      affinity:
        podAntiAffinity:
          preferredDuringSchedulingIgnoredDuringExecution:
          - weight: 1
            podAffinityTerm:
              topologyKey: kubernetes.io/hostname
              labelSelector:
                matchExpressions:
                - key: app
                  operator: In
                  values:
                  - "elasticsearch-master"
      terminationGracePeriodSeconds: 120
      volumes:
        - name: elastic-certificates
          secret:
            secretName: elastic-certificates
        - name: esconfig
          configMap:
            name: elasticsearch-master-config
      enableServiceLinks: true
      initContainers:
      - name: configure-sysctl
        securityContext:
          runAsUser: 0
          privileged: true
        image: "docker.elastic.co/elasticsearch/elasticsearch:7.10.2"
        imagePullPolicy: "IfNotPresent"
        command: ["sysctl", "-w", "vm.max_map_count=262144"]
        resources:
          {}

      containers:
      - name: "elasticsearch"
        securityContext:
          capabilities:
            drop:
            - ALL
          runAsNonRoot: true
          runAsUser: 1000
        image: "docker.elastic.co/elasticsearch/elasticsearch:7.10.2"
        imagePullPolicy: "IfNotPresent"
        readinessProbe:
          exec:
            command:
              - sh
              - -c
              - |
                #!/usr/bin/env bash -e
                # If the node is starting up wait for the cluster to be ready (request params: "wait_for_status=green&timeout=1s" )
                # Once it has started only check that the node itself is responding
                START_FILE=/tmp/.es_start_file

                # Disable nss cache to avoid filling dentry cache when calling curl
                # This is required with Elasticsearch Docker using nss < 3.52
                export NSS_SDB_USE_CACHE=no

                http () {
                  local path="${1}"
                  local args="${2}"
                  set -- -XGET -s

                  if [ "$args" != "" ]; then
                    set -- "$@" $args
                  fi

                  if [ -n "${ELASTIC_USERNAME}" ] && [ -n "${ELASTIC_PASSWORD}" ]; then
                    set -- "$@" -u "${ELASTIC_USERNAME}:${ELASTIC_PASSWORD}"
                  fi

                  curl --output /dev/null -k "$@" "http://<IP_ADDRESS>:9200${path}"
                }

                if [ -f "${START_FILE}" ]; then
                  echo 'Elasticsearch is already running, lets check the node is healthy'
                  HTTP_CODE=$(http "/" "-w %{http_code}")
                  RC=$?
                  if [[ ${RC} -ne 0 ]]; then
                    echo "curl --output /dev/null -k -XGET -s -w '%{http_code}' \${BASIC_AUTH} http://<IP_ADDRESS>:9200/ failed with RC ${RC}"
                    exit ${RC}
                  fi
                  # ready if HTTP code 200, 503 is tolerable if ES version is 6.x
                  if [[ ${HTTP_CODE} == "200" ]]; then
                    exit 0
                  elif [[ ${HTTP_CODE} == "503" && "7" == "6" ]]; then
                    exit 0
                  else
                    echo "curl --output /dev/null -k -XGET -s -w '%{http_code}' \${BASIC_AUTH} http://<IP_ADDRESS>:9200/ failed with HTTP code ${HTTP_CODE}"
                    exit 1
                  fi

                else
                  echo 'Waiting for elasticsearch cluster to become ready (request params: "wait_for_status=green&timeout=1s" )'
                  if http "/_cluster/health?wait_for_status=green&timeout=1s" "--fail" ; then
                    touch ${START_FILE}
                    exit 0
                  else
                    echo 'Cluster is not yet ready (request params: "wait_for_status=green&timeout=1s" )'
                    exit 1
                  fi
                fi
          failureThreshold: 3
          initialDelaySeconds: 60
          periodSeconds: 30
          successThreshold: 3
          timeoutSeconds: 15
        ports:
        - name: http
          containerPort: 9200
        - name: transport
          containerPort: 9300
        resources:
          limits:
            cpu: 500m
            memory: 800Mi
          requests:
            cpu: 500m
            memory: 800Mi
        env:
          - name: node.name
            valueFrom:
              fieldRef:
                fieldPath: metadata.name
          - name: cluster.initial_master_nodes
            value: "elasticsearch-master-0,elasticsearch-master-1,"
          - name: discovery.seed_hosts
            value: "elasticsearch-master-headless"
          - name: cluster.name
            value: "elasticsearch"
          - name: network.host
            value: "<IP_ADDRESS>"
          - name: ES_JAVA_OPTS
            value: "-Xmx256m -Xms256m"
          - name: node.data
            value: "true"
          - name: node.ingest
            value: "true"
          - name: node.master
            value: "true"
          - name: node.remote_cluster_client
            value: "true"
          - name: ELASTIC_PASSWORD
            valueFrom:
              secretKeyRef:
                key: password
                name: elastic-credentials
          - name: ELASTIC_USERNAME
            valueFrom:
              secretKeyRef:
                key: username
                name: elastic-credentials
        volumeMounts:
          - name: "elasticsearch-master"
            mountPath: /usr/share/elasticsearch/data

          - name: elastic-certificates
            mountPath: /usr/share/elasticsearch/config/certs
          - name: esconfig
            mountPath: /usr/share/elasticsearch/config/elasticsearch.yml
            subPath: elasticsearch.yml

NOTES:
1. Watch all cluster members come up.
  $ kubectl get pods --namespace=elastic -l app=elasticsearch-master -w
2. Test cluster health using Helm test.
  $ helm test elasticsearch

Output of helm get all kibana
NAME: kibana
LAST DEPLOYED: Fri Jan 15 10:42:10 2021
NAMESPACE: elastic
STATUS: deployed
REVISION: 1
TEST SUITE: None
USER-SUPPLIED VALUES:
affinity: {}
elasticsearchHosts: http://elasticsearch-master:9200
elasticsearchURL: ""
envFrom: []
extraContainers: ""
extraEnvs:
- name: NODE_OPTIONS
  value: --max-old-space-size=1800
- name: ELASTICSEARCH_USERNAME
  valueFrom:
    secretKeyRef:
      key: username
      name: elastic-credentials
- name: ELASTICSEARCH_PASSWORD
  valueFrom:
    secretKeyRef:
      key: password
      name: elastic-credentials
- name: KIBANA_ENCRYPTION_KEY
  valueFrom:
    secretKeyRef:
      key: encryptionkey
      name: kibana
extraInitContainers: ""
fullnameOverride: ""
healthCheckPath: /app/kibana
hostAliases: []
httpPort: 5601
image: docker.elastic.co/kibana/kibana
imagePullPolicy: IfNotPresent
imagePullSecrets: []
imageTag: 7.10.2
ingress:
  annotations: {}
  enabled: false
  hosts:
  - host: chart-example.local
    paths:
    - path: /
  tls: []
kibanaConfig:
  kibana.yml: |
    kibana:
      autocompleteTimeout: 10000
    # server.ssl:
    #   enabled: true
    #   key: /usr/share/kibana/config/certs/elastic-certificate.pem
    #   certificate: /usr/share/kibana/config/certs/elastic-certificate.pem
    # xpack.security.encryptionKey: ${KIBANA_ENCRYPTION_KEY}
    elasticsearch:
      requestTimeout: 1200000
      shardTimeout: 0
      # ssl:
      #   certificateAuthorities: /usr/share/kibana/config/certs/elastic-certificate.pem
      #   verificationMode: certificate
labels: {}
lifecycle: {}
nameOverride: ""
nodeSelector: {}
podAnnotations: {}
podSecurityContext:
  fsGroup: 1000
priorityClassName: ""
protocol: http
readinessProbe:
  failureThreshold: 3
  initialDelaySeconds: 10
  periodSeconds: 10
  successThreshold: 3
  timeoutSeconds: 5
replicas: 1
resources:
  limits:
    cpu: 250m
    memory: 1000Mi
  requests:
    cpu: 250m
    memory: 700Mi
secretMounts:
- name: elastic-certificate-pem
  path: /usr/share/kibana/config/certs
  secretName: elastic-certificate-pem
securityContext:
  capabilities:
    drop:
    - ALL
  runAsNonRoot: true
  runAsUser: 1000
serverHost: <IP_ADDRESS>
service:
  annotations: {}
  httpPortName: http
  labels: {}
  loadBalancerIP: ""
  loadBalancerSourceRanges: []
  nodePort: ""
  port: 5601
  type: ClusterIP
serviceAccount: ""
tolerations: []
updateStrategy:
  type: Recreate

COMPUTED VALUES:
affinity: {}
elasticsearchHosts: http://elasticsearch-master:9200
elasticsearchURL: ""
envFrom: []
extraContainers: ""
extraEnvs:
- name: NODE_OPTIONS
  value: --max-old-space-size=1800
- name: ELASTICSEARCH_USERNAME
  valueFrom:
    secretKeyRef:
      key: username
      name: elastic-credentials
- name: ELASTICSEARCH_PASSWORD
  valueFrom:
    secretKeyRef:
      key: password
      name: elastic-credentials
- name: KIBANA_ENCRYPTION_KEY
  valueFrom:
    secretKeyRef:
      key: encryptionkey
      name: kibana
extraInitContainers: ""
fullnameOverride: ""
healthCheckPath: /app/kibana
hostAliases: []
httpPort: 5601
image: docker.elastic.co/kibana/kibana
imagePullPolicy: IfNotPresent
imagePullSecrets: []
imageTag: 7.10.2
ingress:
  annotations: {}
  enabled: false
  hosts:
  - host: chart-example.local
    paths:
    - path: /
  path: /
  tls: []
kibanaConfig:
  kibana.yml: |
    kibana:
      autocompleteTimeout: 10000
    # server.ssl:
    #   enabled: true
    #   key: /usr/share/kibana/config/certs/elastic-certificate.pem
    #   certificate: /usr/share/kibana/config/certs/elastic-certificate.pem
    # xpack.security.encryptionKey: ${KIBANA_ENCRYPTION_KEY}
    elasticsearch:
      requestTimeout: 1200000
      shardTimeout: 0
      # ssl:
      #   certificateAuthorities: /usr/share/kibana/config/certs/elastic-certificate.pem
      #   verificationMode: certificate
labels: {}
lifecycle: {}
nameOverride: ""
nodeSelector: {}
podAnnotations: {}
podSecurityContext:
  fsGroup: 1000
priorityClassName: ""
protocol: http
readinessProbe:
  failureThreshold: 3
  initialDelaySeconds: 10
  periodSeconds: 10
  successThreshold: 3
  timeoutSeconds: 5
replicas: 1
resources:
  limits:
    cpu: 250m
    memory: 1000Mi
  requests:
    cpu: 250m
    memory: 700Mi
secretMounts:
- name: elastic-certificate-pem
  path: /usr/share/kibana/config/certs
  secretName: elastic-certificate-pem
securityContext:
  capabilities:
    drop:
    - ALL
  runAsNonRoot: true
  runAsUser: 1000
serverHost: <IP_ADDRESS>
service:
  annotations: {}
  httpPortName: http
  labels: {}
  loadBalancerIP: ""
  loadBalancerSourceRanges: []
  nodePort: ""
  port: 5601
  type: ClusterIP
serviceAccount: ""
tolerations: []
updateStrategy:
  type: Recreate

HOOKS:
MANIFEST:
---
# Source: kibana/templates/configmap.yaml
apiVersion: v1
kind: ConfigMap
metadata:
  name: kibana-kibana-config
  labels:
    app: kibana
    release: "kibana"
    heritage: Helm
data:
  kibana.yml: |
    kibana:
      autocompleteTimeout: 10000
    # server.ssl:
    #   enabled: true
    #   key: /usr/share/kibana/config/certs/elastic-certificate.pem
    #   certificate: /usr/share/kibana/config/certs/elastic-certificate.pem
    # xpack.security.encryptionKey: ${KIBANA_ENCRYPTION_KEY}
    elasticsearch:
      requestTimeout: 1200000
      shardTimeout: 0
      # ssl:
      #   certificateAuthorities: /usr/share/kibana/config/certs/elastic-certificate.pem
      #   verificationMode: certificate
---
# Source: kibana/templates/service.yaml
apiVersion: v1
kind: Service
metadata:
  name: kibana-kibana
  labels:
    app: kibana
    release: "kibana"
    heritage: Helm
spec:
  type: ClusterIP
  ports:
    - port: 5601
      protocol: TCP
      name: http
      targetPort: 5601
  selector:
    app: kibana
    release: "kibana"
---
# Source: kibana/templates/deployment.yaml
apiVersion: apps/v1
kind: Deployment
metadata:
  name: kibana-kibana
  labels:
    app: kibana
    release: "kibana"
    heritage: Helm
spec:
  replicas: 1
  strategy:
    type: Recreate
  selector:
    matchLabels:
      app: kibana
      release: "kibana"
  template:
    metadata:
      labels:
        app: kibana
        release: "kibana"
      annotations:

        configchecksum: 00fe223dec8aa4956dccd07e8866221c027f61d5a296a046fea67a3de34fe33
    spec:
      securityContext:
        fsGroup: 1000
      volumes:
        - name: elastic-certificate-pem
          secret:
            secretName: elastic-certificate-pem
        - name: kibanaconfig
          configMap:
            name: kibana-kibana-config
      containers:
      - name: kibana
        securityContext:
          capabilities:
            drop:
            - ALL
          runAsNonRoot: true
          runAsUser: 1000
        image: "docker.elastic.co/kibana/kibana:7.10.2"
        imagePullPolicy: "IfNotPresent"
        env:
          - name: ELASTICSEARCH_HOSTS
            value: "http://elasticsearch-master:9200"
          - name: SERVER_HOST
            value: "<IP_ADDRESS>"
          - name: NODE_OPTIONS
            value: --max-old-space-size=1800
          - name: ELASTICSEARCH_USERNAME
            valueFrom:
              secretKeyRef:
                key: username
                name: elastic-credentials
          - name: ELASTICSEARCH_PASSWORD
            valueFrom:
              secretKeyRef:
                key: password
                name: elastic-credentials
          - name: KIBANA_ENCRYPTION_KEY
            valueFrom:
              secretKeyRef:
                key: encryptionkey
                name: kibana
        readinessProbe:
          failureThreshold: 3
          initialDelaySeconds: 10
          periodSeconds: 10
          successThreshold: 3
          timeoutSeconds: 5
          exec:
            command:
              - sh
              - -c
              - |
                #!/usr/bin/env bash -e

                # Disable nss cache to avoid filling dentry cache when calling curl
                # This is required with Kibana Docker using nss < 3.52
                export NSS_SDB_USE_CACHE=no

                http () {
                    local path="${1}"
                    set -- -XGET -s --fail -L

                    if [ -n "${ELASTICSEARCH_USERNAME}" ] && [ -n "${ELASTICSEARCH_PASSWORD}" ]; then
                      set -- "$@" -u "${ELASTICSEARCH_USERNAME}:${ELASTICSEARCH_PASSWORD}"
                    fi

                    STATUS=$(curl --output /dev/null --write-out "%{http_code}" -k "$@" "http://localhost:5601${path}")
                    if [[ "${STATUS}" -eq 200 ]]; then
                      exit 0
                    fi

                    echo "Error: Got HTTP code ${STATUS} but expected a 200"
                    exit 1
                }

                http "/app/kibana"
        ports:
        - containerPort: 5601
        resources:
          limits:
            cpu: 250m
            memory: 1000Mi
          requests:
            cpu: 250m
            memory: 700Mi
        volumeMounts:
          - name: elastic-certificate-pem
            mountPath: /usr/share/kibana/config/certs
          - name: kibanaconfig
            mountPath: /usr/share/kibana/config/kibana.yml
            subPath: kibana.yml

Output of helm get all filebeat
NAME: filebeat
LAST DEPLOYED: Fri Jan 15 10:42:10 2021
NAMESPACE: elastic
STATUS: deployed
REVISION: 1
TEST SUITE: None
USER-SUPPLIED VALUES:
affinity: {}
clusterRoleRules:
- apiGroups:
  - ""
  resources:
  - namespaces
  - nodes
  - pods
  verbs:
  - get
  - list
  - watch
daemonset:
  affinity: {}
  annotations: {}
  enabled: true
  envFrom: []
  extraEnvs:
  - name: ELASTICSEARCH_USERNAME
    valueFrom:
      secretKeyRef:
        key: username
        name: elastic-credentials
  - name: ELASTICSEARCH_PASSWORD
    valueFrom:
      secretKeyRef:
        key: password
        name: elastic-credentials
  extraVolumeMounts: []
  extraVolumes: []
  filebeatConfig: {}
  hostNetworking: false
  labels: {}
  nodeSelector: {}
  resources:
    limits:
      cpu: 250m
      memory: 200Mi
    requests:
      cpu: 100m
      memory: 100Mi
  secretMounts:
  - name: elastic-certificate-pem
    path: /usr/share/filebeat/config/certs
    secretName: elastic-certificate-pem
  securityContext:
    privileged: false
    runAsUser: 0
  tolerations: []
dnsConfig: {}
envFrom: []
extraContainers: ""
extraEnvs:
- name: ELASTICSEARCH_USERNAME
  valueFrom:
    secretKeyRef:
      key: username
      name: elastic-credentials
- name: ELASTICSEARCH_PASSWORD
  valueFrom:
    secretKeyRef:
      key: password
      name: elastic-credentials
extraInitContainers: []
extraVolumeMounts: []
extraVolumes: []
filebeatConfig:
  filebeat.yml: |
    filebeat.inputs:
    - type: container
      paths:
        - /var/log/containers/*.log
      processors:
      - add_kubernetes_metadata:
          host: ${NODE_NAME}
          matchers:
          - logs_path:
              logs_path: "/var/log/containers/"
      - drop_event:
          when:
            not:
              equals:
                kubernetes.namespace: "elastic"
    output.elasticsearch:
      # username: '${ELASTICSEARCH_USERNAME}'
      # password: '${ELASTICSEARCH_PASSWORD}'
      protocol: http
      hosts: ["elasticsearch-master:9200"]
      # ssl.certificate_authorities:
      #   - /usr/share/filebeat/config/certs/elastic-certificate.pem
fullnameOverride: ""
hostAliases: []
hostPathRoot: /var/lib
image: docker.elastic.co/beats/filebeat
imagePullPolicy: IfNotPresent
imagePullSecrets: []
imageTag: 7.10.2
labels: {}
livenessProbe:
  exec:
    command:
    - sh
    - -c
    - |
      #!/usr/bin/env bash -e
      curl --fail <IP_ADDRESS>:5066
  failureThreshold: 3
  initialDelaySeconds: 10
  periodSeconds: 10
  timeoutSeconds: 5
managedServiceAccount: true
nameOverride: ""
nodeSelector: {}
podAnnotations: {}
podSecurityContext: {}
priorityClassName: ""
readinessProbe:
  exec:
    command:
    - sh
    - -c
    - |
      #!/usr/bin/env bash -e
      filebeat test output
  failureThreshold: 3
  initialDelaySeconds: 10
  periodSeconds: 10
  timeoutSeconds: 5
replicas: 1
resources: {}
secretMounts:
- name: elastic-certificate-pem
  path: /usr/share/filebeat/config/certs
  secretName: elastic-certificate-pem
serviceAccount: ""
serviceAccountAnnotations: {}
terminationGracePeriod: 30
tolerations: []
updateStrategy: RollingUpdate

COMPUTED VALUES:
affinity: {}
clusterRoleRules:
- apiGroups:
  - ""
  resources:
  - namespaces
  - nodes
  - pods
  verbs:
  - get
  - list
  - watch
daemonset:
  affinity: {}
  annotations: {}
  enabled: true
  envFrom: []
  extraEnvs:
  - name: ELASTICSEARCH_USERNAME
    valueFrom:
      secretKeyRef:
        key: username
        name: elastic-credentials
  - name: ELASTICSEARCH_PASSWORD
    valueFrom:
      secretKeyRef:
        key: password
        name: elastic-credentials
  extraVolumeMounts: []
  extraVolumes: []
  filebeatConfig: {}
  hostNetworking: false
  labels: {}
  nodeSelector: {}
  resources:
    limits:
      cpu: 250m
      memory: 200Mi
    requests:
      cpu: 100m
      memory: 100Mi
  secretMounts:
  - name: elastic-certificate-pem
    path: /usr/share/filebeat/config/certs
    secretName: elastic-certificate-pem
  securityContext:
    privileged: false
    runAsUser: 0
  tolerations: []
dnsConfig: {}
envFrom: []
extraContainers: ""
extraEnvs:
- name: ELASTICSEARCH_USERNAME
  valueFrom:
    secretKeyRef:
      key: username
      name: elastic-credentials
- name: ELASTICSEARCH_PASSWORD
  valueFrom:
    secretKeyRef:
      key: password
      name: elastic-credentials
extraInitContainers: []
extraVolumeMounts: []
extraVolumes: []
filebeatConfig:
  filebeat.yml: |
    filebeat.inputs:
    - type: container
      paths:
        - /var/log/containers/*.log
      processors:
      - add_kubernetes_metadata:
          host: ${NODE_NAME}
          matchers:
          - logs_path:
              logs_path: "/var/log/containers/"
      - drop_event:
          when:
            not:
              equals:
                kubernetes.namespace: "elastic"
    output.elasticsearch:
      # username: '${ELASTICSEARCH_USERNAME}'
      # password: '${ELASTICSEARCH_PASSWORD}'
      protocol: http
      hosts: ["elasticsearch-master:9200"]
      # ssl.certificate_authorities:
      #   - /usr/share/filebeat/config/certs/elastic-certificate.pem
fullnameOverride: ""
hostAliases: []
hostNetworking: false
hostPathRoot: /var/lib
image: docker.elastic.co/beats/filebeat
imagePullPolicy: IfNotPresent
imagePullSecrets: []
imageTag: 7.10.2
labels: {}
livenessProbe:
  exec:
    command:
    - sh
    - -c
    - |
      #!/usr/bin/env bash -e
      curl --fail <IP_ADDRESS>:5066
  failureThreshold: 3
  initialDelaySeconds: 10
  periodSeconds: 10
  timeoutSeconds: 5
managedServiceAccount: true
nameOverride: ""
nodeSelector: {}
podAnnotations: {}
podSecurityContext:
  privileged: false
  runAsUser: 0
priorityClassName: ""
readinessProbe:
  exec:
    command:
    - sh
    - -c
    - |
      #!/usr/bin/env bash -e
      filebeat test output
  failureThreshold: 3
  initialDelaySeconds: 10
  periodSeconds: 10
  timeoutSeconds: 5
replicas: 1
resources:
  limits:
    cpu: 1000m
    memory: 200Mi
  requests:
    cpu: 100m
    memory: 100Mi
secretMounts:
- name: elastic-certificate-pem
  path: /usr/share/filebeat/config/certs
  secretName: elastic-certificate-pem
serviceAccount: ""
serviceAccountAnnotations: {}
terminationGracePeriod: 30
tolerations: []
updateStrategy: RollingUpdate

HOOKS:
MANIFEST:
---
# Source: filebeat/templates/serviceaccount.yaml
apiVersion: v1
kind: ServiceAccount
metadata:
  name: filebeat-filebeat
  annotations:
  labels:
    app: "filebeat-filebeat"
    chart: "filebeat-7.10.2"
    heritage: "Helm"
    release: "filebeat"
---
# Source: filebeat/templates/configmap.yaml
apiVersion: v1
kind: ConfigMap
metadata:
  name: filebeat-filebeat-config
  labels:
    app: "filebeat-filebeat"
    chart: "filebeat-7.10.2"
    heritage: "Helm"
    release: "filebeat"
data:
  filebeat.yml: |
    filebeat.inputs:
    - type: container
      paths:
        - /var/log/containers/*.log
      processors:
      - add_kubernetes_metadata:
          host: ${NODE_NAME}
          matchers:
          - logs_path:
              logs_path: "/var/log/containers/"
      - drop_event:
          when:
            not:
              equals:
                kubernetes.namespace: "elastic"
    output.elasticsearch:
      # username: '${ELASTICSEARCH_USERNAME}'
      # password: '${ELASTICSEARCH_PASSWORD}'
      protocol: http
      hosts: ["elasticsearch-master:9200"]
      # ssl.certificate_authorities:
      #   - /usr/share/filebeat/config/certs/elastic-certificate.pem
---
# Source: filebeat/templates/clusterrole.yaml
apiVersion: rbac.authorization.k8s.io/v1
kind: ClusterRole
metadata:
  name: filebeat-filebeat-cluster-role
  labels:
    app: "filebeat-filebeat"
    chart: "filebeat-7.10.2"
    heritage: "Helm"
    release: "filebeat"
rules:
- apiGroups:
  - ""
  resources:
  - namespaces
  - nodes
  - pods
  verbs:
  - get
  - list
  - watch
---
# Source: filebeat/templates/clusterrolebinding.yaml
apiVersion: rbac.authorization.k8s.io/v1
kind: ClusterRoleBinding
metadata:
  name: filebeat-filebeat-cluster-role-binding
  labels:
    app: "filebeat-filebeat"
    chart: "filebeat-7.10.2"
    heritage: "Helm"
    release: "filebeat"
roleRef:
  kind: ClusterRole
  name: filebeat-filebeat-cluster-role
  apiGroup: rbac.authorization.k8s.io
subjects:
- kind: ServiceAccount
  name: filebeat-filebeat
  namespace: elastic
---
# Source: filebeat/templates/daemonset.yaml
apiVersion: apps/v1
kind: DaemonSet
metadata:
  name: filebeat-filebeat
  labels:
    app: "filebeat-filebeat"
    chart: "filebeat-7.10.2"
    heritage: "Helm"
    release: "filebeat"
spec:
  selector:
    matchLabels:
      app: "filebeat-filebeat"
      release: "filebeat"
  updateStrategy:
    type: RollingUpdate
  template:
    metadata:
      annotations:

        configChecksum: 063808c5f8066ddb0eaaabf6206998b2b6a33e5e4e25070853ab2e88a67b03b
      name: "filebeat-filebeat"
      labels:
        app: "filebeat-filebeat"
        chart: "filebeat-7.10.2"
        heritage: "Helm"
        release: "filebeat"
    spec:
      serviceAccountName: filebeat-filebeat
      terminationGracePeriodSeconds: 30
      volumes:
      - name: elastic-certificate-pem
        secret:
          secretName: elastic-certificate-pem
      - name: filebeat-config
        configMap:
          defaultMode: 0600
          name: filebeat-filebeat-config
      - name: data
        hostPath:
          path: /var/lib/filebeat-filebeat-elastic-data
          type: DirectoryOrCreate
      - name: varlibdockercontainers
        hostPath:
          path: /var/lib/docker/containers
      - name: varlog
        hostPath:
          path: /var/log
      - name: varrundockersock
        hostPath:
          path: /var/run/docker.sock
      containers:
      - name: "filebeat"
        image: "docker.elastic.co/beats/filebeat:7.10.2"
        imagePullPolicy: "IfNotPresent"
        args:
        - "-e"
        - "-E"
        - "http.enabled=true"
        livenessProbe:
          exec:
            command:
            - sh
            - -c
            - |
              #!/usr/bin/env bash -e
              curl --fail <IP_ADDRESS>:5066
          failureThreshold: 3
          initialDelaySeconds: 10
          periodSeconds: 10
          timeoutSeconds: 5
        readinessProbe:
          exec:
            command:
            - sh
            - -c
            - |
              #!/usr/bin/env bash -e
              filebeat test output
          failureThreshold: 3
          initialDelaySeconds: 10
          periodSeconds: 10
          timeoutSeconds: 5
        resources:
          limits:
            cpu: 1000m
            memory: 200Mi
          requests:
            cpu: 100m
            memory: 100Mi
        env:
        - name: POD_NAMESPACE
          valueFrom:
            fieldRef:
              fieldPath: metadata.namespace
        - name: NODE_NAME
          valueFrom:
            fieldRef:
              fieldPath: spec.nodeName
        - name: ELASTICSEARCH_USERNAME
          valueFrom:
            secretKeyRef:
              key: username
              name: elastic-credentials
        - name: ELASTICSEARCH_PASSWORD
          valueFrom:
            secretKeyRef:
              key: password
              name: elastic-credentials
        securityContext:
          privileged: false
          runAsUser: 0
        volumeMounts:
        - name: elastic-certificate-pem
          mountPath: /usr/share/filebeat/config/certs
        - name: filebeat-config
          mountPath: /usr/share/filebeat/filebeat.yml
          readOnly: true
          subPath: filebeat.yml
        - name: data
          mountPath: /usr/share/filebeat/data
        - name: varlibdockercontainers
          mountPath: /var/lib/docker/containers
          readOnly: true
        - name: varlog
          mountPath: /var/log
          readOnly: true
        # Necessary when using autodiscovery; avoid mounting it otherwise
        # See: https://www.elastic.co/guide/en/beats/filebeat/7.10/configuration-autodiscover.html
        - name: varrundockersock
          mountPath: /var/run/docker.sock
          readOnly: true

NOTES:
1. Watch all containers come up.
  $ kubectl get pods --namespace=elastic -l app=filebeat-filebeat -w

Describe the bug:
When trying to create an index pattern i get this:

(Request Timeout)
in kibana logs I get this (multiple times):
{"type":"response","@timestamp":"2021-01-15T09:58:05Z","tags":[],"pid":6,"method":"get","statusCode":200,"req":{"url":"/app/kibana","method":"get","headers":{"host":"localhost:5601","user-agent":"curl/7.61.1","accept":"*/*"}

Steps to reproduce:
install elasticsearch, filebeat and kibana with the provided values, do a port-forward, then create an index pattern in kibana.
Things I tried

with xpack enabled
with xpack disabled
with one replica of elasticsearch
with 2 replicas of elasticsearch
increased the elasticsearch.requestTimeout and elasticsearch.shardTimeout in kibana settings
increased the memory size for elasticsearch up to 2Gb (and '-Xmx1500m -Xms1500m')

Expected behavior:
That the index pattern is created.
Provide logs and/or server output (if relevant):
{"type":"response","@timestamp":"2021-01-15T09:58:05Z","tags":[],"pid":6,"method":"get","statusCode":200,"req":{"url":"/app/kibana","method":"get","headers":{"host":"localhost:5601","user-agent":"curl/7.61.1","accept":"*/*"}

Any additional context:
index status as shown from kibana:

Are you able to use elasticsearch with Kibana ? try with the dev-tool console first.

Are you able to use elasticsearch with Kibana ? try with the dev-tool console first.

I had to remove the charts to try out Elastic Cloud on Kubernetes(ECK),
but when i had the three charts installed (elasticsearch, kibana and filebeat) i could see the logs in the Logs UI view of kibana,
also, as shown in the screenshot, i can see indices

I had to remove the charts to try out Elastic Cloud on Kubernetes(ECK),
but when i had the three charts installed (elasticsearch, kibana and filebeat) i could see the logs in the Logs UI view of kibana,
also, as shown in the screenshot, i can see indices

That's weird, I couldn't reproduce it myself.


Acronym Style

What
When using acronyms, the acronym tag should be used. This provides a unique styling to it similar to a link
Why
Government services often use acronyms in their descriptions. We should avoid them when we can, but when they are used they should have proper tagging for screen readers and for users to see what the acronym is.
Anything else
Guidance should be included to try and avoid acronyms where possible

WCAG guidane https://www.w3.org/WAI/WCAG21/Understanding/abbreviations.html
H28: Providing definitions for abbreviations by using the abbr element
G102: Providing the expansion or explanation of an abbreviation for the first occurrence of the abbreviation in a Web page using one of the following techniques:


Fix generation date parameters using form data

Hey there!
When we create a multipart/form-data request and pass date parameters, they transform into the string using .toString() function, but you used .toJSON() transformation for dates in every part of this repository.
Controllers cannot parse format like this:

Thu Mar 28 2019 10:39:19 GMT+0200 (Eastern European Standard Time)

Therefore we must transform dates to ISO format.

LGTM. Thanks for the PR!


Windows build can fail

Issue https://github.com/mrtnetwork/flutter_windows_notification/issues/9 needs to be reopened.
I have it too on my Github action CI/CD (flutter 3.16.5) but not in my local Windows 11 setup.
Github action extract:
obs:
build:
runs-on: windows-latest
steps:
  - name: Check out Git repository
    uses: actions/checkout@v3

  - name: Flutter Action
    uses: subosito/flutter-action@v2

  - name: Dart Language
    uses: dart-lang/setup-dart@v1

  - name: Install dependencies
    run: flutter pub get

  - name: Build application
    run: flutter build windows --release -v

Error message:
Error: [        ]   D:\a\edamame\edamame\windows\flutter\ephemeral.plugin_symlinks\windows_notification\windows\windows_notification_plugin.cpp(275,32): error C2664: 'std::string winrt::to_string(std::wstring_view)': cannot convert argument 1 from 'winrt::com_ptr' to 'std::wstring_view' [D:\a\edamame\edamame\build\windows\x64\plugins\windows_notification\windows_notification_plugin.vcxproj]
[        ] "D:\a\edamame\edamame\build\windows\x64\INSTALL.vcxproj" (default target) (1) ->
[        ] "D:\a\edamame\edamame\build\windows\x64\ALL_BUILD.vcxproj" (default target) (3) ->
[        ] "D:\a\edamame\edamame\build\windows\x64\runner\edamame.vcxproj" (default target) (14) ->
[        ] "D:\a\edamame\edamame\build\windows\x64\plugins\windows_notification\windows_notification_plugin.vcxproj" (default target) (23) ->
[        ] (ClCompile target) ->
[        ]     2 Warning(s)
[        ]     1 Error(s)
[        ] Time Elapsed 00:14:25.44
[  +80 ms] Building Windows application... (completed in 886.5s)
[   +2 ms] "flutter windows" took 888,784ms.

I see that the https://github.com/mrtnetwork/flutter_windows_notification/pull/10 has a fix. The version on pub.dev needs to be updated.

I confirm the fix is working with Github CI/CD. Closing.


Move to github.com/fonttools org

@anthrotype can you prepare a CL for moving the CI integrations?  I think I also need to do some stuff manually to move coveralls, AppVeyor, etc?

sure.. but what's a "CL"? 😁

Obviously, a "CL" is "a Cosimo Lupo".

Hahaha.  My bad.  The github lingo is a "PR".  CL as in ChangeList; some other code-review systems use that.

Before we can move the CI, we need to create the the new repository
https://github.com/fonttools/fonttools.
You need to do this first:
https://help.github.com/articles/about-repository-transfers/

any news on moving the repo to https://github.com/fonttools/fonttools?

Yes I wanted to do this and get a release or begir atypi but was busy with opentype-gx branches.  Can we look into it on Tue night?

Done.  Please fix up any continuous-integration things it broke!

Both Travis and Appveyor CI are now hooked up to the new fonttools/fonttools repo.


[SPARK-13642][Yarn] Properly handle signal kill in ApplicationMaster

What changes were proposed in this pull request?
This patch is fixing the race condition in ApplicationMaster when receiving a signal. In the current implementation, if signal is received and with no any exception, this application will be finished with successful state in Yarn, and there's no another attempt. Actually the application is killed by signal in the runtime, so another attempt is expected.
This patch adds a signal handler to handle the signal things, if signal is received, marking this application finished with failure, rather than success.
How was this patch tested?
This patch is tested with following situations:

Application is finished normally.
Application is finished by calling System.exit(n).
Application is killed by yarn command.

ApplicationMaster is killed by NM with "SIGTERM" in case of NM failure.

All the scenarios return the expected states.
CC @tgravescs , please help to review this fix, thanks a lot.

Test build #52448 has started for PR 11512 at commit b461b71.

Test build #52448 has finished for PR 11512 at commit b461b71.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/52448/
Test PASSed.

So I think the problem with this is still that we don't know the real state of the application.  There is still a race condition here where the users application and sparkcontext could be succeeded (ie wrote output and was about to finish) but if we get a SIGTERM at the wrong point we mark it as failed rather then succeeded.
Normally if Spark was actually running anything the DAGScheduler would throw an exception. I think your use case here is the driver is sleeping and not running anything distributed so the scheduler doesn't throw, it just calls sc.stop().  I would rather explore having the scheduler throw if it has any jobs, including inactive ones or allowing the application master to know the state of the Spark jobs.

Thanks a lot for your comment @tgravescs , I think the scenario you mentioned though has race condition, it seldom happens, and currently we don't have solutions to handle that, since driver and AM are independent.
Yes, normally we should expect scheduler throw all the exceptions, but you cannot expect any user code will starting a job immediately after sc is created, or exception will definitely be thrown to AM, what if main  function catch all the exceptions?

So if they catch exceptions themselves we have to assume succeeded which is what we do now.  I just hate to add more logic and not really solve the underlying problem.  But unfortunately its really hard for us to know since its any arbitrary user code.  We can't just ask the scheduler if its done.
So I'm thinking about this some more and I'm wondering if we just don't change the behavior for 2.x to report failed by default.  The reason we do it this way is the SPARK code itself and examples used to System.exit().  We have removed those quite a few releases back now.  People shouldn't be calling System.exit and should just be calling sc.stop().   2.x gives us an opportunity to change that behavior.
@vanzin @pwendell  Do you guys have any concerns about this?
if we want to pull this into 1.6.x line I would be ok adding in the signal handler to fix this one issue.

The signal handler change looks fine to me; I agree with Saisai that the race would happen very rarely and shouldn't be a problem.
Regarding the change in behavior...

I'm wondering if we just don't change the behavior for 2.x to report failed by default

So this would only apply to applications that do System.exit explicitly, right? At this point in time I hope people have stopped doing that, so it should be fine. A quick grep in Spark code shows that System.exit seems to be used only for error cases, so the change would actually help with that (not that Spark should be calling System.exit itself, but that's a different problem).

Yes its only if they explicitly System.exit.  Or someone puts a System.exit back into Spark but that shouldn't happen except on failure.
ok @jerryshao  can you update pr for master to just be to change default behavior of shutdown hook assume failures.  Then a PR to 1.6 with this signal handler

Sure, thanks @tgravescs and @vanzin for your comments. I will close this create new PRs accordingly.

Reopen it and change the title.


MaryTTS doesn't work in official Docker image due to lack of Java

Using a "bin" script of:
#!/usr/bin/env bash
docker run \
  -i \
  -v "${HOME}:${HOME}" \
  -w "$(pwd)" \
  -e "HOME=${HOME}" \
  --user "$(id -u):$(id -g)" \
  'synesthesiam/voice2json' "$@"

and an appropriately-trained profile, I get the following result:
$ voice2json speak-sentence 'hello.'
[14] Failed to execute script __main__
Traceback (most recent call last):
  File "voice2json/__main__.py", line 1766, in <module>
  File "voice2json/__main__.py", line 353, in main
  File "voice2json/__main__.py", line 1596, in speak
  File "voice2json/__main__.py", line 1723, in speak_marytts
  File "voice2json/__main__.py", line 1666, in start_marytts
  File "subprocess.py", line 709, in __init__
  File "subprocess.py", line 1344, in _execute_child
FileNotFoundError: [Errno 2] No such file or directory: 'java': 'java'

The above command with the exact same profile works as expected if I use the following custom Dockerfile:
FROM ubuntu:bionic

RUN \
  apt-get update -y \
  && apt-get install -y \
    sox \
    jq \
    alsa-utils \
    espeak-ng \
    sphinxtrain \
    perl

COPY voice2json_1.0_amd64.deb /voice2json.deb

RUN apt install -y /voice2json.deb

ENTRYPOINT ["voice2json"]

It seems all that's missing is having a JRE installed in the official image, which seems to be installed by the .deb as one of its required dependencies.

Moved to an external MaryTTS Docker image: https://github.com/synesthesiam/docker-marytts


Constant definitions should be able to omit require paths

if (process.env.NODE_ENV === 'production')
  require('x')

Should not list 'x' as a dependency when process.env.NODE_ENV is not 'production'.

Fixed.


Add option to override route name

Currently it is not possible to create a named route without it inheriting the name of its parent group.
This PR adds an option to override the route name belonging to a group.
Ex:
Route::group([
    'prefix' => 'admin',
    'as' => 'admin.',
    ], function(){

    Route::get('not-override-route-name')
            ->name(name: 'not-override-name');
    # result name: admin.not-override-name

    Route::get('override-route-name')
        ->name(name: 'override-name',override: true);
    # result name: override-name
});

Thanks for your pull request to Laravel!
Unfortunately, I'm going to delay merging this code for now. To preserve our ability to adequately maintain the framework, we need to be very careful regarding the amount of code we include.
If possible, please consider releasing your code as a package so that the community can still take advantage of your contributions!
If you feel absolutely certain that this code corrects a bug in the framework, please "@" mention me in a follow-up comment with further explanation so that GitHub will send me a notification of your response.


BibsAndAttachedToSolr export not generating shelflist item manifests correctly

When running a BibsAndAttachedToSolr compound export process, the final_callback method on the exporter for each individual record type (including both bibs and items) runs after all chunks have been processed. When the shelflist.export.ItemsToSolr.final_callback method runs, it attempts to create shelflist item manifests and store them in Redis--i.e., for each location in the record set, it sorts all of the items in Solr at that location by normalized call number and assigns row numbers.
While working on a separate issue and running a BibsAndAttachedToSolr export process on a single bib record, I noticed that the relevant shelflist item manifest was not being generated: when I looked at the shelflist_item resources at the location that should have had the manifest created, the rowNumber field was null after running the export.
The Celery log did log a "Creating shelflist item manifests" message, which indicates that the shelflist.export.ItemsToSolr.final_callback method did run. And, running one of the item records at that location through the ItemsToSolr process did correctly generate the shelflist item manifest.
I suspect that the problem may be here. When run as an ItemsToSolr job by itself, exp.get_records() returns the set of item records that were just loaded, and pulling out the set of locations associated with those items gives you the correct set of locations to generate shelflist item manifests for. But, when run as part of a BibsAndAttachedToSolr job, I think exp.get_records() is probably returning the set of bib records associated with that job, which means the following lines aren't pulling out item location codes correctly.

I'd add, although I assigned this a "priority high" label, the affect this is having on our production data should be negligible. The BibsAndAttachedToSolr process does run once a night to sync bib records from Sierra, but the ItemsToSolr process runs by itself during the day every two hours and correctly regenerates shelflist manifests each time it runs.
It could theoretically cause a problem if the call number on a bib record were changed and neither the attached items nor any of the items at that location were updated the next day. In that case, the worst you'd have would be the items attached to that bib record would appear to be out of order in the shelflist (and therefore in the inventory app) until an item at that location were run through ItemsToSolr. As far as I know, we haven't yet run into that after 9 months of using the inventory app.

Fixed in PR #48.


Explicitly set the minimum supported rust version

Depends on gakonst/evm#1. Probably need to update the lockfile before merging.
Besides setting the Rust version:

Run the tests against 1.51 plus stable.
Run the tests against the whole workspace.
Run clippy against the whole workspace.
Fix a couple clippy warnings.
Add --from-utf8 and make --from-ascii an alias to it, since UTF-8 is more accurate.

Really nice work! Some nits about compatibility with upstream but lgtm once these are addressed.

Really nice work! Some nits about compatibility with upstream but lgtm once these are addressed. I merged the PR on the EVM, can you update the dep to that?

Can do!

Also, might be worth up streaming?

The evm crate changes? I can certainly try!


Arch diagram should be at pointing at the OCM repo

Signed-off-by: Mike Ng<EMAIL_ADDRESS>

/assign @dhaiducek
Thanks Dale.


Split repository into a library and CLI

This makes the big split of breaking up the repository into a workspace and making libsignify separate from the signify CLI tool. I took the approach of signify and libsignify for:

Most users probably only want the CLI and its functionality. cargo install signify is much nicer then cargo install signify-cli.
clap and rpassword aren't good dependencies to have in a regular library, which would be required if the CLI just became src/cli/main.rs in the signify crate.

I thought libsignify was the best name out of signify-lib and others. Please feel free to recommend anything better since it isn't perfect.
I attempted (and failed a few times) to design the library's API to be mostly dead-simple. It gets to the point of signify: it can sign and verify files and messages. There aren't any internal details exposed about the "scheme" itself, like comment headers, lengths, etc. Another goal of the design was friendliness towards eventually making it no_std compatible (and maybe no_alloc) for low-level consumers. For example: maybe an OS kernel or software updater. Slices are preferred most of the time and external reliance on std::io::{Read, Write} is removed. I think its use internally can be cleaned up later. However, even given this, the APIs around deserialization still provide hints to allow for consumers with std to make use of it in regards to memory efficiency.
@badboy if you get a chance, please take a look and see if this aligns with your ideals too.
Depends on #36
Part 2/2 of the bigger lib/CLI split.
I plan on following up with more docs, README updates, and general repo structure cleanup after this. I didn't do it here in the interest of keeping it easier to review. I dropped the crate's include = [...] sections until this is worked out for simplicity too.

I also changed the Makefile to require bash to run the test scripts. Execute bits on files in Git are shockingly fragile when Windows is involved.

WUHU!
I'm putting this on my list, hopefully for the weekend.
Thanks for the thorough explanation, overall I think that's a very good approach.

@badboy Many thanks for the review, I'll try to have the next set of PRs up soon.


Oliver daemon db

High-level comments: 1) Add a description about this PR; 2) Use a more appropriate subject; 3) Is it the "smallest" PR?


size mismatch for w2v_encoder while loading pretrained model(wav2vec2.0)

❓ Questions and Help
What is your question?
RuntimeError: Error(s) in loading state_dict for Wav2VecCtc:
size mismatch for w2v_encoder.proj.weight: copying a param with shape torch.Size([32, 768]) from checkpoint, the shape in current model is torch.Size([512, 768]).
size mismatch for w2v_encoder.proj.bias: copying a param with shape torch.Size([32]) from checkpoint, the shape in current model is torch.Size([512]).
Code
python train.py /data/home/v_liwenxu/data/LibriSpeech/train-pipeline/data/
--save-dir /data/home/v_liwenxu/data/LibriSpeech/train-pipeline/models/ --fp16
--post-process letter --valid-subset /data/home/v_liwenxu/data/LibriSpeech/train-pipeline/data/libris-train
--no-epoch-checkpoints --best-checkpoint-metric wer --num-workers 4
--max-update 80000 --sentence-avg --task audio_pretraining --arch wav2vec_ctc --w2v-path /data/home/v_liwenxu/data/LibriSpeech/train-pipeline/models/wav2vec_small_960h.pt
--labels ltr --apply-mask --mask-selection static --mask-other 0 --mask-length 10 --mask-prob 0.5 --layerdrop 0.1
--mask-channel-selection static --mask-channel-other 0 --mask-channel-length 64 --mask-channel-prob 0.5 --zero-infinity
--feature-grad-mult 0.0 --freeze-finetune-updates 10000 --validate-after-updates 10000 --optimizer adam
--adam-betas '(0.9, 0.98)' --adam-eps 1e-08 --lr 2e-05 --lr-scheduler tri_stage --warmup-steps 8000 --hold-steps 32000
--decay-steps 40000 --final-lr-scale 0.05 --final-dropout 0.0 --dropout 0.0 --activation-dropout 0.1 --criterion ctc
--attention-dropout 0.0 --max-tokens 1280000 --seed 2337 --log-format json --log-interval 500 --ddp-backend no_c10d
I am trying to fine-tune the pre-trained model in wav2vec2.0，wav2vec_small_960h.pt ，specifically. However, while I ran the above code, the following error emerged.:
Traceback (most recent call last):
File "/data/home/v_liwenxu/miniconda3/envs/mirex/lib/python3.6/site-packages/torch/multiprocessing/spawn.py", line 20, in _wrap
fn(i, *args)
File "/data1/home/v_liwenxu/fairseq/fairseq/distributed_utils.py", line 156, in distributed_main
main(args, **kwargs)
File "/data1/home/v_liwenxu/fairseq/fairseq_cli/train.py", line 67, in main
model = task.build_model(args)
File "/data1/home/v_liwenxu/fairseq/fairseq/tasks/fairseq_task.py", line 248, in build_model
model = models.build_model(args, self)
File "/data1/home/v_liwenxu/fairseq/fairseq/models/init.py", line 48, in build_model
return ARCH_MODEL_REGISTRY[args.arch].build_model(args, task)
File "/data1/home/v_liwenxu/fairseq/fairseq/models/wav2vec/wav2vec2_asr.py", line 168, in build_model
w2v_encoder = Wav2VecEncoder(args, task.target_dictionary)
File "/data1/home/v_liwenxu/fairseq/fairseq/models/wav2vec/wav2vec2_asr.py", line 345, in init
model.load_state_dict(state["model"], strict=True)
File "/data1/home/v_liwenxu/fairseq/fairseq/models/fairseq_model.py", line 93, in load_state_dict
return super().load_state_dict(new_state_dict, strict)
File "/data/home/v_liwenxu/miniconda3/envs/mirex/lib/python3.6/site-packages/torch/nn/modules/module.py", line 847, in load_state_dict
self.class.name, "\n\t".join(error_msgs)))
RuntimeError: Error(s) in loading state_dict for Wav2VecCtc:
size mismatch for w2v_encoder.proj.weight: copying a param with shape torch.Size([32, 768]) from checkpoint, the shape in current model is torch.Size([512, 768]).
size mismatch for w2v_encoder.proj.bias: copying a param with shape torch.Size([32]) from checkpoint, the shape in current model is torch.Size([512]).
I really have no idea how to fix this problem, could anyone help?

the model you are trying to finetune is itself a finetuned model. what you probably want is to download the model with "no finetuning", and finetune that instead. or if you want to continue training a model that has already been fine-tuned, then you can just use it as a checkpoint (--restore-file /path/to/model), and dont forget to set the various --reset-x flags as well

Did you manage to solve this problem? I tried to --restore-file and --reset and still get this error.....

actually i guess someone added a --finetune-from-model arg that resets all the relevant things, so maybe you can try using that (if you are finetuning a finetuned model)

Hello @alexeib ! I am trying to fine-tune an already fine-tuned wav2vec 2.0 base model (wav2vec 2.0 base model fine tuned on 100 hours of librispeech). However, I am trying to fine-tune it on a different language and therefore with a different dict.ltr.txt. So the dimensions of the final output layer would of course be different. I want that layer to be replaced with the new dimensions for my new letter targets, but I wish to fine-tune the layers before that by starting from the already fine-tuned model. Can this be done?
Also, I am facing the same error as above even with the --fine-tune-from-model arg and with the --restore-file arg.
RuntimeError: Error(s) in loading state_dict for Wav2VecCtc:
size mismatch for w2v_encoder.proj.weight: copying a param with shape torch.Size([32, 768]) from checkpoint, the shape in current model is torch.Size([512, 768]).
size mismatch for w2v_encoder.proj.bias: copying a param with shape torch.Size([32]) from checkpoint, the shape in current model is torch.Size([512]).
Please help me solve these two problems.

i would suggest finetuning the pretrained ("no finetuning") model instead of one that has been already finetuned for english.
however to do what you are trying to do, you can just modify the code in wav2vec2_asr.py to load the weights in non-strict mode - either modify or create an alternative to load_checkpoint_to_cpu where torch.load is called with strict=False flag. for example you can add "strict" argument to load_checkpoint_to_cpu defaulted to True and change this:
    with PathManager.open(path, "rb") as f:
        state = torch.load(
            f, map_location=lambda s, l: default_restore_location(s, "cpu"), strict=False
        )

Hello @alexeib ! I am trying to fine-tune an already fine-tuned wav2vec 2.0 base model (wav2vec 2.0 base model fine tuned on 100 hours of librispeech). However, I am trying to fine-tune it on a different language and therefore with a different dict.ltr.txt. So the dimensions of the final output layer would of course be different. I want that layer to be replaced with the new dimensions for my new letter targets, but I wish to fine-tune the layers before that by starting from the already fine-tuned model. Can this be done?
Also, I am facing the same error as above even with the --fine-tune-from-model arg and with the --restore-file arg.
RuntimeError: Error(s) in loading state_dict for Wav2VecCtc:
size mismatch for w2v_encoder.proj.weight: copying a param with shape torch.Size([32, 768]) from checkpoint, the shape in current model is torch.Size([512, 768]).
size mismatch for w2v_encoder.proj.bias: copying a param with shape torch.Size([32]) from checkpoint, the shape in current model is torch.Size([512]).
Please help me solve these two problems.

@tarang-jain have you solved this issue.


✨ Add support for Pydantic v2 (while keeping support for v1 if v2 is not available), including initial work by AntonDeMeester

✨ Add support for Pydantic v2 (while keeping support for v1 if v2 is not available)
This includes the commits in the initial work by @AntonDeMeester in https://github.com/tiangolo/sqlmodel/pull/699

I reverted some things, refactored some parts, fixed some hidden bugs.
Restructured the logic in compat.
Updated the methods to be available in both Pydantic v1 and v2.
Deprecated old methods (from_orm(), etc), adding deprecation markers (they show up in editors), and refactoring the code to use the new ones.
Update the docs to use .model_validate() instead of .from_orm() and .parse_obj().
Re-implemented several internal parts to support data updates in .model_validate() and keep compatibility with Pydantic v2 and v1, whichever is installed.
Implemented the necessary logic to allow keeping values without defaults without them.
Implemented the logic to support SQLAlchemy's custom init overriding while keeping support for non-SQLAlchemy models.
Updated all the necessary tests to be compatible with both Pydantic v2 and v1, minimizing the cases where its needed to have separate tests.

Oh sweet!!

Really amazing news, thanks for all the work that went into this!


Unexpected error when visiting "Recurring financial contributions"

Describe the bug

I got an unexpected error on https://opencollective.com/sloria/subscriptions while I was trying to view my subscriptions.
To Reproduce

Go to https://opencollective.com//subscriptions

Device

OS: macOS Mojave
Browser: Firefox 67.0

@sloria thank you for reporting. there is something specific to your account that is triggering the error, we're looking into it.

OK, no rush on this on my end. Let me know if I can help diagnose.

Seems a collective you pledged to was deleted (pytest). This is an unexpected case. If that's right, I can delete the pledge.
They joined the platform with a different account: http://opencollective.com/pytest

Yes, go ahead and delete the pledge.

Done!


Exporting files needed to execute zkevm-prover from starky.

This PR is on hold while starky people investigates why the consttree.bin exported from starky is different from JS pil-stark.

@lvella is this still not working from the starky side?


Internal connection pooling does not work with Read-Write Splitting Plugin when cluster url is used

Describe the bug
Internal connection pooling does not work with Read-Write Splitting Plugin when cluster url is used.
Expected Behavior

Perform internal connection pooling also when aurora cluster url is used in the jdbc url.
Cluster topology is discovered by the driver and connections are opened to the available reader and writer instances.
Read and write connection are kept in dedicated connection pools

What plugins are used? What other connection properties were set?
readWriteSplitting
Current Behavior
Application startup logs when cluster url is used
Redacted url: jdbc:aws-wrapper:postgresql://us-dev-pg-cluster.cluster-xxxxxxxxxx.us-east-1.rds.amazonaws.com/xxxxxxx
15:47:41.386 [main] INFO  o.h.validator.internal.util.Version - HV000001: Hibernate Validator 6.1.7.Final - {}
15:47:41.798 [main] INFO  o.h.jpa.internal.util.LogHelper - HHH000204: Processing PersistenceUnitInfo [name: default] - {}
15:47:41.854 [main] INFO  org.hibernate.Version - HHH000412: Hibernate ORM core version 5.4.33 - {}
15:47:42.009 [main] INFO  o.h.annotations.common.Version - HCANN000001: Hibernate Commons Annotations {5.1.2.Final} - {}
15:47:44.556 [main] INFO  org.hibernate.dialect.Dialect - HHH000400: Using dialect: infra.db.boundary.CustomPostgresqlDialect - {}
15:47:46.687 [main] WARN  org.hibernate.cfg.AnnotationBinder - HHH000491: The [createdBy] association in the [features.commerceorders.entity.Status] entity uses both @NotFound(action = NotFoundAction.IGNORE) and FetchType.LAZY. The NotFoundAction.IGNORE @ManyToOne and @OneToOne associations are always fetched eagerly. - {}
15:47:48.782 [main] INFO  o.h.e.t.j.p.i.JtaPlatformInitiator - HHH000490: Using JtaPlatform implementation: [org.hibernate.engine.transaction.jta.platform.internal.NoJtaPlatform] - {}
15:47:48.786 [main] INFO  o.s.o.j.LocalContainerEntityManagerFactoryBean - Initialized JPA EntityManagerFactory for persistence unit 'default' - {}

Application startup logs when instance url is used
Redacted url: jdbc:aws-wrapper:postgresql://backenddevusstoragestack-databas-auroradbinstance1-jjaw8nsn0cul.xxxxxxxxxx.us-east-1.rds.amazonaws.com/xxxxxxxx
15:50:45.312 [main] INFO  o.h.validator.internal.util.Version - HV000001: Hibernate Validator 6.1.7.Final - {}
15:50:45.716 [main] INFO  o.h.jpa.internal.util.LogHelper - HHH000204: Processing PersistenceUnitInfo [name: default] - {}
15:50:45.758 [main] INFO  org.hibernate.Version - HHH000412: Hibernate ORM core version 5.4.33 - {}
15:50:45.878 [main] INFO  o.h.annotations.common.Version - HCANN000001: Hibernate Commons Annotations {5.1.2.Final} - {}
15:50:46.100 [main] INFO  com.zaxxer.hikari.HikariDataSource - HikariPool-1 - Starting... - {}
15:50:47.938 [main] INFO  com.zaxxer.hikari.HikariDataSource - HikariPool-1 - Start completed. - {}
15:50:48.768 [main] INFO  org.hibernate.dialect.Dialect - HHH000400: Using dialect: infra.db.boundary.CustomPostgresqlDialect - {}
15:50:51.060 [main] WARN  org.hibernate.cfg.AnnotationBinder - HHH000491: The [createdBy] association in the [features.commerceorders.entity.Status] entity uses both @NotFound(action = NotFoundAction.IGNORE) and FetchType.LAZY. The NotFoundAction.IGNORE @ManyToOne and @OneToOne associations are always fetched eagerly. - {}
15:50:53.565 [main] INFO  o.h.e.t.j.p.i.JtaPlatformInitiator - HHH000490: Using JtaPlatform implementation: [org.hibernate.engine.transaction.jta.platform.internal.NoJtaPlatform] - {}
15:50:53.573 [main] INFO  o.s.o.j.LocalContainerEntityManagerFactoryBean - Initialized JPA EntityManagerFactory for persistence unit 'default' - {}

Reproduction Steps

Use cluster url in the connection string
Set plugins to either auroraHostList,readWriteSplitting or readWriteSplitting,failover,efm
Startup the application

Possible Solution
HikariPooledConnectionProvider works only for urls of type RdsUrlType.RDS_INSTANCE, but RDS_WRITER_CLUSTER url is supplied by the wrapper.
Additional Information/Context
The behavior is identical no matter what set of plugins I use, be it readWriteSplitting,failover,efm or auroraHostList,readWriteSplitting
The AWS Advanced JDBC Driver version used
2.1.2
JDK version used
17.0.7
Operating System and version
Linux pop-os 6.2.6-76060206-generic #202303130630~1683753207~22.04~77c1465 SMP PREEMPT_DYNAMIC Wed M x86_64 x86_64 x86_64 GNU/Linux

Hi @firebike,
Thanks for reaching out and raising this issue.
We'll take a look at this and keep you updated as we investigate.
Thank you for your patience!

Hi @firebike, thanks for reaching out. With the current code we intentionally avoid creating a connection pool for cluster URLs. This is because it may be problematic to create a pool for a URL that can resolve to different instances over time. Currently, the main benefit of internal pools is when setReadOnly is called. When setReadOnly is called (regardless of the initial connection URL), an internal pool will be created for the writer/reader that the plugin switches to and connections for that instance can be reused in the future. In general, initial connections won't be pooled unless the user supplies an instance URL.

@congoamz What is the preferred configuration for this setup as in regards to the urls etc. We have a 2 nodes setup with one reader and one writer.

@congoamz Thank you for this explanation. My incorrect understanding was that I can now fully delegate connection pool management to the aws-wrapper driver. However, as it is not the case, I still have to maintain the connection pool in the application. The good thing is that I can now keep a singe pool for both reader and writer connections and ditch custom routing datasource from the codebase.
After reworking the setup I can confirm that:

The application connection pool creates WRITER connections using writer cluster url that I've provided in the JDBC Url.  :+1:
The aws-wrapper creates READER connections using discovered reader instance url :+1:
The READER connections are pooled :+1:

I'm gonna test failover switching next.

@congoamz What is the preferred configuration for this setup as in regards to the urls etc. We have a 2 nodes setup with one reader and one writer.

Hi @datenbrille, I suggest you use the cluster URLs because they track the roles (writer or reader) of the instances after failover events (which can cause instance roles to change). If the connection you are requesting will only be performing reads you can use the reader cluster URL, otherwise you can use the writer cluster URL. You can also call setReadOnly on the connection object to switch to an instance with a different role later on. Note that the initial connection will not be pooled when you use cluster URLs. However, when setReadOnly is called, an internal pool will be created for the writer/reader that the plugin switches to and connections for that instance can be reused by future setReadOnly calls.

I can confirm that the failover switch worked flawlessly. The connections were re-established in seconds. :+1:


Enhancement: Support OPA/Rego on the verified provenance?

Possibility, seems to be an ask from a variety of users

I'm in favor of doing this too

closing this in favor of https://github.com/slsa-framework/slsa-verifier/issues/31, since it contains some links


Naming Conflict in Generated Query File for AuthResetGroup Schema

[x] The issue is present in the latest release.
[x] I have searched the issues of this repository and believe that this is not a duplicate.

Current Behavior 😯
When generating code for a schema named AuthResetGroup, a naming conflict occurs in the generated authresetgroup_query.go file. The variable name args conflicts with a function parameter, causing a compilation error:
Expected Behavior 🤔
The generated code should not have naming conflicts and should compile without errors. Variable names should be unique and not conflict with function parameters or other variables.
Steps to Reproduce 🕹
Steps:

Define a schema named AuthResetGroup.
Generate the code using the Ent framework.
Observe the generated authresetgroup_query.go file for naming conflicts involving the args variable.

Your Environment 🌎

Tech
Version

Go
1.21.6

Ent
0.13.1

Database
MySQL

Driver
https://github.com/go-sql-driver/mysql v1.8.0

I had something similar and even more obvious.  I wanted to create a new ent schema called Schema which generated code but was horribly broken and even overwrote my schema/schema.go file with generate code.


safety node initial commit

The safety node subscribes to /scan topic and publishes 0 geometry_msgs::cmd_vel over the topic cmd_vel_mux/safety if any of the range elements are less than the distance_threshold. The distance_threshold is a parameter has a default value of 2.5 meters and can be changed.
For integration, the cmd_vel_mux shall subscribe to the cmd_vel_mux/safety topic and forward data whenever cmd_vel_mux/safety publishes, overriding the data from move_base, not overriding the data from manual twist input.

Had to change interface from sensor_msgs::LaserScan to sensor_msgs::Range


Allow setting canceller for token swap

Allow a DAO to delegate the ability to withdraw from a token swap to an address. This address withdrawing would cause the funds to be returned to the DAO.

@Art3miX working on this !

@0xekez I wonder, can this wallet also fund the swap?
reason why I ask is because I modified get_counterparty function, and as a byproduct the address can do anything the party address (the dao) can do, which is fund and withdraw.
I don't really see harm in doing it now, but to avoid confusing for future improvements and features, we either:

Call the field "delegate_rights" or something similar, to make it obvious the address will be able to talk in your behalf
Or call it "allow_withdraw", and strictly allow this address only withdraw funds.

My guess is the 2nd one, but want to confirm before making the PR.


Add camel entity and animations

The camel will be an important aspect of the survival experience and is part of the logo; so it would be good to implement for the MMD Jam so as to not mislead/disappoint.

As you probably know, Codetaylor has finished the commission and has sent a PR.
There are still a few things that need to be done before this issue can be closed.
First I need to know wherever the camel has the same number of health points (hearts) as the lama which it is based off. This will allow me to add that info to the wiki.
Next you will need give the camel an equipment interface the same as the llama's; and add in the functionality to access it (see https://github.com/yooksi/Odyssey/wiki/Camel for more info).
Additionally, the general inventory should be completely unlocked from the start; when with the llama that requires you to place chests on either side first.
What this video for context:
https://www.youtube.com/watch?v=rMd2Upb-jE8

I will be making the model/texture for the camels carpet/saddle & storage over the weekend and will post a link to the file downloads here.

The camel moves around annoyingly when sitting, I think it would be best to disable its horizontal rotational movement when it is sitting.


add build check to pull latest content

This should resolve #21 by ensuring the source content is pulled and updated with the latest content from master before building.
/assign @castrojo

/lgtm
/approve


Blades in the Dark v1.8

Question: do I need to update all translations like this for the future, or only the translation.json?

You just need to make changes to translation.json, the other language files will be updated automatically. Thanks!


Drop support for py3.3, which is EOL

Python 3.3 has reached end of life (since 2017-09-29).
See:

Python 3.3.0 Release | Python.org
Python Insider: Python 3.3.7rc1 is now available prior to Python 3.3.x end-of-life

@dolang 👍


Study list at /eda route needs key prop

Warning: Each child in a list should have a unique "key" prop.

Check the render method of `StudyList`. See https://reactjs.org/link/warning-keys for more information.
li
StudyList@https://localhost:3000/static/js/main.chunk.js:22325:73
Route@https://localhost:3000/static/js/4.chunk.js:224379:29
Switch@https://localhost:3000/static/js/4.chunk.js:224581:29
WorkspaceRouter@https://localhost:3000/static/js/main.chunk.js:23241:25
component

Is this as simple as

        {studies.value.map((study) => {
          const dataset = datasets.records.find(
            (r) => r.attributes.dataset_id === study.datasetId
          );
          return (

  // <<<<<<<<<<<<<<<<<<<<<<<
              <Link to={`${url}/${study.datasetId}`}>
                {dataset ? safeHtml(dataset.displayName) : study.id}
              </Link>

          );
        })}

?

 doesn't have a key attribute, but JSX HTML elements are all wrapped in React magic?

Yes that does work - will add as a separate PR in a minute.


Add missing text for db handler registrations

tests did not detect typo in "db "
  if (config.processEventsAfterPublish) {
    cds.on("connect", (service) => {
      if (service.name === "db ") {
        dbHandler.registerEventQueueDbHandler(service);
      }
    });
  }

problem is runners are attached and picked up the work
make sure events are processed by db handler
add dedicated test that db handler is being registered


Clean up all the ops backwards compatibility code

Once ops 2.17 is released it would be good to get rid of all the compatibility code, and probably also there should be CI and/or tox checks that make sure that the compatibility with ops versions doesn't break.

Opened a PR in the operator repo.


Provide a usage function on RuntimeJob so metrics don't have to be parsed

What is the expected feature or enhancement?
The RuntimeJob.metrics() method does not document what is in that metrics dictionary.
For the quantum channel the API docs are here. For the cloud channel the API docs are here.
There are 3 different fields in there that talk about usage:

It'd be nice if the client didn't have to know which of these to use to get the usage of a terminal-state job and instead a usage() method or something like that could abstract that information in the SDK.
This is sort of similar to how Session.details() has the usage_time field, but at least that's documented.
Acceptance criteria
Provide a method on RuntimeJob to get the usage time of a job.

We should do the same for Session + Batch. We'll need to update docs once that's done.

We should do the same for Session + Batch. We'll need to update docs once that's done.

Added an issue to update the docs once this is in the newest release https://github.com/Qiskit/documentation/issues/1971


Expense - "Unapprove" option is available in report with deleted expense that has comments

If you haven’t already, check out our contributing guidelines for onboarding and email<EMAIL_ADDRESS>to request to join our Slack channel!

Version Number: 9.0.5-4
Reproducible in staging?: Y
Reproducible in production?: N
If this was caught during regression testing, add the test name, ID and link from TestRail: N/A
Issue reported by: Applause - Internal Team
Action Performed:

Go to staging.new.expensify.com
[User A] Submit two expenses to User B
[User A] Go to transaction thread of one of the expenses, and add some comments
[User A] Delete the expense that has comments
[User B] Go to DM with User A
{User B] Click on the expense preview
[User B] Pay the report
[User B] Go to the report that has comments (expense deleted)
[User B] Click on the report header

Expected Result:
"Unapprove" option should not appear since the expense is deleted, only comments are left in the report
Actual Result:
"Unapprove" options shows up even though the expense is deleted
Workaround:
Unknown
Platforms:

Which of our officially supported platforms is this issue occurring on?

[x] Android: Native
[x] Android: mWeb Chrome
[x] iOS: Native
[x] iOS: mWeb Safari
[x] MacOS: Chrome / Safari
[x] MacOS: Desktop

Screenshots/Videos
Add any screenshot/video evidence

https://github.com/Expensify/App/assets/78819774/2e55eb7b-9be4-46a6-94c3-4a5c46cc777e
View all open jobs on GitHub

@blimpich   FYI I haven't added the External label as I wasn't 100% sure about this issue. Please take a look and add the label if you agree it's a bug and can be handled by external contributors

We think that this bug might be related to #wave-collect - Release 1

Looking into this

Think I know what caused this, testing locally.

Having trouble repro-ing locally.

Was able to repro and confirm it stems from this PR

Demoting because this is edge case.

@Beamanator @rushatgabhane assigned both of you as this is follow up for this PR you worked on recently.

cool cool we have to check for deleted report here
https://github.com/Expensify/App/pull/44229/files#diff-409b0e2fb439856e9897b808014031ce244a427d116ed30f37a2e0117599adc4R202

@rushatgabhane I don't think we should be showing Unapprove at the expense level to begin with.

Fix merged & CPing

This should be fixed already


NoMethodError inconsistent on attributes

f = Foo.new
f.bar

Throws NoMethodError
but...
Foo.new bar: 'bar'
f = Foo.new
f.bar

Returns nil

agree it is a bit surprising. is this something you stumbled across or was this at the root cause of an issue you were troubleshooting?

It was an issue when testing. It could have been a problem in production though. Basically we were assuming the method would work because in test data it was.

Gonna close due to inactivity. Feel free to reopen if this is still an issue.


README documentation on scalapb_proto_library is outdated

README documentation on scalapb_proto_library lists a number of arguments which were moved to scala_proto_toolchain in #700.
The documentation suggest one should do the following to include gRPC:
scalapb_proto_library(
    name='ping_scala',
    deps=[':ping'],
    with_grpc = True,
)

Which will result in an error as with_grpc argument is unexpected for scalapb_proto_library. Instead you must overwrite the toolchain in your BUILD file:
load("@io_bazel_rules_scala//scala_proto:scala_proto_toolchain.bzl", "scala_proto_toolchain")

scala_proto_toolchain(
    name = "scala_proto_toolchain_configuration",
    with_grpc = False,
)

toolchain(
    name = "scalapb_toolchain",
    toolchain = ":scala_proto_toolchain_configuration",
    toolchain_type = "@io_bazel_rules_scala//scala_proto:toolchain_type",
    visibility = ["//visibility:public"],
)

AFAIK this change is not documented anywhere.

yes that's right. A PR to improve the documentation would be welcomed!


make stdio configurable

This PR adds options to uvwasi_init() to allow setting the stdio file descriptors. This will allow embedders like Node.js to run multiple WASI applications in the same process without sharing stdio.
Unfortunately, Windows doesn't seem to like the use of the names stdin, stdout, and stderr as struct members, which is why I went with in, out, and err.

Tested these changes in the Node test suite (on macOS) and everything seems fine. Thanks for the review Anna.


Keyboard shortcuts don't scroll view as far as necessary

Type: Bug
I have been using VS Code for ~4 years, and I like it overall. But there is an annoying bug that I've started noticing in the last 1-2 weeks.
If I try to go to the top of the file I have open by pressing command+up, it scrolls up, but not all the way. It seems like the cursor moves to the top of the file, but I can't actually see it unless I scroll up some more using my trackpad.
Similar things happen if I try to go to the bottom of the file using command+down, or if I try to search for text using command+G.
VS Code version: Code 1.75.1 (Universal) (441438abd1ac652551dbe4d408dfcec8a499b8bf, 2023-02-08T21:34:59.000Z)
OS version: Darwin x64 20.6.0
Modes:
Sandboxed: No

System Info

Item
Value

CPUs
Intel(R) Core(TM) i7-9750H CPU @ 2.60GHz (12 x 2600)

GPU Status
2d_canvas: enabledcanvas_oop_rasterization: disabled_offdirect_rendering_display_compositor: disabled_off_okgpu_compositing: enabledmetal: disabled_offmultiple_raster_threads: enabled_onopengl: enabled_onrasterization: enabledraw_draw: disabled_off_okskia_renderer: enabled_onvideo_decode: enabledvideo_encode: enabledvulkan: disabled_offwebgl: enabledwebgl2: enabledwebgpu: disabled_off

Load (avg)
5, 4, 4

Memory (System)
16.00GB (0.18GB free)

Process Argv
--crash-reporter-id 8546bdc4-919c-427c-bd8c-2a7b47b5943e

Screen Reader
no

VM
0%

Extensions (21)

Extension
Author (truncated)
Version

Nix
bbe
1.0.1

gitlens
eam
13.2.0

prettier-vscode
esb
9.10.4

pyformat
giy
1.0.2

vscode-graphql
Gra
0.8.5

vscode-graphql-execution
Gra
0.1.7

vscode-graphql-syntax
Gra
1.0.6

vscode-docker
ms-
1.23.3

isort
ms-
2022.8.0

python
ms-
2023.2.0

vscode-pylance
ms-
2023.2.30

jupyter
ms-
2023.1.2010391206

jupyter-keymap
ms-
1.0.0

jupyter-renderers
ms-
1.0.14

vscode-jupyter-cell-tags
ms-
0.1.6

vscode-jupyter-slideshow
ms-
0.1.5

color-highlight
nau
2.5.0

fish-vscode
sky
0.2.1

language-stylus
sys
1.16.0

jest-snapshot-language-support
tle
1.1.1

selectline-statusbar
tom
0.0.2

A/B Experiments
vsliv368:30146709
vsreu685:30147344
python383cf:30185419
vspor879:30202332
vspor708:30202333
vspor363:30204092
vslsvsres303:30308271
pythonvspyl392:30443607
vserr242cf:30382550
pythontb:30283811
vsjup518:30340749
pythonptprofiler:30281270
vshan820:30294714
vstes263cf:30335440
vscoreces:30445986
pythondataviewer:30285071
vscod805:30301674
binariesv615:30325510
bridge0708:30335490
bridge0723:30353136
cmake_vspar411:30581797
vsaa593cf:30376535
pythonvs932:30410667
cppdebug:30492333
vsclangdf:30486550
c4g48928:30535728
dsvsc012:30540252
azure-dev_surveyone:30548225
pyindex848:30662994
nodejswelcome1cf:30587006
3biah626:30602489
pyind779cf:30662993
89544117:30613380
pythonsymbol12cf:30657549

I've been noticing this too, especially when jumping to a particular line, or instances of a string found using Command-F.
But I can't get a consistent repro: sometimes it scrolls the desired line into view, sometimes it doesn't.

Found related issue https://github.com/microsoft/vscode/issues/173487; I did have editor.smoothScrolling enabled. Disabling that setting to see if it helps.

I disabled smooth scrolling, and this no longer happens. That is a good enough workaround for me. Thanks @drbr.

Let's continue tracking in #173487. @elias6 I am not able to reproduce this on a vanilla vscode with only the smooth scrolling setting turned on. I would love to find out if this reproduces for you after disabling extensions.


Getting this Error using the Instructions in the Readme

There is no column with name 'category_id' on table 'forum_categories'

Laravel will implicitly put any commands that add new or modify existing columns at the very beginning of the commands array when the migration is executed

Are there tests for these migrations?

Unfortunately no, but it's a simple fix at least. Thanks for the heads up.
Fix is in 361115b591e0dd896e57a7c644f5a66cb08ebbe1


Add maintainers page to main meu

Actual Behaviour
There is no maintainers menu item
Expected Behaviour
Add maintainers page to the main menu.
It should look like this.

Would you like to work on the issue?
anyone can get

Claiming


jira create hangs after prompting in powershell/cmd (works via bash)

To be clear doesnt appear windows platform per se, as using bash via windows works fine.
Commands like "jira search", etc, work fine via powershell or cmd.exe

Invoke "jira create"
jira prompts for "? Project: "
Accept default choice, press Enter
ACTUAL
---> appears to "hang", any keyboard input appears ignored.
---> ctrl+break will lead to "terminate batch job (y/n)"
EXPECTED
---> accepts value and leads to next prompt

Interestingly... when I first attempted and ran "jira" and it began initial config it led me through all the prompts and only hung after the very last one.  Pressing ctrl+break aborted it, but the "~/.jira-cli.json" had been successfully created.  This seems relevant in case it's a more generic issue with the "prompt the user"

Hello @feelingsofwhite, sorry for the late reply (I've been busy), that seems to be a problem with interactive mode lib, I'll check if it's related specifically with our options

I think this issue is already solved with the last update, can you please check with v1.2.1? thanks :)

Let me know if you're still having this issue so I'll re-open it


Update deprecated actions

CI was complaining:

The following actions uses Node.js version which is deprecated and will be forced to run on node20: actions/checkout@v3, actions/setup-python@v4. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/

Rebase of https://github.com/astral-sh/packse/pull/210


extract nhk world's new stream provider

IMPORTANT: PRs without the template will be CLOSED
Description of your pull request and other information

friendship ended with piksel
now stream.co.jp is my best friend
- nhk, probably
I think it would be a good idea to cache the api url/token - they probably don't change at all
but grub4k said don't do that kind of thing in yt-dlp proper in the discord, so i won't
Fixes #8242
Template

Before submitting a pull request make sure you have:

[x] At least skimmed through contributing guidelines including yt-dlp coding conventions
[x] Searched the bugtracker for similar pull requests
[x] Checked the code with flake8 and ran relevant tests

In order to be accepted and merged into yt-dlp each piece of code must be in public domain or released under Unlicense. Check all of the following options that apply:

[x] I am the original author of this code and I am willing to release it under Unlicense
[ ] I am not the original author of this code but it is in public domain or released under Unlicense (provide reliable evidence)

What is the purpose of your pull request?

[x] Fix or improvement to an extractor (Make sure to add/update tests)
[ ] New extractor (Piracy websites will not be accepted)
[ ] Core bug fix/improvement
[ ] New feature (It is strongly recommended to open an issue first)

Copilot Summary

🤖 Generated by Copilot at 932e0a0
Summary
🇯🇵📺🛠

Improve NHK video extraction by using a new method to get and parse stream data. Fix Piksel extractor issue.

Piksel extractor
fails for some NHK videos
new method works well

Walkthrough

Add a method to extract stream API url and token from JavaScript file (_get_vod_api, link)
Use the new method to download and parse stream information as JSON (_extract_episode_info, link)
Extract formats and subtitles from stream URLs using existing method (_extract_m3u8_formats_and_subtitles, link)
Replace the use of Piksel extractor with the new approach (_extract_episode_info, link)

IIRC videos from this site expire rather quickly, but can we extract old pre-9/26 videos from both piksel and the new API endpoint?

the piksel APIs are gone apparently

cc @chrominance


Write a Swift program to convert miles to inches

Description
Write a Swift program to convert miles to inches
1 mile = 63360 inches
Input  : 5
Output : 316800

How to contribute

Save the solution in program/ConvertMilesToInches.swift file
Add ConvertMilesToInches.swift file in convert-miles-to-inches folder

!assign


Add metadata support

@dgoerlich I would also benefit from having this
Could we please get this in?


Introduce per-object profiling in queue agent

This PR revamps lib/alert_manager to facilitate alert aggregation across several logical components and adds multiple features related to queue agent introspection, including:

New metrics for reporting the number of rows/chunks/tables exported into static tables.
Per-object alerts are now collected for queues, exposing trim/static export errors to Cypress.
Per-object alerts are reported via gauges in profiling.

Shipped!


Update Site settings “info”

Automatically generated by Netlify CMS

👷 Deploy Preview for heuristic-hodgkin-5f2ff7 processing.
🔨 Explore the source changes: f34f9ef868f76b39d3f837cf18f88acd0f999a09
🔍 Inspect the deploy log: https://app.netlify.com/sites/heuristic-hodgkin-5f2ff7/deploys/61d5018efa5dd50007902192