Without a better progress indicator, one can falsely think that formatting has hung
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 35/100
- Issue type
- Feature
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- python
- Domain
- desktop, operating-systems
Research direction
Start by locating mintstick's formatting workflow and how it currently reports formatter activity, then determine whether ext4 or FAT32 operations expose usable progress data. Done means a long-running format shows changing progress or a meaningful estimate instead of only a busy indicator, without claiming precision the formatter cannot provide.
Written by the indexing model from the issue text.
Description
The problem. I formatted a USB stick to ext4. The stick was 32GB. So one might think that format will take a while. But, still, formatting - at least when FAT32? - can be quick. This format was slow - so slow, that I considered removing drive. I thought the formatting had hung. But then the formatting completed.
The solution: have the formatter show more than a busy-type indicator. That is, have it show a percentage or something like that (and the indicator need not be very accurate). It's true that a drive reporting that it is X% formatted might still have hung, but if one can see progress - X%, then X+Y% - one is less likely to be misled. Still, perhaps the low-level formatting process does not give much data about progress. In that case, perhaps mintstick could estimate, in advance, the likely time, and then do something, indicator wise, with that (well, with that and the elapsed time).
mintstick 1.6.2
- Dominant language
- Python
- Stars
- 173
- Forks
- 64
- PR merge metrics
- No merged PRs in 30d
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from linuxmint/mintstick
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
Difficulty 4/5 3-5 days Newbie friendliness 58/100
-
Difficulty 3/5 1-2 days Newbie friendliness 48/100
-
Difficulty 3/5 1-2 days Newbie friendliness 35/100
-
Difficulty 3/5 1-2 days Newbie friendliness 30/100
All issues in linuxmint/mintstick
Similar issues
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
zostera/django-bootstrap4#894 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
use-agent-os/agent-os#3276 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
zephyrproject-rtos/zephyr#119726 ·
-
area/auth bug comp/agent P3 platform/discord type/security
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
NousResearch/hermes-agent#117848 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
zilliztech/memsearch#759 ·