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: system status #5743
Feature: system status #5743
Conversation
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## dev #5743 +/- ##
==========================================
+ Coverage 96.97% 96.99% +0.02%
==========================================
Files 408 412 +4
Lines 16249 16376 +127
Branches 1180 1185 +5
==========================================
+ Hits 15757 15884 +127
Misses 492 492
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. |
e47c128
to
8af49c8
Compare
If possible, please add the underlying file system, too. |
It displays the info for the |
The size/free space info. I would really like to know (see my feature request 8-) ) whether the file system has certain features (e. g. external attributes) (or whether it was a good choice -- I know someone running on exFAT...). That would be good to know for you, too, if you decide to add a button "click here and copy it into a JSON structure to paste into a bug report" later. |
Given most users are running inside docker I’m not sure how much of that is available to the python backend. In general the goal here is not to be a comprehensive stack inspector, just to alert the user of potential problems and the basics of their setup. |
Would it make sense to include the status of the search index as well as the classification model? |
840caef
to
ab9b5d5
Compare
f624ed2
to
914db68
Compare
Thanks stumpy. Yea my thing with this one is a little unsure how it will behave in some environments (looking at you nixOS), may need some iterating... |
This pull request has been automatically locked since there has not been any recent activity after it was closed. Please open a new discussion or issue for related concerns. See our contributing guidelines for more details. |
Proposed change
Seems like a useful but hopefully unobtrusive little thing to have. Im not totally certain about some of the methods for retrieving environment etc. but I got expected results when testing myself. Would be good to check that, false-positive errors (or false negatives) would suck.
No rush on this, happy to iterate.
Closes #5704
Type of change
Checklist:
pre-commit
hooks, see documentation.