fix(selur-compose): recover poisoned mock locks - #211
Merged
Conversation
Contributor
Up to standards ✅🟢 Issues
|
| Metric | Results |
|---|---|
| Duplication | 0 |
AI Reviewer: first review requested successfully. AI can make mistakes. Always validate suggestions.
TIP This summary will be updated as you push new changes.
27 tasks
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.
Outcome
Closes the one still-reproducible high/error Hypatia source finding from Burble’s stale alert set:
Mutex::lock().unwrap()in the selur-compose test driver with a typed helper that recovers poisoned fixture state#comments in two Rust modules; these made the selur-compose workspace fail to parse before tests could runThe old SSL-verification and unsafe-term findings are already fixed on current
main; their referenced source path is gone or usesbinary_to_term(..., [:safe]). The neural-state@bitCastoperations are intentional fixed-width float/integer serialization, not pointer reinterpretation. The credential findings are documentation/module-name false positives rather than embedded values.Verification
cargo test --manifest-path tools/selur-compose/Cargo.toml -p selur-compose-driver: 46/46 unit tests passedgit diff --check: pass