Fix ACML information and timezone problem for VLDB - #1554
Merged
Conversation
PT (US Pacific Time) is UTC-7 during daylight saving and UTC-8 otherwise, so a single fixed offset cannot represent it. This was wrong for VLDB, whose rolling deadlines span April through March and cross the DST boundary — winter deadlines were off by one hour under the fixed UTC-7. Resolve the offset per deadline date: PT picks UTC-7/UTC-8 based on whether the date falls within US DST (2nd Sunday of March to 1st Sunday of November). All other timezones keep their existing fixed offsets, verified byte-identical across every value used in the dataset. - showtable.rs: add is_us_dst/resolve_tz_offset; parse_deadline_to_rfc3339 now resolves the offset from the deadline date - schema + README: add PT - vldb.yml: switch to PT
Contributor
|
Welcome to ccf-deadlines! |
jacklightChen
approved these changes
Jun 7, 2026
Contributor
|
Great job! |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Closes #1553 Closes #1449
1 Update ACML 2026 Information
Update the deadline and time zone.
2 Support PT (Pacific Time) timezone
Problem
PT is UTC-7 during daylight saving (2nd Sunday of March → 1st Sunday of November) and UTC-8 otherwise. A single fixed offset can't express this. VLDB's rolling submission deadlines run April→March, straddling the DST boundary — so the previous
timezone: UTC-7made every winter deadline (Nov–Mar) wrong by one hour.Change
PTas a supported timezone. Its offset is resolved per deadline date using the US daylight-saving rules, instead of from the static offset map.parse_deadline_to_rfc3339now takes the raw timezone label and resolves the offset internally, so each deadline/abstract deadline is computed against its own date.vldb.ymltoPT.Compatibility
All other timezones (
UTC±N,AoE,UTC) are untouched. I verified the new resolution path produces byte-identical offsets to the old code for all 18 distinct timezone values currently in the dataset, and that the RFC-3339 formatting and current-deadline selection logic are unchanged. The one behavioral difference is defensive: an unmapped timezone now skips gracefully instead of panicking.Testing
cargo buildpassesvldb.ymlvalidates against the updated schema