Repository navigation
Update warp_parser.py - #164
Open
MaddipatlaChetan24 wants to merge 1 commit into
Open
MaddipatlaChetan24 wants to merge 1 commit into
MaddipatlaChetan24 wants to merge 1 commit into
Conversation
This branch has not been deployed
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.
Related issue: N/A
What changed?
WarpParser.init and parse_all() now guard Path.exists() calls against OSError. Previously an inaccessible candidate path (e.g. the sandboxed macOS Group Container entry in DB_PATHS) could raise PermissionError uncaught, crashing parser construction or the entire parse_all() run.
Why?
ClineParser in this same codebase already handles this exact case (per-candidate try/except OSError), but WarpParser didn’t, leaving an inconsistent and unguarded failure path for a realistic scenario (restricted sandbox container access).
What type of PR is this? (check all applicable)
How did you test it?
py_compile for syntax validation; manually traced both call sites to confirm the new try/except blocks catch OSError and fall back to record_diagnostic/default path instead of propagating.
Potential risks
Low — the change only adds exception handling around existing exists() checks; no change to SQL, parsing, or data-extraction logic.