We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
The default rate limit for AbstractWaitStrategy is a constant rate of one try per second.
While this safe choice makes sense, some quick-to-start container would benefit from higher rates and thus making testcontainer faster.
My proposal is to add a withRateLimiter method to AbstractWaitStrategy allowing to override the default DOCKER_CLIENT_RATE_LIMITER.
The text was updated successfully, but these errors were encountered:
PR available here: #838
Sorry, something went wrong.
We have this out in a Release Candidate build (1.9.0-rc1) for anyone who is keen to try it!
Release notes
Cool, I will have a look!
Is there some planned release date for 1.9.0?
Released as 1.9.0 :)
No branches or pull requests
The default rate limit for AbstractWaitStrategy is a constant rate of one try per second.
While this safe choice makes sense, some quick-to-start container would benefit from higher rates and thus making testcontainer faster.
My proposal is to add a withRateLimiter method to AbstractWaitStrategy allowing to override the default DOCKER_CLIENT_RATE_LIMITER.
The text was updated successfully, but these errors were encountered: