Retire built-in and aging time zone database in favor of using IANA

Open

#67 opened on Jan 6, 2018 9 comments 3 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty: 5/5
Estimated time: Over a week
Newbie friendliness: 25/100

Issue type: Feature
Clarity: Mostly clear
Activity status: Stale
Tech stack: cpp
Domain: backend

Research direction

Start by reviewing the built-in CSV file in the data directory and the time zone code that consumes it, then compare their behavior with the IANA time zone database linked in the issue. Done means the aging built-in database is retired, IANA data is used, and historical conversions honor each zone's valid time ranges.

Written by the indexing model from the issue text.

Description

enhancement

Problem

If you apply timezone to a time in the past and that timezone changed the timezone specification to behave differently after a certain point, the existing timezone database does not encapsulate the older formats. Therefore the result is wrong for times in the past where that timezone changed rules.

Solution

The IANA time zone database is the most complete database available:

https://www.iana.org/time-zones

They have data, code, or combined releases. Their time zone information contains the start and end time for each zone change - something that the built-in csv file in the data directory does not have.

Recommend retiring the built-in time zone database in favor of using the IANA database and modifying the time zone code to apply time zones based on the valid time ranges for those zones. Sounds like a fair amount of work.

Background

https://svn.boost.org/trac10/ticket/10087
https://svn.boost.org/trac10/ticket/596

Dominant language: C++
Stars: 70
Forks: 99
PR merge metrics: No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

First steps

Read the whole issue, then the project's contributing guide.
Comment on the issue to say you are picking it up — it saves two people doing the same work.
Fork the repository and make your change on a branch.
Open a pull request that references the issue number.

Similar issues

[Bug] NULL pointer dereference in llm_running_callback (NGZA-AX-LLM #3) Open

Difficulty 1/5 Under an hour Newbie friendliness 90/100

AXERA-TECH/ax-llm#77 · Opened Sep 22, 2026
resume() sends a second HTTP response (400) after a successful resume Open

Difficulty 1/5 Under an hour Newbie friendliness 90/100

games-on-whales/wolf#509 · Opened Sep 21, 2026
pn7160: reader goes permanently deaf — post-read IRQ-low check fails reads that succeeded Open

Difficulty 2/5 1-3 hours Newbie friendliness 74/100

esphome/esphome#19452 · Opened Sep 21, 2026
Eval bug: Ministral-3 tool-calls during reasoning are not processed Open

bug-unconfirmed

Difficulty 2/5 1-3 hours Newbie friendliness 76/100

ggml-org/llama.cpp#29248 · Opened Sep 21, 2026
run_tests.py fails on windows, but running tests individually works Open

Difficulty 2/5 1-3 hours Newbie friendliness 74/100

NVIDIA/cuda-samples#453 · Opened Sep 21, 2026

More C++ issues