[Bug]: Sync panel sometimes shows negative size while uploading

[anonbergine]

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

• This is a bug, not a question or a configuration issue.
• This issue is not already reported on Github (I've searched it).
• Nextcloud Server and Desktop Client are up to date. See Server Maintenance and Release Schedule and Desktop Releases for supported versions.
• I agree to follow Nextcloud's Code of Conduct

Bug description

Sometimes, while uploading, the filesize under the progress bar goes negative:

Steps to reproduce

It's intermittent. Just every so often the display shows negative bytes during a sync.

Notably, it's often on relatively small files so it's unlikely to be an bigint (I assume?) overflow.

Expected behavior

File size should never be negative.

Which files are affected by this bug

Random files.

Operating system

Windows

Which version of the operating system you are running.

windows-10.0.19045

Package

Appimage

Nextcloud Server version

Unknown but was updated by admin 2-3 days ago

Nextcloud Desktop Client version

3.7.4 (Windows)

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

Updated from a minor version (ex. 3.4.2 to 3.4.4)

Are you using the Nextcloud Server Encryption module?

Encryption is Enabled

Are you using an external user-backend?

• Default internal user-backend
• LDAP/ Active Directory
• SSO - SAML
• Other

Nextcloud Server logs

Unable to obtain.

Additional info

The bug is rare, and doesn't seem to cause any major problems.

I've noticed this bug for a while - it's cropped up several times over past 6 months. It's not caused due to a recent update, it seems to be a long-standing issue.

[LorbusChris]

Also happening on Fedora (Version 3.7.4 (Fedora))

[github-actions]

This bug report did not receive an update in the last 4 weeks. Please take a look again and update the issue with new details, otherwise the issue will be automatically closed in 2 weeks. Thank you!

[TobiGr]

The bug is still present in Nextcloud client 3.9.0 (linux) with server 26. I encountered the bug after adding many files to one of the synced folders and starting Nextcloud client afterwards:

Screenshot

[19kmunz]

Present immediately after updating to Version 3.9.1 on Windows 10. The update happened in the middle of an upload process. It will display negative values, get up to the actual update progress (right now around 450 MB), reset to -560,000,000~ B, then return again to the actual update progress with more uploaded bytes (~-560,000,000B -> ~450MB -> ~-560,000,000B -> ~500MB -> repeat until done). The starting negative value is not consistent, but is always above -250,000,000B. Ive seen as high as ~-750,000,000B.

[karthikiyengar]

Still present, 26.0.3 + client version 3.9.2 on ubuntu, no encryption.

[zachsmith]

I'm seeing this as well with Flatpak com.nextcloud.desktopclient.nextcloud version 3.9.3 on Debian 12. Server is Nextcloud Hub 5 27.0.2 (running with AIO setup)

[lorenzohess]

Still present:

$ Nextcloud-3.9.4-x86_64.AppImage --version
Nextcloud version 3.9.4 (build 17551)
Git revision c8fec0118f90f6297a7af1fec4f7b44f3e6b3821
Using Qt 5.15.10, built against Qt 5.15.10
Using Qt platform plugin 'xcb'
Using 'OpenSSL 3.0.10 1 Aug 2023'
Running on Debian GNU/Linux 11 (bullseye), x86_64

The client has many <filename>: Network error: 302 errors. It goes back and forth between upload an actual file size (i.e. >0B) and the negative file sizes.

Other errors began appearing when the next sync started:
<filename>: Server replied "500 Internal Server Error" to "PUT <dav_file_link>" (An exception occurred while executing a query: SQLSTATE[40001]: Serialization failure: 1213 Deadlock found when trying to get lock: try restarting transaction). Perhaps these new errors are related to the negative file sizes?

[msviba]

Same experience with Version 3.10.0stable-Win64 (build 20230915)

[Krinkle]

I used Nextcloud Desktop for the first time today and upon replacing a few files, I noticed this issue.

Client Version 3.10.0 (osx-22.5.0).

[nickdavies92]

I'm running the latest version and have the same issue. Everytime I try and sync a new folder, it will get majority of the way through and then keep looping as others have described above (negative b number > 0b, cycles 100 files at a time, repeats this until the max number of files in the folder has been reached, and then starts again). Restarting both the nextcloud host and nextcloud client doesn't help.

I'm going to try the Nextcloudpi image but in the past I've not had any issues running it on Buster and installing manually.
I used this guide: https://pimylifeup.com/raspberry-pi-nextcloud-server/

In this current state, nextcloud is unusable.

NextCloud Desktop Client 3.4.1
Windows-10.0.19045

[mgallien]

@nickdavies92 I recommend that you upgrade to our latest release and test again. We no longer fix bug i the 3.4 release series. In this stable branch 3.4.1 is also not the latest release and we would not backport a fix to this old version (like doing a 3.4.1.1 release)

[Morpheu5]

Can confirm the bug is present on macOS, latest clients and servers, but for me this is also part of a larger problem, as reported in #6117

[ax1036]

Same with latest versions, client use 100% for one CPU and gui freeze with all +2M files
Upload with web interface work fine and client download file without issue.

Client version:

$ ./Nextcloud-3.10.0-x86_64.AppImage --version
Nextcloud version 3.10.0 (build 17672)
Git revision ad2cf1b575e45c2adb2832f6b8642bb9f79d105b
Using Qt 5.15.10, built against Qt 5.15.10
Using Qt platform plugin 'xcb'
Using 'OpenSSL 3.0.10 1 Aug 2023'
Running on Debian GNU/Linux 12 (bookworm), x86_64

Server Version: 27.1.2 / debian 12

[ax1036]

More infos:
with head -c 2M /dev/urandom > 2m.file on my server, negative size and client freeze/crash.

but with same client 3.10.0 same generated file on drive.shadow.tech will work fine (positive size & upload done)
current server version « Nextcloud 26.0.4.3 » (from scan.nextcloud.com)

[Morpheu5]

I haven't tried an earlier version of the server but I might, at this point. If that works, it means the negative size bug and the issue I'm experiencing with the client not syncing correctly at all may be somewhere in between the client and the latest version of the server.

[Morpheu5]

I tried installing version 26 of the server and I still get the negative size bug, but at least I'm able to sync again (see #6117 )

[github-actions]

This bug report did not receive an update in the last 4 weeks. Please take a look again and update the issue with new details, otherwise the issue will be automatically closed in 2 weeks. Thank you!

[ax1036]

Some new tests with "my server" and "drive.shadow.tech" with proxying it.
Server with negative use this endpoint: "POST /remote.php/dav/bulk HTTP/1.1"
Server working fine use this one: "PUT /remote.php/dav/files/[username]/2M.file"

Question is why are differents ?

[allexzander]

Fixed in #6227