Rework progress bar to single unified component#408
Merged
Conversation
The old 1% progress threshold caused the UI to appear frozen on large files (e.g. 1GB) because many read/write iterations passed between redraws. Switching to a 100ms time-based interval ensures consistent UI responsiveness regardless of file size.
Call self.view() right after mount_progress_bar() at all 6 call sites so the bar is visible on screen before the transfer loop begins.
|
✔️ 7f294c0...c74c1c9 - Conventional commits check succeeded. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
TransferProgressBarcomponent that tracks bytes transferred with lazy estimationtransfer_progress_barfieldremotefs-sshto 0.8.1Test plan
transfer_progress_barfieldcargo test --no-default-features --features github-actions --no-fail-fast