You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Error: commitCache failed: {"$id":"1","innerException":null,"message":"Request was blocked due to exceeding usage of resource 'Count' in namespace ''.","typeName":"Microsoft.TeamFoundation.Framework.Server.RequestBlockedException, Microsoft.TeamFoundation.Framework.Server","typeKey":"RequestBlockedException","errorCode":0,"eventId":3000}
at /home/runner/work/_actions/burrunan/gradle-cache-action/v1.4/dist/cache-action-entrypoint.js:15662:11
at Generator.throw (<anonymous>)
at rejected (/home/runner/work/_actions/burrunan/gradle-cache-action/v1.4/dist/cache-action-entrypoint.js:15615:27)
at runMicrotasks (<anonymous>)
at processTicksAndRejections (internal/process/task_queues.js:93:5)
So the workarounds could be:
a) Allow users to configure the order of remote build cache bs GitHub-based remote build cache (e.g. try S3-based cache first, and GitHub-based cache later)
b) Allow users to configure regexp of the task needs to be cached (e.g. cache .*test.* only)
c) Implement throttling in the build-cache proxy (e.g. respond with "not found" for requests coming too often)
c) Disable GitHub-based remote build cache by default (==revert to old file-based caching approach)
The text was updated successfully, but these errors were encountered:
See open-telemetry/opentelemetry-java-instrumentation#1205
So the workarounds could be:
a) Allow users to configure the order of
remote build cache
bsGitHub-based remote build cache
(e.g. try S3-based cache first, and GitHub-based cache later)b) Allow users to configure regexp of the task needs to be cached (e.g. cache
.*test.*
only)c) Implement throttling in the build-cache proxy (e.g. respond with "not found" for requests coming too often)
c) Disable GitHub-based remote build cache by default (==revert to old file-based caching approach)
The text was updated successfully, but these errors were encountered: