Aurora Lahtela

Could you send new screenshots

I was not able to reproduce the issue because my computer is using GMT+3 as timezone, and the issue was likely caused by FullCalendar using 'local' instead of 'UTC' as...

Still happening it seems.

Caught this in a test by accident by running test at 21:01GMT+3 > MySQLTest#sqlParsingSanityCheck() > SELECT DATE(FROM_UNIXTIME(1625259676)) as date > > expected: but was: > Expected :2021-07-02 > Actual :2021-07-03

Host machine timezone is used even when the session timezone set is attempted ``` hikariConfig.addDataSourceProperty("connectionInitSql", "set time_zone = '+00:00'"); ``` Reproduced the issue again similar to previous comment > MySQLTest#sqlParsingSanityCheck()...

Reverting commit 396b51873cbcc2103039bb986a5ab53c44c8e703 (Related issue #1482) fixes tests. It appears the timezone is not set by the hikaricp property, it might be ignored entirely. Hopefully that resolves this issue.

Still occurs when using SQLite (MySQL should be fixed)

It should be a bit easier to get a forge version now that Plan has been ported to fabric since some of the code can be reused. This is still...

You can use this build until it's fixed https://github.com/plan-player-analytics/Plan/actions/runs/2668170724

This plugin requires purchase in order to use the API (Their API is not distributed and compiling has been made difficult)