Update form name by storing name on FormDef instead of Form

Closes #355 by moving a form's name (or  as defined in the form XML) from Form to FormDef. Form will always reference the appropriate FormDef and get the name from there.
This PR includes a migration that adds name to the form_defs table and backfills it with form title information read from form XML. It also includes a migration to drop the name field from the forms table. (Er, I was nervous about dropping that field so I just changed the column name but will change the migration to drop the column before I finalize this PR.)
One thing that changes is that a little bit more information about an unpublished form comes through the API (like its version and sha) when that information used to be null. It is still possible to determine if a form is unpublished by looking at its publishedAt field, though. We should probably add a note about this to the docs.
Endpoints that only show published forms (like the OpenRosa formList) are unaffected and work the same as before.

The frontend COULD show the historical form names, now, and not just the version...

merged via https://github.com/getodk/central-backend/commit/ee7ba91488e6b3d83e2d0d69eed09e6143902e90


Client send large amount of info?t request on fail connection

Here is my stack : Spring + SockJS + StompJS. When the connexion fails the client sends tons of info?t request (see screenshot). Is there a way to avoid this behavior??

Any update on this topic?


any interest in Vulkan-ValidationLayers test results?

I ran the current KhronosGroup/Vulkan-ValidationLayers tests against MoltenVK.  Most tests pass; there are 3 test cases that abort, 8 that segfault, and 598 that fail.  I'm not in a position to analyze whether these failures are due to test issues in Vulkan-ValidationLayers, product issues in MoltenVK, or Apple driver issues.
If there's any interest from MoltenVK in investigating these issues, I'd be happy to help where I can.
I'll post a list of failed tests momentarily, for the curious.

moltenvk.txt

@lunarpapillo Thanks for providing this.
We also rely heavily on Vulkan CTS (which also shows many fails), and this can prove helpful as well.


Change default normalization of B-field in torus to the HARM-style normalization

PR Summary
What it says on the can. This was required to get the torus to look more like the one we're all used to. There's a switch in the problem generator to use one or the other. I also made several quality of life changes:

I changed the problem modifier to set up the grid exactly as bhlight does by default. This moves the inner boundary further into the horizon. The problem modifier now reports what it changed x1min and x1max to, as well as what the inner radius is.
I wrote some routines to calculate b^2 in relativity_utils.hpp
I added a routine to calculate the beta used for normalization via the minimum value or the old HARM style. The problem generator now reports both values.
I changed the default inner and outer radii of the torus in the input deck to match the standard values for a 2D torus in HARM/bhlight.
I moved all the utility functions in torus.cpp to the bottom of the file, with some prototypes at the top. I find this easier to read.

PR Checklist

[x] Adds a test for any bugs fixed. Adds tests for new features.
[x] Format your changes by calling scripts/bash/format.sh.
[x] Explain what you did.

Because I was sick of waiting, I also modified the movie scripts to render the frames in parallel.


zero_or_one and at_most_k

There is a "zero_or_more" and "one_or_more" in guidance. It would be nice to have a "zero_or_one" and a "at_most_k" as well to make composing / building grammars easier.
The zero_or_one in particular would be pleasant. I see this for zero_or_more in the guidance codebase:
@guidance(stateless=True)
def zero_or_more(model, value):
return model + select(["", value], recurse=True)
Would this work for zero_or_one?
@guidance(stateless=True)
def zero_or_one(model, value):
return model + select(["", value], recurse=False)

Actually, I was able to do this in the end with:
@guidance(stateless=True)
def zero_or_one(model, value):
return model + select(["", value], recurse=False)
@guidance(stateless=True)
def at_most_k_times(model, value, k):    # k should be greater than 1
assert k > 1, "k should be more than 1 repetition"
result = model + zero_or_one(value)
for i in range(k-1):
    result += zero_or_one(value)
return result

Leaving this up for now in case anyone spots that I messed up something.

zero_or_one exists under the name "optional":
https://github.com/guidance-ai/guidance/blob/25bb53d90bb18e3689170f7915cd30743d5896e5/guidance/library/_optional.py#L4


indentation issue, should be indent 10 and not 12

https://github.com/aquasecurity/aqua-helm/blob/2c1ccf41702c6cd153c95f4a949c95a36b0f1f57/scanner/templates/scanner-deployment.yaml#L68

Hi @alexinthesky, Thanks for writing.
Raised a PR for the fix PR: https://github.com/aquasecurity/aqua-helm/pull/167


Combine rpc-extras and rpc-maas, include os-a-d

This moves the maas plugins into rpc-extras along osad.
We still need to rename the repo though.
Pinning will be easy, we just update the submodule to the pin, then pin this repo.
MaaS is more fun, given that it is made to run only with how we deploy live environments, I can only test some/most of the play.  It works and the failures are where I expect given I am testing on a public cloud instance and not an actual install.  So I'm calling it good til we get better testing.

:-1: You should strip all commits from me just for giggles.

Seriously though, :+1: good work.

ya, wasn't sure people wanted history, so defaulted to the safe option :D

History is fine until someone tries to blame something on me. =P

Thanks for this. I'm going to do a few test deploys with this before giving a thumbs up.

ya, if anything it probably needs that readme you were working on I think

So far I've been able to spin up instances and run RPC playbooks without issue (save for where I've left configuration values out).
I think we should update the README before merging this stuff in, so we have at least have some reference outside of git history.

https://github.com/nrb/rpc-extras/commit/572db1e5784a1acdf971cbbd47e521a0e7975957#commitcomment-10949800
the readme still needs some updates and probably an additional script for the logstash deploy

it's my understanding that osad sources it's config from it's repo, then afterwords copies to /etc is it the other way around?

os-a-d should only source from /etc/

https://review.openstack.org/#/c/181496/ should fix the aio issue


stable/redis: Master not failing over to slave

Using this helm chart, deployed 1 master + 3 slaves + 4 sentinels on 4 different nodes in ICP kubernetes.

In the sentinel, I did this
sentinel get-master-addr-by-name mymaster
lets say i get output "master1"
In the master Redis I do this
redis-cli -p 6379 DEBUG sleep 30
(This command will make our master no longer reachable, sleeping for 30 seconds. It basically simulates a master hanging for some reason.)
Now when i repeat #1 until 30+ seconds, at some point the output should differ from the output in #1. But it does not happen. Master remains master.
This does not pass the fail over test I am doing. What am I doing wrong?

I am evaluating this chart for our production use. My criteria is:

master and slaves should be on different nodes.
no single point failure.

do you have any thoughts on above test? Please let me know
But let's say if i do just the below, then fail over happens and a slave becomes new master.
SENTINEL failover <master name>
(Force a failover as if the master was not reachable, and without asking for agreement to other Sentinels (however a new version of the configuration will be published so that the other Sentinels will update their configurations).

Reference: https://redis.io/topics/sentinel#a-quick-tutorial

Hi @ravinderb2 ,
The test you are using should be correct as it is documented on the Redis website.
You could also try to kill the master pod directly, in that way it is sure it will be not reachable.
Apart from that, I think you could be interested in the next major changes for this Helm Chart. You can see the PR here: https://github.com/helm/charts/pull/21258
With those changes, sentinel won't be needed anymore.

Hi @ravinderb2
Just came here to report a very similar issue but it looks like it's the same issue as yourself.
Just to put things in context:

The cluster contains 3 nodes and each node is running redis+sentinel
By default 3 pods are started redis-master-0, redis-slave-0 and redis-slave1 (all on different nodes)
If I force of failover of redis-master-0 then one of the slave is promoted, in this case slave-0
Problem is when master-0 comes back online redis ends up being split-brain, slave-0 is master, slave-1 is a slave of slave-0 but master-0 is also master without any slaves.

Here are the relevant redis info from the different nodes:
redis-master-0 (after restart from failover)
# Replication
role:master
connected_slaves:0
master_replid:81e9f47b37fab6f3aa19c5cc7f7ebd88b35e6bb5
master_replid2:0000000000000000000000000000000000000000
master_repl_offset:0
second_repl_offset:-1
repl_backlog_active:0
repl_backlog_size:1048576
repl_backlog_first_byte_offset:0
repl_backlog_histlen:0

redis-slave-0 (after promotion to master)
# Replication
role:master
connected_slaves:1
slave0:ip=<IP_ADDRESS>,port=6379,state=online,offset=742199557,lag=1
master_replid:c81fc2e5d50177c91b8113909459302139039932
master_replid2:0a4fc8dbd0c9b315eda864042c40c771e58a23cd
master_repl_offset:742199557
second_repl_offset:526794803
repl_backlog_active:1
repl_backlog_size:1048576
repl_backlog_first_byte_offset:741150982
repl_backlog_histlen:1048576

redis-slave-1
# Replication
role:slave
master_host:<IP_ADDRESS>
master_port:6379
master_link_status:up
master_last_io_seconds_ago:2
master_sync_in_progress:0
slave_repl_offset:742202495
slave_priority:100
slave_read_only:1
connected_slaves:0
master_replid:c81fc2e5d50177c91b8113909459302139039932
master_replid2:0a4fc8dbd0c9b315eda864042c40c771e58a23cd
master_repl_offset:742202495
second_repl_offset:526794803
repl_backlog_active:1
repl_backlog_size:1048576
repl_backlog_first_byte_offset:741153920
repl_backlog_histlen:1048576

Here is the config i'm using:
# Based on values-production.yaml

global:
  redis: {}

## Bitnami Redis image version
## ref: https://hub.docker.com/r/bitnami/redis/tags/
##
image:
  registry: docker.io
  repository: bitnami/redis
  tag: 5.0.7-debian-9-r50
  pullPolicy: IfNotPresent

## String to partially override redis.fullname template (will maintain the release name)
##
# nameOverride:

## String to fully override redis.fullname template
##
# fullnameOverride:

## Cluster settings
cluster:
  enabled: true
  slaveCount: 2

## Use redis sentinel in the redis pod. This will disable the master and slave services and
## create one redis service with ports to the sentinel and the redis instances
sentinel:
  enabled: true
  ## Require password authentication on the sentinel itself
  ## ref: https://redis.io/topics/sentinel
  usePassword: true
  ## Bitnami Redis Sentintel image version
  ## ref: https://hub.docker.com/r/bitnami/redis-sentinel/tags/
  ##
  image:
    registry: docker.io
    repository: bitnami/redis-sentinel
    ## Bitnami Redis image tag
    ## ref: https://github.com/bitnami/bitnami-docker-redis-sentinel#supported-tags-and-respective-dockerfile-links
    ##
    tag: 5.0.7-debian-9-r44
    ## Specify a imagePullPolicy
    ## Defaults to 'Always' if image tag is 'latest', else set to 'IfNotPresent'
    ## ref: http://kubernetes.io/docs/user-guide/images/#pre-pulling-images
    ##
    pullPolicy: IfNotPresent
    ## Optionally specify an array of imagePullSecrets.
    ## Secrets must be manually created in the namespace.
    ## ref: https://kubernetes.io/docs/tasks/configure-pod-container/pull-image-private-registry/
    ##
    # pullSecrets:
    #   - myRegistryKeySecretName
  masterSet: mymaster
  initialCheckTimeout: 5
  quorum: 2
  downAfterMilliseconds: 60000
  failoverTimeout: 18000
  parallelSyncs: 1
  port: 26379
  ## Additional Redis configuration for the sentinel nodes
  ## ref: https://redis.io/topics/config
  ##
  configmap:
  ## Enable or disable static sentinel IDs for each replicas
  ## If disabled each sentinel will generate a random id at startup
  ## If enabled, each replicas will have a constant ID on each start-up
  ##
  staticID: false
  ## Configure extra options for Redis Sentinel liveness and readiness probes
  ## ref: https://kubernetes.io/docs/tasks/configure-pod-container/configure-liveness-readiness-probes/#configure-probes)
  ##
  livenessProbe:
    enabled: true
    initialDelaySeconds: 5
    periodSeconds: 5
    timeoutSeconds: 5
    successThreshold: 1
    failureThreshold: 5
  readinessProbe:
    enabled: true
    initialDelaySeconds: 5
    periodSeconds: 5
    timeoutSeconds: 1
    successThreshold: 1
    failureThreshold: 5
  ## Redis Sentinel resource requests and limits
  ## ref: http://kubernetes.io/docs/user-guide/compute-resources/
  # resources:
  #   requests:
  #     memory: 256Mi
  #     cpu: 100m
  ## Redis Sentinel Service properties
  service:
    ##  Redis Sentinel Service type
    type: ClusterIP
    sentinelPort: 26379
    redisPort: 6379

    ## Specify the nodePort value for the LoadBalancer and NodePort service types.
    ## ref: https://kubernetes.io/docs/concepts/services-networking/service/#type-nodeport
    ##
    # sentinelNodePort:
    # redisNodePort:

    ## Provide any additional annotations which may be required. This can be used to
    ## set the LoadBalancer service type to internal only.
    ## ref: https://kubernetes.io/docs/concepts/services-networking/service/#internal-load-balancer
    ##
    annotations: {}
    labels: {}
    loadBalancerIP:

## Specifies the Kubernetes Cluster's Domain Name.
##
clusterDomain: cluster.local

networkPolicy:
  ## Specifies whether a NetworkPolicy should be created
  ##
  enabled: false

  ## The Policy model to apply. When set to false, only pods with the correct
  ## client label will have network access to the port Redis is listening
  ## on. When true, Redis will accept connections from any source
  ## (with the correct destination port).
  ##
  # allowExternal: true

  ## Allow connections from other namespacess. Just set label for namespace and set label for pods (optional).
  ##
  ingressNSMatchLabels: {}
  ingressNSPodMatchLabels: {}

serviceAccount:
  ## Specifies whether a ServiceAccount should be created
  ##
  create: false
  ## The name of the ServiceAccount to use.
  ## If not set and create is true, a name is generated using the fullname template
  name:

rbac:
  ## Specifies whether RBAC resources should be created
  ##
  create: false

  role:
    ## Rules to create. It follows the role specification
    # rules:
    #  - apiGroups:
    #    - extensions
    #    resources:
    #      - podsecuritypolicies
    #    verbs:
    #      - use
    #    resourceNames:
    #      - gce.unprivileged
    rules: []

## Redis pod Security Context
securityContext:
  enabled: true
  fsGroup: 1001
  runAsUser: 1001
  ## sysctl settings for master and slave pods
  ##
  ## Uncomment the setting below to increase the net.core.somaxconn value
  ##
  # sysctls:
  # - name: net.core.somaxconn
  #   value: "10000"

## Use password authentication
usePassword: true
## Redis password (both master and slave)
## Defaults to a random 10-character alphanumeric string if not set and usePassword is true
## ref: https://github.com/bitnami/bitnami-docker-redis#setting-the-server-password-on-first-run
##
password:
## Use existing secret (ignores previous password)
existingSecret: redis
## Password key to be retrieved from Redis secret
##
existingSecretPasswordKey: redis-password

## Mount secrets as files instead of environment variables
usePasswordFile: false

## Persist data to a persistent volume (Redis Master)
persistence: {}
  ## A manually managed Persistent Volume and Claim
  ## Requires persistence.enabled: true
  ## If defined, PVC must be created manually before volume will be bound
  # existingClaim:

# Redis port
redisPort: 6379

##
## Redis Master parameters
##
master:
  ## Redis command arguments
  ##
  ## Can be used to specify command line arguments, for example:
  ##
  command: "/run.sh"
  ## Additional Redis configuration for the master nodes
  ## ref: https://redis.io/topics/config
  ##
  configmap:
  ## Redis additional command line flags
  ##
  ## Can be used to specify command line flags, for example:
  ##
  ## extraFlags:
  ##  - "--maxmemory-policy volatile-ttl"
  ##  - "--repl-backlog-size 1024mb"
  extraFlags: []
  ## Comma-separated list of Redis commands to disable
  ##
  ## Can be used to disable Redis commands for security reasons.
  ## Commands will be completely disabled by renaming each to an empty string.
  ## ref: https://redis.io/topics/security#disabling-of-specific-commands
  ##
  # disableCommands:
  # - FLUSHDB
  # - FLUSHALL

  ## Redis Master additional pod labels and annotations
  ## ref: https://kubernetes.io/docs/concepts/overview/working-with-objects/labels/
  podLabels: {}
  podAnnotations: {}

  ## Redis Master resource requests and limits
  ## ref: http://kubernetes.io/docs/user-guide/compute-resources/
  # resources:
  #   requests:
  #     memory: 256Mi
  #     cpu: 100m
  ## Use an alternate scheduler, e.g. "stork".
  ## ref: https://kubernetes.io/docs/tasks/administer-cluster/configure-multiple-schedulers/
  ##
  # schedulerName:

  ## Configure extra options for Redis Master liveness and readiness probes
  ## ref: https://kubernetes.io/docs/tasks/configure-pod-container/configure-liveness-readiness-probes/#configure-probes)
  ##
  livenessProbe:
    enabled: true
    initialDelaySeconds: 5
    periodSeconds: 5
    timeoutSeconds: 5
    successThreshold: 1
    failureThreshold: 5
  readinessProbe:
    enabled: true
    initialDelaySeconds: 5
    periodSeconds: 5
    timeoutSeconds: 1
    successThreshold: 1
    failureThreshold: 5

  ## Redis Master Node selectors and tolerations for pod assignment
  ## ref: https://kubernetes.io/docs/concepts/configuration/assign-pod-node/#nodeselector
  ## ref: https://kubernetes.io/docs/concepts/configuration/assign-pod-node/#taints-and-tolerations-beta-feature
  ##
  # nodeSelector: {"beta.kubernetes.io/arch": "amd64"}
  # tolerations: []
  ## Redis Master pod/node affinity/anti-affinity
  ##
  affinity: {}

  ## Redis Master Service properties
  service:
    ##  Redis Master Service type
    type: ClusterIP
    port: 6379

    ## Specify the nodePort value for the LoadBalancer and NodePort service types.
    ## ref: https://kubernetes.io/docs/concepts/services-networking/service/#type-nodeport
    ##
    # nodePort:

    ## Provide any additional annotations which may be required. This can be used to
    ## set the LoadBalancer service type to internal only.
    ## ref: https://kubernetes.io/docs/concepts/services-networking/service/#internal-load-balancer
    ##
    annotations: {}
    labels: {}
    loadBalancerIP:
    # loadBalancerSourceRanges: ["<IP_ADDRESS>/8"]

  ## Enable persistence using Persistent Volume Claims
  ## ref: http://kubernetes.io/docs/user-guide/persistent-volumes/
  ##
  persistence:
    enabled: true
    ## The path the volume will be mounted at, useful when using different
    ## Redis images.
    path: /data
    ## The subdirectory of the volume to mount to, useful in dev environments
    ## and one PV for multiple services.
    subPath: ""
    ## redis data 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: "-"
    accessModes:
    - ReadWriteOnce
    size: 8Gi

  ## Update strategy, can be set to RollingUpdate or onDelete by default.
  ## https://kubernetes.io/docs/tutorials/stateful-application/basic-stateful-set/#updating-statefulsets
  statefulset:
    updateStrategy: RollingUpdate
    ## Partition update strategy
    ## https://kubernetes.io/docs/concepts/workloads/controllers/statefulset/#partitions
    # rollingUpdatePartition:

  ## Redis Master pod priorityClassName
  # priorityClassName: {}

##
## Redis Slave properties
## Note: service.type is a mandatory parameter
## The rest of the parameters are either optional or, if undefined, will inherit those declared in Redis Master
##
slave:
  ## Slave Service properties
  service:
    ## Redis Slave Service type
    type: ClusterIP
    ## Redis port
    port: 6379
    ## Specify the nodePort value for the LoadBalancer and NodePort service types.
    ## ref: https://kubernetes.io/docs/concepts/services-networking/service/#type-nodeport
    ##
    # nodePort:

    ## Provide any additional annotations which may be required. This can be used to
    ## set the LoadBalancer service type to internal only.
    ## ref: https://kubernetes.io/docs/concepts/services-networking/service/#internal-load-balancer
    ##
    annotations: {}
    labels: {}
    loadBalancerIP:
    # loadBalancerSourceRanges: ["<IP_ADDRESS>/8"]

  ## Redis slave port
  port: 6379
  ## Can be used to specify command line arguments, for example:
  ##
  command: "/run.sh"
  ## Additional Redis configuration for the slave nodes
  ## ref: https://redis.io/topics/config
  ##
  configmap:
  ## Redis extra flags
  extraFlags: []
  ## List of Redis commands to disable
  # disableCommands:
  # - FLUSHDB
  # - FLUSHALL

  ## Redis Slave pod/node affinity/anti-affinity
  ##
  affinity: {}

  ## Configure extra options for Redis Slave liveness and readiness probes
  ## ref: https://kubernetes.io/docs/tasks/configure-pod-container/configure-liveness-readiness-probes/#configure-probes)
  ##
  livenessProbe:
    enabled: true
    initialDelaySeconds: 30
    periodSeconds: 10
    timeoutSeconds: 5
    successThreshold: 1
    failureThreshold: 5
  readinessProbe:
    enabled: true
    initialDelaySeconds: 5
    periodSeconds: 10
    timeoutSeconds: 10
    successThreshold: 1
    failureThreshold: 5

  ## Redis slave Resource
  # resources:
  #   requests:
  #     memory: 256Mi
  #     cpu: 100m

  ## Redis slave selectors and tolerations for pod assignment
  # nodeSelector: {"beta.kubernetes.io/arch": "amd64"}
  # tolerations: []

  ## Use an alternate scheduler, e.g. "stork".
  ## ref: https://kubernetes.io/docs/tasks/administer-cluster/configure-multiple-schedulers/
  ##
  # schedulerName:

  ## Redis slave pod Annotation and Labels
  podLabels: {}
  podAnnotations: {}

  ## Redis slave pod priorityClassName
  # priorityClassName: {}

  ## Enable persistence using Persistent Volume Claims
  ## ref: http://kubernetes.io/docs/user-guide/persistent-volumes/
  ##
  persistence:
    enabled: true
    ## The path the volume will be mounted at, useful when using different
    ## Redis images.
    path: /data
    ## The subdirectory of the volume to mount to, useful in dev environments
    ## and one PV for multiple services.
    subPath: ""
    ## redis data 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: "-"
    accessModes:
    - ReadWriteOnce
    size: 8Gi

  ## Update strategy, can be set to RollingUpdate or onDelete by default.
  ## https://kubernetes.io/docs/tutorials/stateful-application/basic-stateful-set/#updating-statefulsets
  statefulset:
    updateStrategy: RollingUpdate
    ## Partition update strategy
    ## https://kubernetes.io/docs/concepts/workloads/controllers/statefulset/#partitions
    # rollingUpdatePartition:

## Prometheus Exporter / Metrics
##
metrics:
  enabled: false

##
## Init containers parameters:
## volumePermissions: Change the owner of the persist volume mountpoint to RunAsUser:fsGroup
##
volumePermissions:
  enabled: false

## Redis config file
## ref: https://redis.io/topics/config
##
configmap: |-
  # Enable AOF https://redis.io/topics/persistence#append-only-file
  appendonly yes
  # Disable RDB persistence, AOF persistence already enabled.
  save ""

## Sysctl InitContainer
## used to perform sysctl operation to modify Kernel settings (needed sometimes to avoid warnings)
sysctlImage:
  enabled: false

## PodSecurityPolicy configuration
## ref: https://kubernetes.io/docs/concepts/policy/pod-security-policy/
##
podSecurityPolicy:
  ## Specifies whether a PodSecurityPolicy should be created
  ##
  create: false

Hi @miguelaeh ,
Thanks so much for you reply. I will try your suggestion right now.
The other question I have:
Output when chart is deployed -
NOTES:
** Please be patient while the chart is being deployed **
Redis can be accessed via port 6379 on the following DNS name from within your cluster:
lame-quail-redis.adphc.svc.cluster.local for read only operations
For read/write operations, first access the Redis Sentinel cluster, which is available in port 26379 using the same domain name above.
To connect to your Redis server:

Run a Redis pod that you can use as a client:
kubectl run --namespace adphc lame-quail-redis-client --rm --tty -i --restart='Never' \
--image docker.io/bitnami/redis:5.0.7-debian-10-r27 -- bash

Connect using the Redis CLI:
redis-cli -h lame-quail-redis -p 6379 # Read only operations
redis-cli -h lame-quail-redis -p 26379 # Sentinel access

To connect to your database from outside the cluster execute the following commands:
kubectl port-forward --namespace adphc svc/lame-quail-redis-master 6379:6379 &
redis-cli -h <IP_ADDRESS> -p 6379

How did this chart got around issue mentioned at - https://redis.io/topics/sentinel#sentinel-docker-nat-and-possible-issues - to achieve lame-quail-redis.adphc.svc.cluster.local DNS to work?
Please let me know.

Question#3
kubectl port-forward --namespace adphc svc/running-kangaroo-redis-master 6379:6379
redis-cli -h <IP_ADDRESS> -p 6379
...is not working for me.
kubectl get services
NAME                              TYPE        CLUSTER-IP      EXTERNAL-IP   PORT(S)              AGE
running-kangaroo-redis            ClusterIP   <IP_ADDRESS>     <none>        6379/TCP,26379/TCP   36m
running-kangaroo-redis-headless   ClusterIP   None            <none>        6379/TCP,26379/TCP   36m

As you see, service is running-kangaroo-redis not running-kangaroo-redis-master.
Port forwarded here
jenkins@069fbc6ba57a:/Users/beerakar$ kubectl port-forward --namespace adphc svc/running-kangaroo-redis 6379:6379
Forwarding from <IP_ADDRESS>:6379 -> 6379

Tried to connect but got error.
544 beerakar:~ $ redis-cli -h localhost -p 6379
Could not connect to Redis at localhost:6379: Connection refused
not connected>

I am debugging here but any help is appreciated.

Hi @ravinderb2 ,

How did this chart got around issue mentioned at - https://redis.io/topics/sentinel#sentinel-docker-nat-and-possible-issues - to achieve lame-quail-redis.adphc.svc.cluster.local DNS to work?
That seems to be an issue with the Chart, it is not supported right now as the announce-ip is not being configured in sentinel. As we are working on a new topology without sentinel this issue should not appear anymore. See the PR above.

Hi @miguelaeh,

Regarding the port-forward, try using <IP_ADDRESS> in the redis-cli command. Also, are your pod running correctly?
<IP_ADDRESS> didn't work neither from redis-cli nor from lettuce java library.
And my pod is working correctly.
I am keeping an eye on your ongoing PR.

Btw, regarding your suggestion on my very first question - yes when I killed the container the fail over worked.
Fail over worked because container port and forwarded port were/are same.

Hi @ravinderb2 ,
Could you provide the exact command you used to deploy the Helm Chart so I can try to reproduce it?
Also, in the mean time could you try with a LoadBalancer service?

Hi @miguelaeh
It's my mistake actually, I was trying from outside our cluster. It was not supposed to work that way. When inside the cluster it worked.
Off the top not sure how to use LoadBalancer service but will give a look.


Thrusters (shuttle go nyoom)

Any time a thruster is enabled it just caches the available impulse for the attached grid
Features:

[x] Click to toggle
[x] Anchoring
[x] Rotating
[x] Visualizer
[x] Ambient sound
[x] Order from cargo
[x] Killing you if you touch them
[x] Fix placement manager

Requires https://github.com/space-wizards/RobustToolbox/pull/2239 to fix the sprite
:cl:

add: Shuttles now require thrust.

What if you add a little distortion effect to the engine's blast when they are active.

What if you add a little distortion effect to the engine's blast when they are active.

what if you coded it


Add more concepts

Merge docs and overview documentation into new data sources page
Add a what is OpenTelemetry page
Move common instrumentation documentation to new instrumenting page
Add a data collection page

Also move collector introduction section of getting started guide to
main collector page.

g2g once the link checker is happy

@austinlparker what am I missing? Appears to pass locally, but fails here -- log message is not helpful, but assume missing something..

/content/en/about/_index.md lines 40 and 41 refer to slugs that used to be at /content/en/docs/_index.md.

Oh didn't look far enough up the log file -- thanks


rename batched -> is_batched_fn

Rename batched to is_batched_fn to more clearly indicate to the user that the flag is referring to whether the function is batched or not.

Codecov Report

Merging #44 (173b9b2) into dev (54f3258) will not change coverage.
The diff coverage is 75.00%.

@@           Coverage Diff           @@
##              dev      #44   +/-   ##
=======================================
  Coverage   64.23%   64.23%
=======================================
  Files          43       43
  Lines        2276     2276
  Branches      404      404
=======================================
  Hits         1462     1462
  Misses        710      710
  Partials      104      104

Flag
Coverage Δ

unittests
64.23% <75.00%> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files
Coverage Δ

mosaic/columns/abstract.py
78.33% <ø> (ø)

mosaic/contrib/wilds/__init__.py
0.00% <ø> (ø)

mosaic/ops/concat.py
89.65% <ø> (ø)

mosaic/mixins/inspect_fn.py
86.00% <60.00%> (ø)

mosaic/datapanel.py
76.14% <100.00%> (ø)

mosaic/mixins/mapping.py
70.49% <100.00%> (ø)

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 54f3258...173b9b2. Read the comment docs.


Missing styling

Hey, cool component.
I've just have some issues by loading the styling, or am i missing something :D?
http://recordit.co/99gKetLtpb
my html
<multiselect v-model="form.client" :options="options" :searchable="false" :close-on-select="false" :show-labels="false" placeholder="Pick a value"></multiselect>

my Vuejs
import Multiselect from 'vue-multiselect'

      data () {
            return {
                options: ['selected'],
                clients: [],
                form: new SparkForm({
                    client: {},
                    notes : '',
                    date  : '',
                    items : [],
                    amount: null
                }),
            };
        },

          components: {
            Multiselect
          },

How did you resolved it?

@janswist Oh i can't remember


Adjustments to #387 (events)

This PR goes through and organises some of the event-handling code. The full list of changes is:

Semantic change: boolean events now trigger when they become truthy (before they occurred when they swap being falsy<->truthy). Note that this required twiddling around a few things as previously it was impossible for an event to trigger on the first step; now they can.
Semantic change: event functions now have the signature (t, y, args *, terms, solver, **etc) for consistency with vector fields and with SaveAt(fn=...).
Feature: now backward-compatible with the old discrete terminating events.
Feature: added diffrax.steady_state_event.
Bugfix: the final t and y from an event are now saved in the correct index of ts and ys, rather than just always being saved at index -1.
Bugfix: at one point args referred to the args coming from a root find rather than the overall diffeqsolve.
Bugfix: the current state.tprev was used instead of the previous state's tnext. (These are usually but not always the same -- in particular when around jumps.)
Bugfix: added some checks when the condition function of an event does not return a bool/float scalar.
Performance: includes a fastpath for skipping the rootfind if no events are triggered.
Performance: now avoiding tracing for the shape of dense_info twice when using adaptive step size controllers alongside events.
Performance: avoided quadratic loop for figuring out what was the first event to trigger.
Chore: added support for the possibility of the final root find (for the time of the event) failing.
Chore: removed some dead code (_bool_event_gradient).
Chore: removed references in the docs to the old discrete_terminating_event.

In addition, some drive-bys:

Fixed warnings about pending deprecations jnp.clip(..., a_min=..., a_max=...).
Had aux_stats (in _integrate.py) forward to the overall output statistics. In practice this is empty but it's worth doing for the future.

Before we can merge this into Diffrax's main branch, there are still some things that need doing -- @cholberg are you able to handle these?

Add a docstring for Event;
Add an example to events.md demonstrating how to use Event;
Update the existing steady-state example to use the new syntax;
Add several tests:

For steady_state_event;
That things behave correctly when a boolean event stops us before we even perform a single step;
Events in combination with adaptive stepping;
Events in combination with vmap (down various different parameters: t, y, and even the definition of the event itself!)
Events in combination with both adaptive stepping and vmap;
Events that are malformed from the user: that we error out appropriately when provided events that return non-scalars, or that return integers, or that return complex numbers.
When using more complicated choice of SaveAt. For example the previous implementation saved results into index -1, which is incorrect in general (e.g. if we have SaveAt(steps=True) then we allocate a buffer of length max_steps, and only expect to partially fill it).

I've tested that this passes all of test_event.py (including all the old ones for discrete terminating events), but haven't checked over every test in Diffrax -- it's possible that I've missed something elsewhere.

That is, you'd like steady_state_,event to return just the condition function, not the Event object itself? If so then sure, that change seems reasonable.


Tech debt for automate HA

Description:
This epic will primarily focus on all tech debt items related to automate HA. We will add a tech-debt label as well to all the issues associated with this epic.
Priority 1 - Health Check script and Advanced validation
Advanced Validation lists
Port Blockage check
Internal connection check PG and ES
Validate system requirements
CIDR validation
Verification on storage and HW/SW requirement
Output/report generation after validation ran
Should be exposed via automate ctl command - HA cluster health check kind of stuff
Pre-deployment  validation script/command - Instances, server, ES, PG count,
Health check list
Heath check script - Metrics, ES heap check, and other metrics for cluster health check

Sharding configuration

HA specific command should not be visible in CLI on automate non-HA.

Versioning for Automate HA - backend components

Removing Kibana from the HA Arch | Should not send logs of PG and ES to same ES | Clean up the kibana, curator service.Public to private for ES ips

For e2e team - Integration testing for all the automate HA CLI commands - Automation of all the CLI commands verification

Note from backend channel updated (Weekly update)
List of identified tech debt items:

Optimise the Airgap bundle: Current size of bundle is 1.9 GB approx, this story is to optimize the size of the bundle

Only relevant code to be pulled:- Currently, the entire code base is in a single bundle (as part of automate deployment), we should pull only those code that is required.

Automate HA deployment should be done via automate deployment service: Currently we are calling automate cluster CLI deploy command internally to deploy automate HA. Might need to make current service.

Support AirGap + non-Airgap (on the fly) type of installations.

Cove scenario for small scale customer:- Chef-Server and Automate running on a single VM

Managed service ( ES | PG )

Integration with new Reporting manager

Adding config like cloud yml to send logs to cloud watch. We can add this as part of the documentation based on the config changes customer can integrate with AWS to get LMM support.

Veracode scanning for automate HA

HA specific command should not be visible in CLI on automate non-HA.

$ sudo chef-automate version
Version: 2
  CLI Build:<PHONE_NUMBER>5409
  Server Build:<PHONE_NUMBER>0523

$ sudo chef-automate --help | grep -i HA
  info                   InFo about automate HA
  init-config-ha         Initialize default config for HA
  provision-infra        Provison automate HA infra.
  secrets                set secrets to automate HA
  ssh                    Set Ssh env for automate HA.
  test                   Run automate HA smoke tests
  workspace              set workspace env for automate HA.

Can/should these all be moved under a top level "HA" command?

sudo chef-automate ha info
sudo chef-automate ha test
etc

Fix the descriptions

capitalize the first letter of each description, e.g. "Set secrets..."
capitalize Automate everywhere
remove the trailing period
Fix "InFo" to Info
Fix typo in Provison to Provision

do not display these commands if automate-cluster-ctl is not installed / check for dependencies

$ sudo chef-automate info
Automate HA info
CommandExecutionError: An issue occurred when running an executable command: please refer

This command will be used to get information of all the components deployed for Automate HA .
Usage:
    chef-automate info
: exec: "automate-cluster-ctl": executable file not found in $PATH

should 'info' be merged into 'status'? can status simply show HA information if we're in an HA mode rather than adding a similar command?
should 'init-config-ha' be merged into 'init-config' ? can we just have sudo chef-automate init-config --ha aws ?


feat: rename some funcs

Codecov Report

Merging #12 (120bb06) into main (3231da7) will decrease coverage by 2.56%.
The diff coverage is 76.66%.

@@            Coverage Diff             @@
##             main      #12      +/-   ##
==========================================
- Coverage   69.61%   67.05%   -2.57%
==========================================
  Files          15       15
  Lines         655      683      +28
==========================================
+ Hits          456      458       +2
- Misses        143      169      +26
  Partials       56       56

Flag
Coverage Δ

unittests
67.05% <76.66%> (-2.57%)
:arrow_down:

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files
Coverage Δ

crtutil/crt.go
62.76% <76.66%> (-23.60%)
:arrow_down:

:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more


Better handling of target_data input without name in grid.transform

[x] Closes #260
[x] Tests added
[x] Passes black .
[ ] User visible changes (including notable bug fixes) are documented in whats-new.rst

I dont think this needs an addition to the whats-new.rst?

I just realized the test was ill-posed, since transform only takes the naming from target_data if target is not an xarray. Fixing that revealed a small bug, but now everything seems in order.
I renamed the function to _check_other_dims to get rid of the misused 'alignment'. How do you feel about that @dcherian?

Thanks for the helpful changes, @rabernat.


perf: use node: prefix to bypass require.cache call for builtins

See https://github.com/fastify/fastify-static/pull/407

Checklist

[ ] run npm run test and npm run benchmark
[ ] tests and/or benchmarks are included
[ ] documentation is changed or added
[x] commit message and code follows the Developer's Certification of Origin
and the Code of conduct

Reran the CI, tests might be flaky

Going to ignore failures. Main branch is failing regardless, so test failures unrelated.


[breadboard-web] Investigate deletion of entries on the Secrets section of the Settings page

In the visual editor, in the Settings modal under the Secrets section, there is something I noticed with the behaviour when deleting an entry which I found a bit counterintuitive.
For example, if I have an existing entry and I click the "trash" icon to delete it, I get asked to confirm the action and then the list is empty with the message "There are currently no entries". This seemed to indicate that the entries were indeed removed. However, it looks like the changes won't apply unless I also click Save before closing the modal, because when I reloaded the page and went back to settings the entry I had "deleted" was still there.
An idea could be to temporarily add deleted entries to a list to indicate that they are "pending deletion" and then when the users click on "Save" at the bottom, they could then get a message from the browser asking if they are sure they want to delete the entries on the "pending" list.
Below is a screenshot of a quick mockup to help with visualising the suggestion above:

You're absolutely right, it's counter-intuitive. Another approach would be to eagerly emit the change since we already ask you if you're sure you want to do it. So I think we should pick one: either don't ask and have a "pending you hitting save" button or we do it eagerly. I think I prefer the former as you might think "bah, I accidentally deleted the wrong secret" and you still have a chance to back out of the change.
What do you think?

A suggestion for the best UX for the pending mode.

Only enable and colour the save button when there are actual changes to be saved.
For "super users" have a "delete without prompt" e.g. Ctrl + Backspace

The "Save" still needs to be pressed after.

Personally, I would prefer to have a way of backing out of deleting secrets too. I agree with using the former approach that you mentioned @paullewis.
I could start looking into implementing this feature following a similar approach to what I presented in the screenshots above if that's okay. But, additionally, it might also be useful to have some "undo" icon next to each entry pending deletion so that people can add/remove entries from that list without having to hit Cancel and then reopen the Settings modal.
I also agree with the UX suggestion from @Mearman. I think disabling the Save button until there's an actual change to "commit" is a good idea.

Just wanted to share an update on this ticket.
Firstly, here is a short demo of what the UI looks like currently:
https://github.com/user-attachments/assets/2ebfb641-79cd-45f8-aa1c-72a96bbce02b
Secondly, I made a list of the main things I've done to achieve the above:

I had a look at the Settings type. See: https://github.com/breadboard-ai/breadboard/blob/a77417aea60472b777d3829ee2685da63ddd607e/packages/visual-editor/src/ui/types/types.ts#L95-L111

Considering that I wanted to see a list of items pending deletion under the existing items, I thought it would make sense to add another prop called pendingItems that would behave in the same way as items:

pendingItems?: Map<SettingEntry["value"]["name"], SettingEntry["value"]>;

Next, I modified the existing deleteItem function by doing the following:

Renamed it to addPendingItem
Removed confirmation dialogue asking the user if they're sure they want to delete a key (since confirming wasn't actually deleting anything unless also hitting Save).
Added a third parameter that sends the entire current item through. The reason for doing this was to be able to get the name and value of the item that is added to the pending list, so that when I try to undo the action, the item will be restored with the original values maintained.

Added a new function called restoreDeletedItem which is called when clicking the Undo button on the UI next to any pending item. This function does pretty much the same as the previous one (addPendingItem), but the other way around. When the undo button is pressed, the item is removed from the pending list and added back into the items list. There is still something that needs to be done at this stage, which is clearing the pendingItems after pressing Save or Cancel. At the moment, even though the Map of pendingItems itself is empty, it still shows on the UI until I reload the page.

The branch I created for this ticket can be found here.
Also, off-topic, all items in any section of the settings overlay seemed to gain an unusual height after editing any property. It's been fixed in this ticket in the highlighted lines here.


vimPlugins: add ChatGPT.nvim

Description of changes

Added https://github.com/jackMort/ChatGPT.nvim
ChatGPT is a Neovim plugin that allows you to interact with OpenAI's GPT-3 language model. With ChatGPT, you can ask questions and get answers from GPT-3 in real-time.
First time contribution!
Hi, this is my first time contribution, so better I will describe what I did.

Run GITHUB_API_TOKEN=<secret> ./update.py --add "jackMort/ChatGPT.nvim" (resulted in the commits in this PR)
Run nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD" (resulted in no code changes / no commits required)
Tested manually with the following config:

{
  inputs = {
    nixpkgs-local.url = "/home/primamateria/dev/nixpkgs";
    flake-utils.url = "github:numtide/flake-utils";

    neovim = {
      url = "github:neovim/neovim?dir=contrib";
      inputs.nixpkgs.follows = "nixpkgs-local";
    };
  };

  outputs = inputs@{ self, flake-utils, nixpkgs-local, neovim, ... }:
    let
      overlay = prev: final: rec {
        neovimPrimaMateria = prev.wrapNeovim neovim.packages.x86_64-linux.neovim {
          withNodeJs = true;
          configure = {
            customRC = ''
              lua << EOF
              require("chatgpt").setup({ })
              EOF
              '';
            packages.myVimPackage.start = [
              final.pkgs.vimPlugins.plenary-nvim
              final.pkgs.vimPlugins.telescope-nvim
              final.pkgs.vimPlugins.nui-nvim
              final.pkgs.vimPlugins.ChatGPT-nvim
            ];
          };
        };
      };

    in flake-utils.lib.eachDefaultSystem (system:
      let
        pkgs = import nixpkgs-local {
          inherit system;
          overlays = [ overlay ];
        };
      in {
        packages = rec {
          inherit (pkgs) neovimPrimaMateria;
          default = neovimPrimaMateria;
        };

        apps = rec {
          neovimPrimaMateria= {
            type = "app";
            program = "${pkgs.neovimPrimaMateria}/bin/nvim";
          };
          default = neovimPrimaMateria;
        };
      });
}

