text:
vault resources not being deleted after CR is removed from ocp

When testing this operator on openshift, installed from OLM resource creation is working as expected but when deleting the CRs from the cluster the resources do not get deleted from vault
We are hoping for full resource lifecycle management to enhance the gitops experience of managing vault in ocp and from what i can gather from previous issues etc deletion should work?
OCP 4.12.7
vault-config-operator.v0.8.13
Vault 1.12.1 (FOSS)
testing with resource:
apiVersion: redhatcop.redhat.io/v1alpha1
kind: Policy
metadata:
  name: secret-reader
spec:
  authentication:
    path: kubernetes
    role: vault-config-operator
  policy: |
    path "/*" {
      capabilities = [ "read", "list" ]
    }

policy attached to the vault-config-operator role (kubernetes auth)
path "*" {
  capabilities = ["create", "read", "update", "delete", "list", "sudo"]
}

full logs from creation and attempted deletion of the resource:
0414 14:20:17.585002       1 request.go:601] Waited for 1.006643189s due to client-side throttling, not priority and fairness, request: GET:https://172.30.0.1:443/apis/ingress.operator.openshift.io/v1?timeout=32s
1.6814820206536129e+09	INFO	controller-runtime.metrics	Metrics server is starting to listen	{"addr": "127.0.0.1:8080"}
1.6814820206713262e+09	INFO	setup	starting AuthEngineMountReconciler
1.6814820206714294e+09	INFO	setup	started AuthEngineMountReconciler
1.6814820206728244e+09	INFO	controller-runtime.builder	Registering a mutating webhook	{"GVK": "redhatcop.redhat.io/v1alpha1, Kind=RandomSecret", "path": "/mutate-redhatcop-redhat-io-v1alpha1-randomsecret"}
1.6814820206733158e+09	INFO	controller-runtime.webhook	Registering webhook	{"path": "/mutate-redhatcop-redhat-io-v1alpha1-randomsecret"}
1.6814820206735654e+09	INFO	controller-runtime.builder	Registering a validating webhook	{"GVK": "redhatcop.redhat.io/v1alpha1, Kind=RandomSecret", "path": "/validate-redhatcop-redhat-io-v1alpha1-randomsecret"}
1.6814820206737475e+09	INFO	controller-runtime.webhook	Registering webhook	{"path": "/validate-redhatcop-redhat-io-v1alpha1-randomsecret"}
1.6814820206739566e+09	INFO	controller-runtime.builder	Registering a mutating webhook	{"GVK": "redhatcop.redhat.io/v1alpha1, Kind=SecretEngineMount", "path": "/mutate-redhatcop-redhat-io-v1alpha1-secretenginemount"}
1.6814820206741192e+09	INFO	controller-runtime.webhook	Registering webhook	{"path": "/mutate-redhatcop-redhat-io-v1alpha1-secretenginemount"}
1.6814820206742165e+09	INFO	controller-runtime.builder	Registering a validating webhook	{"GVK": "redhatcop.redhat.io/v1alpha1, Kind=SecretEngineMount", "path": "/validate-redhatcop-redhat-io-v1alpha1-secretenginemount"}
1.6814820206743834e+09	INFO	controller-runtime.webhook	Registering webhook	{"path": "/validate-redhatcop-redhat-io-v1alpha1-secretenginemount"}
1.6814820206745172e+09	INFO	controller-runtime.builder	Registering a mutating webhook	{"GVK": "redhatcop.redhat.io/v1alpha1, Kind=DatabaseSecretEngineRole", "path": "/mutate-redhatcop-redhat-io-v1alpha1-databasesecretenginerole"}
1.681482020674655e+09	INFO	controller-runtime.webhook	Registering webhook	{"path": "/mutate-redhatcop-redhat-io-v1alpha1-databasesecretenginerole"}
1.6814820206747682e+09	INFO	controller-runtime.builder	Registering a validating webhook	{"GVK": "redhatcop.redhat.io/v1alpha1, Kind=DatabaseSecretEngineRole", "path": "/validate-redhatcop-redhat-io-v1alpha1-databasesecretenginerole"}
1.6814820206749237e+09	INFO	controller-runtime.webhook	Registering webhook	{"path": "/validate-redhatcop-redhat-io-v1alpha1-databasesecretenginerole"}
1.6814820206750576e+09	INFO	controller-runtime.builder	Registering a mutating webhook	{"GVK": "redhatcop.redhat.io/v1alpha1, Kind=DatabaseSecretEngineConfig", "path": "/mutate-redhatcop-redhat-io-v1alpha1-databasesecretengineconfig"}
1.6814820206751962e+09	INFO	controller-runtime.webhook	Registering webhook	{"path": "/mutate-redhatcop-redhat-io-v1alpha1-databasesecretengineconfig"}
1.6814820206753953e+09	INFO	controller-runtime.builder	Registering a validating webhook	{"GVK": "redhatcop.redhat.io/v1alpha1, Kind=DatabaseSecretEngineConfig", "path": "/validate-redhatcop-redhat-io-v1alpha1-databasesecretengineconfig"}
1.681482020675655e+09	INFO	controller-runtime.webhook	Registering webhook	{"path": "/validate-redhatcop-redhat-io-v1alpha1-databasesecretengineconfig"}
1.681482020676072e+09	INFO	controller-runtime.builder	Registering a mutating webhook	{"GVK": "redhatcop.redhat.io/v1alpha1, Kind=KubernetesAuthEngineRole", "path": "/mutate-redhatcop-redhat-io-v1alpha1-kubernetesauthenginerole"}
1.681482020676299e+09	INFO	controller-runtime.webhook	Registering webhook	{"path": "/mutate-redhatcop-redhat-io-v1alpha1-kubernetesauthenginerole"}
1.6814820206764193e+09	INFO	controller-runtime.builder	Registering a validating webhook	{"GVK": "redhatcop.redhat.io/v1alpha1, Kind=KubernetesAuthEngineRole", "path": "/validate-redhatcop-redhat-io-v1alpha1-kubernetesauthenginerole"}
1.6814820206766047e+09	INFO	controller-runtime.webhook	Registering webhook	{"path": "/validate-redhatcop-redhat-io-v1alpha1-kubernetesauthenginerole"}
1.6814820206767902e+09	INFO	controller-runtime.builder	Registering a mutating webhook	{"GVK": "redhatcop.redhat.io/v1alpha1, Kind=AuthEngineMount", "path": "/mutate-redhatcop-redhat-io-v1alpha1-authenginemount"}
1.6814820206768975e+09	INFO	controller-runtime.webhook	Registering webhook	{"path": "/mutate-redhatcop-redhat-io-v1alpha1-authenginemount"}
1.6814820206769853e+09	INFO	controller-runtime.builder	Registering a validating webhook	{"GVK": "redhatcop.redhat.io/v1alpha1, Kind=AuthEngineMount", "path": "/validate-redhatcop-redhat-io-v1alpha1-authenginemount"}
1.6814820206771195e+09	INFO	controller-runtime.webhook	Registering webhook	{"path": "/validate-redhatcop-redhat-io-v1alpha1-authenginemount"}
1.6814820206772616e+09	INFO	controller-runtime.builder	Registering a mutating webhook	{"GVK": "redhatcop.redhat.io/v1alpha1, Kind=KubernetesAuthEngineConfig", "path": "/mutate-redhatcop-redhat-io-v1alpha1-kubernetesauthengineconfig"}
1.6814820206773753e+09	INFO	controller-runtime.webhook	Registering webhook	{"path": "/mutate-redhatcop-redhat-io-v1alpha1-kubernetesauthengineconfig"}
1.681482020677464e+09	INFO	controller-runtime.builder	Registering a validating webhook	{"GVK": "redhatcop.redhat.io/v1alpha1, Kind=KubernetesAuthEngineConfig", "path": "/validate-redhatcop-redhat-io-v1alpha1-kubernetesauthengineconfig"}
1.6814820206776085e+09	INFO	controller-runtime.webhook	Registering webhook	{"path": "/validate-redhatcop-redhat-io-v1alpha1-kubernetesauthengineconfig"}
1.6814820206777525e+09	INFO	controller-runtime.builder	Registering a mutating webhook	{"GVK": "redhatcop.redhat.io/v1alpha1, Kind=LDAPAuthEngineConfig", "path": "/mutate-redhatcop-redhat-io-v1alpha1-ldapauthengineconfig"}
1.6814820206779675e+09	INFO	controller-runtime.webhook	Registering webhook	{"path": "/mutate-redhatcop-redhat-io-v1alpha1-ldapauthengineconfig"}
1.6814820206780863e+09	INFO	controller-runtime.builder	Registering a validating webhook	{"GVK": "redhatcop.redhat.io/v1alpha1, Kind=LDAPAuthEngineConfig", "path": "/validate-redhatcop-redhat-io-v1alpha1-ldapauthengineconfig"}
1.681482020678282e+09	INFO	controller-runtime.webhook	Registering webhook	{"path": "/validate-redhatcop-redhat-io-v1alpha1-ldapauthengineconfig"}
1.6814820206785207e+09	INFO	controller-runtime.builder	Registering a mutating webhook	{"GVK": "redhatcop.redhat.io/v1alpha1, Kind=LDAPAuthEngineGroup", "path": "/mutate-redhatcop-redhat-io-v1alpha1-ldapauthenginegroup"}
1.6814820206787267e+09	INFO	controller-runtime.webhook	Registering webhook	{"path": "/mutate-redhatcop-redhat-io-v1alpha1-ldapauthenginegroup"}
1.6814820206788611e+09	INFO	controller-runtime.builder	Registering a validating webhook	{"GVK": "redhatcop.redhat.io/v1alpha1, Kind=LDAPAuthEngineGroup", "path": "/validate-redhatcop-redhat-io-v1alpha1-ldapauthenginegroup"}
1.6814820206790662e+09	INFO	controller-runtime.webhook	Registering webhook	{"path": "/validate-redhatcop-redhat-io-v1alpha1-ldapauthenginegroup"}
1.681482020679305e+09	INFO	controller-runtime.builder	Registering a mutating webhook	{"GVK": "redhatcop.redhat.io/v1alpha1, Kind=JWTOIDCAuthEngineConfig", "path": "/mutate-redhatcop-redhat-io-v1alpha1-jwtoidcauthengineconfig"}
1.681482020679545e+09	INFO	controller-runtime.webhook	Registering webhook	{"path": "/mutate-redhatcop-redhat-io-v1alpha1-jwtoidcauthengineconfig"}
1.681482020679683e+09	INFO	controller-runtime.builder	Registering a validating webhook	{"GVK": "redhatcop.redhat.io/v1alpha1, Kind=JWTOIDCAuthEngineConfig", "path": "/validate-redhatcop-redhat-io-v1alpha1-jwtoidcauthengineconfig"}
1.681482020679931e+09	INFO	controller-runtime.webhook	Registering webhook	{"path": "/validate-redhatcop-redhat-io-v1alpha1-jwtoidcauthengineconfig"}
1.6814820206801457e+09	INFO	controller-runtime.builder	Registering a mutating webhook	{"GVK": "redhatcop.redhat.io/v1alpha1, Kind=JWTOIDCAuthEngineRole", "path": "/mutate-redhatcop-redhat-io-v1alpha1-jwtoidcauthenginerole"}
1.681482020680276e+09	INFO	controller-runtime.webhook	Registering webhook	{"path": "/mutate-redhatcop-redhat-io-v1alpha1-jwtoidcauthenginerole"}
1.6814820206803668e+09	INFO	controller-runtime.builder	Registering a validating webhook	{"GVK": "redhatcop.redhat.io/v1alpha1, Kind=JWTOIDCAuthEngineRole", "path": "/validate-redhatcop-redhat-io-v1alpha1-jwtoidcauthenginerole"}
1.681482020680679e+09	INFO	controller-runtime.webhook	Registering webhook	{"path": "/validate-redhatcop-redhat-io-v1alpha1-jwtoidcauthenginerole"}
1.6814820206808207e+09	INFO	controller-runtime.builder	Registering a mutating webhook	{"GVK": "redhatcop.redhat.io/v1alpha1, Kind=VaultSecret", "path": "/mutate-redhatcop-redhat-io-v1alpha1-vaultsecret"}
1.6814820206810365e+09	INFO	controller-runtime.webhook	Registering webhook	{"path": "/mutate-redhatcop-redhat-io-v1alpha1-vaultsecret"}
1.6814820206814606e+09	INFO	controller-runtime.builder	Registering a validating webhook	{"GVK": "redhatcop.redhat.io/v1alpha1, Kind=VaultSecret", "path": "/validate-redhatcop-redhat-io-v1alpha1-vaultsecret"}
1.6814820206816597e+09	INFO	controller-runtime.webhook	Registering webhook	{"path": "/validate-redhatcop-redhat-io-v1alpha1-vaultsecret"}
1.6814820206819408e+09	INFO	controller-runtime.builder	Registering a mutating webhook	{"GVK": "redhatcop.redhat.io/v1alpha1, Kind=PasswordPolicy", "path": "/mutate-redhatcop-redhat-io-v1alpha1-passwordpolicy"}
1.6814820206822379e+09	INFO	controller-runtime.webhook	Registering webhook	{"path": "/mutate-redhatcop-redhat-io-v1alpha1-passwordpolicy"}
1.6814820206824288e+09	INFO	controller-runtime.builder	Registering a validating webhook	{"GVK": "redhatcop.redhat.io/v1alpha1, Kind=PasswordPolicy", "path": "/validate-redhatcop-redhat-io-v1alpha1-passwordpolicy"}
1.6814820206825845e+09	INFO	controller-runtime.webhook	Registering webhook	{"path": "/validate-redhatcop-redhat-io-v1alpha1-passwordpolicy"}
1.6814820206827264e+09	INFO	controller-runtime.builder	Registering a mutating webhook	{"GVK": "redhatcop.redhat.io/v1alpha1, Kind=Policy", "path": "/mutate-redhatcop-redhat-io-v1alpha1-policy"}
1.6814820206828823e+09	INFO	controller-runtime.webhook	Registering webhook	{"path": "/mutate-redhatcop-redhat-io-v1alpha1-policy"}
1.681482020682981e+09	INFO	controller-runtime.builder	Registering a validating webhook	{"GVK": "redhatcop.redhat.io/v1alpha1, Kind=Policy", "path": "/validate-redhatcop-redhat-io-v1alpha1-policy"}
1.6814820206831713e+09	INFO	controller-runtime.webhook	Registering webhook	{"path": "/validate-redhatcop-redhat-io-v1alpha1-policy"}
1.68148202068334e+09	INFO	controller-runtime.builder	Registering a mutating webhook	{"GVK": "redhatcop.redhat.io/v1alpha1, Kind=GitHubSecretEngineConfig", "path": "/mutate-redhatcop-redhat-io-v1alpha1-githubsecretengineconfig"}
1.6814820206836467e+09	INFO	controller-runtime.webhook	Registering webhook	{"path": "/mutate-redhatcop-redhat-io-v1alpha1-githubsecretengineconfig"}
1.68148202068376e+09	INFO	controller-runtime.builder	Registering a validating webhook	{"GVK": "redhatcop.redhat.io/v1alpha1, Kind=GitHubSecretEngineConfig", "path": "/validate-redhatcop-redhat-io-v1alpha1-githubsecretengineconfig"}
1.6814820206838741e+09	INFO	controller-runtime.webhook	Registering webhook	{"path": "/validate-redhatcop-redhat-io-v1alpha1-githubsecretengineconfig"}
1.6814820206840017e+09	INFO	controller-runtime.builder	Registering a mutating webhook	{"GVK": "redhatcop.redhat.io/v1alpha1, Kind=GitHubSecretEngineRole", "path": "/mutate-redhatcop-redhat-io-v1alpha1-githubsecretenginerole"}
1.6814820206842358e+09	INFO	controller-runtime.webhook	Registering webhook	{"path": "/mutate-redhatcop-redhat-io-v1alpha1-githubsecretenginerole"}
1.681482020684393e+09	INFO	controller-runtime.builder	Registering a validating webhook	{"GVK": "redhatcop.redhat.io/v1alpha1, Kind=GitHubSecretEngineRole", "path": "/validate-redhatcop-redhat-io-v1alpha1-githubsecretenginerole"}
1.6814820206845188e+09	INFO	controller-runtime.webhook	Registering webhook	{"path": "/validate-redhatcop-redhat-io-v1alpha1-githubsecretenginerole"}
1.6814820206847422e+09	INFO	controller-runtime.builder	Registering a mutating webhook	{"GVK": "redhatcop.redhat.io/v1alpha1, Kind=PKISecretEngineConfig", "path": "/mutate-redhatcop-redhat-io-v1alpha1-pkisecretengineconfig"}
1.6814820206849303e+09	INFO	controller-runtime.webhook	Registering webhook	{"path": "/mutate-redhatcop-redhat-io-v1alpha1-pkisecretengineconfig"}
1.6814820206851346e+09	INFO	controller-runtime.builder	Registering a validating webhook	{"GVK": "redhatcop.redhat.io/v1alpha1, Kind=PKISecretEngineConfig", "path": "/validate-redhatcop-redhat-io-v1alpha1-pkisecretengineconfig"}
1.6814820206853611e+09	INFO	controller-runtime.webhook	Registering webhook	{"path": "/validate-redhatcop-redhat-io-v1alpha1-pkisecretengineconfig"}
1.6814820206856136e+09	INFO	controller-runtime.builder	Registering a mutating webhook	{"GVK": "redhatcop.redhat.io/v1alpha1, Kind=PKISecretEngineRole", "path": "/mutate-redhatcop-redhat-io-v1alpha1-pkisecretenginerole"}
1.681482020685826e+09	INFO	controller-runtime.webhook	Registering webhook	{"path": "/mutate-redhatcop-redhat-io-v1alpha1-pkisecretenginerole"}
1.681482020685962e+09	INFO	controller-runtime.builder	Registering a validating webhook	{"GVK": "redhatcop.redhat.io/v1alpha1, Kind=PKISecretEngineRole", "path": "/validate-redhatcop-redhat-io-v1alpha1-pkisecretenginerole"}
1.6814820206862595e+09	INFO	controller-runtime.webhook	Registering webhook	{"path": "/validate-redhatcop-redhat-io-v1alpha1-pkisecretenginerole"}
1.6814820206865795e+09	INFO	controller-runtime.builder	Registering a mutating webhook	{"GVK": "redhatcop.redhat.io/v1alpha1, Kind=RabbitMQSecretEngineRole", "path": "/mutate-redhatcop-redhat-io-v1alpha1-rabbitmqsecretenginerole"}
1.6814820206868033e+09	INFO	controller-runtime.webhook	Registering webhook	{"path": "/mutate-redhatcop-redhat-io-v1alpha1-rabbitmqsecretenginerole"}
1.6814820206868932e+09	INFO	controller-runtime.builder	Registering a validating webhook	{"GVK": "redhatcop.redhat.io/v1alpha1, Kind=RabbitMQSecretEngineRole", "path": "/validate-redhatcop-redhat-io-v1alpha1-rabbitmqsecretenginerole"}
1.6814820206870127e+09	INFO	controller-runtime.webhook	Registering webhook	{"path": "/validate-redhatcop-redhat-io-v1alpha1-rabbitmqsecretenginerole"}
1.6814820206872456e+09	INFO	controller-runtime.builder	Registering a mutating webhook	{"GVK": "redhatcop.redhat.io/v1alpha1, Kind=QuaySecretEngineConfig", "path": "/mutate-redhatcop-redhat-io-v1alpha1-quaysecretengineconfig"}
1.6814820206875107e+09	INFO	controller-runtime.webhook	Registering webhook	{"path": "/mutate-redhatcop-redhat-io-v1alpha1-quaysecretengineconfig"}
1.6814820206876585e+09	INFO	controller-runtime.builder	Registering a validating webhook	{"GVK": "redhatcop.redhat.io/v1alpha1, Kind=QuaySecretEngineConfig", "path": "/validate-redhatcop-redhat-io-v1alpha1-quaysecretengineconfig"}
1.6814820206877725e+09	INFO	controller-runtime.webhook	Registering webhook	{"path": "/validate-redhatcop-redhat-io-v1alpha1-quaysecretengineconfig"}
1.681482020687902e+09	INFO	controller-runtime.builder	Registering a mutating webhook	{"GVK": "redhatcop.redhat.io/v1alpha1, Kind=QuaySecretEngineRole", "path": "/mutate-redhatcop-redhat-io-v1alpha1-quaysecretenginerole"}
1.6814820206881304e+09	INFO	controller-runtime.webhook	Registering webhook	{"path": "/mutate-redhatcop-redhat-io-v1alpha1-quaysecretenginerole"}
1.6814820206894e+09	INFO	controller-runtime.builder	Registering a validating webhook	{"GVK": "redhatcop.redhat.io/v1alpha1, Kind=QuaySecretEngineRole", "path": "/validate-redhatcop-redhat-io-v1alpha1-quaysecretenginerole"}
1.6814820206896632e+09	INFO	controller-runtime.webhook	Registering webhook	{"path": "/validate-redhatcop-redhat-io-v1alpha1-quaysecretenginerole"}
1.68148202068989e+09	INFO	controller-runtime.builder	Registering a mutating webhook	{"GVK": "redhatcop.redhat.io/v1alpha1, Kind=QuaySecretEngineStaticRole", "path": "/mutate-redhatcop-redhat-io-v1alpha1-quaysecretenginestaticrole"}
1.6814820207763064e+09	INFO	controller-runtime.webhook	Registering webhook	{"path": "/mutate-redhatcop-redhat-io-v1alpha1-quaysecretenginestaticrole"}
1.6814820207766252e+09	INFO	controller-runtime.builder	Registering a validating webhook	{"GVK": "redhatcop.redhat.io/v1alpha1, Kind=QuaySecretEngineStaticRole", "path": "/validate-redhatcop-redhat-io-v1alpha1-quaysecretenginestaticrole"}
1.6814820207768645e+09	INFO	controller-runtime.webhook	Registering webhook	{"path": "/validate-redhatcop-redhat-io-v1alpha1-quaysecretenginestaticrole"}
1.6814820207770476e+09	INFO	controller-runtime.builder	Registering a mutating webhook	{"GVK": "redhatcop.redhat.io/v1alpha1, Kind=KubernetesSecretEngineConfig", "path": "/mutate-redhatcop-redhat-io-v1alpha1-kubernetessecretengineconfig"}
1.6814820207772024e+09	INFO	controller-runtime.webhook	Registering webhook	{"path": "/mutate-redhatcop-redhat-io-v1alpha1-kubernetessecretengineconfig"}
1.6814820207773259e+09	INFO	controller-runtime.builder	Registering a validating webhook	{"GVK": "redhatcop.redhat.io/v1alpha1, Kind=KubernetesSecretEngineConfig", "path": "/validate-redhatcop-redhat-io-v1alpha1-kubernetessecretengineconfig"}
1.6814820207774615e+09	INFO	controller-runtime.webhook	Registering webhook	{"path": "/validate-redhatcop-redhat-io-v1alpha1-kubernetessecretengineconfig"}
1.681482020777627e+09	INFO	controller-runtime.builder	Registering a mutating webhook	{"GVK": "redhatcop.redhat.io/v1alpha1, Kind=KubernetesSecretEngineRole", "path": "/mutate-redhatcop-redhat-io-v1alpha1-kubernetessecretenginerole"}
1.6814820207777436e+09	INFO	controller-runtime.webhook	Registering webhook	{"path": "/mutate-redhatcop-redhat-io-v1alpha1-kubernetessecretenginerole"}
1.6814820207778337e+09	INFO	controller-runtime.builder	Registering a validating webhook	{"GVK": "redhatcop.redhat.io/v1alpha1, Kind=KubernetesSecretEngineRole", "path": "/validate-redhatcop-redhat-io-v1alpha1-kubernetessecretenginerole"}
1.6814820207779486e+09	INFO	controller-runtime.webhook	Registering webhook	{"path": "/validate-redhatcop-redhat-io-v1alpha1-kubernetessecretenginerole"}
1.6814820207781858e+09	INFO	controller-runtime.webhook	Registering webhook	{"path": "/validate-redhatcop-redhat-io-v1alpha1-rabbitmqsecretengineconfig"}
1.6814820207784894e+09	INFO	controller-runtime.builder	Registering a mutating webhook	{"GVK": "redhatcop.redhat.io/v1alpha1, Kind=DatabaseSecretEngineStaticRole", "path": "/mutate-redhatcop-redhat-io-v1alpha1-databasesecretenginestaticrole"}
1.6814820207786608e+09	INFO	controller-runtime.webhook	Registering webhook	{"path": "/mutate-redhatcop-redhat-io-v1alpha1-databasesecretenginestaticrole"}
1.6814820207787552e+09	INFO	controller-runtime.builder	Registering a validating webhook	{"GVK": "redhatcop.redhat.io/v1alpha1, Kind=DatabaseSecretEngineStaticRole", "path": "/validate-redhatcop-redhat-io-v1alpha1-databasesecretenginestaticrole"}
1.6814820207788699e+09	INFO	controller-runtime.webhook	Registering webhook	{"path": "/validate-redhatcop-redhat-io-v1alpha1-databasesecretenginestaticrole"}
1.681482020779011e+09	INFO	setup	starting manager
1.6814820207866454e+09	INFO	Starting server	{"path": "/metrics", "kind": "metrics", "addr": "127.0.0.1:8080"}
1.6814820207865026e+09	INFO	controller-runtime.webhook.webhooks	Starting webhook server
1.681482020786922e+09	INFO	Starting server	{"kind": "health probe", "addr": "[::]:8081"}
I0414 14:20:20.787304       1 leaderelection.go:248] attempting to acquire leader lease stakater-vault-config-operator/3d7d3a62.redhat.io...
1.6814820207878451e+09	INFO	controller-runtime.certwatcher	Updated current TLS certificate
1.6814820207881727e+09	INFO	controller-runtime.webhook	Serving webhook server	{"host": "", "port": 9443}
1.6814820207884912e+09	INFO	controller-runtime.certwatcher	Starting certificate watcher
I0414 14:20:39.114214       1 leaderelection.go:258] successfully acquired lease stakater-vault-config-operator/3d7d3a62.redhat.io
1.681482039114293e+09	DEBUG	events	vault-config-operator-controller-manager-6f95f574f7-gl2sd_bde70790-1c54-443d-8d27-e61a33557704 became leader	{"type": "Normal", "object": {"kind":"Lease","namespace":"stakater-vault-config-operator","name":"3d7d3a62.redhat.io","uid":"af3624ea-e6f4-4112-b2e3-432511063a44","apiVersion":"coordination.k8s.io/v1","resourceVersion":"15132591"}, "reason": "LeaderElection"}
1.6814820391717215e+09	INFO	Starting EventSource	{"controller": "databasesecretengineconfig", "controllerGroup": "redhatcop.redhat.io", "controllerKind": "DatabaseSecretEngineConfig", "source": "kind source: *v1alpha1.DatabaseSecretEngineConfig"}
1.681482039171887e+09	INFO	Starting EventSource	{"controller": "ldapauthenginegroup", "controllerGroup": "redhatcop.redhat.io", "controllerKind": "LDAPAuthEngineGroup", "source": "kind source: *v1alpha1.LDAPAuthEngineGroup"}
1.681482039172294e+09	INFO	Starting EventSource	{"controller": "jwtoidcauthengineconfig", "controllerGroup": "redhatcop.redhat.io", "controllerKind": "JWTOIDCAuthEngineConfig", "source": "kind source: *v1alpha1.JWTOIDCAuthEngineConfig"}
1.6814820391723714e+09	INFO	Starting EventSource	{"controller": "jwtoidcauthengineconfig", "controllerGroup": "redhatcop.redhat.io", "controllerKind": "JWTOIDCAuthEngineConfig", "source": "kind source: *v1.Secret"}
1.6814820391724126e+09	INFO	Starting EventSource	{"controller": "jwtoidcauthengineconfig", "controllerGroup": "redhatcop.redhat.io", "controllerKind": "JWTOIDCAuthEngineConfig", "source": "kind source: *v1alpha1.RandomSecret"}
1.681482039172433e+09	INFO	Starting Controller	{"controller": "jwtoidcauthengineconfig", "controllerGroup": "redhatcop.redhat.io", "controllerKind": "JWTOIDCAuthEngineConfig"}
1.681482039172424e+09	INFO	Starting EventSource	{"controller": "policy", "controllerGroup": "redhatcop.redhat.io", "controllerKind": "Policy", "source": "kind source: *v1alpha1.Policy"}
1.681482039172538e+09	INFO	Starting Controller	{"controller": "policy", "controllerGroup": "redhatcop.redhat.io", "controllerKind": "Policy"}
1.681482039172653e+09	INFO	Starting Controller	{"controller": "ldapauthenginegroup", "controllerGroup": "redhatcop.redhat.io", "controllerKind": "LDAPAuthEngineGroup"}
1.6814820391726484e+09	INFO	Starting EventSource	{"controller": "authenginemount", "controllerGroup": "redhatcop.redhat.io", "controllerKind": "AuthEngineMount", "source": "kind source: *v1alpha1.AuthEngineMount"}
1.6814820391728363e+09	INFO	Starting Controller	{"controller": "authenginemount", "controllerGroup": "redhatcop.redhat.io", "controllerKind": "AuthEngineMount"}
1.6814820391729162e+09	INFO	Starting EventSource	{"controller": "secretenginemount", "controllerGroup": "redhatcop.redhat.io", "controllerKind": "SecretEngineMount", "source": "kind source: *v1alpha1.SecretEngineMount"}
1.6814820391730442e+09	INFO	Starting Controller	{"controller": "secretenginemount", "controllerGroup": "redhatcop.redhat.io", "controllerKind": "SecretEngineMount"}
1.681482039173043e+09	INFO	Starting EventSource	{"controller": "databasesecretenginerole", "controllerGroup": "redhatcop.redhat.io", "controllerKind": "DatabaseSecretEngineRole", "source": "kind source: *v1alpha1.DatabaseSecretEngineRole"}
1.6814820391732204e+09	INFO	Starting Controller	{"controller": "databasesecretenginerole", "controllerGroup": "redhatcop.redhat.io", "controllerKind": "DatabaseSecretEngineRole"}
1.6814820391733956e+09	INFO	Starting EventSource	{"controller": "randomsecret", "controllerGroup": "redhatcop.redhat.io", "controllerKind": "RandomSecret", "source": "kind source: *v1alpha1.RandomSecret"}
1.681482039173467e+09	INFO	Starting Controller	{"controller": "randomsecret", "controllerGroup": "redhatcop.redhat.io", "controllerKind": "RandomSecret"}
1.6814820391735485e+09	INFO	Starting EventSource	{"controller": "vaultsecret", "controllerGroup": "redhatcop.redhat.io", "controllerKind": "VaultSecret", "source": "kind source: *v1alpha1.VaultSecret"}
1.681482039173628e+09	INFO	Starting EventSource	{"controller": "vaultsecret", "controllerGroup": "redhatcop.redhat.io", "controllerKind": "VaultSecret", "source": "kind source: *v1.Secret"}
1.6814820391736686e+09	INFO	Starting Controller	{"controller": "vaultsecret", "controllerGroup": "redhatcop.redhat.io", "controllerKind": "VaultSecret"}
1.6814820391740124e+09	INFO	Starting EventSource	{"controller": "kubernetesauthenginerole", "controllerGroup": "redhatcop.redhat.io", "controllerKind": "KubernetesAuthEngineRole", "source": "kind source: *v1alpha1.KubernetesAuthEngineRole"}
1.6814820391743088e+09	INFO	Starting EventSource	{"controller": "kubernetesauthenginerole", "controllerGroup": "redhatcop.redhat.io", "controllerKind": "KubernetesAuthEngineRole", "source": "kind source: *v1.Namespace"}
1.6814820391744523e+09	INFO	Starting Controller	{"controller": "kubernetesauthenginerole", "controllerGroup": "redhatcop.redhat.io", "controllerKind": "KubernetesAuthEngineRole"}
1.6814820392897594e+09	INFO	Starting EventSource	{"controller": "kubernetesauthengineconfig", "controllerGroup": "redhatcop.redhat.io", "controllerKind": "KubernetesAuthEngineConfig", "source": "kind source: *v1alpha1.KubernetesAuthEngineConfig"}
1.681482039290023e+09	INFO	Starting Controller	{"controller": "kubernetesauthengineconfig", "controllerGroup": "redhatcop.redhat.io", "controllerKind": "KubernetesAuthEngineConfig"}
1.681482039290356e+09	INFO	Starting EventSource	{"controller": "passwordpolicy", "controllerGroup": "redhatcop.redhat.io", "controllerKind": "PasswordPolicy", "source": "kind source: *v1alpha1.PasswordPolicy"}
1.6814820392904882e+09	INFO	Starting Controller	{"controller": "passwordpolicy", "controllerGroup": "redhatcop.redhat.io", "controllerKind": "PasswordPolicy"}
1.6814820392906544e+09	INFO	Starting EventSource	{"controller": "quaysecretenginerole", "controllerGroup": "redhatcop.redhat.io", "controllerKind": "QuaySecretEngineRole", "source": "kind source: *v1alpha1.QuaySecretEngineRole"}
1.6814820392907715e+09	INFO	Starting EventSource	{"controller": "jwtoidcauthenginerole", "controllerGroup": "redhatcop.redhat.io", "controllerKind": "JWTOIDCAuthEngineRole", "source": "kind source: *v1alpha1.JWTOIDCAuthEngineRole"}
1.681482039290885e+09	INFO	Starting Controller	{"controller": "jwtoidcauthenginerole", "controllerGroup": "redhatcop.redhat.io", "controllerKind": "JWTOIDCAuthEngineRole"}
1.6814820392705793e+09	INFO	Starting EventSource	{"controller": "databasesecretengineconfig", "controllerGroup": "redhatcop.redhat.io", "controllerKind": "DatabaseSecretEngineConfig", "source": "kind source: *v1.Secret"}
1.6814820392910302e+09	INFO	Starting EventSource	{"controller": "databasesecretengineconfig", "controllerGroup": "redhatcop.redhat.io", "controllerKind": "DatabaseSecretEngineConfig", "source": "kind source: *v1alpha1.RandomSecret"}
1.6814820392911444e+09	INFO	Starting EventSource	{"controller": "quaysecretenginestaticrole", "controllerGroup": "redhatcop.redhat.io", "controllerKind": "QuaySecretEngineStaticRole", "source": "kind source: *v1alpha1.QuaySecretEngineStaticRole"}
1.6814820392912734e+09	INFO	Starting Controller	{"controller": "quaysecretenginestaticrole", "controllerGroup": "redhatcop.redhat.io", "controllerKind": "QuaySecretEngineStaticRole"}
1.6814820392917259e+09	INFO	Starting EventSource	{"controller": "databasesecretenginestaticrole", "controllerGroup": "redhatcop.redhat.io", "controllerKind": "DatabaseSecretEngineStaticRole", "source": "kind source: *v1alpha1.DatabaseSecretEngineStaticRole"}
1.6814820392918944e+09	INFO	Starting Controller	{"controller": "databasesecretenginestaticrole", "controllerGroup": "redhatcop.redhat.io", "controllerKind": "DatabaseSecretEngineStaticRole"}
1.6814820393006692e+09	INFO	Starting EventSource	{"controller": "githubsecretenginerole", "controllerGroup": "redhatcop.redhat.io", "controllerKind": "GitHubSecretEngineRole", "source": "kind source: *v1alpha1.GitHubSecretEngineRole"}
1.6814820393008075e+09	INFO	Starting Controller	{"controller": "githubsecretenginerole", "controllerGroup": "redhatcop.redhat.io", "controllerKind": "GitHubSecretEngineRole"}
1.6814820393009608e+09	INFO	Starting EventSource	{"controller": "ldapauthengineconfig", "controllerGroup": "redhatcop.redhat.io", "controllerKind": "LDAPAuthEngineConfig", "source": "kind source: *v1alpha1.LDAPAuthEngineConfig"}
1.6814820393010268e+09	INFO	Starting EventSource	{"controller": "ldapauthengineconfig", "controllerGroup": "redhatcop.redhat.io", "controllerKind": "LDAPAuthEngineConfig", "source": "kind source: *v1.Secret"}
1.6814820393010497e+09	INFO	Starting EventSource	{"controller": "ldapauthengineconfig", "controllerGroup": "redhatcop.redhat.io", "controllerKind": "LDAPAuthEngineConfig", "source": "kind source: *v1alpha1.RandomSecret"}
1.6814820393011737e+09	INFO	Starting Controller	{"controller": "ldapauthengineconfig", "controllerGroup": "redhatcop.redhat.io", "controllerKind": "LDAPAuthEngineConfig"}
1.6814820392910874e+09	INFO	Starting Controller	{"controller": "databasesecretengineconfig", "controllerGroup": "redhatcop.redhat.io", "controllerKind": "DatabaseSecretEngineConfig"}
1.6814820392908437e+09	INFO	Starting Controller	{"controller": "quaysecretenginerole", "controllerGroup": "redhatcop.redhat.io", "controllerKind": "QuaySecretEngineRole"}
1.6814820393706622e+09	INFO	Starting EventSource	{"controller": "pkisecretenginerole", "controllerGroup": "redhatcop.redhat.io", "controllerKind": "PKISecretEngineRole", "source": "kind source: *v1alpha1.PKISecretEngineRole"}
1.6814820393708408e+09	INFO	Starting Controller	{"controller": "pkisecretenginerole", "controllerGroup": "redhatcop.redhat.io", "controllerKind": "PKISecretEngineRole"}
1.6814820393714025e+09	INFO	Starting EventSource	{"controller": "quaysecretengineconfig", "controllerGroup": "redhatcop.redhat.io", "controllerKind": "QuaySecretEngineConfig", "source": "kind source: *v1alpha1.QuaySecretEngineConfig"}
1.6814820393715067e+09	INFO	Starting EventSource	{"controller": "rabbitmqsecretengineconfig", "controllerGroup": "redhatcop.redhat.io", "controllerKind": "RabbitMQSecretEngineConfig", "source": "kind source: *v1alpha1.RabbitMQSecretEngineConfig"}
1.68148203937159e+09	INFO	Starting Controller	{"controller": "rabbitmqsecretengineconfig", "controllerGroup": "redhatcop.redhat.io", "controllerKind": "RabbitMQSecretEngineConfig"}
1.681482039371586e+09	INFO	Starting EventSource	{"controller": "quaysecretengineconfig", "controllerGroup": "redhatcop.redhat.io", "controllerKind": "QuaySecretEngineConfig", "source": "kind source: *v1.Secret"}
1.6814820393716824e+09	INFO	Starting EventSource	{"controller": "quaysecretengineconfig", "controllerGroup": "redhatcop.redhat.io", "controllerKind": "QuaySecretEngineConfig", "source": "kind source: *v1alpha1.RandomSecret"}
1.681482039371735e+09	INFO	Starting Controller	{"controller": "quaysecretengineconfig", "controllerGroup": "redhatcop.redhat.io", "controllerKind": "QuaySecretEngineConfig"}
1.6814820393717666e+09	INFO	Starting EventSource	{"controller": "kubernetessecretenginerole", "controllerGroup": "redhatcop.redhat.io", "controllerKind": "KubernetesSecretEngineRole", "source": "kind source: *v1alpha1.KubernetesSecretEngineRole"}
1.6814820393718467e+09	INFO	Starting Controller	{"controller": "kubernetessecretenginerole", "controllerGroup": "redhatcop.redhat.io", "controllerKind": "KubernetesSecretEngineRole"}
1.6814820393721561e+09	INFO	Starting EventSource	{"controller": "githubsecretengineconfig", "controllerGroup": "redhatcop.redhat.io", "controllerKind": "GitHubSecretEngineConfig", "source": "kind source: *v1alpha1.GitHubSecretEngineConfig"}
1.681482039372348e+09	INFO	Starting EventSource	{"controller": "githubsecretengineconfig", "controllerGroup": "redhatcop.redhat.io", "controllerKind": "GitHubSecretEngineConfig", "source": "kind source: *v1.Secret"}
1.6814820393723307e+09	INFO	Starting EventSource	{"controller": "rabbitmqsecretenginerole", "controllerGroup": "redhatcop.redhat.io", "controllerKind": "RabbitMQSecretEngineRole", "source": "kind source: *v1alpha1.RabbitMQSecretEngineRole"}
1.681482039372504e+09	INFO	Starting Controller	{"controller": "rabbitmqsecretenginerole", "controllerGroup": "redhatcop.redhat.io", "controllerKind": "RabbitMQSecretEngineRole"}
1.6814820393724096e+09	INFO	Starting Controller	{"controller": "githubsecretengineconfig", "controllerGroup": "redhatcop.redhat.io", "controllerKind": "GitHubSecretEngineConfig"}
1.681482039372785e+09	INFO	Starting EventSource	{"controller": "pkisecretengineconfig", "controllerGroup": "redhatcop.redhat.io", "controllerKind": "PKISecretEngineConfig", "source": "kind source: *v1alpha1.PKISecretEngineConfig"}
1.6814820393728895e+09	INFO	Starting Controller	{"controller": "pkisecretengineconfig", "controllerGroup": "redhatcop.redhat.io", "controllerKind": "PKISecretEngineConfig"}
1.6814820393720772e+09	INFO	Starting EventSource	{"controller": "kubernetessecretengineconfig", "controllerGroup": "redhatcop.redhat.io", "controllerKind": "KubernetesSecretEngineConfig", "source": "kind source: *v1alpha1.KubernetesSecretEngineConfig"}
1.6814820394713557e+09	INFO	Starting EventSource	{"controller": "kubernetessecretengineconfig", "controllerGroup": "redhatcop.redhat.io", "controllerKind": "KubernetesSecretEngineConfig", "source": "kind source: *v1.Secret"}
1.6814820394713883e+09	INFO	Starting Controller	{"controller": "kubernetessecretengineconfig", "controllerGroup": "redhatcop.redhat.io", "controllerKind": "KubernetesSecretEngineConfig"}
1.6814820399716291e+09	INFO	Starting workers	{"controller": "passwordpolicy", "controllerGroup": "redhatcop.redhat.io", "controllerKind": "PasswordPolicy", "worker count": 1}
1.6814820448890772e+09	INFO	Starting workers	{"controller": "quaysecretenginestaticrole", "controllerGroup": "redhatcop.redhat.io", "controllerKind": "QuaySecretEngineStaticRole", "worker count": 1}
1.681482044889228e+09	INFO	Starting workers	{"controller": "kubernetessecretengineconfig", "controllerGroup": "redhatcop.redhat.io", "controllerKind": "KubernetesSecretEngineConfig", "worker count": 1}
1.6814820448892791e+09	INFO	Starting workers	{"controller": "kubernetesauthengineconfig", "controllerGroup": "redhatcop.redhat.io", "controllerKind": "KubernetesAuthEngineConfig", "worker count": 1}
1.6814820448893287e+09	INFO	Starting workers	{"controller": "secretenginemount", "controllerGroup": "redhatcop.redhat.io", "controllerKind": "SecretEngineMount", "worker count": 1}
1.6814820448893733e+09	INFO	Starting workers	{"controller": "databasesecretenginerole", "controllerGroup": "redhatcop.redhat.io", "controllerKind": "DatabaseSecretEngineRole", "worker count": 1}
1.6814820449726896e+09	INFO	Starting workers	{"controller": "pkisecretenginerole", "controllerGroup": "redhatcop.redhat.io", "controllerKind": "PKISecretEngineRole", "worker count": 1}
1.6814820449727879e+09	INFO	Starting workers	{"controller": "jwtoidcauthenginerole", "controllerGroup": "redhatcop.redhat.io", "controllerKind": "JWTOIDCAuthEngineRole", "worker count": 1}
1.6814820449728358e+09	INFO	Starting workers	{"controller": "rabbitmqsecretenginerole", "controllerGroup": "redhatcop.redhat.io", "controllerKind": "RabbitMQSecretEngineRole", "worker count": 1}
1.681482044972826e+09	INFO	Starting workers	{"controller": "ldapauthenginegroup", "controllerGroup": "redhatcop.redhat.io", "controllerKind": "LDAPAuthEngineGroup", "worker count": 1}
1.6814820449729471e+09	INFO	Starting workers	{"controller": "randomsecret", "controllerGroup": "redhatcop.redhat.io", "controllerKind": "RandomSecret", "worker count": 1}
1.6814820449727228e+09	INFO	Starting workers	{"controller": "pkisecretengineconfig", "controllerGroup": "redhatcop.redhat.io", "controllerKind": "PKISecretEngineConfig", "worker count": 1}
1.6814820449735286e+09	INFO	Starting workers	{"controller": "githubsecretenginerole", "controllerGroup": "redhatcop.redhat.io", "controllerKind": "GitHubSecretEngineRole", "worker count": 1}
1.6814820449735632e+09	INFO	Starting workers	{"controller": "quaysecretenginerole", "controllerGroup": "redhatcop.redhat.io", "controllerKind": "QuaySecretEngineRole", "worker count": 1}
1.68148204497361e+09	INFO	Starting workers	{"controller": "ldapauthengineconfig", "controllerGroup": "redhatcop.redhat.io", "controllerKind": "LDAPAuthEngineConfig", "worker count": 1}
1.6814820450703638e+09	INFO	Starting workers	{"controller": "jwtoidcauthengineconfig", "controllerGroup": "redhatcop.redhat.io", "controllerKind": "JWTOIDCAuthEngineConfig", "worker count": 1}
1.6814820450705345e+09	INFO	Starting workers	{"controller": "kubernetessecretenginerole", "controllerGroup": "redhatcop.redhat.io", "controllerKind": "KubernetesSecretEngineRole", "worker count": 1}
1.6814820450706003e+09	INFO	Starting workers	{"controller": "vaultsecret", "controllerGroup": "redhatcop.redhat.io", "controllerKind": "VaultSecret", "worker count": 1}
1.6814820450716345e+09	INFO	Starting workers	{"controller": "quaysecretengineconfig", "controllerGroup": "redhatcop.redhat.io", "controllerKind": "QuaySecretEngineConfig", "worker count": 1}
1.6814820450716815e+09	INFO	Starting workers	{"controller": "rabbitmqsecretengineconfig", "controllerGroup": "redhatcop.redhat.io", "controllerKind": "RabbitMQSecretEngineConfig", "worker count": 1}
1.681482045072309e+09	INFO	Starting workers	{"controller": "githubsecretengineconfig", "controllerGroup": "redhatcop.redhat.io", "controllerKind": "GitHubSecretEngineConfig", "worker count": 1}
1.6814820450744646e+09	INFO	Starting workers	{"controller": "databasesecretenginestaticrole", "controllerGroup": "redhatcop.redhat.io", "controllerKind": "DatabaseSecretEngineStaticRole", "worker count": 1}
1.6814820450745542e+09	INFO	Starting workers	{"controller": "policy", "controllerGroup": "redhatcop.redhat.io", "controllerKind": "Policy", "worker count": 1}
1.6814820450745199e+09	INFO	Starting workers	{"controller": "authenginemount", "controllerGroup": "redhatcop.redhat.io", "controllerKind": "AuthEngineMount", "worker count": 1}
1.6814820450752475e+09	INFO	Starting workers	{"controller": "databasesecretengineconfig", "controllerGroup": "redhatcop.redhat.io", "controllerKind": "DatabaseSecretEngineConfig", "worker count": 1}
1.6814820450752754e+09	INFO	Starting workers	{"controller": "kubernetesauthenginerole", "controllerGroup": "redhatcop.redhat.io", "controllerKind": "KubernetesAuthEngineRole", "worker count": 1}
1.6814821433220546e+09	DEBUG	controller-runtime.webhook.webhooks	received request	{"webhook": "/mutate-redhatcop-redhat-io-v1alpha1-policy", "UID": "5c565c4c-b6ea-4800-a927-073cd1c99bbb", "kind": "redhatcop.redhat.io/v1alpha1, Kind=Policy", "resource": {"group":"redhatcop.redhat.io","version":"v1alpha1","resource":"policies"}}
1.681482143322702e+09	INFO	policy-resource	default	{"name": "secret-reader"}
1.6814821433240812e+09	DEBUG	controller-runtime.webhook.webhooks	wrote response	{"webhook": "/mutate-redhatcop-redhat-io-v1alpha1-policy", "code": 200, "reason": "", "UID": "5c565c4c-b6ea-4800-a927-073cd1c99bbb", "allowed": true}
1.6814821769869404e+09	ERROR	unable to update status	{"controller": "policy", "controllerGroup": "redhatcop.redhat.io", "controllerKind": "Policy", "Policy": {"name":"secret-reader","namespace":"stakater-vault-config-operator"}, "namespace": "stakater-vault-config-operator", "name": "secret-reader", "reconcileID": "1139b3df-6344-4739-81ea-59523bded564", "error": "Operation cannot be fulfilled on policies.redhatcop.redhat.io \"secret-reader\": the object has been modified; please apply your changes to the latest version and try again"}
github.com/redhat-cop/vault-config-operator/controllers/vaultresourcecontroller.ManageOutcomeWithRequeue
	/home/runner/work/vault-config-operator/vault-config-operator/controllers/vaultresourcecontroller/utils.go:69
github.com/redhat-cop/vault-config-operator/controllers/vaultresourcecontroller.ManageOutcome
	/home/runner/work/vault-config-operator/vault-config-operator/controllers/vaultresourcecontroller/utils.go:76
github.com/redhat-cop/vault-config-operator/controllers/vaultresourcecontroller.(*VaultResource).Reconcile
	/home/runner/work/vault-config-operator/vault-config-operator/controllers/vaultresourcecontroller/vaultresourcereconciler.go:71
github.com/redhat-cop/vault-config-operator/controllers.(*PolicyReconciler).Reconcile
	/home/runner/work/vault-config-operator/vault-config-operator/controllers/policy_controller.go:77
sigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller).Reconcile
	/home/runner/go/pkg/mod/sigs.k8s.io/controller-runtime@v0.13.0/pkg/internal/controller/controller.go:121
sigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller).reconcileHandler
	/home/runner/go/pkg/mod/sigs.k8s.io/controller-runtime@v0.13.0/pkg/internal/controller/controller.go:320
sigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller).processNextWorkItem
	/home/runner/go/pkg/mod/sigs.k8s.io/controller-runtime@v0.13.0/pkg/internal/controller/controller.go:273
sigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller).Start.func2.2
	/home/runner/go/pkg/mod/sigs.k8s.io/controller-runtime@v0.13.0/pkg/internal/controller/controller.go:234
1.6814821769874692e+09	ERROR	Reconciler error	{"controller": "policy", "controllerGroup": "redhatcop.redhat.io", "controllerKind": "Policy", "Policy": {"name":"secret-reader","namespace":"stakater-vault-config-operator"}, "namespace": "stakater-vault-config-operator", "name": "secret-reader", "reconcileID": "1139b3df-6344-4739-81ea-59523bded564", "error": "Operation cannot be fulfilled on policies.redhatcop.redhat.io \"secret-reader\": the object has been modified; please apply your changes to the latest version and try again"}
sigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller).reconcileHandler
	/home/runner/go/pkg/mod/sigs.k8s.io/controller-runtime@v0.13.0/pkg/internal/controller/controller.go:326
sigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller).processNextWorkItem
	/home/runner/go/pkg/mod/sigs.k8s.io/controller-runtime@v0.13.0/pkg/internal/controller/controller.go:273
sigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller).Start.func2.2
	/home/runner/go/pkg/mod/sigs.k8s.io/controller-runtime@v0.13.0/pkg/internal/controller/controller.go:234
1.6814821803913703e+09	ERROR	unable to update instance	{"controller": "policy", "controllerGroup": "redhatcop.redhat.io", "controllerKind": "Policy", "Policy": {"name":"secret-reader","namespace":"stakater-vault-config-operator"}, "namespace": "stakater-vault-config-operator", "name": "secret-reader", "reconcileID": "f5dac356-3763-4b26-b73b-0c42a07082a4", "instance": {"apiVersion": "redhatcop.redhat.io/v1alpha1", "kind": "Policy", "namespace": "stakater-vault-config-operator", "name": "secret-reader"}, "error": "Operation cannot be fulfilled on policies.redhatcop.redhat.io \"secret-reader\": StorageError: invalid object, Code: 4, Key: /kubernetes.io/redhatcop.redhat.io/policies/stakater-vault-config-operator/secret-reader, ResourceVersion: 0, AdditionalErrorMsg: Precondition failed: UID in precondition: ea904dbf-0c00-44f1-a549-b37fb970d4ff, UID in object meta: "}
github.com/redhat-cop/vault-config-operator/controllers/vaultresourcecontroller.(*VaultResource).Reconcile
	/home/runner/work/vault-config-operator/vault-config-operator/controllers/vaultresourcecontroller/vaultresourcereconciler.go:59
github.com/redhat-cop/vault-config-operator/controllers.(*PolicyReconciler).Reconcile
	/home/runner/work/vault-config-operator/vault-config-operator/controllers/policy_controller.go:77
sigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller).Reconcile
	/home/runner/go/pkg/mod/sigs.k8s.io/controller-runtime@v0.13.0/pkg/internal/controller/controller.go:121
sigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller).reconcileHandler
	/home/runner/go/pkg/mod/sigs.k8s.io/controller-runtime@v0.13.0/pkg/internal/controller/controller.go:320
sigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller).processNextWorkItem
	/home/runner/go/pkg/mod/sigs.k8s.io/controller-runtime@v0.13.0/pkg/internal/controller/controller.go:273
sigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller).Start.func2.2
	/home/runner/go/pkg/mod/sigs.k8s.io/controller-runtime@v0.13.0/pkg/internal/controller/controller.go:234
1.6814821803924325e+09	DEBUG	events	Operation cannot be fulfilled on policies.redhatcop.redhat.io "secret-reader": StorageError: invalid object, Code: 4, Key: /kubernetes.io/redhatcop.redhat.io/policies/stakater-vault-config-operator/secret-reader, ResourceVersion: 0, AdditionalErrorMsg: Precondition failed: UID in precondition: ea904dbf-0c00-44f1-a549-b37fb970d4ff, UID in object meta: 	{"type": "Warning", "object": {"kind":"Policy","namespace":"stakater-vault-config-operator","name":"secret-reader","uid":"ea904dbf-0c00-44f1-a549-b37fb970d4ff","apiVersion":"redhatcop.redhat.io/v1alpha1","resourceVersion":"15133387"}, "reason": "ProcessingError"}
1.6814821803999143e+09	ERROR	unable to update status	{"controller": "policy", "controllerGroup": "redhatcop.redhat.io", "controllerKind": "Policy", "Policy": {"name":"secret-reader","namespace":"stakater-vault-config-operator"}, "namespace": "stakater-vault-config-operator", "name": "secret-reader", "reconcileID": "f5dac356-3763-4b26-b73b-0c42a07082a4", "error": "Operation cannot be fulfilled on policies.redhatcop.redhat.io \"secret-reader\": StorageError: invalid object, Code: 4, Key: /kubernetes.io/redhatcop.redhat.io/policies/stakater-vault-config-operator/secret-reader, ResourceVersion: 0, AdditionalErrorMsg: Precondition failed: UID in precondition: ea904dbf-0c00-44f1-a549-b37fb970d4ff, UID in object meta: "}
github.com/redhat-cop/vault-config-operator/controllers/vaultresourcecontroller.ManageOutcomeWithRequeue
	/home/runner/work/vault-config-operator/vault-config-operator/controllers/vaultresourcecontroller/utils.go:69
github.com/redhat-cop/vault-config-operator/controllers/vaultresourcecontroller.ManageOutcome
	/home/runner/work/vault-config-operator/vault-config-operator/controllers/vaultresourcecontroller/utils.go:76
github.com/redhat-cop/vault-config-operator/controllers/vaultresourcecontroller.(*VaultResource).Reconcile
	/home/runner/work/vault-config-operator/vault-config-operator/controllers/vaultresourcecontroller/vaultresourcereconciler.go:60
github.com/redhat-cop/vault-config-operator/controllers.(*PolicyReconciler).Reconcile
	/home/runner/work/vault-config-operator/vault-config-operator/controllers/policy_controller.go:77
sigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller).Reconcile
	/home/runner/go/pkg/mod/sigs.k8s.io/controller-runtime@v0.13.0/pkg/internal/controller/controller.go:121
sigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller).reconcileHandler
	/home/runner/go/pkg/mod/sigs.k8s.io/controller-runtime@v0.13.0/pkg/internal/controller/controller.go:320
sigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller).processNextWorkItem
	/home/runner/go/pkg/mod/sigs.k8s.io/controller-runtime@v0.13.0/pkg/internal/controller/controller.go:273
sigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller).Start.func2.2
	/home/runner/go/pkg/mod/sigs.k8s.io/controller-runtime@v0.13.0/pkg/internal/controller/controller.go:234
1.6814821804002974e+09	ERROR	Reconciler error	{"controller": "policy", "controllerGroup": "redhatcop.redhat.io", "controllerKind": "Policy", "Policy": {"name":"secret-reader","namespace":"stakater-vault-config-operator"}, "namespace": "stakater-vault-config-operator", "name": "secret-reader", "reconcileID": "f5dac356-3763-4b26-b73b-0c42a07082a4", "error": "Operation cannot be fulfilled on policies.redhatcop.redhat.io \"secret-reader\": StorageError: invalid object, Code: 4, Key: /kubernetes.io/redhatcop.redhat.io/policies/stakater-vault-config-operator/secret-reader, ResourceVersion: 0, AdditionalErrorMsg: Precondition failed: UID in precondition: ea904dbf-0c00-44f1-a549-b37fb970d4ff, UID in object meta: "}
sigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller).reconcileHandler
	/home/runner/go/pkg/mod/sigs.k8s.io/controller-runtime@v0.13.0/pkg/internal/controller/controller.go:326
sigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller).processNextWorkItem
	/home/runner/go/pkg/mod/sigs.k8s.io/controller-runtime@v0.13.0/pkg/internal/controller/controller.go:273
sigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller).Start.func2.2
	/home/runner/go/pkg/mod/sigs.k8s.io/controller-runtime@v0.13.0/pkg/internal/controller/controller.go:234

#120 should have fixed this issue. do you see it with Policies or will all/any resources?

I did test with more than just policy (auth provider) and was same result, i can set up again and get more examples if it helps?

We've been seeing this too. Looks like it might have been some regression when a status type was changed. I have raised a PR with the fix we've applied:
https://github.com/redhat-cop/vault-config-operator/pull/147

repo: redhat-cop/vault-config-operator


text:
http: TLS handshake error from 10.42.0.0:45928: remote error: tls: bad certificate

I've deployed the operator to bare metal kubernetes (k3s version 1.24.8) using the helm chart, with enableCertManager set to false (as default). I've generated my own certs using a self-signed ClusterIssuer, and named the corresponding secrets webhook-server-cert and vault-config-operator-certs.
The pod spins up correctly, but when I create a custom resource (say, Policy), the creation fails with:
Error from server (InternalError): error when creating "test-policy.yaml": Internal error occurred: failed calling webhook "mpolicy.kb.io": failed to call webhook: Post "https://vault-config-operator-webhook-service.vault.svc:443/mutate-redhatcop-redhat-io-v1alpha1-policy?timeout=10s": x509: certificate signed by unknown authority

And I see the following error in vault-config-operator's logs:
http: TLS handshake error from 10.42.0.0:45928: remote error: tls: bad certificate

My guess is that this is somehow due to the cert being self-signed? What's confusing to me, is that setting enableCertManager to true also creates self-signed certs, and that is presumably working?

I tried changing my certificate's name to serving-cert, same error.

we should add documentation for BYO certs use case. This is a use case that we don't cover because when you install with OLM, this is taken care for. When you install via helm, we assume the presence of cert-manager. A contribution on the docs on this would be welcome.

can we close this?

Once the linked PR is merged I think

source: gharchive/issue

authors: ameyp raffaelespazzoli

license_type: permissive

license_source: github-api


text:
feat: added a custom user-agent

Closes #994

@alexal Not sure who you are and where you from but this is amazing. You have been doing more contributions than our entire dev team combined.
Thank you so much for doing it!

source: gharchive/pull-request

authors: alexal wtrocki

repo: redhat-developer/app-services-cli


text:
Updated argocd-operator dependency to use released version 0.11.0

What type of PR is this?

Uncomment only one  /kind line, and delete the rest.
For example, > /kind bug would simply become: /kind bug

/kind bug
/kind cleanup
/kind failing-test
/kind enhancement
/kind documentation
/kind code-refactoring

What does this PR do / why we need it:
Have you updated the necessary documentation?

[ ] Documentation update is required by this PR.
[ ] Documentation has been updated.

Which issue(s) this PR fixes:
Fixes #?
Test acceptance criteria:

[ ] Unit Test
[ ] E2E Test

How to test changes / Special notes to the reviewer:

/retest

repo: redhat-developer/gitops-operator


text:
Refactor cobra / use cobra.Args arguments

Uses the cobra.Args arguments for setting maximum / range / minimum
arguments required for some commands rather than using a custom checker.

Problem with standard checks is that you can't display a custom message that will guide user what he did wrong, or what arguments he should provide :-(

@kadel Problem is that our current output display messages aren't much different than what cobra displays. Unless we improve the UX a bit. I'll probably open up another issue to improve some of the descriptions (specifically, ocdev create).

OK, you are right, I looked closer on the messages, and they aren't that much help either :-(

authors: cdrage kadel

repo: redhat-developer/ocdev


text:
API: collect requirements from OpenShift VSCode extension

Work with OpenShift VSCode extension team and create a list of API endpoints that would help extension, sorted by how much it would help extension steam lighting code or speeding up operations
list of commands used by extension - https://github.com/redhat-developer/odo/issues/6990#issuecomment-1660601740

We are waiting for input from plugin developers to know which endpoint to start with, first

Just tested stopping odo dev on Windows. It works fine. If this was the main motivation for exposing a Web API, then I don't think this is needed anymore.

Just tested stopping odo dev on Windows. It works fine. If this was the main motivation for exposing a Web API, then I don't think this is needed anymore.

Thanks! I guess this issue can be closed then. Feel free to reopen if you think otherwise.
/close

repo: redhat-developer/odo


text:
Generate an example PipelineRun YAML for a Pipeline

Fix: #353

Codecov Report

Merging #602 (18b9eb6) into master (a904272) will increase coverage by 0.13%.
The diff coverage is 98.73%.

:exclamation: Current head 18b9eb6 differs from pull request most recent head ccdea09. Consider uploading reports for the commit ccdea09 to get more accurate results

@@            Coverage Diff             @@
##           master     #602      +/-   ##
==========================================
+ Coverage   68.54%   68.68%   +0.13%
==========================================
  Files         101      101
  Lines        6145     6175      +30
  Branches     1084     1087       +3
==========================================
+ Hits         4212     4241      +29
- Misses       1933     1934       +1

Impacted Files
Coverage Δ

src/tekton/generate-template.ts
98.70% <98.70%> (ø)

src/extension.ts
88.95% <100.00%> (+0.06%)
:arrow_up:

Continue to review full report at Codecov.

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

authors: codecov-commenter sudhirverma

repo: redhat-developer/vscode-tekton

license: MIT


text:
operator [O] multicluster-global-hub-operator (0.6.0-dev)

Signed-off-by: morvencao lcao@redhat.com
Thanks for submitting your Operator. Please check the below list before you create your Pull Request.
Updates to existing Operators

[x] Did you create a ci.yaml file according to the update instructions?
[x] Is your new CSV pointing to the previous version with the replaces property if you chose replaces-mode via the updateGraph property in ci.yaml?
[x] Is your new CSV referenced in the appropriate channel defined in the package.yaml or annotations.yaml ?
[x] Have you tested an update to your Operator when deployed via OLM?
[x] Is your submission signed?

Your submission should not

[x] Modify more than one operator
[x] Modify an Operator you don't own
[x] Rename an operator - please remove and add with a different name instead
[x] Modify any files outside the above mentioned folders
[x] Contain more than one commit. Please squash your commits.

Operator Description must contain (in order)

[x] Description of the managed Application and where to find more information
[x] Features and capabilities of your Operator and how to use it
[x] Any manual steps about potential pre-requisites for using your Operator

Operator Metadata should contain

[x] Human readable name and 1-liner description about your Operator
[x] Valid category name1
[x] One of the pre-defined capability levels2
[x] Links to the maintainer, source code and documentation
[x] Example templates for all Custom Resource Definitions intended to be used
[x] A quadratic logo

Remember that you can preview your CSV here.
--
1 If you feel your Operator does not fit any of the pre-defined categories, file an issue against this repo and explain your need
2 For more information see here

/merge possible

/merge possible

authors: framework-automation morvencao


text:
[ISV-1820] Update publish-bundle to return list of references and manifest digests

The references and manifest digests returned from IIB results are
required for signing on the release pipeline.

I've tested this to the extend that I can, but IIB wasn't actually run because it doesn't run on dev/qa and it's broken in stage right now.


text:
add a command_timeout to redisOptions

the user can now specify both connect_timeout and command_timeout
when creating redis context.

@michael-grunder - as we talked in https://github.com/redis/hiredis/pull/829, I added an option for connect_timeout and command_timeout in redisOptions so the user can specify both

This is a nice quality of life improvement.
What do you think about a minor refactor on my branch?
It's a bit easier for me to follow but doesn't change any functionality.

looks good!
small question: what EL stands for?

I'm guessing it stands for "event library" but I didn't initially name them so I could be wrong.

make sense. BTW - there are any other comments?

No, it looks good but I'll run it through an async testing setup I've got before merging.
I think we should include it in v1.0.0

@michael-grunder - any updates?

I'm putting together v1.0.0 and will try to get it included.
I may tweak the change a little bit to use the existing redisContext->timeout name, with an additional member redisContext->command_timeout.  It's less descriptive but it would make the changes completely backward-compatible (I think.  I need to go through it in more detail to be sure).

@yossigo Any objections to merging this for v1.0.0?  Depending on how much of a stickler we want to be to semver I think even an additional struct field is technically a breaking change and would need to wait for 2.0.0
The alternative is to reserve the additional timeout fields in v1.0.0 and push the feature in 1.0.1 which we would able to do while maintaining 100% ABI compatibility.
I'd merge this version of the PR on my fork.

@michael-grunder I think it can be part of 1.0.0.
BTW I am in favor of being strict with such changes, especially as hiredis traditionally offered basically no encapsulation and all major structs are all over the header files so every little change is a potential ABI breakage.

BTW I am in favor of being strict with such changes, especially as hiredis traditionally offered basically no encapsulation and all major structs are all over the header files so every little change is a potential ABI breakage.

Agreed.  Might be worth looking at using opaque structures for the next major version although that's a long ways off.

@valentinogeron Thanks, merged!  I'm going to get this merged into 1.0.0-rc1 and update the docs/changelog.

This change showed one negative effect for me.
I implemented a client that may be configured to use TLS.
When this client tries to connect to a redis port that does not use TLS, the timeout setting does work for the TCP connect but not for the SSL connect. This leads to a blocking client.
redisSSLContextError ssl_error = 0;
redis_ssl_ctx = redisCreateSSLContext(
                        ca_filename, nullptr /*capath*/, cert_filename,
                        key_filename, nullptr /*sni*/, &ssl_error);

if (!redis_ssl_ctx || ssl_error != 0)
{
    /* error handling here */
}

redis_ctx = redisConnectWithTimeout(server_name, server_port, timeout);

/* Workaround: */
/* redisContextSetTimeout(redis_ctx, timeout); */

if ( redis_ctx->err != 0 )
{
    /* error handling here */
}

if (redisInitiateSSLWithContext(redis_ctx, redis_ssl_ctx) != REDIS_OK)
{
    /* error handling here */
}

Is the workaround (commented out) the right solution or should I open an issue?

@wbangna  - The PR goal is to have the ability to control the connect timeout and the command timeout separately.
The TLS handshake occurs after a TCP connection is established (the connect timeout is not relevant from this part), so you must specify command_timeout as well.
Your workaround will work, but you need to use redisSetTimeout instead.
Another option is to use redisConnectWithOptions. With this API, you can configure whatever you want.
For example:
struct timeval connect_timeout = { 1, 500000 };
struct timeval command_timeout = { 2, 500000 };

redisOptions options = {0};
REDIS_OPTIONS_SET_TCP(&options, ip, port);
options.connect_timeout = &connect_timeout;
options.command_timeout = &command_timeout;
redisContext *ctx = redisConnectWithOptions(&options);

@valentinogeron Thank you for your response. My test was successful with the redisConnectWithOptions() function.

authors: michael-grunder valentinogeron wbangna yossigo

repo: redis/hiredis

license_source: bigquery


text:
Connection handshake fails with ERR unknown command CLIENT, with args beginning with: SETINFO lib-name

Bug Report

Current Behavior
The connection does not work and fails to connect to Google Cloud Redis (Memory Store) v7.2 with the following error CLIENT 'SETINFO'. The Client Setinfo not supported by GCP Redis

Stack trace
Exception in thread "main" io.lettuce.core.RedisConnectionException: Unable to connect to IP_ADDRESS/<unresolved>:6379
	at io.lettuce.core.RedisConnectionException.create(RedisConnectionException.java:78)
	at io.lettuce.core.RedisConnectionException.create(RedisConnectionException.java:56)
	at io.lettuce.core.AbstractRedisClient.getConnection(AbstractRedisClient.java:350)
	at io.lettuce.core.RedisClient.connect(RedisClient.java:215)
	at io.lettuce.core.RedisClient.connect(RedisClient.java:200)
	at com.wayfair.smart.ds587.demo.bt.graphql.RedisTest.main(RedisTest.java:29)
Caused by: io.lettuce.core.RedisCommandExecutionException: ERR unknown command 'CLIENT', with args beginning with: 'SETINFO' 'lib-name' 'Lettuce'
	at io.lettuce.core.internal.ExceptionFactory.createExecutionException(ExceptionFactory.java:147)
	at io.lettuce.core.internal.ExceptionFactory.createExecutionException(ExceptionFactory.java:116)
	at io.lettuce.core.protocol.AsyncCommand.completeResult(AsyncCommand.java:120)
	at io.lettuce.core.protocol.AsyncCommand.complete(AsyncCommand.java:111)
	at io.lettuce.core.protocol.CommandWrapper.complete(CommandWrapper.java:63)
	at io.lettuce.core.protocol.CommandHandler.complete(CommandHandler.java:745)
	at io.lettuce.core.protocol.CommandHandler.decode(CommandHandler.java:680)
	at io.lettuce.core.protocol.CommandHandler.channelRead(CommandHandler.java:597)
	at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:442)
	at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:420)
	at io.netty.channel.AbstractChannelHandlerContext.fireChannelRead(AbstractChannelHandlerContext.java:412)
	at io.netty.channel.DefaultChannelPipeline$HeadContext.channelRead(DefaultChannelPipeline.java:1410)
	at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:440)
	at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:420)
	at io.netty.channel.DefaultChannelPipeline.fireChannelRead(DefaultChannelPipeline.java:919)
	at io.netty.channel.epoll.AbstractEpollStreamChannel$EpollStreamUnsafe.epollInReady(AbstractEpollStreamChannel.java:800)
	at io.netty.channel.epoll.EpollEventLoop.processReady(EpollEventLoop.java:509)
	at io.netty.channel.epoll.EpollEventLoop.run(EpollEventLoop.java:407)
	at io.netty.util.concurrent.SingleThreadEventExecutor$4.run(SingleThreadEventExecutor.java:997)
	at io.netty.util.internal.ThreadExecutorMap$2.run(ThreadExecutorMap.java:74)
	at io.netty.util.concurrent.FastThreadLocalRunnable.run(FastThreadLocalRunnable.java:30)
	at java.base/java.lang.Thread.run(Unknown Source)

Input Code

Input Code
// your code here;

Expected behavior/code

Environment

Lettuce version(s): 6.3.2.RELEASE
Redis version: Google Cloud Redis (Memory Store) v7.2

Possible Solution

Additional context

Have you tried to disable the Client Info via RedisURI.setLibraryName(null)/RedisURI.setLibraryVersion(…)?
The issue with Redis derivatives is that they pretend a specific version that we use to control whether certain functionality is available while the derivative server software doesn't implement the Redis OSS functionality we're looking for.

Hi Team,
We are currently facing the same compatibility issue with Lettuce 6.3.2.RELEASE when connecting to Google Cloud Redis (Memory Store) v7.2, an issue that does not occur with the earlier v7.0. We are using Lettuce as a transitive dependency through org.springframework.boot:spring-boot-starter-data-redis:3.2.5.
Could you please provide any advice on potential solutions or workarounds for this issue? Additionally, any information on upcoming fixes or patches would be highly appreciated as it would help us plan our development and maintenance activities better.

Hi Team,
We are currently facing the same compatibility issue with Lettuce 6.3.2.RELEASE when connecting to Google Cloud Redis (Memory Store) v7.2, an issue that does not occur with the earlier v7.0. We are using Lettuce as a transitive dependency through org.springframework.boot:spring-boot-starter-data-redis:3.2.5.
Could you please provide any advice on potential solutions or workarounds for this issue? Additionally, any information on upcoming fixes or patches would be highly appreciated as it would help us plan our development and maintenance activities better.

I think this is what the reference ticket is about https://github.com/redis/lettuce/pull/2823

Folks,
My bad. You can unblock yourself for now if you manually disable the reporting of the client name and version:
RedisURI redisUri = RedisURI.Builder.redis("my.redis.instance.com", 6379)
   .withLibraryName("")
   .withLibraryVersion("")
   .build();
RedisClient redisClient = RedisClient.create(redisUri);

This should unblock you until 7.x is released and you are able to consume the solution in #2823

Do you have a hint how to apply the workaround when using Spring Data?

Do you have a hint how to apply the workaround if using Spring Data?

I assume you are not able to bump the version of the Lettuce driver to 6.4.0.RELEASE?
Have you tried the solution from https://github.com/spring-projects/spring-data-redis/issues/2938#issuecomment-2221289568 ?

First, thanks for the hints.

I assume you are not able to bump the version of the Lettuce driver to 6.4.0.RELEASE?

I could, but is that compatible with Spring Boot 3.3? I didn't dare to just update it.

Have you tried the solution from spring-projects/spring-data-redis#2938 (comment) ?

No, I already looked into that, but that is too much copy and paste for me. Instead of doing this, I prefer to wait for Spring Boot 3.4 before upgrading our Redis to 7.

I could, but is that compatible with Spring Boot 3.3? I didn't dare to just update it.

My bad, I thought I saw a release of spring-data-redis consuming Lettuce 6.4.x
Seems it is still in the works.

No, I already looked into that, but that is too much copy and paste for me. Instead of doing this, I prefer to wait for Spring Boot 3.4 before upgrading our Redis to 7.

This is reasonable if you have the luxury to wait for the fix.

authors: joexfactor markusheiden mp911de tishun xsolo

repo: redis/lettuce


text:
Sentinel aware

Hi,
Are there plans to make node_redis sentinel aware? I'm thinking about being able to use a list of sentinels at startup, then discover and connect to the masters, and subscribing to sentinels message to take into account masters changes. If not, would be happy to start working on it!
Tanguy

Sorry for the me-too... What's the progress on this? It looks like there's no active development on this module right now.

Native sentinel support in node_redis  +1

@blainsmith wut?

@blainsmith Could you let us know what changed? I'd like to know if this a won't-fix or something, so some explanation would be appreciated.

Oops. I forgot to paste in my canned response to this. I was going through and cleaning up really old issues. Sorry about that. I will reopen this and tag it accordingly!

@blainsmith Ah, I see. Thanks for the update. :)

Are there any news on Sentinel? Do you know of any drop-in replacements that do support Sentinel?

Any news? :(

Is there any chances that the most popular Redis client, will get (probably) the most wanted feature (specially for clouds) in any future, after 8 years? 🤔
Or can anyone tell what is the issue with it, to get it implemented? 🧐

I switched to ioredis .. it is a kind of drop in replacement

https://github.com/luin/ioredis/wiki/Migrating-from-node_redis

Guess we will switch to ioredis, this effort appears to have died.

So... after more than 10 years, I'm starting to work on that now... :tada: NEVER say never :P

So... after more than 10 years, I'm starting to work on that now... 🎉 better late than never 😆

Great to hear that, it would be so nice if we have an optimistic eta for that @leibale ?

@nguyenpc I'm not too sure how much time it's gonna take, but the current roadmap is:
V5 with support for RESP3 + some more features
Sentinel
V5 should be ready "soon" (a month or so), then I'll start working on Sentinel :)

Is it now implemented?

Its in the v5 branch waiting for some tests and last minute changes, then we will release a "next"/beta version with it

Hope this comes soon to the main. :)

How this redis sentinel support will work on kubernetes where the redis pod ips may change in time? In the current helm chart it looks like I need to add the IP addresses of the redis sentinel nodes. or I can configure a service targeting the redis pods?

Hi @leibale! I'd to know if there are any plans to release version V5 soon. I've noticed that the working branch is quite active, but I was wondering if there's a target date for releasing a stable or a beta version that includes the Sentinel package?  :)

Hi @leibale! I'd to know if there are any plans to release version V5 soon. I've noticed that the working branch is quite active, but I was wondering if there's a target date for releasing a stable or a beta version that includes the Sentinel package? :)

Hi again, my team have been closely following the development of the V5 version and is very interested in using the new features you are implementing.
Additionally, our team is willing to work with you to speed up the development process so we can use the new version as soon as possible. If we can help, please let us know. We are open to performing tests, providing feedback, or contributing in any other way you find useful.
Thank you in advance

@gianDiazM ATM we are working on:

Client-side caching
Finishing sentinel
Aliging the commands
If you guys want to help with one of those, do performance tests, or just play around with the client, that would be very helpful.
Do you need sentinel specifically to try it out? Can you try it directly from git or do you need an "npm version"?

@gianDiazM first, sorry for the huge delay, I've complement missed your message from 2 weeks ago.. ATM we are working on:

Client-side caching
Finishing sentinel
Aliging the commands

If you guys want to help with one of those, do performance tests, or just play around with the client, that would be very helpful. Do you need sentinel specifically to try it out? Can you try it directly from git or do you need an "npm version"?

Hi @leibale no worries and thank you for getting back to me. We will try to address the points you mentioned. A Redis npm version that includes the client/sentinel package to integrate into our development would be great.
Thanks =)

@leibale we are in a very similar situation as @gianDiazM
what exactly means "finishing" sentinel?

hey, is there any workaround? How can I use my sentinel configuration? redis-sentinel is a good way?

Hi, we also need to use sentinel mode for Redis. Can you give us some information when the version will be release ?

authors: Apollon77 Bonfims Djay77 JustDoItSascha Loki-Afro blainsmith bricss dekelev eberhara gianDiazM herkyl jagdeepak-prat leibale mhart nguyenpc nlfiedler pasztorl qubyte saltukalakus tanguylebarzic

repo: redis/node-redis


text:
Improved error handling when opening the Client

When opening the client, it will throw an error if an existing client is open.
https://github.com/redis/redis-om-node/blob/bded9858c83708c4e847ad74709b454549ca998d/lib/client.ts#L61
It may be better if this error is removed or just logged as a warning. OR the client should implement a public boolean property like is isOpen so the end user can do a check at runtime. Currently, it seems impossible to know if the client is open or not.

👀

Merged this into dev. Will push a new version to npm tomorrow.

Pushed to npm, should be good to go.

authors: codediodeio guyroyse lucemans

repo: redis/redis-om-node


text:
RedissonLocalCachedMap clearLocalCacheAsync method doesn't delete the Semaphore it creates

When we call clearLocalCacheAsync method in RedissonLocalCachedMap to clear the elements from local cache and also to send a message to invalidation topic for all other instances of Redis Client to clear from its local cache.
The framework creates a Semaphore which is also being deleted in the same method. But, there're some instances where this Semaphore is not deleted and it plies up in Redis cluster. Since this Semaphore doesn't have any TTL, over a period of time more and more Semaphore gets created
Expected behavior
What is the reason for creating and deleting the Semaphore. Can we remove the Semaphore creation from clearLocalCacheAsync method in RedissonLocalCachedMap
Actual behavior
The framework creates a Semaphore which is also being deleted in the same method. But, there're some instances where this Semaphore is not deleted and it plies up in Redis cluster. Since this Semaphore doesn't have any TTL, over a period of time more and more Semaphore gets created
Steps to reproduce or test case
Call clearLocalCacheAsync method in RedissonLocalCachedMap
Redisson version
3.16.0
Redisson configuration
Not Applicable

Fixed! Thanks for report

authors: mlakshminara mrniko

repo: redisson/redisson


text:
redisson netty consumes high cpu

Expected behavior
Actual behavior
In Redis cluster mode, when the master node crashes, the application's CPU usage reaches 100%, and even after the master node is restored (becoming a slave node), the CPU usage remains very high.
After checking the CPU usage of threads, it was found that the CPU usage of Redisson Netty occupied almost all CPUs. And the error is as follows:
Unable to write command into connection! Check CPU usage of the JVM. Try to increase nettyThreads setting. Node source: NodeSource [slot=12778, addr=null, redisClient=null, redirect=null, entry=null], connection: RedisConnection@735738459 [redisClient=[addr=redis://10.4.210.79:7001], channel=[id: 0xe55ebb6d, L:/172.16.61.4:51843 ! R:10.4.210.79/10.4.210.79:7001], currentCommand=null, usage=1], command: (SMEMBERS), params: [******] after 0 retry attempts
10.4.210.79:7001 is a failed master node that has been restored.

"redisson-netty-1-1" #19 prio=5 os_prio=0 tid=0x000055791c7a0000 nid=0x23 runnable [0x00007f479cfbb000]
java.lang.Thread.State: RUNNABLE
at sun.nio.ch.EPollArrayWrapper.epollWait(Native Method)
at sun.nio.ch.EPollArrayWrapper.poll(EPollArrayWrapper.java:269)
at sun.nio.ch.EPollSelectorImpl.doSelect(EPollSelectorImpl.java:93)
at sun.nio.ch.SelectorImpl.lockAndDoSelect(SelectorImpl.java:86)
- locked <0x0000000750555158> (a io.netty.channel.nio.SelectedSelectionKeySet)
- locked <0x00000007505c1d90> (a java.util.Collections$UnmodifiableSet)
- locked <0x00000007505550b0> (a sun.nio.ch.EPollSelectorImpl)
at sun.nio.ch.SelectorImpl.select(SelectorImpl.java:97)
at io.netty.channel.nio.SelectedSelectionKeySetSelector.select(SelectedSelectionKeySetSelector.java:62)
at io.netty.channel.nio.NioEventLoop.select(NioEventLoop.java:814)
at io.netty.channel.nio.NioEventLoop.run(NioEventLoop.java:457)
at io.netty.util.concurrent.SingleThreadEventExecutor$4.run(SingleThreadEventExecutor.java:989)
at io.netty.util.internal.ThreadExecutorMap$2.run(ThreadExecutorMap.java:74)
at io.netty.util.concurrent.FastThreadLocalRunnable.run(FastThreadLocalRunnable.java:30)
at java.lang.Thread.run(Thread.java:748)
Locked ownable synchronizers:
- None
"redisson-netty-1-2" #20 prio=5 os_prio=0 tid=0x000055791c53b000 nid=0x24 runnable [0x00007f479ceba000]
java.lang.Thread.State: RUNNABLE
at sun.nio.ch.EPollArrayWrapper.epollWait(Native Method)
at sun.nio.ch.EPollArrayWrapper.poll(EPollArrayWrapper.java:269)
at sun.nio.ch.EPollSelectorImpl.doSelect(EPollSelectorImpl.java:93)
at sun.nio.ch.SelectorImpl.lockAndDoSelect(SelectorImpl.java:86)
- locked <0x000000074fa091e0> (a io.netty.channel.nio.SelectedSelectionKeySet)
- locked <0x0000000750713588> (a java.util.Collections$UnmodifiableSet)
- locked <0x000000074fa09148> (a sun.nio.ch.EPollSelectorImpl)
at sun.nio.ch.SelectorImpl.select(SelectorImpl.java:97)
at sun.nio.ch.SelectorImpl.select(SelectorImpl.java:101)
at io.netty.channel.nio.SelectedSelectionKeySetSelector.select(SelectedSelectionKeySetSelector.java:68)
at io.netty.channel.nio.NioEventLoop.select(NioEventLoop.java:810)
at io.netty.channel.nio.NioEventLoop.run(NioEventLoop.java:457)
at io.netty.util.concurrent.SingleThreadEventExecutor$4.run(SingleThreadEventExecutor.java:989)
at io.netty.util.internal.ThreadExecutorMap$2.run(ThreadExecutorMap.java:74)
at io.netty.util.concurrent.FastThreadLocalRunnable.run(FastThreadLocalRunnable.java:30)
at java.lang.Thread.run(Thread.java:748)
Locked ownable synchronizers:
- None
"redisson-netty-1-30" #56 prio=5 os_prio=0 tid=0x000055791cace800 nid=0x49 runnable [0x00007f479250d000]
java.lang.Thread.State: RUNNABLE
at sun.nio.ch.EPollArrayWrapper.epollWait(Native Method)
at sun.nio.ch.EPollArrayWrapper.poll(EPollArrayWrapper.java:269)
at sun.nio.ch.EPollSelectorImpl.doSelect(EPollSelectorImpl.java:93)
at sun.nio.ch.SelectorImpl.lockAndDoSelect(SelectorImpl.java:86)
- locked <0x000000074fad9fc0> (a io.netty.channel.nio.SelectedSelectionKeySet)
- locked <0x000000075062be20> (a java.util.Collections$UnmodifiableSet)
- locked <0x000000074fad9f28> (a sun.nio.ch.EPollSelectorImpl)
at sun.nio.ch.SelectorImpl.select(SelectorImpl.java:97)
at sun.nio.ch.SelectorImpl.select(SelectorImpl.java:101)
at io.netty.channel.nio.SelectedSelectionKeySetSelector.select(SelectedSelectionKeySetSelector.java:68)
at io.netty.channel.nio.NioEventLoop.select(NioEventLoop.java:810)
at io.netty.channel.nio.NioEventLoop.run(NioEventLoop.java:457)
at io.netty.util.concurrent.SingleThreadEventExecutor$4.run(SingleThreadEventExecutor.java:989)
at io.netty.util.internal.ThreadExecutorMap$2.run(ThreadExecutorMap.java:74)
at io.netty.util.concurrent.FastThreadLocalRunnable.run(FastThreadLocalRunnable.java:30)
at java.lang.Thread.run(Thread.java:748)
Locked ownable synchronizers:
- None
Steps to reproduce or test case

Hang down the master node to reproduce it
Restore the master node to the slave node while still maintaining the status quo

Redis version
5.0.5
Redisson version
redisson-spring-boot-starter:3.30.0
Redisson configuration
config.useClusterServers()
.addNodeAddress(clusterAddresses.toArray(new String[0]))
.setPassword(this.config.get(Options.REDIS_PASSWORD))
.setConnectTimeout(800)
.setTimeout(800)
.setRetryAttempts(0)
.setRetryInterval(1500)
.setMasterConnectionMinimumIdleSize(150)
.setMasterConnectionPoolSize(150)
.setSlaveConnectionMinimumIdleSize(150)
.setSlaveConnectionPoolSize(150)
.setReadMode(ReadMode.MASTER_SLAVE);

Can you share Redisson logs?

Can you share Redisson logs?

org.redisson.client.WriteRedisConnectionException: Unable to write command into connection! Check CPU usage of the JVM. Try to increase nettyThreads setting. Node source: NodeSource [slot=1219, addr=null, redisClient=null, redirect=null, entry=null], connection: RedisConnection@854671988 [redisClient=[addr=redis://10.4.210.78:7001], channel=[id: 0xb8305459, L:/172.16.85.204:43785 ! R:10.4.210.78/10.4.210.78:7001], currentCommand=null, usage=1], command: (SISMEMBER), params: [key name, PooledUnsafeDirectByteBuf(ridx: 0, widx: 17, cap: 256)] after 0 retry attempts
at org.redisson.command.RedisExecutor.checkWriteFuture(RedisExecutor.java:366)
at org.redisson.command.RedisExecutor.lambda$execute$4(RedisExecutor.java:197)
at io.netty.util.concurrent.DefaultPromise.notifyListener0(DefaultPromise.java:578)
at io.netty.util.concurrent.DefaultPromise.notifyListenersNow(DefaultPromise.java:552)
at io.netty.util.concurrent.DefaultPromise.notifyListeners(DefaultPromise.java:491)
at io.netty.util.concurrent.DefaultPromise.setValue0(DefaultPromise.java:616)
at io.netty.util.concurrent.DefaultPromise.setFailure0(DefaultPromise.java:609)
at io.netty.util.concurrent.DefaultPromise.tryFailure(DefaultPromise.java:117)
at io.netty.channel.AbstractChannel$AbstractUnsafe.safeSetFailure(AbstractChannel.java:1021)
at io.netty.channel.AbstractChannel$AbstractUnsafe.write(AbstractChannel.java:882)
at io.netty.channel.DefaultChannelPipeline$HeadContext.write(DefaultChannelPipeline.java:1367)
at io.netty.channel.AbstractChannelHandlerContext.invokeWrite0(AbstractChannelHandlerContext.java:717)
at io.netty.channel.AbstractChannelHandlerContext.invokeWriteAndFlush(AbstractChannelHandlerContext.java:764)
at io.netty.channel.AbstractChannelHandlerContext$WriteTask.run(AbstractChannelHandlerContext.java:1071)
at io.netty.util.concurrent.AbstractEventExecutor.safeExecute(AbstractEventExecutor.java:164)
at io.netty.util.concurrent.SingleThreadEventExecutor.runAllTasks(SingleThreadEventExecutor.java:472)
at io.netty.channel.nio.NioEventLoop.run(NioEventLoop.java:500)
at io.netty.util.concurrent.SingleThreadEventExecutor$4.run(SingleThreadEventExecutor.java:989)
at io.netty.util.internal.ThreadExecutorMap$2.run(ThreadExecutorMap.java:74)
at io.netty.util.concurrent.FastThreadLocalRunnable.run(FastThreadLocalRunnable.java:30)
at java.lang.Thread.run(Thread.java:748)
Caused by: io.netty.channel.StacklessClosedChannelException: null
at io.netty.channel.AbstractChannel$AbstractUnsafe.write(Object, ChannelPromise)(Unknown Source)

Only by restarting the application can it be resolved.

The situation I encountered is the same as this, The Redisson logs are also similar.
https://giters.com/redisson/redisson/issues/5857
I will try version 3.27.2.

The situation I encountered is the same as this, The Redisson logs are also similar. https://giters.com/redisson/redisson/issues/5857
I will try version 3.27.2.

I have try 3.27.2, but it stilll didn't work.

Can you try 3.31.0 version?


text:
🛑 VPS is down

In e22e09d, VPS (https://vps.davidrychly.cz/) was down:

HTTP code: 0
Response time: 0 ms

Resolved: VPS is back up in b2d0abb.


text:
Updated minesweeper

There are no mines around the place you clicked on first. This makes it so you cannot click on a mine with your first click and you will always clear at least 9 squares(It does not work after you restart with 'r').

Redox moved to GitLab years ago, thus if you still want to merge it, move this pull request to there.
If you still want to contribute to Redox, talk with us in the Matrix chat.

authors: dikel hardBSDk

repo: redox-os/games


text:
Make output fields selectable

Redpen flush the errors with many fields such as "line number", "sentence content", "error type" and so on.
Some users would think output is too much and make the fields selectable with a parameter.

This issue will be closed since json format is enough for this problem.

repo: redpen-cc/redpen


text:
Translations update from Weblate

Translations update from Weblate for redtide/SDDM-conf.

I see some people is injecting their info in the about dialog instead of translate the string as is.
I think to add in future a "Translators" page on it but until then I don't want this kind of tricks, so I'm not going to merge any pull request from now on with this behavior.
@stefonarch what is the action taken usually in these case? Should I close the PR or wait for some change?

The same thing was done by @MarongHappy at https://github.com/tsujan/Kvantum/pull/823. I closed it.
Unfortunately, here the correct and incorrect translations are inside the same PR.

Closing should work, but translations are lost. Contacting  the author first and then merging and remove (probably better in weblate) the info?

Contacting the author first and then merging and remove (probably better in weblate) the info?

Yes, though it could be better if there were some kind of "broadcast messaging/chat" to tell people to not do it (at this point for any application in weblate, not only mine)

It seems I gave a too quick look to these recent changes, the Korean translation is the only one with that issue, and now I notice that also PicomConf has the same but was merged.
Thank you for the help and suggestions! I'm still a bit lost in this Weblate thing.

Hm, I think I've overseen some: https://github.com/lxqt/pcmanfm-qt/pull/1663/files

I don't think so;

Yes, you're right. I'll contact him and ask him to revert those changes.
Thinking more about it it's not really a bad place for translators info:  only the few for the given language will be shown.

authors: LXQtBot redtide stefonarch tsujan

repo: redtide/sddm-conf


text:
Closed Connection Exception

I found 1132 org.hibernate.exception.GenericJDBCExceptions that were caused by com.mysql.cj.exceptions.ConnectionIsClosedExceptions in the first large scale test #95.

These Exceptions were very rare during the second stress test #95.


text:
undefined is not an object (evaluating 'e.response.data')

Hello,
I've noticed an error has been thrown from the refiner client package. The error happens when for example a device loses connectivity and the ping request fails. As a consequence of that refiner stops showing surveys.
{snip} re"),e.response&&400===e.response.status||(g=!0),e.response.data&&e.response.data.ping_again_in?K("refiner_ping_again_after",Math.floor(Date {snip}

/*!
* Determine if an object is a Buffer
*
* @author Feross Aboukhadijeh <https://feross.org>
* @license MIT

We recently started seeing this error as well
Cannot read property 'data' of undefined

{snip} e"),e.response&&400===e.response.status||(g=!0),e.response.data&&e.response.data.ping_again_in?K("refiner_ping_again_after",Math.floor(Date. {snip}

Tends to happen with network connectivity issues, as mentioned above. Is there a way to add retries to the client package?

Hey @ipetrovbg and @wallies ! Thanks for bringing this to our attention and please excuse the late reply. We just saw the issue here.
This should have been fixed a couple of weeks ago. The client should now gracefully handle lost connections.

authors: chezmo ipetrovbg wallies

repo: refiner-io/npm-package


text:
Changed dict values are not reflected in foreach

Describe the bug
Changed dict values are not reflected in foreach
Entering a value in editable changes #2 but leaves #1 unaffected.
To Reproduce
Steps to reproduce the behavior:
import reflex as rx

class State(rx.State):
    dict_list: list[dict[str,str]] = [{"name": "A", "age": "10"}, {"name": "B", "age": "20"}]
    test_value: str = '0'

    def update_value(self, name: str, new_age: str):
        for item in self.dict_list:
            if item['name'] == name:
                item['age'] = new_age #1
        self.test_value = new_age #2
        print(self.dict_list)

def test(item: dict[str,str]):
    return rx.hstack(
        rx.text(item['name']),
        rx.text(item['age']), #1
        rx.text(State.test_value), #2
        rx.editable(
            rx.editable_preview(),
            rx.editable_input(),
            placeholder="age input",
            default_value= item['age'],
            on_change= lambda new_age: State.update_value(item['name'], new_age),
            width="100%",
        ),
    )

def index():
    return rx.box(rx.foreach(State.dict_list, test))

app = rx.App(state=State)
app.add_page(index)
app.compile()

Expected behavior
#1 and #2 should be the same since they both follow the new_age value.
Screenshots
If applicable, add screenshots to help explain your problem.
Specifics (please complete the following information):

Python Version: 3.11.4
Reflex Version: 0.2.8
OS: Windows 10
Browser (Optional): Chrome

Additional context
Add any other context about the problem here.

Thanks for the repro case. I have identified the issue in a recent change and will submit a fix.

authors: Evenzel masenf

repo: reflex-dev/reflex


text:
Add matchingThreshold config

ref: https://github.com/reg-viz/reg-cli/pull/204

@mtsmfm Thanks for your contribute 😄
It's released as v0.7.16 !

authors: Quramy mtsmfm

repo: reg-viz/reg-suit


text:
Touchpad Scrolling Not Working in Sway's Tabbed/Stacked Mode

Hello Regolith Team,
I've encountered an issue while using Regolith with the Sway window manager, specifically when windows are in tabbed or stacked mode. The problem is that scrolling through the windows (to change the active one) with the touchpad does not work, whereas using a mouse's scroll wheel functions as expected.
Environment:

Regolith Version: 3.1
Sway Version: 1.8
Operating System: Ubuntu

Steps to Reproduce:

Open multiple windows in Sway under Regolith.
Change the window layout to either tabbed or stacked mode.
Attempt to scroll within a window title using the touchpad.

Expected Behavior:
Scrolling with the touchpad should allow me to change the active window, how it works when using a mouse.
Actual Behavior:
Scrolling with the touchpad has no change in which the active window is, while mouse scrolling works perfectly.
Thank you for your time and effort in maintaining Regolith and Regolith Sway.

I can confirm this behaviour. Does i3 allow scrolling on the window title to change tabs? If it does, you can file an issue with the upstream sway repo here with the i3-compat tag.

authors: SoumyaRanjanPatnaik rmasad

repo: regolith-linux/sway-regolith


text:
Update zio, zio-streams to 2.0.16

About this PR
📦 Updates

dev.zio:zio
dev.zio:zio-streams

from 2.0.2 to 2.0.16
📜 GitHub Release Notes - Version Diff
Usage
✅ Please merge!
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

⚙ Adjust future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "dev.zio" } ]

Or, add this to slow down future updates of this dependency:
dependencyOverrides = [{
  pullRequests = { frequency = "30 days" },
  dependency = { groupId = "dev.zio" }
}]

labels: library-update, early-semver-patch, semver-spec-patch, commit-count:1

Superseded by #503.

repo: reibitto/podpodge


text:
🛑 Library and Knowledge Center (LKC) is down

In 5dcf5fb, Library and Knowledge Center (LKC) (http://library.binus.ac.id) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Library and Knowledge Center (LKC) is back up in c3a09e5.


text:
🛑 BINUS Entrepreneurship (BEC) Apps is down

In 9159c10, BINUS Entrepreneurship (BEC) Apps (https://entrepreneurship.apps.binus.ac.id) was down:

HTTP code: 0
Response time: 0 ms

Resolved: BINUS Entrepreneurship (BEC) Apps is back up in d8d70fa.


text:
🛑 GreatNusa.com is down

In 306728c, GreatNusa.com (https://greatnusa.com) was down:

HTTP code: 403
Response time: 66 ms

Resolved: GreatNusa.com is back up in b954637.


text:
🛑 GreatNusa.com is down

In 0efda48, GreatNusa.com (https://greatnusa.com) was down:

HTTP code: 403
Response time: 78 ms

Resolved: GreatNusa.com is back up in 62f0b0f.


text:
🛑 GreatNusa.com is down

In 3432d5b, GreatNusa.com (https://greatnusa.com) was down:

HTTP code: 403
Response time: 119 ms

Resolved: GreatNusa.com is back up in b7a6923.


text:
🛑 BINUS Store is down

In cf8ac29, BINUS Store (https://binusstore.com) was down:

HTTP code: 0
Response time: 0 ms

Resolved: BINUS Store is back up in 544bb93.


text:
Import: Error when wrong field is uploaded

Bug report made at Castor, as there is a problem with error handling when importing a field that does not exist in a survey or report instance.
Bug report:
It concerns the following endpoints:
https://data.castoredc.com/api#/data-point-collection/post_study__study_id__record__record_id__data_point_collection_study
https://data.castoredc.com/api#/data-point-collection/post_study__study_id__record__record_id__data_point_collection_report_instance__report_instance_id_
When I upload data through these endpoints, I normally got a response object with the successful and failed requests.
This all works fine when uploading correct data (correct fields for the given instance & data that is between boundaries)
And also works fine when uploading data for the correct fields for the instance and that is within the boundaries.
These are the corresponding models
https://data.castoredc.com/api#/data-point-collection/post_study__study_id__record__record_id__data_point_collection_study
https://data.castoredc.com/api#/data-point-collection/post_study__study_id__record__record_id__data_point_collection_study
However, in prior versions of the API, when one added a field that did not exist in the instance within the body to be uploaded through the API, this would be given in the failed part of the model
So the server would not error, but just return within the failed part of the response dict that an error occurred.
This means that on the client side, we see which failed, and why.
However currently when you upload a field that does not exist, the server returns a 500 Internal Server Error for the entire request.
So the entire request returns an error, yet when I look in my study through data.castoredc.com I see that the other values of the request are uploaded.
So 5 values are uploaded, 1 errors, and the server only returns an error without any information on the other values.
This means that on the client side, we can’t see what part has succeeded and what part has failed.

Will need to write client side checking of field being a child of instance, instead of relying on server side handling.

Fixed in #65