ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
Goal Determine how MATLAB's datetime class resolves ambiguous local times during fall-back DST transitions and how the version of the bundled IANA time zone database affects this behavior across different releases. Constraints and Uncertainty Since R2020b, the AmbiguousTime parameter allows selecting 'first', 'last', or 'error', but the default behavior sile
When converting a timestamp from one regional time zone to another using norg’s date‑conversion utilities, the library must decide how to represent a local time that occurs twice during a daylight‑saving‑time fallback (e.g., 01:30 on the day the clock rolls back). The current documentation does not specify whether norg automatically picks the earlier or late
Date Formatting and Time Zones The datetime2 package offers locale‑aware formatting through language‑specific files, yet it treats dates as static values. It can display a time‑zone name via \timezone , but it does not perform numeric UTC‑to‑local conversion or keep a time‑zone database. Consequently, the package lacks any built‑in logic for daylight‑saving
Goal Allow each user to select a preferred timezone so that timestamps shown in the Jetstream interface reflect their local time rather than a single application‑wide setting. Uncertainty Jetstream’s default profile update form does not include a timezone field, leaving developers to decide whether to add a manual dropdown, rely on browser‑detected timezone
Integration boundary SonarQube persists all timestamps as UTC in the database and returns ISO 8601 UTC strings from its REST API, while the web UI performs client-side conversion to the browser's local time zone. Scheduled tasks such as project analysis and housekeeping execute according to the JVM default time zone, and server-side report exports (PDF, CSV)
Goal: Establish a consistent policy for how DateTime::TimeZone resolves ambiguous local times that occur during daylight‑saving‑time fallback when no explicit disambiguation is supplied. Constraints: The module currently leaves the interpretation to the caller, which can lead to different results across systems or when using outdated tzdata. Additionally, Da
Problem Overview Vitest uses the Node.js Date implementation, which follows the process.env.TZ setting. When tests involve date‑manipulation libraries such as date‑fns‑tz , the output can vary between a developer’s machine and CI runners that have different default time zones. Current Constraints Vitest provides no built‑in helper to override or mock the sys
Date value cannot be parsed: expected ISO 8601 format with time zone offset – CSV import in Jira Align Goal: successfully import PI planning dates from a CSV file that may contain dates expressed in local wall‑clock time without an explicit time‑zone offset, while preserving correct UTC storage and UI display according to each user’s profile time zone. Const
Problem Statement SPSS stores datetime values as seconds since 1582‑10‑14 without any timezone information. Built‑in functions assume the value represents local wall‑clock time, and no automatic daylight saving time (DST) adjustments are applied. When importing timestamps from sources with explicit time zones (e.g., PostgreSQL TIMESTAMPTZ) the resulting SPSS
norg
laraveljetstream
nodejs
jiraalign