You can see that this plugin depends on other 3 plugins. I was thinking if something needs to be done in the overrides.nix, but as far as I understand, this would not help. These plugins must be listed in the array of plugins explicitly by the user to be available in the nvim runtime.
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

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

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

[x] Fits CONTRIBUTING.md.

I was thinking if something needs to be done in the overrides.nix

I think this might be what you wanted
{
  # ...
  ChatGPT-nvim = super.ChatGPT-nvim.overrideAttrs (old: {
    dependencies = with self; [ nui-nvim plenary-nvim telescope-nvim ];
  });
  # ...
}

I have added the dependencies to the overrides.nix. But this will only install them to the store, and it will not automatically include them to the list of plugins used in neovim. So, the user will still need to explicitly list them in their configuration. At least, it didn't work with my flake I have used for testing.

I was able to start neovim with this with no issues
{
  inputs = {
    nixpkgs.url = "github:PrimaMateria/nixpkgs/vimPlugins-add-chatgptnvim";
  };

  outputs = { self, nixpkgs }:
    let
      inherit (nixpkgs.lib) genAttrs systems;
    in
    {
      packages = genAttrs systems.flakeExposed (system: {
        default = with nixpkgs.legacyPackages.${system}; neovim.override {
          configure = {
            customRC = ''
              lua require("chatgpt").setup({ })
            '';
            packages.all.start = with vimPlugins; [ ChatGPT-nvim ];
          };
        };
      });
    };
}

Oh yes, it works. Also, my config works. I had to be doing something wrong. Probably, I didn't run nix flake update after updating the overrides locally, so I have built it with previously cached nixpkgs.


libgcc_s.so.1 must be installed for pthread_cancel to work

Device: Jetson AGX Xavier
OS: L4T 32.7.4 (Linux 18.04)
ROS Version: Melodic
Python version: 3.6.9
gcc Versions: 8.4.0 and 7.5.0 (Currently 8.4.0 in use)
g++ Version: 8.4.0
bazel Version: 5.2.0
Mediapipe Version: 0.8.9 (This one)
OpenCV Version: 4.8.1
Tensorflow Version: 2.7.0
scikit_learn Version: 0.24.2

Hello,
I am trying to use this package at a Jetson AGX Xavier. After solving the issue here when I try to roslaunch ros_hand_gesture_recognition hand_sign.launch, I see such an output on my terminal screen:
process[hand_sign_recognition-1]: started with pid [22518]
libgcc_s.so.1 must be installed for pthread_cancel to work
[hand_sign_recognition-1] process has died [pid 22518, exit code -6, cmd /home/mericgeren/catkin_ws/src/ros_hand_gesture_recognition/src/hand_sign_recognition.py __name:=hand_sign_recognition __log:=/home/mericgeren/.ros/log/b02b8112-8dc7-11ee-9d36-00044bcc3306/hand_sign_recognition-1.log].
log file: /home/mericgeren/.ros/log/b02b8112-8dc7-11ee-9d36-00044bcc3306/hand_sign_recognition-1*.log
all processes on machine have died, roslaunch will exit
shutting down processing monitor...
... shutting down processing monitor complete
done

Then I have tried the command export OMP_NUM_THREADS=1 and then, I have seen such an output:

Traceback (most recent call last):
  File "/home/mericgeren/catkin_ws/src/ros_hand_gesture_recognition/src/hand_sign_recognition.py", line 50, in <module>
    hand_sign = HandSignRecognition()
  File "/home/mericgeren/catkin_ws/src/ros_hand_gesture_recognition/src/hand_sign_recognition.py", line 25, in __init__
    rospy.get_param("hand_sign_recognition/keypoint_classifier_model"))
  File "/home/mericgeren/catkin_ws/src/ros_hand_gesture_recognition/src/gesture_recognition.py", line 32, in __init__
    self.hands, self.keypoint_classifier, self.keypoint_classifier_labels = self.load_model()
  File "/home/mericgeren/catkin_ws/src/ros_hand_gesture_recognition/src/gesture_recognition.py", line 41, in load_model
    min_tracking_confidence=self.min_tracking_confidence,
  File "/home/mericgeren/.local/lib/python3.6/site-packages/mediapipe/python/solutions/hands.py", line 129, in __init__
    'multi_handedness'
  File "/home/mericgeren/.local/lib/python3.6/site-packages/mediapipe/python/solution_base.py", line 262, in __init__
    self._graph.start_run(self._input_side_packets)
RuntimeError: ; eglGetDisplay() returned error 0x3000ontext_egl.cc:156)
libgcc_s.so.1 must be installed for pthread_cancel to work

Could you offer your advice and guidance please?
Kindest regards.

I have tried to switching back to 7.5.0 version which has it's libgcc_s.so.1 file inside /lib/aarch64-linux-gnu. But, the error persisted. Also, tried this command:
export LD_LIBRARY_PATH=$LD_LIBRARY_PATH:/lib/aarch64-linux-gnu

But nodes still shut themselves down and I still see that " libgcc_s.so.1 must be installed for pthread_cancel to work " message on the screen.


Does Flashinfer support 8-bit attention calculation?

I mean without dequantizing 8-bit kv-cache to fp16

This should be in the plan. ref https://github.com/sgl-project/sglang/pull/1286#issuecomment-2323725290

@Juelianqvq  The feature was deferred because the wheel binary size explosion, I'll work on this after #507 was merged.


Don't modify project libraries during build

[x] This contribution adheres to CONTRIBUTING.md.

What does this Pull Request accomplish?
Don't modify project libraries during build.
Why should this Pull Request be merged?
Since the custom devices in this repo share source dependencies, but don't necessarily all use the same set of VIs from those dependencies, modifying the libraries during build can result in run-time failures.
This is a partial, speculative fix for some issues @Karl-G1 saw in System Explorer when switching between custom devices.
What testing has been done?
Attempted to reproduce the bug after rebuilding SLSC Switch and NI-SWITCH locally but could not.

Have you run the automated tests after building these? There was a change at some point to explicitly modify at least one of these libraries due to something failing. Unfortunately, there's no documentation on what that commit was intended to fix. I only know it was intentional to fix something and not just a standard thing we do because I vaguely remember a conversation that led us to make this change.
https://github.com/ni/niveristand-routing-and-faulting-custom-device/pull/6/commits/2ba0189f9825bbcf9c4158a416d20cbe066225d0

@buckd I have not. I did some sanity checking in System Explorer, but nothing beyond that. I can run the tests manually on the ATS setup tomorrow.

@buckd I've tested concurrent deployments of NI-SWITCH and SLSC Switch (multiple instances of both) without issues, so I'm satisfied with these changes.


ConcurrentModification exception when saving from Studio

OrientDB Version, operating system, or hardware.
v2.2.15
Operating System
Linux
Hi,
A simple save from the studio (just open any record and hit 'Save' button) always throws a ConcurrentModificationException. Here's the log
2017-01-30 18:16:44:402 FINE  {db=nsdev} onOpen [OLuceneIndexFactory]
2017-01-30 18:16:44:407 FINE  {db=nsdev} Read record #107:15305 v.21 size=5867 bytes [OLocalPaginatedStorage]
2017-01-30 18:16:44:410 FINE  {db=nsdev} Updated record #107:15305 v.22 size=5886 [OLocalPaginatedStorage]
2017-01-30 18:16:44:414 FINE  {db=nsdev} onClose [OLuceneIndexFactory]Caught exception
com.orientechnologies.orient.core.exception.OConcurrentModificationException: Cannot UPDATE the record #107:15305 because the version is not the latest. Probably you are updating an old record or it has been modified by another user (db=v22 your=v21)
        DB name="nsdev"
        at com.orientechnologies.orient.core.conflict.OVersionRecordConflictStrategy.checkVersions(OVersionRecordConflictStrategy.java:56)
        at com.orientechnologies.orient.core.conflict.OVersionRecordConflictStrategy.onUpdate(OVersionRecordConflictStrategy.java:43)
        at com.orientechnologies.orient.core.storage.impl.local.OAbstractPaginatedStorage.checkAndIncrementVersion(OAbstractPaginatedStorage.java:3568)
        at com.orientechnologies.orient.core.storage.impl.local.OAbstractPaginatedStorage.doUpdateRecord(OAbstractPaginatedStorage.java:3065)
        at com.orientechnologies.orient.core.storage.impl.local.OAbstractPaginatedStorage.updateRecord(OAbstractPaginatedStorage.java:1121)
        at com.orientechnologies.orient.core.db.document.ODatabaseDocumentTx.executeSaveRecord(ODatabaseDocumentTx.java:2190)
        at com.orientechnologies.orient.core.tx.OTransactionNoTx.saveRecord(OTransactionNoTx.java:181)
        at com.orientechnologies.orient.core.db.document.ODatabaseDocumentTx.save(ODatabaseDocumentTx.java:2716)
        at com.orientechnologies.orient.core.db.document.ODatabaseDocumentTx.save(ODatabaseDocumentTx.java:103)
        at com.orientechnologies.orient.core.record.impl.ODocument.save(ODocument.java:1802)
        at com.orientechnologies.orient.core.record.impl.ODocument.save(ODocument.java:1793)
        at com.orientechnologies.orient.server.network.protocol.http.command.put.OServerCommandPutDocument.execute(OServerCommandPutDocument.java:96)
        at com.orientechnologies.orient.server.network.protocol.http.ONetworkProtocolHttpAbstract.service(ONetworkProtocolHttpAbstract.java:169)
        at com.orientechnologies.orient.server.network.protocol.http.ONetworkProtocolHttpAbstract.execute(ONetworkProtocolHttpAbstract.java:622)
        at com.orientechnologies.common.thread.OSoftThread.run(OSoftThread.java:77)

@andreyvk
i was not able to reproduce it with the bundled db GratefulDeadConcerts
How can i replicate it?

@maggiolo00 strange...
I've actually tried more records and some save fine and some throw this exception. I've already set log level to the FINEST. There's no more log that i can gather for you. Is it possible to debug this some other way?

@andreyvk
If you can create a dataset with some records that fail would be awesome.
I should debug and see the internal state of the record
Could be some field type that makes the difference

@maggiolo00 I'll see what I can do. This is a production db. It's very large and I cant disclose it. However, plz keep this issue open. I'll come back to it.

@andreyvk is the very same record updated in background by the application or any other process?

@lvca no, there's no process on the background.
The database that we have was moved over from 2.1.19.  And previously from earlier versions of Orient.  The whole class of records - one that causes concurrency exception now - seems to have a problem. On top of this issue we are having another one: some indexes are not updated, when we create a new record from our software (basically we cant search properly after that). However, when I store a record from a script (using the same library as is used in our software) or directly from the studio - no problem.
So, it's a mess, basically. When I have something concrete I can send you guys, I'll knock. Meanwhile i'll close this issue.


Add IPython dependency for reqmgr2ms.

Fixes #10676
Status
ready
Description
Adding dependency from IPython because of reqmgr2ms and more precisely MSUnmerged.
Is it backward compatible (if not, which system it affects?)
YES
Related PRs
https://github.com/cms-sw/cmsdist/pull/7148
External dependencies / deployment changes
Yes - it is needed because we use IPython.lib in one of our micro services.

@todor-ivanov can you please elaborate on why iPython is needed in reqmgr2ms and whether there was any alternative for that? Unless it's really needed, we should avoid increasing our image size and our software stack, it's just more maintenance in the long run.
Can you please also point which WMCore PR introduced that dependency (the library being used, not the requirements).

@amaltaro this is the PR which introduces the requirement:
https://github.com/dmwm/WMCore/pull/10671
And the reason is because we want to have a major dump of the the structure of an RSE element with only few  element  per key instead of a full dump. This is trivial with IPython.lib.pretty while it requires quite a lot of additional coding to achieve if we want to implement it with the default pformat library

Thanks, Todor. Since it's only a single line using it, and for a debug logging level, I would suggest to actually update the WMCore code such that we do not depend on it. It's always an extra burden to maintain those...
Spot checks in my inbox make me believe you are already replacing it and also removing this dependency from our stack, right? If not, can you please do so? even if that costs us a few more lines of code.

it is already done @amaltaro :
https://github.com/dmwm/WMCore/pull/10679/files


Add healthcheck for registry-console in openshift e2e

@jim-minter @kwoodson @mjudeikis ptal

label orchestrator/openshift

/label orchestrator/openshift

/approve

@pweil- you can try /lgtming once more, seems to be working now

@CecileRobertMichon @jackfrancis I think the last step to get us to fully functional automated merges is running tests automatically (and possibly having the ability to retest). What needs to happen for that to move forward?

/lgtm


Wikiduino's README out of sync

The README.md of the Wikiduino server is out of sync. Two files are mentioned i.e.

Wikiduino.pde
Wikiduino.ino

But only the Wikduino.ino is present.

Good catch. Have now revised this documentation to acknowledge that we only use the arduino 1.0 suffix convention.


Combined badge + pinning service for package repos

"Badges" are popular for READMEs found on repos hosted on GitHub and other places:
For example:
https://github.com/badges/shields
I was brainstorming ideas with @andrew and we came up with the idea of using badges together with packages that are backed up by IPFS.
A badge could point to a URL hosted on https somewhere that would generate the badge. Clicking on the badge would lead to a web page that would explain how to install the package via a method (or several methods) that uses IPFS.
Additionally, the server that generates the badges could log and crawl the source repos to determine the latest CIDs, and possibly even pin the packages into a ipfs-cluster to ensure they are available via IPFS.

Can we define the output benefits of this workstream?

a nice visible way to indicate a package is available on ipfs?
an easy tool for connecting a github repo to it's published package on ipfs?
a way to get metrics on adoption of packages hosted on ipfs on github?
?

What would cause someone to use this badge vs any other badge, or over just putting a link around an image?


Add sticky headers on homepage table

Fixes #146

Could you review this again, unable to reproduce it?

works for me

looks like chrome is not supporting sticky,
but the artical suggests that chrome should support it

@bnap00 you need to add display:block too to get sticky to work

@satishsingh35 I think that did the trick

Just a thought. Should we also change the font size and background of the header row to match the last row (total)?

Just a thought. Should we also change the font size and background of the header row to match the last row (total)?

the total row is also transparent.
cannot do anything that is transparent

Wasn't able to test this out locally :/
But thank you, closing this because I went with a later submitted patch that worked!


Disposing Sampler causes exceptions, even when Transport is cancelled

When I use the Sampler Instrument and have a tone sequence scheduled and playing, I cannot dispose the sampler immediately after calling Tone.Transport.cancel().
I am currently working around this problem by checking if the active sources have been disposed already.
const samplerTriggerAttack = Tone.Sampler.prototype.triggerAttack;
Tone.Sampler.prototype.triggerAttack = function(notes, time, velocity) {
    if (this._activeSources === null) return this;
    return samplerTriggerAttack.call(this, notes, time, velocity);
};

UPDATE:
Turned out that my Tone.Transport.stop() didn't get called before (my mistake).
I assume Tone.Transport.cancel() does not achieve the same thing here?
UPDATE 2:
I am experiencing this issue again, after I thought it wouldn't occur anymore.
Any suggestions?

I looked at this a bit further and noticed that the onended handler seems to be the perpetrator here:
//remove it when it's done
source.onended = function(){
    var index = this._activeSources[midi].indexOf(source);
    if (index !== -1){
        this._activeSources[midi].splice(index, 1);
    }
}.bind(this);

It gets called after I call sampler.dispose() and the _activeSources reference is already set to null

I have created a small example that is fairly close to my setup:
https://codepen.io/redfox_dw/pen/maPVOr


Change default appVersion to 0.0.0 for fybrik and fybrik-crd charts

Signed-off-by: Revital Sur<EMAIL_ADDRESS>

Closing this as running quick-start  with Install latest development version from GitHub makes the control-plane pods fail due to Imagepull error.
The reason is that the Chart.yaml of fybrik is 0.0.0 which is also the image tag that does not exist in the public repo.


Thank you for push access

Thank you for push access.
In fact, if every PR is merged, it may be even better to go on with usual GitHub flow, as it is better for talking over changes.

sure. I also added you as contributor. And, thanks for contributing too.


HostEndpoint objects remain after calico node is deleted when DATASTORE_TYPE is kubernetes

related issue : #4015
by addressing issue #4015, HostEndpoint objects are deleted after calico node is deleted if we use etcd datastore type. however in kubernetes datastore type, they are still remain. (as NodeDeletionController is registered only when the datastore type is etcd. (sorry if I my understanding is wrong)) I am not sure if hep should be automatically deleted by calico though, it would be great if calico can take care of their deletion.
Expected Behavior

HostEndpoint objects associated with the deleted Node should be deleted after the Node is deleted
Current Behavior

HostEndpoint objects associated with the deleted Node are not deleted after the Node is deleted
Possible Solution

Delete them
Steps to Reproduce (for bugs)

create a k8s cluster with calico in kuberneted datastore type
provision worker node and create HostEndpoint associated with it
delete that worker node and check if HostEndpoint is deleted
after k8s node deletion, calico node is also deleted but HostEndpoint still remains

Context

Your Environment

Calico version : v3.26
Orchestrator version (e.g. kubernetes, mesos, rkt): k8s v1.28
Operating System and version:
Link to your project (optional):

One way we might consider doing this is simply using OwnerReferences to leverage Kubernetes garbage collection of child resources.


Updated to new desktop client beta version (beta2)

Please accept the udpate to desktop client 1.8.0 beta2

Tested if

ownCloud-<IP_ADDRESS>05beta2-setup.exe
ownCloud-<IP_ADDRESS>4beta1.pkg
ownCloud-<IP_ADDRESS>8beta2.pkg

exist. They do. Otherwise, text looks good, too. :+1:, will merge.


Histogram Matching

PR for issue #20

@geekquad have a look at it

Amazing work @SatYu26.

Thank you @geekquad


Please Style the Profile Tab

Conveniently found at /account/profile/ when logged in.  I've connected the profile fields, but it is a bit hideous.  AutoForm does follow Bootstrap styles, in case you're familiar with that.

closed with commit #7d108d0.
A fix for launch sake has been placed where we grab a custom select template.
Defaults will still need to be designed and attributed, but the profile tab now looks functional.


Seeking Assistance with Reproducing Results in 'Interpreting biologically informed neural networks' Paper

Dear Professor,
Sorry to disturb you.
When we reproduced the article BINN, we found that Figure 3 and Figure 4 (a, c) could not be reproduced successfully, and the important features we got could not match the conclusions drawn in your article. Would you like to provide some suggestions to solve the problems?
Best Regards.

Hi!
What aspect of Fig. 3 did you have problems to re-create? Did you run BINN with the same parameters as in the paper, and on the same data (using all samples as background in SHAP)? There is some stochasticity in the detected features, but especially the top features (showcased) should be the same (see our new notebook on robustness).
For Fig. 4 a and c. These are just clustermaps of the top identified proteins (created using seaborn). The proteins can be identified in the first layer of the BINN.
Feel free to get back to me with more information about your pipeline and how I can help you further :)


Consolidate and refactor repo

Currently, this repo is a bit of a mess.
I've started moving portions into their own repos (with history) and starting new for others.
At this stage, only the verify-conformance bot has been moved (to https://github.com/cncf-infra/verify-conformance)
Things to relocate

instant prow cluster
prow.cncf.io configuration
prow.cncf.io Terraform -> cncf-infra/aws-infra ?

I'm unsure what else should be kept and not just archived

chart?
org

An likely archive org

An likely archive org

@hh, what do you mean?

I'm unsure what else should be kept and not just archived

archive the org folder with the repo, or copy over to ii/org in a subfolder

I'm unsure what else should be kept and not just archived

archive the org folder with the repo, or copy over to ii/org in a subfolder

Taking a look at the folder
https://github.com/cncf-infra/prow-config/tree/master/org
is minimal and mostly out dated.
Things that could be kept include

https://github.com/cncf-infra/prow-config/blob/master/org/k8sConf-pr1493.org

ii/org is another story, see https://github.com/ii/org/issues/24.

Yeah either way is fine with me
.


refactor: refine the storage engine

The storage engine in foyer-storage crate was initially designed for large entries disk cache. It used direct i/o and carefully aligned i/o to minimize page cache buffer copy. But it is not optimized for small entries and updates.

For small object, we could use the design of cachelib's BigHash?

Finished.


error in docker-py setup command: ivalid environment marker:python_version < "3.5" when installed docker-py-1.9.0

the environment is:
python 2.7.5
requests-2.10.0
six-1.10.0
websocket_client-0.37.0
backports.ssl_match_hostname-<IP_ADDRESS>
ipaddress-1.0.17
docker 1.12.1
When I installed the docker-py-1.9.0 using "python setup.py build", it is shown below：
error in docker-py setup command: ivalid environment marker:python_version < "3.5"
Why is this error message, how to fix it? Thanks.

I think this is a problem for docker-py
You can probably fix it by updating your version of setuptools


feat: support custom coralogix subsystem name

pass as CORALOGIX_SUBSYSTEM in environment

:tada: This PR is included in version 1.3.0 :tada:
The release is available on:

v1.3.0
v1.3.0
GitHub release

Your semantic-release bot :package::rocket:


always add current poisition as the first point in trajectory points

hi, currently, joint trajectoy action server behavios
if points is 1, add current position to the first point in trajectory points
others, assuming that user set current position to the first point in trajectory points
Is there any reason to do this? why not always put first point in trajectory points ?
c.f https://github.com/RethinkRobotics/baxter_interface/pull/55, https://github.com/RethinkRobotics/baxter_interface/pull/55

Yep. This change makes sense. I considered this behavior in the past as well, but never followed through. I'd be willing to merge if you retarget at the development branch.

ok, rebased

@IanTheEngineer

Yep. This change makes sense. I considered this behavior in the past as well, but never followed through. I'd be willing to merge if you retarget at the development branch.

sorry, I missed this commend. Created new pull request -> https://github.com/RethinkRobotics/baxter_interface/pull/74


Steering

This does not include all original changes of the steering branch, but I don't want to delay the merge any longer.

Merging in changes, custom steering works


Adding a deprecation note to readme

@shoyer should we do this, or something along these lines, before the paper is published?

Merged in as 5e800506c36927bf8af9ab4f56e63f667a701ae1


Shared round robin scheduling

So far, every c-api process maintained its own round robin sequence  for c-bak service.
This patch attempts to create a common round robin sequence
that is shared between multiple c-api processes in multiple nodes.
Closes-Bug: #JBS-78

Just a suggestion, could we not just query for cinderdb for services table for binary cinder-backup and route the requests to them in a RR fashion? Something simpler and similar to volume scheduler?

not merging it


Command description buffering

In android 11  after search command description is not loading it keep on buffering please help me thanks in advance
Please find the attached pic

Hey is this the latest version? Please update to the latest version from github releases. Fdroid and Playstore releases will come soon.

If I install offline apk version v8a from GitHub the problem is there.

If I install offline apk version v8a from GitHub the problem is there.

You need to install this https://github.com/Techno-Disaster/tldr-flutter/releases/tag/v2.2.0 apk. have internet on the first time you open the app. After that it will work even in offline mode

Thank you it is working


chore(deps): bump https://github.com/jenkins-x/jx-cli to 3.0.162

Update jenkins-x/jx-cli to 3.0.162
Command run was ./promote/main

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by:
To complete the pull request process, please assign daveconde
You can assign the PR to them by writing /assign @daveconde in a comment when ready.
The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment


Remove final keyword in an arrow file to attempt to generate an ARROW…

… label

Closing this PR as it's no longer needed as the labels have been merged in upstream.


Capability with Neovim

Vim-pasta doesn't seem to be working with Neovim. I set verbose=1 and no errors were shown. Have you had any success getting vim-pasta to work with Neovim?

Maybe it has to do with Neovim issue 2048?

I am also facing issues with neovim and vim-pasta compatibility.

Has it fixed?

I don't use neovim and I have no idea what's wrong here :/

@kepbod , I use neovim 0.1.5, and it works fine for me.

Seems to work fine now. I am using nvim-v0.1.7.

Doesn't work for some reason, neovim 0.1.7.
Just aligns by the left edge.

I am also having neovim issues with neovim 0.2.2


MarkdownNoteView edits are not entering in the .md file ?

I just created a couple pages of content using the MarkdownNoteView window.   When I look at the source file (.md) for the View window, it is not updating.
I did not do any editing in the .md file.
I did save the .md file once.  I think I clicked in the window and used Ctrl-S.  But I might have used File->Save.
Is this a bug ?
Is there a way to force the View window to write to the .md file ?
Idea: is it possible to hide the .md file while editing in the View window ?  It would be less confusing and more intuitive not to see the source .md file.  You could then toggle back and forth between seeing the View and seeing the raw .md file ?
Edit: just had it happen again.  It has something to do with saving the .md file.
BTW: I LOVE having cells in a MD document.

@linuxguy123
Thanks for your feedback, I've just read your comments, and want to reply so far.
I will investigate these issues today, and reply later.

Idea: is it possible to hide the .md file while editing in the View window ? It would be less confusing and more intuitive not to see the source .md file.

Probably, you even did not take time to read
https://github.com/ken-okabe/vscode-markdown-note/blob/main/README.md
Please read it though before you propose your Idea.
https://github.com/ken-okabe/vscode-markdown-note/blob/main/README.md#-reload-to-side-or-overlay

Please read it though before you propose your Idea.
https://github.com/ken-okabe/vscode-markdown-note/blob/main/README.md#-reload-to-side-or-overlay

I understand how that works.  The problem is that when I'm editing in View, the .md file is not being updated.  I know I can edit the .md and then refresh the View. I get that.

Idea: is it possible to hide the .md file while editing in the View window ? It would be less confusing and more intuitive not to see the source .md file.

The problem is that when I'm editing in View, the .md file is not being updated

The point is in "Overlay" mode, as the word suggests, the mode is " to hide the .md file while editing in the View window".
In this mode, we never have an issue  for "when I'm editing in View, the .md file is not being updated".
In "to Side" mode, surely you can observe how the md source text is updated; however, the update is not based on every typing but every Cell update.

test
test3


Filter not working if accessorFn returns null for any row

          Fixed by #4441

Originally posted by @KevinVandy in https://github.com/TanStack/table/issues/4245#issuecomment-1312965743
Hello, even with this fix :
If the 1st value is null, globalFilter doesn't work.

I've noticed the same thing

I encountered the same issue, I've made a repro here https://codesandbox.io/p/sandbox/wispy-moon-58wym7?embed=1&file=%2Fsrc%2FmakeData.ts%3A37%2C11. if you try to filter on something in the first name column it wont filter.

I have also encountered the same thing, seems to happen for column filters and/or global filters depending on specifics. I have a hunch the issue has something to do with the "includesString" filter that seems to be the default if no other filter is specified. My steps to repro:

Take the standard "React Filters" example.
Replace the "makedata" import with a simple static definition for "Person" with a nullable lastName, and make the first entry for the Data be someone who has no last name:
`
type Person = {
firstName: string
lastName: null | string
age: number
visits: number
status: string
progress: number
}

const defaultData: Person[] = [
{
firstName: 'madonna',
lastName: null,
age: 65,
visits: 1000,
status: 'In Relationship',
progress: 60,
},
{
firstName: 'tanner',
lastName: 'linsley',
age: 24,
visits: 100,
status: 'In Relationship',
progress: 50,
},
{
firstName: 'tandy',
lastName: 'miller',
age: 40,
visits: 40,
status: 'Single',
progress: 80,
},
{
firstName: 'joe',
lastName: 'dirte',
age: 45,
visits: 20,
status: 'Complicated',
progress: 10,
},
]
`
3. remove the computed "fullName" column to avoid false positives.
4. replace setData call with this defaultData.
5. remove all references to the "fuzzyFilter" defined in the React Filters example (so all filtering will use the default "includesString" filter)
With no filtering:

Partial match filtering on first name works as expected:

Partial match filtering on last name fails:

Partial match filtering via global filter also fails, for matches that should be in the lastName column (should also return row with "linsley"):

Workaround for me is to modify my types to not allow nulls in any columns, and use empty string in such cases. That works fine for my specific case, but may not be an acceptable solution for all cases.

Well here's the root cause... table-core/src/features/Filters.ts Lines 406-441:
    column.getAutoFilterFn = () => {
      const firstRow = table.getCoreRowModel().flatRows[0]

      const value = firstRow?.getValue(column.id)

      if (typeof value === 'string') {
        return filterFns.includesString
      }

      if (typeof value === 'number') {
        return filterFns.inNumberRange
      }

      if (typeof value === 'boolean') {
        return filterFns.equals
      }

      if (value !== null && typeof value === 'object') {
        return filterFns.equals
      }

      if (Array.isArray(value)) {
        return filterFns.arrIncludes
      }

      return filterFns.weakEquals
    }
    column.getFilterFn = () => {
      return isFunction(column.columnDef.filterFn)
        ? column.columnDef.filterFn
        : column.columnDef.filterFn === 'auto'
          ? column.getAutoFilterFn()
          : // @ts-ignore
            table.options.filterFns?.[column.columnDef.filterFn as string] ??
            filterFns[column.columnDef.filterFn as BuiltInFilterFn]
    }

For any given column:

if the value in the first row happens to be null then the "auto" filter function is set to "weakEquals" for that entire column
if any subsequent rows have a non-null value then they will be compared with "weakEquals" (ie. cell "==" filter, with double-equals not triple-equals) which in the examples provided is counter-intuitive, because we are expecting "includesString" or some other type-appropriate function.
explicitly specifying a particular filter in your column definition with filterFn: 'includesString' (or one of the others) will successfully force the filter for that column to use the filter function you want... this is an alternative workaround if you need nullable values and all you want is column filtering.

However, specifying an equivalent globalFilterFn: 'includesString' in your table options STILL does not fix the global filtering in the same way, because (a) the global auto filter function is already defaulted to 'includeString' under the hood anyway, and (b)  #5138 means the default implementation of getColumnCanGlobalFilter() will still completely exclude any column if the value in the first row of the column is not a string or a number. Lines 391-398:
      getColumnCanGlobalFilter: column => {
        const value = table
          .getCoreRowModel()
          .flatRows[0]?._getAllCellsByColumnId()
          [column.id]?.getValue()

        return typeof value === 'string' || typeof value === 'number'
      }

The workaround for global filtering therefore is to override getColumnCanGlobalFilter() with your own implementation when setting the table options... the crudest example being:
getColumnCanGlobalFilter: () => true

TLDR; the table tries to do type inference by looking at the first row of data, then deciding what the "type" of each column is based only on the values in that first row, then defaulting to filtering algorithms based on the inferred type for that column. If the first value in any given column happens to be null, then the column filtering defaults to weakEquals and the column is excluded from global filtering entirely.
Not only does this result in counter-intuitive default behaviour, but it could conceivably lead to intermittent bugs ... eg. filtering could potentially work, then break, then work again, then break again, all because the first row in the underlying data is changing.
If your dataset may contain null values, your options are:

replace the nulls with some appropriate non-null value that has a string type (eg. empty string) or number type (eg. NaN)
or
be explicit about the filter function you want to use for any possibly-nullable column (eg. explicitly set filterFn: 'includesString' or whatever on the definition for that column) and if you want global filtering, also override getColumnCanGlobalFilter in the table options with some appropriate custom implementation for your case.

Related issues: #5138, #4783, #4711, #4673, #4594.


Middleware makes 2X calls to all the views!!

Big bug and a pretty frustrating one..
https://github.com/descope/django-descope/blob/main/django_descope/middleware.py#L17
All views get called 2X if using the descope middleware.

@chachra thanks for reporting, looking at this ASAP

hi @chachra, I'm afraid I'm unable to reproduce
Could you please share more information about your app?
a pip freeze would be helpful
perhaps logs showing the double calls

See revised code below. If user is logged in get_response is being called twice. See commented out line below.
`class DescopeMiddleware:
_auth = DescopeAuthentication()
def __init__(self, get_response: HttpResponse = None):
    self.get_response = get_response

def __call__(self, request: HttpRequest):
    # response: HttpResponse = self.get_response(request)

    user = self._auth.authenticate(request)
    if user:
        login(request, user)

    response: HttpResponse = self.get_response(request)

    return response

`

Thanks for fixing folks! Didn't mean to scare anyone... I just lost 2 days of sleep having never seen such behavior in Django.
Sorry if I made anyone work on the weekend! Cheers.


Updated OutputState

See #171

Whoops! I didn't see this, I already sort of rebased this myself. So most of this should be in the branch, can you double check what is missing/incorrect?

Thanks for checking!


Allow selecting custom model names in openai LLM

I am using SimpleAI to host some models and would like to use langflow to chat with them. It would be good to be allowed to enter custom model names in the text box.

Hi @Nintorac, can you share their website or repo?

Oh yes, can be quite hard to find. It's here https://github.com/lhenault/simpleAI


fix: add WalletConnect deeplink choice to local storage

tl;dr we now set the WALLETCONNECT_DEEPLINK_CHOICE local storage value that WalletConnect sets in their official modal.

Seems like the WalletConnect modal removes this property on disconnect, do you think we should do that as well?

@nickbytes Ah, good catch, I'll have a look into it.

@nickbytes I've updated the PR to clear the local storage data when disconnected. Let me know what you think.


Add function name to instrucmentation template functions.

Also add arguments to report_call function in instrumentation template.

I signed it!

Making this change internally; closing this pull request.
Sorry for the noise.


remote_theme for hosting on github.

Hi Tian Qi,
For hosting the site on github, its actually better to use remote_theme: kitian616/jekyll-text-theme in _config.yml. I wrote some notes here using jekyll and your theme. Btw, thanks for open source your theme. Really like it.

This proposal is very good，Does it work?

Yes, tried on both my Mac and github. Works fine.

@turing4ever thx for the issue, I didn't know much about remote_theme before. I'll add it in the docs latter.


ESXi: Add missing commands for splunk ThreatHunting app that existed in vagrant bootstrap file

When comparing ./ESXi/ansible/roles/logger/tasks/main.yml with ./Vagrant/bootstrap.sh, there are a few critical commands that were missing including the removal all the 'rename = xmlwineventlog' directives in prop files for window and sysmon TA apps. The other item is the command for correcting hostnames in the props.conf for the threathunting app.
Without these changes, the threathunting app index wasn't getting populated and malicious actions weren't getting caught, rendering the app useless.

Thanks @sean-code , I appreciate the PR!


[GDTCORDataFuture initWithCoder:] Crash

[READ] Step 1: Are you in the right place?
0
libsystem_platform.dylib
_os_unfair_lock_recursive_abort + 36
4
CoreFoundation
+[NSException exceptionWithName:reason:userInfo:] + 68
5
osee2unifiedRelease
_xad_handle_signal(int, __siginfo*, void*) +<PHONE_NUMBER>
6
libsystem_platform.dylib
_sigtramp + 44
14
Foundation
-[NSKeyedUnarchiver decodeObjectOfClasses:forKey:] + 428
15
osee2unifiedRelease
GDTCORDataFuture.m - 第 58 行
-[GDTCORDataFuture initWithCoder:] + 58
16
Foundation
_decodeObjectBinary + 2000
19
Foundation
-[NSKeyedUnarchiver decodeObjectOfClasses:forKey:] + 428
20
osee2unifiedRelease
GDTCORStoredEvent.m - 第 75 行
-[GDTCORStoredEvent initWithCoder:] + 75
21
Foundation
_decodeObjectBinary + 2000
28
Foundation
-[NSKeyedUnarchiver decodeObjectOfClasses:forKey:] + 428
29
osee2unifiedRelease
GDTCORStorage.m - 第 294 行
__31-[GDTCORStorage initWithCoder:]_block_invoke + 294
30
libdispatch.dylib
_dispatch_client_callout + 20
31
libdispatch.dylib
_dispatch_lane_barrier_sync_invoke_and_complete + 60
32
osee2unifiedRelease
GDTCORStorage.m - 第 291 行
-[GDTCORStorage initWithCoder:] + 291
33
Foundation
_decodeObjectBinary + 2000
40
Foundation
+[NSKeyedUnarchiver unarchivedObjectOfClass:fromData:error:] + 112
41
osee2unifiedRelease
GDTCORStorage.m - 第 221 行
-[GDTCORStorage appWillForeground:] + 221
42
osee2unifiedRelease
GDTCORLifecycle.m - 第 93 行
-[GDTCORLifecycle applicationWillEnterForeground:] + 93
43
Foundation
__57-[NSNotificationCenter addObserver:selector:name:object:]_block_invoke_2 + 28
50
Foundation
-[NSNotificationCenter postNotificationName:object:userInfo:] + 72
51
osee2unifiedRelease
GDTCORPlatform.m - 第 176 行
-[GDTCORApplication iOSApplicationWillEnterForeground:] + 176
52
Foundation
__57-[NSNotificationCenter addObserver:selector:name:object:]_block_invoke_2 + 28
81
UIKitCore
UIApplicationMain + 216
82
osee2unifiedRelease
main.m - 第 13 行
main + 13
83
libdyld.dylib
start + 4

[REQUIRED] Step 2: Describe your environment

Xcode version: 11.1
Firebase SDK version: 6.13.0
Firebase Component: Crashlytics 3.14.0  Fabric 1.10.2 GoogleDataTransport 3.1.0 GoogleDataTransportCCTSupport 1.2.1

Hi @JianweiWangs thanks for the report. I'm not able to reproduce this based on just the stack trace given (blank project, backgrounding the app, pulling it back up, each GDTCORStoredEvent unarchives successfully (Xcode 11.1, iOS 13 simulator).
A few questions before we can move forward with this:

Do you have more information about the exception (like the text of the exception, saying why it threw)?
Have you been able to reproduce this? If so, how?
Is this happening on a specific iOS version?
Is this a one-off crash or have you seen a large number of these crashes?

The encoding here is pretty straight forward (just two URLs) so I'm curious as to why it would be throwing an exception, potentially an object of a different type is being encoded.
Thanks!

Hi @ryanwilson  thanks for your reply.
1.
已崩溃：com.google.GDTCORStorage
EXC_BREAKPOINT 0x00000001897461a4

it's only info I get.
2. I can't reproduce it, we get this crash from firebase, only  times per day, we have about 3M active users online per day.
3. Not specific iOS version, from 10 to 13
4. not one-off but few
Thanks for your help!

Thanks for getting back to me! Hmm, this is going to be a tough one to debug without other information or a repro but we can keep trying.
Two more quick questions if you don't mind - is there a specific device model this is happening on (i.e. iPhone 5S)? I want to make sure it's not a 32 vs 64 bit issue. Other thing would be (if you are able to find out) are the crashes the same device crashing over and over again or does each device typically only crash once?
Thanks!

@ryanwilson, could it be related to this line here?
AFAIK the initWithCoder: initializer should be calling super initWithCoder: and passing in the same decoder. I'm not familiar with NSCoding internals, but the _os_unfair_lock_recursive_abort in this case may indicate some bad state in the decoder as a result of it not being passed to super.

@morganchen12 since the superclass in this case is NSObject, and NSObject doesn't conform to NSCoding so it shouldn't call super initWithCoder: as far as I'm aware.


fix: in app notification text cut off

This PR resolves PHIRE-848
Description

Fixes text being cut off in certain in app notifications due to a bad width calculation for the text field.

Before

After

PR Checklist

[ ] I have tested my changes on iOS and Android.
[x] I hid my changes behind a feature flag, or they don't need one.
[x] I have included screenshots or videos, or I have not changed the UI.
[x] I have added tests, or my changes don't require any.
[x] I added an app state migration, or my changes do not require one.
[x] I have documented any follow-up work that this PR will require, or it does not require any.
[x] I have added a changelog entry below, or my changes do not require one.

To the reviewers 👀

[ ] I would like at least one of the reviewers to run this PR on the simulator or device.

Changelog updates
Changelog updates

Cross-platform user-facing changes

iOS user-facing changes

fix in app notification text cut off - Brian

Android user-facing changes

Dev changes

Need help with something? Have a look at our docs, or get in touch with us.

This PR contains the following changes:

iOS user-facing changes (fix in app notification text cut off - Brian)

  Generated by :no_entry_sign: dangerJS against 41f5b4b3c962f4e6fb9306858e01b6f178285307


Problems with loading packages

I am trying to install the 'forecast' package, however there are a few dependencies.
Amongsth the dependencies are the packages 'Rcpp' and 'ggplot2' which seems to be working fine in newer versions of R.
As it stands I have tried installing previous versions of the packages, only available as .tar.gz files and trying to implement a newer version of R.
Following your guide with a zip file of the Rcpp package we get the following error:
Unhandled exception from user code: "Error: package or namespace load failed for 'Rcpp'
Do you have any suggestions for implementing these kinds of packages, or do you intend to update the version of R in the near future.
Thank you for your help.
Regards Stig

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

ID: 4c16c92b-449e-a614-b392-eae90e6972ae
Version Independent ID: 67afebf9-3735-8c86-d8db-87c050fa51d2
Content: Extend U-SQL scripts with R in Azure Data Lake Analytics
Content Source: articles/data-lake-analytics/data-lake-analytics-u-sql-r-extensions.md
Service: data-lake-analytics
GitHub Login: @saveenr
Microsoft Alias: saveenr

@StigSH
Thanks for the feedback! We are currently investigating and will update you shortly.

@StigSH Thanks for the feedback! I have assigned the issue to the content author to evaluate and update as appropriate.

Since we launched the preview of the R features, based on customer feedback we are prioritizing other areas and no plans exist to address any issues with the R integration.


fixes #590: change isCompoundSelector to not match prop selector

Thanks for this @joeduncan, all the extra tests are awesome. Since all of our existing tests look good as well, this LGTM.
I'd like to keep this open for review since I'm not 100% with regexes, so maybe someone like @ljharb can take a look as well.

Is there anything I can do here?

@joeduncan Thanks for your contribution! When you have a moment, will you please rebase this onto the latest master branch?

Rebased and ready for merge.


Trying to pass argument to job queue

I'm using the following example with a simple modification:
import Queue
import time
import threading
import schedule

def job(msg):
    print(msg)

def worker_main():
    while 1:
        job_func = jobqueue.get()
        job_func()
        jobqueue.task_done()

jobqueue = Queue.Queue()

msg = 'I'm working'

schedule.every(10).seconds.do(jobqueue.put, job, msg)

worker_thread = threading.Thread(target=worker_main)
worker_thread.start()

while 1:
    schedule.run_pending()
    time.sleep(1)

But it always returns a TypeError: job() missing 1 required positional argument: 'msg', can you point me on what i'm missing?

I get the same issue when the function has multiple arguments.

I have a related question: what if I want to pass a list as argument and schedule a job for each item in the list?
My attempt:
import queue
import time
import threading
import schedule

def job(name):
    print(name)

def worker_main():
    while 1:
        (job_func,job_msg) = jobqueue.get()
        job_func(job_msg)
        jobqueue.task_done()

name = ['jane', 'alice', 'mary']
jobqueue = queue.Queue()

schedule.every(2).seconds.do(jobqueue.put, (job, name))

worker_thread = threading.Thread(target=worker_main)
worker_thread.start()

while 1:
    schedule.run_pending()
    time.sleep(1)

Unfortunately, this approach run 1 job for all items in the list all together.
If this is not the best way to do this, feel free to point me towards an alternative solution.
Thank you.


azure blob storage ContainerClient exists() sdk authentication issue with sas token

Package Name: azure.storage.blob
Package Version: 12.8.1
Operating System: ubuntu 20.04
Python Version: 3.8.5

Describe the bug
ContainerClient.exists() does not include sas token in authentication header
To Reproduce
Steps to reproduce the behavior:

create ContainerClient object using sas key.
call exist method
http athentication failure returned.
Expected behavior
return true if container exists

Thanks for opening this issue, we'll investigate as soon as possible.

Thanks for opening this issue, we'll investigate as soon as possible.

Thanks, if a quick demo on problem is helpful, please feel free to ping falyu on teams

@fanzhe98 Since you are checking for existence of a container, you would need an account SAS. Once you confirm that you used account SAS, we will reach out to you in teams. @xiafu-msft fyi

Thanks!  I constructed the ContainerClient via a Container SAS. Then, is there a way to check whether a container SAS input matches to a existed container?

Hi @fanzhe98, unfortunately you do require an account SAS to make a call to container.exists(). The exists() method calls get_properties() under the hood and therefore requires at least an account SAS.
Let us know if you have any further questions, otherwise I can go ahead and close this issue.