Incorrect timezone offset when using `Etc/` timezones about crab.fit HOT 13 CLOSED

Disclaimer: I am not part of the developing team, just a user of crab.fit that wants it to work properly and be a true alternative to when2meet.

Crab.fit relies on the dayjs library for this functionality. Maybe you should have a look if the library is responsible for the behaviour you describe. And maybe the library should be updated if the issue has been corrected there.

Etc/GMT+2 is actually -02 according to the IANA database. That does not explain all the issue, but maybe some timezones do not match what their names indicate.

from crab.fit.

Thanks @robin-francois, and @astrojuanlu for reporting this. Sorry I've been focusing on work projects lately and haven't had the time I'd like to work on Crab Fit.
I'll look into dayjs, it's possible I simply need to update to a newer version. The list of timezones I'm using may also not be fully supported by dayjs.

from crab.fit.

Did a quick test, and it worked with Europe/Madrid and America/Buenos Aires, Europe/Amsterdam, Europe/London 👍🏽 Updating the issue title

from crab.fit.

There are several tickets open on the dayjs repository about timezone issues, more precisely around UTC/GMT:
iamkun/dayjs#1843
iamkun/dayjs#1606

Issues could be upstream.

from crab.fit.

Thanks @robin-francois. I've updated all dependencies in Crab Fit including day.js, however if these issues exist in that library this is likely an issue we'll have to wait for them to resolve. In the meantime, I'd suggest using city-specific timezones, e.g. here in Australia I use Australia/Sydney rather than Etc/GMT+10. Just be wary of daylight savings.

I have looked into other date/time libraries for JavaScript, however day.js is still the best option based on package size and functionality. I'll leave this issue open for now, hopefully these issues can be fixed in the day.js code.

from crab.fit.

Thanks for that. I hope @astrojuanlu can still enjoy using crab.fit despite some timezone oddities due to upstream libraries (and confusing timezone names).

from crab.fit.

Hi @robin-francois, thanks for staying on top of this. Unfortunately this is quite critical so for now I'm left with no alternative other than when2meet. It's unfortunate that dayjs has not solved these issues but the end result is that crab.fit is not usable.

from crab.fit.

Have you tried not using Etc/* timezones? As I said, those seem to be misleading by design.

from crab.fit.