Add diagnostic warning when source database is overwritten#16
Closed
Add diagnostic warning when source database is overwritten#16
Conversation
…init When initializeTargetDatabase is called on a file that was previously marked as a source, log a warning. This should never happen during normal builds — it indicates a source file is being incorrectly treated as a build target, which corrupts the database and leads to permanent "No rule to build" errors. This diagnostic will help identify the root cause of source database corruption that some users have reported after branch switches. Co-Authored-By: Claude Opus 4.6 (1M context) <[email protected]>
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
1 participant
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.
Summary
initializeTargetDatabasewhen it's about to overwrite a database that has a source marker (yentry)..dofile path, which will identify exactly which build rule is causing the corruption.Context
Users have reported intermittent "No rule to build" errors for source files after branch switches. We've narrowed the corruption to source files losing their source marker in the redo database, but haven't identified the exact trigger for always-existing files. This diagnostic will fire the moment the corruption happens, revealing the code path responsible.
Test plan
newsourcecorner case test (which deliberately converts source → target)🤖 Generated with Claude Code