fix(date): support timezone abbreviations in date --set` #8944
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.
Fixes #1882 - a 4-year-old issue where
date --set
failed with timezone abbreviations like AWST, EST, PST.The Problem:
Three tests were marked "expected to fail" since 2021 because the underlying parser couldn't handle timezone abbreviations that GNU date supports.
The Solution:
Instead of hardcoding hundreds of timezones, I built a smart resolution system:
OnceLock
for zero startup costThis means
date --set "Sat 20 Mar 2021 14:53:01 AWST"
finally works! The implementation actually goes beyond GNU by supporting additional abbreviations like Australian timezones.