Skip to content

Conversation

@ndossche
Copy link
Member

@ndossche ndossche commented Mar 3, 2023

Fixes GH-10766

Due to an incorrect check, the datetime was never actually set. To test this we need to write the file using phar, but read the file using a different method to not get a cached, or a value that's been transformed twice and is therefore accidentally correct.

…not keep files metadata (datetime)

Due to an incorrect check, the datetime was never actually set.
To test this we need to write the file using phar, but read the file
using a different method to not get a cached, or a value that's been
transformed twice and is therefore accidentally correct.
Copy link
Member

@devnexen devnexen left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM, I leave the honour to follow through if you prefer when you can.

@ndossche
Copy link
Member Author

ndossche commented Mar 4, 2023

Thank you for your review. :)
I'll merge it when I can. It sounds like I'll have to wait a bit until I get the permissions on GitHub as well, or until my email is ready.

@ndossche ndossche closed this in e633be3 Mar 4, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants