mirror of
https://github.com/d99kris/nmail.git
synced 2026-04-26 17:56:00 +03:00
[GH-ISSUE #80] [Enhancement] Better full-sync reporting #67
Labels
No labels
bug
enhancement
pull-request
question
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/nmail#67
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @Kabouik on GitHub (May 8, 2021).
Original GitHub issue: https://github.com/d99kris/nmail/issues/80
Originally assigned to: @d99kris on GitHub.
Currently nmail full-sync reports fetching individually for each folder, but there is no indication of how many folders have to be fetched, how big they are, how much total disk space will be required, or that the fetching percentage being reported is indeed supposed to restart from 0 when fetching a new folder.
This may not be trivial for new users or others (I only recently understood that the percentage restarting from zero multiple times is expected, before that I was wondering if my full-syncs were working as intended or if I should interrupt them and restart). Better reporting may also help towards #79 when fetching large folders, so a user can interrupt before reaching an error if the folders to fetch are too big.
Side question: is there currently a way to fully synchornize individual folders, and possibly to also clear the corresponding cache for individual folders from within nmail as well? Would it make any sense or should cache clearing be done only outside nmail? I have no firm opinion, just asking what you think.
@d99kris commented on GitHub (Aug 6, 2022):
Improved progress reporting for full sync should be fixed with above commit. Please let me know if you're still encountering any issues.