[Bug]: File modified in future

[jlaba]

⚠️ 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 (I've searched it).
• Nextcloud Server is up to date. See Maintenance and Release Schedule for supported versions.
• Nextcloud Server is running on 64bit capable CPU, PHP and OS.
• I agree to follow Nextcloud's Code of Conduct.

Bug description

I have uploaded a file with current iOS client. On my linux (up to date openSUSE Leap 15.4) laptop the file could not be synchronised. In nextcloud a folder a little bit higher in the hierarchy (=containing the new file in a sub folder) has a modification date in 83 years in the future. On the filesystem it has the correct datetime from 4 years ago. Nothing else has been changed in the directory.

Using occ files:scan has not solved the issue.

Any help is welcomed.

Steps to reproduce

1. Not tested, if it is reproducable

Expected behavior

Correct datetimes

Installation method

None

Nextcloud Server version

25

Operating system

Debian/Ubuntu

PHP engine version

None

Web server

Apache (supported)

Database engine version

MariaDB

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

-

Nextcloud Signing status

No response

Nextcloud Logs

No response

Additional info

No response

[Jerome-Herbinet]

Same with NC 28.0.5. I'll check again with very last 28 minor version as soon as possible.

[vpecinka]

I have the same problem. A user drags & drops a file with future datetime to the browser and it results in the whole folder hierarchy becomes future datetime and the sync clients get broken.

As seen in the screenshot, date is set to yer 2107 before drag & drop.

The file is put to a group folder and all database records up to fileid=1 have changed modification date mtime

MariaDB [central]> select fileid, from_unixtime(storage_mtime), from_unixtime(mtime), path from oc_filecache where storage = 1 order by mtime desc limit 20;
+----------+------------------------------+----------------------+----------------------------------------------------------------------+
| fileid   | from_unixtime(storage_mtime) | from_unixtime(mtime) | path                                                                 |
+----------+------------------------------+----------------------+----------------------------------------------------------------------+
| 80182785 | NULL                         | NULL                 | __groupfolders/trash/16/FP1-24-3832.d1721901745                      |
| 79945440 | NULL                         | NULL                 | __groupfolders/16/Marketing podklady/2024/06_červen                  |
| 76870586 | 2024-07-08 11:16:03          | NULL                 | __groupfolders/16/Marketing podklady/2024                            |
| 68365402 | 2024-07-08 11:16:03          | NULL                 | __groupfolders/16/Marketing podklady                                 |
| 45988828 | 2024-07-22 09:56:23          | NULL                 | __groupfolders/16                                                    |
| 22312564 | 2024-07-17 13:15:36          | NULL                 | __groupfolders                                                       |
|        1 | 2024-07-17 13:15:36          | NULL                 |  

Edit:

Nextcloud 28.0.5 (Linux amd64)
Groupfolders 16.0.6

Note:

The use that does the upload uses the group folder indirectly (it is being shared to him).

[skjnldsv]

So it's only an iOS/MacOS issue?

[vpecinka]

So it's only an iOS/MacOS issue?

Don't know. However, in my case the file is uploaded via browser and has future time before upload (so nothing changes it during upload). But the future time stored in nextcloud breaks the sync process for the other users (with other's nextcloud sync client on windows in my case).

[bricewge]

Looks like PR #49551 should fix this issue.

[vpecinka]

I'm running v29 (29.0.10, released Dec 5, 2024) and it has happened again (in a shared folder) few moments ago.

[bricewge]

@vpecinka, if I understood properly it's expected because #49551 wasn't backported in 29.0.10. Even tho it was planned initially.
Fortunately it was backported for 29.0.11in #49283, but that version hasn't been released yet. You can see the changed milestone in #49283:

@blizzz blizzz modified the milestones: Nextcloud 29.0.10, Nextcloud 29.0.11 Dec 5, 2024