Repository navigation
Make test worktree-safe and interpreter-hijack-proof #27
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
Merged
Merged
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
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
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,27 @@ | ||
| """Guard against the editable-install finder silently serving another | ||
| checkout's code. | ||
|
|
||
| `python -m pytest` puts this checkout first on sys.path, but the venv's | ||
| editable install (a MetaPathFinder appended by setuptools, with absolute | ||
| paths into the main checkout) catches anything that falls through — e.g. a | ||
| module deleted or renamed on a worktree branch would silently import the main | ||
| checkout's stale copy and the suite would pass against the wrong code. For a | ||
| project whose review contract is bit-exactness, that is the worst failure | ||
| mode: green and wrong. So: every repo package the tests import must resolve | ||
| under this conftest's own directory, worktree or main checkout alike. | ||
| """ | ||
| from pathlib import Path | ||
|
|
||
|
|
||
| def pytest_sessionstart(session): | ||
| import model | ||
| import tools | ||
| import vectors | ||
|
|
||
| root = Path(__file__).resolve().parent | ||
| for pkg in (model, tools, vectors): | ||
| p = Path(pkg.__file__).resolve() | ||
| assert root in p.parents, ( | ||
| f"{pkg.__name__} imported from {p}, outside the test root {root}: " | ||
| "the editable-install finder is serving another checkout's code" | ||
| ) | ||
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
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
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🎯 Functional Correctness | 🟠 Major | ⚡ Quick win
🧩 Analysis chain
🏁 Script executed:
Repository: jackthepunished/ternoise
Length of output: 1934
🌐 Web query:
site:github.com/jackthepunished/ternoise conftest.py "outside the test root"💡 Result:
I couldn’t find an indexed match for that exact query in
jackthepunished/ternoise. The closest result suggeststests/conftest.pyexists, but not the phrase “outside the test root.” (gist.github.com)Citations:
🏁 Script executed:
Repository: jackthepunished/ternoise
Length of output: 1934
Use an explicit exception for the checkout guard.
Python removes
assertstatements under-OorPYTHONOPTIMIZE. RaiseRuntimeErrorwhenroot not in p.parentsso the guard rejects stale imports in all interpreter modes.🤖 Prompt for AI Agents