ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
Date/time handling in ShotGrid API ShotGrid stores all timestamp fields internally in UTC and the REST API returns ISO 8601 strings without any explicit timezone offset. The web UI automatically converts these values to the user’s local time zone based on browser or profile settings. This design leaves a gap for client applications: they must assume UTC and
Goal Convert a civil date-time to a UTC instant in Ballerina using an explicit IANA time-zone identifier, while preserving the intended wall-clock meaning across daylight-saving-time transitions. Constraints and uncertainty Ballerina separates UTC instants from civil date-times and requires a named zone such as America/New_York . A local time inside a spring
In GNU awk, the strftime() function formats epoch seconds into date strings based on the TZ environment variable. While mktime() generates a timestamp from date components, the resulting output shifts automatically according to the system's local time zone unless explicitly overridden. This behavior creates challenges when scripts must maintain consistent UT
Choosing a Time‑Zone Policy for Notebook Metadata The nbformat specification (v4) requires the created and last_modified fields to be ISO 8601 strings ending with a trailing Z , implying UTC. However, JupyterLab’s UI automatically converts these values to the user’s local time, and many collaborators would prefer to preserve the author’s local context in the
Goal Determine how Ghost’s scheduler maps a user‑entered publish time to the UTC timestamp stored in the database when the site’s timezone setting is configured. Current Constraints Ghost records all timestamps in UTC, and the timezone key only affects front‑end formatting via moment‑timezone. The scheduler, executed by a background worker, treats the time e
shotgrid
ballerina
awk
jupyter
ghost