nextcloud / desktop

💻 Desktop sync client for Nextcloud
https://nextcloud.com/install/#install-clients
GNU General Public License v2.0
2.99k stars 790 forks source link

"Copy public link" not shown for a while after syncing. #4448

Open svenlange2 opened 2 years ago

svenlange2 commented 2 years ago

⚠️ Before submitting, please verify the following: ⚠️

Bug description

Windows context menu for files does not show "Copy public link" right after the file has been synced to the server. The syncing takes place immediately and the file appears in web UI and public link sharing is possible right away but not in windows contect menu for the file. Usually the "Copy public link" selection appears after ca 1 minute which is too long. Especially for small files that are long uploaded by that time.

Steps to reproduce

  1. Right click on the file
  2. Click on Nextcloud
  3. The menu does not show "Copy public link" for at least 1 minute after file upload is complete (even if you constantly redo the right click menu opening).

Expected behavior

The "Copy public link" appears immediately after file has been synced with the server.

Which files are affected by this bug

All new files that are synced

Operating system

Windows

Which version of the operating system you are running.

Windows 10

Package

Appimage

Nextcloud Server version

23.0.3

Is this bug present after an update or on a fresh install?

Fresh desktop client install

Are you using the Nextcloud Server Encryption module?

Encryption is Disabled

Are you using an external user-backend?

Nextcloud Server logs

No response

Additional info

It seems from the dektop client log, that the nextcloud.sync.csync.updater finds the file just about 1 minute later while communicating with server and updates metadata and then the public sharing link appears. It would be highly desireable at least for my personal workflow, that this happens faster or preferrably on demand if its known that new fles are uploaded to server. 1 minute delay is too long.

joshtrichards commented 10 months ago

This may be due to capabilities fetching latency (though I can't find the timing code at the moment to verify). It's also possible it may improved if using notify_push.