-
Notifications
You must be signed in to change notification settings - Fork 49
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
you cannot check the time of the north pole #288
Comments
This isn't a bug. Antarctica/South_Pole exists and is UTC +12 or +13 depending on daylight saving time, per the zoneinfo database. The North Pole does not have permanent settlement or an assigned timezone, and therefore does not have a standardized time. See https://en.wikipedia.org/wiki/North_Pole#Time for more info. |
bitbot's location settings seem to disagree
|
this is a problem of the reverse geocoding API we use and the timezone library we use disagreeing and im not excited about trying to explicitly exclude known-to-be-invalid timezones, but guess I'll have to |
More specifically, it's the geocoding API spitting out GMT offsets for locations like the North Pole that don't have a zoneinfo timezone assigned to them. If anything, the bug here is that GMT offsets are shown and stored in location config, I could see it making sense to check for and null those, but it's more of an implementation detail than anything else. |
this should adequately destroy this inconsistency 8cc47a9 |
expected behavior
BitBot will tell you the time of the location
observed behavior
BitBot will not respond when you check the time of the north pole.
this bug was found by @kiedtl a few weeks ago, but it seems he was too busy to file an issue
The text was updated successfully, but these errors were encountered: