Fix timeout error message race condition for ENG-3372#2144
Merged
Conversation
- Check if using default timeout vs user-specified timeout - Show 'Scrape timed out' for user timeouts - Show 'Scrape timed out due to maximum length of 5 minutes' for default timeout - Fixes race condition where fallback timeout was always showing 5-minute message Co-Authored-By: mogery <mo.geryy@gmail.com>
Contributor
Author
🤖 Devin AI EngineerI'll be helping with this pull request! Here's what you should know: ✅ I will automatically:
Note: I can only respond to comments from users who have write access to this repository. ⚙️ Control Options:
|
mogery
approved these changes
Sep 15, 2025
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.
Fix timeout error message race condition for ENG-3372
Summary
Fixes a race condition where users were incorrectly seeing "Scrape timed out due to maximum length of 5 minutes" during user-specified timeouts instead of the expected "Scrape timed out" message.
The issue occurred in the Promise.race fallback timeout handler in
scrapeURLLoop, which was always using the 5-minute message regardless of whether a user had specified their own timeout. The fix adds a conditional check to determine if we're using the default timeout vs a user-specified timeout and displays the appropriate message.Changes:
usingDefaultTimeoutcheck based onmeta.abort.scrapeTimeout() === undefinedReview & Testing Checklist for Human
Notes
meta.abort.scrapeTimeout() === undefinedreliably indicates default timeout usageLink to Devin run: https://app.devin.ai/sessions/0ab061541606484dae4b2df909405ffb
Requested by: @mogery
Summary by cubic
Fixes a race condition that showed the wrong timeout message during scrapes, addressing ENG-3372. User-set timeouts now show “Scrape timed out,” while default timeouts still show the 5-minute message.