[Bug]: php-opencloud bug corrupts large file with Swift storage, patch recommended

[vpecinka]

⚠️ This issue respects the following points: ⚠️

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

Bug description

I have reported this bug in php-opencloud

php-opencloud/openstack#365

As there can be significant delay until it gets to mainstream, I suggest to provide local patch in nextcloud code base to resolve this issue.

Steps to reproduce

Upload any large object to the storage (the default SEGMENT SIZE is 1 GB, so the file has to be more than 10 GB).

Expected behavior

segments should have name 00001, 00002, 00003 and so on to be correctly reconstructed.

Installation method

Community Manual installation with Archive

Nextcloud Server version

27

Operating system

Debian/Ubuntu

PHP engine version

PHP 8.2

Web server

Nginx

Database engine version

MySQL

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

None

Are you using the Nextcloud Server Encryption module?

None

What user-backends are you using?

• Default user-backend (database)
• LDAP/ Active Directory
• SSO - SAML
• Other

Configuration report

No response

List of activated Apps

No response

Nextcloud Signing status

No response

Nextcloud Logs

No response

Additional info

No response

[kesselb]

Good finding, sounds reasonable 👍

Would you mind submitting a pull request to the upstream project?

[vpecinka]

no problem, php-opencloud/openstack#366

[vpecinka]

Upstream PR merged

[joshtrichards]

Released in php-opencloud v3.3.0:

https://github.com/php-opencloud/openstack/releases/tag/v3.3.0