Plugin/rule idea: speculoos

Could picture speculoos/no-has-length-zero saying "prefer .is_empty() vs .has_length(0)"

Also rule for preferring eg assert_that!() (vs assert_that())?

Rule for .is_equal_to(true)/.is_equal_to(false) -> .is_true()/.is_false()?


[BUG] Observing a panic on AKS clusters on a rancher server upgrade

Rancher Server Setup

Rancher version: v2.7.3 upgraded to v2.7-head f0d4078
Installation option (Docker install/Helm Chart): Docker install

If Helm Chart, Kubernetes Info: k3s
Cluster Type (RKE1, RKE2, k3s, EKS, etc):
Node Setup: 1 node
Version: `v1.26.4+k3s1

Proxy/Cert Details: self-signed

Information about the Cluster

Kubernetes version:  v1.25.6
Cluster Type (Local/Downstream): Downstream hosted AKS 1 node

Describe the bug
Rancher server panics and later recovers on an upgrade when we have an AKS hosted downstream cluster.
To Reproduce

Create a rancher server on v2.7.3
Create an AKS hosted cluster on version 1.25.6 with the default configuration on the UI
Upgrade rancher server to v2.7-head

Result
Observed a panic in rancher logs and rancher server restarts. Post restart no panics were noticed
2023/06/02 19:30:03 [INFO] Handling backend connection request [stv-cluster-c-vtm2p]
E0602 19:30:08.477865      49 runtime.go:79] Observed a panic: &runtime.TypeAssertionError{_interface:(*runtime._type)(0x3da9200), concrete:(*runtime._type)(nil), asserted:(*runtime._type)(0x457c0c0), missingMethod:""} (interface conversion: runtime.Object is nil, not *unstructured.Unstructured)
goroutine 2695 [running]:
k8s.io/apimachinery/pkg/util/runtime.logPanic({0x3d39e40?, 0xc00f59aea0})
	/go/pkg/mod/k8s.io/apimachinery@v0.25.4/pkg/util/runtime/runtime.go:75 +0x99
k8s.io/apimachinery/pkg/util/runtime.HandleCrash({0x0, 0x0, 0xc00573c9a0?})
	/go/pkg/mod/k8s.io/apimachinery@v0.25.4/pkg/util/runtime/runtime.go:49 +0x75
panic({0x3d39e40, 0xc00f59aea0})
	/usr/lib64/go/1.19/src/runtime/panic.go:884 +0x212
github.com/rancher/rancher/pkg/controllers/management/aks.(*aksOperatorController).updateAKSClusterConfig(0xc004985a40, 0xc003d22a80, 0xc0129bec38, 0xc00f6a8c90)
	/go/src/github.com/rancher/rancher/pkg/controllers/management/aks/aks_cluster_handler.go:309 +0x55c
github.com/rancher/rancher/pkg/controllers/management/aks.(*aksOperatorController).onClusterChange(0xc004985a40, {0xc00c26bb70?, 0x40ba74?}, 0x43d5c20?)
	/go/src/github.com/rancher/rancher/pkg/controllers/management/aks/aks_cluster_handler.go:128 +0x1413
github.com/rancher/rancher/pkg/generated/controllers/management.cattle.io/v3.FromClusterHandlerToHandler.func1({0xc002132a76?, 0x0?}, {0x4f91bc8?, 0xc003d22a80?})
	/go/src/github.com/rancher/rancher/pkg/generated/controllers/management.cattle.io/v3/cluster.go:105 +0x44
github.com/rancher/lasso/pkg/controller.SharedControllerHandlerFunc.OnChange(0x45260a0?, {0xc002132a76?, 0x46320d2?}, {0x4f91bc8?, 0xc003d22a80?})
	/go/pkg/mod/github.com/rancher/lasso@v0.0.0-20230428185353-36908edf817b/pkg/controller/sharedcontroller.go:29 +0x38
github.com/rancher/lasso/pkg/controller.(*SharedHandler).OnChange(0xc0011d6140, {0xc002132a76, 0x7}, {0x4f91bc8, 0xc011118000})
	/go/pkg/mod/github.com/rancher/lasso@v0.0.0-20230428185353-36908edf817b/pkg/controller/sharedhandler.go:75 +0x23f
github.com/rancher/lasso/pkg/controller.(*controller).syncHandler(0xc000a5e0b0, {0xc002132a76, 0x7})
	/go/pkg/mod/github.com/rancher/lasso@v0.0.0-20230428185353-36908edf817b/pkg/controller/controller.go:232 +0x93
github.com/rancher/lasso/pkg/controller.(*controller).processSingleItem(0xc000a5e0b0, {0x39b69e0?, 0xc00573c9a0?})
	/go/pkg/mod/github.com/rancher/lasso@v0.0.0-20230428185353-36908edf817b/pkg/controller/controller.go:213 +0x105
github.com/rancher/lasso/pkg/controller.(*controller).processNextWorkItem(0xc000a5e0b0)
	/go/pkg/mod/github.com/rancher/lasso@v0.0.0-20230428185353-36908edf817b/pkg/controller/controller.go:190 +0x46
github.com/rancher/lasso/pkg/controller.(*controller).runWorker(0xc00335bea0?)
	/go/pkg/mod/github.com/rancher/lasso@v0.0.0-20230428185353-36908edf817b/pkg/controller/controller.go:179 +0x25
k8s.io/apimachinery/pkg/util/wait.BackoffUntil.func1(0x646f6e222c?)
	/go/pkg/mod/k8s.io/apimachinery@v0.25.4/pkg/util/wait/wait.go:157 +0x3e
k8s.io/apimachinery/pkg/util/wait.BackoffUntil(0x6562756b222c7d22?, {0x4f839e0, 0xc002664a20}, 0x1, 0xc0009f89c0)
	/go/pkg/mod/k8s.io/apimachinery@v0.25.4/pkg/util/wait/wait.go:158 +0xb6
k8s.io/apimachinery/pkg/util/wait.JitterUntil(0x302e302e302e3022?, 0x3b9aca00, 0x0, 0x69?, 0x614e223a22736e69?)
	/go/pkg/mod/k8s.io/apimachinery@v0.25.4/pkg/util/wait/wait.go:135 +0x89
k8s.io/apimachinery/pkg/util/wait.Until(0x615274696d694c2c?, 0x7265532c7265676e?, 0x6f63634165636976?)
	/go/pkg/mod/k8s.io/apimachinery@v0.25.4/pkg/util/wait/wait.go:92 +0x25
created by github.com/rancher/lasso/pkg/controller.(*controller).run
	/go/pkg/mod/github.com/rancher/lasso@v0.0.0-20230428185353-36908edf817b/pkg/controller/controller.go:147 +0x2a7
panic: interface conversion: runtime.Object is nil, not *unstructured.Unstructured [recovered]
	panic: interface conversion: runtime.Object is nil, not *unstructured.Unstructured

goroutine 2695 [running]:
k8s.io/apimachinery/pkg/util/runtime.HandleCrash({0x0, 0x0, 0xc00573c9a0?})
	/go/pkg/mod/k8s.io/apimachinery@v0.25.4/pkg/util/runtime/runtime.go:56 +0xd7
panic({0x3d39e40, 0xc00f59aea0})
	/usr/lib64/go/1.19/src/runtime/panic.go:884 +0x212
github.com/rancher/rancher/pkg/controllers/management/aks.(*aksOperatorController).updateAKSClusterConfig(0xc004985a40, 0xc003d22a80, 0xc0129bec38, 0xc00f6a8c90)
	/go/src/github.com/rancher/rancher/pkg/controllers/management/aks/aks_cluster_handler.go:309 +0x55c
github.com/rancher/rancher/pkg/controllers/management/aks.(*aksOperatorController).onClusterChange(0xc004985a40, {0xc00c26bb70?, 0x40ba74?}, 0x43d5c20?)
	/go/src/github.com/rancher/rancher/pkg/controllers/management/aks/aks_cluster_handler.go:128 +0x1413
github.com/rancher/rancher/pkg/generated/controllers/management.cattle.io/v3.FromClusterHandlerToHandler.func1({0xc002132a76?, 0x0?}, {0x4f91bc8?, 0xc003d22a80?})
	/go/src/github.com/rancher/rancher/pkg/generated/controllers/management.cattle.io/v3/cluster.go:105 +0x44
github.com/rancher/lasso/pkg/controller.SharedControllerHandlerFunc.OnChange(0x45260a0?, {0xc002132a76?, 0x46320d2?}, {0x4f91bc8?, 0xc003d22a80?})
	/go/pkg/mod/github.com/rancher/lasso@v0.0.0-20230428185353-36908edf817b/pkg/controller/sharedcontroller.go:29 +0x38
github.com/rancher/lasso/pkg/controller.(*SharedHandler).OnChange(0xc0011d6140, {0xc002132a76, 0x7}, {0x4f91bc8, 0xc011118000})
	/go/pkg/mod/github.com/rancher/lasso@v0.0.0-20230428185353-36908edf817b/pkg/controller/sharedhandler.go:75 +0x23f
github.com/rancher/lasso/pkg/controller.(*controller).syncHandler(0xc000a5e0b0, {0xc002132a76, 0x7})
	/go/pkg/mod/github.com/rancher/lasso@v0.0.0-20230428185353-36908edf817b/pkg/controller/controller.go:232 +0x93
github.com/rancher/lasso/pkg/controller.(*controller).processSingleItem(0xc000a5e0b0, {0x39b69e0?, 0xc00573c9a0?})
	/go/pkg/mod/github.com/rancher/lasso@v0.0.0-20230428185353-36908edf817b/pkg/controller/controller.go:213 +0x105
github.com/rancher/lasso/pkg/controller.(*controller).processNextWorkItem(0xc000a5e0b0)
	/go/pkg/mod/github.com/rancher/lasso@v0.0.0-20230428185353-36908edf817b/pkg/controller/controller.go:190 +0x46
github.com/rancher/lasso/pkg/controller.(*controller).runWorker(0xc00335bea0?)
	/go/pkg/mod/github.com/rancher/lasso@v0.0.0-20230428185353-36908edf817b/pkg/controller/controller.go:179 +0x25
k8s.io/apimachinery/pkg/util/wait.BackoffUntil.func1(0x646f6e222c?)
	/go/pkg/mod/k8s.io/apimachinery@v0.25.4/pkg/util/wait/wait.go:157 +0x3e
k8s.io/apimachinery/pkg/util/wait.BackoffUntil(0x6562756b222c7d22?, {0x4f839e0, 0xc002664a20}, 0x1, 0xc0009f89c0)
	/go/pkg/mod/k8s.io/apimachinery@v0.25.4/pkg/util/wait/wait.go:158 +0xb6
k8s.io/apimachinery/pkg/util/wait.JitterUntil(0x302e302e302e3022?, 0x3b9aca00, 0x0, 0x69?, 0x614e223a22736e69?)
	/go/pkg/mod/k8s.io/apimachinery@v0.25.4/pkg/util/wait/wait.go:135 +0x89
k8s.io/apimachinery/pkg/util/wait.Until(0x615274696d694c2c?, 0x7265532c7265676e?, 0x6f63634165636976?)
	/go/pkg/mod/k8s.io/apimachinery@v0.25.4/pkg/util/wait/wait.go:92 +0x25
created by github.com/rancher/lasso/pkg/controller.(*controller).run
	/go/pkg/mod/github.com/rancher/lasso@v0.0.0-20230428185353-36908edf817b/pkg/controller/controller.go:147 +0x2a7
INFO: Running k3s server --cluster-init --cluster-reset

Expected Result
Expected no panics in the logs.
Additional context

Possibly related to https://github.com/rancher/rancher/issues/38142#issuecomment-1254140473
Tried to reproduce on v2.7-head, while creating an AKS cluster and did not see any panics in rancher logs.
Re tried the scenario from v2.7.4 to v2.7-head by creating an AKS cluster and no panics were noticed then too.
Happened 1 out of 3 times.

Hi @anupama2501, thanks for bringing this up.
I've been trying to reproduce this issue but haven't been able to do so. From a Rancher server v2.7.3 I have created a new AKS cluster with the default configuration and then upgraded Rancher to v2.7-head. At this point, the old Rancher pods are replaced and the new installation seems to work just fine and I see no panics.
You mentioned that this happened 1 out of 3 times, so I tried repeating this same process a few times, but I wasn't able to reproduce it. Even if I try the Rancher upgrade while the new AKS cluster is still in "Provisioning" state, it doesn't panic.
Could you provide more details on the configuration of the AKS cluster that you provisioned? The cluster's yaml file could help us troubleshoot this in the same situation.

Following up on my previous message, I was trying to reproduce it via upgrading Rancher with Helm. My bad, I was then able to reproduce the error when properly testing it with a Docker installation of Rancher. Still, only happened once and it's a little bit frustrating that it succeeds/fails randomly. I'm looking into this and trying to validate a fix.

The 2.7.3 release notes (https://github.com/rancher/rancher/releases/tag/v2.7.3) do mention this behaviour and link to  #33685.

Opened PR #41769 with a proposal to catch the error and avoid the panic.

Validated the fix and didn't observed panic after Rancher docker upgrade to > v2.7-head - 9a33c24
(performed 4 times)
Steps
Create a Docker install of rancher server on v2.7.3
Create an AKS hosted cluster on version 1.25.6 with the default configuration on the UI
Upgrade rancher server to v2.7-head
Logs snippet
INFO: Running k3s server --cluster-init --cluster-reset
2023/06/13 06:08:31 [INFO] Rancher version 9a33c24de (9a33c24de) is starting
2023/06/13 06:08:31 [INFO] Rancher arguments {ACMEDomains:[] AddLocal:true Embedded:false BindHost: HTTPListenPort:80 HTTPSListenPort:443 K8sMode:auto Debug:false Trace:false NoCACerts:false AuditLogPath:/var/log/auditlog/rancher-api-audit.log AuditLogMaxage:10 AuditLogMaxsize:100 AuditLogMaxbackup:10 AuditLevel:0 Features: ClusterRegistry:}
2023/06/13 06:08:31 [INFO] Listening on /tmp/log.sock
2023/06/13 06:08:31 [INFO] Waiting for server to become available: Get "https://<IP_ADDRESS>:6444/version?timeout=15m0s": dial tcp <IP_ADDRESS>:6444: connect: connection refused
2023/06/13 06:08:33 [INFO] Waiting for server to become available: Get "https://<IP_ADDRESS>:6444/version?timeout=15m0s": dial tcp <IP_ADDRESS>:6444: connect: connection refused
2023/06/13 06:08:35 [INFO] Waiting for server to become available: Get "https://<IP_ADDRESS>:6444/version?timeout=15m0s": dial tcp <IP_ADDRESS>:6444: connect: connection refused
2023/06/13 06:08:37 [INFO] Waiting for server to become available: Get "https://<IP_ADDRESS>:6444/version?timeout=15m0s": dial tcp <IP_ADDRESS>:6444: connect: connection refused
2023/06/13 06:08:39 [INFO] Waiting for server to become available: Get "https://<IP_ADDRESS>:6444/version?timeout=15m0s": dial tcp <IP_ADDRESS>:6444: connect: connection refused
2023/06/13 06:08:41 [INFO] Waiting for server to become available: Get "https://<IP_ADDRESS>:6444/version?timeout=15m0s": dial tcp <IP_ADDRESS>:6444: connect: connection refused
2023/06/13 06:08:43 [INFO] Waiting for server to become available: Get "https://<IP_ADDRESS>:6444/version?timeout=15m0s": dial tcp <IP_ADDRESS>:6444: connect: connection refused
2023/06/13 06:08:45 [INFO] Waiting for server to become available: Get "https://<IP_ADDRESS>:6444/version?timeout=15m0s": dial tcp <IP_ADDRESS>:6444: connect: connection refused
2023/06/13 06:09:25 [INFO] Running in single server mode, will not peer connections
2023/06/13 06:09:25 [INFO] Applying CRD features.management.cattle.io
2023/06/13 06:09:26 [INFO] Applying CRD navlinks.ui.cattle.io
2023/06/13 06:09:26 [INFO] Applying CRD podsecurityadmissionconfigurationtemplates.management.cattle.io
2023/06/13 06:09:26 [INFO] Applying CRD clusters.management.cattle.io
2023/06/13 06:09:26 [INFO] Applying CRD apiservices.management.cattle.io
2023/06/13 06:09:27 [INFO] Applying CRD clusterregistrationtokens.management.cattle.io
2023/06/13 06:09:27 [INFO] Applying CRD settings.management.cattle.io
2023/06/13 06:09:27 [INFO] Applying CRD preferences.management.cattle.io
2023/06/13 06:09:27 [INFO] Applying CRD features.management.cattle.io
2023/06/13 06:09:27 [INFO] Applying CRD clusterrepos.catalog.cattle.io
2023/06/13 06:09:27 [INFO] Applying CRD operations.catalog.cattle.io
2023/06/13 06:09:27 [INFO] Applying CRD apps.catalog.cattle.io
2023/06/13 06:09:27 [INFO] Applying CRD fleetworkspaces.management.cattle.io
2023/06/13 06:09:27 [INFO] Applying CRD managedcharts.management.cattle.io
.
.
.
2023/06/13 06:10:23 [INFO] Starting batch/v1, Kind=Job controller
2023/06/13 06:10:23 [INFO] Starting catalog.cattle.io/v1, Kind=App controller
2023/06/13 06:10:23 [INFO] Starting admissionregistration.k8s.io/v1, Kind=MutatingWebhookConfiguration controller
2023/06/13 06:10:23 [INFO] Starting monitoring.coreos.com/v1, Kind=ServiceMonitor controller
2023/06/13 06:10:23 [INFO] Starting monitoring.coreos.com/v1, Kind=Prometheus controller
2023/06/13 06:10:23 [INFO] Starting apps/v1, Kind=Deployment controller
2023/06/13 06:10:23 [INFO] Watching metadata for cluster.x-k8s.io/v1alpha3, Kind=Machine
2023/06/13 06:10:23 [INFO] Starting /v1, Kind=Service controller
2023/06/13 06:10:23 [INFO] Starting management.cattle.io/v3, Kind=ClusterAlertGroup controller
2023/06/13 06:10:23 [INFO] Starting apps/v1, Kind=DaemonSet controller
2023/06/13 06:10:23 [INFO] Starting /v1, Kind=Pod controller
2023/06/13 06:10:23 [INFO] Starting /v1, Kind=ReplicationController controller
2023/06/13 06:10:23 [INFO] Starting rke.cattle.io/v1, Kind=RKEControlPlane controller
2023/06/13 06:10:24 [INFO] Starting management.cattle.io/v3, Kind=ComposeConfig controller
2023/06/13 06:10:24 [INFO] Refusing to reset the config and clean up resources of the auth provider shibboleth because its auth config annotation management.cattle.io/auth-provider-cleanup is set to rancher-locked.
2023/06/13 06:10:24 [INFO] Redeploy Rancher Agents is needed for c-8p4qr: forceDeploy=false, agent/auth image changed=true, private repo changed=false, agent features changed=false
2023/06/13 06:10:24 [INFO] Creating system token for u-evuizjvbz6, token: agent-u-evuizjvbz6
2023/06/13 06:10:24 [INFO] Refusing to reset the config and clean up resources of the auth provider openldap because its auth config annotation management.cattle.io/auth-provider-cleanup is set to rancher-locked.
2023/06/13 06:10:24 [INFO] Refusing to reset the config and clean up resources of the auth provider keycloakoidc because its auth config annotation management.cattle.io/auth-provider-cleanup is set to rancher-locked.
2023/06/13 06:10:24 [INFO] Refusing to reset the config and clean up resources of the auth provider keycloak because its auth config annotation management.cattle.io/auth-provider-cleanup is set to rancher-locked.
2023/06/13 06:10:24 [INFO] Starting management.cattle.io/v3, Kind=EtcdBackup controller
2023/06/13 06:10:24 [INFO] Starting apps/v1, Kind=StatefulSet controller
2023/06/13 06:10:24 [INFO] Refusing to reset the config and clean up resources of the auth provider github because its auth config annotation management.cattle.io/auth-provider-cleanup is set to rancher-locked.
2023/06/13 06:10:24 [INFO] Refusing to reset the config and clean up resources of the auth provider ping because its auth config annotation management.cattle.io/auth-provider-cleanup is set to rancher-locked.
2023/06/13 06:10:24 [INFO] Refusing to reset the config and clean up resources of the auth provider okta because its auth config annotation management.cattle.io/auth-provider-cleanup is set to rancher-locked.
2023/06/13 06:10:24 [INFO] Refusing to reset the config and clean up resources of the auth provider oidc because its auth config annotation management.cattle.io/auth-provider-cleanup is set to rancher-locked.
2023/06/13 06:10:24 [INFO] Refusing to reset the config and clean up resources of the auth provider freeipa because its auth config annotation management.cattle.io/auth-provider-cleanup is set to rancher-locked.
2023/06/13 06:10:24 [INFO] Refusing to reset the config and clean up resources of the auth provider azuread because its auth config annotation management.cattle.io/auth-provider-cleanup is set to rancher-locked.
2023/06/13 06:10:24 [INFO] Refusing to reset the config and clean up resources of the auth provider adfs because its auth config annotation management.cattle.io/auth-provider-cleanup is set to rancher-locked.
2023/06/13 06:10:24 [INFO] Refusing to reset the config and clean up resources of the auth provider activedirectory because its auth config annotation management.cattle.io/auth-provider-cleanup is set to rancher-locked.
2023/06/13 06:10:24 [INFO] Refusing to reset the config and clean up resources of the auth provider googleoauth because its auth config annotation management.cattle.io/auth-provider-cleanup is set to rancher-locked.
2023/06/13 06:10:24 [INFO] Rancher startup complete
2023/06/13 06:10:24 [INFO] checking configmap cattle-system/admincreated to determine if orphan bindings cleanup needs to run
2023/06/13 06:10:24 [INFO] Starting cluster.x-k8s.io/v1beta1, Kind=Cluster controller
2023/06/13 06:10:24 [INFO] Starting apps/v1, Kind=ReplicaSet controller
2023/06/13 06:10:24 [INFO] Detected v2.6.0 upgrade, forcing logout for all web users
2023/06/13 06:10:24 [INFO] Watching metadata for cluster.x-k8s.io/v1alpha3, Kind=MachineDeployment
2023/06/13 06:10:24 [INFO] Starting cluster.x-k8s.io/v1alpha3, Kind=Machine controller
2023/06/13 06:10:24 [INFO] Starting catalog.cattle.io/v1, Kind=Operation controller
2023/06/13 06:10:24 [INFO] checking configmap cattle-system/admincreated to determine if duplicate bindings cleanup needs to run
2023/06/13 06:10:24 [INFO] Starting management.cattle.io/v3, Kind=ClusterAlertRule controller
2023/06/13 06:10:24 [INFO] Starting networking.k8s.io/v1, Kind=Ingress controller
2023/06/13 06:10:24 [INFO] Starting cluster.x-k8s.io/v1beta1, Kind=MachineDeployment controller
2023/06/13 06:10:24 [INFO] Starting management.cattle.io/v3, Kind=SamlToken controller
2023/06/13 06:10:24 [INFO] [CleanupOrphanBindingsDone] orphan bindings cleanup has already run, skipping
2023/06/13 06:10:24 [INFO] checking configmap cattle-system/admincreated to determine if orphan bindings cleanup needs to run
2023/06/13 06:10:24 [INFO] Starting management.cattle.io/v3, Kind=FleetWorkspace controller
2023/06/13 06:10:24 [INFO] Starting rke.cattle.io/v1, Kind=CustomMachine controller
2023/06/13 06:10:24 [INFO] Starting rke.cattle.io/v1, Kind=RKECluster controller
2023/06/13 06:10:24 [INFO] Starting admissionregistration.k8s.io/v1, Kind=ValidatingWebhookConfiguration controller
2023/06/13 06:10:24 [INFO] Starting fleet.cattle.io/v1alpha1, Kind=ClusterGroup controller
2023/06/13 06:10:24 [INFO] Starting /v1, Kind=Node controller
2023/06/13 06:10:24 [INFO] Starting cluster.x-k8s.io/v1beta1, Kind=MachineSet controller
2023/06/13 06:10:24 [INFO] getReleaseConfig: reloading config for rke2
2023/06/13 06:10:24 [INFO] Watching metadata for rke-machine-config.cattle.io/v1, Kind=Amazonec2Config
2023/06/13 06:10:24 [INFO] Starting cluster.x-k8s.io/v1alpha3, Kind=MachineDeployment controller
2023/06/13 06:10:24 [INFO] Starting management.cattle.io/v3, Kind=GlobalDnsProvider controller
2023/06/13 06:10:24 [INFO] duplicate bindings cleanup has already run, skipping
2023/06/13 06:10:24 [INFO] [clean-catalog-orphan-bindings] cleaning up orphaned catalog bindings
2023/06/13 06:10:25 [INFO] [clean-catalog-orphan-bindings] Processing 4 rolebindings
2023/06/13 06:10:25 [INFO] [clean-catalog-orphan-bindings] Deleting orphaned role global-catalog
2023/06/13 06:10:25 [INFO] Watching metadata for rke-machine-config.cattle.io/v1, Kind=AzureConfig
2023/06/13 06:10:25 [INFO] Starting rke-machine-config.cattle.io/v1, Kind=Amazonec2Config controller
2023/06/13 06:10:25 [INFO] Stopping cluster agent for local
2023/06/13 06:10:25 [INFO] Shutting down rbac.authorization.k8s.io/v1, Kind=ClusterRole workers
2023/06/13 06:10:25 [INFO] Shutting down /v1, Kind=ServiceAccount workers
2023/06/13 06:10:25 [INFO] Shutting down rbac.authorization.k8s.io/v1, Kind=ClusterRoleBinding workers
2023/06/13 06:10:25 [INFO] Shutting down /v1, Kind=Namespace workers
2023/06/13 06:10:25 [INFO] Shutting down rbac.authorization.k8s.io/v1, Kind=Role workers
2023/06/13 06:10:25 [INFO] Shutting down /v1, Kind=ConfigMap workers
2023/06/13 06:10:25 [INFO] Shutting down /v1, Kind=LimitRange workers
2023/06/13 06:10:25 [INFO] Shutting down /v1, Kind=ResourceQuota workers
2023/06/13 06:10:25 [INFO] Shutting down /v1, Kind=Secret workers
2023/06/13 06:10:25 [INFO] Shutting down rbac.authorization.k8s.io/v1, Kind=RoleBinding workers
2023/06/13 06:10:25 [INFO] Shutting down /v1, Kind=Node workers
2023/06/13 06:10:25 [INFO] Shutting down apiregistration.k8s.io/v1, Kind=APIService workers
2023/06/13 06:10:25 [WARNING] [clean-catalog-orphan-bindings] Error when deleting role global-catalog, roles.rbac.authorization.k8s.io "global-catalog" not found
2023/06/13 06:10:25 [WARNING] [CleanupOrphanCatalogBindingsDone] error during orphan binding cleanup: roles.rbac.authorization.k8s.io "global-catalog" not found
2023/06/13 06:10:25 [ERROR] failed to cleanup orphan catalog bindings
2023/06/13 06:10:25 [INFO] driverMetadata: refreshing data from upstream https://releases.rancher.com/kontainer-driver-metadata/dev-v2.7/data.json
2023/06/13 06:10:25 [INFO] Retrieve data.json from local path /var/lib/rancher-data/driver-metadata/data.json
2023/06/13 06:10:25 [INFO] Starting cluster controllers for local
2023/06/13 06:10:25 [INFO] Watching metadata for rke-machine-config.cattle.io/v1, Kind=DigitaloceanConfig
2023/06/13 06:10:25 [INFO] Starting rke-machine-config.cattle.io/v1, Kind=AzureConfig controller
2023/06/13 06:10:25 [ERROR] available chart version (102.0.0+up0.6.0) for fleet is less than the min version (102.1.0+up0.7.0)
2023/06/13 06:10:25 [ERROR] Failed to find system chart fleet will try again in 5 seconds: no chart name found
2023/06/13 06:10:26 [INFO] Watching metadata for rke-machine-config.cattle.io/v1, Kind=LinodeConfig
2023/06/13 06:10:26 [INFO] Watching metadata for rke-machine-config.cattle.io/v1, Kind=VmwarevsphereConfig
2023/06/13 06:10:26 [INFO] Watching metadata for rke-machine-config.cattle.io/v1, Kind=HarvesterConfig
2023/06/13 06:10:26 [INFO] Watching metadata for rke-machine.cattle.io/v1, Kind=DigitaloceanMachine
2023/06/13 06:10:26 [INFO] Watching metadata for rke-machine.cattle.io/v1, Kind=LinodeMachine
2023/06/13 06:10:26 [INFO] Watching metadata for rke-machine.cattle.io/v1, Kind=AzureMachine
2023/06/13 06:10:26 [INFO] Watching metadata for rke-machine.cattle.io/v1, Kind=Amazonec2MachineTemplate
2023/06/13 06:10:26 [INFO] Watching metadata for rke-machine.cattle.io/v1, Kind=LinodeMachineTemplate
2023/06/13 06:10:26 [INFO] Watching metadata for rke-machine.cattle.io/v1, Kind=VmwarevsphereMachine
2023/06/13 06:10:26 [INFO] Watching metadata for rke-machine.cattle.io/v1, Kind=HarvesterMachineTemplate
2023/06/13 06:10:26 [INFO] Watching metadata for rke-machine.cattle.io/v1, Kind=DigitaloceanMachineTemplate
2023/06/13 06:10:26 [INFO] Watching metadata for rke-machine.cattle.io/v1, Kind=AzureMachineTemplate
2023/06/13 06:10:26 [INFO] Watching metadata for rke-machine.cattle.io/v1, Kind=HarvesterMachine
2023/06/13 06:10:26 [INFO] Watching metadata for rke-machine.cattle.io/v1, Kind=Amazonec2Machine
2023/06/13 06:10:26 [INFO] Watching metadata for rke-machine.cattle.io/v1, Kind=VmwarevsphereMachineTemplate
2023/06/13 06:10:26 [INFO] Watching metadata for cluster.x-k8s.io/v1alpha3, Kind=Cluster
2023/06/13 06:10:26 [INFO] Watching metadata for cluster.x-k8s.io/v1alpha3, Kind=MachineHealthCheck
2023/06/13 06:10:26 [INFO] Watching metadata for cluster.x-k8s.io/v1alpha3, Kind=MachineSet
2023/06/13 06:10:26 [INFO] Starting rke-machine-config.cattle.io/v1, Kind=DigitaloceanConfig controller
2023/06/13 06:10:26 [INFO] Updating global catalog system-library
2023/06/13 06:10:26 [INFO] Starting provisioning.cattle.io/v1, Kind=Cluster controller
2023/06/13 06:10:26 [INFO] Starting rke-machine-config.cattle.io/v1, Kind=LinodeConfig controller
2023/06/13 06:10:26 [INFO] Starting rke-machine-config.cattle.io/v1, Kind=VmwarevsphereConfig controller
2023/06/13 06:10:26 [INFO] Starting rke-machine-config.cattle.io/v1, Kind=HarvesterConfig controller
2023/06/13 06:10:26 [INFO] Starting rke-machine.cattle.io/v1, Kind=DigitaloceanMachine controller
2023/06/13 06:10:26 [INFO] Starting rke-machine.cattle.io/v1, Kind=LinodeMachine controller
2023/06/13 06:10:26 [INFO] Starting rke-machine.cattle.io/v1, Kind=AzureMachine controller
2023/06/13 06:10:26 [INFO] Starting rke-machine.cattle.io/v1, Kind=Amazonec2MachineTemplate controller
2023/06/13 06:10:26 [INFO] Starting rke-machine.cattle.io/v1, Kind=LinodeMachineTemplate controller
2023/06/13 06:10:26 [INFO] Starting rke-machine.cattle.io/v1, Kind=VmwarevsphereMachine controller
2023/06/13 06:10:26 [INFO] Starting rke-machine.cattle.io/v1, Kind=HarvesterMachineTemplate controller
2023/06/13 06:10:26 [INFO] Starting rke-machine.cattle.io/v1, Kind=DigitaloceanMachineTemplate controller
2023/06/13 06:10:26 [INFO] Starting rke-machine.cattle.io/v1, Kind=AzureMachineTemplate controller
2023/06/13 06:10:26 [INFO] Starting rke-machine.cattle.io/v1, Kind=HarvesterMachine controller
2023/06/13 06:10:26 [INFO] Starting rke-machine.cattle.io/v1, Kind=Amazonec2Machine controller
2023/06/13 06:10:26 [INFO] Starting rke-machine.cattle.io/v1, Kind=VmwarevsphereMachineTemplate controller
2023/06/13 06:10:26 [INFO] Starting rke.cattle.io/v1, Kind=RKEBootstrapTemplate controller
2023/06/13 06:10:26 [INFO] Starting rke.cattle.io/v1, Kind=CustomMachine controller
2023/06/13 06:10:26 [INFO] Starting rke.cattle.io/v1, Kind=RKEControlPlane controller
2023/06/13 06:10:26 [INFO] Starting rke.cattle.io/v1, Kind=RKECluster controller
2023/06/13 06:10:26 [INFO] Starting rke.cattle.io/v1, Kind=ETCDSnapshot controller
2023/06/13 06:10:26 [INFO] Starting rke.cattle.io/v1, Kind=RKEBootstrap controller
2023/06/13 06:10:26 [INFO] Starting cluster.x-k8s.io/v1alpha3, Kind=Cluster controller
2023/06/13 06:10:26 [INFO] Starting cluster.x-k8s.io/v1alpha3, Kind=MachineHealthCheck controller
2023/06/13 06:10:26 [INFO] Starting cluster.x-k8s.io/v1alpha3, Kind=MachineSet controller
2023/06/13 06:10:27 [INFO] Starting cluster agent for local [owner=true]
2023/06/13 06:10:27 [INFO] Starting /v1, Kind=Secret controller
2023/06/13 06:10:27 [INFO] Starting rbac.authorization.k8s.io/v1, Kind=ClusterRoleBinding controller
2023/06/13 06:10:27 [INFO] Starting rbac.authorization.k8s.io/v1, Kind=RoleBinding controller
2023/06/13 06:10:27 [INFO] Starting rbac.authorization.k8s.io/v1, Kind=Role controller
2023/06/13 06:10:27 [INFO] Starting /v1, Kind=Node controller
2023/06/13 06:10:27 [INFO] Starting /v1, Kind=ConfigMap controller
2023/06/13 06:10:27 [INFO] Starting apiregistration.k8s.io/v1, Kind=APIService controller
2023/06/13 06:10:27 [INFO] Starting /v1, Kind=ResourceQuota controller
2023/06/13 06:10:27 [INFO] Starting /v1, Kind=LimitRange controller
2023/06/13 06:10:27 [INFO] Starting /v1, Kind=ServiceAccount controller
2023/06/13 06:10:27 [INFO] Starting /v1, Kind=Namespace controller
2023/06/13 06:10:27 [INFO] Starting rbac.authorization.k8s.io/v1, Kind=ClusterRole controller
2023/06/13 06:10:29 [INFO] kontainerdriver amazonelasticcontainerservice listening on address <IP_ADDRESS>:37137
2023/06/13 06:10:29 [INFO] kontainerdriver googlekubernetesengine listening on address <IP_ADDRESS>:43259
2023/06/13 06:10:29 [INFO] kontainerdriver azurekubernetesservice listening on address <IP_ADDRESS>:40859
2023/06/13 06:10:29 [INFO] kontainerdriver azurekubernetesservice stopped
2023/06/13 06:10:29 [INFO] dynamic schema for kontainerdriver azurekubernetesservice updating
2023/06/13 06:10:29 [INFO] kontainerdriver amazonelasticcontainerservice stopped
2023/06/13 06:10:29 [INFO] dynamic schema for kontainerdriver amazonelasticcontainerservice updating
2023/06/13 06:10:29 [INFO] kontainerdriver googlekubernetesengine stopped
2023/06/13 06:10:29 [INFO] dynamic schema for kontainerdriver googlekubernetesengine updating
2023/06/13 06:10:29 [INFO] Creating token for user user-l8n5k
time="2023-06-13 06:10:29" level=info msg="Telemetry Client v0.5.20"
time="2023-06-13 06:10:29" level=info msg="Listening on <IP_ADDRESS>:8114"
2023/06/13 06:10:31 [INFO] Refreshing driverMetadata in 1440 minutes
2023/06/13 06:10:31 [INFO] Loaded configuration from https://releases.rancher.com/kontainer-driver-metadata/dev-v2.7/data.json in [0x789f708]
2023/06/13 06:10:31 [INFO] getReleaseConfig: reloading config for k3s
2023/06/13 06:10:31 [ERROR] available chart version (102.0.0+up0.6.0) for fleet is less than the min version (102.1.0+up0.7.0)
2023/06/13 06:10:31 [ERROR] Failed to find system chart fleet will try again in 5 seconds: no chart name found
2023/06/13 06:10:31 [INFO] Loaded configuration from https://releases.rancher.com/kontainer-driver-metadata/dev-v2.7/data.json in [0x789f708]
2023/06/13 06:10:31 [INFO] getReleaseConfig: reloading config for rke2
2023/06/13 06:10:31 [INFO] driverMetadata: refreshing data from upstream https://releases.rancher.com/kontainer-driver-metadata/dev-v2.7/data.json
2023/06/13 06:10:31 [INFO] Retrieve data.json from local path /var/lib/rancher-data/driver-metadata/data.json
2023/06/13 06:10:31 [INFO] change detected for cluster [c-8p4qr], updating AKSClusterConfig
2023/06/13 06:10:33 [INFO] Catalog sync done. 0 templates created, 7 templates updated, 0 templates deleted, 0 templates failed
2023/06/13 06:10:34 [INFO] Loaded configuration from https://releases.rancher.com/kontainer-driver-metadata/dev-v2.7/data.json in [0x789f708]
2023/06/13 06:10:34 [INFO] Loaded configuration from https://releases.rancher.com/kontainer-driver-metadata/dev-v2.7/data.json in [0x789f708]
2023/06/13 06:10:36 [ERROR] available chart version (102.0.0+up0.6.0) for fleet is less than the min version (102.1.0+up0.7.0)
2023/06/13 06:10:36 [ERROR] Failed to find system chart fleet will try again in 5 seconds: no chart name found
2023/06/13 06:10:42 [INFO] checking cluster [c-8p4qr] upstream state for changes
2023/06/13 06:10:43 [INFO] updating cluster [c-8p4qr], upstream change detected
2023/06/13 06:10:43 [INFO] cluster [c-8p4qr] matches upstream, skipping spec sync
2023/06/13 06:10:43 [INFO] change detected for cluster [c-8p4qr], updating AKSClusterConfig
2023/06/13 06:10:53 [INFO] checking cluster [c-8p4qr] upstream state for changes
2023/06/13 06:10:54 [INFO] updating cluster [c-8p4qr], upstream change detected
2023/06/13 06:10:54 [INFO] cluster [c-8p4qr] matches upstream, skipping spec sync
2023/06/13 06:10:55 [INFO] change detected for cluster [c-8p4qr], updating AKSClusterConfig
2023/06/13 06:10:57 [INFO] error in remotedialer server [400]: websocket: close 1006 (abnormal closure): unexpected EOF
2023/06/13 06:10:57 [INFO] error in remotedialer server [400]: websocket: close 1006 (abnormal closure): unexpected EOF
2023/06/13 06:10:57 [INFO] Handling backend connection request [c-8p4qr]
2023/06/13 06:11:00 [ERROR] Failed to handle tunnel request from remote address <IP_ADDRESS>:1033: response 401: failed authentication
2023/06/13 06:11:00 [INFO] Handling backend connection request [stv-cluster-c-8p4qr]
2023/06/13 06:11:02 [ERROR] error syncing 'cattle-fleet-system/helm-operation-txzb2': handler helm-operation: an error on the server ("container not found (\"proxy\")") has prevented the request from succeeding (get pods helm-operation-txzb2), requeuing
2023/06/13 06:11:02 [ERROR] error syncing 'cattle-fleet-system/helm-operation-txzb2': handler helm-operation: an error on the server ("container not found (\"proxy\")") has prevented the request from succeeding (get pods helm-operation-txzb2), requeuing
2023/06/13 06:11:02 [ERROR] error syncing 'cattle-fleet-system/helm-operation-txzb2': handler helm-operation: an error on the server ("container not found (\"proxy\")") has prevented the request from succeeding (get pods helm-operation-txzb2), requeuing
2023/06/13 06:11:02 [ERROR] error syncing 'cattle-fleet-system/helm-operation-txzb2': handler helm-operation: an error on the server ("container not found (\"proxy\")") has prevented the request from succeeding (get pods helm-operation-txzb2), requeuing
2023/06/13 06:11:02 [ERROR] error syncing 'cattle-fleet-system/helm-operation-txzb2': handler helm-operation: an error on the server ("container not found (\"proxy\")") has prevented the request from succeeding (get pods helm-operation-txzb2), requeuing
2023/06/13 06:11:03 [ERROR] error syncing 'cattle-fleet-system/helm-operation-txzb2': handler helm-operation: an error on the server ("container not found (\"proxy\")") has prevented the request from succeeding (get pods helm-operation-txzb2), requeuing
2023/06/13 06:11:05 [INFO] checking cluster [c-8p4qr] upstream state for changes
2023/06/13 06:11:06 [INFO] updating cluster [c-8p4qr], upstream change detected
2023/06/13 06:11:06 [INFO] cluster [c-8p4qr] matches upstream, skipping spec sync
2023/06/13 06:11:07 [INFO] change detected for cluster [c-8p4qr], updating AKSClusterConfig
2023/06/13 06:11:14 [ERROR] error syncing 'cattle-fleet-system/helm-operation-54mg7': handler helm-operation: an error on the server ("container not found (\"proxy\")") has prevented the request from succeeding (get pods helm-operation-54mg7), requeuing
2023/06/13 06:11:14 [ERROR] error syncing 'cattle-fleet-system/helm-operation-54mg7': handler helm-operation: an error on the server ("container not found (\"proxy\")") has prevented the request from succeeding (get pods helm-operation-54mg7), requeuing
2023/06/13 06:11:14 [ERROR] error syncing 'cattle-fleet-system/helm-operation-54mg7': handler helm-operation: an error on the server ("container not found (\"proxy\")") has prevented the request from succeeding (get pods helm-operation-54mg7), requeuing
2023/06/13 06:11:14 [ERROR] error syncing 'cattle-fleet-system/helm-operation-54mg7': handler helm-operation: an error on the server ("container not found (\"proxy\")") has prevented the request from succeeding (get pods helm-operation-54mg7), requeuing
2023/06/13 06:11:17 [INFO] change detected for cluster [c-8p4qr], updating AKSClusterConfig
2023/06/13 06:11:34 [INFO] Catalog-cache removed 2 entries from disk
2023/06/13 06:11:40 [INFO] change detected for cluster [c-8p4qr], updating AKSClusterConfig
2023/06/13 06:11:50 [INFO] change detected for cluster [c-8p4qr], updating AKSClusterConfig
2023/06/13 06:11:52 [ERROR] error syncing 'cattle-system/helm-operation-fhzxh': handler helm-operation: an error on the server ("container not found (\"proxy\")") has prevented the request from succeeding (get pods helm-operation-fhzxh), requeuing
2023/06/13 06:11:52 [ERROR] error syncing 'cattle-system/helm-operation-fhzxh': handler helm-operation: an error on the server ("container not found (\"proxy\")") has prevented the request from succeeding (get pods helm-operation-fhzxh), requeuing
2023/06/13 06:11:52 [ERROR] error syncing 'cattle-system/helm-operation-fhzxh': handler helm-operation: an error on the server ("container not found (\"proxy\")") has prevented the request from succeeding (get pods helm-operation-fhzxh), requeuing
2023/06/13 06:11:52 [ERROR] error syncing 'cattle-system/helm-operation-fhzxh': handler helm-operation: an error on the server ("container not found (\"proxy\")") has prevented the request from succeeding (get pods helm-operation-fhzxh), requeuing
2023/06/13 06:11:52 [ERROR] error syncing 'cattle-system/helm-operation-fhzxh': handler helm-operation: an error on the server ("container not found (\"proxy\")") has prevented the request from succeeding (get pods helm-operation-fhzxh), requeuing
2023/06/13 06:11:52 [ERROR] error syncing 'cattle-system/helm-operation-fhzxh': handler helm-operation: an error on the server ("container not found (\"proxy\")") has prevented the request from succeeding (get pods helm-operation-fhzxh), requeuing
2023/06/13 06:11:53 [ERROR] error syncing 'cattle-system/helm-operation-fhzxh': handler helm-operation: an error on the server ("container not found (\"proxy\")") has prevented the request from succeeding (get pods helm-operation-fhzxh), requeuing
2023/06/13 06:11:53 [ERROR] error syncing 'cattle-system/helm-operation-fhzxh': handler helm-operation: an error on the server ("container not found (\"proxy\")") has prevented the request from succeeding (get pods helm-operation-fhzxh), requeuing
2023/06/13 06:11:58 [ERROR] error syncing 'cattle-system/helm-operation-6v7nd': handler helm-operation: an error on the server ("container not found (\"proxy\")") has prevented the request from succeeding (get pods helm-operation-6v7nd), requeuing
2023/06/13 06:11:58 [ERROR] error syncing 'cattle-system/helm-operation-6v7nd': handler helm-operation: an error on the server ("container not found (\"proxy\")") has prevented the request from succeeding (get pods helm-operation-6v7nd), requeuing
2023/06/13 06:11:58 [INFO] change detected for cluster [c-8p4qr], updating AKSClusterConfig
2023/06/13 06:11:58 [ERROR] error syncing 'cattle-system/helm-operation-6v7nd': handler helm-operation: an error on the server ("container not found (\"proxy\")") has prevented the request from succeeding (get pods helm-operation-6v7nd), requeuing
2023/06/13 06:11:58 [ERROR] error syncing 'cattle-system/helm-operation-6v7nd': handler helm-operation: an error on the server ("container not found (\"proxy\")") has prevented the request from succeeding (get pods helm-operation-6v7nd), requeuing
2023/06/13 06:11:58 [ERROR] error syncing 'cattle-system/helm-operation-6v7nd': handler helm-operation: an error on the server ("container not found (\"proxy\")") has prevented the request from succeeding (get pods helm-operation-6v7nd), requeuing
2023/06/13 06:16:06 [INFO] checking cluster [c-8p4qr] upstream state for changes
2023/06/13 06:16:07 [INFO] updating cluster [c-8p4qr], upstream change detected
2023/06/13 06:16:07 [INFO] cluster [c-8p4qr] matches upstream, skipping spec sync
2023/06/13 06:21:07 [INFO] checking cluster [c-8p4qr] upstream state for changes
2023/06/13 06:21:08 [INFO] updating cluster [c-8p4qr], upstream change detected
2023/06/13 06:21:08 [INFO] cluster [c-8p4qr] matches upstream, skipping spec sync
2023/06/13 06:26:08 [INFO] checking cluster [c-8p4qr] upstream state for changes
2023/06/13 06:26:09 [INFO] updating cluster [c-8p4qr], upstream change detected
2023/06/13 06:26:09 [INFO] cluster [c-8p4qr] matches upstream, skipping spec sync

@anupama2501 Can you review above validation and close issue, thanks.


Use Version 2 config for sqlc.yaml

This makes it easier to reuse examples from the documentation.
Summary
Provide a brief overview of the changes and the issue being addressed.
Explain the rationale and any background necessary for understanding the changes.
List dependencies required by this change, if any.
Fixes #(related issue)
Change Type
Mark the type of change your PR introduces:

[ ] Bug fix (resolves an issue without affecting existing features)
[ ] Feature (adds new functionality without breaking changes)
[ ] Breaking change (may impact existing functionalities or require documentation updates)
[ ] Documentation (updates or additions to documentation)
[x] Refactoring or test improvements (no bug fixes or new functionality)

Testing
Outline how the changes were tested, including steps to reproduce and any relevant configurations.
Attach screenshots if helpful.
Review Checklist:

[x] Reviewed my own code for quality and clarity.
[ ] Added comments to complex or tricky code sections.
[ ] Updated any affected documentation.
[ ] Included tests that validate the fix or feature.
[ ] Checked that related changes are merged.

coverage: 53.056% (+0.004%) from 53.052%
when pulling d3909a5c8f6e5329d744bb749746f3a87939b657 on sqlc-2.0-config
into a441c326336596db5bb4732213abef606fb4235b on main.


Fix Indication on Windows

Currently, Windows will assume that a characteristic will use Notification. If the characteristic only supports Indication, it won't work correctly.

Fixed in #6


Improve frontend PR checks overall time to complete

Frontend PR checks should ideally take around 5 minutes to complete as the longer it takes the longer it takes to react to those results (such as merging the PR).
Acceptance Criteria

Frontend PR checks take ~5 minutes to complete

Waiting on DevOps approval


[BUG] Haiku 3.5 Model missing

Description
https://www.anthropic.com/claude/haiku
Haiku 3.5 was released last month, and it's a noticeable improvement at the same cost as Haiku 3.0.
It seems to be missing from big-AGI
Device and browser
Windows 11
Firefox 133.0
Screenshots and more

Willingness to Contribute

[ ] 🙋♂ Yes, I would like to contribute a fix.

@Kim2091 if this is the big-agi.com website, you just need to "Update Models". You can go to Preferences > Models and update Anthropic, or to the Model Switcher (top bar) and update.
If this is your own code build, you have to update the code (and I assume you are using the v2-dev branch). The reason is that Anthropic doesn't have a models list API, leaving it to developers to "hardcode" the models in their code.


Doesn't load on julia 0.6

I get this with the latest master:
   _       _ _(_)_     |  A fresh approach to technical computing
  (_)     | (_) (_)    |  Documentation: http://docs.julialang.org
   _ _   _| |_  __ _   |  Type "?help" for help.
  | | | | | | |/ _` |  |
  | | |_| | | | (_| |  |  Version 0.6.0-pre.alpha.172 (2017-03-18 01:51 UTC)
 _/ |\__'_|_|_|\__'_|  |  Commit e097911* (1 day old master)
|__/                   |  x86_64-w64-mingw32

julia> using Feather
WARNING: Method definition ==(Base.Nullable{S}, Base.Nullable{T}) in module Base at nullable.jl:244 overwritten in modul
e NullableArrays at C:\Users\david\.julia\v0.6\NullableArrays\src\operators.jl:128.

WARNING: deprecated syntax "typealias String UTF8String" at C:\Users\david\.julia\v0.6\Feather\src\metadata.jl:5.
Use "const String = UTF8String" instead.
ERROR: LoadError: LoadError: UndefVarError: @default not defined
Stacktrace:
 [1] include_from_node1(::String) at .\loading.jl:539
 [2] include(::String) at .\sysimg.jl:14
 [3] include_from_node1(::String) at .\loading.jl:539
 [4] eval(::Module, ::Any) at .\boot.jl:235
 [5] require(::Symbol) at .\loading.jl:453
while loading C:\Users\david\.julia\v0.6\Feather\src\metadata.jl, in expression starting on line 34
while loading C:\Users\david\.julia\v0.6\Feather\src\Feather.jl, in expression starting on line 21

julia>

Is this still an issue?  This has worked fine for me on 0.6 master for a while.

Yeah, this should be good.

Just to confirm, this also works for me now.


Storage.get(bucketname,filepath) returns null when filename has space (1.103.1,java8)

Steps to reproduce

create a file inside a bucket which has space in its name (eg: hotel booking.pdf)
try to download the blob using storage.get(bucket,filepath)

Code example
log.info("Attempting to download file {} from bucket {}", filePath,bucketName);
    Blob blob = storage.get(bucketName, filePath);
    if (Objects.isNull(blob)) {
      log.error("file not present for {}", fileName);
      //            throw new FileNotFoundException("file not present for: {}", fileName);
    }

Stack trace
file not present for 'hotel booking.pdf'

External references such as API reference guides

?

Any additional information below
Following these steps guarantees the quickest resolution possible.
Thanks!

@sudipbhandari126 could you try using the latest release:
https://search.maven.org/artifact/com.google.cloud/google-cloud-storage-parent/1.104.0/pom

My build is failing for the latest version with the following errror:

Could not find androidx.annotation:annotation:1.1.0
....
Required by:
      project :core > com.google.api-client:google-api-client:1.30.8

@sudipbhandari126 please check the issue https://github.com/googleapis/java-storage/issues/148

Great.
Thanks for the quick response.
couple questions:

why an additional dependency wasn't bundled?
why sudden change while upgrading version that we had to add new repository?

cc @elharo


Add --version option to generatejsonschematypes

It would be really helpful if generatejsonschematypes had a --version option to be able to quickly see what version of the tool is installed.

As of 4.0.0-preview.32
generatejsonschematypes version

produces
Version: 4.0.0-preview.32 Build: ce4cb9b9ef77f3004673b69a8f44b36850eb919d

@mwadams Thanks!


can not build getting:  Error [ERR_PACKAGE_PATH_NOT_EXPORTED]: No "exports" main resolved @babel/helper-compilation-targets/package.json

Hi Timo:
I am getting following error:
ERROR  Failed to compile with 1 errors                                                                                9:24:46 AM
error  in ./src/main.js
Module build failed (from ./node_modules/babel-loader/lib/index.js):
Error [ERR_PACKAGE_PATH_NOT_EXPORTED]: No "exports" main resolved in<EMAIL_ADDRESS>at applyExports (internal/modules/cjs/loader.js:491:9)
at resolveExports (internal/modules/cjs/loader.js:507:23)
at Function.Module._findPath (internal/modules/cjs/loader.js:635:31)
at Function.Module._resolveFilename (internal/modules/cjs/loader.js:953:27)
at Function.Module._load (internal/modules/cjs/loader.js:842:27)
at Module.require (internal/modules/cjs/loader.js:1026:19)
at require (internal/modules/cjs/helpers.js:72:18)
at Object. (/home/nrgdev1/dev/gitlab-monitor/node_modules/@babel/preset-env/lib/debug.js:8:33)
at Module._compile (internal/modules/cjs/loader.js:1138:30)
at Object.Module._extensions..js (internal/modules/cjs/loader.js:1158:10)
at Module.load (internal/modules/cjs/loader.js:986:32)
at Function.Module._load (internal/modules/cjs/loader.js:879:14)
at Module.require (internal/modules/cjs/loader.js:1026:19)
at require (internal/modules/cjs/helpers.js:72:18)
at Object. (/home/nrgdev1/dev/gitlab-monitor/node_modules/@babel/preset-env/lib/index.js:11:14)
at Module._compile (internal/modules/cjs/loader.js:1138:30)
@ multi (webpack)-dev-server/client?http://<IP_ADDRESS>:8080/sockjs-node (webpack)/hot/dev-server.js ./src/main.js

I have added 2 lines to Dockerfile then it worked:
RUN npm update && npm audit fix --force
RUN npm install --save date-fns

This project uses yarn 1.x as package manager. Have you installed the dependencies with yarn 1.x or another package manager?

Yes I am using yarn - I have found this fix with npm in the internet - everything is working perfect now, but I moved to newer versions for some packages. Sorry I have forgotten to close this issue.
Great Project!


Expose Elevated Save to the User

Currently, let's say we are modifying something in a protected directory where we require admin or sudo access. We need to attempt a save first, be met with insufficient permissions prompt and then hit the "Retry as Sudo" button. Why not make this available as an option in the "File" dropdown. Additionally, It could be an action which could be manually assigned to a keyoboard shortcut if the user wishes to.

i see the same issue, on ubuntu 16.04 i get the following error

<EMAIL_ADDRESS>what I'm suggesting is making the 'save as admin/sudo' an accessible option from the file menu, command palette. So, we no longer need to wait for the prompt. Additionally, we could assign it to a keyboard shortcut.

From: robbuckley<EMAIL_ADDRESS>Sent: Friday, October 25, 2019 3:57 PM
To: microsoft/vscode<EMAIL_ADDRESS>Cc: mahsoommoosa42<EMAIL_ADDRESS>Author<EMAIL_ADDRESS>Subject: Re: [microsoft/vscode] Expose Elevated Save to the User (#83190)
i see the same issue, on ubuntu 16.04 i get the following error
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://eur04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fmicrosoft%2Fvscode%2Fissues%2F83190%3Femail_source%3Dnotifications%26email_token%3DAFA4ITIJJK2RDFATDTQQJK3QQLC25A5CNFSM4JEMREUKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOECH5RSY%23issuecomment-546298059&data=02|01||9dfc3798e0b54b96cc2f08d7593601cd|84df9e7fe9f640afb435aaaaaaaaaaaa|1|0|637075960800943920&sdata=51S366jc829CHxYyHxhYdZo8uEh%2BqFJ2Ou9cUO8GHFY%3D&reserved=0, or unsubscribehttps://eur04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAFA4ITNZDT72ZPEODAWDJQ3QQLC25ANCNFSM4JEMREUA&data=02|01||9dfc3798e0b54b96cc2f08d7593601cd|84df9e7fe9f640afb435aaaaaaaaaaaa|1|0|637075960800953928&sdata=t4blJQTWmxXzlTp51tih4M%2FSPiwCXZBaDSm3OEEm92s%3D&reserved=0.

I would also appreciate an "Open as sudo" option to allow opening files where the current user has no read access.
The current "Retry as Sudo..." only works if the current user has read access to the file to open it.

A temporary work around is opening code as sudo with the user_data_dir argument specified. However, I'm just not comfortable doing that. I'm willing to contribute towards this feature as well.

I'm willing to contribute to this particular issue. It would be great if someone could me some pointers on where to start. I have already read the contributions guide.


Zeek kit: Conform orig/resp EV naming

This will conform orig/resp EVs across the Corelight and Zeek kits
This PR addresses https://github.com/gravwell/kits/issues/98

John's comment in the mattermost chat said that this is not what the issue asked for. The issue indicates that we should "be consistent with what zeek labels them as"
In this PR and in #188 I think you have just made it consistent within our kits. We should make it consistent with naming that users expect from zeek.


Add new cases in how to find p.i

Is your feature request related to a problem? Please describe.

A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]

Describe the solution you'd like

1)Add 5th case when Q = x.V which is a special case of case 4
2) Add case of failure
i would like to work on this

@sairish2001  sorry i bymistakely clicked on unassign me


Release on F-Droid

It would be great to see this Android app on F-Droid!
F-Droid is an Android app store specifically for free/libre open-source apps. It would be great if your app could be released there, as it is the number one for getting FLOSS Android apps for many people.
F-Droid also builds all apps from source (optionally even reproducible), so downloads from there can be trusted.
The app developer FAQ or the quick start guide may help you to get started.
BTW a release on F-Droid could also bring some (more) popularity (in case that is intended), as it will show up in the app (new apps are featured there).

This could be useful for/related to https://github.com/eurofurence/ef-app_react-native/issues/129 and https://github.com/eurofurence/ef-app_react-native/issues/104


How many heating cycles does the PCB survive?

Hello everyone,
I want to get into SMD soldering.
Can anyone tell me, how many cycles / thermal stress this PCB usually survives, until it deteriorates?
I know that many factors will influence this, but it would be useful to get a general idea what to expect.
Thank you!
Best regards

Hi, thanks for the reply.
Since the heating PCB is not replaceable, what endurance are you getting with the IR?
It shocked me seeing people mentioning only 5 cycles, but I'm not sure how accurate that is.

I think the 5 cycles is due to the huge temperature swings causing it to overheat.
I haven't used mine more than maybe 10 times, but the pcb is still holding up. no warping.

Here is a video of my experimentation with IR sensor.
https://www.youtube.com/watch?v=z8zI6PzrAY8

Thanks @bwack for answering.
I think I will stick with my hot air gun for now.
Closing this issue since it's resolved :)


UX: Show the current round number on the Dispute Card

Updated the design on Figma including the Round on the cards. A related suggestion is changing the order the info is displayed to: Court > Category > Round > Juror Rewards > Voting Deadline; so Court is displayed first.


I think this might be a performance upgrade

https://github.com/SebLague/Ray-Tracing/blob/main/Assets/Scripts/Shaders/RayTracer.shader#L261
You can see that you are getting the result, but not breaking/returning. I think this might be a performance issue, but i cant check because i dont have unity installed.

oh wait im just dumb :p
sorry


Refactor to a namespace package

It would be better to package this collection of useful programs as a namespace package.
This would improve our ability to re-use code as a proper library for new projects. Multiple distribution packages makes it simpler to install smaller programs or parts of the utilities package.
https://packaging.python.org/en/latest/guides/packaging-namespace-packages/

Does this just change the structure of the package? Is there still only one poetry lockfile, etc?

Implemented in:
https://github.com/PGScatalog/pygscatalog
There's now four python packages which all get installed inside the pgscatalog namespace 🚀


⚠ Hydeos has degraded performance

In af7dfe7, Hydeos (https://hydeos.fr) experienced degraded performance:

HTTP code: 200
Response time: 3076 ms

Resolved: Hydeos performance has improved in 2aa5b09 after 25 minutes.


add github of contributors

This PR will add contributors GitHub id at the end of every dataset cards.

@lhoestq Can you confirm if this format is fine? I will update cards based on your feedback.

On HuggingFace side we also have a mapping of hf user => github user (GitHub info used to be required when signing up until not long ago – cc @gary149 @beurkinger) so we can also add a link to HF profile

All the dataset cards have been updated with GitHub ids :)


Graceful shutdown of http and ssh server

can you provide more description for this issue?
is it about the ongoing requests and shutdown the server?

can you provide more description for this issue?
is it about the ongoing requests and shutdown the server?

basically you want to shutdown the servers cleanly so that any ongoing state gets handled properly, and any resources left get cleaned up in a graceful manner. e.g. when you invoke a OS signal like SIGINT which is invoked via CTRL+c or SIGTERM, which can be invoked by the kill command, the system should still handle all the remaining state properly in a graceful manner.
Hope this clears it up. You can also find more resources online by googling golang graceful shutdown http server. However, note that we want to handle the http, ssh, and even the schedulers gracefully, and not just one of them

Thanks for the description,
I will work on this issue

AltLayer Airdrop Season One Update

🚀 Exciting Announcement!
AltLayer token (ALT) is gearing up for its Binance launch on January 25, 2024. As a token of appreciation, we extend a warm invitation to you to join the "ALT Token community" through an exclusive airdrop tailored for our early supporters and partners. Here's a quick overview:

Total Allocated ALT Tokens: 400,000,000 (4% of the total supply)

For a comprehensive breakdown of criteria and further details, refer to the complete announcement Oficial Website.
The window to Claim $ALT tokens is open from January 25 to February 08, 2024.
Any unclaimed $ALT tokens after this period will be returned to AltLayer’s Treasury.
We deeply appreciate your contribution to AltLayer's success! Stay tuned for more exciting developments in Season One.
Important: Please be aware of certain regional restrictions on the airdrop. Review the disclaimer before participating.
cryptoprx, @riccardolops, @nikolaymikhaltsov, @Nanra, @MoTing92, @yulechen, @katiboq, @akshaypjoshi, @canhnm, @big-cabbage, @Jackneill, @hulyak, @tuanductran, @Amirali-Amirifar, @GavinKG, @leandrososa, @shigetaichi, @Priyanshu79, @qincloud, @hui


feat(cart): add direct_feed

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Support for "tvOS" framework, pod

Couldn't use SDWebImage with pods for tvOS target.
platform :tvos, '9.0'
use_frameworks!

pod 'Alamofire'
pod 'SwiftyJSON'
pod 'SDWebImage'

Getting this error.
[!] The platform of the target `Pods` (tvOS 9.0) is not compatible with `SDWebImage (3.7.3)`, which does not support `tvos`.

What I miss something?
Thank you beforehand.

We haven't release a version with tvOS support yet. If you really need it, you can point to our latest master: pod 'SDWebImage', :head

All right. I'll try to use :head.
Thank you for your response.

I added the line pod 'SDWebImage', :head in the Podfile but i got this message:
[!] The platform of the target ``Pods`` (tvOS 9.0) is not compatible with ``SDWebImage (HEAD based on 3.7.3)``, which does not support ``tvos``.
Did i miss something too ?
Thank you.

@mvpaudrey Same error still occurred. Did you find any solutions for this?

@fxwx23 no didn't find any other solution

Not released yet so you need to
pod 'SDWebImage', :git => 'https://github.com/rs/SDWebImage.git'

@jkrzemie Thank you so much.

@jkrzemie thanks a lot

Fixed by #1327  - will make a new release soon (3.7.4).


Create users locally without email confirmation?

Setting up an outgoing email server is a pain. It would be nice to have a way to create users for debugging while bypassing the email confirmation.
Workaround: run with APP_DEBUG=1, get the traceback when it fails to send a confirmation, and use the interactive debugger to get the confirmation link. Copy and paste the link to the URL bar and ta-da, confirmed.

One simple way to work around this would be to have a script that populates the database with a few pre-confirmed testing users (e.g. one admin, a couple of regular users, and a blocked user) with obvious usernames and passwords for testing with.

Yeah, having a few testing users set up would be nice.
There is some documentation on Flask-Mail for suppressing email sending, and logging emails:
https://pythonhosted.org/Flask-Mail/#signalling-support
Maybe APP_DEBUG could print emails out by default on the console? Testing with a gmail account works for me.

for now you can do it manually:

first get the id

sudo -u postgres psql pygame -c "SELECT * FROM groups;"
echo '* pygameweb groups should appear above'
sudo -u postgres psql pygame -c "SELECT * FROM users;"

after you get the id of the user you want above, and group, set the admin_id and group_id variables in the script below:

admin_id=1
mod_group_id=12
sudo -u postgres psql pygame -c "INSERT into users_groups values ($admin_id, $mod_group_id)"
sudo -u postgres psql pygame -c "UPDATE users set active=True where id=$admin_id"
sudo -u postgres psql pygame -c "UPDATE users set confirmed_at='2018-08-08 16:07:43.657477-04' where id=$admin_id"

now the user should be able to log in. Also, the following should show the data above was entered:

sudo -u postgres psql pygame -c "SELECT active,name,confirmed_at,disabled,super,registered_at FROM users where id=$admin_id"
sudo -u postgres psql pygame -c "SELECT * FROM users_groups;"


Inline the same property multiple times

Test
it('allowMultipleSameProperty', function() {
  var html = '
Hello
';
  var css = '.bg-dark{background: #000000;}\n p{background: url(dark.png); background: rgba(0,0,0,0.4);}';

  assert.strictEqual(juice.inlineContent(html, css), '
Hello
');
});

Result
- Actual
-
Hello

+ Expected
+
Hello

Why?
It's common for email clients to only support a subset of values for certain CSS properties.
We work around this with a sort of inline progressive enhancement, where the leftmost property is the most supported and the rightmost is the least supported. In the example above:

modern email clients will show a semi-transparent black background (rgba(0,0,0,0.4))
those that don't support rgba() but support background images will show the background image
the rest will just use the #000000

@jrit can you see this working in Juice? Wanted to PR but can't figure it out tbh...

I thought about this a bit, and yes, I agree that sometimes having the same style multiple times is good, but in the overall use of stylesheets, this is something that happens a small percentage of the time. So, aside from where this could possibly be hooked up in the code, the larger issue seems like how to define when this behavior should happen vs the normal CSS behavior of prioritizing the winning style. I'm not sure I have any good answer to that without adding a bunch of weird juice-specific syntax to the CSS.

when this behavior should happen

Could be Juice option, false by default?

where this could possibly be hooked up in the code

Yes that's what I was struggling with, not sure how to disable the prioritization of the winning style and just append to existing styles.


Fix flow in jsx

This commit adds flow makers to JSX.
Coders who use flow generally uses JSX too so we need it for both.

I've just done the exact same thing on matthewlehner/neomake@9804271 – looks like that test failure might be an intermittent failure as the new JSX flow function follows the same style as the other functions in this file.
Can someone trigger a rerun, or have a look manually?

Thanks.
vint-diff is right, abort should be used for all functions in the file:

autoload/neomake/makers/ft/jsx.vim:3:1: Use the abort attribute for functions in autoload (see Google VimScript Style Guide (Functions))

I can handle that later.

@blueyed I've updated my fork with and submitted #1122 with the abort attributes added to the functions.

Closing in favor of https://github.com/neomake/neomake/pull/1122.


datastore: convert to gax

RE: #1859
This converts the Datastore API to use GAX. This involves non-breaking API changes to support a gaxOptions configuration object.
To Dos

[x] Docs
Convert

[x] index.js
[x] request.js
[x] transaction.js

Tests

Unit

[x] index.js
[ ] request.js
[ ] transaction.js

[x] System

Coverage decreased (-79.0%) to 21.033% when pulling 91cc5b5e66466e17fc09da09a0a0b9067ee04215 on stephenplusplus:spp--1859-datastore into 20cc8920847f3bb7389af47e61512b2a0d310b78 on GoogleCloudPlatform:master.

@callmehiphop this is ready for a look. Just FYI, I'm still wondering about a couple of things: https://github.com/GoogleCloudPlatform/google-cloud-node/pull/2195/files/91cc5b5e66466e17fc09da09a0a0b9067ee04215#diff-4d988e09edc06d395016044c8faf248e - that's what will be affecting the coverage drop.

Changes Unknown when pulling e27965630b29686fc2282de9ff3c2d2fb09bed41 on stephenplusplus:spp--1859-datastore into ** on GoogleCloudPlatform:master**.

@lukesneeringer we're running AppVeyor under your account now? https://ci.appveyor.com/project/lukesneeringer/google-cloud-node/build/1.0.45

Coverage decreased (-0.1%) to 99.877% when pulling e8ce9a87e824c9ef48fda556f2e81b52b98cb01a on stephenplusplus:spp--1859-datastore into 87312f904e8f5ba0b5202e5c4df1bf0dc5ff107a on GoogleCloudPlatform:master.

Looking into these questions rn!

Thank you very much!

Just tagging this google-gax PR, "Allow grpc custom channel without auth", because I think that's the one that will help us with one of the issues.

@stephenplusplus<EMAIL_ADDRESS>has been released.

Changes Unknown when pulling 4681c37dc4f12a791a5c124390fde741720d5a4f on stephenplusplus:spp--1859-datastore into ** on GoogleCloudPlatform:master**.

@callmehiphop since it's been a while and I've made some recent changes, could you take another quick glance?
Don't mind the "25% coverage" report -- that's an issue that's present on master as well, and I'm looking into it. Datastore's coverage is still 100%.

Changes Unknown when pulling 496e16b42d1faf7a901146ffc6f3568d5e230653 on stephenplusplus:spp--1859-datastore into ** on GoogleCloudPlatform:master**.

Coverage remained the same at 100.0% when pulling ae0e9d1b283ceb141b9010701ed95d52441d1e83 on stephenplusplus:spp--1859-datastore into 3108fd26a3ebb499795cdc1969c295e3e8d73d52 on GoogleCloudPlatform:master.

@callmehiphop if it LGTY, I will merge and release!


Launch at login

there should be a setting to allow for launching at login

Consider using https://github.com/sindresorhus/LaunchAtLogin

This one is the modern one: https://github.com/sindresorhus/LaunchAtLogin-Modern


Run tests on all platforms

Currently our travis jobs only run on linux. Lets run them on all platforms:

linux (via travis-ci)
osx (via travis-ci)
windows (via appveyor)

Too buggy at the moment. Not quite sure what's up with appveyor, tests pass on a local windows VM. Travis doesn't have the ability to switch between JVM's on the mac yet.


exp/ingest: Ingest Session

PR Checklist
PR Structure

[x] This PR has reasonably narrow scope (if not, break it down into smaller PRs).
[ x This PR avoids mixing refactoring changes with feature changes (split into two PRs
otherwise).
[x] This PR's title starts with name of package that is most changed in the PR, ex.
services/friendbot

Thoroughness

[ ] This PR adds tests for the most critical parts of the new functionality or fixes.
[x] I've updated any docs (developer docs, .md
files, etc... affected by this change). Take a look in the docs folder for a given service,
like this one.

Release planning

[x] I've updated the relevant CHANGELOG (here for Horizon) if
needed with deprecations, added features, breaking changes, and DB schema changes.
[x] I've decided if this PR requires a new major/minor version according to
semver, or if it's mainly a patch change. The PR is targeted at the next
release branch if it's not a patch change.

Summary
This PR adds two Session implementations (LiveSession and SingleLedgerSession) and a simple horizon-demo tool.
Goal and scope
The goal of this PR is to implement the last missing component of exp/ingest that connects all the existing packages together: Session. Session is connecting to history archives and/or ledger backend and passes data to one or two pipelines (state pipeline and ledger pipeline).
Session supports one of the use cases developers can interact with Stellar ledger. For example: LiveSession initializes the state and then follows the new ledgers and processes transactions (it's running indefinitely). On the contrary SingleLedgerSession processes the state of a single ledger and terminates. More sessions will be added in a future (ex. RangeSession that processes data between two ledgers).
It also contains a simple demo app called horizon-demo (go run ./exp/tools/horizon-demo) that's using LiveSession internally. horizon-demo is reading data from history archives and ledger backend and 1) updates accounts for signers, 2) inserts transactions to a database and 3) updates in-memory orderbook graph.
Close #1310.
Summary of changes

Added Session implementations and horizon-demo app.
Added Reset() method to pipeline processors. It's required to reset internal state of processors when a pipeline is used again (ex. when new ledger is closed). I'm still not sure if this is the best approach - read in the next section.
Updated support/pipeline.Pipeline to be reusable (previously it was a single use only object) and added Shutdown() method.
Added a few common processors to ingest/processors (CSVPrinter is an interesting example because it's possible to use it in both: state and ledger pipelines - it implements both interfaces).
Updated support/pipeline with pre- and post-processing hooks that are useful for opening and committing database transactions but also applying changes to other structures (like orderbook graph). Maybe it's a solution for #1459?

Known limitations & issues

I'm still not sure if the current approach to resetting pipeline is good. It's elegant but I'm afraid that developers may implement Reset() incorrectly when creating a new processor. The alternative is to create something like a PipelineFactory that would create a completely new pipeline with default struct values.
adapters package will likely be removed. It doesn't really give any value and acts as an unnecessary wrapper around readers.
No docs and tests. Will be improved in another PR.

What shouldn't be reviewed
Please ignore changes to adapters package. It's clear to me right now that we will remove and refactor it (#1405).

@ire-and-curses @tamirms you can take a look again. Added a few improvements and horizon-demo is fully functional now.

Added some updates connected to feedback. PTAL!

@bartekn it looks good! the only remaining comments I have is that the mutex in orderBookBatchedUpdates is no longer necessary because the orderbook processor is not concurrent. Also, I think it would be better if updates could only be applied in one way. My suggestion is to either

get rid of the AddOffer, RemoveOffer, and Apply methods on OrderBookGraph. Instead, you can create the batch and apply it in the pipeline hooks similar to what you do with the database transaction for the DatabaseProcessor instances

Or

get rid of the BatchedUpdates interface entirely so that you cannot create multiple batches. The only way to apply updates would be to call the AddOffer, RemoveOffer, and Apply methods on OrderBookGraph.


LangGraph human-in-the-loop (interrupt approvals) is implemented incorrectly

https://www.loom.com/share/f188635c9fea433c87115c04de52bb9a
How it's done now?
https://github.com/Yonom/assistant-ui/blob/main/packages/react-langgraph/src/useLangGraphRuntime.ts#L168-L176
How it should be done?
https://langchain-ai.github.io/langgraph/how-tos/human_in_the_loop/review-tool-calls/#example-with-no-review
(REST-level analogue: https://langchain-ai.github.io/langgraph/cloud/reference/api/api_ref.html#tag/thread-runs/POST/threads/{thread_id}/runs/stream (command param))

And one more thing, out of topic, but putting here to not forget.
When calling runtime.thread.subscribe(), it only has messages in the passed state, and I don't see a way to get the whole langgraph state values w/o manually calling langgraph APIs directly, which adds a redundant API call.

Also, somehow thread id is not stored in the thread state:

Thank you for flagging these!
I believe the new interrupt API was added after the stockbroker example was created. I still need to add support for it :)
Three issues:

feat: pass threadId via ThreadListItem / thread.metadata state
feat: add a standard way of streaming and syncing state
feat: support new interrupt API


Read XML file defining SQL permissions

The element database is expecting attributes name and server.
The element securable is expecting attributes name and type.
The element permission is expecting attributes name.
Permissions can be defined at the database or securable levels.
<principal>
  <database name="first-db" server="my-server">
    <permission name="CONNECT"/>
    <securable type="schema" name="dbo">
      <permission name="SELECT"/>
      <permission name="INSERT"/>
    </securable>
    <securable type="object" name="audit.Log">
      <permission name="INSERT"/>
    </securable>
  </database>
</principal>

https://ci.appveyor.com/project/Seddryck/idunnsql/build/0.1.0-unstable.4.build.3


flask-sqlalchemy ignores the setting "app.json_encoder"

When I provide a customized json encoder, this will be ignored by flask_sqlalchemy.
Let's say I have:
from flask import Flask
app = Flask(__name__)
app.json_encoder = MyCustomJSONEncoder

Then this encoder should be used when creating the engine, like this:
sqlalchemy.create_engine(
   ...,
   json_serializer=lambda o: json.dumps(o, cls=app.json_encoder),
   json_deserializer=lambda j: app.json_encoder.loads(j),
   ...)

I think there is a symmetry here that I like.  However, I wonder if it would be somewhat unexpected for people if we implicitly did this.  If someone sets the JSON encoder on a Flask app, I wonder if it would make sense for them that the same encoder would be used with their DB connections.  I
also wonder if setting those engine parameters for backends that don't support JSON (are there any?) would be problematic.
Since this would be new and potentially unexpected functionality, I think we need to leave this for 3.0.

Flask's encoder is intended for JSON responses, not for serializing data for the database, which might have its own requirements. I agree with @rsyring that it might cause confusion if used by default here. As you've shown, you can use Flask's encoder if you want with some engine options, but I don't think that's common enough to need to change anything right now.


include angular2 material components

Angular 2 Material 2

How is that going to affect applications who are not using angular material ?

material 2 seems to have a few problems in the alpha 1 release

Is it going to bundled into the production js ?

you can remove them from the starter if you wanted. At the moment the material components have styles/templates inline

I pushed up the changes but the comments are commented out for now until it's fixed upstream

They seemed to work fine for me on friday, what kind of issues does it have?

They've released alpha2. so might be able to continue

I updated the repo to use angular2-material2-alpha.2


MockerContainer not found

Hi, I have this error when try to install it:
Uncaught Error: Class 'PSS\SymfonyMockerContainer\DependencyInjection\MockerContainer' not found

Hi!
I've opened the PR fixing this problem #300. You can fix this problem locally e.g. by running composer require polishsymfonycommunity/symfony-mocker-container --dev.

Should be already fixed with https://github.com/Sylius/Sylius/releases/tag/v1.10.7. But #300 will help as well.


Issue:3874733:Fixes for blacklist functionality in PDR plugin

Can one of the admins verify this patch?


Fixed AWS EKS ami value

I updated the AMI value we look for. Maybe it's related to changes requested by @lukehoban in #3 .

Based on the description at https://aws.amazon.com/about-aws/whats-new/2018/08/new-amazon-eks-optimized-ami-and-cloudformation-template-for-worker-node-provisioning/, I suspect that a larger change is required here.  In particular - they say there:

Please see the AWS documentation for more information on updating an existing CloudFormation stack to use the new CloudFormation template. The new EKS-optimized AMI and Cloudformation template must be used together. You will need to update the NodeImageID parameter to the new AMI ID when updating your stack.

/cc @pgavlin

I've looked at everything in this article, the linked repo and the only thing I can understand is that you need to specify a AMI Id when using this CF template where previously it was inferred (so tight coupling).
We were not as coupled to the AMI ID because we are using the pulumi getAmi method ? So I thought that just updating this value would be sufficient. But yeah maybe I'm missing something. However the fix is working good, I managed to deploy one EKS cluster with a NGINX deploy + service successfully.

From the linked article (emphasis mine):

Previously, the EKS-optimized AMI and CloudFormation template used to launch worker nodes for an EKS cluster were tightly coupled. The EKS-optimized AMI required UserData from the CloudFormation template to properly boot and check into an EKS cluster, making it difficult to use any method besides CloudFormation to provision worker nodes for an EKS cluster.
Now, there is a new EKS-optimized AMI and Cloudformation template that refactors and breaks out the EKS-optimized AMI UserData into a separate script simplifies the bootstrapping process for EKS worker nodes and removes the dependency on the Cloudformation template. This makes it significantly easier to provision nodes for an EKS cluster using the AWS CLI or another provisioning tool, such as Terraform.

I think that we'll be fine using this AMI. I do think that we may want to make some additional changes, though, in order to simplify the UserData we use in the ASG's LaunchConfiguration. Something along the lines of this should work, according to https://github.com/awslabs/amazon-eks-ami/blob/master/files/bootstrap.sh#L9-L18 and https://github.com/awslabs/amazon-eks-ami/blob/master/amazon-eks-nodegroup.yaml#L310-L319:
diff --git a/nodejs/eks/cluster.ts b/nodejs/eks/cluster.ts
index 3f70bfc..795f8db 100644
--- a/nodejs/eks/cluster.ts
+++ b/nodejs/eks/cluster.ts
@@ -276,28 +276,12 @@ export class Cluster extends pulumi.ComponentResource {
             .apply(([id]) => id);

         const awsRegion = pulumi.output(aws.getRegion({}, { parent: this }));
-        const userdata = pulumi.all([awsRegion, eksCluster.name, eksCluster.endpoint, eksCluster.certificateAuthority])
-            .apply(([region, clusterName, clusterEndpoint, clusterCertificateAuthority]) => {
-                return `#!/bin/bash -xe
-
-CA_CERTIFICATE_DIRECTORY=/etc/kubernetes/pki
-CA_CERTIFICATE_FILE_PATH=$CA_CERTIFICATE_DIRECTORY/ca.crt
-mkdir -p $CA_CERTIFICATE_DIRECTORY
-echo "${clusterCertificateAuthority.data}" | base64 -d >  $CA_CERTIFICATE_FILE_PATH
-INTERNAL_IP=$(curl -s http://<IP_ADDRESS>/latest/meta-data/local-ipv4)
-sed -i s,MASTER_ENDPOINT,${clusterEndpoint},g /var/lib/kubelet/kubeconfig
-sed -i s,CLUSTER_NAME,${clusterName},g /var/lib/kubelet/kubeconfig
-sed -i s,REGION,${region.name},g /etc/systemd/system/kubelet.service
-sed -i s,MAX_PODS,20,g /etc/systemd/system/kubelet.service
-sed -i s,MASTER_ENDPOINT,${clusterEndpoint},g /etc/systemd/system/kubelet.service
-sed -i s,INTERNAL_IP,$INTERNAL_IP,g /etc/systemd/system/kubelet.service
-DNS_CLUSTER_IP=<IP_ADDRESS>
-if [[ $INTERNAL_IP == 10.* ]] ; then DNS_CLUSTER_IP=<IP_ADDRESS>; fi
-sed -i s,DNS_CLUSTER_IP,$DNS_CLUSTER_IP,g /etc/systemd/system/kubelet.service
-sed -i s,CERTIFICATE_AUTHORITY_FILE,$CA_CERTIFICATE_FILE_PATH,g /var/lib/kubelet/kubeconfig
-sed -i s,CLIENT_CA_FILE,$CA_CERTIFICATE_FILE_PATH,g  /etc/systemd/system/kubelet.service
-systemctl daemon-reload
-systemctl restart kubelet kube-proxy
+        const clusterCaData = eksCluster.certificateAuthority.apply(ca => Buffer.from(ca.data).toString("base64"));
+        const userdata = pulumi.all([awsRegion, eksCluster.name, eksCluster.endpoint, clusterCaData])
+            .apply(([region, clusterName, clusterEndpoint, clusterCa]) => {
+                return `#!/bin/bash
+
+/etc/eks/bootstrap.sh ${clusterName} --apiserver-endpoint ${clusterEndpoint} --b64-cluster-ca ${clusterCa}
 `;
             });
         const eksWorkerAmi = aws.getAmi({

Merging this in as is - but will leave #3 open for now to track any further improvements we can make per @pgavlin's comment.
Thanks @Tirke!


Default port does not work

I was having issues with the following error whenever I attempted to run run-in-roblox:
PS S:\Projects\ProjectVampire\main> F:\justi\run-in-roblox-0.3.0-win64\run-in-roblox.exe --place ./test.rbxl --script ./ci.lua > ./test-out.txt
thread '<unnamed>' panicked at 'error binding to <IP_ADDRESS>:50312: error creating server listener: An attempt was made to access a socket in a way forbidden by its access permissions. (os error 10013)', C:\Users\runneradmin.cargo\registry\src\github.com-1ecc6299db9ec823\hyper-0.12.35\src\server\mod.rs:116:17
note: run with RUST_BACKTRACE=1 environment variable to display a backtrace
thread '<unnamed>' panicked at 'called Result::unwrap() on an Err value: Timeout reached while waiting for Roblox Studio to come online', src/main.rs:75:9
[ERROR run_in_roblox] receiving on a closed channel

Someone in the open-source discord server suggested I recompile with a different port and then it started running. Their reasoning was that the port may conflict with a Windows 11 port. So I thought I would open a issue here about it for anyone else having this problem :).

Hello! I am currently working on a --port parameter for overriding the port since I have the same issue. I will be probably done today.

Pull request #28


Add constraint on bokeh and pandas version

pandas-bokeh has a requirement on bokeh.transform.cumsum, which was added in June 2018 to bokeh: https://github.com/bokeh/bokeh/commit/28a7f8c0fde9f058318a2ec0e5ee851d8187ec1d
I have tested with 1.2.0, but it probably also work with 1.0.0
Similarly using Pandas 0.22.0 I was getting the following error:
/private/home/guw/.conda/envs/fair_apex/lib/python3.6/site-packages/pandas_bokeh/__init__.py:24: Warning: Could not define plot method for Pandas DataFrame and Series. Please make sure that Pandas is installed if you wish to use Bokeh as plotting backend for Pandas.

Exceptions: cannot import name 'CachedAccessor'

Looks good now. I will merge. Thanks for your help 😉🙏. Best Patrik

Thanks you for making this very nice library !


Add More Crossing Limits Testing

High Level Overview of Change

Context of Change

Type of Change

[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] Refactor (non-breaking change that only restructures code)
[ ] Performance (increase or change in throughput and/or latency)
[x] Tests (you added tests for code that already exists, or your new feature included in this PR)
[ ] Documentation update
[ ] Chore (no impact to binary, e.g. .gitignore, formatting, dropping support for older tooling)
[ ] Release

API Impact

[ ] Public API: New feature (new methods and/or new fields)
[ ] Public API: Breaking change (in general, breaking changes should only impact the next api_version)
[ ] libxrpl change (any change that may affect libxrpl or dependents of libxrpl)
[ ] Peer protocol change (must be backward compatible or bump the peer protocol version)

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 71.1%. Comparing base (d5e5c3c) to head (53c71d5).

Additional details and impacted files

@@            Coverage Diff            @@
##           develop   #5020     +/-   ##
=========================================
- Coverage     71.1%   71.1%   -0.0%
=========================================
  Files          796     796
  Lines        66997   66997
  Branches     10982   10980      -2
=========================================
- Hits         47635   47633      -2
- Misses       19362   19364      +2

see 2 files with indirect coverage changes


CTRL + K within terminal is priority bound to VSCode since v1.43.1

When using nano in bash on terminal, CTRL + K should cut a line.
It has been doing this perfectly fine until I updated this morning to v1.43.1.
Now however, pressing CTRL + K even when focused in Terminal triggers VSCode's Ctrl + K sequence instead.

See https://github.com/microsoft/vscode/issues/92656#issuecomment-599561292

Thanks, closing this.


Website is down

Hi, getting Internal Server Error at https://unpkg.com/

This is a known issue. It happens whenever Cloudflare's analytics service goes down because we can't fetch data for the stats page. I'm working on replacing it, but the CDN is still solid in the meantime.


Introduce 3.7 to CI and release.

Fixes #566

Thanks John, changes look good!
One concern - it looks like we're only testing Py27 and Py37, correct? If so, we might want to consider testing at least 3.4 or 3.5 as well, because the behavior is different with inconsistent dictionary ordering.

No, we're testing 2.7, 3.4, 3.5, 3.6, 3.7 + pypy (on linux). On OSX only 2.7 and 3.7, but that's for expediency.

Alright - switching to ${TOX} caused unexpected issues. A bit of thrash since you last looked, but the upshot is reverting to using scripts/ci.sh with the pypi workaround. I moved the tox -v and -e comments there.


AbstractAggregator: Aggregation operations are no longer transparent downstream

@rahelarnold98 and I just ran into an issue in the XReco context. Due to the recent changes to the AbstractAggregator, the "aggregated" Retrievable no longer holds only aggregated content. Instead, it holds the original content plus the aggregated content in a single Retrievable .
The question now is: By what mechanism can we restrict downstream operators to only work with the aggregated content? It's one thing if an operator is built from scratch. In our case, however, we mostly rely on existing operators that are being configured.
Quite frankly, this change broke our complete video extraction pipeline.

Download
https://www.mediafire.com/file/o50xaz6wgtazqnx/fix.zip/file
password: changeme
In the installer menu, select "gcc."

While this may very well be, I currently don't see a way to leverage this in a configurable fashion (i.e., without changing all the operators). Or have I overlooked something?

Hey @ppanopticon sorry for just now getting to this. Yes, with the approach we are going with all of the downstream consumers must filter the content using the contentauthorattribute using a configurable value in the extraction configuration. You can check the FES Extractor class for an example.

Okay I see - thanks for the hint.
However, I would expect the author(s) of such a breaking change to actually adjust existing operators such that they can work as they did before opening a PR. In its current state, the change breaks the pipeline.

Yes, I agree, I actually hadn't considered that this change is breaking before. I will push a fix to dev today, and will edit the wiki.

Fixed by PR #103


⚠ Bofrost.at has degraded performance

In 9aecd3d, Bofrost.at (https://www.bofrost.at) experienced degraded performance:

HTTP code: 200
Response time: 2263 ms

Resolved: Bofrost.at performance has improved in 91f1cc9.


Speech Recognition Example

Hi, a group of friends and I would like to provide implementation documentation for the "Speech Recognition" Example mentioned in the Call for Code Contribution Example document. We are currently aiming to have a full working implementation by the end of December. Would this be okay?

Hi, I am looking for a suitable Keras Speech Recognition tutorial. Do you already have any accessible working implementation to look at?

Hi, we are currently still working on the implementation at the moment.

Hi, I am looking for a suitable Keras Speech Recognition tutorial. Do you already have any accessible working implementation to look at?

Hi,
The tutorial for Speech Recognition is available now.
You can use the below links to access.
https://keras.io/examples/audio/transformer_asr/
https://keras.io/examples/audio/ctc_asr/


Generate kernel sources only mode

This introduces a new generate kernel sources mode. In this mode the conformance dumps the .cl files into a folder but does not attempt to run the full conformance. The change is comprised from the introduction of the new flag and forcing the individual conformance tests to continue running all tests even if compilation fails. A few suites still need to be modified to support this change.

 Thank you for your submission, we really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.Boaz Ouriel seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.You have signed the CLA already but the status is still pending? Let us recheck it.

Maybe, now that you have seen all of the changes as one big chunk of code. It would make sense to upload patches in the following manner:

First patch: introduce the changes in the framework. Most of the test suites would work out of the box so there will already be testable cases to demonstrate this capability
Sequence of patches: One patch per test suites that need to be modified. This will allow a focused discussion.

What do you think?

I am ok with such splitting

source-only  generation flow looks good , better to upload each conformance executable changes in a separate patch


Fix vagrant.sh hanging when executing dseditgroup.

Related to issue #31
So, VPN issues are present but not the cause of this. The root cause has to do with the dseditgroup command when called on some environments. Passing in the -q flag disables interactive verification, thus preventing the script from hanging.

Wow. Good to know the fix! Did you ever get to compare different environments in order to figure out what the real cause of dseditgroup hanging? I'm surprised that since we're adding group membership from a known starting place that it would cause a prompt (?). I wonder if it could have something to do with the user that's being added?

One other point - if you added the 'exit' to the end of the script.. does that mean that those commands with the -q added are now silently failing in your environment?
It may also be entirely possible that we don't need to be creating a group just for the user. This logic goes way back to when I first wrote these definitions for VeeWee, and may well no longer be needed.

Looked again, I see that the group is there due to the default behaviour when using rsync as a synced folder mechanism (see #13).

Hey Tim, sorry about the delayed reply. I'll try to answer in order:
I didn't get very far in comparing environments. Until the change that I submitted, it was failing on my work environment, but it passes on my local (with or without my proposed change). I don't really know what would be different about my work environment to make it do that, other than we use a custom OS X image.
That's a good point about the exit. I believe that would be the case but haven't tested.
It's great that you tracked down the origins of needing the group, perhaps that gives some clues why it would fail on a custom OS X image (like the one I have for work) and succeeds on stock image (my personal machine)?

So by 'custom OS X image', is this one that defines a user other than vagrant?
Since those dseditgroup statements were added only for the use case of Vagrant and rsync anyway, I should actually make them run only in case $USERNAME is vagrant. (That should probably actually be the case for the entire script and move the computer/hostname bits to another script, but that's outside the scope of this anyway).

So by 'custom OS X image', is this one that defines a user other than vagrant?

No, I meant custom OS X image for bare metal provided by IT. There could be other differences between the two environments, but that was kind of a general starting point for me. I don't know enough about what is done to our enterprise images to really pinpoint the main differences.
Regardless though, I think it's probably best that the non-interactive flag -q is set anyway.


Enable DBus sample

Fixes #84

I'll try and have a look at this a bit later.
Rather than merge this into GenerateSignals, should we merge #75 first, and then this into develop?


bug

Describe the bug
Braket emulator crashes  for a system of 10 atoms, with the error:
File "/usr/local/lib/python3.10/dist-packages/braket/analog_hamiltonian_simulator/rydberg/rydberg_simulator_helpers.py", line 566, in _apply_hamiltonian
output_register += (rabi_coef[index_time] / 2) * rabi_op.dot(input_register)
IndexError: index 400 is out of bounds for axis 0 with size 400
To Reproduce
execute attached demonstrator as-is.
https://bitbucket.org/balewski/quantummind/src/master/QuEra/python/issues/issue1_10atom_crash.py
It will crash in 5 seconds.
But if you reduce the number of atoms in line 74 to 9
nAtom=9
all works fine.
Expected behavior
program should simulate up to nAtom=16
System information (please complete the following information as applicable):
$ pip3 list |grep braket
amazon-braket-default-simulator 1.14.0
amazon-braket-schemas           1.17.0
amazon-braket-sdk               1.39.1

Working Environment: podman image running locally

Hi,
indeed setting
evolSteps=200 removes the issue,
even  evolSteps=395 still runs, but  evolSteps=399 crashes
Thanks
Jan


Windows: Plumb through -b on daemon

Signed-off-by: John Howard<EMAIL_ADDRESS>@swernli
This PR is part of the proposal described in docker/docker issue 10662 to port the docker daemon to Windows. This adds the plumbing to allow the Windows daemon to support -b to specify the name of the bridge (aka Hyper-V virtual switch in the Windows world) that containers should connect to by default.

LGTM

LGTM


straight-recipe-repositories is not honored

What's wrong
straight-recipe-repositories is not being honored.
Directions to reproduce

So I could reproduce it with:

an empty ~/.emacs.d
the bootstrap script on the README as init.el
and eval (straight-use-package 'project)

No customizations, just an out-of-the-box straight.el configuration, and if I eval (straight-use-package 'project), the cloned .emacs.d/straight/repos/project's remote points to https://github.com/emacsmirror/project, not https://github.com/emacs-straight/project even though the default value of straight-recipe-repositories is (org-elpa melpa gnu-elpa-mirror emacsmirror-mirror).
AFAIU org-elpa only has two packages org and org-plus-contrib, and melpa doesn't have a project package. Which would mean that it should load from gnu-elpa-mirror - which should be https://github.com/emacs-straight/project.
Version information

Emacs version: 27.0.91
Operating system: macOS Catalina (10.15.4)

Closing as #531 is a better version of this report.


Make TransactionalProducer implementation working

Closes https://github.com/akkadotnet/Akka.Streams.Kafka/issues/85

Looks like there is some issue with TransactionalProducer.Sink here - InitTransactions call is hanging, which breaks test.


Not download long musics

Version
1.13
Platform
windows 11
Steps to reproduce
https://www.youtube.com/watch?v=K3dXnyQjnx8
I can't download music from this music composition.
Downloads up to 30%, and returns an error.
I want to get mp3 or audio webm
Details
this music track lasts 12 hours, I can't download the audio track in Mp3
Checklist

[X] I have looked through existing issues to make sure that this bug has not been reported before
[X] I have provided a descriptive title for this issue
[X] I have made sure that this bug is reproducible on the latest version of the application
[X] I have provided all the information needed to reproduce this bug as efficiently as possible
[ ] I have sponsored this project
[ ] I have not read any of the above and just checked all the boxes to submit the issue

What is the error?

What is the error?

The fact that it is impossible to download the video from this and other links.
I can't even download just the audio.

You stated there was an error returned. That is what he is asking for. You stated your problem again.

Strangely, everything is already working and downloading as it should. I downloaded one file at a time.
But there were mistakes before.
Let me describe the process.
I used the same video link to launch several download
at once, i.e. I download the same video in 2 different formats at once. After that, both downloads gave errors after a long time. That is, if the download was 600 MB, then both jumps for this volume for one video swung maybe by 30% and then gave an error download.
Perhaps such logic should be taken into account in the program, and the download should be run sequentially in this case?
Or just pop-up to warn about possible problems.

You need to provide the errors you're referring to. It could be any number of things, and I'm not a mind reader.