fix: version-control init race condition + missing pydantic Field import - #2
Open
MikyJ05 wants to merge 2 commits into
Open
fix: version-control init race condition + missing pydantic Field import#2MikyJ05 wants to merge 2 commits into
MikyJ05 wants to merge 2 commits into
Conversation
… init Multiple components initialize version control on mount; share a single in-flight init promise per project and recover gracefully if a concurrent init already created the main branch. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Ekaanth
self-requested a review
July 15, 2026 08:54
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
2 participants
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.
Two small bug fixes:
1.
fix(web): prevent duplicatemainbranch on concurrent version-control initMultiple components call
VersionManager.initialize()on mount. When two calls raced, both could try to create themainbranch, causing a failure on the unique by-name index. This change shares a single in-flight init promise per project and, as a safety net, recovers gracefully if a concurrent init already createdmain(reuses the existing branch instead of throwing).2.
fix(ai-backend): add missingFieldimport inengagement.pyapp/routes/engagement.pyusesField(...)in several request/response models (e.g.image_urls: list[str] = Field(..., min_length=1, max_length=10)) but only importedBaseModelfrom pydantic, so importing the module raisesNameError: name 'Field' is not definedand the engagement routes fail to load.Both verified locally on Windows: web app boots clean (Next.js 16.1.3) and the AI backend starts with all routes registered and
/healthresponding.🤖 Generated with Claude Code