vipzhicheng/logseq-plugin-block-calendar

Calendar desyncs after 10th day of some months.

Closed this issue Β· 14 comments

win10, logseq ver 0.8.5, block calendar 0.1.5

2022-09-12.12-55-22.mp4

I have exactly the same issue using Block Calendar v 0.1.7 in Logseq 0.8.8 using both a Windows 10 pc (OS Build 19044.2006) and a MacBook Pro M1 running Monterey 12.6. Can anyone else reproduce this issue?

+1, seeing the same issue using Block Calendar v 0.1.7 in Logseq 0.8.8 using a MacBook Pro Intel, running Monterey 12.6.

has been fixed, please upgrade.

Logseq_XVNprb2edu.mp4

still broken, 0.1.11

only appears on oct, nov, dec
The 10th day behaves like 9th

Thank you for attempting to fix this issue, however I confirm what thompson-vii noted. January through September work correctly, but October, November and December are out of sync by one day starting with the 10th of the month up to the end of the month. So, for example. when I click on December 10th, December 9th is displayed; when I click on December 11th, December 10th is displayed; and so on, right up to when I click on Dec. 31, December 30th is displayed. The same is true for all days in October, November & December from the 10tth of the month through the end of the month.

As of today, February 9, 2023 using Block Calendar version 0.2.2, this issue still persists.

On Dec. 16, 2022 I wrote "Thank you for attempting to fix this issue, however I confirm what thompson-vii noted. January through September work correctly, but October, November and December are out of sync by one day starting with the 10th of the month up to the end of the month. So, for example. when I click on December 10th, December 9th is displayed; when I click on December 11th, December 10th is displayed; and so on, right up to when I click on Dec. 31, December 30th is displayed. The same is true for all days in October, November & December from the 10tth of the month through the end of the month."

I thought I had fixed this issue, but seems still have issues.

I can not reproduce this issue on my local, so please run the code below in your computer browser console to see which timezone you are in.

Intl.DateTimeFormat().resolvedOptions().timeZone

v0.2.3 is a small fix, but I don't know if it works, please have a test.

Please try again. Because I can not reproduce it on my local. I have no idea what is wrong. So I can only try to fix it by guessing. 😭