[Bug] Galera is failing to recover after all instances shutdown

Documentation

[x] I acknowledge that I have read the relevant documentation.

Describe the bug
I've been testing an operator with basic Galera setup for past couple of weeks. Now I've entered pessimistic case scenarios where my network can change or k8s cluster goes down and started to getting some problems. Currently I'm testing it locally with Microk8s.
So let's start with basics. I tried following command to simulate a Galera cluster recovery:
kubectl delete pods -l app.kubernetes.io/instance=mariadb-galera

This works fine for me, I didn't face any issues with recovery process. But in cases where I delete MariaDB config, shutdown k8s cluster or apply some changes on network it forces my mariadb pods to restart and seems that it's randomly whether cluster recovers fully, partially or enters infinite loop of pod restarts with the status of CrashLoopBackOff.
Let's stick with this basic Galera setup:
apiVersion: k8s.mariadb.com/v1alpha1
kind: MariaDB
metadata:
  name: mariadb-galera
spec:
  rootPasswordSecretKeyRef:
    name: mariadb
    key: root-password

  storage:
    size: 1Gi

  replicas: 3

  galera:
    enabled: true
    primary:
      podIndex: 0
      automaticFailover: true
    sst: mariabackup
    recovery:
      enabled: true
      minClusterSize: 30%
      clusterMonitorInterval: 10s
      clusterHealthyTimeout: 1m
      clusterBootstrapTimeout: 10m
      podRecoveryTimeout: 5m
      podSyncTimeout: 5m

  service:
    type: LoadBalancer
    metadata:
      annotations:
        metallb.universe.tf/loadBalancerIPs: <IP_ADDRESS>

  primaryService:
    type: LoadBalancer
    metadata:
      annotations:
        metallb.universe.tf/loadBalancerIPs: <IP_ADDRESS>

  secondaryService:
    type: LoadBalancer
    metadata:
      annotations:
        metallb.universe.tf/loadBalancerIPs: <IP_ADDRESS>

  resources:
    requests:
      cpu: 256m
      memory: 256Mi
    limits:
      memory: 1Gi

  metrics:
    enabled: true

Expected behaviour

After k8s cluster/worker node shutdown, network change or reapplication of configuration the mariadb instances shall reconnect into Galera cluster, recover it's stored data and become available for other apps.
Steps to reproduce the bug

Apply manifests from examples/manifests/config
Apply above MariaDB kind config
Populate database with some schema and test data
Either delete and apply MariaDB config (keep PVCs created earlier), shutdown k8s cluster or apply some network changes (like a VPN client)
Some of instances or all of them will enter crash loop

Debug information
Pods:
 kubectl get pods -o wide
NAME                                                READY   STATUS             RESTARTS       AGE     IP             NODE     NOMINATED NODE   READINESS GATES
mariadb-galera-0                                    1/2     CrashLoopBackOff   5 (110s ago)   7m19s   <IP_ADDRESS>   pk-dev   <none>           <none>
mariadb-galera-1                                    1/2     CrashLoopBackOff   5 (2m5s ago)   7m19s   <IP_ADDRESS>   pk-dev   <none>           <none>
mariadb-galera-2                                    1/2     CrashLoopBackOff   5 (104s ago)   6m44s   <IP_ADDRESS>    pk-dev   <none>           <none>
mariadb-galera-init-qtwr4                           0/1     Completed          0              7m24s   <IP_ADDRESS>    pk-dev   <none>           <none>
mariadb-operator-cert-controller-5ff77bd795-g487d   1/1     Running            0              4h51m   <IP_ADDRESS>    pk-dev   <none>           <none>
mariadb-operator-dd9567c95-4c8lw                    1/1     Running            0              4h51m   <IP_ADDRESS>   pk-dev   <none>           <none>
mariadb-operator-webhook-7b79c9df99-dclcl           1/1     Running            0              4h51m   <IP_ADDRESS>   pk-dev   <none>           <none>
prometheus-operator-69cbc6f76c-ctd9q                1/1     Running            40 (8h ago)    6d7h    <IP_ADDRESS>    pk-dev   <none>           <none>

Events:
LAST SEEN   TYPE     REASON                 OBJECT                               MESSAGE
4m46s       Normal   NoPods                 poddisruptionbudget/mariadb-galera   No matching pods found
4m46s       Normal   SuccessfulCreate       statefulset/mariadb-galera           create Claim galera-mariadb-galera-0 Pod mariadb-galera-0 in StatefulSet mariadb-galera success
4m46s       Normal   SuccessfulCreate       statefulset/mariadb-galera           create Pod mariadb-galera-0 in StatefulSet mariadb-galera successful
4m46s       Normal   SuccessfulCreate       statefulset/mariadb-galera           create Claim storage-mariadb-galera-2 Pod mariadb-galera-2 in StatefulSet mariadb-galera success
4m46s       Normal   SuccessfulCreate       statefulset/mariadb-galera           create Claim storage-mariadb-galera-1 Pod mariadb-galera-1 in StatefulSet mariadb-galera success
4m46s       Normal   SuccessfulCreate       statefulset/mariadb-galera           create Claim galera-mariadb-galera-2 Pod mariadb-galera-2 in StatefulSet mariadb-galera success
4m46s       Normal   SuccessfulCreate       statefulset/mariadb-galera           create Claim galera-mariadb-galera-1 Pod mariadb-galera-1 in StatefulSet mariadb-galera success
4m46s       Normal   SuccessfulCreate       statefulset/mariadb-galera           create Pod mariadb-galera-2 in StatefulSet mariadb-galera successful
4m46s       Normal   SuccessfulCreate       statefulset/mariadb-galera           create Pod mariadb-galera-1 in StatefulSet mariadb-galera successful
3m29s       Normal   GaleraClusterHealthy   mariadb/mariadb-galera               Galera cluster is healthy
0s          Warning   CalculateExpectedPodCountFailed   poddisruptionbudget/mariadb-galera   Failed to calculate the number of expected pods: found no controllers for pod "mariadb-galera-2"
0s          Normal    SuccessfulCreate                  statefulset/mariadb-galera           create Pod mariadb-galera-0 in StatefulSet mariadb-galera successful
0s          Warning   CalculateExpectedPodCountFailed   poddisruptionbudget/mariadb-galera   Failed to calculate the number of expected pods: found no controllers for pod "mariadb-galera-2"
0s          Normal    SuccessfulCreate                  statefulset/mariadb-galera           create Pod mariadb-galera-1 in StatefulSet mariadb-galera successful
0s          Warning   CalculateExpectedPodCountFailed   poddisruptionbudget/mariadb-galera   Failed to calculate the number of expected pods: found no controllers for pod "mariadb-galera-2"
0s          Warning   CalculateExpectedPodCountFailed   poddisruptionbudget/mariadb-galera   Failed to calculate the number of expected pods: found no controllers for pod "mariadb-galera-2"
0s          Warning   CalculateExpectedPodCountFailed   poddisruptionbudget/mariadb-galera   Failed to calculate the number of expected pods: found no controllers for pod "mariadb-galera-2"
0s          Warning   CalculateExpectedPodCountFailed   poddisruptionbudget/mariadb-galera   Failed to calculate the number of expected pods: found no controllers for pod "mariadb-galera-2"
0s          Warning   CalculateExpectedPodCountFailed   poddisruptionbudget/mariadb-galera   Failed to calculate the number of expected pods: found no controllers for pod "mariadb-galera-2"
0s          Warning   CalculateExpectedPodCountFailed   poddisruptionbudget/mariadb-galera   Failed to calculate the number of expected pods: found no controllers for pod "mariadb-galera-2"
0s          Warning   CalculateExpectedPodCountFailed   poddisruptionbudget/mariadb-galera   Failed to calculate the number of expected pods: found no controllers for pod "mariadb-galera-2"
0s          Warning   CalculateExpectedPodCountFailed   poddisruptionbudget/mariadb-galera   Failed to calculate the number of expected pods: found no controllers for pod "mariadb-galera-2"
0s          Warning   CalculateExpectedPodCountFailed   poddisruptionbudget/mariadb-galera   Failed to calculate the number of expected pods: found no controllers for pod "mariadb-galera-2"
0s          Warning   CalculateExpectedPodCountFailed   poddisruptionbudget/mariadb-galera   Failed to calculate the number of expected pods: found no controllers for pod "mariadb-galera-2"
0s          Warning   CalculateExpectedPodCountFailed   poddisruptionbudget/mariadb-galera   Failed to calculate the number of expected pods: found no controllers for pod "mariadb-galera-2"
0s          Warning   CalculateExpectedPodCountFailed   poddisruptionbudget/mariadb-galera   Failed to calculate the number of expected pods: found no controllers for pod "mariadb-galera-2"
0s          Warning   CalculateExpectedPodCountFailed   poddisruptionbudget/mariadb-galera   Failed to calculate the number of expected pods: found no controllers for pod "mariadb-galera-2"
0s          Warning   CalculateExpectedPodCountFailed   poddisruptionbudget/mariadb-galera   Failed to calculate the number of expected pods: found no controllers for pod "mariadb-galera-2"
0s          Warning   CalculateExpectedPodCountFailed   poddisruptionbudget/mariadb-galera   Failed to calculate the number of expected pods: found no controllers for pod "mariadb-galera-2"
0s          Warning   CalculateExpectedPodCountFailed   poddisruptionbudget/mariadb-galera   Failed to calculate the number of expected pods: found no controllers for pod "mariadb-galera-2"
0s          Warning   CalculateExpectedPodCountFailed   poddisruptionbudget/mariadb-galera   Failed to calculate the number of expected pods: found no controllers for pod "mariadb-galera-2"
0s          Warning   CalculateExpectedPodCountFailed   poddisruptionbudget/mariadb-galera   Failed to calculate the number of expected pods: found no controllers for pod "mariadb-galera-2"
5m15s       Normal    NoPods                            poddisruptionbudget/mariadb-galera   No matching pods found
5m15s       Normal    SuccessfulCreate                  statefulset/mariadb-galera           create Claim galera-mariadb-galera-0 Pod mariadb-galera-0 in StatefulSet mariadb-galera success
5m15s       Normal    SuccessfulCreate                  statefulset/mariadb-galera           create Pod mariadb-galera-0 in StatefulSet mariadb-galera successful
5m15s       Normal    SuccessfulCreate                  statefulset/mariadb-galera           create Claim storage-mariadb-galera-2 Pod mariadb-galera-2 in StatefulSet mariadb-galera success
5m15s       Normal    SuccessfulCreate                  statefulset/mariadb-galera           create Claim storage-mariadb-galera-1 Pod mariadb-galera-1 in StatefulSet mariadb-galera success
5m15s       Normal    SuccessfulCreate                  statefulset/mariadb-galera           create Claim galera-mariadb-galera-2 Pod mariadb-galera-2 in StatefulSet mariadb-galera success
5m15s       Normal    SuccessfulCreate                  statefulset/mariadb-galera           create Claim galera-mariadb-galera-1 Pod mariadb-galera-1 in StatefulSet mariadb-galera success
5m15s       Normal    SuccessfulCreate                  statefulset/mariadb-galera           create Pod mariadb-galera-2 in StatefulSet mariadb-galera successful
5m15s       Normal    SuccessfulCreate                  statefulset/mariadb-galera           create Pod mariadb-galera-1 in StatefulSet mariadb-galera successful
0s          Normal    SuccessfulCreate                  statefulset/mariadb-galera           create Pod mariadb-galera-2 in StatefulSet mariadb-galera successful
5m15s       Normal    GaleraClusterHealthy              mariadb/mariadb-galera               Galera cluster is healthy
5m15s       Normal    SuccessfulCreate                  statefulset/mariadb-galera           create Pod mariadb-galera-0 in StatefulSet mariadb-galera successful
5m15s       Normal    SuccessfulCreate                  statefulset/mariadb-galera           create Pod mariadb-galera-1 in StatefulSet mariadb-galera successful
5m15s       Warning   CalculateExpectedPodCountFailed   poddisruptionbudget/mariadb-galera   Failed to calculate the number of expected pods: found no controllers for pod "mariadb-galera-2"
5m15s       Normal    SuccessfulCreate                  statefulset/mariadb-galera           create Pod mariadb-galera-2 in StatefulSet mariadb-galera successful

Endpoints:
apiVersion: v1
kind: Endpoints
metadata:
  annotations:
    endpoints.kubernetes.io/last-change-trigger-time: "2024-07-01T14:15:47Z"
  creationTimestamp: "2024-07-01T14:15:12Z"
  labels:
    service.kubernetes.io/headless: ""
  name: mariadb-galera-internal
  namespace: default
  resourceVersion: "2590444"
  uid: 746f5cab-c8d7-48af-991e-4306b921f49b
subsets:
- addresses:
  - hostname: mariadb-galera-0
    ip: <IP_ADDRESS>
    nodeName: pk-dev
    targetRef:
      kind: Pod
      name: mariadb-galera-0
      namespace: default
      uid: 05d78567-eaf3-42ab-bb21-c2f67a36e5fb
  - hostname: mariadb-galera-1
    ip: <IP_ADDRESS>
    nodeName: pk-dev
    targetRef:
      kind: Pod
      name: mariadb-galera-1
      namespace: default
      uid: 00f7ec4f-20a7-468b-9311-a086b8be1c87
  - hostname: mariadb-galera-2
    ip: <IP_ADDRESS>
    nodeName: pk-dev
    targetRef:
      kind: Pod
      name: mariadb-galera-2
      namespace: default
      uid: 48a6d18b-2626-4367-8cee-c2f5fbef39b5
  ports:
  - name: sst
    port: 4444
    protocol: TCP
  - name: cluster
    port: 4567
    protocol: TCP
  - name: ist
    port: 4568
    protocol: TCP
  - name: mariadb
    port: 3306
    protocol: TCP
  - name: agent
    port: 5555
    protocol: TCP

Environment details:

Kubernetes version: [v1.29.4]
mariadb-operator version: [v0.0.28]
Install method: [helm, static manifests]
Install flavor: [custom]

Additional context

Also I have fetched content of grastate.dat from one of the failing instances:
cat /var/lib/mysql/grastate.dat
# GALERA saved state
version: 2.1
uuid:    c045a915-378c-11ef-848a-ab7c4e33bf0b
seqno:   -1
safe_to_bootstrap: 0

According to Galera docs:
https://galeracluster.com/library/documentation/crash-recovery.html
it seems that it's a "All Nodes Go Down Without a Proper Shutdown Procedure" case and operator have some problems with stable recovery in this scenario.
mariadb_galera_error.log
mariadb_galera_agent.log
mariadb_galera_init.log
mariadb_galera_operator_part.log

Hey there @PeterStuck ! Thanks a lot for the detailed information.
I'm debugging what seems to be a similar issue here, please take a look: https://github.com/mariadb-operator/mariadb-operator/issues/672#issuecomment-2210499152

changes on network

Please bear in mind that the operator needs to fetch the sequence number by making HTTP calls to the Galera agents. All the sequence numbers need to be obtained before a new cluster is bootstrapped, otherwise we might be causing data loss by bootstrapping a new cluster in a node that is not up to date.

We managed solve the problem in this related issue, we have described the steps to follow in-depth. Please let me know if this works for you: https://github.com/mariadb-operator/mariadb-operator/issues/669
TL;DR

Set podSecurityContext in MariaDB:

  podSecurityContext:
    runAsUser: 999
    runAsGroup: 999
    fsGroup: 999

If the CRI/kubelet does not change the permissions, delete the PVC from the Pods that can't be recovered.

Hi @mmontes11 thanks for taking our time on this case!
I changed security permissions like you proposed, extended podRecoveryTimeout to 5m, but it unfortunetely doesn't fix this problem.
After simple pod deletion:
kubectl delete pods -l app.kubernetes.io/instance=mariadb-galera

All my instances are stuck in same place in logs:
Defaulted container "mariadb" out of: mariadb, agent, init (init)
2024-07-08 09:43:28+00:00 [Note] [Entrypoint]: Entrypoint script for MariaDB Server 1:10.11.7+maria~ubu2204 started.
2024-07-08 09:43:29+00:00 [Note] [Entrypoint]: MariaDB upgrade information missing, assuming required
2024-07-08 09:43:29+00:00 [Note] [Entrypoint]: MariaDB upgrade (mariadb-upgrade or creating healthcheck users) required, but skipped due to $MARIADB_AUTO_UPGRADE setting
mariadbd: Can't create file '/dev/stdout.err' (errno: 13 "Permission denied")
2024-07-08  9:43:29 0 [Note] Starting MariaDB 10.11.7-MariaDB-1:10.11.7+maria~ubu2204-log source revision 87e13722a95af5d9378d990caf48cb6874439347 as process 1
2024-07-08  9:43:29 0 [Note] InnoDB: Compressed tables use zlib 1.2.11
2024-07-08  9:43:29 0 [Note] InnoDB: Number of transaction pools: 1
2024-07-08  9:43:29 0 [Note] InnoDB: Using crc32 + pclmulqdq instructions
2024-07-08  9:43:29 0 [Note] mariadbd: O_TMPFILE is not supported on /tmp (disabling future attempts)
2024-07-08  9:43:29 0 [Note] InnoDB: Initializing buffer pool, total size = 128.000MiB, chunk size = 2.000MiB
2024-07-08  9:43:29 0 [Note] InnoDB: Completed initialization of buffer pool
2024-07-08  9:43:29 0 [Note] InnoDB: File system buffers for log disabled (block size=512 bytes)
2024-07-08  9:43:29 0 [Note] InnoDB: End of log at LSN=2353585
2024-07-08  9:43:29 0 [Note] InnoDB: 128 rollback segments are active.
2024-07-08  9:43:29 0 [Note] InnoDB: Setting file './ibtmp1' size to 12.000MiB. Physically writing the file full; Please wait ...
2024-07-08  9:43:29 0 [Note] InnoDB: File './ibtmp1' size is now 12.000MiB.
2024-07-08  9:43:29 0 [Note] InnoDB: log sequence number 2353585; transaction id 5362
2024-07-08  9:43:29 0 [Warning] InnoDB: Skipping buffer pool dump/restore during wsrep recovery.
2024-07-08  9:43:29 0 [Note] Plugin 'FEEDBACK' is disabled.
2024-07-08  9:43:29 0 [Note] Server socket created on IP: '<IP_ADDRESS>'.
2024-07-08  9:43:29 0 [Note] Server socket created on IP: '::'.
2024-07-08  9:43:29 0 [Note] WSREP: Recovered position: 7855ea03-3d0d-11ef-b11c-6b62aaac85b0:2608

On cluster restart case I'm getting slighty different log (recovered position part):
2024-07-08 11:16:50+00:00 [Note] [Entrypoint]: Entrypoint script for MariaDB Server 1:10.11.7+maria~ubu2204 started.
2024-07-08 11:16:51+00:00 [Note] [Entrypoint]: MariaDB upgrade information missing, assuming required
2024-07-08 11:16:51+00:00 [Note] [Entrypoint]: MariaDB upgrade (mariadb-upgrade or creating healthcheck users) required, but skipped due to $MARIADB_AUTO_UPGRADE setting
mariadbd: Can't create file '/dev/stdout.err' (errno: 13 "Permission denied")
2024-07-08 11:16:51 0 [Note] Starting MariaDB 10.11.7-MariaDB-1:10.11.7+maria~ubu2204-log source revision 87e13722a95af5d9378d990caf48cb6874439347 as process 1
2024-07-08 11:16:51 0 [Note] InnoDB: Compressed tables use zlib 1.2.11
2024-07-08 11:16:51 0 [Note] InnoDB: Number of transaction pools: 1
2024-07-08 11:16:51 0 [Note] InnoDB: Using crc32 + pclmulqdq instructions
2024-07-08 11:16:51 0 [Note] mariadbd: O_TMPFILE is not supported on /tmp (disabling future attempts)
2024-07-08 11:16:51 0 [Note] InnoDB: Initializing buffer pool, total size = 128.000MiB, chunk size = 2.000MiB
2024-07-08 11:16:51 0 [Note] InnoDB: Completed initialization of buffer pool
2024-07-08 11:16:51 0 [Note] InnoDB: File system buffers for log disabled (block size=512 bytes)
2024-07-08 11:16:51 0 [Note] InnoDB: End of log at LSN=2483216
2024-07-08 11:16:51 0 [Note] InnoDB: 128 rollback segments are active.
2024-07-08 11:16:51 0 [Note] InnoDB: Setting file './ibtmp1' size to 12.000MiB. Physically writing the file full; Please wait ...
2024-07-08 11:16:51 0 [Note] InnoDB: File './ibtmp1' size is now 12.000MiB.
2024-07-08 11:16:51 0 [Note] InnoDB: log sequence number 2483216; transaction id 5384
2024-07-08 11:16:51 0 [Warning] InnoDB: Skipping buffer pool dump/restore during wsrep recovery.
2024-07-08 11:16:51 0 [Note] Plugin 'FEEDBACK' is disabled.
2024-07-08 11:16:51 0 [Note] Server socket created on IP: '<IP_ADDRESS>'.
2024-07-08 11:16:51 0 [Note] Server socket created on IP: '::'.
2024-07-08 11:16:51 0 [Note] WSREP: Recovered position: 00000000-0000-0000-0000-000000000000:0

There are no error logs in agent and init containers. Seems that the recovery feature works but it's not stable based on my observation. To further analyze this let's sync mariadb config:
# https://github.com/mariadb-operator/mariadb-operator/blob/main/docs/API_REFERENCE.md
apiVersion: k8s.mariadb.com/v1alpha1
kind: MariaDB
metadata:
  name: mariadb-galera
  namespace: ovoo-rvms
spec:
  rootPasswordSecretKeyRef:
    name: mariadb
    key: root-password
    generate: true

  image: mariadb:10.11.7
  imagePullPolicy: IfNotPresent

  replicas: 3 # always an odd number of nodes

  galera:
    enabled: true
    primary:
      podIndex: 0
      automaticFailover: true
    replicaThreads: 1
    agent:
      image: ghcr.io/mariadb-operator/mariadb-operator:v0.0.28 # refer to appVersion in Chart.yaml for mariadb-operator
      port: 5555
      kubernetesAuth:
        enabled: true
      gracefulShutdownTimeout: 1s
    recovery:
      enabled: true
      minClusterSize: 50%
      clusterMonitorInterval: 10s
      clusterHealthyTimeout: 30s
      clusterBootstrapTimeout: 10m
      podRecoveryTimeout: 5m
      podSyncTimeout: 5m
    config:
      reuseStorageVolume: false
      volumeClaimTemplate:
        resources:
          requests:
            storage: 1Gi
        accessModes:
          - ReadWriteOnce

  port: 3306

  storage:
    size: 1Gi
    storageClassName: microk8s-hostpath
    resizeInUseVolumes: true
    waitForVolumeResize: true
    volumeClaimTemplate:
      accessModes:
        - ReadWriteOnce
      resources:
        requests:
          storage: 1Gi
      storageClassName: microk8s-hostpath
      volumeMode: Filesystem

  myCnf: |
    [mariadb]
    bind-address=*
    default_storage_engine=InnoDB
    binlog_format=row
    innodb_autoinc_lock_mode=2
    max_allowed_packet=256M

    general_log = 1
    #general_log_file = /var/log/mysql/mysql.log
    general_log_file = /dev/stdout

    #log_error = /var/log/mysql/error.log
    log_error = /dev/stdout

  resources:
    requests:
      cpu: 64m
      memory: 128M
    limits:
      cpu: 256m
      memory: 1Gi

  env:
    - name: MARIADB_ROOT_PASSWORD
      valueFrom:
        secretKeyRef:
          name: mariadb
          key: root-password

  podSecurityContext:
#    runAsUser: 0
    runAsUser: 999
    runAsGroup: 999
    fsGroup: 999

#  securityContext:
#    allowPrivilegeEscalation: false

  livenessProbe:
    exec:
      command:
        - bash
        - -c
        - mysql -u root -p"${MARIADB_ROOT_PASSWORD}" -e "SELECT 1;"
    initialDelaySeconds: 20
    periodSeconds: 5
    timeoutSeconds: 5

  readinessProbe:
    exec:
      command:
        - bash
        - -c
        - mysql -u root -p"${MARIADB_ROOT_PASSWORD}" -e "SELECT 1;"
    initialDelaySeconds: 20
    periodSeconds: 5
    timeoutSeconds: 5

  affinity:
    antiAffinityEnabled: false
    # todo enable conditionally
#    podAntiAffinity:
#      requiredDuringSchedulingIgnoredDuringExecution:
#        - labelSelector:
#            matchLabels:
#              app.kubernetes.io/instance: mariadb-galera
#          topologyKey: kubernetes.io/hostname

  podDisruptionBudget:
    maxUnavailable: 50%

  updateStrategy:
    type: RollingUpdate

  service:
    type: LoadBalancer
    metadata:
      annotations:
        metallb.universe.tf/loadBalancerIPs: <IP_ADDRESS>
    externalTrafficPolicy: Cluster
    sessionAffinity: None

  primaryService:
    type: LoadBalancer
    metadata:
      annotations:
        metallb.universe.tf/loadBalancerIPs: <IP_ADDRESS>

  secondaryService:
    type: LoadBalancer
    metadata:
      annotations:
        metallb.universe.tf/loadBalancerIPs: <IP_ADDRESS>

  metrics:
    enabled: true
    exporter:
      image: prom/mysqld-exporter:v0.15.1
      port: 9104
    serviceMonitor:
      jobLabel: system-monitoring-prometheus
      interval: 15s
      scrapeTimeout: 15s

Again thanks a lot for your input in this problem!

@PeterStuck Thanks again for the detailed response and the logs!

WSREP: Recovered position: 00000000-0000-0000-0000-000000000000:0

Judging by this, it seems like I've managed to reproduce a similar if not the same problem, see:

https://github.com/mariadb-operator/mariadb-operator/issues/672#issuecomment-2236251146

@mmontes11 I think if proposal in #672 will fix the issue we can close that one.

Thanks @PeterStuck ! Closing!


IPC-HDW3549HP-AS-PV  working

IPC-HDW3549HP-AS-PV  All functions seem to work well

Thank you! I've updated the readme.


Rate limit requests - OpenAI

https://platform.openai.com/settings/organization/limits
3 RPM

Using a QUERY_APPLIED_EMAIL_FILTER  which is much simpler to filter for specific emails.


⚠ Bofrost.at has degraded performance

In 739a5c0, Bofrost.at (https://www.bofrost.at) experienced degraded performance:

HTTP code: 200
Response time: 1174 ms

Resolved: Bofrost.at performance has improved in b2d4ff5 after 7 minutes.


[ci] Cut down apt-requirements

These system dependencies don't seem to be required any more.

I see that we have a cmake rule here.
I am not sure if this uses the system's cmake or not.
Our documentation recommends autoconf to build verilator here.
We also seem to depend on ninja in airgapped builds and in tool requirement checks and in some weird files.
I would first double-check if those files are outdated or not. If we remove the tools for apt, then we should update the doc/files.

Hmm, you're right. I was hoping CI would catch any problems but there are two reasons why it might not:

GitHub / Azure hosted runners come with some tools pre-installed (like cmake and autoconf)
Our self-hosted runners come with packages pre-installed in the container, but that container isn't updated automatically for this PR

I'm going to drop this, don't think it's worth the work.


tools/redact: remove sensitive information from member directory

Sometimes wal logs and boltdb data have sensitive data that can't be shared. This is bad for debugging since the metadata is useful for finding why a cluster has broken.
To get that metadata, etcd needs a tool that will redact keys/values/cluster info from a member directory while preserving everything else (raft indexes, etcd revisions, etc).

/cc @jpbetz

@jpbetz do you want to work on this for the next release cycle?


Menubar apps should not quit

The normal behaviour for menubar apps is to not quit until explicitly chosen from the right click menu. I keep accidentaly quitting toggl with command-Q.

Cmd+Q is the built in shutdown command I don't think it makes sense to try to block it. Many menubar apps that have menubar icons act the same way. (skype for instance)

The normal way of doing this is adding CMD-Q as a shortcut to the menu item for quit. But menubar apps doesn't have a menu on their windows. So I am assuming Toggl actually has done extra work in order to catch CMD-Q when running without a dock icon.

It should work as follows:
If dock icon is visible - cmd+Q will quit the app.
If dock icon is not visible - cmd+Q does nothing. App can be closed by selecting quit from the menubar menu

FWIW, don't agree with this (at all).
Every single one of the menubar applications I have running are quittable via Cmd-Q when focused: Dropbox, Harvest, Creative Cloud, Fantastical, CloudApp.

Oh no @Leland you did not just bring Harvest into the play! On a more serious note. I've looked into the way many of the menubar apps work. And what I've found is that when the menubar app has no window to show it works as described by the creator of the issue and does not close the app with Cmd+Q. It makes sense as with these types of apps the app is never actually in focus as there is no window to focus.
Apps that have window and menubar icon usually follow the rule that Cmd+Q will quit the whole app. With this new info, I revert the previous decision and we will not change the current shortcut logic for quitting Toggl Desktop.
Thank you for your input on this!


HIVE-25580: Increase the performance of getTableColumnStatistics and getPartitionColumnStatistics

What changes were proposed in this pull request?
Limit the query range based on the cat/db/table
Why are the changes needed?
To gain performance
Does this PR introduce any user-facing change?
No
How was this patch tested?
Added a test to run a quick check, but existing test should already cover this path

LGTM (pending tests)


Version 1.2

This will not be worked on for a while, but it is nice to have something set up.
This will close #17

[ ] Checker Function
[ ] Basic Logger
[ ] Custom Names

Features are not ready, so this will be done at a later date.


Tooltip 'before' and 'after' doesn't work when dynamically toggling RTL

Bug, feature request, or proposal:
Tooltip doesn't work on RTL with before and after when dynamically toggling the dir="rtl".
However it does work correctly when setting the dir at page load.
Also this highlighted right text in the documentation overview should be renamed to left.

What is the expected behavior?
Tooltip position should be on the left in the image above, because we are in a right-to-left layout.
What is the current behavior?
Tooltip position is still on the right, position doesn't change when dynamically toggling between LTR and RTL.
What are the steps to reproduce?
https://stackblitz.com/edit/angular-tj4iyk?file=app/tooltip-position-example.css
What is the use-case or motivation for changing an existing behavior?
Implement dynamic RTL for tooltips, because language is also changed dynamically, without needing to reload the whole page.
Which versions of Angular, Material, OS, TypeScript, browsers are affected?
"@angular/material": "^5.2.1",
Is there anything else we should know?

It actually works but I should have set the dir on an app control, but typo should still be corrected.
Maybe explain this also in the documentation on how to set the dir value:
https://material.angular.io/cdk/bidi/overview


Decomp2dbg doesn't work when using an existing BinaryNinja database

I noticed that when I try to continue with saved work, thus from a BNDB, decomp2dbg won't show the decompiler view, nor do the memory addresses reflect the proper names + offset in the assembly view. Maybe this is related to it being a PIE binary? (related to  https://github.com/mahaloz/decomp2dbg/issues/60 ?)

@owah can I assume you are doing this the same way as #60 ? Where you rebased the addresses in Binja, then started debugging?

I have created a new bndb of two executables without rebasing anything, and then it loads fine.

Alright, I'm closing this since the base cause seems to be the same as #60.


helm3; update to 1.0.0

For helm3 supported version operators; we should know that having a major version as 1 means it could process helm release as helm3 protocol.

Looks fine but didn't we have problems with 1.X before?
Worst case can we use a hardcoded version and replace it once we're ready to deploy?

I think that happened because of below line in app-operator.
https://github.com/giantswarm/app-operator/blob/c0ebff892744814fc435006bedd0b19c5433046c/integration/test/app/basic/simple_test.go#L48
but this is just an app version update and it merely lives in the test catalog so I think it's fine.

OK cool we need to use v1.0.0 for the helm 3 release. So no blocker if this helps. 👍


Cpi swap bugfix

Sorry , I don't understand the change ..is that the line you talk about ?
// use the pay date of the last coupon
payNotional = floatingLeg.Last().date();


path still baked in in Mac binary builds in make/Makevars_lib

In taking the .tar.gz from my Linux machine (I suspect this would be the case building from the Github repo on Mac too) and doing the following on one Mac
R CMD INSTALL -l /tmp/build3 --build nimble_0.6.tar.gz
to create
nimble_0.6.tgz
and then installing that on another Mac, I am getting:
NIMBLE_DIR="/private/tmp/build3/nimble"
in make/Makevars_lib
I don't think this causes issues, presumably per Duncan's point a while back about that being in an ifndef, but per Perry's point about it looking weird, I wanted to note it.
Looks like we might just need another stanza in configure.ac for NIMBLE_DIR (like for NIMBLE_INC_DIR) that sets NIMBLE_DIR to "WILL_BE_SET_IN_LOCAL_MAKEVARS" when ENABLE_LIB (i.e. enable-dylib) lib is FALSE.

done


TabMon not collecting backgrounder, vizql, services metric after upgrading Version 1.3

TabMon not collecting backgrounder, vizql server metrics after upgrading to vesion 1.3.
we recently upgraded our Tableau server to version 2018.2, due to in compatibility issues we also upgraded previous TabMon 1.2 to v 1.3, configured as per the KB document and configured service port enabled and added Tabconfiguration content in cluster part.
After starting TabMon i can see only Gateway, Postgres, Tabportsrv services metrics, other metircs like backgrounder, vizql are not avaiable.
Please help me to fix this issue, we need to check pefrom before and after the upgrade.
Attaching snapshots and log file, Please need help ASAP.
Thanks,
Naveen

TabMon.log.txt

Same thing here. I noticed that the process descriptions in task manager now says things like "run-backgrounder", so I wonder if it is due to a change in Tableau Server architecture. I'm running 2018.2. I tried changing the config file instance names to include "run-", but that didn't work.

Hi Team,
Can anyone please help us quickly.
Thanks in advance.
Thanks,
Naveen

Hi Team,
Can anyone please help us quickly.
Thanks in advance.
Thanks,
Naveen

Hi Dan,
Any update on this? Appreciate if you could look on this. Many Thanks!
Thanks,
Naveen

Hi Dan,
Great to hear this from you, Waiting for the update, Many Thanks!

Naveen

Hello @naveentalari and @ugamarkj,
I believe this issue was due to a bug in the workbook. I uploaded the fixed workbook (in a zip file) to issue #204.
Please let me know if this issue persists after using the new workbook. If it does, we will continue troubleshooting the issue. Until then, I am going to close this.
Thanks,
Dan

Hello Dan,
Thanks for the workbook, That's fixed the issue.
Now i can see all services metrics on what's going on page.
Thanks for your efforts, Much appreciated.
Thanks,
Naveen


Daden/bertsumext

Description

Related Issues

Checklist:

[ ] My code follows the code style of this project, as detailed in our contribution guidelines.
[ ] I have added tests.
[ ] I have updated the documentation accordingly.

replication of pull request 574


Render equations

Some answers generate equations to explain things. The equations look like LaTeX code. Can we render equations using mathjax or something, so that the reader doesnt have to imagine what the equation is actually trying to say?

Totally doable. I've used both in prior projects, and imo KaTeX is a lot better than MathJax (better defaults, faster engine, better output when they do differ, etc).
The main point of consideration here that any rendering engine will be a pretty massive bundle, and will balloon our load times. It would only make sense if we don't load it initially, then lazily load it at some point based on page content. Not a major hurtle, but it's not completely trivial either.
One thing that might be useful: do you have a prompt which currently cases the system to output equations as part of an answer?

Originally I saw equations as part of these prompts -

What is KL-divergence?
What is the kelly criterion and how does it relate to ai alignment?

It is not 100% guaranteed that equations show up though. You could just explicitly ask for equations to test, e.g. by using:
What is the equation for KL-divergence?

In theory the system is 100% deterministic, with the only variance we haven't quite nailed down yet coming from slightly non-deterministic order of citations (though they almost always are deterministic, it's weird). Testing it out, I see the aforementioned equations in the first question, though weirdly not in the second. Thanks for the prompts!!


Rename Curve/Curve2D/Curve3D/Gradient interpolate() to sample()

"sampling" is a more accurate term than "interpolating" for what's happening when using that function.
See https://github.com/godotengine/godot/issues/54161#issuecomment-1193189694.

We discussed this in a PR meeting. It seems slightly better, and has some user support, but we're not sure it's really going to make the API clearer, and it might annoy some users that the compat is broken here too.
But well, we can merge and see what happens. Needs a rebase.

Thanks!


Transaction building migration

https://github.com/mlabs-haskell/bot-plutus-interface is deprecated, and COOP needs to migrate to a different PAB solution.
Reproducing transaction building logic is not necessarily difficult, however, having a stable and robust test suite as we do currently have with Plutip might need more work.
Candidates:

https://github.com/geniusyield/atlas emerged as the most modern and robust solution that’s being adopted throughout the Haskell community for backend based transaction building.

Transaction metadata feature is missing https://github.com/geniusyield/atlas/issues/144
However there's a patch implementing it at https://github.com/eddiemundo/atlas/commit/5d2dafa3d207dd41a4ac5111add3c626b2471857

https://github.com/Plutonomicon/cardano-transaction-lib is a Purescript/Nodejs based tool that we can definitely leverage and has all the features we need.

Concretely, this work is about reworking the coop-pab component in the repo. Transaction building is abstracted behind the TxBuilder gRPC service https://github.com/mlabs-haskell/cardano-open-oracle-protocol/blob/main/coop-proto/tx-builder-service.proto. This means switching implementations would not in theory affect its use sites (concretely coop-publisher).

The question of BPI revival
I spent some time trying to upgrade our key dependency which is https://github.com/mlabs-haskell/bot-plutus-interface. This feels like a game of whac-a-mole and chess and it's uncertain how much effort will it require and if at all we will emerge victorious in a reasonable amount of time.
My strong suggestion is to completely remove BPI as a dependency and move to either CTL or Atlas. I'm currently leaning more towards CTL as there's the least unknowns associated with it.


Problem reading struct

I working on a project with an S71200 PLC and it has a DB with 3 words and 16 booleans.  My struct is below.  When I try to read this DB from the PLC using
   var data = (FromPLCStruct)_plc.ReadStruct(typeof(FromPLCStruct), 8);
I get an IndexOutOfRange error.
I tracked it down to here.  It appears that COTP.TSDU.Read is returning a byte array with only 12 bytes. I'm not sure what it should be sending but it is obviously supposed to be more than 12.  Is this maybe an error code or something?

 public struct FromPLCStruct     {          public ushort BkStatus1;         public ushort BkStatus2;         public ushort BkStatus3;         public bool HeartbeatOk;         public bool Spare1;         public bool Spare2;         public bool Spare3;         public bool Spare4;         public bool Spare5;         public bool Spare6;         public bool Spare7;         public bool Spare8;         public bool Spare9;         public bool Spare10;         public bool Spare11;         public bool Spare12;         public bool Spare13;         public bool Spare14;         public bool Spare15;     }

@thoj can you have a look ?

I found the problem.  The PLC programmer forgot to check the "Permit access with Get/Put..." on the PLC.  If this is an error code it should be possible to pass it right?


[top_earlgrey] Integrate pwrmgr

Integrate pwrmgr into top_earlgrey.
Various related fixes were required as part of this process.

Would you guys mind having a look at the 3 commits?
The first commit i'll break it out into its own PR, i just wanted to get some review cycles in.
The other two will probably end up as a single PR.

will try and review tomorrow
On Mon, Apr 13, 2020 at 11:34 PM tjaychen<EMAIL_ADDRESS>wrote:

Would you guys mind having a look at the 3 commits?
The first commit i'll break it out into its own PR, i just wanted to get
some review cycles in.
The other two will probably end up as a single PR.
—
You are receiving this because your review was requested.
Reply to this email directly, view it on GitHub
https://github.com/lowRISC/opentitan/pull/1954#issuecomment-613253012,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AJZQKVJP5YT5HGMNTI44Z4TRMP7XJANCNFSM4MHPLEIA
.

LGTM as well.

ah! thank you.
On Wed, Apr 15, 2020 at 2:55 PM Michael Schaffner<EMAIL_ADDRESS>wrote:

@msfschaffner approved this pull request.
LGTM
In hw/ip/pwrmgr/data/pwrmgr.hjson
https://github.com/lowRISC/opentitan/pull/1954#discussion_r409156461:

 hwaccess: "hwo",

 hwext: "true",

 desc: '''

 Controls the configurability of the CONTROL register.

 This register ensures the contents do not change once a low power hint and

 WFI has occurred.

 It unlocks whenever a low power transition has completed (transition back to the

 ACTIVE state) for any reason.

 ''',

 fields: [

   { bits: "0",

     name: "EN",

     desc: "Configuration enable.  Once set to 0, it can longer be configured to 1",

nit: it can no longer be configured to 1
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/lowRISC/opentitan/pull/1954#pullrequestreview-394162032,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAH2RSVWIZXZFSNI5FDIL7TRMYUMHANCNFSM4MHPLEIA
.

any other thoughts on this one?

From what I can follow, this makes sense. I will admit the intricacies can be hard to follow. We might have to do a cleanup pass in the future, or maybe I just need to stare at it longer.
@tjaychen is this ready to merge now?

From what I can follow, this makes sense. I will admit the intricacies can be hard to follow. We might have to do a cleanup pass in the future, or maybe I just need to stare at it longer.
@tjaychen is this ready to merge now?

sorry @sjgitty i forgot to respond. The answer is not quite because @eunchan updated the intermodule functions, and i wanted to absorb that correctly before merging.  We are almost there. I may also gate this one on #2011

i think this is ready to merge now. I'll wait until tomorrow morning to see if there are objections.

Thanks weicai, let me clarify that comment.
This one is RO to software because it's a hwext.. so all the conditions are
managed by hardware.
On Thu, Apr 23, 2020, 10:45 weicaiyang<EMAIL_ADDRESS>wrote:

@weicaiyang commented on this pull request.
In hw/ip/pwrmgr/data/pwrmgr.hjson
https://github.com/lowRISC/opentitan/pull/1954#discussion_r413998387:

@@ -70,6 +77,30 @@
regwidth: "32",
registers: [

{ name: "CTRL_CFG_REGWEN",

 swaccess: "ro",

@tjaychen https://github.com/tjaychen sorry for the late comment
Is this reg "RO" for SW? It's a bit weird for write enable register.
Is the description "Once set to 0, it can no longer be configured to 1"
true for field "EN"? HW will only set it to 0.
@cindychip https://github.com/cindychip for visibility
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/lowRISC/opentitan/pull/1954#pullrequestreview-399334493,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAH2RSTYULTADGSIYPDGP7TROB5FLANCNFSM4MHPLEIA
.

Thanks weicai, let me clarify that comment. This one is RO to software because it's a hwext.. so all the conditions are managed by hardware.

Thanks Tim for confirming.


Improve conda activate

activate becomes fast by simply parsing a text file
activate is now also able to resolve environments without name
(specifically those with prefix)

this also resolves #30

Unfortunately I was not able to find documentation on $HOME/.conda/environments.txt, so I am not sure if this works on every platform

not working on my side because my environments.txt looks like this
/home/minhduc0711/miniconda3
/home/minhduc0711/miniconda3/envs/asr
/home/minhduc0711/miniconda3/envs/dl-pytorch

However, the proposal in #30 works for me.

not working on my side because my environments.txt looks like this

Could you please specify your problems? The file on your system seems very similar to the one on my system. Note that on your setup i.e. conda activate as should be auto-completed to conda activate /home/minhduc0711/miniconda3/envs/asr which works too.
In comparison to the approach in #30 the base env is missing in my approach. However this can be fixed by adding a echo base &&, I will fix this.

The most recent change covers all cases. On my console:
$ conda activate
base                                      /home/niels/anaconda3/envs/cr36_newccosy
cr36                                      /home/niels/anaconda3/envs/i2dl_ex
cr36_newccosy                             /home/niels/.test
/home/niels/anaconda3                     i2dl_ex
/home/niels/anaconda3/envs/cr36

@nielstron yeah sorry, I thought the intended behavior was to show environment names only.
I see that you have included the idea from #30. It works perfectly as I want now, ty very much :)

@nielstron thanks for submitting this. I have a request: could you perhaps make this configurable? In my case this change will flood my terminal with all my unnamed environments, none of which I would like to complete. I appreciate the changes in speed, but this decreases usability for me. If you could make it configurable (and document this option), I would gladly merge this PR!
/Users/esc/git/dask-integration-testing/miniconda3
/Users/esc/git/dask-integration-testing/miniconda3/envs/xarray
/Users/esc/git/numba-integration-testing/miniconda3
/Users/esc/git/numba-integration-testing/miniconda3/envs/fastparquet
/Users/esc/git/texasbbq/miniconda3
/Users/esc/git/texasbbq/miniconda3/envs/pandas
/Users/esc/miniconda3
/Users/esc/miniconda3/envs/anaconda_client
/Users/esc/miniconda3/envs/dgen
/Users/esc/miniconda3/envs/ds_3.8
/Users/esc/miniconda3/envs/llvm-bld
/Users/esc/miniconda3/envs/llvm-bld/conda-bld/llvmdev_1592322593242/_build_env
/Users/esc/miniconda3/envs/llvm-bld/conda-bld/llvmdev_1592322827318/_build_env
/Users/esc/miniconda3/envs/llvm-bld/conda-bld/llvmdev_1592325320699/_build_env
/Users/esc/miniconda3/envs/llvm-bld/conda-bld/llvmdev_1592325611974/_build_env
/Users/esc/miniconda3/envs/llvm-bld/conda-bld/llvmdev_1592384015187/_build_env
/Users/esc/miniconda3/envs/llvm-bld/conda-bld/llvmdev_1592384334118/_build_env
/Users/esc/miniconda3/envs/llvm-bld/conda-bld/llvmdev_1594899909668/_build_env
/Users/esc/miniconda3/envs/llvm-bld/conda-bld/llvmdev_1594900301579/_build_env
/Users/esc/miniconda3/envs/llvm-bld/conda-bld/llvmdev_1594900458459/_build_env
/Users/esc/miniconda3/envs/llvm-bld/conda-bld/llvmlite_1592322202376/_build_env
/Users/esc/miniconda3/envs/llvm-bld/conda-bld/llvmlite_1592389300926/_build_env
/Users/esc/miniconda3/envs/nltk
/Users/esc/miniconda3/envs/numba_3.7
/Users/esc/miniconda3/envs/numba_3.8
/Users/esc/miniconda3/envs/numba_3.8_numpy_1.19
/Users/esc/miniconda3/envs/numba_datashader
/Users/esc/miniconda3/envs/numba_llvm10
/Users/esc/miniconda3/envs/numba_pandas
/Users/esc/miniconda3/envs/numba_weekly_meeting
/Users/esc/miniconda3/envs/taichi
/Users/esc/miniconda3/envs/test_n117_nb046
/Users/esc/miniconda3/envs/testenv_f0c68fd0-52b9-4532-abf3-92c961662ea4
anaconda_client
base
dgen
ds_3.8
llvm-bld
nltk
numba_3.7
numba_3.8
numba_3.8_numpy_1.19
numba_datashader
numba_llvm10
numba_pandas
numba_weekly_meeting
taichi
test_n117_nb046
testenv_f0c68fd0-52b9-4532-abf3-92c961662ea4

You could also think about using the file reading approach, but filtering the  unnamed environments, if that is possible it should become the default.

I think this is possible. I would simply include an internal variable that can be set to toggle reading the environments file. The only difference to listing conda/env are the unnamed environments and absolute paths (the latter of which are rather useless)

@nielstron that sounds good, there are several configuration options available for this completion already. Probably best to make another one along the same lines.

I tested the most recent push on my own machine but you might want to have a look at it yourself

@nielstron I tested on my machine and it works for (and is a  lot quicker). I appreciate the changes so thank you very much for your contribution!

https://github.com/esc/conda-zsh-completion/tree/v0.9 <--- new version, out now.


Graphs wont show on XTerm

Hello,
I'm using XTerm on ArchLinux with 256-colors support inside tmux.
When I open vtop with whatever theme no graph is being rendered I only get the percentages.
On XTerm

echo $TERM gives "xterm-256color"
This is not the problem with other terminal emulators though.
On Urxvt

I too am experiencing this issue.  I'm using Nodejs 8 on Ubuntu 16.04 minimal install.  Using xterm on i3.


Add option to choose a different susi server

Add custom url support similar to android app. ref issue PR. Add option to either select susi default server or custom server. If user chooses custom server, ask for Base url of the server.
Also add an option to change server in settings. In that option simply log out the user. Check screenshot in the referred PR for more details.

Fixed. Please close this Issue, thanks! @chiragw15


Find a more "automatic" way to manage references

It would be great to have a less manual way of doing this (no repeat of the link, in-order numbering)
I don't know if there is a convenient way to do it in Madoko, maybe we can abuse the bibliography support.

Thanks, but that's not really what we wanted to do. We would still like to have a reference section at the end with a list of links and number values in the text pointing to a specific reference in the list. For example.
Section1
See this [1], and that [2]
Section2
Or maybe this[3]
References
[1] http://
[2] http://
[3] http://

Then http://madoko.org/reference.html#sec-bib?

Yes that's what I was suggesting by "abusing the bibliography support". I haven't had time to try it though.

I see :-)

Actually we should probably look at the source for the Madoko reference documentation and copy it: http://madoko.org/reference.html#sec-references


⚠ Turnos 24x7 has degraded performance

In ead52e3, Turnos 24x7 (https://reservas-dev.alternativasinteligentes.com/) experienced degraded performance:

HTTP code: 200
Response time: 3162 ms

Resolved: Turnos 24x7 performance has improved in 90a419b.


UI: Explore page improvements

Improve the font-sizes and profile picture size of the owner and improve spacing for better UX.
@devyani-kaushik  to provide mocks

@devyani-kaushik Thank you for posting the mock. The placeholder profile picture("S") looks good when there is no real profile picture. Will it look good or make sense to display the real profile pictures at this size?

So on this page, our priority is the entity, which is why we have given a smaller size to the user profile. And as per the priority, it shouldn't be an issue if the image is small


Need ability to poll for all holders of an asset

Let's say I sell an asset. Some people buy it to trade it, others to buy it and hold it so that they get a kickback on the success of the project.
How do I know who is holding that asset so that I can pay them? It would be great if we could tie in the scheduled and recurring payments feature with this polling feature so that we don't have to pay them out manually.
@xeroc suggested that I post this desire here.
Thank you, kenCode

Ivan from CCEDK has asked for this features aswell

I got more people asking for this feature!

Technically we can add an index in the database for this feature, however query of that index is relatively expensive since you don't know how many records will be there. So pagination is needed, but the paginated result could be inconsistent since the records may change every block. So best to use it in debug mode (#596) only, or call it only when distribution of the asset is in a frozen stat.
By the way, some holders may put all their assets in orders and/or collateral, so additional indexes are needed.

@abitmore alternatively to limiting this to debug mode would be to add another API (similar to crypto_api, or network_node_api) that requires authentication. Then those that need that feature need to properly authenticate at the witness node and are fine to use more resources. That way, resource-hungry calls are limited to authenticated users and you could even query indices from collateral or orders.

I'm not sure if this call (to any asset) can be finished in 3 seconds (a block interval), depends on how much data need to be returned, and how powerful the hardware of API server is, and maybe network latency factor. If it need more than 3 seconds, even if you limit that only one client can do this at a time, the result may be inconsistent in some cases.

This issue was moved to bitshares/bitshares-core#107


pgoapi.exceptions.UnexpectedResponseException: Unexpected HTTP server response - needs 200 got 502

Expected Behavior
Bot continues to run, doesn't crash
Actual Behavior
Traceback (most recent call last):
  File "./pokecli.py", line 442, in <module>
    main()
  File "./pokecli.py", line 85, in main
    report_summary(bot)
  File "./pokecli.py", line 93, in report_summary
    metrics.capture_stats()
  File "/home/junaos/PokemonGo-Bot/pokemongo_bot/metrics.py", line 76, in capture_stats
    response_dict = request.call()
  File "/home/junaos/PokemonGo-Bot/pokemongo_bot/api_wrapper.py", line 100, in call
    result = self._call()
  File "/home/junaos/PokemonGo-Bot/pokemongo_bot/api_wrapper.py", line 60, in _call
    return PGoApiRequest.call(self)
  File "/home/junaos/PokemonGo-Bot/src/pgoapi/pgoapi/pgoapi.py", line 182, in call
    response = request.request(self._api_endpoint, self._req_method_list, self.get_position())
  File "/home/junaos/PokemonGo-Bot/src/pgoapi/pgoapi/rpc_api.py", line 106, in request
    response_dict = self._parse_main_response(response, subrequests)
  File "/home/junaos/PokemonGo-Bot/src/pgoapi/pgoapi/rpc_api.py", line 237, in _parse_main_response
    raise UnexpectedResponseException(error)
pgoapi.exceptions.UnexpectedResponseException: Unexpected HTTP server response - needs 200 got 502

Steps to Reproduce
Nothing in particular -- just started happening as of 23:25 UTC, is now happening frequently.
502 is bad gateway, so the servers may be overloaded; we should catch this exception and retry.
Other Information
OS: Ubuntu 14.04.4 LTS
Git Commit:  bdf2e7d9cc0b2fa5fb04bb9dc4f9f09f967cd9ea
Python Version: Python 2.7.6

Niantic is starting to change things ... getting this too, and some other like 'GET_INVENTORY']['inventory_delta']['inventory_items'] KeyError: 'inventory_delta'

Well, 502 is just an HTTP error code for Bad Gateway; I'm willing to put money on their infrastructure just being overloaded.

Either way, #2407 was submitted to catch this one and retry, using similar logic to your fixes for throttling in the refactor :)

PR fixing merged.


Consider making the SeriesId attribute Optional when storing dataset

The Series ID is a required attribute when querying a DICOM dataset. However, it seems there are a number of datasets that are missing this attribute and are failing to be stored.
I'm considering making this not a requirement at storage for the DICOMcloud and let the user enforce it they need to.

done


Release "extract resources before caching responses".

Promote previous experimental-parse-extract logic to be always enabled.
This eliminates work for cached or prefetched responses by extracting resources
from HTML strings during parsing, which happens once before the response is
cached, instead of during processing, which happens each time the response is
used for navigation.
Closes #307.

lgtm

Had to update to handle null values in multipart responses: https://github.com/youtube/spfjs/pull/335/files#diff-1448f5f6820416b51bfdbf7d29dd0df9R503
It's a corner case and technically a malformed response, but I'll follow up to handle this nicely throughout.

lgtm


[cloud_firestore] Lacking documentation on transaction handlers and return types

Regarding: cloud_firestore, Firestore.instance.runTransaction
See:
https://pub.dev/documentation/cloud_firestore/latest/cloud_firestore/Firestore/runTransaction.html
Currently, it is not clear, what the transactionHandler is supposed to return or how to access results from a transaction from the callback of runTransaction. Nor is it clear, how to recognize a failed transaction. Please improve the documentation on that part, as it is somewhat important to be able, to correctly handle bundled requests for the firebase database.

Closing as a duplicate of #1642. Please follow that issue for updates.


Fitting unresolved binaries?

Hi @hover2pi -
I am wondering whether sedkit has the capability of fitting unresolved binaries?
The application I'm thinking of is fitting for temperature inhomogeneity on
TRAPPIST-1 by modeling it as two(+) stars with different temperatures.  Is this
something sedkit might be capable of, or that could be added easily?
Thanks,
Eric Agol

Eric,
No, it can’t do that yet but Adam Burgasser has the Splat package that does exactly that! It’s at github.com/aburgasser/splat. It’s a little harder to use than sedkit (in my opinion) but has the capability you’re looking for. This is on my to do list. If you want to make a Github issue for sedkit, feel free!
But what you’re describing is basically what we did in Wakeford et al. (2018) to determine parameters for Trappist-1g. Check it out!

Joe

On Sep 15, 2020, at 12:55 PM, Eric Agol<EMAIL_ADDRESS>wrote:

Hi @hover2pihttps://github.com/hover2pi -
I am wondering whether sedkit has the capability of fitting unresolved binaries?
The application I'm thinking of is fitting for temperature inhomogeneity on
TRAPPIST-1 by modeling it as two(+) stars with different temperatures. Is this
something sedkit might be capable of, or that could be added easily?
Thanks,
Eric Agol
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://github.com/hover2pi/sedkit/issues/55, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AAAIO7YQRYIWSN27WX4OTODSF6MAHANCNFSM4RNNU6FQ.

@hover2pi  Thanks for your quick help!  I'm familiar with the Wakeford et al. (2018) paper, and I'm interested in carrying this out for all seven planets based on the data from Ducrot et al. (2020).  Take care, Eric


Assert tests

This enables the remaining trivial assert tests.
Blocked on: https://github.com/runtimeverification/k/issues/2812

Closing for the moment.


mdns cannot resolve hostname by giving IP (IDFGH-3043)

Module or chip used: ESP32-WROOM-32
IDF version: v4.2-dev-1034-ge599b794bebe
Build System: CMake
Compiler version: xtensa-esp32-elf-gcc (crosstool-NG esp-2020r1) 8.2.0
Operating System: Linux
Power Supply: USB
Test using examples/protocols/mdns.
Verify resolve host name and address by below commands on Linux:
$ avahi-resolve-host-name esp32-mdns.local
esp32-mdns.local        <IP_ADDRESS>
$ avahi-resolve-address <IP_ADDRESS>
Failed to resolve address '<IP_ADDRESS>': Timeout reached
Expected behavior: avahi-resolve-address should work.

From the wireshark, it's clear esp32 mdns does not response to below: ( by avahi-resolve-address <IP_ADDRESS> )
19      4.649283002     <IP_ADDRESS>   <IP_ADDRESS>     MDNS    86      Standard query 0x0000 PTR <IP_ADDRESS>.in-addr.arpa, "QM" question
Is this a bug?

@AxelLin
The esp mdns library doesn't support reverse lookups.
This could be implemented, if desired, preferably if more users vote for this functionality.

Hi @david-cermak
Then can I use the mdns responder from lwIP? (How to enable mdns from lwIP?)

@AxelLin
I'm not familiar with lwip mdns responder (seems to have some limitation in conflict resolution)
To get it compiled, you might need to provide some of those definitions as PUBLIC,  since they are used in public APIs in other components, too. Also adding a apps/mdns/mdns.c might be needed.
idf_component_get_property(lwip lwip COMPONENT_LIB)
target_compile_definitions(${lwip} PUBLIC -DLWIP_MDNS_RESPONDER=1 PUBLIC -DLWIP_NUM_NETIF_CLIENT_DATA=1 PRIVATE -DLWIP_NETIF_EXT_STATUS_CALLBACK=1)
target_sources(${lwip} PRIVATE "lwip/src/apps/mdns/mdns.c")

Hi @david-cermak
Follow above changes, I can include lwIP mdns to build.
However, it seems does not work well.
From wireshark log I can observe the device keep sending query but does not send response.
This is strange because exactly the same lwip mdns.c code works when I test on other platform(using different sdk but with similar lwip version).
Thanks,
Axel


Issue/3026 is defined gradual (#3035)

Pull request opened by the merge tool on behalf of #3035

Merged into branches iso4 in 08cc7ce329cd30b9c853dac6e0b5b7f6713188ce


Generate report failing to generate in some instances

Failed to generate a pdf or word report when selected all Sections for the 'Chilcotin caribou plan' area of interest
- generated a report when I selected:
- summary
- summary and forestry
- grizzly and forestry
- forestry
- didn't generate a report when I selected:
- caribou
- summary and caribou
- forestry and caribou
- forestry, grizzly, summary
- also had an error in generating ppt report when selecting summary

Getting this issue for .pdf report:
Quitting from lines 107-158 (./reports/summary.Rmd)
Quitting from lines 57-71 (./reports/summary.Rmd)
Warning: Error in : plot.data' contains value(s) < centre.y
[No stack trace available]


(PUP-10142) Add flag for global context initialization during settings configuration

The puppetserver will begin generating new settings objects during
compilations; in order to keep the code DRY, it needs to be able
to tell initialization methods whether or not to load the global
context.

CLA signed by all contributors.


Add landscape as a management tool for our server

Since in the past there's been a whole lot of issues concerning the server and administration in my absence, I've suggested to use canonical landscape for management and monitoring.
I've been in touch with the Canonical team at London, and after a quick chat they've supervised me with https://landscape.canonical.com/set-up-on-prem
On-premises will be free for up to 10 servers..
I'll add this to our infrastructure soon and will add a launchpad/management group as well, so Inexor core members can easily monitor and manage the server via the interface.

Very nice!

We are using linux-dash at stats.inexor.org


Improve JSDocs by adding examples of usages

@ivpavici
Updated:
✅ src/utils/calldata/formatter
✅ src/utils/calldata/tuple
Fixed #1090

@ivpavici I have updated it.

Hi!
We will double check and potentially merge this PR into https://github.com/starknet-io/starknet.js/pull/1221 !
cc @lukasaric

ok, merged and @lukasaric will continue in his PR if there are some changes to do

@RuneRogue sent you a small reward on OnlyDust!

@ivpavici Thank you for reward.


Django samples

@nathanielmanistaatgoogle responded to all comments but need to take another pass myself but have to run at this minute, will finish up later tonight. Will also stop importing functions across the samples though as discussed debatable whether it makes more sense to stick with Django conventions over oauth2client conventions.

@nathanielmanistaatgoogle ok ready for another pass, also cleaned up some unnecessary files. Following the style guide for imports does make sense to me, I think it's just the types in settings.py we should leave alone.
Whenever review is LGTM, besides needing to squash the review commits, I'd like to do a final pass on an actual server for both these samples before merge.

Starting a new build on Jenkins!

Build on Jenkins Started!

Build finished. No test results found.

Sorry experimenting with Jenkins job to report system tests in background.

Completed another review pass; I don't think I noticed anything beyond cosmetics.

@waprin did you have the chance to take a look at the comments?

@wasabigeek was on vacation from work and programming in general, will look back around on this tonight!

@wasabigeek @nathanielmanistaatgoogle thanks for review comments, I addressed all the issues and tested them again, ready for another pass at review pass. Prob should wait until a release before we merge though since the samples working do depend on some of the bugfixes.

I'm satisfied. Who else will be reviewing this?

I think we had an oauth2client maintainer and someone who tried the samples (thanks again @wasabigeek ) so we should be good to merge. I will also at some point take a look at the google-api-python-client and see if it makes sense to redirect here which should get us more eyes. But since the samples will have known bug fixes until the next release, maybe @jonparrott wants to merge whenever next release is cut (after we update the requirements.txt)?

@waprin the next release is cut for what? this library? What changes are needed?

@jonparrott #623 #651 #614 . Otherwise the samples are unfortunately probably too buggy to even have in the repo.

I'm going to merge this and cut a new release.

Actually, I can't release without bumping a major version which we wanted to reserve for the transport refactors.
@waprin where are these samples referenced?

@jonparrott they are only referenced here for now

@waprin then I am okay with the situation for now. Let's hold off on any external references until we can release 4.0.0.


Installation Error: vpm with curl on Virtual machine Ubuntu

Using Ubuntu 20.04 LTS here on Virtual Machine, Error pops up with Installing VPM using curl. (Maybe the architectural difference)

ARM? RISC-V? x86?

ARM? RISC-V? x86?

it is x86_64 on Ubuntu

Which curl did you run?
Try this one: curl -sSfL https://raw.githubusercontent.com/getinstachip/vpm/main/install.sh | sh

Did it work? Our request to package on Linux distros is under review. Will let you know when those alternative approaches go through.

No. Unfortunately, that didn't work well enough.


Python Tooling

[x] PDM
[x] FastAPI
[x] linting (Ruff, MyPy, iSort)
[x] testing (pytest)

What about Jinja2?

Love it. Please submit a PR.

Yolo Atlas

The greatest app on Earth!

Perhaps?

It's perfect.

Implemented by #7 pull request.


Facing an issue in auto generating debug apk from my branch

Hi Faruk ,
I  have gone through your artical on medium.
i.e. https://medium.com/android-bits/android-app-from-scratch-part-5-continuous-integration-with-travis-ci-1a6d30d22822
you have explain very nicely about CI/CD
now i am facing an issue   in   travis.yml script
i am not be able to generate debug apk in my branch / release section in github
after successful build in travis-ci
at bottom its shows warning message
BUILD SUCCESSFUL in 5m 20s
26 actionable tasks: 26 executed
The command "./gradlew assembleDebug" exited with 0.
Skipping a deployment with the releases provider because this is not a tagged commit

Below is is my .travis.yml script
can you help me out  in this
Thanks in Advance.
//------------------------------------------------------------------------------------------
language: android
jdk: oraclejdk8
#sudo: false
android:
components:
- platform-tools
- tools
- build-tools-28.0.3

- android-28

- extra-google-google_play_services
- extra-google-m2repository
- extra-android-m2repository
- addon-google_apis-google-19

before_install:

yes | sdkmanager "platforms;android-28"

script:

./gradlew assembleDebug

deploy:
provider: releases
api-key: $GITHUB_API_KEY
file: $TRAVIS_BUILD_DIR/app/build/outputs/apk/debug/app-debug.apk
skip_cleanup: true
name: dev-build-$TRAVIS_TAG
body: Automatic build of $TRAVIS_BRANCH ($TRAVIS_COMMIT) built by Travis CI on $(date +'%F %T %Z').
prerelease: true
overwrite: true
target_commitish: $TRAVIS_COMMIT
on:
branch: spike_1.3.1
tags: true

after_deploy:

rm -rf $TRAVIS_BUILD_DIR/app/build/outputs

Hi @rizwanonekosmos  tags: true means that you have to tag your commit before pushing it. If your commit is tagged deploy will start.


Resource to handle SmartScreen Filter

I used this script to turn off Smart Screen filter. I suggest we make this into a resource, or add this as a parameter to an existing resource.
I do not know if this module is the correct one for this. If not, let me know and I will submit this in the correct module.
SmartScreen Filter: FAQ
If there is a better way to accomplish this, then please let me know. 😄
        Script (New-ResourceName -Name 'EnableSmartScreenFilter')
        {
            SetScript = {
                <#
                    'Off' equals off.
                    'Prompt' equals 'Warn before running an unrecognized app, but don't require administrator approval'.
                    'RequireAdmin' equals 'Get administrator approval before running an unrecognizd app from the Internet (recommended)'
                #>
                Set-ItemProperty -Path HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Explorer -Name SmartScreenEnabled -ErrorAction Stop -Value 'RequireAdmin' -Force
            }

            TestScript = {
                $smartFilterStatus = (Get-ItemProperty -Path 'HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Explorer' -Name SmartScreenEnabled -ErrorAction SilentlyContinue).SmartScreenEnabled

                return ($smartFilterStatus -eq 'RequireAdmin')
            }

            GetScript = {
                $smartFilterStatus = (Get-ItemProperty -Path 'HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Explorer' -Name SmartScreenEnabled -ErrorAction SilentlyContinue).SmartScreenEnabled

                return @{
                    SmartFilterStatus = $smartFilterStatus
                }
            }
        }

@johlju - sounds like a good idea - and a really easy one to do if someone is looking for something easy to start with. Especially as you've provided much of the code :grin:


Split MapPools and related collections/cache into repositories

Describe your changes
This PR acts to serve as an example of how to split objects/collections into repositories.
In this example, the data was simply moved out of application memory and now only exists in the SQL database. I suspect the implementation for clans will be very similar, as clans are made up only of persistent data (clans and clan members).
The implementation of channels will be somewhat similar -- because similarly there are channels and channel members, however channel members are ephemeral.
The matches will be a bit different - in the current bancho.py model, they're entirely ephermeral data which only exists until the server reboots. They should likely be moved to redis in the long-term, but could stay in application memory and still be encapsulated in a repository. Either would be acceptable for a PR.
Splitting up players will be the trickiest bit, as I think we should divide the persistent and ephemeral pieces of a player up into separate repositories - the accounts and the sessions.
Related Issues / Projects
Checklist

[x] I've manually tested my code

Needs testing. Marking as draft for now.

Tested and working


Use webpack.config.ts instead of webpack.config.js

We can simply rename the file and use it in gulpfile.ts.

https://github.com/lunchclass/absolute/pull/498
this is right?


sendMessage -> payload.author.id error

To Reproduce Steps to reproduce the behavior:

When using the sendMessage() function
Returns...

Version details (please complete the following information):

Discordeno version: [e.g. 13.0.0-rc18]
Deno version: [e.g. 1.17.1]

Additional context Add any other context about the problem here.
I did some digging... when calling sendMessage(), a message transformer is called<EMAIL_ADDRESS>and it seems that in its 18th line is called, looking for a payload.author.id
but when console logging the payload there is neither an author property nor even a payload property.
Is it just maybe me using it with the wrong Discord permission maybe or it really isn't supposed to contain this property.
Discord permissions on the server, currently include administration and either bot/gateway intents contain: "Guilds", "GuildMessages", 'DirectMessages'

Do you have any way to replicate this behavior? For example if you can send me a mod.ts file with a createBot and such that i can simply run and test this i can debug it. Sadly i am not being able to replicate this error.

Sure!
I pushed all here: https://github.com/Disq-Code-Bot/disq-code-replic
If you prefer I may send it here directly too...

The error seems to be the discord payload doesn't have the property author, which is impossible?

or it could be discord payload is undefined/null (aka discord payload return NOTHING, instead of a proper message payload)

So you couldn't replicate the error? (just so I can know, because then probably there something I'm doing wrong somewhere)
Ok. I'm going to fork the project then, to try and debug this with some console logs or something else.
I'll send the results (or solution if I find one).

I am not able to replicate this error.
This error also seems to be very odd, since the author property of a message should always exist when using the sendMessage function.

Figured out what it is. It seems there are two issues here:

Requests made to the Rest listener by the rest.runMethod method that receive 401 errors aren't handled;
The second issue: I discovered that the secret was the issue, which already was something weird as I'm testing it by only using "1234" as a secret (that by the way, yes, they are correctly defined both in the gateway and rest). But... I still tried changing the secret and also leaving it undefined. And after looking into it, it seems that, independently of what is set as secret, the rest.runMethod method, makes its call to the Rest API with the following "discordeno_best_lib_ever" as value for the secret. I haven't looked after the origin of this, but after hard resetting this value to "1234" just before the call, this was solved.

After this, the bot worked just fine.
I added a little handler for API errors so that at least the error is handled correctly, instead of getting undefined when the payload is equal to { error: "Invalid authorization key." }. #1893
But haven't looked into the secret definition issue yet. But this is maybe a mistyping error and I think you know where this resides.

since the pr is merged can we close this? or is there still any issues/errors?


Fix: Issue #29 Remove ./src/lib from source include (doesn't exist)

Not sure why this fixes a BigInt error, but since ./src/lib doesn't exist, I removed it from the source include and now the docs can be created.

This change might solve the problem of not generating the JSdocs but it means it excludes the documentation of the entire XKPasswd-JS, which is actually worse.


fix(mangadex): do not fail chapter parsing if externalUrl is null

Looking at #25, it looks like the idea was to filter out chapters where the externalUrl is not null; however the current logic filters both when externalUrl is null and when it's a string (so essentially always I think?). Changed the logic to filter only chapters where externalUrl is a string.
A manga where chapters are filtered incorrectly is Houseki no Kuni (API call, note how externalUrl is always null).
I haven't tested this with Aidoku itself (as I do not own a iOS/macOS device), but with a custom client that uses Aidoku's sources; it seems to work properly
Checklist:

[x] Updated source's version for individual source changes
[x] Updated all sources' versions for template changes
[x] Set appropriate nsfw value
[x] Did not change id even if a source's name or language were changed
[ ] Tested the modifications by running it on the simulator or a test device

Honestly, looking at the code, it seems like you're right, but in practice these chapters aren't actually being filtered out. If you look at Houseki no Kuni in Aidoku, all the proper chapters are there. @beerpiss do you know why the code is checking if the fetched attribute is none?

Yeah, it's a bit weird to me that this works within Aidoku, because by looking at ValueRef's implementation it seems like either the check for a ValueKind::Null (inside is_none()) or for a ValueKind::String (inside as_string()) will succeed; so I'd assume ext_url is some other ValueKind here?

Honestly, looking at the code, it seems like you're right, but in practice these chapters aren't actually being filtered out. If you look at Houseki no Kuni in Aidoku, all the proper chapters are there. @beerpiss do you know why the code is checking if the fetched attribute is none?

It's been a super long time that I couldn't remember, sorry. Maybe I copied it from the Tachi extension?

@hanatsumi do you know any titles that actually come out differently with the change? I think I'm probably fine with just merging it but I'm curious if there's an actual difference

@Skittyblock On my custom client, pretty much all titles change, because as it is now chapter parsing always fails due to the is_none check. I don't really know if any titles change within Aidoku, but I believe the behaviour should stay the same.

Alright, likely an issue with Aidoku's api or aidoku-rs then.


Fix Styling

Add new styles and new UI.
Add rabbit logo (inline SVG) and make it’s face follow the cursor.
Change the rabbit color, code color, link color according to the category.
**Suggestion
I think adding colors in tips.json and change the category color with js will be better.

@OsamaJandali Sorry for not reviewing this yet, I've been having some depression this week and haven't been able to get much work done. I'm sure this is amazing work though and I will merge it as soon as I'm feeling better in a couple of days!

@OsamaJandali This is amazing, thanks for this <3

wow that's coool 😊


deno: 1.34.2 -> 1.35.0

Description of changes
Updated deno from 1.34.2 to 1.35.0
Things done

Built on platform(s)

[X] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

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

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

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

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[X] Fits CONTRIBUTING.md.

Tests:
Result for nix-build -A deno.tests:
deno 1.35.0 (release, x86_64-unknown-linux-gnu)
Test 'basic' passed
Test 'fail-read-file' failed as expected
Test 'import-json' passed
Test 'import-ts' passed
Test 'read-file' passed

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

9 packages built:

deno
python310Packages.nbdev
python310Packages.nbdev.dist
python311Packages.nbdev
python311Packages.nbdev.dist
quarto
quartoMinimal
vimPlugins.denops-vim
windmill

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

9 packages built:

deno
python310Packages.nbdev
python310Packages.nbdev.dist
python311Packages.nbdev
python311Packages.nbdev.dist
quarto
quartoMinimal
vimPlugins.denops-vim
windmill


Sirens not shown in the new app

Looks like for some reason the device for the siren is not showing up in the new app.

Which Ring device(s) do you have setup? Also, could you add a screenshot of what you are seeing in the new app?

Sorry, I’ve been away for awhile. The one I’m having problems with is the Floodlight Cam. I am attaching a screenshot of my Floodlight Cam(Driveway) and my Spot Light Cam(Porch)

This was fixed in #10.

This was fixed in #10.


Calendar service does not work

Good afternoon, I have verified that this service fails:
https://ryuanime-api.chrismichael.now.sh/api/v1/calender
It takes several days without showing the animes that come out by day of the week
I have been doing the tests from Windows in Google Chrome, in addition to testing with Postman, but it has not given any results
I hope you can review it, thank you very much in advance for your work
Regards

Right, the calendar has stopped working for a long time, I hardly noticed :D

Hello @Jeluchu ,
Sorry for the delay.
I have migrated the ryuanime api to the jkanime repositiory for a long time, so I will be giving more support to the jkanime api.
As for the calendar, I have removed it from the api for now because I need to find a way to structure the JSON format in a simple way. In the way ryuanime api had presented it, it was not the most suitable for the client side.That is why in the next few days I will be working on that part, so that you (the developer users) can use it.
I greatly appreciate your interest in using the API.
So, don't hesitate to ask me anything about the project.

Hello @Jeluchu ,
I just included the schedule method to api, and other minimal changes.
I should mention that jkanime's api only works for now using the jkanime package from npm.
Apologies for the inconvenience.


User Story AB#647091:Enable PREFast warnings as errors. [Error Type: C26429: Use not null] -Minecraft.Shared.Splits-Submodule entt

ADO

https://dev-mc.visualstudio.com/Minecraft/_workitems/edit/647091

Description / PR Commit Message

Check with PREFast, found 15 errors:
1. C:\Minecraftpe\handheld\src-external\entt_\entt\src\entt\meta\meta.hpp(970): warning C26429: Symbol 'args' is never tested for nullness, it can be marked as not_null (f.23).
2. C:\Minecraftpe\handheld\src-external\entt_\entt\src\entt\meta\factory.hpp(599): warning C26429: Symbol 'curr' is never tested for nullness, it can be marked as not_null (f.23).
3. C:\Minecraftpe\handheld\src-external\entt_\entt\src\entt\meta\factory.hpp(601): warning C26429: Symbol 'it' is never tested for nullness, it can be marked as not_null (f.23).
4. C:\Minecraftpe\handheld\src-external\entt_\entt\src\entt\meta\node.hpp(200): warning C26429: Symbol 'node' is never tested for nullness, it can be marked as not_null (f.23).
5. C:\Minecraftpe\handheld\src-external\entt_\entt\src\entt\core\any.hpp(459): warning C26429: Symbol 'data' is never tested for nullness, it can be marked as not_null (f.23).
6. C:\Minecraftpe\handheld\src-external\entt_\entt\src\entt\meta\node.hpp(141): warning C26429: Symbol 'value' is never tested for nullness, it can be marked as not_null (f.23).
7. C:\Minecraftpe\handheld\src-external\entt_\entt\src\entt\core\any.hpp(452): warning C26429: Symbol 'data' is never tested for nullness, it can be marked as not_null (f.23).
8. C:\Minecraftpe\handheld\src-external\entt_\entt\src\entt\core\any.hpp(48): warning C26429: Symbol 'instance' is never tested for nullness, it can be marked as not_null (f.23).
9. C:\Minecraftpe\handheld\src-external\entt_\entt\src\entt\core\any.hpp(46): warning C26429: Symbol 'to' is never tested for nullness, it can be marked as not_null (f.23).
10. C:\Minecraftpe\handheld\src-external\entt_\entt\src\entt\entity\storage.hpp(646): warning C26429: Symbol 'elem' is never tested for nullness, it can be marked as not_null (f.23).
11. C:\Minecraftpe\handheld\src-external\entt_\entt\src\entt\meta\meta.hpp(158): warning C26429: Symbol 'to' is never tested for nullness, it can be marked as not_null (f.23).
12. C:\Minecraftpe\handheld\src-external\entt_\entt\src\entt\meta\meta.hpp(1466): warning C26429: Symbol 'to' is never tested for nullness, it can be marked as not_null (f.23).
13. C:\Minecraftpe\handheld\src-external\entt_\entt\src\entt\entity\registry.hpp(873): warning C26429: Symbol 'cpool' is never tested for nullness, it can be marked as not_null (f.23).
14. C:\Minecraftpe\handheld\src-external\entt_\entt\src\entt\meta\node.hpp(145): warning C26429: Symbol 'value' is never tested for nullness, it can be marked as not_null (f.23).
15. C:\Minecraftpe\handheld\src-external\entt_\entt\src\entt\entity\view.hpp(315): warning C26429: Symbol 'lhs' is never tested for nullness, it can be marked as not_null (f.23).

The modifications are as following:
Use ENTT_ASSERT to test for nullness.
Guidance for Review

Synchronize with main on 2021-11-11.
Author's Checklist

[ ] Completed Automated Test Review or have Exemption (automated test policy).
[ ] Have Changelogs for Public Changes or have Exemption (changelogs policy).
[x] Set the Manual Quality Validation Required field and applicable Validation Notes in ADO item(s).
[x] Builds and Test Runs passed.
[x] Reliability runs of affected tests passed (Unit 1 time, Server 10 time, Functional 50 times).

Reviewers' Checklist

[ ] Correct target branch.
[ ] Reason/root cause understood; documented in Description / PR Commit message.
[ ] Architecturally fits accepted patterns.
[ ] Introduced no known bugs and is secure.
[ ] No hard-coded "secrets".
[ ] Follows Coding Standards (contributing.md).
[ ] Content creator impact is understood and acceptable.

Codecov Report

Merging #7 (eaba249) into master (b13713c) will not change coverage.
The diff coverage is 100.00%.

@@            Coverage Diff            @@
##            master        #7   +/-   ##
=========================================
  Coverage   100.00%   100.00%
=========================================
  Files          126       126
  Lines        17401     17421   +20
=========================================
+ Hits         17401     17421   +20

Impacted Files
Coverage Δ

src/entt/core/any.hpp
100.00% <100.00%> (ø)

src/entt/entity/registry.hpp
100.00% <100.00%> (ø)

src/entt/entity/storage.hpp
100.00% <100.00%> (ø)

src/entt/entity/view.hpp
100.00% <100.00%> (ø)

src/entt/meta/factory.hpp
100.00% <100.00%> (ø)

src/entt/meta/meta.hpp
100.00% <100.00%> (ø)

src/entt/meta/node.hpp
100.00% <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 b13713c...eaba249. Read the comment docs.

Hi @EricJia01 I was updating the repo and saw this PR.
Since we try to keep this fork in sync with the upstream repo (project that we have control over, as I'm the owner and original author), perhaps it would be better to pass these changes to the EnTT team and let us bring them to both repositories.
This would avoid seeing them diverge. As a result, it would also make it easier for us to work with them in the future.
Let me know if it makes sense to you and feel free to reach out on slack if needed. Thanks. 🙂

Hi, Michele @.***>, I’m ok with that. Thanks. 🙂
Sent from Mailhttps://go.microsoft.com/fwlink/?LinkId=550986 for Windows
From: Michele @.>
Sent: Monday, November 15, 2021 8:51 PM
To: @.>
Cc: Eric Jia (CSI Interfusion @.>; @.>
Subject: Re: [Mojang/entt] User Story AB#647091:Enable PREFast warnings as errors. [Error Type: C26429: Use not null] -Minecraft.Shared.Splits-Submodule entt (PR #7)
Hi @EricJia01https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FEricJia01&data=04|01|v-ericjia%40microsoft.com|53fac10bf3364d5b4e2f08d9a8369f93|72f988bf86f141af91ab2d7cd011db47|1|0|637725774856011644|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|3000&sdata=CQYed5EfC7pNCIw4%2Fg0S9Cff2hsqWVvThE%2Fyyqy7s10%3D&reserved=0 I was updating the repo and saw this PR.
Since we try to keep this fork in sync with the upstream repo (project that we have control over, as I'm the owner and original author), perhaps it would be better to pass these changes to the EnTT team and let us bring them to both repositories.
This would avoid seeing them diverge. As a result, it would also make it easier for us to work with them in the future.
Let me know if it makes sense to you and feel free to reach out on slack if needed. Thanks. 🙂
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FMojang%2Fentt%2Fpull%2F7%23issuecomment-968879565&data=04|01|v-ericjia%40microsoft.com|53fac10bf3364d5b4e2f08d9a8369f93|72f988bf86f141af91ab2d7cd011db47|1|0|637725774856021602|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|3000&sdata=8zOFcP9kCIKNOqcoY9sQv%2FMNrhb9nyLuniyXIA9RRRo%3D&reserved=0, or unsubscribehttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FASOJBI6ARRS6AG2XHINLZ7DUMD64PANCNFSM5HZOYD2Q&data=04|01|v-ericjia%40microsoft.com|53fac10bf3364d5b4e2f08d9a8369f93|72f988bf86f141af91ab2d7cd011db47|1|0|637725774856031557|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|3000&sdata=B%2Bjkxrt9uou7G8juQxwg4BIxY5bTVunQvPzSDh6T9%2FI%3D&reserved=0.
Triage notifications on the go with GitHub Mobile for iOShttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fapps.apple.com%2Fapp%2Fapple-store%2Fid1477376905%3Fct%3Dnotification-email%26mt%3D8%26pt%3D524675&data=04|01|v-ericjia%40microsoft.com|53fac10bf3364d5b4e2f08d9a8369f93|72f988bf86f141af91ab2d7cd011db47|1|0|637725774856031557|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|3000&sdata=GMmyKoHH2ByEGWRjo83SePA1FhCGJll0qMzD94zPbOE%3D&reserved=0 or Androidhttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fplay.google.com%2Fstore%2Fapps%2Fdetails%3Fid%3Dcom.github.android%26referrer%3Dutm_campaign%253Dnotification-email%2526utm_medium%253Demail%2526utm_source%253Dgithub&data=04|01|v-ericjia%40microsoft.com|53fac10bf3364d5b4e2f08d9a8369f93|72f988bf86f141af91ab2d7cd011db47|1|0|637725774856041514|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|3000&sdata=Xf0V2SX%2Fqxq13cRb4kfKrRPx6Vl4NE%2FSbnAxfkhCLiw%3D&reserved=0.

Per thread (https://mojangab.slack.com/archives/C027PD3D0V6/p1639435557139300) from Aaron in Slack channel signals_csi, we need close the user story and related PR.


[Outlook] (activation rules) - Update info about ItemHasRegularExpressionMatch rule

Fixes issue 370 in OfficeDev/outlook-dev-docs.

OPS Build status updates of commit d8c0c20:
:clock10: Preparing: average preparing time is 44 sec(s)

OPS Build status updates of commit d8c0c20:
:clock10: Incremental building: average incremental building time is 28 sec(s)

OPS Build status updates of commit d8c0c20:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docs/reference/manifest/rule.md
:white_check_mark:Succeeded

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


[AutoPR frontdoor/resource-manager] Updating readme.md updates that were missing from previous commit

Created to sync https://github.com/Azure/azure-rest-api-specs/pull/6899

(message created by the CI based on PR content)


CDP integration

Build and push docker images to the open-source repository on commit to the master branch.

👍

:+1:

Coverage remained the same at 7.818% when pulling 52aad3b72a362714521308a0df84508664a4a4c6 on cdp-test into fe6c162e5914bb768eabab07c402f243b008237a on master.


HAWQ-1170. Crash at cleanup_allocation_algorithm() when enable '--ena…

…ble-cassert' option

@zhangh43  @xunzhang   please help to review, thanks.

+1 LGTM

+1 LGTM

+1

Merged into master.


vendor: remove direct dependency on github.com/golang/protobuf

This module has been superseeded by google.golang.org/protobuf and shall not be used anymore.

Rebased to pick up #394 to fix the EKS workflows.


D435i: memory usage increasing constantly

Required Info

Camera Model
D435I

Firmware Version
<IP_ADDRESS>

Operating System & Version
Win 10

Platform
PC

SDK Version
2.19.0

Language
C++

Issue Description
https://github.com/IntelRealSense/librealsense/blob/master/doc/d435i.md
Processing IMU sensor data according to the above, process memory (Private Bytes) has increase about 27KB/sec.
Leave it running 36 hours, memory usage keep increased and process has died.
Strangely, I got same result by more simple code.
#include <librealsense2/rs.hpp>

int main()
{
    rs2::config cfg;
    cfg.enable_stream(RS2_STREAM_GYRO);
    cfg.enable_stream(RS2_STREAM_ACCEL);

    rs2::pipeline pipe;
    pipe.start(cfg);
    getchar();
}

This looks like a memory leak to me. Is there a suspected cause?

@terranas hello, thank you for the report.
Seem like a possible bug. We'll look into this

I am having a similar issue using the Intel D415.
Required Info |
-- | --
Camera Model | D415
Firmware Version | <IP_ADDRESS>
Operating System & Version | Ubuntu 18.04
Platform | PC
SDK Version | 2.24.0
Language | C++
Just so we are on the same page I used the code example provided by terranas and evaluated it with Valgrind.
valgrind_report.txt

I've met the same problem. Have you got any solution?

Hi all, we have also experienced similar issues running the same setup @JamesPiggott used. We have also tested on Ubuntu 16.04 which gave similar results.
Also, the valgrind report @JamesPiggott attached is similar to the one in #3433 (GitHub cannot reference the issue correctly).
Downgrading to SDK 2.17.1, a version we previously used, gives no memory leak.

This seems to be affecting us as well. Any updates? We are on 2.19.1 but are happy to update to one where it's fixed

@terranas This issue was fixed in the current SDK release. Could you please give it a try?

@terranas If we don't hear from you in 7 days, this issue will be closed.


Function to regrid from hybrid Z coordinates to fixed Z axis

Reported by Ansley B Manke on 2 Nov 2004 22:16 UTC
Use technique of ZAXREPLACE, computing regridding at each space and time as the
hybrid Z layers may depend on x, y, and t.
Migrated-From: http://dunkel.pmel.noaa.gov/trac/ferret/ticket/1061

Comment by<EMAIL_ADDRESS>on 2 Nov 2004 22:18 UTC
Function is ZAXREPLACE_ZLEV
ZAXREPLACE_ZLEV(V,THICKNESS,ZAX)
regrid V onto Z axis of ZAX based on layer thickness
V: Variable on native z axis
THICKNESS: Thickness corresponding to input Z axis layers in units of
output Z axis
ZAX: Variable with desired z (depth) axis


Changed 'tmp_name' to 'name'

Coverage remained the same at 89.88% when pulling ef005420c4b5726b45015e786811980c6c4ddb69 on damianoporta:master into d780446e33c085eb526493a1d831393c4c575c33 on davidyell:master.

Duplicates #71


Improvements to EOG iteration and more applications

Multiple (future) passes or analyses compute a fix-point by traversing the EOG and performing some operations. We do not want to implement the same strategy multiple times, so I tried to generalize the EOG iteration and the respective transformation of a state.
This PR...

[x] adds a (basic) implementation of the "worklist" fix-point iteration and provides generic interface for lattices and the program state.
[x] changes the ControlFlowSensitiveDFGPass to make use of this algorithm
[x] handles InitializerListExpression (closes #1141 but turned out to be a bug in the frontend)
[x] adds a new node abstracting all kinds of nodes which have a conditional execution of paths (BranchingNode) as discussed in (#1066). It has the field branchingDecision which is the condition or similar. The following nodes implement this interface:

IfStatement
WhileStatement
ForStatement
ForEachStatement
SwitchStatement
CatchClause (even if it is incorrectly handled in the EOGPass)
ConditionalExpression (see #1142 )
ShortCircuitOperator which extends BinaryOperator. This one has to be adapted for each language (i.e., the language frontend has to decide if a binary op is a normal BinaryOperator or a ShortCircuitOperator. There's already a configuration in the Language class).

[x] adds the fields nextCDGEdges and prevCDGEdges to the class Node. These hold the control dependence graph.
[x] implements the new (optional?) pass ControlDependenceGraphPass which adds the CDG edges for each function (intraprocedurally).
[x] Propagates the Unreachable properties of EOG edges (Closes #1067)

There seem to be some issues with identifying loops in the EOG for the ControlFlowSensitiveDFGPass.

@peckto Could you test if there are performance issues with the new and redesigned passes which haven't been there before?


[AutoPR storage/resource-manager] Azure Storage 2018-02-01

Created to sync https://github.com/Azure/azure-rest-api-specs/pull/2937

(message created by the CI based on PR content)

This PR has been merged into https://github.com/Azure/azure-sdk-for-python/pull/2471


Update Dependencies #6

:clipboard: slack audit #6
We should update the dependencies listed from the Audit see

[ ] update frontend dependencies
[ ] update rust dependencies

for time dependency, we don't need to fix it. In summary, time package is only used by chrono in our dependency tree. And chrono does not use the vulnerable part of the time crate. https://github.com/chronotope/chrono/issues/602#issuecomment-1224908456

As mentioned on the Dev Sync, frontend dependencies with vulnerabilities (got and git-clone) are devDependencies, which are not included in the production bundle. I also notified Quasar devs about these vulnerabilities and they promised to fix/update those

The remaining unticked dependencies above, are not security issues, but rather warnings about unmaintained dependencies. Thus, they are not blockers for the audit. It is sufficient to have an issue for them to keep track.
These are indirect dependencies, and there are opened issues for replacing these unmaintained ones with alternatives. When the parent dependencies of these indirect ones, replace these unmaintained ones, we can upgrade our dependencies as well, and these minor warnings will be resolved then.
Again, since these are NOT security issues, it's not mandatory but a good to have to replace them when the appropriate time comes.