Age | Commit message (Collapse) | Author |
|
(cherry picked from commit f8ff0360e905a11b8b5929b8e69839a887c8d439)
|
|
(cherry picked from commit 425f4877dec8b4ee2f0796241e54b8a2f71a6c61)
|
|
(cherry picked from commit 58e18da0c32017e526e2ba02f8ed9ebc2ad991e9)
|
|
(#398)
So it seems that tui-rs doesn't like rendering my CPU bars if the height is exactly 1. It needs at least 2. I have no idea why, this is probably something weird with how I render.
This, of course, breaks when there is only one row to report (i.e. with a dual core setup in #397).
The workaround switches the gap between the CPU and mem/net parts to 0, and increases the CPU's draw height by 1, only when the height is otherwise 1 (so the draw height is now at least 2). This does have the side effect of including an extra line to the side borders, but I think it's fine.
(cherry picked from commit d48e6cd7e080432daeca54a0aff9271c60a45107)
|
|
Fixes a bug where you could make the sorting arrow disappear in the mem column if you did:
1. Go to proc widget
2. Switch to memory values from %
3. Press `m`
(cherry picked from commit e30518bf6213bb99d333f836ecaeb252f967d41e)
|
|
Fixes the `hide_table_gap` option not working with the battery widget.
(cherry picked from commit cfddb7e223ce05ab916965abd72cebf40466058c)
|
|
Fixes the colour order being off in basic mode, and not using the average CPU colour.
(cherry picked from commit 23ad597d18f28cbe079f29f720d74506bd858c53)
|
|
(cherry picked from commit bfdaa09e3a397df08ff45c44022537195bab0c2b)
|
|
Use heim on ARM targets again where appropriate.
(cherry picked from commit 682f6493d1b0cd7e138b734cf5e789d81530bda5)
|
|
(cherry picked from commit 061cdb913b04aa6cd7e29cf0cc285227ac21846a)
|
|
(cherry picked from commit 4471ecc16162edce8616f5b92c756a5fd46cccd4)
|
|
(cherry picked from commit 49cfc75aca75ccda53f1dd40be584f82094389fb)
|
|
|
|
|
|
- Move data rather than cloning during data transferring step
- Try using beef?
|
|
|
|
Making some small changes that would hopefully improve performance a bit.
- Remove redundant string generations for CPU data conversion
- Switch to fnv for PID hashmap and hashsets
- Use buffered reading to avoid having to store too many lines as strings
|
|
Turns out there was yet another bug with the CPU colour allocation. I had forgotten to use the same index calculation for the "all" position.
|
|
|
|
Fixes some performance regressions and forgotten cleanup.
Changes to attempt to improve performance to match 0.4.x:
- Remove `trace!` and `--debug` for now. These were a significant hog. Removing this dropped initial memory usage by about half.
- Add additional cleaning step for `pid_mapping` during process harvesting. This should hopefully improve memory usage as time goes on.
- Slightly change how we do sorting to hopefully be a bit more optimal? This was just an easy change to make that I spotted.
- Fix broken cleaning child thread task.
|
|
Move from gnu to musl to avoid glibc issues.
|
|
|
|
Fixes another change breaking states from showing in processes.
|
|
|
|
|
|
|
|
|
|
Refactors the data harvesting system function names.
|
|
|
|
Adds the option to enable an "out of" indicator for scrollable table widgets (using --show_table_scroll_position).
|
|
Previously it was CURL-ing from a non-existent URL, giving the wrong SHA hashes.
Changed to upload the binaries as artifacts and using those directly.
|
|
|
|
Fixes colour theming for batteries being flipped.
|
|
- Fix bug with choco and homebrew using incorrect bash syntax causing broken downloads. Why this didn't fail, idk.
- Add tag entry for manual runs to make it easier to deploy/re-run
- Fixed some typos
- Fixed incorrect string in choco python script
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Switch from lazy_static to once_cell.
|
|
|
|
Fixes an issue in the windows deployment action.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|