You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When testing SunKit, the dumpDateInfos function includes the following:
Civil dusk -> Tuesday, May 2, 2023 at 5:31:09 AM Mountain Daylight Time
Civil Dawn -> Tuesday, May 2, 2023 at 8:21:42 PM Mountain Daylight Time
Nautical Dusk -> Tuesday, May 2, 2023 at 4:56:05 AM Mountain Daylight Time
Nautical Dawn -> Tuesday, May 2, 2023 at 8:56:46 PM Mountain Daylight Time
Astronomical Dusk -> Tuesday, May 2, 2023 at 4:18:26 AM Mountain Daylight Time
Astronomical Dawn -> Tuesday, May 2, 2023 at 9:34:25 PM Mountain Daylight Time
In each case, dawn is shown as being in the evening, while dusk is in the morning.
I thought at first that the dawn times were for tomorrow, i.e. the next time dawn arrived, but they all show the same date. Printing their UTC values shows the same issue, dusk occurs before dawn:
Hello. The solar events' names are indeed inverted: dawn happens in the morning while dusk happens in the evening. Thank you for reporting. A fix should come soon in the next release.
When testing SunKit, the
dumpDateInfos
function includes the following:In each case, dawn is shown as being in the evening, while dusk is in the morning.
I thought at first that the dawn times were for tomorrow, i.e. the next time dawn arrived, but they all show the same date. Printing their UTC values shows the same issue, dusk occurs before dawn:
I don’t know if this means dawn and dusk times are reversed or if there’s some other problem.
My
Package.resolved
shows that I’m using tag 2.6.3, so I should be up to date.The text was updated successfully, but these errors were encountered: