Fail closed on unknown Kokoro TTS runtime hashes - #46
Closed
Blackspirits wants to merge 2 commits into
Closed
Blackspirits wants to merge 2 commits into
Blackspirits wants to merge 2 commits into
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
1 participant
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.
Superseded by internal PR #55, which carries the Kokoro TTS fail-closed runtime hardening on current upstream base
9be10e12d0f04655f2f134718b00679f89b2b15f, adds explicit null-key/empty-stream coverage, reconfirms all four current v0.1.2 release digests, and passes restore/build/full-suite CI on the first run (#34705356330). This draft is retained only as historical evidence and must not be merged.