-
Notifications
You must be signed in to change notification settings - Fork 22
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
Feature: Add basic progress indicator & activity info #33
base: main
Are you sure you want to change the base?
Feature: Add basic progress indicator & activity info #33
Conversation
Codecov Report
@@ Coverage Diff @@
## main #33 +/- ##
==========================================
- Coverage 59.91% 59.57% -0.34%
==========================================
Files 3 3
Lines 232 235 +3
==========================================
+ Hits 139 140 +1
- Misses 93 95 +2
|
Test fails seem to be due to: napari/napari#4747 (comment) |
I can't see the direct connection to the importlib-metadata issue mentioned in that comment, but yes, if we're not explicitly pinning the napari dependency here to v0.14.4 (the last one to support 3.7), then i wouldn't expect any tests to work on 3.7. go ahead and drop |
Hi @tlambert03 the python 3.7 tests are actually running in napari 0.4.14, but failing due to the |
Hmm, so now it's the same symptom as Edit: The tests hang for my locally too, even though everything works when run in napari, so it's something related to qtbot/pytest-qt? |
Grr, the hanging tests.
Note: that control-C to interrupt wasn't successful, I had to kill the python processes -- there were 2. |
This is a basic attempt at addressing #27
and showing some status/busy info the napari gui.
The potentially long running tasks will now show an indicator that something is happening (the neato moving boxes in the lower right)
Additionally, a notification is provided of the main tasks after click
run
: (down)loading models and running segmentationcc: @kandarpksk