date: fix -u flag to match GNU behavior for input parsing #10715
+122
−44
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There are a few test cases in the date GNU test and an issue that was made about the behavior that in many use cases the -u flag is not used and the behavior of the date implementation was not matching the GNU implementation when the date is passed as stdin and when when combinations of the -u and -d were used.
The main summary of the change is that parse_date takes in Zoned now which uses the same logic for every location where a date is parsed and it will use the -u flag if it is applied. There were also issues with the logic for parsing the timezone where: "Try to parse the date with UTC first to get timestamp" was used and this causes the uutils implementation to provide the incorrect date.
Fixes: #9018