ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
An Elixir application using Ecto with PostgreSQL needs to store all timestamps as UTC via :utc_datetime / timestamptz while accepting and presenting values in a per-user regional time zone. tzdata is available for Calendar.DateTime.shift_zone/3. Ecto does not perform automatic regional conversion. The documented pattern is UTC storage in the database with co
The goal is to ascertain whether MS‑DOS offers any built‑in means to interpret FAT directory timestamps as UTC or to apply a timezone offset when files are read or written across different regional settings. MS‑DOS stores file creation, modification and access times as local‑time values in FAT entries, derives those values from the BIOS real‑time clock via I
Goal Determine whether CMake's string(TIMESTAMP) can reliably produce a timezone name ( %Z ) when the underlying system lacks timezone data, and what the expected output should be in such cases. Constraints/Uncertainty The command forwards the format string to the C runtime's strftime , which may return an empty string for %Z if timezone information is unava
Goal: Ensure that helm status and helm history display timestamps in a predictable, zone‑agnostic manner so that audit logs and CI pipelines produce consistent times regardless of the client’s local time zone setting. Constraint: Helm stores each release timestamp as an RFC3339 UTC string in the release ConfigMap and converts it to the client’s local time zo
Goal I want to convert a local wall-clock time to UTC using Gleam's DateTime module, which relies on the Erlang VM's timezone database. The conversion should work for a named IANA zone such as "Europe/Berlin", including dates that fall inside a daylight-saving transition. Constraints and uncertainty The conversion API requires an explicit timezone identifier
Kibana handles temporal data by storing timestamps in UTC and typically converting them to the browser's local time zone for visualization. While the Advanced Settings provide a global timezone override to standardize the display across the instance, this setting applies universally to all users regardless of their physical location. In environments where te
Timezone Consistency Between Main and Renderer Processes Developers building Electron applications often need to format dates and times according to the user's regional settings in both the main and renderer processes. The goal is to obtain identical timezone information from Intl.DateTimeFormat in each process so that displayed timestamps remain consistent
Goal: Achieve consistent regional timestamp handling in a Cloudflare Worker so that all business logic sees times in a chosen zone while the underlying Date object remains UTC. Constraints: The Workers runtime provides only the ECMAScript Date API, which always returns UTC values and ignores any TZ environment variable; explicit zone conversion must be perfo
Unresolved naive datetime rendering in the Python debugger PyCharm's debugger displays timezone-aware datetime objects with their UTC offset, but naive datetime objects are rendered in the configured IDE time zone without any visual indicator that they lack timezone information. An open YouTrack issue debates whether naive datetimes should be assumed UTC or
ecto
msdos
helm
gleam
kibana
elasticsearch
electron
cloudflareworkers