Vault broken when all nodes went offline like in case of power failure

Preflight Checklist

[X] I have searched the issue tracker for an issue that matches the one I want to file, without success.
[X] I am not looking for support or already pursued the available support channels without success.
[X] I agree to follow the Code of Conduct.

Operator Version
1.22.1
Installation Type
Official Helm chart
Bank-Vaults Version
No response
Kubernetes Version
1.28
Kubernetes Distribution/Provisioner
OKD
Expected Behavior
Vault should come back online successfull
Actual Behavior
Vault is broken and stays broken
Steps To Reproduce

Provision a Vault with provided config
Turn off all kubernetes compute nodes (Simulate a power failure)
Turn nodes back on
Vault broken

Configuration
apiVersion: vault.banzaicloud.com/v1alpha1
kind: Vault
metadata:
  name: vault
  namespace: openshift-bank-vault
  labels:
    app.kubernetes.io/name: vault
    vault_cr: vault
spec:
  existingTlsSecretName: selfsigned-cert-vault-tls
  veleroEnabled: false
  size: 3
  serviceMonitorEnabled: true
  unsealConfig:
    kubernetes:
      secretNamespace: openshift-bank-vault
  externalConfig:
    policies:
      - name: allow_secrets
        rules: path "secret/*" { capabilities = ["create", "read", "update", "delete", "list"] }
          path "auth/token/create" { capabilities = [ "update" ] }
    auth:
      - type: kubernetes
        roles:
          # Allow every pod in the default namespace to use the secret kv store
          - name: default
            bound_service_account_names:
            - default
            - vault-mutating-webhook-vault-secrets-webhook
            - vault
            bound_service_account_namespaces:
              - "*"
            policies:
              - allow_secrets
            ttl: 1h
          - name: secretsmutation
            bound_service_account_names:
              - vault-mutating-webhook-vault-secrets-webhook
              - default
            bound_service_account_namespaces:
              - openshift-bank-vault
            policies:
              - allow_secrets
            ttl: 1h
    secrets:
      - path: secret
        type: kv
        description: General secrets.
        options:
          version: 2
    # Allows writing some secrets to Vault (useful for development purposes).
    # See https://www.vaultproject.io/docs/secrets/kv/index.html for more information.
    startupSecrets:
      - type: kv
        path: secret/data/example/account
        data:
          data:
            USER: secretId
            PASS: s3cr3t
  ingress:
    annotations:
      #nginx.ingress.kubernetes.io/backend-protocol: HTTPS
      route.openshift.io/termination: reencrypt
      route.openshift.io/destination-ca-certificate-secret: selfsigned-cert-vault-tls
    spec:
      ingressClassName: openshift-default
      rules:
      - host: secrets.example.com
        http:
          paths:
          - backend:
              service:
                name: vault
                port:
                  number: 8200
            path: /
            pathType: Prefix
  # In some cases, you have to set permissions for the raft directory.
  # For example in the case of using a local kind cluster, uncomment the lines below.
  vaultInitContainers:
    - name: raft-permission
      image: busybox
      command:
        - /bin/sh
        - -c
        - |
          chown -R 100:1000 /vault/file
      volumeMounts:
        - name: vault-raft
          mountPath: /vault/file
  caNamespaces:
    - "*"
  image: hashicorp/vault:1.14.8

  # Vault Pods , Services and TLS Secret annotations
  vaultAnnotations:
    type/instance: vault

  # Vault Configurer Pods and Services annotations
  vaultConfigurerAnnotations:
    type/instance: vaultconfigurer

  # Specify the ServiceAccount where the Vault Pod and the Bank-Vaults configurer/unsealer is running
  serviceAccount: vault

  # Specify the Service's type where the Vault Service is exposed
  # Please note that some Ingress controllers like https://github.com/kubernetes/ingress-gce
  # forces you to expose your Service on a NodePort
  serviceType: ClusterIP

  # Use local disk to store Vault raft data, see config section.
  volumeClaimTemplates:
    - metadata:
        name: vault-raft
      spec:
        # https://kubernetes.io/docs/concepts/storage/persistent-volumes/#class-1
        # storageClassName: ""
        accessModes:
          - ReadWriteOnce
        volumeMode: Filesystem
        resources:
          requests:
            storage: 1Gi

  config:
    storage:
      raft:
        path: "/vault/file"
    listener:
      tcp:
        address: "<IP_ADDRESS>:8200"
        tls_cert_file: /vault/tls/server.crt
        tls_key_file: /vault/tls/server.key
    api_addr: https://vault.openshift-bank-vault.svc:8200
    cluster_addr: "https://${.Env.POD_NAME}:8201"
    ui: true

  statsdDisabled: true

  serviceRegistrationEnabled: true

  resources:
    # A YAML representation of resource ResourceRequirements for vault container
    # Detail can reference: https://kubernetes.io/docs/concepts/configuration/manage-compute-resources-container
    vault:
      limits: {}
      requests:
        memory: "256Mi"
        cpu: "100m"

Logs
operator logs:
{"level":"info","ts":"2024-05-24T19:50:36Z","logger":"cmd","msg":"no watched namespace found, watching the entire cluster"}
{"level":"info","ts":"2024-05-24T19:50:36Z","logger":"cmd","msg":"registering manager checks"}
{"level":"info","ts":"2024-05-24T19:50:36Z","logger":"cmd","msg":"bootstrapping manager"}
{"level":"info","ts":"2024-05-24T19:50:36Z","logger":"cmd","msg":"starting manager"}
{"level":"info","ts":"2024-05-24T19:50:36Z","logger":"controller-runtime.metrics","msg":"Starting metrics server"}
{"level":"info","ts":"2024-05-24T19:50:36Z","logger":"controller-runtime.metrics","msg":"Serving metrics server","bindAddress":":8383","secure":false}
{"level":"info","ts":"2024-05-24T19:50:36Z","msg":"starting server","kind":"health probe","addr":"[::]:8080"}
I0524 19:50:36.204688       1 leaderelection.go:250] attempting to acquire leader lease openshift-bank-vault/vault-operator-lock...
I0524 19:50:53.462609       1 leaderelection.go:260] successfully acquired lease openshift-bank-vault/vault-operator-lock
{"level":"info","ts":"2024-05-24T19:50:53Z","msg":"Starting EventSource","controller":"vault-controller","source":"kind source: *v1alpha1.Vault"}
{"level":"info","ts":"2024-05-24T19:50:53Z","msg":"Starting Controller","controller":"vault-controller"}
{"level":"info","ts":"2024-05-24T19:50:53Z","msg":"Starting workers","controller":"vault-controller","worker count":1}
{"level":"info","ts":"2024-05-24T19:50:53Z","logger":"controller_vault","msg":"Reconciling Vault","Request.Namespace":"openshift-bank-vault","Request.Name":"vault"}
{"level":"info","ts":"2024-05-24T19:51:04Z","logger":"KubeAPIWarningLogger","msg":"would violate PodSecurity \"restricted:latest\": allowPrivilegeEscalation != false (containers \"config-templating\", \"raft-permission\", \"vault\", \"bank-vaults\" must set securityContext.allowPrivilegeEscalation=false), unrestricted capabilities (containers \"config-templating\", \"raft-permission\", \"vault\", \"bank-vaults\" must set securityContext.capabilities.drop=[\"ALL\"]; container \"vault\" must not include \"IPC_LOCK\", \"SETFCAP\" in securityContext.capabilities.add), runAsNonRoot != true (pod or containers \"config-templating\", \"raft-permission\", \"vault\", \"bank-vaults\" must set securityContext.runAsNonRoot=true), seccompProfile (pod or containers \"config-templating\", \"raft-permission\", \"vault\", \"bank-vaults\" must set securityContext.seccompProfile.type to \"RuntimeDefault\" or \"Localhost\")"}
{"level":"info","ts":"2024-05-24T19:51:12Z","logger":"controller_vault","msg":"Reconciling Vault","Request.Namespace":"openshift-bank-vault","Request.Name":"vault"}
{"level":"info","ts":"2024-05-24T19:51:39Z","logger":"controller_vault","msg":"Reconciling Vault","Request.Namespace":"openshift-bank-vault","Request.Name":"vault"}
{"level":"info","ts":"2024-05-24T19:51:53Z","logger":"controller_vault","msg":"Reconciling Vault","Request.Namespace":"openshift-bank-vault","Request.Name":"vault"}
{"level":"info","ts":"2024-05-24T19:52:52Z","logger":"controller_vault","msg":"Reconciling Vault","Request.Namespace":"openshift-bank-vault","Request.Name":"vault"}
{"level":"info","ts":"2024-05-24T19:53:51Z","logger":"controller_vault","msg":"Reconciling Vault","Request.Namespace":"openshift-bank-vault","Request.Name":"vault"}
{"level":"info","ts":"2024-05-24T19:54:51Z","logger":"controller_vault","msg":"Reconciling Vault","Request.Namespace":"openshift-bank-vault","Request.Name":"vault"}
{"level":"info","ts":"2024-05-24T19:55:50Z","logger":"controller_vault","msg":"Reconciling Vault","Request.Namespace":"openshift-bank-vault","Request.Name":"vault"}
{"level":"info","ts":"2024-05-24T19:56:01Z","logger":"controller_vault","msg":"Reconciling Vault","Request.Namespace":"openshift-bank-vault","Request.Name":"vault"}
{"level":"info","ts":"2024-05-24T19:56:12Z","logger":"controller_vault","msg":"Reconciling Vault","Request.Namespace":"openshift-bank-vault","Request.Name":"vault"}

Vault logs:
==> Vault server configuration:

Administrative Namespace:
             Api Address: https://vault.openshift-bank-vault.svc:8200
                     Cgo: disabled
         Cluster Address: https://vault-0:8201
   Environment Variables: GODEBUG, GOTRACEBACK, HOME, HOSTNAME, KUBERNETES_PORT, KUBERNETES_PORT_443_TCP, KUBERNETES_PORT_443_TCP_ADDR, KUBERNETES_PORT_443_TCP_PORT, KUBERNETES_PORT_443_TCP_PROTO, KUBERNETES_SERVICE_HOST, KUBERNETES_SERVICE_PORT, KUBERNETES_SERVICE_PORT_HTTPS, NAME, NSS_SDB_USE_CACHE, PATH, PWD, SHLVL, TERM, VAULT_0_PORT, VAULT_0_PORT_8200_TCP, VAULT_0_PORT_8200_TCP_ADDR, VAULT_0_PORT_8200_TCP_PORT, VAULT_0_PORT_8200_TCP_PROTO, VAULT_0_PORT_8201_TCP, VAULT_0_PORT_8201_TCP_ADDR, VAULT_0_PORT_8201_TCP_PORT, VAULT_0_PORT_8201_TCP_PROTO, VAULT_0_PORT_9091_TCP, VAULT_0_PORT_9091_TCP_ADDR, VAULT_0_PORT_9091_TCP_PORT, VAULT_0_PORT_9091_TCP_PROTO, VAULT_0_SERVICE_HOST, VAULT_0_SERVICE_PORT, VAULT_0_SERVICE_PORT_API_PORT, VAULT_0_SERVICE_PORT_CLUSTER_PORT, VAULT_0_SERVICE_PORT_METRICS, VAULT_1_PORT, VAULT_1_PORT_8200_TCP, VAULT_1_PORT_8200_TCP_ADDR, VAULT_1_PORT_8200_TCP_PORT, VAULT_1_PORT_8200_TCP_PROTO, VAULT_1_PORT_8201_TCP, VAULT_1_PORT_8201_TCP_ADDR, VAULT_1_PORT_8201_TCP_PORT, VAULT_1_PORT_8201_TCP_PROTO, VAULT_1_PORT_9091_TCP, VAULT_1_PORT_9091_TCP_ADDR, VAULT_1_PORT_9091_TCP_PORT, VAULT_1_PORT_9091_TCP_PROTO, VAULT_1_SERVICE_HOST, VAULT_1_SERVICE_PORT, VAULT_1_SERVICE_PORT_API_PORT, VAULT_1_SERVICE_PORT_CLUSTER_PORT, VAULT_1_SERVICE_PORT_METRICS, VAULT_2_PORT, VAULT_2_PORT_8200_TCP, VAULT_2_PORT_8200_TCP_ADDR, VAULT_2_PORT_8200_TCP_PORT, VAULT_2_PORT_8200_TCP_PROTO, VAULT_2_PORT_8201_TCP, VAULT_2_PORT_8201_TCP_ADDR, VAULT_2_PORT_8201_TCP_PORT, VAULT_2_PORT_8201_TCP_PROTO, VAULT_2_PORT_9091_TCP, VAULT_2_PORT_9091_TCP_ADDR, VAULT_2_PORT_9091_TCP_PORT, VAULT_2_PORT_9091_TCP_PROTO, VAULT_2_SERVICE_HOST, VAULT_2_SERVICE_PORT, VAULT_2_SERVICE_PORT_API_PORT, VAULT_2_SERVICE_PORT_CLUSTER_PORT, VAULT_2_SERVICE_PORT_METRICS, VAULT_CONFIGURER_PORT, VAULT_CONFIGURER_PORT_9091_TCP, VAULT_CONFIGURER_PORT_9091_TCP_ADDR, VAULT_CONFIGURER_PORT_9091_TCP_PORT, VAULT_CONFIGURER_PORT_9091_TCP_PROTO, VAULT_CONFIGURER_SERVICE_HOST, VAULT_CONFIGURER_SERVICE_PORT, VAULT_CONFIGURER_SERVICE_PORT_METRICS, VAULT_K8S_POD_NAME, VAULT_MUTATING_WEBHOOK_VAULT_SECRETS_WEBHOOK_PORT, VAULT_MUTATING_WEBHOOK_VAULT_SECRETS_WEBHOOK_PORT_443_TCP, VAULT_MUTATING_WEBHOOK_VAULT_SECRETS_WEBHOOK_PORT_443_TCP_ADDR, VAULT_MUTATING_WEBHOOK_VAULT_SECRETS_WEBHOOK_PORT_443_TCP_PORT, VAULT_MUTATING_WEBHOOK_VAULT_SECRETS_WEBHOOK_PORT_443_TCP_PROTO, VAULT_MUTATING_WEBHOOK_VAULT_SECRETS_WEBHOOK_SERVICE_HOST, VAULT_MUTATING_WEBHOOK_VAULT_SECRETS_WEBHOOK_SERVICE_PORT, VAULT_MUTATING_WEBHOOK_VAULT_SECRETS_WEBHOOK_SERVICE_PORT_VAULT_SECRETS_WEBHOOK, VAULT_OPERATOR_PORT, VAULT_OPERATOR_PORT_80_TCP, VAULT_OPERATOR_PORT_80_TCP_ADDR, VAULT_OPERATOR_PORT_80_TCP_PORT, VAULT_OPERATOR_PORT_80_TCP_PROTO, VAULT_OPERATOR_PORT_8383_TCP, VAULT_OPERATOR_PORT_8383_TCP_ADDR, VAULT_OPERATOR_PORT_8383_TCP_PORT, VAULT_OPERATOR_PORT_8383_TCP_PROTO, VAULT_OPERATOR_SERVICE_HOST, VAULT_OPERATOR_SERVICE_PORT, VAULT_OPERATOR_SERVICE_PORT_HTTP, VAULT_OPERATOR_SERVICE_PORT_HTTP_METRICS, VAULT_PORT, VAULT_PORT_8200_TCP, VAULT_PORT_8200_TCP_ADDR, VAULT_PORT_8200_TCP_PORT, VAULT_PORT_8200_TCP_PROTO, VAULT_PORT_8201_TCP, VAULT_PORT_8201_TCP_ADDR, VAULT_PORT_8201_TCP_PORT, VAULT_PORT_8201_TCP_PROTO, VAULT_PORT_9091_TCP, VAULT_PORT_9091_TCP_ADDR, VAULT_PORT_9091_TCP_PORT, VAULT_PORT_9091_TCP_PROTO, VAULT_PORT_9102_TCP, VAULT_PORT_9102_TCP_ADDR, VAULT_PORT_9102_TCP_PORT, VAULT_PORT_9102_TCP_PROTO, VAULT_SERVICE_HOST, VAULT_SERVICE_PORT, VAULT_SERVICE_PORT_API_PORT, VAULT_SERVICE_PORT_CLUSTER_PORT, VAULT_SERVICE_PORT_METRICS, VAULT_SERVICE_PORT_STATSD, VERSION
              Go Version: go1.20.11
              Listener 1: tcp (addr: "<IP_ADDRESS>:8200", cluster address: "<IP_ADDRESS>:8201", max_request_duration: "1m30s", max_request_size: "33554432", tls: "enabled")
               Log Level:
                   Mlock: supported: true, enabled: true
           Recovery Mode: false
                 Storage: raft (HA available)
                 Version: Vault v1.14.8, built 2023-12-04T17:45:23Z
             Version Sha: 446f213c47cabf47d52d065647ef666ce4bf8692

==> Vault server started! Log data will stream in below:

2024-05-24T19:55:13.932Z [INFO]  proxy environment: http_proxy="" https_proxy="" no_proxy=""
2024-05-24T19:55:14.300Z [INFO]  core: Initializing version history cache for core
2024-05-24T19:55:14.868Z [INFO]  core: security barrier not initialized
2024-05-24T19:55:14.870Z [INFO]  core: security barrier not initialized
2024-05-24T19:55:14.870Z [INFO]  core: security barrier not initialized
2024-05-24T19:55:14.870Z [INFO]  core: attempting to join possible raft leader node: leader_addr=https://vault:8200
2024-05-24T19:55:14.873Z [ERROR] core: failed to get raft challenge: leader_addr=https://vault:8200 error="error during raft bootstrap init call: Put \"https://vault:8200/v1/sys/storage/raft/bootstrap/challenge\": dial tcp <IP_ADDRESS>:8200: connect: connection refused"
2024-05-24T19:55:14.873Z [ERROR] core: failed to join raft cluster: error="failed to get raft challenge"
2024-05-24T19:55:16.220Z [INFO]  core: security barrier not initialized
2024-05-24T19:55:16.220Z [INFO]  core: security barrier not initialized
2024-05-24T19:55:16.220Z [INFO]  core: attempting to join possible raft leader node: leader_addr=https://vault:8200
2024-05-24T19:55:16.222Z [ERROR] core: failed to get raft challenge: leader_addr=https://vault:8200 error="error during raft bootstrap init call: Put \"https://vault:8200/v1/sys/storage/raft/bootstrap/challenge\": dial tcp <IP_ADDRESS>:8200: connect: connection refused"
2024-05-24T19:55:16.222Z [ERROR] core: failed to join raft cluster: error="failed to get raft challenge"
2024-05-24T19:55:18.580Z [INFO]  core: security barrier not initialized
2024-05-24T19:55:18.580Z [INFO]  core: security barrier not initialized
2024-05-24T19:55:18.580Z [INFO]  core: attempting to join possible raft leader node: leader_addr=https://vault:8200
2024-05-24T19:55:18.581Z [ERROR] core: failed to get raft challenge: leader_addr=https://vault:8200 error="error during raft bootstrap init call: Put \"https://vault:8200/v1/sys/storage/raft/bootstrap/challenge\": dial tcp <IP_ADDRESS>:8200: connect: connection refused"
2024-05-24T19:55:18.581Z [ERROR] core: failed to join raft cluster: error="failed to get raft challenge"
2024-05-24T19:55:19.279Z [INFO]  core: security barrier not initialized
2024-05-24T19:55:19.280Z [INFO]  core: security barrier not initialized
2024-05-24T19:55:19.280Z [INFO]  core: security barrier not initialized
2024-05-24T19:55:19.280Z [INFO]  core: attempting to join possible raft leader node: leader_addr=https://vault:8200
2024-05-24T19:55:19.282Z [ERROR] core: failed to get raft challenge: leader_addr=https://vault:8200 error="error during raft bootstrap init call: Put \"https://vault:8200/v1/sys/storage/raft/bootstrap/challenge\": dial tcp <IP_ADDRESS>:8200: connect: connection refused"
2024-05-24T19:55:19.282Z [ERROR] core: failed to join raft cluster: error="failed to get raft challenge"
2024-05-24T19:55:20.451Z [INFO]  core: security barrier not initialized
2024-05-24T19:55:20.451Z [INFO]  core: security barrier not initialized
2024-05-24T19:55:20.451Z [INFO]  core: attempting to join possible raft leader node: leader_addr=https://vault:8200
2024-05-24T19:55:20.453Z [ERROR] core: failed to get raft challenge: leader_addr=https://vault:8200 error="error during raft bootstrap init call: Put \"https://vault:8200/v1/sys/storage/raft/bootstrap/challenge\": dial tcp <IP_ADDRESS>:8200: connect: connection refused"
2024-05-24T19:55:20.453Z [ERROR] core: failed to join raft cluster: error="failed to get raft challenge"
2024-05-24T19:55:22.590Z [INFO]  core: security barrier not initialized
2024-05-24T19:55:22.590Z [INFO]  core: security barrier not initialized
2024-05-24T19:55:22.590Z [INFO]  core: attempting to join possible raft leader node: leader_addr=https://vault:8200
2024-05-24T19:55:22.592Z [ERROR] core: failed to get raft challenge: leader_addr=https://vault:8200 error="error during raft bootstrap init call: Put \"https://vault:8200/v1/sys/storage/raft/bootstrap/challenge\": dial tcp <IP_ADDRESS>:8200: connect: connection refused"
2024-05-24T19:55:22.592Z [ERROR] core: failed to join raft cluster: error="failed to get raft challenge"
2024-05-24T19:55:22.627Z [INFO]  core: security barrier not initialized
2024-05-24T19:55:23.069Z [INFO]  core: security barrier not initialized
2024-05-24T19:55:24.073Z [INFO]  core: security barrier not initialized
2024-05-24T19:55:27.625Z [INFO]  core: security barrier not initialized
2024-05-24T19:55:32.625Z [INFO]  core: security barrier not initialized
2024-05-24T19:55:32.626Z [INFO]  core: security barrier not initialized
2024-05-24T19:55:37.631Z [INFO]  core: security barrier not initialized
2024-05-24T19:55:39.146Z [INFO]  core: security barrier not initialized
2024-05-24T19:55:39.369Z [INFO]  core: security barrier not initialized
2024-05-24T19:55:39.370Z [INFO]  core: security barrier not initialized
2024-05-24T19:55:39.370Z [INFO]  core: security barrier not initialized
2024-05-24T19:55:39.370Z [INFO]  core: attempting to join possible raft leader node: leader_addr=https://vault:8200
2024-05-24T19:55:39.374Z [ERROR] core: failed to get raft challenge: leader_addr=https://vault:8200 error="error during raft bootstrap init call: Put \"https://vault:8200/v1/sys/storage/raft/bootstrap/challenge\": dial tcp <IP_ADDRESS>:8200: connect: connection refused"
2024-05-24T19:55:39.374Z [ERROR] core: failed to join raft cluster: error="failed to get raft challenge"
2024-05-24T19:55:40.137Z [INFO]  core: security barrier not initialized
2024-05-24T19:55:40.603Z [INFO]  core: security barrier not initialized
2024-05-24T19:55:40.603Z [INFO]  core: security barrier not initialized
2024-05-24T19:55:40.603Z [INFO]  core: attempting to join possible raft leader node: leader_addr=https://vault:8200
2024-05-24T19:55:40.605Z [ERROR] core: failed to get raft challenge: leader_addr=https://vault:8200 error="error during raft bootstrap init call: Put \"https://vault:8200/v1/sys/storage/raft/bootstrap/challenge\": dial tcp <IP_ADDRESS>:8200: connect: connection refused"
2024-05-24T19:55:40.605Z [ERROR] core: failed to join raft cluster: error="failed to get raft challenge"
2024-05-24T19:55:42.625Z [INFO]  core: security barrier not initialized
2024-05-24T19:55:42.626Z [INFO]  core: security barrier not initialized
2024-05-24T19:55:43.278Z [INFO]  core: security barrier not initialized
2024-05-24T19:55:43.279Z [INFO]  core: security barrier not initialized
2024-05-24T19:55:43.279Z [INFO]  core: attempting to join possible raft leader node: leader_addr=https://vault:8200
2024-05-24T19:55:43.280Z [ERROR] core: failed to get raft challenge: leader_addr=https://vault:8200 error="error during raft bootstrap init call: Put \"https://vault:8200/v1/sys/storage/raft/bootstrap/challenge\": dial tcp <IP_ADDRESS>:8200: connect: connection refused"
2024-05-24T19:55:43.280Z [ERROR] core: failed to join raft cluster: error="failed to get raft challenge"
2024-05-24T19:55:44.152Z [INFO]  core: security barrier not initialized
2024-05-24T19:55:47.626Z [INFO]  core: security barrier not initialized
2024-05-24T19:55:52.626Z [INFO]  core: security barrier not initialized
2024-05-24T19:55:52.626Z [INFO]  core: security barrier not initialized
2024-05-24T19:55:57.625Z [INFO]  core: security barrier not initialized
2024-05-24T19:55:58.006Z [INFO]  core: security barrier not initialized
2024-05-24T19:55:58.145Z [INFO]  core: security barrier not initialized
2024-05-24T19:56:02.625Z [INFO]  core: security barrier not initialized
2024-05-24T19:56:02.626Z [INFO]  core: security barrier not initialized
2024-05-24T19:56:07.625Z [INFO]  core: security barrier not initialized
2024-05-24T19:56:09.308Z [INFO]  core: security barrier not initialized
2024-05-24T19:56:10.145Z [INFO]  core: security barrier not initialized
2024-05-24T19:56:10.319Z [INFO]  core: security barrier not initialized
2024-05-24T19:56:10.320Z [INFO]  core: security barrier not initialized
2024-05-24T19:56:10.320Z [INFO]  core: security barrier not initialized
2024-05-24T19:56:10.320Z [INFO]  core: attempting to join possible raft leader node: leader_addr=https://vault:8200
2024-05-24T19:56:10.323Z [ERROR] core: failed to get raft challenge: leader_addr=https://vault:8200 error="error during raft bootstrap init call: Put \"https://vault:8200/v1/sys/storage/raft/bootstrap/challenge\": dial tcp <IP_ADDRESS>:8200: connect: connection refused"
2024-05-24T19:56:10.323Z [ERROR] core: failed to join raft cluster: error="failed to get raft challenge"
2024-05-24T19:56:11.226Z [INFO]  core: security barrier not initialized
2024-05-24T19:56:11.457Z [INFO]  core: security barrier not initialized
2024-05-24T19:56:11.457Z [INFO]  core: security barrier not initialized
2024-05-24T19:56:11.457Z [INFO]  core: attempting to join possible raft leader node: leader_addr=https://vault:8200
2024-05-24T19:56:11.459Z [ERROR] core: failed to get raft challenge: leader_addr=https://vault:8200 error="error during raft bootstrap init call: Put \"https://vault:8200/v1/sys/storage/raft/bootstrap/challenge\": dial tcp <IP_ADDRESS>:8200: connect: connection refused"
2024-05-24T19:56:11.459Z [ERROR] core: failed to join raft cluster: error="failed to get raft challenge"
2024-05-24T19:56:12.625Z [INFO]  core: security barrier not initialized
2024-05-24T19:56:12.625Z [INFO]  core: security barrier not initialized
2024-05-24T19:56:14.188Z [INFO]  core: security barrier not initialized
2024-05-24T19:56:14.188Z [INFO]  core: security barrier not initialized
2024-05-24T19:56:14.188Z [INFO]  core: attempting to join possible raft leader node: leader_addr=https://vault:8200
2024-05-24T19:56:14.189Z [ERROR] core: failed to get raft challenge: leader_addr=https://vault:8200 error="error during raft bootstrap init call: Put \"https://vault:8200/v1/sys/storage/raft/bootstrap/challenge\": dial tcp <IP_ADDRESS>:8200: connect: connection refused"
2024-05-24T19:56:14.189Z [ERROR] core: failed to join raft cluster: error="failed to get raft challenge"
2024-05-24T19:56:14.236Z [INFO]  core: security barrier not initialized
2024-05-24T19:56:17.626Z [INFO]  core: security barrier not initialized
2024-05-24T19:56:20.113Z [INFO]  core: security barrier not initialized
2024-05-24T19:56:22.626Z [INFO]  core: security barrier not initialized
2024-05-24T19:56:22.626Z [INFO]  core: security barrier not initialized
2024-05-24T19:56:25.145Z [INFO]  core: security barrier not initialized
2024-05-24T19:56:27.625Z [INFO]  core: security barrier not initialized
2024-05-24T19:56:32.626Z [INFO]  core: security barrier not initialized
2024-05-24T19:56:32.626Z [INFO]  core: security barrier not initialized
2024-05-24T19:56:37.626Z [INFO]  core: security barrier not initialized
2024-05-24T19:56:40.144Z [INFO]  core: security barrier not initialized
2024-05-24T19:56:42.625Z [INFO]  core: security barrier not initialized
2024-05-24T19:56:42.626Z [INFO]  core: security barrier not initialized
2024-05-24T19:56:47.625Z [INFO]  core: security barrier not initialized
2024-05-24T19:56:52.627Z [INFO]  core: security barrier not initialized
2024-05-24T19:56:52.628Z [INFO]  core: security barrier not initialized
2024-05-24T19:56:53.145Z [INFO]  core: security barrier not initialized
2024-05-24T19:56:57.406Z [INFO]  core: security barrier not initialized
2024-05-24T19:56:57.626Z [INFO]  core: security barrier not initialized
2024-05-24T19:57:02.630Z [INFO]  core: security barrier not initialized
2024-05-24T19:57:02.630Z [INFO]  core: security barrier not initialized
2024-05-24T19:57:06.145Z [INFO]  core: security barrier not initialized
2024-05-24T19:57:06.371Z [INFO]  core: security barrier not initialized
2024-05-24T19:57:06.403Z [INFO]  core: security barrier not initialized
2024-05-24T19:57:06.404Z [INFO]  core: security barrier not initialized
2024-05-24T19:57:06.404Z [INFO]  core: security barrier not initialized
2024-05-24T19:57:06.404Z [INFO]  core: attempting to join possible raft leader node: leader_addr=https://vault:8200
2024-05-24T19:57:06.406Z [ERROR] core: failed to get raft challenge: leader_addr=https://vault:8200 error="error during raft bootstrap init call: Put \"https://vault:8200/v1/sys/storage/raft/bootstrap/challenge\": dial tcp <IP_ADDRESS>:8200: connect: connection refused"
2024-05-24T19:57:06.406Z [ERROR] core: failed to join raft cluster: error="failed to get raft challenge"
2024-05-24T19:57:07.419Z [INFO]  core: security barrier not initialized
2024-05-24T19:57:07.419Z [INFO]  core: security barrier not initialized
2024-05-24T19:57:07.419Z [INFO]  core: attempting to join possible raft leader node: leader_addr=https://vault:8200
2024-05-24T19:57:07.420Z [ERROR] core: failed to get raft challenge: leader_addr=https://vault:8200 error="error during raft bootstrap init call: Put \"https://vault:8200/v1/sys/storage/raft/bootstrap/challenge\": dial tcp <IP_ADDRESS>:8200: connect: connection refused"
2024-05-24T19:57:07.420Z [ERROR] core: failed to join raft cluster: error="failed to get raft challenge"
2024-05-24T19:57:07.625Z [INFO]  core: security barrier not initialized
2024-05-24T19:57:09.526Z [INFO]  core: security barrier not initialized
2024-05-24T19:57:09.526Z [INFO]  core: security barrier not initialized
2024-05-24T19:57:09.526Z [INFO]  core: attempting to join possible raft leader node: leader_addr=https://vault:8200
2024-05-24T19:57:09.528Z [ERROR] core: failed to get raft challenge: leader_addr=https://vault:8200 error="error during raft bootstrap init call: Put \"https://vault:8200/v1/sys/storage/raft/bootstrap/challenge\": dial tcp <IP_ADDRESS>:8200: connect: connection refused"
2024-05-24T19:57:09.528Z [ERROR] core: failed to join raft cluster: error="failed to get raft challenge"
2024-05-24T19:57:10.382Z [INFO]  core: security barrier not initialized
2024-05-24T19:57:12.625Z [INFO]  core: security barrier not initialized
2024-05-24T19:57:12.626Z [INFO]  core: security barrier not initialized
2024-05-24T19:57:17.625Z [INFO]  core: security barrier not initialized

Additional Information
No response

which seems not a problem related to bank vaults as far as I investigated:
i think its https://support.hashicorp.com/hc/en-us/articles/360050756393-How-to-recover-from-permanently-lost-quorum-while-using-Raft-integrated-storage-with-Vault
questions remaining are:

Can we workaround / automate this with the vault operator?
Is it intended to use velero to handle those situations?

As I found out, this happens if unsealconfig is kubernetes
  unsealConfig:
    options:
      preFlightChecks: true
      storeRootToken: true
      secretShares: 5
      secretThreshold: 3
    kubernetes:
      secretNamespace: vault

with this config, vault does not survive an outage, if you kill all vault pods, vault doesn't come back up by itself
with another config, example, and the same storage backend (raft) vault does survive an outage of all vault nodes, comes back up online successfully without interaction
    google:
      kmsKeyRing: ${kms_keyring}
      kmsCryptoKey: ${kms_crypto_key}
      kmsLocation: ${region}
      kmsProject: ${project}
      storageBucket: ${storage_bucket}

Why this work for google but not Kubernetes unsealConfig?
How its intended to run bv operater operated vault in clusters where no cloud provider is used/available?

Hey @Elyytscha,
Thanks for investigating this.

The Vault Operator can automate the unseal process after a cluster outage by interacting with the Kubernetes API to retrieve the necessary secrets. It can be configured to wait until the Kubernetes control plane and the necessary secrets are available before attempting to unseal Vault.
Velero can back up Kubernetes Secrets, ConfigMaps, and other resources that Vault depends on. If a cluster-wide outage occurs, Velero can restore these resources, helping to ensure that Vault has the necessary keys available when it restarts.
NOTE: You can use Cluster State Restoration:
In cases where the entire cluster needs to be restored, Velero can be used to bring back the cluster to a known good state, including all the necessary Vault-related resources. After restoration, you may still need to ensure that the Vault Operator (or some other automation) handles the unseal process correctly, as restoring resources does not necessarily mean they will be available in the correct order or timing.
The key difference between the Google KMS and Kubernetes Secret-based configurations is that Google KMS is an external, highly available service that is not affected by the state of your Kubernetes cluster. In contrast, Kubernetes Secrets are tightly coupled to the availability and timing of the Kubernetes control plane, making them less reliable in scenarios where the entire cluster experiences an outage.
There are several things you might try, but I would suggest using Consul for managing backup unseal keys instead of Kubernetes Secrets. Consul can be deployed outside of Kubernetes, or even within Kubernetes, but with better recovery mechanisms compared to etcd. Also there are several KMS stores supported by Bank-Vaults CLI that works in cooperation with the Operator, therefore enabling you to utilise them as external storage for unseal keys.

I'm going to close this because you managed to solve the original issue, if you have anymore question, please open another ticket.


use -cp flag instead of env var fixes #402

@sriv  I'm not able to recollect properly, but I guess we used to set classpath as env because using it as a flag can exceed the limit of command length.

Yes, I think that's going to be a problem too. So what's the way out? The golang launcher was working quite well...

@sriv Using arguments file might help us solve this problem.

Closing this, since this brings in another limitation i.e. command path length


Fixed a small xml doc mistake

What does the pull request do?

What is the current behavior?

What is the updated/expected behavior with this PR?

How was the solution implemented (if it's not obvious)?

Checklist

[ ] Added unit tests (if possible)?
[x] Added XML documentation to any related classes?
[ ] Consider submitting a PR to https://github.com/AvaloniaUI/Documentation with user documentation

Breaking changes

Obsoletions / Deprecations

Fixed issues

@dotnet-policy-service agree

You can test this PR using the following package version. 11.0.999-cibuild0037143-beta. (feed url: https://nuget-feed-all.avaloniaui.net/v3/index.json) [PRBUILDID]

You can test this PR using the following package version. 11.0.999-cibuild0037165-beta. (feed url: https://nuget-feed-all.avaloniaui.net/v3/index.json) [PRBUILDID]

Thanks!

You can test this PR using the following package version. 11.0.999-cibuild0037242-beta. (feed url: https://nuget-feed-all.avaloniaui.net/v3/index.json) [PRBUILDID]


Uddate readme and screenshoot sample (good with iphne x)

Just added a PR for this task

thanks for your  PR @NSMyself
i close this issue


makes sure label width remains same on every OS

Problem is that -moz-... font changes on different OS and some have greater character width so puttin a static min-width for labels is not enough

removed text-wrap from labels. table layout can be used. Still, can't find anything good enough to close this issue.

https://stackoverflow.com/questions/45696879/self-adjusting-layout-using-flex/


Use pytest in TestJoin

Prepare for #5759.
@pytest.mark.parametrize does not seem to work with methods of test classes deriving from unittest.TestCase. To use it, this PR fixes TestJoin to be pytest-based instead of unittest.

Jenkins CI test (for commit 1866eab12aef31d69842bda38fb43f7676bc87f1, target branch master) failed with status FAILURE.

Jenkins, test this please

Jenkins CI test (for commit 1866eab12aef31d69842bda38fb43f7676bc87f1, target branch master) failed with status FAILURE.

Jenkins, test this please

Jenkins CI test (for commit 1866eab12aef31d69842bda38fb43f7676bc87f1, target branch master) succeeded!


Changed metamodel code to align with Rahul's implementation

This is a draft for a potential PR about changing the metamodel EOS source code to align with Rahul's EOS code, which you can find at this link together with this link.
This means, among others:

Changing the empirical local energy functional to ELFc rather than ELFc as called in the metamodeling (Margueron et al) paper.
Adding kinetic energy
Compute cs2 for crust and metamodel and use it to compute pressure and energy density.

There are a few advantages to this, such as being able to verify the EOS code against Rahul's code. That seems to work out pretty well in the current implementation: see a cross-check here. Moreover, this removes the need for the Jacobian since we use the analytical derivatives to compute pressure and cs2, which therefore makes the code more efficient.
Note that the current implementation mixes a bit of the old Jose with Rahul's code. For instance
Some things to keep in mind for now:

The higher density part seems much dependent on mu_lowest, i.e the specific details of the crust. This is a bit weird to me and perhaps requires double checking.
The code is currently put in a separate file. I will try to refine it, and then, if OK, merge to replace the old metamodel code.

Tests are OK: new structure works


Explain the script tools

add explanation of scripts in scripts/ to the Readme.

[x] deployGH-Pages.sh
[x] fixAllFileComments.sh
[x] fixSingleFileComment.sh

Documentation added in the wiki instead of the readme, because the scripts are mainly for developers, not end users.


Redesign of parameter architecture

[ ] #29
[ ] #32

Some parameters must be stored in an attrs dataclass, and others in the xarray.Dataset :


Add StartsWith validation

As mentioned in https://github.com/tempestphp/tempest-framework/issues/3

Thanks, @AdamWills!


[Unity] Implement relax.Function.bind_symbolic_vars

If a function has dynamic shape parameters, it can be useful to replace them with static parameters (e.g. when producing several models within the same family).  This commit introduces a utility function relax.Function.bind_symbolic_vars, which allows symbolic variables to be replaced with static values.
This is a related to the parameter binding done in relax.transform.BindParam, but does not require the bound parameter to be fully static data array.

Ooh, thank you for pointing it out!  That would explain why I didn't see the functionality anywhere in the unity branch itself.
Looking through it, I think the main differences are:

This PR accepts either tir.Var (less ambiguous, easier to generate programmatically), or strings (more ambiguous, much easier to hand-write), where #15246 only accepts strings.

This PR operates on a relax function, where #15246 operates on an IRModule.

This PR would ignore functions that are defined within a local function definition, where #15246 would update their symbolic variables.

This PR would replace any TIR usage supported by tir::ExprMutator, where #15246 checks for specific TIR nodes.

This PR raises an error if no symbolic variable is known by that name, where #15246 would silently ignore it.

Thoughts on making a merged PR with the best of both implementations:

Providing methods to update either a IRModule transform or a relax Function would provide the most flexibility.
Implementing a IRModule transform on top of a relax Function update would be require constructing fewer intermediates than implementing a relax Function update on top of an IRModule transform.

Any preference on which of the two PRs should be updated overall? Since both provide similar functionality, I don't have a huge preference.

Thank you for the great summary!
In fact, I like your PR in the sense that it offers broader supports for TIR and it accepts both strings and tir.Var.
Since I think a pass would be convenient when we are dealing with IRModule with multiple functions inside, how about creating a function pass that wraps your utility function? I agree that this would be easier path to merge our PRs.

@sunggg How does the IRModule pass in the latest commit look?

Swapped order of binding_map and func_name, to allow a default value of func_name = None.  If no function name is specified, all functions within the module with be updated.
Pulled in the error checking from the relax.Function.bind_symbolic_vars for the IRModule pass.  If a single function is updated, each value in the binding_map must be used in that function.  If multiple functions are updated, each values in the binding_map must occur as a replacement in at least one function.
Allows replacement either by TIR variable or by name.  If multiple functions are updated, a replacement by name may result in updates to a different TIR variable in each function, so long as it uniquely maps to a TIR variable within a given function.  (e.g. Replacing "batch_size" in all functions in a module.)

The error checking was why I ended up going with a module pass instead of just wrapping the utility with a function pass.  Since the string names would be very convenient to hand-write, they're also the greatest risk of a user typo, which I wanted to guard against.  Having a function pass would require either disabling the "all replacements are used", or restricting the updates to a single function.

@sunggg Also, I've added you as a co-author for this PR.


[DOC] update design/tradeoffs doc regarding scanner vuln reports

What kind of documentation improvement is needed?
Incorrect or outdated information
What is the change that is needed?
This doc can be improved since copa doesn't have to rely on scanner reports anymore
https://project-copacetic.github.io/copacetic/website/design#tradeoffs
Are you willing to submit PRs to contribute to documentation?

[ ] Yes, I am willing to implement it.

Please assign to me @sozercan, will update the docs


TestCase location hint

This issue was originally filed by<EMAIL_ADDRESS>
Add locationHint field with location of the Test.

This issue has been moved to dart-lang/test#150.


powerdevil: fix brightness wonkiness on some laptops

Description of changes
See: https://bugs.kde.org/show_bug.cgi?id=454161
Works for me on an Dell Latitude 5420.
Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[x] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[x] Tested basic functionality of all binary files (usually in ./result/bin/)
22.11 Release Notes (or backporting 22.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module
[ ] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[x] Fits CONTRIBUTING.md.

I think #165717 is caused by the issue referenced here.

Unlikely, unless illum depends on Powerdevil in some convoluted way I can't immediately track down.

@K900 You're right, probably. Sorry for the noise. However, the workaround described there is applicable here too. I am using Brightnessctl to set the brightness as a workaround for this issue.


reconsider default to zfs

when looking at replacing broken kexec nixos-generators with this, was surprised to see zfs a default. Would prefer to see this use boot.kernelPackages = lib.mkDefault pkgs.linuxPackages_testing; so that it can more-aggressively target new platforms.

We already use the latest kernel that supports zfs (6.6 just now, which is the latest release). We need zfs in many places, so this is not an option.


Fix not to hash secret when client_secret_jwt

Fix #1344

@jgrandja
I have fixed it, please review again.


Show pulses, parameters in Circuit.toGraph()

The graph produced by Circuit.toGraph() (and thus the graphviz output) is currently missing Instruction parameters and Pulse instructions, so modify it to include both. For context, I'm using the Pulse instruction for the native GTRI testbed operations, like (if I recall correctly) you suggested.
Here's an example of rendered graphviz:

If I'm doing anything strange here please let me know

I'm going to close this for now since @amccaskey pointed out that the way I'm currently using Pulse to represent logical gates is arguably a misuse of the Pulse instruction. Once I fix that (i.e., add new Gates for XX and R(phi, theta)), I'll revisit this


Workaround for removed feature: additional grammars

Commit https://github.com/mattberkowitz/autoclose-html/commit/73cdb1292978c3b491ef5adc24bb108001aebce3 removed the additional grammars feature. However this feature was used for our language UX. Can I somehow set a setting in our grammar, so that your plugin still works with our language again? (https://github.com/fusetools/Fuse.AtomPlugin/blob/master/grammars/ux.cson)

The new method of detecting "grammar" is to keybind to ">" in text editors with data-grammar that contains "html". I believe the data-grammar attribute is driven by the scopeName of the grammar.
If you go to Atom Preferences > Keybindings, there is a link at the top "your keymap file". Click that and try adding:
'atom-text-editor[data-grammar~="ux"]':
	'>': 'autoclose-html:close-and-complete'

to your keymap file

Thank you for getting back to me, and for sharing a solution. I am gonna share my experience after some tests, but I am closing this ticket for now.


Check error in dynamic flag completion results and log an error in debug mode

These three places we are fetching data from an API to populate the flag completion values:
https://github.com/redhat-developer/app-services-cli/blob/33219ceec41eba2e64cacb71e8e9f74135744c51/pkg/cmd/kafka/describe/describe.go#L87
https://github.com/redhat-developer/app-services-cli/blob/33219ceec41eba2e64cacb71e8e9f74135744c51/pkg/cmd/kafka/delete/delete.go#L87
https://github.com/redhat-developer/app-services-cli/blob/f25528215ade451f12b16094a7e284ae77b4595b/pkg/cmd/kafka/use/use.go#L70
We are ignoring the error though, which is highly possible. We should log this error in debug mode. It is fine if there is an error as the flag will still work, but it can be a useful addition.
Requires https://github.com/redhat-developer/app-services-cli/issues/914 to be completed first.

@craicoverflow I would love to work on this as well as on #914.


Question: Azure and WEBSITE_NODE_DEFAULT_VERSION

So, I was able to deploy this quite easily to azure once I got the build and publish working in visual studio online. The only piece I am not happy with (since it requires a configuration on the webapp) is setting the WEBSITE_NODE_DEFAULT_VERSION in the azure web app. I've read a bit about the iisnode.yml and specifying the server script but unless I set the WEBSITE_NODE_DEFAULT_VERSION to the version on the box, which is 8.1.4, the azure app fails to start. Has anyone gotten a fully setup automated deployment to Azure without having to set the WEBSITE_NODE_DEFAULT_VERSION or some other way ?
(Package json start up script?)

You should be able to do it with the package.json if I'm not mistaken?
"engines":{ "node": "8.1.4" }

that did not seem to have any effect..
I even tried something to do with an iisnode.yml file I found reference to but nothing yet..
Let me know if you (or anyone else) gets around to trying it...

@NelsonLamprecht I imagine none of the options here worked for you?
https://docs.microsoft.com/en-us/azure/nodejs-specify-node-version-azure-apps

@NelsonLamprecht closing this, please reopen if you are still having issues


JCBanner inside a TableViewCell

Hello, it's a nice library. I would like to know how to implement this inside a table view cell. Thank you!.

@tobitech Hi, I haven't tried, but you can use it as just a normal UIView to customize a cell


Develop a suite of RVV-optimized code that can be applied to various vector lengths (VLENs).

Is there a plan to develop a suite of RVV-optimized code that can be applied to various vector lengths (VLENs), rather than developing RVV-optimized code specific to certain VLENs for each processor with built-in vectors, , such as C910, X280, etc., shown as below in the Makefile.riscv64 file?

see #4050 - RVV length specificity was a necessary evil while  the standards were maturing and individual physical implementations were key

see #4050 - RVV length specificity was a necessary evil while the standards were maturing and individual physical implementations were key

Thanks

(C910V will have to remain a separate target as it only supports RVV 0.7.1)


The choice of parameters

Thank you for sharing.
I played on the colab and obtained unpleasing results at most time. It is hard to decide what vaule to use if different edits require different parameters of the CLIP loss.
Then I tried to use the pretrained CLIP model in my own work TediGAN and the obtained results are not sensitive to the weights. Adding additional perceptual loss and image reconstruction loss may help stabilize the optimization process.

Hi @weihaox ,
Thanks for your interest!
I agree that the parameters tuning may be a bit challenging at the moment, this is only an initial version of my project and I hope that I will be able to improve it.
I was not aware of TediGAN, thanks for sharing, looks interesting.
Anyway, according to the results, which text prompt did you use? From the way that the images look, I believe that the issue may be the quality of the inversion.
You may want to look at this paper, where we discuss the intimate relation between and editing in StyleGAN's latent space. The encoder's (from the paper) code will hopefully be publicly available within the few next days, and I am pretty confident that it will improve your results.

Thank you for your reply.  I am looking forward to the new version.


Failed test_verb143 dataset Test

http://ci.mxnet.io/blue/organizations/jenkins/GluonNLP-py3-cpu-unittest/detail/PR-918/5/
Dataset cannot be downloaded.

Connection issue

I retriggered CI. The link seems to work fine now. Closing for now.

Failed again in http://ci.mxnet.io/blue/organizations/jenkins/GluonNLP-py3-cpu-unittest/detail/PR-929/3/pipeline

Did you try if the link was working at the time that the CI errored out? It currently (4 hours later) is working well.
Besides the Failed to establish a new connection: [Errno -2] Name or service not known errors (observed for http://ie.technion.ac.il/) we also time to time get Temporary failure in name resolution errors with conda:
CondaHTTPError: HTTP 000 CONNECTION FAILED for url <https://conda.anaconda.org/conda-forge/noarch/repodata.json>

Elapsed: -

An HTTP error occurred when trying to retrieve this URL.

HTTP errors are often intermittent, and a simple retry will get you on your way.

ConnectionError(MaxRetryError("HTTPSConnectionPool(host='conda.anaconda.org', port=443): Max retries exceeded with url: /conda-forge/noarch/repodata.json (Caused by NewConnectionError('<urllib3.connection.VerifiedHTTPSConnection object at 0x7fbcccfc95f8>: Failed to establish a new connection: [Errno -3] Temporary failure in name resolution',))",),)

http://ci.mxnet.io/blue/organizations/jenkins/GluonNLP-py3-cpu-unittest/detail/PR-928/1/pipeline


Support json format for exploding values and outputs RECORD type in JSON

JSON and JSONB variables outputs are just inlined and not exploded in the variable view.
For RECORD type, as it's returned as a ROW without type we can outputs it as JSONB.
@cvas71 what's your feelings about it?

A good idea. I thought about it. But I don't know yet how to do it. I do not yet know the methods by which it could be done. It is possible that you will need to add something to the extension code.

I released it yesterday and waiting for your feedback 😉
As it implied pldebugger changes don't miss to pull the latest image.
I'm looking for your PR too
Obtenir Outlook pour Androidhttps://aka.ms/AAb9ysg

From: Constantine Grischenko @.>
Sent: Monday, October 3, 2022 7:54:24 AM
To: ng-galien/idea-plpgdebugger @.>
Cc: Alexandre Boyer @.>; State change @.>
Subject: Re: [ng-galien/idea-plpgdebugger] Support json format for exploding values and outputs RECORD type in JSON (Issue #82)
A good idea. I thought about it. But I don't know yet how to do it. I do not yet know the methods by which it could be done. It is possible that you will need to add something to the extension code.
—
Reply to this email directly, view it on GitHubhttps://github.com/ng-galien/idea-plpgdebugger/issues/82#issuecomment-1264967740, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AH6YDP7Q35IODUCTFF3ANI3WBJYJBANCNFSM6AAAAAAQ2M7B5Q.
You are receiving this because you modified the open/close state.Message ID: @.***>

Excellent! Installed plugin 222.2, compiled the plugin_debugger library. Everything is great. I would also like my changes (https://github.com/ng-galien/pldebugger/pull/4) that I made to be included in the build as well.

@cvas71 Your modifications are pushed to the pldebugger and dockers images 13 & 14 (branch print-vars)
Thanks again!

I am very pleased that my participation in your project was useful.


[v8] Investigate updating the React-Redux benchmarks repo

Background: #1740
After v6 turned out to be too slow, we wanted v7 to be really fast.  I ended up creating a React-Redux benchmarks repo at https://github.com/reduxjs/react-redux-benchmarks , which has some stress tests for creating large trees in various scenarios, and dispatching many actions quickly.  It then tries to measure number of re-renders and raw update FPS as a proxy for performance.
I haven't touched that repo since early 2019.  I'd appreciate it if someone could look over that repo and see what might need to be done to prepare things for working with React 18 and some React-Redux v8 alphas.
It would also be good if we can figure out more stats to record in comparison, and maybe better proxies for performance than FPS.

@markerikson Since Looking npm trends search result, I confirmed Recoil doesn't getting a constant user rate.

So I decide migrate Recoil to 'Redux Toolkit' as an one of acceptable de facto standard State Management library, in this project.
Create React App TypeScript Todo Example 2021
I'll rewrite this weekend and I'd like this to be used for benchmarking purposes if that is helpful for your sake.

@ryota-murakami FWIW, for this issue I'm specifically interested in looking at the https://github.com/reduxjs/react-redux-benchmarks and seeing what needs to be done to get ready for updated performance testing with React-Redux v8 and React 18.  Like, obviously some packages will need to be updated, but also I don't remember how the useSelector perf tests ended up being defined, or if they cover all the same scenarios that the connect tests do.  I also want to see if we can improve how we're measuring "performance" here.
If you or anyone else comes up with additional benchmarks that would be useful too, but my main goal here is just the existing benchmarks repo.

@markerikson I see. I guess @dai-shi has some resource like that...

Well, https://github.com/reduxjs/react-redux-benchmarks/pull/26 is my last work there. It should be easy to remove r-r-r, but the changes are still too big and duplicated.
If someone is gonna work on this, they can do a better way, because what we want to compare is r-r v7 and r-r v8 and comparing with connect is not primary.

Hello here, I am really interested in subjects around performance so I would love to give this a try. I will first take a look at https://github.com/reduxjs/react-redux-benchmarks to see how it works

@alk-mandrianarijaona cool. FYI, I actually did a major update since posting this issue, to redo the build setup entirely and make it easier to add scenarios:

https://github.com/reduxjs/react-redux-benchmarks/pull/28
https://github.com/reduxjs/react-redux-benchmarks/pull/29
https://github.com/reduxjs/react-redux-benchmarks/pull/30

@markerikson thanks for that, so what are the next steps you suggest I should look into?

@alk-mandrianarijaona : I just merged the one open PR I had over there .  I think the next steps would be to update the React and React-Redux deps to use the latest React 18 and React-Redux v8 alphas, and then try to add more hooks-based equivalents of the existing connect-based usage scenarios.


[23543] Multi words zones now work while searching for timezones.

Details
Improved search functionality on the select timezone page.
Fixed Issues
$ https://github.com/Expensify/App/issues/23543
PROPOSAL: https://github.com/Expensify/App/issues/23543#issuecomment-1675395081
Tests
Same as QA Steps.

[X] Verify that no errors appear in the JS console

Offline tests
Same as QA Steps.
QA Steps

Go to Settings -> Profile -> Timezone;
Uncheck the "Automatically determine your location." checkbox;
Click on "Timezone";
Input a multi word zone such as "New York", "Isle of Man", "East Indiana" in the search text;
Verify that the correct result appears.

[X] Verify that no errors appear in the JS console

PR Author Checklist

[X] I linked the correct issue in the ### Fixed Issues section above
[X] I wrote clear testing steps that cover the changes made in this PR

[X] I added steps for local testing in the Tests section
[X] I added steps for the expected offline behavior in the Offline steps section
[X] I added steps for Staging and/or Production testing in the QA steps section
[X] I added steps to cover failure scenarios (i.e. verify an input displays the correct error message if the entered data is not correct)
[X] I turned off my network connection and tested it while offline to ensure it matches the expected behavior (i.e. verify the default avatar icon is displayed if app is offline)
[X] I tested this PR with a High Traffic account against the staging or production API to ensure there are no regressions (e.g. long loading states that impact usability).

[X] I included screenshots or videos for tests on all platforms
[X] I ran the tests on all platforms & verified they passed on:

[X] Android / native
[X] Android / Chrome
[x] iOS / native
[X] iOS / Safari
[X] MacOS / Chrome / Safari
[X] MacOS / Desktop

[X] I verified there are no console errors (if there's a console error not related to the PR, report it or open an issue for it to be fixed)
[X] I followed proper code patterns (see Reviewing the code)

[X] I verified that any callback methods that were added or modified are named for what the method does and never what callback they handle (i.e. toggleReport and not onIconClick)
[X] I verified that the left part of a conditional rendering a React component is a boolean and NOT a string, e.g. myBool && <MyComponent />.
[X] I verified that comments were added to code that is not self explanatory
[X] I verified that any new or modified comments were clear, correct English, and explained "why" the code was doing something instead of only explaining "what" the code was doing.
[X] I verified any copy / text shown in the product is localized by adding it to src/languages/* files and using the translation method

[X] If any non-english text was added/modified, I verified the translation was requested/reviewed in #expensify-open-source and it was approved by an internal Expensify engineer. Link to Slack message:

[X] I verified all numbers, amounts, dates and phone numbers shown in the product are using the localization methods
[X] I verified any copy / text that was added to the app is grammatically correct in English. It adheres to proper capitalization guidelines (note: only the first word of header/labels should be capitalized), and is approved by marketing by adding the Waiting for Copy label for a copy review on the original GH to get the correct copy.
[X] I verified proper file naming conventions were followed for any new files or renamed files. All non-platform specific files are named after what they export and are not named "index.js". All platform-specific files are named for the platform the code supports as outlined in the README.
[X] I verified the JSDocs style guidelines (in STYLE.md) were followed

[X] If a new code pattern is added I verified it was agreed to be used by multiple Expensify engineers
[X] I followed the guidelines as stated in the Review Guidelines
[X] I tested other components that can be impacted by my changes (i.e. if the PR modifies a shared library or component like Avatar, I verified the components using Avatar are working as expected)
[X] I verified all code is DRY (the PR doesn't include any logic written more than once, with the exception of tests)
[X] I verified any variables that can be defined as constants (ie. in CONST.js or at the top of the file that uses the constant) are defined as such
[X] I verified that if a function's arguments changed that all usages have also been updated correctly
[X] If a new component is created I verified that:

[X] A similar component doesn't exist in the codebase
[X] All props are defined accurately and each prop has a /** comment above it */
[X] The file is named correctly
[X] The component has a clear name that is non-ambiguous and the purpose of the component can be inferred from the name alone
[X] The only data being stored in the state is data necessary for rendering and nothing else
[X] If we are not using the full Onyx data that we loaded, I've added the proper selector in order to ensure the component only re-renders when the data it is using changes
[X] For Class Components, any internal methods passed to components event handlers are bound to this properly so there are no scoping issues (i.e. for onClick={this.submit} the method this.submit should be bound to this in the constructor)
[X] Any internal methods bound to this are necessary to be bound (i.e. avoid this.submit = this.submit.bind(this); if this.submit is never passed to a component event handler like onClick)
[X] All JSX used for rendering exists in the render method
[X] The component has the minimum amount of code necessary for its purpose, and it is broken down into smaller components in order to separate concerns and functions

[X] If any new file was added I verified that:

[X] The file has a description of what it does and/or why is needed at the top of the file if the code is not self explanatory

[X] If a new CSS style is added I verified that:

[X] A similar style doesn't already exist
[X] The style can't be created with an existing StyleUtils function (i.e. StyleUtils.getBackgroundAndBorderStyle(themeColors.componentBG))

[X] If the PR modifies code that runs when editing or sending messages, I tested and verified there is no unexpected behavior for all supported markdown - URLs, single line code, code blocks, quotes, headings, bold, strikethrough, and italic.
[X] If the PR modifies a generic component, I tested and verified that those changes do not break usages of that component in the rest of the App (i.e. if a shared library or component like Avatar is modified, I verified that Avatar is working as expected in all cases)
[X] If the PR modifies a component related to any of the existing Storybook stories, I tested and verified all stories for that component are still working as expected.
[X] If the PR modifies a component or page that can be accessed by a direct deeplink, I verified that the code functions as expected when the deeplink is used - from a logged in and logged out account.
[X] If a new page is added, I verified it's using the ScrollView component to make it scrollable when more elements are added to the page.
[X] If the main branch was merged into this PR after a review, I tested again and verified the outcome was still expected according to the Test steps.
[X] I have checked off every checkbox in the PR author checklist, including those that don't apply to this PR.

Screenshots/Videos

Web

Mobile Web - Chrome

Mobile Web - Safari

Desktop

iOS

Android

I need to add Screenshots/Videos, but I firstly wanted to agree on the desired functionality. This version works as follows:

"Europe/Isle_of_Man":
1.1.  Works with: "Isle of Man", "Isl o M", "Eur Isl", "man of isle", "  Isle   Man  ", "Europe/Isl", "Eur/Isl", "Isle_of", "Isle_of man";
1.2. Does not work with: "IsleOfMan".

"Asia/Calcutta"
2.1. Works with: "cal".

"US/East-Indiana"
3.1. Works with: "US East", "East I"(shown at the end), "East In"(shown first now), "East-I".

"GMT+0"
4.1. Works with: "gmt", "GMT", "GMT+", "gmt 0";
4.2. Does not work with: "gmt0".

The only downsides for now are that "IsleOfMan" dows not work, and that "East I" shows "US/East-Indiana" at the end of the list. I've tried some changes, but I seem to lose some other functionality by fixing these.
@fedirjh Would you say that it's ok as is, or would you want me to make some changes? If so, please tell me what changes. I'll come back with a potential fix & a list of any new downside. Thank you!

@fedirjh Isn't this regex:
const searchWords = searchText.toLowerCase().replace(/[^a-z0-9]/g, ' ').split(' ');
searchWords.forEach((word) => {
    if (tz.text.toLowerCase().replace(/[^a-z0-9]/g, ' ').indexOf(word) < 0) shouldShow = false;
})

Simpler, more future proof, and with almost the same functionality?
We don't exactly specify the special characters(+, -, /) here, maybe some new ones will appear in the future. Only diff in functionality is that "IsleOfMan" does not work and "Eur/Isl" does. Personally, I think I'd prefer this, but let me know which one you want to keep & I'll make a new commit. Thanks!

@fedirjh Yes, that PR kind of simplified the timezones list.

If we were to update the timezone list in the future to include timezones like GMT +/-, this regex would also need to be updated accordingly.

It will still show the GMT -1 in the results, but it won't be the first option. When searching for "gmt -1", users will see:
GMT +1
GMT -1
GMT 1

If the priority issue is to be resolved, I do agree with you, it's not future proof enough. It will be capable to show the results, but will have small problems in prioritizing them, especially for those with special characters. Same is happening in the present, but it's simply resolved by entering one more letter, as seen now for "San M"(shown at the end) vs "San Ma"(shown at the top as it's the only result). This, IMO, can be considered intended.

@bondydaa bump to PR approval, thanks!

:hand: This PR was not deployed to staging yet because QA is ongoing. It will be automatically deployed to staging after the next production release.

🚀 Deployed to staging by https://github.com/bondydaa in version: 1.3.59-0 🚀

platform
result

🤖 android 🤖
failure ❌

🖥 desktop 🖥
success ✅

🍎 iOS 🍎
success ✅

🕸 web 🕸
success ✅

🚀 Deployed to staging by https://github.com/bondydaa in version: 1.3.60-0 🚀

platform
result

🤖 android 🤖
success ✅

🖥 desktop 🖥
success ✅

🍎 iOS 🍎
failure ❌

🕸 web 🕸
success ✅

🚀 Deployed to production by https://github.com/luacmartins in version: 1.3.59-5 🚀

platform
result

🤖 android 🤖
success ✅

🖥 desktop 🖥
success ✅

🍎 iOS 🍎
failure ❌

🕸 web 🕸
success ✅

🚀 Deployed to production by https://github.com/luacmartins in version: 1.3.60-3 🚀

platform
result

🤖 android 🤖
success ✅

🖥 desktop 🖥
success ✅

🍎 iOS 🍎
success ✅

🕸 web 🕸
success ✅


IdentityModel.Tokens.Jwt < 5.3.0

To prevent error "Error validating identity token: Microsoft.IdentityModel.Tokens.SecurityTokenSignatureKeyNotFoundException: IDX10501: Signature validation failed. Unable to match keys …."
While this is closed, even Android has this issue

I don't like this change. We should rather wait for them to fix their code.


"INTERNAL_OPENAI_COMPATIBLE_API_BASE_URL=""

Bug description
This doesn't work with "INTERNAL_OPENAI_COMPATIBLE_API_BASE_URL" while it works if I manually enter the website.

Steps to reproduce
ACCESS_KEYS="ABC123,JUD71F,HUWE3"
INTERNAL_OPENAI_COMPATIBLE_API_BASE_URL="https://hubs0924.snia.ch/v1"
INTERNAL_OPENAI_COMPATIBLE_API_KEY="sk-XzzuL6fILhg49TW3B4C247E706E4437dB240D1Bf5727Ff72"
INTERNAL_OPENAI_COMPATIBLE_API_MODEL="pixtral-12b:free"
INTERNAL_OPENAI_COMPATIBLE_API_NAME="pixtral-12b:free"
Expected behavior
I expect not to have to manually enter information on the site!
Device info
No response
Additional context
No response

I couldn't reproduce it.
Here's what I tried:

Stopped the server.
Used the same info you provided in .env:

Ran docker compose -f docker-compose.production.yml up --build
Accessed http://localhost:7860/ and checked the menu:

Executed the search using this option:

Maybe you forgot to restart the docker instance after changing the .env?

Hello,
I am sincerely sorry, but my .env file did not go to the right directory, so I had two .env files!
I have modified the settings.ts file located in the client/modules directory.
To be able to configure in .env what we want by default.
settings.ts:
import { addLogEntry } from "./logEntries";
import { isF16Supported } from "./webGpu";

export const defaultSettings = {
  enableAiResponse: true,
  enableWebGpu: true,
  enableImageSearch: true,
  webLlmModelId: isF16Supported
    ? VITE_WEBLLM_DEFAULT_F16_MODEL_ID
    : VITE_WEBLLM_DEFAULT_F32_MODEL_ID,
  wllamaModelId: VITE_WLLAMA_DEFAULT_MODEL_ID,
  cpuThreads: 1,
  searchResultsToConsider: 3,
  systemPrompt: `You are a research assistant. Provide detailed, step-by-step responses following these guidelines:
- Use Markdown
- Explain thoroughly
- Use an analytical, formal tone
- Break down complex problems
- Communicate thought process clearly
- Keep in mind today's date and time ({{dateTime}}).
- Answer in the same language as the person interacting with you
- Base your responses on the provided search results and your general knowledge about the topic
- Include additional relevant context, even if not directly requested

Search results:
{{searchResults}}`,
  inferenceType: import.meta.env.VITE_INFERENCE_TYPE || "browser", // Utilise la variable d'environnement
  openAiApiBaseUrl: "",
  openAiApiKey: "",
  openAiApiModel: "",
  enterToSubmit: true,
};

addLogEntry(
  `Number of logical processors in CPU: ${navigator.hardwareConcurrency ?? "unknown"}`,
);

export type Settings = typeof defaultSettings;

export const inferenceTypes = [
  ...(VITE_INTERNAL_API_ENABLED
    ? [{ value: "internal", label: VITE_INTERNAL_API_NAME }]
    : []),
  { value: "browser", label: "Browser-Based" },
  { value: "openai", label: "OpenAI-Compatible API" },
];

.env:
# Type d'inférence à utiliser (internal, browser, openai, etc.)
VITE_INFERENCE_TYPE=internal

Ok, thanks for letting me know it's working!
Currently it will use the "internal" by default if the internal API is defined, but I agree that making it configurable is beneficial for other users. I'll add that new Environment Variable.

Alright, @comeback01! You can now set DEFAULT_INFERENCE_TYPE on .env to configure the default inference type, like this:


milestone 1 spec

Still points to CL specs 1.1.6 and engine API alpha.5. v1.1.9 and alpha.6 don't seem to impinge directly too much on this, as the SignedBeaconBlock aspect in particular isn't changed.

@terencechain @realbigsean @tersec I'm sorry for the long time without a reply. We were reorganizing the team to make sure that we could maintain this for the merge.
Now @thegostep @metachris @jparyani and me will be working on this, first getting the milestone 1 tested on kiln.
Thanks a lot for your reviews and feedback. Some things are very straightforward and we are working on those. For some others I'll have more questions as I get to understand more details about the specification.

We have cleaned a milestone1 specification in https://github.com/flashbots/mev-boost/blob/main/docs/specification.md and all the pending discussions are now in the issues. Please check and let me know if I missed any concerns, to make sure we are not dropping anything important. Moving forward, we should have one issue and one PR per concern, so it's easier to focus.
Thanks for work and the nice discussion everybody. I'm closing this one.


Pkg out always appends pkg

Pkg out always appends pkg even when pkg already given as output arg
if output.endswith(".pkg"):
    output = output[:-4]

Will be fixed as soon as I feel like fixing this issue.


PFE should break if a URL-specified workflow ID is inactive

We don't want it to fall back and produce an unwanted classification
cc @tingard

Related: #32

^I like this, better than redirecting to a mutable "inactive" workflow.

Wait, does this supersede #27

Yes - which is why I referenced it there :)


ImportError: No module named util

Hi,
I built carla the developer mode and I am trying to roslaunch carla_ros_bridge carla_ros_bridge_with_example_ego_vehicle.launch and I am getting "No module name util". When I run one of the example codes in the PythonAPI using python3 there is no issue. Therefore, I know that error is because the egg file for carla 0.9.10 is for python3.7 and my system is probably running it with python2.7, but I don't have the egg file for python2.7.

. My pc has Ubuntu 18.04 and I am using ros melodic.
Any suggestions?

Just do make PythonAPI.2 and you should have the .egg file for Python 2.7.

The carla I downloaded from here https://github.com/carla-simulator/carla/releases/tag/0.9.10 doesn't have any make file or anything so I can't generate the egg file

The carla I downloaded from here https://github.com/carla-simulator/carla/releases/tag/0.9.10 doesn't have any make file or anything so I can't generate the egg file

Please, download the <IP_ADDRESS> version, or also the 0.9.11 version, which also includes the .egg file for Python 2. The 0.9.10 is the only one that doesn't.

Thanks, I got it working

Hii I am facing the same error now, my system is running noetic with supports python3 alone and because of that I had set the egg file to python 3.7 version and am still facing the same issue any help here please?

me too! =)

Thanks, I got it working

Hi, May I ask how did you fix that? Thanks! @Johanfanas


Get DM Stack under CIT

Extend CIT to include use of docker to recreate Stack v15 environment. Needs #16 #17 and #18 t happen first. Belongs to epic #15.

News from the DM team is that Frossie is working on a proper CIT system for the LSP - so we can close this out and just use her system when it is built. Hurrah!


Fix issue #135: Add DSRV operator website link

Add DSRV operator website link

@heejin-github, hey!
I'm afraid you have to resolve the branches conflict


Provide a ready made ADA graphics configuration for mono OLED's

Provide a ready made graphics configuration with suitable settings for the most common OLED displays such as 1306.
TODO - get a list of other such drivers.

Available now on master.

accidentally closed, this is not yet fully added

OLED 1306 etc will be available from 1.3.1


Support rediss:// --tls support

Please add rediss:// --tls support for spin-redis-trigger.
https://docs.rs/redis/latest/redis/struct.Client.html#method.build_with_tls

From Discord discussion I think @seungjin's priority is the Redis trigger, but we should allow it on the outbound Redis API too (including a suitable default port for allowed_outbound_hosts?).

Actually it works well with publishing messages to Redis with rediss:// in spim.toml
allowed_outbound_hosts = [
    "redis://{{ redis_host }}:{{ redis_port }}",
    "rediss://{{ redis_host }}:{{ redis_port }}",
]

With above, I can publish and can see messages were being passed with redis-cli.
The problem is trigger. Trigger is not getting from rediss://
[application.trigger.redis]
address = "rediss://{{ redis_credential }}@{{ redis_host }}:{{ redis_port }}"

redis trigger with rediss:// never triggered.
This is currently NOT high priority - but good to have (ATM).

@seungjin Locally or on fermyon's cloud ? For me locally it's working fine on secured redis endpoint.

ref https://github.com/fermyon/spin/pull/999

@radu-matei #999 only covers outbound - from comments above it looks like the trigger is the problem (although evidently working for some folks).  I'll update the issue title.


StarterKit for Germany

Let's create a starter kit that includes important information and useful links.

Where to find what?
Important phone numbers
Links to Government websites
Activities
Basic German words

May I add some points?

Link to current COVID regulations (in best case to an English website, does not need to be in depth, just an overview explaining how this works in Germany)
Basic information which supermarkets are available and what they offer
Basic information where one can find the next hospital/doctor/pharmacy/etc.

@Ein-Tim good points 👍🏼

Important phone numbers:
110 - police
112 - fire department
116117 - medical emergencies (also to search for a doctor or treatment)
Some important links for refugees:
Online Health Guide: https://www.bundesgesundheitsministerium.de/en/topics/health-guide-for-asylum-seekers.html

includes vaccination, "who does what", pregnancies and protection from diseases

FAQs by ministry for labor and social affairs: https://www.bmas.de/DE/Europa-und-die-Welt/Europa/Ukraine/FAQ-EN/faq-art-en.html
FAQs by the ministry of interior and community:

in Ukrainian: https://www.bmi.bund.de/SharedDocs/faqs/DE/themen/ministerium/ukrain-war-ukr/faq-list-ukrain-war.html
in English: https://www.bmi.bund.de/SharedDocs/faqs/EN/topics/ministry/ukraine-war-eng/faq-list-ukrain-war-en.html

FAQs by the ministry for migration, refugees and integration:

in Ukrainian: https://www.integrationsbeauftragte.de/ib-de/staatsministerin/війна-в-україні-2008512
in English: https://www.integrationsbeauftragte.de/ib-de/staatsministerin/war-in-ukraine-2008510

Important German phrases (translated with Google translate)
Hallo - Здравствуйте
Ich spreche kein Deutsch - Я не розмовляю німецькою
Sprichst du Englisch? - Ви розмовляєте англійською?
Wo ist der nächste Supermarkt? - Де наступний супермаркет?
Ich suche ... - Я шукаю
Krankenhaus - лікарні
Arzt - лікар
Apotheke - аптека
Amt - урядова установа
Hilfe - допомогти
to be continued (not sure if Ukrainians can read the Latin alphabet)
Which supermarkets are there in Germany?
Aldi
Lidl
Penny
Netto
Rewe
Edeka
Real
Globus
Which drug stores are there in Germany?
dm
Rossmann
How do I find a pharmacy?
 I guess even I can learn something. Is that a Cologne thing or where can I find those stores?

Globus is not commonly known? Well, I guess than it's rather a Cologne/NRW thing.

We should add a list of online services and translators who offer their services for free

Russischsprachige Telefonseelsorge
https://www.diakonie-portal.de/themen/ehrenamt-freiwilligendienste/ehrenamt-und-engagement/telefon-doweria-telefon-doverija

https://www.germany4ukraine.de/hilfeportal-en

Nothing for the StarterKit but good to know: https://www.youtube.com/watch?v=E138aiB8sf4

Basic Version of this StarterKit will go live today with v1.0
We will further improve it for 1.1

StarterKits should be personalized, e.g. family with children need other information than a single person

As a second priority, we could create a starter kit for hosts. This kit could include information like the legal information that you shared in the Youtube link above.
I think a lot of people are considering hosting refugees but are unsure about the legal implications. A starter kit for them could be the right push in the right direction.


Standard: api returns ready=True but not all components are ready

Clients in standard address space tests sometimes fail on "no-route-to-destination" when try to connect to topic. We with @tkratky tried to wait after api return ready=True for 5 sec and client connected to topic in standard address space properly. So it can be workaround for while, but we need better way to check if all components of standard address space include topic pod are ready.
Wait after ready check can be workaround for  #832 too.

https://github.com/EnMasseProject/enmasse/pull/1008


(Wait for #2071, #2075) [Memory] Add apply gradient step

After derivative calculation, gradient needs to be applied. But, the
order for it was merged with derv calculation.
This patch divide apply graident order, and modify related lifespans.
Signed-off-by: Jiho Chu<EMAIL_ADDRESS>

:memo: TAOS-CI Version: 1.5.20200925. Thank you for submitting PR #2094. Please a submit 1commit/1PR (one commit per one PR) policy to get comments quickly from reviewers. Your PR must pass all verificiation processes of cibot before starting a review process from reviewers. If you are new member to join this project, please read manuals in documentation folder and wiki page. In order to monitor a progress status of your PR in more detail, visit http://ci.nnstreamer.ai/.

:octocat: cibot: @jihochu, A builder checker could not be completed because one of the checkers is not completed. In order to find out a reason, please go to http://ci.nnstreamer.ai/nntrainer/ci/repo-workers/pr-checker/2094-202301040952440.69440793991089-9727c626088564ccccb183dd8a1d1dfa4438e44f/.

:octocat: cibot: @jihochu, A builder checker could not be completed because one of the checkers is not completed. In order to find out a reason, please go to http://ci.nnstreamer.ai/nntrainer/ci/repo-workers/pr-checker/2094-202301301851090.61000609397888-436f392cd0f33952f0fa504e7741930f9352feff/.

LGTM

:octocat: cibot: @jihochu, A builder checker could not be completed because one of the checkers is not completed. In order to find out a reason, please go to http://ci.nnstreamer.ai/nntrainer/ci/repo-workers/pr-checker/2094-202302201306290.94351410865784-308841ff93d73735fdba2e3b6cbe72617adfd7f0/.


index.html references ../build/test.css

The build creates ../build/build.css

Running npm run build-test should fix this


Feature request: Support providing changelogs instances directly

I have a feature request for mongock that could be interesting. I see mongock is able to scan packages looking for changesets and automatically instantiate classes, which is good. However, in some use-cases, changesets could be manually instantiated, and in my use-case I would need to provide those instances directly to mongock, instead of letting the framework instantiate them.
Something like this:
val changeSet = MyChangeSet("custom instantiation parameters")

MongockStandalone.builder()
    .setDriver(MongoSync4Driver.withDefaultLock(client, "db"))
    .addChangeSet(changeSet)
    .buildRunner()
    .execute()

I haven't looked deep into the architecture, but I believe this would be quite simple to implement. Let me know what you think!

Hello @pelletier197 ,
first at all thanks for your contribution and use Mongock.
That's a good idea. We actually have it in our roadmap for coming version 5(we are not adding any new feature to current version).
We are actually going further in Spring, we will provide the ability to load the changeLogs from the Spring context.
However, this has to be approached with caution. All the parameters Mongock pass to. a changeSet are proxies(unless the developers specifies the opposite) to ensure that the lock is wrapping the i/o operations to the database, at least the writes.  If you construct your changeLog on your own, this is going to be a problem, as a lot of developers won't be aware of this fact.
Can you tell me why do you really need this?

Thanks for your quick reply, and thanks to you for providing such a great framework to the community!

All the parameters Mongock pass to. a changeSet are proxies(unless the developers specifies the opposite) to ensure that the lock is wrapping the i/o operations to the database, at least the writes.
I unserstand perfectly your concern. However, this arises a small question : why do you put a lock on every parameter of the changelog? Wouldn't it be simpler to wrap the call to  the changeset methods in a transaction and revert if any of the changelog fail?

Can you tell me why do you really need this?
Yes, so I have a special use case for Mongo to support multi-tenancy, meaning each customer uses the same instance of Mongo, but will see his data stored in a completely different database. This is not well supported by Mongo either (we use spring), so we had to develop a little custom code to make this work.

However, this means I have to run my migrations on multiple databases, which does not really fit into the use case for spring (or maybe there's a magical way to do this I don't know of) . So instead, I though of having an Interface MongoChsngeSet,  and annotate the implementations with@Configuration so I could inject the changesets directly into Mongock, while still letting spring wire them, but I realized Mongock didn't allow that.
Si here I am. Maybe there's a better alternative I didn't think of? Thanks for your help!

However, this arises a small question : why do you put a lock on every parameter of the changelog? Wouldn't it be simpler to wrap the call to the changeset methods in a transaction and revert if any of the changelog fail?

That would be a much easier approach. Mongock acquires the lock before the process starts, lets say for 3 minutes, and before every changeLog runs, it makes sure the lock is acquired for 3 minutes, right? What happens if a changeLog takes 4 minutes? The changeLog will be partially executed without lock. A solution it's to reserve the lock longer, lets say 5 minutes. Now, if another changeLog takes 6 minutes?...well, put something safe, an hour, as we know that mongock will release the lock once the process is finished, it won't probably take the hour ever. Well, that's ok, but what happens if the jvm is interrupted and Mongock cannot release the lock. Mongock won't be able to run for that hour.
I guess you get my point, basically that's not a robust approach. Instead, we have provided a more sophisticated mechanism hat guarantees the process is fully synchronised, based on a pessimistic lock which ensures every access(at least every write) is synchronised.
You may suggest using demon, but that's not that reliable and threads my not fit all the ecosystems.

Regarding your scenario, I have a couple of questions

Do you know which databases you will be working with beforehand?
When do you run the Mongock process? At starting(standard) or in the middle of the application, triggered by something(non standard)

As part of version 5 we are addressing this scenario, as it's starting to be a common one, specially for consultancies. That's what I made this questions, I'd like to understand your needs so we can provide the best solution :)

Yeah, I understand the problems with the lock. This is actually the first system I see that has a lock with a duration. Usually, I believe they put the lock in the database at the beginning of the process and remove it at the end (either the changelog crashes or not). This is an interesting approach, but i honestly don't see the advantages of it right away. You surely designed it this way for a reason, so I trust your judgment 😉
Anyway here's the answer to both questions above :

We have a different set of credentials for every tenant, and every set of credential has access to only a specific database. It's a standard for highly secure applications (not for most applications I think), so the database is known beforehand, and we have a different MongoClient per tenant.
We run the migrations at startup and they must all complete before the application finishes booting. We usually only add indexes, so they are instant most of the time. We haven't used Mongo long enough to need to change a large dataset.

Hope this helps 🙂

I know your point. This is something that doesn't really shines and may not be needed in most of the cases for you, but it's a must for a robust system, specially in containerised environments with everything automated. Actually the reason we started this project was because we experienced a big issue, that happened sometimes, but when happened, the service couldn't get recovered and we had to remove the lock collection and deploy it manually again. It was reeeeally hard to find.
It may look a bit over-engineered, but we are obsessed with robustness, so the tool gives the less problems possible and you can focus on your business.

Coming back to you scenario.
Apart from the fact that you are managing multiple databases, you are doing it as it's supposed to be done. That's good!! Let me think about your case and will come back to discuss the best solution for you, ideally using the spring module 😉
But this will be provided in the version 5, which will be released around end of May, but we can provide you with a beta version

Just out of curiosity? Which company are you? If you can't give the name, could you at least provides the industry?
Cheers


[MINOR][CONNECT][DOCS] Fix typo in connect/README.md

What changes were proposed in this pull request?
This pr fix typo in connect/README.md
Why are the changes needed?
Fix typo in connect/README.md
Does this PR introduce any user-facing change?
No
How was this patch tested?
Pass Github Actions

cc @HyukjinKwon just a typo fix

merged into master

Thanks @zhengruifeng


I am not finding the PowerShell Commandlets after installing the SPMT. Please go to https://aka.ms/spmt, you will find "Version 2 is now publicly available for download here: SharePoint Migration Tool Version 2", download SPMT and install UI tool. The PowerShell module is installed in %userprofile%\Documents\WindowsPowerShell\Modules.

Import-Module Microsoft.SharePoint.MigrationTool.PowerShell, you can use all migration cmdlets.
Originally posted by @wenhua-helen in https://github.com/MicrosoftDocs/OfficeDocs-SharePoint/issues/120#issuecomment-409436795

@mikebrunak Do you have an issue on an article?


Update sbt to 1.6.2

Updates org.scala-sbt:sbt from 1.5.8 to 1.6.2.
GitHub Release Notes - Version Diff
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

Ignore future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "org.scala-sbt", artifactId = "sbt" } ]

Note that the Scala Steward config file `.scala-steward.conf` wasn't parsed correctly
cron4s.InvalidCron: Either DayOfMonth and DayOfWeek must have a ? expression: DownField(frequency),DownField(pullRequests)

labels: library-update, early-semver-minor, semver-spec-minor, commit-count:1

@jackkoenig is it time to re-visit this? I am unable to run sbt on my laptop with this repo without using 1.6.2

I am unable to run sbt on my laptop with this repo without using 1.6.2

That sounds weird, what version of the JVM are you using on your laptop?
We could revisit this, we'd have to drop Scala 2.12.4, which is admittedly very old but if there are any users using Chisel with it, they would be a bit burned. See I am unable to run sbt on my laptop with this repo without using 1.6.2
That being said, upgrading from 2.12.4 to 2.12.5+ is pretty easy so it's probably okay, I just don't love having to drop Scala versions due to bumping our build tool...

java -version
java version "11.0.13" 2021-10-19 LTS
Java(TM) SE Runtime Environment 18.9 (build 11.0.13+10-LTS-370)
Java HotSpot(TM) 64-Bit Server VM 18.9 (build 11.0.13+10-LTS-370, mixed mode)


Upgrade sinon-chai version

Upgrade sinon-chai version to version 3.2.0, which provides support for Sinon v6.x.

Pull Request Test Coverage Report for Build 87

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 100.0%

Totals

Change from base Build 84:
0.0%

Covered Lines:
74

Relevant Lines:
74

💛  - Coveralls


Update README.md

I have two accounts and one that commited is yunatamos

Sounds good @yunatamos!


Add param for All Users installation. Fix syntax errors.

Two changes:

Add /InstallAllUsers parameter to switch to a system-wide install.
Fix syntax errors where a value for an installer argument is provided; the help information obtained directly from the Opera installer (execute it with --help as the argument) indicates using an equals sign to join an argument with its value. I have noticed that some arguments noticeably do not work without the equals sign.

Description

Motivation and Context

This adds a sorely lacking command line argument for the installer: the ability to control the installation context (system-wide vs user-only).
How Has this Been Tested?

This has been tested locally, by pulling and installing from a Nexus Repository Manager nuget repo which I use with chocolatey.
Screenshot (if appropriate, usually isn't needed):
Types of changes

[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)
[ ] Migrated package (a package has been migrated from another repository)

Checklist:

[*] My code follows the code style of this repository.
[ ] My change requires a change to documentation (this usually means the notes in the description of a package).
[ ] I have updated the documentation accordingly (this usually means the notes in the description of a package).
[ ] All files are up to date with the latest Contributing Guidelines
[ ] The added/modified package passed install/uninstall in the chocolatey test environment.
[*] The changes only affect a single package (not including meta package).

:white_check_mark: Package verification completed without issues. PR is now pending human review

:white_check_mark: Package verification completed without issues. PR is now pending human review

:white_check_mark: Package verification completed without issues. PR is now pending human review

@Jekotia thank you for your contribution to the core team packages repository.
The changes will be part of the next version of the opera package.
I do not believe there to be necessary to provide a fix version, as the Opera developers seem to push out new releases quite regularly.


Add tabbed sections to some pages

Add horizontal separators between each function on function index pages

Please limit PRs to one feature / set of formatting changes at a time


Add Nack CRDs

https://github.com/datreeio/CRDs-catalog/issues/371
Adding NACK Crds.
Location of the CRDs.
https://github.com/nats-io/nack/blob/main/deploy/crds.yml
Generated using Crds extractor script

@eyarz can you please review and approve this?


feat(ci): switch to github action

@sferik json_pure tests are failing. I skept them as I don't understand what is the issue about. I think it is better to have tests like this to avoid further regressions and then look for the issue. I'll be less disponible next days, so here's a mergeable (IMHO) proposal
You'd have to activate Gihub Actions for the project, and branch protect master (and rename it ? <3)

Just merged this but noticed one more change that needs to be made: the build status badge in the README needs to be updated too.

Arf I forgot it... Could you add it committing directly ?
e```markdown

[![CI](https://github.com/intridea/multi_json/workflows/Test/badge.svg)](https://github.com/intridea/multi_json/actions?query=workflow%3ATest+branch%3Amaster+event%3Apush)

I could do the PR once the branch is changed otherwise :)


[BUG] Edit history does not save correctly

Describe the bug
Individual events don't seem to be saving edit history. It's strange because some events do seem to save their history, but a lot of the events don't have an edit history attached to them :/
To Reproduce
Steps to reproduce the behavior:

Go to https://tams.club/edit/history/events/07d1f5cf-b38e-458d-863a-beedcdf28b74
It doesn't seem to have an edit history :(

Expected behavior
It should create an edit history object whenever an event is created.
Screenshots or Links
Could possibly be broken by #547
Environment
N/A
Additional context
Add any other context about the problem here.

This seems to also cause the site to crash occasionally:
TypeError: Cannot read properties of null (reading 'save')
    at /app/server/app.js:202:19156
    at runMicrotasks (<anonymous>)
    at processTicksAndRejections (node:internal/process/task_queues:96:5)
node:internal/errors:477
    ErrorCaptureStackTrace(err);
    ^

ah yes... javascript errors >:((

Hmm... it seems like history entries with the resourceId of "events" are being deleted. This could potentially be caused by the deletion of repeating events (not working properly). Besides that, it seems NEW edit histories are being created correctly. Note that these issues does NOT affect the clubs or volunteering resources, only events.


Improve CI tests

[ ] All tests passed. If this feature is not already covered by the tests, I added new tests.
[x] This pull request is on the dev branch.
[x] I used gofmt for formatting the code before submitting the pull request.

Fix Pip tests - the virtual env was never activated.
Fix Gradle tests - turn off the Gradle daemon to make sure the Windows tests aren't stuck forever.
Remove branch restrictions to allow running the tests on all branches under jfrog/ repo.
Improve visibility - I changed the test name to <suite> (<os>).
Java tests - use Adopt Open JDK instead of Zulu.
Remove spaces and realign yaml.

Let's update v1 as well


DoneJS prerelease: using setVal with promises is broken.

I'm not sure where to file this.  Returning a promise from a getter is throwing the error below.  The ViewModel looks like this.  I'm using Promise.resolve to eliminate the Model as the possible cause of the error:
import Component from 'can-component';
import DefineMap from 'can-define/map/';
import './account-list.less';
import template from './account-list.stache';
import Account from 'mma-test/models/account';

export const ViewModel = DefineMap.extend({
  accounts: {
    get(val, setVal){
      return Promise.resolve(new Account.List([
        {name: 'Checking'},
        {name: 'Savings'},
      ])).then(setVal);
    }
  }
});

This template results in the error.  It probably has something with trying to iterate over a promise with #each.

  I'm probably returning the promise"  It turned out to be true, but removing the return before the promise didn't fix it, but it did send it into an infinite loop.

this.observation.get() is always undefined or an empty array, here: https://github.com/canjs/can-compute/blob/bbae2aad1f667cca9a9931ec4f9bf17e60b24d22/proto-compute.js#L365

This would almost certainly be a CanJS error.  Anyway you can create a test in can-stache?  There's a define-map test in stache.  I'm closing for an issue there.
It's odd for a property value to be a promise, and then when setVal is called, be something else.


added link for the examples of envFrom

resolved #40572 by adding link to the examples for envFrom

Hey, @dipesh-rawat thank you for your feedback. I would surely look into it and try to incorporate all the suggestion that you have made.

@dipesh-rawat I made the changes you suggested but I am still not confident that if this would work. So I just pushed the changes to show what I have worked on. I know these changes are not up to the standard but I would like some feedback.

checks are failing, what did I do wrong ?

@sftim why are my checks failing?

@KhushPatibandha Could you try to push an empty commit to re-trigger the checks?

Hi @KhushPatibandha Please restart netlify checks by force pushing an empty commit .

/label tide/merge-method-squash
If you can, please squash the commits on your branch @KhushPatibandha. You should also verify that these changes preview OK locally.

Hello @KhushPatibandha , since there have been no comments/commits on this PR despite reminders, I'll be closing it. Please note that if you find the bandwidth to address the suggestions and work on it again, feel free to issue the /reopen command.
/close


Java Model Decorators (beta)

Adds the ability to pass in an accompanying decorations file for:

Extending a class
Implementing interfaces
Adding annotations to the class, property variables, property getters, other methods
Specifying additional imports

Example usage:
plank --lang=java --java_decorations_beta=decorations.json my_model.json
decorations.json:
{
    "class": {
        "extends": "BaseModel",
        "implements": ["ModelInterface"],
        "annotations": ["CustomAnnotation"]
    },
    "constructor" : {
        "annotations": ["CustomAnnotation"]
    },
    "properties": {
        "my_property": {
            "variable": {
                "annotations": ["CustomAnnotation"]
            },
            "getter": {
                "annotations": ["CustomAnnotation"]
            }
        }
    },
    "methods": {
        "mergeFrom": {
            "annotations": ["CustomAnnotation"]
        }
    },
    "imports": [
        "com.test.package.BaseModel",
        "com.test.package.ModelInterface",
        "com.test.package.CustomAnnotation"
    ]
}

@RicoYao - Why would we do extension in the decorators file vs the schema? We have support for extends which I assume would be sufficient here

@RicoYao - Why would we do extension in the decorators file vs the schema? We have support for extends which I assume would be sufficient here

@rahul-malik Perhaps I misunderstood our last discussion, but I believe extends in the schema is meant to be used for inheriting properties, but not to actually define class extension. That was a design decision that predates my involvement, but I agree with it FWIW, as we don't want to encourage class extension.


Add 2020 speaker pictures back into static folder

@tompollard noticed that the 2020 speaker pictures were missing. This PR adds them back in via the original commit.

thanks @briangow