ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
Decision context Weblate stores all timestamps in UTC and renders UI dates using the server‑wide TIME_ZONE setting. There is no per‑user time‑zone field in the user profile, and only a few JavaScript components perform browser‑local conversion for relative times. Trade‑off Single server zone – simple, consistent across logs, deadlines, and API responses; req
Goal Develop a COBOL program that reliably converts a DATE‑TZ value from one region to another, accounting for daylight‑saving time (DST) boundaries. Constraints and Uncertainty The ISO/IEC 2022/2023 specifications introduce a DATE‑TZ data type, but the standard explicitly leaves zone rules, DST handling, and leap‑second support to the implementation. IBM En
I am building a web app that receives date-time strings from a backend and must display them converted to each user's regional time zone. The app needs to work reliably in Safari as well as Chrome and Firefox. My understanding is that Safari's Date parser is stricter than other engines. Strings like 2024-01-15 10:30:00 (space separator instead of the ISO T )
Vagrant relies on provider-specific mechanisms to synchronize the guest clock with the host system. While the VirtualBox provider manages clock drift and synchronization by default, the actual system timezone and regional date formats are typically handled via guest OS locale settings during the provisioning phase. There is a potential conflict when using sh
Goal: Obtain the same instant‑to‑zone conversion result when a DateTime value with Kind.Unspecified is passed to TimeZoneInfo.ConvertTime on both Windows and Linux. Constraint: The current implementation treats Unspecified as the local time zone of the process, which can produce different offsets if the value actually represents UTC, especially in cloud‑nati
Laravel's Eloquent date casts serialize attributes to naive Y-m-d H:i:s strings by default, while config('app.timezone') supplies a single application-level default zone for Carbon instances. When that default zone is changed after rows have already been stored, existing database values are not automatically converted; instead, they are reinterpreted in the
Goal I need deterministic tests for date formatting that uses Intl.DateTimeFormat with an explicit timeZone option (for example America/New_York ). The plan is to freeze the clock with jest.useFakeTimers() and jest.setSystemTime(new Date('2026-10-12T00:00:00Z')) so assertions on formatted output are stable. Constraints and uncertainty Two issues are unclear.
Goal: Determine whether tmux should automatically re‑evaluate the TZ environment variable on each status‑interval tick so that the status line reflects zone changes without restarting the server. Currently tmux reads TZ once when the server starts and uses that value for all subsequent strftime calls; the update‑environment option only propagates TZ to newly
Perl's core Time::Piece and Time::Local modules rely on the underlying system C library for timezone offsets. When managing regional time conversions, the TZ environment variable is typically used to define the process-level timezone context for localtime() calls. A design challenge arises when a single process must handle multiple regional time zones dynami
weblate
laravel
jest
tmux
perl