Bug Report: Modification time is not kept properly for directories when copying

[batagy]

Describe the bug
I was testing the new feature "keep file & folder modification time when copying" with version v19.6.6.

Unfortunately some issue still remained. With this version, original mtime is kept for directories only if they don't contain any subdirectory. If directory contains at least one subdirectory, directory mtime will be current time after copy.

To Reproduce
Copy a folder which contains at least one subdirectory.

Expected behavior
Original mtime should be kept for all directories.

Desktop (please complete the following information):

• Version (cloudcmd -v): v19.6.6
• Node Version node -v: N/A, running from docker container
• OS (uname -a on Linux): Debian 13

{}

• 🎁 I'm ready to donate on https://opencollective.com/cloudcmd
• 🎁 I'm ready to donate on https://ko-fi.com/coderaiser
• 💪 I'm willing to work on this issue

Thanks in advance

[coderaiser]

I have no idea, before creating file or directory we preserve mtime, and then set it back https://github.com/coderaiser/redzip/blob/8649d69f6b3341383508f8c61ca04fdae8a31c1e/lib/local/date.js#L20

Maybe the problem with order of copying in copymitter: https://github.com/coderaiser/node-copymitter/blob/master/lib/copymitter.js

Here I need help

[batagy]

Ok, I'll check it later.

[coderaiser]

I figured it out, the thing is order of copying it worked from last to first, and now should be correct, please check Cloud Commander v19.6.8

[batagy]

I finished testing of v19.6.8 and glad to say that everything is perfect now. :)
Copying both files and all directories is now keeping modification time, as wanted!

I even tested on external NTFS USB disk , not only on internal EXT4 (both from Debian 13).

Thanks a lot @coderaiser , great work that I appreciate it! This feature is very useful for me.

You can close the case.