-
Notifications
You must be signed in to change notification settings - Fork 592
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
Evidently Collector in v0.4.16 #1012
Labels
bug
Something isn't working
Comments
thanks for reporting! let us take a look at this |
@mike0sv |
@c0t0ber yes, go ahead. Also you'll need to annotate some routes's return types |
c0t0ber
added a commit
to c0t0ber/evidently
that referenced
this issue
Feb 29, 2024
emeli-dral
pushed a commit
that referenced
this issue
Mar 15, 2024
* New trigger has been added to initiate a snapshot for the collector based on time or the number of rows * fix: Collector litestar server cant start #1012 * Implement repeated call of check_snapshots_factory using lifespan * Update linestar to 2.6.3 litestar-org/litestar#3150 - Schema generation fixed * Added error logging for snapshot creation * Added call of synchronous functions using ThreadPoolExecutor in create_snapshot to avoid blocking the loop * CollectorClient returns the response as a dict * Added smoke tests for the core functionality of the collector api * Update tests/collector/test_app.py Co-authored-by: Janek Nouvertné <[email protected]> * Skip server tests --------- Co-authored-by: Mikhail Sveshnikov <[email protected]> Co-authored-by: Janek Nouvertné <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
When I try to run
evidently collector
from version 0.4.16, I am getting the following error:The text was updated successfully, but these errors were encountered: