version next (currently 1.68.0) does not support anymore config.executions schema

When deploying next version for n8n (currently the 1.68.0) the pod keeps restarting because the config.executions schema did not match anymore.
Is it a breaking change for the upcoming version? What's the suggested way to migrate to the next version?
Currently, the helm chart provide a couple of configuration keys
https://github.com/8gears/n8n-helm-chart/blob/main/charts/n8n/values.yaml#L8
Given the current n8n documentation states about environment variables usage (https://docs.n8n.io/hosting/scaling/execution-data/#enable-data-pruning) shouldn't be easier to move everything to the env variables instead of the config map?

The issue actually begins in 1.67.1

There are multiple pull requests wich remove sections from the configuration schema since version 1.50.0 it seems:

diagnostics: https://github.com/n8n-io/n8n/pull/11761
pruning: https://github.com/n8n-io/n8n/pull/11507
security: https://github.com/n8n-io/n8n/pull/11440
license: https://github.com/n8n-io/n8n/pull/11428
generic: https://github.com/n8n-io/n8n/pull/11316
scaling: https://github.com/n8n-io/n8n/pull/10321
cache: https://github.com/n8n-io/n8n/pull/10286
endpoints: https://github.com/n8n-io/n8n/pull/10268
path, host, port, listen_address, protocol: https://github.com/n8n-io/n8n/pull/10223
workflows: https://github.com/n8n-io/n8n/pull/10173
external storage: https://github.com/n8n-io/n8n/pull/10169
nodes: https://github.com/n8n-io/n8n/pull/10140
event bus: https://github.com/n8n-io/n8n/pull/10111
templates: https://github.com/n8n-io/n8n/pull/10103
external secrets: https://github.com/n8n-io/n8n/pull/10094
version notifications: https://github.com/n8n-io/n8n/pull/10087
publicApi: https://github.com/n8n-io/n8n/pull/10082

These changes seem all be breaking and not documented as well :(

@MaSpeng, @finkinfridom @medwingADMIN for binging that up!
I am not thrilled to fully switch from the config file to env vars. The main reason is, that this will have quite some impact on existing charts users, and we would bump the major version of the chart to +1.
We would also need to change how we approach configs and docs in that chart.
Maybe @ivov from n8n can shed some light on the strategy.
As the first step, I suggest removing executions from values.yaml

https://truecharts.org/charts/stable/n8n/

i know im a noob, but my friend who set my k8s up for me used the other chart i linked above, im on 1.68 now with no problems in queue mode woth workers, webhook processors and replicas

@MaSpeng, @finkinfridom @medwingADMIN for binging that up!
I am not thrilled to fully switch from the config file to env vars. The main reason is, that this will have quite some impact on existing charts users, and we would bump the major version of the chart to +1. We would also need to change how we approach configs and docs in that chart.
Maybe @ivov from n8n can shed some light on the strategy.
As the first step, I suggest removing executions from values.yaml

@MaSpeng Thanks for bringing this up.
Our config schema has grown too large and does not support dependency injection, so we are slowly moving towards smaller independent configs that support DI.
The env vars continue to work as before, but we did not realize that the internal structure of the config schema was being relied on externally. Sorry for the inconvenience - we'll rename back those keys. But please bear in mind we will likely deprecate and later drop N8N_CONFIG_FILES in n8n v2, in favor of .env files and *_FILE env vars.

thank you all for the input and contributions.
The next step would be to prepare this chart for the breaking change.
My main intent is to provide a clear and actionable path for users to be able to upgrade that chart.
I find applications that have multiple levels of configuration to be easier to operate and reason about because one likely end up with config file for general configuration setup and env vars for environment-specific changes. This makes it easy to see what is a general config option and what is env-specific.
For the next chart iteration, I suggest maintaining the structured  format of yaml and translate it to env vars.
db:
  type: postgresdb
  postgresdb:
    database: n8n
    host: localhost
    port: 12345
...

will become env variables
DB_TYPE=postgresdb
DB_POSTGRESDB_DATABASE=n8n
DB_POSTGRESDB_HOST=localhost
DB_POSTGRESDB_PORT=12345
...

There are also the .*_FILE env vars, I am not sure if we should incorporate that too.

@Vad1mo I appreciate the changes you want to make.
The incorporation of the _FILE environments could be useful, for example when using a secret management/vault which provides the secrets through files, DB_POSTGRESDB_PASSWORD_FILE as example for this use case.
I think this would look like this in the end:
db:
  type: postgresdb
  postgresdb:
    database: n8n
    host: localhost
    port: 5432
    password_file: /var/secrets/postgres_secret

I would suggest to also provide a schema  to ensure that a specific configuration is only provided through an environment or a file.
This might be a general improvement to ensure the configuration is sensible, so not someone tries to configure sqlite as database when the type is already set to postgresdb.
By the way could also be a good time to remove deprecated configurations like mysqldb.

password_file: /var/secrets/postgres_secret would be supported out of the box, I wonder how /var/secrets/postgres_secret is mounted, I think given the various solutions this should be something out of the scope of this chart.

Schema is a good key word, I had that in mind too, especially since I recently stumbled across helm-cel, do you know if there is a list of support env vars for n8n?
Because I would rather not limit the chart in a way that prevents people form setting env vars that are not yet supported by this chart.

Agree

@Vad1mo

I guess given the various solutions, this should be something out of the scope of this chart.

I agree with the part out of scope.

Schema is a good key word, I had that in mind too, especially since I recently stumbled across helm-cel, do you know if there is a list of support env vars for n8n? the closest I got was this

Personally, I would use the documentation for this topic: https://docs.n8n.io/hosting/configuration/environment-variables/

However, I would rather not limit the chart to be too strictly in a way that prevents people from setting env vars that are not yet supported by this chart.

I would also not limit the extraEnvs part, I mostly thought about the configuration parameter like database and so on.

This is the n8n helm chart values for the next version.
I designed it that you can now configure n8n, worker, and webhook individually.
Please look at the values files and let me know it that makes sense from the user perspective.
@finkinfridom
@MaSpeng
@mayphilc
@ivov
@medwingADMIN
# README
# High level values structure, overview and explanation of the values.yaml file.
# 1. chart wide values, like the image repository, image tag, etc.
# 2. ingress, (tested with nginx, but it likly works with other too)
# 3. n8n app configuration + kubernetes specific settings
# 4. worker related settings + kubernetes specific settings
# 5. webhook related settings + kubernetes specific settings
# 6. Redis related settings + kubernetes specific settings

##
##
## Common Kubernetes Config Settings for this entire n8n deployment
##
image:
  repository: n8nio/n8n
  pullPolicy: IfNotPresent
  # Overrides the image tag whose default is the chart appVersion.
  tag: ""
imagePullSecrets: []

ingress:
  enabled: false
  annotations: {}
  # kubernetes.io/ingress.class: nginx
  # kubernetes.io/tls-acme: "true"
  hosts:
    - host: chart-example.local
      paths: []
  tls: []
  #  - secretName: chart-example-tls
  #    hosts:
  #      - chart-example.local

  # define a custom incressClassName, like "traefik" or "nginx"
  className: ""

# n8n application related n8n configuration + Kubernetes specific settings
n8n:
  # The config: {} dictionary is converted to environmental variables in the ConfigMap.
  # Example: the YAML entry db.postgresdb.host: loclahost is transformed DB_POSTGRESDB_HOST=localhost
  # See https://docs.n8n.io/hosting/configuration/environment-variables/ for all values.
  config:
    n8n:
      # If not specified, n8n will create a random encryption key for encrypting saved credentials, and saves it in the dir ~/.n8n folder
      # if you run a stateless n8n, you should provide an encryption key here.
      encryption_key:
    #  db:
    #    type: postgresdb
    #    postgresdb:
    #      host: <IP_ADDRESS>

  # Dictionary for secrets, unlike config:, the values here will end up in the secret file.
  # The YAML entry db.postgresdb.password: my_secret is transformed DB_POSTGRESDB_password=bXlfc2VjcmV0
  # See https://docs.n8n.io/hosting/configuration/environment-variables/
  secret:
  #    database:
  #      postgresdb:
  #        password: 'big secret'

  ##
  ## N8n Kubernetes specific settings
  ##
  persistence:
    ## If true, use a Persistent Volume Claim, If false, use emptyDir
    ##
    enabled: false
    # what type volume, possible options are [existing, emptyDir, dynamic] dynamic for Dynamic Volume Provisioning, existing for using an existing Claim
    type: emptyDir
    ## Persistent Volume Storage Class
    ## If defined, storageClassName: <storageClass>
    ## If set to "-", storageClassName: "", which disables dynamic provisioning
    ## If undefined (the default) or set to null, no storageClassName spec is
    ##   set, choosing the default provisioner.  (gp2 on AWS, standard on
    ##   GKE, AWS & OpenStack)
    ##
    # storageClass: "-"
    ## PVC annotations
    #
    # If you need this annotation include it under `values.yml` file and pvc.yml template will add it.
    # This is not maintained at Helm v3 anymore.
    # https://github.com/8gears/n8n-helm-chart/issues/8
    #
    # annotations:
    #   helm.sh/resource-policy: keep
    ## Persistent Volume Access Mode
    ##
    accessModes:
      - ReadWriteOnce
    ## Persistent Volume size
    ##
    size: 1Gi
    ## Use an existing PVC
    ##
    # existingClaim:

  replicaCount: 1

  # here you can specify the deployment strategy as Recreate or RollingUpdate with optional maxSurge and maxUnavailable
  # If these options are not set, default values are 25%
  # deploymentStrategy:
  #  type: RollingUpdate
  #  maxSurge: "50%"
  #  maxUnavailable: "50%"

  deploymentStrategy:
    type: "Recreate"

  nameOverride: ""
  fullnameOverride: ""

  serviceAccount:
    # Specifies whether a service account should be created
    create: true
    # Annotations to add to the service account
    annotations: {}
    # The name of the service account to use.
    # If not set and create is true, a name is generated using the fullname template
    name: ""

  podAnnotations: {}

  podLabels: {}

  podSecurityContext:
    runAsNonRoot: true
    runAsUser: 1000
    runAsGroup: 1000
    fsGroup: 1000

  securityContext: {}
    # capabilities:
    #   drop:
    #   - ALL
    # readOnlyRootFilesystem: true
    #  runAsNonRoot: true
  #  runAsUser: 1000

  # here you can specify lifecycle hooks - it can be used e.g., to easily add packages to the container without building
  # your own docker image
  # see https://github.com/8gears/n8n-helm-chart/pull/30
  lifecycle:
    {}

  #  here's the sample configuration to add mysql-client to the container
  # lifecycle:
  #  postStart:
  #    exec:
  #      command: ["/bin/sh", "-c", "apk add mysql-client"]

  # here you can override a command for main container
  # it may be used to override a starting script (e.g., to resolve issues like https://github.com/n8n-io/n8n/issues/6412) or
  # run additional preparation steps (e.g., installing additional software)
  command: []

  # sample configuration that overrides starting script and solves above issue (also it runs n8n as root, so be careful):
  # command:
  #  - tini
  #  - --
  #  - /bin/sh
  #  - -c
  #  - chmod o+rx /root; chown -R node /root/.n8n || true; chown -R node /root/.n8n; ln -s /root/.n8n /home/node; chown -R node /home/node || true; node /usr/local/bin/n8n

  # here you can override the livenessProbe for the main container
  # it may be used to increase the timeout for the livenessProbe (e.g., to resolve issues like

  livenessProbe:
    httpGet:
      path: /healthz
      port: http
    # initialDelaySeconds: 30
    # periodSeconds: 10
    # timeoutSeconds: 5
    # failureThreshold: 6
    # successThreshold: 1

  # here you can override the readinessProbe for the main container
  # it may be used to increase the timeout for the readinessProbe (e.g., to resolve issues like

  readinessProbe:
    httpGet:
      path: /healthz
      port: http
    # initialDelaySeconds: 30
    # periodSeconds: 10
    # timeoutSeconds: 5
    # failureThreshold: 6
    # successThreshold: 1

  # here you can add init containers to the various deployments
  initContainers: []

  service:
    type: ClusterIP
    port: 80
    annotations: {}
  workerResources:
    {}
  webhookResources:
    {}
  resources:
    {}
    # We usually recommend not specifying default resources and to leave this as a conscious
    # choice for the user. This also increases chances charts run on environments with little
    # resources, such as Minikube. If you do want to specify resources, uncomment the following
    # lines, adjust them as necessary, and remove the curly braces after 'resources:'.
    # limits:
    #   cpu: 100m
    #   memory: 128Mi
    # requests:
    #   cpu: 100m
  #   memory: 128Mi

  autoscaling:
    enabled: false
    minReplicas: 1
    maxReplicas: 100
    targetCPUUtilizationPercentage: 80
    # targetMemoryUtilizationPercentage: 80
  nodeSelector: {}
  tolerations: []
  affinity: {}

## Worker related settings
worker:
  enabled: false
  count: 2
  concurrency: 2
  config: {}
  secret: {}

  ##
  ## Worker Kubernetes specific settings
  ##
  persistence:
    ## If true, use a Persistent Volume Claim, If false, use emptyDir
    ##
    enabled: false
    # what type volume, possible options are [existing, emptyDir, dynamic] dynamic for Dynamic Volume Provisioning, existing for using an existing Claim
    type: emptyDir
    ## Persistent Volume Storage Class
    ## If defined, storageClassName: <storageClass>
    ## If set to "-", storageClassName: "", which disables dynamic provisioning
    ## If undefined (the default) or set to null, no storageClassName spec is
    ##   set, choosing the default provisioner.  (gp2 on AWS, standard on
    ##   GKE, AWS & OpenStack)
    ##
    # storageClass: "-"
    ## PVC annotations
    #
    # If you need this annotation include it under `values.yml` file and pvc.yml template will add it.
    # This is not maintained at Helm v3 anymore.
    # https://github.com/8gears/n8n-helm-chart/issues/8
    #
    # annotations:
    #   helm.sh/resource-policy: keep
    ## Persistent Volume Access Mode
    ##
    accessModes:
      - ReadWriteOnce
    ## Persistent Volume size
    ##
    size: 1Gi
    ## Use an existing PVC
    ##
    # existingClaim:

  replicaCount: 1

  # here you can specify the deployment strategy as Recreate or RollingUpdate with optional maxSurge and maxUnavailable
  # If these options are not set, default values are 25%
  # deploymentStrategy:
  #  type: RollingUpdate
  #  maxSurge: "50%"
  #  maxUnavailable: "50%"

  deploymentStrategy:
    type: "Recreate"

  nameOverride: ""
  fullnameOverride: ""

  serviceAccount:
    # Specifies whether a service account should be created
    create: true
    # Annotations to add to the service account
    annotations: {}
    # The name of the service account to use.
    # If not set and create is true, a name is generated using the fullname template
    name: ""

  podAnnotations: {}

  podLabels: {}

  podSecurityContext:
    runAsNonRoot: true
    runAsUser: 1000
    runAsGroup: 1000
    fsGroup: 1000

  securityContext: {}
    # capabilities:
    #   drop:
    #   - ALL
    # readOnlyRootFilesystem: true
  #  runAsNonRoot: true
  #  runAsUser: 1000

  # here you can specify lifecycle hooks - it can be used e.g., to easily add packages to the container without building
  # your own docker image
  # see https://github.com/8gears/n8n-helm-chart/pull/30
  lifecycle:
    {}

  #  here's the sample configuration to add mysql-client to the container
  # lifecycle:
  #  postStart:
  #    exec:
  #      command: ["/bin/sh", "-c", "apk add mysql-client"]

  # here you can override a command for main container
  # it may be used to override a starting script (e.g., to resolve issues like https://github.com/n8n-io/n8n/issues/6412) or
  # run additional preparation steps (e.g., installing additional software)
  command: []

  # sample configuration that overrides starting script and solves above issue (also it runs n8n as root, so be careful):
  # command:
  #  - tini
  #  - --
  #  - /bin/sh
  #  - -c
  #  - chmod o+rx /root; chown -R node /root/.n8n || true; chown -R node /root/.n8n; ln -s /root/.n8n /home/node; chown -R node /home/node || true; node /usr/local/bin/n8n

  # here you can override the livenessProbe for the main container
  # it may be used to increase the timeout for the livenessProbe (e.g., to resolve issues like

  livenessProbe:
    httpGet:
      path: /healthz
      port: http
    # initialDelaySeconds: 30
    # periodSeconds: 10
    # timeoutSeconds: 5
    # failureThreshold: 6
    # successThreshold: 1

  # here you can override the readinessProbe for the main container
  # it may be used to increase the timeout for the readinessProbe (e.g., to resolve issues like

  readinessProbe:
    httpGet:
      path: /healthz
      port: http
    # initialDelaySeconds: 30
    # periodSeconds: 10
    # timeoutSeconds: 5
    # failureThreshold: 6
    # successThreshold: 1

  # here you can add init containers to the various deployments
  initContainers: []

  service:
    type: ClusterIP
    port: 80
    annotations: {}

  workerResources:
    {}

  webhookResources:
    {}

  resources:
    {}
    # We usually recommend not specifying default resources and to leave this as a conscious
    # choice for the user. This also increases chances charts run on environments with little
    # resources, such as Minikube. If you do want to specify resources, uncomment the following
    # lines, adjust them as necessary, and remove the curly braces after 'resources:'.
    # limits:
    #   cpu: 100m
    #   memory: 128Mi
    # requests:
  #   cpu: 100m
  #   memory: 128Mi

  autoscaling:
    enabled: false
    minReplicas: 1
    maxReplicas: 100
    targetCPUUtilizationPercentage: 80
    # targetMemoryUtilizationPercentage: 80

  nodeSelector: {}

  tolerations: []

  affinity: {}

## Webhook related settings
# With .Values.scaling.webhook.enabled=true you disable Webhooks from the main process, but you enable the processing on a different Webhook instance.
# See https://github.com/8gears/n8n-helm-chart/issues/39#issuecomment-1579991754 for the full explanation.
webhooks:
  enabled: false
  count: 1
  config: {}
  secret: {}
  ##
  ## Webhook Kubernetes specific settings
  ##
  persistence:
    ## If true, use a Persistent Volume Claim, If false, use emptyDir
    ##
    enabled: false
    # what type volume, possible options are [existing, emptyDir, dynamic] dynamic for Dynamic Volume Provisioning, existing for using an existing Claim
    type: emptyDir
    ## Persistent Volume Storage Class
    ## If defined, storageClassName: <storageClass>
    ## If set to "-", storageClassName: "", which disables dynamic provisioning
    ## If undefined (the default) or set to null, no storageClassName spec is
    ##   set, choosing the default provisioner.  (gp2 on AWS, standard on
    ##   GKE, AWS & OpenStack)
    ##
    # storageClass: "-"
    ## PVC annotations
    #
    # If you need this annotation include it under `values.yml` file and pvc.yml template will add it.
    # This is not maintained at Helm v3 anymore.
    # https://github.com/8gears/n8n-helm-chart/issues/8
    #
    # annotations:
    #   helm.sh/resource-policy: keep
    ## Persistent Volume Access Mode
    ##
    accessModes:
      - ReadWriteOnce
    ## Persistent Volume size
    ##
    size: 1Gi
    ## Use an existing PVC
    ##
    # existingClaim:

  replicaCount: 1

  # here you can specify the deployment strategy as Recreate or RollingUpdate with optional maxSurge and maxUnavailable
  # If these options are not set, default values are 25%
  # deploymentStrategy:
  #  type: RollingUpdate
  #  maxSurge: "50%"
  #  maxUnavailable: "50%"

  deploymentStrategy:
    type: "Recreate"

  nameOverride: ""
  fullnameOverride: ""

  serviceAccount:
    # Specifies whether a service account should be created
    create: true
    # Annotations to add to the service account
    annotations: {}
    # The name of the service account to use.
    # If not set and create is true, a name is generated using the fullname template
    name: ""

  podAnnotations: {}

  podLabels: {}

  podSecurityContext:
    runAsNonRoot: true
    runAsUser: 1000
    runAsGroup: 1000
    fsGroup: 1000

  securityContext: {}
    # capabilities:
    #   drop:
    #   - ALL
    # readOnlyRootFilesystem: true
  #  runAsNonRoot: true
  #  runAsUser: 1000

  # here you can specify lifecycle hooks - it can be used e.g., to easily add packages to the container without building
  # your own docker image
  # see https://github.com/8gears/n8n-helm-chart/pull/30
  lifecycle:
    {}

  #  here's the sample configuration to add mysql-client to the container
  # lifecycle:
  #  postStart:
  #    exec:
  #      command: ["/bin/sh", "-c", "apk add mysql-client"]

  # here you can override a command for main container
  # it may be used to override a starting script (e.g., to resolve issues like https://github.com/n8n-io/n8n/issues/6412) or
  # run additional preparation steps (e.g., installing additional software)
  command: []

  # sample configuration that overrides starting script and solves above issue (also it runs n8n as root, so be careful):
  # command:
  #  - tini
  #  - --
  #  - /bin/sh
  #  - -c
  #  - chmod o+rx /root; chown -R node /root/.n8n || true; chown -R node /root/.n8n; ln -s /root/.n8n /home/node; chown -R node /home/node || true; node /usr/local/bin/n8n

  # here you can override the livenessProbe for the main container
  # it may be used to increase the timeout for the livenessProbe (e.g., to resolve issues like

  livenessProbe:
    httpGet:
      path: /healthz
      port: http
    # initialDelaySeconds: 30
    # periodSeconds: 10
    # timeoutSeconds: 5
    # failureThreshold: 6
    # successThreshold: 1

  # here you can override the readinessProbe for the main container
  # it may be used to increase the timeout for the readinessProbe (e.g., to resolve issues like

  readinessProbe:
    httpGet:
      path: /healthz
      port: http
    # initialDelaySeconds: 30
    # periodSeconds: 10
    # timeoutSeconds: 5
    # failureThreshold: 6
    # successThreshold: 1

  # here you can add init containers to the various deployments
  initContainers: []

  service:
    type: ClusterIP
    port: 80
    annotations: {}

  workerResources:
    {}

  webhookResources:
    {}

  resources:
    {}
    # We usually recommend not specifying default resources and to leave this as a conscious
    # choice for the user. This also increases chances charts run on environments with little
    # resources, such as Minikube. If you do want to specify resources, uncomment the following
    # lines, adjust them as necessary, and remove the curly braces after 'resources:'.
    # limits:
    #   cpu: 100m
    #   memory: 128Mi
    # requests:
  #   cpu: 100m
  #   memory: 128Mi

  autoscaling:
    enabled: false
    minReplicas: 1
    maxReplicas: 100
    targetCPUUtilizationPercentage: 80
    # targetMemoryUtilizationPercentage: 80

  nodeSelector: {}

  tolerations: []

  affinity: {}

## Bitnami Valkey configuration
## https://artifacthub.io/packages/helm/bitnami/valkey
redis:
  enabled: false
  architecture: standalone

  master:
    persistence:
      enabled: true
      existingClaim: ""
      size: 2Gi

@Vad1mo
I cant think of anything else it would need

@Vad1mo looks good to me 👍. The execution mode is a good topic, in the past, this was conditionaly set based on .Values.scaling.enabled, how do you plan to do this in the future?

@Vad1mo looks good to me too. thanks a lot

now you do it like this with enabled: true
like:
webhooks:
  enabled: false
  config: {}
  secret: {}
  ...
worker:
  enabled: false
  count: 2
  concurrency: 2
  config: {}
  secret: {}

@Vad1mo looks good to me 👍. The execution mode is a good topic, in the past, this was conditionaly set based on .Values.scaling.enabled, how do you plan to do this in the future?

now you do it like this with enabled: true
like:
webhooks:
  enabled: false
  config: {}
  secret: {}
  ...
worker:
  enabled: false
  count: 2
  concurrency: 2
  config: {}
  secret: {}

@Vad1mo looks good to me 👍. The execution mode is a good topic, in the past, this was conditionaly set based on .Values.scaling.enabled, how do you plan to do this in the future?

now you do it like this with enabled: true
like:
webhooks:
  enabled: false
  config: {}
  secret: {}
  ...
worker:
  enabled: false
  count: 2
  concurrency: 2
  config: {}
  secret: {}

what about enabling queue mode

is concurrency equivalent to replicas

@Vad1mo looks good to me 👍. The execution mode is a good topic, in the past, this was conditionaly set based on .Values.scaling.enabled, how do you plan to do this in the future?

now you do it like this with enabled: true
like:
webhooks:
  enabled: false
  config: {}
  secret: {}
  ...
worker:
  enabled: false
  count: 2
  concurrency: 2
  config: {}
  secret: {}

what about enabling queue mode

@mayphilc Thats what was talked about in this topic, the "queue" mode is actually the "EXECUTIONS_MODE", so I when enabling the webhook/worker options, the chart will set the execution mode to "queue", at least that what I expect by now :).

webhook/worker
We haven't used webhook/worker so far, and I didn't look into the underlying code too deep. I am looking at it purely from a consumer perspective.

I now see that I need to take Redis into account when enabling the queue mode. So it will likely have an influence on each other.
I have other questions regarding webhook/worker.
In the future, webhook/worker will have their dedicated config.

Do webhook/worker have always the same config as the main?
Should webhook/worker have a config that is different from main
Should webhook/worker be able to extend the config of main?

@Vad1mo From the environment variable configuration in the n8n documentation, it looks like you could at least use each environment variable on each service. If it will have any effect is decided at the runtime and seems not to be documented.
As a consequence we normally share the same environment variables on each service (main, webhook, worker), which is especially important if you allow additional build in or external modules for code nodes.
You could enable them for main and while your are developing and testing a workflow, everything would be fine, but if you would forget to do the same on the worker service, the workflow would fail when executed regularly through a webhook or a schedule as example.
I think in the end, you should at least be able to overwrite or nullify a particular setting for a specific service so in the end, the consumer of this helm chart has the freedom to configure his specific needs, but could also be a case of YAGNI ^^.

I think in the end, you should at least be able to overwrite or nullify a particular setting for a specific service so in the end, the consumer of this helm chart has the freedom to configure his specific needs, but could also be a case of YAGNI ^^.

Thanks for your view. I was thinking the same.


Show progressbar only in console titlebar, use --console-title and --no-progress at the same time

[X] I'm reporting a feature request
[X] I've verified that I'm running youtube-dl version 2021.05.16
[X] I've searched the bugtracker for similar feature requests including closed ones

Description
I would like to remove the progress line in my console output but keep it on the console titlebar. With
./youtube-dl --console-title <URL>
I see a progress bar in the console and additionally on the titlebar. With
./youtube-dl --no-progress --console-title <URL>
or
./youtube-dl --quiet --console-title <URL>
I see no progress-bar at all.
I would like to have the option --console-title working independant of the option --no-progress to only see relevant information in the console window.
--no-progress: Don't show progress in the output of the console
--console-title: Show progress in titlebar (independant of --no-progress)
Today I have this:

You should be able to achieve this result by changing these lines of downloader/common.py (not tested).
Change l.235
        else:

to
        elif not self.params.get('noprogress'):

And l.263
        if self.params.get('noprogress'):

to
        if self.params.get('noprogress') and not self.params.get('consoletitle', False) :

Since you are opening a request, I think you should close the question #29164.


Build for M1 fails (no rules to make target)

Expected Behavior
Navigating into node_modules/iohook, running npm install and then npm run build builds iohook for the arm64 platform
Current Behavior
The npm install command passes with the following output:
nikolamilev@MacBook-Pro iohook % npm install
npm WARN deprecated<EMAIL_ADDRESS>See https://github.com/lydell/source-map-url#deprecated
npm WARN deprecated<EMAIL_ADDRESS>Please see https://github.com/lydell/urix#deprecated
npm WARN deprecated<EMAIL_ADDRESS>this library is no longer supported
npm WARN deprecated<EMAIL_ADDRESS>https://github.com/lydell/resolve-url#deprecated
npm WARN deprecated<EMAIL_ADDRESS>See https://github.com/lydell/source-map-resolve#deprecated
npm WARN deprecated<EMAIL_ADDRESS>some dependency vulnerabilities fixed, support for node < 10 dropped, and newer ECMAScript syntax/features added
npm WARN deprecated<EMAIL_ADDRESS>Chokidar 2 does not receive security updates since 2019. Upgrade to chokidar 3 with 15x fewer dependencies
npm WARN deprecated<EMAIL_ADDRESS>fsevents 1 will break on node v14+ and could be using insecure binaries. Upgrade to fsevents 2.
npm WARN deprecated<EMAIL_ADDRESS>The querystring API is considered Legacy. new code should use the URLSearchParams API instead.
npm WARN deprecated<EMAIL_ADDRESS>Please upgrade  to version 7 or higher.  Older versions may use Math.random() in certain circumstances, which is known to be problematic.  See https://v8.dev/blog/math-random for details.
npm WARN deprecated<EMAIL_ADDRESS>Please upgrade  to version 7 or higher.  Older versions may use Math.random() in certain circumstances, which is known to be problematic.  See https://v8.dev/blog/math-random for details.
npm WARN deprecated<EMAIL_ADDRESS>request has been deprecated, see https://github.com/request/request/issues/3142
npm WARN deprecated<EMAIL_ADDRESS>This SVGO version is no longer supported. Upgrade to v2.x.x.
npm WARN deprecated<EMAIL_ADDRESS>This package has been deprecated and is no longer maintained. Please use @docsearch/js.
npm WARN deprecated<EMAIL_ADDRESS>This version of tar is no longer supported, and will not receive security updates. Please upgrade asap.
npm WARN deprecated<EMAIL_ADDRESS>This version of tar is no longer supported, and will not receive security updates. Please upgrade asap.
npm WARN deprecated<EMAIL_ADDRESS>Support has ended for 9.x series. Upgrade to @latest
npm WARN deprecated<EMAIL_ADDRESS>Legacy versions of mkdirp are no longer supported. Please update to mkdirp 1.x. (Note that the API surface has changed to use Promises in 1.x.)

><EMAIL_ADDRESS>install
> node install.js

electron 87 win32 x64
Downloading prebuild for platform: iohook-v0.9.3-electron-v87-win32-x64
Downloading prebuild.tar.gz
[============================================>] 100.0% of 157 kB (157 kB/s)
Downloading prebuild.tar.gz
[============================================>] 100.0% of 26.8 kB (26.8 kB/s)

added 1966 packages, and audited 1967 packages in 1m

128 packages are looking for funding
  run `npm fund` for details

36 vulnerabilities (1 low, 12 moderate, 23 high)

To address issues that do not require attention, run:
  npm audit fix

To address all issues (including breaking changes), run:
  npm audit fix --force

Run `npm audit` for details.

The npm run build command fails with the following output:
nikolamilev@MacBook-Pro iohook % npm run build

><EMAIL_ADDRESS>build
> node build.js --upload=false

Building iohook for electron v12.0.0>>>>
gyp info it worked if it ends with ok
gyp info using<EMAIL_ADDRESS>gyp info using<EMAIL_ADDRESS>| darwin | arm64
gyp info find Python using Python version 3.9.12 found at<EMAIL_ADDRESS>gyp http GET https://atom.io/download/electron/v12.0.0/node-v12.0.0-headers.tar.gz
gyp http 200 https://atom.io/download/electron/v12.0.0/node-v12.0.0-headers.tar.gz
gyp http GET https://atom.io/download/electron/v12.0.0/SHASUMS256.txt
gyp http 200 https://atom.io/download/electron/v12.0.0/SHASUMS256.txt
(node:99473) [DEP0150] DeprecationWarning: Setting process.config is deprecated. In the future the property will be read-only.
  Stop.
gyp ERR! build error
gyp ERR! stack Error: `make` failed with exit code: 2
gyp ERR! stack     at ChildProcess.onExit (/Users/nikolamilev/projects/colony/platform/parrot-editor/node_modules/iohook/node_modules/node-gyp/lib/build.js:194:23)
gyp ERR! stack     at ChildProcess.emit (node:events:526:28)
gyp ERR! stack     at Process.ChildProcess._handle.onexit (node:internal/child_process:291:12)
gyp ERR! System Darwin 21.4.0
gyp ERR! command "/usr/local/bin/node" "/Users/nikolamilev/projects/colony/platform/parrot-editor/node_modules/iohook/node_modules/.bin/node-gyp" "configure" "rebuild" "--target=12.0.0" "--arch=arm64" "--dist-url=https://atom.io/download/electron" "--v8_enable_pointer_compression=0" "--v8_enable_31bit_smis_on_64bit_arch=1" "--build_v8_with_gn=false" "--enable_lto=false"
gyp ERR! cwd /Users/nikolamilev/projects/colony/platform/parrot-editor/node_modules/iohook
gyp ERR! node -v v16.14.2
gyp ERR! node-gyp -v v7.1.2
gyp ERR! not ok
Error: Failed to build...
    at ChildProcess.<anonymous> (/Users/nikolamilev/projects/colony/platform/parrot-editor/node_modules/iohook/build.js:188:23)
    at ChildProcess.emit (node:events:526:28)
    at Process.ChildProcess._handle.onexit (node:internal/child_process:291:12)

Trying with yarn produced the same results.
Possible Solution

Steps to Reproduce (for bugs)

On a M1 machine, attempt to build iohook as per instructions given here.

Context

Trying to run a development version of our Electron app is not possible on M1.
Your Environment

IOHook Version: 0.9.3
Environment name and version (e.g. Chrome 39, node.js 5.4, electron 11.2): Electron 18.0.4
Operating System and version (desktop or mobile): macOS Monterey 12.3.1
Optional Link to your project: /

The manual build instructions are a bit misleading, see #380. You need to make sure to clone the whole iohook repo not just npm install it otherwise you won't have all the needed build assets, you need the contents of the iohook/libuiohook folder.
Also, I believe you'll need to specify the Electron version and ABI with the build command, I don't think you can rely on it autodetecting an unofficially supported target (note in your quoted output it says Building iohook for electron v12.0.0, not sure where it's getting v12 from). If you're targeting Electron 18 then it would be node build.js --runtime electron --version 18.0.4 --abi 103 --upload=false
I've successfully built iohook for darwin arm64 for Electron 13 but I haven't tried later Electron versions so I can't guarantee it will work 🤷♂

Since you're using electron 18, you may want to clone PR #363 instead.

@jove0610 It turns out I am using electron 12, but thanks.
@marcelblum I followed your help and managed to build. Needed to copy the build dir into iohook directory inside node_modules, but it all works great.
Thanks for the help!
I read somewhere that the docs can be improved, and I absolutely agree. Other than that, it was quick and painless.

Since I solved my issue, closing this.

@nmilev-scribe How did you solve it on m1 mac?
Can you plz explain it step by step?


cleanup codes for figure creation

The files are a mess. We want to better exploit matplotlib API to streamline the process. This is a good time to get your hands on one of the many books that provide an overview of it. From my own experience, you need to spend some time reading such a book to get a systematic overview of the ideas behind the library syntax.
Also, https://numpydoc.readthedocs.io/en/latest/format.html

The filling below the line is too dark, pleas use a lighter grey

I guess this can be removed? https://github.com/OpenSourceEconomics/handout-eckstein-keane-wolpin-models/tree/master/material/legacy-model-spec-figures

Yes, I just left it in there as a backup in case you did not like the new model spec figures.

@luward , what is the status here?

I could not get access to any of the matplotlib books via the ULB sadly and then I forgot about the task... Do you happen to have a digital versions of one of the books?

@MaxBlesch @luward , let's close this in the time of our hackathon.


Calling getNodes does not return new added nodes using addNodes

What platform were you using when you found the bug?

React Flow / Svelte Flow version: 12.0.3
Browser and version: Chrome 126.0.6478.182
OS and version: Ubuntu 22.04

Live code example
https://codesandbox.io/p/sandbox/vibrant-hermann-36pls8
Describe the Bug
Hi,
I am appreciate your efforts on this wonderful library. I got an issue but not sure it's intent or it's a bug. Please tell me also if I'm using your library or understanding in a wrong way.
My scenario is:

Having a button to add node.
Whenever a node is added, the layout should be updated.

By this, I'm using useReactFlow to get the flow then calling addNodes to add node into the flow and getNodes to re-layout it using dagre.
The weird thing to me is that I don't see the new added node when calling getNodes right after addNodes.
Then I tried to play around a bit further, by trying access the nodes from setNodes or use the useNodesInitialized, I can see the new added node (This is how I'm working around for the moment).
One more thing I'm wondering is, as far as I understand from the documents, the useNodesInitialized will be triggered after the nodes has been updated theirs measures. But for layouting, I need some events to trigger after the nodes has been updated not only theirs measures but also theirs position. So that the fitView will work properly in my case.
useEffect(() => {
    if (nodesInitialized) {
      relayout_using_dagre();
      fitView();
    }
  }, [nodesInitialized]);

Best regards
Steps to reproduce the bug or issue

Call addNodes to add new nodes
Call getNodes to get all the nodes including the new nodes

Expected behavior
I expected to see the new added nodes when calling getNodes, but instead I'm seeing only the old nodes.
Screenshots or Videos
No response
Additional context
No response

The reason for this is that addNodes and setNodes is batched and not processed when you call getNodes in the same render tick. I will see what we can do about it.

@moklick ,
Is it possible for the getNodes to check against the batched when getting data from the store?

I don't think that we can/want to do anything about it. getNodes should return measured nodes and for that we need to wait for the next render. You could wait by using requestAnimationFrame or queueMicrotask:
queueMicrotask(() => {
  setNodeCount(reactFlow.getNodes().length);
});

Yes, It's OK for me as a work-around for the moment. Thank you.

Hey, this is quite confusing that getNodes only returns measured nodes how do we just get all nodes

But from a developer point of view the names getNodes does indicate that it would return alll the nodes that are visible.

If a node hasn't been measured it's not visible, so technically getNodes does only return nodes that are visible ^^


Changes floating point values to rounded integers

if i have a value like 3.76412, when i read it it converts the value to 376, and if the value is 3.7677 it converts to 377

I’m not quite sure what you mean. h5netcdf itself doesn’t any logic for doing something like this, so I suspect the culprit is something else in the stack. Could you share a code example?

@KillerStrike17 If this is still relevant, please provide a minimal reproducible example.

Please reopen with minimal reproducible example.


release: publish 0.14.1 stable release

Release the 0.14.1 that includes:

Updates the grafana API, that removed the name field from the dashboard crd #186
Redis event handling improvements to avoid invalid memory accesses #185

/kind release
/priority important-soon
/assign

/lgtm

/approve


add DNS Server and make "scoreboard" available

for easier usage it would be nice to be able to access http://scoreboard/ instead of the IP (e.g. http://<IP_ADDRESS> )

[ ] install DNS Server
[ ] provide DNS in DHCP
[ ] set own hotspot IP as A Record for "scoreboard"

already installed via dnsmasq. uses /etc/hosts to define hostnames


ft(API end point): Register a user

What does this PR do?
A new feature(endpoint for user sign up).
Description of Task to be completed?

Writing endpoint using the MVC structure

How should this be manually tested?

Clone the repo using git clone https://github.com/fejiroofficial/stackOverflow-lite.git.

run git checkout ft-register-user-159989615

run npm install and npm start.

To test for error

npm test

Pull Request Test Coverage Report for Build 74

34 of 77 (44.16%)  changed or added relevant lines in 8 files are covered.
17 unchanged lines in 3 files lost coverage.
Overall coverage decreased (-64.8%) to 32.222%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

db/index.js
18
20
90.0%

models/user.js
3
10
30.0%

controllers/user/signup.js
3
16
18.75%

middlewares/validateSignup.js
2
23
8.7%

Files with Coverage Reduction
New Missed Lines
%

app.js
2
78.95%

middlewares/validatePostAnswer.js
7
8.33%

middlewares/validatePostQuestion.js
8
5.88%

Totals

Change from base Build 71:
-64.8%

Covered Lines:
54

Relevant Lines:
114

💛  - Coveralls


Some performance issue

Hello,
Basically in our flow we are sending very large body's in the requests (we are buffering lot of events and send them bulk via a single http call to one of our services). Buoy is great but we noticed at least a theoretical issue:
We are using the async interface and in the message that we receive as response, request is included as well which means very huge binaries are still referenced so they still reside in memory and are not released once they were sent to the server.
Do you think it's possible to set some option and to not include the request in the response message?
Silviu

Hi @silviucpp,
I will see what I can do. This functionality is abstracted away by shackle, so I'll have to patch it there.
I'll keep this ticket updated when I have news.

Fixed by https://github.com/lpgauth/buoy/pull/21.

I see now you removed the entire request record. If you have multiple pools to multiple hosts is hard to know what host failed... Before we used the server information from request record.

You can get the pool used by checking the ReqID. The first element of the tuple is the server that handled the requests.
https://github.com/lpgauth/shackle/blob/master/include/shackle.hrl#L5


document.cookie value is undefined

Hello,
I'm trying to get value of cookie in javascript run at ruby on rails, but when I'm trying to print its value .... I got empty string or 'undefined' although I'm sure that the value of the cookie is setted
Thank you so much.

What is the name of the cookie you're trying to read? Maybe rails is obfuscating the cookie in some way, or you simply don't have access to it, due to path or httpOnly attributes...?


fix: article vigilance météo

:tada: This PR is included in version 1.9.6 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


2024-10-17_01-34-56_master-next_aws-c-common

Automatically created.

Successfully created backport PR for kirkstone-next:

#10002

Successfully created backport PR for scarthgap-next:

#10003

Successfully created backport PR for styhead-next:

#10004


Fixes #307: filter out saved values from the allowed values list

This PR fixes #307, where the multivalue control was showing selected values (separated by a ';') as a new dropdown item. This was due to a change in the getAllowedFieldValues API, which now returns both predefined and user-saved values.
The fix filters out user-saved values from the allowed values list to prevent them from showing up as separate options.
Testing:

Verified that the dropdown no longer shows duplicate values.
Confirmed that predefined values without semicolons are still correctly displayed.
Tested with both 'Allow users to enter custom values' selected and unselected.

@AminTi

I am going to close this one and create a new one from a clean state.


How to configure

I am new to this plugin.
In past I have had lua sumneko server install using lspinstall and configured using the standard config found at the lspinstall site.
local lua_settings = `{`
Lua = {
	runtime = {
		-- LuaJIT in the case of Neovim
		version = "LuaJIT",
		path = vim.split(package.path, ";"),
	},
	diagnostics = {
		-- Get the language server to recognize the `vim` global
		globals = { "vim" },
	},
	workspace = {
		-- Make the server aware of Neovim runtime files
		library = {
			[vim.fn.expand("$VIMRUNTIME/lua")] = true,
			[vim.fn.expand("$VIMRUNTIME/lua/vim/lsp")] = true,
	},

It was kind of working and then I came upon on this plugin of yours and wanted to give it a try. I commented out the above settings and installed your setup with the default settings . I didn't deinstall the  lua completion server installed through lspinstall
Now its though its running using the configs from this plugin I am getting the following message in Lspinfo. Is there something I am missing in my setup. Also does this plugin give any additional benefit over the setup I had initially

You need to specify the full path to the sumneko cmd as a key in lspconfig in setup.
This plugin includes stubs with all the definitions of the internal Neovim API, so that you can get proper completion with documentation.


⚠ Fortnite has degraded performance

In e19089d, Fortnite (https://fortnite.com) experienced degraded performance:

HTTP code: 200
Response time: 1784 ms

Resolved: Fortnite performance has improved in 696fc7f.


Wrong chars in VS generated class

I opened a classfile generated by VisualStudio.
File contains some wrong chars at the beginning.

Thx.


Discussion on BTC module construction

Hello everyone,
I have noticed that our repository already includes some content related to Bitcoin (BTC). To better continue and expand the task mechanism we use in dapp learning, I have organized the related topics and tasks into a detailed outline, which I have published in this Issue. The purpose of this is to facilitate task claiming, thereby not only improving our work efficiency but also ensuring the quality of content.
Below is the outline I propose, with each section detailing the topics and subtopics that need to be explored. Please review it and claim any sections you are interested in the comments. If you have any suggestions or additional content you’d like to add, please feel free to bring it up.
1. Basic Features
1.1 Payment Addresses

P2PKH
P2SH-P2PKH
P2WPKH
P2TR
Base58
Bech32
Bech32m

1.2 Wallets

Standard Wallets
HD Wallets

1.3 Transactions

Transaction Construction
Fee Estimation
Signature Algorithms

1.4 Tools

Blockchain Explorers
API Services
Data Analysis Tools

2. Advanced Features
2.1 PSBT (Partially Signed Bitcoin Transaction)

PSBT Protocol Introduction
Creating and Parsing PSBT

2.2 Taproot

Schnorr Signatures
MAST
Privacy and Efficiency Improvements

2.3 Multisig Addresses

Multisig Address Process
Multisig Address Creation
Signing Process

3. Protocol Introduction
3.1 BRC20
Protocol Introduction

Functionality and Purpose
Comparison with Other Standards

Code Implementation
3.2 ARC20
Protocol Introduction

Functionality and Purpose
Application Scenarios

Code Implementation
3.3 Runes
Protocol Introduction

Design Philosophy
Key Features

Code Implementation
3.4 SRC20
Protocol Introduction

Standard Specifications
Interaction Modes

Code Implementation
4. Ecosystem Applications
4.1 Babylon
Protocol Introduction
Core Logic
4.2 RGB
Protocol Introduction
Core Logic
4.3 Lightning Network
Protocol Introduction
Core Logic
etc...

Looks good!
Maybe we can add more content to Payment Address, such as multi-signature address, in the future

Looks good! Maybe we can add more content to Payment Address, such as multi-signature address, in the future

After the basic content is complete, we can add more advanced usage
PRs welcome

Looking forward to the content related to Taproot
Another question, how to claim the related tasks?

Looking forward to the content related to Taproot
Another question, how to claim the related tasks?

We will sort out the relevant outlines to ensure the quality of the content, all discussions can be held under this issue
I think you can directly reply to the content you are interested in, Welcome your PR

I think I can help organize the taproot address related information😎

Let's buidl together!

I added the principles and applications of MAST in Taproot. More discussion and guidance are welcome.https://github.com/Dapp-Learning-DAO/Dapp-Learning/pull/1144

The cryptocurrency world is ruthless, but the world is full of love. We will continue to build✊

I added the principles and applications of MAST in Taproot. More discussion and guidance are welcome.#1144

The content is quite complete and good, but the analysis of specific cases can be increased


Better error handling

A lot of places that should return errors over WAMP instead just log out an error and do nothing.
(I will be submitting PRs on this issue)

fixed


wit-component: Allow cabi_realloc to be weakly defined

If a weak "default" visibility symbol is defined in a shared library, wasm-ld emits an import for the symbol for the "env" module for the case where the symbol is overridden by other modules. https://github.com/llvm/llvm-project/blob/5b1cc58b3c72f51b8a1ce27e5fba15783d447d7c/lld/wasm/Writer.cpp#L733-L737
cabi_realloc is usually defined weakly by wit-bindgen'ed code, and if the code is compiled with -fvisibility=default, it emits an import for "env.cabi_realloc". The import leads re-exporting the symbol to the "env" module, and it conflicts with the special re-exporting logic for cabi_realloc.
This commit fixes the duplicate re-exporting issue.

@dicej Gentle ping :)

That's a nightly build issue, I'll work on getting that sorted out.


Feature Request: Generate a web.config starting point for IIS

I'd like to have a fast and secure web.config starting point that will past most/all of the linting rules to start off. I could go through all the lint errors and add those in (and learn a lot in the process), but I'd like to have a better starting point the Visual Studio > New Project.
Proposal:
add a sonarwhal command line gen-webconfig option

prompt for the type of config

IIS/10
iisnode

Include all of the best practices that will work on an Azure AppService environment.
Alternative: add a web.config example in the github repository. I've been looking at https://github.com/sonarwhal/sonarwhal.com/blob/master/web.config, but that's for iisnode.

I could go through all the lint errors and add those in (and learn a lot in the process),

The documentation for every rule that can be fixed by configuring the server does contain examples of server configs (e.g.: for rule-http-compression).

I could go through all

But, I see your point.

Alternative: add a web.config example in the github repository. I've been looking

@aligneddev What do you think about have a documentation page with the full (copy-paste ready) server configs?

A documentation page would be great!

There's a PR (#1224) with a generic web.config. @aligneddev feel free to comment on it!


Bump block header protocol version

Alonzo will now broadcast 7.2 (even though we are actually moving to 7.0, this is to distinguish from other versions of the node that are broadcasting major version 7). Babbage will now broadcast 7.0, the version that we are actually moving to.

You also have a haddock failure I think due to the line with only --

You also have a haddock failure I think due to the line with only --

ah, that's too bad, I thought the white space there was helpful. thanks!

I am closing this PR since we should only be cherry picking onto this branch from master.


Update Nuget package meta-data

Summary
I wish for the nuget packages to have the licence expression property set correctly
Details
The licence expression property should be set to the correct licence type I.e. MIT as this will enable analysis of licences in use to occur in external tools & the license type will be shown in Nuget etc.

Could you please clarify what exactly you are talking about?
I just checked JsonShema.NET 6.1.0 and 6.0.4 nuget package, and their nuspec files features a license expressions for the MIT license.

Okay, i can confirm. Every nuget package listed on https://github.com/gregsdennis/json-everything# except the JsonSchema.NET package doesn't have an MIT license expression in their respective nuspec files.

Nuget has updated how they capture various information since I started publishing packages, and I just haven't kept up.  For instance, I need to create proper readmes as well.

Thanks @gregsdennis


Starter set - Ubersreik map scale vs Foundry Measure Distance

On the Ubersreik map the map scale do not fit with the measure distance tool in foundry. If you use the tool on the map scale in the lower left corner, 400 yards measure to 468 yards (se picture). Is this fixable on the user/GM side ?

If I recall I fiddled with this for a while and it was the closest I could get


ContentTypes

Gets correct parsers/writers from factory when using a vendorspecific contenttype.

@joanne-ter-maat thanks! Do you think we can add tests for this too?

Thanks @joanne-ter-maat!


Update README; Correct Docker Command

I receive the following error when running the Docker command from the README.
└─$ sudo docker run --rm -it -p 1234:1234 28785:28785/udp ghcr.io/cfoust/sour
[sudo] password for christian:
Unable to find image '28785:28785/udp:latest' locally

I received this both on my home server and Linux laptop.
Docker version 20.10.11, build dea9396

Correction is just specifying the -p flag again before the second port mapping.

Nice catch! Feel free to merge whenever :)

Thank you! It doesn't appear I can merge this pull request though since I don't have write access.

Woops, you're right! Sorry about that!


Get correct swift path from swiftenv

swiftenv uses a shim shell script to run swift. This fix gets the real swift executable from the shim.
If we don't do this LLDB initialisation can fail, also it allows swiftenv to change the swift version without us knowing

I'm a little uneasy about having tool specific stuff in here - ideally swiftenv would just fix this and expose Swift and LLDB in the path for us to pick up etc. However since it's currently the de facto standard and causing issues lets add it

I'm not happy with this either, but swiftenv is the de facto way of installing swift on linux at the moment and if we don't fix up the paths at initialisation there are a number of issues that can occur. I don't see swiftenv changing their methods either given they need these shell scripts to support local setting of swift version.


Fix potential bugs

potintial bugs ...

check if err first before use var
use engine if is param
remove always true statement

Codecov Report

:exclamation: No coverage uploaded for pull request base (master@c810d53). Click here to learn what that means.
The diff coverage is n/a.

@@            Coverage Diff            @@
##             master   #10513   +/-   ##
=========================================
  Coverage          ?   43.66%
=========================================
  Files             ?      586
  Lines             ?    81475
  Branches          ?        0
=========================================
  Hits              ?    35576
  Misses            ?    41486
  Partials          ?     4413

Continue to review full report at Codecov.

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

@6543 could you send a backport to v1.11?

backport: #10518


train speed is too slow

I found that when the context length is 512k, the training speed is too slow, which is different from your experimental results. It takes 585 seconds for training a batch of 512k , which is to 512000/585.85=873.94 tokens/s
And I used A100-80G*8 with NVLINK.
accelerate launch \
--config_file accelerate_configs/single_node.yaml \
train.py \
--batch-size 1 \
--gradient-accumulate-every 2  \
--output-dir  ./output/7B_0.5M_bs_1M_rope_250M_step_90_lr_2e-5 \
--seed 2027 \
--max-train-steps 90  \
--learning-rate 1e-5  \
--dataset PY007/slimpajama_llama_tokenized_upsample_4096_chunk_1M \
--model meta-llama/Llama-2-7b-hf  \
--seq-length 512000 \
--rope-theta 250000000 \
--parallel_mode zigzag_ring_attn

gradient-accumulate-every is set to two. So it should be 512000* 2 /585.85

gradient-accumulate-every is set to two. So it should be 512000* 2 /585.85
I see, thanks.


Sonarcloud code coverage

Description
Sonarcloud supports displaying coverage information, it would be usefull if we could put the coverage results of our testsuite over there

@norhh This doesn't seem to be fixed yet, is that right?

Yep, it requires some weird xml format, I just gave it a shot with typical xml format

@JoranHonig , by any chance can add to circleci to run the coverage_report.sh? as my local circleci is throwing some permission denied errors out of nowhere suddenly and I don't want to spam the gihub's circleci.

I'm not 100% sure what I should do here
Do you wan't me to add something like the following to the config.yaml and run circleci locally?
      - run:
          name: coverage
          command: ./coverage_report.sh
          working_directory: /home/mythril

yes, it should be run before the sonnar-scanner.


ClusterLogForwarderTemplate controler to create / update ClusterLogForwarder CR in each namespace

Why
ClusterLogForwarder CR needs to create in HyperShift NS

/hold


Dicom support

Initial commit for for processing grayscale dicom files in Nyxus (both single frame and whole-slide image)

Added NyxusGrayScaleDicomLoader class
Modified CMakeLists.txt for including DCMTK
Added steps to build DCMTK and its dependencies in install_prereq_* scripts
Updated workflows to build wheels
Added dcmtk as a dependency for conda build

Closing it for now to fix the build issue.

Reopened after fixing the build issue.


Could not resolve all files for configuration ':annotationProcessor'.

Execution failed for task ':compileJava'.
> Could not resolve all files for configuration ':annotationProcessor'.
   > Could not find com.fasterxml.jackson:jackson-bom:<IP_ADDRESS>.
     Searched in the following locations:
       - file:/Users/yein/.m2/repository/com/fasterxml/jackson/jackson-bom/<IP_ADDRESS>/jackson-bom-<IP_ADDRESS>.pom
       - https://repo.maven.apache.org/maven2/com/fasterxml/jackson/jackson-bom/<IP_ADDRESS>/jackson-bom-<IP_ADDRESS>.pom
     Required by:
         project : > io.avaje:avaje-http-jex-generator:1.19 > io.avaje:avaje-http-generator-core:1.19 > com.fasterxml.jackson.core:jackson-databind:<IP_ADDRESS>
   > Could not find com.fasterxml.jackson:jackson-bom:<IP_ADDRESS>.
     Searched in the following locations:
       - file:/Users/yein/.m2/repository/com/fasterxml/jackson/jackson-bom/<IP_ADDRESS>/jackson-bom-<IP_ADDRESS>.pom
       - https://repo.maven.apache.org/maven2/com/fasterxml/jackson/jackson-bom/<IP_ADDRESS>/jackson-bom-<IP_ADDRESS>.pom
     Required by:
         project : > io.avaje:avaje-http-jex-generator:1.19 > io.avaje:avaje-http-generator-core:1.19 > com.fasterxml.jackson.core:jackson-databind:<IP_ADDRESS> > com.fasterxml.jackson.core:jackson-annotations:2.13.4
         project : > io.avaje:avaje-http-jex-generator:1.19 > io.avaje:avaje-http-generator-core:1.19 > com.fasterxml.jackson.core:jackson-databind:<IP_ADDRESS> > com.fasterxml.jackson.core:jackson-core:2.13.4

Possible solution:
 - Declare repository providing the artifact, see the documentation at https://docs.gradle.org/current/userguide/declaring_repositories.html

Hi, No dependencies found.

@kevin70 are you still having issue?

@SentryMan
Hello, I didn't define this version. It should be defined here. See
I have manually defined the version of jackson, which can be solved.
annotationProcessor(platform("com.fasterxml.jackson:jackson-bom:2.14.0"))

The pom file there does not define any jackson bom dependency. It defines only jackson databind, for which <IP_ADDRESS> is valid. Even in the parent pom it is not defined.
Would it be possible to see the whole Gradle build file?

@SentryMan
Hello I created a project https://github.com/kevin70/avaje-http-samples.
Directly building the project will get error information.
> ./gradlew build

we removed Jackson as a dependency, do you still see this issue?

resolved


Google.js plugin no longer works with leaflet master branch

Layers now must extend from L.Layer. As a result, the Google.js plugin no longer works with the Leaflet .80 dev version (master). Do you plan to update this plugin?

As i said in #112 i'll wait as soon as leaflet 0.8 will be released...

Maybe it would be a good idea to make a branch for leaflet 0.8 compatibility. So that users who decide to use 0.8 despite the fact that it is not finished yet can still use your plugin.

Maybe, but i'm really not hurried about this since #112 was opened a year ago and Leaflet 0.8 is still not released today :p

I understand. Had to switch to .8 recently to use the leaflet.ems plugin. Honeslty considering abandoning leaflet until it's released.


Using karma-browserify and browserify-istanbul to generate test coverage report for a multimodule JS application

I try to generate test coverage report for my multimodule JS application. I uploaded a simplified example that demonstrates the problem: https://github.com/szgabsz91/browserify-karma-coverage
The submodule (moduleA) is an npm dependency of the app and I created a gulp task in the app package that executes the tests in both packages and generates a test coverage report. However, only the app's files are included in this report, moduleA is ignored.
First I thought maybe the symlink causes this (I use npm link for testing), but replacing the link with a real folder works the same way.
I don't know how to fix my configuration, could you please help me? I guess at some point the node_modules folder is ignored, but I don't know where. Is it karma? Or karma-browserify? Or simply my configuration is wrong? But it's interesting that the tests are executed, only the coverage is problematic.
Thanks in advance, any help is appreciated.

Transforms don't run on code in node_modules. Your options are:

Run tests, coverage, etc. for moduleA independently. This is the right way to go because it's a separate package.
Add {global: true} to the transform options for the transform covering your code. This will now cover everything, including all deps. So you'd have to get super creative with globs for ignoring all but your code.


need to laravel 5.8 support

Laravel 5.8 has been realased and need to laravel 5.8 support

please help me
i need install lfm on laravel 5.8 and it's not install and have error.
check it and help me

@mdhosseini,
I am also hoping someone from the contributor/ admins will update the version tag for Laravel 5.8 support. I have to manually update the repository which takes time for individual projects.

@SHSharkar You were able to force Composer to install Laravel 5.8 with LFM? I'm trying to do this few hours and can't find anything how to do this.
Thank you

composer require unisharp/laravel-filemanager
Works on Laravel 5.8

@ujackson you are right! I guess all of use talking about version 2.0 alpha version.

composer require unisharp/laravel-filemanager
this command install version 1.9 but i need to dev-master version or 2.00.alpha.7 or newer
please check it
thanks

The composer.json should be adapted. Everywhere you see "5.4.* || 5.5.* || 5.6.* || 5.7.*", should become "5.4.* || 5.5.* || 5.6.* || 5.7.* || 5.8.*",

Here is pull request https://github.com/UniSharp/laravel-filemanager/pull/772 by @rsmalc
Now it enought to change composer.json like this (add repositories and require dev-master):
"repositories": [
    {
        "type": "vcs",
        "url": "https://github.com/rsmalc/laravel-filemanager"
    }
],
"require": {
    "unisharp/laravel-filemanager": "dev-master",
    ...
}

when laravel 5.8 support add?

If the update is not coming soon, I'll have another idea or change my filemanager

laravel 5.8 support add?

laravel 5.8 support add?

hi still not support laravel 5.8 and we are waiting for change.
i use another filemanager and wait for this filemanager update

I hope you can find some time to update this repository @streamtw
It's not possible to install this package (latest alpha version) on a fresh Laravel 5.8 installation. Any help appreciated 😉

I'm sorry for the late reply. v2.0.0-alpha8 has been released today. Please upgrade to this version.


pytensor 2.23.0

pytensor 2.23.0
Destination channel: Default
Links

PKG-6364
dev_url:        https://github.com/pymc-devs/pytensor/tree/rel-2.23.0
conda_forge:    None
pypi:           n/a
pypi inspector: n/a

Explanation of changes:

new version number

Linter check found the following problems:
ERROR conda.cli.main_run:execute(125): `conda run conda-lint /tmp/abs_3a6qp2k2g8/clone` failed. (See above for error)
The following problems have been found:
===== WARNINGS =====

clone/recipe/meta.yaml:84: invalid_url: https://pytensor.readthedocs.io : Not reachable: 403

===== ERRORS =====

clone/recipe/meta.yaml:46: compilers_must_be_in_build: The recipe requests a compiler in a section other than build
clone/recipe/meta.yaml:47: compilers_must_be_in_build: The recipe requests a compiler in a section other than build
===== Final Report: =====
2 Errors and 1 Warning were found


Set up devcontainer with Jekyll

Context
@thekaveman , @machikoyasuda , and I settled on using Jekyll to at least start the new Compiler website. We have experience with Jekyll and it has a good amount of flexibility/control for us to get something up and running in the next month.
This task is for setting up this project's devcontainer, containing a basic installation of Jekyll.
Acceptance Criteria

[x] Devcontainer is set up with git and pre-commit
[x] Jekyll tooling is available (no need for actual Jekyll files yet)

Done in https://github.com/compilerla/compiler.la/commit/9c00d506c3f3f0f8832dfa68143c7184b98a75f3. I went ahead and merged this in since the goal right now is to just get something working. Feel free to leave comments here though if there's something that looks wrong with changes in that commit.


Ccore ap ichanges

I think it is time to merge this branch to master.   I just checked in a C++ test program for the ProcessingHistory object that follows more of the guidelines you suggest for such tests.   It isn't perfect but it does test all the methods (I think - I think you have tools to show what it does and doesn't test).   Anyway, it is time we make this origin.   Suggest you (ian) work on fixing python code these changes break while I assimilate the deconvolution code that came from you original work in with the new api.   Decon operators will be a good core algorithm for timing tests.

It seems I can just comment that out

I fixed a couple minor issues, now the test_history code errors out with clang compiler somehow. If you look at the output, it is the number of history record doesn't match after reduction call. Have you seen that before? Kind of weird that it works fine for gcc...


API relay for MiqRequest#approve and #deny

Based on #12109
Required to route MiqRequest approvals to the correct region

Labeling as a bug because without this, the request will get approved on the global region, but the automation will not run.

Euwe Backport details:
$ git log -1
commit c87d46fada9143fc455bf326b8ed07c7c92be380
Author: Nick Carboni<EMAIL_ADDRESS>Date:   Mon Oct 31 09:25:19 2016 -0400

    Merge pull request #12258 from bdunne/approve_deny

    API relay for MiqRequest#approve and #deny
    (cherry picked from commit dd594c1de72a7b40133caba0e85c58a494ce28a6)


Add support for PostgreSQL 9.6 and fix backends_status

The pg_stat_activity schema has changed again with PostgreSQL 9.6. The wait events monitoring adds some more complexity to monitor lock waits. This first attempt adds only a case for heavyweight locks to appears as sessions waiting for lock. The bufferpin and LWlock event types are not taken in account right now. We should probably add some new perfdata for those, but this will come later.

You're right, I did this patch two times and forgot to edit this one. I'll fix it, sorry.


50 evals research notebook (sampling method)

Almost done, will add the visualization function and interactive part Thursday evening - Friday morning this week


docs(website): update the watch vs -w section

📑 Description
Update the watch vs -w section
✅ Checks

[ ] My code requires changes to the documentation
[ ] I have updated the documentation as required

ℹ Additional Information


Revert @formatjs/intl v2.6.8

This is blocking the UI from rendering

Codecov Report

Merging #3000 (7f91ef3) into main (0e0abf2) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff            @@
##             main    #3000    +/-   ##
========================================
  Coverage   65.12%   65.12%
========================================
  Files         507      507
  Lines        9764     9764
  Branches     2242     2090   -152
========================================
  Hits         6359     6359
  Misses       3402     3402
  Partials        3        3

Continue to review full report in Codecov by Sentry.

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


Allow to install pg 0.18.0

pg 0.18.0 was released yesterday and seems to be backward compatible with 0.17. Without allowing pg 0.18 the Rails test suite can't install queue_classic > 0.3.2.

:scream: I'll take a look. Thanks for reporting :yellow_heart:

@jipiboily would be nice to cut a new release :hamster:

Thanks for reporting! I just pushed 3.0.3 with @senny's fix. Thanks you both guys. :heart:


[BUG] Build currently fails because Flex has moved its repository

Following this guide, we should be able to get the build up and running again: https://symfony.com/blog/upgrade-flex-on-your-symfony-projects
Currently, the build fails when using the documentation's instruction (eg: docker-compose up --build) because it cannot curl https://flex.symfony.com/versions.json) as seen in the following screenshot

I have attempted to build locally flex and update manually flex, but I could not get it to work. We should look into it ASAP because new users cannot build smersh right now.

Hi,
To solve this issue, you need to run: docker-compose run php composer update and rebuild.
I tried a lot of command, so I will do a clean install and post other modifications if necessary.
Best.

Awesome, I will try it this afternoon and let you know. Thank you very much !

Hello @bogdzn, thank you for the link it was exactly the right thing to do
in my case i did
docker-compose run php composer global update after
docker-compose run php composer update symfony/flex --no-plugins --no-scripts
and regenerate jwt like this :

docker-compose exec php sh -c '
    set -e
    apk add openssl
    mkdir -p config/jwt
    jwt_passphrase=${JWT_PASSPHRASE:-$(grep ''^JWT_PASSPHRASE='' .env | cut -f 2 -d ''='')}
    echo "$jwt_passphrase" | openssl genpkey -out config/jwt/private.pem -pass stdin -aes256 -algorithm rsa -pkeyopt rsa_keygen_bits:4096
    echo "$jwt_passphrase" | openssl pkey -in config/jwt/private.pem -passin stdin -out config/jwt/public.pem -pubout
    setfacl -R -m u:www-data:rX -m u:"$(whoami)":rwX config/jwt
    setfacl -dR -m u:www-data:rX -m u:"$(whoami)":rwX config/jwt
'

Because i had this message :

Finaly i had this error :
docker-compose logs -f api
Attaching to smersh_api_1
api_1        | 2022/06/24 19:55:14 [crit] 6#6: *1 realpath() "/srv/api/public" failed (2: No such file or directory), client: <IP_ADDRESS>, server: , request: "GET / HTTP/1.1", host: "api.smersh.lan"

and i fixed it using docker-compose down then docker-compose up


OPENAI_API_KEY for GPT-4

Hi - this looks like such a great project.
You say "It's also recommended that you use at least GPT-4, preferably GPT-4-32k.
Set your OpenAI API key and install the python requirements:
export OPENAI_API_KEY="
My key only permits GPT-3.5 at present, am on the waiting list for GPT-4 - I presume I won't be able to use your appliction in the meantime?

You can use GPT-3.5 by defining it in the --model option. That said, with large files it might hit the context window limit, which will be fixed soon with #2

Got you - thanks for the quick response


[Symfony] Handle property exists on ContainerGetToConstructorInjectionRector

Fixes https://github.com/rectorphp/rector-symfony/issues/111

/cc @mkrauser

All checks have passed 🎉 @TomasVotruba it is ready for review.

Thank you


Create a sample for Language Model on One Billion Word Benchmark

Signed-off-by: yqliu<EMAIL_ADDRESS>

First of all, thanks for your intention to contribute to Open Model Zoo. But, could you please review Open Model Zoo contribution guide to see what is expected from contribution to OMZ?


[cryptolib] KMAC driver header and testing cleanup

This PR brings three changes that I worked on a while ago:

Add more organized hardcoded KMAC vectors in sw/device/tests/crypto. There is also a python script which generates C header from hardcoded HJSON file.
Remove previous hardcoded test vectors and test executable from sw/device/lib/crypto/drivers. Therefore there is no more hard-coded C header that contains bunch of KMAC vectors.
Since gluing code to cryptolib API is complete since #16936, I moved internal functions/structs/enums from sw/device/lib/crypto/drivers/kmac.h to sw/device/lib/crypto/drivers/kmac.c. In the end, kmac.h only contains minimum set of functions that are needed for KMAC algorithms. The diff of these changes look large, but they are just relocation of structs and enum types to kmac.c and removal of some obsolete assertions.

Related to #16410.


[Test] Write test for replay protection for nonce

Write test for replay protection for,

[ ] Missing nonce
[ ] Duplicate nonce.

Nonce logic is covered quite comprehensively here


Circular Volume

A challenge I’m willing to accept (and honestly the lowest priority on the list), but a way to make a knob to control the volume. This will be handled last in the list of updates.

Closed because of a duplicate of #32.


Update dependencies for Senzing 3.8.0

See https://github.com/Senzing/senzing-tools/issues/137

Pull requests:

https://github.com/Senzing/demo-entity-search/pull/10


Using Function.bind causes a method-unbinding error.

Flow version: v0.153.0
Expected behavior
A method bound to the this reference should suppress the method-unbinding error. Binding a method to this prevents the exact errors that the method-unbinding check is meant uncover. It also makes it difficult to bind event handlers using vanilla JS or JQuery.
Actual behavior
The following code:
class A {
  events() {
    this._onSubmit.bind(this);
  }
  _onSubmit() {}
}

produces the error:
../\-:3:     this._onSubmit.bind(this);
                  ^ Cannot get `this._onSubmit` because property `_onSubmit` [1] cannot be unbound from the context [2] where it was defined. [method-unbinding]
    References:
    ../\-:3:     this._onSubmit.bind(this);
                      ^ [1]
    ../\-:5:   _onSubmit() {}
               ^ [2]

Link to Try-Flow or Github repo: https://flow.org/try/#0MYGwhgzhAECC0G8BQ1oFMBuaB2AXCAFAJSIqrS4AWAlhAHQD6A9tgMoCuARgLbW52dq2ACYEqtIgG4yAXzLM2XXrmKI5MoA

This is working as intended. Prefer to use an auto-binding arrow method in cases like this.


Mention backtracking resistance in the project summary?

My first thought was "why aren't other fast stream ciphers (e.g. Salsa) sufficient"?
Looks like the main qualitative motivation is backtracking resistance, which takes a dive into the README to understand. I think it would be nice to highlight at the top of the project to distinguish its goals!

Hi, thanks for suggesting this :) Changed to "Fast backtracking-resistant random generator (pending publication)" - does that cover all the bases?

Looks like it to me! Thanks for making the change. :-)


[Open Contribution Bounty] Track #3: Technical Blog

Description
List of track topics can be found here: https://gist.github.com/danielbui12/bba6f5676d2fb2cc801ee065a021aa62
Please read this information first before working on this issue
Before committing to the tasks in the community, please skim through the guidelines below to grasp the overall idea of how the community works first. It does not take long but I believe it will give you a big picture of the vision and culture of OpenGuild.

OpenGuild Contribution Guidelines 🤝: https://github.com/orgs/openguild-labs/discussions/8
OpenGuild Community Guidelines 🔥: https://github.com/orgs/openguild-labs/discussions/3
FAQ Who own the community assets?: https://github.com/orgs/openguild-labs/discussions/9

Hi, I took a look at the guidelines, I would like to be assigned to the task.

Hey @Emmanueltech, it's good to hear that. This is part of Open Guild's Open Contribution Bounty program. If you'd like to participate, you can register using this form: https://noteforms.com/forms/open-contribution-bounty-ofolad.
There are also many other exciting tracks, you can check them out here: https://openguild.wtf/bounty.
Don't forget to join Open Guild's Discord: https://discord.com/invite/CAHuhcYkPN. If you have any questions, don't hesitate to ask in the Discord.
Thanks!

Can I message you on Discord to keep this channel clean?

@Emmanueltech sure, here is my Discord 👉 danielbui12


Streamlink Twitch GUI

PR for the upcoming repo-rename changes.
I would like to do all this during this weekend if possible.
This will enable the 1.0.0 release.
@cdrage
I'll send you an email (the address on your GH profile) regarding the repo transition, but I also wanted to ping you here, so you can see the status of this PR.

To the package maintainers:
I'm pinging you here, because I want to make sure that the transition will be as smooth as possible.
Also, let's ignore the automation part I was talking about in the last release for now... 😃
@InfernoZeus
https://github.com/bastimeyer/livestreamer-twitch-gui/commit/94a4a844f52f0877faf02f540ec211e861c1a7af#commitcomment-19451912
The package changes can all easily be done after the 1.0.0 release.
Could you add me to the co-maintainer list then, so I can apply changes to it as well? Btw, the xorg-xwininfo package is not required anymore. Can we also please change the format of the package version to not include the "v"? I'm just using it for the git tags and file names and it shouldn't be included in package version.
The streamlink AUR package is being maintained by @mmetak, but he already asked a packager of the community repo to include it in there (see https://github.com/streamlink/streamlink/pull/188#issuecomment-262067461).
@scowalt
https://github.com/bastimeyer/livestreamer-twitch-gui/commit/94a4a844f52f0877faf02f540ec211e861c1a7af#commitcomment-19439801
This PR also includes changes to the choco package config files, although probably unnecessary, since you've said that you wanted to change the package to not be downloader-package anymore. But wouldn't this require a setup for automatically built packages? I think it's probably wiser to keep everything the way it is for now, so the release doesn't get delayed any further.
Btw, I'm not sure if I have messed up the changelog parser by using a different format in the latest changelog. You should validate this before publishing it.
@NGMarmaduke
This will probably just be a simple package name and file URL change.
Btw, I will change the filename again before I'm going to release 1.0.0 (MacOS instead of osx64).
@scowalt
@NGMarmaduke
Do you guys also want to create a package for Streamlink, so we don't need to depend on Livestreamer any more? There are no streamlink packages available yet in the repos of these package managers.
I hope I don't sound in any way demanding or so. 😄  If you want to do this, please open a thread on the streamlink repo and let them know.
https://chocolatey.org/packages/livestreamer
https://github.com/Homebrew/homebrew-core/blob/master/Formula/livestreamer.rb

Thanks a lot!
I hope I don't have missed anything important.

Regarding chocolatey packing automation: I agree that now is not the right time for that change.
Regarding Streamlink chocolatey package: Sounds like a great idea! I can get one up and running this weekend and I'll let the Streamlink team know.


Update default.vue

Types of changes

[x] Bug fix (a non-breaking change which fixes an issue)
[ ] New feature (a non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)

Description
Since vuetify 2.3 v-content became v-main
Checklist:

[ ] My change requires a change to the documentation.
[ ] I have updated the documentation accordingly. (PR: #)
[ ] I have added tests to cover my changes (if not applicable, please state why)
[ ] All new and existing tests are passing.

Codecov Report

Merging #7638 into dev will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##              dev    #7638   +/-   ##
=======================================
  Coverage   70.28%   70.28%
=======================================
  Files          88       88
  Lines        3749     3749
  Branches     1019     1019
=======================================
  Hits         2635     2635
  Misses        906      906
  Partials      208      208

Flag
Coverage Δ

#unittests
70.28% <ø> (ø)

Continue to review full report at Codecov.

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

Thanks @Kawacrepe for your contribution. For next PRs, would be better using a title compatible to conventional commit :)


Unify cell buttons

Value
It looks like there is a lot of common between our cells, that represent status buttons for many places in the dashboard. If we extract some repeated functionality into a parent class, then the next buttons will be much simpler.
Possible solution
Detect repeated patterns in multiple cells, extract common methods into a parent class.
For tests also define some shared examples, that can simplify testing.

Also consider such cases https://github.com/howtohireme/give-me-poc/pull/356/files#diff-da4c2ca4d0dcbe9e8086f667bdc436deR19 and move them to cells.
Probably it deserves a separate refactoring task.


Create an all features installable example

Description
To ease with development, it would be useful to have an installable example that has the following:

Singleton
Nested module
Regular module
Block with all supported fields
Repeater with all supported fields
Module with all supported fields

We can also use this in the future for automated testing.

Hello,
Where can I find this example?
Thanks a lot.


[feature] Make screenpipe able to use the computer

describe the feature
Same as computer use from https://www.anthropic.com/news/3-5-models-and-computer-use
why is this needed?
Why would computer users do things on computers if they can just ask the AI to do it?
alternatives considered
Integrate with the lower level APIs of every possible app. This is a much harder problem.

Related https://github.com/mediar-ai/screenpipe/issues/429

haha yeah
i was thinking in creating API so people can use JS API to interact with mouse, keyboard, etc. in our plugin system
then later we can just generate automation of their work day

ill launch it in 1h

i think this is still early, openinterpreter and adept are on this for a while and there is still no real use case, nobody use this
for screenpipe we're more focused on building solid data infrastructure and let people experiment with this, but I think LLM are still a bit early for something really reliable and actually useful, in addition to the fact that an AI taking control over my computer will actually reduce my bandwidth, but maybe at night

Yeah agreed it's early, I think it becomes real in 6 months - one year
I think it might make more sense in a VM, so it automates boring things without taking the user time. That or truly be in sync with the user intent and work together but that's harder

hmm i like the idea of the VM
the problem of tools like Zapier, gumloop, etc.

cost 10x more because it runs on the server
needs very sensitive access like gmail etc. needs tons of tokens and things like this that are there on the client
basically the vm can copy paste the tokens easily
no interruption

i can imagine that you do some work and then there is 100 AI VMs doing other things for you on the internet based on your activity

Yeah I agree it's not easy to solve the security topic here.

you do some work and then there is 100 AI VMs doing other things for you
on the internet based on your activity

Yeah I think that would be great. Given full context of one person work, I
think it should be possible even for current LLM to follow up on some of
the most trivial but time intensive tasks independently. For example doing
all kind of redtape filling for the user, checking the state of various
system of interest (PRs/issue solved, release of dependencies, state of
projects of interest...), testing out projects of competition and
aggregating the info...
On Sat, Nov 2, 2024, 00:12 Louis Beaumont @.***> wrote:

Yeah agreed it's early, I think it becomes real in 6 months - one year
I think it might make more sense in a VM, so it automates boring things
without taking the user time. That or truly be in sync with the user intent
and work together but that's harder
hmm i like the idea of the VM
the problem of tools like Zapier, gumloop, etc.

cost 10x more because it runs on the server
needs very sensitive access like gmail etc. needs tons of tokens and
things like this that are there on the client
basically the vm can copy paste the tokens easily
no interruption

i can imagine that you do some work and then there is 100 AI VMs doing
other things for you on the internet based on your activity
—
Reply to this email directly, view it on GitHub
https://github.com/mediar-ai/screenpipe/issues/567#issuecomment-2452705280,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAR437QUZHRZX7OQ6BLFSVLZ6QDHNAVCNFSM6AAAAABQNRGM22VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDINJSG4YDKMRYGA
.
You are receiving this because you authored the thread.Message ID:
@.***>


Fix for PHP 7.3: "continue" targeting switch is equivalent to "break"…

…. Did you mean to use "continue 2"?
From Fedora QA
https://apps.fedoraproject.org/koschei/package/php-zendframework-zend-file?collection=f30

@remicollet thank you


externalContracts section tweaks

Description:

Moved the externalContracts section to its own page.
Tweaked hooks.md page with some more context around deployedContracts.ts
Added a note in  useScaffoldWatchContractEvent about https://github.com/scaffold-eth/scaffold-eth-2/issues/838

Love this @technophile-04 Thanks! It was hard to find before. Just left a emoji comment :D

Merging this 🙌