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 dev branch of the client is meant to be compatible with the qdrant dev image.
dev
As it depends on a moving API, the client can become broken without any changes to the client itself.
We would like to detect those issues early on in order to stay functional and potential fix unintentional breakes in the API.
One way to improve the situation would be the have a daily CRON job executing the tests against the latest qdrant dev image.
A notification could be pushed on failure.
The text was updated successfully, but these errors were encountered:
No branches or pull requests
The
dev
branch of the client is meant to be compatible with the qdrantdev
image.As it depends on a moving API, the client can become broken without any changes to the client itself.
We would like to detect those issues early on in order to stay functional and potential fix unintentional breakes in the API.
One way to improve the situation would be the have a daily CRON job executing the tests against the latest qdrant
dev
image.A notification could be pushed on failure.
The text was updated successfully, but these errors were encountered: