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
{{ message }}
Repository navigation
Hourly slots start at :30 for hosts in UTC+3:30 / +5:30 / +5:45 (Tehran, India, Nepal, Adelaide, Newfoundland) #182
I've searched existing issues and this isn't a duplicate.
This is a reproducible bug in Calnode — not a configuration/setup question or a feature request.
What's the bug?
alignUp (internal/slots/generate.go) rounds slot starts to multiples of the interval counted from the Unix epoch, i.e. on the UTC clock. For a host whose UTC offset is not a whole number of hours, every hourly boundary lands on :30 or :45 local time. A Tehran host working 09:00–17:00 with a 60-minute interval is offered 09:30, 10:30 … 15:30 and never 09:00. Intervals that don't divide a day (50 or 35 min) also drift from one day to the next, even for UTC hosts.
Steps to reproduce
Host timezone Asia/Tehran, Monday 09:00–12:00, duration and interval 60 → /slots offers 09:30 and 10:30 (expected 09:00, 10:00, 11:00).
Activity
pullfrog commentedon Oct 28, 2026