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.

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

streamline prediction destination code #827

Merged
merged 1 commit into from
Oct 8, 2024

Conversation

panentheos
Copy link
Collaborator

Summary of changes

This change is in support of an larger refactor. It removes some soft error handling in destination_for_prediction, simplifying the callers. This code has been stable for a long time, and the logs show no indication that it ever fails during normal operation. Going forward, any unexpected predictions would cause this to fail loudly, which seems like a decent approach.

@panentheos panentheos requested a review from a team as a code owner October 7, 2024 18:23
Copy link
Contributor

@digitalcora digitalcora left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Let It Crash™

Just to be clear about the failure boundaries, if this were to ever crash (and it wasn't a transient condition that resolved on process restart), what would happen with signs? Would the issue be limited only to specific signs?

@panentheos
Copy link
Collaborator Author

We've tuned the supervision layer so that individual sign crashes don't bring down the entire system, they just continuously restart (with a small delay). So the impact would be limited to signs seeing unexpected data, and they would recover automatically when the data went away.

@panentheos panentheos merged commit 666eeb5 into main Oct 8, 2024
2 checks passed
@panentheos panentheos deleted the bhw/prediction-destination branch October 8, 2024 12:41
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants