Skip to content
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

BUG: Unknown or bad timezone Australia/ACT #342

Open
kevinpapst opened this issue Aug 5, 2024 · 2 comments · May be fixed by #343
Open

BUG: Unknown or bad timezone Australia/ACT #342

kevinpapst opened this issue Aug 5, 2024 · 2 comments · May be fixed by #343
Labels
Milestone

Comments

@kevinpapst
Copy link

kevinpapst commented Aug 5, 2024

Hi and thanks for Yasumi!

I ran into an issue: the used timezone Australia/ACT is not an official timezone in PHP, at least in the latest timezone database version 2024.1:

Log entry:

CRITICAL: Uncaught PHP Exception DateInvalidTimeZoneException: "DateTimeZone::__construct(): Unknown or bad timezone (Australia/ACT)" at DateTimeZoneFactory.php line 31 {"exception":"[object] (DateInvalidTimeZoneException(code: 0): DateTimeZone::__construct(): Unknown or bad timezone (Australia/ACT) at /var/www/kimai/vendor/azuyalabs/yasumi/src/Yasumi/Provider/DateTimeZoneFactory.php:31)"} []

It happened with PHP 8.3.6.

This comes from the AustralianCapitalTerritory.

@kevinpapst kevinpapst changed the title Unknown or bad timezone: Australia/ACT BUG: Unknown or bad timezone Australia/ACT Aug 5, 2024
@kevinpapst
Copy link
Author

BTW: The same issue exists for Europe/Kyiv (new) vs Europe/Kiev (old).

Is there a way to dynamically change the timezone?

@stelgenhof
Copy link
Member

Hi @kevinpapst Thank you very much for reporting this. I may not have much time this week, but will have a look at it next week.

@stelgenhof stelgenhof added the bug label Oct 21, 2024
@stelgenhof stelgenhof added this to the v2.8.0 milestone Oct 21, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants