-
Notifications
You must be signed in to change notification settings - Fork 1.3k
update screenshot collector stop method #1425
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
Conversation
|
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.
No issues found across 21 files
Greptile OverviewGreptile SummaryFixed a bug where the final screenshot was not being captured before the
Confidence Score: 5/5
Important Files ChangedFile Analysis
Sequence DiagramsequenceDiagram
participant EvalTask
participant ScreenshotCollector
participant Page
EvalTask->>ScreenshotCollector: start()
loop Every interval
ScreenshotCollector->>Page: screenshot()
Page-->>ScreenshotCollector: Buffer
end
EvalTask->>ScreenshotCollector: await stop()
ScreenshotCollector->>ScreenshotCollector: clearInterval()
ScreenshotCollector->>Page: await screenshot() (final)
Page-->>ScreenshotCollector: Buffer
ScreenshotCollector-->>EvalTask: Buffer[]
|
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.
21 files reviewed, no comments
why
Currently, we do not await the final screenshot when stop method is called, resulting in missing screenshots within the screenshot collector
what changed
changed stop be async, and added await to stop method calls
test plan
Summary by cubic
Make ScreenshotCollector.stop async and wait for the final screenshot so journeys include the last frame. Updated all agent tasks to await stop to prevent missing screenshots.
Bug Fixes
Migration
Written for commit fbdb1bb. Summary will update automatically on new commits.