Repository navigation
perf(desktop-gpui): bound capped screenshot scans like recordings #2753
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Open
celeroncoder
wants to merge
3
commits into
CapSoftware:main
Choose a base branch
from
celeroncoder:perf/gpui-bounded-screenshot-and-recovery-scans
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
+190
−49
Open
Changes from all commits
Commits
Show all changes
3 commits
Select commit
Hold shift + click to select a range
0fdb3ff
perf(desktop-gpui): bound capped screenshot scans like recordings
celeroncoder 34c4f1c
test(desktop-gpui): make the bounded screenshot test tolerate timesta…
celeroncoder 1e66bc0
Merge branch 'main' into perf/gpui-bounded-screenshot-and-recovery-scans
richiemcilroy File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
If the temporary filesystem has timestamp precision coarser than 6 ms, consecutive PNGs can share a timestamp despite the sleeps. The strict
>assertion then fails even when the listing is correct. The assertions that the hard-linked pair occupies the first two positions have the same dependency.Use controlled sort times, or allow other ties and locate the hard-linked pair by path.
Prompt To Fix With AI
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Fixed in 34c4f1c.
set_modifiedis not an option here because the sort key preferscreated(), so the test now tolerates ties instead: the hard-linked pair is located by bundle path and must share a timestamp, and every adjacent pair in the listing must be strictly newer-to-older or, on equal timestamps, keepread_dirorder (the stable-sort property the production code relies on). The assertions that assumed the sleeps produce distinct times (legacylast, the pair at positions 0-1, the strict>chain) are gone; the equivalence with the old listing, thetake(K)prefix loop and the laziness check are unchanged. The pair is deliberately not asserted adjacent, since on a coarse filesystem a third bundle could share the timestamp and sit between them in directory order.Fix written by Claude Opus 5.5, reviewed by DeepSeek V4.1 Flash and Gemini 3.8 Flash.