-
Notifications
You must be signed in to change notification settings - Fork 0
Fail fast at startup when git binary predates GIT_NO_LAZY_FETCH (2.45) #77
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
Open
0lut
wants to merge
4
commits into
main
Choose a base branch
from
devin/1781084980-git-min-version-check
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Changes from 1 commit
Commits
Show all changes
4 commits
Select commit
Hold shift + click to select a range
d2d6b33
Fail fast at startup when git binary predates GIT_NO_LAZY_FETCH (2.45)
devin-ai-integration[bot] 1c8bf81
Merge origin/main into git-min-version-check; apply version gate in a…
devin-ai-integration[bot] f3fc430
Merge origin/main; move parse_git_version tests into extracted tests …
devin-ai-integration[bot] 511f296
Apply rustfmt
devin-ai-integration[bot] 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
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.
🚩 Version check only applies to the async initialization path
The
ensure_supported_binary_version()call is added only toapp_result_async(crates/git-cache-api/src/lib.rs:51), which is the production entry point used inmain.rs:16. The syncapp_resultandappfunctions—used by all integration tests (e.g.tests/correctness.rs:61,tests/git_protocol.rs:62)—do not perform the check. This is likely intentional: tests run with whatever git the CI provides and the sync path can't easily call async code. However,app_resultis a public API, so any external consumer using the sync path would silently skip the version gate. Worth confirming this is the desired contract.Was this helpful? React with 👍 or 👎 to provide feedback.
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.
Intentional: the gate targets the server startup path (
main→app_result_async) so a misbuilt runtime image fails at boot rather than with request-time 400s. The syncapp_result/appconstructors stay check-free on purpose — they're used by tests that must run against whatever git the host provides, and a blocking subprocess call doesn't fit the sync path. Callers on the sync path can still invokeGit::ensure_supported_binary_version()themselves if they want the gate.