Skip to content
This repository has been archived by the owner on Feb 25, 2024. It is now read-only.

dst/leap: be more confident in announcement bits #31

Closed
rene0 opened this issue Mar 25, 2018 · 2 comments
Closed

dst/leap: be more confident in announcement bits #31

rene0 opened this issue Mar 25, 2018 · 2 comments
Assignees
@rene0
Labels
bug

Comments

@rene0
Copy link
Owner

rene0 commented Mar 25, 2018

Currently the threshold for the amount of announcement bits for DST/leap second is half the current minute value of more. This imposes a problem if the program is started after half the hour (at minute m), because in that case the number of announcements can never catch up with the minute value.
@rene0 rene0 added the bug label Mar 25, 2018
@rene0 rene0 self-assigned this Mar 25, 2018
rene0 pushed a commit that referenced this issue Mar 25, 2018
Fix registering the DST or leap second announcement in case the progr…
25d5832 
…am is started after half the hour.

Use the number of correctly received minutes in this hour instead of the
current minute value to compare the number of correctly received
announcements against.

Issue #31
@rene0
Copy link
Owner Author

rene0 commented Mar 25, 2018

TODO: write a regression test.

@rene0
Copy link
Owner Author

rene0 commented May 27, 2018

regression test is part of #3

@rene0 rene0 closed this as completed May 27, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees

@rene0 rene0

Labels
bug
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@rene0