Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Finder file progress circles show incorrect values #16738

Closed
sensibleish opened this issue Jan 2, 2025 · 0 comments
Closed

Finder file progress circles show incorrect values #16738

sensibleish opened this issue Jan 2, 2025 · 0 comments
Assignees
Milestone

Comments

@sensibleish
Copy link

sensibleish commented Jan 2, 2025

Describe the bug
When copying multiple files, Cyberduck triggers macOS Finder to display circular progress indicators by each file. The indicators incorrectly show the status of the overall transfer instead of each file's progress. Except for the last file copied, after the full copy ends the indicators remain visible in incomplete state.

To Reproduce

  1. Open a Finder window with files to copy. I use list view, but doubt that matters.
  2. In Cyberduck, open a window to a remote file server. I tested with SFTP.
  3. Copy the files to the remote server by dragging the files from Finder to the remote server window.
  4. In Finder, observe the circular progress indicators by each file's name. Each shows the status of the overall transfer while that file was copying.

Expected behavior
Finder displays circular progress indicators by each file's name. As each file transfers, its indicator fills. The % of fill corresponds to the % copied of that file. When each file is fully copied, its indicator reaches full state and disappears.

Screenshots
Here's what it looks like after copying 4 files of similar size:

image

Desktop (please complete the following information):

  • OS: macOS 15.2
  • Version 9.1.1

Additional context
I didn't test whether the problem happens when copying from remote to local.

I was surprised to see the progress indicators on source files. My intuition is these should only appear on destination files, when copying files from a remote server to the local disk. But maybe this bug exists in that situation too.

@dkocher dkocher self-assigned this Jan 3, 2025
@dkocher dkocher added this to the 9.1.2 milestone Jan 3, 2025
@dkocher dkocher closed this as completed Jan 3, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants