Repository navigation
fix: own source-test fixture recovery scope - #21
Merged
Merged
Conversation
Source validation runs tests below the Go runner. Own fixture containers in that test process so the inherited CLI grandparent identity is never treated as valid ownership.
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.
Fix at the owner
Actual source validation inherits a recovery marker owned by the CLI grandparent. TestMain now establishes ownership in the process that creates the fixture containers. Production checks and storage lifecycle are unchanged.
Verification
Published Go v0.0.55 through codefly test source: 28 passed of 28; asserting Init status exposed the actual ownership error before the nil-configuration symptom. Build and vet pass. No existing user databases or shared services were restarted or cleaned.
Refs codefly-dev/core#622.