Repository navigation
Conversation
|
🚨 Contributor flagged. Click here for more info: Superagent Dashboard |
Member
|
hey @greptileai, please re-review the PR |
Member
|
Thanks so much for this contribution, @Alx8g! Cap's desktop app has now fully moved from Tauri to our new native GPUI app ( |
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
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.
Transient clipboard contention no longer drops an otherwise successful screenshot automation.
The desktop host now retries failed image clipboard writes with a short, bounded exponential backoff. Raw files and rendered project outputs share the same path. Project rendering happens once; each attempt only rebuilds clipboard image data. The clipboard lock is released before waiting, so unrelated operations are not held behind the backoff.
This follows a transient Windows clipboard ownership failure observed in production, where an immediate retry succeeded. A focused test covers the retry bounds, and the existing source-selection tests remain unchanged.
Rust formatting and diff checks pass. Local Cargo tests did not start because Git Bash exited the Visual Studio environment wrapper before Cargo; upstream CI is the compile and test gate. No native clipboard acceptance run was performed for this branch.

Confidence Score: 5/5
The reviewed changes appear safe to merge, with no actionable defect found.Summary
Screenshot automation now retries failed clipboard image writes up to four times.
The previous and current commits have different merge bases, so this review used the full PR diff. Previous review threads were not supplied and could not be retrieved. No Cargo tests or native clipboard checks were run during this review.
Reviews (2) · Last reviewed commit: "Merge branch 'main' into fix/retry-clipb..." · Reviewed by Greptile