Error "corrupted on transfer" is not corrupt - SHA1 case mismatch?

[valahna]

I love what you are building here! @hwittenborn :100: :+1: :1st_place_medal: :smile: :trophy:

I have seen this with both Nextcloud and Proton Drive configured:

"X errors found. Directory has finished sync checks. Please resolve the reported syncing issues." which then further shows: "corrupted on transfer: sha1 hash differ "SHA1 HASH" vs "sha1 hash" for a number of files. The files are not corrupt, everything is fine. It appears that the case mismatch is cause for the error?

[hwittenborn]

Thanks for the kind words @valahna! It looks like you're correct in that the hashes only differ by capitalization, so it definitely shouldn't be causing any issues.

I haven't ever experienced that on my machines though - the place that the error would be happening at is solely inside of librclone, which Celeste wouldn't have much control over. I'm suspecting it's due to a bug inside of that library, though I'm not positive.

How are you running Celeste (Flatpak, Snap, etc)?

[valahna]

I am running it via Flatpak

[hwittenborn]

Hey @valahna were you getting this issue with Nextcloud as well, or just your Proton Drive? If it's just Proton Drive, it looks like it might be the same issue as https://github.com/rclone/rclone/issues/7345.

[valahna]

Yes, only on Proton Drive - That seems to be it precisely! :D

[cytopia]

I can confirm that this happens to me as well on Proton Drive.

[felschr]

Same issue here on NixOS with Proton Drive.