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
There are various blocking and background operations within the extension.
Such as waiting for the test containers to start or verifying all the brokers have started.
Currently these are hard coded, we should expose them somehow to users.
We could:
The other question we need to address is the timeout global or local. I.e. is it one timeout to cover all operations or a per operation timeout.
For the moment I don't see a need to be able to customise different calls individually.
The text was updated successfully, but these errors were encountered:
No branches or pull requests
There are various blocking and background operations within the extension.
Such as waiting for the test containers to start or verifying all the brokers have started.
Currently these are hard coded, we should expose them somehow to users.
We could:
The other question we need to address is the timeout global or local. I.e. is it one timeout to cover all operations or a per operation timeout.
For the moment I don't see a need to be able to customise different calls individually.
The text was updated successfully, but these errors were encountered: