GitHub Community
getCacheEntry failed: {"$id":"1","innerException":null,"message":"Database pool DefaultPartitionPool is full. Raise the MaxDatabaseLimit or use a different pool #25791
-
|
Github Actions is currently throwing database errors during my pipeline runs. I have run the same workflow templates running fine on different repos and it works but this specific repo is kind of borked I guess, or it’s physically located somewhere where there are some technical problems. Just thought I would share. the initial error was… The issue seems out of my control… Failed Runs: Update pre-commit-check.yaml · gregnrobinson/kube-secrets@3baa48c · GitHub I don’t think the repo has been able to do one successful run yet.  Update pre-commit-check.yaml · gregnrobinson/kube-secrets@3baa48cA project that provides a simple interface to deploy Kubernetes secrets from a single configuration file. - Update pre-commit-check.yaml · gregnrobinson/kube-secrets@3baa48c |
Beta Was this translation helpful? Give feedback.
Replies: 3 comments
-
|
I’m seeing the same error with a different action. The Github Status Page shows no active incidents on Actions. |
Beta Was this translation helpful? Give feedback.
-
|
Hi, thanks for reporting this. The issue should now be mitigated. We’re tracking any followup at Cache creation failed · Issue #698 · actions/cache · GitHub |
Beta Was this translation helpful? Give feedback.
-
|
Thank you. That fixed the issue for me. 👍 |
Beta Was this translation helpful? Give feedback.
Hi, thanks for reporting this. The issue should now be mitigated. We’re tracking any followup at Cache creation failed · Issue #698 · actions/cache · GitHub