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

Check fountain processing schedule #198

Closed
mmmatthew opened this issue Apr 29, 2019 · 3 comments
Closed

Check fountain processing schedule #198

mmmatthew opened this issue Apr 29, 2019 · 3 comments
Assignees
@mmmatthew
Labels
Verified The closed issue was verified by a second party and can be archived
Milestone
Out of Beta

Comments

@mmmatthew
Copy link
Member

Sometimes there might be interruptions in the fountain processing schedule, which should take place on a 2-hour basis. Issue raised by @ralfhauser.

A logging system for fountain processing would help identify when the error occurs.
@ralfhauser ralfhauser mentioned this issue Apr 29, 2019
Closed
@ralfhauser ralfhauser added this to the Out of Beta milestone May 8, 2019
@mmmatthew mmmatthew added the 4 - In Review ready to submit a PR for review. label May 9, 2019
@mmmatthew
Copy link
Member Author

If this is actually covered by #188, then we can close this issue.

@mmmatthew
Copy link
Member Author

closed by accident

@mmmatthew mmmatthew reopened this May 9, 2019
@mmmatthew mmmatthew self-assigned this May 17, 2019
@mmmatthew
Copy link
Member Author

We now have web logging thanks to water-fountains/datablue#28

@ralfhauser ralfhauser removed the 4 - In Review ready to submit a PR for review. label May 25, 2019
@mmmatthew mmmatthew added the Verified The closed issue was verified by a second party and can be archived label May 25, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@mmmatthew mmmatthew

Labels
Verified The closed issue was verified by a second party and can be archived
Projects
None yet
Milestone
Out of Beta
Development

No branches or pull requests
2 participants
@ralfhauser @mmmatthew