Reogrid slow setting style backcolor

Hi,
We're trying the reoGrid .NET control in our application.
In the grid, we have 25 columns and 75 rows.
It's a sort of calendar.
Now we have to set the backcolor for some cells (can be up to 200 cells). All different colors.
But running this functionality is very slow. It can take up to 10 seconds.
We can't take a range to speed up.
So how can this get running faster ?
I'm using sheet.cells[cell].styles.backcolor = ….
Regards
Bart

Post some code or upload a project that shows your problem.

Meanwhile find out how to speed up.
Using sheet.range instead of sheet.cells goes much faster


veleroEnabled setting removed in reconciliation loop

Describe the bug:
When a Vault CR is created (or edited) with veleroEnabled: true shortly after the reconciliation loop removes this from the Vault CR object.
Expected behaviour:
Velero annotations and pod added to Vault servers.
Steps to reproduce the bug:
Create Vault without veleroEnabled setting and wait to initialize.
Set veleroEnabled: true on Vault CR object, then wait for it to disappear.
Additional context:
Using a RAFT-storage backed 5-replica Vault deployment we're trying to enable Velero backup. Apparently the operator disregards the veleroEnabled setting which prevents backing up.
Environment details:

Kubernetes version (e.g. v1.10.2):

Server Version: version.Info{Major:"1", Minor:"15+", GitVersion:"v1.15.11-eks-af3caf", GitCommit:"af3caf6136cd355f467083651cc1010a499f59b1", GitTreeState:"clean", BuildDate:"2020-03-27T21:51:36Z", GoVersion:"go1.12.17", Compiler:"gc", Platform:"linux/amd64"}

Cloud-provider/provisioner: EKS
bank-vaults version (e.g. 0.4.17): latest
Install method: Helm chart 1.0.1
Logs from the misbehaving component (and any other relevant logs):
Resource definition (possibly in YAML format) that caused the issue, without sensitive data:

apiVersion: vault.banzaicloud.com/v1alpha1
kind: Vault
metadata:
  labels:
    app.kubernetes.io/name: vault
    vault_cr: vault
  name: vault
  namespace: vault-operator
spec:
  annotations: null
  bankVaultsImage: banzaicloud/bank-vaults:latest
  config:
    api_addr: https://vault.vault-operator:8200
    cluster_addr: https://${.Env.POD_NAME}:8201
    cluster_name: vault
    default_lease_ttl: 30m
    listener:
    - tcp:
        address: <IP_ADDRESS>:8200
        tls_cert_file: /vault/tls/server.crt
        tls_key_file: /vault/tls/server.key
    storage:
      raft:
        path: /vault/raft
    telemetry:
      statsd_address: localhost:9125
    ui: true
  credentialsConfig:
    env: ""
    path: ""
    secretName: ""
  etcdSize: 0
  etcdVersion: ""
  externalConfig:
    secrets:
    - description: General secrets.
      options:
        version: 2
      path: secret
      type: kv
    startupSecrets:
    - data:
        data:
          AWS_ACCESS_KEY_ID: secretId
          AWS_SECRET_ACCESS_KEY: s3cr3t
      path: secret/data/accounts/aws
      type: kv
  fluentdConfig: ""
  fluentdEnabled: false
  fluentdImage: ""
  image: vault:1.3.2
  nodeAffinity: {}
  nodeSelector: null
  podAntiAffinity: ""
  raftLeaderAddress: ""
  securityContext: {}
  serviceAccount: vault
  servicePorts:
    api-port: 8200
    cluster-port: 8201
    ext-api-port: 8300
    ext-clu-port: 8301
  serviceType: ClusterIP
  size: 5
  statsdDisabled: false
  statsdImage: ""
  tolerations: null
  unsealConfig:
    kubernetes:
      secretName: ""
      secretNamespace: vault-operator
    options: {}
  vaultAnnotations:
    type/instance: vault
  vaultConfigurerAnnotations:
    type/instance: vaultconfigurer
  vaultConfigurerLabels:
    example.com/log-format: string
  vaultConfigurerPodSpec:
    containers: null
  vaultEnvsConfig: null
  vaultLabels:
    example.com/log-format: json

/kind bug

Can't reproduce with the following CR with latest Bank-Vaults, can you make sure that veleroEnabled: true has the right level of indentation?
apiVersion: "vault.banzaicloud.com/v1alpha1"
kind: "Vault"
metadata:
  name: "vault"
spec:
  size: 1
  image: vault:1.4.2
  bankVaultsImage: banzaicloud/bank-vaults:latest

  # Common annotations for all created resources
  annotations:
    common/annotation: "true"

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

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

  # Vault Pods , Services and TLS Secret labels
  vaultLabels:
    example.com/log-format: "json"

  # Vault Configurer Pods and Services labels
  vaultConfigurerLabels:
    example.com/log-format: "string"

  # Support for nodeAffinity Rules
  # nodeAffinity:
  #   requiredDuringSchedulingIgnoredDuringExecution:
  #     nodeSelectorTerms:
  #     - matchExpressions:
  #       - key : "node-role.kubernetes.io/your_role"
  #         operator: In
  #         values: ["true"]

  # Support for pod nodeSelector rules to control which nodes can be chosen to run
  # the given pods
  # nodeSelector:
  #   "node-role.kubernetes.io/your_role": "true"

  # Support for node tolerations that work together with node taints to control
  # the pods that can like on a node
  # tolerations:
  # - effect: NoSchedule
  #   key: node-role.kubernetes.io/your_role
  #   operator: Equal
  #   value: "true"

  # 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

  # Specify existing secret contains TLS certificate (accepted secret type: kubernetes.io/tls)
  # If it is set, generating certificate will be disabled
  # existingTlsSecretName: selfsigned-cert-tls

  # Specify threshold for renewing certificates. Valid time units are "ns", "us", "ms", "s", "m", "h".
  # tlsExpiryThreshold: 168h

  # Request an Ingress controller with the default configuration
  ingress:
    # Specify Ingress object annotations here, if TLS is enabled (which is by default)
    # the operator will add NGINX, Traefik and HAProxy Ingress compatible annotations
    # to support TLS backends
    annotations:
    # Override the default Ingress specification here
    # This follows the same format as the standard Kubernetes Ingress
    # See: https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.13/#ingressspec-v1beta1-extensions
    spec: {}

  # Use local disk to store Vault file data, see config section.
  volumes:
    - name: vault-file
      persistentVolumeClaim:
        claimName: vault-file

  volumeMounts:
    - name: vault-file
      mountPath: /vault/file

  # Support for distributing the generated CA certificate Secret to other namespaces.
  # Define a list of namespaces or use ["*"] for all namespaces.
  caNamespaces:
    - "vswh"

  # Describe where you would like to store the Vault unseal keys and root token.
  unsealConfig:
    options:
      # The preFlightChecks flag enables unseal and root token storage tests
      # This is true by default
      preFlightChecks: true
    kubernetes:
      secretNamespace: default

  # A YAML representation of a final vault config file.
  # See https://www.vaultproject.io/docs/configuration/ for more information.
  config:
    storage:
      file:
        path: "${ .Env.VAULT_STORAGE_FILE }" # An example how Vault config environment interpolation can be used
    listener:
      tcp:
        address: "<IP_ADDRESS>:8200"
        # Uncommenting the following line and deleting tls_cert_file and tls_key_file disables TLS
        # tls_disable: true
        tls_cert_file: /vault/tls/server.crt
        tls_key_file: /vault/tls/server.key
    telemetry:
      statsd_address: localhost:9125
    ui: true

  # See: https://github.com/banzaicloud/bank-vaults#example-external-vault-configuration for more details.
  externalConfig:
    policies:
      - name: allow_secrets
        rules: path "secret/*" {
          capabilities = ["create", "read", "update", "delete", "list"]
          }
      - name: allow_pki
        rules: path "pki/*" {
          capabilities = ["create", "read", "update", "delete", "list"]
          }
    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-secrets-webhook", "vault"]
            bound_service_account_namespaces: ["default", "vswh"]
            policies: ["allow_secrets", "allow_pki"]
            ttl: 1h

    secrets:
      - path: secret
        type: kv
        description: General secrets.
        options:
          version: 2

      - type: pki
        description: Vault PKI Backend
        config:
          default_lease_ttl: 168h
          max_lease_ttl: 720h
        configuration:
          config:
          - name: urls
            issuing_certificates: https://vault.default:8200/v1/pki/ca
            crl_distribution_points: https://vault.default:8200/v1/pki/crl
          root/generate:
          - name: internal
            common_name: vault.default
          roles:
          - name: default
            allowed_domains: localhost,pod,svc,default
            allow_subdomains: true
            generate_lease: true
            ttl: 1m

    # 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/accounts/aws
        data:
          data:
            AWS_ACCESS_KEY_ID: secretId
            AWS_SECRET_ACCESS_KEY: s3cr3t
      - type: kv
        path: secret/data/dockerrepo
        data:
          data:
            DOCKER_REPO_USER: dockerrepouser
            DOCKER_REPO_PASSWORD: dockerrepopassword
      - type: kv
        path: secret/data/mysql
        data:
          data:
            MYSQL_ROOT_PASSWORD: s3cr3t
            MYSQL_PASSWORD: 3xtr3ms3cr3t

  vaultEnvsConfig:
    - name: VAULT_LOG_LEVEL
      value: debug
    - name: VAULT_STORAGE_FILE
      value: "/vault/file"

  # Marks presence of Istio, which influences things like port namings
  istioEnabled: false

  veleroEnabled: true

---
apiVersion: v1
kind: PersistentVolumeClaim
metadata:
  name: vault-file
spec:
  # https://kubernetes.io/docs/concepts/storage/persistent-volumes/#class-1
  # storageClassName: ""
  accessModes:
    - ReadWriteOnce
  resources:
    requests:
      storage: 1Gi

@bonifaido : Creating the Vault you shared with a service account and role like this still ends up removing the veleroEnabled setting.
Tried:
apiVersion: v1
kind: ServiceAccount
metadata:
  name: vault
---
apiVersion: rbac.authorization.k8s.io/v1
kind: Role
metadata:
  name: vault-secrets
  labels:
    app.kubernetes.io/name: vault
rules:
- apiGroups:
  - ""
  resources:
  - secrets
  verbs:
  - get
  - list
  - watch
  - update
  - patch
  - delete
  - create
---
apiVersion: rbac.authorization.k8s.io/v1
kind: RoleBinding
metadata:
  name: vault
roleRef:
  apiGroup: rbac.authorization.k8s.io
  kind: Role
  name: vault-secrets
subjects:
- kind: ServiceAccount
  name: vault
---
apiVersion: "vault.banzaicloud.com/v1alpha1"
kind: "Vault"
metadata:
  name: "vault"
spec:
  size: 1
  image: vault:1.4.2
  bankVaultsImage: banzaicloud/bank-vaults:latest

  # Common annotations for all created resources
  annotations:
    common/annotation: "true"

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

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

  # Vault Pods , Services and TLS Secret labels
  vaultLabels:
    example.com/log-format: "json"

  # Vault Configurer Pods and Services labels
  vaultConfigurerLabels:
    example.com/log-format: "string"

  # Support for nodeAffinity Rules
  # nodeAffinity:
  #   requiredDuringSchedulingIgnoredDuringExecution:
  #     nodeSelectorTerms:
  #     - matchExpressions:
  #       - key : "node-role.kubernetes.io/your_role"
  #         operator: In
  #         values: ["true"]

  # Support for pod nodeSelector rules to control which nodes can be chosen to run
  # the given pods
  # nodeSelector:
  #   "node-role.kubernetes.io/your_role": "true"

  # Support for node tolerations that work together with node taints to control
  # the pods that can like on a node
  # tolerations:
  # - effect: NoSchedule
  #   key: node-role.kubernetes.io/your_role
  #   operator: Equal
  #   value: "true"

  # 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

  # Specify existing secret contains TLS certificate (accepted secret type: kubernetes.io/tls)
  # If it is set, generating certificate will be disabled
  # existingTlsSecretName: selfsigned-cert-tls

  # Specify threshold for renewing certificates. Valid time units are "ns", "us", "ms", "s", "m", "h".
  # tlsExpiryThreshold: 168h

  # Request an Ingress controller with the default configuration
  ingress:
    # Specify Ingress object annotations here, if TLS is enabled (which is by default)
    # the operator will add NGINX, Traefik and HAProxy Ingress compatible annotations
    # to support TLS backends
    annotations:
    # Override the default Ingress specification here
    # This follows the same format as the standard Kubernetes Ingress
    # See: https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.13/#ingressspec-v1beta1-extensions
    spec: {}

  # Use local disk to store Vault file data, see config section.
  volumes:
    - name: vault-file
      persistentVolumeClaim:
        claimName: vault-file

  volumeMounts:
    - name: vault-file
      mountPath: /vault/file

  # Support for distributing the generated CA certificate Secret to other namespaces.
  # Define a list of namespaces or use ["*"] for all namespaces.
  caNamespaces:
    - "vswh"

  # Describe where you would like to store the Vault unseal keys and root token.
  unsealConfig:
    options:
      # The preFlightChecks flag enables unseal and root token storage tests
      # This is true by default
      preFlightChecks: true
    kubernetes:
      secretNamespace: test-velero-vault

  # A YAML representation of a final vault config file.
  # See https://www.vaultproject.io/docs/configuration/ for more information.
  config:
    storage:
      file:
        path: "${ .Env.VAULT_STORAGE_FILE }" # An example how Vault config environment interpolation can be used
    listener:
      tcp:
        address: "<IP_ADDRESS>:8200"
        # Uncommenting the following line and deleting tls_cert_file and tls_key_file disables TLS
        # tls_disable: true
        tls_cert_file: /vault/tls/server.crt
        tls_key_file: /vault/tls/server.key
    telemetry:
      statsd_address: localhost:9125
    ui: true

  # See: https://github.com/banzaicloud/bank-vaults#example-external-vault-configuration for more details.
  externalConfig:
    policies:
      - name: allow_secrets
        rules: path "secret/*" {
          capabilities = ["create", "read", "update", "delete", "list"]
          }
      - name: allow_pki
        rules: path "pki/*" {
          capabilities = ["create", "read", "update", "delete", "list"]
          }
    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-secrets-webhook", "vault"]
            bound_service_account_namespaces: ["default", "vswh"]
            policies: ["allow_secrets", "allow_pki"]
            ttl: 1h

    secrets:
      - path: secret
        type: kv
        description: General secrets.
        options:
          version: 2

      - type: pki
        description: Vault PKI Backend
        config:
          default_lease_ttl: 168h
          max_lease_ttl: 720h
        configuration:
          config:
          - name: urls
            issuing_certificates: https://vault.default:8200/v1/pki/ca
            crl_distribution_points: https://vault.default:8200/v1/pki/crl
          root/generate:
          - name: internal
            common_name: vault.default
          roles:
          - name: default
            allowed_domains: localhost,pod,svc,default
            allow_subdomains: true
            generate_lease: true
            ttl: 1m

    # 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/accounts/aws
        data:
          data:
            AWS_ACCESS_KEY_ID: secretId
            AWS_SECRET_ACCESS_KEY: s3cr3t
      - type: kv
        path: secret/data/dockerrepo
        data:
          data:
            DOCKER_REPO_USER: dockerrepouser
            DOCKER_REPO_PASSWORD: dockerrepopassword
      - type: kv
        path: secret/data/mysql
        data:
          data:
            MYSQL_ROOT_PASSWORD: s3cr3t
            MYSQL_PASSWORD: 3xtr3ms3cr3t

  vaultEnvsConfig:
    - name: VAULT_LOG_LEVEL
      value: debug
    - name: VAULT_STORAGE_FILE
      value: "/vault/file"

  # Marks presence of Istio, which influences things like port namings
  istioEnabled: false
  veleroEnabled: true
---
apiVersion: v1
kind: PersistentVolumeClaim
metadata:
  name: vault-file
spec:
  # https://kubernetes.io/docs/concepts/storage/persistent-volumes/#class-1
  # storageClassName: ""
  accessModes:
    - ReadWriteOnce
  resources:
    requests:
      storage: 1Gi

Querying the Vault CR after the pod is initialized and is available shows that even though the veleroEnabled: true was applied, it's no longer part of the CR (search for veleroEnabled in  kubectl.kubernetes.io/last-applied-configuration :
apiVersion: vault.banzaicloud.com/v1alpha1
kind: Vault
metadata:
  annotations:
    kubectl.kubernetes.io/last-applied-configuration: |
      {"apiVersion":"vault.banzaicloud.com/v1alpha1","kind":"Vault","metadata":{"annotations":{},"name":"vault","namespace":"test-velero-vault"},"spec":{"annotations":{"common/annotation":"true"},"bankVaultsImage":"banzaicloud/bank-vaults:latest","caNamespaces":["vswh"],"config":{"listener":{"tcp":{"address":"<IP_ADDRESS>:8200","tls_cert_file":"/vault/tls/server.crt","tls_key_file":"/vault/tls/server.key"}},"storage":{"file":{"path":"${ .Env.VAULT_STORAGE_FILE }"}},"telemetry":{"statsd_address":"localhost:9125"},"ui":true},"externalConfig":{"auth":[{"roles":[{"bound_service_account_names":["default","vault-secrets-webhook","vault"],"bound_service_account_namespaces":["default","vswh"],"name":"default","policies":["allow_secrets","allow_pki"],"ttl":"1h"}],"type":"kubernetes"}],"policies":[{"name":"allow_secrets","rules":"path \"secret/*\" { capabilities = [\"create\", \"read\", \"update\", \"delete\", \"list\"] }"},{"name":"allow_pki","rules":"path \"pki/*\" { capabilities = [\"create\", \"read\", \"update\", \"delete\", \"list\"] }"}],"secrets":[{"description":"General secrets.","options":{"version":2},"path":"secret","type":"kv"},{"config":{"default_lease_ttl":"168h","max_lease_ttl":"720h"},"configuration":{"config":[{"crl_distribution_points":"https://vault.default:8200/v1/pki/crl","issuing_certificates":"https://vault.default:8200/v1/pki/ca","name":"urls"}],"roles":[{"allow_subdomains":true,"allowed_domains":"localhost,pod,svc,default","generate_lease":true,"name":"default","ttl":"1m"}],"root/generate":[{"common_name":"vault.default","name":"internal"}]},"description":"Vault PKI Backend","type":"pki"}],"startupSecrets":[{"data":{"data":{"AWS_ACCESS_KEY_ID":"secretId","AWS_SECRET_ACCESS_KEY":"s3cr3t"}},"path":"secret/data/accounts/aws","type":"kv"},{"data":{"data":{"DOCKER_REPO_PASSWORD":"dockerrepopassword","DOCKER_REPO_USER":"dockerrepouser"}},"path":"secret/data/dockerrepo","type":"kv"},{"data":{"data":{"MYSQL_PASSWORD":"3xtr3ms3cr3t","MYSQL_ROOT_PASSWORD":"s3cr3t"}},"path":"secret/data/mysql","type":"kv"}]},"image":"vault:1.4.2","ingress":{"annotations":null,"spec":{}},"istioEnabled":false,"serviceAccount":"vault","serviceType":"ClusterIP","size":1,"unsealConfig":{"kubernetes":{"secretNamespace":"test-velero-vault"},"options":{"preFlightChecks":true}},"vaultAnnotations":{"type/instance":"vault"},"vaultConfigurerAnnotations":{"type/instance":"vaultconfigurer"},"vaultConfigurerLabels":{"example.com/log-format":"string"},"vaultEnvsConfig":[{"name":"VAULT_LOG_LEVEL","value":"debug"},{"name":"VAULT_STORAGE_FILE","value":"/vault/file"}],"vaultLabels":{"example.com/log-format":"json"},"veleroEnabled":true,"volumeMounts":[{"mountPath":"/vault/file","name":"vault-file"}],"volumes":[{"name":"vault-file","persistentVolumeClaim":{"claimName":"vault-file"}}]}}
  creationTimestamp: "2020-06-18T22:57:41Z"
  generation: 4
  name: vault
  namespace: test-velero-vault
  resourceVersion: "73962989"
  selfLink: /apis/vault.banzaicloud.com/v1alpha1/namespaces/test-velero-vault/vaults/vault
  uid: c12895e7-b160-4b35-baef-40f9576f0226
spec:
  annotations:
    common/annotation: "true"
  bankVaultsImage: banzaicloud/bank-vaults:latest
  caNamespaces:
  - vswh
  config:
    listener:
      tcp:
        address: <IP_ADDRESS>:8200
        tls_cert_file: /vault/tls/server.crt
        tls_key_file: /vault/tls/server.key
    storage:
      file:
        path: ${ .Env.VAULT_STORAGE_FILE }
    telemetry:
      statsd_address: localhost:9125
    ui: true
  credentialsConfig:
    env: ""
    path: ""
    secretName: ""
  envsConfig: null
  etcdSize: 0
  etcdVersion: ""
  externalConfig:
    auth:
    - roles:
      - bound_service_account_names:
        - default
        - vault-secrets-webhook
        - vault
        bound_service_account_namespaces:
        - default
        - vswh
        name: default
        policies:
        - allow_secrets
        - allow_pki
        ttl: 1h
      type: kubernetes
    policies:
    - name: allow_secrets
      rules: path "secret/*" { capabilities = ["create", "read", "update", "delete",
        "list"] }
    - name: allow_pki
      rules: path "pki/*" { capabilities = ["create", "read", "update", "delete",
        "list"] }
    secrets:
    - description: General secrets.
      options:
        version: 2
      path: secret
      type: kv
    - config:
        default_lease_ttl: 168h
        max_lease_ttl: 720h
      configuration:
        config:
        - crl_distribution_points: https://vault.default:8200/v1/pki/crl
          issuing_certificates: https://vault.default:8200/v1/pki/ca
          name: urls
        roles:
        - allow_subdomains: true
          allowed_domains: localhost,pod,svc,default
          generate_lease: true
          name: default
          ttl: 1m
        root/generate:
        - common_name: vault.default
          name: internal
      description: Vault PKI Backend
      type: pki
    startupSecrets:
    - data:
        data:
          AWS_ACCESS_KEY_ID: secretId
          AWS_SECRET_ACCESS_KEY: s3cr3t
      path: secret/data/accounts/aws
      type: kv
    - data:
        data:
          DOCKER_REPO_PASSWORD: dockerrepopassword
          DOCKER_REPO_USER: dockerrepouser
      path: secret/data/dockerrepo
      type: kv
    - data:
        data:
          MYSQL_PASSWORD: 3xtr3ms3cr3t
          MYSQL_ROOT_PASSWORD: s3cr3t
      path: secret/data/mysql
      type: kv
  fluentdConfig: ""
  fluentdEnabled: false
  fluentdImage: ""
  image: vault:1.4.2
  ingress:
    spec: {}
  nodeAffinity: {}
  nodeSelector: null
  podAntiAffinity: ""
  raftLeaderAddress: ""
  securityContext: {}
  serviceAccount: vault
  servicePorts: null
  serviceType: ClusterIP
  size: 1
  statsdDisabled: false
  statsdImage: ""
  tolerations: null
  unsealConfig:
    kubernetes:
      secretName: ""
      secretNamespace: test-velero-vault
    options:
      preFlightChecks: true
  vaultAnnotations:
    type/instance: vault
  vaultConfigurerAnnotations:
    type/instance: vaultconfigurer
  vaultConfigurerLabels:
    example.com/log-format: string
  vaultConfigurerPodSpec:
    containers: null
  vaultEnvsConfig:
  - name: VAULT_LOG_LEVEL
    value: debug
  - name: VAULT_STORAGE_FILE
    value: /vault/file
  vaultLabels:
    example.com/log-format: json
  vaultPodSpec:
    containers: null
  volumeMounts:
  - mountPath: /vault/file
    name: vault-file
  volumes:
  - name: vault-file
    persistentVolumeClaim:
      claimName: vault-file
  watchedSecretsAnnotations: null
  watchedSecretsLabels: null
status:
  leader: vault-0
  nodes:
  - vault-0

@bonifaido : Have you had a chance to take a look?


⚠ Secret Website 2 has degraded performance

In 2b2054c, Secret Website 2 ($SECRET_WEBSITE_2) experienced degraded performance:

HTTP code: 200
Response time: 5091 ms

Resolved: Secret Website 2 performance has improved in 5081d41.


download release

Hi @AnnieLR can you please review the changes I've made here.
Feel free to correct anything you like...
Thank you!


Set UefiCapabilty for all hypervisors in hostresponse

Description
Sets the ueficapability flag for all hypervisor types, not just KVM
Types of changes

[ ] Breaking change (fix or feature that would cause existing functionality to change)
[ ] New feature (non-breaking change which adds functionality)
[x] Bug fix (non-breaking change which fixes an issue)
[ ] Enhancement (improves an existing feature and functionality)
[ ] Cleanup (Code refactoring and cleanup, that may add test cases)

Bug Severity

[ ] BLOCKER
[ ] Critical
[ ] Major
[ ] Minor
[x] Trivial

How Has This Been Tested?
Before :
(localhost) 🐱 > list hosts filter=name,ueficapability,
{
  "count": 5,
  "host": [
    {
      "name": "s-2-VM"
    },
    {
      "name": "SimulatedAgent.92502eaf-4bd2-4f79-a16b-ef71b7283a51"
    },
    {
      "name": "SimulatedAgent.ce1e03f7-7240-4655-9a7a-6fa81286c289"
    },
    {
      "name": "SimulatedAgent.225c478e-9777-450f-ac80-c4657b0beeb3"
    },
    {
      "name": "SimulatedAgent.9c33d117-7fef-46aa-a806-0ff58a81d7c7"
    }
  ]
}

After :
(localhost) 🐱 > list hosts filter=name,ueficapability,
{
  "count": 5,
  "host": [
    {
      "name": "s-2-VM"
    },
    {
      "name": "SimulatedAgent.92502eaf-4bd2-4f79-a16b-ef71b7283a51",
      "ueficapability": false
    },
    {
      "name": "SimulatedAgent.ce1e03f7-7240-4655-9a7a-6fa81286c289",
      "ueficapability": false
    },
    {
      "name": "SimulatedAgent.225c478e-9777-450f-ac80-c4657b0beeb3",
      "ueficapability": true
    },
    {
      "name": "SimulatedAgent.9c33d117-7fef-46aa-a806-0ff58a81d7c7",
      "ueficapability": true
    }
  ]
}

@blueorangutan package

@davidjumani a Jenkins job has been kicked to build packages. It will be bundled with  KVM, XenServer and VMware SystemVM templates. I'll keep you posted as I make progress.

Packaging result: :heavy_check_mark: el7 :heavy_check_mark: el8 :heavy_check_mark: debian :heavy_check_mark: suse15. SL-JID 2929

@davidjumani a Trillian-Jenkins test job (centos7 mgmt + kvm-centos7) has been kicked to run smoke tests

Trillian test result (tid-3663)
Environment: kvm-centos7 (x2), Advanced Networking with Mgmt server 7
Total time taken: 31503 seconds
Marvin logs: https://github.com/blueorangutan/acs-prs/releases/download/trillian/pr6140-t3663-kvm-centos7.zip
Smoke tests completed. 92 look OK, 0 have errors
Only failed tests results shown below:

Test
Result
Time (s)
Test File


Fix the crash on firmware master, fix the stop list to make it not clip on round

Let me know if I should adjust the train times list in the same way, or if there will be any side effects to removing InverterLayer.

The InverterLayer was what caused the dividing lines to show up — they're missing now:

You've also removed the time display, which is somewhat important in a schedule app.

I'll leave the crash to you, then, seeing as you're the SDK wizard. This PR is just the stop list change now.

Thanks!


made my change

Added my name on line 100

Please I am sorry for all the trouble we have caused you but count it all joy. Your PR is about to be merged and you will be able to see your name on this url.
To enable me to do this, READ the README again carefully, update your code with the latest and push the update. I am here for you for the next 6 hours before I close the PR so you can initiate a fresh PR which will be easier to merge.


Windows: Updates for virtual user account

Signed-off-by: John Howard<EMAIL_ADDRESS>TP5 introduces a virtual account for apps running in containers. This updates the tests which were checking for local system ("SYSTEM") on TP4 to be compatible with TP5 once that CI comes online.
Cute animals below :)

:heart_eyes_cat: LGTM

userns failure is unrelated to this change. Just being its usual flaky self.

LGTM


The model: gpt-4 does not exist

From a fresh install. Seems after end of month everyone will have access to gpt-4. After clicking research I get:
Exception in ASGI application
Traceback (most recent call last):
File "/mnt/c/Users/Kontor/Github Repos/gpt-researcher/.venv/lib/python3.10/site-packages/uvicorn/protocols/websockets/wsproto_impl.py", line 249, in run_asgi
result = await self.app(self.scope, self.receive, self.send)
File "/mnt/c/Users/Kontor/Github Repos/gpt-researcher/.venv/lib/python3.10/site-packages/uvicorn/middleware/proxy_headers.py", line 78, in call
return await self.app(scope, receive, send)
File "/mnt/c/Users/Kontor/Github Repos/gpt-researcher/.venv/lib/python3.10/site-packages/fastapi/applications.py", line 289, in call
await super().call(scope, receive, send)
File "/mnt/c/Users/Kontor/Github Repos/gpt-researcher/.venv/lib/python3.10/site-packages/starlette/applications.py", line 122, in call
await self.middleware_stack(scope, receive, send)
File "/mnt/c/Users/Kontor/Github Repos/gpt-researcher/.venv/lib/python3.10/site-packages/starlette/middleware/errors.py", line 149, in call
await self.app(scope, receive, send)
File "/mnt/c/Users/Kontor/Github Repos/gpt-researcher/.venv/lib/python3.10/site-packages/starlette/middleware/exceptions.py", line 79, in call
raise exc
File "/mnt/c/Users/Kontor/Github Repos/gpt-researcher/.venv/lib/python3.10/site-packages/starlette/middleware/exceptions.py", line 68, in call
await self.app(scope, receive, sender)
File "/mnt/c/Users/Kontor/Github Repos/gpt-researcher/.venv/lib/python3.10/site-packages/fastapi/middleware/asyncexitstack.py", line 20, in call
raise e
File "/mnt/c/Users/Kontor/Github Repos/gpt-researcher/.venv/lib/python3.10/site-packages/fastapi/middleware/asyncexitstack.py", line 17, in call
await self.app(scope, receive, send)
File "/mnt/c/Users/Kontor/Github Repos/gpt-researcher/.venv/lib/python3.10/site-packages/starlette/routing.py", line 718, in call
await route.handle(scope, receive, send)
File "/mnt/c/Users/Kontor/Github Repos/gpt-researcher/.venv/lib/python3.10/site-packages/starlette/routing.py", line 341, in handle
await self.app(scope, receive, send)
File "/mnt/c/Users/Kontor/Github Repos/gpt-researcher/.venv/lib/python3.10/site-packages/starlette/routing.py", line 82, in app
await func(session)
File "/mnt/c/Users/Kontor/Github Repos/gpt-researcher/.venv/lib/python3.10/site-packages/fastapi/routing.py", line 324, in app
await dependant.call(**values)
File "/mnt/c/Users/Kontor/Github Repos/gpt-researcher/main.py", line 50, in websocket_endpoint
await manager.start_streaming(task, report_type, agent, websocket)
File "/mnt/c/Users/Kontor/Github Repos/gpt-researcher/agent/run.py", line 38, in start_streaming
report, path = await run_agent(task, report_type, agent, websocket)
File "/mnt/c/Users/Kontor/Github Repos/gpt-researcher/agent/run.py", line 50, in run_agent
await assistant.conduct_research()
File "/mnt/c/Users/Kontor/Github Repos/gpt-researcher/agent/research_agent.py", line 133, in conduct_research
search_queries = await self.create_search_queries()
File "/mnt/c/Users/Kontor/Github Repos/gpt-researcher/agent/research_agent.py", line 89, in create_search_queries
result = await self.call_agent(prompts.generate_search_queries_prompt(self.question))
File "/mnt/c/Users/Kontor/Github Repos/gpt-researcher/agent/research_agent.py", line 76, in call_agent
answer = create_chat_completion(
File "/mnt/c/Users/Kontor/Github Repos/gpt-researcher/agent/llm_utils.py", line 48, in create_chat_completion
response = send_chat_completion_request(
File "/mnt/c/Users/Kontor/Github Repos/gpt-researcher/agent/llm_utils.py", line 69, in send_chat_completion_request
result = openai.ChatCompletion.create(
File "/mnt/c/Users/Kontor/Github Repos/gpt-researcher/.venv/lib/python3.10/site-packages/openai/api_resources/chat_completion.py", line 25, in create
return super().create(*args, **kwargs)
File "/mnt/c/Users/Kontor/Github Repos/gpt-researcher/.venv/lib/python3.10/site-packages/openai/api_resources/abstract/engine_api_resource.py", line 153, in create
response, _, api_key = requestor.request(
File "/mnt/c/Users/Kontor/Github Repos/gpt-researcher/.venv/lib/python3.10/site-packages/openai/api_requestor.py", line 298, in request
resp, got_stream = self._interpret_response(result, stream)
File "/mnt/c/Users/Kontor/Github Repos/gpt-researcher/.venv/lib/python3.10/site-packages/openai/api_requestor.py", line 700, in _interpret_response
self._interpret_response_line(
File "/mnt/c/Users/Kontor/Github Repos/gpt-researcher/.venv/lib/python3.10/site-packages/openai/api_requestor.py", line 763, in _interpret_response_line
raise self.handle_error_response(
openai.error.InvalidRequestError: The model: gpt-4 does not exist

Yeah it shows no access. they said "we gave all API users who have a history of successful payments access to the GPT-4 API (8k). We plan to open up access to new developers by the end of July 2023".
In the meanwhile you can change it to gpt3.5 in the config file just to see it runs.

I made the following change in the config file:
-        self.smart_llm_model = os.getenv("SMART_LLM_MODEL", "gpt-4")
+        self.smart_llm_model = os.getenv("SMART_LLM_MODEL", "gpt-3.5-turbo-16k")

But I get the following error:
ERROR:    Exception in ASGI application
Traceback (most recent call last):
  File "/home/ec2-user/.local/lib/python3.9/site-packages/uvicorn/protocols/websockets/wsproto_impl.py", line 249, in run_asgi
    result = await self.app(self.scope, self.receive, self.send)
  File "/home/ec2-user/.local/lib/python3.9/site-packages/uvicorn/middleware/proxy_headers.py", line 78, in __call__
    return await self.app(scope, receive, send)
  File "/home/ec2-user/.local/lib/python3.9/site-packages/fastapi/applications.py", line 289, in __call__
    await super().__call__(scope, receive, send)
  File "/home/ec2-user/.local/lib/python3.9/site-packages/starlette/applications.py", line 122, in __call__
    await self.middleware_stack(scope, receive, send)
  File "/home/ec2-user/.local/lib/python3.9/site-packages/starlette/middleware/errors.py", line 149, in __call__
    await self.app(scope, receive, send)
  File "/home/ec2-user/.local/lib/python3.9/site-packages/starlette/middleware/exceptions.py", line 68, in __call__
    await self.app(scope, receive, sender)
  File "/home/ec2-user/.local/lib/python3.9/site-packages/fastapi/middleware/asyncexitstack.py", line 17, in __call__
    await self.app(scope, receive, send)
  File "/home/ec2-user/.local/lib/python3.9/site-packages/starlette/routing.py", line 718, in __call__
    await route.handle(scope, receive, send)
  File "/home/ec2-user/.local/lib/python3.9/site-packages/starlette/routing.py", line 341, in handle
    await self.app(scope, receive, send)
  File "/home/ec2-user/.local/lib/python3.9/site-packages/starlette/routing.py", line 82, in app
    await func(session)
  File "/home/ec2-user/.local/lib/python3.9/site-packages/fastapi/routing.py", line 324, in app
    await dependant.call(**values)
  File "/home/ec2-user/gpt-researcher/main.py", line 50, in websocket_endpoint
    await manager.start_streaming(task, report_type, agent, websocket)
  File "/home/ec2-user/gpt-researcher/agent/run.py", line 38, in start_streaming
    report, path = await run_agent(task, report_type, agent, websocket)
  File "/home/ec2-user/gpt-researcher/agent/run.py", line 43, in run_agent
    check_openai_api_key()
  File "/home/ec2-user/gpt-researcher/config/config.py", line 82, in check_openai_api_key
    exit(1)
  File "/usr/lib64/python3.9/_sitebuiltins.py", line 26, in __call__
    raise SystemExit(code)
SystemExit: 1

I can't see what is causing this in the code.

Please do the following:
      self.fast_llm_model = os.getenv("FAST_LLM_MODEL", "gpt-3.5-turbo-16k")
      self.smart_llm_model = os.getenv("SMART_LLM_MODEL", "gpt-3.5-turbo-16k")

That's what I did. I also found that gpt-4 is referenced in research_agent.py, and changed it there as well. Now I'm getting the following error:
ERROR:    Exception in ASGI application
Traceback (most recent call last):
File "/home/ec2-user/.local/lib/python3.9/site-packages/uvicorn/protocols/websockets/wsproto_impl.py", line 249, in run_asgi
result = await self.app(self.scope, self.receive, self.send)
File "/home/ec2-user/.local/lib/python3.9/site-packages/uvicorn/middleware/proxy_headers.py", line 78, in call
return await self.app(scope, receive, send)
File "/home/ec2-user/.local/lib/python3.9/site-packages/fastapi/applications.py", line 289, in call
await super().call(scope, receive, send)
File "/home/ec2-user/.local/lib/python3.9/site-packages/starlette/applications.py", line 122, in call
await self.middleware_stack(scope, receive, send)
File "/home/ec2-user/.local/lib/python3.9/site-packages/starlette/middleware/errors.py", line 149, in call
await self.app(scope, receive, send)
File "/home/ec2-user/.local/lib/python3.9/site-packages/starlette/middleware/exceptions.py", line 79, in call
raise exc
File "/home/ec2-user/.local/lib/python3.9/site-packages/starlette/middleware/exceptions.py", line 68, in call
await self.app(scope, receive, sender)
File "/home/ec2-user/.local/lib/python3.9/site-packages/fastapi/middleware/asyncexitstack.py", line 20, in call
raise e
File "/home/ec2-user/.local/lib/python3.9/site-packages/fastapi/middleware/asyncexitstack.py", line 17, in call
await self.app(scope, receive, send)
File "/home/ec2-user/.local/lib/python3.9/site-packages/starlette/routing.py", line 718, in call
await route.handle(scope, receive, send)
File "/home/ec2-user/.local/lib/python3.9/site-packages/starlette/routing.py", line 341, in handle
await self.app(scope, receive, send)
File "/home/ec2-user/.local/lib/python3.9/site-packages/starlette/routing.py", line 82, in app
await func(session)
File "/home/ec2-user/.local/lib/python3.9/site-packages/fastapi/routing.py", line 324, in app
await dependant.call(**values)
File "/home/ec2-user/gpt-researcher/main.py", line 50, in websocket_endpoint
await manager.start_streaming(task, report_type, agent, websocket)
File "/home/ec2-user/gpt-researcher/agent/run.py", line 39, in start_streaming
report, path = await run_agent(task, report_type, agent, websocket)
File "/home/ec2-user/gpt-researcher/agent/run.py", line 53, in run_agent
await assistant.conduct_research()
File "/home/ec2-user/gpt-researcher/agent/research_agent.py", line 133, in conduct_research
search_queries = await self.create_search_queries()
File "/home/ec2-user/gpt-researcher/agent/research_agent.py", line 91, in create_search_queries
return json.loads(result)
File "/usr/lib64/python3.9/json/init.py", line 346, in loads
return _default_decoder.decode(s)
File "/usr/lib64/python3.9/json/decoder.py", line 340, in decode
raise JSONDecodeError("Extra data", s, end)
json.decoder.JSONDecodeError: Extra data: line 2 column 1 (char 81)
Looks like gpt-3.5 is returning something that doesn't conform to json format? Seems strange. I can't see what is being decoded, I'm not proficient in python and so far my efforts to debug this using print() statements hasn't been successful, stdout seems to be redirected somewhere. I also tried import logging; logging.info() but the output is also getting swallowed somewhere.

Yes, if you look at prompts.py at generate_search_queries_prompt, it asks it to produce the list of queries in certain format. it is completely stable with gpt4 but not with gpt3.5 . I will dig into modifying the prompt to be more stable with gpt3.5. in the meanwhile try to run it again
add a print here to debug it:
async def create_search_queries(self):
""" Creates the search queries for the given question.
Args: None
Returns: list[str]: The search queries for the given question
"""
result = await self.call_agent(prompts.generate_search_queries_prompt(self.question))
print(result)
await self.websocket.send_json({"type": "logs", "output": f"🧠 I will conduct my research based on the following queries: {result}..."})
return json.loads(result)

I added
print(f"result1 = {result}", file=sys.stderr, flush=True)
after self.call_agent and got an invalid json string:
result = ["<query1>"] ["<query2>"] ["<query3>"] ["<query4>"]

this edit to the prompt is slightly more stable. Please edit generate_search_queries_prompt in the meanwhile:
You must respond only with a list of strings in the following json format: ["query 1", "query 2", "query 3", "query 4"]
Thank you!

That helped, now I'm getting "cannot find Chrome binary", I'll install that now and report back.

Hmm, it didn't throw an error, but it generated an empty report:
Agent Output
Thinking about research questions for the task...
Total research words: 679
Writing research_report for research task: <my input>
End time: 2023-07-10 23:04:24.691949
Total run time: 0:00:01.192128

Research Report

Please empty the output directory and run again

Now it started downloading things for the research, but got this error:
An error occurred while processing the url https://research.tdameritrade.com/grid/public/etfs/profile/ratingsandriskBuffer.asp?symbol=VOOG: [Errno 26] Text file busy: '/home/ec2-user/.wdm/drivers/chromedriver/linux64/114.0.5735.90/chromedriver'

By the way, thanks for the hand-holding, you're awesome!

Of course! can you try run the project locally?

I'm running it on an AWS instance, I can't run it locally, my mac is too old, brew doesn't support my OSX anymore and I can't install python3.

Got it. okay I will try play with an instance as well and update you. We haven't deployed it on an instance yet. If you have any insights feel free to share!

Cheaper to use docker, I don't want you spending money on my behalf. :)

Hi @firerish @rotemweiss57 ! I'm having the same issue:
json.decoder.JSONDecodeError: Extra data: line 2 column 1 (char 51)
I can run the project locally on my Mac, but I was unable to follow the modifications you suggested which would have potentially worked locally. Sorry about that, I'm not very experienced with package development. Would you please be able to suggest some changes I can make to the prompts.py to see if it's working on my end? Thanks for this wonderful package by the way, I saw it on LinkedIn and was immediately interested!

Hi @AHerik of course! Do you currently have gpt-4 working? or are you using gpt-3?
If you already changed the config file to gpt3 (based on your error I assume you have), All you need to do is to go to /agent/prompts.py and in that file look for the function "generate_search_queries_prompt(question)"
Inside that function, modify this line: "You must respond with a list of strings in the following format: ["query 1", "query 2", "query 3", "query 4"]"
to: "You must respond only with a list of strings in the following json format: ["query 1", "query 2", "query 3", "query 4"]"
Again, it is best to use gpt 4, but it should be stable enough.
Hope it helps!

Hi @rotemweiss57 Thank you so much for the prompt reply! Indeed, I'm using GPT-3 as I cannot access the gpt-4 api currently due to whatever limit OpenAI has. Thank you for helping me with the issue, the package works excellently. I'm going to be testing it as a way to compile sources for a manuscript that I'm working on. Will update you on how well it works, and hopefully I will be able to use GPT-4 soon.
Thanks again!

Happy this is resolved. Closing this thread for now


[FR] Delete value from source file

Probably it is not an easily achieved enhancement, but it would be cool to right click an entry among the list to delete the value from the source file (where rule is: one value on one line). Sometimes the ready-made dictionary lists contain unclean or lexically wrong items.
Doable?

Thank you for your FR, @zanodor :)
That looks good. However, I might should add the following features before the one you suggested.

Show words in the custom dictionary
Update a word in the custom dictionary
Delete a word in the custom dictionary

So let me set the status of this issue as "gathering interest"🙏

Might this Issue also be relevant?
https://github.com/tadashi-aikawa/obsidian-various-complements-plugin/issues/27


[$500] Android-IOU-Description entered cannot be seen but displayed in IOU details page.

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

Version Number: 1.3.97-1
Reproducible in staging?: Y
Reproducible in production?: N
If this was caught during regression testing, add the test name, ID and link from TestRail:
Email or phone of affected tester (no customers):
Logs: https://stackoverflow.com/c/expensify/questions/4856
Expensify/Expensify Issue URL:
Issue reported by: Applause-Internal Team
Slack conversation: @
Action Performed:

Launch app
Tap fab
Tap request money
Tap manual
Enter an amount
Tap next
Select an user
Tap 3 dots and tap "add receipt"
Tap Request
Tap IOU to open IOU details page
Tap description
Enter any text
Tap save

Expected Result:
User must be able to see description entered.
Actual Result:
Description entered cannot be seen but displayed in IOU details page.
Workaround:
Unknown
Platforms:

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

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

Screenshots/Videos
Add any screenshot/video evidence
https://github.com/Expensify/App/assets/115492554/e83a288d-fa66-49cc-a5bc-f335928610ef

View all open jobs on GitHub
Upwork Automation - Do Not Edit

Upwork Job URL: https://www.upwork.com/jobs/~018aa91dfca07b2ed6
Upwork Job ID:<PHONE_NUMBER>529140224
Last Price Increase: 2023-11-09

Not reproduced in production
https://github.com/Expensify/App/assets/115492554/5a04d10c-03bf-43de-89ff-8002b28aa20f

:wave: Friendly reminder that deploy blockers are time-sensitive ⏱ issues! Check out the open StagingDeployCash deploy checklist to see the list of PRs included in this release, then work quickly to do one of the following:

Identify the pull request that introduced this issue and revert it.
Find someone who can quickly fix the issue.
Fix the issue yourself.

Proposal
Root cause
verticalAlign is passed like this in MoneyRequestDescription:
                            containerStyles={[styles.autoGrowHeightMultilineInput, styles.verticalAlignTop]}

Changes
We should pass it as
containerStyles={[styles.autoGrowHeightMultilineInput]}
                            inputStyle={[styles.verticalAlignTop]}

I'm available to raise a PR quickly... @Santhosh-Sellavel @mountiny

I'm available to raise a PR quickly

@esh-g can you please raise the PR as quickly as possbile? thanks!

Yes @mountiny Just working on it now

Requesting a CP, @esh-g could you please identify which PR caused this regression?

Yes, the PR that caused this issue is this: https://github.com/Expensify/App/pull/24482
(don't think a regression test is needed for this)

Ok thanks!

Fix was CP'd. Removing the blocker label.

[x]  [@akinwale] The PR that introduced the bug has been identified. Link to the PR:
[x]  [@akinwale] The offending PR has been commented on, pointing out the bug it caused and why, so the author and reviewers can learn from the mistake. Link to comment:
[x]  [@akinwale] A discussion in #expensify-bugs has been started about whether any other steps should be taken (e.g. updating the PR review checklist) in order to catch this type of bug sooner. Link to discussion:

The issue here was as a result of the react-native-web update done in https://github.com/Expensify/App/pull/24482, not due to a feature implementation nor code changes.

[x]  [@akinwale] Determine if we should create a regression test for this bug.
[x]  [@akinwale] If we decide to create a regression test for the bug, please propose the regression test steps to ensure the same bug will not reach production again.

Regression test

Launch the Expensify app.
Navigate to an existing money request or create a new one, ensuring that a description is provided before saving.
Tap on the description to edit.
Verify that the description text is visible in the text input field.
Verify that the description text is editable.

Do we agree 👍 or 👎?

@mallenexpensify Just noting here that the correct payment date here should be 2013-11-17, since the PR was initially deployed to production on 2023-11-10. Thanks.

Contributor: @esh-g paid $500 via Upwork
Contributor+: @akinwale paid $500 via Upwork
Regression test update

https://github.com/Expensify/Expensify/issues/337591

Thanks!


1615 remove guava part 4

This is the last PR for #1615 work in killbill-commons repository. After this, killbill-commons will be Guava-free. Notes:

DefaultStateMachine line ~164 : Refactor from IllegalStateException to NoSuchElementException, otherwise TestStateMachine failed. This is caused by Optional#get() in Guava and java 8 throw different exception.

DefaultStateMachineConfig line ~121 : Refactor from IllegalStateException to NoSuchElementException . Same reason as point 1.

Woops, sorry. Wrong branch!


'Today' fails on plain datepicker control

I have a page with different controls
one of them is plain jQuery datePicker $('elem1').datepicker();
If I click 'Today' button it fails in $.datepicker._gotoToday method because tp_inst is undefined in that case.
Additional check for that case should be added.
Regards,

Thanks for the catch.  I added a check for this in the dev branch


Does not compile

Hi Author,
i was not able to compile the code. Do i really need this code to implement the External Link additional trigger functionality? I downloaded the sitecore package and i was able to see those options on the external links. Is that sufficient or do i still need that code?

Hi, you can just use the package.
This code could have small updates / fixes though.


Activared Redstone Torch Lever looks weird with certain resource packs

Describe the bug
A clear and concise description of what the bug is, including expected behavior.
Screenshots or crash report (if relevant)
If applicable, add screenshots to help explain your problem.
Versions (please complete the following information):

Minecraft: 1.12.2
Mantle: <IP_ADDRESS>
Inspirations

Other mods required
List any other mods required to reproduce this issue. Test by running the game with minimal mods.

You filled out none of the issue template. Plus this is a resource pack problem. Plus this feature was removed in 1.16 and I doubt 1.12 is getting another build.


wrong generation of config cmake files

pinocchioConfig.cmake
windows 10, MinGW gcc
the lib file name should be *pinocchio.lib.a instead of *pinocchio.lib

# Find absolute library paths for all _PKG_CONFIG_LIBS as CMake expects full paths, while pkg-config does not.
set(_PACKAGE_CONFIG_LIBRARIES "")
set("_pinocchio_PKG_CONFIG_LIBDIR" "C:/Program Files (x86)/pinocchio/lib")
set("_pinocchio_PKG_CONFIG_LIBS_LIST" " -lpinocchio.lib -LC:/Users/seaso/Apps/boost_1_77_0/stage/lib -llibboost_filesystem-mgw8-mt-x64-1_77.a -llibboost_serialization-mgw8-mt-x64-1_77.a -llibboost_system-mgw8-mt-x64-1_77.a -llibboost_unit_test_framework-mgw8-mt-x64-1_77.a")

Most likely because it was compiled by mingw.

We may add a specific case for MinGW then. Do you really need to use MinGC?

We may add a specific case for MinGW then. Do you really need to use MinGW?

I am not sure.... I need to use C++/C on windows for the sake of communication with simulink. Personally I prefer mingw rather than MSVC. So far I dont think preparation for development using MSVC is easier than mingw...
Any better suggestions on using pinocchio with C++? Currently I am stuck in the generation of crocoddyl makefiles, which threw a error CMake generation problem.
Already thinking about using python now....

Croco is not yet compatible with Windows. It is not exporting the symbols.
I would say for Pinocchio, cmake tool is very intuitive and easy to use. Please check with the Windows CI (https://github.com/stack-of-tasks/pinocchio/blob/master/.github/workflows/windows-conda-v142.yml).

Related to https://github.com/loco-3d/crocoddyl/issues/1014

@xeonz1 If you just need to install Pinocchio, then relying on conda for that is the easy way.

@xeonz1 If you just need to install Pinocchio, then relying on conda for that is the easy way.

Not familiar with conda. Can I still use c++ with conda ver. pinocchio?

Yes. Of course !

De: "xeonz1" @.>
À: "stack-of-tasks/pinocchio" @.>
Cc: "Justin Carpentier" @.>, "Comment"
@.>
Envoyé: Mardi, Novembre 30, 2021 07:42:36 AM
Objet: Re: [stack-of-tasks/pinocchio] wrong generation of config cmake files
(Issue #1557)

@xeonz1 If you just need to install Pinocchio, then relying on conda for that is
the easy way.
Not familiar with conda. Can I still use c++ with conda ver. pinocchio?

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub , or unsubscribe .
Triage notifications on the go with GitHub Mobile for iOS or Android .


Formatting axes

Hello, I am trying but can't for the life of me format my axes labels and the numbers on mouseover. Here is my code, please tell me what I'm doing wrong. Thank you!
  var dynamicData = [];
  $scope.chartObject = {};
  $scope.chartObject.http = [["January", "2"], ["February", "1594"], ["March", "0"], ["April", "0"], ["May", "0"], ["June", "0"], ["July", "0"], ["August", "0"], ["September", "0"], ["October", "0"], ["November", "0"], ["December", "0"]];
  $scope.length = $scope.chartObject.http.length;
  $scope.chartObject.type = "ColumnChart";
  $scope.chartObject.chart = [];

  for (var x = 0; x < $scope.length; x++) {
    dynamicData.push({
      c: [
        {v: String($scope.chartObject.http[x][0])},
        {v: $scope.chartObject.http[x][1]}
      ]
    });
  }
  console.log(dynamicData);

  $scope.chartObject.data = {
    cols: [
      {id: 'h', label: 'Hour', type: 'string'},
      {id: 'i', label: 'Impressions', type: 'number'}
    ],
    rows: dynamicData
  };

  $scope.chartObject.options = {
    "legend": {
      "position": "top"
    },
    "bar": {
      "groupWidth": "75%"
    }
  };
  $scope.chartObject.formatters = {
    "number": [{
      columnNumber: 0,
      "decimalSymbol": ".",
      "groupingSymbol": ","
    },
      {
        columnNumber: 1,
        "decimalSymbol": ".",
        "groupingSymbol": ","
      }]
  };
}

I am trying to format the numbers in the thousands and to make the y-axis go 0, 500, 1,000, 1,500, 2,000.
Thank you!

The only thing I see is that while you're setting the second column of your DataTable as type number, the values you are passing are strings.  Try removing the quotes from the number values and see if that does anything.
As for your y-axis markers, there are option settings to manually set the interval of markers on the axes, just check the documentation at https://developers.google.com/chart/interactive/docs/gallery/columnchart#Configuration_Options. I think the options you are looking for are vAxis.ticks, vAxis.maxValue, vAxis.minValue, and possibly vAxis.format.  vAxis.format would be unnecessary if you give vAxis.Ticks an array of objects with values and formatted values.  There's an explanation for that in the docs.


Fix date-picker animation in IE11

Bug description:
In IE11 the animation for changing the month in the date-picker is not smooth.

This pull-request should fix this problem.

THANKS!


Add http-parser and BalsaParser tests for "Connection: close".

Commit Message: Add http-parser and BalsaParser tests for "Connection: close".
Additional Description: new tests
Risk Level: low
Testing: //test/common/http/http1:codec_impl_test
Docs Changes: n/a
Release Notes: n/a
Platform Specific Features: n/a

/assign @krajshiva

Is this difference in behavior only relevant for tests? I would think Envoy should close the connection with the connection: close header on both request and response paths regardless of the H/1 codec it uses.
/wait-any

Is this difference in behavior only relevant for tests? I would think Envoy should close the connection with the connection: close header on both request and response paths regardless of the H/1 codec it uses.
/wait-any

Yes, I agree with you, there is more work to be done in future PRs here. UHV or ConnectionImpl is probably a better place for the proposed change to close the connection than the codecs themselves.
This issue came up in a discussion and Kirti asked me to confirm the difference in behavior between the two codecs. I wrote these tests to answer the question.

Thanks for testing the behavior @bencebeky . We stumbled upon this while working on a FR. I think we all agree on behavior to be RFC compliant


It gives RecursionError: maximum recursion depth exceeded Error

For sites with many links it gives "RecursionError: maximum recursion depth exceeded" error. I think it uses tail recursion and that is why it stucks at default recursion limit of python. The logic needs to be improvised to not face this limit issue. Can you help?
Traceback (most recent call last):
File "email_crawler.py", line 146, in
crawl.crawl()
File "email_crawler.py", line 40, in crawl
self.crawl()
File "email_crawler.py", line 40, in crawl
self.crawl()
File "email_crawler.py", line 40, in crawl
self.crawl()
[Previous line repeated 958 more times]
File "email_crawler.py", line 36, in crawl
self.parse_url(url)
File "email_crawler.py", line 62, in parse_url
response = requests.get(current_url, headers=self.headers)
File "\lib\site-packages\requests\api.py", line 76, in get
return request('get', url, params=params, **kwargs)
File "\lib\site-packages\requests\api.py", line 61, in request
return session.request(method=method, url=url, **kwargs)
File "\lib\site-packages\requests\sessions.py", line 530, in request
resp = self.send(prep, **send_kwargs)
File "\lib\site-packages\requests\sessions.py", line 665, in send
history = [resp for resp in gen]
File "\lib\site-packages\requests\sessions.py", line 665, in
history = [resp for resp in gen]
File "\lib\site-packages\requests\sessions.py", line 245, in resolve_redirects
**adapter_kwargs
File "\lib\site-packages\requests\sessions.py", line 643, in send
r = adapter.send(request, **kwargs)
File "\lib\site-packages\requests\adapters.py", line 533, in send
return self.build_response(request, resp)
File "\lib\site-packages\requests\adapters.py", line 265, in build_response
response = Response()
File "\lib\site-packages\requests\models.py", line 608, in init
self.headers = CaseInsensitiveDict()
File "\lib\site-packages\requests\structures.py", line 46, in init
self.update(data, **kwargs)
File "\lib_collections_abc.py", line 839, in update
if isinstance(other, Mapping):
File "\lib\abc.py", line 182, in instancecheck
if subclass in cls._abc_cache:
RecursionError: maximum recursion depth exceeded

I have encountered this same issue.


Improve documentation of Compilation and Compiler

Feature to document
Compilation and Compiler API.
The Plugin API documentation is very good when it comes to the availability of hooks, but provides very little documentation of the Compilation and Compiler objects which are so heavily used in them - and the docs even say that

Among the two most important resources while developing plugins are the compiler and compilation objects. Understanding their roles is an important first step in extending the webpack engine.

There are some limited docs on the Compiler (which is not referenced from the plugin docs), but it does not cover most of the available methods or properties of the compiler.  There doesn't appear to be even this much information on the Compilation, even though examples show some functionality (e.g. the "writing a plugin" section contains an example that writes to compilation.assets but there's no explanation of the assets property and how that works).
The issue template mentions a PR to the feature, but as it's a core part of webpack I'm not really sure what to reference!
Author(s)
@sokra, @TheLarkInn, and @ooflorent come up first in the contributors list for Compilation.js and Compiler.js but there are many contributors.
Additional information
While low level "this is what this method/property is and what it does" is useful, some sort of "if you're trying to do something like X, then try looking at Y method and Z property" might also be useful.  I've ended up solving my particular problem (force a recompile of a given file whenever another given file changes) but in what I suspect is totally the wrong way - I figured out how to mess with the fileTimestamps entry for the file I wanted to force to recompiled, but I suspect that if I could somehow inform webpack of the dependency between the two then it would handle the rest itself.
[ ] I am willing to work on this issue and submit a pull request.
I cannot, because I don't understand them :D

I think most of the questions can be answered by using node's inspect. Although it would be great to add this into the docs.

Yes, reading the code or inspecting the behaviour at runtime are certainly options to figure out what's going on, but are a significantly higher barrier than reading documentation :)


'Wrong transactional state (no active transaction, wrong type of transaction, or transaction already in progress)

How frequently does the bug occur?
Sometimes
Description
used extension
all write operations make at queue
   static var operationQueue: OperationQueue {
        get {
          queue.qualityOfService = .userInteractive
          queue.maxConcurrentOperationCount = 1
          return queue
        }
    }
    static let serialQueue = DispatchQueue.init(label: "serial-queue", qos: DispatchQoS.userInitiated) // ....

   // open realm
    serialQueue.async {
            do {
                RealmManager.sharedRealm = try Realm(configuration: .defaultConfiguration, queue: serialQueue)
            }
   }

extension Realm {
    public func safeWrite(_ block: (() throws -> Void)) throws {
        if isInWriteTransaction {
            try block()
        } else {
            try write(block)
        }
    }
}

crash at line   try block()

that means  realm isInWriteTransaction == true
how it possible
Crash happened some time
screenshots

Stacktrace & log output
*** Terminating app due to uncaught exception 'RLMException', reason: 'Wrong transactional state (no active transaction, wrong type of transaction, or transaction already in progress)
Exception backtrace:
0   Realm                               0x000000010ac8cc08 _ZN5realm4util6detail26ExceptionWithBacktraceBaseC2Ev + 48
1   Realm                               0x000000010ac8cb6c _ZN5realm4util22ExceptionWithBacktraceISt9exceptionEC2IJEEEDpOT_ + 68
2   Realm                               0x000000010ac8cb00 _ZN5realm10LogicErrorC2ENS0_9ErrorKindE + 60
3   Realm                               0x000000010ac8ca20 _ZN5realm10LogicErrorC1ENS0_9ErrorKindE + 36
4   Realm                               0x000000010b0309d4 _ZN5realm4Node16do_copy_on_writeEm + 400
5   Realm                               0x000000010af96580 _ZN5realm5Array3setEmx + 124
6   Realm                               0x000000010b03092c _ZN5realm4Node16do_copy_on_writeEm + 232
7   Realm                               0x000000010af96580 _ZN5realm5Array3setEmx + 124
8   Realm                               0x000000010ac743a4 _ZN5realm5Array16update_child_refEmm + 40
9   Realm                               0x000000010b03092c _ZN5realm4Node16do_copy_on_writeEm + 232
10  Realm                               0x000000010af96580 _ZN5realm5Array3setEmx + 124
11  Realm                               0x000000010afc3464 _ZN5realm16ClusterNodeInner20update_ref_in_parentENS_6ObjKeyEm + 88
12  Realm                               0x000000010b031250 _ZN5realm3Obj3setINS_10StringDataEEERS0_NS_6ColKeyET_b + 864
13  Realm                               0x000000010ac8eb48 _ZZN12_GLOBAL__N_114setValueOrNullIN5realm10StringDataEEEvP13RLMObjectBaseNS1_6ColKeyEP11objc_objectENKUlvE_clEv + 136
14  Realm                               0x000000010ac8ea34 _ZL17RLMTranslateErrorIZN12_GLOBAL__N_114setValueOrNullIN5realm10StringDataEEEvP13RLMObjectBaseNS2_6ColKeyEP11objc_objectEUlvE_EDaOT_ + 24
15  Realm                               0x000000010ac8ea10 _ZN12_GLOBAL__N_114setValueOrNullIN5realm10StringDataEEEvP13RLMObjectBaseNS1_6ColKeyEP11objc_object + 88
16  Realm                               0x000000010ac8e9ac _ZN12_GLOBAL__N_18setValueEP13RLMObjectBaseN5realm6ColKeyEP8NSString + 48
17  Realm                               0x000000010ac679c4 _ZN12_GLOBAL__N_111kvoSetValueIU8__strongP8NSStringS3_EEvP13RLMObjectBasemT_ + 136
18  Realm                               0x000000010ac678fc RLMSetSwiftPropertyString + 72
19  RealmSwift                          0x000000010bf13c7c $sSS10RealmSwiftE15_rlmSetPropertyyySo13RLMObjectBaseC_s6UInt16VSStFZ + 124
20  RealmSwift                          0x000000010bf13d2c $sSS10RealmSwift12_PersistableA2aBP15_rlmSetPropertyyySo13RLMObjectBaseC_s6UInt16VxtFZTW + 24
21  RealmSwift                          0x000000010bfa58b0 $s10RealmSwift9PersistedV3set_5valueySo13RLMObjectBaseC_xtF + 2076
22  RealmSwift                          0x000000010bfa502c $s10RealmSwift9PersistedV18_enclosingInstance7wrapped7storagexqd___s24ReferenceWritableKeyPathCyqd__xGAHyqd__ACyxGGtcSo13RLMObjectBaseCRbd__luisZ + 228
23  Me                                  0x0000000101021a10 $s2Me9RealmUserC9firstNameSSvs + 156
24  Me                                  0x000000010103d01c $s2Me9RealmUserC7setJSON33_28A8C472E5AD302037F6F876A8769A88LL_7toModely06SwiftyE00E0V_ACtFZ + 1256
25  Me                                  0x000000010103ca40 $s2Me9RealmUserC6upsert4jsony10SwiftyJSON0G0V_tFZyycfU_yyXEfU_ + 64
26  Me                                  0x00000001014ba8b8 $s10RealmSwift0A0V2MeE9safeWriteyyyyKXEKF + 112

Can you reproduce the bug?
Yes, sometimes
Reproduction Steps
multiple transactions at background
Version
pod 'RealmSwift', '~>10.28.2'
What SDK flavour are you using?
Local Database only
Are you using encryption?
No, not using encryption
Platform OS and version(s)
iOS 12, 14, 15
Build environment
Xcode version: ... Version 13.3.1 (13E500a)

@mr-grey having the serial queue being dispatched inside another operation queue seems like it might be the culprit to the issue. Could you try removing operationQueue? Also Realms are cached so I would not recommend creating a singleton manager class to access a Realm. You should create transient instances to the Realm when you need to access it.

Hi,  1. operationQueue was added for prevent inTransaction state . because multiple different transactions in threads make crash .
2. This issue 'Wrong transactional state..' occurs only for old devices , possible it unable to write to file or some like this
am modified a extension for it wait for InTransaction become false.
public func safeWrite(_ block: (() throws -> Void)) throws {

        //time in microseconds instead

        while isInWriteTransaction {

            usleep(10000)

        }

        try write(block)
    }

'Realms are cached so I would not recommend creating a singleton manager class to access a Realm. ' - one Realm used for all write operations.  Also how about memory consumption, on older devices it a problem , in first time we have used singe Realm  for single get \ write data operations. but it provides multiple crashed via memory issues .

I would try peel back the layers of abstraction and use the realm instance in a more transient way. Hopefully that would solve the issue here.


Major performance drop in 1.23.3

Pex 1.23.3 on Spigot 1.8.3
Performance is horrible:
http://timings.aikar.co/?url=11756899

1.23.3 removes a performance fix that some people were having issues with. If 1.23.2 worked better for you, feel free to downgrade (and disable the autoupdater in config.yml) -- reverting that performance fix was the only change in 1.23.3.

No version of PEX ever worked good for me sadly


[Feature] Add bce loss for multilabel task

Hi,
In this pull request, bce loss was implemented.
Please kindly take a look. Thanks.

Please fix the linting issue, then I will handle the conflicts before merging into master.

Please fix the linting issue, then I will handle the conflicts before merging into master.


OCPBUGS-13128: Retry initialization error conditions (#2979)

When the api server is flakey (e.g. during a cluster install), it is possible for some of the OLM initialization to fail. When this happens, OLM gets into a bad state (e.g. a monitoring go routine terminates) and can't recover without a restart.
There were at least two places I found where a retry mechanism is needed to handle intialization errors. This was as far as I peeled the onion. It's not an exponential backoff retry, but a 1 minute retry interval should be sufficient (no other backoffs are exponential).
The ServerVersion only retries once with a minute in between. This required fixing a unit-test to take the retry into account.
Upstream-repository: operator-lifecycle-manager
Upstream-commit: e908cfc6b

/jira refresh

/retest

/approve
/lgtm


Cannot Redeploy without Overwritting EB configuration

Describe the bug
Redeploying with the publish to AWS dialog overwrites the EB configuration on deployment.  This is preventing me from making any changes to my environment on AWS.  This is required since the toolkit dialog only supports a fraction of the options.   I am deploying a .NET 9 (bundled option) "asp.net Core app to AWS Elastic Beanstalk on Linux".
To Reproduce

Publish to a new Target
Make a change to the environment such as changing from a single instance to a load balancer from AWS gui.
Publish to existing target to the same previously created environment.
The load balancer is removed and the environment is reverted to single instance.

Expected behavior
The environment should only be modified on creation or explicitly instructed to change the existing environment.  The legacy dialog works this way, it does not change the environment.
Development System (please complete the following information):
AWS Toolkit <IP_ADDRESS>
VS 2022 17.12.1
Windows 10
Additional context
Although a separate issue, this could be related.  If I create an environment on AWS, I cannot see it as an option to deploy on the "publish to AWS" dialog.  It does show in the legacy dialog.

The "Publish to AWS" experience in Visual Studio uses AWS CDK on the backend, which maintains the state of the application being deployed. If you change settings in Beanstalk directly, for which CDK is maintaining state, then they will be overridden on redeployment. As an example, you mentioned you updated the environment from Single Instance to Load balanced. The "Publish to AWS" experience already provides settings to update that behavior, which is why your manual updates were overridden since CDK still thinks you are using a Single Instance. However, for any setting that we do not expose, manually updating the environment will not override those settings.

I was scratching my head what I missed here.  I see that if I create a new environment I can specify the environment type to single instance or load balanced.  This option is subsequently hidden upon redeployments in the adjustable options. It would be helpful still expose the option for redeployments like the other options.


Adopt some WMI windows agents implied dependencies

Adopt some WMI Windows Agents implied dependencies

Let markewaite adopt discard-old-build plugin
Let markewaite adopt skip-certificate-check plugin
Let markewaite adopt the JDK parameter plugin

Reduce the problems related to implied dependencies on the WMI Windows Agents plugin by releasing new versions of the more popular plugins so that users can upgrade to those new versions and then remove the WMI Windows Agents plugin.
Repositories are:

https://github.com/jenkinsci/discard-old-build-plugin
https://github.com/jenkinsci/skip-certificate-check-plugin
https://github.com/jenkinsci/JDK_Parameter_Plugin-plugin

No existing maintainers to mention.
Submitter checklist for adding or changing permissions
Always

[x] Add link to plugin/component Git repository in description above

When adding new uploaders (this includes newly created permissions files)

[x] Make sure to @mention an existing maintainer to confirm the permissions request, if applicable
[x] Use the Jenkins community (LDAP) account name in the YAML file, not the GitHub account name
[x] Make sure to @mention the users being added so their GitHub account names are known if they require GitHub merge access (see below).
[x] All newly added users have logged in to Artifactory and Jira at least once

Reviewer checklist (not for requesters!)

[ ] Check this if newly added person also needs to be given merge permission to the GitHub repo (please @ the people/person with their GitHub username in this issue as well). If needed, it can be done using an IRC Bot command
[ ] Check that the $pluginId Developers team has Admin permissions while granting the access.
[ ] In the case of plugin adoption, ensure that the Jenkins Jira default assignee is either removed or changed to the new maintainer.
[ ] If security contacts are changed (this includes add/remove), ping the security officer (currently @Wadeck) in this pull request. If an email contact is changed, wait for approval from the security officer.

There are IRC Bot commands for it

Thanks so much for merging this @slide.  Unfortunately, I don't yet seem to have permissions for those repositories.  Did I make some mistake in the syntax?  Is the bot that processes GitHub permission changes offline?

I added you.

My bad, I forgot the bot part.


SUS

EEEEEEEEEEEEEEEEEEE
A clear and concise description of what the bug is.

[x] hi
To Reproduce
Steps to reproduce the behavior:

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

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

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

Smartphone (please complete the following information):

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

Additional context
Add any other context about the problem here.

Done


Begin Modernization of our Futures Interface

This represents a proposal to modernize our futures interface, moving them towards a more object-oriented interface. ck::future is templated, and can be used with any pup'able types; pup'ing is automatically handled behind-the-scenes.
CkFuture CkCreateFuture(void) -> ck::future<T>()
void CkReleaseFuture(CkFuture fut) -> void ck::future<T>::release()
int CkProbeFuture(CkFuture fut) -> bool ck::future<T>::probe()
void *CkWaitFuture(CkFuture fut) -> T ck::future<T>::get()
void CkSendToFuture(CkFuture fut, void *msg) -> void ck::future<T>::set(T)

It seems like the Windows build issues stem from using CkMarshallMsg in ckfutures.h, does anyone have any thoughts on where to put the object-oriented interface so this isn't an issue? Perhaps another header file, if so what would be a good name for it? Something like <ck/future.hpp> would be the most modern solution, but that wouldn't fit into typical Charm++ conventions well (and I'm unsure whether the build scripts would handle it correctly).


make h12.me the canonical import path

Currently attempt to "go install -v ./..." produces errors like these:
examples/main.go:23: cannot use "github.com/hailiang/html-query/expr".Class("tags") (type "github.com/hailiang/html-query/expr".Checker) as type "h12.me/html-query/expr".Checker in argument to item.Span
# h12.me/html-query/gen
gen/spec.go:105: cannot use "github.com/hailiang/html-query/expr".CaptionText("List of attributes") (type "github.com/hailiang/html-query/expr".Checker) as type "h12.me/html-query/expr".Checker in argument to root.Table

Suggest to use h12.me as the canonical import path throughout all the imports, similar to http://godoc.org/h12.me/socks and analogous to the change in https://github.com/hailiang/socks/pull/4/files

Perfect! Thanks!


Package subpath './inertia-helpers' is not defined by "exports"

Vite Plugin Version
0.7.6
Laravel Version
10.10.1
Node Version
20.1.0
NPM Version
9.6.4
Operating System
macOS
OS Version
13.3.1
Web browser and version
terminal
Running in Sail?
No
Description
Hello, in the new version of laravel-vite-plugin (0.7.6), I've got an error you fixed already in the past (with the version 0.4.0 I think).
ESLint gives me that error:
Package subpath './inertia-helpers' is not defined by "exports" in /Users/xxx/projects/www/jinx/node_modules/laravel-vite-plugin/package.json
Here is my app.tsx where the import is made:
import { resolvePageComponent } from 'laravel-vite-plugin/inertia-helpers';
Everything was ok with the exact same code and config (node, vite, laravel...) but with laravel-vite-plugin version 0.7.4
thanks for your help
Steps To Reproduce

update laravel-vite-plugin from 0.7.4 to 0.7.5
use this import: import { resolvePageComponent } from 'laravel-vite-plugin/inertia-helpers

Hi @Xor767,
Could you please provide a minimal reproduction repository? There are a lot of unknowns here. It seems like you're using React and TypeScript, but we don't know how you have configured ESLint and can't replicate the issue.

Hi @jessarcher,
here is a reproduction repository: https://codesandbox.io/p/sandbox/laravel-vite-plugin-xf51rf?welcome=true
please run the code-sample task named "npx eslint src".
thanks for your help.

Thanks, @Xor767 - I've been able to replicate the issue now.
It seems to be triggered by the eslint-import-resolver-alias package you're using.
We have a potential workaround that I'd like you to confirm for us. In your node_modules/laravel-vite-plugin/package.json file, locate the "exports" section and make the following change:
      "exports": {
          ".": {
              "import": "./dist/index.mjs",
              "require": "./dist/index.cjs",
              "types": "./dist/index.d.ts"
          },
          "./inertia-helpers": {
              "import": "./inertia-helpers/index.js",
-             "types": "./inertia-helpers/index.d.ts"
+             "types": "./inertia-helpers/index.d.ts",
+             "node": "./inertia-helpers/index.js"
          }
      },

If this solves the issue, we can tag a new release with this in place.

Hi @jessarcher ! yes your workaround solves the issue in my project 💪
thanks a lot!

I've opened a PR to address this issue.


Evaluate changes to projects needed to support the new proxy submitter model

Evaluate which projects need to be updated based on model changes, and create issues to deal with them. (e.g. NIHMS submission ETL may need changes to algorithm).   Things like changed field names, default values etc. Those are the sorts of things this will aim to identify.
Expected outcomes include draft cards for each components. Each component lead will need to work with you on the part that is relevant to their components.
RET 1 days <-- i think this is going to take more than 1 day

The following issues were generated as a result of this:
https://github.com/OA-PASS/general-issues/issues/18
https://github.com/OA-PASS/nihms-submission-etl/issues/21
https://github.com/OA-PASS/pass-grant-loader/issues/23
https://github.com/OA-PASS/deposit-services/issues/150
https://github.com/OA-PASS/pass-docker/issues/120
https://github.com/OA-PASS/pass-docker/issues/121
https://github.com/OA-PASS/java-fedora-client/issues/50
https://github.com/OA-PASS/general-issues/issues/19
https://github.com/OA-PASS/general-issues/issues/13 (not new, added more info, need to revise time)
No new issues were added for pass-ember, pass-authz, or notification-services since the updates for those related to the data model are basically the work for proxy user!


nixos/xdg/icons: match XCURSOR_PATH spec

Motivation for this change
Match what is supposed to be in XCURSOR_PATH

https://gitlab.freedesktop.org/xorg/lib/libxcursor/commit/2263c196cb0dcb8547b378df7b35f83b8b99c01e

#define XCURSORPATH "~/.local/share/icons:~/.icons:/usr/share/icons:/usr/share/pixmaps:"ICONDIR

XCURSOR_PATH in a shell
eval echo $XCURSOR_PATH
/home/worldofpeace/.local/share/icons:/home/worldofpeace/.icons:/home/worldofpeace/.nix-profile/share/icons:/home/worldofpeace/.nix-profile/share/pixmaps:/etc/profiles/per-user/worldofpeace/share/icons:/etc/profiles/per-user/worldofpeace/share/pixmaps:/nix/var/nix/profiles/default/share/icons:/nix/var/nix/profiles/default/share/pixmaps:/run/current-system/sw/share/icons:/run/current-system/sw/share/pixmaps

Things done

[ ] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS)
Built on platform(s)

[ ] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nix-review --run "nix-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Ensured that relevant documentation is up to date
[ ] Fits CONTRIBUTING.md.

Notify maintainers
cc @

We have libXcursor 1.2.0 which has the aforementioned commit. Though it doesn't change much since gtk already prefers XDG_DATA_HOME/icons.

I believe the comment about GTK preferring XDG_DATA_HOME/icons refers to icons. I did not notice anything like that during a brief look through the GTK file, it just seems to let Xcursor handle that.

So in that case we really need to have .local/share/icons in XCURSOR_PATH.

Looks good. A comment about how these values are derived would help posterity! e.g. my understanding is that we have to manually set XCURSOR_PATH to look in the places that the icon spec specifies.

Note that the directories in https://www.x.org/releases/current/doc/man/man3/Xcursor.3.xhtml are out of date, but probably because they need to update the docs on their server.
i.e the man page has it substituted in https://gitlab.freedesktop.org/xorg/lib/libxcursor/blob/master/man/Xcursor.man#L143

If you find yourself with an error like this:
error: The unique option `environment.variables.XCURSOR_PATH' is defined multiple times, in:
 - /home/grahamc/projects/grahamc/nixos-config/devices/petunia/configuration.nix
 - /home/grahamc/projects/github.com/NixOS/nixpkgs/nixos/modules/config/shells-environment.nix.
(use '--show-trace' to show detailed location information)

then you probably have a line in your config like:
environment.variables.XCURSOR_PATH = [ "${pkgs.gnome3.adwaita-icon-theme}/share/icons" ];

and you can just put pkgs.gnome3.adwaita-icon-theme in your systemPackages instead, or use lib.mkForce.


Unpredictable nan in Array

Description
Hi there,
I tried to apply some nd operations on data. But the returned array seemed to randomly contain a nan element for a certain index.
Environment info (Required)
Built from source
----------Python Info----------
('Version      :', '2.7.12')
('Compiler     :', 'GCC 5.4.0 20160609')
('Build        :', ('default', 'Nov 19 2016 06:48:10'))
('Arch         :', ('64bit', 'ELF'))
----------MXNet Info-----------
('Version      :', '1.2.0')
('Directory    :', '/home/workspace/incubator-mxnet/python/mxnet')
----------System Info----------
('Platform     :', 'Linux-4.4.0-96-generic-x86_64-with-Ubuntu-16.04-xenial')
('system       :', 'Linux')
('release      :', '4.4.0-96-generic')

Package used (Python/R/Scala/Julia):
Python
MXNet commit hash:
97570916f844bcb4515d972c75fb0a75da345d97
Error Message:
# `Ctrl+F` to find the place where `nan` occurs
# $ python batch_loss_bug.py
[[ 0.54881352  0.59284461]
 [ 0.71518934  0.84426576]
 [ 0.60276335  0.85794562]
 [ 0.54488319  0.84725171]
 [ 0.42365479  0.62356371]]
[[ 0.79172504  0.81216872]
 [ 0.5288949   0.47997716]
 [ 0.56804454  0.3927848 ]
 [ 0.92559665  0.83607876]
 [ 0.07103606  0.33739617]]
--------------------
[[ 0.24291152  0.21932411]
 [ 0.24291152  0.21932411]
 [ 0.24291152  0.21932411]
 [ 0.24291152  0.21932411]
 [ 0.24291152  0.21932411]
 [-0.18629444 -0.3642886 ]
 [-0.18629444 -0.3642886 ]
 [-0.18629444 -0.3642886 ]
 [-0.18629444 -0.3642886 ]
 [-0.18629444 -0.3642886 ]
 [-0.03471881 -0.46516082]
 [-0.03471881 -0.46516082]
 [-0.03471881 -0.46516082]
 [-0.03471881 -0.46516082]
 [-0.03471881 -0.46516082]
 [ 0.38071346 -0.01117295]
 [ 0.38071346 -0.01117295]
 [ 0.38071346 -0.01117295]
 [        nan -0.01117295]     #     NaN occurs here!
 [ 0.38071346 -0.01117295]
 [-0.35261875 -0.28616753]
 [-0.35261875 -0.28616753]
 [-0.35261875 -0.28616753]
 [-0.35261875 -0.28616753]
 [-0.35261875 -0.28616753]]

Minimum reproducible example
Run the following code several times (must be less than 10 times in my experiments), and there is a chance to observe the trouble output.
import mxnet as mx
import numpy as np
def bench_mark(D_slice, P_slice):
    n= D_slice.shape[0]
    e3 = mx.nd.empty((n*n,2))
    for i in xrange(n):
        e3[n*i:n*(i+1)]  = (e3[n*i:n*(i+1)]*0+1)*( P_slice[i] - D_slice[i])
    return e3

x = mx.nd.random.uniform(shape=(2,5,2))
y = mx.nd.random.uniform(shape=(2,5,2))
e3_bm = bench_mark(x[0], y[0])
print x[0].asnumpy()
print y[0].asnumpy()
print '-'*20
print (e3_bm).asnumpy()

What have you tried to solve it?
Maybe the function of bench_mark should be replaced by the other( but I still think the problem  makes sense).

@CXMA479 Thanks for reporting this!. It seems to be a bug. I've revised the code to repeat the process multiple times:
import mxnet as mx
import numpy as np
def bench_mark(D_slice, P_slice):
    n= D_slice.shape[0]
    e3 = mx.nd.empty((n*n,2))
    for i in range(n):
        e3[n*i:n*(i+1)]  = (e3[n*i:n*(i+1)]*0+1)*( P_slice[i] - D_slice[i])
    return e3

for i in range(100):
    x = mx.nd.random.uniform(shape=(2,5,2))
    y = mx.nd.random.uniform(shape=(2,5,2))
    e3_bm = bench_mark(x[0], y[0])
    print(x[0].asnumpy())
    print(y[0].asnumpy())
    print('-'*20)
    # print((e3_bm).asnumpy())
    e3_bm_npy = e3_bm.asnumpy()
    assert(np.isnan(e3_bm_npy).any() == False), str(e3_bm_npy)

Result:
     17     # print((e3_bm).asnumpy())
     18     e3_bm_npy = e3_bm.asnumpy()
---> 19     assert(np.isnan(e3_bm_npy).any() == False), str(e3_bm_npy)
     20

AssertionError: [[ 0.5124911   0.45078474]
 [ 0.5124911   0.45078474]
 [ 0.5124911   0.45078474]
 [ 0.5124911   0.45078474]
 [ 0.5124911   0.45078474]
 [        nan         nan]
 [-0.57626355  0.13732177]
 [-0.57626355  0.13732177]
 [-0.57626355  0.13732177]
 [-0.57626355  0.13732177]
 [ 0.2129727  -0.06519118]
 [ 0.2129727  -0.06519118]
 [ 0.2129727  -0.06519118]
 [ 0.2129727  -0.06519118]
 [ 0.2129727  -0.06519118]
 [ 0.17914966 -0.17914736]
 [ 0.17914966 -0.17914736]
 [ 0.17914966 -0.17914736]
 [ 0.17914966 -0.17914736]
 [ 0.17914966 -0.17914736]
 [-0.6420211   0.68399173]
 [-0.6420211   0.68399173]
 [-0.6420211   0.68399173]
 [-0.6420211   0.68399173]
 [-0.6420211   0.68399173]]

@mxnet-label-bot add [NDArray]


[type:improve] Get rid of the dead code and add some improvements

Make sure that:

[ ] You have read the contribution guidelines.
[ ] You submit test cases (unit or integration tests) that back your changes.
[ ] Your local test passed ./mvnw clean install -Dmaven.javadoc.skip=true.

@Aias00 PLS, Review this PR


Continue area drawing

Sometimes you might need to continue drawing an area, e.g. river bed. Right now you have to cut the line, detach, continue drawing from one of the ends and merge the lines at the end. It would be nice to have a possibility to continue drawing an area from any node.

This also happens when you accidentally close an area - would be good to be able to undo and continue in area edit mode again.

This is a duplicate of #2272
We might also support a modifier key or some other special mode to let you extend areas or lines
see https://github.com/openstreetmap/iD/issues/1711#issuecomment-92989335


Changing colors of some mapbox navigation's widgets

Hi. Is it possible to change the colors of widgets? like this one of appbar? or is it possible to style this map? I'm also having an issue on my navigation icon(marker) as you can see, it's black and it was supposed to be blueish within a white circle. Any help will be much appreciated. And thanks for making this awesome package👏.

with enable changing the style in next update

set the mapStyleURL to the MapBox Style in version 0.0.16


Fix GHC 9.2.8 builds due to Prelude.liftA2

liftA2 has been reexported from Prelude only since base-4.18 (GHC 9.6.X), so references to liftA2 without the accompanying Control.Applicative import causes build failures in earlier GHC versions. Simply adding import Control.Applicative (liftA2) to this repo fixes the issue for earlier GHC versions, but that causes an "unused import" warning in GHC 9.6, which becomes a build failure due to the -Werror flag.
This PR allows us to build pact with GHC 9.2.8 as well as GHC 9.6.3 without any issues, by importing Control.Applicative qualified and referring to liftA2 with the Control.Applicative. prefix, avoiding the warning in GHC 9.6.3 and fixing the missing reference in 9.2.8.
I'm not sure how important that is for the pact project, but chainweb-data currently can't be upgraded to GHC 9.6.X due its transitive dependencies (see https://github.com/kadena-io/chainweb-data/pull/172) and it also can't stay with an earlier pact version, since pact made a sudden jump from 8.10 to 9.6 skipping all the intermediate GHC releases, so it may, in general, be desirable to allow it to build with earlier versions.
 Using CPP would be even uglier, or I could replace liftA2 with ... <$> ... <*> ..., but that could in (far-fetched) theory affect the performance, so opted for a fix that's obviously equivalent.
Feel free to close this PR if GHC 9.2.8 is considered irrelevant for pact.

I'm skipping the PR checklist since it's hard to imagine how this change can have any effect on the program behavior.

 _Skipped PR checklist_
  PR checklist:

[ ] Test coverage for the proposed changes
[ ] PR description contains example output from repl interaction or a snippet from unit test output
[ ] Documentation has been updated if new natives or FV properties have been added. To generate new documentation, issue cabal run tests. If they pass locally, docs are generated.
[ ] Any changes that could be relevant to users have been recorded in the changelog
[ ] In case of  changes to the Pact trace output (pact -t), make sure pact-lsp is in sync.

Additionally, please justify why you should or should not do the following:

[ ] Confirm replay/back compat
[ ] Benchmark regressions
[ ] (For Kadena engineers) Run integration-tests against a Chainweb built with this version of Pact

LGTM @enobayram  - can @jwiegley  or @jmcardon please :+1:  this so we can get it in?


When proposing diasamb, the classification does not use prefixes

Also the class should be depicted in the same way as in the Table (label and then URI to the brackets)


AKAudioPlayer: refining the buffer filling

I've refined the fill buffer routine more now. Also, I've changed the name of setPCMBuffer() to updatePCMBuffer(), which is more accurate to what it's doing.
The buffer is updated only on these occasions now:

initialize()
set startTime
set endTime
on immediate playback within a sound file (when the startTime is being set on the fly)

Previously the buffer was being filled with the same data over and over (on stop() which was called too often) even if it didn't need to change. So, this should be more efficient. I've tested with 20 concurrent samples all playing at the same time and it was solid. I do think the current implementation is better suited towards shorter sound files as Laurent mentioned. More on that soon.
One other recommended change: I've commented out the auto-play within the startTime/endTime. I think that this should be in the specific application control class rather than within the API. If you are doing edits while a group of sounds are playing, if one starting playing again immediately when you didn't ask it to, it would be a bug.

This all seems reasonable to me.  Probably don't need to comment out the stuff, just remove it with good git commits, but I see why you're doing it to be extra clear and careful.

Excellent!

I thought you wanted to set buffer at every "play" action but that's not the case and thank you for fixing unnecessary buffer setting.
You're absolutely right about renaming set buffer into update buffer.
Thanks !
:-)
Laurent.
Envoyé de mon iPhone

Le 29 oct. 2016 à 00:18, Ryan Francesconi<EMAIL_ADDRESS>a écrit :
I've refined the fill buffer routine more now. Also, I've changed the name of setPCMBuffer() to updatePCMBuffer(), which is more accurate to what it's doing.
The buffer is updated only on these occasions now:
initialize()
set startTime
set endTime
on immediate playback within a sound file (when the startTime is being set on the fly)
Previously the buffer was being filled with the same data over and over (on stop() which was called too often) even if it didn't need to change. So, this should be more efficient. I've tested with 20 concurrent samples all playing at the same time and it was solid. I do think the current implementation is better suited towards shorter sound files as Laurent mentioned. More on that soon.
One other recommended change: I've commented out the auto-play within the startTime/endTime. I think that this should be in the specific application control class rather than within the API. If you are doing edits while a group of sounds are playing, if one starting playing again immediately when you didn't ask it to, it would be a bug.
You can view, comment on, or merge this pull request online at:
https://github.com/audiokit/AudioKit/pull/595
Commit Summary
I've refined the fill buffer route more now. Also, I've changed the name of setPCMBuffer() to updatePCMBuffer(), which is more accurate to what it's doing.
File Changes
M AudioKit/Common/Nodes/Playback/Player/AKAudioPlayer.swift (99)
Patch Links:
https://github.com/audiokit/AudioKit/pull/595.patch
https://github.com/audiokit/AudioKit/pull/595.diff
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.

cool thanks guys - It felt a little bold of me to remove your code, that's why I left it in commented out in case you didn't agree. But, I'll clean it up now!


[Keyvault] az keyvault backup start: Add status in output

Related command

az keyvault backup start
Description

In previous PR #26422 to upgrade the azure-keyvault-administration SDK, the output for az keyvault backup start had a breaking change to keep only folderUrl. Customer reported that status is also useful info so this PR adds status back.
Testing Guide

History Notes

[Component Name 1] BREAKING CHANGE: az command a: Make some customer-facing breaking change
[Component Name 2] az command b: Add some customer-facing feature

This checklist is used to make sure that common guidelines for a pull request are followed.

[ ] The PR title and description has followed the guideline in Submitting Pull Requests.

[ ] I adhere to the Command Guidelines.

[ ] I adhere to the Error Handling Guidelines.

Keyvault


Can't specify callback function

Hi,
I ran into a problem where I can't add callback functions to the default config because it always returns with an error:
Uncaught TypeError: d.call is not a function
    at k.b (theme.min.js:4)
    at c.i [as fire] (tinymce.min.js:8)
    at k.fire (theme.min.js:2)
    at k.<anonymous> (theme.min.js:3)
    at c.i [as fire] (tinymce.min.js:8)
    at k.fire (theme.min.js:2)
    at HTMLDivElement.c (theme.min.js:1)
    at m (tinymce.min.js:2)
    at HTMLDivElement.y (tinymce.min.js:2)
b @ theme.min.js:4
i @ tinymce.min.js:8
fire @ theme.min.js:2
(anonymous) @ theme.min.js:3
i @ tinymce.min.js:8
fire @ theme.min.js:2
c @ theme.min.js:1
m @ tinymce.min.js:2
y @ tinymce.min.js:2

The callback function is defined as a string, and it looks like TInymce treats it as a string rather than a function which causes the problem. Am I doing something wrong?
Looks like the same issue has been fixed in django-tinyme before: https://github.com/aljosa/django-tinymce/issues/152 I'm not sure if the same thing is happening here or not.

All JavaScript callbacks must be defined via TINYMCE_CALLBACKS config option: http://romanvm.github.io/django-tinymce4-lite/configuration.html#application-configuration

This solved it in a second, I read through the documentation multiple times but must have carefully missed this section.
Thank you! 👍


[Request]: upgrade Beyond Compare to v4.4.7

Prerequisites

[X] I have searched all issues/PRs to ensure it has not already been reported or fixed.

Criteria

[X] Reasonably well-known and widely used (e.g. if it's a GitHub project, it should have at least 100 stars and/or 50 forks)
[X] English interface (or at least English documentation)
[X] Latest stable version
[X] Full version (i.e. not a trial version)
[X] Fairly standard install (e.g. uses a version-specific download URL, no elaborate pre/post install scripts)

Name
Beyond Compare
Description
(Same as existing package)
Homepage
https://www.scootersoftware.com/
Download Link(s)
https://www.scootersoftware.com/kb/dl4_winalternate
Some Indication of Popularity/Repute
Package already exists, needs update.
(PS: Should there be a separate Update Request issue type offered? Both Bug and Request don't really fit the bill.)

Sorry, I now see there is already a PR: #12120


Corrected required declaration of PodioByLine.php

It used to have lower case l instead of L. That created problems on linux systems which are case sensitive.

Fixed by dda9ebf0f35df59fa967164f3e458661154e7801