Closed glin closed 1 month ago
The checks passed but the it wasn't reported back to the PR properly, and I couldn't merge the PR. I thought this new PR would fix it, but I think it's still happening.
With this PR, now I'm getting some docker issue?
ERROR: failed to create cluster: failed to pull image "kindest/node:v1.19.1@sha256:98cf5288864662e37115e362b23e4369c8c4a408f99cbc06e58ac30ddc721600": command "docker pull kindest/node:v1.19.1@sha256:98cf5288864662e37115e362b23e4369c8c4a408f99cbc06e58ac30ddc721600" failed with error: exit status 1
Command Output: Error response from daemon: Get "https://registry-1.docker.io/v2/kindest/node/manifests/sha256:98cf5288864662e37115e362b[23](https://github.com/rstudio/helm/actions/runs/11077279815/job/30783680906#step:7:24)e4369c8c4a408f99cbc06e58ac30ddc721600": received unexpected HTTP status: 500 Internal Server Error
Same as #561, redoing for CI issue
Postgres.UsageDataPassword
is supposed to default toPostgres.Password
, but a bug in recent PPM versions prevents this from working. So as a temporary workaround, thePostgres.UsageDataPassword
setting must be explicitly set toPostgres.Password
when using Postgres with usage data enabled.This will be fixed in the next Package Manager release. The config can be removed after the next release, but it also won't cause any issues if you keep it around for the next release.