Closed jkbecker closed 3 years ago
The changes above result in this runtime behavior - it's definitely suboptimal because some crucial information is missing, but I believe this can be added by looking into how glances gets these values (for example). Without these changes, none of the panels are able to run, as there are exceptions thrown in _cpu.py
, _mem.py
, _info.py
, and _proc_list.py
.
I'd already merge it now because the PR adds functionality and removes nothing, but let me know when you yourself are happy with it.
Sure, maybe that's a good idea - I can't promise that I'll be able to work on any of the more extensive fixes any time soon, so it's probably better to not hold this here artificially if you're ok with the changes.
I've now merged a bunch of PRs which should fix most (?) of the issues. Could you try again with v0.0.6?
All merged changes are an improvement except for the memory change
values = [mem.used, mem.available, mem.cached if hasattr(mem, 'cached') else 0, mem.free]
which seems to be reverted in the other PRs. Should I add it back or do you prefer a different way of mitigating this?
This is handled differently now.
Ah, I see what you were doing there... it's missing the values, which still break. Fix coming up, I think that should be it then.
A more fitting fix is in #18.
I think all of the issues here are fixed now.
These are just some basic fixes and a WIP, not ready for merging yet.
Turns out some neat features have to be solved differently for macOS specifically, or are specifically Linux-only, which will make them either go missing or have weird values on non-Linux OSes.
Fixes #6.