[Bug] Saving unchanged cluster leads to update status and cluster changes

Setup

Rancher version:
2.6.6 and 2.6.7 backend pointing at latest UI for dev.

Describe the bug

Saving unchanged cluster leads to update status and cluster changes.
To Reproduce

Create a cluster.
Wait for cluster to go to active.
Go to edit the cluster.
Switch to yaml (I think this is actually optional).
Hit save.

Result
Fields are added and the cluster goes into updating.
Expected Result

The cluster should remain unchanged and should not go into updating.
Additional context
<!--Add any other context about the problem here. -->
The diff between cluster before save and after save:
<  generation: 27
---
>  generation: 28
25c25
<  resourceVersion: "114966"
---
>  resourceVersion: "116054"
28c28,29
<  agentImageOverride: ""
---
>  agentEnvVars: []
>  agentImageOverride: null
30,32c31,36
<  description: ""
<  desiredAgentImage: ""
<  desiredAuthImage: ""
---
>  clusterTemplateRevisionName: null
>  defaultClusterRoleForProjectMembers: null
>  defaultPodSecurityPolicyTemplateName: null
>  description: null
>  desiredAgentImage: null
>  desiredAuthImage: null
50c54,57
<    nodelocal: {}
---
>    linearAutoscalerParams: {}
>    nodelocal:
>     updateStrategy: {}
>    updateStrategy: {}
98c105,113
<  scheduledClusterScan: {}
---
>  scheduledClusterScan:
>   enabled: false
>   scanConfig:
>    cisScanConfig:
>     overrideBenchmarkVersion: rke-cis-1.5
>     profile: permissive
>   scheduleConfig:
>    cronSchedule: 0 0 * * *
>    retention: 24

Potentially a blocker, adding label to discuss.

Just reproduced it. Also noticed the same thing happens if I save the cluster from the edit config form without switching to YAML.

@rmweir When I go to edit a cluster, click Edit as YAML, and click Show Diff, I see these changes to hostNamePrefix:

I don't know why that's being added. Should the UI not add that change at all, or should it wait to apply that change until after the user has changed something?

Gathered a little more information:

The code that adds the node pool prefix was added by Vince in March 2021/Rancher v2.5.16 https://github.com/rancher/dashboard/commit/75ec34c756192b70733a713ef6e82e06763be04a#diff-7d87fdaaff449429c3eb17683445ad23033fb135e86941814b8f4aaa43b94326R301
The code that adds the default values for the authorized cluster endpoint was added by Vince in May 2021/Rancher v2.6.5) https://github.com/rancher/dashboard/commit/6de4934e3f37e27f649f6bcc0ce2aac5bde26b9e#diff-f32dce3947d86b7c96a1cc70b768e414984a5025d2410c2094a213bbf5ae9b2cR27
The code that sets ignoreErrors to false was added by Vince in May 2020/Rancher v2.6.5 https://github.com/rancher/dashboard/commit/afdc49d1d65894c20a46f23337d8263b4a45dc22#diff-a14eebe4bb7d477d4e4239e9004d2dd737fd44468f337129c232f54f4bfa732dR13

Taking blocker off but leaving as a priority/0. This has been around for a few versions so alas, it's not a true regression but it's still weird.

@rmweir What's the Rancher version where you remember it working properly?

@catherineluse I don't know which rancher version worked properly. I just know it's in 2.6.6+ at least.

Here's the behavior in 2.6.5:

@catherineluse indicated that backend couldn't repro this consistently though they do see some issue. They've pushed their corresponding issue to 2.7.1, so we'll do the same.

This is also the source of https://github.com/rancher/rancher/issues/39020 & https://github.com/rancher/rancher/issues/39023. On update for k3s clusters, the following fields are populated under machineGlobalConfig if empty:
   "disable-cloud-controller": false,
   "disable-etcd": false,
   "disable-network-policy": false,
   "docker": false,
   "secrets-encryption": false,
   "selinux": false,

This is then rendered down to the /etc/rancher/k3s/config.yaml.d/50-rancher.yaml file; rancher has to restart k3s after this file is changed (rke2 and it's 50-rancher.yaml file have the same requirement, if that helps with debugging this issue), which is what triggers draining.

Here is the POST request for a k3s cluster on create:
{
  "id": "fleet-default/jhyde-k3s-test",
  "type": "provisioning.cattle.io.cluster",
  "links": {
    "remove": "https://jhyde.ngrok.io/v1/provisioning.cattle.io.clusters/fleet-default/jhyde-k3s-test",
    "self": "https://jhyde.ngrok.io/v1/provisioning.cattle.io.clusters/fleet-default/jhyde-k3s-test",
    "update": "https://jhyde.ngrok.io/v1/provisioning.cattle.io.clusters/fleet-default/jhyde-k3s-test",
    "view": "https://jhyde.ngrok.io/apis/provisioning.cattle.io/v1/namespaces/fleet-default/clusters/jhyde-k3s-test"
  },
  "apiVersion": "provisioning.cattle.io/v1",
  "kind": "Cluster",
  "metadata": {
    "annotations": {
      "field.cattle.io/creatorId": "user-pt952"
    },
    "creationTimestamp": "2022-10-05T22:03:22Z",
    "fields": [
      "jhyde-k3s-test",
      null,
      null
    ],
    "generation": 1,
    "managedFields": [
      {
        "apiVersion": "provisioning.cattle.io/v1",
        "fieldsType": "FieldsV1",
        "fieldsV1": {
          "f:spec": {
            ".": {},
            "f:cloudCredentialSecretName": {},
            "f:defaultPodSecurityPolicyTemplateName": {},
            "f:kubernetesVersion": {},
            "f:localClusterAuthEndpoint": {
              ".": {},
              "f:caCerts": {},
              "f:enabled": {},
              "f:fqdn": {}
            },
            "f:rkeConfig": {
              ".": {},
              "f:chartValues": {},
              "f:etcd": {
                ".": {},
                "f:disableSnapshots": {},
                "f:s3": {},
                "f:snapshotRetention": {},
                "f:snapshotScheduleCron": {}
              },
              "f:machineGlobalConfig": {
                ".": {},
                "f:disable-kube-proxy": {},
                "f:etcd-expose-metrics": {},
                "f:profile": {}
              },
              "f:machinePools": {},
              "f:machineSelectorConfig": {},
              "f:registries": {
                ".": {},
                "f:configs": {},
                "f:mirrors": {}
              },
              "f:upgradeStrategy": {
                ".": {},
                "f:controlPlaneConcurrency": {},
                "f:controlPlaneDrainOptions": {
                  ".": {},
                  "f:deleteEmptyDirData": {},
                  "f:disableEviction": {},
                  "f:enabled": {},
                  "f:force": {},
                  "f:gracePeriod": {},
                  "f:ignoreDaemonSets": {},
                  "f:ignoreErrors": {},
                  "f:skipWaitForDeleteTimeoutSeconds": {},
                  "f:timeout": {}
                },
                "f:workerConcurrency": {},
                "f:workerDrainOptions": {
                  ".": {},
                  "f:deleteEmptyDirData": {},
                  "f:disableEviction": {},
                  "f:enabled": {},
                  "f:force": {},
                  "f:gracePeriod": {},
                  "f:ignoreDaemonSets": {},
                  "f:ignoreErrors": {},
                  "f:skipWaitForDeleteTimeoutSeconds": {},
                  "f:timeout": {}
                }
              }
            }
          }
        },
        "manager": "___go_build_main_go__no_delete_",
        "operation": "Update",
        "time": "2022-10-05T22:03:22Z"
      }
    ],
    "name": "jhyde-k3s-test",
    "namespace": "fleet-default",
    "relationships": null,
    "resourceVersion": "81104",
    "state": {
      "error": false,
      "message": "Resource is current",
      "name": "active",
      "transitioning": false
    },
    "uid": "2ea69631-0cd0-4751-ac9e-b198a9cc500e"
  },
  "spec": {
    "cloudCredentialSecretName": "cattle-global-data:cc-jsb7f",
    "defaultPodSecurityPolicyTemplateName": "",
    "kubernetesVersion": "v1.24.6+k3s1",
    "localClusterAuthEndpoint": {
      "caCerts": "",
      "enabled": false,
      "fqdn": ""
    },
    "rkeConfig": {
      "chartValues": {},
      "etcd": {
        "disableSnapshots": false,
        "s3": null,
        "snapshotRetention": 5,
        "snapshotScheduleCron": "0 */5 * * *"
      },
      "machineGlobalConfig": {
        "disable-kube-proxy": false,
        "etcd-expose-metrics": false,
        "profile": null
      },
      "machinePools": [
        {
          "controlPlaneRole": true,
          "etcdRole": false,
          "labels": {},
          "machineConfigRef": {
            "kind": "DigitaloceanConfig",
            "name": "nc-jhyde-k3s-test-controlplane-n5hbt"
          },
          "name": "controlplane",
          "quantity": 2,
          "unhealthyNodeTimeout": "0m",
          "workerRole": false
        },
        {
          "controlPlaneRole": false,
          "etcdRole": false,
          "labels": {},
          "machineConfigRef": {
            "kind": "DigitaloceanConfig",
            "name": "nc-jhyde-k3s-test-worker-nbsk4"
          },
          "name": "worker",
          "quantity": 3,
          "unhealthyNodeTimeout": "0m",
          "workerRole": true
        },
        {
          "controlPlaneRole": false,
          "etcdRole": true,
          "labels": {},
          "machineConfigRef": {
            "kind": "DigitaloceanConfig",
            "name": "nc-jhyde-k3s-test-etcd-2tzbn"
          },
          "name": "etcd",
          "quantity": 3,
          "unhealthyNodeTimeout": "0m",
          "workerRole": false
        }
      ],
      "machineSelectorConfig": [
        {
          "config": {
            "protect-kernel-defaults": false
          }
        }
      ],
      "registries": {
        "configs": {},
        "mirrors": {}
      },
      "upgradeStrategy": {
        "controlPlaneConcurrency": "1",
        "controlPlaneDrainOptions": {
          "deleteEmptyDirData": true,
          "disableEviction": false,
          "enabled": false,
          "force": false,
          "gracePeriod": -1,
          "ignoreDaemonSets": true,
          "ignoreErrors": false,
          "skipWaitForDeleteTimeoutSeconds": 0,
          "timeout": 120
        },
        "workerConcurrency": "1",
        "workerDrainOptions": {
          "deleteEmptyDirData": true,
          "disableEviction": false,
          "enabled": false,
          "force": false,
          "gracePeriod": -1,
          "ignoreDaemonSets": true,
          "ignoreErrors": false,
          "skipWaitForDeleteTimeoutSeconds": 0,
          "timeout": 120
        }
      }
    }
  }
}

And the subsequent POST request on update:
{
  "id": "fleet-default/jhyde-k3s-test",
  "type": "provisioning.cattle.io.cluster",
  "links": {
    "remove": "https://jhyde.ngrok.io/v1/provisioning.cattle.io.clusters/fleet-default/jhyde-k3s-test",
    "self": "https://jhyde.ngrok.io/v1/provisioning.cattle.io.clusters/fleet-default/jhyde-k3s-test",
    "update": "https://jhyde.ngrok.io/v1/provisioning.cattle.io.clusters/fleet-default/jhyde-k3s-test",
    "view": "https://jhyde.ngrok.io/apis/provisioning.cattle.io/v1/namespaces/fleet-default/clusters/jhyde-k3s-test"
  },
  "apiVersion": "provisioning.cattle.io/v1",
  "kind": "Cluster",
  "metadata": {
    "annotations": {
      "field.cattle.io/creatorId": "user-pt952"
    },
    "creationTimestamp": "2022-10-05T22:03:22Z",
    "fields": [
      "jhyde-k3s-test",
      "true",
      "jhyde-k3s-test-kubeconfig"
    ],
    "finalizers": [
      "wrangler.cattle.io/cloud-config-secret-remover",
      "wrangler.cattle.io/provisioning-cluster-remove",
      "wrangler.cattle.io/rke-cluster-remove"
    ],
    "generation": 3,
    "managedFields": [
      {
        "apiVersion": "provisioning.cattle.io/v1",
        "fieldsType": "FieldsV1",
        "fieldsV1": {
          "f:status": {
            ".": {},
            "f:agentDeployed": {},
            "f:clientSecretName": {},
            "f:clusterName": {},
            "f:conditions": {},
            "f:observedGeneration": {},
            "f:ready": {}
          }
        },
        "manager": "___go_build_main_go__no_delete_",
        "operation": "Update",
        "subresource": "status",
        "time": "2022-10-05T22:07:24Z"
      },
      {
        "apiVersion": "provisioning.cattle.io/v1",
        "fieldsType": "FieldsV1",
        "fieldsV1": {
          "f:metadata": {
            "f:finalizers": {
              ".": {},
              "v:\"wrangler.cattle.io/cloud-config-secret-remover\"": {},
              "v:\"wrangler.cattle.io/provisioning-cluster-remove\"": {},
              "v:\"wrangler.cattle.io/rke-cluster-remove\"": {}
            }
          },
          "f:spec": {
            ".": {},
            "f:cloudCredentialSecretName": {},
            "f:defaultPodSecurityPolicyTemplateName": {},
            "f:kubernetesVersion": {},
            "f:localClusterAuthEndpoint": {
              ".": {},
              "f:caCerts": {},
              "f:enabled": {},
              "f:fqdn": {}
            },
            "f:rkeConfig": {
              ".": {},
              "f:chartValues": {},
              "f:etcd": {
                ".": {},
                "f:disableSnapshots": {},
                "f:snapshotRetention": {},
                "f:snapshotScheduleCron": {}
              },
              "f:machineGlobalConfig": {
                ".": {},
                "f:disable-apiserver": {},
                "f:disable-cloud-controller": {},
                "f:disable-controller-manager": {},
                "f:disable-etcd": {},
                "f:disable-kube-proxy": {},
                "f:disable-network-policy": {},
                "f:disable-scheduler": {},
                "f:etcd-expose-metrics": {},
                "f:profile": {},
                "f:secrets-encryption": {}
              },
              "f:machinePools": {},
              "f:machineSelectorConfig": {},
              "f:registries": {
                ".": {},
                "f:configs": {},
                "f:mirrors": {}
              },
              "f:upgradeStrategy": {
                ".": {},
                "f:controlPlaneConcurrency": {},
                "f:controlPlaneDrainOptions": {
                  ".": {},
                  "f:deleteEmptyDirData": {},
                  "f:disableEviction": {},
                  "f:enabled": {},
                  "f:force": {},
                  "f:gracePeriod": {},
                  "f:ignoreDaemonSets": {},
                  "f:ignoreErrors": {},
                  "f:skipWaitForDeleteTimeoutSeconds": {},
                  "f:timeout": {}
                },
                "f:workerConcurrency": {},
                "f:workerDrainOptions": {
                  ".": {},
                  "f:deleteEmptyDirData": {},
                  "f:disableEviction": {},
                  "f:enabled": {},
                  "f:force": {},
                  "f:gracePeriod": {},
                  "f:ignoreDaemonSets": {},
                  "f:ignoreErrors": {},
                  "f:skipWaitForDeleteTimeoutSeconds": {},
                  "f:timeout": {}
                }
              }
            }
          }
        },
        "manager": "___go_build_main_go__no_delete_",
        "operation": "Update",
        "time": "2022-10-05T22:24:11Z"
      }
    ],
    "name": "jhyde-k3s-test",
    "namespace": "fleet-default",
    "relationships": [
      {
        "toId": "fleet-default/nc-jhyde-k3s-test-controlplane-n5hbt",
        "toType": "rke-machine-config.cattle.io.digitaloceanconfig",
        "rel": "owner",
        "state": "active",
        "message": "Resource is current"
      },
      {
        "toId": "fleet-default/r-cluster-jhyde-k3s-test-view-p-dd499-creator-project-own-b3c54",
        "toType": "rbac.authorization.k8s.io.rolebinding",
        "rel": "owner",
        "state": "active",
        "message": "Resource is current"
      },
      {
        "toId": "fleet-default/jhyde-k3s-test",
        "toType": "fleet.cattle.io.cluster",
        "rel": "applies",
        "state": "active",
        "message": "Resource is Ready"
      },
      {
        "toId": "c-m-v4r6lz8w",
        "toType": "management.cattle.io.cluster",
        "rel": "applies",
        "state": "active",
        "message": "Resource is Ready"
      },
      {
        "toId": "fleet-default/crt-jhyde-k3s-test-nodes-manage",
        "toType": "rbac.authorization.k8s.io.role",
        "rel": "owner",
        "state": "active",
        "message": "Resource is current"
      },
      {
        "toId": "fleet-default/r-cluster-jhyde-k3s-test-view-p-s8bjz-creator-project-own-7346a",
        "toType": "rbac.authorization.k8s.io.rolebinding",
        "rel": "owner",
        "state": "active",
        "message": "Resource is current"
      },
      {
        "toId": "fleet-default/crt-jhyde-k3s-test-cluster-admin",
        "toType": "rbac.authorization.k8s.io.role",
        "rel": "owner",
        "state": "active",
        "message": "Resource is current"
      },
      {
        "toId": "fleet-default/crt-jhyde-k3s-test-nodes-view",
        "toType": "rbac.authorization.k8s.io.role",
        "rel": "owner",
        "state": "active",
        "message": "Resource is current"
      },
      {
        "toId": "fleet-default/nc-jhyde-k3s-test-worker-nbsk4",
        "toType": "rke-machine-config.cattle.io.digitaloceanconfig",
        "rel": "owner",
        "state": "active",
        "message": "Resource is current"
      },
      {
        "toId": "fleet-default/r-cluster-jhyde-k3s-test-view",
        "toType": "rbac.authorization.k8s.io.role",
        "rel": "owner",
        "state": "active",
        "message": "Resource is current"
      },
      {
        "toId": "fleet-default/crt-jhyde-k3s-test-cluster-member",
        "toType": "rbac.authorization.k8s.io.role",
        "rel": "owner",
        "state": "active",
        "message": "Resource is current"
      },
      {
        "toId": "fleet-default/jhyde-k3s-test",
        "toType": "cluster.x-k8s.io.cluster",
        "rel": "owner",
        "state": "provisioned"
      },
      {
        "toId": "fleet-default/jhyde-k3s-test-kubeconfig",
        "toType": "secret",
        "rel": "owner",
        "state": "active",
        "message": "Resource is always ready"
      },
      {
        "toId": "fleet-default/jhyde-k3s-test-managed-system-upgrade-controller",
        "toType": "management.cattle.io.managedchart",
        "rel": "owner",
        "state": "active",
        "message": "Resource is Ready"
      },
      {
        "toId": "c-m-v4r6lz8w/c-m-v4r6lz8w-fleet-default-owner",
        "toType": "management.cattle.io.clusterroletemplatebinding",
        "rel": "applies",
        "state": "active",
        "message": "Resource is current"
      },
      {
        "toId": "fleet-default/crt-jhyde-k3s-test-cluster-owner",
        "toType": "rbac.authorization.k8s.io.role",
        "rel": "owner",
        "state": "active",
        "message": "Resource is current"
      },
      {
        "toId": "fleet-default/nc-jhyde-k3s-test-etcd-2tzbn",
        "toType": "rke-machine-config.cattle.io.digitaloceanconfig",
        "rel": "owner",
        "state": "active",
        "message": "Resource is current"
      }
    ],
    "resourceVersion": "87901",
    "state": {
      "error": false,
      "message": "Cluster generation is 3, but latest observed generation is 2",
      "name": "in-progress",
      "transitioning": true
    },
    "uid": "2ea69631-0cd0-4751-ac9e-b198a9cc500e"
  },
  "spec": {
    "cloudCredentialSecretName": "cattle-global-data:cc-jsb7f",
    "defaultPodSecurityPolicyTemplateName": "",
    "kubernetesVersion": "v1.24.6+k3s1",
    "localClusterAuthEndpoint": {
      "caCerts": "",
      "enabled": false,
      "fqdn": ""
    },
    "rkeConfig": {
      "chartValues": {},
      "etcd": {
        "disableSnapshots": false,
        "snapshotRetention": 5,
        "snapshotScheduleCron": "0 */5 * * *"
      },
      "machineGlobalConfig": {
        "disable-apiserver": false,
        "disable-cloud-controller": false,
        "disable-controller-manager": false,
        "disable-etcd": false,
        "disable-kube-proxy": false,
        "disable-network-policy": false,
        "disable-scheduler": false,
        "etcd-expose-metrics": false,
        "profile": null,
        "secrets-encryption": false
      },
      "machinePools": [
        {
          "controlPlaneRole": true,
          "machineConfigRef": {
            "kind": "DigitaloceanConfig",
            "name": "nc-jhyde-k3s-test-controlplane-n5hbt"
          },
          "name": "controlplane",
          "quantity": 2,
          "unhealthyNodeTimeout": "0s"
        },
        {
          "machineConfigRef": {
            "kind": "DigitaloceanConfig",
            "name": "nc-jhyde-k3s-test-worker-nbsk4"
          },
          "name": "worker",
          "quantity": 3,
          "unhealthyNodeTimeout": "0s",
          "workerRole": true
        },
        {
          "etcdRole": true,
          "machineConfigRef": {
            "kind": "DigitaloceanConfig",
            "name": "nc-jhyde-k3s-test-etcd-2tzbn"
          },
          "name": "etcd",
          "quantity": 3,
          "unhealthyNodeTimeout": "0s"
        }
      ],
      "machineSelectorConfig": [
        {
          "config": {
            "docker": false,
            "protect-kernel-defaults": false,
            "selinux": false
          }
        }
      ],
      "registries": {
        "configs": {},
        "mirrors": {}
      },
      "upgradeStrategy": {
        "controlPlaneConcurrency": "1",
        "controlPlaneDrainOptions": {
          "deleteEmptyDirData": true,
          "disableEviction": false,
          "enabled": true,
          "force": false,
          "gracePeriod": -1,
          "ignoreDaemonSets": true,
          "ignoreErrors": false,
          "skipWaitForDeleteTimeoutSeconds": 0,
          "timeout": 120
        },
        "workerConcurrency": "2",
        "workerDrainOptions": {
          "deleteEmptyDirData": true,
          "disableEviction": false,
          "enabled": true,
          "force": false,
          "gracePeriod": -1,
          "ignoreDaemonSets": true,
          "ignoreErrors": false,
          "skipWaitForDeleteTimeoutSeconds": 0,
          "timeout": 120
        }
      }
    }
  },
  "status": {
    "agentDeployed": true,
    "clientSecretName": "jhyde-k3s-test-kubeconfig",
    "clusterName": "c-m-v4r6lz8w",
    "conditions": [
      {
        "error": false,
        "lastUpdateTime": "2022-10-05T22:07:24Z",
        "status": "False",
        "transitioning": false,
        "type": "Reconciling"
      },
      {
        "error": false,
        "lastUpdateTime": "2022-10-05T22:03:22Z",
        "status": "False",
        "transitioning": false,
        "type": "Stalled"
      },
      {
        "error": false,
        "lastUpdateTime": "2022-10-05T22:07:24Z",
        "status": "True",
        "transitioning": false,
        "type": "Created"
      },
      {
        "error": false,
        "lastUpdateTime": "2022-10-05T22:14:39Z",
        "status": "True",
        "transitioning": false,
        "type": "RKECluster"
      },
      {
        "error": false,
        "lastUpdateTime": "2022-10-05T18:03:22-04:00",
        "status": "True",
        "transitioning": false,
        "type": "BackingNamespaceCreated"
      },
      {
        "error": false,
        "lastUpdateTime": "2022-10-05T18:03:22-04:00",
        "status": "True",
        "transitioning": false,
        "type": "DefaultProjectCreated"
      },
      {
        "error": false,
        "lastUpdateTime": "2022-10-05T18:03:22-04:00",
        "status": "True",
        "transitioning": false,
        "type": "SystemProjectCreated"
      },
      {
        "error": false,
        "lastUpdateTime": "2022-10-05T18:03:22-04:00",
        "status": "True",
        "transitioning": false,
        "type": "InitialRolesPopulated"
      },
      {
        "error": false,
        "lastUpdateTime": "2022-10-05T18:03:23-04:00",
        "status": "True",
        "transitioning": false,
        "type": "CreatorMadeOwner"
      },
      {
        "error": false,
        "lastUpdateTime": "2022-10-05T18:03:23-04:00",
        "status": "True",
        "transitioning": false,
        "type": "NoDiskPressure"
      },
      {
        "error": false,
        "lastUpdateTime": "2022-10-05T18:03:23-04:00",
        "status": "True",
        "transitioning": false,
        "type": "NoMemoryPressure"
      },
      {
        "error": false,
        "lastUpdateTime": "2022-10-05T18:03:23-04:00",
        "status": "True",
        "transitioning": false,
        "type": "SecretsMigrated"
      },
      {
        "error": false,
        "lastUpdateTime": "2022-10-05T18:03:23-04:00",
        "status": "True",
        "transitioning": false,
        "type": "ServiceAccountSecretsMigrated"
      },
      {
        "error": false,
        "lastUpdateTime": "2022-10-05T22:04:30Z",
        "status": "True",
        "transitioning": false,
        "type": "Provisioned"
      },
      {
        "error": false,
        "lastUpdateTime": "2022-10-05T22:07:14Z",
        "status": "True",
        "transitioning": false,
        "type": "Connected"
      },
      {
        "error": false,
        "lastUpdateTime": "2022-10-05T22:14:39Z",
        "status": "True",
        "transitioning": false,
        "type": "Updated"
      },
      {
        "error": false,
        "lastUpdateTime": "2022-10-05T18:07:24-04:00",
        "status": "True",
        "transitioning": false,
        "type": "Ready"
      },
      {
        "error": false,
        "lastUpdateTime": "2022-10-05T18:06:54-04:00",
        "status": "True",
        "transitioning": false,
        "type": "GlobalAdminsSynced"
      },
      {
        "error": false,
        "lastUpdateTime": "2022-10-05T18:07:00-04:00",
        "status": "True",
        "transitioning": false,
        "type": "SystemAccountCreated"
      },
      {
        "error": false,
        "lastUpdateTime": "2022-10-05T18:07:05-04:00",
        "status": "True",
        "transitioning": false,
        "type": "AgentDeployed"
      },
      {
        "error": false,
        "lastUpdateTime": "2022-10-05T18:07:24-04:00",
        "status": "True",
        "transitioning": false,
        "type": "Waiting"
      }
    ],
    "observedGeneration": 2,
    "ready": true
  }
}

Notably, the machineGlobalConfig after create:
      "machineGlobalConfig": {
        "disable-kube-proxy": false,
        "etcd-expose-metrics": false,
        "profile": null
      },

and after update:
      "machineGlobalConfig": {
        "disable-apiserver": false,
        "disable-cloud-controller": false,
        "disable-controller-manager": false,
        "disable-etcd": false,
        "disable-kube-proxy": false,
        "disable-network-policy": false,
        "disable-scheduler": false,
        "etcd-expose-metrics": false,
        "profile": null,
        "secrets-encryption": false
      },

https://github.com/rancher/rancher/issues/39020 needs this for 2.7.0. Thankfully we have a PR up for review so this could make it in earlier than expected.

Test Environment:
Rancher version: v2.7-head 76c98b4
Rancher cluster type: HA
Docker version: 20.10
Downstream cluster type: RKE2 and k3s and RKE1

Testing:

Provision RKE1/RKE2/K3s cluster
Once active, edit config
Click switch to yaml
Click Save

Result
Generation was updated and clusters went into Updating although no changes were made.
@gaktive could you take a look? Thank you!

Sure I can look @thaneunsoo; did you see this on RKE1, RKE2, and K3s?

@mantis-toboggan-md yes, for rke1,rke2,k3s

Interesting: RKE1 provisioning is done through the old UI so there's either the same problem in both UIs or there is another problem entirely. I'm not seeing the behaviour you are on my own setup but it is older; I'm making a fresh one and looking into this further now

@thaneunsoo I was able to repro this behavior with rke2 and k3s; a fix is now merged: https://github.com/rancher/dashboard/pull/7218
What I saw specifically was that the rke2 or k3s cluster would go into an updating state after saving from a different view than the cluster had previously been saved in. So: provision a cluster without hitting 'view as yaml', go to 'edit config', then click 'view as yaml', save, the cluster updates despite you not changing anything. Again go to 'edit config', click 'view as yaml', save, the cluster does not change state. Go to 'edit config', save without clicking 'view as yaml', the cluster goes into updating...you get the idea
I'm having a harder time reproducing this consistently with RKE1. Could we potentially file a separate issue for that @thaneunsoo ?

Test Environment:
Rancher version: v2.7-head 9f1e043
Rancher cluster type: HA
Docker version: 20.10
Downstream cluster type: RKE2/K3s

Testing:

Provision RKE2/K3s cluster
Wait for cluster to become active
a. Click Edit Config >  Save
b. Click Edit Config > View as YAML > Save

Results
Clusters do not go into Updating state. I did notice that the first I performed either of steps 2a or 2b, the cluster would go into In Progress for a split second and then go to active. If the user took their eyes off the screen for a second, they would miss this. This seems to be okay as there is editing in progress. Closing this issue as fixed

/backport v2.6.10

@gaktive @nwmac , we will need this fixed in 2.6.10 as well. I've tried to create backport, but it looks like backport/forwardport bot is not available in this repo.
Could you please create a backport to ensure this is fixed in 2.6.10?
cc: @sowmyav27


Evaluate options for producing a native binary

Description
As an AlgoKit developer
I want to evaluate the various options for producing a native binary
So that I'm informed of the tradeoffs of each approach
Technical Details
Options to evaluate:

PyInstaller
cx_Freeze
PyOxidizer
Nuitka

Environments to Support:

Windows (10+)
MacOS (-1 from current)
Linux - RPM Based - CentOS/RHEL
Linux - Debian Based - Ubuntu/Fedora/Qubes OS (16.0.4+)
Linux - Arch

Architectures to Support:

x86
x86_64
arm64
Apple silicon

Acceptance Criteria

A representative proof of concept has been built to assess suitability of each option
Any findings/limitations/trade offs/problems that have been discovered are documented, allowing us to critically assess the options

Tasks

[x] Create a PyInstaller PoC @negar-abbasi
[x] Create a cx_Freeze PoC
[x] Create a PyOxidizer PoC
[x] Create a Nuitka PoC

separate adr on distribution via snap, brew, winget is to follow


Retry request when GOAWAY is received

There's no clean way to handle this using the Java API unfortunately... https://stackoverflow.com/a/55092354
So we just have to catch the exception and make the request again

Added in https://github.com/NamelessMC/Nameless-Java-API/commit/3aa8e55cada2885084187b1936b01e3d51ccd8db


Format Numbers as currency

We have some dashboards in use, which shows some currencies in the list widget,
how is the best way to show it with , as decimal separator and . as thousands separator (european style)

Fork the Number widget and modify the fork to support these features.

Please close this issue.


Feature request: async store

Hi,
I tried to make simple-auth-chrome-storage-store, but that was difficult. chrome.storage has  only async API (documentation is here). However, SimpleAuth.Storage.Base.restore() expects to return the data immediately.
Are there any plans about this?

No, there are no plans for this but pull requests are welcome.

Thank you for your quick reply, I'll try this.


Stay Request - Decline Message

It would be a nice gesture and feature to be able to send a decline message.
Currently the host can either accept or decline the request.
Either way, but imo more importantly for declining, it would be nice for the host to send a little message with the decline. Maybe stating the reason or any other kind of message.
This would be in the feature group of chat functionality.

I think that is a great feature for the in-app chat / bot functionality

Done.


ENABLE_TEST_CLOUD is not defined anywhere

The docs refer to the ENABLE_TEST_CLOUD compiler flag, saying that newer versions of VS define this for you - but they don't. Tested with VS2017 15.8 and VS for Mac 7.7, this compiler flag is not set in the blank forms app templates either directly, or intrinsically at compile time.
Can this be changed to be DEBUG, of else can the templates be fixed up.

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

ID: cfd5535b-f176-9808-90c3-e35d1ad4ca88
Version Independent ID: 382fe3a0-b895-8283-95ad-615475c94d5e
Content: UITest Cheat Sheet - Visual Studio App Center
Content Source: docs/test-cloud/uitest/cheatsheet.md
Service: vs-appcenter
GitHub Login: @glennwester
Microsoft Alias: glwest

@jimbobbennett I'll ask the PM to take a look and respond.
Don't forget, App Center support is provided directly from within the App Center portal. Any time you need help, just click the blue chat button in the lower-right corner of any page and our dedicated support team will respond. For additional information, see the App Center Help Center.

@jimbobbennett Thanks for reporting! We'll get this fix to the template in for a future version of Visual Studio.


Change ModuleNotFoundError by ImportError

ModuleNotFoundError is a new exception in Python 3.6, whereas earlier versions use ImportError.

This should fix: https://github.com/APSL/django-hattori/issues/1


Gradle Version in AAR is out of date

When trying to import the gradle version of the library into my current project, I was receiving an issue with the ic_launcher.png being duplicated within my project and the library. Upon looking into this, I found this which says that the problem arises because the version of the gradle plugin being used in the library is out of date with my current plugin version. In looking at the source, the library is currently using version 1.1.0 while the current release version is 1.2.3. If you could please update the build to correct this issue, that would help with further compatibility issues.

The bug causing this has also been fixed, but just haven't made a new release yet. It's coming soon, but in the meantime, you can either grab the latest in code or the SNAPSHOT build which has the fix. But will update the gradle version as well, thanks for that.

Gradle version updated on https://github.com/anothem/android-range-seek-bar/pull/21
Also on SNAPSHOT build now (use org.florescu.android.rangeseekbar:rangeseekbar-library:0.3.0-SNAPSHOT)


CB-13523: Add automaticProvisioning to iOS signing docs

Docs side of https://github.com/apache/cordova-ios/commit/5cb8bd199fe8df85272678d6d4c6343dd080f2a3
Also tried to clean up the manual flags to indicate that automatic signing is generally recommended, and you should only need to specify a provisioningProfile UUID if you're using manual signing.
Platforms affected
iOS
What does this PR do?
Adds docs for the --automaticProvisioning option

LGTM. @dpogue ready to merge or wait until after next iOS release?

The --automaticProvisioning flag won't be available until the next iOS release

This has now been released in Cordova-iOS 4.5.4 and can be merged

Cool! Forgot about this PR, merging in!


Update robot meshes

Hi again,
Is it planned to commit the authentic meshes of the robot ?
Thank you

Hi,
Yes we eventually want to have a virtual model as close as possible from the real one, updating the meshes of the model will greatly improve this resemblance

Updated meshes for the Pepper robot have been released in v1.4.0


Nvida Hardware support...

Any change to take a benefit of this ?
http://www.phoronix.com/scan.php?page=news_item&px=FFmpeg-NVENC-H265-Encode

#75 addresses this. I did some testing with the latest generation cards, and while they are quick, they are very very limited in their options. You basically get a few presets and have to use that, hardware acceleration is mainly meant for streaming. Another thing is that they are not as efficient as software encoders, I haven't tested it in a while but I believe the difference is substantial.
The only real gain I see from using hw accel is decoding videos when necessary, and even then some of my tests showed similar cpu usage, along with the added gpu usage, as software decoding and slower than just using the cpu.
All in all this is something to look into but most likely will always be in the backlog till I find some real extra time and reason to do it.
Your not missing out on as much as you think.

Well... many thx for that statement! Just looking forward to speed up to encode my let me say giant collection ;-) never mind will properly buy some bigger CPU :-D  and many thx for your job!! great tool!

Check out the new AMD and Intel CPU's that haven't come out yet. Encoders usually scale well and perform better the more cores you throw at them.

Can agree there, work great on my Dual Xeon E5-2687W's :)

Duplicate of #75.


Update methods

With this PR I add two new methods; the first one updates all the orientation and gravity task at once by passing an unordered map with the number of nodes and the new struct nodeStruct containing the orientation and angular velocity data of the nodes. The second one calibrates all the nodes by passing the already described unordered map.

Thank you @traversaro! Merging!


Consolidate package delivery down to 2 VIP files

[x] This contribution adheres to CONTRIBUTING.md.

TODO: Check the above box with an 'x' indicating you've read and followed CONTRIBUTING.md.
What does this Pull Request accomplish?
TODO: Include high-level description of the changes in this pull request.
Why should this Pull Request be merged?
TODO: Justify why this contribution should be part of the project.
What testing has been done?
TODO: Detail what testing has been done to ensure this submission meets requirements.

This looks good. I was present for all of the refactoring as pair programming. IMO, we should go ahead and check this in so the large re-org is done and then follow up with fix ups of tests, and any fallout after the fact.
We should update any instructions for contributing, etc. and then produce a release.


Add chart to the Lost Dao chapter on decentralization

The chapter discusses Paul Baran's work, which helped define "decentralized" v. "distributed" networks and has classic visual representations.  These should be added to that section.

 Gov4Git notices
On Thursday, 29-Feb-24 21:35:46 UTC by Gov4Git dev
Notice naxswf
Started managing this issue as Gov4Git concern 41 with initial priority score of 0.000000.
This project is managed by Gov4Git, a decentralized governance system for collaborative git projects.
To participate in governance, install the Gov4Git desktop app.
Notice mfcinw
This issue's priority score is now 0.000000.
The cost of priority is 0.000000.
The projected bounty is now 0.000000.
Notice 3dsdfp
The set of eligible proposals claiming this issue is empty.

 Gov4Git notices
On Friday, 01-Mar-24 20:45:13 UTC by Gov4Git dev
Notice ao3gmj
This issue's priority score is now 40.000000.
The cost of priority is 1600.000000.
The projected bounty is now 80.000000.
Notice w4v5io
The set of eligible proposals claiming this issue is empty.


Wrong IP value for the default DNS server used by spoke VNET

In the WorkFlow part for the private DNS resolver section, we have these lines :
"All Azure spoke virtual networks use the default Azure DNS server at the IP address <IP_ADDRESS>. All spoke networks are peered with the hub virtual network."
The IP address <IP_ADDRESS> is not the Azure default DNS, this may confuse the client, we may need to replace this lime with the Azure default DNS "<IP_ADDRESS>"

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

ID: 6ce03940-eeb4-98b6-4624-1615715beec4
Version Independent ID: 6ce03940-eeb4-98b6-4624-1615715beec4
Content: Azure DNS Private Resolver - Azure Example Scenarios
Content Source: docs/example-scenario/networking/azure-dns-private-resolver.yml
Service: architecture-center
Sub-service: example-scenario
GitHub Login: @moorthyannadurai
Microsoft Alias: moannadu

@mohijazi Thanks for the feedback. We will review and update as appropriate.

I've contacted the article contributor and will resolve this issue as soon as he advises me about this edit.

Thank you for reporting this @mohijazi -- I've just made the update and it will go live later on Monday.


VX RPP - Backend Support

AMD RPP - Build with CPU/OpenCL/HIP
VX_RPP - CPU only backend missing
VX_RPP - link with the right backend

@asalmanp can you look into building vx_rpp with a CPU-only install.


Recursive rendering based on nested objects, not 'children' arrays

I need to present data serialized from MongoDB objects. This data does not have predefined {'name': 'SomeKey', 'value': 'someValue', 'children': [{'name': 'SomeOtherKey', 'value': 'someOtherValue'}]}  structure but looks just like a nested hierarchy of objects  {'key1': 'someValue1', 'key2': {'key3':'someValue2'}, 'key4': ['arrayValue1', arrayValue2]}. My questions are

would modifying angular-ui-tree for achieving this be something that could be done with reasonable amount of effort, or would you estimate this change as too complex/contradicting with angulajs internals (for instance ng-repeat)
If it is doable, I would appreciate any hints on where to start. I do not need drag-drop, addition, deletion functionality: just rendering and filtering.

Please ask for ideas in our chat room, see https://gitter.im/angular-ui-tree/angular-ui-tree

I did a week ago. I would appreciate your comments on this.


Google calendar bot not able to update status emoji to calendar once user status has been set with users.profile.set method

Description
I am working on the bot. As per the user's interaction with bot, I am updating the user's profile status with users.profile.set method. But once the status has been updated with this API, no other bot e.g., GoogleCalendar or Slack Huddle not showing its respective icons (emojis) during their respective events.
Is there something I am missing while setting the profile or need to add as an enhancement to the bolt?
Previously when I was using RTM API, google calendar bot was updating emoji, even though I had set it already.
What type of issue is this? (place an x in one of the [ ])

[ ] bug
[ ] enhancement (feature request)
[x] question
[ ] documentation related
[ ] example code related
[ ] testing related
[x] discussion

Requirements (place an x in each of the [ ])

[x] I've read and understood the Contributing guidelines and have done my best effort to follow them.
[x] I've read and agree to the Code of Conduct.
[x] I've searched for any related issues and avoided creating a duplicate issue.

Bug Report
Reproducible in:
package version:  ^3.5.0
node version: 14.17.4
OS version(s): Windows 10
Steps to reproduce:

Set user profile status using users.profile.set method (make sure to set status_emoji and status_text)
Start huddle, or google calendar event. And observe whether its updating the status_emoji.
Clear the status and again start huddle / calendar event. Now it will update the status_emoji

Expected result:
If the status is set with users.profile.set  but google calendar should set status emoji to calendar icon during meeting times
Actual result:
GoogleCalendar did not update emoji.  Older status was maintained

Thanks, @seratch, for mentioning the Slack product side change.
Pls, share, if you find a way to customize this behavior.


Android - Number pad input lags - reported by @mdneyazahmad

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

Action Performed:

Open app
Start IOU request
Type any number

Expected Result:
Numbers should be immediately displayed
Actual Result:
For some small time the second digit becomes first and it restores
Workaround:
unknown
Platform:

Where is this issue occurring?

Android

Version Number: 1.1.38-0
Reproducible in staging?: Need repro
Reproducible in production?: need repro
Logs: https://stackoverflow.com/c/expensify/questions/4856
Notes/Photos/Videos: Any additional supporting documentation
https://user-images.githubusercontent.com/43995119/154411244-eafa1c78-e1b4-4f95-972a-322cb7d40494.mp4
Expensify/Expensify Issue URL:
Issue reported by: @mdneyazahmad
Slack conversation: https://expensify.slack.com/archives/C01GTK53T8Q/p1643396599038599
View all open jobs on GitHub

Video in the issue is at 0.25x


ReferenceError: [BABEL] /rsg-alt/app/index.js: Unknown option: direct.presets

Hi, I'm trying to get this library integrated with my project and I'm getting the following error.
{
	"name": "rsg/rsg-lib",
	"hostname": "UK134489.local",
	"pid": 15776,
	"level": 50,
	"msg": "[ './~/rsg-alt/app/index.js\\nModule build failed: ReferenceError: [BABEL] /Users/mdell/Work/Repos/web/node_modules/rsg-alt/app/index.js: Unknown option: direct.presets\\n    at Logger.error (/Users/mdell/Work/Repos/web/node_modules/babel-core/lib/transformation/file/logger.js:58:11)\\n    at OptionManager.mergeOptions (/Users/mdell/Work/Repos/web/node_modules/babel-core/lib/transformation/file/options/option-manager.js:126:29)\\n    at OptionManager.init (/Users/mdell/Work/Repos/web/node_modules/babel-core/lib/transformation/file/options/option-manager.js:216:10)\\n    at File.initOptions (/Users/mdell/Work/Repos/web/node_modules/babel-core/lib/transformation/file/index.js:147:75)\\n    at new File (/Users/mdell/Work/Repos/web/node_modules/babel-core/lib/transformation/file/index.js:137:22)\\n    at Pipeline.transform (/Users/mdell/Work/Repos/web/node_modules/babel-core/lib/transformation/pipeline.js:164:16)\\n    at transpile (/Users/mdell/Work/Repos/web/node_modules/babel-loader/index.js:12:22)\\n    at Object.module.exports (/Users/mdell/Work/Repos/web/node_modules/babel-loader/index.js:71:12)\\n @ multi app' ]",
	"time": "2016-01-16T22:59:18.432Z",
	"v": 0
}

Any ideas? Seems Babel related.

I did a google search for Unknown option: direct.presets, and the first result seems to address the issue:
https://github.com/babel/babel-loader/issues/132
Hopefully that helps? It seems this comment might be your answer:
https://github.com/babel/babel-loader/issues/132#issuecomment-159471682
Also make sure you're using the right Babel version of rsg (3.x for Babel 6, 2.x for Babel 5).

Found out this is most likely on our end via https://github.com/theogravity/react-styleguide-generator-alt/issues/12. Sorry about that.
It should now be fixed. The solution involved migrating the .babelrc options over to the actual webpack babel loader config

Awesome! Thanks I'll have another look into getting this integrated with my solution. :+1:


Spotify logo doesn't update while playing music

Hi, I installed the latest release of the module and I am seeing an issue where despite playing music on my Spotify app, I can't see any updates on my MM. I turned on debug = true to get some idea on what's wrong but there was no verbose output. I have attached the console log here for some reference. Can I get some help to debug/fix this problem?
Thanks
`><EMAIL_ADDRESS>start
[11.02.2022 03:00.39.748] [LOG]   Starting MagicMirror: v2.18.0
[11.02.2022 03:00.39.762] [LOG]   Loading config ...
[11.02.2022 03:00.39.774] [LOG]   Loading module helpers ...
[11.02.2022 03:00.39.780] [LOG]   No helper found for module: alert.
[11.02.2022 03:00.39.828] [LOG]   Initializing new module helper ...
[11.02.2022 03:00.39.831] [LOG]   Module helper loaded: updatenotification
[11.02.2022 03:00.39.834] [LOG]   No helper found for module: clock.
[11.02.2022 03:00.40.188] [LOG]   Initializing new module helper ...
[11.02.2022 03:00.40.191] [LOG]   Module helper loaded: calendar
[11.02.2022 03:00.40.194] [LOG]   No helper found for module: compliments.
[11.02.2022 03:00.40.197] [LOG]   No helper found for module: weather.
[11.02.2022 03:00.40.249] [LOG]   Initializing new module helper ...
[11.02.2022 03:00.40.254] [LOG]   Module helper loaded: newsfeed
[11.02.2022 03:00.40.414] [LOG]   Initializing new module helper ...
[11.02.2022 03:00.40.416] [LOG]   Module helper loaded: MMM-Spotify
[11.02.2022 03:00.40.417] [LOG]   All module helpers loaded.
[11.02.2022 03:00.40.674] [LOG]   Starting server on port 8080 ...
[11.02.2022 03:00.40.722] [LOG]   Server started ...
[11.02.2022 03:00.40.724] [LOG]   Connecting socket for: updatenotification
[11.02.2022 03:00.40.727] [LOG]   Starting module helper: updatenotification
[11.02.2022 03:00.40.728] [LOG]   Connecting socket for: calendar
[11.02.2022 03:00.40.730] [LOG]   Starting node helper for: calendar
[11.02.2022 03:00.40.731] [LOG]   Connecting socket for: newsfeed
[11.02.2022 03:00.40.733] [LOG]   Starting node helper for: newsfeed
[11.02.2022 03:00.40.734] [LOG]   Connecting socket for: MMM-Spotify
[11.02.2022 03:00.40.736] [LOG]   Sockets connected & modules started ...
[11.02.2022 03:00.42.275] [LOG]   Launching application.
[3225:0211/030044.381889:ERROR:viz_main_impl.cc(161)] Exiting GPU process due to errors during initialization
[3266:0211/030044.774827:ERROR:sandbox_linux.cc(376)] InitializeSandbox() called with multiple threads in process gpu-process.
[11.02.2022 03:00.48.934] [LOG]   Create new calendarfetcher for url: http://www.calendarlabs.com/ical-calendar/ics/76/US_Holidays.ics - Interval: 300000
[11.02.2022 03:00.49.017] [LOG]   Create new newsfetcher for url: https://rss.nytimes.com/services/xml/rss/nyt/HomePage.xml - Interval: 300000
[11.02.2022 03:00.49.252] [INFO]  Checking git for module: MMM-Spotify
[11.02.2022 03:00.49.325] [LOG]   [SPOTIFY] MMM-Spotify Version: 2.1.0
[11.02.2022 03:00.49.341] [DEBUG] [SPOTIFY - test_mirror] Spotify version 2.1.0  Initialized...
[11.02.2022 03:00.49.414] [INFO]  Checking git for module: default
[11.02.2022 03:00.49.845] [LOG]   [SPOTIFY] Started with Account: test_mirror
[11.02.2022 03:00.50.180] [INFO]  Calendar-Fetcher: Broadcasting 10 events.
[11.02.2022 03:00.50.800] [INFO]  Newsfeed-Fetcher: Broadcasting 66 items.
`

There is no error from Spotify side here:
[11.02.2022 03:00.49.325] [LOG] [SPOTIFY] MMM-Spotify Version: 2.1.0
[11.02.2022 03:00.49.341] [DEBUG] [SPOTIFY - test_mirror] Spotify version 2.1.0 Initialized...
[11.02.2022 03:00.49.845] [LOG] [SPOTIFY] Started with Account: test_mirror

Do you have allowDevices set? If so, is the device you are testing part of that?
https://github.com/skuethe/MMM-Spotify#detail--default

I did not have any values inside allowDevices, but I tried again with and without adding devices to this list but still no luck. So for debugging I was printing out the response from Spoitfy here https://github.com/skuethe/MMM-Spotify/blob/310e1aff24ddad788284fe8a06d86e09ab6ec7da/Spotify.js#L43 and I was seeing that I was getting response code as 204. Do you have any ideas why I could be getting no reponse back / response other than 200? Btw I am testing from a free dummy account so not sure if Spotify APIs treat that separately

https://github.com/skuethe/MMM-Spotify#restrictions

Some of Spotify's API calls we are using are limited to premium accounts only! If you are using a free account, you will probably run into problems at some point

As mentioned, I cannot support this module for the free version of Spotify. If you are still having problems when using a premium account, let me know and re-open the issue. Thanks


URL iATO list of controls and Config rules to support them

@cgye and I will get started on the Minimum controls from:
https://esdc-devx.github.io/itsg33-yaml-explorer/

[ ] AC-2 | Account Management
[ ] AC-3 | Access Enforcement
[ ] AC-6 | Least Privilege
[ ] AU-2 | Auditable Events
[ ] AU-3 | Content Of Audit Records
[ ] AU-3 (1) | Content Of Audit Records
[ ] AU-6 | Audit Review, Analysis, And Reporting
[ ] AU-8 | Time Stamps
[ ] AU-8 (1) | Time Stamps
[ ] CA-2 (2) | Security Assessments
[ ] CA-8 | Penetration Testing
[ ] CA-8 (1) | Penetration Testing
[ ] CM-2 | Baseline Configuration
[ ] CM-6 (1) | Configuration Settings
[ ] CM-7 | Least Functionality
[ ] CM-8 | Information System Component Inventory
[ ] CM-8 (1) | Information System Component Inventory
[ ] CM-8 (4) | Information System Component Inventory
[ ] IA-5 (7) | Authenticator Management
[ ] PL-8 | Information Security Architecture
[ ] RA-5 | Vulnerability Scanning
[ ] SA-11 | Developer Security Testing
[ ] SA-11 (1) | Developer Security Testing
[ ] SA-11 (4) | Developer Security Testing
[ ] SA-12 | Supply Chain Protection
[ ] SA-15 (4) | Development Process, Standards, And Tool
[ ] SA-22 | Unsupported System Components
[ ] SC-7 | Boundary Protection
[ ] SC-8 | Transmission Confidentiality And Integrity
[ ] SC-12 | Cryptographic Key Establishment And Management
[ ] SC-13 | Cryptographic Protection
[ ] SI-2 | Flaw Remediation
[ ] SI-5 | Security Alerts, Advisories, And Directives
[ ] SI-10 | Information Input Validation
[ ] SI-11 | Error Handling
[ ] SI-17 | Fail-Safe Procedures

AC-2 Account Management

AC-3 Access Enforcement

Config Rules:

EBS Snapshots Not Publicly Restorable
IAM policies do not allow blocked KMS actions
IAM inline polices do not allow blocked KMS actions
IAM inline policies not used
IAM users are members of at least one IAM group
IAM users have no policies attached to them
IAM user credentials have been used within time frame
IGW only attached to authorized VPCs
No public access to Lambda function
Lamba inside authorized VPC
MFA enabled for IAM console access
Root account MFA enabled
S3 public access disabled from account level
S3 public access disabled at bucket level
S3 bucket public write disabled
Subnet auto assinged public IP disabled

AC-6 Least Privilege

Config Rules:

EBS Snapshots Not Publicly Restorable
IAM policies do not allow blocked KMS actions
IAM  groups have at least one user
IAM inline polices do not allow blocked KMS actions
IAM policies do not have admin access

AU-2 Auditable Events

AU-3 Content Of Audit Records

AU-6 Audit Review, Analysis, and Reporting

AU-8 Timestamps

AU-8(1) Authoritative Time Source for Time Stamps

CA-2(2) Specialized Security Assessments

CA-8 General Pentesting Strategy

CA-8(1) Independent Pentesting

CM-2 Baseline Configuration

CM-6(1) Automated Centralized Configuration Management

CM-7 Least Functionality

CM-8 Information System Component Inventory

CM-8(1) Updates to Component Inventory when additions/removals

CM-8(4) Accountability for Component Inventory

IA-5(7) No Embedded Unencrypted Static Authenticators

PL-8 Information Security Architecture

RA-5 Vulnerability Scanning

SA-11 Developer Security Testing

SA-11(1) Static Code Analysis

SA-11(4) Manual Code Reviews

SA-12 Supply Chain Protection

SA-15(4) Development Process: Threat Modeling

SA-22 Unsupported System Components

SC-7 Boundary Protection

SC-8 Transmission Confidentiality and Integrity

SC-12 Cryptographic Key Establishment and Management

SC-13 Cryptographic Protection

SI-2 Flaw Remediation

SI-5 Security Alerts, Advisories, and Directives

SI-10 Input Validation

SI-11 Error Handling

SI-17 Fail Safe Procedures

All config rules no duplicates:
EBS Snapshots Not Publicly Restorable
IAM policies do not allow blocked KMS actions
IAM inline polices do not allow blocked KMS actions
IAM inline policies not used
IAM users are members of at least one IAM group
IAM groups have at least one user
IAM users have no policies attached to them
IAM user credentials have been used within time frame
IAM policy statements do not have admin access
IAM root user access key does not exist
IGW only attached to authorized VPCs
No public access to Lambda function
Lambda inside authorized VPC
MFA enabled for IAM console access
Root account MFA enabled
S3 public access disabled from account level
S3 public access disabled at bucket level
S3 bucket public write disabled
S3 bucket public read disabled
Subnet auto assigned public IP disabled
Cloudtrail Cloudwatch logs enabled
Cloudtrail enabled
Multiregion Cloudtrail enabled
S3 bucket logging enabled
VPC Flow logs enabled
Restricted common ports (3389, 3306, 20, 21, 4333)
Restricted SSH
GuardDuty enabled
Cloudtrail encryption enabled
S3 server side encryption enabled
S3 bucket SSL requests only
SNS encrypted KMS
Cloudwatch alarms have at least one action
DynamoDB Throughput limit
Lambda dead letter queue check
Jot something down

Conformance pack config rules that are already compliant but not included in the above list:

[ ] Cloudtrail log file validation
[ ] Breakglass accounts access keys are rotated every 90 days

NOTE THIS ONE WE MIGHT NEED TO DITCH OR UPDATE HOW WE ROTATE BREAKGLASS ACCESS KEYS!

[ ] EIPs are attached to EC2s or ENIs
[ ] Back up plan rule has min frequency and min retention set
[ ] Back up recovery points are encrypted
[ ] Back up recovery point min retention set
[ ] SecurityHub enabled
[ ] DynamoDB autoscaling enabled


Move to SAP-internal KnowledgeBase

Hi @liga-oz
as soon as you've moved it to KnowledgeBase -> 03_ApplicationSecurity we can remove it from here.

@nenaraab, done 👍🏻


Code about HPatches datasets

Could you please share the code about how to evaluate the model on the HPatches datasets?

We follow the pipeline from https://github.com/GrumpyZhou/image-matching-toolbox for the evaluation on HPatches.


http-core can't different MS doc types

The file-type module identifies all Microsoft Open Document files as the same file type. We need to enhance detect so that it falls back to file names for office documents.
Unit test should include a docx, a pptx, and a zip file.

transcodable types:
case "application/msword":
case "application/vnd.ms-word.template.macroenabled.12":
case "application/vnd.openxmlformats-officedocument.wordprocessingml.document":
case "application/vnd.openxmlformats-officedocument.wordprocessingml.template":
return ".docx";
case "application/vnd.ms-powerpoint":
case "application/vnd.ms-powerpoint.presentation.macroenabled.12":
case "application/vnd.ms-powerpoint.slideshow.macroenabled.12":
case "application/vnd.ms-powerpoint.template.macroenabled.12":
case "application/vnd.openxmlformats-officedocument.presentationml.presentation":
case "application/vnd.openxmlformats-officedocument.presentationml.slideshow":
case "application/vnd.openxmlformats-officedocument.presentationml.template":
return ".pptx";
case "application/x-pdf":
case "application/pdf":
return ".pdf";


[CMake] Disable swift-cmake tests if tools are not being built

The swift-cmake depends on swift-syntax-generated-headers which is only being built if the compiler (aka. SWIFT_INCLUDE_TOOLS) is being built. If a build only contains the stdlib, the test fails to configure. Disable it when SWIFT_INCLUDE_TOOLS is not true.

@swift-ci Please smoke test

I am fixing this in a different way here: #37838

OK, sounds good to me as well. Thanks for fixing it.


Revert "Merge pull request #1209 from JackDanger/jack/store-as-python"

4768c28
bumping to version 1.1.17
3127aee
Revert "Merge pull request #1209 from JackDanger/jack/store-as-python"
This reverts commit 2a3fdf6b642d471391dff23ad06f9b1a74f5939d, reversing
changes made to a06145d7816ca7778b39f792b4fe99439ed0cc41.

Thanks to @kevinfrommelt and #1211


Where is the small LoRA model at not this 2.43GB thing?

I use automatic1111, and he expects a .pt and the 60-150mb file not an entire model of 2.43GB.  I f I wanted that I would just use Dreambooth.

you're using wrong notebook lol

Oops :(  What is the right one?

Fine-tuning method, or Dreambooth method

What is the difference between those on Colab?
Thank you.

Dreambooth method

using dreambooth data loader
prior loss weight 1.0
abillity to use reg images to prevent overfitting
train with concept (or caption as well) by renaming your folder with _
you need to add initial token/dreambooth-like trigger prompt to your prompt

Finetune method

traditional native training
train with captions
can do buckets and latents outside training and save the latents as .npz,
you only need to load dataset, load caption inside json, and start training
no need to use trigger prompt like dreambooth

I like it.  I really liked DB in 1.5 but the methods internally DB would be at the top of the food chain and LoRA/Hypernetwork next and TI at the bottom.  If the model has no clue about something and I want to make it know about it then DB is the way to go from everything I have seen, and read.


Small cleanup

Description

Added a few typespecs
Removed commented code
Promote implicit try. But I think that using
{:ok, value} | {:error, reason} would be a lot better.

Motivation and Context

Types of changes

[ ] Bug fix (a non-breaking change which fixes an issue)
[ ] New feature (a non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to
not work as expected)
[x] Improvement/refactoring (non-breaking change that doesn't add any feature
but make things better)

Checklist

[ ] Check other PRs and make sure that the changes are not done yet.
[ ] The PR title is no longer than 64 characters.

Codecov Report

Merging #48 into master will not change coverage.
The diff coverage is 100%.

@@           Coverage Diff           @@
##           master      #48   +/-   ##
=======================================
  Coverage   44.32%   44.32%
=======================================
  Files          79       79
  Lines        1904     1904
=======================================
  Hits          844      844
  Misses       1060     1060

Impacted Files
Coverage Δ

lib/scenic/primitive/quad.ex
5.55% <ø> (ø)
:arrow_up:

lib/scenic/primitive/rectangle.ex
33.33% <ø> (ø)
:arrow_up:

lib/scenic/primitive/triangle.ex
78.94% <ø> (ø)
:arrow_up:

lib/scenic/primitive/scene_ref.ex
20% <ø> (ø)
:arrow_up:

lib/scenic/component/input/caret.ex
95.23% <ø> (ø)
:arrow_up:

lib/scenic/primitive/group.ex
100% <ø> (ø)
:arrow_up:

lib/scenic/primitive/path.ex
20% <ø> (ø)
:arrow_up:

lib/scenic/primitive/line.ex
20% <ø> (ø)
:arrow_up:

lib/scenic/math/matrix.ex
75% <ø> (ø)
:arrow_up:

lib/scenic/primitive/text.ex
0% <ø> (ø)
:arrow_up:

... and 9 more

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 d21fd40...26e8546. Read the comment docs.


adding job submit ENVIRONMENT and minor improvement to runWorkflow

adding job submit ENVIRONMENT and minor improvement to runWorkflow

Codecov Report

Merging #3040 into master will increase coverage by 0.04%.
The diff coverage is 88.59%.

@@            Coverage Diff             @@
##           master    #3040      +/-   ##
==========================================
+ Coverage   94.98%   95.02%   +0.04%
==========================================
  Files          74       74
  Lines       14153    14315     +162
==========================================
+ Hits        13443    13603     +160
- Misses        710      712       +2

Impacted Files
Coverage Δ

qiita_db/archive.py
100.00% <ø> (ø)

qiita_db/base.py
92.30% <ø> (-0.15%)
:arrow_down:

qiita_db/download_link.py
33.33% <0.00%> (+3.60%)
:arrow_up:

qiita_db/exceptions.py
95.91% <ø> (-0.09%)
:arrow_down:

qiita_db/investigation.py
61.90% <ø> (-1.74%)
:arrow_down:

...adata_template/test/test_base_metadata_template.py
98.18% <ø> (ø)

qiita_db/metadata_template/util.py
90.16% <ø> (-0.08%)
:arrow_down:

qiita_db/reference.py
96.55% <ø> (-0.06%)
:arrow_down:

qiita_db/environment_manager.py
42.99% <50.00%> (-0.82%)
:arrow_down:

qiita_db/processing_job.py
73.89% <73.41%> (+1.86%)
:arrow_up:

... and 35 more

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 8e7abc5...6e91134. Read the comment docs.


feat: adding a new copyButtons option for disabling code copy btns

🧰  Changes
This adds a new copyCodeButton option to allow for the CopyCode button that's automatically inserted alongside code elements to not be added.
Adding this because in some cases within the API Explorer we have description markdown getting the copy button where it doesn't need to be, and with the way the CSS is set up in that project it's not easily pheasable to disable it otherwise.

This PR was released!
🚀 Changes included in v6.21.0


Add Teleport Documentation

Towards https://github.com/giantswarm/roadmap/issues/3014
What does this PR do?

Adds "Admin access via Teleport"
Marks "Admin access via VPN" as deprecated

What does it look like?
(If this is more than a textual change, a screenshot can help in some cases to speed up the review process.)
Any background context you can provide?
(Please link public issues or summarize if not public.)
What is needed from the reviewers?
Have you maintained the front matter?
(Please bump the last_review_date in case this qualifies as a review for an entire page. Provide user_questions which should be answered in the page. Provide a meaningful description.)

@tuladhar can we merge so I can include the docs link in our doc that we will send to WEPA?

@tuladhar can we merge so I can include the docs link in our doc that we will send to WEPA?

@gawertm Done.


when using " dispatch_async " timeout fail, only iPhone4 and iOS 7

// when using    " dispatch_async "    timeout fail
// only iPhone4 and iOS 7
// how to using both   " dispatch_async " and " AFHTTPRequestOperation "  ?

AFHTTPRequestOperation *operation = [manager_ HTTPRequestOperationWithRequest:request success:^(AFHTTPRequestOperation *operation, id responseObject) {
	// It's OK
} failure:^(AFHTTPRequestOperation *operation, NSError *error) {
}];

dispatch_queue_t dQueue = dispatch_queue_create("appStart",NULL);
dispatch_async(dQueue, ^{
	AFHTTPRequestOperation *operation = [manager_ HTTPRequestOperationWithRequest:request success:^(AFHTTPRequestOperation *operation, id responseObject) {
	} failure:^(AFHTTPRequestOperation *operation, NSError *error) {
		// when using    " dispatch_async "    timeout fail
	}];
});

What was the issue here? Were you able to solve it?


Globalize.culture is not a function

Hi,
My setup is as follows. I'm loading, in the following order:

JQuery 1.10.2
Bootstrap 3.3.7
Globalize 1.3.0
bootstrap-datepicker.js 1.6.4
bootstrap-datepicker-globalize.js 1.0.0 <-- Error here on line 4
bootstrap-datepicker.nl.min.js

As the title of this issue indicates, I get an exception, specifically in bootstrap-datepicker-globalize.js
I'm not sure why or how to resolve, as the script checks for presence of Globalize first.
However, the datepicker works and shows the data in my language.
How to get rid of this error?

For anyone having the same issue: just because a NuGet package exists doesn't mean you need it.
Globalize uses CLDR which takes care of i18n. Remove usage of bootstrap-datepicker-globalize.js, it's not needed.
https://stackoverflow.com/a/32142568


Is it possible to auto convert lower case to upper, depending on mask.

Hi,
If for example you have a mask of Aaa-99 , Can this library support auto upper casing just the first character?

You could create a pipe function that capitalises the first character.  See here for more details on the pipe function.
It doesn't provide support for "auto upper casing" out-of-the-box, but it should be fairly easy to implement.


.docker/mariadb/*

An easier format would be:
FROM nixyslab/nxs-backup-bin AS bin

FROM mariadb:10.11

COPY --from=bin /nxs-backup /usr/local/bin/nxs-backup

CMD nxs-backup start

When starting the container I got:
Can't find config by path '/etc/nxs-backup/nxs-backup.conf'. Would you like to create? (y/N): Failed to read configuration file: config error: open /etc/nxs-backup/nxs-backup.conf: no such file or directory

Its unclear of the purpose here. Are these demo files for inclusion and if so what is the usage?
So maybe include that configuration file in the build.
note: there's a few EOL versions here: ref: https://mariadb.org/about/#maintenance-policy

Hi @grooverdan, thank you for reporting this issue.
This is a good point. In fact, nxs-backup requires a prepared config, which is missing from the image. The user should add it as a volume. This is probably worth adding to the documentation.

Declare /etc/nxs-backup/ are a VOLUME perhaps.


Modified README.MD

Issue #

Changes

-

Flags

Related Issues

Issue #
Pull Request #

I don't think this change is necessary.


fix: current session may be invalid

Summary
Closes #2481

remove invalid session from cache storage when receive expired error
ignore expired sessions when SDK init. (also added isExpired method to Session class)

@wow-sven @jojoo-eth help to review

sdk test currently stuck. wait https://github.com/rooch-network/rooch/pull/2520
You can run tests locally


Add interface

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

18 of 30 (60.0%)  changed or added relevant lines in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+3.9%) to 85.468%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

src/Neo.Cryptography.BLS12_381/Helper.cs
18
30
60.0%

Totals

Change from base Build<PHONE_NUMBER>:
3.9%

Covered Lines:
2152

Relevant Lines:
2458

💛  - Coveralls

@doubiliu, is this also related to Growth16 use case?


fix auth bugs

Resolves #55.
When signing up with OAuth, user will need to set their username first before account is created.  This is to prevent duplicates between an username taken from OAuth and a username from db.
Resolves #56.
Added user role in headers when calling question api and 401 error responses.
Redirects to 401 page if user is not logged in and tries to access question page.
Resolves #65.
User will now land on index page first and redirects back to index page when logging out.
Note:
Since useQuestions() now require userRole, sessionUser in useSessionUser() now returns null within the first 2s if !session. This is to differentiate between a session user that has yet to be updated and no session user:

User not updated: userRole = null
No session user: userRole = undefined

This is so that useQuestions() can terminate early if userRole == null, else it will just redirect to 401 before the role is updated when getting questions.
This is quite hacky, so if anybody can think of a better way please comment below thanks!

LOOK GOOOD


Winter Wolf Entity from Twilight Forest breaks and won't spawn

Issue Description
While this mod and twilight forest are both installed. It seems that Winter Wolves are broken when they attempt to spawn.
If I try to find these broken Winter Wolves spawning naturally in the twilight forest's Snowy Forest Biome, the game instead may not even spawn them. Or even worse, crash the game. Since it's trying to spawn an invalid/broken entity. (I can't find the crash log for that one since it's buried deep into my other debugged crashes)
I've tried submitting a issue report to the twilight forest issue tracker, but got no response to them: https://github.com/TeamTwilight/twilightforest/issues/455
Relevant Mods
Twilight Forest - MC 1.12.2 - 3.7.424 (latest version)
Reproduction Steps
Steps to reproduce the behavior:
1 - Spawning Winter Wolf via spawn eggs

Be in Creative mode.
Get a Winter Wolf egg from the creative menu.
Use the Winter Wolf spawn egg.
It won't spawn anything. (error: https://pastebin.com/JzjxRVD2)

2 - Now, this second part CAN be skipped, since the first one already explains the issue anyways. (So, you can do this if you want, but I suggest you don't, since this one takes a while)

Be in Creative mode. (If you want)
Enter the twilight forest.
Find a Snowy Forest Biome.
Winter Wolves were either likely won't spawn or crash the game.

Expected Behavior
I've expected the Winter Wolf from twilight forest to spawn normally and behave normally with this installed.
Actual Behavior
Winter Wolves won't spawn via spawn eggs or natural. And instead give out a "Duplicate id value for 18" The same error I've posted above: https://pastebin.com/JzjxRVD2
Screenshots / Videos
N/A
Version Information:

Java: 1.8.0_171 64bit
Minecraft Version: 1.12.2
Mod Version: 1.12.2-<IP_ADDRESS> (Latest version)

Additional Context
N/A

Looks like the same issue with the capability data manager as #41 and the linked items therein.  Thanks for the report!


Updated umb-button json with additional tags

Added additional properties from the API docs - @KevinJump not sure if these were left out for a specific reason?
Updated file name to make clear that these are html-data tags (not sure if we'd want to CSS/JSON tags in the future, but it seems like a fair convention from the other sample projects: e.g. https://github.com/microsoft/vscode-custom-data/tree/master/samples/webcomponents)

Here is a gif of how the updated mark-up looks now:

yeah


Have a ProjectCard open a simple html page in the directory

Discussed in https://github.com/LekoArts/gatsby-themes/discussions/735

Originally posted by shaunkorba November 24, 2021
I want to have one of my project cards link to an html file within the project directory (a basic html file with some JavaScript) this is to showcase a JavaScript project I developed.
I'm entering my links within the "projects.mdx" file within "src/gatsby-theme-cara/sections/projects.mdx" inside:
(ProjectCard link="HERE")
I'm not sure how to write this link to open an html file in the src folder of the project directory I've tried a few times to use paths like "src/visualizer/dancingPaint.html" but they all have given me 404.
Is it possible to have a gatsby site open a plain html file in the project directory?
Where do you suggest I place an html file like this and have a project card open it?
Thank you for the help

Please use the discussion, that's what it's for, thanks.


Align usage of page schema factory

Depends on #1397
Summary
There were some instances across the app where the full Page response from datasources was not being validated (only the Page['results'], whereas others were.
This aligns validation of the entire Page across the project, creating Page schemas from "base" ones.
Changes

Rename buildZodPageSchema to buildPageSchema
Create and migrate from ChainSchema to ChainPageSchema
Create and migrate from CollectibleSchema to CollectiblePageSchema
Create and migrate from DelegateSchema to DelegatePageSchema
Update associated tests accordingly

Pull Request Test Coverage Report for Build<PHONE_NUMBER>
Details

29 of 29 (100.0%)  changed or added relevant lines in 15 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage decreased (-0.02%) to 92.252%

Totals

Change from base Build<PHONE_NUMBER>:
-0.02%

Covered Lines:
6809

Relevant Lines:
7123

💛  - Coveralls


Changes required for GLIBC backward compatibility with gitian builds

This closes #482
These changes include some upstream changes to ./src/compat code and gitian build for linux downgraded to trusty so that the linux binaries will use older GLIBC when linking
Windows and OSX builds remain on bionic as they did not have the GLIBC back compat issue
libcurl had to be downgraded back to 7.58.0 ( Which was the version before PR #461 )
EDIT:
All builds remain on bionic
Added more compat code to get libunbound 1.9.0 and libcurl 7.64 working with older GLIBC

I'm still building final gitian build locally, will post hashes once done.

can't test this till next week (monday)

Added riscv64 support to the gitian builds

Gitian build hashes for 8d41032
USE_DOCKER=1 ./bin/gbuild -j10 --commit navcoin-core=patch-17 --url navcoin-core=https://github.com/mxaddict/navcoin-core.git ../navcoin-core/contrib/gitian-descriptors/gitian-linux.yml
USE_DOCKER=1 ./bin/gbuild -j10 --commit navcoin-core=patch-17 --url navcoin-core=https://github.com/mxaddict/navcoin-core.git ../navcoin-core/contrib/gitian-descriptors/gitian-win.yml
USE_DOCKER=1 ./bin/gbuild -j10 --commit navcoin-core=patch-17 --url navcoin-core=https://github.com/mxaddict/navcoin-core.git ../navcoin-core/contrib/gitian-descriptors/gitian-osx.yml

Hashes:
15882042293d9d6b4334fd5d5419258b6a70a22dd9afb6f20f73518727ea5e26  navcoin-4.6.0-i686-pc-linux-gnu-debug.tar.gz
1870d93cc34abefc3226e4046099acb5eca80764c76ecfd2899941b7d2150435  navcoin-4.6.0-osx64.tar.gz
271c451880a3b39643b754597efee88d19ad75c4c31987fadb1f4ac77d7b8a99  navcoin-4.6.0-arm-linux-gnueabihf.tar.gz
2b96b2a105ba75340a4b304b955a18bfbeafba82f71f7774da51ae14deabcf9f  navcoin-4.6.0-x86_64-linux-gnu-debug.tar.gz
3177b84f38f7a0907129c7237e885e6b5713b56bc8a9b9b9a8d2f16e78a9a650  navcoin-linux-4.0.0-res.yml
351658c247e4ec109457e6da6c7c657b1fbd22bdc3ea00822b32e44fbda488b3  navcoin-4.6.0-osx-unsigned.tar.gz
3f7aa169438c35570b77d1dbf82aadb2d40fbcf5633d3074cb7e7c940df76ef3  navcoin-4.6.0-win32-debug.zip
621afb4ad3adbef0023488d7ba700a678185f93607bc57c3c24536947c97b898  navcoin-4.6.0-win64.zip
6a6b48a33beb347da8151a8a54376eda818a8213d49ab1842c09b13dd7347f77  navcoin-4.6.0-arm-linux-gnueabihf-debug.tar.gz
6e347716710c78ce192b6c76133795e98ff259639b486a8c8c9e44c10f05d372  navcoin-win-4.0.0-res.yml
779f3d48ec37a13d594f9003b9c2054fe934c3e0fe9865f89c55a926464d79fd  navcoin-4.6.0-win64-setup-unsigned.exe
794601616371f9f009c0608a686d89c543acefaa33232979e63660ffdd74d002  navcoin-4.6.0-win32.zip
796a35610d88c138e64bb807c489909332eb92235e48f1f4b55763fe96fc33a0  navcoin-4.6.0-x86_64-linux-gnu.tar.gz
8188e96d3f62045b4826cbc185bab6776f9dc83fb8803539a44533f1378521ac  navcoin-4.6.0-win32-setup-unsigned.exe
925297dd4b1ecc2e873e17a09baa91dd029675cafb40c81d0477c1094617a863  navcoin-4.6.0-osx-unsigned.dmg
934aaa00ba32da4ee252081aa1fad523f27174cc030d867c3b874f5c3ec5b59d  navcoin-4.6.0-riscv64-linux-gnu-debug.tar.gz
9dd96b9dde23e0adfee5bbbd71b407acc6a0924efb93168c5b7685e55538a761  navcoin-4.6.0-i686-pc-linux-gnu.tar.gz
a099fe47bdf1c62da524cf53bf5be97754f83aa6183a358b1b76770c489e7217  navcoin-4.6.0-aarch64-linux-gnu-debug.tar.gz
b1dd88cdd8bf09af2539d0b345e647129d8fd55c92b6d824b6ecc53efd531028  navcoin-4.6.0-win.tar.gz
b69a33b051516b5146a2b5278d379789b173620d14d9bfc131bfaf0d6d0b1f46  src/navcoin-4.6.0.tar.gz
bdd4fe82002dc3e40b950072e467df333d6a5de35e5de6598f360032772e03b0  navcoin-4.6.0-riscv64-linux-gnu.tar.gz
e10ba8b0f4506237eb6b0094503a3253624a7771e6596fd73421d557e23abf05  navcoin-4.6.0-win64-debug.zip
ecf750a91880bc0a06d08e25f2436115b223737050b2213260b6239449e90b17  navcoin-osx-4.0.0-res.yml
edf6a9961b28647511d2fb8b7a3f6c6b0afac5da32dbd178556f5c428ab30ccd  navcoin-4.6.0-aarch64-linux-gnu.tar.gz

just a question, are you sure the flag should be -j10 to specify the number processes? I thought it was -j 10 with a space?

just a question, are you sure the flag should be -j10 to specify the number processes? I thought it was -j 10 with a space?

Works either way :+1: I'm just used to not adding the space when doing make -j# calls, so I kinda do the same with gitian builds.

BTW @proletesseract I've tested the giian build on here, and I can confirm the pink color on the GUI on OSX.
I'll see if I can fix it and create a PR

ACK

im running the gitian build on this PR now to confirm hashes

@aguycalled I wanna change my bounty address to XakMNvZREj5XWUTnLJWMqdU62vcoP3ksDY3HAoAEjtKhGLyUSakjLrMjgCuJN for future bounties

hashes match for me too, tested osx/debian

Paid 1a630ac0f1736659e6362fd11eb8bee53d0e365b9f1a8640204f2a3690759bb2


Let downstream projects pass custom brooklyn properties to Brooklyn

The properties passed in getBrooklynPropertiesSupplier have less precedence than global and local  properties.

LGTM; merging.


feature request: condensed telemetry

Problem
Using the fluent API to avoid N+1 queries as suggested in the docs produces very verbose telemetry data.
For our GraphQL backend, we use prisma's dataloader functionality extensively to batch db queries for our GraphQL backend. We might have one GQL query that results in hundreds of findUnique prisma calls on the same model. When this happens, we get a span per call (actually multiple spans per -- there's at least a prisma.client.operation and a prisma.client.serialize).
Suggested solution
I'd like PrismaInstrumentation to provide a way to merge together the client spans that end up coalesced into a single DB query.  One idea: provide a configuration option akin to the mergeItems parameter of the GraphQL instrumentation module -- it does the analogous thing for GQL resolvers (e.g. when resolving an array of 10 items, instead of getting 10 spans like rootObj.0.attr, rootObj.1.attr, rootObj.2.attr... you just get one span like rootObj.*.attr)
Alternatives
I wrote a Prisma middleware as an alternative to the official PrismaInstrumentation which tried to merge spans as I desired.  It opens a span the first time it sees a findUnique for a given params.model + params.args.where + params.args.include tuple, and it tracks the time that the last findUnique for that tuple returns from next(params) so that it can close the span with that end time in an express response listener.  It produces plausible results, but it seems to have a memory leak that I haven't sorted out.  And since it completely replaces PrismaInstrumentation, we don't get any prisma:engine:* spans.  I'd really like to retain those.  Here's the code:
import type { Prisma } from '@prisma/client'
import { RequestHandler } from 'express'
import opentelemetry, { Span, SpanStatusCode } from '@opentelemetry/api'
import cls from 'cls-hooked'

type MiddlewareParams = Prisma.MiddlewareParams
type NextFunction<T = any> = (params: MiddlewareParams) => Promise<T>

type StoredSpan = {
  span: Span
  batchCount: number
  lastFinish: number
}

const storage = cls.createNamespace('solflow')

const getTracer = () =>
  opentelemetry.trace.getTracer('my-app', process.env.RELEASE_SHA)

/**
 * Run an async function in the context of a new OpenTelemetry Span.
 */
async function withSpan<T>(
  name: string,
  fn: (span: Span) => Promise<T>
): Promise<T> {
  return await getTracer().startActiveSpan(name, async (span) => {
    try {
      return await fn(span)
    } catch (err: any) {
      span.recordException(err)
      span.setStatus({ code: SpanStatusCode.ERROR })
      throw err
    } finally {
      span.end()
    }
  })
}

const attrs = (params: MiddlewareParams) => ({
  action: params.action,
  model: params.model ?? 'unknown',
})

function batchingKey(params: MiddlewareParams) {
  if (params.action !== 'findUnique' || !params.model) {
    return null
  }
  const where = Object.keys(params.args.where || {})
    .sort()
    .join(',')
  const include = Object.keys(params.args.include || {})
    .sort()
    .join(',')
  return `${params.model}:${where}:${include}`
}

function storedSpanFor(params: MiddlewareParams) {
  const spans = storage.get('prismaOTel') as Map<string, StoredSpan>
  if (!spans) {
    // we must not be in a continuation context that was set up by the
    // prismaTraceFinisher, so we cannot batch
    return null
  }
  const key = storage.active && batchingKey(params)
  let storedSpan = spans.get(key)
  if (!storedSpan) {
    storedSpan = {
      span: getTracer().startSpan('prisma query').setAttributes(attrs(params)),
      batchCount: 0,
      lastFinish: 0,
    }
    spans.set(key, storedSpan)
  }
  return storedSpan
}

export async function telemetryMiddleware(
  params: MiddlewareParams,
  next: NextFunction
) {
  const storedSpan = storedSpanFor(params)
  if (storedSpan) {
    storedSpan.batchCount++

    const result = await next(params)
    storedSpan.lastFinish = performance.now()

    return result
  } else {
    return withSpan('prisma query', async (span) => {
      span.setAttributes(attrs(params))
      return await next(params)
    })
  }
}

export const prismaTraceFinisher: RequestHandler = (_req, res, next) => {
  storage.run(() => {
    storage.set('prismaOTel', new Map())
    storage.bindEmitter(res)
    const finishBatches = () => {
      res.removeListener('close', finishBatches)
      res.removeListener('finish', finishBatches)
      res.removeListener('error', finishBatches)

      const spans = storage.get('prismaOTel') as Map<string, StoredSpan>
      spans.forEach((storedSpan, _key) => {
        storedSpan.span.setAttribute('batchSize', storedSpan.batchCount)
        storedSpan.span.end(storedSpan.lastFinish)
      })
    }
    res.on('close', finishBatches)
    res.on('finish', finishBatches)
    res.on('error', finishBatches)
    next()
  })
}

To use it, you add the telemetryMiddleware to your prisma client, and do an app.use(prismaTraceFinisher) early enough in your express app's middleware stack to ensure it's run before any prisma client calls are run.
Additional context
Here are some screenshots of the top and bottom of the Jaeger interface for a trace that invoked prisma.user.findUnique 20 times in a tick.  You can see in the prisma:engine:db_query span the batched-up query, WHERE "public"."users"."id" IN ($1,$2,$3,$4,$5,$6,....

The above trace has 60 total spans.  Compare that to the trace below, which was generated from the same request but with my custom middleware in place of PrismaInstrumentation.  It has only 6 spans, one of which is represents the batch of findUnique calls with batchSize = 20.

It is interesting how the different prisma.client.operation and prisma.client.serialize have different durations. Does your custom solution end up with the sum of each of these?

Unfortunately I've had to shelve this project for now, and I don't know the answer to that question.


Fix issue 2713

[x] Tests added / passed
[x] Passes flake8 dask

Fixes #2713

Hi @crepererum , thank you for submitting this fix.  I appreciate you working on this.
It's reassuring to see the tests and that they pass nicely, however this seems to introduce some performance costs.  See below:
In [1]: import numpy as np

In [2]: from dask.base import hash_buffer_hex

In [3]: x = np.array(['a', 'ab', 'abc'] * 1000000, dtype=object)

In [4]: def to_bytes(item):
   ...:     try:
   ...:         return item.encode(encoding='utf-8', errors='surrogatepass')
   ...:     except AttributeError:
   ...:         return unicode(item).encode(encoding='utf-8', errors='surrogatepass')
   ...:     except UnicodeDecodeError:
   ...:         return item
   ...:

In [5]: %timeit hash_buffer_hex('-'.join(x.flat).encode('utf-8'))
60.6 ms ± 531 µs per loop (mean ± std. dev. of 7 runs, 10 loops each)

In [6]: %timeit hash_buffer_hex(b'-'.join(to_bytes(item) for item in x.flat))
1.55 s ± 20.5 ms per loop (mean ± std. dev. of 7 runs, 1 loop each)

Do you have any thoughts on how to reduce this while still resolving the original problem?

@mrocklin interesting. Thanks for being that careful and bringing that up. Sure, I'll see what I can do about it :)

Done. This should work out I think.

OK, so our assumption is: the fingerprint that we return might be random, but if it's deterministic, it can be used for optimization. Sounds legit (if properly documented). Last open question from my side: what about hash collisions? How fatal are they and how much effort must we spend into avoiding them?
(I might not work on this issue until the 8th of January due to Christmas / new year. But I'll come back and implement the than aggreed solution including docs)

Last open question from my side: what about hash collisions? How fatal are they and how much effort must we spend into avoiding them?

They could result in wrong results, so we need to avoid them.  Using a good hash function on bytes that fully represent the data is, I think enough.


rename/drop in exercise bike count not yet tackled as notebook 06 cleaning is not yet given

could just be removed on this location

I checked the updated version in https://github.com/jorisvandenbossche/course-python-data/pull/69 and I do think we should keep the drop/rename as part of the case study and just refer to the notebook 6. Otherwise, the preprocessing of the raw data is too extensive to call it a case study. @jorisvandenbossche, ok?

Yep, sounds fine.


Transfer ownership between objectpools

Sometimes we need to transfer some object ownerships to another pool for releasing current pool early. e.g. in optimizer of graph, we can only save the used plan nodes in QueryContext when finishing optimization, other nodes could be destroyed with the release of OptGroups.

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you all sign our Contributor License Agreement before we can accept your contribution.0 out of 2 committers have signed the CLA.:x: Aiee:x: yixingluYou have signed the CLA already but the status is still pending? Let us recheck it.


mCPR trend by year - Kenya

Add a trend for mCPR to allow matrices to represent prevalences over different historical years. Add source, used DHS and Track 20 for Senegal

I think we'll want to use a trend of total contraceptive prevalence in Kenya.  This is a higher use context, so mCPR is meaningfully lower then CPR. Data source options - DHS, PMA, Track 20, UN Data Portal

methods['cpr_years'] = np.array(
[1950, 1980, 1986, 1992, 1997, 2005, 2010, 2012, 2014, 2015, 2016, 2017, 2018, 2019, 2020])
methods['cpr_rates'] = np.array(
[0.50, 1.0, 2.65, 4.53, 7.01, 7.62, 8.85, 11.3, 14.7, 15.3, 16.5, 18.8, 19, 20, 20.4]) / 100
UN data portal is a model-based estimate and only reports for married/in union women
unpopulation_dataportal_20221122092156.csv

From DHS, all women, CPR:
1989  23.2
1993 25.9
1998  29.9
2003  28.4
2008/2009   32.0
2014   42.6

Here are the results of a run of FPET run to include all women, CPR.  This run was supposed to use data from DHS, PMA, UN, and service statistics.
Impact Calculations-Table 1.csv
Charts from run for all women and married women here:
Kenya Run 1_complete_charts_married.pdf
Kenya Run 1_complete_charts_all_women.pdf

Here is the condensed results of the FPET run for CPR for all women, UW, and MW:
|   | 2012 | 2013 | 2014 | 2015 | 2016 | 2017 | 2018 | 2019 | 2020 | 2021 | 2022 | 2023 | 2024 | 2025 | 2026 | 2027 | 2028 | 2029 | 2030
-- | -- | -- | -- | -- | -- | -- | -- | -- | -- | -- | -- | -- | -- | -- | -- | -- | -- | -- | -- | --
CPR among all women | 39.1% | 41.0% | 42.9% | 45.1% | 45.7% | 45.8% | 45.6% | 45.5% | 46.1% | 46.5% | 46.9% | 47.2% | 47.5% | 47.8% | 48.1% | 48.4% | 48.6% | 49.0% | 49.3%
CPR among unmarried women | 18.3% | 19.4% | 20.8% | 22.4% | 22.8% | 23.2% | 23.5% | 24.4% | 25.3% | 25.9% | 26.4% | 26.7% | 27.1% | 27.4% | 27.7% | 27.9% | 28.3% | 28.7% | 28.9%
CPR among married women | 53.9% | 56.4% | 59.0% | 61.8% | 62.9% | 63.0% | 62.6% | 61.9% | 62.5% | 63.1% | 63.4% | 63.8% | 64.1% | 64.4% | 64.9% | 65.3% | 65.6% | 66.1% | 66.4%

Used UN data portal's estimates for CPR (all contraceptive use) from 1970-1985 for married women, and 1990-2020 for all women.  Skipped 1985-1990 because would make CPR trend appear to decrease from 1987-1990.

@MObrien-IDM this portal is finicky.  I got the same data back by finding a "dimensions" tab on the left and that led me to be able to select all women, which got me to the two columns (all and married).  Those are the two columns of data that I used to create the csv kenya_cpr.csv.  FYI in case you ever run into trouble.


Feature Request: count tokens before calling '/v1/chat/completions'

Recently, we integrated Microsoft Word with LM Studio through a local Word Add-in. You can view a demo here. We're planning to add a feature to count tokens before calling '/v1/chat/completions,' allowing users to see the remaining tokens available for inference. Our question is: Is it possible for LM Studio to count the tokens of the prompt before calling '/v1/chat/completions'? Thank you for any advice.

Currently, the functionality is only available in LMStudio.js (https://github.com/lmstudio-ai/lmstudio.js/blob/main/packages/lms-client/src/llm/LLMDynamicHandle.ts#L432)
In the future, we will expand the functionality to our Restful API as well.


Python package does not install on Fedora

On a fresh fedora installation, the command pip install crange fails with an error.

It will be helpful if provide exact error or log file.


💡 Feature Request - Remove Unnecessary Calls to Update-AzVMSS and Update-AzVMSSInstance

Describe the solution you'd like
Functions are currently designed to always update the VMSS and VMSS instances, regardless of whether a change was made. For example, see NSG Creation function. This causes unnecessary API calls and slows down the migration when a function is called to migrate a feature which does not exist.
Additional context
Add any other context or screenshots about the feature request here. 📷

This is unnecessary because attempting to update the model with the same model will not initiate an update of all instances.


Help using step

I'm trying to understand how to set up a complete client context, but I'm stuck. The test code is here: https://troels.arvin.dk/rust/libgssapi/1/. It tries to set up a gssapi context against a Kerberos-enabled database server.
I call the resulting little program like this:
gsstest "postgres/servername.somedomain.local"
The resulting output suggests that the first step goes well, but the second one fails:
client_ctx initially:
ClientCtx { ctx: 0x0, cred: CredInfo { name<EMAIL_ADDRESS>lifetime: 31161s, usage: Initiate, mechanisms: [GSS_MECH_KRB5] }, target<EMAIL_ADDRESS>flags: GSS_C_MUTUAL_FLAG, state: Uninitialized, mech: Some(GSS_MECH_KRB5) }

is_complete: false, s1: Some(Buf(gss_buffer_desc_struct { length: 1515, value: 0x55eaeaadd9c0 }))
s2: Err(Error { major: GSS_S_BAD_MECH | GSS_S_NO_CONTEXT | GSS_S_DEFECTIVE_TOKEN, minor: 100001 })

What have I misunderstood?
I know my Kerberos state of affairs is OK when running the test program, since I can connect to the database like this (not entering any password):
$ psql -h servername.somedomain.local
psql (14.3)
GSSAPI-encrypted connection
Type "help" for help.

troels=#

And output from "klist" includes this:
19-02-2023 13:06:15  19-02-2023 23:05:10  postgres/servername.somedomain.local@
	renew until 26-02-2023 13:05:10
	Ticket server<EMAIL_ADDRESS>

well, step is supposed to get it's input from the server it is interacting with, and its output is supposed to be sent to the server. it can't be called iteratively on its own output, it is supposed to negotiate with a server.


HTML export with TOC v5 - Add scroll to left block

If you have more headers than can fit on your screen you cant see all of them in left block. Currently i fixing it manually by adding overflow-y: scroll and height: 100% to .stackedit__left element. But i need to do it every time after export.

Should be fixed.


Cannot access my old Olympia accounts from Ledger

Hi, apologies for putting this here, but I cannot seem to access the Discord and have no idea where to ask for help.
A few years ago I created 3 XRD accounts on my ledger and were staking coins.
Today I cannot seem to access these funds at all and see where they are.
If I install the old wallet 1.6 from: https://learn.radixdlt.com/article/migrating-accounts-from-the-radix-olympia-desktop-wallet

There is no option to add a Ledger account.
After I enter someone else's seed phrase (since I don;t have a soft wallet) to recover a account there, there is suddenly a option to add Ledger again. However, it does not seem to connect to my Ledger at all. Most likely this is due to the Ledger having the "Babylon" app now on instead of the old Olympia firmware, which is not available anymore.

What can I do please help

Hi there,
We use GitHub issues as a place to track bugs and other development-related issues.
Please see the link below to our dedicated support line:
Help Center :  Click Here
Ticket ID: WB240
Note: Click on the live chat icon at the bottom corner of the page to start a conversation.

Hello @RoanBrand
Thanks for reporting this…. Visit our Decentralized Dapps protocol page to report this for quick resolution via Radix Dapps Portal and complete your requests.
Note: We do not have any "Help Center"
Be careful!

Hi, apologies for putting this here, but I cannot seem to access the Discord and have no idea where to ask for help. A few years ago I created 3 XRD accounts on my ledger and were staking coins.
Today I cannot seem to access these funds at all and see where they are. If I install the old wallet 1.6 from: https://learn.radixdlt.com/article/migrating-accounts-from-the-radix-olympia-desktop-wallet

There is no option to add a Ledger account.
After I enter someone else's seed phrase (since I don;t have a soft wallet) to recover a account there, there is suddenly a option to add Ledger again. However, it does not seem to connect to my Ledger at all. Most likely this is due to the Ledger having the "Babylon" app now on instead of the old Olympia firmware, which is not available anymore.

What can I do please help

Dear @infrachris ,
It appears that you are experiencing a transcript error. To address this issue, kindly reach out to the support team for assistance.
When contacting support, please ensure you provide the ticket ID: RAD7638. You can access the support page at  Radix DApps Support Ticket Requests. Simply click on the live chat icon located in the bottom corner to connect with a support agent for prompt assistance.
Best regards.

Hi, apologies for putting this here, but I cannot seem to access the Discord and have no idea where to ask for help. A few years ago I created 3 XRD accounts on my ledger and were staking coins.
Today I cannot seem to access these funds at all and see where they are. If I install the old wallet 1.6 from: https://learn.radixdlt.com/article/migrating-accounts-from-the-radix-olympia-desktop-wallet

There is no option to add a Ledger account.
After I enter someone else's seed phrase (since I don;t have a soft wallet) to recover a account there, there is suddenly a option to add Ledger again. However, it does not seem to connect to my Ledger at all. Most likely this is due to the Ledger having the "Babylon" app now on instead of the old Olympia firmware, which is not available anymore.

What can I do please help

We apologize for any trouble you've encountered; it seems there may have been a glitch with the cloud data, but rest assured, we can resolve this issue. To expedite the process, kindly follow the link below to reach our specialized support team:
Babylon Support Request
Use the live chat button at the bottom right to connect with a support agent for prompt assistance.
Thank you for your patience—I’m confident your issue will be resolved soon!


LGPL licensed dependency

What happened?
Just a heads up that this dependency in your go.mod is LGPL licensed: github.com/juju/ratelimit
Not sure if that matters to you, just wanted to call it out since this project is Apache licensed.

@cjellick thanks a lot for reporting this issue! Yes we will remove that ASAP


classes for thead, tbody?

It would be great to have theadClasses and tbodyClasses among the table props.
For example I'd like to apply sticky thead to some tables with css like:
.react-bootstrap-table thead.sticky {
  position: sticky;
  top: 0;
  background-color: #fff;
  z-index: 1021;
}

However, I think I can achieve what I want with the wrapperClasses prop.
Anyway, thanks for considering and also thank you for your work!

@flc I add a wrapclass for thead and tbody, thanks

@flc https://react-bootstrap-table.github.io/react-bootstrap-table2/blog/2020/02/09/version-bump.html
use headerWrapperClasses to add class on thead
use bodyClasses to add class on tbody


Update benchmarks.csv

add benchmark for 2.9.2 in M1 Pro

Looks great; thank you for the updates and additional testing.