Description
When listing calendar events, gog calendar events displays times in Pacific/Asia (UTC+13) instead of the user's local timezone or the event's
configured timezone.
Steps to Reproduce
- Create a calendar event with Africa/Windhoek timezone (UTC+2):
gog calendar create primary \
--summary "Dr XXXXX Followup" \
--from "2026-04-08T09:00:00+02:00" \
--to "2026-04-08T09:20:00+02:00" \
--location "Windhoek, Namibia"
2. List events:
```bash
gog calendar events --account <email> --from 2026-04-08 --to 2026-04-09
Expected Behavior
Event should display as:
09:00–09:20 Dr XXXXX Followup
Actual Behavior
Event displays as:
20:00–20:20+13:00 Dr XXXXX Followup
Note: 09:00+02:00 and 20:00+13:00 represent the same instant, but the display timezone is incorrect.
Environment
- gog version: v0.12.0 (c18c58c 2026-03-09T05:53:14Z)
- OS: macOS Darwin 25.4.0 (arm64)
- System timezone: Africa/Windhoek (UTC+2)
- gog calendar time output:
timezone Africa/Windhoek
current_time 2026-04-07T22:22:21+02:00
Additional Context
- Event JSON from API shows correct timezone: "timeZone": "Etc/GMT-2"
- Google Calendar web UI displays correct local time (09:00)
- Only gog calendar events plain text output is wrong
- JSON output (-j) may also be affected
The issue appears to be in how gog converts and displays event times, not in how events are stored.
Workaround
Edit events directly in Google Calendar web UI, which displays times correctly, but this is counterproductive.
Description
When listing calendar events,
gog calendar eventsdisplays times in Pacific/Asia (UTC+13) instead of the user's local timezone or the event'sconfigured timezone.
Steps to Reproduce
Expected Behavior
Event should display as:
Actual Behavior
Event displays as:
Note: 09:00+02:00 and 20:00+13:00 represent the same instant, but the display timezone is incorrect.
Environment
Additional Context
The issue appears to be in how gog converts and displays event times, not in how events are stored.
Workaround
Edit events directly in Google Calendar web UI, which displays times correctly, but this is counterproductive.