Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Use an empty optional in the ValveScheduler to signal no schedule being set #254

Open
lptr opened this issue Dec 4, 2024 · 0 comments
Open

Use an empty optional in the ValveScheduler to signal no schedule being set #254

lptr opened this issue Dec 4, 2024 · 0 comments
Assignees
@lptr
Labels
internal Internal change no-changelog Do not mention in release notes

Comments

@lptr
Copy link
Member

lptr commented Dec 4, 2024

Currently we use nanoseconds::max() as the next change, and that's leading to printouts like:

I (31912103) farmhub: Valve 'flow-control-a' state is -1, will change after 9223372036.85 sec at -7490067033
@lptr lptr added the internal Internal change label Dec 4, 2024
@lptr lptr self-assigned this Dec 4, 2024
@lptr lptr added the no-changelog Do not mention in release notes label Dec 4, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@lptr lptr

Labels
internal Internal change no-changelog Do not mention in release notes
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@lptr