-
Notifications
You must be signed in to change notification settings - Fork 373
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
chore(#994): simplify server start #1014
Conversation
Codecov Report
@@ Coverage Diff @@
## master #1014 +/- ##
==========================================
- Coverage 95.36% 95.14% -0.23%
==========================================
Files 110 111 +1
Lines 4248 4260 +12
==========================================
+ Hits 4051 4053 +2
- Misses 197 207 +10
Flags with carried forward coverage won't be shown. Click here to find out more.
Continue to review full report at Codecov.
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
💯 Just a few inline suggestions. also, the setup&installation docs will be updated soon due to #994.
@frascuchon ah, I forgot, if we want to deprecate the |
One additional comment, which is a feedback we get often. I don't know where is the best place but I would like to have a very clear message when some starts the server and the Elasticsearch endpoint is not available/running, etc, I don't know if we check that at some point but I recall the message it's a standard trace. We should be very informative at this point, explaining:
Ideally this should be applicable to other scenarios when the ES instance is not responding --> including a trace in the server process. I think this is key to help our users troubleshoot the issues with Elastic which is frequently the only bottleneck for getting started. I understand this should go on another issue/PR |
Yes, i prefer include in a separate PR. Could you create a issue to track the change @dvsrepo ? |
Done |
Co-authored-by: David Fidalgo <david@recogn.ai>
* 'master' of https://github.com/recognai/rubrix: (28 commits) chore(#994): simplify server start (#1014) refactor(#945): elasticsearch index configuration per task (#1018) docs(#980): Add majorityvote example to weak supervision guide (#1004) fix(#1015): manage emojis in Token Classification records (#1016) fix(#1010): fix WeakLabels when not providing rules (#1011) fix(Breadcrumbs): Copy text function (#1003) fix(statics): handle 404 errors for static files (#1006) refactor: Rename 'exclude_missing_annotation' argument for WeakLabels.annotation (#1005) docs: update video for spacy ner tutorial (#1000) fix(#977) Remove redirection when accessing login (#996) feat(#951): new uncovered_by_rules records filter (#991) feat(#735): add warning when agent but no prediction/annotation is provided (#987) fix(#800): limit number of metadata fields (#993) docs: improve annotate records section in web app reference (#985) fix(#844) Keep header layout when errors occurred in dataset view (#992) fix(#974): display the dropdown in the last record of the scroll (#986) refactor: compute common aggregations one by one (#990) feat(#953): add additional metrics to `LabelModel.score` method (#979) refactor(rules): using labeling rules management with vuex store (#878) feat(#955): add default for `rules` in WeakLabels (#976) ...
* refactor: move server launch to main module * docs: update setup section * revert: remove old __main__ file * chore: include FutureWarning * Update docs/getting_started/setup&installation.rst Co-authored-by: David Fidalgo <david@recogn.ai> Co-authored-by: David Fidalgo <david@recogn.ai> (cherry picked from commit 7667ae8)
This PR changes how to launch rubrix server to:
The old command (
python -m rubrix.server
) is also availableAlso, include setup info about uvicorn setup. Basically, you can launch rubrix server using uvicorn: