ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
When generating static sites with Eleventy, converting regional date-time strings into UTC timestamps often encounters edge cases during Daylight Saving Time (DST) transitions. Specifically, when a local time is repeated (an overlap) or skipped (a gap), the resulting Instant becomes ambiguous. While Eleventy typically relies on JavaScript Date objects or lib
Jule convertToZone: Unclear handling of ambiguous DST times Goal: determine how the Jule library resolves local times that occur twice during a daylight‑saving time (DST) transition, such as 2023‑11‑05 01:30:00 in America/New_York. Constraint: The convertToZone(Date, String) API returns a ZonedDateTime but lacks documentation on which offset is chosen when t
Problem I'm using Maya 0.6.1 to parse local datetimes in a US/Eastern context and convert them across zones. According to the documented behavior, a naive string parsed with timezone='US/Eastern' that falls in the DST fallback window (e.g., 2023-11-05 01:30) resolves to the first occurrence (EDT) with no warning, and spring-forward gaps raise NonExistentTime
Goal Ensure that audit log timestamps and time‑based role expressions are displayed and evaluated with correct daylight‑saving adjustments for any regional time zone chosen by administrators or users. Uncertainty Teleport stores all event timestamps in UTC and converts them for display using either the IANA time‑zone database bundled with the binary or the h
Goal: diagnose which instant Vala selects when converting an offset-less local wall-clock timestamp to UTC through GLib.DateTime during a DST fall-back overlap, where one local time can map to two UTC instants. Constraint: Vala relies on the host system's tzdata via GLib.TimeZone and does not expose an explicit disambiguation parameter in the standard DateTi
Developers must convert regional local times to UTC for Twilio message scheduling and TaskRouter worker availability. Twilio's send_at parameter requires an ISO 8601 UTC timestamp and TaskRouter worker timezone strings must be valid IANA zones; during DST fallback the same local time occurs twice, requiring a decision on which offset to apply. Which UTC offs
The goal is to choose a timestamp representation that lets a CouchDB view return the correct set of documents for a user‑specified local‑time range, even when that range spans an ambiguous hour during a daylight‑saving transition. CouchDB stores timestamps as JSON strings; map/reduce views run SpiderMonkey JavaScript, where new Date() parses ISO 8601 strings
When converting Unix epoch timestamps to regional wall-clock times, Time::Piece delegates localtime to the underlying C library and the process TZ environment variable, making output dependent on the host operating system's time zone database. Time::TimeZone offers explicit regional offset lookups that do not rely on the OS locale, but combining the two appr
A scheduling dashboard stores every timestamp in UTC but must render each one in a per-user IANA zone such as America/New_York or Asia/Tokyo, without mutating the stored instant. Two documented paths Intl.DateTimeFormat (ECMA-402) takes a timeZone option: it formats an existing Date in a named zone and leaves the underlying epoch untouched. The alternative i
eleventy
jule
twilio
perl