Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

GitHub throttles requests #21

Open
vlsi opened this issue Sep 16, 2020 · 0 comments
Open

GitHub throttles requests #21

vlsi opened this issue Sep 16, 2020 · 0 comments

Comments

@vlsi
Copy link
Contributor

vlsi commented Sep 16, 2020

See open-telemetry/opentelemetry-java-instrumentation#1205

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)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant