Fix "cannot detect diffs" error#12126
Conversation
|
I'm starting a first review of this pull request. You can view the conversation on Warp. I completed the review and no human review was requested for this pull request. Comment Powered by Oz |
There was a problem hiding this comment.
Overview
This PR introduces an explicit Detecting internal state for the local diff model, maps that in-progress state to DiffState::Loading, and only emits NotInRepository after repository detection definitively fails.
Concerns
- No blocking correctness, security, or spec-drift concerns found in the changed lines.
- The PR description includes a Loom recording, satisfying the repo visual-evidence requirement for this user-facing behavior.
Verdict
Found: 0 critical, 0 important, 0 suggestions
Approve
Comment /oz-review on this pull request to retrigger a review (up to 3 times on the same pull request).
Powered by Oz
kevinchevalier
left a comment
There was a problem hiding this comment.
Nice! This makes the state clear!
Description
DiffState::NotInRepositoryon creation which the view maps to this error messageNotInRepositoryas a loading state ifrepo_path.is_some(), but with the refactors made to support a remote diff state model, the semantics forNotInRepositorychanged to be a valid error where the path was definitively not inside a git repoDiffState::Detectingexplicitly means that we're actively detecting the repo before loading the diffsLinked Issue
Reported in:
Testing
https://www.loom.com/share/7bab61e0fe624f4d8a5cdfc440e28258
./script/runAgent Mode