ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
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)
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 To determine how ModX should handle regional time zones when converting stored UTC timestamps to the user’s locale. Context The core file modx/model/modx/date.php throws a generic exception when DateTime::createFromFormat receives an invalid timezone string, resulting in the PHP warning "DateTime::createFromFormat(): Failed to parse time string" . ModX
The goal is to configure Chakra UI’s DatePicker (v2) so that the value passed to onChange represents a UTC timestamp while the calendar continues to display the date according to the chosen locale (e.g., 'fr-FR'). This would eliminate the need for manual offset conversion in application code and ensure consistent date handling across users in different time
Context Sulu resolves content through a webspace → portal → localization hierarchy. When a request locale does not match any portal localization, the system silently falls back to the first localization defined in that portal’s localizations array. Problem The admin UI “Default” checkbox on a localization affects only content-editing preselection, not fronte
weblate
chakraui