Repository navigation
fix: reload changed models and validate runtime health reports - #6
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Predictions now reload a replaced model artifact without restarting the worker, while unchanged artifacts are deserialized only once. Deleted or corrupt replacements return 503 instead of serving the cached model. The cache includes path, inode, size and nanosecond timestamps; deploy models with atomic replacement.
Readiness and /health now share validation of the required top-level report fields, score bounds and status. Empty/incomplete reports and malformed types return 503; existing optional report fields are preserved.
Fixes #2
Fixes #3
Validation: 236 tests passed on Python 3.12; scoped Ruff and git diff --check passed. Four reload regressions and 32 health-schema cases failed before their corresponding changes. The health check validates the top-level contract, not every nested report value. AI-assisted implementation and validation.