feat: add repo-log error logging context and settle handling - #126
Open
Amar07Singh wants to merge 3 commits into
Open
Amar07Singh wants to merge 3 commits into
Amar07Singh wants to merge 3 commits into
Conversation
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.
What changed
ingestreason/category/detail, and HTTP timeout/status hints.logs/repos/<label>.log(moved tologs/archive/once the job settles) plus a server-log reset on each successful index.Why
Index errors were hard to trace: the shared server log grew unbounded and interleaved every repo, and CLI errors hid the real cause (Neo4j auth, Mongo down, OpenRouter 402/503). These changes make each failure self-explanatory and each repo's run independently readable.
How to test
bytebell index <github-url>twice — confirm a freshrepos/<label>.logappears while indexing and moves toarchive/<label>.logwhen it finishes (success or retries exhausted).Screenshots
N/A — backend + CLI only.