Not able to install this chart - Error: YAML parse error on traefik/templates/deployment.yaml: error converting YAML to JSON: yaml: line 35: mapping values are not allowed in this context

Just copied the values.yaml and made minimal adjustments:
certResolver: "leresolver"
persistence.enabled: true
additionalArguments:
  - "--certificatesresolvers.leresolver.acme.storage=/data/acme.json"
  - "--certificatesresolvers.leresolver.acme.tlschallenge=true"
  - "--certificatesresolvers.leresolver.acme.httpchallenge=true"
  - "--certificatesresolvers.leresolver.acme.httpchallenge.entrypoint=web"
  -<EMAIL_ADDRESS>  - "--certificatesresolvers.leresolver.acme.caserver=https://acme-staging-v02.api.letsencrypt.org/directory"

Then executed:
helm upgrade --install traefik traefik/traefik  -f /path/to/values.yaml  --namespace default
which results in:
Release "traefik" does not exist. Installing it now.
W0610 10:20:51.255512 2362191 warnings.go:70] apiextensions.k8s.io/v1beta1 CustomResourceDefinition is deprecated in v1.16+, unavailable in v1.22+; use apiextensions.k8s.io/v1 CustomResourceDefinition
W0610 10:20:51.333222 2362191 warnings.go:70] apiextensions.k8s.io/v1beta1 CustomResourceDefinition is deprecated in v1.16+, unavailable in v1.22+; use apiextensions.k8s.io/v1 CustomResourceDefinition
W0610 10:20:51.401750 2362191 warnings.go:70] apiextensions.k8s.io/v1beta1 CustomResourceDefinition is deprecated in v1.16+, unavailable in v1.22+; use apiextensions.k8s.io/v1 CustomResourceDefinition
W0610 10:20:51.580603 2362191 warnings.go:70] apiextensions.k8s.io/v1beta1 CustomResourceDefinition is deprecated in v1.16+, unavailable in v1.22+; use apiextensions.k8s.io/v1 CustomResourceDefinition
W0610 10:20:51.674921 2362191 warnings.go:70] apiextensions.k8s.io/v1beta1 CustomResourceDefinition is deprecated in v1.16+, unavailable in v1.22+; use apiextensions.k8s.io/v1 CustomResourceDefinition
W0610 10:20:51.748299 2362191 warnings.go:70] apiextensions.k8s.io/v1beta1 CustomResourceDefinition is deprecated in v1.16+, unavailable in v1.22+; use apiextensions.k8s.io/v1 CustomResourceDefinition
W0610 10:20:51.821993 2362191 warnings.go:70] apiextensions.k8s.io/v1beta1 CustomResourceDefinition is deprecated in v1.16+, unavailable in v1.22+; use apiextensions.k8s.io/v1 CustomResourceDefinition
Error: YAML parse error on traefik/templates/deployment.yaml: error converting YAML to JSON: yaml: line 35: mapping values are not allowed in this context

Could you try with:
helm upgrade --dry-run --debug --install traefik traefik/traefik -f /path/to/values.yaml --namespace default
It would show you Helm generated YAML files, without applying them.
You should be able to find the content of your deployment.yaml
If you're still not sure what the issue could be, looking at it: send a copy here.
I've generated one using the latest chart and your sample values:
apiVersion: apps/v1
kind: Deployment
metadata:
  name: traefik
  labels:
    app.kubernetes.io/name: traefik
    helm.sh/chart: traefik-9.19.1
    app.kubernetes.io/managed-by: Helm
    app.kubernetes.io/instance: traefik
  annotations:
spec:
  replicas: 1
  selector:
    matchLabels:
      app.kubernetes.io/name: traefik
      app.kubernetes.io/instance: traefik
  strategy:
    type: RollingUpdate
    rollingUpdate:
      maxSurge: 1
      maxUnavailable: 1
  template:
    metadata:
      annotations:
      labels:
        app.kubernetes.io/name: traefik
        helm.sh/chart: traefik-9.19.1
        app.kubernetes.io/managed-by: Helm
        app.kubernetes.io/instance: traefik
    spec:
      serviceAccountName: traefik
      terminationGracePeriodSeconds: 60
      hostNetwork: false
      containers:
      - image: "traefik:2.4.8"
        imagePullPolicy: IfNotPresent
        name: traefik
        resources:
        readinessProbe:
          httpGet:
            path: /ping
            port: 9000
          failureThreshold: 1
          initialDelaySeconds: 10
          periodSeconds: 10
          successThreshold: 1
          timeoutSeconds: 2
        livenessProbe:
          httpGet:
            path: /ping
            port: 9000
          failureThreshold: 3
          initialDelaySeconds: 10
          periodSeconds: 10
          successThreshold: 1
          timeoutSeconds: 2
        ports:
        - name: "traefik"
          containerPort: 9000
          protocol: "TCP"
        - name: "web"
          containerPort: 8000
          protocol: "TCP"
        - name: "websecure"
          containerPort: 8443
          protocol: "TCP"
        securityContext:
          capabilities:
            drop:
            - ALL
          readOnlyRootFilesystem: true
          runAsGroup: 65532
          runAsNonRoot: true
          runAsUser: 65532
        volumeMounts:
          - name: data
            mountPath: /data
          - name: tmp
            mountPath: /tmp
        args:
          - "--global.checknewversion"
          - "--global.sendanonymoususage"
          - "--entryPoints.traefik.address=:9000/tcp"
          - "--entryPoints.web.address=:8000/tcp"
          - "--entryPoints.websecure.address=:8443/tcp"
          - "--api.dashboard=true"
          - "--ping=true"
          - "--providers.kubernetescrd"
          - "--providers.kubernetesingress"
          - "--certificatesresolvers.leresolver.acme.storage=/data/acme.json"
          - "--certificatesresolvers.leresolver.acme.tlschallenge=true"
          - "--certificatesresolvers.leresolver.acme.httpchallenge=true"
          - "--certificatesresolvers.leresolver.acme.httpchallenge.entrypoint=web"
          -<EMAIL_ADDRESS>          - "--certificatesresolvers.leresolver.acme.caserver=https://acme-staging-v02.api.letsencrypt.org/directory"
      volumes:
        - name: data
          emptyDir: {}
        - name: tmp
          emptyDir: {}
      securityContext:
        fsGroup: 65532

Resulting object is valid, I can apply it: I'm not sure what could be wrong in your case.

I get the same error when installing the helm chart with an unmodified values.yaml.  Interestingly my old values.yaml does not trigger the error.  Installing without supplying a values.yaml also works.
Here (in order) are the error message, the new, faulty values.yaml, and the old, working values.yaml from December 2020.
install.go:190: [debug] CHART PATH: /Users/ithil/Library/Caches/helm/repository/traefik-9.1.1.tgz

install.go:190: [debug] WARNING: This chart or one of its subcharts contains CRDs. Rendering may fail or contain inaccuracies.
Error: YAML parse error on traefik/templates/deployment.yaml: error converting YAML to JSON: yaml: line 35: mapping values are not allowed in this context
helm.go:81: [debug] error converting YAML to JSON: yaml: line 35: mapping values are not allowed in this context
YAML parse error on traefik/templates/deployment.yaml
helm.sh/helm/v3/pkg/releaseutil.(*manifestFile).sort
        /private/tmp/helm-20210310-51670-30olmy/pkg/releaseutil/manifest_sorter.go:146
helm.sh/helm/v3/pkg/releaseutil.SortManifests
        /private/tmp/helm-20210310-51670-30olmy/pkg/releaseutil/manifest_sorter.go:106
helm.sh/helm/v3/pkg/action.(*Configuration).renderResources
        /private/tmp/helm-20210310-51670-30olmy/pkg/action/action.go:165
helm.sh/helm/v3/pkg/action.(*Install).Run
        /private/tmp/helm-20210310-51670-30olmy/pkg/action/install.go:240
main.runInstall
        /private/tmp/helm-20210310-51670-30olmy/cmd/helm/install.go:242
main.newUpgradeCmd.func2
        /private/tmp/helm-20210310-51670-30olmy/cmd/helm/upgrade.go:115
github.com/spf13/cobra.(*Command).execute
        /Users/brew/Library/Caches/Homebrew/go_mod_cache/pkg/mod/github.com/spf13/cobra@v1.1.1/command.go:850
github.com/spf13/cobra.(*Command).ExecuteC
        /Users/brew/Library/Caches/Homebrew/go_mod_cache/pkg/mod/github.com/spf13/cobra@v1.1.1/command.go:958
github.com/spf13/cobra.(*Command).Execute
        /Users/brew/Library/Caches/Homebrew/go_mod_cache/pkg/mod/github.com/spf13/cobra@v1.1.1/command.go:895
main.main
        /private/tmp/helm-20210310-51670-30olmy/cmd/helm/helm.go:80
runtime.main
        /usr/local/Cellar/go/1.16/libexec/src/runtime/proc.go:225
runtime.goexit
        /usr/local/Cellar/go/1.16/libexec/src/runtime/asm_amd64.s:1371

The new values.yaml:
# Default values for Traefik
image:
  name: traefik
  # defaults to appVersion
  tag: ""
  pullPolicy: IfNotPresent

#
# Configure the deployment
#
deployment:
  enabled: true
  # Can be either Deployment or DaemonSet
  kind: Deployment
  # Number of pods of the deployment (only applies when kind == Deployment)
  replicas: 1
  # Additional deployment annotations (e.g. for jaeger-operator sidecar injection)
  annotations: {}
  # Additional deployment labels (e.g. for filtering deployment by custom labels)
  labels: {}
  # Additional pod annotations (e.g. for mesh injection or prometheus scraping)
  podAnnotations: {}
  # Additional Pod labels (e.g. for filtering Pod by custom labels)
  podLabels: {}
  # Additional containers (e.g. for metric offloading sidecars)
  additionalContainers: []
    # https://docs.datadoghq.com/developers/dogstatsd/unix_socket/?tab=host
    # - name: socat-proxy
    # image: alpine/socat:1.0.5
    # args: ["-s", "-u", "udp-recv:8125", "unix-sendto:/socket/socket"]
    # volumeMounts:
    #   - name: dsdsocket
    #     mountPath: /socket
  # Additional volumes available for use with initContainers and additionalContainers
  additionalVolumes: []
    # - name: dsdsocket
    #   hostPath:
    #     path: /var/run/statsd-exporter
  # Additional initContainers (e.g. for setting file permission as shown below)
  initContainers: []
    # The "volume-permissions" init container is required if you run into permission issues.
    # Related issue: https://github.com/traefik/traefik/issues/6972
    # - name: volume-permissions
    #   image: busybox:1.31.1
    #   command: ["sh", "-c", "chmod -Rv 600 /data/*"]
    #   volumeMounts:
    #     - name: data
    #       mountPath: /data
  # Custom pod DNS policy. Apply if `hostNetwork: true`
  # dnsPolicy: ClusterFirstWithHostNet
  # Additional imagePullSecrets
  imagePullSecrets: []
   # - name: myRegistryKeySecretName

# Pod disruption budget
podDisruptionBudget:
  enabled: false
  # maxUnavailable: 1
  # minAvailable: 0

# Use ingressClass. Ignored if Traefik version < 2.3 / kubernetes < 1.18.x
ingressClass:
  # true is not unit-testable yet, pending https://github.com/rancher/helm-unittest/pull/12
  enabled: false
  isDefaultClass: false
  # Use to force a networking.k8s.io API Version for certain CI/CD applications. E.g. "v1beta1"
  fallbackApiVersion:

# Activate Pilot integration
pilot:
  enabled: false
  token: ""
  # Toggle Pilot Dashboard
  # dashboard: false

# Enable experimental features
experimental:
  plugins:
    enabled: false
  kubernetesGateway:
    enabled: false
    appLabelSelector: "traefik"
    certificates: []
    # - group: "core"
    #   kind: "Secret"
    #   name: "mysecret"

# Create an IngressRoute for the dashboard
ingressRoute:
  dashboard:
    enabled: true
    # Additional ingressRoute annotations (e.g. for kubernetes.io/ingress.class)
    annotations: {}
    # Additional ingressRoute labels (e.g. for filtering IngressRoute by custom labels)
    labels: {}

rollingUpdate:
  maxUnavailable: 1
  maxSurge: 1

#
# Configure providers
#
providers:
  kubernetesCRD:
    enabled: true
    namespaces: []
      # - "default"
  kubernetesIngress:
    enabled: true
    # labelSelector: environment=production,method=traefik
    namespaces: []
      # - "default"
    # IP used for Kubernetes Ingress endpoints
    publishedService:
      enabled: false
      # Published Kubernetes Service to copy status from. Format: namespace/servicename
      # By default this Traefik service
      # pathOverride: ""

#
# Add volumes to the traefik pod. The volume name will be passed to tpl.
# This can be used to mount a cert pair or a configmap that holds a config.toml file.
# After the volume has been mounted, add the configs into traefik by using the `additionalArguments` list below, eg:
# additionalArguments:
# - "--providers.file.filename=/config/dynamic.toml"
# - "--ping"
# - "--ping.entrypoint=web"
volumes: []
# - name: public-cert
#   mountPath: "/certs"
#   type: secret
# - name: '{{ printf "%s-configs" .Release.Name }}'
#   mountPath: "/config"
#   type: configMap

# Additional volumeMounts to add to the Traefik container
additionalVolumeMounts: []
  # For instance when using a logshipper for access logs
  # - name: traefik-logs
  #   mountPath: /var/log/traefik

# Logs
# https://docs.traefik.io/observability/logs/
logs:
  # Traefik logs concern everything that happens to Traefik itself (startup, configuration, events, shutdown, and so on).
  general:
    # By default, the logs use a text format (common), but you can
    # also ask for the json format in the format option
    # format: json
    # By default, the level is set to ERROR. Alternative logging levels are DEBUG, PANIC, FATAL, ERROR, WARN, and INFO.
    level: ERROR
  access:
    # To enable access logs
    enabled: false
    # By default, logs are written using the Common Log Format (CLF).
    # To write logs in JSON, use json in the format option.
    # If the given format is unsupported, the default (CLF) is used instead.
    # format: json
    # To write the logs in an asynchronous fashion, specify a bufferingSize option.
    # This option represents the number of log lines Traefik will keep in memory before writing
    # them to the selected output. In some cases, this option can greatly help performances.
    # bufferingSize: 100
    # Filtering https://docs.traefik.io/observability/access-logs/#filtering
    filters: {}
      # statuscodes: "200,300-302"
      # retryattempts: true
      # minduration: 10ms
    # Fields
    # https://docs.traefik.io/observability/access-logs/#limiting-the-fieldsincluding-headers
    fields:
      general:
        defaultmode: keep
        names: {}
          # Examples:
          # ClientUsername: drop
      headers:
        defaultmode: drop
        names: {}
          # Examples:
          # User-Agent: redact
          # Authorization: drop
          # Content-Type: keep

globalArguments:
  - "--global.checknewversion"
  - "--global.sendanonymoususage"

#
# Configure Traefik static configuration
# Additional arguments to be passed at Traefik's binary
# All available options available on https://docs.traefik.io/reference/static-configuration/cli/
## Use curly braces to pass values: `helm install --set="additionalArguments={--providers.kubernetesingress.ingressclass=traefik-internal,--log.level=DEBUG}"`
additionalArguments: []
#  - "--providers.kubernetesingress.ingressclass=traefik-internal"
#  - "--log.level=DEBUG"

# Environment variables to be passed to Traefik's binary
env: []
# - name: SOME_VAR
#   value: some-var-value
# - name: SOME_VAR_FROM_CONFIG_MAP
#   valueFrom:
#     configMapRef:
#       name: configmap-name
#       key: config-key
# - name: SOME_SECRET
#   valueFrom:
#     secretKeyRef:
#       name: secret-name
#       key: secret-key

envFrom: []
# - configMapRef:
#     name: config-map-name
# - secretRef:
#     name: secret-name

# Configure ports
ports:
  # The name of this one can't be changed as it is used for the readiness and
  # liveness probes, but you can adjust its config to your liking
  traefik:
    port: 9000
    # Use hostPort if set.
    # hostPort: 9000
    #
    # Use hostIP if set. If not set, Kubernetes will default to <IP_ADDRESS>, which
    # means it's listening on all your interfaces and all your IPs. You may want
    # to set this value if you need traefik to listen on specific interface
    # only.
    # hostIP: <IP_ADDRESS>

    # Override the liveness/readiness port. This is useful to integrate traefik
    # with an external Load Balancer that performs healthchecks.
    # healthchecksPort: 9000

    # Defines whether the port is exposed if service.type is LoadBalancer or
    # NodePort.
    #
    # You SHOULD NOT expose the traefik port on production deployments.
    # If you want to access it from outside of your cluster,
    # use `kubectl port-forward` or create a secure ingress
    expose: false
    # The exposed port for this service
    exposedPort: 9000
    # The port protocol (TCP/UDP)
    protocol: TCP
  web:
    port: 8000
    # hostPort: 8000
    expose: true
    exposedPort: 80
    # The port protocol (TCP/UDP)
    protocol: TCP
    # Use nodeport if set. This is useful if you have configured Traefik in a
    # LoadBalancer
    # nodePort: 32080
    # Port Redirections
    # Added in 2.2, you can make permanent redirects via entrypoints.
    # https://docs.traefik.io/routing/entrypoints/#redirection
    # redirectTo: websecure
  websecure:
    port: 8443
    # hostPort: 8443
    expose: true
    exposedPort: 443
    # The port protocol (TCP/UDP)
    protocol: TCP
    # nodePort: 32443
    # Set TLS at the entrypoint
    # https://doc.traefik.io/traefik/routing/entrypoints/#tls
    tls:
      enabled: false
      # this is the name of a TLSOption definition
      options: ""
      certResolver: ""
      domains: []
      # - main: example.com
      #   sans:
      #     - foo.example.com
      #     - bar.example.com

# TLS Options are created as TLSOption CRDs
# https://doc.traefik.io/traefik/https/tls/#tls-options
# Example:
# tlsOptions:
#   default:
#     sniStrict: true
#     preferServerCipherSuites: true
#   foobar:
#     curvePreferences:
#       - CurveP521
#       - CurveP384
tlsOptions: {}

# Options for the main traefik service, where the entrypoints traffic comes
# from.
service:
  enabled: true
  type: LoadBalancer
  # Additional annotations (e.g. for cloud provider specific config)
  annotations: {}
  # Additional service labels (e.g. for filtering Service by custom labels)
  labels: {}
  # Additional entries here will be added to the service spec. Cannot contains
  # type, selector or ports entries.
  spec: {}
    # externalTrafficPolicy: Cluster
    # loadBalancerIP: "<IP_ADDRESS>"
    # clusterIP: "<IP_ADDRESS>"
  loadBalancerSourceRanges: []
    # - <IP_ADDRESS>/32
    # - <IP_ADDRESS>/16
  externalIPs: []
    # - <IP_ADDRESS>

## Create HorizontalPodAutoscaler object.
##
autoscaling:
  enabled: false
#   minReplicas: 1
#   maxReplicas: 10
#   metrics:
#   - type: Resource
#     resource:
#       name: cpu
#       targetAverageUtilization: 60
#   - type: Resource
#     resource:
#       name: memory
#       targetAverageUtilization: 60

# Enable persistence using Persistent Volume Claims
# ref: http://kubernetes.io/docs/user-guide/persistent-volumes/
# After the pvc has been mounted, add the configs into traefik by using the `additionalArguments` list below, eg:
# additionalArguments:
# - "--certificatesresolvers.le.acme.storage=/data/acme.json"
# It will persist TLS certificates.
persistence:
  enabled: false
  name: data
#  existingClaim: ""
  accessMode: ReadWriteOnce
  size: 128Mi
  # storageClass: ""
  path: /data
  annotations: {}
  # subPath: "" # only mount a subpath of the Volume into the pod

# If hostNetwork is true, runs traefik in the host network namespace
# To prevent unschedulabel pods due to port collisions, if hostNetwork=true
# and replicas>1, a pod anti-affinity is recommended and will be set if the
# affinity is left as default.
hostNetwork: false

# Whether Role Based Access Control objects like roles and rolebindings should be created
rbac:
  enabled: true

  # If set to false, installs ClusterRole and ClusterRoleBinding so Traefik can be used across namespaces.
  # If set to true, installs namespace-specific Role and RoleBinding and requires provider configuration be set to that same namespace
  namespaced: false

# Enable to create a PodSecurityPolicy and assign it to the Service Account via RoleBinding or ClusterRoleBinding
podSecurityPolicy:
  enabled: false

# The service account the pods will use to interact with the Kubernetes API
serviceAccount:
  # If set, an existing service account is used
  # If not set, a service account is created automatically using the fullname template
  name: ""

# Additional serviceAccount annotations (e.g. for oidc authentication)
serviceAccountAnnotations: {}

resources: {}
  # requests:
  #   cpu: "100m"
  #   memory: "50Mi"
  # limits:
  #   cpu: "300m"
  #   memory: "150Mi"
affinity: {}
# # This example pod anti-affinity forces the scheduler to put traefik pods
# # on nodes where no other traefik pods are scheduled.
# # It should be used when hostNetwork: true to prevent port conflicts
#   podAntiAffinity:
#     requiredDuringSchedulingIgnoredDuringExecution:
#     - labelSelector:
#         matchExpressions:
#         - key: app
#           operator: In
#           values:
#           - {{ template "traefik.name" . }}
#       topologyKey: failure-domain.beta.kubernetes.io/zone
nodeSelector: {}
tolerations: []

# Pods can have priority.
# Priority indicates the importance of a Pod relative to other Pods.
priorityClassName: ""

# Set the container security context
# To run the container with ports below 1024 this will need to be adjust to run as root
securityContext:
  capabilities:
    drop: [ALL]
  readOnlyRootFilesystem: true
  runAsGroup: 65532
  runAsNonRoot: true
  runAsUser: 65532

podSecurityContext:
  fsGroup: 65532

The old, working values.yaml
# Default values for Traefik
image:
  name: traefik
  # defaults to appVersion
  tag: "v2.4.8"
  pullPolicy: IfNotPresent

#
# Configure the deployment
#
deployment:
  enabled: true
  # Number of pods of the deployment
  replicas: 1
  # Additional deployment annotations (e.g. for jaeger-operator sidecar injection)
  annotations: {}
  # Additional pod annotations (e.g. for mesh injection or prometheus scraping)
  podAnnotations: {}
  # Additional Pod labels (e.g. for filtering Pod by custom labels)
  podLabels: {}
  # Additional containers (e.g. for metric offloading sidecars)
  additionalContainers: []
    # https://docs.datadoghq.com/developers/dogstatsd/unix_socket/?tab=host
    # - name: socat-proxy
    # image: alpine/socat:1.0.5
    # args: ["-s", "-u", "udp-recv:8125", "unix-sendto:/socket/socket"]
    # volumeMounts:
    #   - name: dsdsocket
    #     mountPath: /socket
  # Additional volumes available for use with initContainers and additionalContainers
  additionalVolumes: []
    # - name: dsdsocket
    #   hostPath:
    #   path: /var/run/statsd-exporter
  # Additional initContainers (e.g. for setting file permission as shown below)
  initContainers: []
    # The "volume-permissions" init container is required if you run into permission issues.
    # Related issue: https://github.com/traefik/traefik/issues/6972
    # - name: volume-permissions
    #   image: busybox:1.31.1
    #   command: ["sh", "-c", "chmod -Rv 600 /data/*"]
    #   volumeMounts:
    #     - name: data
    #       mountPath: /data
  # Custom pod DNS policy. Apply if `hostNetwork: true`
  # dnsPolicy: ClusterFirstWithHostNet
  # Additional imagePullSecrets
  imagePullSecrets: []
   # - name: myRegistryKeySecretName

# Pod disruption budget
podDisruptionBudget:
  enabled: false
  # maxUnavailable: 1
  # minAvailable: 0

# Use ingressClass. Ignored if Traefik version < 2.3 / kubernetes < 1.18.x
ingressClass:
  # true is not unit-testable yet, pending https://github.com/rancher/helm-unittest/pull/12
  enabled: false
  isDefaultClass: false

# Activate Pilot integration
pilot:
  enabled: false
  token: ""

# Enable experimental features
experimental:
  plugins:
    enabled: false

# Create an IngressRoute for the dashboard
ingressRoute:
  dashboard:
    enabled: true
    # Additional ingressRoute annotations (e.g. for kubernetes.io/ingress.class)
    annotations: {}
    # Additional ingressRoute labels (e.g. for filtering IngressRoute by custom labels)
    labels: {}

rollingUpdate:
  maxUnavailable: 1
  maxSurge: 1

#
# Configure providers
#
providers:
  kubernetesCRD:
    enabled: true
    namespaces: []
      # - "default"
  kubernetesIngress:
    enabled: true
    namespaces: []
      # - "default"
    # IP used for Kubernetes Ingress endpoints
    publishedService:
      enabled: false
      # Published Kubernetes Service to copy status from. Format: namespace/servicename
      # By default this Traefik service
      # pathOverride: ""

#
# Add volumes to the traefik pod. The volume name will be passed to tpl.
# This can be used to mount a cert pair or a configmap that holds a config.toml file.
# After the volume has been mounted, add the configs into traefik by using the `additionalArguments` list below, eg:
# additionalArguments:
# - "--providers.file.filename=/config/dynamic.toml"
volumes:
  - name: traefik-config
    mountPath: "/static_config"
    type: configMap

# - name: public-cert
#   mountPath: "/certs"
#   type: secret
# - name: '{{ printf "%s-configs" .Release.Name }}'
#   mountPath: "/config"
#   type: configMap

# Additional volumeMounts to add to the Traefik container
additionalVolumeMounts: []
  # - name: static-config-volume
  #   mountPath: /static_config
# For instance when using a logshipper for access logs
# - name: traefik-logs
#   mountPath: /var/log/traefik

# Logs
# https://docs.traefik.io/observability/logs/
logs:
  # Traefik logs concern everything that happens to Traefik itself (startup, configuration, events, shutdown, and so on).
  general:
    # By default, the logs use a text format (common), but you can
    # also ask for the json format in the format option
    # format: json
    # By default, the level is set to ERROR. Alternative logging levels are DEBUG, PANIC, FATAL, ERROR, WARN, and INFO.
    level: ERROR
  access:
    # To enable access logs
    enabled: true
    # By default, logs are written using the Common Log Format (CLF).
    # To write logs in JSON, use json in the format option.
    # If the given format is unsupported, the default (CLF) is used instead.
    # format: json
    # To write the logs in an asynchronous fashion, specify a bufferingSize option.
    # This option represents the number of log lines Traefik will keep in memory before writing
    # them to the selected output. In some cases, this option can greatly help performances.
    # bufferingSize: 100
    # Filtering https://docs.traefik.io/observability/access-logs/#filtering
    filters: {}
      # statuscodes: "200,300-302"
      # retryattempts: true
      # minduration: 10ms
    # Fields
    # https://docs.traefik.io/observability/access-logs/#limiting-the-fieldsincluding-headers
    fields:
      general:
        defaultmode: keep
        names: {}
          # Examples:
          # ClientUsername: drop
      headers:
        defaultmode: drop
        names: {}
          # Examples:
          # User-Agent: redact
          # Authorization: drop
          # Content-Type: keep

globalArguments:
  - "--global.checknewversion"
  - "--global.sendanonymoususage"

#
# Configure Traefik static configuration
# Additional arguments to be passed at Traefik's binary
# All available options available on https://docs.traefik.io/reference/static-configuration/cli/
## Use curly braces to pass values: `helm install --set="additionalArguments={--providers.kubernetesingress.ingressclass=traefik-internal,--log.level=DEBUG}"`
additionalArguments: []
  # - "--providers.file.filename=/static_config/config.toml"
  # - "--configFile=/static_config/config.toml"
#  - "--providers.kubernetesingress.ingressclass=traefik-internal"
#  - "--log.level=DEBUG"

# Environment variables to be passed to Traefik's binary
env: []
# - name: SOME_VAR
#   value: some-var-value
# - name: SOME_VAR_FROM_CONFIG_MAP
#   valueFrom:
#     configMapRef:
#       name: configmap-name
#       key: config-key
# - name: SOME_SECRET
#   valueFrom:
#     secretKeyRef:
#       name: secret-name
#       key: secret-key

envFrom: []
# - configMapRef:
#     name: config-map-name
# - secretRef:
#     name: secret-name

# Configure ports
ports:
  # The name of this one can't be changed as it is used for the readiness and
  # liveness probes, but you can adjust its config to your liking
  traefik:
    port: 9000
    # Use hostPort if set.
    # hostPort: 9000
    #
    # Use hostIP if set. If not set, Kubernetes will default to <IP_ADDRESS>, which
    # means it's listening on all your interfaces and all your IPs. You may want
    # to set this value if you need traefik to listen on specific interface
    # only.
    # hostIP: <IP_ADDRESS>

    # Defines whether the port is exposed if service.type is LoadBalancer or
    # NodePort.
    #
    # You SHOULD NOT expose the traefik port on production deployments.
    # If you want to access it from outside of your cluster,
    # use `kubectl port-forward` or create a secure ingress
    expose: false
    # The exposed port for this service
    exposedPort: 9000
    # The port protocol (TCP/UDP)
    protocol: TCP
  web:
    port: 8000
    # hostPort: 8000
    expose: true
    exposedPort: 80
    # The port protocol (TCP/UDP)
    protocol: TCP
    # Use nodeport if set. This is useful if you have configured Traefik in a
    # LoadBalancer
    # nodePort: 32080
    # Port Redirections
    # Added in 2.2, you can make permanent redirects via entrypoints.
    # https://docs.traefik.io/routing/entrypoints/#redirection
    # redirectTo: websecure
  websecure:
    port: 8443
    # hostPort: 8443
    expose: true
    exposedPort: 443
    # The port protocol (TCP/UDP)
    protocol: TCP
    # nodePort: 32443
    # Set TLS at the entrypoint
    # https://doc.traefik.io/traefik/routing/entrypoints/#tls
    tls:
      enabled: true
      # this is the name of a TLSOption definition
      options: ""
      certResolver: ""
      domains: []
      # - main: example.com
      #   sans:
      #     - foo.example.com
      #     - bar.example.com

# TLS Options are created as TLSOption CRDs
# https://doc.traefik.io/traefik/https/tls/#tls-options
# Example:
# tlsOptions:
#   default:
#     sniStrict: true
#     preferServerCipherSuites: true
#   foobar:
#     curvePreferences:
#       - CurveP521
#       - CurveP384
tlsOptions: {}

# Options for the main traefik service, where the entrypoints traffic comes
# from.
service:
  enabled: true
  type: LoadBalancer
  # Additional annotations (e.g. for cloud provider specific config)
  annotations: {}
  # Additional service labels (e.g. for filtering Service by custom labels)
  labels: {}
  # Additional entries here will be added to the service spec. Cannot contains
  # type, selector or ports entries.
  spec:
    # clusterIP: "<IP_ADDRESS>"
    # externalTrafficPolicy: Cluster
    loadBalancerIP: "<IP_ADDRESS>"
    # clusterIP: "<IP_ADDRESS>"
  loadBalancerSourceRanges: []
    # - <IP_ADDRESS>/16
    # - <IP_ADDRESS>/32
  externalIPs: []
    # - <IP_ADDRESS>

## Create HorizontalPodAutoscaler object.
##
autoscaling:
  enabled: true
  minReplicas: 1
  maxReplicas: 4
#   metrics:
#   - type: Resource
#     resource:
#       name: cpu
#       targetAverageUtilization: 60
#   - type: Resource
#     resource:
#       name: memory
#       targetAverageUtilization: 60

# Enable persistence using Persistent Volume Claims
# ref: http://kubernetes.io/docs/user-guide/persistent-volumes/
# After the pvc has been mounted, add the configs into traefik by using the `additionalArguments` list below, eg:
# additionalArguments:
# - "--certificatesresolvers.le.acme.storage=/data/acme.json"
# It will persist TLS certificates.
persistence:
  enabled: false
#  existingClaim: ""
  accessMode: ReadWriteOnce
  size: 128Mi
  # storageClass: ""
  path: /data
  annotations: {}
  # subPath: "" # only mount a subpath of the Volume into the pod

# If hostNetwork is true, runs traefik in the host network namespace
# To prevent unschedulabel pods due to port collisions, if hostNetwork=true
# and replicas>1, a pod anti-affinity is recommended and will be set if the
# affinity is left as default.
hostNetwork: false

# Whether Role Based Access Control objects like roles and rolebindings should be created
rbac:
  enabled: true

  # If set to false, installs ClusterRole and ClusterRoleBinding so Traefik can be used across namespaces.
  # If set to true, installs namespace-specific Role and RoleBinding and requires provider configuration be set to that same namespace
  namespaced: false

# Enable to create a PodSecurityPolicy and assign it to the Service Account via RoleBindin or ClusterRoleBinding
podSecurityPolicy:
  enabled: false

# The service account the pods will use to interact with the Kubernetes API
serviceAccount:
  # If set, an existing service account is used
  # If not set, a service account is created automatically using the fullname template
  name: ""

# Additional serviceAccount annotations (e.g. for oidc authentication)
serviceAccountAnnotations: {}

resources: {}
  # requests:
  #   cpu: "100m"
  #   memory: "50Mi"
  # limits:
  #   cpu: "300m"
  #   memory: "150Mi"
affinity: {}
# # This example pod anti-affinity forces the scheduler to put traefik pods
# # on nodes where no other traefik pods are scheduled.
# # It should be used when hostNetwork: true to prevent port conflicts
#   podAntiAffinity:
#     requiredDuringSchedulingIgnoredDuringExecution:
#     - labelSelector:
#         matchExpressions:
#         - key: app
#           operator: In
#           values:
#           - {{ template "traefik.name" . }}
#       topologyKey: failure-domain.beta.kubernetes.io/zone
nodeSelector: {}
tolerations: []

# Pods can have priority.
# Priority indicates the importance of a Pod relative to other Pods.
priorityClassName: ""

# Set the container security context
# To run the container with ports below 1024 this will need to be adjust to run as root
securityContext:
  capabilities:
    drop: [ALL]
  readOnlyRootFilesystem: true
  runAsGroup: 65532
  runAsNonRoot: true
  runAsUser: 65532

podSecurityContext:
  fsGroup: 65532

Using your new values, I could not reproduce the issue. The deployment object generated is valid and can be created:
---
# Source: traefik/templates/deployment.yaml
apiVersion: apps/v1
kind: Deployment
metadata:
  name: traefik
  namespace: default
  labels:
    app.kubernetes.io/name: traefik
    helm.sh/chart: traefik-9.19.1
    app.kubernetes.io/managed-by: Helm
    app.kubernetes.io/instance: traefik
  annotations:
spec:
  replicas: 1
  selector:
    matchLabels:
      app.kubernetes.io/name: traefik
      app.kubernetes.io/instance: traefik
  strategy:
    type: RollingUpdate
    rollingUpdate:
      maxSurge: 1
      maxUnavailable: 1
  template:
    metadata:
      annotations:
      labels:
        app.kubernetes.io/name: traefik
        helm.sh/chart: traefik-9.19.1
        app.kubernetes.io/managed-by: Helm
        app.kubernetes.io/instance: traefik
    spec:
      serviceAccountName: traefik
      terminationGracePeriodSeconds: 60
      hostNetwork: false
      containers:
      - image: "traefik:2.4.8"
        imagePullPolicy: IfNotPresent
        name: traefik
        resources:
        readinessProbe:
          httpGet:
            path: /ping
            port: 9000
          failureThreshold: 1
          initialDelaySeconds: 10
          periodSeconds: 10
          successThreshold: 1
          timeoutSeconds: 2
        livenessProbe:
          httpGet:
            path: /ping
            port: 9000
          failureThreshold: 3
          initialDelaySeconds: 10
          periodSeconds: 10
          successThreshold: 1
          timeoutSeconds: 2
        ports:
        - name: "traefik"
          containerPort: 9000
          protocol: "TCP"
        - name: "web"
          containerPort: 8000
          protocol: "TCP"
        - name: "websecure"
          containerPort: 8443
          protocol: "TCP"
        securityContext:
          capabilities:
            drop:
            - ALL
          readOnlyRootFilesystem: true
          runAsGroup: 65532
          runAsNonRoot: true
          runAsUser: 65532
        volumeMounts:
          - name: data
            mountPath: /data
          - name: tmp
            mountPath: /tmp
        args:
          - "--global.checknewversion"
          - "--global.sendanonymoususage"
          - "--entryPoints.traefik.address=:9000/tcp"
          - "--entryPoints.web.address=:8000/tcp"
          - "--entryPoints.websecure.address=:8443/tcp"
          - "--api.dashboard=true"
          - "--ping=true"
          - "--providers.kubernetescrd"
          - "--providers.kubernetesingress"
      volumes:
        - name: data
          emptyDir: {}
        - name: tmp
          emptyDir: {}
      securityContext:
        fsGroup: 65532

And... testing back with the actual latest Chart version also works, no real change to that Deployment object:
#  diff deployment-431.yaml deployment-431-bis.yaml
10c10
<     helm.sh/chart: traefik-9.19.1
---
>     helm.sh/chart: traefik-9.19.2
30c30
<         helm.sh/chart: traefik-9.19.1
---
>         helm.sh/chart: traefik-9.19.2

Could you tell us: which version of the Chart are you using?
Using Helm dry-run option loading your values would show you the YAML instead of applying them.
If there's a syntax issue, it should be more obvious than trying to guess what's been generated in between.
Feel free to share the output of - especially the definition for the generated Deployment object:
helm upgrade --dry-run --debug --install traefik traefik/traefik -f /path/to/values.yaml --namespace default

Now, line 35 in that yaml is the spec.template.containers[0].image definition.
Between your working and non-working yamls, an obvious difference is that the later does not set an image.tag.
Which, in theory, should default to your Chart appVersion.
As a wild-guess, try to set that tag in your values - or don't mention it at all/don't set an empty string.
How would that go?

In the cases above, the resources key has no value. Set some resources or set it to {} in your values.yaml.


Update DG (target profile, proposition, user stories)

Update target profile, user proposition and user stories sections of DG

lgtm!


mnemonic: rewrite implementation in pure v

Implementing the mnemonic (BIP39) doesn't seems difficult: https://github.com/bitcoin/bips/blob/master/bip-0039.mediawiki
I suggest to drop the broken C library and rewrite implementation in pure V which would drop external dependencies and make code better in control of V.
This would fix #220 and #301

Working first implementation https://github.com/freeflowuniverse/crystallib/commit/1994b20764dcfddf38eac9bccf7c0deaf5811aa1


Added Italian translation

Added Italian translation.
Modified RecordingSession.java to load notification text from strings.xml

Someone already fixed RecordingSession so I rebased and just grabbed the translations. Thanks!


WIP: Changes related to metrics exporter

Description
Expected: Needs to run metrics services as in new pod.
Added initial changes to expose metrics to prometheus.
Notes wrt. folder structure.

Added metrics folder keep changes related to exporter separately.
Will be setting all the metrics value in metrics/collector folder.
All the configuration files added in metrics/deploy folder.

Please suggest any change required to make improve the code as well as design. Would love to address your input.

@rchikatw can you add verification steps, how to verify/test this PR. Thanks

@rchikatw can you add verification steps, how to verify/test this PR. Thanks

this is more or less at my request so that we can sync on on-going issues. We should, though, convert this to a Draft.

Ok, we should be in a non-notification Draft state now. Rohan and I will use this to work out some RBAC issues, but for others that find their way here, no need to review at this time (unless you want to wade in on the RBAC setup ;) )

@rchikatw can you close this PR as the we are going approach as operator-sdk recommendation for metrics

Closing this PR as the another approach is considered.


Heapster can not connect due to invalid certificate

I'm using the v1.0.1 pre-release.
I've created a single machine cluster (v0.19.3) using the KUBERNETES_PROVIDER=ubuntu ./kube-up.sh command. It started normally.
Then I tried to start the Heapster on the "cluster":
wicked@w:~/docker/kubernetes $ kubectl create -f cluster/addons/cluster-monitoring/influxdb --namespace=kube-system
services/monitoring-grafana
replicationcontrollers/monitoring-heapster-v5
services/monitoring-heapster
replicationcontrollers/monitoring-influx-grafana-v1
services/monitoring-influxdb

It has created 5 docker containers running:
a8b397bb47d1        gcr.io/google_containers/heapster_grafana:v0.7                                    "/kuisp -p 8080 -c /   9 minutes ago       Up 9 minutes                                                         k8s_grafana.7ff9ddef_monitoring-influx-grafana-v1-xumof_kube-system_efec7e43-2f69-11e5-9ca4-005056010186_d3fc3378
78ce40555bb7        gcr.io/google_containers/heapster_influxdb:v0.3                                   "/run.sh"              9 minutes ago       Up 9 minutes                                                         k8s_influxdb.787acd0e_monitoring-influx-grafana-v1-xumof_kube-system_efec7e43-2f69-11e5-9ca4-005056010186_03ef2fc5
5bf518831100        gcr.io/google_containers/heapster:v0.16.0                                         "/heapster --source=   9 minutes ago       Up 9 minutes                                                         k8s_heapster.8972800b_monitoring-heapster-v5-jy7o5_kube-system_efd4cc8c-2f69-11e5-9ca4-005056010186_4f1014d0
c5d90b64aca7        gcr.io/google_containers/pause:0.8.0                                              "/pause"               9 minutes ago       Up 9 minutes        <IP_ADDRESS>:8083->8083/tcp, <IP_ADDRESS>:8086->8086/tcp   k8s_POD.fc880c63_monitoring-influx-grafana-v1-xumof_kube-system_efec7e43-2f69-11e5-9ca4-005056010186_46d51def
c63dbddfd38d        gcr.io/google_containers/pause:0.8.0                                              "/pause"               9 minutes ago       Up 9 minutes                                                         k8s_POD.e4cc795_monitoring-heapster-v5-jy7o5_kube-system_efd4cc8c-2f69-11e5-9ca4-005056010186_a34b8057

But the heapster container repeatedly reports an error:
E0721 05:48:45.733960       1 reflector.go:136] Failed to list *api.Node: Get https://<IP_ADDRESS>:443/api/v1/nodes: x509: failed to load system roots and no roots provided
E0721 05:48:45.954969       1 reflector.go:136] Failed to list *api.Pod: Get https://<IP_ADDRESS>:443/api/v1/pods?fieldSelector=spec.nodeName%21%3D: x509: failed to load system roots and no roots provided
E0721 05:48:46.385188       1 reflector.go:136] Failed to list *api.Namespace: Get https://<IP_ADDRESS>:443/api/v1/namespaces: x509: failed to load system roots and no roots provided

Seems to be a duplicate of https://github.com/GoogleCloudPlatform/heapster/issues/422

If I install Heapster according to Heapster's documentation it does not work the same way.

Have you setup Service Accounts in your kubernetes cluster? If not, can you try running heapster with auth disabled as explained here

@vishh sounds good from the point of view that it performs a reguar http-connection. I think this will help me, but in general this is more like avoiding to fix issues with the certificate and with documentation.

Agreed. Kubernetes security config has changes quite a bit over the last
few months. But it should be more stable moving forward. Better
documentation underway.
On Tue, Jul 21, 2015 at 5:05 PM, Alexey Kupershtokh <
<EMAIL_ADDRESS>wrote:

@vishh https://github.com/vishh sounds good from the point of view that
it performs a reguar http-connection. I think this will help me, but in
general this is more like avoiding to fix issues with the certificate and
with documentation.
—
Reply to this email directly or view it on GitHub
https://github.com/GoogleCloudPlatform/kubernetes/issues/11654#issuecomment-123513192
.

I've played a bit with the container.
Actually it starts with the following messages:
wicked@battler-01:~$ docker exec -it 332bc1c82892 /heapster "--source=kubernetes:http://kubernetes-ro?useServiceAccount=true&auth=&insecure=true" "--sink=influxdb:http://monitoring-influxdb:80"
I0723 00:14:46.403805      55 heapster.go:52] /heapster --source=kubernetes:http://kubernetes-ro?useServiceAccount=true&auth=&insecure=true --sink=influxdb:http://monitoring-influxdb:80
I0723 00:14:46.404415      55 heapster.go:53] Heapster version 0.16.0
E0723 00:14:46.405312      55 helper.go:247] expected to load root ca config from /var/run/secrets/kubernetes.io/serviceaccount/ca.crt, but got err: open /var/run/secrets/kubernetes.io/serviceaccount/ca.crt: no such file or directory
I0723 00:14:46.406180      55 kube_factory.go:169] Using Kubernetes client with master "https://<IP_ADDRESS>:443" and version "v1"
I0723 00:14:46.416792      55 kube_factory.go:170] Using kubelet port 10255
E0723 00:14:46.416697      55 reflector.go:136] Failed to list *api.Node: Get https://<IP_ADDRESS>:443/api/v1/nodes: x509: failed to load system roots and no roots provided
E0723 00:14:46.436944      55 reflector.go:136] Failed to list *api.Pod: Get https://<IP_ADDRESS>:443/api/v1/pods?fieldSelector=spec.nodeName%21%3D: x509: failed to load system roots and no roots provided

I copied a base64_decoded certificate from my ~/.kube/config, but it didn't help a lot because of ips mismatch:
I0723 00:30:49.693451       1 heapster.go:52] /heapster --source=kubernetes:http://kubernetes-ro?useServiceAccount=true&auth=&insecure=true --sink=influxdb:http://monitoring-influxdb:80
I0723 00:30:49.693690       1 heapster.go:53] Heapster version 0.16.0
I0723 00:30:49.695987       1 kube_factory.go:169] Using Kubernetes client with master "https://<IP_ADDRESS>:443" and version "v1"
I0723 00:30:49.696010       1 kube_factory.go:170] Using kubelet port 10255
E0723 00:30:49.720956       1 reflector.go:136] Failed to list *api.Pod: Get https://<IP_ADDRESS>:443/api/v1/pods?fieldSelector=spec.nodeName%21%3D: x509: certificate is valid for <IP_ADDRESS>, not <IP_ADDRESS>
E0723 00:30:49.725511       1 reflector.go:136] Failed to list *api.Node: Get https://<IP_ADDRESS>:443/api/v1/nodes: x509: certificate is valid for <IP_ADDRESS>, not <IP_ADDRESS>
E0723 00:30:49.744039       1 kube_events.go:96] Failed to load events: Get https://<IP_ADDRESS>:443/api/v1/events: x509: certificate is valid for <IP_ADDRESS>, not <IP_ADDRESS>

I've also tried to use a service account.
As far as I understood it should have been sufficient to edit deploy/kube-config/influxdb/heapster-controller.json and add "serviceAccount": "heapster" into the container's spec. Then I re-created the RC but the ca.crt file didn't come up. Does this approach working on the cluster v0.19.3 ?

I had a similar problem with kube-dns not being able to connect to the master. Adding --client-ca-file=/etc/kubernetes/certs/ca.crt to kube-apiserver then deleting the default-token (kubectl get secret) and letting it get recreated fixed the issue for me. Note that I'm on 1.0.1 and YMMV.

@philk Thank you for a starting point. It seems that I've resolved the issue with the ca.crt.
Details are in comments in another issue:

https://github.com/GoogleCloudPlatform/heapster/issues/429#issuecomment-125653775
https://github.com/GoogleCloudPlatform/heapster/issues/429#issuecomment-125798911

Now I'm getting another error though:
E0729 01:28:14.393329       1 reflector.go:136] Failed to list *api.Node:
the server has asked for the client to provide credentials (get nodes)
E0729 01:28:14.395981       1 reflector.go:136] Failed to list *api.Namespace:
the server has asked for the client to provide credentials (get namespaces)
E0729 01:28:14.397820       1 reflector.go:136] Failed to list *api.Pod:
the server has asked for the client to provide credentials (get pods)

We’re going through old support issues and asking everyone to direct your questions to stackoverflow.
We are trying to consolidate the channels to which questions for help/support are posted so that we can improve our efficiency in responding to your requests, and to make it easier for you to find answers to frequently asked questions and how to address common use cases.
We regularly see messages posted in multiple forums, with the full response thread only in one place or, worse, spread across multiple forums. Also, the large volume of support issues on github is making it difficult for us to use issues to identify real bugs.
The Kubernetes team scans stackoverflow on a regular basis, and will try to ensure your questions don't go unanswered.


Show endpoints on saml application settings

Preflight Checklist

[X] I could not find a solution in the existing issues, docs, nor discussions
[X] I have joined the ZITADEL chat

Describe your problem
For OIDC apps we show the most important urls in the application settings. But not for SAML.
Describe your ideal solution
Show the links to the SAML endpoints on the app config page with the actual instance domain:

Certificate
Login
Logout (see: https://github.com/zitadel/zitadel/issues/5084)

Version
No response
Environment
ZITADEL Cloud
Additional Context
Logout is not at all documented: https://github.com/zitadel/zitadel/issues/5084
Relates also to: https://github.com/zitadel/zitadel/issues/6507

@hifabienne I have this issue #6510 and #6508 ready to send this weekend... if you can assign them to me... you know we now have more contributors which means great news but also more chances for collision :smile:
Thanks!

@hifabienne maybe this can be closed? My PR #6841 included links for certificate, sso and slo


Popup rendered outside visible area in v3.0.2 also

Describe the bug
The issue https://github.com/nhn/tui.editor/issues/1633 was fixed in 3.0.2, but it is still there.
To Reproduce
Steps to reproduce the behavior:

Go to https://stackblitz.com/edit/react-2ajz1z
Open in mobile device (not dev tools)
or open this in mobile device https://react-2ajz1z.stackblitz.io

Expected behavior
A clear and concise description of what you expected to happen.
Screenshots
If applicable, add screenshots to help explain your problem.
https://user-images.githubusercontent.com/54087826/128279591-29b474ea-335f-4081-b6d9-b5a1e7a0b41e.mp4
Device dimensions

@ats1999
Thanks for letting me know.
But the editor's width is narrower than the basic pop-up. In general, it is unlikely to be used in such situations.

See the dimensions of my mobile, i have added an image above.
Width is 360 px, and height is 684

@ats1999
As mentioned above, mobile usability has not yet been considered.

Ohh, got it, thanks


Access to audio files

Thanks for the project @Shahabks. Can I get access to the audio files you used for training the models? It helps me to extend your approaches for research at my university.

That is great that you have a plan to pull the project to the next level ....... I wish I could have been able to give the audio files to you, I am afraid that it is impossible. The reason is that the audio files belong to the company that we developed the full version of SpeeChat for .... we were permitted to publish publicly a toy version of SpeeChat with only the model parameters.


fix: Updates the default branch for packages

The default branch is master on this repo, and without it the packages always come out as preview

/azp run


#3503 refactor Subject area line ends.

@immmus It would be great if you could review this change, as you have been working in this area.

The general gradle issue is addressed.
However this PR is failing since the change to use the open types archiver introduces a change in the pom.xml and we need to make the corresponding change in build.gradle to fix:
/home/vsts/work/1/s/open-metadata-implementation/access-services/subject-area/subject-area-api/src/main/java/org/odpi/openmetadata/accessservices/subjectarea/properties/objects/graph/Line.java:15: error: package org.odpi.openmetadata.opentypes does not exist
import org.odpi.openmetadata.opentypes.OpenMetadataTypesArchiveAccessor;
                                      ^
/home/vsts/work/1/s/open-metadata-implementation/access-services/subject-area/subject-area-api/src/main/java/org/odpi/openmetadata/accessservices/subjectarea/properties/objects/graph/Line.java:95: error: cannot find symbol
        OpenMetadataTypesArchiveAccessor archiveAccessor = OpenMetadataTypesArchiveAccessor.getInstance();
        ^
  symbol:   class OpenMetadataTypesArchiveAccessor
  location: class Line
/home/vsts/work/1/s/open-metadata-implementation/access-services/subject-area/subject-area-api/src/main/java/org/odpi/openmetadata/accessservices/subjectarea/properties/objects/graph/Line.java:95: error: cannot find symbol
        OpenMetadataTypesArchiveAccessor archiveAccessor = OpenMetadataTypesArchiveAccessor.getInstance();
                                                           ^
  symbol:   variable OpenMetadataTypesArchiveAccessor
  location: class Line
Note: Some input files use unchecked or unsafe operations.
Note: Recompile with -Xlint:unchecked for details.
3 errors

FAILURE: Build failed with an exception.

Would you like to do this ? Or I can push a fix (later today) if you like
That being said I share @immmus 's concern that this new dependency affects the client - which could be problematic, so it maybe something to address after you've made any decision on refactoring that piece?

@immmus shall I merge?

@davidradl Thank you, you can merge.


Self referencing schema fails to compile

ajv version: 4.8.2
ajv options: {allErrors: true, v5: true}
General description:
I have a problem compiling a circular, self referencing schema -
JSON Schema
var schema = {
  "type": "object",
  "id": "dialog",
  "properties": {
    "steps": { "$ref": "#/definitions/steps" },
  },
  "definitions": {
    "steps": {
      "id": "steps",
      "type": "array",
      "items": {
        "type": "object",
        "properties": {
          "steps": {
            "$ref": "#/definitions/steps"
          }
        }
      }
    }
  }
}
;

Code
var Ajv = require('ajv');
var ajv = Ajv({allErrors: true, v5: true});

var schema = {...};
var validate = ajv.compile(schema);

Result
I expect this schema to compile, but I see the following exception:
        throw $error;
        ^

Error: can't resolve reference #/definitions/steps from id steps
    at Object.generate_ref [as code] (c:\temp\ajv-test\node_modules\ajv\lib\dotjs\ref.js:62:22)
    at Object.generate_validate [as validate] (c:\temp\ajv-test\node_modules\ajv\lib\dotjs\validate.js:157:37)
    at Object.generate_properties [as code] (c:\temp\ajv-test\node_modules\ajv\lib\dotjs\properties.js:198:26)
    at Object.generate_validate [as validate] (c:\temp\ajv-test\node_modules\ajv\lib\dotjs\validate.js:230:37)
    at Object.generate_items [as code] (c:\temp\ajv-test\node_modules\ajv\lib\dotjs\items.js:122:20)
    at generate_validate (c:\temp\ajv-test\node_modules\ajv\lib\dotjs\validate.js:230:37)
    at Ajv.localCompile (c:\temp\ajv-test\node_modules\ajv\lib\compile\index.js:98:22)
    at Ajv.resolve (c:\temp\ajv-test\node_modules\ajv\lib\compile\resolve.js:53:19)
    at Object.resolveRef (c:\temp\ajv-test\node_modules\ajv\lib\compile\index.js:209:21)
    at Object.generate_ref [as code] (c:\temp\ajv-test\node_modules\ajv\lib\dotjs\ref.js:22:22)

I understand the issue. The problem is {"id": "steps"}, it makes "#/definitions/steps" resolve to "stesp#/definitions/steps" i.e. some fragment of schema with id "steps" and although this "id" exists here, there are no "definitions" inside it. That's by the spec. See this schema:
{
  "type": "object",
  "id": "dialog",
  "properties": {
    "steps": { "$ref": "#/definitions/steps" },
  },
  "definitions": {
    "steps": {
      "id": "steps",
      "definitions": {
        "steps": {
          "description": "this is what internal $ref points to, but it does not exist in your schema"
        }
      },
      "type": "array",
      "items": {
        "type": "object",
        "properties": {
          "steps": {
            "$ref": "#/definitions/steps"
          }
        }
      }
    }
  }
}

You just need to remove this id, it serves no purpose.
Maybe the intention was to have "id": "#steps" to be able to use it instead of "#/definitions/steps"? This would work.
I hope it makes sense.

Actually the error message gives a subtle hint: "can't resolve reference #/definitions/steps from id steps". The key here was "from id steps" :)

Using id #steps did the trick. Thanks!

The problem is "id": "step". id attribute changes resolution scope (by spec), there is no "#steps" inside "step", it's outside. Just remove it or replace with "#step".

@epoberezkin changing to #step works, but I don't completely understand why

@morsh because your $ref is a relative URI (hash fragment) and id attribute defines base URI for $ref. #step doesn't change base URI because it is also a fragment, step does because it's a different file name

@epoberezkin thank you!


Interbank detects root

Describe the bug
Interbank still detects root when using the module.
This is the app: https://play.google.com/store/apps/details?id=pe.com.interbank.mobilebanking
Context

Device: Mi A3
OS: LineageOS 21
Version of Magisk, KSU or APatch: Magisk official v27
Other Root Module(s): microG Installer Revived
LSPosed Module(s): NoStorageRestrict, XPL-EX (Interbank app is not enabled in any of the modules)

Seems to work fine on my end. Try disabling LSPosed


C++ Style Checking in CI

The problem
It would be best if we could automate the checking of C++ code style in CI. This would allow PR reviewers to spend less time manually linting.
Possible solution
Add a cpplint step to automated CI test. Linter script must be installed on CI Docker image as well.

Have a look as well to github actions and clang-format: https://github.com/marketplace/actions/clang-format-lint


During upgrade, "Field Help" specified for a fields that cannot be found

field [stylefilename], content [People]
Field help specified for a field that cannot be found, field [inlinescript], content [Add-ons]
Field help specified for a field that cannot be found, field [scriptingmodules], content [Add-ons]
Field help specified for a field that cannot be found, field [allowcrosslogin], content [Domains]

not an issue


feat: support eip-1159 in buildSendTransaction

Intended to supersede #439. Required for https://github.com/shapeshift/web/issues/1181. Fixes #441. Relevant to https://github.com/shapeshift/web/issues/1025.

High level question, is there any reason for us to be signing legacy transaction at all if we support eip1559? I assume we can reduce the type complexity once web is updated?

@kaladinlight Not all wallets support 1559; the hdwallet interface does, but the user might connect a wallet which doesn't.

Ok, then I defer to my comment regarding typing as a clearer way to achieve this that is more easily understandable (in my opinion).


ability to go through doors, with considerations

The previous person who made this change has never came back to it. This pull request brings back that feature with a lot more. continuation of #84
There is still work to do and currently I got no idea how to implement it.
dilemma
When the door is open, sometimes the bot get stuck and unable to move, this is because an open door is treated like air block, there need to be a function specifically for going through doors.
That function will specifically tell the bot to go the opposite direction of the door's occupied space, so it doesn't collide it.
the free space that an open door has depend on the direction and the facing of the door. but generally the length of that space is 0.0212 block only, which is a small number to get through, this needs accurate calculations.
The pathfinder sometimes has the ability to go through it with no problems, thanks to the fullStop function that centers the bot exactly in the middle of the block.
empty spaces can start like this:
[0.0488 -> 0.0700] or [0.0300 -> 0.0512]
Those numbers are always like that, which one is present depends on the facing and the direction of the door.

this is because an open door is treated like air block

I don't think this is suppose to be the case. Doors should be treated as solid blocks at the moment.

The pathfinder sometimes has the ability to go through it with no problems, thanks to the fullStop function that centers the bot exactly in the middle of the block.

Full stop should only apply when the bot stops and should not be used when trying to path somewhere. A better Approach is to place a node inside of the door the bot can follow.
How I would do it is to change the coordinate of the node the bot should walk towards. This function https://github.com/PrismarineJS/mineflayer-pathfinder/blob/367205e7e31e39cba7e3df09d45fcde720667846/index.js#L168 takes the calculated path from A* and adapts it so the bot can walk along it. In this function I would make a new check for a door block. And then determent where the node has to be offset so that the bot can walk through the door. So for instance:
If you have a door at position 5, 1, 5 then the center of the block is at 5.5, 1, 5.5 (Block center). (The A* result returns only full numbers and post process adds the + 0.5 to each node).
Now we need to figure out in what direction the door is opened. For this we can make a map of door states and door direction. So for instance door has its main hitbox towards -x. Then we add 0.1 or 0.2 to the node x value. Making it something like 5.6, 1, 5.5 (New node position). This should make the bot walk through the door without issues.

For figuring out in what direction the door is opened you might be able to use the block properties. https://github.com/PrismarineJS/prismarine-block/blob/master/doc/API.md#blockgetproperties this should give you the direction the door is in and if it is opened or closed. This should make it easier to get the door state across different versions instead of having to map the block stateId.

Okay, I understand now, I had doubts in my ways and didn't really fully understand how path-finding completely works, thank you for this great clarification and advices

Is there any progress on this PR being merged into master? I think it would be pretty useful.

hi @LetsChill want to have another look here?

I don’t know mate I’ve been busy with major stuff lately


GEODE-6380: Add static analysis for mutable static fields

Add a pmd rule to look for any static fields that are marked as static but not final, or static final but have values that can be modified (like a HashMap). This will allow us to eventually eliminate and enforce not having mutable static fields.
Adding a few annotations to categorize our static fields:

Immutable - mark classes or fields that are really immutable as immutable. The pmd rule can ignore these.
MakeImmutable - Temporary annotation to mark fields that aren't immutable but should be. For example a static final HashMap that we never change.
MakeNonStatic - Temporary annotation mark fields that are static that we are allowing to be modified at runtime. These fields should be turned into instance fields or cache.
MutableForTests - Temporary annotation to mark fields that should be immutable, but are not to allow setting them in tests. These also should eventually be turned into instance fields.

Annotating fields within geode-core with these annotations.

I haven't annotated everything yet, and the rules only apply to geode-core so far.


The Last Hierophant pre-fight check option

Problem: Recurring Zaishen Bounty for Duncan the Black requires that four prerequisite objectives are met otherwise access to Duncan's room is barred. In the case of a team activity all members are asked to check their status of The Last Hierophant before proceeding. However, often it is found that upon arrival at Duncan's room the door is locked as a team member does not have the prerequisite tasks completed, despite reporting otherwise.
Proposed solution: Introduce a chat command (for example /duncan) that interrogates the player's quest list for The Last Hierophant and reports the status of the sub-quests on the Team channel, for example, "4/5 completed - ready for Duncan" (in green text) or "x/5 completed - not ready" (in red text).
Intended outcome: All team members are made aware of each other's status, and non-compliant members become obvious. This will save much time and unnecessary investigation after arrival at Duncan's door. Any non-users of gwtoolbox obviously will fail the chat command and can be queried individually.

Can’t do text colour but other than that this is no problem, good idea

Excellent work. Thank you.


[Documentation] Add api/cdn/resize/image endpoint to OpenAPI specification

The API for go-fast-cdn is based on the OpenAPI specification, and the api/cdn/resize/image endpoint is yet to be added to the specification.

I will cover this issue

Sounds great! Assigning you now!


Pane toolbar buttons are not sized properly

Problem Description
The icon size is scaled as expected, but not the tool buttons size. We thus end up with "big" tool buttons with small icons. Enabling or disabling auto high dpi scaling does not change anything.

Paste Traceback/Error Below (if applicable)
I suspect that this due to the fact that we are setting the icon size for the panes with Qt, but are setting a fixed size for the toolbuttons in the stylesheet.
In MainWidgetToolbar.set_icon_size, we are using the QToolbar.setIconSize method to set the icon size of the toolbars.  Pinging @ccordoba12 @juanis2112 @steff456 just in case

This is by design @jnsebgosselin, as described here: spyder-ide/ux-improvements#28.

This is by design @jnsebgosselin, as described here: spyder-ide/ux-improvements#28.

Ah, thanks for the clarification. This adds so much empty space, this is an interesting design...

@isabela-pf advised us to do it for accessibility reasons: the minimal clickable area of buttons is 44 x 44px, according to most standards.
However, you're welcome to add options in Preferences to control that because we agree we can have smaller sizes, as long as the default remains 44x44 (see spyder-ide/ux-improvements#41).

I understand. I agree that accessibility is important and I applaud you for taking that into consideration in the new design. I am not sure however that using these standards as default is a good idea... I mean, if we follow that logic, we would also use a high contrast theme by default in spyder with a larger fonts and larger icon size, not small icons that are not very accessible visually...
Anyway, I don't want to sound confrontational. Though I do not agree with this design decision, I respect it and I welcome the fact that you are open to add an option to make the interface look "slimmer".

I mean, if we follow that logic, we would also use a high contrast theme by default in spyder with larger fonts and larger icons

The contrast of all colors in our new dark and light themes was carefully designed too (see https://github.com/spyder-ide/ux-improvements/issues/13).

You can discuss that with @isabela-pf, we just followed her recommendations.

Though I do not agree with this design decision, I respect it and I welcome the fact that you are open to add an option to make the interface look "slimmer".

Sure, you're welcome to contribute in that regard.

You clearly put a lot of work and thoughts into this, this is really impressive.
I am willing to help adding a new option in the preferences to make the toolbars more compact.
I used the "Find" and "Outline" panes to illustrate what I would like this option to do. What do you think?

Should I open a new issue titled "Feature request: add an option for compact panes toolbar in the preferences" or I can reopen this one and simply change the title?

I am willing to help adding a new option in the preferences that would allow users to make the toolbar of the panes more compact.

I agree with adding an option called something like Use compact toolbars to Preferences > Application > Interface.

Should I open a new issue?

We already have an issue for that:  spyder-ide/ux-improvements#41.

Thank you very much for you answer @isabela-pf, it is much appreciated!
I think for the main toolbar, what you did looks great.
It is only in the panes toolbar where I think the buttons are a bit too big. I understand that according to some standards, the minimal clickable area of buttons should 44px x 44px. From what I understand though, this standard seems mostly for web and mobile apps that are meant to be accessed with touchscreens. I am not sure this is fully necessary/applicable in the context of a desktop application, where we use the mouse pointer to click.
I think what is bothering me is that overall, the buttons in the panes toolbar are kind of looking out of place with the rest of the UI. Most of Spyder interface does not follow the 44px standard, e.g. the height of the QComboBox, QListWidget, QLineEdit, QTabBar, etc.
I am concerned that if you decide to apply the 44 px standard everywhere in Spyder for consistency, we are going to lose so much screen real-estate.
For example, in MS Office 365, which has very complex toolbars, the buttons are smaller than 44px and, most importantly, their size is consistent with the rest the UI. In comparison, the "Find" panes in Spyder 5 looks quite inconsistent, in contrast to the "Find and Replace" toolbar, which looks great in my opinion.
Anyway, this is just my opinion as an avid enthusiast and daily user of Spyder, I am by no means a UI/UX expert. I almost live in Spyder and MS Word, so that is why I have provided these examples for comparison.


Question: is it safe to reuse JsonSerializerOptions across threads?

The article recommends reusing instances of JsonSerializerOptions to improve performance, but it doesn't say whether it's safe to do so across multiple threads (e.g. can I pass the same instance to multiple calls to ReadFromJsonAsync() when making concurrent HTTP requests and processing the JSON response content?)

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

ID: 279af375-abfa-e10e-046a-625cc14826be
Version Independent ID: 1df274ad-ecf0-49e7-90c6-e6f05dce0788
Content: How to instantiate JsonSerializerOptions with System.Text.Json
Content Source: docs/standard/serialization/system-text-json-configure-options.md
Product: dotnet-fundamentals
GitHub Login: @tdykstra
Microsoft Alias: tdykstra

cc @layomia

Yes it is safe to use the same instance across multiple threads. The metadata caches on the options instance a thread-safe, and the fact that the instance is immutable after the first (de)serialization helps us further.

Many thanks @layomia for the prompt clarification and @tdykstra for promptly updating the docs! :+1:


minecraft:on_use has been deprecated

The table at the end lists (at least one) deprecated component.
[Item][error]-minecraft:on_use has been deprecated and is not available in json format 1.20.50

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

ID: f0a2c7a9-3387-2fb3-63b5-dd2819d323e4
Version Independent ID: f0a2c7a9-3387-2fb3-63b5-dd2819d323e4
Content: Introducing Custom Components
Content Source: creator/Documents/CustomComponents.md
Service: minecraft-bedrock-edition
GitHub Login: @mammerla
Microsoft Alias: mikeam

Hi! It looks like this got resolved at some point. I'm going to close this issue. If that's not yet, feel free to reopen this issue or make a new one. Thanks!


android/arm64 compile failed

Hi,
I want to compile source code for android/arm64
I already set env to android/arm64
but I get this error
$ python hyperbole.py build -r
fatal: Not a valid object name HEAD
F:\This Pc\Desktop\hysteria-master\hyperbole.py:179: DeprecationWarning: datetime.datetime.utcnow() is deprecated and scheduled for removal in a future version. Use timezone-aware objects to represent datetimes in UTC: datetime.datetime.now(datetime.UTC).
  app_date = datetime.datetime.utcnow().strftime("%Y-%m-%dT%H:%M:%SZ")
fatal: ambiguous argument 'HEAD': unknown revision or path not in the working tree.
Use '--' to separate paths from revisions, like this:
'git <command> [<revision>...] -- [<file>...]'
Building for android/arm64...
Traceback (most recent call last):
  File "F:\This Pc\Desktop\hysteria-master\hyperbole.py", line 513, in <module>
    main()
  File "F:\This Pc\Desktop\hysteria-master\hyperbole.py", line 493, in main
    cmd_build(args.pprof, args.release, args.race)
  File "F:\This Pc\Desktop\hysteria-master\hyperbole.py", line 216, in cmd_build
    os.environ.get("ANDROID_NDK_HOME")
TypeError: unsupported operand type(s) for +: 'NoneType' and 'str'

Hi there,
To build Hysteria with HY_APP_PLATFORMS=android/arm64, please have the Android NDK installed and set the ANDROID_NDK_HOME.
For an example of how to build Hysteria android/arm64 on Debian 12:
# Install Android SDK Manager
# If your distribution doesn't provide this package, you can also
# manually download it from
# https://developer.android.com/studio#command-line-tools-only
apt update && apt install -y sdkmanager

# Install NDK (Side by side) 27.0.12077973 with sdkmanager
sdkmanager --install 'ndk;27.0.12077973'

# Set ANDROID_NDK_HOME to the <sdk>/ndk/<ndk-version>
export ANDROID_NDK_HOME=/opt/android-sdk/ndk/27.0.12077973

# Build hysteria
cd /path/to/hysteria-src
HY_APP_PLATFORMS=android/arm64 python3 hyperbole.py build

Hi there,
To build Hysteria with HY_APP_PLATFORMS=android/arm64, please have the Android NDK installed and set the ANDROID_NDK_HOME.
For an example of how to build Hysteria android/arm64 on Debian 12:
# Install Android SDK Manager
# If your distribution doesn't provide this package, you can also
# manually download it from
# https://developer.android.com/studio#command-line-tools-only
apt update && apt install -y sdkmanager

# Install NDK (Side by side) 27.0.12077973 with sdkmanager
sdkmanager --install 'ndk;27.0.12077973'

# Set ANDROID_NDK_HOME to the <sdk>/ndk/<ndk-version>
export ANDROID_NDK_HOME=/opt/android-sdk/ndk/27.0.12077973

# Build hysteria
cd /path/to/hysteria-src
HY_APP_PLATFORMS=android/arm64 python3 hyperbole.py build

thanks that was helpful
now im stuck at this error:
$ python hyperbole.py build -r
fatal: Not a valid object name HEAD
F:\This Pc\Desktop\hysteria-master\hyperbole.py:179: DeprecationWarning: datetime.datetime.utcnow() is deprecated and scheduled for removal in a future version. Use timezone-aware objects to represent datetimes in UTC: datetime.datetime.now(datetime.UTC).
  app_date = datetime.datetime.utcnow().strftime("%Y-%m-%dT%H:%M:%SZ")
fatal: ambiguous argument 'HEAD': unknown revision or path not in the working tree.
Use '--' to separate paths from revisions, like this:
'git <command> [<revision>...] -- [<file>...]'
# runtime/cgo
cgo: C compiler "F:\\This" not found: exec: "F:\\This": executable file not found in %PATH%
Building for android/arm64...
Failed to build for android/arm64

fatal: Not a valid object name HEAD

Instead of downloading an archive tarball from the release page, please use git clone. Or maybe you can use the following alternative build command (without versioning the built binary).
GOOS=android GOARCH=arm64 go build -o build/hysteria-android-arm64 ./app

cgo: C compiler "F:\This" not found: exec: "F:\This": executable file not found in %PATH%

And this is because you have a space in your ANDROID_NDK_HOME. On the linux/bash, we use quotes like
export ANDROID_NDK_HOME="/path/with space in it/android-sdk/ndk/xxx"

I don't use Windows, maybe you can ask ChatGPT how to handle this.

fatal: Not a valid object name HEAD

Instead of downloading an archive tarball from the release page, please use git clone. Or maybe you can use the following alternative build command (without versioning the built binary).
GOOS=android GOARCH=arm64 go build -o build/hysteria-android-arm64 ./app

I did use "" for specifying the PATH for ANDROID_NDK_HOME

cgo: C compiler "F:\This" not found: exec: "F:\This": executable file not found in %PATH%

And this is because you have a space in your ANDROID_NDK_HOME. On the linux/bash, we use quotes like
export ANDROID_NDK_HOME="/path/with space in it/android-sdk/ndk/xxx"

I don't use Windows, maybe you can ask ChatGPT how to handle this.

This command gave me a file
I want to build the .apk file for nekobox app

I want to build the .apk plugin file for nekobox app

Hello,
For any questions related to third-party clients, please open a new issue in their own repo.
Please note that third-party clients are not maintained by us, nor are we familiar with their codebase.


feat(meta): initialization and modeling for sql-backend based meta store

I hereby agree to the terms of the RisingWave Labs, Inc. Contributor License Agreement.
What's changed and what's your intention?
Related #12449 , this is the very first step of sql-backend based meta store. In this PR, we have modeled and initialized the existing entities except those related to hummock, and implemented some controller logic based on these models, such as SystemParamsController, CatalogController, etc. For other models, you can refer to their implementation to gradually replace other managers.
I added a README.md doc under model_v2 to introduce the steps of defining relations and changes of new model and generate of related files. Cc @zwang28, you can refer to this to model hummock metadata.
Close #12475.
Checklist

[ ] I have written necessary rustdoc comments
[ ] I have added necessary unit tests and integration tests
[ ] I have added fuzzing tests or opened an issue to track them. (Optional, recommended for new SQL features #7934).
[ ] My PR contains breaking changes. (If it deprecates some features, please create a tracking issue to remove them in the future).
[ ] All checks passed in ./risedev check (or alias, ./risedev c)
[ ] My PR changes performance-critical code. (Please run macro/micro-benchmarks and show the results.)

[ ] My PR contains critical fixes that are necessary to be merged into the latest release. (Please check out the details)

Documentation

[ ] My PR needs documentation updates. (Please use the Release note section below to summarize the impact on users)

Release note
If this PR includes changes that directly affect users or other significant modifications relevant to the community, kindly draft a release note to provide a concise summary of these changes. Please prioritize highlighting the impact these changes will have on users.

Will review later. 🥵

BTW, have we investigated diesel ORM or directly using sqlx. What's the comparison between them?

BTW, have we investigated diesel ORM or directly using sqlx? What's the comparison between them?

diesel is non-async right now. Using sea-orm is to be compatible with different backends and avoid writing duplicate logic for different backends.

BTW, have we investigated diesel ORM or directly using sqlx? What's the comparison between them?

diesel is non-async right now. Using sea-orm is to be compatible with different backends and avoid writing duplicate logic for different backends.

I see.

diesel-async is experimental, where sqlite is not supported.
Although sqlx supports any driver, it doesn't seem to handle the dialects between different systems.


Send submission start email

Is your proposal related to a problem?
Since the orchestrator email can't be customized, we can send our own email and modify the orchestrator setting to not send a submission started email.
@tschaffter Can you comment below on what you want the "submission started" email text to be.

Duplicate of #129


Autogenerate TypedDocumentNode

Hi!
Sorry if this is completely not related as I haven't tried the library yet but just a thought I had:
If you know the queries/fragments, you could already import them with their Typescript types..
Check out this article: https://the-guild.dev/blog/typed-document-node
Sorry and feel free to close in case this is not related at all :)

Hey thanks for the suggestion! I'm actually in the process of a rewrite with support for auto generating queries. The link you provided will actually help me a lot in some of the problems I've run into with this, so I'll keep this issue open.
Thanks again, I remember seeing something like what you linked a while ago but couldn't remember exactly what it was 😅

That's awesome!  if you have any questions for us or things we could help with, just let us know!


Expose API for logging of response bodies with condition only on errors and/or successes

JMeter has a feature called Listeners->"View Results Tree" that is disable-able and allows logging of response bodies either always / when error occur / when successes occur.
This is missing now in Gatling.
Currently to log response bodies I need to within a request to use check to save the bodyString to session and then afterward log it and then remove the value from session.
This is a very expensive operation to perform and cannot be easily automatically switched on or off according to the log level in the logback.xml file.

My suggestion is to on the request level add a ".log" API in addition to the ".http" and ".check" APIs of the HttpRequestBuilder
A more general API on the scenario and/or the simulation level in addition to the request level could also be very useful.

No. You have to tune the logging level on the http module, see logback.xml.

if debug logging (see logback.xml) is enabled and the request fails, the full (session, request, response) is logged
if trace logging is enabled, all of them are logged, not only the failed ones.

Please slandelle read the first comment of this issue.
This is not something I am able to set up from the logback.xml and JMeter has this feature out of the box.
I have a task of converting highly used JMeter scripts to Gatling.
Some of the most important scripts we have have this feature widely used...

Why doesn't the logback logging suite your needs?

because that would force me to run all future load tests in trace log level which is not really useful, due to the amount of redundant logging that would be done just to get some specific successful requests logged.

This feature is intended for debugging, not to run on production.
I suspect you use it for something else, in which case you really should elaborate.


Broadlink RM Mini 3 D

Hi,
there are a new model and his mac address begin with 24dfa7.
Broadlink qtt bridge find it but  won’t go into learning mode.

Hi, I met exactly the same issue. I bought a new one recently, it can be detected but is not responsive to any instructions sent from this plugin.
Its mac address also begin with 24dfa7. The machine itself is good since it can be controlled by its official APP.
@lprhodes Please @ me if you need any more information to fix it

Hi,
mine also start with 24:DF:A7 and te version of the firware is 44057
Il giorno sab 29 feb 2020 alle ore 16:21 孙国强<EMAIL_ADDRESS>ha
scritto:

Hi, I met exactly the same issue. I bought a new one recently, it can be
detected but is not responsive to any instructions sent from this plugin.
Its mac address also begin with 24dfa7. The machine itself is good since
it can be controlled by its official APP.
@lprhodes https://github.com/lprhodes Please @ me if you need any more
information to fix it
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/lprhodes/homebridge-broadlink-rm/issues/566?email_source=notifications&email_token=ALMQCC64KGYUARRQFT6ZQ3TRFETXZA5CNFSM4KY6WLLKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOENL4UCY#issuecomment-592955915,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ALMQCC4USKUZTPUBKPASM2LRFETXZANCNFSM4KY6WLLA
.

Same here. Can't connect, can't learn etc.
device type code: "62bc"
MAC starts with 24:df:A7,
firmware is V52071,
SDK 2.13
[Broadlink RM] Learn getSwitchState: undefined
[Broadlink RM] Scan Frequency getSwitchState: undefined
[ERROR] Learn Code (Couldn't learn code, device not found)

@lprhodes I seems that there is already a fix: https://github.com/mjg59/python-broadlink/pull/317

@lprhodes It seems that there is already a fix: mjg59/python-broadlink#317

yes but how integration on bridge?

I’ve got exactly the same problem. Also a new Rm3 with a Mac adres starting with 24:DF:A7.
The plug-in adds the BroadLink but the BroadLink doesn’t do anything (don’t send and can’t learn).
Is there already someone with a fix for this problem under HomeBridge?

Same Problem. I'm using a Broadlink RM mini3 bought last week. MAC 24:df:a7. I got it connected and working with the app, so the TV answers properly. However, it doesn't learn anything.

I’ve got exactly the same problem. Also a new Rm3 with a Mac Address starting with 24:DF:A7.
Any good news?

Hello. Yesterday (5th april) and before, my BroadLink Rm2 Pro was working great with home assistant, suddenly, today (6th april), it's just not working. I'm sending the command using broadlink.send. Everything is right, as I'm doing exactly the same that I was doing before, when it was working.
My device is also 24:DF:A7...
I read something somewhere where they were updating the libraries to make it work with the new Rm4. Could it be that the reason my device is not working??
Thanks

I have a device with mac address starting with 24:DF:A7 as well and I can't use the Learn function on homebridge as well.

Same problem here

Same problem, thourhg my mac starts with a7:df:24

My device is working again. It's seems sometimes it works, and sometimes it doesn't. A restart, or a couple of restarts on home assistant, make it working again. My device is "BroadLink Rm2 Pro", also with MAC address "24:DF:A7..."

I think its more about the device type than the mac add. My device type is 279d with mac 24:df:a7 and i cannot see that device type in
https://github.com/lprhodes/broadlinkjs-rm/blob/master/index.js

I have the same issue, device type code: "62bc". Any ideas how to fix?

@issic looks like I have the same decide code, have you managed to fix it?

Sorry for being a bit vague with this, but I made notes to myself to use the version 3.6.18 and replace the index.js file in
/usr/local/lib/node_modules/homebridge-broadlink-rm/node_modules/broadlinkjs-rm/
.. since  "there’s some issues with support for the latest RM3 Mini devices". I just didn't make notes on what it should be replaced with, dumb me... Anyway, I uploaded the files here:
Original: https://raw.githubusercontent.com/Naqsaq/Home-Automation/master/index_backup.js
Replaced with: https://raw.githubusercontent.com/Naqsaq/Home-Automation/master/index.js
Hope this helps some of you.


Input isn't updated when open={false} and click outside

Describe the bug
I use the library as a date field, never showing the popper, by using open={false}.
When you click outside the input, an incorrect value (like "02/31/2000") isn't fixed (but when you use tab it is).
To Reproduce
<DatePicker
selected={value}
onChange={setValue}
open={false} // problem is caused by this setting
/>

Enter "02/31/2000" then press tab (this works, the input date is fixed)
Enter "02/31/2000" then click outside input (this doesn't work, notice how the input isn't updated)

Codesandbox example.
Expected behavior
When I click outside the input, I expect the value to be fixed. Just like what happens when you press tab.
Desktop :

OS: Mac Os 15
Browser: Chrome
Version: 131

** Additional **
When you dont' use "open={false}", it works as expected.

Understood, I'll work on it


Decode URI component for search functionality in docs

Before:

After:

@straight-shoota looks more like a bugfix to me than the feature


"Loading..." on Mac app

I use the Zulip app on a Mac. I leave it open all the time and check it periodically. However, after some time, it always eventually starts showing the message
Loading...

If this message does not go away, please wait a couple seconds and reload the page.

The message does not go away. The word "reload" is highlighted as a link, but clicking it does nothing. Right-clicking doesn't give an option to reload the page.
I've just realised while writing this bug report that I can press CMD-R to reload, and this does work, but that wasn't so obvious, so up to now I've had to quit and re-open the app whenever this happens.
It's worth noting that my machine is a laptop and our WiFi is sometimes unstable, so my guess is this happens either when my machine goes to sleep or when I change networks, or when the network is very slow, but I haven't managed to catch it in the act to find out which is the case.
OS X version is 10.11.6 (which I realise is old but I have no plans to update it), and Zulip Desktop version is 5.4.2.

@timabbott can you move the issue to https://github.com/zulip/zulip-desktop?


[FLINK-36679][runtime] Add a metric to track checkpoint _metadata size

What is the purpose of the change
Add a metric to track checkpoint _metadata size
Brief change log
Add a metric lastCheckpointMetadataSize to track checkpoint _metadata size
Verifying this change
Updated existing unit tests.
Does this pull request potentially affect one of the following parts:

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

Documentation

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

The failing test RescaleCheckpointManuallyITCase.testCheckpointRescalingInKeyedState seems to be unreliable. I see it's failing in multiple recent builds of other PRs.

Thanks for the feedback! The reason this being a draft is I haven't spend time testing this end to end. Also I was wondering if other folks in community think this is a useful metric as we found. I'll make this a PR for review shortly.


Fixes problem with multi-dimensional files array

Symfony\Component\BrowserKit\Request->getFiles() can return a multi-dimensional array with nested uploads for example given an input-element which has an array as name:
<input type="file" name="baa[foo]" />

would result in an array like:
array(1) {
  ["baa"]=>
  array(1) {
    ["foo"]=>
    array(5) {
      ["name"]=>
      string(13) "some_file.txt"
      ["type"]=>
      string(0) ""
      ["tmp_name"]=>
      string(17) "/tmp/uploadRYvrqA"
      ["error"]=>
      string(1) "0"
      ["size"]=>
      string(2) "16"
    }
  }
}

So it needs to recursivly go through the array and add the files.
Related to https://github.com/Behat/Mink/issues/106

Damn, old Version of patched Client.php - new pullrequest comming - ignore this one :)


bingo: 0.6.0 -> 0.7.0

Description of changes

Things done

Built on platform(s)

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

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

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

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

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

[ ] Fits CONTRIBUTING.md.

Result of nixpkgs-review pr 195641 run on x86_64-linux 1

1 package built:

bingo

Thank you! Looks a bit cleaner and easier to maintain now


Join node fails for 'Array', Key/value' and 'merged object'  if using was set to buffer

What are the steps to reproduce?

add join node
set mode to ’manual
set ‘join using’ to buffer
set ‘to create’ to any of 'an Array',  ‘a key/value Object’ or 'a merged Object'
set ‘After a number of message parts’ to 2
uncheck ‘and every subsequent message.’
Hit ‘Done’

What happens?
If you now sent two msgs to the join with different topics, the join will not happen. The reason is that when you set ‘Join using’ to buffer, internally ‘joinerType’ has been set to ‘bin’ but it needs to be ‘str’
What do you expect to happen?
The join should work
Please tell us about your environment:

[ ] Node-RED version: V1.0.3
[ ] Node.js version: v12.13.0
[ ] npm version: 6.13.4
[ ] Platform/OS: macOS 10.14.6
[ ] Browser: Safari

Can you supply a small test case that shows this ? If I try a simple join bot the array and key/value object work fine and the merged object fails as the inputs aren't objects. (in my case).

Here is a flow with a good join and one that doesn't work:
[{"id":"b00f156.29f2368","type":"tab","label":"Flow 14","disabled":false,"info":""},{"id":"3baa6f27.4b00c","type":"inject","z":"b00f156.29f2368","name":"","topic":"","payload":"","payloadType":"date","repeat":"","crontab":"","once":false,"onceDelay":0.1,"x":100,"y":180,"wires":[["fa01acf.91f11d","dc8b9d65.3ac2f8"]]},{"id":"fa01acf.91f11d","type":"change","z":"b00f156.29f2368","name":"Topic 't1'payload 'hello'","rules":[{"t":"set","p":"payload","pt":"msg","to":"hello","tot":"str"},{"t":"set","p":"topic","pt":"msg","to":"t1","tot":"str"}],"action":"","property":"","from":"","to":"","reg":false,"x":330,"y":160,"wires":[["3976176a.83ac98"]]},{"id":"dc8b9d65.3ac2f8","type":"change","z":"b00f156.29f2368","name":"Topic 't2'payload 'world'","rules":[{"t":"set","p":"payload","pt":"msg","to":"world","tot":"str"},{"t":"set","p":"topic","pt":"msg","to":"t2","tot":"str"}],"action":"","property":"","from":"","to":"","reg":false,"x":330,"y":200,"wires":[["3976176a.83ac98"]]},{"id":"980cc088.081b88","type":"debug","z":"b00f156.29f2368","name":"","active":true,"tosidebar":true,"console":false,"tostatus":false,"complete":"true","targetType":"full","x":690,"y":180,"wires":[]},{"id":"3976176a.83ac98","type":"join","z":"b00f156.29f2368","name":"","mode":"custom","build":"object","property":"payload","propertyType":"msg","key":"topic","joiner":"\n","joinerType":"str","accumulate":false,"timeout":"","count":"2","reduceRight":false,"reduceExp":"","reduceInit":"","reduceInitType":"","reduceFixup":"","x":550,"y":180,"wires":[["980cc088.081b88"]]},{"id":"4922786.124bc88","type":"comment","z":"b00f156.29f2368","name":"This flow works","info":"","x":180,"y":100,"wires":[]},{"id":"610231f2.ac005","type":"inject","z":"b00f156.29f2368","name":"","topic":"","payload":"","payloadType":"date","repeat":"","crontab":"","once":false,"onceDelay":0.1,"x":100,"y":340,"wires":[["b7a2cdeb.3f0f68","c33fa9ef.5f9128"]]},{"id":"b7a2cdeb.3f0f68","type":"change","z":"b00f156.29f2368","name":"Topic 't1'payload 'hello'","rules":[{"t":"set","p":"payload","pt":"msg","to":"hello","tot":"str"},{"t":"set","p":"topic","pt":"msg","to":"t1","tot":"str"}],"action":"","property":"","from":"","to":"","reg":false,"x":330,"y":320,"wires":[["b165420e.906658"]]},{"id":"c33fa9ef.5f9128","type":"change","z":"b00f156.29f2368","name":"Topic 't2'payload 'world'","rules":[{"t":"set","p":"payload","pt":"msg","to":"world","tot":"str"},{"t":"set","p":"topic","pt":"msg","to":"t2","tot":"str"}],"action":"","property":"","from":"","to":"","reg":false,"x":330,"y":360,"wires":[["b165420e.906658"]]},{"id":"5cd82fcd.f6d5f","type":"debug","z":"b00f156.29f2368","name":"","active":true,"tosidebar":true,"console":false,"tostatus":false,"complete":"true","targetType":"full","x":690,"y":340,"wires":[]},{"id":"b165420e.906658","type":"join","z":"b00f156.29f2368","name":"","mode":"custom","build":"object","property":"payload","propertyType":"msg","key":"topic","joiner":"\n","joinerType":"bin","accumulate":false,"timeout":"","count":"2","reduceRight":false,"reduceExp":"","reduceInit":"","reduceInitType":"","reduceFixup":"","x":550,"y":340,"wires":[["5cd82fcd.f6d5f"]]},{"id":"8f45c296.742a88","type":"comment","z":"b00f156.29f2368","name":"This flow does not works","info":"","x":210,"y":260,"wires":[]}]
if you export just the join node you get this
this is the join node from the good flow
[{"id":"3976176a.83ac98","type":"join","z":"b00f156.29f2368","name":"","mode":"custom","build":"object","property":"payload","propertyType":"msg","key":"topic","joiner":"\n","joinerType":"str","accumulate":false,"timeout":"","count":"2","reduceRight":false,"reduceExp":"","reduceInit":"","reduceInitType":"","reduceFixup":"","x":550,"y":180,"wires":[["980cc088.081b88"]]}]
this is the join node from the bad flow
[{"id":"b165420e.906658","type":"join","z":"b00f156.29f2368","name":"","mode":"custom","build":"object","property":"payload","propertyType":"msg","key":"topic","joiner":"\n","joinerType":"bin","accumulate":false,"timeout":"","count":"2","reduceRight":false,"reduceExp":"","reduceInit":"","reduceInitType":"","reduceFixup":"","x":550,"y":340,"wires":[["5cd82fcd.f6d5f"]]}]
if you look at the "joinerType" in the working flow it is 'str' in the bad flow it is 'bin'

It looks to me that the issue is if you set the 'to create' option to 'string' or 'buffer' and change the 'join using to 'buffer, then switch  the 'to create' option' to  'an Array', ‘a key/value Object’ or 'a merged Object' the problem occurs

I actually get an error when I try to deploy that flow.
Which seems to be because the join buffer is missing.
(so that needs to be fixed anyway - but not sure if that is what you are describing)

The 'bad' flow doesn't output anything in the debug.

well no - because it deploys with an error - (but it shouldn't)

Yes I see that error and it is caused by the joinerType being 'bin' but you can ttell that flooking at the node becasue it doesn show the 'join using' when the 'to create' is set to 'an Array', ‘a key/value Object’ or 'a merged Object
I would think the code should change the joinetType to 'str' when you choose one of those three 'to create' types


Assert after_response gets a proper response

@ljharb @gdborton
This PR makes sure that after_response gets the correct "response"
In 1.0.2 we introduced a bug where after_response would receive the "formatted response" which was a hash of tokens => html (string)
after_response should be receiving the full response from the Hypernova server, the only difference being that any blank html fields should have the fallback client-rendering markup.
With this change we'll now receive the full response, and then we'll go back to doing what we were doing before (creating the hash of tokens => html)

Change looks good to me other than the couple of comments.

LGTM